TSM Error Codes

IBM Tivoli Storage Manager
Version 6.3.3
Server Messages and Error Codes
SC27-2877-03
IBM Tivoli Storage Manager

Version 6.3.3
Server Messages and Error Codes
SC27-2877-03
Note:
Before using this information and the product it supports, read the information in Notices on page 761.
This edition applies to Version 6.3.3 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 or technical
newsletters. This edition replaces SC27-2877-02.
Copyright IBM Corporation 1995, 2012.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v
About this publication . . . . . . . . vii
Who should read this publication . .
Publications . . . . . . . . .
Tivoli Storage Manager publications
Support information . . . . . . .
Getting technical training . . . .
Searching knowledge bases . . .
Contacting IBM Software Support .
.
.
.
.
.
.
.
.
.
.
.
.
. vii
. vii
. vii
. . . . . x
. . . . . x
. . . . . x
. . . . . xii
Chapter 1. Introduction to messages . . 1

Tivoli Storage Manager server and client messages
format . . . . . . . . . . . . . . .
Interpreting return code messages . . . . . .
Example one for QUERY EVENT command . .
Example two for DEFINE VOLUME command .
.
.
.
.
1
2
3
3
Chapter 2. ANE: Client events logged to

the server version 6.3 . . . . . . . . . 5
ANE messages changes from version 6.2.0 to version
6.3.0 . . . . . . . . . . . . . . . . . 5
Version 6.3.0 new ANE messages . . . . . . 5
Version 6.3.0 changed ANE messages . . . . . 8
ANE messages that are deleted at version 6.3.0
10
Version 6.3.0 ANE messages . . . . . . . . . 10
Version 6.3.1 ANE new and changed messages . . 44
Version 6.3.0 ANR messages . . . . . . . .

Version 6.3.1 ANR new and changed messages .
Version 6.3.3 ANR new messages . . . . .
Version 6.3.3 ANR changed messages . . .
ANR messages that are deleted at version 6.3.3
.
.
.
.
.
. 57
716
717
719
719
733
745
Chapter 4. Descriptions of I/O codes

in server messages . . . . . . . . . 747
Completion code and operation code values
overview . . . . . . . . . . . . . .
Device drivers completion codes: Common
codes . . . . . . . . . . . . . .
Device drivers completion codes: Media
changers . . . . . . . . . . . . .
Device drivers completion codes: Tape and
optical drives . . . . . . . . . . .
Device drivers operation codes: Tape library
devices . . . . . . . . . . . . .
Descriptions of standard ASC and ASCQ codes .
ASC and ASCQ codes in Windows Event Log
. 748
. 748
. 749
. 750
. 752
. 752
755
Chapter 5. Device error codes in the

AIX system error log . . . . . . . . 757
Appendix. Accessibility features for
the Tivoli Storage Manager product
family. . . . . . . . . . . . . . . 759
Chapter 3. ANR: Server common and

platform-specific messages version 6.3 49
Notices . . . . . . . . . . . . . . 761
Changes from version 6.2.0 to version 6.3.0 .

Version 6.3.0 ANR new messages . . .
Version 6.3.0 ANR changed messages. .
ANR messages that are deleted at version
Glossary . . . . . . . . . . . . . 765
Copyright IBM Corp. 1995, 2012
. .
. .
. .
6.3.0
. 49
. 49
. 53
56
Trademarks .
. 763
iii
iv
IBM Tivoli Storage Manager: Server Messages and Error Codes
Tables
1.
2.
3.
4.
5.
6.
Tivoli Storage Manager server publications

vii
Tivoli Storage Manager storage agent
publications . . . . . . . . . . . . viii
Tivoli Storage Manager client publications
viii
Tivoli Storage Manager data protection
publications . . . . . . . . . . . . ix
IBM Tivoli Storage Manager troubleshooting
and tuning publications . . . . . . . . ix
Version 6.3.3 changed messages summary
733
7.
8.
9.
10.
11.
Completion code values common to all

device classes . . . . . . . . . .
Completion code values for media changers
Completion code values for tape and optical
drives . . . . . . . . . . . . .
Operation code values for tape library
devices. . . . . . . . . . . . .
Descriptions of standard ASC and ASCQ
codes . . . . . . . . . . . . .
. 748
749
. 750
. 752
. 752
vi
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
Tivoli Storage Manager components.
Publications
Publications for the IBM 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 all publications, go to the Tivoli Storage Manager information center at
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3.
You can download PDF versions of publications from the Tivoli Storage Manager
information center or from the IBM Publications Center at http://www.ibm.com/
shop/publications/order/.
Go to Tivoli Documentation Central to find information centers that contain official
product documentation for current and previous versions of Tivoli products,
including the Tivoli Storage Manager product family. You can find Tivoli
Documentation Central at https://www.ibm.com/developerworks/wikis/display/
tivolidoccentral/Home.
You can also order some related publications from the IBM Publications Center
website at http://www.ibm.com/shop/publications/order/. The website provides
information about ordering publications from countries other than the United
States. In the United States, you can order publications by calling 1-800-879-2755.
Tivoli Storage Manager publications

The following tables list the publications that make up the Tivoli Storage Manager
library.
Table 1. Tivoli Storage Manager server publications
Publication title
Order number
IBM Tivoli Storage Manager for AIX Installation Guide
GC23-9781
IBM Tivoli Storage Manager for AIX Administrator's Guide
SC23-9769
IBM Tivoli Storage Manager for AIX Administrator's Reference
SC23-9775
vii
Table 1. Tivoli Storage Manager server publications (continued)

Publication title
Order number
IBM Tivoli Storage Manager for HP-UX Installation Guide
GC23-9782
IBM Tivoli Storage Manager for HP-UX Administrator's Guide
SC23-9770
IBM Tivoli Storage Manager for HP-UX Administrator's Reference
SC23-9776
IBM Tivoli Storage Manager for Linux Installation Guide
GC23-9783
IBM Tivoli Storage Manager for Linux Administrator's Guide
SC23-9771
IBM Tivoli Storage Manager for Linux Administrator's Reference
SC23-9777
IBM Tivoli Storage Manager for Oracle Solaris Installation Guide
GC23-9784
IBM Tivoli Storage Manager for Oracle Solaris Administrator's Guide
SC23-9772
IBM Tivoli Storage Manager for Oracle Solaris Administrator's Reference
SC23-9778
IBM Tivoli Storage Manager for Windows Installation Guide
GC23-9785
IBM Tivoli Storage Manager for Windows Administrator's Guide
SC23-9773
IBM Tivoli Storage Manager for Windows Administrator's Reference
SC23-9779
IBM Tivoli Storage Manager for z/OS Media Installation and User's
Guide
SC27-4018
IBM Tivoli Storage Manager Upgrade and Migration Guide for V5

Servers
GC27-4017
IBM Tivoli Storage Manager Integration Guide for Tivoli Storage

Manager FastBack
SC27-2828
Table 2. Tivoli Storage Manager storage agent publications

Publication title
Order number
IBM Tivoli Storage Manager for SAN for AIX Storage Agent User's
Guide
SC23-9797
IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent User's
Guide
SC23-9798
IBM Tivoli Storage Manager for SAN for Linux Storage Agent User's
Guide
SC23-9799
IBM Tivoli Storage Manager for SAN for Oracle Solaris Storage Agent
User's Guide
SC23-9800
IBM Tivoli Storage Manager for SAN for Windows Storage Agent User's
Guide
SC23-9553
Table 3. Tivoli Storage Manager client publications

Publication title
Order number
IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive

Clients Installation and User's Guide
SC23-9791
IBM Tivoli Storage Manager for Windows: Backup-Archive Clients

Installation and User's Guide
SC23-9792
IBM Tivoli Storage Manager Using the Application Programming

Interface
SC23-9793
IBM Tivoli Storage Manager for Space Management for UNIX and Linux: SC23-9794
Users Guide
IBM Tivoli Storage Manager HSM for Windows Administration Guide
viii
SC23-9795
Table 4. Tivoli Storage Manager data protection publications

Publication title
Order number
IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft
SQL Server Installation and Users Guide
GC27-4010
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for SC27-4019
UNIX and Linux Installation and Users Guide
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for SC27-4020
Windows Installation and Users Guide
IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft
Exchange Server Installation and Users Guide
GC27-4009
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino SC27-4021
UNIX and Linux Installation and Users Guide
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino
for Windows Installation and Users Guide
SC27-4022
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data

Protection for SAP Installation and Users Guide for DB2
SC33-6341

Protection for SAP Installation and Users Guide for Oracle
SC33-6340
IBM Tivoli Storage Manager for Virtual Environments Installation and

Users Guide
SC27-2898
IBM Tivoli Storage Manager for Microsoft SharePoint Guide
N/A
Table 5. IBM Tivoli Storage Manager troubleshooting and tuning publications

Publication title
Order number
IBM Tivoli Storage Manager Problem Determination Guide
GC23-9789
IBM Tivoli Storage Manager Performance Tuning Guide
GC23-9788
IBM Tivoli Storage Manager Client Messages and Application

Programming Interface Return Codes
SC27-2878
IBM Tivoli Storage Manager Server Messages and Error Codes
SC27-2877
IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft
Exchange Server Messages
GC27-4011
IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft
SQL Server Messages
GC27-4012
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle
Messages
SC27-4014
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino
Messages
SC27-4015

Protection for SAP Messages
SC27-4016
Note: You can find information about IBM System Storage Archive Manager at
the Tivoli Storage Manager v6.3.0 information center.
ix
Support information
You can find support information for IBM products from various sources.
Start at the IBM Support Portal: 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.
Getting technical training

Information about Tivoli technical training courses is available online.
Go to the following websites to sign up for training, ask questions, and interact
with others who use IBM storage products.
Tivoli software training and certification
Choose from instructor led, online classroom training, self-paced Web
classes, Tivoli certification preparation, and other training options at
http://www.ibm.com/software/tivoli/education/
Tivoli Support Technical Exchange
Technical experts share their knowledge and answer your questions in
webcasts at http://www.ibm.com/software/sysmgmt/products/support/
supp_tech_exch.html.
Storage Management community
Interact with others who use IBM storage management products at
http://www.ibm.com/developerworks/servicemanagement/sm/
index.html
Global Tivoli User Community
Share information and learn from other Tivoli users throughout the world
at http://www.tivoli-ug.org/.
IBM Education Assistant
View short "how to" recordings designed to help you use IBM software
products more effectively at http://publib.boulder.ibm.com/infocenter/
ieduasst/tivv1r0/index.jsp
Searching knowledge bases

If you have a problem with your Tivoli Storage Manager family product, there are
several knowledge bases that you can search.
Begin by searching the Tivoli Storage Manager Information Center at
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3. From this website, you can
search the current Tivoli Storage Manager documentation.
Searching the Internet

If you cannot find an answer to your question in the IBM 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 including:
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.
If you still cannot find a solution to the problem, you can search forums and
newsgroups on the Internet for the latest information that might help you find
problem resolution.
An independent user discussion list, ADSM-L, is hosted by Marist College. You can
subscribe by sending 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.
To share your experiences and learn from others in the Tivoli Storage Manager and
Tivoli Storage FlashCopy Manager user communities, go to Service Management
Connect (http://www.ibm.com/developerworks/servicemanagement/sm/
index.html). From there you can find links to product wikis and user communities.
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.
To learn about which products are supported, go to the IBM Support Assistant
download web page at http://www.ibm.com/software/support/isa/
download.html.
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 at the IBM Support Assistant website:
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.
xi
Finding product fixes

A product fix to resolve your problem might be available from the IBM software
support website.
You can determine what fixes are available by checking the IBM software support
website at http://www.ibm.com/support/entry/portal/.
v If you previously customized the site based on your product usage:
1. Click the link for your product, or a component for which you want to find a
fix.
2. Click Downloads, and then click Fixes by version.
v If you have not customized the site based on your product usage, click
Downloads and search for your product.
Receiving notification of product fixes

You can receive notifications about fixes, flashes, upgrades, and other news about
IBM products.
To sign up to receive notifications about IBM products, follow these steps:
1. From the support page at http://www.ibm.com/support/entry/portal/, click
Sign in to create, manage, or view your subscriptions in the Notifications
pane.
2. 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.
3. Click Manage all my subscriptions in the Notifications pane.
4. Click the Subscribe tab and then click Tivoli.
5. Select the products for which you want to receive notifications and click
Continue.
6. 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.
To obtain help from IBM Software Support, complete the following steps:
1. Ensure that you have completed the following prerequisites:
a. Set up a subscription and support contract.
b. Determine the business impact of your problem.
c. Describe your problem and gather background information.
2. Follow the instructions in Submitting the problem to IBM Software Support
on page xiv.
xii
Setting up a subscription and support contract

Set up a subscription and support contract. The type of contract that you need
depends on the type of product you have.
For IBM distributed software products (including, but not limited to, IBM Tivoli,
Lotus, and Rational products, as well as IBM DB2 and IBM WebSphere
products that run on Microsoft Windows or on operating systems such as AIX or
Linux), 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: 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 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.
xiii
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 the telephone number to call in your country, go to the IBM Software
Support Handbook at http://www14.software.ibm.com/webapp/set2/sas/
f/handbook/home.html and click Contacts.
xiv
Chapter 1. Introduction to messages

This information contains explanations and suggested actions for messages issued
by IBM Tivoli Storage Manager products and components.
This introduction contains information to help you understand the messages.
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 documented.
Messages 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 Managerprovides 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
v
v
v
When client sessions start or end

When migration starts or ends
When backed up files are expired from server storage
Any output generated from background processes
See the IBM Tivoli Storage Manager Administrator's Guide for more information
about activity logs.
Tivoli Storage Manager server and client messages format

IBM 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 letters give an indication of the severity
of the action that generated the message. The severity codes and their meanings
are as follows:
S
Severe
Error
Warning
The product or a product function cannot continue. User

response is required.
An error is encountered during processing. Processing might
stop. User response might be required.
Processing continues, but problems might occur later as a
result of the warning.
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 accessible only in documentation.
The image below presents a typical Tivoli Storage Manager server message.
The callouts on the right of the image 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
available for normal operation.
Explanation
System Action: Server completes installation

processing.
System Action
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.
Example one for QUERY EVENT command
Example two for DEFINE VOLUME command
Chapter 1. Introduction to messages
Chapter 2. ANE: Client events logged to the server version 6.3

This section contains ANE messages for the Tivoli Storage Manager server version
6.3. All messages with ANE prefix are client events logged to the server.
Version 6.3.0 ANE messages that are new, changed, or deleted since version 6.2.0
are listed in one section. All version 6.3.0 ANE messages are documented in
another section.
ANE messages changes from version 6.2.0 to version 6.3.0

The following version 6.3.0 ANE server messages are new, changed, or deleted
since version 6.2.0. Only the message ID is listed.
Version 6.3.0 new ANE messages

The following version 6.3.0 ANE server messages are new since version 6.2.0. Only
the message ID is listed.
v
v
v
v
v
ANE4039E
ANE4050W
ANE4051E
ANE4052E
ANE4053E
v ANE4054E
v ANE4055E
v
v
v
v
v
v
v
ANE4077E
ANE4081E
ANE4082I
ANE4083I
ANE4084E
ANE4085I
ANE4086W
v
v
v
v
v
ANE4087I
ANE4088I
ANE4089W
ANE4090I
ANE4091I
v ANE4099E
v ANE4100I
v ANE4101I
v ANE4102I
v ANE4103I
v ANE4104I
v ANE4105I
v ANE4106I
v ANE4107I
v
v
v
v
v
ANE4108I
ANE4109I
ANE4110I
ANE4111I
ANE4112I
v
v
v
v
v
v
v
ANE4113I
ANE4114I
ANE4115I
ANE4116I
ANE4117I
ANE4118I
ANE4119I
v
v
v
v
v
v
ANE4120I
ANE4121I
ANE4122I
ANE4123I
ANE4124I
ANE4125I
v ANE4126I
v ANE4127I
v ANE4128I
v
v
v
v
ANE4129I
ANE4130I
ANE4131I
ANE4132I
v ANE4133I
v ANE4134I
v ANE4135I
v
v
v
v
v
ANE4136I
ANE4137I
ANE4138I
ANE4139I
ANE4140I
v ANE4141I
v ANE4142I
v
v
v
v
v
v
v
ANE4143I
ANE4144I
ANE4145I
ANE4146I
ANE4147I
ANE4148E
ANE4149I
v ANE4150E
v ANE4151E
v ANE4152E
v
v
v
v
v
ANE4153E
ANE4154E
ANE4155E
ANE4156E
ANE4157I
v
v
v
v
v
v
v
ANE4158I
ANE4159E
ANE4160E
ANE4161E
ANE4162E
ANE4163I
ANE4164W
v
v
v
v
v
v
ANE4165E
ANE4166E
ANE4167E
ANE4168E
ANE4169E
ANE4170E
v ANE4171E
v ANE4172I
v ANE4173I
v
v
v
v
ANE4174E
ANE4175I
ANE4176I
ANE4177E
v ANE4198I
v ANE4199W
v ANE4251W
v
v
v
v
v
ANE4254E
ANE4255E
ANE4256E
ANE4257E
ANE4258E
v ANE4259E
v ANE4260E
v
v
v
v
v
v
v
ANE4261E
ANE4262E
ANE4263E
ANE4264E
ANE4265I
ANE4266I
ANE4267I
v ANE4268I
v ANE4269W
v ANE4270I
v
v
v
v
v
ANE4271E
ANE4272E
ANE4273E
ANE4274E
ANE4275E
v
v
v
v
v
v
v
ANE4276E
ANE4277E
ANE4278E
ANE4279I
ANE4280E
ANE4281E
ANE4282E
v
v
v
v
v
v
ANE4283E
ANE4284E
ANE4901E
ANE4939I
ANE4942E
ANE4943I
v ANE4975I
v ANE4976I
v ANE4977I
v
v
v
v
ANE4978I
ANE4979I
ANE4980I
ANE4981I
v ANE4982I
v ANE4983I
v ANE4984I
v ANE4997E
v ANE4998E
Version 6.3.0 changed ANE messages

The following version 6.3.0 ANE server messages are changed since version 6.2.0.
In addition to the message number, the message element that has changed is listed.
Message Number
ANE4000E
ANE4001E
ANE4002E
ANE4003E
ANE4004E
ANE4005E
ANE4006E
ANE4007E
ANE4009E
ANE4011E
ANE4012E
ANE4013E
Change
Message
Message
Message
Message
Message
Message
Message
Message
Message
Message
Message
Message
text,
text,
text,
text,
text
text,
text,
text
text,
text
text,
text
explanation, system action, user response

system action
explanation
system action, user response
Message Number Change

ANE4014E
Message text (in casing or blank spaces only), explanation, system
action, user response
ANE4015E
Message text, explanation, system action, user response
ANE4016E
Message text
ANE4017E
Message text
ANE4018E
Message text, explanation, user response
ANE4019E
Message text, system action
ANE4020E
ANE4021E
Message text, user response
ANE4022E
ANE4023E
Message text
ANE4024E
Message text
ANE4025E
Message text, explanation
ANE4026W
System action
ANE4028E
Message text
ANE4029E
ANE4030E
Message text
ANE4031E
ANE4032E
Message text
ANE4033E
ANE4034E
ANE4035W
ANE4036E
Explanation, user response
ANE4037E
Message text, system action, user response
ANE4040E
Explanation, system action
ANE4041W
ANE4042E
Message text
ANE4043
Message type, and Not previously documented
ANE4044E
Message text (in casing or blank spaces only)
ANE4046E
Explanation
ANE4047E
ANE4048W
System action, user response
ANE4049I
Explanation, system action, user response
ANE4201
ANE4203
ANE4205
ANE4207
ANE4208E
Message text
ANE4209
ANE4211
ANE4212E
Explanation
ANE4216E
Message text
ANE4220E
ANE4223E
Message text
ANE4224
ANE4233
ANE4297W
ANE4298E
ANE4299E
ANE4900W
ANE4940
ANE4941
ANE4951
ANE4952
ANE4000E
Message Number
ANE4953
ANE4954
ANE4955
ANE4956
ANE4957
ANE4958
ANE4959
ANE4960
ANE4961
ANE4961
ANE4963
ANE4964
ANE4965
ANE4966
ANE4967
ANE4968
ANE4969
ANE4970
ANE4971
ANE4972
ANE4974E
ANE4985
ANE4986
ANE4987E
ANE4988W
ANE4989E
ANE4990
ANE4991I
ANE4992W
ANE4993E
ANE4994S
ANE4995
ANE4996
ANE4999
Change
Explanation
Message text, explanation, system action
Message type, message text, explanation, system action, user response
ANE messages that are deleted at version 6.3.0

No ANE messages are deleted at version 6.3.0.
Version 6.3.0 ANE messages

Tivoli Storage Manager server version 6.3.0 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.
ANE4000E
Error processing 'filespace-name': file

space does not exist.
Explanation: The specified file space (domain) is

incorrect or does not exist on the workstation. If the
message results from the BACKUP IMAGE command
with the -MODE=INCREMENTAL option, it means that
you have entered the name of a raw logical volume.
10
The MODE=INCREMENTAL option is not valid for

raw logical volumes.
System action: Processing stops.
User response: Try the operation again, specifying an
existing domain (drive letter or file system name). If
the message resulted from improper use of the
ANE4001E ANE4008E
MODE=INCREMENTAL option, try the command
again, omitting that option.
ANE4001E
The file space for domain 'filespace-name'

could not be found on the TSM server.
Explanation: The specified file space was expected to

be found on the server, but it no longer exists. It is
possible that a command was issued to delete the file
space from the server while the current operation was
in progress.
System action: TSM processing stops.
User response: Try the operation again. If the problem
recurs, check the error log for any other messages that
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
further assistance.
ANE4002E
Error processing 'filespace-name': volume

label does not exist
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: 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
volume label, and retry the operation.
ANE4003E
Error processing 'filespace-name':

duplicate volume label encountered
Explanation: The selected drive has a duplicate

volume label. Because TSM uses the volume label to
keep track of backup/archive information, it cannot
back up or archive files from a drive with a duplicate
volume label.
System action: TSM cannot select the drive.
User response: If the volume needs to be available to
the system, exit TSM, and assign a volume label to the
drive. Restart TSM and retry the operation.
ANE4004E
Error processing 'filespace

namepath-namefile-name': destination file
or directory is write locked
ANE4005E

namepath-namefile-name': file not found
Explanation: The file being processed for backup,

archive or migrate no longer exists on the client.
Another process deletes the file before it can be backed
up, archived or migrated by TSM.
System action: File skipped.
User response: None.
ANE4006E

namepath-namefile-name': directory path
not found
Explanation: The operating system returned a "path

not found" status when IBM Tivoli Storage Manager
attempted to access the directory. You either have
specified a directory that does not exist, as shown in
the message (path-name), or the directory being
processed no longer exists on the client because another
process deleted it before it could be backed up or
archived by IBM Tivoli Storage Manager.
System action: The directory is skipped, processing
continues
User response: Recheck all spelling and punctuation,
particularly the placement of directory delimiters (for
example, "\"). Correct the syntax if it is incorrect, then
retry the operation. Ensure that the path is specified
correctly and that the directory actually exists. Retry
the command with the corrected path and directory
name. If you cannot correct the directory name, use the
Exclude option to exclude the directory from the
operation.
ANE4007E

namepath-namefile-name': access to the
object is denied
Explanation: Access to the specified file or directory is

denied. You tried to read from or write to a file and
you do not have access permission for either the file or
the directory.
System action: Processing stopped.
User response: Ensure that you specified the correct
file or directory name, correct the permissions, or
specify a new location.
Explanation: The file or directory being restored or

retrieved from the server cannot be written to because
the destination is write locked. Another operation
might have the file open and will not allow it to be
updated.
ANE4008E
User response: Either determine which operation has

the file write locked, or restore the file to another name
or location.
User response: Check and see if file is locked by other

process. If not, retry the command.

namepath-namefile-name': file is
temporarily unavailable
Explanation: File is temporarily unavailable.
11
ANE4009E ANE4017E
ANE4009E

namepath-namefile-name': disk full
condition
Explanation: No more files can be restored or

retrieved because the destination disk is full.
System action: The client prompts you for action:
ANE4013E

namepath-namefile-name': invalid file
handle
Explanation: An internal system error occurred. A file

operation failed because an invalid file handle was
passed.
v Retry this object
v Skip this object
User response: Report the problem to your system

administrator, and then retry the operation.
v Abort the action

User response: Select the appropriate action for this
object. Create some free space on the destination disk
before you retry the operation. Another option is to
restore or retrieve the file to another disk.
ANE4010E

namepath-namefile-name': stale NFS handle
Explanation: An NFS file system becomes stale.

System action: File system skipped.
ANE4014E

namepath-namefile-name': unknown system
error (error-code) encountered. Program
ending.
Explanation: An unrecognized and unexpected

error-code occurred within the client program. This is a
programming failure and the client program ends.
System action: processing stops.
User response: Check the NFS mounted filesystem.

continues, report the error to your TSM administrator.
ANE4011E
ANE4015E

namepath-namefile-name': no file handles
available
Explanation: All file handles for your system are

currently in use. No more are available.
User response: Either free some file handles by ending
other processes, or modify your system setup to allow
for more files to be open at the same time.
ANE4012E
'filespace namepath-namefile-name' already

exists. It will be skipped.
Explanation: The client tried to restore or retrieve the

specified file, but the file already existed in the target
restore location and the user chose not to replace the
existing file.
System action: The file is skipped, a message is
logged in dsmerror.log, and restore or retrieve
processing continues with the next object.
User response: The file was skipped because either
REPLACE NO was in effect, causing all existing files
and directories to be skipped, or REPLACE PROMPT
was in effect, and when prompted, the user chose to
skip this file or all existing directories and files. No
additional action is necessary if the decision to skip the
file was deliberate. Otherwise the operation can be
retried using either REPLACE ALL REPLACE
PROMPT.

namepath-namefile-name': unexpected TSM
error (error-code) encountered
Explanation: An unexpected error occurred. This

might be a low-level system or communication error
that TSM cannot handle or recover from.
continues, look for other indications of system
problems to determine where the problem exists. Most
systems have error or event logs which may contain
additional information. See your system administrator
or TSM administrator for further help.
ANE4016E

namepath-namefile-name': file is being
executed; write permission denied
Explanation: The current file cannot be opened to

write to because it is currently being run by another
operation.
User response: Stop the operation that is running the
file and retry the operation, or restore or retrieve the
file to a different name or directory.
ANE4017E

namepath-namefile-name': too many
symbolic links were detected while
resolving name
Explanation: While trying to resolve the file name, too
12
ANE4018E ANE4025E
many symbolic links were found.
ANE4021E

User response: Ensure that you do not have a looping
symbolic link for the file.
ANE4018E

namepath-namefile-name': file name too
long
Explanation: The file name specified is too long to be

handled by TSM.
Explanation: The file system/drive was not ready for

access.
User response: Ensure that the drive is available to
TSM, and then retry the operation.
ANE4022E
System action: File is skipped.

User response: See the appropriate Using the
Backup-Archive Client book for the particular operating
system, for the file names that are handled by TSM.
ANE4019E

namepath-namefile-name': file system is
locked by system
Explanation: File system cannot be accessed because it

is locked by the system.

namepath-namefile-name': file system not
ready

namepath-namefile-name': file system is
invalid.
Explanation: The drive was not available for access.

User response: Ensure that the drive is operational,
and then try the operation again. If this is unsuccessful,
check the error log.
ANE4023E
System action: TSM cannot complete the operation.

namepath-namefile-name': file input/output
error
User response: See your system administrator.
Explanation: An error was found while reading from

or writing to the file.
ANE4020E
The data format for object 'filespace

namepath-namefile-name' is unknown. The
unknown format usually occurs when
the file was backed up or archived by a
later version of IBM Tivoli Storage
Manager.
Explanation: When a file is backed up or archived,

IBM Tivoli Storage Manager includes some additional
information about the file. This message is issued if
IBM Tivoli Storage Manager cannot recognize the
information during a restore or retrieve operation. The
most likely cause is that the file was backed up or
archived with a newer version of IBM Tivoli Storage
Manager. If the file was backed up from a
case-preserving but not case-sensitive file system, the
file name might be displayed with incorrect casing. The
incorrect casing does not otherwise affect processing
since the file is skipped.
System action: The file is not restored or retrieved.
Processing continues with the next file.
User response: Try the restore or retrieve operation
again with a current version of the IBM Tivoli Storage
Manager client software. If the problem persists, contact
IBM technical support for further assistance.
User response: Check your system to ensure that it is

operating properly. For OS/2, run CHKDSK /F for the
failing drive which can be found in dsmerror.log.
ANE4024E

namepath-namefile-name': file write error
Explanation: An error was found while writing to the

file.
operating properly.
ANE4025E

namepath-namefile-name': file exceeds user
or system file limit
Explanation: A file being backed up/restored or

archived/retrieved exceeds system set limits for this
user. Shown below are the filesize limits corresponding
to various platforms.
AIX
68,589,453,312 (64GB)
HP-UX 1,099,511,627,775 (1TB-1)

Linux
2,147,483,647 (2GB)
Mac pre-OS9
2,147,482,624 (2GB-1K)
13
ANE4026W ANE4031E
Mac OS9
18,446,744,073,709,551,616 (16EB)
NetWare
4,294,963,200 (4GB -4KB)
NUMA-Q DYNIX/ptx
4.5 1,095,216,660,480 (1TB-4GB)

User response: Ensure that you have the proper
authorization to create the directory for file being
restored or retrieved.
ANE4029E
OS/390 4,294,967,295 (4GB)

SGI
18,446,744,073,709,551,615 (16EB-1)
Solaris 2.6 or higher

1,099,511,627,775 (1TB-1)
Tru64 UNIX
1,099,511,627,776 (1TB)
UnixWare
2,147,483,647 (2GB)
Windows ME (FAT32)
4,294,967,295 (4GB)
Windows NT/2000 (NTFS)
17,592,185,978,880 (16TB-64K)
User response: Ensure that the system limits are set
properly.
ANE4026W

namepath-namefile-name': size of 'file-size'
exceeded the maximum file size limit on
your system
Explanation: You tried to restore or retrieve a file that

has exceeded the maximum file size limitation on your
system.
System action: TSM cannot restore or retrieve the file.
User response: Restore or retrieve this file on a system
that supports the file size. See your system
administrator.
ANE4027S

namepath-namefile-name': internal program
message 'value' encountered

namepath-namefile-name': unable to build
a directory path; a file exists with the
same name as a directory
Explanation: TSM tried to create a directory path, but

is unable to because a file exists that has the same
name as a directory.
User response: Remove the file that has the same
name as the directory. Refer to the last restore/retrieve
operation and check all directories along the path.
ANE4030E

namepath-namefile-name': disk space limit
for this process reached
Explanation: The disk space allocated for the client

owner is full.
User response: Free up disk space and retry the
restore or retrieve operation.
ANE4031E
Error processing
'file_space_namepath_namefile_name'. Name
exceeds an internal TSM limit.
Explanation: During a file operation, TSM

encountered a filename where at least one component
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
confused with the operating system limits for
file_space_name, path_name or directory_name,
file_name.
Shown below are the TSM internal file name limits for
various platforms.
AIX HP-UX Solaris
File_space_name
Path_name or directory_name
File_name
1024
1023
256
User response: Retry the operation. If the problem

continues, see your system administrator or service
representative.
Linux
File_space_name
File_name
1024
768
256
ANE4028E
Windows XP/2000/2003
File_space_name
File_name
1024
248
248
Explanation: An unexpected catastrophic program

failure occurred, indicated by value.

namepath-namefile-name': cannot create
file/directory entry
Explanation: The directory path for files being

restored or retrieved cannot be created.
14
System action: The file is skipped.
ANE4032E ANE4039E
User response: Reduce the size of the filename so that
it is smaller that the TSM internal limits.
ANE4032E

namepath-namefile-name': file is not
compressed.
Explanation: A file that was flagged as compressed

was not compressed, and the system failed.
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
require several megabytes of free space. Also check the
Windows permissions on the ADSM.SYS staging
directory and ensure that the Windows user under
which you are running TSM has full access to that
directory and its contents.
ANE4037E
User response: See your system administrator to

report this problem. This error is a system failure.
ANE4033E

namepath-namefile-name': file compressed
on a different client machine that has
more memory
Explanation: You are trying to restore a file that was

backed up and compressed on another client
workstation that had more memory than your client
workstation. You cannot restore this file. When the file
is restored, it is expanded and your workstation does
not have enough memory.
Object 'file-namefile-namefile-name'
changed during processing. Object
skipped.
Explanation: The specified file-name was skipped

during backup, archive, or migrate because it was
changing during the attempt to process it.
System action: TSM skipped the object.
User response: If you want the file backed up,
archived, or migrated, retry the operation. If it fails,
determine why the object is being changed. For more
information on backing up, archiving, or migrating
changing objects, see your system administrator.
ANE4038E
System action: TSM canceled the operation.
An error occurred processing file system

'filespace name'.
User response: Obtain a machine with more memory

and retry the operation.
Explanation: File system 'filespace name' is corrupted or

contains one or more corrupted directories and cannot
be processed.
ANE4034E
System action: File system is skipped.

namepath-namefile-name': unknown system
error
Explanation: An unknown error occurred. This might

be a low-level system or communication error that TSM
cannot handle or recover from.

operating properly. For the Windows environment, run
CHKDSK utility for the failing drive. More information
about corrupted directories can be found in
dsmerror.log.

continues, determine where the problem exists. See
your system administrator for further help.
ANE4035W
File 'filespace namepath-namefile-name'

currently unavailable on server.

is currently not available from the TSM server.
System action: TSM Cannot restore or retrieve the file.
User response: Try to restore or retrieve after the file
was made available on the server. See your system
administrator.
ANE4036E
An error occurred saving the registry

key.
Explanation: The active registry key cannot be copied

to the ADSM.SYS staging directory.
System action: Registry backup operation terminates.
ANE4039E

namepath-namefile-name': compressed file
is corrupted and cannot be expanded.
Explanation: The compressed file cannot be expanded

correctly due to one of the following reasons:
v There is a problem on the tape.
v There is a communications problem.
v The compressed file was corrupted on the TSM
Server.
User response: 1) The compressed file is corrupted
because there is a problem on the tape. To know if this
is the problem, please issue the following command on
the TSM Server: audit volume <volume_name> fix=no
If there is any problem reported, you could move the
data from that volume to a new one (see command
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
corrupted during the transmission. If you use a gigabit
15
ANE4040E ANE4047E
ethernet adapter on the Server please upgrade the card
driver (AIX platform) or add provided by Oracle
suggested changes to some system network options
which have resolved this problem (Solaris platform). 3)
Please verify with your network support if during the
restore there are no any problems between the TSM
Client/Server that is originating the file corruption.
ANE4040E

namepath-namefile-name': file system
filespace name has exceeded its space
management quota.
Explanation: TSM detects that the file system has

exceeded its quota. No more data can be migrated out
of this file system.
ANE4044E
Explanation: While processing the specified file on the

workstation, another file name was encountered with a
similar name which only differed in case. The
Backup-Archive client does not allow names which
differ only in case on this platform and cannot
guarantee the integrity of the file, so the file is skipped.
System action: This object will be skipped.
User response: Rename the file in question to a
unique name.
ANE4045E
System action: TSM will not migrate files from this

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

namepath-namefile-name': Out of free space
or inodes in file system to migrate or
recall.
Explanation: The file system is full. No more free

space or free inodes are available to be allocated for the
transaction file that is needed when a file is being
migrated or recalled.
System action: TSM terminates the current operation
for this file system.
Object name 'filespace

namepath-namefile-name' contains one or
more unrecognised characters and is not
valid.
Explanation: The filename, directory name, or volume

label syntax is incorrect.
User response: You need to check the disk for errors.
ANE4043I
Total number of objects recalled: Number

of objects
Explanation: This message reports statistics or

information for a client operation performed to this
server. This is logged for informational purposes.
System action: Processing continues.
User response: None required.
16
Error processing 'filespace-namepathnamefile-name': Case-sensitive name

conflict exists. The directory tree will be
skipped.
Explanation: While processing the specified file on the

workstation, another object name was encountered with
a similar name which only differed in case. The
Backup-Archive client does not allow names which
differ only in case on this platform and cannot
guarantee the integrity of the file, so the directory and
all of the objects contained within it are skipped.
User response: Rename the file in question to a
unique name.
ANE4046E
User response: Remove some files in the file system,

and then run reconciliation. Retry the operation.
ANE4042E
Error processing 'filespace-namepathnamefile-name': Case-sensitive name

conflict exists.
There is an error processing

'filespace-namepath-namefile-name': the
object is corrupted and unreadable.
Explanation: You tried to read from or write to a file

or directory that is corrupted. The corrupted file is
skipped. If this is a directory, the objects contained in
the directory and its subdirectories are skipped.
User response: Check your system to ensure that the
filespace is not corrupted by using system tools like
chkdsk (Windows) or fsck (UNIX).
ANE4047E
There is a read error on

'file-namefile-namefile-name'. The file is
skipped.
Explanation: The specified file-name was skipped

during backup archive because the file could not be
read.
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
snapshot was created. This could cause the snapshot to
become invalid thereby preventing TSM client from
reading the snapshot.
ANE4048W ANE4053E
System action: TSM skipped the file.
ANE4051E

operating properly.
If you are performing a JFS2 snapshot based operation,
please use the default snapshotcachesize of 100% and
ensure that the volume group has sufficient disk space
to allocate snapshots at least as large as the file system
ANE4048W
LAN-Free connection failed.
Explanation: ENABLELANFREE option is set to YES

for this session, but an attempt to establish LAN-Free
connection failed.
System action: The TSM client will failover to non
LAN-Free support.

namepath-namefile-name': The decryption
option is in effect, but the user ID
under which back-up or archive is being
run is not authorized to decrypt this
encrypted-file-system (EFS) file.
Explanation: The file being processed is encrypted by

an encrypted file system (EFS). The option is specified
to back-up or archive the file in decrypted form. The
user ID under which the back-up or archive is being
run does not have decryption rights for this file.
User response: There are three possible ways to make
decryption work:
v Re-encrypt the file under the encryption key of a
group to which both the owner and the
back-up/archive user IDs belong
User response: Review the TSM error.log for

LAN-Free failures. Check your LAN-Free setup and
verify that all components are working properly.
v Add the back-up/archive user ID to the list of users

authorized to decrypt this file
ANE4049I
v Run the back-up or archive under the owner's user

ID, if possible
Established LAN-Free connection.
Explanation: ENABLELANFREE option is set to YES

for this session and the TSM client successfully
established LAN-Free connection with server, after the
LAN-Free connection was broken.
ANE4052E
System action: The TSM client will communicate with

the server via LAN-Free.
User response: Review the TSM error.log for
LAN-Free errors. Check your LAN-Free setup and
verify that all components are working properly.
ANE4050W
Scheduled action 'schedule-action' did not

execute for schedule 'schedule-name' as
the TSM administrator has been
disabled from executing the scheduled
action on the client.
Explanation: One or more of the client options schedcmddisabled, srvprepostscheddisabled,

srvprepostsnapdisabled, restretrscheddisabled, have
been set to YES on the client thereby preventing the
TSM administrator from executing one of the following
scheduled actions on the client - preschedule,
postschedule, presnapshot, postsnapshot or scheduled
operating system commands, restore or retrieve
operations.
System action: The scheduled operation will not be
executed and a message will be logged to TSM Server
indicating this.

namepath-namefile-name':
Encrypted-file-system (EFS) file cannot
be restored, because file system does
not support restore from the raw-EFS
back-up data, or possibly because the
restore function does not have write
access to the directory.

an encrypted file system (EFS). The file was backed up
in the raw encrypted format. Either the target
filesystem does not support the encrypted format, or
restore does not have write access to the directory to
which the file is to be restored.
System action: The restore is terminated.
User response:
v The file cannot be restored to this location if the file
system is not the AIX Enhanced Journaled File
System (JFS2)
v If the file is JFS2 but EFS is not enabled, then EFS
must be enabled before the file can be restored
v If the user ID under which restore is being run does
not have write permission for the directory, the
permissions must be changed or the restore must be
run under a different user ID
ANE4053E
Error processing 'filespace path filename':

The file cannot be restored because the
file system or operating system does not
support the Encrypting File System
(EFS) data.
Explanation: The specified object was backed-up as

17
ANE4054E ANE4082I
archive operation is attempted with a client V5.5 or
lower.
raw Encrypting File System (EFS) data. The client is

trying to restore or retrieve the object to a destination
that does not support the EFS data. The location might
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
ANE4077E
v EFS support has not been activated on the operating

system
v The target file system does not support the EFS data
System action: The object is not restored or retrieved.
Processing continues with the next object.
User response: If this file must be restored, restore it
to an AIX operating system environment supporting
EFS data.
ANE4054E

namepath-namefile-name': The encryption
key is not loaded.

an encrypted file system (EFS). The option is specified
to backup or archive the file in decrypted form. The
encryption key, required to decrypt the file, is not
loaded in the kernel keyring.
User response: There are three situations in which this
problem can occur:
v You just performed initial activation of EFS on the
AIX system, and have not logged out. AIX does load
the keys for the session running at the time of initial
activation. Solution: Logout and login again.
v The login password has been changed recently, and
you normally run with the EFS password the same
as the login password. AIX does not automatically
change the EFS password when you change the login
password. Solution: Issue 'efskeymgr -n' to set the
EFS password to be the same as the login password.
v You need to run the decrypting backup when the
EFS password is different from the login password.
Solution: Issue 'efskeymgr -o ksh' to launch a new
shell with the keys loaded. AIX will prompt you for
the EFS password as you launch the shell. Run the
backup from the new shell.
ANE4055E
Cannot update file space 'filespace-name':

the file space version on the TSM server
is not compatible with this client
Explanation: The file space on the TSM server is not

compatible with this client. This is caused by
performing a backup or archive operation with a client
and then using a down-level client and attempting a
backup or archive operation targeting the same file
space. This problem occurs specifically after a Windows
or AIX client V6.1 or higher performs a backup or
archive operation and then a subsequent backup or
18
File 'filespace namepath-namefile-name' is

encrypted by Microsoft EFS and
contains at least one sparse data stream.
The operating system does not support
restore for this file so it is not backed
up or restored.
Explanation: An error in the Microsoft Windows API

prevents successful restore of files that meet the
following conditions:
v The file is encrypted by Microsoft Encrypting File
System (EFS) at the time it was backed up
v The file includes at least one data stream (alternate
"named" stream or unnamed stream) that is sparse
v The operating system is any edition of Microsoft XP,
Microsoft Windows Server 2003, or Microsoft
Windows Server 2003 R2
Because the file cannot be restored, IBM Tivoli Storage
Manager does not back it up. The problem is
documented by Microsoft at http://
support.microsoft.com/kb/2525290.
System action: The file is not backed up or restored.
Processing continues with the next object or ends if
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.
v If a backup copy of the file is not necessary, you can
exclude it from backup.
ANE4081E
Error processing 'filespace-name': file

space type is not supported.
Explanation: The specified file space type is not

currently supported by TSM on this platform.
System action: The unsupported file system is
skipped. Processing continues with the next file system.
User response: Refer to the documentation for
information on what file space types are supported.
ANE4082I
Node password has been reset to the

administrative id password.
Explanation: The client logged in using administrative

id rather than node name. The node password has been
reset to be in sync with the administrative password.
ANE4083I ANE4091I
ANE4083I
New node password has been

generated.
Explanation: The client logged in using administrative

id rather than node name. New random node password
has been generated and recorded.
ANE4088I
Error


ANE4089W
ANE4084E
Error processing 'filespace-namepathnamefile-name': cannot get file status.
Explanation: While processing the file, the lstat() call

set EOVERFLOW error code.
System action: This file will be skipped.
User response: The file is skipped. Processing
continues with the next file.
ANE4085I
Assigned 'number' objects from previous

systemstate backup to the new
systemstate backup.
Explanation: Objects in the previous System State

backup have not changed and were assigned to the
new System State backup.
File server file-server-name has been

upgraded to Data ONTAP version
'version.modifcation.submodification'.
Perform a full incremental backup by
specifying option
createnewbase=migrate as soon as
possible.
Explanation: The file server has been upgraded to a

version that supports unicode file names for
incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
unicode names that may have been skipped by the
previous version of the IBM Tivoli Storage Manager
client.
User response: Perform a full incremental by

specifying the command line option
createnewbase=migrate with the snapdiff option as
soon as possible.
ANE4086W
ANE4090I
Failed to assign unchanged objects from

previous systemstate backup to the new
systemstate backup. Objects will be
backed up.
Explanation: Objects in the previous System State

backup have not changed and should be assigned to
the new systemstate backup. Due to error assign
operation failed and objects will be backed up.
persists, contact TSM technical support.
ANE4087I
An attemp to load data for the wizard

failed. For more information, please see
the log file.


'version.modifcation.submodification'.
Perform a full incremental backup by
specifying option
createnewbase=migrate as soon as
possible.
Explanation: The file server has been upgraded to a

incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
unicode names that may have been skipped by the
previous version of the IBM Tivoli Storage Manager
client.
User response: Perform a full incremental backup by
specifying the command line option
createnewbase=migrate with the snapdiff option as
soon as possible.
ANE4091I
Starting Full VM Incremental backup of

Virtual Machine 'vmname'

19
ANE4099E ANE4109I
ANE4099E
The system volume cannot be

identified. Therefore the system state
cannot be backed up.
Explanation: The system volume contains the

hardware-specific system state files that are needed to
start Windows, such as Ntldr, Boot.ini, Ntdetect.com or
Bootmgr. If the system volume cannot be identified,
then these files cannot be backed up. Therefore it is not
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
additional assistance. Your TSM administrator can help
you configure the trace.
ANE4100I
Objects Scanned : Number of objects

ANE4104I
Resident Objects : Number of objects New

: Number of new objects

ANE4105I
Premigrated Objects : Number of objects

New : Number of new objects

ANE4106I
Migrated Objects : Number of objects New

: Number of new objects

ANE4101I
Files : Number of files New : Number of

new files
ANE4107I

Candidates : Number of migration

candidates Migrated : Number of migrated
objects Premigrated : Number of
premigrated objects

ANE4102I
Directories : Number of directories New :

Number of new directories

ANE4103I
Entries Entered : Number of entries


ANE4108I
Objects Removed : Number of objects

ANE4109I
Searching for premigrated candidates

20
ANE4110I ANE4121I
ANE4110I
Searching for largest and oldest

candidates (level1)

ANE4116I
Search finished


ANE4117I
ANE4111I
Searching for largest or oldest

candidates (level2)

ANE4112I
Searching for remaining candidates

(level3)

ANE4113I
Waiting for dsmautomig

Current search state :

ANE4118I
Objects scanned in hash : Number of

objects

ANE4119I
Premigrated candidates : Number of

objects


ANE4120I
ANE4114I
Waiting for a new scan

Level 1 candidates : Number of objects


ANE4121I
ANE4115I
Creating pool file


21
ANE4122I ANE4133I
ANE4122I
ANE4128I
Scan complete


ANE4123I
Total candidates found : Number of objects
ANE4129I
Scan time was Number of seconds seconds


ANE4124I
ANE4130I
NO INFORMATION AVAILABLE

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'

22
ANE4134I ANE4145I
ANE4134I
Incremental backup of Virtual Machine

'vmname'

ANE4140I
Backup VM command complete


ANE4141I
ANE4135I
Querying all_local drives for VM

'vmname'

Total number of virtual machines

backed up successfully: num


ANE4142I
ANE4136I
Searching for VM 'vmname' volumes for

backup at location: volname

virtual machine vmname backed up to

nodename nodename


ANE4143I
ANE4137I
Unmount virtual machine disk on

backup proxy for VM 'vmname'

Total number of virtual machines failed:

num


ANE4144I
ANE4138I
Filespace Query for Virtual Machine

'vmname'

ANE4139I
Successful incremental backup of


virtual machine vmname

ANE4145I
Backup VM command started. Total

number of virtual machines to process:
num

23
ANE4146I ANE4155E
ANE4146I
Starting Full VM backup of Virtual

Machine 'vmname'

ANE4147I
Successful Full VM backup of Virtual

Machine 'vmname'

ANE4151E
Explanation: The VMware failed to mount virtual

machine disk.
System action: The backup of the virtual machine can
not continue. The next virtual machine in the vmlist
will be processed. Refer to dsmerror.log for detailed
error message for the reason for the failure.
User response: Refer to dsmerror.log for detailed error
message.
ANE4152E

ANE4148E
Full VM backup of Virtual Machine

'vmname' failed with RC rc
Explanation: The Full VM backup of virtual machine

failed.
System action: The full backup of the virtual machine
finished with failures. The next virtual machine in the
vmlist will be processed. The reason for the failure is
written to the local client error log.
User response: Check the local client error log for
reason for the failure.
ANE4149I
Total number of virtual machines

processed: num

Failure mounting Virtual Machine

'vmname'. RC=rc
Failure initializing VMware virtual

machine environment. RC=rc. Refer to
client dsmerror.log for detailed error
messages.
Explanation: Failure initializing VMware virtual

machine environment. Refer to dsmerror.log for
detailed error messages.
System action: The backup can not continue.
User response: Refer to dsmerror.log for detailed error
message.
ANE4153E
Hostname could not be found for

Explanation: The backup of virtual machine failed.

System action: The backup of the virtual machine
ANE4154E

Possible cause Virtual Machine is not

running and does not have a static IP
address.

ANE4150E
Incremental backup of Virtual Machine

'vmname' failed with RC rc
Explanation: The incremental backup of virtual

machine volumes failed.

ANE4155E
Virtual Machine 'vmname' could not be

found on VMware server.

24
ANE4156E ANE4164W
ANE4156E
File level VM backup of virtual machine

'vmname' not supported. File level VM
backup not support on non Windows
platform guest OS. Platform type:
'platform'.
User response: The TSM server administrator must

grant proxy authority for this node. See the
administrator command "Grant Proxynode".
ANE4161E

User response: Backup using Full VM support.
ANE4157I
backuptype BACKUP VM of virtual

machines specified in option option.

ANE4158I
backuptype BACKUP VM of virtual

machines 'option'.
Duplicate virtual machine name

'vmname' was detected in the same
backup operation. Backup of virtual
machine 'vmfullname' can not continue
without a unique object name.

User response: Choose a unique name for the virtual
machine.
ANE4162E
The virtual machine

'virtual-machine-name' has not been
previously backed up.
Explanation: The specified virtual machine has not

been previously backed up, so can not be specified for
restore.
System action: The specified virtual machine is
skipped, and the next virtual machine in the restore list
is processed.

User response: Verify the virtual machine name to be

restored, and re-try the operation.
ANE4163I

ANE4159E
Backup of Virtual Machine 'vmname'

failed. rc=rc.

ANE4160E
Proxy Rejected: Proxy authority has not

been granted to Agent Node: 'agent_node'
for Target Node: 'target_node'.

the node has not been granted proxy authority to
access the node named by the backup proxy node. The
TSM administrator must first grant proxy authority.
Encryption is currently enabled, but the

virtual machine backup for
'virtual-machine-name' will not be
encrypted.
Explanation: Virtual Machine files are not encrypted

when backed up to the TSM server.
System action: The virtual machine files are not
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
because client-side deduplication is not
being used.
Explanation: Virtual machine files are not compressed

because data is stored in a storage pool that is not
enabled for client-side data deduplication. The virtual
machine files are not compressed during the backup
processing unless data is stored in a storage pool that is
enabled for client-data deduplication.
System action: Backup continues, and data is not
compressed.
25
ANE4165E ANE4175I
User response: Ensure that the storage pool is enabled
for client-side data deduplication: Ensure that the
deduplication parameter for the node is
"ClientOrServer" and that deduplication is set for the
client.
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.
ANE4169E
ANE4165E
Creating a Virtual Machine, but the

hostname 'virtual-machine-name' was not
found.
Explanation: The Virtual Machine being creating must

have a valid hostname to be created.
System action: Check the virtual machine hostname
specified for correctness.
User response: Correct the virtual machine hostname
specified and retry the restore.
ANE4166E

datacenter 'virtual-machine-name' was not
found. The name may be incorrect or
may be located in a VMware folder and
require the folder name such as
vmfolder\dcname.
Explanation: The Virtual Machine being created must

have a valid datacenter to be created.
User response: Check the virtual machine datacenter
specified for correctness. If the datacenter is contained
in a folder then the full datacenter name, complete with
the folder path, must be specified.
Explanation: There was a write error from the local

disk used to store the virtual machine virtual disk
information. Usually the write error is due to lack of
disk space, lack of write permissions, or some similar
problem with the local disk. The VMBACKDIR option
can be used to assign a different disk location if the
local drive does not have enough free space for the
operation.
System action: A disk write error occurred, and the
operation failed.
User response: Check the local disk for possible
causes of the write error, and use the VMBACKDIR
option to assign another disk if needed.
ANE4170E
ANE4167E

datastore 'virtual-machine-name' was not
found.
Explanation: The Virtual Machine being creating must

have a valid datastore to be created.
System action: Check the virtual machine datastore
specified for correctness.
User response: Correct the virtual machine datastore
specified and retry the restore.
ANE4168E
VMware has reported an error via their

SOAP interface. On the Detailed Status
Report panel, view the last error
message reported. Also check the error
log for more information about the
problem that occurred.
Explanation: The command to VMware failed to

complete. The error returned is displayed on the
Restore or Backup summary panel under the Last Error
Message section.
Can not create a Virtual Machine on

VMware release 'release-version-target'
which was backed up from VMware
release 'release-version-source'.
Explanation: The Virtual Machine being created was

backed up from a version of VMware which is not
compatible with the target VMware release version
being used for 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.
ANE4175I
Cluster Option File name and location

System action: An error occurred, and the operation

failed.
26
A write failure occurred on the local

disk proxy used to temporarily store the
virtual machine virtual disk
information. The write failure can be
caused by the lack of available disk
space on the drive used to store this
information. The VMBACKDIR option
can be used to assign a different disk
location for this purpose. Check the
drive being used and ensure that there
is enough space available for this
operation.
ANE4176I ANE4187I
ANE4176I
Cluster Option File

ANE4182I
Cluster configuration has completed

successfully...

ANE4177I
Scheduler Wizard Complete.

ANE4178I
Specify the options file that the Cluster

Protection scheduler should use. Note: If
file exists in specified location, file will
be overwritten.
ANE4183I
Cluster configuration could not be

completed.

ANE4184I
Cluster configuration is being

removed...


ANE4179I
ANE4185I
Cluster Group: Not Available

Cluster configuration has been removed

successfully...

ANE4180I
The TSM Cluster Options File has been

successfully written

ANE4186I
Cluster configuration could not be

removed.

ANE4181I
Cluster configuration has started...

ANE4187I
Done with creating generic service

resource...

27
ANE4188I ANE4201I
ANE4188I
Done with removing generic service

resource...
ANE4198I
Total bytes after deduplication: Number

of bytes


ANE4189I
ANE4199W
Cluster Group:

ANE4190I
Cluster Opt File Name

ANE4191I
Type the fully-qualified name of the

client options file. The client options
file is usually named dsm.opt.

File 'file name' is not backed up as part

of the system state because cluster disk
'volume name' is not accessible.
Explanation: The indicated file or directory was

returned by VSS as part of the backup file list of the
writer. However, the cluster disk where the file is
located is not accessible. The reasons for this problem
can be that the cluster disk is offline or belongs to
another node.
System action: The file is not backed up. Processing
continues.
User response: This problem is documented in
Microsoft knowledge base topic 980794
http://support.microsoft.com/default.aspx?scid=kb;ENUS;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 Manager does not back up files that
are not enumerated by VSS. If the volume is brought
online to the node performing the system state backup,
then it cannot be backed up. You must remove the
volume from the registry key and restart the system
before you can back up the volume. If you do not want
to implement the hotfix for this problem, IBM Tivoli
Storage Manager continues to issue this message.

ANE4200I
ANE4192I
The Cluster Options File name can not

be a directory

ANE4193I
The specified path is invalid. Specify a

valid directory and a filename

Explanation: The Deployment Manager process was

started as a post schedule command. This is the first
message from the Deployment Manager. The
architecture of the client, schedule name, and domain
name are identified at the beginning of the message
text.
System action: Deployment Manager continues to
process.
User response: None
ANE4201I

28
architecture, schedule-name, domain-name:

The Deployment Manager process was
started successfully. Deployment
Manager Version Information: version.
The Deployment Manager successfully

installed lagnuage pack: language pack
name.

ANE4202E ANE4211I
ANE4202E
The Deployment Manager failed to

install language pack: language pack
name. The Microsoft Installer error code
was error code.
User response: Make sure that there is sufficient disk

space on the client computer.
Make sure that all of the Windows self extracting client
images on the client computer are valid.
ANE4207I
The Deployment Manager shut down

service successfully: service name.
Explanation: The previous language pack has been

uninstalled, and the installation of the new language
pack failed.

User response: Check the technote for Microsoft

Installer error code description: http://www01.ibm.com/support/docview.wss?uid=swg21050782
&rs=663
Check the install log on the client computer.

ANE4203I

retrieved system information.

ANE4204E
The Operating System of the client

computer: os name is not supported by
the target version: target version.
Explanation: The operating system level of the client

computer is no longer supported by the target level.
ANE4208E
Explanation: None
User response: None
ANE4209I
ANE4205I
The Deployment Manager succesfully

extracted from installation image: image
name.

ANE4206E
The Deployment Manager received an

error while extracting from installation
image: image name.
Explanation: The installation image might be missing,

corrupted, or there might be insufficient disk space on
the client computer.

installed package: client package name.

ANE4210E

User response: Check the release documentation for
information on supported operating system levels.
The Deployment Manager could not

shut down TSM service: service name.

install package: client package name. The
Microsoft Installer error code was error
code.
Explanation: The previous client package has been

uninstalled, and the installation of the new client
package failed.
&rs=663
ANE4211I

restarted service: service name.

System action: Deployment Manager stops.

29
ANE4212E ANE4221E
ANE4212E

restart service: service name.
Explanation: After the automatic client deployment,

the TSM client services failed to start.
User response: Please make sure that the installation

package is valid.
ANE4217E

User response: Log on to the client machine and
check the backup-archive client error log.
ANE4213E
Automatic restart of the client computer

was required because reason
Explanation: The Deployment Manager determined

that the deployment requires restarting the client.
Automatic restart is not enabled. The Deployment
Manager process cancels the deployment.
Explanation: The Deployment Manager process failed

when setting up the client API.
User response: Check the error log on the client
computer.
ANE4218E
The current client is not uninstalled or updated.

System action: Deployment Manager cancels the client
deployment and stops
User response: Reschedule the client deployment.
ANE4214E
The operating system platform of the

client package 'OS platform of package' is
incompatible with the client computer
'OS platform of client computer'.
User response: Reschedule the client deployment. Use

a client package with the appropriate operating system
platform.
ANE4215E
The automatic deployment path from

the current client code version 'source
version' to the client package version
'target version' is not supported.

computer.
ANE4219E
User response: Refer to the Tivoli Storage Manager

Backup-Archive Client documentation in the
information center.
Reschedule the client deployment with an appropriate
target level.
ANE4216E
The TSM API library version API version

is at an earlier version than the version
of the client package package version.
Explanation: The client package for automatic

deployment is invalid. In the client package, the API
version does not match the Deployment Manager
version.
System action: Deployment Manager stops processing.
30

error while creating a pipe for the
standard output of the child process.
Explanation: The Deployment Manager failed to

create a pipe for the standard output of the child
process.
computer.
ANE4220E
Explanation: None

error while initializing the client API.
The standard API function being
invoked was API init function name.
Explanation: The Deployment Manager process failed

when initializing the client API.
Explanation: None

error while setting up the client API.
The standard API function being
invoked is API setup function name.
The Deployment Manager is unable to

determine if TSM processes are still
running.
Explanation: The Deployment Manager could not

determine whether all TSM processes were shut down
successfully.
System action: If automatic restart (autoreboot) is
enabled, the Deployment Manager continues. If
automatic restart is not enabled, Deployment Manager
stops.
User response: Reschedule with automatic restart
(autoreboot) enabled.
ANE4221E
The architecture of the package: package

architecture does not match the current
client: system architecture.
Explanation: The setup script was unable to retrieve

the matching package from the server.
ANE4222E ANE4229I
ANE4226E
User response: Ensure that the client packages for all

architectures are available on the server.
ANE4222E
The Deployment Manager is unable to

read information in file: file name.
There is at least one error in the post

schedule command of the client
deployment schedule.
Explanation: The Deployment Manager encountered

at least one error while parsing the post schedule
command of the client deployment schedule.
Explanation: Deployment Manager failed to open a

file containing required system information.
System action: Processing stops, and client

deployment will not begin.

information on the format of the post schedule
command of the client deployment schedule.

computer.
ANE4223E
The Deployment Manager is missing

required information in file: file_name.
Explanation: The Deployment Manager relies on the

information in this file to complete the client
deployment.
computer.
ANE4224I

shuts down backup-archive client
processes with names starting with
"dsm" .

ANE4227E
Explanation: The previous client package has been

uninstalled, and the installation of the new client
package failed because the client computer is out of
disk space.
&rs=663
ANE4228E

ANE4225W
The setup script is still waiting for the

result of querying system information.
Ensure that "PASSWORDACCESS
GENERATE" is set in the client options
file and that a connection to the server
can be made without being prompted
for a password.
Explanation: The results of querying the system

information has taken longer than expected. This could
be caused by either a slow system or becuase there is
no password saved for the node.
System action: If the password is not generated,
processing stops and client deployment will not begin.
If the system is slow, processing continues.
User response: Ensure that "PASSWORDACCESS
GENERATE" is set in the client options file and that a
connection to the server has been made without being
prompted for a password. Ignore the warning if the
password has been generated.

install package: client package name. The
client computer is out of disk space. The
Microsoft Installer error code was error
code.

install language pack: language pack
name. The client computer is out of disk
space. The Microsoft Installer error code
was error code.
Explanation: The previous language pack has been

uninstalled, and the installation of the new language
pack failed because the client computer is out of disk
space.
&rs=663
ANE4229I
The client computer is required to

restart to complete the new
Backup-Archive client installation.
Explanation: The deployment of the new

backup-archive client will not be complete until the
client computer is restarted. The restart is scheduled to
happen immediately after all language packs are
deployed.
31
ANE4230I ANE4237W
System action: The Deployment Manager process
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.
User response: None
ANE4230I
The client computer will be shut down

and restarted immediately.
Explanation: The Deployment Manager needs to

restart the client computer to complete the client
deployment. It is possible the other messages provide
details of the deployment.
continues. The client computer will be shut down and
restarted immediately after all language packs are
deployed, or immediately if there are no language pack
to install.
User response: None
ANE4231E
The deployment for language pack:

image name was cancelled.
Explanation: The Deployment Manager does not

uninstall or update the current language pack. It is
possible the other messages provide details of the
deployment.
System action: Processing stops. The client computer
will be shut down and restarted immediately after all
language packs are deployed, or immediately if there
are no language pack to install.
computer. Manually deploy the language pack.
ANE4232E
Self-extracting installation image: image

name cannot be found.
Explanation: The Deployment Manager could not find

the required installation image.
System action: Processing stops. Client deployment
will be cancelled.
User response: Check the server's activity log or the
scheduler log on the client computer. Reshcedule the
client deployment.
ANE4233I
The Deployment Manager will install

the Backup-Archive client with the
following feature set: feature set.

ANE4234E
Explanation: The Deployment Manager failed to

install one or more language packs. It is possible the
other messages provide details of the installation.
continues.
User response: Check the error log and installation on
the client computer. Identify the language packs that
failed to install and manually deploy them.
ANE4235I
The deployment manager cannot log

events to the server.
Explanation: The Deployment Manager is unable to

log events to the server. It is possible the other
messages provide details of the communications.
continues. Events will be logged locally on the client
machine only.
User response: Check network connection and the
error log on the client computer.
ANE4236E
The setup script was unable to query

the registry for the Tivoli Storage
Manager client installation directory.
Explanation: The setup script encountered an error

while querying the Windows registry for
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\
BackupClient].
information on supported Windows platforms and
ensure the REG.EXE command is available on the client
computer.
ANE4237W
Query system information was

completed with warnings or errors.
ErrorLevel was error level
Explanation: The setup script encountered warnings

or errors while querying system information.
System action: Processing continues. The Deployment
Manager will check to see if required system
information is available. Client deployment could be
cancelled if required information is missing.
User response: Check the error log of the
backup-archive client for warning and error messages.

32
The deployment for language packs

failed.
ANE4238E ANE4248E
ANE4238E
Processor Architecture information is

missing in the system information.
Explanation: It is possible the setup script

encountered a warning or error while querying system
information.
ANE4243I
The setup script successfully retrieved

the client package for architecture.
Explanation: The client package that was downloaded

matches the processor architecture of the current client.

will not start.
User response: None
User response: Check the error log of the

backup-archive client for warning and error messages.
ANE4244E
ANE4239E
Processor Architecture information is

missing in the client package.
Explanation: It is possible the client deployment

package is missing or corrupted.
will not start.
User response: Ensure that the client package is
available and imported to the server correctly.
ANE4240E
Client version information is missing in

the client package.
Explanation: It is possible the client deployment

package is missing or corrupted.
will not start.
User response: Ensure that the client package is
available and imported to the server correctly.
ANE4241I
Architecture of the package: package

architecture does not match the current
client: system architecture. The setup
script is attempting to retrieve the
matching package.
Explanation: The setup script is trying to retrieve the

matching client package from the server.
User response: Ensure that the client packages for all
architectures are available on the server.
ANE4242E
The setup script encountered a warning

or error while retrieving the client
package for architecture. The error level
is error level.
The setup script failed to install the

Microsoft Visual C++ redistributable
package. Error Level is error level.
Explanation: The Microsoft Visual C++ redistributable

package is required by the new client.
User response: Check the installation log file for
names with "vcredist*.log" file in system temp directory.
ANE4245I
The setup script successfully installed

the Microsoft Visual C++ redistributable
package.
Explanation: The Microsoft Visual C++ redistributable

package is required by the new client.
User response: none
ANE4246E
The setup script failed to start the

Deployment Manager program. Error
Level is error level.
Explanation: The setup script could not start the client

deployment process.
User response: Check the log files on the client
computer for more details. Ensure the client package is
not corrupted.
ANE4247I
The setup script successfully started the

Deployment Manager program.
Explanation: The setup script invokes the Deployment

Manager to manage the deployment process.
User response: None
Explanation: It is possible the client package is not

available on the server.
ANE4248E
Explanation: Processing stopped because the

automatic client deployment feature does not support
the installation of a client to a workstation that is
already at its target level.
User response: Ensure that client packages for all

architectures are available on the server. Check the
backup-archive client error log for more detailed error
messages.
The client is already at the target level:

'target version'.
System action: Your current backup-archive client is

not affected.
33
ANE4249E ANE4256E
User response: Refer to the Tivoli Storage Manager
Backup-Archive Client documentation in 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
ANE4249E
The setup script was unable to query

the registry for the client scheduler
service name.
Explanation: The setup script encountered an error

while querying the Windows registry for
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\
BackupClient\Scheduler Service].
information on supported Windows platforms and
ensure the REG.EXE command is available on the client
computer.
ANE4250E
There is already a deployment manager

running on this computer.
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
new client code only needs to be deployed to one node
per computer. Each client deployment instance can take
a few minutes to complete.
User response: Ensure only one client deployment
task is scheduled to run at a time.
ANE4251W
writername file 'filename': not found.
Explanation: The indicated VSS writer file or directory

was returned by VSS as part of the backup file list of
the writer. However, the object does not exist on the
disk..
System action: Processing stops if
SKIPMISSINGSYSWFILES option is set to NO.
Processing continues if SKIPMISSINGSYSWFILES
option is set to YES.
User response: Verify that this file can be skipped
during system state backup.
ANE4252E
The deployment manager failed to start

as a scheduled task.
Explanation: The setup script failed to start the

deployment manager as a scheduled task with the
Windows "at" command.
Explanation: The deployment manager determined

there was insufficient free disk space for the client
deployment.
User response: Free up required disk space and
reschedule the client deployment.
ANE4254E
The deployment manager detected an

HSM client on the workstation that it
needs to deploy the Backup-Archive
client to.
Explanation: An attempt was made to deploy the

Backup-Archive client to a workstation that already has
the HSM client installed. The Backup-Archive client
cannot be deployed to a workstation that has the HSM
client.
User response: Uninstall the HSM client and
reschedule the Backup-Archive client deployment.
ANE4255E
There is not enough memory for the

deployment manager to create the
system information object
Explanation: The system information object could not

be created because there is not enough available RAM
to temporarily write the data into.
User response: Close all unneeded applications on the
client workstation and reschedule the deployment.
ANE4256E
The DSMI_DIR environment variable is

not defined.
Explanation: The deployment manager cannot initiate

a connection to the server because the DSMI_DIR
environment variable is not set. This error can occur if
the deployment manager is started without using the
client scheduler.
User response: Read the available documentation to
determine how to use the client scheduler to create a
client deployment task.

User response: Ensure that the Windows Task
Scheduler service is running. It is possible that the
34
There was not enough disk space on the

client computer. Required space: package
space bytes; available space: system space
bytes.
ANE4257E ANE4265I
ANE4257E
The deployment manager cannot parse

information in file: file name.
Explanation: The deployment manager could not

parse or extract the required information from the
specified file.
User response: Check the error log file on the client
workstation.
ANE4258E
The deployment manager received the

Windows "OpenSCManager failed" error
message.
Explanation: The deployment manager could not

connect to the Windows service control manager to
start the client scheduler. In general, this error occurs
because the user who is initiating the task does not
have sufficient authority.
User response: Check the installation directory of the

current Backup-Archive Client. If the Backup-Archive
Client is not installed in the default location, manually
upgrade the Backup-Archive Client . If the DSM_DIR,
DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
environment variables are defined with a relative path,
define them with an absolute path and try the client
deployment again.
ANE4262E
The preview of the client installation

failed.
Explanation: The deployment manager did not

uninstall the current client. The client code is
unchanged.
User response: Check the deployment manager log
and trace files on the client workstation for specific
issues identified during the preview. Reschedule a
deployment after any issues are resolved.
User response: Ensure that the user who starts the

client scheduler has administrative privileges.
ANE4263E
ANE4259E
Explanation: The deployment manager received an

error while uninstalling the current client.
The client scheduler is not started as a

root user.
Explanation: The client scheduler requires root user

privileges to upgrade the client code.
User response: Log in as root and start the client
scheduler.

and trace files on the client workstation for more
details on the error. You might have to manually
uninstall the client.
ANE4264E
ANE4260E
The installation file system is not

writeable.
The deployment manager failed to

uninstall the backup-archive client.

install the backup-archive client.
Explanation: The deployment manager cannot write

to the installation file system.
Explanation: The current client was uninstalled and

the deployment manager received an error while
installing the new client code.
User response: Check the installation file system

permissions. It is possible that the current client node
runs in a virtualized environment using the client code
installed in a shared storage of the physical
environment. Reschedule the client deployment with
the client node in the physical environment.

and trace files on the client workstation for more
details on the error. Manully install the new client after
the issue is resolved.
ANE4261E
The deployment manager cannot

upgrade the Backup-Archive Client.
Explanation: The Backup-Archive Client cannot be

upgraded because either the current location is not the
default installation location or the DSM_DIR,
DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
environment variables are defined with a relative path
and not an absolute path.
ANE4265I
Client deployment options are not

specified in the scheduler command or
from client services.
Explanation: The default client options file will be

used. The deployment manager might not report the
correct server and node information when reporting
status.
User response: Configure the client deployment from
the Administration Center and start the client scheduler
as a Windows service.
35
ANE4266I ANE4274E
ANE4266I

install non-English language pack(s).
ANE4271E
The deployment package is missing one

or more required installation image
files.
Explanation: The previous packages were uninstalled,

and the installation of one or more new language packs
were not successful.
Explanation: The client deployment package might

not have been imported correctly to the server.
User response: Check the deployment trace file on the

client workstation for specific language pack
information.
User response: Ensure that client packages are

available on the server. Check the backup-archive client
error log file for more detailed error messages.
ANE4267I
ANE4272E

install the hardware plugin package.
Explanation: The previous package was uninstalled.

The installation of the new hardware plugin package
failed.
client workstation.
The processor type of the package:

package processor type does not match the
current client: system processor type.
Explanation: The processor type supported by the

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
for the deployment manager to connect to the server
and report the error.
ANE4268I

install the journal-based backup
package.
Explanation: The previous journal-based backup

package was uninstalled. The new journal based
backup package installation failed.
User response: Verify that you are using the correct

client package for the processor architecture of the
computer that you want to upgrade. Then restart the
deployment.
ANE4273E

client workstation.
ANE4269W
The deployment manager is stopping

the scheduler and/or CAD processes.
Explanation: Before deploying the new client, the

deployment manager must stop the scheduler and
CAD processes. After the deployment, the processes
must be restarted.
User response: The client scheduler is interrupted
during the deployment.
ANE4270I
The deployment manager and the new

client installation packages were
downloaded to directory: file name.
Explanation: The download directory contains

everything required to complete the new client
deployment. Deployment log and trace files can be
found in the log/ sub-directory.
Explanation: An attempt was made to deploy the

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
workstation that has the JBB client installed.
User response: Uninstall the JBB client and reschedule
the Backup-Archive Client deployment.
ANE4274E
The deployment manager cannot stop

the scheduler or the CAD processes.
Explanation: The deployment manager tried to shut

down the Backup-Archive Client scheduler or CAD
processes but the Backup-Archive Client might be busy
with other tasks.
User response: Reschedule the Backup-Archive Client
deployment.

User response: Obtain log and trace files from the
download directory for problem determination. The
files are found within the log/ sub-directory.
36
The deployment manager detected a

journal based backup (JBB) client on the
workstation where it needs to deploy
the Backup-Archive Client.
ANE4275E ANE4296I
ANE4275E
The deployment manager cannot restart

the scheduler or the CAD processes.
Explanation: Before exiting, the deployment manager

could not restart the Backup-Archive Client scheduler
or CAD processes. The deployment manager stopped
the processes prior to the client upgrade.
User response: Log on to the Backup-Archive Client
workstation and check the error log file. If you have set
environment variables make sure they are not defined
using relative path.

ANE4280E
Explanation: One or more of the running client

services include AUTODEPLOY = NO in the option
file.
User response: Change the AUTODEPLOY option on
the client and reschedule the client deployment.
ANE4281E
ANE4276E
The deployment manager cannot obtain

information about the scheduler or the
CAD processes.
Automatic client deployment is not

allowed on the client workstation.
The update manager cannot remove the

TIVsmCapi package from non-global
zone(s): zone name.
Explanation: The deployment manager needs process

information in order to stop and restart the
Backup-Archive Client scheduler or CAD processes.
Explanation: APAR IC57433 prevents the removal of

the TIVsmCapi package on Solaris on a sparse-root,
non-global zone if uninstalling is done from the global
zone.

workstation and check the error log file and the
deployment manager error log file.
User response: Manually uninstall the Tivoli Storage

Manager client directly from the non-global zones and
reschedule the deployment.
ANE4277E
ANE4295W
The target operating system version

target operating system does not meet the
minimum required version minimum
required version
Explanation: The operating system version is earlier

than the version required by the automatic deployment
package.
System action: The deployment is canceled.
User response: Ensure that the TSM version being
deployed is supported by the target operating system.
ANE4278E
The deployment manager cannot obtain

information about the Logical Volume
Snapshot Agent (LVSA).
Explanation: The deployment manager needs to

determine whether an LVSA is installed on the client
workstation.

The client deployment was not
completed pending the restart of the
client computer. The deployment
manager did not restart the client
computer automatically because the
AUTODEPLOY option was set to
NOREBOOT.
Explanation: The previous client has been uninstalled,

and the installation of the new client was not
completed pending the restart of the client computer.
The architecture of the client, schedule name, and
domain name are identified at the beginning of the
message text.
completes.
User response: Manually restart the client computer
as soon as possible.

workstation and check the error log file and the
deployment manager error log file.
ANE4279I
Server information is not available in

the deployment schedule.

ANE4296I

The client deployment was completed
successfully, and the client computer is
being restarted.
Explanation: Restarting the computer is required to

complete the client deployment. The architecture of the
client, schedule name, and domain name are identified
at the beginning of the message text.
completes. The client computer will be shut down and
restarted.
37
ANE4297W ANE4940I
User response: None
ANE4297W

Client deployment was completed with
warnings: warnings.
Explanation: This message is a generic warning

message. It is possible that other messages provide
details of the deployment. The architecture of the client,
schedule name, and domain name are identified at the
beginning of the message text.
completes.
User response: Check the warning messages from the
server administration center, the server activity log, or
error log on the client computer for more information.
ANE4298E

The client deployment was canceled.
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
the deployment. The architecture of the client, schedule
name, and domain name are identified at the beginning
of the message text.
name are identified at the beginning of the message

text.
completes.
User response: None
ANE4900W
Schedule 'schedule-name' has opened a

new session with the server.
Explanation: A scheduled event endsbecause of a

connection failure. The scheduled event had to be
restarted outside its normal startup window to
continue the operation.
System action: The scheduled event is completed
using more than one session.
User response: None required. If this is a recurrent
condition, you may want to check for network
problems.
ANE4901E
The following object contains one or

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
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
must be at the end of the line. If there is no closing
quotation mark or the closing quotation mark has been
encountered in the middle of the line, it is an invalid
input.
System action: The object is skipped.
ANE4299E

The client deployment failed. The
previous event causing the failure is:
event.
Explanation: This message is a generic message that

the client deployment failed. It is possible that other
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.
ANE4300I

Client deployment was completed
successfully.
Explanation: This is a generic message that the client

deployment was successful. It is possible that other
messages provide details of the deployment. The
architecture of the client, schedule name, and domain
38
User response: Correct the specification of the object.

ANE4939I
Total snapshot difference objects:

Number

ANE4940I
Backing up object 'writer-name'

component 'component-name' using
shadow copy.

ANE4941I ANE4958I
ANE4941I
Backup of object 'writer-name'

component 'component-name' finished
successfully.

ANE4953I
Total number of objects archived:

Number of objects


ANE4954I
ANE4942E
The file specification 'string' is invalid.
Explanation: The operating system indicated that the

file specification is invalid. One possible reason is that
the file specification contains unrecognized characters.
Another possible cause is incorrect use of quotation
marks in the file specification.
User response: Enter a correct file specification as
described in the Using the Backup-Archive Client book
for the particular operating system. Ensure that the file
specification contains valid characters. Verify correct
use of quotation marks for specifications that contain
blanks spaces. If multiple file specifications are used,
make sure that any use of quotation marks does not
cause the file specifications to be treated as a single file
specification.
ANE4943I
Existing filespace name 'filespace-name'

has been renamed to 'filespace-name'
Total number of objects backed up:

Number of objects

ANE4955I
Total number of objects restored:

Number of objects

ANE4956I
Total number of objects retrieved:

Number of objects


ANE4951I
ANE4957I
Total number of objects assigned:

Number of objects
Total number of objects deleted: Number

of objects


ANE4952I
ANE4958I
Total number of objects inspected:

Number of objects
Total number of objects updated:

Number of objects


39
ANE4959I ANE4970I
ANE4959I
Total number of objects failed: Number

of objects
ANE4965I
Total number of subfile objects: Number

of objects


ANE4960I
ANE4966I
Total number of objects rebound:

Number of objects
Network data transfer rate: Transfer rate

KB/sec


ANE4961I
ANE4967I
Total number of bytes transferred:

Number of bytes
Aggregate data transfer rate: Transfer rate

KB/sec


ANE4962I
Average file size: Size
ANE4968I
Objects compressed by: Number%%


ANE4963I
Data transfer time: Transfer time sec
ANE4969I
Subfile objects reduced by: Number%%


ANE4964I
Elapsed processing time: Elapsed time

ANE4970I
Total number of objects expired: Number

of objects

40
ANE4971I ANE4980I
ANE4971I
LanFree data bytes: Number of bytes

ANE4975I
Total number of bytes processed:

Number of bytes

ANE4972W

'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
as soon as possible.
Explanation: The file server has been upgraded from a

incremental backup using snapshot difference to a
version that does not. If you have upgraded from Data
ONTAP version 7.3.3 (or later) to 8.0, you lose the
ability to back up files with unicode file names when
performing snapshot difference incremental backup.
System action: Processing continues. However, files
with unicode names are not backed up.
User response: Upgrade to a version that supports
unicode file names as soon as possible. If you have
upgraded from Data ONTAP version 7.3.3 (or later) to
8.0, upgrade to 8.1 (or later). If it is not possible to
upgrade at this time, you can suppress this warning
message by renaming the file space on the IBM Tivoli
Storage Manager server and performing a snapshot
difference incremental backup.
ANE4976I
Total data reduction ratio: Number%%

ANE4977I
Total number of bytes inspected: Number

of bytes

ANE4978I
Deduplication Reduction:

ANE4973E
An error occurred accessing NTFS

security information for file 'filespace
namepath-namefile-name'
ANE4979I
Total Data Reduction:
Explanation: An access denied error occurred while

attempting to access NTFS security info rmation.

User response: See your system administrator or

bypass the failing check by using SkipNTSecu rity
option.

ANE4980I
ANE4974E

namepath-namefile-name': a required NT
privilege is not held.
Explanation: The user account running TSM does not

possess a required NT user right/pr ivilege for
performing the current operation.
Total Bytes Inspected:


User response: Your system administrator has the
authority to grant the needed privilege.
41
ANE4981I ANE4990I
ANE4981I
Deduplication reduction: Number%%

ANE4982I
Total objects deduplicated: Number of

objects

ANE4987E
Explanation: The specified file is being used by

another process. You tried to read from or write to a
file that is currently being used by another process.
User response: Ensure that the file is not locked by
another process. If the file is not locked, retry the
command.
ANE4988W

ANE4983I
Files Deduplicated:


namepath-namefile-name': the object is in
use by another process
File 'filespace namepath-namefile-name' is

currently unavailable on server and has
been skipped.

is currently not available from the TSM server. This is
most likely a temporary condition.
System action: TSM cannot restore or retrieve the file.
User response: Try to restore or retrieve the file again
after the file becomes available on the server. If the
problem persists, see your TSM administrator for
assistance.

ANE4989E
ANE4984I
Total bytes before deduplication: number

of bytes

ANE4985I
Session

ANE4986I
Node

42

namepath-namefile-name': the directory is
in use by another process. All objects in
the directory and any of its
subdirectories are skipped.
Explanation: The specified directory is being used by

another process. You tried to read from or write to a
directory that is currently being used by another
process. The objects contained in the directory and its
subdirectories are not backed up.
System action: Processing stopped for that directory.
If other files and directories were also specified in this
backup, they are processed
directory name, correct the permissions, or specify a
new location.If the directory name is correct, retry the
backup when no process has exclusive use of the
directory.
ANE4990I
@1%s

ANE4991I ANE4999I
ANE4991I
Application Type Application Message Id

Application Message
Explanation: This is a message sent by the application

you are currently running with TSM.
System action: TSM logs the application message.
User response: Refer to the documentation for the
application that you are using.
ANE4992W

Application Message

ANE4997E
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
ANE4993E

Application Message

ANE4994S

Application Message

ANE4995I
@1%s @2%s @3%s

ANE4996I

namepath-namefile-name': file system quota
reached condition - no space left.
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.
@1%s @2%s @3%s

43
ANE4056I ANE4173I
Version 6.3.1 ANE new and changed messages

No ANE messages are new or changed for version 6.3.1.

The following Tivoli Storage Manager server ANE messages are new or changed
for version 6.3.2. The 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.
ANE4056I
Pre-requisite Microsoft Windows hotfix

'hotfix name' is not installed.
Explanation: This message is issued when you

attempt to perform an operation that uses Microsoft
Volume Shadow Copy Service (VSS) and the
pre-requisite hotfix cited in the message text is not
installed. This hotfix is known to fix a number of issues
that prevent successful VSS operations on Microsoft
Windows Server 2003. Some of the operations that can
be impacted include system state backup, incremental
backup using Open File Support when VSS is specified
as the snapshot provider, and image backup when VSS
is specified as the snapshot provider. The IBM Tivoli
Storage Manager Microsoft Windows Client
Requirements web page documents this hotfix as a
pre-requisite when performing operations that use VSS.
Visit the Microsoft support page http://
support.microsoft.com for more information about the
hotfix.
User response: If IBM Tivoli Storage Manager
backup-archive client operations that use VSS do not
complete successfully due to VSS related errors, install
the hotfix, then try the operation again. Even if VSS
operations currently complete successfully, install the
hotfix as a preventive measure.

ANE4178W

the virtual machine control files for
compressed because client-side
deduplication is not being used for the
management class default or specified
by the -vmctlmc option for
'vm-ctl-mgmt-class-name'.
Explanation: Virtual machine control files are not

compressed because data is stored in a storage pool
that is not enabled for client-side data deduplication.
The virtual machine control files are not compressed
during the backup processing unless data is stored in a
storage pool that is enabled for client-data
deduplication.
System action: Backup continues, and control file data
is not compressed.
for client-side data deduplication: Ensure that the
deduplication parameter for the node is
"ClientOrServer" and that deduplication is set for the
client.

The following Tivoli Storage Manager server ANE messages are new or changed
ANE4172I
Starting Full VM backup of VMware

Virtual Machine 'vmname' mode:
'full_or_incr' target node name:
'target_node_name' data mover node
name: 'data_mover_node_name' application
protection type:
'application_protection_type' application(s)
protected: 'application_list'

44

ANE4173I
Successful Full VM backup of VMware

Virtual Machine 'vmname' mode:
'full_or_incr' target node name:
'target_node_name' data mover node
name: 'data_mover_node_name'

ANE4178W ANE4187W
ANE4178W

the virtual machine control files for
compressed because client-side
deduplication is not being used for the
management class default or specified
by the -vmctlmc option for
'vm-ctl-mgmt-class-name'.
Explanation: Virtual machine control files are not

compressed because data is stored in a storage pool
that is not enabled for client-side data deduplication.
The virtual machine control files are not compressed
during the backup processing unless data is stored in a
storage pool that is enabled for client-data
deduplication.
ANE4182I
AS_ENTITY='AS_ENTITY'

ANE4183I
SUB_ENTITY='SUB_ENTITY'

System action: Backup continues, and control file data

is not compressed.

for client-side data deduplication: run "q stg <pool
name> f=d" and verify that the value of "Deduplicate
Data?" is "yes". Ensure that client-side data
deduplication is enabled on the server. To enable
client-side data deduplication, use the
DEDUPLICATION parameter on the REGISTER NODE
or UPDATE NODE server command. Set the value of
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
CLIENTOPT command to set the DEDUPLICATION
option in a client option set. To prevent the client from
overriding the value in the client option set, specify
FORCE=YES. Ensure that the deduplication parameter
for the node is "ClientOrServer": The value of the
DEDUPLICATION option on the client must be set to
YES.
ANE4184I
ANE4180I
BYTES='BYTES'
ACTIVITY_TYPE='ACTIVITY_TYPE'

ANE4185I
RC='RC'

ANE4186I
ENTITY='ENTITY'


ANE4187W

ANE4181I
ACTIVITY_DETAILS='DETAILS'

CPU and Memory Resource Allocation

configuration settings cannot be restored
when the IBM Tivoli Storage Manager
data mover node is connected directly to
a Virtual Center managed ESX/ESXi
host. These settings have been skipped.
Explanation: The VMware vStorage APIs do not

support the restore of CPU and Memory Resource
Allocation configuration settings when connected
directly to an ESX/ESXi host that is managed by a
Virtual Center.
System action: CPU and Memory Resource Allocation
configuration settings are skipped. Processing
continues.
45
ANE4188I ANE4292E
User response: Virtual machine CPU and Memory
Resource Allocation configuration settings will be
restored when the IBM Tivoli Storage Manager data
mover node connects directly to a vCenter Server.
Modify the VMCHOST to connect the TSM data mover
to a vCenter Server.
ANE4188I
EXAMINED='EXAMINED'

ANE4192I

ANE4285E

ANE4189I
AFFECTED='AFFECTED'

Years='Years' Months='Months'
Days='Days' Hours='Hours'
Minutes='Minutes' Seconds='Seconds'
The update restore operation to an

existing virtual machine 'VmName'
failed. The virtual machine is not in
power off state.
Explanation: The update restore operation to an

existing virtual machine is not supported for a running
machine and will be aborted.
System action: Restore aborted.
User response: Turn off the virtual machine and
re-run the update restore command.

ANE4290E
ANE4190I
FAILED='FAILED'
Only one virtual machine can be

selected for restore.

Explanation: Restoring multiple virtual machines is

not allowed. Only one virtual machine can be selected
for restore.
System action: No processing occurs.
User response: Select only one virtual machine for

restore.
ANE4191E
Restore VM operation failed using 'san'

transport mode. In some cases switching
from SAN to network-based VM
restores can be successful.
Explanation: Restore VM operations that fail using

SAN transport mode can often be successful over a
LAN path. If a restore vm operation fails using the
'SAN' transport mode, set the client option
VMVSTORTRANSPORT to "nbd:nbdssl" and try the
restore vm operation again.
System action: Restore VM operation failed using 'san'
transport mode. Restore may be successful using
'nbd:nbdssl' transport modes.
User response: Restore VM operation failed using
'san' transport mode. In some cases network-based VM
restores can be successful when using 'nbd' or 'nbdssl'
transport modes. The VMVSTORTRANSPORT option
can used to restrict the TSM client to use only the
specified transport modes.
46
ANE4291E
Virtual Machine could not be found on

VMware server.

ANE4292E
No virtual machine found.
Explanation: No virtual machine found with name or

specified in domain option.
User response: Specify a correct VM name or domain
option.
ANE4944I ANE4950I
ANE4944I
Virtual machine: 'vm-name' disk:

'disk-name' is excluded by user.

backup vm ..." command with the -preview option to

display a listing of the disk labels which exist on the
virtual machine. For a restore operation, use the "dsmc
query vm ..." command with the -detail option to
display a listing of the disk labels which exist on the
virtual machine backup. Check the spelling of the disk
label and correct the disk label and then retry the
operation.

ANE4949I
ANE4945I

'disk-name' is included by user.

'disk-name' was excluded when the
backup was performed.


ANE4946W
ANE4950I
Warning: virtual machine: 'vm-name'

disk: 'disk-name' excluded by user, was
not found.
Explanation: The specified virtual disk does not exist

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

'disk-name' is excluded from restore by
user.

Error: virtual machine: 'vm-name' disk:

'disk-name' included by user, was not
found.
Explanation: The specified virtual disk does not exist

User response: Use the "dsmc backup vm ..."
command with the -preview option to display a listing
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.
ANE4948E
A specified virtual disk was not found

Explanation: You must specify a virtual disk label

name which exists on the virtual machine.
User response: For a backup operation, use the "dsmc
47
48
Chapter 3. ANR: Server common and platform-specific

messages version 6.3
This section contains all publishable ANR messages for the Tivoli Storage Manager
server, version 6.3. All messages with prefix ANR are issued by the Tivoli Storage
Manager server. Some messages are common to all server platforms, and some are
specific to platform.
Version 6.3.0 ANR messages that are new, changed, or deleted since version 6.2.0
are listed in one section. All version 6.3.0 ANR messages are documented in
another section.
Changes from version 6.2.0 to version 6.3.0

The following Tivoli Storage Manager server ANR messages are new or changed
for version 6.3.0.
Version 6.3.0 ANR new messages

The following version 6.3.0 ANR server messages are new since version 6.2.0. Only
the message ID is listed.
v
v
v
v
v
ANR0317I
ANR0318I
ANR0319W
ANR0324E
ANR0325E
v
v
v
v
v
v
v
v
ANR0326E
ANR0327I
ANR0328I
ANR0329I
ANR0330W
ANR0331W
ANR0332E
ANR0333E
v
v
v
v
v
v
v
ANR0334E
ANR0335I
ANR0336I
ANR0337I
ANR0338E
ANR0339E
ANR0340E
v
v
v
v
v
ANR0341E
ANR0343W
ANR0507E
ANR1549W
ANR1589E
49
v
v
v
v
v
ANR1626I
ANR1627I
ANR1628I
ANR1629W
ANR1630W
v
v
v
v
v
v
v
ANR1631I
ANR1632E
ANR1633E
ANR1634I
ANR1747E
ANR1812E
ANR1813W
v
v
v
v
v
v
ANR1814W
ANR1815W
ANR1816W
ANR1817W
ANR1818W
ANR1819E
v ANR1820E
v ANR1877E
v ANR1878E
v
v
v
v
ANR1890W
ANR1891I
ANR1892W
ANR1893E
v ANR1894E
v ANR1900E
v ANR1901I
v
v
v
v
v
ANR1902W
ANR1928W
ANR1929E
ANR1930E
ANR1931E
v ANR1934W
v ANR1950W
v
v
v
v
v
v
v
ANR1951W
ANR1952I
ANR1953E
ANR1954W
ANR1955E
ANR1992E
ANR2720E
v ANR2721E
v ANR2722I
v ANR2723I
50
v
v
v
v
v
ANR2724I
ANR2725I
ANR2726E
ANR2727E
ANR2728E
v
v
v
v
v
v
v
ANR2729W
ANR2995E
ANR3008I
ANR3009E
ANR3095W
ANR3096I
ANR3178E
v
v
v
v
v
v
ANR3179E
ANR3180E
ANR3181E
ANR3199I
ANR3240W
ANR3241W
v ANR3486I
v ANR3548E
v ANR3613W
v
v
v
v
ANR4536E
ANR4587E
ANR4588E
ANR4591I
v ANR4592I
v ANR4593E
v ANR4594E
v
v
v
v
v
ANR4595E
ANR4596E
ANR4597E
ANR4598I
ANR4624I
v ANR4625W
v ANR4626I
v
v
v
v
v
v
v
ANR4763E
ANR4768E
ANR4865W
ANR4866I
ANR4897I
ANR4911E
ANR7804E Linux
v ANR7804E Solaris
v ANR8395E
v ANR8396E
Chapter 3. ANR: Server common and platform-specific messages version 6.3
51
v
v
v
v
v
ANR8397E
ANR8398E
ANR8399E
ANR8510E
ANR8511E
v
v
v
v
v
v
v
ANR8512E
ANR8513E
ANR8514W
ANR8515W
ANR8516W
ANR8517E
ANR8518E
v
v
v
v
v
v
ANR8519E
ANR8520E
ANR8521E
ANR8522E
ANR8523E
ANR8524W
v ANR8525E
v ANR8594I AIX
v ANR8594I HP-UX
v
v
v
v
ANR8594I Linux
ANR8594I Solaris
ANR8594I Windows
ANR8595I AIX
v ANR8595I HP-UX
v ANR8595I Linux
v ANR8595I Solaris
v
v
v
v
v
ANR8595I Windows
ANR8596E AIX
ANR8596E HP-UX
ANR8596E Linux
ANR8596E Solaris
v ANR8596E Windows
v ANR8597E AIX
v
v
v
v
v
v
v
ANR8597E HP-UX
ANR8597E Linux
ANR8597E Solaris
ANR8597E Windows
ANR8598I AIX
ANR8598I HP-UX
ANR8598I Linux
v ANR8598I Solaris
v ANR8598I Windows
v ANR8758W
52
v
v
v
v
v
ANR8762E
ANR8886E
ANR8998W
ANR8999E
ANR9000E
v ANR9001W
v ANR9002E
v ANR9003E
Version 6.3.0 ANR changed messages

The following version 6.3.0 ANR server messages are changed since version 6.2.0.
In addition to the message number, the message element that has changed is listed.
If the change is a blank space added or deleted, that change is visible when the
message appears in the activity log, but not when the message appears in the
published list of messages.
In the change descriptions below, if a message text changes only in casing or in
blank spaces, the distinction is noted. This distinction is not noted for changes to
the message explanation, system action, or user response.
Message Number
ANR0101E
ANR0102E
ANR0103E
ANR0104E
ANR0105E
ANR0106E
ANR0107W
ANR0124W
ANR0154E
ANR0155E
ANR0274E
ANR0379W
ANR0412I
ANR0454E
ANR0456W
ANR0504I
ANR0530W
ANR0874E
ANR0939E
ANR0946E
ANR1000I
ANR1001I
ANR1049W
ANR1055E
ANR1059I
ANR1063I
ANR1064I
ANR1065I
ANR1066I
ANR1079I
ANR1092E
Change
Message text
Explanation
User response
Message text
User response
Message text
Message text
Message text
User response
53
Message Number
ANR1095E
ANR1104E
ANR1108W
ANR1112W
ANR1113E
ANR1114E
ANR1119W
ANR1136W
ANR1142I
ANR1166E
ANR1167E
ANR1168W
ANR1172E
ANR1173E
ANR1176I
ANR1181E
ANR1186I
ANR1211I
ANR1212I
ANR1213I
ANR1214I
ANR1227E
ANR1234I
ANR1238I
ANR1239I
ANR1290I
ANR1298W
ANR1299E
ANR1330E
ANR1331E
ANR1332W
ANR1350E
ANR1351I
ANR1360I
ANR1363I
ANR1368W
ANR1370E
ANR1371I
ANR1372I
ANR1375I
ANR1383I
ANR1390E
ANR1393I
ANR1479I
ANR1508E
ANR1510I
ANR1511I
ANR1512I
ANR1514I
ANR1520I
ANR1521I
ANR1522I
ANR1530I
ANR1531I
54
Change
Message text (in casing or blank
Message text, user response
User response
Message text
Message text
spaces only)
spaces only)
spaces only)
spaces only)
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
spaces
spaces
spaces
spaces
spaces
only)
only)
only)
only)
only)
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
spaces only)
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
spaces
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
only)
Message Number
ANR1532I
ANR1535I
ANR1537I
ANR1545W
ANR1546W
ANR1550W
ANR1551W
ANR1552W
ANR1553W
ANR1554W
ANR1557W
ANR1558E
ANR1568E
ANR1588W
ANR1608E
ANR1616W
ANR1620E
ANR1621E
ANR1622E
ANR1658E
ANR1665E
ANR1676I
ANR1678I
ANR1685I
ANR1687I
ANR1688I
ANR1689E
ANR1693E
ANR1696E
ANR1697I
ANR1707
ANR1723E
ANR1726E
ANR1728E
ANR1740E
ANR1743E
ANR1746E
ANR1760E
ANR1767W
ANR1770E
ANR1772E
ANR1777I
ANR1787W
ANR1788W
ANR1801E
ANR1852E
ANR1854E
ANR1855E
ANR1859W
ANR1865I
ANR1866I
ANR1867I
ANR1868I
ANR2018E
Change
Message text
Message type
Message text
Message text (in casing or blank spaces only), explanation
User response
55
Message Number
ANR2153E
ANR2229W
ANR2238W
ANR2337W
ANR2338E
ANR2380E
ANR2576W
ANR2586W
ANR2678E
ANR2716E
ANR2968E
ANR4373E
ANR4502
ANR4510E
ANR4511E
ANR4767E
ANR7804 (AIX)
ANR7804
(HP-UX)
ANR7804
(Windows)
ANR7823S
(Linux)
ANR8355E
ANR8411E
ANR8439I
ANR8440E
ANR8441E
ANR8578E
(Windows)
ANR8591E
(Windows)
ANR8773E
ANR8779E
ANR8840E
ANR8883W
ANR8970E
ANR8971E
ANR8988
ANR8992E
ANR8993I
ANR9741E
Change
Explanation
User response
Message text
Message text
Message text
User response
User response
User response
Message type, message text, explanation, system action, user response
Message text
Message type, message text, explanation, user response
User response
User response
Explanation
Message text
Message text
Message text
Message text
Message text
Message type, user response
Explanation

The following ANR messages existed before version 6.3.0 but are not in version
6.3.0. Only the message ID is listed.
v ANR0361E
v ANR2594E
56
ANR0100E ANR0105E
Version 6.3.0 ANR messages

Tivoli Storage Manager server version 6.3.0 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.
ANR0100E
Source file(line number): Error error code

creating table "table name".
Explanation: An internal error has occurred in an

attempt to create a server database table. This message
always accompanies another error message and
provides more detail about that error.
was updated in a server database table. This error

message always accompanies another error message
which provides more details about the error.
System action: The activity that generated this error
fails.
Explanation: An internal error occurred when a server

database table was being accessed. This error message
always accompanies another error message which
provides more details about the error.
User response: An error occurred when a row was

inserted into a server database table. Typically, this
error causes an error code value of 2 to be displayed.
An error code value of 2 indicates that the record being
updated does not exist in the database. This type of
error might be caused by a timing issue with the server
or a synchronization issue involving server processes,
client sessions, or other server actions. Review the
activity log file to determine what operations were in
progress and were affected by this error. Try the
operation again and change the timing so that it does
not run with the same processes or actions as when the
error occurred.

fails.
ANR0104E

fails.
User response: Contact your service representative.
ANR0101E

opening table "table name".
User response: If the server or storage agent stops in

response to a HALT command, you can ignore this
error message.
ANR0102E

inserting row in table "table name".
Explanation: An internal error occurred when data

was added to a server database table. This error
message always accompanies another error message
which provides more details about the error.
fails.
inserted into a server database table. Typically, this
inserted already exists in the database. This type of
error occurred.
ANR0103E

updating row in table "table name".

deleting row from table "table name".

was being removed from a server database table. This
error message always accompanies another error
message which provides more details about the error.
fails.
deleted from a server database table. Typically, this
deleted does not exist in the database. This type of
error occurred.
ANR0105E
Source file(line number): Error setting

search bounds for table "table name".

was being accessed from a server database table. This
fails.
57
ANR0106E ANR0113E
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
change the timing so that it does not run with the same
processes or actions as when the error occurred.
ANR0106E
Source file(line number): Unexpected error

error code fetching row in table "table
name".

was being accessed from a server database table. This
fails.
User response: Review the activity log to determine
what operations were in progress and were affected by
this error. Try the operation again and change the
timing so that it does not run with the same processes
or actions as when the error occurred.
ANR0107W
Source file(line number): Transaction

transaction ID was not committed due to
an internal error.
Explanation: An internal error was detected during

transaction commit. This message is typically preceded
by another error message which provides more details
about the error.
User response: Verify that the ICC cryptography

directory is located in either the application root
directory or the directory specified in the platform
specific environment variable (the DSMSERV_DIR for
Unix platforms or the Windows registry).
ANR0110E
Explanation: The server has noted that the current

system date is suspect. It is earlier than the server
install date or has suddenly moved into the future by
30 days or more.
System action: The server is disabled for client, server
and administrative access. Most server processes will
not execute.
User response: If the current system date is not valid,
reset the date. Use the ACCEPT DATE command to
establish the current date as valid on the server. After
executing this command, you can use the ENABLE
SESSIONS ALL command to enable the server for
sessions. Accepting an invalid date can cause any of the
following problems: Premature deletion of data
Excessive retention of data Scheduling problems Event
record problems Password expiration problems.
ANR0111E

fails.
User response: Review the activity log to determine
what operations were in progress and were affected by
this error. Try the operation again and change the
timing so that it does not run with the same processes
or actions as when the error occurred.
ANR0108E
Source file(line number): could not start a

new transaction.
Explanation: An error occurred while attempting to

start a new transaction. Possibly there is not enough
memory.
fails.
User response: See the documentation for the
operating system about how to increase memory for an
application.
ANR0109E
Attempt number att_num Unable to load

cryptography module from 'icc location'.

load the cryptography module.
Command: The BEGINNODEID and

ENDNODEID are both required to be
specified.
Explanation: The BEGINNODEID and ENDNODEID

are both required to be specified or neither of them are
required.
System action: The server fails the command.
User response: Reissue the command, specifying both
BEGINNODEID and ENDNODEID, or neither of them.
ANR0112E
Command: The specified

BEGINNODEID node id is greater than
the ENDNODEID node id.
Explanation: Either the BEGINNODEID or the

ENDNODEID is invalid because the value of the
BEGINNODEID is greater than the ENDNODEID.
User response: Reissue the command, specifying the
ENDNODEID to be greater than the BEGINNODEID,
or both to be equal.
ANR0113E
System action: The application will not start.
58
An unexpected system date has been

detected; the server is disabled. Verify
the system date and use the ACCEPT
DATE command to establish the current
date as valid.
Command: The storage pool list specified

with the parameter parameter name
includes storage pool storage pool name
more than once for simultaneous write.
ANR0114E ANR0120I
Explanation: The storage pool name specified has
been specified more than once. The name occurs more
than once in the COPYSTGPOOLS list, more than once
in the ACTIVEDATAPOOLS list, or it has been
specified in both lists.
User response: Reduce the number of parallel

commands or scripts that are running on the server at
any one time.
ANR0117E
System action: The command fails.

User response: Reissue the command specifying
unique storage pool names.
ANR0114E
Command: The NUMBER parameter is

required on this command. The current
default value is 0.
Explanation: The NUMBER parameter is required for

the FORMAT LFVOLUME COMMAND when the
LFVOLUMEFORMATCOUNT option is set to 0.
System action: The command is not executed.
User response: Either reissue the command with the
NUMBER parameter or else use the the SETOPT
command to change the LFVOLUMEFORMATCOUNT
value.
ANR0115W
The server script script name attempted

to start more parallel commands than
are allowed for a single script. A single
script is limited to parallel command limit
parallel commands.
Explanation: The server waits for all previous parallel

commands started by the script to complete. When all
previous parallel commands are complete, the server
allows the script to continue. The script can attempt to
start more parallel commands.
System action: The server waits for all previous
parallel commands before allowing the script to
continue.
User response: If you need to start more parallel
commands than the script limit allows, modify the
script to invoke multiple scripts in parallel, each of
which can start multiple parallel commands, up to the
script limit.
ANR0116W
The server script script name attempted

to start more parallel commands than
are allowed for the server. The server is
limited to parallel command limit parallel
commands.
Explanation: The server waits for all previous parallel

commands started by the script to complete. When all
previous parallel commands are complete, the server
allows the script to continue. The script can attempt to
start more parallel commands. If the limit is exceeded,
the command will run serially.
System action: The server waits for all previous
parallel commands before allowing the script to
continue.
The server contains stored data. Archive

data retention protection cannot be
changed.
Explanation: The archive data retention protection

state cannot be changed while the server contains any
backup, archive, or space-managed data.
User response: In order to change the archive data
retention protection state, the server must contain no
backup, archive, or space-managed data. Either
re-initialize the server database, or delete all stored
data and try the command again.
ANR0118W
The client option client option is not

valid and will not be sent to the client.
Use the INCLEXCL option instead.
Explanation: The client options INCLUDE and

EXCLUDE are not valid and have been replaced by the
combined INCLEXCL. If INCLUDE and EXCLUDE are
used in client option sets, use the INCLEXCL option
along with the specific include or exclude option that
you want the clients to use.
System action: The option is ignored and is not sent
to the client. The server continues processing.
User response: Client options INCLUDE and
EXCLUDE are not valid; use the INCLEXCL option
along with the specific include or exclude option that
you want the clients to use.
ANR0119W
The client option client option is not

valid and will not be sent to the client.
Delete it from client option set.
Explanation: The client option is not supported by

this server and should be deleted from the client option
set.
System action: The option is ignored and is not sent
to the client. The server continues processing.
User response: Delete the option from the option set.
Check the documentation for a possible replacement for
the option.
ANR0120I
Archive data retention protection is set

to state of archive data retention protection.
Explanation: The archive data retention protection

state has been set.
59
ANR0121E ANR0130E
ANR0121E
command is not allowed when archive

data retention is enabled.
Explanation: The specified command is not allowed

when archive data retention protection is enabled on
the server.
ANR0126W
DELETE VOLUME: Volume volume name

contains retention protected data and
can not be deleted.
Explanation: The specified volume cannot be deleted

because it contains one or more objects that must be
retained because of one of the following:
v Archive retention protection is enabled and the
object's retention period has not elapsed.
v The object is part of a deletion hold.
ANR0122E
command: A node cannot be assigned to

a new domain when archive data
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

ANR0123E
command: A device type of SERVER is

not allowed when archive data retention
is enabled.
Explanation: The specified device type is not allowed

when archive data retention protection is enabled on
the server.
ANR0124W
Object object name (object id hi ) for node

node name (node id), filespace filespace
name (filespace id) is retention protected
and can not be deleted.
Explanation: The specified object can not be deleted

because:
object's retention period has not elapsed, or
command to another server is not

allowed when data retention protection
is enabled on the target server.
Explanation: The specified command is not allowed

when data retention protection is enabled on the target
server.
ANR0128W
The previous database upgrade did not

complete successfully.
Explanation: At server startup, the server discovered

that a previously started database upgrade operation
did not complete successfully. To complete the database
upgrade, specify the UPGRADEDB parameter when
starting the server.
User response: Check the server error messages on
console to determine the reason the previous database
upgrade did not complete successfully. Correct the
problem, and perform the database upgrade again, if
possible. If the problem cannot be corrected, contact
your service representative.

System action: Server operation continues.
ANR0129I

ANR0125W
DELETE FILESPACE filespace name for

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:
object's retention period has not elapsed.
System action: The file space is not deleted.
60
Database upgrade completed

successfully.
Explanation: The requested database upgrade

operation completed successfully.
ANR0130E
Diagnostic(ID): Server LOG space

exhausted.
Explanation: There is no space to write data to the

server recovery log.
fails.
User response: To increase the amount of log space
ANR0131E ANR0138E
available to the server, evaluate the directories and
filesystem assigned to the ACTIVELOGDIR,
ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. An
out of log space condition may occur because the
ACTIVELOGDIR location is full. Alternatively, an out
of log condition may occur if the log files in the
ACTIVELOGDIR which are no longer active can not be
archived to the ARCHIVELOGDIR and
ARCHFAILOVERLOGDIR locations. If necessary, a
larger ARCHIVELOGDIR or ARCHFAILOVERLOGDIR
can be specified by updating this option in the
dsmserv.opt file and then restarting the server.
ANR0131E
Diagnostic(ID): Server DB space

exhausted.
Explanation: There is no space to write data to the

server database.
fails.
User response: To increase the amount of database
space available to the server, an authorized
administrator can add database volumes by using the
DEFINE DBSPACE command. Once additional space
has been added for the database, the server database
manager will automatically extend into that space and
use it.
ANR0132E
Diagnostic(ID): Memory allocation failed:

object object name, size size.
Explanation: The server cannot obtain enough

memory to create the object named.
fails.
application.
ANR0133E
Error loading module modname: error

string
Explanation: The error specified by error string

occurred when the server attempted to load module
modname
System action: Server operation continues, but the
function provided by the module is not available.
User response: Refer to the error string and correct
the condition causing the load to fail.
ANR0134W
There is an error reading from standard

input; the console input daemon
stopped.
User response: If the server was started in the

background, there is no error, or else standard input is
in an error state.
ANR0135I
Table maintenance performed

successfully for processed tables of total
tables.
Explanation: The server periodically performs

maintenance on the database tables. The maintenance
processing allows the database to update statistics used
to determine how to best access a given table. The
maintenance processing will periodically process all
tables for the server. And during other processing
cycles, it will only process those tables that have
changes such as inserts, updates, or deletes for records
in that table.
User response: No user action required.
ANR0136I
Table updating statistics performed

successfully for processed tables of total
tables.
Explanation: The server periodically performs

maintenance on the database tables. The maintenance
processing allows the database to update statistics
determine how to best access a given table. The
maintenance processing will periodically process all
tables for the server.
ANR0137E

allocating num rows database rows.
Explanation: An internal error has occurred in an

attempt to allocate storage for the requested number of
database rows indicated.
fails.
ANR0138E
Value primary logs for number of

primary logs is invalid.
Explanation: The command has been issued with an

invalid number of primary logs.
System action: Server installation stops.
User response: Reissue the command with a valid
number of primary logs.
Explanation: Warning: warning string

System action: Server operation continues, but
standard input is not available.
61
ANR0139I ANR0149E
ANR0139I
This command has been disable for

DB2.
Explanation: During DB2 development cycle. This

command/function has been temporarily disable.
System action: System operation continues.

User response: Verify that both nodes have been
defined to the server and then issue the command
again.
ANR0145E

ANR0140I
Command: success. Node node_id_1 is

granted proxy authority to node
node_id_2.
Command: failed. Node node_id_1 already

has been granted proxynode authority to
node node_id_2.
Explanation: The command failed because a proxy

relationship between the two nodes already exists.
Explanation: The command was successful.
System action: The server fails the command, but

does not change the existing association.
System action: The server performs the command.

ANR0146E
ANR0141E
Command: failed. Node node_id_1 was not

granted proxynode authority to node
node_id_2.
Explanation: The command fails if either of the nodes

do not exist, or if the administrator issuing the
command does not have sufficient authority.
Explanation: The command failed because a node

cannot have a proxy relationship defined to itself.
ANR0147E
User response: Verify that both nodes exist and that

the administrator has sufficient authority, then issue the
command again.
ANR0142I
Command: success. Proxynode authority

for node node_id_1 has been revoked
from node node_id_2.
Explanation: The command was successful.

System action: The server performs the command.
ANR0143E
Command: failed. Proxynode authority

for node node_id_1 has not been revoked
to node node_id_2.
Explanation: The command fails if the administrator

issuing the command does not have sufficient authority.

granted proxynode authority to itself.
Command: failed. Proxy node authority

for node node_id_1 to node node_id_2 was
not revoked because node
node_id_missing has not been defined to
the server.
Explanation: The command failed because one of the

nodes has not been defined to the server.
User response: Verify that both nodes have been
defined to the server, and then issue the command
again.
ANR0148I
Command: No proxy relationships were

found.
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
unrestricted policy authority; then issue the command
again.
ANR0144E

granted proxynode authority to node
node_id_2 because node node_id_missing
has not been defined to the server.
ANR0149E
Explanation: The command failed. The requested

filespace was deleted concurrently with the command.
System action: The server will fail the command.
User response: Retry the command.
Explanation: The command failed because one of the

nodes has not been defined to the server.
62
Filespace filespace for node node_name

was deleted concurrently with the
command.
ANR0150E ANR0158W
ANR0150E
Failed to open object object_name. There

was an error decrypting the
password_type password.
Explanation: The server could not open the object

specified due to the error encountered while decrypting
the password.
System action: The server will fail the related
command or action.
User response: Reset the password using the
appropriate UPDATE command and retry the failing
command or action.
ANR0151W
Command: The number of active data

pool names specified with the
ACTIVEDESTINATION parameter
cannot exceed 10.
Explanation: The maximum number of active data

pool names that you can specify with the
ACTIVEDESTINATION parameter is 10. You may enter
up to 10 unique names, separated by commas.
User response: Reissue the command specifying up to
10 unique active-data pool names separated only by
commas.
Failure starting database manager.
Explanation: The server was unable to start the

database manager.
System action: The server operation terminates.
User response: If the server is not able to run without
the database manager. Evaluate recent changes to the
server machine and the available system error logs to
try to determine the cause of the failure.
ANR0152I
ANR0155E
Database manager successfully started.
Explanation: The server was successfully able to start

the database manager.
ANR0156E
Command: The pool active data pool name

with pool ID pool ID is not an active
pool.
Explanation: The storage pool specified is not an

active-data pool. Only active-data pools are allowed to
be specified in the ACTIVEDESTINATION parameter.
User response: Reissue the command specifying ten or
fewer active-data pool names.
ANR0157W
System action: The server operations continue.
Database operation table operation for

table table name failed with result code
op code and tracking ID: id.
Explanation: An error occurred during the specified

table operation for the table indicated.
ANR0153I

fails.
Database manager already running.
Explanation: The server database manager is already

running.
System action: The server continues startup.
ANR0154E
Command: The active data pool list that

you specified with the
includes active data pool active data pool
name that is a duplicate. All names must
be unique.
Explanation: You may enter up to 10 unique active

data pool names specified with the
ACTIVEDESTINATION parameter.
unique active-data pool names.
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
resulted in a failure for a client session or server
process, this information is needed to help diagnose the
issue. In the even of a failure, please contact your IBM
service representative for further assistance.
ANR0158W
Database operation table operation for

table table name failed with operation
code op code and tracking id tracking
number. The data for column column
number is: column data.
Explanation: An error occurred during the specified

table operation for the table indicated.
fails.
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
resulted in a failure for a client session or server
process, this information is needed to help diagnose the
63
ANR0159E ANR0166I
issue. In the even of a failure, please contact your IBM
ANR0159E
Diagnostic(ID): Database deadlock

detected on DB2 Statement Handle.
Explanation: The database server detected a deadlock

situation and rolled back the outstanding work on this
statement handle. When server processes encounter a
database deadlock, they usually reattempt the work
that was in progress when the deadlock was
encountered. Not all processes can explicitly try an
operation again. For example, migration and
reclamation will eventually be tried again. However,
something such as a delete volume run in a macro will
only be tried again if the delete command is reissued
either in the macro or the command line.
System action: The work being done on the statement
handle is rolled back. Some processes will attempt to
retry the request. Others will just stop. Server operation
continues.
User response: If a process can retry (like migration),
then monitor the re-try attempt to see if it succeeds or
not. If the process or command is not able to retry on
it's own, then reissue the command or macro that
caused the action to occur.
ANR0160I
Displaying segment segment number of

total segments for client object object
identifier with text: object name.
Explanation: Display a client object, such as a file or

directory, that uses a long fully qualified name. The
name is displayed in smaller segments until the entire
name is shown. The segment numbers are incremented
from 1 to N until all the segments for this object name
are displayed.
System action: The fully qualified name for this object
is displayed.
ANR0161I
Displaying segment segment number for

message insert insert identifier with text
segment text.
Explanation: Display a segment of a message insert

that was too long to be displayed within the specified
message. There may be one or more segments
displayed for a given message insert.
System action: The entire message insert segment is
displayed.
64
ANR0162W
Supplemental database diagnostic

information: dbReturnCode:dbState:dbCode
(dbErrorMessage).
Explanation: The dbReturnCode, dbState, and dbCode are

displayed as supplemental information. This
information should be used in conjunction with any
other database error or warning messages issues to
assist with diagnosing a given issue.
fails.
User response: None. This is supplemental
information corresponding to another database error or
warning message issued.
ANR0163E
Diagnostic(ID): Database insufficient

memory detected on DB2 Statement
Handle.
Explanation: The database server detected an

insufficient memory condition and rolled back the
outstanding work on this statement handle.
System action: The work being done on the statement
handle is rolled back. Server operation continues.
application.
ANR0165I
Inventory file expiration started

processing for node nodename, filespace
filespace name, copygroup copygroup and
object type type.
Explanation: Inventory file expiration processing

started processing for the node name and filespace name
indicated. For this node name and filespace name the
indicated copygroup and object types are currently
being evaluated.
System action: Inventory file expiration continues.
User response: This message is for informational
purposes only and is only displayed if the expiration
processing is executed with QUIET=NO.
ANR0166I
Inventory file expiration finished

processing for node nodename, filespace
filespace name, copygroup copygroup and
object type type with processing
statistics: examined examined, deleted
deleted, retrying retrying, and failed failed.
Explanation: Inventory file expiration processing

finished processing for the node name and filespace name
indicated. For this node name and filespace name the
indicated copygroup and object types were evaluated.
And the ending statistics show the number of objects
examined, deleted, retrying and those that failed to be
processed.
ANR0167I ANR0173I
processing is executed with QUIET=NO.
ANR0167I
Inventory file expiration process process

ID processed for minutes minutes.
Explanation: Server expiration processing ran for the

indicated number of minutes.
ANR0171I
Diagnostic(ID): Error detected on DB2

Statement Handle, database in evaluation
mode.
Explanation: The TSM server encountered an error on

the database and will take action to determine the type
of error and whether or not it can recover from the
error.
System action: Server processing continues.

ANR0168I
be started, manually issue the DB2 RESTART DB

command, then attempt to start the TSM server again.
Analyst authority for administrator

admin name will be ignored. Analyst
authority is not supported on this
server.
Explanation: Analyst authority is not supported for

servers at V6.1 or later.
User response: This is an information message. As the

TSM server attempts to resolve the error, it might issue
other messages. Follow the instructions indicated in
any associated messages.
ANR0172I
Diagnostic(ID): Error encountered

performing action action.
Explanation: The TSM server encountered an error

performing the specified database action. This error
caused the action to fail and prevented the server from
being able to continue.
ANR0169E
System action: Server processing terminates, the

requested action fails.
System action: The operation continues.
An unexpected error has occurred and

the TSM server is stopping.

from which it cannot recover, and the server is halting.
Other messages will be issued along with this message
indicating the specific error conditions which have
occurred.
System action: The server halts.
User response: Follow the instructions indicated in
any associated messages, then start the server.
ANR0170E
Diagnostic(ID): Error detected on DB2

Statement Handle, database restart
required.
Explanation: The TSM server encountered an error on

the database and needs to issue a DB2 RESTART DB to
the database manager. All connections to the database
server are severed, and uncompleted operations are
aborted. The TSM server will then restart the database
and attempt to continue. If the database manager
cannot be restarted, the TSM server will halt. Other
messages may be issued along with this message
indicating the specific error conditions which have
occurred.
System action: The server continues, or if it cannot
restart the database, it halts.
User response: If the server is able to recover, no
action is needed, except to restart operations that were
aborted. However, if the server cannot recover, it will
halt. Follow the instructions indicated in any associated
messages, then start the server. If the server still cannot
User response: Review other messages issued to

determine the actual error and then take steps to
remedy that failure before retrying the operation.
ANR0173I
The database failed action action because

of insufficient system memory available.

while performing the specified action. Specifically, the
server database did not have sufficient memory to
communicate with the server database or was unable to
acquire the memory needed for the server buffer pools.
System action: Server processing terminates, the
requested action fails.
User response: In most cases, this indicates a lack of
available resources on the system. This may be a lack
of physical resources or it may be an environment
setting that prevents the server from having access to
the needed resources. For instance, on Linux systems,
this may be caused by the SHMMAX value (maximum
allowed shared memory) being set too low. On Linux,
this can be viewed using the command "ipcs -l".
Similarly, for Linux, this value can be increased using
the command "sysctl -w kernel.shmmax=nnn" where
nnn is the new maximum memory value to assign to
be used for shared memory. As a general
recommendation, this value should be set to
approximately 1.25 GB or higher depending upon the
actual physical memory (RAM) available on that
system.
65
ANR0174E ANR0190I
ANR0174E
Diagnostic(ID): Maximum DB2

connections reached on DB2 Handle.
Explanation: There are no more available connections

to the server database.
fails.
User response: To increase the number of database
connections available to the server, the DB2
administrator can modify the IDBACK parameter in the
DSNzPARM settings.
ANR0175E
Diagnostic(ID): Space exhausted for one

or more of the following: DB, LOG, or
instance directory.
ANR0186E
Explanation: If the server is starting, then the user ID

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
to perform the server operations.
System action: The server process ends, and the
server stops if it is running.
User response: Ensure that the user ID under which
the server is running is authorized to start the database
manager. Take the following actions:
v Log in to the user ID for your Tivoli Storage
Manager instance and start the server.
To run the server using the root user ID on a
UNIX system, add the root user ID to the primary
group of the Tivoli Storage Manager instance user
ID.
Explanation: The space assigned to the server

database, the recovery log, or instance directory has
been exhausted.
System action: The server terminates.
User response: Review the filesystems or other space
assigned to the server for the database, recovery log or
instance directory. If the space assigned to the database
is full, restart the server and add additional database
space using the EXTEND DBSPACE command or use
the DSMSERV EXTEND DBSPACE utility. If the server
ACTIVELOGDIR is full, update this server option to a
new location that has space available for the server to
use for logging changes to the database. If the server
instance directory is full, remove unneeded files or else
extend this filesystem.
Please note that the server should be configured with
the database, activelog, and archivelogs using different
directories and storage devices. For example, if the
database and activelog are configured to use the same
directory and underlying storage device, this may
adversely impact performance. This may also
compromise the server's ability to manage the database
and active log space effectively. Similarly, the server's
instance directory should also be monitored and
managed with some amount of space available. The
server instance directory is used to record and log some
server and database actions.
ANR0185E
The data in primary storage pool name can

not be copied to active data pool name.
The active-data pool is not defined to a
domain.

User response: Define the active-data pool to a
domain using the ACTIVEDESTINATION parameter on
either the DEFINE DOMAIN or UPDATE DOMAIN
command.
There is insufficient authority to start

Or, to run the server using the instance user ID on

a UNIX system, when using the automatic start,
specify the -u option when you start the server.
ANR0187E
Database db name was not found.
Explanation: The server attempted to open the

database, but it was not found by the database
manager. If this occurs immediately after formatting a
new database, it could mean the format operation
failed.
System action: The server process ends.
User response: Ensure that you format the database
before starting it the first time. Ensure that all database
and log directories are online and available.
ANR0188E
Fail to start the database manager.

Database manager license not found
Explanation: Could not find database manager license.

ANR0189E
Fail to start the database manager.

Database manager license has expired
Explanation: Database manager license has expired.

ANR0190I
Inventory file expiration started

processing node node name for backup
sets.
Explanation: Expiration processing is currently

evaluating information for backup sets for the node
specified.
66
ANR0191I ANR0200I
ANR0197E

processing is invoked with QUIET=NO.
ANR0191I
Inventory file expiration finished

processing node node name for backup
sets with processing statistics: examined
examined, deleted deleted, retrying
retrying, and failed failed.
Explanation: Expiration processing has finished

processing backup sets for the node specified.The
ending statistics show the number of objects examined,
deleted, and those that failed to be processed.
processing is invoked with QUIET=NO.
ANR0193E
The REPAIR EXPIRATION TYPE=type

command cannot be issued from the
server console.
Removal of extraneous database entries

for volume volume name failed due to
contention with other server processes
or activities.
Explanation: The server was not able to remove

extraneous database entries for the specified volume.
This was due to contention with another server process
or activity.
System action: System operation continues and this
volume still has extraneous database entries.
User response: It is possible that future server
activities or processes will select this volume and
attempt to repair it. If this occurs and the future
attempt is successful, no further action is needed. The
server administrator should review the activity log for
the time that the repair was attempted and try to
determine what caused the contention. If you are
unable to determine the cause of the contention of the
problem persists, please contact your service
representative for additional assistance.
ANR0198E

for volume volume name failed.
Explanation: The specified REPAIR EXPIRATION

command was issued from the server console. This
command cannot be issued from the server console
because the administrator must be prompted to
continue processing the command.

System action: The server ignores the command and

continues processing.
User response: The server administrator should

review the activity log for the time that the repair was
attempted and try to determine the cause of the failure.
If you are unable to determine the cause of the
contention of the problem persists, please contact your
service representative for additional assistance.
User response: Issue the command from an

administrative client.
ANR0195W
Attempting to remove extraneous

database entries for volume volume name.
System action: System operation continues and this

volume still has extraneous database entries.
ANR0199W
Explanation: The server is attempting to remove

System action: TSM will attempt to remove the
extraneous database entries for this volume.
User response: Review the completion messages for
this volume to determine if the removal of the
extraneous database entries was successful or if an
error was encountered.
ANR0196I

for volume volume name was successful.
Not possible to repair volume volume

name due to other database references to
this volume.

extraneous database entries for the specified volume
because other database references to this volume exist.
User response: The volume repair operation for this
volume is not able to take any action because other
unexpected database references to this volume exists.
For additional assistance contact your IBM service
representative.
Explanation: The server successfully removed

ANR0200I
System action: System operation continues and future

operations on the specified volume should work
normally.
Explanation: The amount of space allocated to the

recovery log is shown.
User response: The server successfully repaired the

specified volume.
Recovery log assigned capacity is size

megabytes.
67
ANR0201I ANR0209E
ANR0201I
Database assigned capacity is size

megabytes.
Explanation: The amount of space allocated to the

database is shown.
ANR0202W
ANR0206W
Database volume volume name varied

offline due to excessive read errors.
Explanation: The database volume shown has been

varied offline because too many read errors have been
encountered.
Explanation: During a write of a database page, an

error occurred so that the page was not completely
written to disk.
System action: The failed I/O operation is retried on a
mirrored volume.
User response: See accompanying messages for
information about the volume in error.
ANR0207E
System action: If available, a mirrored copy of the

volume is used.
User response: Correct the cause of the read errors.
ANR0203W

offline due to excessive write errors.
Partial write detected on database

volume volume name, logical page logical
page number (physical page physical page
number).
Page address mismatch detected on

database volume volume name, logical
page logical page number (physical page
physical page number); actual: logical page
number.
Explanation: During a read of a database page, the

page does not contain the expected page address.
mirrored volume.
Explanation: The database volume shown has been

varied offline because too many write errors have been
encountered.


volume is used.
ANR0208W
User response: Correct the cause of the write errors.

ANR0204W
Recovery log volume volume name varied

offline due to excessive read errors.
Explanation: The recovery log volume shown has

been varied offline because too many read errors have
been encountered.
volume is used.
User response: Correct the cause of the read errors.
ANR0205W
Partial write detected on recovery log

volume volume name, logical page logical
page number (physical page physical page
number).
Explanation: During a write of a recovery log page,

an error occurs so that the page is not completely
written to disk.
mirrored volume.
ANR0209E

offline due to excessive write errors.
Page address mismatch detected on

recovery log volume volume name, logical
page logical page number (physical page
physical page number); actual: logical page
number.
Explanation: The recovery log volume shown has

been varied offline because too many write errors have
been encountered.
Explanation: During a read of a recovery log page, the

page does not contain the expected page address.

volume is used.

mirrored volume.
User response: Correct the cause of the write errors.

68
ANR0210S ANR0219I
ANR0210S
Inconsistency found in LVM data page

page number - partial write detected.
Explanation: During a write of an LVM internal page,

an error occurs so that the page is not completely
written to disk.
mirrored volume.
ANR0211S
Inconsistency found in LVM data page

page number - page address mismatch
(actual page number).
Explanation: During a read of an LVM internal page,

the page does not contain the expected page address.
ANR0215W
Recovery log volume volume name is in

the offline state - VARY ON required.
Explanation: At system startup, the server finds that

the recovery log volume shown is in the offline state.
System action: The volume is not accessed.
User response: Determine the reason for the volume
being offline; if possible, vary it online.
ANR0216I
Database volume volume name is in the

"stale" state - synchronization process
started.

the database volume shown is not synchronized.
System action: A process is started to synchronize the
volume.

mirrored volume.

ANR0217I
ANR0212E
Unable to read disk definition file file

specification.
Explanation: At startup, the server cannot read the

indicated file in order to obtain a list of disk volumes
to mount.

the recovery log volume shown is not synchronized.
System action: A process is started to synchronize the
volume.
System action: Server initialization fails.

User response: Use a text editor to recreate the file; it
should contain one line with the name of a single log
or database volume. Then restart the server.
ANR0213W
Unable to rewrite disk definition file.
Explanation: An error occurs trying to update the disk

definition file.
User response: Attempt to determine the cause of the
write error and correct it.
ANR0218I
Database volume volume name is in the

offline state - VARY ON required.

the specified database volume is in the offline state.
System action: The volume is not accessed.
User response: Determine the reason for the volume
being offline; if possible, vary it online.
Unable to install database volume

volume name - capacity must be at least 5
megabytes.
Explanation: An attempt has been made to add a

database volume that is smaller than the server
minimum.
System action: The volume is not added.
User response: Increase the size of the volume or
supply another larger volume.
ANR0219I
ANR0214W
Recovery log volume volume name is in

the "stale" state - synchronization
process started.
Unable to install recovery log volume

volume name - capacity must be at least 5
megabytes.
Explanation: An attempt has been made to add a

recovery log volume that is smaller than the server
minimum.
System action: The volume is not added.
User response: Increase the size of the volume or
supply another larger volume.
69
ANR0220I ANR0228S
ANR0220I
Synchronization of database volume

volume name started as process process ID.
Explanation: A background process was started to

synchronize the contents of the database volume shown
with its copy volume. The background process was
assigned the process ID shown.
System action: The background process starts to
synchronize the volume and server operation continues.
User response: The administrator may query the
status of the background process by using the QUERY
PROCESS command, or cancel the process by using the
CANCEL PROCESS command.
ANR0221I
Synchronization of recovery log volume

volume name started as process process ID.

synchronize the contents of the recovery log volume
shown with its copy volume(s). The background
process was assigned the process ID shown.
System action: The background process starts to
synchronize the volume and server operation continues.
PROCESS command, or cancel the process by using the
ANR0222E
Error action disk definition file file

specification.
Explanation: An error occurred creating or changing

the disk definition file.
write error and correct it.
ANR0223E
Error writing list of disks to disk

definition file.
Explanation: The disk definition file cannot be

written.
System action: Installation ends.
User response: Determine the cause of the write error
and correct it.
ANR0224E
Volume volume name is specified more

than once - server installation failed.
Explanation: The specified volume name was

specified more than once in the server installation
execution.
System action: Installation ends.
User response: Reinitialize the server install specifying
70
a unique name for each database and recovery log

volume.
ANR0225S
Invalid use of the -S command-line

option.
Explanation: The -S option cannot be specified on the

command line if the database ID file (dsmserv.dbid) is
intact. This option is to be used only if the ID file does
not exist.
System action: The server does not start.
User response: Start the server without specifying the
-S command-line option.
ANR0226S
The database ID file could not be found

for server startup.
Explanation: The server's database ID file

(dsmserv.dbid) could not be found. This file is created
when the database is formatted, is stored in the
directory from which the format is performed, and is
required for normal server operation.
User response: Ensure that you are starting the server
from the correct instance directory, and that the
dsmserv.dbid file exists and can be read. If no
dsmserv.dbid file exists, restart the server with the -S
option to create a new database ID file.
ANR0227S
Incorrect database opened. Server

cannot start.
Explanation: The ID of the database opened does not

match the ID stored in the database ID file
(dsmserv.dbid).
User response: Ensure that you are in the proper
instance directory for the database being opened, and
that the environment is set up correctly. The instance
directory is generally the directory from which you
formatted the database, or, if on UNIX, have specified
with the -i command-line option.
When the ID of the database that is opened does not
match the ID that is stored in the database ID file
(dsmserv.dbid), the server will not start. Use the -S
(skip DB ID check) parameter after deleting the
dsmserv.dbid file. After the initial use of the -S
parameter in a restore scenario, the server creates a
new dsmserv.dbid file in the instance directory.
ANR0228S
Error errno opening the database ID file

for server startup.
Explanation: The server's database ID file

(dsmserv.dbid) could not be opened. The errno
indicates the reason for the failure.
ANR0229W ANR0238E
ANR0233I
User response: Ensure that you are starting the server

from the correct instance directory, and that the
dsmserv.dbid file has the correct ownership and
permission. If the file is empty, erase the file, and
restart the server with the -S command-line option to
generate a new database ID file.
ANR0229W
Server is unable to add entries to the

Activity Log. Console messages will not
be logged until database access is
available.
Explanation: The process that monitors the default

(console) output stream and maintains the activity log
cannot update the activity log. The error is due to the
inability of the server to access the server database.
System action: The server does not update the activity
log. The activity log will continue to run and attempt
to recover from this situation.
User response: Access to the server database is
temporarily unavailable. The server database manager
will attempt to recover from this situation and
reestablish access to the server database. When access
to the server database is reestablished, the activity log
processing will continue. If the server database access
fails to be reestablished, additional messages will be
issued providing more information.
Explanation: The process that was attempting to

synchronize the database volume shown has been
canceled.
System action: The volume is in the stale state.
User response: If desired, issue a VARY ONLINE
command to start another synchronize process.
ANR0234I
System action: The volume is varied online.

ANR0235I

User response: See accompanying messages for more
information.
ANR0231E
Synchronization process failed for

recovery log volume volume name.
Synchronization complete for recovery

log volume volume name.
Explanation: The synchronization process for the

recovery log volume named has finished successfully.
Synchronization process failed for

database volume volume name.

synchronize the database volume shown has failed.
Synchronization complete for database

volume volume name.
Explanation: The synchronization process for the

database volume named has finished successfully.
ANR0236E
ANR0230E
Synchronization process canceled for

Fail to start the database manager due to

an I/0 error. Check for filesystem full
conditions, file permissions, and
operating system errors.
Explanation: The TSM server encountered an I/O

error while attempting to start the database manager.
User response: Review the filesystems assigned to the
server for the database and recovery log.
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.
Some common reasons for this error are:

information.
ANR0232I
Synchronization process canceled for


synchronize the database volume shown has been
canceled.
User response: If desired, issue a VARY ONLINE
command to start another synchronize process.
v The system name where you ran the server has been
changed
v The system date and time is set incorrectly
ANR0238E
A database recovery task is prohibiting

activation of db name with sqlcode
dbCode.
Explanation: While attempting to activate the database

an error occured because the database was busy
71
ANR0239E ANR0246E
performing a BACKUP, RESTORE or was in
ROLLFORWARD pending state. Examine the sqlcode to
determine the condition that is preventing the database
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
( -1116 ) indicates a database BACKUP is pending and
must complete prior to activating the database. Once
the database BACKUP is complete,the database can be
activated by starting the server.
SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates a
database Roll Forward operation is pending and must
complete before activating the database. After the Roll
Forward recovery step is complete, the database can be
SQLE_RC_BKP_INPROG ( -1118 ) occurs when an
attempt to activate the database fails because a
database BACKUP was in progress. Prior to activating
the database, it is necessary to rerun database BACKUP.
Once the database BACKUP completes successfully, the
database can be activated by starting the server.
SQLE_RC_RST_INPROG ( -1119 ) shows that a
database RESTORE was in progress when the database
failed to activate. The RESTORE database must be
restarted and allowed to complete successfully before
activating the database. Once the database RESTORE in
complete, the database can be activated by starting the
server. SQLE_RC_BR_INPROG ( -1120 ) means that
either a database BACKUP or RESTORE must complete
before activating the database. Ensure that either a
BACKUP or RESTORE operation completes successfully
before activating the database.
System action: The server is not started because the
database cannot be activated.
User response: See message explanation for more
information.
ANR0239E
The DB2 instance name instance name

may not be valid or is not configured
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.
database instance is not valid.
User response: Verify that the database instance exists
and that it is configured properly. You can list DB2
instances by issuing the db2ilist command from the
instance directory, under the DB2 installation directory.
Example: c:\Program Files\tivoli\tsm\db2\instance\
db2ilist
ANR0240E
Deletion process failed for database

volume volume name.

delete the database volume shown has failed.
72
System action: The volume is not deleted.

information.
ANR0241E
Deletion process failed for recovery log

volume volume name.

delete the recovery log volume shown has failed.
information.
ANR0242I
Deletion process canceled for database

volume volume name.

delete the database volume shown has been canceled.
ANR0243I
Deletion process canceled for recovery

log volume volume name.

delete the recovery log volume shown has been
canceled.
ANR0244I
Deletion complete for database volume

volume name.
Explanation: The delete process for the database

volume named has finished successfully.
System action: The volume is deleted.
ANR0245I
Deletion complete for recovery log

volume volume name.
Explanation: The delete process for the recovery log

volume named has finished successfully.
ANR0246E
Error reading logical page logical page

number (physical page physical page
number) from database volume volume
name.
Explanation: An error has been encountered when

attempting to read a page from the specified database
volume.
ANR0247I ANR0254E
mirrored volume, if available.

information about the volume in error. If the error
persists and another mirrored copy of the volume is
available, the failing volume should be taken offline by
using the VARY OFF command, and repaired.
Otherwise, halt the server and repair the volume. Then
restart the server.
ANR0251E
ANR0247I
Database page logical page number

successfully read from an alternate copy
on volume volume name.
Explanation: After a read error, the server is able to

read the desired page from another synchronized
mirrored volume.
Explanation: After a read error, the server is unable to

read the desired page from another mirrored volume
because no other mirrored volume was in the
synchronized state. This message is normally preceded
by a message indicating which volume failed.
System action: Processing is ended.
User response: You can repair the failed volume by
halting the server and correcting the volume errors.
ANR0252E
Unable to read database page logical page

number from any alternate copy.
Explanation: After a read error, the server is unable to

read the desired page from another mirrored volume
because no other mirrored volume is in the

Error reading logical page logical page
number) from recovery log volume
volume name.

attempting to read a page from the specified recovery
log volume.
mirrored volume, if available.
information about the volume in error. If the error
persists and another mirrored copy of the volume is
available, the failing volume should be taken offline, by
using the VARY OFF command, and repaired.
ANR0250I
System action: If a mirrored volume is available then

the failing volume is forced into the offline state.
User response: Repair the failing volume, and then
use the VARY ON command to bring the volume back
online.
ANR0253E
ANR0249E
Error writing logical page logical page

number) to database volume volume name.

attempting to write a page to the specified database
volume.

ANR0248E
Unable to read recovery log page logical

page number from any alternate copy.
Recovery log page logical page number

successfully read from an alternate copy
on volume volume name.
Unable to write database page logical

page number to any alternate copy.
Explanation: After a write error, the server is unable

to write the desired page to another mirrored volume
User response: Repair the failed volume.
ANR0254E
Error writing logical page logical page

number) to recovery log volume volume
name.

attempting to write a page to the specified recovery log
volume.
System action: If a mirrored volume is available, the
failing volume is forced into the offline state.
online.
Explanation: After a read error, the server is able to

read the desired page from another synchronized
mirrored volume.
73
ANR0255E ANR0263I
ANR0255E
Unable to write recovery log page logical

page number to any alternate copy.
information from any of the defined database or

recovery log volumes.
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

recovery log volumes are available for use by the
server.
ANR0260I

ANR0256E
Error writing physical page physical page

number to restart/checkpoint area on

volume.
online.
Database page logical page number

successfully resynchronized.
Explanation: After detecting a partially-written

database page, the server is able to rewrite the page by
using a synchronized mirror copy.
ANR0261I
Recovery log page logical page number

successfully resynchronized.
Explanation: After detecting a partially-written

recovery log page, the server is able to rewrite the page
by using a synchronized mirror copy.
ANR0257E
Error writing physical page physical page

number to restart/checkpoint area on

volume.
ANR0262W
Incompatible database restart/recovery

area has been detected.
Explanation: The restart/recovery area of the server

database and recovery log volumes were written in a
format that is not compatible with the restart/recovery
area written by other versions of the server.

online.
System action: The server starts normally. If the

database and recovery log are writable (not Read
Only), then the restart/recovery area will be converted
to a compatible format. Message ANR0263I will be
issued when the conversion has been completed.
ANR0258E
Unable to write complete

restart/checkpoint information to disk.
Explanation: While writing restart/checkpoint

information to disk, the server encounters an error
writing to a database or recovery log volume for which
no synchronized mirrored copy is available. This
message is normally preceded by a message indicating
which volume failed.
User response: Repair the failing volume.
ANR0259E
Unable to read complete

restart/checkpoint information from any
database or recovery log volume.
ANR0263I
Explanation: The server converted the

restart/recovery areas of its database and recover log
volumes to a format compatible with the
restart/recovery area written by other versions of the
server. This is a one time conversion, and will only be
performed if the restart/recovery area was not already
in the compatible format.
System action: The restart/recovery area was
successfully converted.
Explanation: During server restart, the server is

unable to read a complete set of restart/checkpoint
74
Database restart/recover area

successfully converted to compatable
format.
ANR0264E ANR0271E
ANR0264E
A database file IO error is prohibiting

dbCode.

an IO error occured when processing a database file.
The problem may have occurred in one of the
following situations: The system cannot open, read
from, or write to a database file. The system cannot
create the database because an error occurred while the
system was creating a database file or a directory for
the database. The system cannot drop the database
because an error occurred while the system was
deleting a database file or a directory for the database.
The system cannot create the database because an
interrupt was received while the system was creating
or deleting a database file or a directory for the
database. The system cannot locate the database
subdirectory or database configuration file during
connect. Problem causes are ordered in terms of their
frequency of occurrence: A log file cannot be found in
the active log path directory. There may be a problem
with the database directory the operation is being
attempted on. There may be inadequate disk space to
complete the operation. The database cannot be used.
User response: Appropriate responses for the problem
causes described above are: To verify if a log file is
missing, check the db2diag.log for the presence of a
logging error (return code contains SQLO_FNEX). If
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
roll-forward the database to an earlier point in time
referenced in a log file preceding the missing log file
(use a timestamp that is earlier than that of the missing
file). There may be a problem with the database
directory. Check the integrity of the directory. Examples
of potential problems include: permissions issues,
mount point problems, corruption. Increase filesystem
size.
ANR0265E
Log disk processing failed: sufficient

memory is not available.
Explanation: At server installation, the server is

unable to process the server log disks due to
insufficient memory.
User response: Restart the server installation process
with more memory available.

User response: Restart the server installation process
with more memory available.
ANR0267E
Explanation: The specified volume cannot be found

during installation.
User response: Determine the reason the disk is
unavailable, and correct the problem. Restart the server
installation process.
ANR0268E
Database disk processing failed:

sufficient memory is not available.
Explanation: At server installation, the server is

unable to process the server database disks due to
Database volume volume name is not

available.
Explanation: The specified volume cannot be found

during installation.
User response: Determine the reason the disk is
unavailable, and correct the problem. Restart the server.
ANR0269E
Process for Log volume volume name

terminated - thread resource not
available.
Explanation: During installation for the indicated

volume, the server cannot start a thread to service I/O
requests.
application.
Restart the server installation process.
ANR0270E
Process for Database volume volume

name terminated - thread resource not
available.
Explanation: During installation for the indicated

volume, the server cannot start a thread to service I/O
requests.
application.
Restart the server installation process.
ANR0271E
ANR0266E
Log volume volume name is not available.
Maximum number of recovery log

volumes exceeded.
Explanation: More recovery log volumes have been

specified than the server can manage.
75
ANR0272E ANR0286W
User response: Reduce the number of recovery log
volumes specified. Restart the server installation
process.
ANR0272E
Maximum number of database volumes

exceeded.
User response: None

ANR0277E
Schema reconciliation for table table

failed.
Explanation: The server was unable to reconcile the

schema differences for the indicated table.
Explanation: More database volumes have been

specified than the server can manage.
System action: Server operation terminates.
User response: Contact your IBM service

representative.
User response: Reduce the number of database

volumes specified. Restart the server installation
process.
ANR0273W
Not initializing library library name

because the library is set offline .
Explanation: The External Library is set offline. It will

not be used for new transactions until it is set online
again.
System action: This server skips the initialization of
the library. The server continues processing.
User response: Refer to the UPDATE PATH command
for details on changing the online option.
ANR0274E
Attempt to access library library name

failed, because the library is set offline.
ANR0278S
The database manager cannot create the

database because of a virtual memory
shortage.
System action: Server operation stops.

User response: Stop other applications running on the
system, especially those that use large amounts of
shared memory.
ANR0279S
The database manager failed to start.

The database manager license key is
invalid or was removed.
Explanation: The database manager license key is

invalid or was removed.
System action: The server operation stops.
System action: This mount fails.
User response: You can issue the following command,

which displays the information about the database and
its license status. Report the output to your service
representative: db2licm -l
User response: Refer to the UPDATE PATH command

for details on changing the online option.
ANR0285I
Explanation: The Library is set offline. It will not be

used for new transactions until it is set online again.
ANR0275I
Detected schema change for table table,

attempting to reconcile.
Explanation: The schema for the table referenced does

not match the server definition for this table. The
schema difference for this table will be reconciled.
System action: Server startup continues if the schema
difference was successfully reconciled. Server startup
will fail if the schema reconciliation failed.
User response: The schema for this table will attempt
to be reconciled. Specifically, the server will try to
modify the table in the database to match the schema
that was expected. A message will be issued indicating
the success or failure of the schema reconciliation.
ANR0276I
Schema reconciliation for table table

succeeded.
Explanation: The schema differences for this table

were successfully reconciled.
Explanation: The database page shadowing function

was started. The file specified is used to store the
shadowed database pages.
ANR0286W
Database page shadowing using file file

name failed to start.

could not start. An error has been encountered
accessing the page shadow file specified.
User response: Verify that there is enough space for
the page shadow file. That page shadow file requires
approximately 65 kilobytes of space, if this space is not
available a new location for the file should be specified.
76
Database page shadowing started using

file file name.
ANR0287W ANR0294I
ANR0287W
Contents of the page shadow file file

name are not valid.

could not use the contents of the existing file. Restart
recovery using this file is not possible.
System action: The server attempts to start without
having the database page shadow file available.
User response: The database page shadow file
contents are not valid. This can be caused by: a partial
write to the page shadow file itself, the file being
manipulated by a process outside of the server, the file
being overlaid by a different file, or the file could have
been erased.
ANR0288W
One or more database pages in the last

batch written is corrupt - contents of
database page shadow file will be used
to fix the page or pages.
Explanation: One or more pages from the last batch of

pages written to the server database has been detected
to be corrupt. The server will attempt to use the
contents of database page shadow file and replace the
corrupted database page.
System action: Server startup continues.
User response: A corruption of a database page within
the server database, is typically caused by a partial
write. A partial write may occur when the server is
brought down external to normal server processing. If
the server terminated without a halt command being
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
drive failure, improperly terminated SCSI bus, or a
failure in a device controller. Please try to identify the
cause of the partial write and take the appropriate
action to prevent this from occurring in the future.
ANR0289W
Damaged database pages were

successfully replaced using contents of
page shadow file.
Explanation: The damaged database pages were

replaced using the corresponding pages from the page
shadow file. The pages were successfully replaced.
System action: The server continues to restart.
ANR0290W
Failure occurred attempting to replace

one or more damaged database pages
using the contents of the page shadow
file.
Explanation: The damaged database pages could not

be replaced using the corresponding pages from the
page shadow file.
System action: The server continues to restart.

ANR0291E
Error writing to database page shadow

file.
Explanation: The server encountered an error writing

to the database page shadow file. The page shadowing
for the server is currently disabled.
System action: Database page shadowing for the
server will remain disabled until the server is halted
and restarted.
User response: Check the file specified as the database
page shadow file. It may be that there is not enough
space for the file. If enough space is available, check
the filesystem, drive, or disk that it resides on for an
indication of the error. Once the error preventing the
server from writing to the page shadow file has been
resolved, restart the server.
ANR0292W
Database page shadow file file name does

not exist.
Explanation: The server attempted to use the page

shadow file referenced but was unable to open the file.
The file does not exist.
System action: The server will continue to operate
and will attempt to create this as a new database page
shadow file.
ANR0293I
Reorganization for table table name

started.
Explanation: The server is performing an online

reorganization for the table referenced.
System action: The server will continue to operate.
User response: Monitor the available log space in the
active log and archive log storage paths. If the log
space available to the filesystem begins to fill up, then
perform a BACKUP DATABASE command with the
TYPE=FULL parameter in order to initiate pruning of
the archive log space.
ANR0294I
Reorganization for table table name

ended.
Explanation: The server online reorganization for the

table referenced has ended.
User response: Review the available log space in the
space available to the filesystem has to filled up or is
close to filling up, then perform a BACKUP
DATABASE command with the TYPE=FULL parameter
in order to initiate pruning of the archive log space.
77
ANR0295I ANR0304I
ANR0295I
A full database backup is needed. The

active log space used is log space used is
megabytes, and the active log space
available is log space available megabytes.
The ratio, active log used ratio, exceeds the
threshold log utilization threshold.
Explanation: When the active log space used exceeds

the log utilization threshold, a database backup is
needed.
authorized to access the database.

ANR0299I
A full database backup will be started.

The archive log space used is archive log
% and the archive log space used
threshold is arch log threshold percent.
Explanation: When the archive log space used exceeds

the threshold, a full database backup will be started.

ANR0300I
ANR0296I
A full database backup is needed. The

total space used in log file system is log
space used megabytes, and the total space
available in the log file system is log
space available megabytes. The ratio is log
file system used ratio and is greater than
the threshold log file system utilization
threshold.
Recovery log format started; assigned

capacity count megabytes.
Explanation: Initial formatting of the server recovery

log has started.
System action: The log is formatted for use by the
server.
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
Explanation: The amount of the server recovery log

shown has been successfully formatted.

ANR0297I
A full database backup might be

required. The last log number used is
last log used and the first log number
used is first log used. The log file size is
log file size megabytes. The maximum log
file size is maximum log file size
megabytes.
Explanation: When the log space used since the last

database backup exceeds the maximum log file size,
either a full database backup is required, or the
maximum log file size must be increased.
ANR0298S
Authority is insufficient to access the

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
server is running and a server operation failed, then the
user ID does not have sufficient authority to perform
the operation.
System action: If the server is starting, the dsmserv
process ends. If the server is running, the server stops.
System action: Formatting continues.

ANR0302I
Recovery log formatting took mseconds

milliseconds.
Explanation: Formatting of the recovery log has

completed and took the number of milliseconds shown.
ANR0303I
Format rate: rate pages/second.
Explanation: During formatting, the formatter

processed the number of pages indicated each second.
ANR0304I
Page service time: rate ms.
Explanation: During formatting, the formatter

required the number of milliseconds indicated to
process each page.
User response: Ensure that the user ID under which

the server is running is either the instance user ID, or is
78
Recovery log format in progress; count

megabytes of count.
ANR0305I ANR0316W
ANR0305I
Recovery log format complete.
Explanation: Formatting of the server recovery log

completed successfully.
ANR0306I
Recovery log volume mount in progress.

Recovery log extend in progress; count
megabytes of count formatted.
Explanation: As a result of an EXTEND LOG

command, the additional recovery log pages are being
formatted.
System action: Formatting continues.
Recovery log extend terminated process canceled.
Explanation: The process started as a result of an

EXTEND LOG command and has been canceled.
System action: The EXTEND command is ended.
ANR0311I
Explanation: This message is issued to notify the

administrator that the server recovery log utilization
exceeds 90% or more of its assigned capacity.
User response:
v If the server is operating in NORMAL log mode,
depending upon the size of your recovery log, add
recovery log volumes, or extend the recovery log, or
both, before it fills completely. Refer to the DEFINE
LOGVOL, and EXTEND LOG commands for more
information on these operations.
v If the server is operating in ROLLFORWARD log
mode:
backup the database, or
define a database backup trigger if one is not
already defined, or
lower the database backup trigger if one is
defined
Refer to the DEFINE DBBACKUPTRIGGER or
UPDATE DBBACKUPTRIGGER commands.

ANR0309I
Recovery log usage exceeds utilization

percentage % of its assigned capacity.
Explanation: During restart, the server is mounting

required recovery log volumes.
ANR0307I
ANR0314W
Recovery log reduce in progress; count

megabytes of count moved.
Explanation: As a result of a REDUCE LOG

command, the amount of data from the recovery log
shown has been moved.
System action: The REDUCE LOG command
continues.
ANR0315E
LOG SCAN ERROR encountered. The

recovery log is unusable and the server
is unable to continue.
Explanation: The server encountered corrupted

information in the recovery log. Typically, the
corruption is caused by a hardware or environmental
failure external to TSM.
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
recovery log mirrors are not available, or all mirrors are
corrupted, restore the server database to the latest
backup and restart the server.

ANR0316W
ANR0313I
Recovery log reduce terminated process canceled.
Explanation: The process started as a result of a

REDUCE LOG command and has been canceled.
System action: The REDUCE command is ended.
A full backup for database DB Name

cannot be started. This backup is
required.
Explanation: An automatic full backup was attempted

for this database. However, the device class for
database backups has not been specified.
System action: The database backup operation is not
started.
User response: Issue the SET DBRECOVERY
command to specify the default device class for
automatic database backups. Then, issue the BACKUP
DB command and specify TYPE=FULL to back up the
database.
79
ANR0317I ANR0321W
ANR0317I
Reorganization for indices for table table

name started.

reorganization for the indices of the referenced table.
User response: Monitor the available log space in the
space available to the filesystem begins to fill up, then
perform a BACKUP DATABASE command with the
TYPE=FULL parameter in order to initiate pruning of
the archive log space.
ANR0318I
Reorganization of indices for table table

name ended with sqlCode dbCode.

indices for the table referenced has ended.
User response: Review the available log space in the
space available to the filesystem has to filled up or is
close to filling up, then perform a BACKUP
DATABASE command with the TYPE=FULL parameter
in order to initiate pruning of the archive log space.
ANR0319W
The file system for the database archive

log has insufficient free space.
Explanation: The usage of the file system for the

database archive log has exceeded the
ARCHLOGUSEDTHRESHOLD. Space is used by files
that are not database archive log files, and the
BACKUP DB command cannot free space in the
filesystem..
User response: Create sufficient free space on the file
system so that usage does not exceed the
ARCHLOGUSEDTHRESHOLD.
ANR0320W
Storage agent storage agent is not able to

use device class device class for storage
pool storagepool for LAN-Free data
movement operations.
Explanation: The storage agent referenced is not able

to perform LAN-Free data movement operations using
this storage pool and device class. The storage agent is
back-level and is not able to support LAN-Free
operations using this device class.
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
to the server.
supported. This change prevents back-level storage

agents from being able to use these device classes. The
storage agent should be upgraded to the same version
and release as the server. Until the storage agent is
upgraded, any LAN-Free data movement operations
that are attempted will be done using the LAN.
ANR0321W
Explanation: The storage agent is at an earlier version

than the server and is not able to use advanced
functions that were requested by a client.
System action: The operation is not allowed.
User response: The storage agent must be upgraded
to a version, release, and level that supports this
operation. Typically, the problem is that the storage
agent and server are not at the same version and
release. For example, if the server is version 5.3.0.0 and
the storage agent is version 5.2.3.0, the storage agent
needs to be upgraded to version 5.3.0.0 to perform the
requested function.
If this was a restore or retrieve operation and the client
node DATAREADPATH setting was ANY or LANFREE,
the server will override this to be LAN only. This will
cause the operation to fail on the storage agent and
message ANR0416W to be issued. Retry the operation
after performing one of the following actions:
v Halt the storage agent, upgrade the storage agent
program, and then restart the storage agent.
v Set the ENABLELANFREE client option to NO, and
then restart the client
If this was a no-query restore operation, the data was
not restored by the storage agent using LAN-Free data
transfer. If the client node is allowed to read data over
the LAN, the data was restored over the LAN. If the
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
UPDATE NODE command.
If this was an operation performed by an agent node
with proxy node authority to a target node, the session
failed with a protocol error. The operation was
attempted by a version 5.3 or higher client and server,
but the storage agent is not able to support this
operation. To allow an agent node to perform
operations for a target node, the storage agent must be
upgraded to version 5.3.0 or later.
User response: In TSM version 5.3, a change was

made to the way the FILE and device classes are
80
Storage agent storage agent name at

version storage agent VRMF does not
support operation operationName,
although the server server name at
version server VRMF can support it.
ANR0322E ANR0328I
ANR0322E
The NEWSTGPOOL parameter is not

valid for deduplicated volume volume
name.
ROLEOVERRIDE parameter.
ANR0327I
Explanation: The volume contains one or more

deduplicated objects and must be restored to the
original storage pool.
User response: To restore the volume to the original
storage pool, reissue the RESTORE VOLUME command
without the NEWSTGPOOL parameter.
ANR0323E
The NEWSTGPOOL parameter is not

valid for deduplicated storage pool pool
name.
Explanation: The storage pool contains deduplicated

objects and must be restored to the original storage
pool.
User response: To restore the storage pool to the
original storage pool, reissue the RESTORE STGPOOL
command without the NEWSTGPOOL parameter.
ANR0324E
command: Replication parameters cannot

be used with the TYPE=SERVER
parameter.
System action: The command failed.

User response: Reissue the command without
replication parameters. Replication parameters include
REPLSTATE, REPLMODE, BKREPLRULEDEFAULT,
ARREPLRULEDEFAULT and SPREPLRULEDEFAULT.
ANR0325E
command: Operation is not allowed

because node nodename is a replica.
Explanation: The specified node is a replica of a node

on another server, created using the REPLICATE NODE
command.
You can restore or retrieve data from this node, but you
cannot store new data or alter existing data in any way.
System action: Client sessions that attempt to store
new data or change existing data will be terminated
with a protocol error. IMPORT operations will skip the
node.
User response: Perform the operation on the server on
which the original node resides.
ANR0326E
command: The ROLEOVERRIDE

parameter cannot be used with either
the TYPE=SERVER or TYPE=NAS
parameter.

User response: Reissue the command without the
Replication of node node list completed.

Files current: files current. Files
replicated: files replicated of files to
replicate. Files updated: files updated of
files to update. Files deleted: files deleted of
files to delete. Amount replicated: amount
replicated of amount to replicate. Amount
transferred: amount transferred. Elapsed
time: elapsed time.
Explanation: The replication process has completed.

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
successfully replicated out of the number of files that
we attempted to replicate.
v Files updated indicates the number of files which
had meta-data updated on the target server out of
the number of files that needed an update.
v Files deleted indicates the number of files deleted
from the target server out of the number that needed
to be deleted.
v Amount replicated indictaes the size of the files that
were replicated out of the size of the files that
needed to be replicated
v Amount transferred indicates the number of bytes
transferred for the files that were replicated. This can
be less than the amount replicated if deduplication is
used to reduce the amount of data transferred.
v Elapsed time indicate how long the process ran
ANR0328I
Replication preview of node(s) node list

completed. Files current: files current.
Files to be replicated: files to replicate.
Files to be updated: files to update. Files
to be deleted: files to delete. Amount to
replicated: amount to replicate. Estimated
run time: estimated runtime.
Explanation: The replication process has completed in

preview mode. The meanings of the numbers are:
v Files current indicates the number of files that do not
need to be replicated.
v Files to be replicated indicates the number of files
requiring replication.
v Files to be updated indicates the number of files
requiring a meta-data update.
v Files to be deleted indicates the number of files to be
deleted from the target server.
v Amount to be replicated indictaes the size of the files
that require replication.
81
ANR0329I ANR0337I
v Estimated run time is an estimate of how long the
process will run.
ANR0333E

ANR0329I
Starting replication of data type data for

node node name, filespace ID filespace id.
Explanation: The replication process has started

processing data for the specified node and file space
ID.
ANR0330W
Session session number for node node

name (client platform) refused - invalid
authentication protocol requested.
Server server name is disabled for

outbound sessions. The session request
is rejected.
Explanation: The DISABLED SESSION SERVER

command disabled outbound sessions for the indicated
server. Sessions to this server are not permitted.
System action: The session request fails. Server
operation continues.
User response: Issue the QUERY STATUS command
to view the servers that are disabled for inbound and
outbound sessions. Issue the ENABLE SESSIONS
SERVER command to make the server available for
outbound sessions.
ANR0334E
Server server name is disabled for

inbound sessions. The session request is
rejected.
Explanation: The server refuses a request to start a

session because an invalid authentication protocol was
requested during sign-on processing. This might be due
to a down-level client, server, or storage agent that is
accessing a server or storage agent that is configured to
disallow such attempts.
Explanation: The DISABLED SESSION SERVER

command disabled inbound sessions for the indicated
server. The indicated server is not permitted to initiate
sessions to this server.
User response: Issue the QUERY STATUS command

to view the servers that are disabled for inbound and
outbound sessions. Issue the ENABLE SESSIONS
SERVER command to make the server available for
inbound sessions.
User response: Upgrade the accessing client, server, or

storage agent to version 6.3 or later, or re-configure the
server to allow access from down-level clients, servers,
or storage agents.
ANR0331W
Replication session for server server name

refused - server is down-level.
Explanation: The server specified for replication

cannot be used because it is not at the current level.
User response: Upgrade the server to version 6.3 or
later, or specify a different server for replication.
System action: The session request fails. Server

ANR0335I
Explanation: The schema for this table is reconciling.

System action: Schema reconciliation will continue for
this table.
User response: None
ANR0336I
ANR0332E
Replication mode source repl mode of

node node name is incompatible with
mode target repl mode on server server
name.
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
SYNCSEND, the target mode must be SYNCRECV. The
source mode cannot be anything other than SEND or
SYNCSEND.
System action: The replication of the node's data fails.
Server operation continues.
User response: Use the UPDATE NODE command to
put the node in the proper state on both the source and
target servers.
82
Schema reconciliation for table table in

progress; pct% completed.
Runstats for table table name started.

runstats on the referenced table.
ANR0337I
Runstats for table table name ended with

sqlCode dbCode.
Explanation: The server online runstats for the table

referenced has completed.
User response: For a non-zero sqlCode, consult the
DB2 Information Center for details.
ANR0338E ANR0340E
ANR0338E
Database create terminated.
Explanation: DB2 detected a problem during the

create database operation. The source of the problem
might be a DB2 limitation. When "No File System
Caching" is used to create a table space with Database
Managed Storage containers, DB2 only supports storage
devices with a sector size of 512 Bytes on AIX, SUN
Solaris, Linux, Windows, and a sector size of 1024 Bytes
on HP-UX.
System action: The create database operation is
terminated.
User response: See the db2diag.log file for additional
information to confirm the DB2 limitation. Change the
sector size to 512 Bytes on AIX, Solaris, Linux,
Windows, and to 1024 Bytes on HP-UX.
ANR0339E
command: Outbound replication is

disabled.
Explanation: Replication operations originating from

this server are disabled.
System action: Processing ends.
User response: Use the ENABLE REPLICATION
command to re-enable the use of replication.
ANR0340E
command: Outbound replication

operations are disabled because the
database was restored.
Explanation: The database for this server was

restored. Data that was on this server but that is not
referenced by the restored database is no longer
accessible. To prevent this server from deleting copies
of data that might exist on the target replication
servers, replication operations originating from this
server are disabled.
User response: To preserve the data that exists on
target replication servers, determine whether copies of
data that are on the target replication server are
needed. If they are, you must replicate data that is on
the target replication server to the source replication
server. After the replication is complete, issue the
ENABLE REPLICATION command to resume
replication operations.
For example, suppose that PRODSRV is the source
replication server. The data belonging to client node
NODE1 was replicated from PRODSRV to DRSRV, the
target replication server. The database on PRODSRV
was restored.
To resume replication, complete the following steps:
1. On PRODSRV and DRSRV, remove NODE1 from
replication by issuing the following command:
REMOVE REPLNODE NODE1.
2. Update NODE1 definitions. When replication

occurs, DRSRV will send the data to PRODSRV that
was lost because of the database restore.
a. On DRSRV, issue the following command:
UPDATE NODE NODE1
REPLSTATE=ENABLED
REPLMODE=SYNCSEND.
b. On PRODSRV, issue the following command:
UPDATE NODE NODE1
REPLSTATE=ENABLED
REPLMODE=SYNCRECEIVE.
3. On DRSRV, set the replication rules to match those
on PRODSRV. For example, if only archive data was
being replicated from PRODSRV to DRSRV, set the
rules on DRSRV to replicate only archive data from
DRSRV to PRODSRV. Backup and space-managed
data will not be replicated to PRODSRV.
4. On DRSRV, set the target replication server by
issuing the following command: SET REPLSERVER
PRODSRV.
5. On DRSRV, replicate data belonging to NODE1 by
issuing the following command: REPLICATE NODE
NODE1. Replication processing changes the
replication mode of NODE1 to SEND on DRSRV
and to RECEIVE on PRODSRV.
7. Update NODE1 definitions:
a. On PRODSRV, issue the following command:
UPDATE NODE NODE1
REPLSTATE=ENABLED
REPLMODE=SYNCSEND.
b. On DRSRV, issue the following command:
UPDATE NODE NODE1
REPLSTATE=ENABLED
8. On PRODSRV, enable replication by issuing the
following command: ENABLE REPLICATION.
9. On PRODSRV, replicate data belonging to NODE1
by issuing the following command: REPLICATE
NODE NODE1. Replication processing changes the
replication mode of NODE1 to SEND on PRODSRV
and to RECEIVE on DRSRV.
The original replication configuration is restored.
PRODSRV has all the data that was lost because of the
database restore.
REMEMBER: To replicate data that was on DRSRV, you
set the target replication server to PRODSRV. In your
original configuration, if you were replicating data from
DRSRV to another server, for example, BKUPDRSRV,
you must reset the target replication server. To reset the
target replication server, issue the following command
on DRSRV: SET REPLSERVER BKUPDRSRV.
83
ANR0341E ANR0350I
ANR0341E
command with keyword keyword is not

allowed when archive data retention
protection is enabled.
Explanation: The specified command with the

specified keyword is not allowed when archive data
retention protection is enabled on the server.
ANR0343W
File space filespace name could not be

created by node $$_TSMDBMGR_$$.
$$_TSMDBMGR_$$ node name is
reserved for Tivoli Storage Manager
database backup and restore.

User response: Node $$_TSMDBMGR_$$ is only used
for Tivoli Storage Manager database backup or restore.
The server does not create a file space with this special
node since there is no running database backup or
restore session.
User response: Use another node name to create this
filespace.
ANR0344E
The server failed to restore the database.

Missing ARCHIVELOGDIR value in the
server option file.
Explanation: While attempting to restore the database,

the Tivoli Storage Manager server detects a missing
value for ARCHIVELOGDIR in the server option file.
System action: Server database restore stops.
User response: Before reissuing the command to
restore the database, check the following items:
v Ensure that ARCHIVELOGDIR option has a valid
value.
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
that the name and location of the file is correct.
ANR0345E
The database manager cannot start

while file file name exists.
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
database restore to the most recent point-in-time
possible.
System action: Database restore processing continues
using point-in-time mode.
User response: Review the ARCHIVELOGDIR server
option in the server options file and determine why
this directory is no longer available to the server. If the
archive log directory and its contents can be recovered
and made available to the server RESTORE DB
processing, retry the DSMSERV RESTORE DB
command.
ANR0347E
Database database name is reporting a

drive is invalid and the database can not
be removed.

administrator that the server has detected that the API
is reporting an invalid drive condition during a
REMOVE DB process.
System action: Server REMOVE DB stops.
User response: Interrogate the database, correct the
problem then issue the command again.
ANR0348S
Database restart record version version is

not recognized.
Explanation: During server initialization, the server

database initialization failed because the version of the
restart record is not recognized.
System action: The Server is terminated.
User response: Install the latest version of the Server
or restore the database to a point in time prior to the
previous upgrade.
ANR0349S
The database has been upgraded from

Express.
Explanation: The Express server has been started

with a database that has been upgraded from Express
to 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.
Explanation: A database restore to the most current

state was requested but it is not possible to perform
this action. The archive logs are not available. This
84
ANR0350I
Recovery checkpoint started.
Explanation: During server initialization, the process

of bringing the server database back to a state of
consistency has begun.
ANR0351I ANR0363I
ANR0351I
ANR0358E
Recovery checkpoint complete.

of bringing the server database back to a state of
consistency has completed successfully.
Database initialization failed: sufficient


database fails initialization because sufficient server
System action: Initialization fails.
User response: Make more memory available to the

server.
ANR0352I
ANR0359E
Transaction recovery complete.

of recovering any incomplete transactions has
Database initialization failed: unable to

read database restart record.

database initialization fails because the required restart
record cannot be read.

ANR0353I
Recovery log analysis pass in progress.

of analyzing the server recovery log has begun.
ANR0360E
Database initialization failed: database

size mismatch; LVM size = size, expected
size = size.

database initialization fails because the size of the
database does not match its prior size.
ANR0354I
Recovery log redo pass in progress.

of committing incomplete transactions has begun.
ANR0362W

ANR0355I
Recovery log undo pass in progress.

of rolling back incomplete transactions has begun.
ANR0356I
Recovery log compression started.
Explanation: The process of removing unneeded data

from the server recovery log has begun.
ANR0357I
Recovery log compression ended.
Explanation: The process of removing unneeded data

from the server recovery log has completed.

administrator that the server database utilization
exceeds 80% or more of its assigned capacity.
User response: Depending upon the size of your
database, add database volumes, or extend the
database, or both, before it fills completely. The server
expiration process may also free up database space
making it available to other server processes. Refer to
the EXPIRE INVENTORY, DEFINE DBVOL, and
EXTEND DB commands for more information on these
operations.
ANR0363I
Database usage exceeds utilization

percentage % of its assigned capacity.
Database was automatically upgraded to

the server program level.

administrator that the server database was
automatically upgraded to the current server program
level. The upgrade is performed when the
UPGRADEDB parameter is specified at server startup
and the server is started over a database that was
written by a down-level version of the server program.
85
ANR0364W ANR0371E
User response: None. The UPGRADEDB parameter
does not need to be specified during future server
start-ups.
ANR0364W
Server has detected a zero bit mismatch

error.

administrator that the server has detected a zero bit
mismatch error during a RESTORE DB process. The
recovery process is the database must be restored with
a process that includes a DSMSERV FORMAT. Either
the data base volumes must be formatted then a
DSMSERV RESTORE DB performed from a data base
backup that does not have this problem, or a
DSMSERV UNLOADDB followed by the formatting,
then a DSMSERV LOADDB. Do not use DSMSERV
DUMPDB on the data base for this recovery.

ANR0368I
Formatting server's database: database

name.
System action: The server is done creating its

database
ANR0369I
Stopping the database manager because

of a server shutdown.
System action: Stopping the server's database

manager.
System action: Server RESTORE DB continues.
User response: Perform one of the data base recovery

actions after the RESTORE DB completes.
ANR0370E
ANR0365E
Database database name is currently in

use and can not be removed.

administrator that the server has detected that the
database is currently in use during a REMOVE DB
process.
User response: Drop all database connections then
issue the command again.
ANR0366I
Database database name was removed

successfully.

administrator that the server has removed the server
database successfully.
User response: The server database was removed. In
order to run the TSM server, you need to format a new
database using the 'DSMSERV FORMAT' command.
ANR0367W
The server failed to format the database

database name. This database name
already exists.
Explanation: While attempting to format a database,

the Tivoli Storage Manager server has found that this
database name already exists.
System action: Server format stops.
format a new database, check the following items:
v Remove the old database using command 'DSMSERV
REMOVEDB DB_NAME'.
86
Diagnostic(ID) During the format

operation, the server cannot create files
in one or more directories that you
specified for log type. Ensure that the file
system where the directory is located
has sufficient space.
Explanation: Space is not available for the server to

write data to the directory.
System action: The format operation stops.
format a new database, check the following items:
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
removed, use the utility DSMSERV REMOVEDB
db_name to remove it.
v Check that space is available to the directories that
you specified for
ACTIVELOGDIR,ARCHIVELOGDIR, and
ARCHFAILOVERLOGDIR. Ensure that the amount
of space meets requirements. For example, the
directory for ACTIVELOGDIR must have at least 8
GB space available.
v Remove any files that are in the directories that you
want to use for the recovery logs.
ANR0371E
Error setting environment variable

environment variable name with value value
- return code return code value.
Explanation: The server is unable to set the content of

the environment variable on the operating system to
the value specified in the message. The return code in
the message is the last error code set in the operating
system. The return code, or, last error code is a system
error code as a result of the failed function call to set
the environment variable.
ANR0372E ANR0379W
User response: Refer to the list of system error codes
provided by the operating system to determine the
cause of the problem. Resolve the problem and retry
the server operation.
ANR0372E
Database database name is currently

damaged and can not be removed.

database is damaged during a REMOVE DB process.
ANR0373E

File error and can not be removed.

database is reporting a File error during a REMOVE DB
process.
ANR0374E
Database database name is invalid and

can not be removed.

is reporting an Invalid DB error during a REMOVE DB
process.

Database database name is reporting an
authorization error and can not be
removed.

database is reporting an authorization error during a
REMOVE DB process.
ANR0376E

ANR0377E
Database database name is not found and

can not be removed.


drive is not found and can not be
removed.

is reporting a database drive cannot be found during a
REMOVE DB process.
ANR0378W

drive is not found and can not be
removed.

is reporting a warning during a REMOVE DB process.
System action: Server REMOVE DB completed
successfully.
User response: The drop database command has
completed successfully, however, there are some nodes
where the database alias or database name was not
found. It is possible that DROP DATABASE AT NODE
was already performed on these nodes.
ANR0379W
ANR0375E
is reporting the DB cannot be found during a REMOVE

DB process.
A server database deadlock situation has

been encountered; the lock request for
the lock name lock, key name will be
denied to resolve the deadlock.
Explanation: The server detected a deadlock situation

between a number of processes attempting to access
database information. A lock request for one of the
processes will be denied to resolve the database
deadlock. When the server processes encounter a
database deadlock, they usually try to run the function
that was in progress when the deadlock was
encountered again. Not all process can explicitly try an
operation again. For example, migration and
reclamation will eventually try again. However,
something like a delete volume run in a macro will
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
deadlocked processes. Server operation continues.
User response: If a process can be retried (like
migration), monitor the retry effort to see if it succeeds.
If the process or command cannot be retried, reissue
87
ANR0380W ANR0387I
the command or macro that caused the action.
ANR0383I
The recovery log maximum utilization

statistic was successfully reset.
Consider what other processes are running at the time

the deadlock is reported. For example, if a process is
started manually, as opposed to running as part of your
regularly scheduled server maintenance tasks, that
process may have caused the deadlock. You might have
to adjust the scheduling of your server maintenance
tasks to avoid the problem.
Explanation: The recovery log maximum utilization

statistic has been reset by the RESET
LOGMAXUTILIZATION command to the current
utilization.
ANR0380W
User response: The QUERY LOG command

(FORMAT=DETAILED) can be used to display the
current value for the maximum utilization.
The database buffer pool recovered

from an overcommit of number of pages
pages. Consider increasing your buffer
pool size by kilobytes needed kilobytes
under current server load.
Explanation: During normal processing, additional

buffer pool space is required beyond that specified in
the BUFPOOLSIZE in the server options file. The
additional kilobytes of buffer pool space that are
required are indicated in the message.
System action: Server operation continues; the
additional buffer pool space is obtained from available
server memory.
User response: If the current server load is typical,
consider increasing the size specified for your
BUFPOOLSIZE option by the number of kilobytes
specified in the message. To do this, you must halt the
server, change the options file, and then restart the
server.
ANR0381I
Buffer pool statistics were successfully

reset.
Explanation: Buffer pool statistics, such as the Cache

Hit Ratio, have been reset. The RESET BUFPOOL
command and the ESTIMATE DBREORGSTATS
command will reset the buffer pool statistics.
ANR0384I
The recovery log consumption statistic

was successfully reset.
Explanation: The recovery log consumption statistic

has been reset by the RESET LOGCONSUMPTION
command.
User response: The QUERY LOG command
current value for recovery log consumption.
ANR0385I
Could not free sufficient buffers to

reach reduced BUFPoolsize.
Explanation: A reduction in the database buffer pool

size was requested. However, too many buffers were in
use to reach the lower buffer pool size.
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
for use on the next server startup.
ANR0386I
The BUFPoolsize has been changed to

buffer pool size.
User response: The QUERY DB command

(FORMAT=DETAILED) can be used to to display the
current values for the buffer pool statistics.
Explanation: The BUFPoolsize option has been

changed to the indicated value.
ANR0382I
The database maximum utilization

statistic was successfully reset.
Explanation: The database maximum utilization

statistic has been reset by the RESET
DBMAXUTILIZATION command to the current
utilization.
current value for the maximum utilization.

ANR0387I
Evaluating node node name using storage

agent storage agent for LAN-free data
movement.
Explanation: The server is evaluating whether the

node and storage agent can use storage pools capable
of LAN-free data movement.
System action: The server evaluates the storage pool
destinations available to this node and reports which
storage pools can and cannot be used for LAN-free
data movement.
User response: Review the results of this processing to
88
ANR0388I ANR0393I
determine if the appropriate LAN-free environment is
configured.
ANR0388I
Node node name using storage agent

storage agent has capable count storage
pools capable of LAN-free data
movement and not capable count storage
pools not capable of LAN-free data
movement.
Explanation: The server has completed evaluation of

the LAN-free and non-LAN-free storage pool
destinations for this node using this storage agent. The
server determined that there are capable count storage
pools that are capable of LAN-free data movement. It
also determined that there are not capable count storage
pools that cannot be used for LAN-free data
movement.
User response: Review the other messages issued to
determine which storage pools are capable of LAN-free
data movement and those which are not capable of
LAN-free data movement for this node using this
storage agent.
ANR0389W
Node node name has data path

restrictions.
User response: If a process can try again (like

migration), then monitor the subsequent attempt to see
if it succeeds or not. If it fails, contact a service
representative. If the process or command is not able to
automatically try again, then reissue the command or
macro that caused the action to occur. If it fails again,
contact a service representative for further assistance to
better isolate the deadlock condition.
ANR0391I
Explanation: The server is evaluating to determine

LAN-free destination storage pools for the node and
storage agent referenced.
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
can not be used LAN-free it will report why that pool
can not be used.
User response: Review the results of this processing to
determine if the appropriate LAN-free environment is
configured.
ANR0392I
Explanation: The node name has data path restrictions.

The registered node has data write path, data read
path, or both, configured to not allow LAN-free
operations.
User response: Issue the command QUERY NODE
node name F=D and evaluate the data read path and
data write path settings. To store data or read data
using LAN-free data movement, set the data write path
to ANY or LANFREE.
Evaluating LAN-free destination for

node node name using storage agent
storage agent.
Node node name using storage agent

storage agent has LAN-free count storage
pools enabled for LAN-free data transfer
and non-LAN-free count storage pools that
are not enabled for LAN-free data
transfer.
Explanation: The server has completed evaluation of

the storage pool destinations for this node using this
storage agent. The server determined that there are
LAN-free count storage pools that are LAN-free enabled.
It also determined that there are non-LAN-free count
storage pools that are not enabled for LAN-free data
transfer for this node.
ANR0390W
A server database deadlock situation has

been encountered; the lock request for
transaction transaction ID will be denied.
Explanation: The server detected a deadlock situation

between a number of processes that were attempting to
access database information. A lock request for one of
the processes is denied, to resolve the database
deadlock. When server processes encounter a database
deadlock, they usually reattempt the function that was
in progress when the deadlock was encountered. Not
all process can explicitly try an operation again. For
example, migration and reclamation will eventually be
tried again. However, something such as a delete
volume run in a macro will 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
deadlocked processes. Server operation continues.

determine which storage pools are capable of LAN-free
data transfer and those which are not capable of
LAN-free data transfer for this node using this storage
agent.
ANR0393I
Management class management class with

destination storage pool for operation type
operations is enabled for LAN-free data
transfer for nodee node name using
storage agent storage agent name.
Explanation: The storage pool is capable of LAN-free

data transfer operations for node node name using
89
ANR0394W ANR0400I
ANR0394W

operations is not enabled for LAN-free
data transfer for node node name using
storage agent storage agent name because
this destination is a CENTERA device.
Explanation: The destination storage pool is not capable

of LAN-free data transfer operations for node node
name using storage agent storage agent name. This
storage pool uses a CENTERA device and as such can
not be used for LAN-free operations.
User response: To configure this node for LAN-free
data transfer operations, update the destination storage
pool for the copygroup or assign this node to a domain
that has LAN-free storage pool destinations.
ANR0395W

operations is not enabled for LAN-free
data transfer for node node name using
storage agent storage agent name because
this destination is configured for
simultaneous write.
is assigned to should be changed to one that is

LAN-free enabled. The next reason a storage pool is
reported as not LAN-free capable is if there are no
paths defined for a device to this storage agent. Use the
QUERY PATH, QUERY SERVER, QUERY STGPOOL,
QUERY LIBRARY, and QUERY DRIVE commands to
determine the drive or drives that need paths defined
to this server (storage agent). The final reason a storage
pool is reported as not LAN-free enabled is if there are
define paths to this storage agent but no paths are
online. Use the QUERY PATH and QUERY DRIVE
commands to evaluate this and if necessary use update
those paths to be online.
ANR0397I
Session session number for node

agent_node has begun a proxy session for
node target_node.
Explanation: A client session has begun proxy

operations.
System action: The server granted a proxy session to
a client node.
ANR0398W

agent_node has failed to begin a proxy
session for node target_node.

name using storage agent storage agent name. This
storage pool is configured for simultaneous write
operations. Simultaneous write operations are only
allowed for data sent directly to the server. Configuring
a storage pool for simultaneous write operations
disqualifies it from being eligible for use for LAN-free
operations.
Explanation: A client session attempted to begin a

proxy operation. The server failed the client request.
This can occur if the agent node does not have a proxy
association with the target node.
User response: To configure this node for LAN-free

data transfer operations, update the destination storage
pool for the copygroup or assign this node to a domain
that has LAN-free storage pool destinations. Or update
this storage pool to disable simultaneous write by
setting the copy storage pools field to blank.
ANR0396W

operations is not LAN-free enabled for
node node name using storage agent name
because no online paths are available.

name using storage agent storage agent name.
User response: A storage pool can be reported as not
having LAN-free enabled paths for a number of
reasons. First, if this is a DISK storage pool, these are
not capable of LAN-free operations. In this case, the
destination for this node or the domain that this node
90
System action: The server blocks the proxy

authorization attempt.
ANR0399I

agent_node has ended a proxy session for
node target_node.
Explanation: A proxy session has been ended. The

server terminates a session if there is an error in the
protocol. On the other hand, the client can also
terminate the session.
System action: The server, or the client, has ended a
proxy session for a client node.
ANR0400I
Session session number started for node

node name (client platform) (communication
method).
Explanation: A new client session has been initiated

by the specified node. The session number, client
platform type and communication method used by this
session are included in the message.
System action: The server begins a communications
ANR0401I ANR0410E
session to service the client node.
ANR0406I

ANR0401I

method) (WDSF client).
Explanation: A new WDSF client session has been

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

by the specified node. The session number, client
platform type, communication method and address
used by this session are included in the message.
ANR0407I

ANR0402I
Session session number started for

administrator administrator ID
(administrators platform) (communication
method).
Explanation: A new administrator client session has

been initiated by the specified administrator. The
session number, administrators platform type and
communication method used by this session are
included in the message.
session to service the administrator client.
Session session number ended for node

node name (client platform).
Explanation: A client session has completed normally.


ANR0408I
Session session number started for server

server name (servers platform)
(communication method) for purpose.
Explanation: A new server session has been initiated

by the specified server for the specified purpose. The
session number, servers platform type and
communication method used by this session are
included in the message.

ANR0404I
Session session number started for

administrator administrator ID
(administrators platform) (communication
method communication address).
Explanation: A new administrator client session has

been initiated by the specified administrator. The
session number, administrators platform type,
communication method and address used by this
session are included in the message.

ANR0403I

method communication address).
Session session number ended for node

node name (client platform) (WDSF client).

Session session number ended for server
server name (client platform).
Explanation: A WDSF client session has completed

normally.
ANR0409I
Explanation: A server has completed normally.

ANR0405I
Session session number ended for

administrator administrator ID (client
platform).
Explanation: An administrative client session has

completed normally.
ANR0410E
EXPORT operation to server server name

rejected - administrator administrator is
not authorized to perform the import
operation on the target server.
Explanation: An export operation to the named server

was rejected, because the administrator issuing the
export command is not defined on the target server or
does not have sufficient authority to perform the
import operation on the target server.
91
ANR0411I ANR0419W
ANR0411I
Session session number for administrator

administrator name logged in as node node
name restored or retrieved object type
object: node node name, filespace filespace
name, object object name.
Explanation: This message logs information about an

object that was restored or retrieved by an
administrator logged in for a node.
ANR0412I

name(Userid=user id), restored or
retrieved object type object: node node
name, filespace filespace name, object object
name.
Explanation: This message logs information to the

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

name is restoring backup set: node node
name, set filespace name.
ANR0416W
Explanation: This session attempted this operation

using the specified data transfer path. This operation is
not permitted for this client.
User response: Issue QUERY NODE
FORMAT=DETAILED for this node to see the current
DATA WRITE PATH or DATA READ PATH settings.
These settings determine if a given operation is
permitted using a specific data transfer path. If this
client node should be permitted to perform this
operation using this data transfer path, the UPDATE
NODE command should be used to correct this.
ANR0417W

ANR0414I

name is restoring backup set: node node
name, set filespace name.
Explanation: This message logs information about a

backup set restored by a node.
ANR0415I
Session session number proxied by storage

agent name started for node node name.
Explanation: This session is started for the indicated

node and the storage agent acts as the proxy for the
node. Client node sessions are used to perform
LAN-free operations between the client and server.
92

name terminated - data transfer path not
allowed.
Explanation: This session attempted an operation that

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
operation and data transfer path was attempted.
ANR0418W
Explanation: This message logs information about a

backup set restored by an administrator logged in for a
node.

name not allowed to operation using path
data transfer path.

administrator name (client platform) is
refused because an incorrect password
was submitted.

client session because an invalid password has been
submitted by the client during sign-on processing.
System action: The server will continue to deny access
attempts by this client until a valid password is
submitted.
User response: Enter the proper password. If you
have forgotten the password, contact an authorized
administrator, who can assign a new password using
the UPDATE ADMIN command.
ANR0419W
Administrative client userid

administrative ID cannot be used when
authentication is on.
Explanation: The server refuses a request for a client

(administrative) session because the user ID specified
cannot be used when authentication of IDs is in effect.
SERVER_CONSOLE is an administrative ID that has
this restriction.
ANR0420W ANR0427W
User response: Use an administrative ID that was

registered for this server and that has a password.
User response: Register the administrator name with

the server before establishing a session. An authorized
administrator must use the REGISTER ADMIN
command to register the administrator with the server.
ANR0420W

name (client platform) refused - server
disabled for user access.

(backup-archive) session because the server is currently
disabled for client access.
Administrative clients are permitted access to the
server.
User response: An authorized administrator must
issue the ENABLE SESSION command before client
nodes are permitted access to the server.
ANR0421W

name (client platform) refused - sign-on
protocol violation.

session because sign-on protocol has been violated.
User response: This error is usually the result of a
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
by an application that is not a part of this product.
ANR0422W

name (client platform) refused - node
name not registered.

client session because the client node name is not
registered in the server database.
ANR0424W

client session because an invalid password has been
submitted by the client during sign-on processing. The
server will continue to deny access attempts by this
client until a valid password is submitted.
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
ANR0425W
ANR0423W

administrator ID (client platform) refused administrator name not registered.
Explanation: The server refuses a request to start an

administrative session because the administrator name
is not registered in the server database.

name (client platform) refused - Node
password has expired.
Explanation: The server refuses the specified session

because the client nodes password has expired.
User response: Upon receipt of this error condition,
the client program immediately reconnects to the server
specifying a password update session and prompts the
user for a new password. After the user enters a new
password, the client reconnects to the server for normal
operations. Alternatively, an authorized administrator
can update the client password using the UPDATE
NODE command.
ANR0426W

User response: Register the node name with the
server before establishing a session. If the server is
running with OPEN registration, no action is required;
the client prompts the user for a password and
registers the client with the server. If CLOSED
registration is in effect on the server, an authorized
administrator must use the REGISTER NODE
command to register the client node name with the
server.

name (client platform) refused - invalid
password submitted.

name (client platform) refused - open
registration not permitted.
Explanation: The server refuses a client session

because an open registration action has been attempted
and the server is running with CLOSED registration.
User response: Ask an authorized administrator to
submit the request using the REGISTER NODE or
REGISTER ADMIN command.
ANR0427W

version is down-level with this client.

because the client program version level is newer than
that supported by the server program.
93
ANR0428W ANR0434W
User response: Apply service to the server program to
make it compatible with the newer client program, or
use an older client program to contact the server.
ANR0428W

name (client platform) refused - client is
down-level with this server version.

because the client program version level is older than
that supported by the server program. For certain
problems (such as the compression fix), once a node
connects to the server using the newer client, the server
records this fact and will not let this node back off this
client version to a version that does not include the fix.
User response: Apply service to the client program to
make it compatible with the newer server program.
ANR0429W

name (client platform) refused - maximum
server sessions (max sessions allowed)
exceeded.
Explanation: The server refuses the specified client or

administrative session because the maximum number
of concurrent client sessions has been exceeded.
User response: If necessary, increase the maximum
number of permitted sessions. To do this, update the
value for the MAXSESSIONS parameter in the server
options file and restart the server with the updated
options file. Note that increasing the MAXSESSIONS
value requires additional memory resource by the
server. You may want to retry the connection at a later
time.
locked from server access (with the LOCK ADMIN

command).
User response: Before the administrator is permitted
to access the server, a properly authorized
administrator must unlock the administrator with the
UNLOCK ADMIN command.
ANR0432W
Explanation: The server ends the specified session

because sufficient memory (virtual memory) is not
available.
System action: The server ends the session and
continues operation.
application.
ANR0433W

name is locked.
Explanation: The server refuses the specified client

session because the node is locked from server access
(with the LOCK NODE command).
User response: Before the client node is permitted to
access the server, a properly authorized administrator
must unlock the node with the UNLOCK NODE
command.
ANR0431W

available to the server, an authorized administrator can
add log volumes using the DEFINE LOGVOLUME
command, and extend the size of the log using the
EXTEND LOG command.
Session session number for node or
administrator ID (client platform) refused insufficient database space.
Explanation: The server ends the specified client or

administrative session because sufficient database space
is not available to complete a database transaction.
administrator can add database volumes using the
DEFINE DBVOLUME command, and extend the size of
the database using the EXTEND DB command.
Session session number refused administrator administrator ID (client

platform) is locked.
Explanation: The server refuses the specified

administrative session because the administrator is
94

administrator ID (client platform) refused insufficient recovery log space.
Explanation: The server ends the specified client or

administrative session because sufficient log space is
not available to complete a database transaction.
ANR0434W
ANR0430W

name (client platform) refused insufficient memory.
ANR0435W ANR0442W
ANR0435W

name (client platform) refused - internal
error detected.

because an internal logic error is detected.
User response: To determine the source of the error,
the administrator can examine server messages issued
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,
contact your service representative.
ANR0436W
Session session number refused - a WDSF

client is attempting to access the server
using client name client node name (client
platform), associated with a non-WDSF
client.

because a Workstation DataSave Facility (WDSF) client
is attempting to access the server using a node name
associated with a non-WDSF client. When converting
from WDSF, WDSF client programs cannot be used to
access the server with a specific node name once the
non-WDSF client program has been used to access the
server with that node name.
User response: Use the QUERY LICENSE command to

determine the license terms that are no longer in
compliance.
ANR0439W
Session session number for node client

node name (client platform) encountered an
internal server error while checking
license compliance.
Explanation: The server encountered an internal error

in determining if the server is in compliance with
license terms.
System action: The client session is ended.
User response: Use the QUERY LICENSE and QUERY
STATUS commands to determine if the server is in
compliance with license terms. Start an AUDIT
LICENSES process to readjust server license
information. When this process completes you may
restart the session. If the problem persists, contact your
service representative.
Explanation: The server refuses a client backup

operation because the current server configuration is
not in compliance with license terms.
System action: Server operation continues. Clients
may perform any action except backup or archive.
compliance.
ANR0440W
Protocol error on session session number

for node client node name (client platform) invalid verb header received.
Explanation: The server detects a protocol error on the

specified session because an invalid verb header has
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: Correct the programming error in the

client program if it has been written by your
installation using WDSF verbs. Otherwise, contact your
ANR0441W
Session session number archive operation

for client client node name (client platform)
has been denied - Server is not in
compliance with license terms.
Explanation: The server refuses a client archive

operation because the current server configuration is
not in compliance with license terms.

for node client node name (client platform) invalid data length received.

specified session because an invalid verb length has
been received from the client.
System action: The server ends the client session.
ANR0442W
ANR0438W
Session session number backup operation

for client client node name (client platform)
has been denied - Server is not in
User response: Access the server using a non-WDSF

client program for the node name.
ANR0437W

may perform any action except backup or archive.

for node client node name (client platform) invalid stream mode switch.

specified session because the client has attempted an
illegal stream operation.
95
ANR0443W ANR0449W
installation. Otherwise, contact your service
representative.
ANR0443W

for node client node name (client platform) invalid "field name" field found in "verb
name" verb (offset offset position).

specified session because an invalid field has been
found in a verb sent from the client node.
method that is no longer supported by the Server.

System action: Server operation continues. The clients
backup operation continues, without compressing the
data.
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
method.
ANR0447W

ANR0444W

for node client node name (client platform) out-of-sequence verb (type verb name)
received.

specified session because a verb has been received that
does not adhere to the client-server exchange sequence.
Session session number space

management migration operation for
client client node name (client platform) has
been denied - Server is not in
Explanation: The server refuses a client space

management migration operation because the current
server configuration is not in compliance with license
terms.
may perform any action except backup, archive, or
space-managed file migration.
compliance.

User response: If the client generating the error is not
an API client, contact your service representative. If the
client generating the error is an API client, contact the
owner of the API client. If the client generating the
error is a client that you have created using WDSF
verbs, correct the programming error in your client
program.
ANR0445W

for node client node name (client platform) maximum group transaction size
exceeded.

specified session because the client has attempted to
group more than the maximum database update
operations in a single database transaction.
ANR0448W
Explanation: The server refuses a client space

management migration operation because the server is
not licensed to support space-managed clients.
User response: Licenses to support space-managed
clients can be obtained from your service provider or
re-seller. The REGISTER LICENSE command can be
used with these licenses to enable space management
support.
ANR0449W

ANR0446W
Session session number client client node

name compression method unsupported Compression forced OFF. Please obtain
the latest level of the client code.
Explanation: The client is using a compression
96

been denied - server is not licensed for
space management support.

client client node name (client platform) is
in violation of server license terms server is not licensed for space
management support.
Explanation: The server warns about a client space

management migration operation because the server is
not licensed to support space-managed clients.
User response: Licenses to support space-managed
clients can be obtained from your service provider or
ANR0450W ANR0455W
re-seller. The REGISTER LICENSE command can be
used with these licenses to enable space management
support.
must use the DEFINE SERVER or UPDATE SERVER

command register the servers and set the passwords.
ANR0453W
ANR0450W
Session session number for server server

name not defined for server to server
communications.

server session because the requesting server name is
not defined in the server database, or the requesting
server definition does not have a SERVERPASSWORD,
or a password or node name is not setup for virtual
volume use on the source server.
ANR0451W

name (server platform) refused - invalid
password submitted.

server session because an invalid password has been
submitted during sign-on processing. The server will
continue to deny access attempts by that server until
valid passwords are submitted.
User response: Set the proper passwords. If the
password has been changed on either server, an
authorized administrator can set new passwords by
using the UPDATE SERVER command with the
SERVERPASSWORD parameter.
ANR0452W
Explanation: The server to server session cannot be

initiated because no server password has been defined
for this server.
User response: Define a server password with the SET
SERVERPASSWORD command and retry the
command.
ANR0454E
User response: Register the requesting server name

with the server before establishing a session, or update
the existing requesting server definition and set a
SERVERPASSWORD. An authorized administrator
must use the DEFINE SERVER or UPDATE SERVER
command to register the requesting server and set the
password. For a virtual volume environment, the
source server must have a definition for the target
server which includes a node name and password.
Session for server server name refused server name not defined for server to
server communications.

server to server session because a server name is not
defined in the server database, or the server definition
does not have a SERVERPASSWORD. Server to server
communications using the serverpassword requires that
the each server has had a server definition for the other
server.
User response: Register the server names on both
servers before establishing a session, or update the
server's existing server definition and set a
SERVERPASSWORD. An authorized administrator
Server to server session refused - no

password defined.
Session rejected by server server name,

reason: rejection reason.
Explanation: The server tried to open a session with

the named server. The session was rejected for the
indicated reason.
System action: The operation fails.
User response: Check both the servers for any
additional messages that might further describe the
reason the session was rejected. For a reason of
AUTHENTICATION FAILURE, ensure that all
passwords have been set correctly on both servers. The
password for the server (set by SET
SERVERPASSWORD on server X) and the password in
the server definition (set by DEFINE or UPDATE
SERVER X SERVERPASSWORD=) are the same
password. For a reason of VERIFICATION FAILURE,
use the QUERY SERVER command to determine that
the HLADDRESS and LLADDRESS of the target server
are correct. If they are not, correct them with the
UPDATE SERVER command. If they are correct,
resynchronize with the target server by issuing the
UPDATE SERVER FORCESYNC=YES. For a reason of
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
session. For a reason of INTERNAL ERROR, use the
messages on the target server to determine the
problem. For all reasons, if none of the above are
applicable, ensure that that the shown server has not
disabled this server with the DISABLE SESSIONS
SERVER command.
ANR0455W
Invalid Command command name for

SNMP session.
Explanation: An SNMP administrative session

attempted to run a command which is not an macro
invocation. SNMP administrative sessions are only
allowed to issue macro commands.
User response: Enter commands through the SNMP
97
ANR0456W ANR0463W
administrative interface which are macros defined on
the server.
ANR0456W
Session rejected for server server name the server name at High level address, Low
level address does not match.
administrator can assign a new password by using the

UPDATE ADMIN command.
ANR0460W
Open registration failed for session

session number - node name node name
(client platform) already exists.
Explanation: The server name at the address specified

does not match the name in the server definition. The
connection is not established.
Explanation: The server refuses a client session during

open registration because the client has specified a
node name that is already registered on the server.
System action: The server continues.
User response: Ensure the HLADDRESS and

LLADDRESS in the define server command are correct,
and that the servername on the server being contacted
matches the name used in the DEFINE SERVER
command.
User response: The client program user must specify a

different node name for the client in the client options
file.
ANR0457W
Session for server server name refused crossdefine is not allowed on this
server.

server to server session for crossdefine because it is not
allowed on this server. The server will deny any
sessions for crossdefine until crossdefine is allowed on
this server.
User response: An authorized administrator must use
the SET CROSSDEFINE ON command to allow cross
registration of servers.
ANR0458S
Server server name does not support

access by the Storage Agent.
Explanation: The storage agent attempted to contact a

Database Server, but the server contacted was not at
the correct level.
ANR0461W

open registration because the STANDARD policy
domain does not exist. All nodes added to the server
database under open registration are automatically
assigned to the STANDARD policy domain. This policy
domain must be defined and have an active policy set
to support open registration.
User response: If you want to support open
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and
activate a valid policy set in the domain. You can issue
the UPDATE NODE command to move nodes to
different policy domains after the nodes have registered
themselves through open registration.
ANR0462W
System action: The Storage Agent terminates.

User response: Specify a correct Database Server in
the devconfig file for the Storage Agent.
ANR0459W
Signon for administrator administrator

name refused - invalid administrator
name and/or password submitted.

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
deny access attempts by this administrator until a valid
password is submitted, or until the administrator is
locked due to maximum number of invalid password
attempts being exceeded.
User response: Enter the proper password. If the
password has been forgotten by the user, an authorized
98

session number for node node name (client
platform) - policy domain STANDARD
does not exist.

platform) - invalid node name.

open registration because the node name specified by
the client is not valid.
User response: Specify a node name in the options file
of the client program that contains valid characters and
does not exceed the maximum length in size. Refer to
Backup-Archive Clients Installation and Users Guide for a
description of the node name restrictions.
ANR0463W

platform) - invalid password.

open registration because the password name specified
by the user is not valid.
ANR0464W ANR0472E
System action: Storage agent operation terminates.
User response: Specify a password that uses valid

characters and is less than the maximum length in size.
Refer to Backup-Archive Clients Installation and Users
Guide for a description of the password restrictions.
User response: None
ANR0464W

platform) - exceeded number of nodes
available under license terms.
Explanation: The server detected an attempt to

register more nodes than allowed by the terms of the
current license.
REGISTER NODE command fails, and the node is not
registered.
compliance.
ANR0465W

platform) - policy domain STANDARD
does not have an ACTIVE policy set.

open registration because the STANDARD policy
domain does not have an active policy set. All nodes
added to the server database under open registration
are automatically assigned to the STANDARD policy
domain. This policy domain must be defined and have
an active policy set to support open registration.
ANR0468E
Explanation: An attempt was made to export to an

outdated server. The server on which the import is
performed must be at the same or later level than the
server from which the data was exported.
System action: The export operation ends and server
User response: Export to a server that is at the same
or later level.
ANR0469W
ANR0466E
The SETSTORAGESERVER command

did not complete successfully.
Explanation: The SETSTORAGESERVER command

encountered an error and did not complete successfully.
System action: Storage agent operation terminates.
User response: Please review prior error messages and
take the necessary corrective actions.
ANR0467I
The SETSTORAGESERVER command

Explanation: The SETSTORAGESERVER command

has completed successfully, and the appropriate device
configuration files have been updated.

not configured for archive retention
protection.

because the client is not configured for archive
retention protection.
User response: Either disable archive retention
protection on the server or configure the client for
archive retention protection.
ANR0470W

User response: If you want to support open
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and
activate a valid policy set in the domain. You can issue
the UPDATE NODE command to move nodes to
different policy domains after the nodes have registered
themselves through open registration.
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.

dministrator name refused - administrator

because the administrators password has expired.
ADMIN command.
ANR0472E
The database manager did not start. A

tablespace container is inaccessible.

database manager.
User response: Before restarting the server, check the
following items:
v Reboot the system.
99
ANR0473W ANR0478W
v Check that the directories for dbdir, log, or devices
exists and that the file system is mounted (if it is on
a separate file system).
v Make sure that the hardware and network
connection are working properly.
User response: The client option file should be

updated to specify the port to be used for client
sessions. This is typically specified by TCPPORT option
in both client and server option files. The MVS server
also uses the ICSPORT option.
v Fix any errors in the system log or db2diag.log.

ANR0476W
ANR0473W

administrator ID (client platform) refused administrator name does not have the
correct level of authority over client
node.

administrative session because the administrator name
does not have appropriate authority over the node.
User response: Use command GRANT AUTHORITY
to grant appropriate authority to the current
administrator ID.
ANR0474W

administrator ID (administrator platform)
was refused because administrators are
not allowed to initiate sessions on the
client port.
Explanation: The server did not start the specified

administrative session because the administrator
connected to the server on the server port that is used
for client sessions, and the option
ADMINONCLIENTPORT is set to NO. When different
port numbers are used for administrative and client
sessions (controlled by the TCPPORT and
TCPADMINPORT options), and option
ADMINONCLIENTPORT is set to NO, administrative
sessions can be started only on the port used for
administrative sessions (as specified by the
TCPADMINPORT option).
User response: Update the client options file to
specify the port to be used for administrative sessions.
This is typically specified by the TCPADMINPORT
option in both client and server option files.
ANR0475W

name (client platform) refused - node is
not allowed to initiate sessions on
administrative port.
Explanation: The server had refused to start a session

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
administrative and client sessions, client sessions may
be started only on the port used for client sessions.
Explanation: The server had refused to start a session

with the specified client node because the node is not
allowed to initiate session. Only server initiated
sessions are allowed with this client. The SESSIONINIT
parameter of the REGISTER NODE and UPDATE
NODE commands control the ability of a client to
initiate sessions.
User response: An administrator can use the UPDATE
NODE command with the SESSIONINIT parameter to
specify that the client may initiate sessions.
Alternatively, sessions can be scheduled with the client
that are stared by the server through server-prompted
scheduling commands ( DEFINE SCHEDULE, DEFINE
ASSOCIATION ).
ANR0477W
Session session number refused - The

client client node name cannot access the
server with a platform type of client
platform.
Explanation: A client with a invalid combination of

node type and platform type has requested a session
with the server. For example, a node id of type NAS
can only sign on with a platform type of "TSMNAS",
all other node types cannot use this platform type.
System action: The session request is refused. The
server operation continues.
User response: Verify that the Id used by a client to
sign on has the proper platform type.
ANR0478W
Session request refused. Server is

running in standalone mode.
Explanation: A client has requested a session with the

server. The server is running in a mode in which it
cannot start client sessions.
User response: No response is required. To reduce or
disable the display of this message, you can update the
server options before running in standalone mode with
the COMMMETHOD NONE option. This will allow the
server to run without enabling client connections.
100

name (client platform) refused - node is
not allowed to initiate sessions.
ANR0479W ANR0484W
ANR0479W

name (server platform) terminated connection with server severed.
Explanation: If server A has opened a connection with

server B, server B's session is ended because the
communications link has been closed by a network
error or by server A's program.
System action: Server A continues operation.
User response: If server B halts operation or in some
way stops communicating with server A, this message
will be displayed on server A indicating that the
connection was closed suddenly by server B. A network
failure can also cause this message to be displayed. If a
large number of these messages occur simultaneously,
check the network for failure and correct any problems.
ANR0480W

name (client platform) terminated connection with client severed.
Explanation: The specified client session is ended

because the communications link has been closed by a
network error or by the client program.
ANR0482W

name (client platform) terminated - idle for
more than idletimeout minutes minutes.
Explanation: The server ends a client session because

it has been idle for more minutes than specified in the
IDLETIMEOUT parameter in the server options file.
The client program will automatically attempt to
reconnect to the server when necessary.
User response: If the problems persists, increase the
value specified for the IDLETIMEOUT parameter in the
server options file and restart the server. Many times,
the client program is idle while waiting for the user to
choose an action to perform (for example, backup,
archive, restore, or retrieve files). If a user starts the
client program and does not choose an action to
perform, the session will eventually time out. The client
program automatically reconnects to the server when
the user chooses an action that requires server
participation. Note that a large number of idle sessions
can inadvertently prevent other users from connecting
to the server, so care should be used when increasing
the IDLETIMEOUT parameter.

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
network failure can also cause this message to be
displayed. If a large number of these messages occur
simultaneously, check the network for failure and
correct any problems.
ANR0481W

name (client platform) terminated - client
did not respond within commtimeout
seconds seconds.
Explanation: The server ends a client session because

the client has been holding database locks (a
transaction was in progress) and the client has not
responded in the number of seconds specified by the
COMMTIMEOUT parameter in the server options file.
System action: The server rolls back the transaction
that has been in progress and the session is ended.
User response: If a large number of these messages
appear, you may want to increment the value specified
for the COMMTIMEOUT value in the server options
file and restart the server. The amount of time that it
takes for a client to respond is dependent upon the
speed and processor load for the client and the network
load.
ANR0483W

name (client platform) terminated - forced
by administrator.
Explanation: The server ends a client session in

response to a CANCEL SESSION command issued by
an authorized administrator.
System action: The server rolls back any transactions
in progress for the terminated client session.
ANR0484W

name (client platform) terminated protocol violation detected.

because a communications protocol error by the client
has been detected.
User response: Examine the client message to
determine the problem. Correct the programming error
in the client program. If the error cannot be isolated
and resolved, contact your service representative.
If this session is a proxied LAN-Free session for a
storage agent, this error may be the result of a mount
point or volume preemption on the storage agent.
Review the messages logged by the storage agent to
determine if a storage agent action caused this to occur.
101
ANR0485W ANR0490I
ANR0485W

name (client platform) terminated sufficient memory is not available.

available.
application.
ANR0486W

name (client platform) terminated internal error detected.
Explanation: The specified client session is ended by

the server because an internal processing error has been
detected on the server. A programming error may have
occurred in the server program.
System action: The session is ended and server
User response: If this session is a proxied LAN-Free
session for a storage agent, this error may be the result
of a mount point or volume preemption on the storage
agent. Review the messages logged by the storage
agent to determine if a storage agent action caused this
to occur.
If the cause of the error can not be determined after
reviewing the activity log, contact your service
representative.
ANR0487W

name (client platform) terminated preempted by another operation.
Explanation: The server ends a client session in

response to a cancel request issued by a higher priority
operation that needed the mount point that the client
was using.
System action: The server rolls back any transactions
in progress for the terminated client session.
User response: Reissue the operation. If this message
appears frequently, consider increasing the mountlimit
value for the affected device class.
ANR0488W

name (client platform) terminated transfer rate is less than (transfer rate)
and more than (elapsed time since first data
transfer) minutes have elapsed since first
data transfer.
Explanation: The server is canceling client session

number session number. Depending on the state of the
session, it may take a while for the session to be
102
canceled. The server ends a client session because it has

been active for more minutes than specified in the
THROUGHPUTTIMETHRESHOLD parameter in the
server options file and the data transfer rate is less than
the amount specified with the
THROUGHPUTDATATHRESHOLD parameter in the
server options file. The client is transferring data to the
server at an abnormally slow rate and may have
become a bottleneck for handling data from other
clients. If the client has caused log records to be
written, it is possible that this client will prevent log
space reclamation.
System action: The session is canceled and server
User response: If a low data transfer rate is not a
problem, the THROUGHPUTTIMETHRESHOLD or
THROUGHPUTDATATHRESHOLD parameters in the
server options file can be set to zero - this will disable
the throughput check. The change can be made without
taking down the server and restarting it by using the
SETOPT THROUGHPUTTIMETHRESHOLD or the
SETOPT THROUGHPUTDATATHRESHOLD
commands. If a low data transfer rate is not expected,
external causes should be investigated. This would
include network problems and problems in accessing
data on the client node. The client program may
automatically reconnect to the server, so this message
may appear on subsequent sessions until the data
transfer problem is resolved. The default server
operation is not to perform a throughput check.
ANR0489W
Session session number refused for client

node name - NAS type nodes are not
supported by a storage agent.
Explanation: The specified client tried to connect to a

storage agent. The storage agent does not support a
node that is defined as TYPE=NAS.
User response: The client should be re-configured to
not try LAN-free operations. This may be done by
setting UPDATE NODE ENABLELANFREE=NO for the
client.
ANR0490I
Canceling session session number for

node node name (client platform) .
Explanation: The server is canceling client session

number session number. This message is displayed in
response to the CANCEL SESSION command.
Depending on the state of the session, it may take a
while for the session to be canceled.
ANR0491I ANR0500W
ANR0491I
No matching session(s) found to cancel.
ANR0495I
Cannot cancel the specified

EXPORT/IMPORT session.
Explanation: The server cannot find any sessions to

cancel matching the specifications entered in the
CANCEL SESSION command.
Explanation: The server cannot cancel the session

specified in the CANCEL SESSION command.
User response: Use the QUERY SESSION command to

ensure that the session you wish to cancel is connected.
Reissue the command using the appropriate session
number to cancel the client session.
User response: Export/Import sessions cannot be

canceled using CANCEL SESSION. The user should
use the CANCEL PROCESS command to terminate the
EXPORT/IMPORT operation.
ANR0492I
All drives in use. Session session number

for node node name (client platform) being
preempted by higher priority operation.
Explanation: When a high priority operation

attempted to find an available drive, all the drives were
being used. To free up a drive for this operation, the
client session identified is being cancelled by the
system.
System action: The lower priority client session is
cancelled to free up a mount point (drive).
User response: When a drive again becomes available,
restart the session that was cancelled. This session was
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
frequently, you may want to increase the number of
drives available. See the MOUNTLIMIT parameter on
the UPDATE DEVCLASS command.
ANR0493I
Restore session session number canceled.
Explanation: The specified session was canceled with

the CANCEL RESTORE command.
ANR0496E

operation because archive retention protection is active.
User response: Do not send the specified operation to
the server when archive retention protection is active.
ANR0497W
ANR0494I
Volume volume name in use. Session

platform) being preempted by higher
priority operation.

attempted to acquire a specific volume, it was being
used. To free the volume for this operation, the client
session identified is being cancelled by the system.
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
finished with the volume. This cancelled session was
most likely a backup/archive session and you may just
want to let it restart automatically during its next
scheduled backup window.
Session request refused from

non-Express client.
Explanation: A non-Express client has requested a

session with the Express server. Only connections from
an Express client will be accepted by an Express server.
ANR0498W
System action: The restore session is canceled and

Session session number operation for

been denied because verb (type verb
name) is not allowed when archive
retention is active.
Session session number refused for client

node name because restore DB is in
progress.
Explanation: Restore DB is in progress, only

connection from Client related to restore DB are
allowed.
server Restore DB operation continues.
ANR0500W
Transaction failed for session session

number for node node name (client
platform) - invalid password submitted.
Explanation: The server ends a password update

transaction because the user has not correctly specified
the current password.
User response: Update your password by correctly
specifying the current password. If the current
password has been misplaced, the administrator can
103
ANR0501W ANR0507E
reassign a password for the client by using the
UPDATE NODE or UPDATE ADMIN command.
ANR0501W

platform) - invalid policy binding
specified.
Explanation: The server ends a database update

transaction for the specified session because an invalid
management class has been specified for a file or
directory object.
System action: The specified session is ended and
ANR0502E

platform) - A storage pool for the target
destination is associated with a device
class that has a Centera device type.

management class has been specified. Centera device
types may be used only for archive objects.
Explanation: This message logs information to the

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.
ANR0505E
Explanation: The server received an unexpected data

value.
System action: The server cannot process the
command.
User response: Before reissuing the command, try the
following actions:
v Reboot the system.
v Check that the directories for dbdir, log, or devices
exists and that the file system is mounted (if it is on
a separate file system).
v Make sure that the hardware and network
connection are working properly.
v Fix any errors in the system log or db2diag.log.
ANR0506I

User response: Ensure that Centera device types are
associated with device classes that are used only for
archive operations. The UPDATE COPYGRP command
can be used to update copy groups associated with
space mamagement and/or backup storage pools so
that they point to valid destinations.
The database manager encountered a

null value for column name during the
data fetching.
A full backup has been started for

database DB Alias. This backup is
required.
Explanation: This level of the Tivoli Storage Manager

server uses a new version of the database manager that
has a new format for log files. Database backups
created prior to this level of the server cannot be used
to restore the database. A new database backup image
is needed to ensure that the database is protected.
System action: A full database backup is started.
ANR0503I

name restored or retrieved object type
object: node node name, filespace filespace
name, object object name, version version
of total version.
Explanation: This message logs information about an

object that was restored or retrieved by an
administrator logged in for a node.

ANR0507E

for node client node name (client platform)
because an owner was not properly
provided for the indicated node.
Explanation: The session does not adhere to the

client-server exchange sequence, therefore the server
detected a protocol error on the specified session.
ANR0504I
104

name(Userid=user id), restored or
retrieved object type object: node node
name filespace filespace name, object object
name, version version of total version.
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
the client in a non-standard environment.
ANR0508E ANR0518W
ANR0508E
An automatic full database backup for

database DB Alias has failed.
Explanation: A full database backup failed. This

message always accompanies one or more other
message that provides more details about the error.
System action: The server operation continues.
User response: Examine the server messages that were
issued prior to this message to determine the source of
the error. Issue the QUERY ACTLOG command to view
the activity log and search for messages.
ANR0513I
Explanation: The indicated process has opened the

specified volume for output processing. You may not
see an associated ANR0515I message for this
process/volume combination, since some volumes are
shared between multiple processes.
ANR0514I
ANR0509E
The database restore failed on DB Alias

due to the log format differences
between database manager versions.
Explanation: The database restore failed because the

backup image was produced by a previous version of
Process process number opened output

volume volume name.
Session session number closed volume

volume name.
Explanation: The indicated session has finished using

the specified volume.
System action: The database restore terminates.

User response: If you need to restore the database
immediately, uninstall the upgraded server, re-install
the previous version of the server, then run the restore
command. Otherwise, start the upgraded server. The
upgraded server creates a new backup image
automatically. After the database backup completes, run
the server restore utility again.
ANR0515I
Process process number closed volume

volume name.
Explanation: The indicated process has finished using

the specified volume. It is possible that the process
indicated was not the process that opened the volume.
ANR0510I
Session session number opened input

volume volume name.
Explanation: The indicated session has opened the

specified volume for input processing.
ANR0511I
ANR0516E
Explanation: The indicated select statement failed. The

failure was caused by a syntax error with the statement
itself.
System action: The select statement failed.
Session session number opened output

volume volume name.
Explanation: The indicated session has opened the

specified volume for output processing.
User response: Review the server activity log for

message ANR0162W for an explanation of the error
that caused this statement to fail.
ANR0517E

ANR0512I
Process process number opened input

volume volume name.
Explanation: The indicated process has opened the

specified volume for input processing. You may or may
not see an associated ANR0515I message for this
process/volume combination, since some volumes are
shared between multiple processes.
SQL processing for statement statement

failed.
command: The DEDUPLICATION

parameter cannot be used with either
the TYPE=SERVER or TYPE=NAS
parameter.

DEDUPLICATION parameter.
ANR0518W
NDMP restore failed for session session

platform), file space filespace.
Explanation: The server ends a restore operation for

the specified NAS node because an error has been
encountered on the server. Some common reasons for
the error are:
105
ANR0519E ANR0523W
v The input volume is unavailable
v The storage pool is unavailable
v Data is corrupted on the input volume
v Hardware or media failure has occurred
v The server database is corrupted
System action: The server ends the restore operation.

transaction for the specified session because the size of
a file sent from the client node is larger than that
allowed in the storage pool specified in the clients
management class copy group. No successor storage
pools to the one specified on the copy group can accept
the large file.
User response: Examine any prior error messages to

determine the source of the error. Use the QUERY
ACTLOG command to view the activity log and search
for messages if needed. Correct any problem and try
the restore again. You can also refer to the Problem
Determination Guide for problem determination hints
and information. If the data is also backed up in a copy
storage pool, the retry operation will attempt to read
the file from the alternate location. If retry of the
restore operation continues to fail contact your service
representative.
User response: If the client is not using compression

to send files to the host, turn compression on for the
client (using the UPDATE NODE command) to try and
resolve the problem. Otherwise, the maximum file size
for one or more of the storage pools in the storage
hierarchy can be increased to accommodate the file. An
authorized administrator can increase the MAXSIZE
parameter by issuing the UPDATE STGPOOL
command.
ANR0519E
ANR0522W
A retrieve or restore operation failed for

session session number for node node name
(client platform). An invalid partial object
request was received.
Explanation: The server ended a file retrieve or restore

operation for the specified session because an invalid
value for the offset, length, or both was received from
the client application for the object being retrieved or
restored.
System action: The server ends the specified operation
and server operation continues.
User response: Specify an offset, length, or both
within the bounds of the object to be retrieved or
restored, and rerun the application.
ANR0520W

platform) - storage pool pool name is not
defined.
Explanation: The server rolls back a database update

transaction for the specified session because the
destination specified for a management class copy
group specifies the named storage pool, but that
storage pool does not exist.
User response: An administrator with policy authority
over the client policy domain must correct management
class definitions so that copy group destinations refer
to defined storage pools, or the specified storage pool
must be created by an authorized administrator.
ANR0521W
106

platform) - object excluded by size in
storage pool pool name and all successor
pools.

platform) - no space available in storage
pool pool name and all successor pools.

transaction for the specified session because the storage
pool specified in the clients management class copy
group does not contain enough free space to hold the
files sent from the client. Successor storage pools to the
one specified on the copy group do not contain enough
free space.
User response: An authorized administrator can issue
the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy. This
action may also involve creating storage space by using
an operating system specific utility.
ANR0523W

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
device.
User response: Query the activity log to find messages
preceding this one that specify the failing device.
Storage pool volumes can be varied offline (by using
the VARY command), or the server may need to be
halted to correct the hardware problem. After the
problem is corrected, the client should retry the
operation.
ANR0524W ANR0531W
ANR0524W

platform) - data transfer interrupted.
Explanation: The database transaction associated with

session session number was aborted because data
transfer to or from data storage was interrupted by an
external event.
User response: Examine the messages issued prior to
this message to determine why the data transfer was
interrupted. Attempt the client operation again if the
problem can be resolved.
ANR0525W

platform) - storage media inaccessible.
Explanation: The server ends a transaction for the

specified session because storage volumes are not
available in the storage pools in which the clients files
are to be stored.

the DEFINE DBVOLUME command to add volumes
for use by the database, and can issue the EXTEND DB
command to extend the size of the database so that the
new volumes are used.
ANR0528W

transaction for the specified session because sufficient
memory is not available for starting additional
processes on the server.
System action: The server ends the specified session
application.
ANR0529W

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
make them available to client nodes for file storage.
ANR0526W

platform) - sufficient recovery log space
is not available.

log space is not available on the server.
the DEFINE LOGVOLUME command to add volumes
for use by the log, and can issue the EXTEND LOG
command to extend the size of the log so that the new
volumes are used.
ANR0527W

platform) - sufficient database space is
not available.

database space is not available on the server.

platform) - thread resource not available.

platform) - insufficient memory.

memory is not available on the server.
application.
ANR0530W

platform) - internal server error detected.

transaction for the specified session because an internal
logic error is detected.
the activity log and search for messages that indicate
the source of the error.
ANR0531W

platform) - invalid file space identifier
specified by client.

transaction for the specified session because the file

107
ANR0532W ANR0536W
space identified by the client for the transaction does
not exist.
System action: This action usually occurs when a
client is operating on a file space that is currently being
deleted as a result of an administrative command or
client action. The server ends the specified session and
User response: Use the QUERY PROCESS command
to monitor and wait for any file space deletion
processes to complete, or cancel the process if you do
not want to delete the file space. Try the client action
again after this action has been taken.
ANR0532W
Diagnostic(ID): Transaction transaction ID

was aborted for session session number
for node node name (client platform).
Explanation: An error has been detected during a

transaction commit for the specified session. This
message should be preceded by other messages that
give additional information about the failed transaction.
fails.
User response: Check for additional messages and
eliminate the condition that caused the failed
transaction. If the error cannot be isolated and resolved,
ANR0533W

number - compression method used by
client not supported. Please obtain the
latest level of the client code.
server operation continues. If pool name is a random

access storage pool with caching enabled, it is also
possible that additional space can be made available in
this storage pool by eliminating cached files. When the
server allocates space based on the size estimate
provided by the client, it frees space occupied by
cached files if this space is needed to obtain the
estimated space. However, if the server later determines
that the file size estimate was too low, it attempts to
obtain additional space that is not utilized, but does not
delete cached files to do so. If the client sending the
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
exceeded the space available in storage pool pool name.
User response: This message may indicate that there
is no additional space in pool name. The following are
possible circumventions:
An authorized administrator can issue the DEFINE
VOLUME command to add storage to this pool.
If the suspected cause of the failure is that pool name is
a DISK storage pool and that space in use by cached
files was not freed, turn off caching for the storage pool
and issue the MOVE DATA command for the volumes
in pool pool name.
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
COMPRESSALWAYS option in the client options file to
NO and retry the operation. This may allow the client
to accurately report the file size and possibly avoid the
out of space condition in the storage pool.
Explanation: The server ends the transaction for the

specified session because the compression method that
is used by the client is no longer supported by the
server.
ANR0535W

Explanation: The server was unable to allocate

sufficient mount points to process the transaction.
User response: The client must either backup the data

with compression turned off, or upgrade to a client that
supports the newer compression method. If the client is
a WDSF client, upgrade to a non-WDSF client in order
to use the compression performed by the client.
System action: The operation is ended and server

ANR0534W

platform) - size estimate exceeded and
server is unable to obtain additional
space in storage pool pool name.

transaction for the specified session because the size
estimate provided by the client is too small. The server
has attempted to obtain additional space in the
indicated storage pool, but was unable to do so.
108

platform) - insufficient mount points
available to satisfy the request.
User response: If necessary, make more mount points

available or validate your device class and library
configuration.
ANR0536W

platform) - down-level client does not
support format of stored files.
Explanation: A client attempts to perform an

operation involving files that are stored in a format that
is not supported by that client level.
User response: Upgrade the client to a later level.
ANR0537E ANR0543W
ANR0537E

platform) - filespace name cannot be
renamed from or to a Unicode name.

transaction for the specified session because a file space
was attempted to be renamed to or from unicode.
System action: The server ends the specified
transaction and server operation continues.
User response: Do not attempt to rename a unicode
file space to a non-unicode name or a non-unicode file
space to a unicode name.
ANR0538I
A resource waiter has been aborted.
If the node is not allowed to acquire any mount points

(the node's MAXNUMMP option is set to zero), issue
the UPDATE NODE command to change the value of
the MAXNUMMP parameter.
ANR0540W
Retrieve or restore failed for session

platform) - data integrity error detected.
Explanation: The server ends a file retrieval operation

for the specified session because an internal database
integrity error has been encountered on the server.
and continues operation.
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.
If this causes a process or a session to fail then there
will be other messages at this time indicating which
process or session has failed. Resources are internal
server resources such as locks and synchronization
objects.
Explanation: The server ends a client retrieval or

restore operation for the specified session because an
I/O error has been encountered by the server in
reading from a device.
System action: The server terminates the resource

with request and server operation continues.

User response: Either a server deadlock situation has

occurred or the resource timeout value is set too low.
Check the setting for the RESOURCETimeout server
option and increase the value. If the problem persists
with a higher timeout then contact your service
representative.

preceding this one that specify the device that is failing.
the VARY OFFLINE command), or the server may need
to be shut down by using the HALT command to
correct the hardware problem. After the problem is
corrected, the client may try the operation again.
ANR0539W

number for node node name. This node
has exceeded its maximum number of
mount points.
Explanation: The server ends the transaction because

the node requires mount points to store data, and
either the node is not allowed to acquire any mount
points, or the node is already using the maximum
number of mount points allowed for the node. The
maximum number of mount points a node is allowed
to use on the server is controlled by the setting of the
MAXNUMMP parameter on the REGISTER NODE or
User response: If the number of mount points that the
node is allowed to use on the server are already
acquired, reduce the number of client sessions for the
specified node that are running concurrently. For
example, decrease the value of the client option
RESOURCEUTILIZATION. If sufficient mount points
(for example, drives) are available to satisfy the data
store operations, issue the UPDATE NODE command
to increase the value of the MAXNUMMP parameter.
ANR0541W
ANR0542W

platform) - error on input storage device.

platform) - storage media inaccessible.

restore operation for the specified session because a
needed storage pool volume has been varied offline or
the storage pool is unavailable.
User response: Use the VARY ONLINE command to
vary offline storage volumes online in the storage
hierarchy and make them available to client nodes for
file storage. If all volumes are online, check the
ACCESS parameter of the storage pool. If the access
mode is UNAVAILABLE, use the UPDATE STGPOOL
command to update it to READONLY or READWRITE.
ANR0543W

platform) - data transfer interrupted.
109
ANR0544W ANR0549W
session session number was aborted because data
external event.
interrupted. Attempt the client operation again, if the
problem can be resolved.
ANR0544W

platform) - thread resource not available.
Explanation: The server ends a file retrieval or restore

operation for the specified session because sufficient
ANR0547E
Explanation: The server console session encounters an

error in formatting output from a command.
System action: The command output is discarded and
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
error if it is found. Contact your service representative
if you cannot resolve the error, or if an error is not
found.
ANR0548W

application.
ANR0545W

platform) - insufficient memory.

operation for the specified session because sufficient
application.
ANR0546W

platform) - internal server error detected.

operation for the specified session because an internal
logic error is detected in the server program.
User response: Examine the server messages issued
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.
Invalid data was encountered in the

command processor output stream:
output formatting terminated for the last
command entered.

platform) processing file space filespace
filespace id for file file name stored as
storage repository - error detected.

for the specified session because an error has been
the error are:
v Database corruption
User response: Try the restore or retrieve operation
again, and if the file is also backed up in a copy storage
pool, the operation will attempt to read the file from
the alternate location. If retry of the restore or retrieve
operation continues to fail examine any prior error
messages to determine the source of the error. Use the
QUERY ACTLOG command to view the activity log
and search for messages if needed. Correct the problem
and try the restore or retrieve again. You can also refer
to the Problem Determination Guide for problem
determination hints and information. If retry of the
restore or retrieve operation continues to fail contact
ANR0549W

platform) - no existing restore session
found.
Explanation: A client attempted to start an additional

no query restore session to increase restore throughput,
but the original restore session was not found.
110
ANR0550E ANR0556E
the problem and try the command again.
User response: Check the status of the original restore.

It may have already completed or been cancelled. The
QUERY SESSION command and the QUERY RESTORE
commands can provide information about existing
sessions and restore sessions which are restartable.
ANR0553E
ANR0550E
The client operation failed for session

platform) - see previous error messages.
Explanation: The indicated operation has failed. This

message is always preceded by one or more other error
messages which provide more detail about why the
command failed.
Client operation failed for session

session number - Administrator
administrator name does not have
adequate authority over node node name.
Explanation: The specified administrator does not

have the proper authority necessary to perform this
operation on the specified node.
System action: The server does not perform the query.
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.

ANR0554E
User response: Examine the previous error messages

to determine the source of the error. Use the QUERY
for messages if needed. Correct the problem and try the
command again.
Explanation: The command failed because the

TOSERVER parameter was not specified.
ANR0551E
The client operation failed for session

platform) - lock conflict.
Explanation: An operation that requires the server to

lock a system resource has been initiated. The operation
cannot be executed because the resource is already in
use by another command or process.
System action: The server does not process the
command.
User response: Try the command again at a later time.
ANR0552E

platform) - destination storage pool
storage pool was skipped.
Explanation: The indicated client operation failed

because the destination storage pool was skipped. A
storage pool may be skipped because it does not have
enough available space, or because it has a MAXSIZE
value that is less than the size of the object to be
inserted.
User response: Ensure that the destination storage
pool is available, has an adequate MAXSIZE setting,
and has adequate space. The MAXSIZE setting may be
changed using the UPDATE STGPOOL command.
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
them online and make them available for use. Correct
command name: The parameter name

parameter is only valid if the
TOSERVER parameter is specified.
System action: The command fails and server

User response: Reissue the command and specify the
TOSERVER parameter. For information on valid values
for the command parameter,refer to the Administrators
Reference for your particular platform.
ANR0555E
command name: The parameter name

parameter cannot be specified when the
TOSERVER parameter is specified.

TOSERVER parameter was not specified.
User response: Reissue the command and omit the
TOSERVER parameter. For information on valid values
for the parameter for the command parameter, refer to
the Administrators Reference for your particular
platform.
ANR0556E
command name: DATES=RELATIVE

parameter value cannot be specified
when merging imported files using the
MERGE=YES parameter value.
Explanation: When importing files and merging them

into existing file spaces, the DATES=RELATIVE
parameter value cannot be specified.
User response: Reissue the command and omit the
DATES=RELATIVE parameter. For information on valid
values for the parameter for the command, refer to the
111
ANR0557I ANR0563W
Administrators Reference for your particular platform.
ANR0557I
Import command: An invalid export

record (version version, copy type copy
type, object type object type) was found.
Explanation: An invalid import record was found for

the specified version, copy type and object type. The
object will be skipped, and import processing will
continue.
User response: Issue QUERY ACTLOG to determine
ANR0558W
Import processing did not create a

proxynode association for nodes
node_id_target and node_id_agent.
Explanation: Import processing did not create a

proxynode association between the two nodes. The
association fails if either of the nodes does not exist on
the server, or if import processing was not allowed to
complete.
System action: The server does not create the
specified proxynode association.
ANR0561E
Export command: Process aborted - sign

on to server, target server name, failed.
Explanation: The server export process encountered

an error in establishing a communication session with
the target server.
System action: The export process ends and server
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
server. Next, check the server definition, administrator
name, and password on both the server issuing the
command and the server specified. Also, check the
communication connection between the two servers.
And finally, verify that the target server specified is
running. If the problem is not resolved, contact your
ANR0562I
Export command: Data transfer complete,

deleting temporary data.
Explanation: The server export process has completed

writing data to the target media or server. Temporary
data used during the operation is now being deleted
from the database.
User response: Verify that both nodes were imported

properly and issue the import command again. Or, use
the GRANT PROXYNODE command to manually
create the proxynode association.
System action: The export process continues until all

temporary data is removed.
ANR0559E
ANR0563W
Too many domains are specified on the

EXPORT NODE command.
Explanation: The maximum length of the domain list

cannot exceed approximately 1400 characters.
System action: The EXPORT command is ended.
User response: If you specified DOMAIN=* on the
command, issue the command again without specifying
the domain to let it default to all domains. If you
specified a domain list, then split up the EXPORT into
multiple export commands to reduce the number of
domains specified on the command.
ANR0560E
Import command: Unable to decrypt

encrypted password or key.
Explanation: The server is not able to decrypt the

password associated with a node or administrator, or
the client encryption key associated with an object
being imported. The password or key was encrypted
with the AES encryption standard, but the server does
not support AES.
System action: The object is not imported.
User response: Rerun the export command, specifying
the ENCryptionstrength=DES option. Or, rerun the
import on a server that supports AES.
112

NDMP restore failed for node node name,
file space filespace.
Explanation: The server ends a restore operation for

the specified NAS node because an error has been
the error are:
v The server database is corrupted
System action: The server ends the restore operation.
for messages if needed. Correct any problem and try
the restore again. You can also refer to the Problem
Determination Guide for problem determination hints
and information. If the data is also backed up in a copy
storage pool, the retry operation will attempt to read
the file from the alternate location. If retry of the
restore operation continues to fail contact your service
representative.
ANR0564E ANR0570E
ANR0564E
Restartable restore request failed for

session session number, restartable restore
session restore session number - sessions
are active from the original restore.
Explanation: A client attempted to restart a restartable

no query restore session; However, sessions from the
original no query restore invocation are still active.
Both the current and restartable restore session
numbers are shown.
System action: The restartable restore request is ended
and server operation continues. The restore's
restartability status does not change.
User response: Check the status of the original restore.
The QUERY RESTORE command can be used to show
the status of restartable restores. The restartable restore
session number is the one for which sessions were
found to be running. Sessions may be active on either
the server or a storage agent. Restartable restores may
be cancelled by issuing the CANCEL RESTORE
command, after which the restore may be retried. Once
CANCEL RESTORE is issued for a restore session, it is
not eligible to be restarted.
ANR0565W

platform). The storage volume volume
name is inaccessible.

restore operation for the specified session because a
needed storage pool volume has been varied offline.
User response: Use the VARY ONLINE command to
vary offline storage volumes online, and make them
available to client nodes for file storage.
ANR0566W

platform) - file was deleted from data
storage during retrieval.

for the specified session because the file has been
deleted from data storage by another process before
retrieval is complete.
User response: Contact your administrator to find out
if DELETE FILESPACE, DELETE VOLUME, or
inventory expiration processes are running; these
processes can delete data storage files during retrieval.
Reissue the restore or retrieve operation and specify a
different file version.
ANR0567W
Retrieve or restored failed for session

platform) - insufficient mount points
available to satisfy the request.

sufficient mount points to process the retrieve or
restore operation.
available.
ANR0568W
Session session number for admin admin

name (client platform) terminated connection with client severed.
Explanation: The specified admin session is ended

because the communications link has been closed by a
network error or by the client program.
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
displayed. If a large number of these messages occur
simultaneously, check the network for failure and
ANR0569I
Object not processed for node name:

type=type, file space=filespace name,
object=object name.
Explanation: An error occurred. The object for node

name, identified by type, file space and object name was
not processed.
System action: Server action is defined by the error
that occurred.
User response: Issue QUERY ACTLOG to determine
ANR0570E
Export command: Invalid value for

DURUNITS parameter detected while
exporting administrative schedule
schedule name - default or existing value
is used during import.
Explanation: During processing of command export

command, an invalid value is encountered for the
DURUNITS parameter for administrative schedule
schedule name.
System action: Export processing continues, but the
exported data contains an unknown DURUNITS value
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
113
ANR0571E ANR0576E
schedule and restart the export command. Alternatively,
the export data with the unknown value can be used,
and the DURUNITS value can be checked and updated
after import processing has been performed.
ANR0571E

PERUNITS parameter detected while

PERUNITS parameter for administrative schedule
schedule name.
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.
User response: Update the PERUNITS value for this
use the export data with the unknown value, and check
and update the PERUNITS value after import
processing has been performed.
ANR0572E

DAYOFWEEK parameter detected while

DAYOFWEEK parameter for administrative schedule
schedule name.
exported data contains an unknown DAYOFWEEK
server uses the default or existing DAYOFWEEK value.
User response: Update the DAYOFWEEK value for
this schedule and restart the export command.
Alternatively, use the export data with the unknown
value, and check and update the DAYOFWEEK value
ANR0573I
Export/import command: Processing

administrative schedule schedule name.
Explanation: The background export or import

process to service the command export/import command
is currently processing the schedule definition
information for administrative schedule schedule name.
System action: Export or import processing for the
command continues.
ANR0574E
Explanation: During preview processing of command

import command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for administrative
schedule schedule name.
System action: Processing of the command continues.
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.
User response: If the data is imported with a later
command, verify that the correct values for
DURATION, DURUNITS, PERIOD, and PERUNITS are
used for this schedule.
ANR0575E
Import command: Invalid value for

DAYOFWEEK parameter in exported
data for administrative schedule schedule
name.

schedule name.
imported, the default or existing DAYOFWEEK value is
used.
command, verify that the correct DAYOFWEEK value is
ANR0576E

DURUNITS or PERUNITS parameter in
exported data - administrative schedule
schedule name defined with default
values for DURATION, DURUNITS,
PERIOD, and PERUNITS.
Explanation: During processing of command import

System action: Processing of the command continues,
by using the default values for DURATION,
DURUNITS, PERIOD, and PERUNITS.
User response: Verify that the correct values have
been used for DURATION, DURUNITS, PERIOD, and
PERUNITS. Update these values, if necessary.
114

exported data for administrative
ANR0577E ANR0582E
ANR0577E

data - administrative schedule schedule
name defined with default DAYOFWEEK
value.

schedule name.
by using the default DAYOFWEEK value for this
schedule.
User response: Verify that the correct DAYOFWEEK
value has been used for this schedule. Update this
value, if necessary.
ANR0578E

exported data - existing values for
DURATION, DURUNITS PERIOD, and
PERUNITS for administrative schedule
schedule name were not updated.

by using the existing values for DURATION,
ANR0579E

data - existing DAYOFWEEK value for
administrative schedule schedule name
was not updated.

schedule name.
by using the existing DAYOFWEEK value for this
schedule.
ANR0580E

SPACEMGTECHNIQUE parameter
detected while exporting management
class management class name in domain
domain name, set policy set name - default
or existing value is used during import.

SPACEMGTECHNIQUE parameter for management
class management class name in domain domain name,
policy set policy set name.
exported data contains an unknown
SPACEMGTECHNIQUE value for this management
class. If this data is imported, the default or existing
SPACEMGTECHNIQUE value is used.
User response: Update the SPACEMGTECHNIQUE
value for this copy group and restart the export.
value, and check and update the
SPACEMGTECHNIQUE value after import processing
has been performed.
ANR0581E

MIGREQUIRESBKUP parameter
detected while exporting management
class management class name in domain
domain name, set policy set name - default

MIGREQUIRESBKUP parameter for management class
management class name in domain domain name, policy
set policy set name.
exported data contains an unknown value for this
management class. If this data is imported, the default
or existing MIGREQUIRESBKUP value is used.
User response: Update the MIGREQUIRESBKUP
value for this copy group and restart the export.
value, and check and update the MIGREQUIRESBKUP
value after import processing has been performed.
ANR0582E

SPACEMGTECHNIQUE parameter in
exported data for management class
management class name in domain domain
name, set policy set name.

class management class name, in policy domain domain
name, policy set policy set name.
imported, the default or existing
SPACEMGTECHNIQUE value is used.
User response: None. If the data is imported with a
later command, verify that the correct
115
ANR0583E ANR0588E
SPACEMGTECHNIQUE value is used for this
management class.
ANR0583E

exported data - management class
name, set policy set name defined with
default SPACEMGTECHNIQUE value.
MIGREQUIRESBKUP value is used for this

management class.
ANR0586E

MIGREQUIRESBKUP parameter in
exported data - management class
name, set policy set name defined with
default MIGREQUIRESBKUP value.


management class name, in policy domain domain name,

by using the default SPACEMGTECHNIQUE value for
this management class.

by using the default MIGREQUIRESBKUP value for
User response: Verify that the correct

SPACEMGTECHNIQUE value has been used for this
management class. Update this value, if necessary.

MIGREQUIRESBKUP value has been used for this
ANR0584E

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

by using the existing SPACEMGTECHNIQUE value for
SPACEMGTECHNIQUE value has been used for this
ANR0585E

exported data for management class
name, set policy set name.

management class name, in policy domain domain name,
If a later command causes the data to be imported, the
default or existing MIGREQUIRESBKUP value is used.
ANR0587E

MIGREQUIRESBKUP parameter.
by using the existing MIGREQUIRESBKUP value for
MIGREQUIRESBKUP parameter has been used for this
ANR0588E
Import command: Server is down-level

compared to export data version version
number.
Explanation: An attempt is made to import data to a

down-level server. The server on which the import is
performed must be at the same or later level than the
server from which the data was exported.
System action: The import process ends and server
User response: Import to a server that is at the same
or later level than the server from which the export
was performed.

later command, verify that the correct
116

exported data - MIGREQUIRESBKUP
value for management class management
class name in domain domain name, set
policy set name was not updated.
ANR0589E ANR0596W
ANR0589E
Import command: Preview processing

terminated abnormally - server is
down-level.
Explanation: Processing for the command import

command in preview mode ends when it is determined
that the server is down-level compared to the export
data.
System action: Import processing ends and server
was performed.
ANR0590E
Import command: Processing terminated

abnormally - server is down-level.

command ends when it is determined that the server is
down-level compared to the export data.
was performed.
ANR0591E
Export/import command: Invalid value for

FILELIST parameter - parameter value.
Explanation: The value (parameter value) specified for

the FILELIST parameter in command export/import
command is not a valid value for this parameter.
User response: Reissue the command and specify a
valid FILELIST parameter. For information on valid
values for the FILELIST parameter for the command,
refer to the Administrators Reference for your particular
platform.
ANR0592E

table of contents parameter - parameter
value.

the table of contents (TOC) parameter in command
export/import command is not a valid value for this
parameter.
valid TOC parameter. For information on valid values
for the TOC parameter for the command, refer to the
ANR0593E

NOSPAN parameter - parameter value.

the NOSPAN parameter in command export/import
valid NOSPAN parameter. For information on valid
values for the NOSPAN parameter for the command,
platform.
ANR0594E
device class: NOSPAN parameter can only

be used with a 3590 device class.
Explanation: The device class specified must be a 3590

device class when NOSPAN is set to True.
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.
ANR0595W
The server deleted object count objects

that were part of incomplete groups.
Explanation: After importing data that was exported

from another server, the server deletes any objects that
are part of incomplete groups. Incomplete groups may
be a result of importing from media written by an
export operation that failed. Incomplete groups may
also be a result of a failed import operation.
User response: Ensure that the export and import
operations run to completion. If any errors are
observed, correct them and run again the export or
import or both, as needed.
ANR0596W
Space-managed object object name for

client node node name, filespace filespace
name already exists on the server - it will
be skipped.
Explanation: While attempting to import a

spaced-managed object, the server discovers that the
object already exists. The space-managed object is
skipped.
117
ANR0597W ANR0604I
ANR0597W
IMPORT: Space management attributes

in management class management class
name for domain domain name is not
defined - default management class will
be used.
Explanation: During import processing, the server

finds that the space management attributes for a
space-managed file being imported does not exist in
the active policy set for the domain to which the node
is assigned.
ANR0600I
Export command: No matching policy

domains found for exporting.
Explanation: The background export process does not

find any policy domains that match the specification
entered in the export command.
System action: The export process continues and no
policy domains are exported from the server.
System action: The default management class for the

nodes policy domain is bound to the space-managed
file and import processing continues.
ANR0601I
User response: If you want to define the missing

management class, an authorized administrator may
cancel the import operation, define the missing space
management attributes or management class for the
domain, and process the import operation again.

find any policy sets defined in domains matching
domain name.
ANR0598W
IMPORT: Space management attributes

not found for default management class
in domain domain name - space managed
files bound to management class
management class name in this domain
cannot be imported.

finds that a management class bound to a
space-managed file being imported does not exist in
the active policy set for the domain to which the node
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
not defined for the default management class.
System action: The file is not imported; import
processing continues.
User response: If you want to define the missing copy
group, an authorized administrator may cancel the
import operation, define the missing space
management attributes or management class for the
domain, and process the import operation again.
ANR0599E
Export/import command: Invalid volume

name volume name specified for device
class device class name.
Explanation: One of the volume names specified in

the VOLUMENAMES parameter for an import or
export command is not a valid volume name for the
device class specified in the DEVCLASS parameter.
System action: The export or import command fails.
User response: Specify volume names in the
VOLUMENAMES parameter that are valid for the
device class specified in the DEVCLASS parameter.
118
Export command: No policy sets found in

policy domain domain name for
exporting.

policy sets are exported from the domain.
ANR0602I
Export command: No management classes

were found in policy domain domain
name for exporting.

find any management classes defined in policy
domains matching domain name.
management classes are exported from the domain.
ANR0603I
Export command: No copy groups were

found in policy domain domain name for
exporting.

find any copy groups defined in policy domains
matching domain name.
copy groups are exported from the domain.
ANR0604I
Export command: No schedules were

found in policy domain domain name for
exporting.

find any schedules defined for policy domains
matching domain name.
schedules are exported for the domain.
ANR0605I ANR0614I
ANR0605I
Export command: No schedule

associations were found in policy
domain domain name for exporting.

find any schedule node associations defined for policy
domains matching domain name.
schedule associations are exported for the domain.
ANR0606I
Export command: No node definitions

were found for exporting.

find any node definitions to export as specified in the
command export command.
System action: The export process continues.
ANR0607I
Export command: No administrator

definitions were found for exporting.

find any administrator definitions to export as specified
in the command export command.
ANR0610I
Explanation: A background process has started to

service the command command entered by administrator
administrator name. The background process is defined
as process process ID.
User response: To query the progress of the
background process, use the QUERY PROCESS
command. To cancel the background process, use the
CANCEL PROCESS command. Use the process ID
number to specify this specific process.
ANR0611I
ANR0608I
Export command: No file spaces were

found for exporting.

find any file space definitions to export as specified in
the command export command.
Command started by administrator name as

process process ID has ended.
Explanation: The background process to service the

command command by administrator administrator name
has completed processing.
System action: The specified process ends, and server
ANR0612I


process process ID.
Import command: Reading EXPORT

SERVER data from server server name
exported export date export time.
Explanation: The background import process to

service the command import command is importing
information exported from server server name with the
EXPORT SERVER command on export date at export
time.
System action: Import processing continues.

ANR0613I

ANR0609I
Command started as process process ID.
Explanation: A background process has been started

to service the command command. The background
process is defined as process process ID.

POLICY data from server server name

EXPORT POLICY command on export date at export
time.
ANR0614I

ADMIN data from server server name

119
ANR0615I ANR0622I
EXPORT ADMIN command on export date at export
time.
number of bytes copied, are displayed on the server

console following this message.

ANR0619I
ANR0615I

NODE data from server server name

EXPORT NODE command on export date at export time.
ANR0616I
Export/import command: Preview

processing completed successfully.

in preview (Preview=Yes) mode has completed
successfully.
command completes. Statistics on the projected number
and type of objects moved, together with the projected
total number of bytes copied, are displayed on the
server console following this message.
ANR0617I

completed with status status.

has completed with status status. If the status is
INCOMPLETE, some files have been skipped due to
errors reading or writing the file.
command completes. Statistics on the number and type
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.
Command: Processing canceled before

completion.

command command has been canceled with the
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,
are displayed on the server console following this
message.
ANR0620I
Export/import command: Copied number

domain(s).

copies number policy domain definitions from the
server database to export media or from export media
into the server database. Data is not actually moved if
Preview=Yes is specified in the command export/import
command.
command completes. Server operation continues.
ANR0621I

policy sets.

copies number policy set definitions from the server
database to export media or from export media into the
server database. Data is not actually moved if
command.

ANR0622I
ANR0618I

processing canceled before completion.

in preview (Preview=Yes) mode has been canceled with
the CANCEL PROCESS command.
command ends. Statistics on the projected number and
type of objects moved, together with the projected total
120

management classes.

copies number management class definitions from the
into the server database. Data is not moved if
command.
ANR0623I ANR0630I

ANR0627I
ANR0623I

copy groups.

copies number copy group definitions from either the
command.

schedules.

copies number schedule definitions from either the
command.
ANR0625I

administrators.

copies number administrator definitions from either the
command.
ANR0626I

copies filespace number client file space definitions,
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
actually moved if Preview=Yes is specified in the
command export/import command.

ANR0624I
Export/import command: Copied filespace

number file spaces archive number archive
files, backup number backup files, and
spacemg number space managed files.

node definitions.

copies number client node definitions from the server
database to export media or from export media into the
server database. Data is not moved if Preview=Yes is
specified in the command export/import command.

ANR0629I

bytes of data.

copies number bytes of data from the server database
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
used during export preview processing to estimate the
number of removable media volumes needed to hold
the exported information from the server.
ANR0630I

kilobytes of data.

copies number kilobytes of data from the server
database and data storage to the export media or from
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
volumes needed to hold the exported information from
the server.

121
ANR0631I ANR0637I
ANR0631I

megabytes of data.

copies number megabytes of data from the server
the server.
ANR0632I

gigabytes of data.

copies number gigabytes of data from the server
the server.
ANR0633I

terabytes of data.

copies number terabytes of data from the server
the server.
ANR0634I
Export/import command: Detected number

errors.

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
and data storage.
122

prior to this message to view the error. Use the QUERY
for messages.
ANR0635I
Export/import command: Processing node

node name in domain domain name.

is currently processing the client node definition
information for node node name. The node will be
imported to domain domain name.
command continues.
ANR0636I
Import command: Processing file space

filespace name for node node name as file
space new filespace name.

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
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
space names so that client file copies are not mixed
with existing definitions. Import processing can then
create file spaces with names generated by the import
processor for client nodes that existed prior to the
import operation.
System action: Import processing for the command
continues.
User response: None; however, clients may want to
examine the contents of the file space with the name
new filespace name so that they know where certain file
copies are kept.
ANR0637I
Export/import command: Processing file

space filespace name for node node name
fsId filespace id .

is currently processing client node file space
information for file space filespace name belonging to
client node node name.
command continues.
ANR0638I ANR0645I
ANR0638I

administrator administrator name.

is currently processing the administrator definition
information for administrator administrator name.
command continues.
definition information for management class class name

belonging to policy set set name in policy domain
domain name.
command continues.
ANR0643I

ANR0639I

domain domain name.

is currently processing the policy domain definition
information for domain domain name.
command continues.

archive copy group in domain domain
name, set set name, management class
class name.
Explanation: The background export process to

service the command export/import command is currently
processing the archive copy group definition
information for management class class name belonging
to policy set set name in policy domain domain name.
System action: Export processing for the command
continues.

ANR0644I
ANR0640I
Export/import command: Processing policy

set set name in policy domain domain
name.

is currently processing the policy set definition
information for policy set set name belonging to policy
domain domain name.
command continues.
ANR0641I

management class class name in domain
domain name, set set name.

is currently processing the management class definition
information for management class class name belonging
to policy set set name in policy domain domain name.
command continues.
ANR0642I

backup copy group in domain domain
class name.

is currently processing the backup copy group
Export command: Processing copy group

of unknown type in domain domain
class name.

process to service the command export command is
currently processing copy group definition information
for management class class name belonging to policy set
set name in policy domain domain name. The type of
copy group being processed is unknown.
command continues. The import or export process
assumes that the copy group is a backup copy group.
User response: After policy definitions are imported,
use the QUERY MGMTCLASS and QUERY
COPYGROUP commands to query the server
definitions for management class class name to ensure
that the copy groups defined have the desired
attributes and types. Alternatively, the copy group can
be deleted and defined with the correct type, and then
the export command can be issued again.
ANR0645I

schedule schedule name in domain domain
name.

is currently processing the schedule definition
information for schedule schedule name belonging to
policy domain domain name.
command continues.
123
ANR0646I ANR0652W
ANR0646I
Export/import command: message
ANR0650W

has received the message message from the server.
command continues, but errors may have been
encountered.
User response: Examine the documentation for the
message message and resolve the problem reported.
ANR0647I
Cancel in progress
Explanation: The export or import operation has been

canceled and will end when resources have been freed
for the background process. This message may be
displayed in response to a QUERY PROCESS command
for an export or import operation.
ANR0648I

ANR0649I
Import command: Domain domain name

does not exist - the system will attempt
to import node node name to domain
STANDARD.

processing client node node name. This node was
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.
System action: Import processing continues, but node
node name will be assigned to domain STANDARD
during import unless one of the following conditions
exist:
v Preview=Yes
v Node node name is already registered and
Replacedefs=No
v Domain STANDARD does not exist
User response: If Preview=Yes, consider defining
domain domain name before nodes are actually
imported. Otherwise, domain domain name can be
created after the node is imported and the UPDATE
NODE command can be used to assign the node to
domain domain name.
124

finds that a management class or copy group bound to
an archive file being imported does not exist in the
active policy set for the domain to which the node is
assigned.
nodes policy domain is bound to the archive file and
import processing continues.
cancel the import operation, define the missing
management class or copy group for the domain, and
process the import operation again.
ANR0651W
Have copied the following:
Explanation: The export or import operation has

copied the number and types of objects displayed. This
message may be displayed in response to a QUERY
PROCESS command for an export or import operation.
IMPORT: Archive copygroup copy group

name in management class management
class name for domain domain name is not
defined, default management class will
be used.
IMPORT: Backup copygroup copy group

class name for domain domain name is not
defined, default management class will
be used.

a backup file being imported does not exist in the
assigned.
nodes policy domain is bound to the backup file copy
and import processing continues.
cancel the import operation, define the missing
management class or copy group for the domain, and
process the import operation again.
ANR0652W
IMPORT: Archive copygroup not found

for default management class in domain
domain name - archive files bound to
management class management class name
in this domain cannot be imported.

an archive file being imported does not exist in the
assigned. When trying to rebind the archive file to the
default management class for the domain, the server
finds that an archive copy group is not defined for the
default management class.
ANR0653W ANR0658W
import operation, define the missing management class
or copy group for the domain, and process the import
operation again.
ANR0653W
IMPORT: Backup copygroup not found

for default management class in domain
domain name - backup files bound to
in this domain cannot be imported.

a backup file being imported does not exist in the
assigned. When trying to rebind the backup file to the
default management class for the domain, the server
finds that a backup copy group is not defined for the
default management class.
import operation, define the missing management class
or copy group for the domain, and process the import
operation again.
ANR0654I
Restartable export command with export

identifier exportID started as process
process ID.

service the command command. The background
background server-to-server export process, issue the
QUERY PROCESS or QUERY EXPORT command. To
suspend the process, issue the SUSPEND EXPORT
command. To cancel the background process, issue the
ANR0655W
Command: Retrieve or restore failed - file

was deleted from data storage during
retrieval.

for the specified command because the file has been
System action: The server ends the command and
Reissue the command after these processes have been
completed or canceled.
ANR0656W
Export/import command: Skipped archive

number archive files, backup number
backup files, and spacemg number space
managed files.

skipped 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 actually moved if Preview=Yes is
User response: Check previous messages for the
names of the files that were not exported or imported,
and problem determination information.
ANR0657W
Export command: Invalid authorization

rule type rule type encountered for file
space filespace name fsId filespace id in
node node name - both backup and
archive will be assumed during import.

encounters an invalid file space authorization rule type
for the indicated file space and node.
User response: After import processing is completed,
ask the user of node node name to query the access rules
and ensure that they are specified as desired. The user
should correct any rules that grant access to objects that
the user does not want others to access.
ANR0658W
Export command: The password for

administrator administrator name could
not be obtained. The value 'password
value' will be assumed: The system
administrator may wish to change this
password after importing administrator
administrator name.

command, the export processor cannot obtain the
password for administrator administrator name. The
value password value is assigned as the password for the
administrator on the export media.
User response: After the administrative definition has
been imported to another server, an authorized
administrator should use the UPDATE ADMIN
command to set a password for the administrator
administrator name.
125
ANR0659W ANR0665W
ANR0659W
Export command: The password for node

node name could not be obtained. The
value 'password value' will be assumed:
The system administrator may wish to
change this password after importing
node node name.

command, the export processor cannot obtain the
password for client node node name. The value password
value is assigned as the password for the client node on
the export media.
User response: After the client node definition has
been imported to another server, an authorized
administrator should use the UPDATE NODE
command to set a password for the node node name.
ANR0660E
Command: Insufficient memory available

in accessing data storage.
Explanation: The server encounters a memory

shortage in accessing data storage during command
command operation.
System action: The command command operation ends
application.
ANR0661E
Command: Internal error encountered in

accessing data storage.
Explanation: The server encounters an internal error

in accessing data storage while processing command
command operation.
System action: The command command operation is
ended and server operation continues.
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 failure can be
found and resolved, reissue the command command
operation. If the failure cannot be found, contact your
service representative for assistance in resolving the
problem.
ANR0662E
Command: Output error encountered in

Explanation: The command command operation ends

because an error has been encountered by the server in
writing to a device. Possible reasons include:

preceding this one to determine the cause of the error.
After the problem is corrected, the command can be
retried.
ANR0663E

command command operation failed because data
external event.
interrupted. Reissue the command command after the
problem is resolved.
ANR0664E
Export/import command: Media not

accessible in accessing data storage.
Explanation: The server ends a transaction for an

export or import operation because storage volumes are
not available in the storage pools in which the client
files are to be stored.
System action: The server ends the export or import
operation and server operation continues.
make them available for file storage.
ANR0665W
Import command: Transaction failed storage pool pool name is not defined.
Explanation: The server rolls back a database update

transaction for an import operation because the
destination specified for a management class copy
group specifies the named storage pool, but that
storage pool does not exist.
System action: The import operation is ended and
User response: An administrator with policy authority
over the client policy domain must correct management
class definitions so that copy group destinations refer
to defined storage pools, or the specified storage pool
must be created by an authorized administrator.
v I/O error writing to a device

v No storage space.
v Incompatible storage pool data format.
126
Command: Data transfer was interrupted

ANR0666W ANR0672W
ANR0666W
Import command: Transaction failed object excluded by size in storage pool

pool name and all successor pools.

transaction for an import operation because the size of
an imported file is larger than that allowed in the
storage pool specified in the bound management class
copy group for the file. No successor storage pools to
the one specified on the copy group can accept the
large file.
User response: The maximum file size for one or more
of the storage pools in the storage hierarchy can be
increased to accommodate the file. An authorized
administrator can increase the MAXSIZE parameter by
issuing the UPDATE STGPOOL command.
Alternatively, the appropriate copygroup definition can
be updated so that a different destination storage pool
is specified.
ANR0667W
Import command: Transaction failed - no

space available in storage pool pool name
and all successor pools.
Explanation: The server ends an import operation

because the storage pool specified in a management
class copy group does not contain enough free space to
hold the files being imported. Successor storage pools
to the one specified on the copy group do not contain
enough free space.
ANR0669W

an export or import operation failed because data
external event.
System action: The export or import operation is
interrupted. Attempt the export/import operation again
after problem is resolved.
ANR0670W
ANR0668W
Export/import command: Transaction failed

- error on output storage device.

- storage media inaccessible.

export or import operation because storage volumes are
not available in the storage pools in which the client
files are to be stored.
ANR0671W

or more storage pools in the storage hierarchy.

- data transfer interrupted.

- sufficient recovery log space is not
available.

transaction for an export or import operation because
sufficient log space is not available on the server.
Explanation: The server ends an export or import

operation for the specified session because an I/O error
has been encountered by the server in writing to a
device.

for use by the log, and the EXTEND LOG command to
extend the size of the log so that the new volumes are
used.

ANR0672W

to be shut down by using the HALT command to
correct the hardware problem. After the problem is
corrected, the client may be able to try the operation
again.

- sufficient database space is not
available.

transaction for an export or import operation because
sufficient database space is not available on the server.
127
ANR0673W ANR0681E
for use by the database, and the EXTEND DB
volumes are used.
ANR0673W
Export/import command: Data storage

retrieve or restore failed - error detected.
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:
ANR0676E
EXPORT/IMPORT: Invalid
Communications Buffer State in SEND.
Explanation: The server export/import process

encounters a communications error in transferring
information to or from the server.
System action: The export or import process ends and

ANR0677E

operation and continues operation.
restore or retrieve again. You can also refer to the
Problem Determination Guide for problem determination
hints and information. If retry of the operation
continues to fail contact your service representative.
ANR0674W
Export command: Retrieve failed - error

on input storage device.
Explanation: The server ends an export operation for

the specified session because an I/O error has been
encountered by the server in reading from a device.
The object for which the I/O was issued is reported in
a later message.
System action: Export processing skips this file, and
to be shut down with the HALT command to correct
the hardware problem.

encounters a communications error in transferring
ANR0678E
EXPORT/IMPORT: Error starting the

Export/Import Session.
Explanation: The server export/import process is not

able to start the session to export information from the
server or import information into the server.

ANR0679E
EXPORT/IMPORT: Communications
Failure in Receiving "verb type" verb.

encounters a communications error in using the verb
type verb to transfer information to or from the server.
EXPORT/IMPORT: Authentication
Failure.

encounters an authentication error in transferring

application.
128
Failure in Sending "verb type" verb.

type verb to transfer information to or from the server.
ANR0681E
ANR0675E
EXPORT/IMPORT: Invalid
Communications Buffer State in
RECEIVE.
ANR0682E ANR0690E
ANR0682E
Failure in Sending "verb type" verb
(command).
ANR0687E
Export/import command: Transaction

failure - could not commit database
transaction.

type verb to issue command command.
Explanation: During processing of command

export/import command, a database transaction cannot be
committed to the server database.

System action: Processing of the command ends.

ANR0683E
EXPORT/IMPORT: Receive Buffer

overflow.

encounters an overflow error in transferring

representative.
ANR0688E

failure - commit called when no
transaction started.

started in the server database.
ANR0684E
failure: bad verb received (verb type).
Explanation: The server encounters an invalid

communications verb during export or import
processing and is not able to continue processing.
ANR0685E
ANR0689W
EXPORT/IMPORT: Internal error:

Invalid table output handle detected.

encounters an internal error in transferring information
to or from the server.
ANR0686E

representative.

failure - could not start database
transaction.

started in the server database.
System action: Processing of the command terminates.
representative.
Import command: Client platform type

(platform type) for imported node node
name conflicts with an existing node
with the same name - the node will not
be imported.

encounters an imported node definition that has the
same name as an existing node, but has a different
client platform type (for example, OS/2 or AIX).
Because file data may not be compatible across
different client platforms, the node is not imported.
System action: Import processing continues, and the
named node is skipped by import processing.
User response: If you want to import the named
node, cancel the import process, rename the existing
node to a new name by using the RENAME NODE
command, and run the import again. After you have
imported the node, use the RENAME NODE command
to set the node names as you desire.
ANR0690E

failure - server aborted the transaction
(abort code).

129
ANR0691E ANR0697E
committed in the server database. The reason code abort
code is returned.
representative.
ANR0691E
Export command: Error abort code writing

export data.

command, an input/output error occurs when writing
the exported information to the export media.
ANR0694E

command, an invalid record type is detected when
reading the exported information from the export
media.
representative.
ANR0695E

representative.
ANR0692E
Command: Out of space on sequential

media, scratch media could not be
mounted.
Explanation: During command command processing,

the process encounters an out-of-space condition
writing to the sequential media. Command command
ends when there is no more space on the sequential
media for storing data and SCRATCH=NO has been
specified on command command.
System action: Command command processing ends.
Server processing continues.
User response: Reissue the command and specify
SCRATCH=YES or specify additional volume names on
the command.
ANR0693E
Import command: Error abort code reading

export data.

command, an input/output error occurs when reading
the exported information from the export media.
representative.
130
Import command: Invalid record format

(format code) detected on import.
Export command: Unexpected error error

code encountered in receiving table
output data.

command, an unexpected error is detected.
representative.
ANR0696E
Export command: Output table error

encountered - 0 columns reported in the
table.

representative.
ANR0697E
Export command: Output table error

encountered - not positioned to the first
column in the table.

representative.
ANR0698E ANR0708E
ANR0698E

FILEDATA parameter - parameter value.

the FILEDATA parameter in command export/import
valid FILEDATA parameter. For information on valid
values for the FILEDATA parameter for the command,
platform.
ANR0699E
Export/import command: Device class

DISK cannot be specified for this
command.
Explanation: The DEVCLASS value DISK cannot be

specified for the command export/import command.
valid device class. Issue the QUERY DEVCLASS
command for a list of valid device classes for the
server.
ANR0700E

PREVIEW parameter - parameter value.

the PREVIEW parameter in command export/import
valid PREVIEW parameter. For information on valid
values for the PREVIEW parameter for the command,
platform.
ANR0701E

SCRATCH parameter - parameter value.
ANR0705E
Export command: The VOLUMENAMES

parameter must be specified when
SCRATCH=NO is specified.
Explanation: The SCRATCH parameter is specified as

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
that can be used for the command.
valid VOLUMENAMES parameter. For information on
valid parameter values for the command, refer to the
ANR0706E
Export command: A device class must be

specified unless PREVIEW=YES is
specified.
Explanation: The DEVCLASS parameter is not

specified in the command export command. Unless
PREVIEW=YES is specified, a DEVCLASS value must
be specified.
server.
ANR0707E
Export command: The FILESPACE

parameter cannot be specified.
Explanation: The FILESPACE parameter is specified

for the command export command, but the FILEDATA
parameter is specified as NONE, or is not specified and
defaults to NONE. File spaces are only copied if the
FILEDATA parameter is specified with a value other
than NONE.

the SCRATCH parameter in command export/import

parameter values for the command, refer to the

ANR0708E

valid SCRATCH parameter. For information on valid
values for the SCRATCH parameter for the command,
platform.
Import command: The FILESPACE

parameter cannot be specified unless the
FILEDATA parameter specifies that files
should be imported.
Explanation: The FILESPACE parameter is specified

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
131
ANR0709E ANR0716E
FILEDATA parameter is specified with a value other
than NONE.
parameter values for the command, refer to the
ANR0709E
Command: No matching nodes registered

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.
valid combination of node and domain names. Use the
QUERY NODE command to view the names of nodes
in the domains that you are interested in exporting.
ANR0710E
Command: Unable to start background

process.

valid DATES parameter. For information on valid
values for the DATES parameter for the command,
platform.
ANR0713E

REPLACEDEFS parameter - parameter
value.

the REPLACEDEFS parameter in command import
valid REPLACEDEFS parameter. For information on
valid values for the REPLACEDEFS parameter for the
command, refer to the Administrators Reference for your
particular platform.
ANR0714E
Import command: The EXTFILE device

class cannot be specified when the
VOLUMENAMES parameter is
specified.
Explanation: The server command processor is not

able to start a background process to perform the
command command.
Explanation: An invalid combination of parameters

has been entered for command import command. The
EXTFILE device class cannot be used in combination
with the VOLUMENAMES parameter.
System action: The command process ends and server



application.
User response: Reissue the command with the correct

syntax.
ANR0715E
ANR0711E
Import command: Unable to start import

process.
Import command: A device class must be

specified.
Explanation: The server import command processor is

not able to start a background process to perform the
import operation.
Explanation: The command import command has been

specified, but does not include specification of the
DEVCLASS parameter. The DEVCLASS parameter
must be specified for this command.



application.

valid device class. For a list of valid device classes for
the server, issue the QUERY DEVCLASS command.
ANR0712E

DATES parameter - parameter value.
ANR0716E
Import command: Invalid export data

detected.

the DATES parameter in command import command is
not a valid value for this parameter.
Explanation: The command import command

encounters invalid data on the export media while
trying to import server information.


132
ANR0717E ANR0723E
User response: Ensure that the mounted export tapes
are in the correct order (mounted in the same order as
they were mounted during export). Reissue the
command, and mount the tapes in the correct order. If
the VOLUMENAMES parameter has been specified,
make sure that the volume names in the command are
specified in the correct order.
ANR0717E

processing terminated abnormally communications send or receive failed.
Explanation: Processing for the command export/import

command in preview mode has been terminated when
an internal communications error is encountered in the
server.
System action: Export/import processing is ended
representative.
ANR0718E

terminated abnormally communications send or receive failed.

command ends when an internal communications error
is encountered in the server.
representative.
ANR0719E

processing terminated abnormally insufficient memory.

command in preview mode is ended because sufficient
application.
ANR0720E
command: Processing terminated

abnormally - insufficient memory.
Explanation: Processing for the command ends

because sufficient memory is not available on the
server.
System action: Command processing is ended and
application.
ANR0721E

processing terminated abnormally unexpected verb received from server.

command in preview mode ends when an internal
communications error is encountered in the server.
System action: Export/import processing ends and
representative.
ANR0722E

terminated abnormally - unexpected
verb received from server.

command ends when an internal communications error
representative.
ANR0723E

processing terminated abnormally transaction failure.

command in preview mode ends when a database
transaction error is encountered in the server.
133
ANR0724E ANR0730E
representative.
ANR0724E

terminated abnormally - transaction
failure.
command in preview mode ends when an internal error


command ends when a database transaction error is
encountered in the server.

representative.

ANR0728E

representative.
ANR0725E

processing terminated abnormally authentication failure.

command in preview mode ends when an authentication
error is encountered in the server.

terminated abnormally - internal error.

command ends when an internal error is encountered in
the server.
representative.

ANR0729E

representative.
Explanation: During processing of the command

import command, an internal syntax error is encountered
in the server.
ANR0726E

terminated abnormally - authentication
failure.

command ends when an authentication error is
Import command: Syntax error from

command 'server command'.
System action: Import processing continues, but the

indicated command will have no effect.
activity log and search for messages. After import
processing is complete, it may be necessary to issue
additional commands manually to obtain the necessary
definitions.

ANR0730E

representative.

command ends when an internal command error is
ANR0727E

processing terminated abnormally internal error.
134
Import command: Internal error from

command 'server command'.

representative.
ANR0731E ANR0738E
ANR0731E

COMPRESSION parameter in exported
data for node node name.

COMPRESSION parameter for node node name.
default or existing COMPRESSION value is used.
later command, verify that the correct COMPRESSION
value is used for this node.
ANR0732E

ARCHDELETE parameter in exported

ARCHDELETE parameter for node node name.
default or existing ARCHDELETE value is used.
later command, verify that the correct ARCHDELETE
ANR0733E

BACKDELETE parameter in exported

BACKDELETE parameter for node node name.
default or existing BACKDELETE value is used.
later command, verify that the correct BACKDELETE
ANR0734E

data - node node name registered with
default COMPRESSION value.

by using the default COMPRESSION value for this
node.
User response: Verify that the correct COMPRESSION
value has been used for this node. Update this value, if
necessary.
ANR0735E

default ARCHDELETE value.

by using the default ARCHDELETE value for this node.
User response: Verify that the correct ARCHDELETE
necessary.
ANR0736E

default BACKDELETE value.

by using the default BACKDELETE value for this node.
User response: Verify that the correct BACKDELETE
necessary.
ANR0737E

data - existing COMPRESSION value
for node node name was not updated.

by using the existing COMPRESSION value for this
node.
User response: Verify that the correct COMPRESSION
necessary.
ANR0738E

data - existing ARCHDELETE value for
node node name was not updated.

by using the existing ARCHDELETE value for this
node.
User response: Verify that the correct ARCHDELETE
135
ANR0739E ANR0744E
necessary.
ANR0739E

data - existing BACKDELETE value for
node node name was not updated.

by using the existing BACKDELETE value for this
node.
User response: Verify that the correct BACKDELETE
necessary.
ANR0740E
Import command: Invalid value for TYPE

parameter in exported data for copy
group copy group name in domain domain
name, set policy set name, management
class management class name - backup is
assumed.

command, an invalid value is encountered for the TYPE
parameter for copy group copy group, in policy domain
domain name, policy set policy set name, management
class management class name.
Based upon other copy group parameters, a copy group
type of backup is assigned.
User response: Verify that the assigned TYPE value of
backup for this copy group is correct.
ANR0741E

class management class name - archive is
assumed.

Based upon other copy group parameters, a copy group
type of archive is assigned.
User response: Verify that the assigned TYPE value of
archive for this copy group is correct.
136
ANR0742E

class management class name - this copy
group will not be imported.

However, this copy group is not imported because a
TYPE value cannot be assigned.
User response: Manually define this copy group, if
necessary.
ANR0743E

MODE parameter in exported data for
archive copy group copy group name in
domain domain name, set policy set name,
management class management class name.

MODE parameter for archive copy group copy group
name, in policy domain domain name, policy set policy set
name, management class management class name.
default or existing MODE value is used.
later command, verify that the correct MODE value is
used for this archive copy group.
ANR0744E

MODE parameter in exported data for
backup copy group copy group name in

MODE parameter for backup copy group copy group
default or existing MODE value is used.
later command, verify that the correct MODE value is
used for this backup copy group.
ANR0745E ANR0750E
ANR0745E

SERIALIZATION parameter in exported
data for archive copy group copy group
name in domain domain name, set policy
set name, management class management
class name.

SERIALIZATION parameter for archive copy group
copy group name, in policy domain domain name, policy
set policy set name, management class management class
name.
default or existing SERIALIZATION value is used.
later command, verify that the correct SERIALIZATION
value is used for this archive copy group.
ANR0748E

by using the default MODE value for this backup copy
group.
User response: Verify that the correct MODE value
has been used for this copy group. Update this value, if
necessary.
ANR0749E
ANR0746E

MODE parameter in exported data backup copy group copy group name in
defined with default MODE value.

data for backup copy group copy group
class name.

data - archive copy group copy group
class name defined with default
SERIALIZATION value.

SERIALIZATION parameter for backup copy group
name.

name.


by using the default SERIALIZATION value for this
archive copy group.

later command, verify that the correct SERIALIZATION
value is used for this backup copy group.

SERIALIZATION value has been used for this copy
group. Update this value, if necessary.
ANR0747E

MODE parameter in exported data archive copy group copy group name in
defined with default MODE value.

by using the default MODE value for this archive copy
group.
necessary.
ANR0750E

data - backup copy group copy group
class name defined with default
SERIALIZATION value.

name.
by using the default SERIALIZATION value for this
backup copy group.
137
ANR0751E ANR0756E
ANR0751E

MODE parameter in exported data existing MODE value for archive copy
class management class name was not
updated.

by using the existing MODE value for this archive copy
group.
necessary.
ANR0752E

MODE parameter in exported data existing MODE value for backup copy
class management class name was not
updated.

by using the existing MODE value for this backup copy
group.
necessary.
ANR0753E

data - existing SERIALIZATION value
for archive copy group copy group name
in domain domain name, set policy set
name, management class management class
name was not updated.

name.
138
by using the existing SERIALIZATION value for this

archive copy group.
ANR0754E

data - existing SERIALIZATION value
for backup copy group copy group name
in domain domain name, set policy set
name, management class management class

name.
by using the existing SERIALIZATION value for this
backup copy group.
ANR0755E

ACTION parameter in exported data for
name.

ACTION parameter for schedule schedule name in policy
domain domain name.
default or existing ACTION value is used.
command, verify that the correct ACTION value is
ANR0756E

exported data for schedule schedule name
in domain domain name.

DURUNITS or PERUNITS parameter for schedule
schedule name in policy domain domain name.
default or existing values are used for DURATION,
ANR0757E ANR0763E
command, verify that the correct values for
DURATION, DURUNITS, PERIOD, and PERUNITS are
ANR0757E

data for schedule schedule name in
domain domain name.

DAYOFWEEK parameter for schedule schedule name in
default or existing DAYOFWEEK value is used.
command, verify that the correct DAYOFWEEK value is
ANR0758E

ACTION parameter in exported data schedule schedule name in domain domain
name defined with default ACTION
value.

domain domain name.
by using the default ACTION value for this schedule.
User response: Verify that the correct ACTION value
has been used for this schedule. Update this value, if
necessary.
ANR0759E

exported data - schedule schedule name in
domain domain name defined with
default values for DURATION,

by using the default values for DURATION,
ANR0760E

data - schedule schedule name in domain
domain name defined with default
DAYOFWEEK value.

by using the default DAYOFWEEK value for this
schedule.
ANR0761E

ACTION parameter in exported data existing ACTION value for schedule
schedule name in domain domain name was
not updated.

domain domain name.
by using the existing ACTION value for this schedule.
User response: Verify that the correct ACTION value
has been used for this schedule. Update this value, if
necessary.
ANR0762E

exported data - existing values for
DURATION, DURUNITS PERIOD, and
PERUNITS for schedule schedule name in
domain domain name were not updated.

by using the existing values for DURATION,
ANR0763E

data - existing DAYOFWEEK value for

139
ANR0764E ANR0769E
command. Alternatively, use the export data with the

unknown value, and the system will attempt to assign
a TYPE during import processing.

by using the existing DAYOFWEEK value for this
schedule.
ANR0767E

ANR0764E
Import command: Invalid lock status

detected while importing node node
name - this node will not be locked.

command, an invalid value is encountered for the lock
status for node node name.
but the node is not locked.
User response: An administrator with the proper
authorization must issue the LOCK NODE command, if
necessary.
ANR0765E
Import command: Invalid lock status

detected while importing administrator
administrator name - this administrator
will not be locked.

MODE parameter for copy group copy group name in
domain domain name, policy set policy set name,
exported data contains an unknown MODE value for
this copy group. If this data is imported, the default or
existing MODE value is used.
User response: Update the MODE value for this copy
group and restart the export command. Alternatively,
and update the MODE value after import processing
has been performed.
ANR0768E

status for administrator administrator name.
but the administrator is not locked.
authorization must issue the LOCK ADMIN command,
if necessary.
ANR0766E
Export command: Invalid value for TYPE

parameter detected while exporting copy
class management class name - system will
attempt to assign value during import.

parameter for copy group copy group name, in domain

MODE parameter detected while
exporting copy group copy group name in
- default or existing value is used
during import.

SERIALIZATION parameter detected
while exporting copy group copy group
class name - default or existing value is
used during import.

SERIALIZATION parameter for copy group copy group
name, in domain domain name, policy set policy set name,
exported data contains an unknown SERIALIZATION
value for this copy group. If this data is imported, the
User response: Update the SERIALIZATION value for
this copy group and restart the export command.
value, and check and update the SERIALIZATION
value after import processing has been performed.
ACTION parameter detected while
exporting schedule schedule name in
domain domain name - default or existing
value is used during import.

exported data contains an unknown TYPE value for
this copy group. If this data is imported, the system
attempts to assign a TYPE value based upon values for
other copy group parameters.
ANR0769E
User response: Delete and define this copy group to

eliminate the invalid data, and then restart the export

140
ANR0770E ANR0774E
ACTION parameter for schedule schedule name in
domain domain name.
exported data will contain an unknown ACTION value
for this schedule. If this data is imported, the default or
existing ACTION value is used.
User response: Update the ACTION value for this
and update the ACTION value after import processing
has been performed.
ANR0770E

DURUNITS parameter detected while

domain domain name.
exported data contains an unknown DAYOFWEEK
default or existing DAYOFWEEK value is used.
User response: Update the DAYOFWEEK value for
value, and check and update the DAYOFWEEK value
ANR0773E
Export command: Invalid lock status

detected while exporting administrator
administrator name - this administrator
will not be locked during import.

DURUNITS parameter for schedule schedule name in
domain domain name.

status for administrator administrator name.

exported data contains an unknown DURUNITS value
for this schedule. If this data is imported, the default or
existing DURUNITS value is used.

exported data contains an unknown lock status for this
administrator. If this data is imported, the
administrator will not be locked.
User response: Update the DURUNITS value for this

and update the DURUNITS value after import

authorization must issue the LOCK NODE or
UNLOCK NODE command to achieve the desired lock
status, and then restart the export command.
status, and issue a LOCK ADMIN or UNLOCK
ADMIN command after import processing has been
performed.
ANR0771E

PERUNITS parameter detected while

PERUNITS parameter for schedule schedule name in
domain domain name.
exported data will contain an unknown PERUNITS
default or existing PERUNITS value is used.
User response: Update the PERUNITS value for this
and update the PERUNITS value after import
ANR0772E
ANR0774E

COMPRESSION parameter detected
while exporting node node name - default

exported data contains an unknown COMPRESSION
value for this node. If this data is imported, the default
or existing COMPRESSION value is used.
User response: Update the COMPRESSION parameter
for this node and restart the export command.
value, and check and update the COMPRESSION value

DAYOFWEEK parameter detected while
141
ANR0775E ANR0782E
ANR0775E
Export command: Invalid lock status

detected while exporting node node name
- this node will not be locked during
import.

status for node node name.
exported data contains an unknown lock status for this
node. If this data is imported, the node will not be
locked.
User response: Lock or unlock the node to achieve the
desired lock status, and then restart the export
command. Alternatively, use the export data with the
unknown status, and lock or unlock the node after
import processing has been performed.
ANR0776E

ARCHDELETE parameter detected
while exporting node node name - default

exported data contains an unknown ARCHDELETE
or existing ARCHDELETE value is used.
User response: Update the ARCHDELETE parameter
value, and check and update the ARCHDELETE value
ANR0777E

BACKDELETE parameter detected while
exporting node node - default or existing

exported data contains an unknown BACKDELETE
or existing BACKDELETE value is used.
User response: Update the BACKDELETE parameter
value, and check and update the BACKDELETE value
ANR0778E
Command: Error encountered in accessing

data storage - device class device class
name is not defined.

an error occurred because the specified device class is
not defined.
System action: The command command is ended and
User response: Make sure the specified device class is
defined.
ANR0779E

data storage - disk volume specified.

an error occurred because a specified volume is a disk
volume rather than a tape volume.
User response: Make sure that all volumes specified
for the command command are tape volumes.
ANR0780E
Export/import command: Process aborted a server communications session could

not be established.

encounters an internal error in establishing an
intermemory communications session with other server
components.
application.
If the error is not resolved, contact your service
representative.
ANR0781E
Export/import command: Process aborted server sign on failed.

encounters an internal error in establishing an
intermemory communications session with other server
components.
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
142
ANR0783E ANR0789E
with the data storage services.
representative.
ANR0783E
Export/import command: Process aborted a server data storage Export/Import

stream could not be established (rc
return code).

encounters an internal error in establishing a session
with the data storage services.
representative.
ANR0784E
Export/import command: Process aborted internal error detected with the

Export/Import level: level number.

encounters an internal error in evaluating the
export/import level (SERVER, NODE, ADMIN,
POLICY).
representative.
ANR0785E
Import command: Invalid record type

xrecord type read from export data.

representative.
ANR0786E
Import command: Invalid export version

version number in exported data.
Explanation: The server import process encounters an

internal error in reading data from the export media.
An invalid export version number (version number) is
encountered during the read operation.
representative.
ANR0787E
Import command: Import of file space

filespace name in node node name aborted
by server (abort reason).

internal error in importing file space filespace name for
client node node name. The reason code abort reason is
encountered.
representative.
ANR0788E
Import command: Error error code during

import of data storage data.

internal data storage error. The error code error code is
encountered.

encounters an internal error in reading data from the
export media. An invalid record type of record type is
encountered during the read operation.

representative.

ANR0789E

Import command: Failure in normalizing

transaction identifier for sending to the
server.
143
ANR0790E ANR0795E
internal database transaction error in importing
information into the server database.
representative.
ANR0790E
Import command: Error in absorbing data

records.

internal error in importing information into the server
database.
representative.
Because the imported information for the rule is

ambiguous, the server assumes that the rule is for
backup data.
System action: The import process continues.
User response: The user for node node name should
query the access rules for the specified node name after
the import process has completed, and correct or delete
any access rules that are in error or not needed.
ANR0793E

in accessing data storage while executing an import or
export preview operation.
cause of the data storage failure. If you find and
resolve the error, retry the export or import operation.
If you cannot find the error, contact your service
representative for assistance in resolving the problem.
ANR0794E
ANR0791E
Export/import command: Protocol error verb "verb type" with length verb length
received, expected "expected type".
Explanation: The server export or import process

encounters an internal protocol error in exporting
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.
representative.
ANR0792E
Import command: Invalid copy type

encountered in an imported file space
authorization rule for node node name,
file space filespace name - a type of
BACKUP will be assumed.
Explanation: During import processing for command

import command, an invalid copy type is encountered
for an authorization rule that grants access for file
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.
144

processing terminated abnormally error accessing data storage.

terminated abnormally - error accessing
data storage.

export operation.
cause of the data storage failure. If the import or export
operation involves a session with another server, run
the QUERY ACTLOG command to examine messages
on the other server as well. Messages on the other
server can help you troubleshoot the error on the local
server. If you find and resolve the error, retry the
export or import operation. If you cannot find the error,
contact your service representative for assistance in
resolving the problem.
ANR0795E

data storage - invalid volume name
specified.
Explanation: The server encounters an error in

accessing data storage while processing command
command. The error occurred because an attempt has
been made to access a volume with an invalid name.
ANR0796E ANR0803I
User response: Issue the command with a valid
volume name.
ANR0796E

data storage - insufficient number of
mount points available for removable
media.

the server cannot allocate sufficient mount points.
available.
ANR0797E

data storage - required volume was not
mounted.
Explanation: During command command processing, a

required volume cannot be mounted. The mount
request may have been canceled.
User response: Issue the command again and make
sure the necessary volumes are accessible.
ANR0798E
Import command: Error encountered in

accessing data storage - volume cannot
be used.
Explanation: During import processing, a volume has

been mounted but cannot be used.
User response: Query the activity log for messages
preceding this one that give additional information.
Make sure a usable volume is specified and mounted.
ANR0799E

data storage - volume already in use.

volume cannot be used because it is already defined in
a storage pool, or has been previously used by an
export, database dump, or database backup operation
(as recorded in the volume history) or is in use by
another process.
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
volume history information. Use the QUERY VOLUME
command to display the names of volumes that are
defined to server storage pools. Use the QUERY

VOLHISTORY command to display the names of
volumes that have been used for export, database
dump, or database backup operations.
ANR0800I
Command command for node node name

started as process process ID.
Explanation: A file space deletion process has started

to delete one or more file spaces for the specified node.
The process is assigned the ID specified in the message.
System action: The server starts a background process
to perform the operation in response to the DELETE
FILESPACE command entered by an administrator.
User response: To obtain status on the file space
deletion process, issue the QUERY PROCESS command.
The process may be canceled with the CANCEL
PROCESS command.
ANR0801I

node node name started as process process
ID.
Explanation: The specified client node has started a

file space deletion process (on the server) to delete one
or more file spaces. The process has been assigned the
ID specified in the message.
to perform the operation in response to a request from
the client node.
The process may be canceled by an authorized
administrator using the CANCEL PROCESS command.
ANR0802I
DELETE FILESPACE filespace name

(backup/archive data) for node node name
started.
Explanation: A background server process has started

(on the server) to delete the specified file space
belonging to the node indicated. If a file space name is
not included in the message, all file spaces belonging to
the node are deleted.
System action: The background process deletes
backup and archive objects for the specified file space
while server operation continues.
ANR0803I

(backup data) for node node name
started.
145
ANR0804I ANR0813I
(on the server) to delete backup objects in the specified
file space belonging to the node indicated. If a file
space name is not included in the message, then the
backup objects for all file spaces that belong to the
node are deleted.
backup objects for the specified file space while server
ANR0804I

(archive data) for node node name started.

(on the server) to delete archive objects in the specified
file space belonging to the node indicated. If a file
space name is not included in the message, then the
archive objects for all file spaces that belong to the
node are deleted.
ANR0811I
Explanation: The server has started roll-off processing

to remove expired client backup and archive file copies,
based on the management class policy that is bound to
the files. The copy group retention and version
parameters for each files copy group are used by the
server to determine if copies are to be deleted from the
server. The expiration process was started as process
number process ID, and may be queried or canceled
with the QUERY PROCESS or CANCEL PROCESS
commands, respectively.
System action: The expiration process is now
cancellable. Server operation continues.
ANR0812I

archive objects for the specified file space while server
ANR0805I

canceled for node node name: number of
objects objects deleted.
Explanation: A background server process that has

been deleting file space data for the indicated node is
canceled by the CANCEL PROCESS command. The
number of objects deleted before the cancel ended the
operation are reported in the message.
System action: The server process is ended and server
User response: No action is required. An authorized
administrator can issue the DELETE FILESPACE
command to delete remaining objects in the file space.
ANR0806I

complete for node node name: number of
objects objects deleted.

ID completed: processed number of nodes
nodes, examined number of objects
objects, deleting number of backup objects
backup objects, number of archive objects
archive objects, number of DB backup
volumes DB backup volumes, and number
of recovery plan files recovery plan files.
retry count objects were retried and error
count errors were encountered.
Explanation: Server roll-off processing has completed.

The number of client objects examined and deleted,
based on management class policy, are displayed in the
message. A total error count is also displayed. The
number of DB backup volumes deleted is based on the
value specified on the SET
DRMDBBACKUPEXPIREDAYS. The number of
recovery plan files deleted is based on the value
specified on the SET DRMRPFEXPIREDAYS. Server
roll-off processing deletes the DB backup volumes and
recovery plan files only if DRM is licensed on the
server and the volumes or plan files are created on the
server to server virtual volumes.
System action: The roll-off process is ended and
User response: If the error count is not equal to 0,
examine messages that may have been issued in the
activity log to determine the cause for the errors.
ANR0813I
Explanation: A server process deleting file space data

for the node specified has completed. The total number
of objects deleted is reported in the message.
146
Inventory client file expiration started as

process process ID.

ID canceled prior to completion:
processed number of nodes nodes,
examined number of objects objects,
deleting number of backup objects backup
objects, number of archive objects archive
objects, number of DB backup volumes DB
backup volumes, and number of recovery
plan files recovery plan files. retry count
objects were retried and error count
errors were encountered.
ANR0814I ANR0820I
Explanation: The inventory file expiration process was
canceled by an administrator. The number of objects
examined and deleted prior to the cancelation are
reported. A total error count is also displayed.
System action: The server ends the file expiration
process.
If the server is low on memory, do the following:

See the documentation for the operating system about
how to increase memory for an application.
ANR0816I

ANR0814I
volumes to the server log and extend the log size.
Expiration retry retry number of maximum

retries in number of seconds seconds.
Explanation: Server roll-off processing has

encountered an error in attempting to remove expired
client file copies from the server database. The
operation will be tried again in the number of seconds
indicated.
System action: The server waits for the number of
seconds indicated and retries the file expiration
operation.
User response: Expiration retry processing occurs
when the server database is full, the log is full, or
sufficient server memory is not available to continue
processing. Use the QUERY ACTLOG command to look
for messages issued prior to this one that indicate the
type of error encountered.
If the server is out of 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
Expiration retry was successful.
Explanation: In accordance with management class

policy, server roll-off processing has been successful in
retrying a client file expiration.
System action: Server roll-off processing continues.
ANR0818I
Waiting to retry expiration because of

insufficient resources.
Explanation: The server inventory expiration process

is waiting to retry expiration processing that failed
because of insufficient memory, database, or log
resources on the server.
System action: Server operation continues. The
expiration processing is reattempted automatically.
examine messages issued prior to this one, which
indicated the resource that is not available to the
expiration process. Correct the shortage.
ANR0819I
Cancel in progress
Explanation: This message is displayed in response to

a QUERY PROCESS command, and indicates that an
inventory expiration process has been canceled. The
process will end shortly.

System action: The expiration process terminates and



ANR0820I
ANR0815I
Expiration retry in progress.
Sorting information for number objects

has been deleted.
Explanation: The server is retrying an operation

during client file roll-off processing. Expiration retry
processing occurs when the server database is full, the
log is full, or sufficient server memory is not available
to continue processing.
Explanation: A background server process has deleted

sorting information for number files from the server
database. This process is started during initialization to
remove any sorting information which is left over from
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
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
database space, issue the DEFINE DBVOLUME and
EXTEND DB commands to add volumes to the server
database and extend the database size.

147
ANR0821E ANR0829E
ANR0821E
Filespace identifier fsId is not valid.
Explanation: The identifier assigned for a filespace is

out of range.
System action: The file space is not added.
ANR0822I
command: Filespace filespace name

(fsId=filespace id) successfully renamed
to new filespace name for node node name.
Explanation: The file space specified was renamed to

the new name specified for the node. This message is
displayed in response to successful completion of the
RENAME FILESPACE command.
System action: The system renames the file space for
the node as indicated
encountered a transaction failure.

System action: The server process is retried if the
maximum number of retry attempts have not been
exceeded.
User response: Transaction failure usually indicates
that a database deadlock was detected during file space
deletion. These deadlock conditions are sometimes
encountered when multiple file space deletion
processes are running at the same time. No action is
required unless the DELETE FILESPACE terminates
without completing the deletion process (see message
ANR0828).
ANR0827I
DELETE FILESPACE filespace name will

be retried for node node name.
Explanation: A file space deletion process for the node

indicated is being retried because an error was
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
Explanation: The file space name specified as a target

name for the command was found to already exist for
the node specified. The command fails.
System action: Server operation continues, the
command fails.
User response: Reissue the command with a different
target filespace name
ANR0824I
Delete Filespace filespace name

(space-managed data) for node node name
started.

(on the server) to delete space-managed objects in the
specified file space belonging to the node indicated. If a
file space name is not included in the message, then the
space-managed objects for all file spaces that belong to
the node are deleted.
space-managed objects for the specified file space while
ANR0826I

node node name encountered a
transaction failure.

been deleting file space data for the indicated node
148

node node name terminated before
completion due to transaction failure:
number of objects objects deleted.

been deleting file space data for the indicated node is
terminated prematurely because of transaction failure.
The number of objects deleted before the operation
ended are reported in the message.
User response: Termination of this process because of
transaction failure usually indicates that a database
deadlock was detected during file space deletion. These
deadlock conditions are sometimes encountered when
multiple file space deletion processes are running at the
same time. The command should be started again
when fewer file space deletion processes are active. An
authorized administrator can issue the DELETE
FILESPACE command to delete remaining files in the
file space(s).
ANR0829E
Command: Invalid combination of TYPE

and DATA parameters.
Explanation: The specified command has been issued

with an invalid combination of the TYPE and DATA
parameters. DATA=IMAGES can only be specified if
TYPE=ANY or TYPE=BACKUP.
command is not processed.
User response: Issue the command and specify a valid
combination of parameters.
ANR0830W ANR0834W
ANR0830W
Management class class name in domain

domain name used by node node name in
file space filespace name is no longer
active, or no longer has a BACKUP copy
group: DEFAULT management class
attributes will be used for expiration.
Explanation: During policy roll-off processing, the

server has found a client file copy whose management
class or backup copy group no longer exists.
System action: The server obtains the DEFAULT
management class for the specified domain and uses its
backup copy group version and retention parameters to
determine if file copies need to be expired.
User response: No action is required. A policy
administrator with authority over the specified domain
may use the DEFINE COPYGROUP, DEFINE
MGMTCLASS, and ACTIVATE POLICY commands to
define and activate a policy set that contains definitions
for the missing management class or copy group.
ANR0831W
The DEFAULT management class class

name in domain domain name does not
have a BACKUP copy group: GRACE
PERIOD will be used for expiration.

server found a client file copy whose management class
or backup copy group no longer exists. The DEFAULT
management class for the indicated policy domain does
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
copies need to be expired and removed from the server
database.
System action: The server obtains the GRACE
PERIOD retention values for the specified domain and
then determines if backup file copies need to be
expired.
for the missing management class or backup copy
group.
ANR0832W

filespace filespace name is no longer
active, or no longer has an ARCHIVE
copy group: DEFAULT management
class attributes will be used for
expiration.

archive copy group retention parameter to determine if
file copies need to be expired.
for the missing management class or copy group.
ANR0833W
The DEFAULT management class class

name in domain domain name does not
have an ARCHIVE copy group: GRACE
PERIOD will be used for expiration.

or archive copy group no longer exists. The DEFAULT
management class for the indicated policy domain does
not contain an archive copy group; therefore, the server
uses the GRACE PERIOD retention value defined for
the specified policy domain to determine if client file
copies need to be expired and removed from the server
database.
System action: The server obtains the GRACE
PERIOD retention values for the specified domain and
then determines if archive file copies need to be
expired.
MGMTCLASS, and ACTIVATE POLICYSET commands
to define and activate a policy set that contains
definitions for the missing management class or backup
copy group.
ANR0834W
Inventory client file expiration cannot

start because of insufficient memory 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.
expiration process will be retried after the stated delay.
application.

or archive copy group no longer exists.
149
ANR0835W ANR0840I
ANR0835W

domain name is no longer active, or no
longer has a BACKUP copy group, or no
longer has an ARCHIVE copy group.
DEFAULT management class used to
delete number of backup files backup files
and number of archive files archive files.
Retention grace period used to delete
number of backup files backup files and
number of archive files archive files.

server found a management class or backup copy
group or archive copy group that no longer exists.
When a management class or backup copy group no
longer exists, the number of backup client file copies
that have been deleted using the default management
class or the retention grace period is displayed in the
message. When a management class or archive copy
group no longer exists, the number of archive client
files that have been deleted using the default
management class or the retention grace period is
displayed in the message.
backup copy group or archive copy group version and
retention parameters to determine if file copies need to
be expired. If, however, the needed backup copy group
or archive copy group does not exist in the DEFAULT
management class, the server will use the retention
grace period for the domain.
User response: No action is required. This message is
only issued when expiration processing has been
started with the QUIET option to suppress detailed
messages. Expiration processing can be started without
the QUIET option to see the detailed messages which
will indicate specific node and filespaces and will
further distinguish between backup and archive copy
groups. A policy administrator with authority over the
specified domain may use the DEFINE COPYGROUP,
DEFINE MGMTCLASS, and ACTIVATE POLICY
commands to define and activate a policy set that
contains definitions for the missing management class
or copy group.
ANR0836W
No query restore processing session

session id for node node name and filespace
name failed to retrieve file high-level file
namelow-level file name - file being
skipped.
Explanation: The no query restore processing for the

session listed relating to the specified node name and
filespace failed to retrieve the specified file. An error
occurred while retrieving this file so it will be skipped.
System action: The no query restore operation
continues.
client can do a restore of the specific file that was

skipped.
ANR0837I
Explanation: An administrator or schedule issued the

command EXPIRE INVENTORY ... DURATION=xxx,
where xxx is the number of minutes for the expire
inventory process to run. That xxx number of minutes
has been reached, so the expire inventory process ends.
System action: The expire inventory process ends.
ANR0838I
Pass pass of group table conversion

processing beginning.
Explanation: The contents of the group information

tables needs to be updated before the server can fully
initialize. This is an informational message indicating
that processing has begun for a particular pass of the
conversion.
ANR0839I
Pass pass of group table conversion

processing complete.
Explanation: The contents of the group information

tables have been successfully converted for the
specified pass.
System action: If all passes of the conversion are
complete, server processing continues. If not, additional
passes will be performed.
ANR0840I
Converting group table information for

node node.
Explanation: The group table information for the

displayed node is being converted.
System action: Server processing continues
User response: Determine the cause of the file retieve

failure and correct it. After this situation is correct, the
150

ID was terminated after exceeding the
duration limit of duration minutes:
processed number of nodes nodes,
examined number of objects objects,
deleting number of backup objects backup
objects, number of archive objects archive
objects, number of DB backup volumes DB
backup volumes, and number of recovery
plan files recovery plan files. retry count
objects were retried and error count
errors were encountered.
ANR0844E ANR0853E
ANR0844E
Command: node name is not a

backup-archive node.
ANR0850E
Command: Cannot Start process name

Process.
Explanation: The specified node name is not a

backup-archive node.
Explanation: The indicated DELETE FILESPACE

process cannot be started on the server.
System action: Processing fails for the command.

System action: The DELETE FILESPACE command is

ended and server processing continues.

node name.
User response: This usually indicates that sufficient

server memory is not available on the server.
ANR0847I

CLEANUP BACKUPGROUPS evaluated

number of groups groups, and deleted
groups deleted orphan groups with
members deleted members deleted.
Explanation: The CLEANUP BACKUPGROUPS has

finished processing, and has deleted the specified
number of orphan groups and members.
Expiration failed to delete file type file

file name for node node name and
filespace filespace name - file will be
skipped.
Explanation: The expiration process was unable to

delete the indicated file. The file will be skipped by
expiration.
System action: The expiration process continues.
User response: Try expiration again to determine if
the cause of the deletion failure was an intermittent
problem or if it is a permanent problem. If after a
subsequent expiration attempt the file still is not
deleted, contact your service representative.
ANR0849E
Cannot start delete file space thread for

node node name.

process cannot be started on the server. Sufficient
memory on the server may not be available.

ANR0848W
ANR0851E
Command: Not permitted for node Node

Name - node of type SERVER.

process is not started because the node specified is of
NODETYPE=SERVER. A DELETE FILESPACE may
only be processed for nodes of this type with the
TYPE=SERVER parameter specified.
User response: If this filespace must be deleted,
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
availability of data for the server that owns these files.

application.
ANR0852E
Command: No matching file spaces

found for node node name.
Explanation: The server did not find any file spaces

for the node indicated matching the names specified in
the command.
System action: The server ends the command.
User response: Enter the command with file space
names that refer to defined file spaces for the specified
node. Note that file space names are case sensitive.
Enter them by using exactly the same uppercase and
lowercase characters that match the file space name
defined on the server. Use the QUERY FILESPACE
command to determine which file spaces are defined
for a node on the server.
ANR0853E
Transaction failed in file space deletion,

DELETE FILESPACE process aborted.
Explanation: A database transaction fails while the

server is deleting file space data.
System action: The server ends the file space deletion
process.
error. Issue the QUERY ACTLOG command to view the
representative.
151
ANR0854E ANR0861E
ANR0854E
Inventory file space query failure,

ANR0858E
Inventory object search failure, DELETE

FILESPACE process aborted.

querying the inventory database during a file space
deletion process.
Explanation: The server encounters an error accessing

the inventory database during file space deletion
processing.

process.

process.

representative.

representative.
ANR0855E
ANR0859E
Server LOG space exhausted, DELETE

Explanation: Insufficient server log space has been

encountered during file space deletion processing.
process.
add log volumes by using the DEFINE LOGVOLUME
command, and can extend the size of the log by using
the EXTEND LOG command.
ANR0856E
Server database space exhausted,

Explanation: Insufficient server database space has

been encountered during file space deletion processing.

removing file copies from data storage during file space
deletion processing.
process.
representative.
ANR0860E

process.
administrator can add log volumes using the DEFINE
DBVOLUME command and can extend the size of the
database using the EXTEND DB command.
ANR0857E
Data storage session failure, DELETE

Explanation: The server encounters an error accessing

data storage during file space deletion processing.
process.
representative.
Data storage object erasure failure,

Expiration process process ID terminated

due to internal error: examined number of
objects objects, deleting number of backup
objects backup objects, number of archive
objects archive objects, number of DB
backup volumes DB backup volumes, and
number of recovery plan files recovery plan
files. retry count objects were retried and
error count errors were encountered.

during file expiration processing. The number of files
examined and deleted prior to the error are reported. A
total error count is also displayed.
System action: The server ends the expiration process.
representative.
ANR0861E
Transaction failed in expiration,

inventory expiration aborted.
Explanation: The server encounters a database

transaction failure during policy roll-off processing.
152
ANR0862E ANR0867E
System action: The server ends roll-off processing.
activity log and search for messages.

representative.

size.
ANR0862E
Expiration processing suspended insufficient memory.
Explanation: The server ends policy roll-off processing

because sufficient server memory is not available.
System action: The server ends policy roll-off
processing and server operation continues.
application.
ANR0863E
Expiration processing suspended insufficient DB space.

because sufficient server database space is not
available.
DEFINE DBVOLUME command and can extend the
size of the database using the EXTEND DB command.
ANR0864E
Expiration processing suspended insufficient LOG space.

because sufficient server log space is not available.
command and can extend the size of the log by using
ANR0865E
Expiration processing failed - internal

server error.
Explanation: Server retry processing during policy

roll-off fails.
processing.

If the error cannot be isolated and resolved, contact
ANR0866E
Expiration processing retries failed - no

success after maximum retries retries.
Explanation: Server policy roll-off processing ends

because retry processing has not been successful in
expiring client file copies from the server database.
activity log and search for messages.
size.
If the error cannot be isolated and resolved, contact
ANR0867E
Unable to open policy domain for node

node name during server operation.
Explanation: Policy roll-off processing on the server

encounters an error while obtaining policy information
related to the specified node.
System action: The server ends roll-off processing and
representative.
153
ANR0868E ANR0875E
ANR0868E
Cannot find management class name for

ID management class ID.

encounters an error while obtaining policy information.
representative.
ANR0869E
Cannot find policy domain for node

node ID.

encounters an error while obtaining policy information
related to the specified node.
representative.
ANR0870E
Cannot find node name for node node

ID.

encounters a database error in obtaining information
for a client node.
representative.
ANR0871E
Cannot find file space name for node

node ID, file space file space ID.

encounters a database error in obtaining information
for a client node.
154

representative.
ANR0872E
Grace Period retention for domain

domain name could not be obtained.

encounters a database error in obtaining GRACE
PERIOD values for the specified policy domain.
representative.
ANR0873E
Invalid copy type encountered in

expiring files: copytype ID

encounters a database error in obtaining copy group
information.
representative.
ANR0874E
Backup object object not found during

inventory processing.
Explanation: Inventory processing on the server

encounters a database error in obtaining backup
information in data storage.
System action: The server ends roll-off processing, or
client session(s) and server operation continues.
representative.
ANR0875E
Archive object object.ID not found

during expiration processing.

encounters a database error in obtaining archive
information in data storage.
ANR0876E ANR0883E
representative.
ANR0876E
Data storage erasure failed during

expiration processing.

encounters a database error while deleting information
from data storage.
representative.
ANR0877E
Copy type not backup for object

object.ID.

encounters a database error in accessing inventory
information.
representative.

information.
representative.
ANR0880E
Explanation: The server did not find any file space

names matching the specifications entered in the
filespace command.
User response: Use the QUERY FILESPACE command
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
file space name (in proper case).
ANR0881E

Entry for backup object object.ID not

found.

information.
representative.
ANR0879E
Error opening inventory file space

query.
Policy Error : the GRACE PERIOD

archive retention value could not be
obtained for domain domain ID during
client inventory processing.

in accessing policy information.
ANR0882E
ANR0878E
Filespace command: No matching file

spaces.
Policy Error: Unable to open policy

domain for node node name during client
inventory query processing.

in accessing policy information.
System action: The client operation is ended and
ANR0883E
Cannot obtain node name for node node

ID.

in accessing client node information.
155
ANR0884E ANR0890I
ANR0884E
Error code during deletion of sorting

information for number objects.
Explanation: A background server process

encountered an internal error after deleting sorting
information for number files from the server database.
This process is started during initialization to remove
any sorting information which is left over from
System action: The backup or archive objects were not
deleted. Only the information used to sort these objects
during the previous export operation was deleted. The
background process was terminated before all sorting
information had been deleted. The system will not
perform further export processing of file data until this
problem has been resolved.
activity log and search for messages. Then restart the
server. If the error cannot be isolated and resolved,
ANR0885I
Import command: Processing management

class management class name for domain
domain name and policy set policy set
name as management class new
management class name.

processing the policy information for management class
management class name in domain domain name and
policy set policy set name. The management class is
imported under the name new management class name.
During import processing, management classes defined
as either DEFAULT or GRACE_PERIOD must be
renamed so that the management class does not conflict
with existing server policy conventions. Import
processing is then able to import file data by using the
renamed management class.
System action: Import processing for the command
continues.
User response: None. However, an administrator may
want to examine the policy definitions for new
management class name so they are aware of the
management classes that may be used if the policy set
containing this management class is activated.
ANR0886E

file space filespace name has no BACKUP
copy group with id copy group id;
Expiration will not be performed for
files from this node and filespace that
are bound to this management class and
copy group id.
156
server finds a client file copy with a management class

or a backup copy group that no longer exists.
System action: The server skips the files in error.
User response: For programming support, contact
ANR0887E

file space filespace name has no archive
copy group with id copy group id. Server
operation will not be performed for files
from this node and filespace that are
bound to this management class and
copy group id.

server finds a client file copy with a management class
or an archive copy group that no longer exists.
System action: The server skips the specified files.
ANR0888E
SQL commands cannot be issued from

the server console.
Explanation: An SQL command was issued from the

server console. SQL commands cannot be issued from
the server console because they may require a long
time complete and the server console should be
available to control other server functions.
User response: Issue the SQL command from an
ANR0889E
The server is not licensed for Central

Administration functions. This includes
the ability to issue SQL commands.
Explanation: An SQL command was issued but the

server is not licensed to support Central Administrative
functions, including SQL query support.
User response: If you have purchased the Central
Administration license, use the REGISTER LICENSE
command to enable the license on the server. If you
have not purchased the license and wish to do so,
ANR0890I

optionset optionset name.

is currently processing optionset definition information.
ANR0891I ANR0903W
command continues.
ANR0891I

optionset definitions.

Export command: No matching optionsets
found for exporting.

find any client optionsets for export command.
option sets from the server.
ANR0893I
Are you sure that you want to accept the

current system date as valid ?
Explanation: This message is displayed when the

ACCEPT DATE command has been issued to confirm
that you want to accept the date on the system as
valid. Accepting an invalid date can cause any of the
following problems: Premature deletion of data
Excessive retention of data Scheduling problems Event
record problems Password expiration problems.
System action: The command waits for you to
confirm the action.
User response: Specify Yes if you want to accept the
system date as valid, or No if you do not want to
execute the command.
ANR0894I
Command: Cannot Start process name

Process.
Explanation: The indicated process cannot be started

on the server.

copies number client optionset definitions from the
command.
ANR0892I
ANR0895E
Current system has been accepted as

valid.

ACCEPT DATE command has been issued and the date
has been accepted as valid by the server.
System action: The specified command is ended and

server processing continues.
ANR0900I
Processing options file filespec.
Explanation: At server initialization, the server is

reading the server options file whose name is shown in
the message.
System action: The server reads and processes the
options in this file.
ANR0901W
Invalid option statement found in file

filespec.
Explanation: While processing the server options file

named, the server has encountered an invalid
statement. The invalid statement type is shown in the
message. The lines following this message provide
more information.
System action: The server ignores the statement in
error. Server initialization continues. The default value
is used for any missing or ignored options.
User response: Ignore the error, or use a text editor to
correct the error and restart the server.
ANR0902W
Unsupported keyword found in file

filespec.

named, the server has encountered an invalid keyword
on an option statement. The lines following this
message provide more information.
System action: The server ignores the option
statement in error. Server initialization continues. The
default value is used for any missing or ignored
options.
System action: The current system date is accepted as

valid by the server. The server will begin processing
using the current system date.
ANR0903W
User response: Issue the ENABLE SESSIONS ALL

command to allow client, server and administrative
sessions to start.
Explanation: While processing the specified server

options file, the server has encountered more of the
named statement type than can be processed.
Excessive option statement found in file

filespec.
157
ANR0904W ANR0915E
System action: The server ignores the extra statement.
Server initialization continues.
ANR0911I

ANR0904W
Duplicate option statement found in file

filespec.

named, the server has encountered a duplicate
statement of the type shown.
System action: The server ignores the duplicate
statement. Server initialization continues.
ANR0905W
Archive conversion processing for node

name completed successfully. The
description tables have description count
descriptions, directory count directories,
file count and files and object set count
object sets.
Explanation: CONVERT ARCHIVE for the specified

node completed successfully. The node can now query
for archive objects specifying a non-wildcarded
description.
ANR0912I
Options file filespec not found.
Undo conversion processing for node

node name completed successfully. The
node is no longer converted.

unable to locate the server options file named.
Explanation: UNDO ARCHCONVERSION was issued

for the specified node. The node will no longer use the
archive description tables.
System action: The server uses the default values for

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
options file to the proper name, or use a text editor to
build the proper server options file, and then restart the
server.
ANR0909E
Insufficient memory to process options

file.

unable to process the server options file due to
System action: Server initialization ends.
User response: Restart the server with more memory
available. Refer to the Administrators Guide for your
ANR0910W
Archive entries for nodeName are already

converted.
Explanation: Archive entries for nodeName have

already been converted to the description tables. They
will not be converted again.

ANR0913E
Archive conversion processing for node

node name did not complete (result).
Explanation: Archive conversion for the indicated

node did not complete because of the specified result.
System action: Archive conversion ends. Server
User response: Check previous messages for error
conditions.
ANR0914E
Diagnostic(ID): a request failed because

object (object name), size (size), exceeds
the maximum size of maximum size.
Explanation: The size of the specified object exceeds

the maximum size defined for that object. The server
cannot handle the new object.
fails.
User response: Determine why the new object's length
exceeds the maximum specified for the object. Reduce
the length of the object.

User response: To force the reconversion of the
archive entries for nodeName, use the FORCE=Yes
option to the CONVERT ARCHIVE command.
ANR0915E
Unable to open language language name

for message formatting.
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
158
ANR0916I ANR0926E
specified in the LANGUAGE option of the server
options file. If a change is made to the options file,
restart the server to activate changes.
ANR0916I
Product Name distributed by Company is

now ready for use.
Explanation: The server has completed startup

processing and is now ready for use.
ANR0921I
Tracing is now active to file file spec.
Explanation: In response to a TRACE START

command, server trace records are being written to the
file named.

ANR0917W
ANR0922I

name (client platform) - in domain domain
name failed because of policy length.
Trace ended.
Explanation: In response to a TRACE END command,

server trace records are no longer being written.
Explanation: The client cannot handle very long

policies.
System action: The client operation is ended and

ANR0923E
User response: Upgrade the client to the latest level,

or activate a policy set with fewer management classes.
ANR0918E
Inventory operation for node node name

terminated - lock conflict.
Explanation: During the indicated operation, the

server needs to obtain a lock that is not available.
System action: The indicated operation ends.
User response: Restart the operation.
Tracing is inactive.
Explanation: A TRACE END command has been

entered, but tracing is not active.
System action: The command is ignored.
User response: If tracing is desired, use the TRACE
ENABLE and TRACE START commands to activate
server tracing.
ANR0924E
Tracing is already active to file file spec.
Explanation: A TRACE BEGIN command has been

entered, but tracing is already active to the file named.
ANR0919E
Filespace name fsName with length

length was encountered for nodes node
list.
Explanation: The specified filespace name was found

for the nodes in the list. The name is not allowed. The
error may occur while processing an administrative
command or client request.
User response: If the error occurs during processing
for an administrative command such as EXPORT
NODE or RENAME FILESPACE, rename the filespace
for the nodes in the list using a valid name. If found
while processing a client request, contact your service
representative.
ANR0920I
Tracing is now active to standard

output.
Explanation: In response to a TRACE START

command, server trace records are being written to the
standard output destination (usually the server
console).
User response: If the current trace output file is

acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
ANR0925E
Tracing is already active to standard

output.

entered, but tracing is already active to the standard
output destination (usually the server console).
User response: If the current trace output destination
is acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
ANR0926E
Missing or invalid TRACE command

parameter.
Explanation: The TRACE command issued contains

an invalid parameter, or is missing a required
parameter.
159
ANR0927E ANR0942E
User response: Reissue the command with the proper
parameters.
ANR0927E
Unknown trace class keyword - class.
Explanation: A TRACE ENABLE command has been

entered which specifies an unknown trace class.
User response: Reissue the TRACE command with the
correct class.
ANR0928E
Unable to open trace file file spec for

appending.
Explanation: A TRACE BEGIN command specifies an

output file, but the server cannot write to that file.
ANR0937I
Expiration process process ID is ending.
Explanation: The expiration process referenced is

ending either because it has been cancelled or because
it has completed the necessary actions. This message is
only issued in the case where expiration was processing
a long-running operation, such as deleting a group of
related files (for example, a backup group). This
message indicates the time when the long-running
operation ended.
ANR0939E
Error error code occurred while locating

base object (baseId) for subfile (subfileId):
Node node name, File space filespace name,
Type file type, File name file name.
User response: Check the file for proper access

permissions, or reissue the TRACE command
specifying a different output file.
Explanation: Export processing did not find the base

object for the specified subfile. Export processing does
not continue.
ANR0929E
System action: Export processing stops. Server

Insufficient memory to activate tracing.

entered, but the server has insufficient memory
available to activate tracing.
User response: Audit the database to correct the

entries.
ANR0940I
User response: If tracing is required, make more

memory available to the server then restart the server.
ANR0936E
Session session ID for session name failed

sending verb verb name because client
not able to handle extended qualifier
attribute.
Cancel request accepted for process

process ID.
Explanation: A CANCEL PROCESS command has

been entered for the specified process. Some processes
will experience a delay before they terminate. This
delay may be lengthy for processes that involve remote
data movement.
Explanation: A server was going to send the reported

verb for the indicated session but was not able to send
it. The verb could not be sent to the client because it
contains extended information about the low-level
qualifier. The extended low-level qualifier is used to
store names up to 512 bytes in length. The client that
this verb was supposed to be sent to does not support
the extented low-level qualifier information.
System action: The send of the verb to the reported

session fails and this server operation will fail and
report a communication error.
System action: The server ignores the command.
User response: The client session reported needs to

have the installed client upgraded to TSM version 5.1.5
or higher in order to support the extended low-level
qualifier.
ANR0941I
Command: Cancel for process process ID

is already pending.

been entered for the specified process, but a cancel is
already pending for that process.

ANR0942E
Command: Process process ID cannot be

found.

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.
User response: If the wrong process number has been
160
ANR0943E ANR0955I
entered, reissue the command with the correct process
number.
ANR0943E
Command: Process process ID could not be

canceled.
command, specifying either the same or a different

output file.
ANR0952W
The filespace Filespace name cannot be

included in the backup set because it
contains encrypted data.

been entered for the specified process, but the process
specified is an automatic process, such as migration or
reclamation, that cannot be canceled.
Explanation: Data from the filespace cannot be

included in the backup set because the filespace
contains encrypted data.
System action: The filespace is skipped.
ANR0944E
Command: No active processes found.
ANR0953W
Explanation: A QUERY PROCESS command has been

entered, and no processes are active.
ANR0945W

was aborted for process process ID.
Explanation: An error is detected during transaction

commit for the specified process. This message should
be preceded by other messages that give additional
information about the failed transaction.
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
audit command is not able to determine which key is
the correct key.
System action: The object's encryption keys are not
modified.
ANR0954W

fails.
ANR0946E
Archive processing fails: Object objId not

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
by an archive delete request, delete filespace or
expiration that began and completed between these
stages.
System action: System processing continues.
User response: Check the client log for error and retry
messages. Reissue the archive request if the retry failed.
ANR0947E
Error writing to trace file file spec.
Explanation: An error occurred while writing to the

specified trace file.
System action: Trace is disabled.
permissions, or for the out of space issue for the trace
file. Once this is corrected, reissue the TRACE BEGIN
Audit command: Redundant encryption

keys for the archive object (object.ID) do
not match.
Audit command: Redundant encryption

keys for the backup object (object.ID) do
not match.
Explanation: The encryption key stored for the backup

object in the Object.Ids table does not match the
encryption key stored in the Backup.Objects table. The
audit command is not able to determine which key is
the correct key.
System action: The object's encryption keys are not
modified.
ANR0955I

node node name failed deletion because
of a restartable restore session.
Explanation: The reported node and filespace have a

restartable restore session active or restartable. A
filespace cannot be deleted while the restartable restore
session exists.
System action: The server process is retried if the
maximum number of retry attempts have not been
exceeded.
User response: Use the QUERY RESTORE command
to view active and restartable restores sessions for this
filespace. Either wait for the sessions to complete or
cancel the sessions with the CANCEL RESTORE
command, and reissue the DELETE FILESPACE
command. To view restartable restore sessions issue the
161
ANR0956I ANR0965I
command QUERY RESTORE. Either:
v wait to reissue the DELETE FILESPACE command
after this restartable restore has completed
v cancel the restartable restore session with the
CANCEL RESTORE command
ANR0956I
Audit command: Active version for

inactive inventory object (object.ID) does
not exist. The expiring object entry must
be corrected.
Explanation: A database audit process found an

expiring object entry for an inactive inventory object
that indicates an active version of the object exists, but
the active version does not exist. Because FIX=NO has
been specified for the command, the expiring object
entry is not corrected.
System action: Audit processing continues.
ANR0957I
Audit command: Active version for

inactive inventory object (object.ID) does
not exist. The expiring object entry will
be corrected.

expiring object entry for an inactive inventory object
that indicates an active version of the object exists, but
the active version does not exist. Because FIX=YES has
been specified for the command, the expiring object
entry will be corrected.
ANR0960I
Process process ID waiting for mount

point in device class device class name.
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.
System action: The process waits for the mount point.
User response: Respond to any mount requests.
ANR0961I
Process process ID waiting for multiple

mount points in device class device class
name.

begun to wait for multiple mount points that can be
used for a volume in the device class shown.
System action: The process waits for the mount
points.
ANR0962I
Process process ID waiting for mount

points in device classes device class name
and device class name.

begun to wait for mount points that can be used for a
volume in the two device classes shown.
System action: The process waits for the mount
points.

ANR0963I
ANR0958I

begun to wait for the mount of the input volume
shown.
CLEANUP BACKUPGROUPS evaluated

objectcount group objects, found
errorcount errors, and deleted deleted
group objects with completion state
state.
Process process ID waiting for mount of

input volume volume name.
System action: The process waits for the mount.
Explanation: The CLEANUP BACKUPGROUPS utility

ended with the presented state.
ANR0964I

ANR0959I
Conversion of grouping table is percent

done percent complete.

output volume volume name.

begun to wait for the mount of the output volume
shown.
Explanation: An internal data base table is being

converted, and the conversion process is the indicated
amount complete.
ANR0965I

scratch volume.

begun to wait for the mount of a scratch volume.
162
ANR0966I ANR0983W
ANR0966I
Process process ID waiting for access to

input volume volume name.

begun to wait for availability of the input volume
shown.
System action: The process waits for the volume to
become available.
ANR0967I
Process process ID waiting for access to

output volume volume name.

begun to wait for availability of the output volume
shown.
System action: The process waits for the volume to
become available.
ANR0969E
The server database must be formatted

and loaded or restored before the server
can be started.
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
process that includes a DSMSERV FORMAT. Perform
one of the following procedures. Either do these steps:
FIX=YES command. For complete details on this

command, refer to the Administrators Reference.
ANR0981E
The server database must be restored

before the server can be started.
Explanation: This message is issued in one of two

cases: 1) The server has been restarted after an
incomplete RESTORE DB. In order to start the server,
you must restore the database to a consistent state
using the DSMSERV RESTORE DB command; 2)
During server operation, an error condition occurred
such that the TSM server cannot continue. This
message is issued, and the server halts. Before you can
start the server again, you need to use the DSMSERV
RESTORE DB command to restore the database.
System action: Server initialization stops, or the server
stops.
User response: If there are other messages issued with
this error message which have instructions associated
with them, follow the instructions in those messages.
Then issue the DSMSERV RESTORE DB command. For
complete details on this command, refer to the
Administrators Reference. After the DSMSERV RESTORE
DB command completes successfully, restart the TSM
server.
ANR0982E
The server database must be initialized

before the database can be loaded.
2. Restore the database using DSMSERV RESTORE DB
Explanation: The server database must be initialized

before it can be loaded with the LOADDB parameter,
by issuing the DSMSERV LOADFORMAT command.
The server database is not currently in the initialized
state.
Or do these steps:
System action: Server LOADDB processing stops.
1. Format the volumes using DSMSERV FORMAT
1. Unload the database using DSMSERV UNLOADDB

3. Load the database using DSMSERV LOADDDB
User response: Issue the DSMSERV LOADFORMAT

command. For complete details on this command, refer
to the Administrators Reference.
Note: Do not use DSMSERV DUMPDB on the database

for this recovery.
ANR0983W
2. Format the volumes using DSMSERV FORMAT
System action: Server initialization stops.

User response: Perform one of the database recovery
actions.
ANR0980E
The server database must be audited

with FIX=YES before the server can be
started.
The server database was recorded by a

down-level version of the server
program. The UPGRADEDB parameter
is required to start the server and
automatically upgrade the database
contents to the current server version.
Please refer to installation instructions
for precautionary backup procedures
prior to doing this.
Explanation: At server startup, the server has

discovered that the database information was written
by an earlier version of the server program and is not
compatible with this version. To automatically upgrade
the server database to this version of the server
program, the UPGRADEDB parameter must be
specified when starting the server.
User response: Issue the DSMSERV AUDITDB
System action: The server ends.
Explanation: The server has been restarted after a

DSMSERV LOADDB command processed a database
image that was known to have inconsistencies. In order
to bring the database back to a consistent state, you
must run the AUDITDB command.
163
ANR0984I ANR0989E
User response: Refer to installation instructions for
specific information on precautionary measures that
you may want to take to back up the database prior to
upgrading it to the current server level. After you have
taken these measures, start the server and specify the
UPGRADEDB parameter. This parameter only needs to
be specified once to start the server, and should NOT
be included in any automated programs that start the
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

started for the process indicated by the process name
running in the indicated state.
ANR0985I
Process process ID for process name

running in the process state completed
with completion state completion state at
process start time.
Explanation: A completion state of FAILURE indicates

that the operation encountered an error condition or
terminated before completion. A completion state of
SUCCESS indicates that the operation ran to
completion, but in some situations may have
encountered and reported conditions that would affect
the outcome of the operation.
User response: If the completion state is FAILURE,
then review the activity log and the event log to try to
determine the cause of the failure. If the completion
state is SUCCESS, the activity log and the event log can
still be checked for warning messages regarding
conditions that could have affected the operation.
ANR0986I

running in the process state processed
items processed items for a total of bytes
processed bytes with a completion state
of completion state at process start time.


ANR0987I

items processed items with a completion
state of completion state at process start
time.

ANR0988I

bytes processed bytes with a completion
state of completion state at process start
time.

ANR0989E
The server database must be inserted or

restored before the server can be started.
Explanation: The server is restarted after the

LOADFORMAT command is run. To start the server,
you must upgrade the database by issuing DSMSERV
INSERTDB or else the database needs to be restored
using the DSMSERV RESTORE DB command.

User response: Issue the DSMSERV INSERTDB or

DSMSERV RESTORE DB command. For complete
details on these commands, refer to the Administrators
Reference. Alternatively, the server can be installed using
the DSMSERV FORMAT command in order to prepare
164
ANR0990I ANR1002I
it for regular use without needing to upgrade an earlier
version server with the DSMSERV INSERTDB
command or restoring the database with the DSMSERV
RESTORE DB command.
ANR0990I
Server restart-recovery in progress.
Explanation: The server has been restarted after a halt

or system failure. If necessary, the server performs
recovery processing in order to bring the system back
to a consistent state.
later version of the server program. This version of the

server program should not be used.
User response: Start a version of the server program
that is at the same level as the prior server program
used.
ANR0996W
System action: Server initialization continues.

discovered that the disk information was written by an
earlier version of the server program and is not
compatible with this version.

ANR0991I
The information on disk was recorded

by a down-level version of the server
program; reinstallation is required to
use this version.
server shutdown complete.
Explanation: In response to a HALT command, the

server or storage agent has completed its termination
processing.
System action: The server or storage agent ends.

User response: Install this version of the server to
bring the information up to the level of the program
being used.

ANR1000I
ANR0992I
Server's database formatting complete.
Explanation: The server formatting procedure has

completed successfully. The server is now available for
normal operation.
System action: Server completes formatting
processing.
ANR0993I
Server initialization complete.
Explanation: The server has been restarted after a halt

or system failure. It is now ready to resume normal
operation.
System action: Server completes initialization.
ANR0994W
This server has not been properly

installed.
Explanation: The server was started for normal

operation, but had not yet been installed.
User response: Install the server properly before
starting it.
ANR0995W
This version of the server program is

down-level with respect to the
information recorded on disk; a newer
version of the program should be used.

discovered that the disk information was written by a
Migration process process ID started for

storage pool storage pool name
automatically or manually,
highMig=highMig value, lowMig=lowMig
value, duration=duration.
Explanation: Because the high migration threshold for

the storage pool shown has been exceeded, a process
has been started to migrate files from the storage pool.
Note: a duration value of No means that the duration
is not specified and hence the migration runs without
duration.
System action: Data is moved from this storage pool
to the next (target) pool.
ANR1001I
Migration process process ID ended for

storage pool storage pool name.
Explanation: A migration process for the named

storage pool ends. This action can occur because the
low migration threshold for the storage pool has been
reached, there are no more nodes with files to be
migrated, there are no more volumes to be migrated, or
the duration specified has been reached.
ANR1002I
Migration for storage pool storage pool

name will be retried in number of seconds
seconds.
Explanation: Because of a problem encountered

attempting migration for the named storage pool,
165
ANR1003I ANR1014W
a. The server will write the data to the next storage
pool and to the copy pools that are associated
with the original destination primary storage
pool.
migration is delayed but will be retried after the time

period shown.
System action: The server waits for the specified
period and then retries migration for the storage pool.
This delay applies to a single migration process. After a
number of unsuccessful retries, the server will
automatically cancel the process. If other migration
processes are executing for the named storage pool,
these processes will continue migration.
b. The setting of the COPYCONTINUE attribute of

the original destination primary pool will be
inherited by the next pool.
c. If the next pool is configured for simultaneous
write operations, the copy storage pools
associated with the next pool will be ignored as
well as the value of its COPYCONTINUE
attribute.
User response: If possible, correct the condition that

has caused delayed migration.
ANR1003I
Migration retry delay ended; checking

migration status for storage pool storage
pool name.
2. If the primary storage pool specified in the

management class copy group does not have copy
pools associated with it for simultaneous write
operations:
a. The server will write the data to the next storage
pool.
Explanation: Because migration for the indicated

storage pool had been delayed due to a problem, the
system waited before retrying. The retry wait period
has ended, and the system will now retry migration.
System action: Migration processing for the storage
pool resumes.
ANR1004I
Server formatting complete, database

ready for loading.
b. If the next pool is configured for simultaneous

write operations, the copy pools associated with
the next pool will be ignored.
User response: None. Refer to the Administrators
Guide for details about simultaneous write
configurations.
The pool type storage pool pool name is
either not available, or does not have
enough space for a simultaneous write
operation.
Explanation: The server formatting procedure has

completed successfully. The server is ready to be
loaded by issuing the DSMSERV LOADDB or the
DSMSERV RESTORE DB command.
ANR1014W
System action: Server completes formatting

processing.
Explanation: During a backup, archive, client

migration, or import operation that is using
simultaneous write, the server cannot write data to the
specified storage pool. Possible reasons include:
User response: The DSMSERV LOADDB or the

DSMSERV RESTORE DB command is required to load
the database before the server will be ready for use. For
complete details on these commands, refer to the
Administrators Reference.
ANR1013I
During a store operation, the server is

switching to a next pool in the storage
hierarchy. The next storage pool will
inherit the simultaneous write
configuration from the destination
primary storage pool.
Explanation: If during a backup, archive, client

migration, or server import operation, the server must
write data to a next pool in a storage pool hierarchy,
the following rules will apply:
1. If the destination storage pool specified in the
management class copy group has one or more
copy storage pools associated with it for
simultaneous write operations:
v The storage pool is unavailable.

v There is not enough space available in the specified
storage pool.
System action: The result of the simultaneous write
operation depends on the setting of the
COPYCONTINUE attribute of the original destination
primary pool destination:
v If the value of the COPYCONTINUE attribute of the
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
pool in the storage hierarchy and any other
remaining copy pools.
destination primary pool is NO, the server will fail
the transaction and discontinue the operation.
Refer to the Administrators Guide for details about the
simultaneous write COPYCONTINUE attribute.
User response: Ensure the copy storage pool is set for
READWRITE access. If needed, make more space
available in the copy storage pool. After the problem is
166
ANR1015I ANR1023W
corrected, take one of the following actions:
destination primary pool is YES, issue the BACKUP
STGPOOL commands to back up any files in
primary storage pools in the storage pool hierarchy
that have not been copied to the copy pool that
failed.
destination primary pool is NO, run the
simultaneous write operation again.
ANR1015I
Storage pool pool name has pending bytes

duplicate bytes pending removal.
Explanation: The number of bytes indicated have been

identified as duplicate bytes in the storage pool, but the
volumes on which the data resides have not yet been
reclaimed.
System action: None
Fibre Channel adapters on the system

cannot be opened.
Explanation: Due to problems with the HBAAPI or

Fibre Channel HBA driver, the HBAAPI function
cannot open any Fibre Channel host bus adapters
(HBAs) on the system.
User response: The Tivoli Storage Manager SAN
discovery function is not working. Check your Fibre
Channel host bus adapter (HBA) vendor and upgrade
your HBAAPI or Fibre Channel HBA driver version.
For a list of supported HBAs and required driver levels
by operating system, go to http://WWW.IBM.COM/
SUPPORT.
ANR1018I
Volume deduplication process process ID

started for storage pool storage pool name,
identify processes=number of identify
processes.
Explanation: A volume deduplication process was

started for the storage pool shown.
Migration process process ID terminated

for storage pool storage pool name process canceled.
Explanation: During migration for the indicated

storage pool, a process performing the migration has
been canceled.
System action: The migration process is terminated. If
other migration processes are executing for the named
storage pool, these processes will continue migration.
ANR1021W

for storage pool storage pool name storage media inaccessible.
System action: The indicated migration process ends.

The server waits for the retry period to expire and then
tries the migration again. If other migration processes
are executing for the named storage pool, these
processes will continue migration.
User response: One possible cause for this failure is
that the access state for the target volume or storage
pool for this operation is not set to READWRITE.
Check the access state for the requested output volume
and storage pool and ensure they are set to
ACCESS=READWRITE.
ANR1022W

for storage pool storage pool name excessive read errors encountered.

storage pool, read errors occur that prevented the
migration from continuing.
User response: If possible, correct the cause of the
read errors.

ANR1019W
ANR1020W

storage pool, a required volume could not be mounted.
User response: None

ANR1016W
device. Check the device configuration on the system.
Unable to get the node attributes for

node name.
Explanation: The HBAAPI function cannot obtain the

node's attributes. Removing devices from the SAN
without reconfiguring the system can cause this
problem.
User response: SAN discovery is not working for this
ANR1023W

for storage pool storage pool name excessive write errors encountered.

storage pool, write errors occur that prevent the
167
ANR1024W ANR1030W
ANR1027W

write errors.
ANR1024W

for storage pool storage pool name - data
transfer interrupted.

storage pool, a data transfer operation was interrupted
and could not be continued.
interruption.
ANR1025W

for storage pool storage pool name insufficient space in subordinate storage
pool.

storage pool, the server cannot move the data from the
storage pool, because there is not enough space on the
next storage pool to hold it.
tries the migration again.
User response: Make more space available in the next
storage pool, or use the UPDATE STGPOOL command
to change the next storage pool to one with more space.
ANR1026W

for storage pool storage pool name unable to move file to subordinate
storage pool due to exclusion by size.

storage pool, the server cannot move the data from the
storage pool, because a file is larger than what is
allowed on the next storage pool.
User response: Use the UPDATE STGPOOL command
to change the next storage pool maximum file size or to
change the next storage pool target.

for storage pool storage pool name sufficient recovery log space is not
available.

storage pool, the server runs out of recovery log space.
User response: If necessary, make more server
recovery log space available.
ANR1028W

for storage pool storage pool name sufficient database space is not
available.

storage pool, the server runs out of database space.
database space available.
ANR1029W

for storage pool storage pool name - lock
conflict.

storage pool, the server needs to obtain a lock that is
not available.
User response: Wait for the server to retry the
migration.
ANR1030W

for storage pool storage pool name - thread
resource not available.

storage pool, the server cannot start a thread for the
migration process.
migration. If the error persists, it may indicate a
shortage of server memory.
168
ANR1031W ANR1043I
ANR1031W

for storage pool storage pool name sufficient memory is not available.

storage pool, there is not enough server memory
available.
User response: If necessary, make more memory
available to the server.
ANR1032W

for storage pool storage pool name internal server error detected.

storage pool, the server encounters an internal error.
ANR1033W

for storage pool storage pool name transaction aborted.

storage pool, the server detected an error while
attempting to commit a transaction. This message
should be preceded by other messages that give
additional information about the failed transaction.
transaction.
ANR1034W
Files stored on volume volume name

cannot be migrated - volume is offline
or access mode is "unavailable" or
"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: 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
name (process number process ID).
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
volume can be reclaimed.
System action: The server starts volume space
reclamation.
ANR1041I
Space reclamation ended for volume

volume name.
Explanation: Space reclamation for the volume named

is complete.
ANR1042I
Space reclamation for storage pool

storage pool name will be retried in
number of seconds seconds.

attempting space reclamation for the named storage
pool, reclamation stops but will be retried after the
time period shown. After a number of unsuccessful
retries, the process will be automatically cancelled.
System action: The system waits for the specified
period and then retries space reclamation for the
storage pool.
has stopped reclamation.
ANR1043I
Space reclamation retry delay ended;

checking volume reclamation status for
Explanation: Because space reclamation for the

indicated storage pool had been stopped due to a
problem, the system waited before retrying. The retry
wait period has ended, and the system can now retry
space reclamation.
System action: Reclamation for the pool begins.
System action: The server continues migration

processing, but skips files stored on the indicated
volume.
169
ANR1044I ANR1054E
ANR1044I
Removable volume volume name is

required for space reclamation.
Explanation: During space reclamation processing, the

server determines that a removable volume is required
in order to complete processing.
System action: The server attempts to mount the
removable volume.
User response: Respond to any mount request for the
indicated volume.
ANR1045E
Reclamation has ended for volume

volume name. The files on the volume are
too large for the target storage pool,
storage pool name.
Explanation: During reclamation for the indicated

volume, the server cannot move the data from the
volume because a file is larger than allowed for the
indicated storage pool.
System action: Reclamation of the volume stops. If
other reclamation processes are running, these
processes will continue the reclamation.
to change the value of the MAXSIZE parameter for the
storage pool. Specify the value as NOLIMIT, or specify
a value larger than the largest file to be reclaimed.
ANR1046E
command: Database upgrade not

currently supported for this server
because it uses backup sets.
Explanation: The current version of the TSM 6.1

server does not support backup sets. However, the
server being upgraded uses backup sets, and so cannot
be upgraded at this time. Note that this is a temporary
limitation that will be lifted in a future TSM 6.1 Server
Fix Pack.
System action: The command ends without inserting
any data into the database.
User response: Rerun the command using a version of
the TSM 6.1 server that supports backup sets.
ANR1047E
command: Database upgrade not

currently supported for this server
because it uses NAS backups with
TOCs.
Explanation: The current version of the TSM 6.1

server does not support NAS backups that use a table
of contents (TOC). However, the server being upgraded
uses TOCs, and so cannot be upgraded at this time.
Note that this is a temporary limitation that will be
lifted in a future TSM 6.1 Server Fix Pack.
170

the TSM 6.1 server that supports NAS backups with
TOCs.
ANR1048E
command: Protocol error out-of-sequence verb (type verb name)

received.
Explanation: The server detects a protocol error while

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
version of the DSMUPGRD utility that is not
compatible with the TSM 6.1 version to which you are
upgrading.
the server compatible with the version of DSMUPGRD
used to extract the data. Or reextract the data using an
older version of DSMUPGRD that is compatible with
the version of the server.
ANR1049W
The server is unable to obtain

number-formatting information from the
system-locale attributes. The server
substitutes alternate number format
nmbrFmt.
Explanation: The server is unable to format some

numbers because it is unable to obtain a valid thousand
and decimal separator value from the system locale.
System action: The server continues. An alternate
number format is used. Numbers are displayed using a
comma character as the thousand separator and a
period character as the decimal separator.
User response: Check whether errors occurred during
server initialization that might indicatea problem
initializing the locale . Check whether the server is
running in a locale supported by the server. If it is not,
restart the server in a supported locale.
ANR1053E
Command: Invalid process number processIdvalue
Explanation: A QUERY EXPORT command was

issued that specifies an invalid process number.
command.
process number.
ANR1054E
Command: Invalid export operation state

- export state
Explanation: A QUERY EXPORT command was

issued that specifies an invalid export state.
ANR1055E ANR1062W
command.
ANR1059I

export operation state.
ANR1055E
Command: Invalid export session

identifier name - export sess name.
Explanation: The issued command specifies an invalid

export session identifier.
command.
export session identifier.
ANR1056E
command name: The PROCESS parameter

is not valid if an export identifier is
specified.
Explanation: The command failed because of an

invalid combination of arguments.
operations continue.
User response: Reissue the command with a valid set
of parameters. For information on valid values for the
command parameter, refer to the Administrators
ANR1057E
command name: The PROCESS parameter

is not valid when the STATE parameter
is specified with a value of
INITIALIZING or SUSPENDED
Explanation: The command failed because of an

invalid combination of arguments.
User response: Reissue the command with a valid set
of parameters. For information on valid values for the
command parameter, refer to the Administrators
Explanation: A restore is started for the indicated file

system of a NAS node. The operation is initiated by the
administrator shown. Selected files and/or directory
trees specified by the administrator will be restored to
the indicated destination.
System action: The indicated process is started.
ANR1060W
command name: TODATE must be

specified when TOTIME is specified.
Explanation: A command supporting the TODATE

and TOTIME parameters was issued with the TOTIME
parameter specified but without the TODATE
parameter. When the TOTIME parameter is used, the
TODATE parameter must be specified.
Error initiating space reclamation for

storage pool storage pool name - lock
conflict.
Explanation: While attempting to initiate space

reclamation for the indicated storage pool, the server
needs to obtain a lock that is not available.
System action: Space reclamation stops. The server
waits for the retry period to expire and then tries the
reclamation again.
reclamation.
ANR1061W

storage pool storage pool name - sufficient
Explanation: During an attempt to initiate space

reclamation for the indicated storage pool, there is not
enough server memory available.
waits for the retry period to expire and then tries the
reclamation again.
ANR1062W
ANR1058E
Selective restore of NAS node nodename,

file system file system, started as process
process ID by administrator administrator.
Specified files and/or directory trees
will be restored to destination
destination.

storage pool storage pool name - internal
server error detected.
Explanation: During an attempt to initiate space

reclamation for the indicated storage pool, an internal
server error is encountered.
will wait for the retry period to expire and then tries
the reclamation again.
User response: Reissue the command and specify both

the TODATE and TOTIME parameters.
171
ANR1063I ANR1072E
ANR1063I
Full backup of NAS node nodename, file

system file system, started as process
Explanation: A full backup is started for the indicated

file system of a NAS node. The operation is initiated by
the administrator shown.
ANR1067I
Explanation: The indicated operation completed.

System action: The indicated process ends.
ANR1068W

ANR1064I
Differential backup of NAS node

nodename, file system file system, started
as process process ID by administrator
administrator.
Explanation: A differential backup is started for the

indicated file system of a NAS node. Only files that
have changed since the last full backup will be
processed. The operation is initiated by the
administrator shown.
ANR1065I
Restore of NAS node nodename, file

A full image for this file system will be
restored to destination destination.

administrator shown. The restore will be performed
using a full image of this file system. The file system
will be restored to the indicated destination.
ANR1066I
Restore of NAS node nodename, file

A full image plus a differential image
for this file system will be restored to
destination destination.

administrator shown. The restore will be performed
using a full image plus a differential image of this file
system. The file system will be restored to the indicated
destination.
Operation process process ID completed.
Operation process process ID terminated process cancelled.
Explanation: During the indicated operation, a

background process was cancelled.
ANR1069E
Operation process process ID terminated insufficient number of mount points

available for removable media.

server could not allocate sufficient mount points for the
volumes required.
available.
ANR1070E
Operation process process ID terminated write errors encountered.
Explanation: During the indicated operation, write

errors prevent the operation from continuing.
errors and restart the operation.
ANR1071E
Operation process process ID terminated read errors encountered.
Explanation: During the indicated operation, read

errors prevent the operation from continuing.
errors and restart the operation.
ANR1072E
Operation process process ID terminated insufficient space in destination storage

pool.
Explanation: During the indicated operation, there is

not enough space available in the destination storage
pool.
User response: Make more space available in the
storage pool and restart the operation.
172
ANR1073E ANR1082E
ANR1073E
Operation process process ID terminated sufficient recovery log space is not

available.

server runs out of recovery log space.
ANR1074E
Operation process process ID terminated sufficient database space is not

available.

server runs out of database space.
ANR1075E
Operation process process ID terminated lock conflict.

server needs to obtain a lock that is not available.
ANR1078E
Operation process process ID terminated internal server error detected.

server encounters an internal error.
ANR1079I
Server-free backup of node nodename,

file system file system, started as process
Explanation: The administrator initiates a server-free

backup of the node's file system.
ANR1080W
Space reclamation is ended for volume

volume name. The process is canceled.
Explanation: During space reclamation for the

indicated volume, the process performing the
reclamation has been canceled.
System action: Space reclamation of the volume stops.

If other reclamation processes are running, these
User response: Restart the operation.
ANR1076E
Operation process process ID terminated sufficient memory is not available.
Explanation: During the indicated operation, not

enough server memory is available.
available to the server, and then restart the operation.
ANR1077E
Operation process process ID terminated transaction aborted.

server detected an error while attempting to commit a
transaction. This message should be preceded by other
messages that give additional information about the
failed transaction.
transaction.
ANR1081E

volume name. Storage media is
inaccessible.

indicated volume, a required volume cannot be
mounted.
If other reclamation processes are executing, these
ANR1082E

volume name. There is an insufficient
number of mount points available for
removable media.

indicated volume, the server could not allocate
sufficient mount points for the volumes required.
available.
173
ANR1083E ANR1091E
ANR1083E

volume name. Excessive read errors were
encountered.
ANR1087E

volume name. Sufficient recovery log
space is not available.

indicated volume, read errors occur that prevent
reclamation from continuing.

indicated volume, the server runs out of recovery log
space.

System action: Space reclamation stops.
User response: If possible, determine and correct the

cause of the read errors.
ANR1084E

volume name. Excessive write errors were
encountered.

indicated volume, write errors occur that prevent
reclamation from continuing.
cause of the write errors.
ANR1085E

volume name. Data transfer was
interrupted.

indicated volume, a data transfer operation has been
interrupted and cannot be continued.

ANR1088E

indicated volume, the server runs out of database
space.
System action: Space reclamation stops.
ANR1089E

volume name. There is insufficient space
in storage pool.

indicated volume, the server determines that data
cannot be moved from the volume due to insufficient
space on other volumes in the storage pool.

volume name. There is a lock conflict.

indicated volume, the server needed to obtain a lock
that is not available.
User response: Wait for the server to try the
reclamation again.
ANR1090E

cause of the interruption.
ANR1086E

volume name. Sufficient database space is
not available.

volume name. Thread resource is not
available.

indicated volume, the server cannot start a thread for
the reclamation process.
User response: Wait for the server to try the
reclamation again. If the error persists, it might indicate
a shortage of server memory.
ANR1091E
User response: Make more space available on other

volumes in the storage pool.

volume name. Sufficient memory is not
available.

indicated volume, there was not enough server
memory available.
174
ANR1092E ANR1097E
v The storage pool is not a NONBLOCK data format,

which is required for server-free operations

v The data format of the storage pool does not match

the data format of the data mover
ANR1092E

volume name. An internal server error
was detected.

indicated volume, the server encounters an internal
error.
the activity log and to look for messages that indicate
the source of the error. Correct any errors that might
have caused the space reclamation to fail and try the
operation again.
ANR1093E

volume name. The transaction is ended.

indicated volume, the server detected an error while
attempting to commit a transaction.
transaction.
ANR1094E
Invalid destination storage pool storage

pool name specified for storage of an
object using data mover data mover.
Explanation: While attempting to store an object using

the indicated data mover, the server determined that
the indicated storage pool was invalid for this
operation. The indicated storage pool is used because it
is specified as the copy group destination of the
assigned management class.
This storage pool could be invalid for any of the
following reasons:
v The storage pool is not defined
v The storage pool is a random-access storage pool and
this operation requires a sequential-access storage
pool
v The storage pool is not a primary storage pool
v The storage pool has a NATIVE or NONBLOCK data
format, which is not supported for this operation
User response: This message usually indicates a

configuration problem with either the storage pool or
the policy. Ensure that the destination storage pool has
appropriate attributes, including data format, for this
operation. Check the copy group of the assigned
management class. If the destination is incorrect, either
assign a new management class, or change the
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
be started - an operation involving this
node and file space is already in
progress.
Explanation: A request has been made to use a data

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
data mover operation involving that node and file
space is already in progress; the indicated file space is
either the source for a currently running backup
operation or is the destination for a currently running
restore operation. To avoid possible conflicts, the new
operation is not performed.
User response: Allow the current operation to
complete before starting a new operation for this node
and file space.
ANR1096E
Operation process process ID terminated storage media inaccessible.
Explanation: During the indicated operation, a

required volume cannot be mounted.
User response: If possible, correct the problem and
restart the operation.
ANR1097E
Operation process process ID terminated data transfer interrupted.
Explanation: During the indicated operation, a data

transfer operation is interrupted and cannot be
continued.
User response: If possible, correct the problem and
restart the operation.
175
ANR1098E ANR1106W
ANR1098E
Operation process process ID terminated file deleted from data storage during
retrieval.
Explanation: During the indicated operation, a file

was deleted from data storage during retrieval.
ANR1099E
Operation process process ID terminated thread resource not available.

server cannot start a thread.
User response: The problem may indicate a shortage
of memory. If necessary, make more memory available
to the server, and then restart the operation.
ANR1100I
Migration started for volume volume

name, storage pool storage pool name
(process number process ID).
Explanation: Because the high migration threshold for

the indicated storage pool has been exceeded,
migration of files from the volume shown begins.
ANR1103E
Explanation: During the indicated operation,

input/output errors were encountered which prevent
the operation from continuing.
User response: Check previous messages for problem
determination information.
ANR1104E

User response: 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, if possible, correct the cause of
the errors and restart the operation.
ANR1106W

Migration ended for volume volume
name.
Explanation: Because the low migration threshold for

the indicated storage pool has been reached, migration
of files from the indicated volume ends.
ANR1102I

required for migration.
Explanation: During migration processing, the server

determines that a removable volume is required in
order to complete processing.
removable volume.
indicated volume.
176
Operation process process ID terminated NAS datamover NAS datamover name

reported NDMP session errors.

NDMP session with the NAS file server reported errors
which prevent the operation from continuing.
System action: The system moves the data from this

volume to the next (target) pool.
ANR1101I
Operation process process ID terminated server-free input/output errors

encountered.
An incorrect destination storage pool

storage pool name was specified for
storing a table of contents for an image.
A table of contents will not be created
for the image.
Explanation: While attempting to store an image

object, the server determined that the indicated table of
contents (TOC) destination storage pool was invalid.
The indicated storage pool is used because it is
specified as the copy group TOC destination of the
following reasons:
v The storage pool has a data format other than
NATIVE or NONBLOCK
System action: The operation continues because TOC
creation is preferred, but not required. A TOC will not
be created for the stored image object.
the policy. Ensure that the TOC destination storage
pool has appropriate attributes, including data format.
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
in the copy group and activate the changed policy.
ANR1107E ANR1112W
ANR1107E
An incorrect destination storage pool

storage pool name was specified for
storage of a table of contents for an
image object. The backup operation
fails.
Explanation: While attempting to store an image

object, the server determined that the indicated table of
contents (TOC) destination storage pool was invalid.
The indicated storage pool is used because it is
specified as the copy group TOC destination of the
following reasons:
v The storage pool has a data format other than
NATIVE or NONBLOCK
the policy. Ensure that the TOC destination storage
pool has appropriate attributes, including data format.
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
in the copy group and activate the changed policy.
ANR1108W
The server is unable to create a table of

contents for node node name, file space
file space in storage pool storage pool name.
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.
problem with the policy. Either assign a new

management class with appropriate attributes, or
correct the assigned management class by setting the
TOC destination in the backup copy group and
activating the changed policy.
ANR1110E
Command: A table of contents was

requested, but there is no table of
contents destination storage pool
specified. The table of contents can not
be created and the operation fails.
Explanation: While preparing to create a table of

contents (TOC), the server determined that the TOC
destination storage pool is not specified in the backup
copy group for the assigned management class.
User response: This message indicates a configuration
activating the changed policy. If a TOC is not required,
change the value of the TOC parameter on the
command.
ANR1111E
Command: An incorrect message number,

message number, was specified.
Explanation: A MSGSTACKTRACE ENABLE or

MSGSTACKTRACE DISABLE command has been
entered that specifies an invalid message number.
Messages must be between 3 and 8 digits. No letters
are allowed on message numbers.
command.

be created for the stored image object.

message number.
User response: Look for previous messages giving a

specific reason for the failure. Take corrective action as
appropriate.
ANR1112W
ANR1109W
Command: A table of contents was

requested, but there is no table of
contents destination storage pool
specified. The table of contents will not
be created, but the operation continues.

be created.
Command: No table of contents

destination storage pool available for
backup set for node Node name (data
type data type). The table of contents
will not be created.

be created.
activating the changed policy.
177
ANR1113E ANR1121E
ANR1113E
Command: No table of contents

destination storage pool available for
backup set for node Node name (data
type data type). The backup set will not
be generated.

activating the changed policy. If a TOC is not required,
change the value of the TOC parameter on the
command.
ANR1117W
Error initiating migration for storage

pool storage pool name - internal server
error detected.
Explanation: While trying to start migration for the

indicated storage pool, the server encounters an
internal error.
System action: Migration stops. The server waits for
the retry period to expire and then tries the migration
again.
ANR1118I
Command: Table of contents successfully

generated for node Node name, backup
set backup set name.
Explanation: You requested a table of contents to be

generated for the specified backup set and data type.
The table of contents was successfully generated.
ANR1114E
Command: No nodes or data types are

eligible for a backup set operation.
Explanation: None of the specified nodes or data

types are eligible to be included in the backup set for
the GENERATE BACKUPSET or DEFINE BACKUPSET
command.

ANR1119W
Command: Table of contents already

exists for node Node name, backup set
backup set name (data type data type). The
table of contents will not be created.
User response: Check previous messages for problem

determination information.
Explanation: You requested a table of contents to be

generated for the specified backup set and data type,
but the table of contents already exists.
ANR1115W
System action: The server will not generate a table of

contents for this backup set and data type.

pool storage pool name - lock conflict.

indicated storage pool, the server needs to obtain a lock
that is not available.
again.
User response: If the specified backup set name and

data type are not correct, re-issue the command with
the correct parameters.
ANR1120W
Migration is ended for volume volume

name. The process is canceled.

migration.

volume, the process performing the migration has been
canceled.
ANR1116W
System action: The migration process stops. If other

migration processes are running, these processes will
continue migration.

pool storage pool name - sufficient

indicated storage pool, there is not enough server
memory available.
ANR1121E

again.

volume a required volume cannot be mounted.

System action: Migration of the volume stops. If other

continue migration.
178

name - storage. Media is inaccessible.
ANR1122E ANR1129E
User response: One possible cause for this failure is
that the access state for the target volume or storage
pool for this operation is not set to READWRITE.
Check the access state for the requested output volume
and storage pool and ensure they are set to
ACCESS=READWRITE.
ANR1122E

name. An insufficient number of mount
points are available for removable
media.

volume the server could not allocate sufficient mount
points for the volumes required.
continue migration.
available.
ANR1123E

name. Excessive read errors were
encountered.

volume, read errors occurred that prevent the migration
from continuing.
continue migration.
read errors.
ANR1124E

name. Excessive write errors were
encountered.

volume, write errors occurred that prevent the

ANR1126E

name. There is insufficient space in
subordinate storage pools.

volume because there is not enough space on the next
storage pool to hold it.
continue migration.
storage pool, or use the UPDATE STGPOOL command
to change the next storage pool to one with more space.
ANR1127E

name. - The server is unable to move
files to subordinate storage pools
because the files are too large.

volume because a file size is larger than allowed on the
next storage pool.
continue migration.
change the next storage pool target.
ANR1128E

name. Sufficient recovery log space is
not available.

volume, the server runs out of recovery log space.
System action: Migration stops.

continue migration.


write errors.
ANR1129E
ANR1125E

name. Data transfer is interrupted.

volume a data transfer operation was interrupted and
could not be continued.
continue migration.

name. Sufficient database space is not
available.

volume pool, the server runs out of database space.
179
ANR1130E ANR1138I
ANR1130E

name. There is a lock conflict.

volume, the server needs to obtain a lock that is not
available.
continue migration.
User response: Wait for the server to try the migration
again.
ANR1131E

name. A thread resource is not available.

volume, the server cannot start a thread for the
migration process.
continue migration.
User response: Wait for the server to try the migration
again. If the error persists, it might indicate a shortage
of server memory.
ANR1132E

name. Sufficient memory is not
available.

volume, there is not enough server memory available.
ANR1133E

name. An internal server error is
detected.

volume, the server encounters an internal error.
continue migration.

again.
available.
ANR1135E

name. The transaction is ended.

volume, the server detected an error while attempting
to commit a transaction.
continue migration.
transaction.
ANR1136W
Operation process process ID completed There is no data to process for the

differential backup of NAS node node
name, file space file space.
Explanation: The NAS file server reported zero bytes

stored at the conclusion of an NDMP backup of the
specified file space. The command ends without
updating the server's database.
ANR1137E
Operation process process ID terminated object excluded by size in destination

storage pool and all successor pools.
Explanation: During the indicated operation, the size

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.
User response: Increase the maximum file size for one
or more of the storage pools in the storage hierarchy to
accommodate the file. An authorized administrator can
increase the MAXSIZE parameter by issuing the
UPDATE STGPOOL command.

ANR1138I
ANR1134E
Migration is ended for storage pool

storage pool name. There is an insufficient
removable media.

storage pool the server could not allocate sufficient
mount points in the next storage pool.
180
entries were created for the no-query

restore with timestamp timestamp.
Explanation: The no-query restore operation identified

by the timestamp now has the indicated number of
entries in the Restore.Srvobj table. This no-query restore
operation continues to find restore candidates until the
server issues message ANR1183I.
User response: This informational message reports
that the no-query restore operation is still searching for
ANR1139E ANR1146W
candidates. You can cancel the restore operation by
issuing the CANCEL RESTORE or CANCEL SESSION
command.
ANR1139E
The command name command failed

because some data was missing.
Explanation: An attempt to gather database statistics

from the database manager failed. This failure can
occur if either of these conditions is met:
v
The buffer pool monitor switch

(DFT_MON_BUFPOOL) has been set to 'OFF.' The
buffer pool monitor switch controls the collection of
database statistics.
The file systems or drives are in a remote network.
There might be a network problem causing the
server fail to collect the statistics of those volumes.

ANR1143W
Move data process terminated for

volume volume name - process canceled.
Explanation: During move data processing for the

indicated volume, the process performing the move
data was canceled. It is possible that the server may
issue this message more than once while the server is
ending this process.
System action: The server ends the MOVE DATA
command.
ANR1144W
System action: The command fails, and the server


volume volume name - storage media
inaccessible.
User response: Take one of the following actions, and

then try running the QUERY DBSPACE command
again:

indicated volume, a required volume cannot be
mounted.
v Stop and restart the server.

command.
v Set the buffer pool monitor switch to 'ON' using this

DB2 command: 'db2 update db cfg using
DFT_MON_BUFPOOL ON'.
v If you cannot obtain drive or file system statistics by
running operating system commands, fix the
problem, then try running the command again.
ANR1140I
Move data process started for volume

volume name (process ID process ID).
Explanation: As a result of a MOVE DATA command,

a process begins to move data from the volume shown.
System action: The server moves all data from the
volume.

ANR1145W

volume volume name - insufficient
removable media.

indicated volume, the server could not allocate
sufficient mount points for the volumes required.
command.

available.
ANR1141I
ANR1146W
Move data process ended for volume

volume name.
Explanation: The MOVE DATA command for the

volume shown completes.
ANR1142I
Moving data for collocation cluster

cluster number of total clusters on volume
volume name.
Explanation: As a result of a MOVE DATA command,

data moves from the volume indicated to new volumes;
the message shows the total number of clusters (data
objects) on the volume and the current cluster being
processed.

volume volume name - excessive read
errors encountered.

indicated volume, read errors occurred that prevented
the move from continuing.
command.
read errors and then reissue the MOVE DATA
command.
181
ANR1147W ANR1154W
ANR1147W

volume volume name - excessive write
errors encountered.
ANR1151W

volume volume name - sufficient recovery
log space is not available.

indicated volume, write errors occurred that prevented
the move from continuing.

indicated volume, the server runs out of recovery log
space.

command.

command.

write errors and then reissue the MOVE DATA
command.

ANR1152W
ANR1148W

volume volume name - data transfer
interrupted.

indicated volume a data transfer operation was
interrupted and could not be continued.
command.

indicated volume, the server runs out of database
space.
command.
ANR1153W
ANR1149W

volume volume name - insufficient space
in target storage pool.

indicated volume, the server cannot move the data
from the volume, because there is not enough space on
the destination storage pool to hold it or the access for
the storage pool is either unavailable or readonly.
command.
storage pool, or specify a storage pool with more space,
and reissue the MOVE DATA command.
ANR1150W

volume volume name - unable to move
file to target storage pool due to
exclusion by size.

indicated volume, the server cannot move the data
from the volume because a file size is larger than
allowed on the next storage pool.
System action: The server ends the MOVE DATA or
MOVE NODEDATA command.
change the next storage pool target, and then reissue
the MOVE DATA or MOVE NODEDATA command.
182

volume volume name - sufficient database

volume volume name - lock conflict.
Explanation: During move data processing, the server

was unable to obtain the volume specified because a
lock was not available or a restartable restore is active
for data on the volume and has it locked. .
command.
User response: Check for restartable restores by
issuing the QUERY RESTORE command. If the volume
specified contains any data from the node and filespace
identifed by the QUERY RESTORE command, the
MOVE DATA command will fail. The restartable
restores must complete or be cancelled before the
MOVE DATA command can succeed.
If the volume does not contain data from the node and
filespace identified by the QUERY RESTORE command,
the reissue the MOVE DATA command.
ANR1154W

volume volume name - thread resource
not available.

indicated volume, the server cannot start a thread for
the migration process.
command.
User response: Reissue the MOVE DATA command. If
the error persists, it may indicate a shortage of server
memory.
ANR1155W ANR1163W
ANR1155W

volume volume name - sufficient memory
is not available.

indicated volume, there is not enough server memory
available.
command.
available to the server, and then reissue the MOVE
DATA command.
ANR1156W

volume volume name - internal server
error detected.

indicated volume, the server encounters an internal
error.
encountered that was previously found to be damaged.

If this file is part of an aggregate, the entire aggregate
was previously marked damaged, possibly because an
error was detected for some other file within the
aggregate.
System action: The damaged file is not moved.
User response: Perform the following actions:
v Audit the indicated volume with FIX=NO to verify
that the file is damaged. The audit 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 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,
attempt to restore damaged files by using the
RESTORE STGPOOL command.
ANR1162W

command.
ANR1157I

required for move process.
Explanation: During move data or move node data

processing, the server determines that the indicated
removable volume is required in order to complete
processing.
removable volume.
indicated volume.
ANR1160W
Transaction was aborted for volume

volume name.
Explanation: An error was detected during transaction

commit. This message should be preceded by other
failed transaction.
fails.
ANR1161W
The move process is skipping a

damaged file on volume volume name:
Node node name, Type file type, File space
filespace name, File name file name.
Explanation: During the move process, a file is
Space reclamation skipping damaged

file on volume volume name: Node node
name, Type file type, File space filespace
name, File name file name.
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
previously marked damaged, possibly because an
integrity error was detected for some other file within
the aggregate.
System action: The damaged file is not moved.
User response: Audit the indicated volume with
FIX=NO to verify that the file is damaged. The audit
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
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
restore damaged files by using the RESTORE
STGPOOL command.
ANR1163W
Offsite volume volume name still

contains files which could not be
moved.
Explanation: During processing of a MOVE DATA

command or reclamation, the server determined that
the indicated offsite volume contained one or more files
that could not be moved. One or more files could not
be copied from the other available volumes.
The server might not move some files if the storage
pool is collocated and the volume being moved or
reclaimed contains files that require different output
volumes. The server will skip these files and no
messages are issued identifying the skipped files. The
files are skipped to honor the collocation attribute of
the storage pool.
183
ANR1165E ANR1168W
If the files in the storage pool are deduplicated, they
could be skipped due to the unavailability of an on-site
copy. This can occur if the file has been logically
deleted from all other storage pools due to either policy
retention settings, or explicit deletion, but must remain
in the offsite storage pool due to deduplication
dependencies.
User response: Check for messages that indicate why
files could not be moved. To complete the move
operation, you have several options:
v Bring the volume back on-site and reissue a MOVE
DATA command to reclaim the volume. If the
storage pool is deduplicated and all primary storage
pool volumes are available, this is the recommended
solution.
v Make the primary volumes available and reissue a
MOVE DATA command to reclaim the volume.
v Delete the files by using the DELETE VOLUME
command.
If the server is skipping files to honor the collocation
attribute of the storage pool, run the MOVE DATA
command, or wait until reclamation runs again. In
either case, the server will move files to the appropriate
output volumes until the volume being moved or
reclaimed is empty. It might take more than one
attempt to totally empty the volume.
ANR1165E
Error detected for file in storage pool

storage pool name: Node node name, Type
file type, File space filespace name, fsId
filespace id, File name file name.
Explanation: The server has detected an error for the

indicated file.
System action: The file will be marked damaged in
the server database, and will not be accessed for future
operations. If this file is part of an 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 operations involving the file.
User response: If the indicated storage pool is a
primary pool, and a usable copy of the file exists in a
copy storage pool, you can recreate the file in the
primary pool using the RESTORE STGPOOL command.
If the indicated storage pool is a copy storage pool, it is
possible that the primary copy of the file is usable, but
was not accessed because the access mode for the
primary storage pool or volume is unavailable. If this is
the case, the primary copy of the file may be made
accessible by changing the access mode of the primary
pool or volume.
ANR1166E
Move Data for offsite volume cannot

copy damaged file in storage pool
storage pool name: Node node name, Type
file type, File space filespace name, fsId
filespace id, File name file name.
Explanation: A move data process for an offsite

volume cannot locate an undamaged copy of the
specified file 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 belongs.
System action: The file will skipped and will not be
moved from the offsite volume.
User response: The indicated storage pool is a
primary pool that contains a damaged copy of the file.
The only usable copy of the file may now only reside
on the offsite volume that was involved in the move
data process. If you bring this volume back onsite, you
can recreate the file in the primary pool by using the
RESTORE STGPOOL command. After the restore, you
can reissue the MOVE DATA command.
ANR1167E
Space reclamation for offsite volume

volume name cannot copy damaged file in
storage pool storage pool name: Node node
name,fsId filespace id , File name file name.
Explanation: A reclamation process of offsite volumes

cannot locate an undamaged copy of the specified file
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
belongs.
System action: The file is skipped and will not be
primary pool that contains a damaged copy of the file.
The only usable copy of the file may now only reside
on an offsite volume that was involved in the
reclamation process, but was not totally reclaimed. If
you bring this volume back onsite, you can recreate the
file in the primary pool by using the RESTORE
STGPOOL command.
ANR1168W
Migration skipping damaged file on

volume volume name: Node node name,
Type file type, File space filespace name,
fsId filespace id, File name file name.
Explanation: During migration, a file is encountered

that was previously found to be damaged. If this file is
part of an aggregate, the entire aggregate was
previously marked damaged, possibly because an
the aggregate.
System action: The damaged file will not be moved.
184
ANR1169W ANR1174W
FIX=NO to verify that the file is damaged. The audit
will reset the file status if the file is found to be
undamaged during the audit. If the file is part of an
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, you can also
attempt to restore damaged files by using the
ANR1169W
Lock conflict on movement of offsite

file - file is skipped.
Explanation: During migration, reclamation, or move

data processing of a volume that is offsite, a copy of
the file that resides in a primary disk storage pool is
locked by another process.
System action: The file is skipped and the process will
try to find another copy of the file in a copy storage
pool. If another copy cannot be used, the move
operation on the volume may be incomplete.
User response: If a move operation was incomplete,
try repeating the operation.
ANR1170E
Out of Space in target copy storage

pool: copy storage pool name.
Explanation: During reclamation, or move data

processing of a volume that is offsite, there was no
volume available in the specified target copy storage
pool.
command after the restore operation has completed in

order to move any remaining files.
ANR1172E
Explanation: A move data process for an offsite

volume cannot locate a copy of the specified file in any
storage pool accessible by the server. If this file is part
of an aggregate, the process could not locate copy of
the aggregate to which the file belongs on an accessible
volume.
System action: The file will skipped and will not be
primary pool that should contain a primary copy of the
file. Perhaps the volume on which that file resides is on
a destroyed volume. The only usable copy of the file
may now only reside on the offsite volume that was
involved in the move data process. If you bring this
volume back onsite, you can recreate the file in the
primary pool by using the RESTORE STGPOOL
command. After the restore, you can reissue the MOVE
DATA command.
ANR1173E
System action: The operation is terminated.

User response: Define volumes to the copy storage
pool or raise the MAXSCRATCH value.
ANR1171W
Unable to move files associated with

node node name, filespace filespace name
fsId filespace id on volume volume name
due to restore in progress.
Explanation: During movement of data (migration,

reclamation, move data) from a sequential volume, one
or more files were encountered that were locked by a
restore operation.
System action: The files are not moved, but are
skipped.
User response: Use the QUERY RESTORE
FORMAT=DETAILED command to determine if the
restore operation is active or is in restartable state. A
restartable restore operation will keep the files locked
from movement until the RESTOREINTERVAL is
reached. QUERY OPTION will display this interval.
You may wish to lower the RESTOREINTERVAL to
cause a restartable restore operation to be removed and
free up the locked files. The RESTOREINTERVAL is a
server option. If you received this message due to a
MOVE DATA operation, reissue the MOVE DATA
Move Data for offsite volume cannot

copy file in storage pool storage pool
name: Node node name, Type file type, File
space filespace name, fsId filespace id, File
name file name.
Space reclamation for offsite volume(s)

cannot copy file in storage pool storage
pool name: Node node name, Type file type,
File space filespace name, fsId filespace id,
File name file name.
Explanation: A reclamation process of offsite volumes

cannot locate a copy of the specified file in any storage
pool accessible by the server. If this file is part of an
aggregate, the process could not locate a copy of the
aggregate to which the file belongs on an accessible
volume.
System action: The file is skipped and will not be
primary pool that should contain a copy of the file.
Perhaps the volume on which that file resides is on a
destroyed volume. The only usable copy of the file may
now only reside on an offsite volume that was involved
in the reclamation process, but was not totally
reclaimed. If you bring this volume back onsite, you
can recreate the file in the primary pool by using the
ANR1174W
One or more cached files were not

deleted on volume volume name.
Explanation: The MOVE DATA command could not

delete one or more cached files on the disk volume
shown. Migration was probably running at the same
time, creating cached files while the MOVE DATA
185
ANR1175W ANR1182I
command was trying to delete them.
ANR1179I
System action: The MOVE DATA command ran to

completion.
User response: If you want the remaining cached files
removed from the disk volume, reissue the MOVE
DATA command.
ANR1175W
Volume volume name contains files which

could not be reclaimed.
Explanation: After reclamation of the indicated

volume, it still contains one or more files that could not
be reclaimed. These files were skipped because of read
errors, or because the files are marked damaged.
Explanation: A preview process has been started to

copy active data from a primary storage pool to the
indicated active data pool.
System action: Preview information about the COPY
ACTIVEDATA operation is collected and displayed, but
files are not copied.
ANR1180W
System action: The volume is marked unavailable so

it will not be chosen again for reclamation.
User response:
v Use the UPDATE VOLUME command to set the
volume access to readonly.
v Try using the MOVE DATA command to manually
reclaim the volume.
v If files still exist on the volume, audit the volume
using AUDIT VOLUME FIX=YES.
v Try using the MOVE DATA command again.
v Use the RESTORE VOLUME command to restore
files marked damaged.
Moving data for collocation set set
number of total sets on volume volume
name.
Explanation: As a result of a move operations, such as

MOVE DATA, MOVE NODEDATA, migration, or
reclamation, the server is moving data from the volume
indicated to new volumes. This message shows the
total sets of data on the volume to be processed.
Depending upon the collocation setting of the
destination storage pool, a set can be file spaces that
belong to the same collocation group, file spaces for a
node, or a single filespace.
ANR1178I
Copying active files from primary

storage pool primary pool name to active
data pool active data pool name started as
process process ID.
Access mode for volume volume name

has been set to "unavailable" due to file
read or integrity errors.
Explanation: During processing of a storage pool

volume, input/output or other errors occur that force
the server to mark the volume unavailable for further
processing.
System action: The server sets the volume status to
unavailable.
User response: Correct the errors that set the volume
to unavailable, or use the DELETE VOLUME command
to remove it from the system.
ANR1181E
ANR1176I
Preview of copying active files from

primary storage pool primary pool name to
active data pool active data pool name
Diagnostic(ID): Data storage transaction

transaction ID was aborted.
Explanation: A database transaction failed because of

an error that was detected during data storage
processing. This message should be preceded by other
failed transaction.
System action: The server operation that encountered
this error during data storage processing fails.
transaction.
ANR1182I

required for a restore request from
session session id.
System action: For every noncached, active file in the

primary pool, a copy is made in the active data pool, if
a copy of that file does not already exist.
Explanation: A restore request will need a removable

volume. This message is issued as soon as the server
determines that the volume will be needed. A mount
request will be made when the volume is actually
needed for processing. When the first pass
determination of needed volumes is complete, message
ANR1183I will be issued. However, it is possible that
additional volumes will be needed later, as indicated in
the explanation for message ANR1183I. This message is
not issued for DISK device class volumes nor is it
issued for FILE device class volumes.
System action: The server continues processing.
Explanation: A process has been started to copy active

data from a primary storage pool to the indicated
active data.
186
ANR1183I ANR1212I
indicated volume.

ANR1189I
ANR1183I
Initial determination of removable

volumes required for a restore request
from session session id is complete.
Additional volumes may still be
required.
Explanation: The first pass determination of needed

volumes is complete for the indicated restore session. It
is possible that additional volumes will be needed as
individual objects are restored. This can happen for a
variety of reasons. Examples of such reasons include: 1.
An object spanning from one volume to another, where
the second volume is not needed for any other objects
during this restore session. 2. An object is found to be
damaged and a copy storage pool volume is needed to
complete the restore. 3. A volume is unavailable and a
copy storage pool volume is needed to complete the
restore.
System action: The server continues processing.
User response: Respond to any mount request for any
additional volumes.
ANR1184I
Copy active data process process ID

ended for storage pool storage pool name.
Explanation: During processing of a COPY

ACTIVEDATA 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.
indicated volume.
ANR1199I

removable volume.
indicated volume.
ANR1210I
Backup of primary storage pool primary

pool name to copy storage pool copy pool
name started as process process ID.
Explanation: A process has been started to back up a

primary storage pool to the indicated copy storage
pool.

Copy active data process process ID
terminated for storage pool storage pool
name - process canceled.
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
executing for the named storage pool, these processes
continue.
ANR1186I

required for audit process.
Explanation: During audit volume processing for the

indicated volume, the server determines that a
removable volume is required in order to complete
processing.
Explanation: A COPY ACTIVEDATA process for the

named primary storage pool has ended.
ANR1185I

required for copying active data.
Restore of node nodename, file system file

system, started as process process ID by
administrator administrator. A full image
for this file system will be restored to
destination destination.
Explanation: The administrator initiates a restore of

the node's file system. The restore will be performed
using a full image of this file system. The file system
will be restored to the indicated destination.
System action: For every noncached file in the

primary pool, a backup copy is made in the copy pool,
if a copy of that file does not already exist.
ANR1211I
Backup preview of primary storage pool

primary pool name to copy storage pool
copy pool name started as process process
ID.

back up a primary storage pool to the indicated copy
storage pool.
System action: Preview information about the backup
operation is collected and displayed, but files are not
backed up.
ANR1212I
Backup process process ID ended for

Explanation: A backup process for the named primary

storage pool has ended.
187
ANR1213I ANR1221E
ANR1213I
Backup process process ID terminated for

storage pool storage pool name - process
canceled.
Explanation: During backup of the indicated primary

storage pool, a process performing the backup has been
canceled.

available. To prevent sessions or processes from having
to wait for a mount point, increase the value of the
MOUNTLIMIT parameter in the device-class definition.
Set the value of the MOUNTLIMIT parameter high
enough to allow all server processes using deduplicated
storage pools to open the number of volumes specified
by the NUMOPENVOLSALLOWED option.
Command: Process process ID terminated excessive read errors encountered.
System action: If other backup processes are executing

for the named storage pool, these processes continue.
ANR1218E
Explanation: During backup processing, read errors

occur that prevent the backup from continuing.
ANR1214I
Backup of primary storage pool primary

pool name to copy storage pool copy pool
name has ended. Files Backed Up:
number of files, Bytes Backed Up: number
of bytes, Unreadable Files: number of
unreadable files, Unreadable Bytes: number
of bytes in unreadable files.
System action: The indicated backup process ends.

read errors and reissue the backup command.
ANR1219E
Command: Process process ID terminated excessive write errors encountered.
Explanation: Backup processing for the specified

storage pool has ended with the results shown.
Explanation: During backup processing, write errors

User response: Examine previous messages to

determine whether all backup processes ended
successfully.

write errors and reissue the backup command.
ANR1220E
ANR1215I
Backup preview of primary storage pool

primary pool name to copy storage pool
copy pool name has ended. Files Backed
Up: number of files, Bytes Backed Up:
number of bytes.
Explanation: Backup preview processing for the

specified storage pool has ended with the results
shown.
Command: Process process ID terminated data transfer interrupted.
Explanation: During backup processing, a data

transfer operation was interrupted and could not be
continued.
interruption and reissue the backup command.

ANR1216E
Command: Process process ID terminated storage media inaccessible.
Explanation: During backup processing, a required

volume could not be mounted.
ANR1217E
Command: Process process ID stopped insufficient number of mount points

Explanation: During backup processing, the server

could not allocate sufficient mount points for the
volumes required.
ANR1221E

cannot copy data to the specified copy or active-data
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
unavailable or readonly.
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
space.
188
Command: Process process ID terminated insufficient space in target storage pool

pool name.
ANR1222E ANR1229W
ANR1222E
Command: Process process ID terminated sufficient recovery log space is not

available.

runs out of recovery log space.
ANR1223E
Command: Process process ID terminated sufficient database space is not

available.

runs out of database space.

ANR1228I

required for storage pool backup.
Explanation: During processing of a BACKUP

STGPOOL command, the server determines that a
removable volume is required.
indicated volume.

ANR1224E
Command: Process process ID terminated lock conflict.
ANR1229W
Volume volume name cannot be backed

up to a copy storage pool or copied to
an active-data storage pool.- the volume
is offline, in use by another process, not
currently mountable, or access mode is
"unavailable" or "destroyed".
Explanation: During storage pool backup or the

copying of active data, the contents of a volume cannot
be backed up or copied if one of the following
conditions exists:
User response: Reissue the backup command.
v The volume is offline.

v The volume is in use by another process.

ANR1225E
Command: Process process ID terminated thread resource not available.

cannot start a thread.
User response: Reissue the backup command. If the
error persists, it may indicate a shortage of server
memory.
ANR1226E
Command: Process process ID terminated sufficient memory is not available.
Explanation: During backup processing, not enough

server memory is available.
available to the server, and then reissue the backup
command.
ANR1227E
Command: Process process ID terminated internal server error detected.

encounters an internal error.
v The volume cannot be be mounted.

v The access mode of the volume does not allow the
operation.
System action: The server continues backup
processing, but skips the indicated volume.
User response: Take one of the following actions:
v If the volume is offline, issue the VARY ONLINE
command for the indicated volume.
v If the access mode of the volume is unavailable, issue
the UPDATE VOLUME command to change the
access mode to readwrite or readonly. If the access
mode of the volume is destroyed, verify with an
administrator whether the access mode should be
updated. If it should, issue the UPDATE VOLUME
command to change the access mode to readwrite or
readonly.
v If the volume is in use by another process, wait for
that process to complete, and then retry the BACKUP
STGPOOL command or the COPY ACTIVEDATA
command.
v If the volume is not currently mountable, verify that
the drive can mount the volume, and then retry the
BACKUP STGPOOL command or the COPY
ACTIVEDATA command.
189
ANR1230I ANR1238I
ANR1230I
Restore of primary storage pool primary

pool name started as process process ID.
ANR1234I
Restore process process ID ended for

Explanation: A process has been started to restore the

indicated primary storage pool.
Explanation: A restore process for the named primary

System action: Non-cached files that reside in the

named primary storage pool are restored if either of the
following criteria are met:
v The file is stored on a volume whose access mode is

destroyed

ANR1235I
v The primary file has been identified as having

data-integrity errors during a previous operation
ANR1231I
Restore preview of primary storage pool

primary pool name started as process
process ID.

restore a primary storage pool.
System action: Preview information about the restore
restored. The restore preview includes noncached files
that reside in the specified primary storage pool and
that meet either of the following conditions:
v The file is stored on a volume whose access mode is
destroyed
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
Restore process process ID terminated for

storage pool storage pool name - process
canceled.
Explanation: During restore of the indicated primary

storage pool, a process performing the restore has been
canceled.
System action: If other restore processes are executing
for the named storage pool, these processes continue.
v The primary file has been identified as having

data-integrity errors during a previous operation
ANR1237I
ANR1232I
Restore of volumes in primary storage

pool primary pool name started as process
process ID.
Explanation: A process has been started to restore one

or more volumes in the indicated primary storage pool.
System action: Noncached files that reside on selected
volumes in the primary storage pool are restored.
ANR1233I
Explanation: During restore of volumes in the

indicated primary storage pool, a process performing
the restore has been canceled.
System action: If other restore processes are executing
for the volumes, these processes continue.
ANR1238I
Restore preview of volumes in primary

storage pool primary pool name started as
process process ID.

restore one or more volumes in the indicated primary
storage pool.
System action: Preview information about the restore
restored. The restore preview includes noncached files
that reside on selected volumes in the primary storage
pool.
Restore of primary storage pool primary

pool name has ended. Files Restored:
number of files, Bytes Restored: number of
bytes, Unreadable Files: number of
Explanation: Restore processing for the specified

determine whether all restore processes ended
successfully.
190
Restore process process ID terminated for

volumes in storage pool storage pool name
- process canceled.
ANR1239I ANR1248E
ANR1239I
Restore preview of primary storage pool

primary pool name has ended. Files
Restored: number of files, Bytes Restored:
number of bytes.
Explanation: Restore preview processing for the

shown.
System action: The indicated restore process ends.

available.
ANR1244E
Command: Process process ID terminated excessive read errors encountered.
Explanation: During restore processing, read errors

occur that prevent the restore from continuing.
ANR1240I

read errors and reissue the restore command.
Restore of volumes in primary storage

pool primary pool name has ended. Files
Restored: number of files, Bytes Restored:
number of bytes, Unreadable Files: number
of unreadable files, Unreadable Bytes:
number of bytes in unreadable files.
Explanation: Restore processing for volumes in the

shown.
ANR1245E
Command: Process process ID terminated excessive write errors encountered.
Explanation: During restore processing, write errors


write errors and reissue the restore command.

determine whether all restore processes ended
successfully.
ANR1246E
ANR1241I
Explanation: During restore processing, a data transfer

operation was interrupted and could not be continued.
Restore preview of volumes in primary

storage pool primary pool name has
ended. Files Restored: number of files,
Bytes Restored: number of bytes.
Explanation: Restore preview processing for volumes

in the specified storage pool has ended with the results
shown.

interruption and reissue the restore command.
ANR1247E

ANR1242E
Command: Process process ID terminated storage media inaccessible.
Explanation: During restore processing, a required

volume could not be mounted.
User response: Verify that the copy and primary
storage pools and volumes being accessed are available.
Check the ACCESS parameter for both of the storage
pools and all related volumes to ensure the ACCESS
state is not preventing access.
ANR1243E
Command: Process process ID terminated insufficient number of mount points

Explanation: During restore processing, the server

could not allocate sufficient mount points for the
volumes required.
Command: Process process ID terminated data transfer interrupted.
Command: Process process ID terminated insufficient space in target primary

storage pool.

cannot copy data to the target primary storage pool,
because not enough space is available in the target
pool.
User response: Make more space available in the
target primary storage pool, and then reissue the
restore command.
ANR1248E
Command: Process process ID terminated sufficient recovery log space is not

available.

runs out of recovery log space.
191
ANR1249E ANR1256W
ANR1249E
Command: Process process ID terminated sufficient database space is not

available.

runs out of database space.
ANR1250E
Command: Process process ID terminated lock conflict.


indicated volume.
ANR1255W
Files on volume volume name cannot be

restored - access mode is "unavailable"
or "offsite".
Explanation: During processing of a RESTORE

STGPOOL or RESTORE VOLUME command, files on a
copy storage pool volume cannot be restored because
of the volumes access mode.
System action: The server continues restore
processing, but skips the indicated volume.
User response: If the volume is stored at an offsite
location, bring the volume onsite. Use the UPDATE
VOLUME command to change the access mode for the
volume and restart the restore command.
User response: Reissue the restore command.

ANR1256W
ANR1251E
Command: Process process ID terminated thread resource not available.

cannot start a thread.
User response: Reissue the restore command. If the
error persists, it may indicate a shortage of server
memory.
ANR1252E
Command: Process process ID terminated sufficient memory is not available.
Explanation: During restore processing, there is not

enough server memory available.
available to the server; and then reissue the restore
command.
ANR1253E
Command: Process process ID terminated internal server error detected.

encounters an internal error.
ANR1254I

required for restore processing.

STGPOOL or RESTORE VOLUME command, the server
determines that a removable volume is required.

STGPOOL or RESTORE VOLUME command, the server
determines that the indicated volume contains one or
more files that could not be restored. If this is a
preview operation, this message indicates that a
restorable backup copy cannot be found for one or
more files on the indicated volume. If this is an actual
restore operation, this message could result if any of
the following conditions exist for a file on the indicated
volume:
v A restorable backup copy cannot be found for the
file.
v A restorable backup copy of the file exists, but is
located on a copy storage pool volume whose access
mode is unavailable or offsite.
v During restore processing, a backup copy was
selected for restore processing, but was deleted or
moved before the file was actually restored. This
action could occur as a result of MOVE DATA,
DELETE VOLUME, AUDIT VOLUME FIX=YES, or
reclamation processing of a copy storage pool
volume while the restore was in progress.
v A restorable backup copy of the file exists, but is on
a copy storage pool volume that cannot be accessed
since no drive path exists.
User response: If this was an actual restore operation,
check for messages indicating that files could not be
restored because a copy storage pool volume was
unavailable or offsite. Check to see if a move data,
delete volume, audit volume, or reclamation process
occurred for a copy storage pool while the restore was
in progress. If either of these conditions existed, correct
the situation and reissue the restore command.

192
Volume volume name contains files that

could not be restored.
ANR1257W ANR1264I
ANR1257W
Storage pool backup skipping damaged

name, fsId filespace id, File name file name.
Explanation: During storage pool backup, a file is

encountered that was previously found to be damaged.
If this file is part of an aggregate, the entire aggregate
was previously marked damaged, possibly because an
the aggregate.
System action: The damaged file will not be backed
up.
FIX=YES. The audit will verify whether or not the file
is damaged and perform one of the following actions:
v If the the file is found to be undamaged, the audit
will reset the file status. If the file is part of an
the entire aggregate is found to be undamaged.
v If the file is found to be damaged and the file had
not previously been backed up to a copy storage
pool, the audit will delete the file.
v If the file is found to be damaged and the file has
previously been backed up to a copy storage pool,
the audit will report the file as damaged and you
must use the RESTORE STGPOOL command to
recover the file.
ANR1258W
Files on volume volume name needed for

move data cannot be accessed - access
mode is "unavailable", "offsite", or
"destroyed".
Explanation: During a move data operation, files on a

storage pool volume cannot be copied because of the
volumes access mode. The server cannot move data on
a volume that has an access mode of "unavailable",
"offsite", or "destroyed".
System action: The server continues move data
processing, but one or more files were not moved from
the volume.
User response: If the specified volume can be made
available, use the UPDATE VOLUME command to
change the access mode for the volume and reissue the
MOVE DATA or MOVE NODEDATA command.
ANR1259W
Files on volume volume name needed for

offsite reclamation cannot be accessed access mode is "unavailable" or "offsite".
Explanation: During reclamation processing of an

offsite volume, files on a storage pool volume cannot
be copied because of the volumes access mode.
System action: The server continues reclamation, but
one or more files were not moved from an offsite
volume, which prevents it from being reclaimed.
User response: If the specified volume can be made

available, use the UPDATE VOLUME command to
change the access mode for the volume and initiate
reclamation again by updating the reclamation
threshold for the copy storage pool.
ANR1260W
Volume volume name contains one or

more damaged, primary files.
Explanation: This message is issued during RESTORE

STGPOOL processing. The indicated volume contains
one or more primary, noncached files that have
previously been found to be damaged.
System action: If this is not a preview operation, the
restore processing attempts to restore the damaged files
from copies located in a copy storage pool. If this is a
preview operation, no system action is taken.
User response: You can take the following actions:
v Issue the QUERY CONTENT command with
DAMAGED=YES to obtain a list of damaged files on
the indicated volume.
v Audit the indicated volume with FIX=NO to verify
that the files are damaged; the audit will reset the
status of any files that are found to be undamaged
during the audit.
v If this message was issued during a restore preview
operation, attempt to restore the damaged files using
the RESTORE STGPOOL command.
v Audit the indicated volume with FIX=YES to delete
the damaged files from the database.
ANR1263I
command: Processing completed

successfully.

command command has completed successfully.
System action: Processing for the command
completes. Statistics on the number and type of objects
message.
ANR1264I

completion.

message.
193
ANR1265E ANR1273I
ANR1265E
Salvage volume command: Processing

data storage.

in accessing data storage while executing a salvage
volume operation.
resolve the error, retry the operation. If you cannot find
the error, contact your service representative for
assistance in resolving the problem.
ANR1266E
Salvage volume command: Processing

terminated abnormally - volume not a
storage pool volume.

in accessing data storage while executing a salvage
volume operation.The error occurred because an
attempt has been made to access a volume that was not
a storage pool volume.
volume name.
ANR1267I
Salvage volume command: Processed

number volume(s).

command Salvage volume command inspected number
input volumes.
System action: Salvage processing for the command
completes. Server operation continues.

ANR1270I
Salvage volume command: File (internal file

identifierinternal file identifier) recovered.

command Salvage volume command recovered a file. The
new file was given a new, system generated name
based on the internal file identifier and the name of the
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.
ANR1271I
Salvage volume command: * number bytes

recovered from volume volume.

command Salvage volume command recovered a file from
the volume volume. The number of bytes recovered from
the volume is listed.
ANR1272I
Salvage volume command: * File is

complete - it began and ended on
volume volume.

the volume volume. The file was completely contained
on volume.
ANR1268I
Salvage volume command: Recovered

number byte(s).

command Salvage volume command recovered number
bytes worth of data.
ANR1269I
Salvage volume command: Recovered

number file(s).

command Salvage volume command recovered number
files.
194
ANR1273I

incomplete - it began on volume volume
but did not end.

the volume volume. The file was not completely
contained on volume. Although the file began on this
volume, it spanned out to a different volume.
ANR1274I ANR1282I
ANR1274I

incomplete - it ended on volume volume
but did not begin there.

contained on volume. Although the file ended on this
volume, it spanned in from a different volume.

incomplete - it did not began or end on
volume volume.

contained on volume. It spanned in from one volume
and spanned out to a another.
ANR1276E
Command: Process terminated - sufficient

Explanation: During salvage processing, not enough

server memory is available.
System action: The salvage process ends.
available to the server, and then reissue the salvage
command.
ANR1277E
Command: Process terminated - the

default management class in the active
policy set in policy domain domain name
does not contain an archive copy group.
Unable to continue with salvage.

command Salvage volume command was unable to
recover any files because the default management class
in the active policy set in policy domain does not contain
an archive copy group.
System action: The salvage process ends.
User response: Add an archive copy group to the
default management class in the active policy set of the
specified domain, and then reissue the salvage
command.
Occupancy is incorrect for storage pool

storage pool name. Occupancy is being
reset.
Explanation: The server has detected incorrect

occupancy information.
System action: The server recalculates the occupancy
value based on current storage pool information.
ANR1279I

ANR1275I
ANR1278I
Occupancy is incorrect for volume name

volume name. Occupancy is being reset.
Explanation: The server has detected incorrect

System action: The server recalculates the occupancy
value based on current sequential volume information.
ANR1280E
Command: Process process ID terminated transaction aborted.

detected an error while attempting to commit a
failed transaction.
transaction.
ANR1281E
Command: Process process ID terminated transaction aborted.

detected an error while attempting to commit a
failed transaction.
transaction.
ANR1282I
Logical occupancy is incorrect for

storage pool storage pool name. Logical
occupancy is being reset.
Explanation: The server has detected incorrect logical

System action: The server recalculates the logical
occupancy value based on current storage pool
information.
195
ANR1283I ANR1294I
ANR1283I
File count is incorrect for storage pool

storage pool name - file count is being
reset.
ANR1291E
Explanation: The server has detected an incorrect

count of the number of files within this storage pool.
System action: The server will correct this
information.
ANR1284I
Move node data started as process

process ID.
Explanation: A process has been started to move data

by node.
Explanation: A database audit process detects

incorrect information for a schedule event record.
User response: Rerun the AUDITDB operation
specifying FIX=YES so that the incorrect schedule event
record can be deleted.
ANR1292E
System action: The indicated process has started.

User response: To query the progress of the process,
use the QUERY PROCESS command. To cancel the
background process, use the CANCEL PROCESS
command. Use the process ID number to specify this
process.
Audit command: Incorrect information

detected in a schedule event record for
node nodename, domain domain, schedule
schedule. Specify FIX=YES to delete the
record.
Audit command: Incorrect information

detected in a schedule event record for
node nodename, domain domain, schedule
schedule. The record will be deleted.

incorrect information for a schedule event record. The
record will be deleted. A subsequent QUERY EVENT
will report this event as "Missed."
ANR1288I
Move node data process process ID

ended for storage pool storage pool name.
Explanation: A move node data process for the named


ANR1293E

ANR1289I
Move node data process process ID

terminated for the storage pool storage
pool name - process canceled.
Explanation: During move node data processing in

the indicated storage pool, the process performing the
move node data has been canceled.
System action: If other move node data processes are
executing for the storage pool, these processes continue.
Space-reclamation process process

number: Fifty files in offsite storage-pool
volumes do not have copies in
accessible storage pools.
Explanation: More files in offsite storage-pool volumes

might exist for which copies cannot be located. If this is
the case, message ANR1173E is not displayed.
System action: The Tivoli Storage Manager server
skips files that do not have copies. The server does not
move the files from offsite storage-pool volumes.
User response: To view detailed information about all
the files that are skipped during the space-reclamation
process, enable trace AFUNAVAILABLE and look in the
trace log.

ANR1294I
ANR1290I
Move node data from storage pool

storage pool name to storage pool storage
pool name has ended. Files Moved:
number of files, Bytes Moved: number of
bytes, Unreadable Files: number of
Explanation: Move node processing for the specified

storage pool has ended with the displayed results.
determine whether all move node data processes ended
successfully.
196
Process process ID skipped skipped files

files on volume volume name because of
deduplicated files.
Explanation: While moving or copying files from the

sequential FILE volume shown to a DISK storage pool,
files that had deduplicated extents were encountered.
As a result, the files were skipped.
The sequential FILE volume shown is assigned to a
storage pool that has deduplication enabled or at one
time had deduplication enabled. Some of the files on
the volume have deduplicated extents and can not be
moved or copied to the DISK storage pool.
System action: The server moves or copies all files
from the volume that do not have deduplicated extents.
ANR1295W ANR1298W
Those files that do have deduplicated extents are
skipped.
names a storage pool that does not contain WORM

FILE volumes.
User response: If attempting a MOVE

DATA/NODEDATA to move the files with
deduplicated extents to the DISK storage pool, one
must first perform a MOVE DATA/NODEDATA to
another sequential storage pool that does not have
deduplication enabled. This move will restore the
deduplicated files to their complete state in the target
storage pool. Once all deduplicated data has been
moved, perform a MOVE DATA or MOVE
NODEDATA to the DISK storage pool from the target
storage pool. It is recommended to use a FILE storage
pool as the target.
When it is issued during the DEFINE and UPDATE

STGPOOL commands, it indicates that the storage pool
being defined or updated is being configured with
WORM FILE volumes (Reclamationtype is SnapLock),
but other storage pools being specified on the storage
pool definition (for example, the Next or Reclaim or
Copy storage pool parameters) do not contain WORM
FILE volumes (Reclamationtype is Threshold). Such
configurations might cause data on those WORM FILE
volumes to be moved to a storage pool that does not
support WORM FILE volumes.
If attempting a RESTORE STGPOOL/VOLUME to copy

the files with deduplicated extents, one must first
perform a RESTORE STGPOOL/VOLUME to another
sequential storage pool that does not have
deduplication enabled. This will restore the
deduplicated files to their complete state in the target
storage pool. Once all deduplicated data has been
restored, perform a MOVE DATA/NODEDATA to the
DISK storage pool from the target storage pool. It is
recommended to use a FILE storage pool as the target.
ANR1295W
An attempt to set end reclamation date

for WORM volume volume name to end
reclamation date failed. end reclamation
date set to SnapLock retention date.
Explanation: Tivoli Storage Manager computes and

attempts to set the end reclamation date for a volume
based on the RETMIN and RETVER COPYGROUP
attributes. When setting the end reclamation date for
the named volume, the Network Appliance SnapLock
file system was unable to fulfil the request. It was,
however, able to set the date to the Snaplock retention
date, which is farther in the future than the requested
date. This is probably due to how the SnapLock NAS
file server's retention date is configured.
This warning message is only issued once per volume,
when this condition is detected when data is first
placed on the volume.
User response: Verify that the Tivoli Storage Manager
COPYGROUP attributes and the retention settings of
the Network Appliance file system are consistent with
your requirements for WORM volume storage.
For other situations, this message might be issued

when there will be a movement of data from a storage
pool with WORM FILE volumes (Reclamationtype is
SnapLock) to a storage pool that does not have WORM
FILE volumes (Reclamationtype is Threshold).
The server allows this type of movement, but the
customer needs to be aware that if data is moved from
a WORM FILE volume to another type of media, the
data may no longer be protected from inadvertent or
malicious deletion. In addition, if this data is on
WORM volumes to meet data retention and protection
requirements for certain legal purposes and is moved
to other media, the data might no longer meet those
requirements.
System action: The command continues.
User response: Verify that the storage pools being
used meet your requirements for data protection and
retention.
ANR1297E
Explanation: Defining storage pools with

RECLAMATION=SNAPLOCK is only supported on a
server with archive data protection enabled.
System action: The define storage pool command
fails.
User response: Define the storage pool with
RECLAMATIONTYPE=THRESHOLD on this server. Or
else enable archive data retention protection on this
server, and try the command again.
ANR1298W
ANR1296W
Storage pool storage pool name does not

contain WORM FILE volumes.
Explanation: This message might be issued during the

definition or updating of a storage pool, or during
BACKUP or RESTORE STGPOOL commands, or in
other such situations when it is determined that data
on WORM volumes might be moved to other media. It
Storage pools with

RECLAMATIONTYPE=SNAPLOCK can
only be defined on servers with archive
data retention protection enabled.
The server encountered an error in

attempting to delete an object in a
Centera storage device. The Centera
representation of the name is Centera
object string. The server was keeping
track of the object in volume id volume
id. The return code received was return
code.
Explanation: The server failed to delete an object in a

197
ANR1299E ANR1308W
Centera storage device after server records concerning
the object were deleted. The object is no longer
accessible through the server. The object continues to
occupy space in the Centera storage device. The return
code that is returned is either from the server interface
to Centera services, or it can be directly from the
Centera device.
System action: The server continues operation, and
the object is logically deleted within the server, but
continues to occupy space in the Centera device.
User response: The server can continue to operate in
spite of this error. Centera service can be required if the
volume of unpurged objects becomes a problem.
ANR1299E
The server encountered an invalid

storage format while attempting a
partial object retrieve for object seg_id.
Explanation: A partial object retrieve was attempted

on a file that was stored in a format that does not
support partial object retrieves.
System action: The transaction ends and the retrieve
request fails.
User response: Try the retrieve again, using a regular
or full retrieve instead of a partial object retrieve.
ANR1303E
Disk volume volume name is already

offline.
Explanation: A VARY OFFLINE command specified a

volume that was already offline.
ANR1304E
Disk volume volume name is currently in

use.
Explanation: A VARY OFFLINE command specified a

volume that is currently in use and cannot be varied
offline at this time.
User response: Try the command again at a later time,
or attempt to determine how it is currently being used
and free it.
ANR1305I
Disk volume volume name varied online.
Explanation: The specified volume has been varied

online as the result of a VARY ONLINE command.
ANR1300I
VARY ONLINE command initiated for

disk volume volume name.
Explanation: A VARY ONLINE command has caused

a vary-on process to be started for the volume
specified.
ANR1306I
Disk volume volume name varied online

(read-only).

online in read-only mode as the result of a VARY
ONLINE command.

ANR1301I
VARY OFFLINE command initiated for

disk volume volume name.
Explanation: A VARY OFFLINE command has caused

a vary-off process to be started for the volume
specified.
System action: The volume is varied offline.
ANR1302E
Disk volume volume name is already

online.
Explanation: A VARY ONLINE command specified a

volume that was already online.
ANR1307I
Disk volume volume name varied offline.

offline as the result of a VARY OFFLINE command.
ANR1308W
Storage agent not sychronized with

server - restart needed.
Explanation: The storage agent has detected that a

policy, storage pool, device class, or other attributes
that is read from the server at initialization is no longer
valid.
System action: The operation of the storage agent
continues. Depending upon what has changed on the
server the storage agent behavior may be
unpredicatable and other failures may result.
User response: The storage agent should be halted
198
ANR1309W ANR1316E
and restarted to synchronize the storage agent with the
server.
ANR1309W
Shred value zero for storage pool storage

pool name may render deleted data non
shreddable.
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
pool hierachy.
The server allows this type of operation, but the
administrator needs to be aware that if data is stored or
moved to the affected storage pool, the data cannot be
shredded after deletion.
When it is issued during the DEFINE command, it
indicates that the storage pool definition is being
configured with a non zero SHRED value, however
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.
When issued during the UPDATE command, it
indicates the specified storage pool may be altering the
SHRED value from non zero to zero or that the
specified Copy, Next or Reclaim storage pool has a
SHRED value zero. Such configurations may result in
data to become non shreddable if data from the
primary random access storage pool is moved to one of
the storage pools with a zero SHRED value.
ANR1312E
Vary-on failed for disk volume volume

name - error reading disk.
Explanation: A VARY ONLINE command has been

issued for the disk volume specified but the server
encounters an error reading the disk.
System action: The volume is not varied online.
read error and correct the problem.
ANR1313E

name - unsupported block size (block
size).

issued for the disk volume specified, but the volume is
formatted with a block size that cannot be used.
User response: Reformat the disk with a block size
that is an evenly divisible by 4096.
ANR1314E

name - reduced capacity (was count
blocks, now count blocks.

issued for the disk volume specified, but the size of the
volume does not match the size expected.
User response: Verify that the storage pools being

used meet your requirements for data protection.
User response: Restore the volume or otherwise

correct the disk volume size, and reissue the command.
ANR1310E

name - insufficient memory.
ANR1315E

name - invalid label block.

issued for the disk volume specified, but sufficient
memory is not available to process the command.

issued for the disk volume specified, but the label block
of the volume is invalid or cannot be read.
User response: Reissue the command at a later time,

or make more memory available to the server.
User response: Restore or reformat the disk volume.

ANR1316E
ANR1311E

name - unable to access disk device.

issued for the disk volume specified, but the server is
unable to access the disk.

name - internal error detected.

issued for the disk volume specified, but fails due to an
internal server error.

inability to access the volume and correct the problem.
199
ANR1317E ANR1325W
ANR1317E
Command: Storage pool storage pool name

is not a shreddable pool.
Explanation: The command indicated specifies the

name of a storage pool which is not a shreddable pool.
The command syntax requires that
SHREDTONOSHRED=YES be specified when data is
moved from a shreddable storage pool to a non
shreddable storage pool.
command.
User response: Reissue the command with
SHREDTONOSHRED=YES.
ANR1318I
Copying active data from primary

storage pool primary pool name to active
data pool active data pool name has ended.
Files Copied Up: number of files, Bytes
Copied Up: number of bytes, Unreadable
Files: number of unreadable files,
Unreadable Bytes: number of bytes in
unreadable files.
ANR1321W
Vary-on not possible for disk volume

volume name - access state is "destroyed".

issued for the disk volume specified, but the status of
the volume is destroyed.
User response: If necessary, use the UPDATE
VOLUME command to change the status of the
volume, and reissue the command.
ANR1322W
The shredding mode is already shredding

mode.
Explanation: A SETOPT SHREDDING command was

issued to change the shredding mode, but the new
mode is the same as the existing mode.
System action: The shredding mode is unchanged.
ANR1323E
Command SHRED DATA is invalid for

automatic shredding mode.
Explanation: Copy active data processing for the

shown.
Explanation: A SHRED DATA command was issued

while shredding mode is set to Automatic.

determine whether all copy active datat processes
ended successfully.
User response: Set the shredding mode to Manual or

wait for automatic shredding to shred the data.
ANR1324E
ANR1319I
Preview of copying active data from

primary storage pool primary pool name to
active data pool active data pool name has
ended. Files Copied: number of files,
Bytes Copied: number of bytes.
Explanation: Preview of copy active data processing

for the specified storage pool has ended with the
results shown.
ANR1320W
Vary-on not possible for disk volume

volume name - access state is
"unavailable".

issued for the disk volume specified, but the status of
the volume is unavailable.
User response: If necessary, use the UPDATE
VOLUME command to change the status of the
200
Process process number is already running

a SHRED DATA.
Explanation: A SHRED DATA command was issued

while another SHRED DATA process is still executing.
Only a single SHRED DATA process is allowed at any
time.
User response: Wait for the current SHRED DATA
process to finish, and issue the command again.
ANR1325W
Shreddable object for node name:

type=type, file space=filespace name,
object=object name skipped.
Explanation: The object for node name, identified by

type, file space and object name was found in a
shreddable storage pool and is skipped, however the
EXPORT continues.
System action: The server process continues exporting
and will skip all shreddable objects.
User response: Specify the
ALLOWSHREDDABLE=YES parameter when exporting
objects from a shreddable storage pool. Using this
option forces EXPORT to process all objects, including
objects found in shreddable storage pools.
ANR1326I ANR1335E
ANR1326I
Shredding process complete after

shredding shredded bytes bytes and
skipping skipped bytes bytes.
Explanation: The shredding process has completed.

The amount of data successfully shredded and the
amount of data that was skipped are reported.
System action: Server operation continues. If any data
was skipped, the server will attempt to shred it the
next time shredding runs.
ANR1327I
User response: Try the failing operation again. If the

operation fails again, review additional information
that is available for this message in the problem
determination section of the Tivoli Storage Manager
information center. Go to the Tivoli Storage Manager
information center (http://publib.boulder.ibm.com/
infocenter/tsminfo/v6r3/topic/com.ibm.itsm.nav.doc/
t_probdeterm.html) and type the message ID in the
Search field. Select a topic from the problem
determination section.
ANR1331E
Automatic shredding stopped. Total

bytes shredded was shredded bytes and
total bytes skipped was skipped bytes
bytes.
Explanation: The automatic shredding process has

ended. The amount of data successfully shredded and
skipped during automatic shredding is reported.
was skipped, the server will attempt to shred it the
next time shredding runs.
Explanation: This message indicates the expected

values when an invalid frame is detected.
User response: If contacting support, please provide
the information from this message.
ANR1332W

ANR1328E
The server has detected an attempt to

restore or retrieve a shredded object.
Explanation: An attempt was made to retrieve or

restore an object which has already been shredded. This
can happen if your datasbase was recently restored,
and data which existed at the time of the database
backup has since been erased and shredded.
User response: Perform an AUDIT VOLUME
operation on the volume containing the shredded data.
ANR1329I
Automatic shredding started.
Explanation: The automatic shredding of deleted

objects is starting.
Shredding cancelled prior to

completion. Total bytes shredded was
shredded bytes and total bytes skipped
was skipped bytes bytes.
Explanation: The shredding process was cancelled

either because the specified duration has elapsed, or
because the CANCEL PROCESS command was used to
cancel it. The amount of data successfully shredded
and skipped is reported.
was skipped or not processed, the server will attempt
to shred it the next time shredding runs.
ANR1335E
command: Database database name cannot

be the target of an upgrade because it is
not empty.
Explanation: The DSMSERV INSERTDB operation

cannot insert data into the specified database because
the database already contains data from another server.
Possible causes for this error include:

ANR1330E
Invalid frame detected. Expected magic

magic sequence number seqNum server id
servId segment id segId.
v The wrong database was specified in the

DATABASEALIAS option in the server's options file.
The server has detected possible

corruption in an object that is being
restored or moved. The actual values for
the incorrect frame are: magic magic hdr
version ver hdr length hdrLen sequence
number seqNum data length length server
ID srvId segment ID segId crc crc.
Explanation: An invalid frame was detected. This

might indicate corruption within the object that is being
restored or moved.
System action: The object is not restored or moved.
v The database was formatted using the DSMSERV

FORMAT command instead of the DSMSERV
LOADFORMAT command.
System action: The DSMSERV INSERTDB command
terminates.
User response: Verify that the correct database name
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
201
ANR1336I ANR1342I
command before rerunning the DSMSERV INSERTDB
command.
ANR1336I
command: Ready for connections from

the source server. Remaining time:
remaining time
Explanation: The command has completed its

initialization, and is ready to begin receiving database
information from the source server.
System action: The command will continue to wait
until the source server establishes a server-to-server
connection and begins sending database information, or
until the specified amount of time has passed.
User response: Initiate a session from the source
server.
ANR1339W
Session session id underestimated a size

allocation request - additional spaceMB
more space was allocated to allow the
operation to continue.
Explanation: This session required additional space

megabytes of space in order for the operation to
continue. The client is responsible for accurately
reporting the size of a file to be stored to the server.
The size reported by the client is used to reserve space
in the DISK storage pool to store this file. If this size is
underestimated, the server may not be able to allocate
the additional space needed for this file to continue
with this operation.
System action: None, the operation was able to
continue.
Explanation: The DSMSERV INSERTDB command

encountered a database backup trigger, a database
space trigger, or recovery log space trigger, and
removed it as part of the database upgrade process.
User response: The installed version of the client for

this node should be evaluated. In most cases, if a client
has underestimated the sizes of files reported to the
server, this may have been corrected in a newer version
of the client. If this is an application using the TSM API
that is not an IBM product, contact the vendor for the
application to have this corrected.
System action: The trigger is deleted from the

upgraded database.
ANR1340I
ANR1337I
A trigger type trigger has been removed.

ANR1338E
One or more constraint violations were

detected. Examine log file log file name
for details.

encountered one or more instances where data being
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
specified log file.
System action: The offending row was not inserted
into the database. Instead, the contents of the row were
written to the specified log file along with additional
information about the specific error.
User response: Because some data was not inserted
into the database, the database is in an inconsistent
state. The server should not be started until the
problem is corrected.
Contact your service representative for assistance in
correcting the problem. You may be directed to
examine the log file, and in some cases, correct the
erroneous data and insert it into the database.
However, due to the sensitive nature of the database,
you should never attempt to do this unless directed to
do so by your service representative.
202
Scratch volume volume name is now

defined in storage pool storage pool name.
Explanation: The scratch volume specified has been

added to the storage pool shown.
ANR1341I
Scratch volume volume name has been

deleted from storage pool storage pool
name.
Explanation: The scratch volume specified is no

longer in use and has been removed from the indicated
storage pool.
ANR1342I
Scratch volume volume name is now

pending - volume will be deleted from
storage pool storage pool name after the
reuse delay period for this storage pool
has elapsed.
Explanation: All files have been deleted from the

indicated scratch volume. The volume will not be
removed from the storage pool until the reuse delay
time period for the indicated storage pool has elapsed.
If the storage pool does not have a reuse tdelay
specified, the indicated volume was emptied after it
had been requested by another process. It will be in the
full or filling state if the process places more data on
the tape, or it will be removed from the storage pool
after it is no longer required.
ANR1343I ANR1349E
manually delete it from the storage pool.

ANR1346E
ANR1343I
Unable to delete scratch volume volume

name.
Explanation: A scratch volume cannot be deleted from

the server and returned to scratch at this time because
all the locks have not be released. A number of retries
have been attempted.
System action: None
User response: The scratch volume will be
automatically deleted when the server is restarted. Or,
you may manually delete this volume later, using the
DELETE VOLUME command.
ANR1344I
Volume volume name cannot be reused.

Remove the volume from server storage.
Explanation: A volume that was full and is now

empty cannot be reused by the server because the
volume is on WORM media.
System action: The volume is in a state where the
access mode is READONLY, the status is FULL, and the
percent utilized is 0. The server considers the volume
to be empty when calculating the occupancy and
utilization fields for the volume.
User response: The volume remains in the library and
in the storage pool, with the attributes described in the
System Action section. If this is not a volume in a
RECLAMATIONTYPE=SNAPLOCK storage pool, you
may remove the volume by performing these steps:
1. Remove the volume from the storage pool by
issuing the DELETE VOLUME command.
2. Remove the volume from the library by issuing the
CHECKOUT LIBVOLUME command.

processing terminated abnormally error accessing data storage.

export preview operation.
ANR1347E

data storage.

export operation.
ANR1348I
Export Operation information for number

objects has been deleted.
If this is a volume in a
RECLAMATIONTYPE=SNAPLOCK storage pool, you
cannot remove the volume. Rather, allow Tivoli Storage
Manager reclamation processing to delete the volume.
Explanation: A background server process deleted

export operation information for number files from the
server database. This process started during
initialization to remove any unneeded export
information.
Volume volume name cannot be reused

by other applications and will remain in
the storage pool.
System action: The actual backup or archive objects

were not deleted. Only information used to sort these
objects during the previous export operation was
deleted.
ANR1345I
Explanation: A WORM (write-once-read-many)

volume that has been written by the server cannot be
used by other applications. This volume was not full
and has been emptied due to expiration, delete
commands, or transaction failure.
System action: The volume remains in the storage
pool to be reused by IBM Tivoli Storage Manager,
unless it is manually deleted. The remaining space on
the volume will be used in the normal course of server
operation.

ANR1349E
Error code during deletion of export

operation information for number
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
User response: If the volume is no longer to be used,

203
ANR1350E ANR1357I
remove any sorting information which is left over from
System action: The backup or archive objects were not
deleted. Only the information used to sort these objects
during the previous export operation was deleted. The
background process was terminated before all sorting
information was deleted. The system will not perform
further export processing of file data until this problem
is resolved.
activity log and search for messages, then restart the
server. If the error cannot be isolated and resolved,
ANR1350E
Command: Invalid time range specified.

FROM: fromdate fromtime TO: todate
totime.
Explanation: A command was issued that specifies an

invalid FROM and TO date or time range. This error
can occur when the FROM date or time is not before
the TO date or time.
command.
ANR1353I
Command: Cannot cancel the EXPORT

operation with export identifier exportId.
The operation is currently active.
Explanation: The server cannot cancel the export

operation specified in the CANCEL EXPORT command
because it is currently running as an active process.
System action: Server operations continue.
User response: Only suspended EXPORT operations
may be cancelled by issuing the CANCEL EXPORT
command. Issue the QUERY EXPORT command to
identify the current state of the EXPORT operation.
ANR1354I
command name: The EXPORTIDentifier

parameter is not supported when the
FILEDATA parameter is set to NONE.
Running as non-restartable export.
Explanation: The EXPORTIDentifier parameter is

ignored while the command continues.
System action: The command runs and server
ANR1355I

date or time range.
command name: An export operation

already exists with the
EXPORTIDentifier export ID.
Explanation: The export command fails.

ANR1351I

suspended with status status.


command command was suspended with a SUSPEND
command.
User response: Reenter the export command with an

unused export identifier.

stops. Statistics on the number and type of objects
message.
ANR1356I

ANR1352I

process process ID has been suspended.
Command: Cannot restart the EXPORT

operation with export identifier exportId.
The operation is currently active.
Explanation: The server cannot restart the export

operation specified in the RESTART EXPORT command
because the export operation is currently running as an
active process.

command command by administrator administrator name
suspended processing.
User response: Only suspended Export operations

may be restarted using RESTART EXPORT command.
Issue the QUERY EXPORT command to identify the
current state the EXPORT operation.
System action: The specified process suspends, and

server operations continue.
ANR1357I
command name: The EXPORTIDentifier

parameter is not supported when the
PREVIEWIMPORT parameter is
specified. Running as non-restartable
export.
Explanation: The EXPORTIDentifier parameter is

ignored while the command continues.
204
ANR1358I ANR1368W
System action: The command runs and server


ANR1364I
ANR1358I
Export Identifier: Export Id
Explanation: This is a restartable export operation that

can be referenced by the displayed EXPORTIDentifier
parameter.
System action: Server operations continue
Input volume volume name closed.
Explanation: During a sequential data operation, the

volume specified has been closed because the operation
is complete.

ANR1365I
ANR1359I
Suspend in progress
Explanation: The server-to-server export operation has

been suspended and will stop when resources have
been freed for the background process. This message
may be displayed in response to a QUERY PROCESS
command for an export operation.
ANR1360I

volume specified has been opened for output as the
volume number shown.
ANR1361I

volume specified has been closed because processing of
the volume is complete.
ANR1366W
Output volume volume name opened

(sequence number sequence number).
Output volume volume name closed.

volume specified has been closed because the export or
dump is complete.
Volume volume name closed (end

reached).
Input volume volume name contains an

invalid identifier.

volume specified has been mounted but contains an
invalid identifier.
System action: The volume is not used.
User response: Make sure you specified the correct
volume for the operation. If a LOADDB operation was
being performed on MVS, the command syntax may be
specified by using a ddname or by specifying a device
class name. You must use the same method that was
used when the database was originally dumped. If you
did not, this error message will be displayed. Try
loading the data base by using the other method of
syntax (ddname).

ANR1367W

ANR1362I
Output volume volume name closed

(full).

volume specified has been closed because the volume is
full.
Import volume volume name was written

by a different export process.
Explanation: During an IMPORT operation, the

volume specified has been mounted but contains an
export identifier that does not match the import
process.
User response: Supply a volume created by the proper
export process.

ANR1368W
ANR1363I
Input volume volume name opened

(sequence number sequence number).
Explanation: Because of a sequential data operation,

the volume specified has been opened for input as the
volume number shown.
Input volume volume name contains

sequence number sequence number;
volume sequence number sequence
number is required.

volume specified has been mounted but contains the
wrong volume sequence number.
205
ANR1369E ANR1377I
User response: Supply the volume with the proper
sequence number. The volume history file can help you
choose the correct volume.
ANR1369E
Input volume volume name contains

Version 1 dump.

volume specified has been mounted but appears to
contain a version 1 database dump.
System action: The volume is not used. The operation
is terminated.
User response: Make sure you specified the correct
volume for the operation. A Version 1 database dump
may not be loaded into a Version 2 server. The Version
1 database dump must only be loaded into a Version 1
server.
ANR1370E
Insufficient number of mount points

available in device class device class name.
Explanation: During IMPORT or EXPORT processing,

the server cannot allocate sufficient mount points for
the device class specified. The device class associated
with the EXPORT or IMPORT drive only has a mount
limit of one. The operation needs to read or write file
data from or to the same device class because file data
is being imported or exported.
System action: The IMPORT or EXPORT command is
ANR1373I
Process process Id for Command has been

suspended on source server.
Explanation: The background import process has been

suspended on the source server.
ANR1374I
Process process Id for Command has been

canceled on source server.
Explanation: The background import process has been

canceled on the source server.
ANR1375I
Command: Cannot suspend the export

operation export Id because the current
state is not valid.
Explanation: This message is returned in response to a

SUSPEND EXPORT command which specified an
export operation that is not currently suspendible. The
export operation may not be running, or it may be in
the process of being suspended.
System action: The specified command fails, and
User response: Make more mount points available.

ANR1376I
ANR1371I
Command: The export operation with

export identifier Export Id has been
deleted.
Explanation: The suspended server-to-server export

operation has been deleted. This operation may no
longer be restarted. This message is be displayed in
response to a CANCEL EXPORT command.
Analyst authority has been revoked for


encountered an administrator with analyst authority,
and revoked the authority as part of the database
upgrade process.
System action: The analyst authority is revoked.

ANR1377I
ANR1372I

encountered an administrator with analyst authority,
and revoked the authority as part of the database
upgrade process.
Suspend export request accepted for

export process with export Identifier
Export Id ( process process ID).
Explanation: A SUSPEND EXPORT command has

been entered for the specified server-to-server export
process. Some processes will experience a delay before
they suspend. This delay may be lengthy for processes
that involve remote data movement.
System action: The analyst authority is revoked.


206
Analyst authority has been revoked for

administrator id administrator id.
ANR1378I ANR1386I
ANR1378I
command: No connection was received

after session wait time minutes.
Explanation: The command waited the specified

amunt of time for the source server to connect, but no
connection was established.
System action: The command terminates.
command: Read bytes bytes and inserted

database entries database entries in elapsed
time (read rate megabytes per hour).
Explanation: The command read the indicated

number of bytes, and wrote the indicated number of
database entries.
ANR1380I
The buffer pool monitor switch is

enabled.
System action: Server continues processing.

User response: No action is required.
The buffer pool monitor switch is
disabled 'OFF'. A manual update might
be needed.
Explanation: The server failed to turn the buffer pool

monitor switch to 'ON'.
User response: No action is required at this time. But
a manual update might be needed before executing
command 'Q DBS' or 'Q DB F=D'. Refer to message
1139I.
ANR1382E
Explanation: The memory dedicated to the database

manager was set successfully.
ANR1384E
The server failed with error code return

code when attempting to update a
database parameter.
Explanation: Cannot update a database parameter

with the value specified in the server options file.
System action: The server initialization fails.
error. Contact your service representative for further
The update to set memory used by TSM

server database to instance memory in
MBMB failed.
Explanation: Attempt to set memory dedicated to

TSM server database failed.
User response: Collect all messages prior to this one
and contact your service representative for further
assistance.
ANR1385E
Explanation: The server has turned the buffer pool

monitor switch to 'ON'.
ANR1381W
Memory usage by the database manager

is limited to instance memory in MBMB.
User response: Rerun the command. Either specify a

larger value for the SESSWAIT parameter, or establish a
connection from the source server more quickly.
ANR1379I
ANR1383I
The database name is either invalid or

missing in the server option file.
Explanation: While attempting to format a database,

the Tivoli Storage Manager server has found that the
database name is either invalid or missing.
System action: Server format stops.
format the database, check the following items:
v Ensure that the server options file has a valid name
for for Tivoli Storage Manager server database. The
database name is specified with the
DATABASEALIAS option. The database name is a
unique character string containing from one to eight
letters, numbers, or keyboard characters. The name
can contain any of the following characters: a-z, A-Z,
0-9, @, #, and $.
ANR1386I
Beginning schema verification for the

database insert process.
Explanation: The database insert process is verifying

that the database schema is correct.
System action: The server will verify the correctness
of the database schema before inserting any database
records.
207
ANR1387I ANR1396E
ANR1387I
Schema verification for the database

insert process has completed.
Explanation: The database insert process has

successfully verified that the database schema is
correct.
wrong column in the target table.

System action: The database insert process terminates.
ANR1392E
System action: If CHECKSCHEMA=YES was specified

then the database insert process will begin inserting
records into the database.
ANR1388E
Schema verification for the database

insert process detected inconsistencies.
Explanation: Inconsistencies were detected during

database schema verification.
Column target column name (target column

number) in target table target table name is
not set by upgrade, but does not allow
NULLs and has no default value.
Explanation: The database insert process has detected

a discrepency while verifying the data base schema. A
column in the target database table is not set, does not
have a default value and does not allow NULLs.

ANR1389I
The database insert process is

terminating because
CHECKSCHEMA=ONLY was specified.
Explanation: The database insert process is

terminating after verifying the database schema
because the CHECKSCHEMA=ONLY parameter was
specified.
User response: Rerun the command without
specifying the CHECKSCHEMA=ONLY parameter.
ANR1390E
Column source column name (source

column number) in legacy table source
table name is mapped to an invalid
column (target column number) in target
table target table name (maximum column
is table size).
ANR1393I
Memory usage by the database manager

is set to AUTOMATIC.
Explanation: The memory dedicated to TSM server

database was set to automatic successfully.
ANR1394E
The update to set memory used by TSM

server database to AUTOMATIC failed.
Explanation: Attempt to set memory dedicated to

TSM server database to automatic failed.
User response: Collect all messages prior to this one
and contact your service representative for further
assistance.
ANR1395I
Insertdb command: Process process number,

database insert, has completed.

column in the source database table was mapped to an
invalid column in the target table. The target column
number is higher than the number of columns in the
target table.
Explanation: The database insert process process

number has completed.
ANR1396E
System action: Database insert processing ends.


ANR1391E
Column source column name (source

column number) in legacy table source
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
208
Insertdb command: Process process number,

database insert, has completed with
errors.
Explanation: The database insert process process

number has completed, but errors were encountered by
the process.
System action: Database insert processing ends.
User response: Review any messages that were issued
by the process, and take corrective action as
appropriate.
ANR1397I ANR1406E
ANR1397I
Insertdb command: Found number of

database objects database objects.
Explanation: This message indicates the total number

of database objects that were found during database
insert processing.
ANR1398I
Insertdb command: Processed number of

database objects database objects.

of database objects that were successfully processed
during database insert processing.
ANR1402W
Mount request denied for volume

volume name - volume unavailable.
Explanation: The volume shown cannot be mounted

because it is not available.
System action: The volume is not mounted.
User response: If the attempted mount occurs in a
library sharing environment and the library manager
was recently recycled, try again in five minutes. In this
case the library manager and library client need a few
minutes to reestablish communication and synchronize
the mounting information between the two servers.
ANR1403W
Scratch volume mount request denied mount canceled.
Explanation: A scratch volume cannot be mounted

because the mount request has been canceled.
System action: The scratch volume is not mounted.
ANR1399I
Insertdb command: Failed to process

number of database objects database
objects.

of database objects that were not successfully processed
ANR1400W

volume name - mount canceled.

because the mount request has been canceled.

ANR1404W
Scratch volume mount request denied mount failed.

because the mount request cannot be completed
successfully. Possible reasons include, an error in device
specifications to the server or the mount request timed
out.
User response: If the device specifications (for
example, DEFINE DEVCLASS) are in error, correct
them and reissue the command that requested the
volume to be mounted.
ANR1405W
ANR1401W

because no scratch volume is available.

volume name - mount failed.

because the mount request cannot be completed
successfully. Possible reasons include, an error in device
specifications to the server or the mount request timed
out.
User response: If the device specifications (DEFINE
DEVCLASS and so forth) are in error, correct them and
reissue the command that requested the volume to be
mounted.
Scratch volume mount request denied no scratch volume available.

ANR1406E
Simultaneous write operation could not

release all the acquired mount points.
Explanation: A simultaneous write to a primary and

copy storage pools failed to release all the acquired
mount points. When a simultaneous write operation
begins it will attempt to acquire all of the necessary
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
209
ANR1407W ANR1415W
message is issued if one of the previously acquired
mount points cannot be released.
System action: At least one mount point acquired by
simultaneous write operation is not released.
ANR1407W
Scratch volume mount request denied storage pool pool name has reached
maxscratch limit.

because the storage pool has reached the maximum
scratch volume limit allowed by the MAXSCRATCH
parameter.
System action: A scratch volume is not mounted.
User response: Use the UPDATE STGPOOL poolname
MAXSCRATCH=xx command command to increase the
number of scratch volumes allowed in the storage pool.
ANR1410W
Explanation: The status of the volume shown has

been set to unavailable.
ANR1411W
Insertdb command: PREVIEW=YES was

specified. No data will be inserted into
the database.
Explanation: PREVIEW=YES was specified on the

INSERTDB command. Database data will be read and
checked for errors, but no data will be written into the
database.

Volume volume name already in use skipped.
Explanation: During an export or database backup, a

a storage pool, or has already been used by the current
operation, or has been previously used by an export or
database backup operation (as recorded in the volume
history) or is in use by another process.
System action: The operation continues and the
volume is skipped.
User response: Use the QUERY VOLUME command
to display the names of volumes that are defined to
server storage pools. Use the QUERY VOLHISTORY
command to display the names of volumes that have
been used for export or database backup operations. If
no volume names are displayed using the query
commands described above, ensure that the volume
identified in this message has not been specified or
used more than once in the operation being performed.
210
Volume volume name access mode is

"unavailable".
Explanation: At server startup, the status of the

indicated volume is unavailable.
ANR1413W

ANR1409W

now set to "read-only" due to write
error.
Explanation: Because of an unrecoverable write error

on the volume shown, the status of the volume has
been set to read-only.
ANR1412W
ANR1408I

now set to "unavailable".

"read-only".

indicated volume is read-only.
ANR1414W

"read-only" due to previous write error.

indicated volume is read-only due to an unrecoverable
write error, or because an administrator used the
UPDATE VOLUME command to set the volume access
mode to read-only.
ANR1415W

DESTROYED.

indicated volume is DESTROYED. This status can
result because the access mode was set to DESTROYED
by a storage administrator. This status can also result
because the server determined that the database
records associated with this volume are damaged and
set the status of the volume to DESTROYED. If this is
ANR1416W ANR1424W
the case, the server also issues an ANR1316E message.
User response: You can issue the RESTORE VOLUME
server command to restore the volume if a storage pool
backup is available.

User response: Reissue the command with both the
FROMDATE and FROMTIME parameters specified.
ANR1420W
ANR1416W

"offsite".

indicated volume is offsite.
Read access denied for volume volume

name - volume access mode =
"unavailable".
Explanation: An attempt to access the named volume

for reading fails because the volume status is
unavailable.
System action: The volume is not used for read
access.

ANR1417W

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
set to read-only.

name - volume is offline.

for reading failed because the volume is offline.

User response: Use QUERY VOLUME
FORMAT=DETAILED for the volume to view the
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
command to restore a readable copy of the file to the
storage pool.
ANR1418E
ANR1421W
command name: Export commands that

target another server cannot be issued
from the server console.
Explanation: An EXPORT command that targets

another server was issued from the server console. This
command cannot be issued from the server console
because it requires authentication of the issuing
administrator on the target server.

ANR1422W

name - volume access mode="offsite".

for reading failed because the volume status is offsite.
access.
ANR1423W
Scratch volume volume name is empty

but will not be deleted - volume access
mode is "offsite".
Explanation: The named scratch volume is empty but

will not be deleted at this time because the access mode
is offsite.

User response: Issue the command from an

User response: After bringing the volume onsite,

change the access mode to read-only so the volume will
be deleted.
ANR1419E
command name : FROMDATE must be

specified when FROMTIME is
specified.
Explanation: A command that supports the

FROMDATE and FROMTIME parameters was issued
with the FROMTIME parameter specified, but without
the FROMDATE parameter. When the FROMTIME
parameter is used, the FROMDATE parameter must be
specified.
ANR1424W

name - volume access mode="destroyed".

for reading failed because the volume status is
destroyed.
access.
211
ANR1425W ANR1431E
ANR1425W
Scratch volume volume name is empty

but will not be deleted - volume state is
"mountablenotinlib".
Explanation: The named scratch volume is empty but

will not be deleted at this time because the state of the
volume is MOUNTABLENOTINLIB. Possible reasons
include, a MOVE MEDIA command was used to check
the volume out of the library and the volume was
subsequently checked into the library using CHECKIN
LIBVOL without first running a MOVE MEDIA
command to update the volume state back to
MOUNTABLEINLIB state. If this should happen, the
QUERY MEDIA will display the volume to be in
MOUNTABLEINLIB state since QUERY MEDIA does
verify if the volume is actually in the library before
displaying the state of the volume.
activity log and search for messages. Contact your

ANR1428W
Explanation: An object on the indicated volume

cannot be shredded because the volume is offline.
System action: The object is not shredded at this time.
When the volume is put back online, another attempt
will be made to shred the object.
User response: Determine why the volume is offline,
and, if possible, place the volume back online.
ANR1429E

User response: The following steps may be used if the
volume is to be deleted:
1. Run CHECKOUT LIBVOL to check the affected
volume out of the library, the REMOVE=NO option
may be used to prevent actual volume movement
2. Run MOVE MEDIA * STG=*
WHERESTATE=MOUNTABLENOTINLIB
WHERESTATUS=EMPTY. When the volume is
moved by MOVE MEDIA
WHERESTATE=MOUNTABLENOTINLIB, the
scratch empty volume is deleted
3. Check the volume back into the library using
CHECKIN LIBVOL command
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
or client action. The server ends import operation.
to monitor and wait for any file space deletion
processes to complete, or cancel the process if you do
not want to delete the file space. Try the import
operation again after this action has been taken.
All legacy FILE volumes have been

marked FULL.
Explanation: As part of the conversion of the database

to Tivoli Storage Manager version 5.3, all existing
non-full volumes of devtype FILE have been marked
FULL to keep them from being extended.
System action: All FILE volumes that were not
already FULL have been marked FULL and cannot be
appended to.
ANR1427E
No legacy FILE volumes were marked

FULL.
Explanation: As part of the conversion of the database

to Tivoli Storage Manager Version 5.3, all existing
non-full volumes of devtype FILE were attempted to be
made FULL. However, a database error prevented the
conversion, and the status of these volumes remains
unchanged.
System action: The volumes are not marked FULL.
212
Transaction failed for Import process invalid file space filespace name for node
node name was detected.

encounters an invalid file space name.
ANR1430W
ANR1426I
Shredding access denied for volume

volume name - volume is offline.
Retrieval request denied for storage

pool storage pool name - access
mode="unavailable".
Explanation: An attempt was made to retrieve a file

from the storage pool shown, but the access mode of
the storage pool is unavailable.
System action: The file is not retrieved from this
storage pool. If possible, the file is retrieved from
another storage pool.
User response: Consider changing the access mode for
the storage pool.
ANR1431E
An error occurred while writing to side

A of volume volume name. An attempt
will be made to write to side B of this
volume.
Explanation: An error occurred while writing to side

A of a two-sided volume.
System action: No additional data will be written to
side A of this volume. Any remaining space on side A
will not be used. An attempt will be made to use the
reverse side (side B) of the volume.
User response: None required if the side B can be
used successfully. However, the administrator should
ANR1432I ANR1438W
investigate the cause of the error and may want to
move data from this volume.
configuration information to the file.

ANR1436E
ANR1432I
Updating device configuration

information to defined files.
Explanation: The server is updating device

configuration information for the files or data sets
specified with the DEVCONFIG option in the server
options file.
ANR1433I
Device configuration information

successfully written to file name.
Explanation: Device configuration information was

successfully written to the file specified.
Device configuration file devconfig file

name cannot be opened.
Explanation: While attempting to write device

configuration information to device configuration files,
the server cannot open the file name specified.
System action: The server does not write device
configuration information to the file specified.
User response: Examine error messages 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 file indicated and that
there is sufficient space in the file system for the file.
On MVS, make sure that the data set has been allocated
and that the server has authority to write to the data
set. After the problem has been corrected, use the
BACKUP DEVCONFIG command to write device
configuration information to the file.

ANR1437E
ANR1434W
No files have been identified for

automatically storing device
configuration information.
Explanation: The server is unable to automatically

update device configuration file. No files were
identified using the DEVCONFIG option in the server
options file.
User response: If you would like to have the server
automatically record device configuration information
to assist in server recovery, use the DEVCONFIG
option in the server options file to specify where device
configuration information should be written. If you
update the options file, halt and then restart the server
so the changes can take effect.
ANR1435E
Server could not write device

configuration information to devconfig
file name.
Explanation: While attempting to write device

configuration information to defined files, the server
cannot write to the file name specified.
System action: The server cannot write device
configuration information to the 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. After the problem has been corrected, use the
BACKUP DEVCONFIG command to write device
No device configuration files could be

used.
Explanation: The server attempts to read device

configuration information from defined files and cannot
open any of the files.
System action: The operation is ended.
problems, if possible. Ensure that the defined device
configuration files have been created. If you can start
the server, you can create the files by using the
BACKUP DEVCONFIG command. If you cannot start
the server, you will need to create a device
configuration file by editing the file and adding the
appropriate DEFINE commands for the device class,
drive, and library definitions. The contents and
requirements for this file are described in the
Administrators Guide. Make sure that the server has
proper authority to read from the defined device
configuration files.
ANR1438W
Skipping device configuration file:

devconfig file name.
Explanation: While attempting to read device

configuration information from a defined device
configuration file, the server encounters problems in
processing the definitions included in the file.
System action: The specified file is skipped, and the
next one specified in the server options file will be
used.
been displayed prior to this message to understand
why the file could not be used. When you can start the
server again, you can refresh this file by using the
BACKUP DEVCONFIG command.
213
ANR1439E ANR1447W
ANR1439E
Allocate prohibited - transaction failed.
Explanation: While attempting to preallocate storage

on a storage pool, the server detected that the
transaction for this operation has previously failed. This
error may occur when a large file is selected for backup
and the client did not properly estimate the file size.
There may not be enough space in the storage pool for
the file.
System action: An internal error is reported by the
server and the operation being performed is ended.
been displayed prior to this message for more
information.
ANR1440I
All drives in use. Process process number

being preempted by higher priority
operation.

User response: Ensure that the copy group destination
storage pool of the assigned management class has the
appropriate NATIVE or NONBLOCK data format.
ANR1443W
Process process ID terminated from

session session id. A potential
drive-contention deadlock was detected.
Explanation: See message.

ANR1444E
No device configuration file is defined.
Explanation: No device configuration file is defined.

Check DEVCONFIG option in server options file.
System action: The specified configuration parameter
is skipped.

attempted to find an available drive, all the drives were
in use. To make a drive available for this operation, the
indicated process is being cancelled by the system.
User response: Add the DEVCONFIG option to the

server options file, specifying a valid file or data set
name to use for the device configuration file.
System action: The lower priority process is cancelled

to make a mount point (drive) available.
ANR1445I
User response: When a drive again becomes available,

restart the process that was cancelled. If the process
was a migration or reclamation process, it will be
automatically restarted when needed. If this message
appears frequently, you may want to increase the
number of drives available. See the MOUNTLIMIT
parameter on the UPDATE DEVCLASS command.
Explanation: This message indicates the total

throughput (megabytes/hour) during database insert
processing.
ANR1441I
Volume volume name is in use. Process

process number being preempted by
higher priority operation.

attempted to use a volume, it was in use. To make a
volume available for this operation, the indicated
process is being cancelled by the system.
System action: The lower priority process is cancelled
to the volume available.
User response: Restart the process that was cancelled.
It will wait until the higher priority process is finished
with the volume. If the cancelled process was a
migration or reclamation process, it will be
automatically restarted when needed.
ANR1442E
Invalid storage pool for store operation:

storage pool.
Explanation: The storage pool selected for a store

operation (for example, backup or archive) was not a
NATIVE or NONBLOCK data format storage pool. This
may be caused by an incorrect management class being
assigned to an object.
214
Insertdb command: Throughput was

megabytes per hour megabytes per hour.

ANR1446I
RUNSTATS: Table updating statistics

started.
Explanation: This message indicates the update

statistics for all tables started.
ANR1447W
command name: The server is not able to

begin a new thread to execute the
command on line line number in parallel.
The command will run serially.
Explanation: This message is issued during a RUN

command to indicate that thread resources are not
available to run the command in parallel. The
command will be executed serially.
System action: The SCRIPT continues.
User response: Increase the resources available to the
server or reduce the number of parallel commands or
scripts that are running on the server at any one time.
ANR1448I ANR1458I
ANR1448I
command name: Beginning serial SCRIPT

command execution on line line number.

command (VERBOSE=YES) to indicate that a SERIAL
command was encountered and following SCRIPT
commands will be executed serially.
System action: The SCRIPT command continues.
User response: See the output of the commands
following the SERIAL command to determine their
results.
ANR1449I
command name: Beginning parallel

SCRIPT command execution on line line
number.

command (VERBOSE=YES) to indicate that a
PARALLEL command was encountered and following
SCRIPT commands will be executed in parallel.
System action: The SCRIPT command continues.
User response: See the output of the commands
following the PARALLEL command to determine their
results.
ANR1450E
command name: Invalid command script

name: command script name.
ANR1453E
command name: Command script command

script name already exists.
Explanation: The script name specified in a DEFINE

SCRIPT command already exists.
User response: Reenter the command specifying a
different command name.
ANR1454I

script name defined.
Explanation: The script name specified in a DEFINE

SCRIPT command was successfully defined.
System action: None
User response: None
ANR1455E

script name does not exist.
Explanation: The script name specified in a DEFINE,

UPDATE, or DELETE SCRIPT command does not exist.
different command name.
script name updated.
Explanation: An invalid script name was specified for

a DEFINE, UPDATE, or DELETE SCRIPT command.
ANR1456I
Explanation: The script name specified in an UPDATE

SCRIPT command was successfully updated.

valid command name.
System action: None

User response: None
ANR1451E
command name: Invalid command:

command.
Explanation: An invalid command was specified for a

DEFINE, UPDATE, or DELETE SCRIPT command.
valid server command.
ANR1452E
command name: Invalid line number: line

number.
Explanation: An invalid line number was specified for

a DEFINE, UPDATE, or DELETE SCRIPT command.
ANR1457I

script name deleted.
Explanation: The script name specified in a DELETE

COMMAND command was successfully deleted.
System action: None
User response: None
ANR1458I
command name: Line line number was

deleted from command script command
script name.
Explanation: The specified line number was deleted

from the command script as a result of a DELETE
SCRIPT command.

valid line number.
System action: None

User response: None
215
ANR1459E ANR1469E
ANR1459E

script name, line line number does not
exist.
command script were not specified in the RUN

command.
Explanation: The line in command script name

specified in a UPDATE, or DELETE SCRIPT command
does not exist.
User response: Reenter the RUN command specifying

all required parameters.
ANR1465E

different line number.
ANR1460I

script name copied to new command script
name.
Explanation: The specified command script was

copied to a new script with the COPY SCRIPT
command.
Explanation: An invalid parameter was encountered

in a command script.
User response: Correct the script definition and
reexecute the RUN command.
ANR1466I
System action: None

User response: None
ANR1461I
command name: Executing command

script command script name.
Explanation: The specified command script is being

executed as a result of a RUN command.

script name, line line number, parameter is
invalid: command line.

script name, Line line number : command
line.
Explanation: The specified line for the command

script is being executed. The contects of the line being
executed are displayed.
System action: None
User response: None
System action: None

User response: None
ANR1462I

script name completed successfully.
ANR1467E

script name, did not end in a
non-continued line command line.
Explanation: The specified command script did not

end in a line that had no continuation character (-).
Explanation: The specified command script, started

with a RUN command, has successfully completed.
System action: None
User response: Correct the specified script so that it

ends in a line that is not continued to the next line.
User response: None

ANR1468E
ANR1463E

script name completed in error.

with a RUN command, encountered errors.
System action: Part or all of the command lines in the
script ended in error. Command processing is
terminated.
User response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
command script and reissue the command.
ANR1464E

script name, line line number, parameter
parameter number was not specified:
command line.
Explanation: All parameters required to execute a
216

script name, continued line is too long
Explanation: The specified command script with

continuation lines is too long to be executed.
User response: Correct the specified command script
so that it is shorter.
ANR1469E

script name, Line line number is an
INVALID command : command line.
Explanation: The specified line for the command

script is not a valid server command. This message is
displayed when a RUN command is executed with the
PREVIEW=YES parameter specified.
System action: Command Preview processing fails
ANR1470I ANR1478E
User response: Correct the script and reenter the RUN
command.
ANR1470I

script name completed successfully
(PREVIEW mode).

with a RUN command, has successfully completed.

script name completed in error
(PREVIEW mode).

with a RUN command, encountered errors.
System action: Part or all of the command lines in the
command script ended in error. Command processing
is terminated.
User response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
script and reissue the command.
ANR1472I
User response: Reenter the command without the line

number OR the FILE= parameter.
ANR1475E

script name renamed to new command
script name.
Explanation: The specified command script was

renamed with the RENAME SCRIPT command.
Explanation: A filename was specified in a command

but the specified file could not be opened by the server.
User response: Examine any messages that might

appear prior to this one in the activity log to determine
if the error can be found. If the file was to exist for use
by the command, ensure that the file does exists and
that the server has proper authority to access the file. If
the file was to be created by the command, ensure that
the filesystem has sufficient space and that the server
has authority to create the file in the location specified.
ANR1476E

command name: A command line cannot
be specified when the FILE= parameter
is used.
Explanation: The FILE= parameter was specified in

the DEFINE SCRIPT command AND a command line
was also specified for the SCRIPT. When the FILE=
parameter is specified, a command line cannot be
specified.

User response: Add script command lines to the file
or specify another file and reenter the command.
ANR1477E
ANR1474E
command name: A line number cannot be

specified when the FILE= parameter is
used.
Explanation: The FILE= parameter was specified in

the DEFINE SCRIPT command AND a line number
was also specified for the SCRIPT. When the FILE=
parameter is specified, a line number cannot be
specified.
command name: The OUTPUTFILE

parameter may only be specified when
FORMAT=RAW is specified.
Explanation: The OUTPUTFILE parameter was

specified in a QUERY SCRIPT command but the
FORMAT parameter did not specify RAW output.
When outputting the QUERY to a file, you MUST
specify RAW output format.
User response: Reenter the command specifyingthe
proper value for the FORMAT parameter or do not
specify the OUTPUTFILE parameter.
ANR1478E
User response: Reenter the command without the

command line OR the FILE= parameter.
command name: File file name contains no

data.
Explanation: The FILE= parameter was specified in a

command but the specified file did not contain script
command lines.
ANR1473E
command name: File file name could not be

opened.

ANR1471E
command name: Error writing to file file

name.
Explanation: An error was encountered while writing

to the file specified.
if the error can be found. Ensure that the filesystem has
sufficient space and that the server has authority to
create the file in the location specified.
217
ANR1479I ANR1489E
ANR1479I
command name: Query output was

written to file file name.
Explanation: The output from the specified query was

successfully written to the specified file.
code condition check succeeded and the IF(..) statement

is executed.
System action: Command processing continues.
System action: The command completes successfully.

ANR1480E
command name: Description text is too

long.
Explanation: The specified description text is too long

for a command that allows description text to be
specified.
shorter description.
ANR1481E
command name: A command line or

description must be specified.
Explanation: An UPDATE SCRIPT command was

specified with out a command line (script line) or
description text.
command line or description text.
ANR1482I
command name: Found label statement label

on line line number and continuing.

command (VERBOSE=YES) to indicate that the target
label for a GOTO statement was found.
ANR1485I
command name: Ending SCRIPT with

EXIT statement on line line number.

command (VERBOSE=YES) to indicate that an EXIT
statement was encountered and SCRIPT termination
will end.
System action: The SCRIPT command ends.
ANR1486I
command name: Executing line line number

GOTO label name.

command (VERBOSE=YES) to indicate that a GOTO
statement was encountered and processing will skip to
the named label.
System action: SCRIPT processing continues.
ANR1487I
command name: Command return code is

symbolic return code (return code severity).

command (VERBOSE=YES) to indicate the return code
that was returned from the latest command.

ANR1483I
command name: Line line number

condition IF(condition) is NOT true statement is skipped.

command (VERBOSE=YES) to indicate that the a return
code condition check failed and the IF(..) statement is
skipped.
ANR1488E

condition IF(condition) is not a valid
condition.
Explanation: This message is issued if an IF()

statement in a SCRIPT does not specify proper
condition values.
System action: Command processing fails.
User response: Reenter the command using valid
conditions for the IF() statement.

ANR1484I

condition IF(condition) is TRUE statement will be executed.

command (VERBOSE=YES) to indicate that the a return
218
ANR1489E
command name: Line line number is a

GOTO to a label (label name) that does
not exist or is associated with a line
prior to line line number.
Explanation: This message is issued if a GOTO

statement in a SCRIPT does not specify a label that
exists in the SCRIPT, or that does exist but is associated
with a line prior to the line that contains the GOTO
statement.
ANR1490W ANR1498E
User response: Correct the SCRIPT definition and
reenter the RUN command.
ANR1490W

script name does not contain any
commands.
Explanation: The script name specified in a RUN

command does not contain any commands.
System action: The RUN operation fails (has nothing
to do).
User response: Server command Scripts that contain
no commands will not execute. Add command lines to
the Script and reenter the RUN command.
system authority, they must have previously created or

updated the script.
command.
authorized administrator ID, or contact the
administrator that created the script.
ANR1494I
command name: Command return code is

numeric return code.

command (VERBOSE=YES) to indicate the numeric
return code that was returned from the latest
command.
ANR1491E
Server command scripts cannot be

started from the server console.
Explanation: A server command script RUN

command was issued from the server console. Server
command scripts cannot be started from the server
console because they may require a long time complete
and the server console should be available to control
other server functions.
User response: Start the server command script from
an administrative client or schedule it for execution
using the administrative command scheduler.

ANR1495E
command name: command script name is

currently running. Define, update or
delete can not be performed.
Explanation: An DEFINE, UPDATE or DELETE

SCRIPT was attempted on a script that is currently
running.
User response: Reenter the command when the script
is not running.
ANR1496I
ANR1492E
command name: A loop has been detected

in server command script RUN
commands - command failed.
Explanation: A server command script DEFINE or

UPDATE command has created a situation where one
or more scripts invoke each other in a loop that can
cause the scripts to run idefinitely.
Explanation: The ISSUE MESSAGE command with a

severity indicator of INFORMATION was issued.
ANR1497W
System action: The command fails to update the

server command script.

severity indicator of WARNING was issued.
User response: Server command scripts can invoke

each other, but not in a fashion that causes a potential
loop in their execution. Specify the scripts in a manner
that does not cause them to invoke each other in a
loop.
ANR1493E
Command: Administrator administrator

name is not authorized to update or
delete command script command script
name.

ANR1498E
severity indicator of ERROR was issued.
Explanation: The specified administrator has entered

the indicated command, but this administrator does not
have the proper authority necessary to update or delete
this command script. If an administrator does not have
219
ANR1499S ANR1507I
ANR1499S
ANR1505W

severity indicator of SEVERE was issued.
ANR1500I
Policy domain domain name defined.
Explanation: In response to the DEFINE DOMAIN

command, the policy domain domain name has been
defined in the server database.
ANR1501I
Policy domain domain name deleted.
Explanation: In response to the DELETE DOMAIN

deleted from the server database. All policy sets,
management classes, copy groups, and schedules
related to the domain have also been removed.
ANR1502I
Policy domain domain name updated.
Explanation: In response to the UPDATE DOMAIN

updated in the server database.
Explanation: This message may be returned from the

DEFINE COPYGROUP, UPDATE COPYGROUP,
VALIDATE POLICYSET or ACTIVATE POLICYSET
command. During the indicated command processing,
the server has found a backup copy group that has a
table of contents (TOC) destination referring to an
undefined storage pool named storage pool name. If this
storage pool is undefined when the policy set is
activated, the creation of the TOC for an image backup
will fail if its TOC creation binds to the management
class whose copy groups reference this pool.
User response: To locate the copy groups that refer to
the undefined storage pool, issue the QUERY
COPYGROUP command. To change the TOC
destination to refer to an existing storage pool, issue
the UPDATE COPYGROUP command. To define the
storage pool, an authorized administrator can issue the
DEFINE STGPOOL command.
ANR1506E

ANR1503I
Policy domain domain name copied to

domain target domain.
Explanation: In response to the COPY DOMAIN

copied to a new policy domain named target domain.
All policy sets, management classes, and copy groups
are also copied to the target domain policy domain.
ANR1504I
Command: No matching domains.
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.
220
The BACKUP copy group in

specifies a table of contents destination
storage pool : storage pool name that does
not exist. If this pool does not exist
when policy set policy set name is
activated, the creation of the table of
contents may fail for an image backup
when this management class is used for
the backup.
Command: An incorrect storage pool

name - storage pool name was specified
for the TOC destination.
Explanation: Server processing for the command

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
an active-data storage pool is not a valid copy group
TOC destination.
User response: Reissue the command using a storage
pool name that is not a copy pool or active-data pool.
For a list of names of defined storage pools, issue the
QUERY STGPOOL command.
ANR1507I
Table of contents load retention is set to

number of minutes minutes.
Explanation: The number of minutes that the

unreferenced table of contents (TOC) data will remain
loaded in the server database has been set to the value
indicated with the SET TOCLOADRETENTION
command.
ANR1508E ANR1515I
ANR1508E
Command: An incorrect table of contents

load retention retention value was
specified.
Explanation: A SET TOCLOADRETENTION

command has been entered that specifies an invalid
table of contents (TOC) retention period.
command.
retention period.
ANR1513I
Explanation: In response to the COPY POLICYSET

command, the policy set set name has been copied to
the policy set new set name in the policy domain named
domain name. All management classes and copy groups
are also copied to the policy set new set name.
ANR1514I
ANR1509E
Error writing option option name to file

file name.
Explanation: An error was encountered while writing

an option entry to server option file.
System action: The format command fails.
if the error can be found. Ensure that the filesystem has
sufficient space and that the server has authority to
update the server option file then reissue the format
command.
ANR1510I
Policy set set name defined in policy

domain domain name.
Explanation: In response to the DEFINE POLICYSET

command, the policy set named set name has been
defined in the policy domain named domain name in the
server database.
ANR1511I
Policy set set name deleted from policy

domain domain name.
Explanation: In response to the DELETE POLICYSET

command, the policy set set name has been deleted from
the policy domain domain name in the server database.
ANR1512I
Policy set set name updated in policy

domain domain name.
Explanation: In response to the UPDATE POLICYSET

command, the policy set set name has been updated in
the policy domain domain name in the server database.
Policy set set name copied to set new set

name in policy domain domain name.
Policy set set name activated in policy

domain domain name.
Explanation: In response to the ACTIVATE

POLICYSET command, the policy set set name has been
activated in the policy domain domain name. All
management class and copy group definitions in the
policy set will be used by clients that start sessions
after this command is committed. Clients that currently
have sessions established with the server will use the
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
specified policy set. These values are returned to client
nodes that start a session with the server after this
command is committed to the server database.
ANR1515I
Policy set set name validated in domain

domain name (ready for activation).
Explanation: This message may be displayed in

response to a VALIDATE POLICYSET command. The
policy set set name has been checked in the domain
domain name to see if the management class and copy
group definitions are adequate for activating the policy
set. This message indicates that the policy set may be
activated. Warning messages may be issued prior to
this message if there are discrepancies in the policy set
with respect to the set that is currently active in the
policy domain.
System action: The server checks its definitions to
determine the policy sets qualifications for activation.
The server does not activate the policy set.
User response: If you are satisfied with any warning
messages that may have been issued prior to this
message concerning any possible discrepancies in the
policy set, issue the ACTIVATE POLICYSET command
to activate the policy set in the policy domain.
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.
221
ANR1516E ANR1525I
ANR1516E

is not enabled for deduplication.

name of a storage pool which does not have
deduplication enabled. The command requires that
deduplication be enabled on the storage pool before the
command can execute.
command.
User response: Update the storage pool to allow data
deduplication by specifying the parameter
DEDUPLICATE=YES. But only do so if you wish to
have duplicates of data in the storage pool removed.
ANR1517I
Insertdb command: Processed number of

database records database records.

of database records that were successfully inserted
ANR1518I
Insertdb command: Read number of bytes

bytes.

of bytes that were successfully read during database
insert processing.
ANR1521I
Management class class name deleted

from policy domain domain name, set set
name.
Explanation: In response to a DELETE MGMTCLASS

command, the management class named class name has
been deleted from the policy set set name belonging to
the policy domain domain name. All copy groups
defined for the management class are also removed.
ANR1522I
Management class class name updated in

policy domain domain name, set set name.
Explanation: In response to the UPDATE

MGMTCLASS command, the management class named
class name has been updated in the policy domain
domain name, policy set set name.
ANR1523I
Management class class name copied to

class new class name in policy domain
Explanation: In response to the COPY MGMTCLASS

command, the management class named class name has
been copied to a new management class named new
class name in policy set set name belonging to policy
domain domain name. All copy groups defined for
management class class name are also copied to
management class new class name.
ANR1519I
Insertdb command: Elapsed time was

elapsed time.
Explanation: This message indicates the total amount

of time that elapsed during database insert processing.
ANR1520I
Management class class name defined in

policy domain domain name, set set name.
Explanation: In response to the DEFINE

MGMTCLASS command, the management class named
class name has been defined in the policy set set name
belonging to the policy domain named domain name.

ANR1524I
Insertdb command: Beginning database

update phase.
Explanation: The database insert process has

completed inserting database records, and has begun
making updates to the inserted records.
ANR1525I
command: Updated database entries of

database entries database entries in elapsed
time.
Explanation: The command has updated the indicated

number of database entries.
222
ANR1526I ANR1534I
ANR1526I
Insertdb command: Building indices and

checking table integrity.
Explanation: The database insert process has begun to

create indices and check the integrity of the database
tables.
ANR1527I
command: Checked database objects of

database objects database objects in elapsed
time.
Explanation: The command has checked the integrity

of the indicated number of database tables.

ANR1531I
Explanation: In response to the DELETE

COPYGROUP command, the backup copy group
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.
ANR1532I

ANR1528I
RUNSTATS: Table updating statistics

completed in elapsed time.
Explanation: This message indicates the update

statistics for all tables completed.
Backup copy group group name deleted

name, management class class name.
Backup copy group group name updated

in policy domain domain name, set set

COPYGROUP command, the backup copy group
named group name has been updated in the

ANR1533E
ANR1529I
Process process ID skipped File state

deduplicated extent Extent id on volume
Volume name.
Explanation: While moving or copying deduplicated

extents from a sequential FILE volume, extents were
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
deleted. The damaged or deleted extents are skipped.
User response: If the deduplicated extent was marked
damaged, audit the indicated volume with FIX=NO to
verify whether the file is damaged. The audit will reset
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.
ANR1530I
Backup copy group group name defined


COPYGROUP command, a backup copy group named
group name has been defined for the management class
named class name in the policy set set name belonging to
command: The target client version that

was specified is not valid. The value
name value: value in the form V.R.M.F. (
Version, Release, Modification, and Fix
Level ) is incorrect.
Explanation: During pre-processing of command

command, an invalid value was encountered for the
client target level. The correct client target level should
be formatted like 6.2.0.0
System action: The register/update node fails.
User response: Specify the correct client target level,
then reissue the command.
ANR1534I
Process process ID skipped Num Files

deduplicated files on volume Volume
name because copies of the files were
not found.
Explanation: The DEDUPREQUIRESBACKUP server

option is set to YES. If the value of this option is YES
(the default), files within a deduplicated storage pool
must be backed up to a non-deduplicated copy storage
pool before the files can be moved.
System action: The operation skips the files without
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.
223
ANR1535I ANR1542E
However, doing so can result in unrecoverable data loss
if a data-integrity error occurs. As a best practice, do
not change the default.
ANR1535I
Archive copy group group name defined


COPYGROUP command, an archive copy group named
group name has been defined for the management class
named class name in the policy set set name belonging to
ANR1539S
Explanation: A DSMSERV INSERTDB command used

to upgrade from Tivoli Storage Manager V5 failed or
was cancelled. The result is a database that does not
contain all of the data from the original database. The
server cannot be run with an incomplete database.
System action: The server will not start.
User response: Rerun the DSMSERV INSERTDB
command.
ANR1540E

ANR1536I
Archive copy group group name deleted


COPYGROUP command, the archive copy group
named group name has been deleted from the
A previous database upgrade did not

succeed. The server cannot start.
Import command: The processing stopped.

The connection with the source server is
broken.
Explanation: The communications link with the source

server broke because of a network error or because the
source-server export process stopped.
System action: The import process ends.
User response: Examine the activity log of the source
server to determine if the export process stopped. A
displayed. If many communication error messages
occur simultaneously, check the network for failure and

ANR1541E
ANR1537I
Archive copy group group name updated


COPYGROUP command, the archive copy group
named group name has been updated in the
ANR1538I
Default management class set to class

name for policy domain domain name, set
set name.
Explanation: The default management class for the

policy set set name in policy domain domain name has
been set to the management class named class name.
System action: If this policy set is activated, clients
use this management class for backup-archive
processing by default, or if other management classes
specified for binding do not exist in the policy set.
224
Export command: The processing stopped.

The connection with the target server is
broken.
Explanation: The communications link with the target

target-server import process stopped.
System action: The export process ends.
User response: Examine the activity log of the target
server to determine if the import process stopped. A
ANR1542E
Import command: Preview processing

stopped. The connection with the source
server is broken.
Explanation: The communications link with the source

source-server export process stopped.
System action: The import process ends.
User response: Examine the activity log of the source
server to determine if the export process stopped. A
ANR1543E ANR1549W
Explanation: The communications link with the target

target-server import process stopped.
configuration wizard, a server database and recovery

log are created. In addition, files are created to hold
database information used by the database manager.
The specified path is the location of the database
information used by the database manager. If there is
no space available, the server can no longer function
correctly.
System action: The export process ends.
User response: Examine the activity log of the target

server to determine if the import process stopped. A
User response: Add space to the file system or free up

space on the file system or disk.
ANR1543E
ANR1544I
Export command: Preview processing

stopped. The connection with the target
server is broken.
The DEDUPTIER3FILESIZE option

value is temporarily updated from old
value to new value.
Explanation: The value for the DEDUPTIER3FILESIZE

option must be greater than or equal to the value for
the DEDUPTIER2FILESIZE option. The value for the
DEDUPTIER3FILESIZE option is increased to match the
value for the DEDUPTIER2FILESIZE option until the
server is restarted or until the value for the
DEDUPTIER3FILESIZE option is updated with the
SETOPT command.
User response: Use the SETOPT command to update
the value for either the DEDUPTIER2FILESIZE option
or the DEDUPTIER3FILESIZE option. Ensure that the
value for the DEDUPTIER3FILESIZE option is greater
than or equal to the value for the
DEDUPTIER2FILESIZE option when you are specifying
the values.
ANR1545W
The diagpath ( path ) file system or disk

is becoming full. Space available: space
available MB of total space MB. Percent
full: file system used ratio percent.
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
databases are in this space.
User response: Add space to the file system or free up
space on the file system or disk.
ANR1546W
Available space for the directory (path) is

less than 1 GB. If there is no space
available the server can no longer
function correctly.
Explanation: There is less than 1 GB of available space

in the file system or disk where the server database
files are located. When a server is initially created, with
the DSMSERV FORMAT utility or with the
ANR1547W
The server failed to update the

DBDIAGLOGSIZE server option due to
insufficient available space. Required
space: new value megabytes; available
space: system free space megabytes. The
current value:current value megabytes.
Explanation: There was not enough free space in the

filesystem or drive to create db2diag.log files.
System action: The update fails but the server
continues.
User response: Because the value in the server option
and logattr.chk have been updated, you must change
them to the current value so that they are consistent
with the value stored in the database manager. Free the
required disk space and update the DBDIAGLOGSIZE
option.
ANR1548E
The server failed to format or initialize

because the available space (free
spacebytes) in the diagnostic data
directory path path is less than 2MB to
allocate db2diag.log files;
Explanation: There was not enough free space in the

diagnostic directory to allocate 2MB db2diag.log files.
User response: Free the required disk space in the
diagnostic directory to at least 2MB and then run the
command again.
ANR1549W

platform). The next storage pool pool name
for the primary storage pool pool name
cannot be a target for LAN-free backup.
Explanation: The server rolled back a database update

transaction for the specified session because the
specified next storage pool of the specified primary
storage pool cannot be a target for LAN-free backup.
the UPDATE STGPOOL command for the specified
225
ANR1550W ANR1553W
primary storage pool to remove the specified next
storage pool from the parameter NEXTSTGPOOLS.
Alternatively, an authorized administrator can enable
LAN-free backup to the specified next storage pool.
ANR1550W
Management class class name is NOT

defined in policy set set name but IS
defined in the ACTIVE policy set for
domain domain name: files bound to this
management class will be REBOUND to
the default management class if/when
this set is activated.

command. During policy set validation processing, the
server has found a management class named class name
in the currently active policy set, but not defined in the
policy set being validated or activated (set name). If
policy set set name is activated, files bound to this
management class in domain domain name are
automatically rebound to the default management class
in policy set set name.
User response: If you do not want files to be rebound
to the default management class, define a management
class with the name specified in the message for the
policy set. To define the proper copy group attributes,
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
using the COPY MGMTCLAS command.
ANR1551W
BACKUP copygroup group name in

management class class name is NOT
defined in policy set set name but is
domain domain name: files bound to this
management class will no longer be
backed up if/when set name is activated.

server has found a backup copy group named group
name for management class class name in the currently
active policy set, but the copy group is not defined for
the management class in the policy set being validated
or activated (set name). If policy set set name is
activated, files bound to management class class name in
domain domain name will no longer be eligible for
backup processing.
ANR1552W

server has found an archive copy group named group
name for management class class name in the currently
active policy set, but the copy group is not defined for
the management class in the policy set being validated
or activated (set name). If policy set set name is
activated, attempting to archive files specifiying this
management class will fail. Existing archives bound to
this management class on the TSM server will be
expired based on the defmgmtclass values, or the
archive retention grace period for the policy domain, if
the default management class does not contain an
archive copygroup.
User response: To archive files specifying this
management class, define an archive copy group for
management class class name by using the DEFINE
COPYGROUP command.
ANR1553W
DEFAULT Management class class name

in policy set domain name set name does
not have a BACKUP copygroup: files
will not be backed up by default if this
set is activated.

command. During policy set validation for policy set
set name in policy domain domain name, the server has
found that the default management class named class
name does not have a backup copy group. This message
warns the administrator that activation of this policy
set results in client files not being backed up, unless
they are bound to a management class (which has a
copy group) other than the default.
User response: To define a backup copy group for the
management class, issue the DEFINE COPYGROUP
command. To assign a different default management
class for the domain, issue the ASSIGN
DEFMGMTCLASS command. Take either action if you
want files to be backed up by default.
User response: If you want files bound to this

management class to be eligible for backup processing,
define an archive copy group for management class
class name by using the DEFINE COPYGROUP
command.
226
ARCHIVE copygroup group name in

management class class name is NOT
defined in policy set set name but is
domain domain name: attempting to
archive files specifiying this
management class will fail if set name is
activated.
ANR1554W ANR1557W
ANR1554W
DEFAULT Management class class name

in policy set domain name set name does
not have an ARCHIVE copygroup: files
will not be archived by default if this
set is activated.

command. During policy set validation for policy set
set name in policy domain domain name, the server has
found that the default management class named class
name does not have an archive copy group. This
message warns the administrator that activation of this
policy set will result in client files not being allowed
archive processing unless they are bound to a
management class (which has an archive copy group)
other than the default.
User response: To define a backup copy group for the
management class, issue the DEFINE COPYGROUP
command. To assign a different default management
class for the domain, issue the ASSIGN
DEFMGMTCLASS command. Take either action if you
want files to be eligible for archive processing by
default.
ANR1555W
The BACKUP copy group in

specifies a destination that does not
refer to a defined storage pool: storage
pool name. If this pool does not exist
activated, clients will fail when using
this management class to backup files to
the server.

command. During policy set validation for set name, the
server has found a backup copy group destination that
references an undefined storage pool named pool name.
If this storage pool is undefined when the policy set is
activated, backup or archive operations will fail for
clients with files bound to the management class whose
copy groups reference this pool.
COPYGROUP command. To change the destination to
refer to an existing storage pool, issue the UPDATE
COPYGROUP command. To define the storage pool, an
authorized administrator can issue the DEFINE
STGPOOL command.
ANR1556W
The ARCHIVE copy group in

specifies a destination that does not
refer to a defined storage pool: storage
pool name. If this pool does not exist
activated, clients will fail when using
this management class to archive files to
the server.

server has found a archive copy group destination that
references an undefined storage pool named pool name.
If this storage pool is undefined when the policy set is
activated, backup or archive operations will fail for
clients with files bound to the management class whose
copy groups reference this pool.
COPYGROUP command. To change the destination to
COPYGROUP command. To define the storage pool, an
STGPOOL command.
ANR1557W
The space management migration

destination in management class
management class name does not refer to a
defined storage pool: storage pool name. If
this pool does not exist when policy set
policy set name is activated, clients will
fail when using this management class
to migrate space-managed files to the
server.

server has found a space management migration
destination that references an undefined storage pool
named pool name. If this storage pool is undefined
when the policy set is activated, space management
migration operations will fail for clients with files
bound to the management class that references this
pool.
User response: To locate the management class that
refers to the undefined storage pool, issue the QUERY
MGMTCLASS command. To change the destination to
MGMTCLASS command. To define the storage pool, an
STGPOOL command.
227
ANR1558E ANR1564E
ANR1558E
The space management migration

destination in management class
management class name in policy set policy
set name refers to copy storage pool:
storage pool name. Copy storage pools are
not a valid migration destination.

server has found a space management migration
destination that references a copy storage pool named
pool name.
ANR1561E
Command: Missing policy domain name.

command fails because the required policy domain
parameter has not been specified.
System action: Database changes for the command are
rolled back and server operation continues. The
command is not successful in changing the server
database.
valid policy domain name.
System action: Server operation continues. The policy

set is not activated.
ANR1562E

refers to the copy storage pool, issue the QUERY
refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.

command fails because the policy domain description
specified is longer than the length limit number of
characters allowed.
ANR1559E
The copy group destination for type

copy group type in management class
management class name in policy set policy
set name refers to copy storage pool:
storage pool name. Copy storage pools are
not a valid copy group destination.

server has found a copy group destination that
references a copy storage pool named pool name.
System action: Server operation continues. The policy
set is not activated.
refers to the copy storage pool, issue the QUERY
refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.
ANR1560E
Command: Invalid policy domain name domain name.

command fails because the policy domain name domain
name specified does not contain valid characters or
contains too many characters.
database.
policy domain name that conforms to these name
requirements. For information on the character and
length specifications for valid policy domain names,
platform.
228
Command: Policy domain description

exceeds length limit characters.

database.
shorter policy domain description.
ANR1563E
Command: Invalid retention period for

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
valid.
database.
valid BACKRETN value. For valid BACKRETN values
for the DEFINE COPYGROUP or UPDATE
COPYGROUP commands, refer to the Administrators
ANR1564E

ARCHRETN parameter - retention value.

value) specified for the ARCHRETN parameter is not
valid.
database.
valid ARCHRETN value. For valid ARCHRETN values
ANR1565E ANR1571E
ANR1565E
Command: Invalid policy set name - set

name.

command fails because the policy set name set name
specified does not contain valid characters or contains
too many characters.
database.
policy set name that conforms to valid name
length specifications for valid policy set names, refer to
the Administrators Reference for your particular
platform.
ANR1566E
Command: Policy set description exceeds

length limit characters.

command fails because the policy set description
characters allowed.
database.
shorter policy set description.
ANR1567E
Command: Invalid management class

name - class name.

command fails because the management class name class
database.
management class name that conforms to valid name
length specifications for valid management class names,
platform.
ANR1568E
Command: Management class description

exceeds length limit characters.

command fails because the management class
description specified is longer than the length limit
number of characters allowed.
database.
shorter management class description. Refer to the
Administrators Guide for your particular platform for
more information.
ANR1569E
Command: Invalid copy group name group name.

command fails because the copy group name group name
specified does not contain valid characters or contains
too many characters.
database.
copy group name that conforms to valid name
length specifications for valid copy group names, refer
to the Administrators Reference for your particular
platform.
ANR1570E
Command: Invalid copy frequency frequency value.

command command fails because the value (frequency
value) specified for the FREQUENCY parameter is not
valid.
database.
valid FREQUENCY value. For valid FREQUENCY
values for the DEFINE COPYGROUP or UPDATE
ANR1571E
Command: Invalid copy destination - pool

name.

specified for the copy group destination or for the table
of contents (TOC) destination does not contain valid
229
ANR1572E ANR1578E
characters or contains too many characters.
database.
storage pool name that conforms to valid name
length specifications for valid storage pool names, refer
to the Administrators Reference for your particular
platform. For a list of names of defined storage pools,
issue the QUERY STGPOOL command.
ANR1572E
Command: Missing copy destination.

command command fails because the required copy
group destination is not specified.
database.
required copy group destination (DEST).
ANR1573E
Command: Invalid copy type - type value.

command command fails because the value (type value)
specified for the TYPE parameter is not valid.
database.
valid TYPE value. For valid TYPE values for the
DEFINE COPYGROUP or UPDATE COPYGROUP
commands, refer to the Administrators Reference for
your particular platform.
ANR1574E
Command: Invalid version count for

VEREXISTS parameter - version value.

command command fails because the value (version
value) specified for the VEREXISTS parameter is not
valid.
database.
valid VEREXISTS value. For valid VEREXISTS values
230
ANR1575E

VERDELETED parameter - version value.

command command fails because the value (version
value) specified for the VERDELETED parameter is not
valid.
database.
valid VERDELETED value. For valid VERDELETED
values for the DEFINE COPYGROUP or UPDATE
ANR1576E

RETEXTRA parameter - retention value.

value) specified for the RETEXTRA parameter is not
valid.
database.
valid RETEXTRA value. For valid RETEXTRA values
ANR1577E

RETONLY parameter - retention value.

value) specified for the RETONLY parameter is not
valid.
database.
valid RETONLY value. For valid RETONLY values for
the DEFINE COPYGROUP or UPDATE COPYGROUP
ANR1578E

RETVER parameter - retention value.

value) specified for the RETVER parameter is not valid.
ANR1579E ANR1584E
database.
valid archive copy group options, refer to the

Administrators Reference and Administrators Guide for

valid RETVER value. For valid RETVER values for the
ANR1582E
ANR1579E
Command: Invalid copy mode - mode

value.

command command fails because the value (mode value)
specified for the MODE parameter is not valid.
database.
valid MODE value. For valid MODE values for the
ANR1580E
Command: Invalid copy serialization

mode - serialization value.

command command fails because the value (serialization
value) specified for the SERIALIZATION parameter is
not valid.
database.
valid SERIALIZATION value. For valid
SERIALIZATION values for the DEFINE COPYGROUP
or UPDATE COPYGROUP commands, refer to the
ANR1581E
Command: The option option is valid only

for backup copy groups.
Explanation: Server processing for the archive copy

group command command fails because the option
specified is only valid for backup copy group
definitions.
database.
User response: Reissue the command specifying valid
archive copy group options, or specify TYPE=BACKUP
if the intent is to operate on a backup copy group. For
Command: The option option is valid only

for archive copy groups.
Explanation: Server processing for the backup copy

group command command fails because the option
specified is only valid for archive copy group
definitions.
database.
User response: Reissue the command specifying valid
backup copy group options, or specifying
TYPE=ARCHIVE if the intent is to operate on an
archive copy group. For valid backup copy group
options, refer to the Administrators Reference and
Administrators Guide for your particular platform.
ANR1583E
Command: Copy frequency for archive

copy groups must be CMD - frequency
value is not valid.

group command command fails because a value other
than CMD has been specified for the FREQUENCY
parameter. The only value that may be specified for the
archive copy group FREQUENCY parameter is CMD.
database.
User response: Reissue the command specifying CMD
for the FREQUENCY parameter, or omitting the
FREQUENCY parameter because the default value for
FREQUENCY is CMD for archive copy groups. For
valid archive copy group options, refer to the
Administrators Reference and Administrators Guide for
ANR1584E
Command: Copy mode for archive copy

groups must be ABSOLUTE - mode value
is not valid.

group command command fails because a value other
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.
database.
ABSOLUTE for the MODE parameter, or omitting the
231
ANR1585E ANR1590E
MODE parameter because the default value for MODE
is ABSOLUTE for archive copy groups. For valid
archive copy group options, refer to the Administrators
Reference and Administrators Guide for your particular
platform.
ANR1585E
Command: Policy set ACTIVE cannot be

modified.

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.
User response: Reissue the command specifying a
policy set other than ACTIVE. To copy the ACTIVE
policy set for a policy domain to another name so that
commands may be used to change its contents, issue
the COPY POLICYSET command. Then to activate the
changes, issue the ACTIVATE POLICYSET command.
ANR1586E
Command: Invalid migration destination

- pool name.

specified for the migration destination is a copy pool. A
copy pool is not a valid migration destination.
database.
pool name that is not a copy pool. For a list of names
of defined storage pools, issue the QUERY STGPOOL
command.
ANR1587E
Command: Invalid copy group

destination - pool name.

specified for the copy group destination is a copy pool
or active-data pool. A copy pool or active-data pool is
not a valid copy group destination.
database.
pool name that is a primary pool, not a copy pool or
active-data pool. For a list of names of defined storage
pools, issue the QUERY STGPOOL command.
232
ANR1588W
The value of the

received from the configuration manager
specifies a storage pool storage pool name
for domain domain name that is not
defined on the managed server.
Explanation: If the storage pool on the managed

server is undefined, the value of the
ACTIVEDESTINATION parameter for domain domain
name is not updated.
User response: Define an active-data storage pool on
the managed server with the same name as that on the
configuration manager.
ANR1589E
Error reason code updating database

manager security plugin file name.
Explanation: The server was unable to update the

database manager security plugin. This plugin controls
access to the database manager from the Tivoli Storage
Manager server. The reason code is the errno from the
fopen subroutine for the file. Some common reason
codes are:
v 26 - The file is in use.
v 13 - Permission to write to the file is denied. On
Windows, this reason code can also indicate that the
file is in use.
For other reason codes, refer to your operating system
reference guide for errno values.
User response: Manually copy the file from the
installation directory to the location identified in the
message, and restart the server. On AIX, you might also
need to run the /usr/sbin/slibclean command as root
after halting the server but before copying the file. This
procedure will unload the plugin from the kernel
memory.
ANR1590E
Command: Policy domain domain name is

not defined.

name specified does not refer to a defined policy
domain in the server database.
database.
policy domain name that is defined in the server
database. For a list of the names of defined policy
domains in the server database, issue the QUERY
DOMAIN command.
ANR1591E ANR1597E
ANR1591E
Command: Policy domain domain name is

already defined.

name specified refers to a policy domain that is already
database.
policy domain name that is not defined in the server
database. For a list of the names of defined policy
domains in the server database, issue the QUERY
DOMAIN command.
ANR1592E
Command: Policy domain domain name

still contains at least one policy set.
Explanation: Server processing for the delete

command command fails because the policy domain
name domain name specified refers to a policy domain
that still contains at least one policy set.
database.
User response: To delete the policy set from the policy
domain, issue the DELETE POLICYSET command.
ANR1593E

still contains at least one node.

command command fails because the policy domain
name domain name specified refers to a policy domain
that still contains at least one node. A policy domain
cannot be deleted if one or more client nodes are still
assigned to the domain.
database.
User response: To remove remaining nodes from the
policy domain, issue the REMOVE NODE command.
After all nodes are removed, issue the delete command
again.
ANR1594E

has no active policy set.
Explanation: Server processing for the update or

register node command command fails because the
policy domain name domain name specified refers to a
policy domain that does not have an active policy set
defined. Nodes cannot be assigned to policy domains
that do not have an active policy set.

database.
User response: To activate a policy set for the
specified policy domain, issue the ACTIVATE
POLICYSET command. After a policy set has been
activated, client nodes may be assigned to the policy
domain.
ANR1595E
Command: Policy set set name is not

defined in policy domain domain name.

specified does not refer to a defined set in policy
domain domain name in the server database.
database.
policy set name that is defined in the policy domain.
For a list of the names of defined policy sets in the
policy domain, issue the QUERY POLICYSET
command.
ANR1596E
Command: Policy set set name is already


specified refers to a policy set that is already defined in
database.
policy set name that is not defined in the policy
domain. For a list of the names of defined policy sets in
the policy domain, issue the QUERY POLICYSET
command.
ANR1597E
policy set command: Policy set set name in

domain domain name still contains at
least one management class.
Explanation: The policy set command failed because the

set still contains at least one management class
definition.
User response: Remove the remaining management
classes from the policy set and reissue the command.
233
ANR1598E ANR1604E
ANR1598E
Command: No default management class

has been assigned for policy set set name
in domain domain name.

command fails because the policy set set name in policy
domain domain name does not have a default
management class assigned.
database.
User response: To assign a default management class
in the policy set, issue the ASSIGN DEFMGMTCLASS
command.
ANR1599E
Command: Management class class name

is not defined in policy domain domain
name, set set name.

command fails because the management class name class
name specified does not refer to a defined management
class in policy set set name belonging to policy domain
domain name.
database.
policy set name that is defined in the policy domain.
For a list of the names of defined policy sets in the
policy domain, issue the QUERY POLICYSET
command.
ANR1600E
Command: Management class class name

is already defined in policy domain

command fails because the specified management class
name class name refers to a management class that is
already defined in policy set set name belonging to
database.
management class name that is not defined in the
policy set. For a list of the names of defined
management classes in the policy domain and policy
set, issue the QUERY MGMTCLASS command.
ANR1602E
Command: Backup copy group group name

is not defined in policy domain domain
class name.

command fails because the backup copy group named
group name specified for management class class name
does not refer to a defined backup copy group 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
in the policy domain or policy set, issue the QUERY
COPYGROUP command.
ANR1603E
Command: Backup copy group group name

is already defined in policy domain
domain name, set set name, management
class class name.

command fails because the specified backup copy group
named group name refers to a copy group that is
already defined for management class (class name) in
name.
database.
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
set, issue the QUERY COPYGROUP command.
ANR1604E
Command: Archive copy group group

name is not defined in policy domain
domain name, set set name, management
class class name.

command fails because the archive copy group named
group name specified for management class class name
does not refer to a defined archive copy group in policy
set set name belonging to policy domain domain name.
database.
copy group name that is defined. For a list of the
234
ANR1605E ANR1611E
names of defined copy groups and management classes
in the policy domain or policy set, issue the QUERY
COPYGROUP command.
ANR1605E
Command: Archive copy group group

name is already defined in policy
domain domain name, set set name,
management class class 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
name.
database.
ANR1608E
Error fetching entry for domain domain

name, set set name.
Explanation: An internal server database error occurs

while retrieving policy information for policy set set
name in domain domain name.
System action: The policy operation is ended and
representative.
ANR1609E
Policy error: unable to find management

class ID for class class name in policy set
set name belonging to domain domain
name.

copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
set, issue the QUERY COPYGROUP command.
Explanation: An internal server database error has

been encountered while retrieving policy information
for management class class name in policy set set name
belonging to policy domain domain name.
ANR1606E

Out of server LOG space in accessing

policy tables.

transaction for policy information because sufficient log
space is not available on the server.
for use by the log and can issue the EXTEND LOG
volumes are used.
ANR1607E
Out of server DB space in accessing

policy tables.

transaction for policy information because sufficient
for use by the database and can issue the EXTEND DB

representative.
ANR1610E
Internal Server error: invalid copy type

copy type integer encountered in policy
set validation.
Explanation: An internal server database error has

been encountered while validating a policy set in
response to the VALIDATE POLICYSET or ACTIVATE
POLICYSET command.
representative.
ANR1611E
Command: Invalid management class

name - management class name.

command fails because the specified management class
name may not be used as a management class name.
235
ANR1612E ANR1617W
database.
another management class name.
ANR1612E
Command: Management class management

class name in policy set set name, domain
domain name specifies
MIGREQUIRESBKUP=YES, but
contains no backup copy group.
Explanation: During policy set validation or activation

for policy set set name in policy domain domain name,
the server has found that the management class named
class name specifies the MIGREQUIRESBKUP=YES
parameter but does not contain a backup copy group.
Policy set validation or activation fails in this case
because it would not be possible to ensure that
space-managed client files are backed up prior to being
migrated to the server.
database.
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.
ANR1613E
Command: Invalid retention initiation retention initiation value.

initiation value) specified for the RETINIT parameter is
not valid.
User response: Issue the command again and specify
a valid RETINIT value. For valid RETINIT values for
the DEFINE copy group or UPDATE copy group
commands, refer to the Administrators Reference.
ANR1614E

database.
a valid RETMIN value. For valid RETMIN values for
Command: RETVER of NOLIMIT cannot

be specified with RETINIT value of
EVENT.

command command fails because the retain versions
value of NOLIMIT is not allowed with the retention
initiation value of EVENT. If this is the UPDATE copy
group command, at least one of the values might have
been defined already.
database.
a valid RETVER or RETMIN value. For valid values for
ANR1616W
Command: the specified RETMIN value

(new days) will be ignored because the
RETINIT value is CREATION for
domain policy set management class.
Explanation: Processing for the copy group command

command detected that a retain minimum number of
days value was specified either with the retention
initiation value of CREATION, or the current retention
initiation value stored for the copy group is
CREATION. The retain minimum number of days
value is not used when the retention initiation value is
CREATION. The copy group will be defined or
updated, but the RETMIN value will not be stored.
System action: The copy group is defined or updated
and system operation continues.
User response: The copy group will be defined or
updated, but the retain minimum number of days
value will not be stored. If you want to specify a
retention initiation value of EVENT, issue the update
command again.
ANR1617W
Command: Invalid number of days for

RETMIN parameter - days value.
Explanation: The command fails.
236
ANR1615E
Command: the new RETVER value (new

days) is less than the value previously
stored (old days) for domain policy set
management class.

command detected that the new number of days to
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
because the retain versions value is not allowed to
decrease.
System action: The copy group is updated and system
User response: The copy group will be updated, but
the copy group might fail validation when the policy
set is validated or activated.
ANR1618W ANR1623E
ANR1618W
Command: the new RETMIN value (new

days) is less than the value previously
stored (old days) for domain policy set
management class.

command detected that the new retain minimum
number of days is less than the number of days
currently stored for the copy group. The policy set
might not activate when archive retention protection is
active, because the retain minimum days value is not
allowed to decrease.

server has found that archive retention protection is
active and the the copy group has a retain minimum
days value that is less than the value in the ACTIVE
policy set. The policy will not be validated or activated.
User response: Update the RETMIN value in the copy
group.
ANR1622E
System action: The copy group is updated and system

User response: The copy group will be updated, but
the copy group might fail validation when the policy
set is validated or activated.
ANR1619E
The RETVER of NOLIMIT is not

allowed with the RETINIT value of
EVENT for domain policy set management
class.
Explanation: This message can be returned from the

server has found the the copy group in the policy has
specified an invalid combination of options. Retain
versions of NOLIMIT and retention initiation of
EVENT are not allowed. The policy will not be
validated or activated.
User response: Update the RETVER or REINIT values
in the copy group. For valid values, refer to the
Administrators Reference for your platform.
ANR1620E
The new RETVER value (new days) is

less than the value in the ACTIVE
policy (old days) for domain policy set
management class.

server has found that archive retention protection is
active and the copy group has a retain versions value
less than the value in the ACTIVE policy set. The
policy will not be validated or activated.
User response: Update the RETVER value in the copy
group.
ANR1621E
The new RETMIN value (new days) is

less than the value in the ACTIVE
policy (old days) for domain policy set
management class.
Management class class name is not

defined in policy set set name, but is
defined in the active policy set for
domain domain name. Archive retention
protection is active, so validation fails.

server found a management class named class name in
the currently active policy set, but not defined in the
policy set being validated or activated (set name). When
archive retention protection is active, all management
classses in the active policy set must be included in the
policy set being validated. Policy validation will fail.
User response: Define a management class with the
name specified in the message for the policy set. To
define the proper copy group attributes, reference the
management class definition in the active policy set or
copy the management class class name from the active
policy set to the policy set set name, using the COPY
MGMTCLAS command.
ANR1623E
Management class class name in policy

set set name for domain domain name does
not have an archive copy group. Archive
retention protection is active, so
validation fails.

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
group. When archive retention protection is active, all
management classses in the policy set being validated
must have an archive copy group. Policy validation
will fail.
User response: Define an archive copy group in
specified management class, then try the validation
again.

237
ANR1624E ANR1631I
ANR1624E
Command: Invalid active pool list - active

pool list name.

command fails because the active pool list active pool list
specified does not contain valid pool.
database.
active pool list that conforms to these name
length specifications for valid active-data pool names,
platform.
ANR1625E
command: Server is down-level compared

to the version of data being inserted
into the database: data version.

encountered data written by a version of the
DSMUPGRD EXTRACTDB command that is newer
than what is supported by the server version.
the server compatible with the version of DSMUPGRD
used to extract the data. Or reextract the data using an
older version of DSMUPGRD that is compatible with
the version of the server.
ANR1626I
The previous message (message number

message number) was repeated repeat count
times.
Explanation: The message issued prior to this message

was issued repeatedly.
ANR1628I
The database manager is using port port

number for server connections.
Explanation: The server configures the database

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
connections exceeds a pre-determined threshold,
connections are made through TCP/IP to the specified
port. If the port is being used by another application,
the database manager cannot receive connections from
the server after the change to TCP/IP connections is
necessary. After this situation occurs, future connections
to the database manager might fail.
ANR1629W
command: This command will result in

ending the replication relationship for
all nodes that match the pattern node
pattern. Replication will no longer be
performed for the specified node(s).
Explanation: A REMOVE REPLMODE command with

prevent the specified nodes from being replicated. The
replication relationship is removed for each node. No
node data is removed from this or any of the other
replication servers.
System action: The system asks whether you wish to
continue with the REMOVE REPLNODE command.
User response: To process the REMOVE REPLNODE
command, enter 'Y' to continue or 'N' to stop the
process.
ANR1630W
command: node name is not configured for

replication.
Explanation: A node specified for a command

operation is not configured for replication. A node is
configured for replication if the replication state of the
node is ENABLED or DISABLED. To determine the
replication state, issue the QUERY NODE
FORMAT=DETAILED command.
ANR1627I
System action: The operation continues but the node

is skipped for this operation.
System action: The duplicate messages were

suppressed.
The previous message was repeated

repeat count times.
Explanation: The message issued prior to this message

was issued repeatedly.
System action: The duplicate messages were
suppressed.
User response: Verify that the nodes specified in the

command are configured for replication and try the
command again. Nodes may be configured for
replication with the UPDATE NODE command.
ANR1631I
command: Replication state information

for the specified nodes have been
removed.
Explanation: All replication state information for the

specified node has been removed from the database
and the node is no longer configured for replication. If
the node was a target of a replication operation it may
238
ANR1632E ANR1641E
now be used to accept client data.

ANR1637W

ANR1632E
command: Command failed. Replication

state information for the specified nodes
could not be removed.
Explanation: A REMVOVE REPLNODE command

failed to complete. The replication state for the
specified node is not changed.
User response: The server reported a problem running
the REMOVE REPLNODE command. See
accompanying messages for further information.
ANR1633E
Command: Node node name is set up for

replication and cannot be renamed or
removed.
Explanation: Any node that is set up for replication

on either a source or target replication server cannot be
renamed or removed.
System action: The requested operation fails.
User response: If you want to rename or remove the
node, you must first remove the node from replication
by issuing the REMOVE REPLNODE command.
Explanation: An error occurred while initializing the

server machine globally unique identifier (GUID).
User response: Handle problems appropriately. A
write error may occur because the server needs root
authority to write the GUID. A read error may occur if
the server does not have authority to read the GUID.
Other error codes are received from the GUID utility.
ANR1638W
Default replication server name set to

server name.
Explanation: The name of the default

target-replication server was set to the value that was
specified with the SET REPLSERVER command. If you
did not specify a value with the command, the existing
target replication server was removed, and client node
data will not be replicated.
Error (error) occurred initializing the

server machine GUID. Old value was
old GUID.
Explanation: An error occurred while initializing the

server machine globally unique identifier (GUID). The
old value is displayed.
User response: Handle problems appropriately. A
write error may occur because the server needs root
authority to write the GUID. A read error may occur if
the server does not have authority to read the GUID.
Other error codes are received from the GUID utility.
ANR1639I
ANR1634I
Error (error) occurred initializing the

server machine GUID.
Attributes changed for node nodeName:

changed attribute list.
Explanation: The TCP/IP name or address, or the

globally unique identifier (GUID) has changed for the
specified node. The old and new values are displayed
for entries that have changed.

ANR1640E

ANR1635I
The server machine GUID, machine

GUID, has initialized.
There is no data mover defined for node

node name.
Explanation: To perform the requested operation, the

specified node must have an associated data mover
defined.
Explanation: The specified globally unique identifier

(GUID) has initialized for the server machine.
User response: Define a data mover for the node and

retry the operation.

ANR1641E
ANR1636W
The server machine GUID changed: old

value (old value), new value (new value).
Explanation: The globally unique identifier (GUID)

has changed for the server machine. The old and new
values are displayed.
command: The node node name has a type

that is not allowed for this command.
Explanation: The node is not the correct type to be

used with this command.

239
ANR1642E ANR1649W
User response: Re-run the command with a node of
the correct type.
ANR1642E
command: The node node name is locked.
Explanation: The node is locked and cannot be used

in this command.
User response: Unlock the node and re-run the
command.
ANR1643I
Command: All file spaces for node node

name, will be moved.
Explanation: The server will attempt to move data for

all the file spaces for the specified node name based on
the criteria entered in the MOVE NODEDATA
command.
System action: Server moves data for the indicated
node.
ANR1644E
Command: Move node data operation

already in progress for storage pool
storage pool.
ANR1646I
Explanation: A node and filespace were entered in a

MOVE NODEDATA command but no filespaces were
found for the specifed node.
System action: The server continues to move other
filespaces for any other nodes specified in the MOVE
NODEDATA command.
ANR1647E
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
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
process ends.

representative.
ANR1648W
System action: The administrator is asked whether to

continue.
User response: Enter 'Y' to continue or 'N' to end the
process.
Command: Data for node node name,

filespace filespace name, FSID filespace ID
will be moved.
Explanation: The server will move data for the

specified filespace name and node name based on the
criteria entered in the MOVE NODEDATA command.
System action: The server moves data for the
specified node and filespaces.
Command:This command will move data

for nodes stored in volumes in storage
pool source storage pool to other volumes
within the same storage pool; the data
will be inaccessible to users until the
operation completes.
Explanation: A MOVE NODEDATA command has

been entered that will move data to other volumes in
the same storage pool. While the data is being moved,
it will not be available to users.
ANR1649W
ANR1645I
Cannot find file space name for node

node ID, file space file space ID.
Explanation: The server could not obtain filespace

information for that node.
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
or more nodes that have been specifed for that same
storage pool.
command.
Command: Node Node name, no filespaces

found to move for this node.
Command:This command will move data

for nodes stored in storage pool source
storage pool to storage pool destination
storage pool; the data will be inaccessible
to users until the operation completes.
Explanation: A MOVE NODEDATA command has

been entered that will move data from the source
storage pool to the destination storage pool shown.
While the data is being moved it, will not be available
to users.
continue.
User response: Enter 'Y' to continue or 'N' to end the
process.
240
ANR1650E ANR1658E
ANR1650E
Server server name is not defined.
Explanation: The server name was not created using

the DEFINE SERVER command. This entry was created
using the REGISTER NODE TYPE=SERVER command
and is not a valid reference.
System action: The current action for the device class
referring to this server fails.
User response: The device class referring to this node
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.
ANR1651E
Server information for server name is not

available.
Explanation: The information for server name was not

available.
SERVER entries were written to a device configuration

file. If this error persists, please contact your service
representative.
ANR1655E
Explanation: An error occurred processing the

password for server name while trying to write this
information to a device configuration file.
System action: This DEFINE SERVER entry is written
to the device configuration file without the password.
User response: The password needs to be specified
after PASSWORD= for this DEFINE SERVER entry in
the device configuration file.
ANR1656E
System action: The current server action fails.

User response: Please review any other messages
prior to this message to determine the cause of the
failure.
ANR1652E
Server information for server name could

not be read from a device configuration
file.
Explanation: An attempt to a server definition for

server name from any device configuration files failed.
User response: Please verify the existence of a device
configuration file and the DEFINE SERVER stanza
within that file.
ANR1653E
Resource lock acquisition for server

server name failed.
Explanation: The acquisition of the resource lock for

server server name failed.
User response: Retry the action referring to the device
class that refers to this server name. If the lock failure
persists, please contact your service representative.
ANR1654E
Server server name will not be written to

a device configuration file.
Explanation: An error occurred accessing the

information for server name while trying to write this
Failure processing password for Server

server name when writing a device
configuration file.
Failure writing server definitions to a

device configuration file.
Explanation: An error occurred writing the server

System action: The BACKUP DEVCONFIG action
fails.
User response: Check that the device configuration
file exists and that the file system the file resides on is
not out of space.
ANR1657E
Command: Invalid server or group name

- server or group name.
Explanation: The command shown specifies an invalid

server or server group name.
command.
name.
ANR1658E
Command: Failure determining

NODENAME for server server name.
Explanation: The command shown was unable to

determine a node name either from the NODENAME=
parameter on this command or from the server name
previously set using the SET SERVERNAME command.
command.
node name parameter or else update the server name
using the SET SERVERNAME command so that a valid
name is available.
System action: This DEFINE SERVER entry is not

processing.
User response: Verify that the necessary DEFINE
241
ANR1659E ANR1668E
ANR1659E
Command: Server or server group server

or group name is already defined.
Explanation: A DEFINE SERVER or DEFINE

SERVERGROUP command has been entered that
specifies a server or server group name that already
exists. The name specified must be a unique name. It
must not duplicate a node name used by a registered
node, a server name used by a defined server, or a
server group name used by a defined server group.
command.
User response: To define the server or server group,
reissue the command and specify a different name.
ANR1660I
Server server name defined successfully.
Explanation: The requested server has been defined to

the system in response to a DEFINE SERVER
command.
ANR1661I
Server server name deleted.
Explanation: In response to a DELETE SERVER

command, the requested server has been removed from
the system.

command.
User response: Reissue the command at a later time.
In order to delete the server specified, it must not be
currently connected to the server, it may not be
referenced in a device class, and it can not be defined
to be the event server.
ANR1665E
Explanation: An error occurred updating the

password for server name.
User response: Re-try the command specifying a
different password.
ANR1666E
Server server name updated.
Explanation: One or more attributes of a server have

been updated by an UPDATE SERVER command.
command: FILEAGGR not allowed with

TYPE=SERVER.
Explanation: The FILEAGGR= parameter may not be

specified with the TYPE=SERVER parameter also being
specified.
User response: Reissue the command command
without the FILEAGGR= parameter if this node is of
type SERVER.
ANR1667E

ANR1662I
command: Failure updating password for

server server name.
command: Action not permitted against

node node name.
Explanation: The command is not permitted against

the entry for node node name. This node entry has a
type of SERVER.

ANR1668E
ANR1663E
command: Server server name not defined
command: Not allowed for server server

name.
Explanation: The DELETE SERVER command is not

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.
Explanation: The server server name is not defined to

the system.
ANR1664W
Command: Server server name is currently

in use.
Explanation: The command shown specifies a server

that is currently in use. The server is referenced by one
or more of the following: a device class of
DEVTYPE=SERVER that specifies this server for the
'SERVERNAME=' parameter, it is defined as the event
server, or a connection with this server is currently
open and in use.
242
User response: If the specified server is the event

server, and you want to delete it, issue the DELETE
EVENTSERVER command and then reissue the
DELETE SERVER command. To remove a node entry,
issue the REMOVE NODE command for the specified
name.
ANR1669I ANR1680E
ANR1669I
Server event server name is defined as the

event server.
Explanation: The specified server is defined.

ANR1675I
Server group server group name deleted.
Explanation: The requested server is removed from

the system in response to a DELETE SERVERGROUP
command.

ANR1670E
Server event server name is already

defined as the event server. You must
issue the DELETE EVENTSERVER
command before defining a new event
server.
ANR1676I
Member member name deleted from

server group server group name.
Explanation: An event server is already defined.
Explanation: The requested member is removed from

the server group in response to a DELETE
GRPMEMBER command,
User response: Delete the existing Event Server and

try the command again.

ANR1677I
ANR1671I
The event server definition has been

deleted.
Explanation: The event server definition has been

deleted.
User response: If an event server definition is desired,

use the DEFINE EVENTSERVER command.
No event server is currently defined.
Explanation: A query was issued to get the name of

the event server; however, no event server is currently
defined.
ANR1678I
Server group original server group name

renamed new server group name.
Explanation: A server group is renamed by a

RENAME SERVERGROUP command. The original
name is not valid.

User response: If an event server definition is desired,
use the DEFINE EVENTSERVER command.
ANR1673I
Explanation: One or more attributes of a server group

is updated by an UPDATE SERVERGROUP command.
ANR1672I
Server group server group name updated.
Server group group name defined

successfully.
Explanation: The requested server group is defined to

the system in response to a DEFINE SERVERGROUP
command.
ANR1679E
Command: Server group server group name

not defined.
Explanation: The server server group name is not

defined to the system.
User response: Retry the command specifying an
existing group.

ANR1680E

ANR1674I
Member member name defined

successfully in server group group name.
Explanation: The requested member is defined in the

server group in response to a DEFINE GRPMEMBER
command.
Command: Member member name not

defined in server group server group
name.
Explanation: The member member name is not defined

in server group server group name.
User response: Retry the command specifying an
existing member of the group.
243
ANR1681E ANR1690E
ANR1681E
Command: Member member name is

already in server group server group
name.
Explanation: The member member name is defined in

server group server group name.
User response: Retry the command and specify a new
member name.
ANR1686I
Member member name moved from

server group group name to server group
new group name.
Explanation: The requested member member name is

moved from server group group name to the server
group new server group in response to a MOVE
GRPMEMBER command.
ANR1682E
A group cannot be a member of itself.
Explanation: The member and group name are the

same. A group may not be a member of itself.
ANR1687I
Output for command 'command' issued

against server server name follows:
Explanation: The output for the command issued

against the indicated server follows this message.
User response: Retry the command and specify

another member name.

ANR1683E
Command: Member member name not

defined.
Explanation: The member member name is not defined

to the system. Server group members must be a
defined server or server group.
User response: Retry the command specifying existing
server or group.
ANR1684E
Route:command: Routed commands

cannot be routed.
Explanation: The command part of a routed command

may not contain route information itself. The allowable
syntax for routed commands is :. The command may
not contain route information. Only one level of routing
is allowed.
System action: Routed commands where the
command portion contains additional routing
information are not processed.
specifying route information in the command portion
of this routed command.
ANR1685I
Server group server group copied to

server group new server group.

the COPY SERVERGROUP command. The server group
named server group is copied to the server group named
new server group.
244
ANR1688I

against server server name completed.
Explanation: This message marks the end of the

output for the command specified that was issued
against the indicated server.
ANR1689E

against server server name terminated.
Explanation: An error condition occurred causing the

output for the command issued against the specified
server to be terminated.
User response: Retry the command against the
requested server once the error condition has been
resolved. If the cause of the error can not be
determined, please contact your local service
representative.
ANR1690E
Error sending command 'command' to

server server name.
Explanation: An error was encountered sending the

specified command to the server indicated.
representative.
ANR1691E ANR1699I
ANR1691E
Error receiving response from server

server name for command 'command'.
Explanation: An error was encountered receiving the

response from the server indicated for the command
that was issued against it.
warnings did not prevent the execution of the

command.
ANR1696E

representative.
Explanation: The server indicated processed the

command but encountered errors. These errors
prevented the successful completion of the command.
Server server name attempted to process

command ' command' but encountered
errors.

ANR1692E
Response for command 'command' from

server server name contains invalid data.
Explanation: The output returned from the specified

server for the command that was issued, contains
invalid output. The command response can not be
processed.
System action: Output processing for this command
response terminates.
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
of the failure. Reissue the command once these errors
are corrected.
ANR1697I
User response: Please contact your local service

representative.
ANR1693E
Unable to issue command 'command'

against server server name - failure
starting thread.
Explanation: A thread could not be started to issue

the specified command against the server indicated.
System action: This command is not issued against
the server specified. The process will attempt to issue
the command against any other servers that were
specified for the command routing information.
error. Retry routing this command to the indicated
server after the cause of the error has been determined
and resolved. If the error cannot be isolated and
resolved, contact your service representative.
ANR1694I
Server server name processed command

'command' and completed successfully.

command successfully.
Command 'command' processed by total

number for servers server(s): number of
successful servers successful, number of
servers with warnings with warnings, and
number of servers with errors with errors.
Explanation: The indicated command was processed

by the number of servers specified. For the total
number of servers, the number indicated were
successful, the number indicated encountered a
warning condition but processed anyway, and finally,
the number indicated encountered errors and could not
process.
ANR1698I
Command 'command' was not issued

against any other servers.
Explanation: The indicated command was not issued

against any other server. Either the routing information
did not resolve to any valid servers or else failures
occurred issuing the command against the required
servers.
User response: Check to see that valid route
information was provided for the command or else
check the activity log for error messages that indicate
why the command was not issued to the other servers.

ANR1699I
ANR1695W
Server server name processed command

'command' but completed with warnings.

command but encountered warnings. However, the
Resolved route information to number of

servers server(s) - issuing command
command against server(s).
Explanation: The route information was resolved to

the number of servers indicated. The specified
command will be issued against those servers.
245
ANR1700E ANR1707E
ANR1700E
Unable to resolve 'route information' to

any server(s).
Explanation: The route information provided for this

command did not resolve to any server names or group
names. Because of this, the command will not be
issued.
User response: Examine the route information
provided. Reissue the command providing correct route
information.
ANR1701E
Command: No matching servers defined.
Explanation: No matching servers are found for the

specified command.
User response: Issue the command and specify
different servers.
ANR1702W
Skipping 'server name' - unable to resolve

to a valid server name.
Explanation: The server name specified is being

skipped because it could not be resolved to a valid
server name.
User response: Reissue the command providing the
correct server name.
ANR1703E
Failure resolving server names.
Explanation: An error occurred while resolving the

server names. Specifically, the resolution of the server
names has terminated because of a significant failure.
to perform these commands where the source server,

the target server, or both servers have authentication
enabled. The command should be retried using an
administrator other than SERVER_CONSOLE.
Check the activity log and server console for other
messages about the cause of the failure. Once the cause
has been resolved, reissue the command.
ANR1705W
Explanation: The ping command was unable to

establish a connection to the server specified. This
could indicate a problem on the server issuing the ping,
a problem with the communication connection between
the two servers, or else it is a problem with the other
server.
on the server issuing this command. Next, check the
communication connection between the two servers.
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
running.
ANR1706I
Ping for server 'server name' was able to

establish a connection.
Explanation: The ping command was able to establish

a connection to the server specified.
on the server issuing this command. Next, check the
communication connection between the two srevers.
And finally, verify the operation of the server specified.
ANR1707E

console for other messages about the cause of the
failure. Once the cause has been resolved, reissue the
command.
Ping for server 'server name' was not able

to establish a connection.
Server information not complete,

crossdefine not allowed.
Explanation: The SERVERHLADDRESS,

SERVERLLADDRESS or SERVERPASSWORD has not
been set for this server. These are required for the
CROSSDEFINE option on the define server command.
ANR1704E
Failure obtaining or using credentials

for administrator admin name.
Explanation: An error occurred obtaining or using the

credentials for the administrator referenced.
User response: Use the QUERY STATUS command to

find what values need to be set. An authorized
administratormust issue the SET SERVERHLADDRESS,
SET and SERVERLLADDRESS or SET
SERVERPASSWORD command to set the missing
values.
User response: If the administrator

SERVER_CONSOLE was being used for a PING or
VALIDATE LANFREE command, the command may
fail. The administrator SERVER_CONSOLE is not able
246
ANR1708I ANR1717E
ANR1708I
Define server for Server name failed

because the crossdefine failed.
Explanation: The define server command failed

because the crossdefine parameter was included, and
the crossdefine was not successful.
User response: Check this server, and the server being
defined for other messages indicating the reason for the
failure.
User response: Reissue the command from an

Administrative client.
ANR1713I
Command 'command' issued against

server server name.
Explanation: The specified command has been sent to

the indicated server. The command is to terminate the
specified server, no confirmation will be recieved.
ANR1709E
Command.: Failure determining current

usage for server or group name Server
name.
ANR1714W
Explanation: The specified command failed to

determine the current use of the server name or server
group specified.
User response: Retry the command. If it continues to
fail and the cause of the failure can not be determined,
please contact your local service representative.
ANR1710E
Command.: Name Name not valid for this

command.
Explanation: The name specified for this command is

not valid for this operation. The first case is that a
server name was specified for a command requiring a
server group name. The other case is where a server
group name was specified for a command requiring a
server name.
User response: Retry the command specifying the
proper name.
ANR1711E
Error accessing the server or server

group name Name.
The password for administrator

administartor name has expired. The
password for this administrator must be
updated on the configuration manager
server server name.
Explanation: The password for the named

administrator has expired, but the administrator is a
managed object on this server. The password must be
updated on the named configuration manager server.
System action: The administrator is allow access to
the server.
User response: Change the administrator's password
on the named configuration manager server.
ANR1715E
Event server cannot be deleted - it is

currently active.
Explanation: The event server cannot be deleted since

it is currently active for event logging.
System action: The server does not delete the event
server entry.
User response: In order to delete the event server, it
must not be currently active for event logging. To stop
event logging to the event server issue END
EVENTLOGGING EVENTSERVER. Then reissue the
DELETE EVENTSERVER command.
Explanation: A server operation attempted to access

the server name or server group name specified. An
error occurred while trying to access the information
for this server name or server group name.
ANR1716I
System action: The server operation fails.
Explanation: An attempt was made to crossdefine the

server to itself.
User response: Review the activity log to try to

determine the cause of the failure. If a cause can not be
determines, please contact your local service
representative.

ANR1717E
ANR1712W
Command routing not allowed from

server console.
Explanation: Command routing is not allowed from

the server console.
Server cannot be crossdefined to itself,

crossdefine not allowed.
Command: Command failed Non-Compatible Filespace name types

have been specified.
Explanation: A server command has been entered but

cannot be processed because Non-Compatible Filespace
name types have been specified.
247
ANR1718E ANR1725E
command.
User response: Specify compatible filespace names.
Unicode to Unicode or Non-Unicode to Non-Unicode.
ANR1718E
Command: Reconstruction of file

aggregates is supported only for
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
operation for which reconstruction is not supported.
Aggregates are reconstructed only when both the
source storage pool and the target storage pool are
sequential-access.
command.
specifying that aggregates should be reconstructed.
Alternatively, specify a move operation involving
transfer of data within a sequential-access storage pool
or between two sequential-access storage pools.
ANR1719E
Storage pool storage pool name specified

on the MOVE NODEDATA command is
not a valid pool name or pool type.
Explanation: If the source storage pool specified in the

command is a primary storage pool, then the
destination storage pool specified must also be a
primary storage pool. If the source storage pool is a
copy storage pool, then the specified destination
storage pool must be the same storage pool as the
source storage pool.
System action: The MOVE NODEDATA process fails.
User response: Provide a valid primary storage pool
name as the destination storage pool if the source pool
is a primary storage pool. If the source pool is a copy
storage pool do not specify a destination pool, or,
specify the same copy storage pool as the destination
pool.
ANR1720I
A path from source name to destination

name has been defined.
Explanation: In response to the DEFINE PATH

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

name has been deleted.
Explanation: In response to the DELETE PATH

command or to an UPDATE DEVCLASS command
with the MOUNTLIMIT parameter, the path from the
source name to the destination name has been deleted
in the server database.
ANR1722I

name has been updated.
Explanation: In response to the UPDATE PATH

command, the path from the source name to the
destination name has been updated in the server
database.
ANR1723E
A path is already defined using source

name and destination name.

command, the server determines that a path with the
same source name and the same destination name
already exists in the server database.
User response: Correct the source name or destination
name and re-enter this command.
ANR1724W
Command: Server server name is currently

in use.
Explanation: The command shown specifies a server

that is currently in use. The server is referenced in a
PATH used for LANFree access to a FILE device type
drive in a shared library.
command.
In order to delete the server specified, it must not be
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
PATH definition as a FILE device type drive.
ANR1725E
resource name is not defined.

command, a resource name was provided that has not
been defined.
User response: Define the source name or the
248
ANR1726E ANR1736E
destination name and re-enter this command.
ANR1726E
A operation using the path from

sourcename to destname is currently being
used.
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.
ANR1731I
Data mover mover name has been

deleted.
Explanation: The data mover has been deleted in the

server database.
ANR1732I
User response: Wait until the operation using this

path is complete, or cancel the operation using this
path, and then reissue the command.
Explanation: The data mover has been updated in the

server database.

updated.

ANR1727E
A path from sourcename to destname does

not exist.
Explanation: The path being updated or deleted does

not exist.
source or destination name or define a new path.

ANR1733E
Data mover mover name is already

defined.
Explanation: A DEFINE DATAMOVER command was

entered for a data mover that already exists in the
server database.
ANR1728E
The library libname is not a SCSI or VTL

library.
Explanation: A drive that is to be used by a NAS data

mover must be attached to a SCSI or VTL library.
User response: Use the UPDATE DATAMOVER to

change the attributes in this data mover. Otherwise use
a different data mover name.
Data mover mover name is not defined.
ANR1734E

drive name.
Explanation: An UPDATE DATAMOVER command

was entered for a data mover that does not exist in the
server database.
ANR1729E
A path using the data mover source name

still exists.
Explanation: In the DELETE DATAMOVER command,

the data mover name supplied is either the source or
the destination in a path that still exists in the server
database.

User response: Correct the data mover name or use
the DEFINE DATAMOVER command to define a new
data mover.
ANR1735E

User response: Delete the existing path and reissue
this command.
ANR1730I

defined.
Explanation: The data mover has been defined in the

server database.
Data mover data mover is currently being

used.
Explanation: A data mover was in use when the

command was entered. The attributes of a data mover
may not be changed while it is being used.
User response: Wait until the operation using this
data mover is complete, or cancel the operation using
this data mover, and then reissue the command.

ANR1736E
Command: Parameter parameter length is

invalid.
Explanation: The specified server command has been

entered with a parameter that is longer or smaller in
length than the allowed length.
249
ANR1737E ANR1746E
User response: Reissue the command and enter the
proper syntax.
ANR1737E
Command: Device name device specified

is invalid.
Explanation: The specified command has been entered

with an invalid device name.
device name.
ANR1738I
Unable to begin a server-free operation

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
was unable to do so.
User response: The server-free data movement will
fail and the client may retry the request using LAN or
LAN-free data transfer.
ANR1739I
Unable to update configuration of data

mover data mover name; received error
error.
Explanation: The server attempted to notify the

specified data mover that a change in the SAN requires
that the configuration be updated. The update failed
because the data mover was busy.
User response: The data mover must finish its current
operation before the configuration can be updated. The
server-free data movement will fail and the client will
retry the request using LAN or LAN-free data transfer.
ANR1740E
For the path defined from disk node

name disk name received lun actual lun
from client, expected expected lun.
Explanation: A client attempted to backup the disk,

but the server path definition was different than that
which was detected by the client.
User response: Correct the path definition from the
disk to a datamover.
which was detected by the client.

User response: Correct the path definition from the
disk to a datamover.
ANR1742E
Explanation: An operation requested the specified

disk. The disk cannot be used because it is not online.
User response: Determine the reason for the disk
being offline; if possible, update the disk status to
online.
ANR1743E
For the path defined from disk node

name disk name received serial number
actual serial from client, expected expected
serial.
Explanation: A client attempted to backup the disk,

but the server path definition was different than that
250
The path from data mover datamover

name to disk node name disk name is not
online.
Explanation: An operation requested the specified

disk. The disk cannot be used because the path from
the datamover to the disk is not online.
User response: Determine the reason for the path
being offline; if possible, update the path status to
online.
ANR1744E
The world wide name is invalid for the

destination of the path being defined.
Explanation: A path was being defined from a

datamover to a destination and that destination has an
incorrect world wide name specified.
User response: Update the destination's definition
with the correct world wide name.
ANR1745I
Unable to discover SAN devices.

Function is busy.
Explanation: The SAN device discovery function is

busy. The requested query cannot be completed at this
time.
User response: Reissue the request when current
queries have completed.
ANR1746E
ANR1741E
The disk node name disk name is not

online.
The path from data mover datamover

name to drive library name drive name is
not online.
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.
ANR1747E ANR1756I
User response: Determine the reason for the path
being offline; if possible, update the path status to
online.
ANR1747E
The library libname is not a ZOSMEDIA

enabled library.
Explanation: Defining a PATH to a library using the

ZOSMEDIASERVER parameter requires the library be a
ZOSMEDIA library ( e.g., DEFINE LIB libname
LIBTYPE=ZOSMEDIA ).
ANR1751I
Disk disk name has been defined.
Explanation: In response to the DEFINE DISK

command, the disk has been defined in the server
database.
ANR1752E
Disk disk name is already defined.
Explanation: A DEFINE DISK command was entered

for a disk that already exists in the server database.

library name.
ANR1748W
The disk node name disk name was not

found on the SAN. The path definition
for this disk has been marked offline.
Explanation: During device discovery on a storage

area network a device was not found that has the same
serial number as the disk defined to TSM.
User response: Verify that the serial number of the
disk definition is correct and that the disk is
operational.
ANR1749W
The drive library name drive name was not

found on the SAN. The path definition
for this drive has been marked offline.
Explanation: During device discovery on a storage

area network a device was not found that has the same
serial number as the drive defined to TSM.
User response: Verify that the serial number of the
drive definition is correct and that the drive is
operational.
ANR1750E
The server detected an internal error,

return code = return code.
User response: Use the UPDATE DISK command to

change the attributes of this disk. Otherwise, use a
different disk name.
ANR1753E
Disk disk name is currently being used.
Explanation: A disk was in use when the command

was entered. The attributes of a disk may not be
changed while it is being used.
User response: Wait until the operation using this disk
is complete, or cancel the operation using this disk, and
then reissue the command.
ANR1754E
Disk disk name is not defined.
Explanation: An UPDATE, DELETE or client function

requested the specified disk, but the disk has not been
defined to the server.
User response: Correct the disk name or use the
DEFINE DISK command to define a new disk.
ANR1755I
Disk disk name has been updated.
Explanation: In response to the UPDATE DISK

command, the disk attributes have been updated in the
server database.
Explanation: An unexpected error occured during

server operation.

found and resolved, retry the operation. If the failure
cannot be found, contact your service representative for
assistance in resolving the problem.
ANR1756I
Disk disk name has been deleted.
Explanation: In response to the DELETE DISK

command, the disk has been deleted in the server
database.
251
ANR1757E ANR1764E
ANR1757E
A path using the disk disk name still

exists.
ANR1761E
Command: Command failed for node

node name, filespace filespace name storage media is inaccessible.
Explanation: The name supplied in a DELETE DISK

command is the destination in a path that still exists in
the server database.
Explanation: The indicated command failed because

required storage media is unavailable.
User response: Delete the existing path using the

DELETE PATH command and re-enter the DELETE
DISK command.
User response: Ensure that there are sufficient

volumes available for storing backups and that any
volumes required for restore are checked in and
available. Correct the problem and try the command
again.
ANR1758E
A path from disk node name disk name to

a datamover cannot be determined.
Explanation: During a backup operation a path from

the disk cannot be found.
User response: Define a path from the disk to a
datamover.
ANR1759E
Command: A device with SCSI

datamover capabilities was not found in
the system configuration for datamover
datamover name.
Explanation: The scsi address could not be

determined for a device that is capable of performing
datamover operations.
User response: Verify that the hardware that can
perform SCSI datamover operations is installed and
powered on.
ANR1760E

node name, filespace filespace name destination storage pool storage pool was
skipped.

the destination storage pool was skipped. A storage
pool may be skipped because it does not have enough
available space, or because it has a MAXSIZE value
that is less than the size of the object to be inserted.
User response: Ensure that the destination storage
pool is available, has an adequate MAXSIZE setting,
and has adequate space. The MAXSIZE setting may be
changed using the UPDATE STGPOOL command.
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
them online and make them available for use. Correct
the problem and reissue the command.
252
ANR1762E

node name, filespace filespace name mount point unavailable.

sufficient mount points are not available.
User response: Ensure that sufficient mount points are
available and working correctly. Correct the problem
and try the command again.
ANR1763E
Command: Command failed - see

previous error messages or view the
activity log.
Explanation: The indicated server command has

failed. This message is always preceded by one or more
other error messages which provide more detail about
why the command failed.
to determine the source of the error. Use the QUERY
command again.
ANR1764E
Command: Command failed - loadable

module module name is not available.
Explanation: The indicated server command has failed

because it requires the availability of the specified
loadable module, but the module is not loaded.
User response: Make sure the necessary loadable
module is available for your platform. Not all modules
are available on all platforms. If the module is available
for your platform and is installed, contact your service
representative for assistance.
ANR1765E ANR1772E
ANR1765E
Command:The number of copy threads

entered, copythreads, exceed the
capabilities of the datamover.
Explanation: A datamover has an upper limit of the

number of copy threads that it is capable of executing.
The copythreads parameter provided is greater than
this limit.
User response: Make sure the value entered for the
copythreads parameter is less than the maximum for
this datamover. Using the default for the number of
copythreads sets the number of copythreads to the
datamover's maximum value.
ANR1766I
The number of sessions currently active

for datamover datamover, exceed the
number of copy threads defined for this
datamover.
Explanation: The datamover definition has a paramter

that is used to limit the number of operations involving
that datamover. This limit was reached.
System action: The operation continues using another
method.
User response: Verify that the number of copy threads
in the datamover definition is sufficient enough to
allow mutliple server-free operations, or define another
datamover to handle additional server-free operations.
User response: Specify a valid DEVICE parameter that

is not used by any other drive or library.
ANR1769E
Explanation: A server script that performs multiple

actions between commit actions is not allowed. For
example, deletion of multiple paths before each of the
deletions is committed is not allowed.
command.
User response: Rewrite the script or macro so that no
new command is issued until the previous command is
committed.
ANR1770E
A datamover with a online path to both

the disk, nodename diskname, and the
drive, libraryname drivename cannot be
found.
Explanation: To perform server-free data movement, a

path must exist from the datamover to both the disk
and the drive. If either path is not defined or is offline
to all datamovers defined then the data movement
cannot occur via server-free.
System action: The operation continues using another
method.
User response: Define the appropriate paths from a
datamover to the disks and drives. If a path is defined
from a datamover to a drive in a library then all drives
in that library should have paths defined from that
same datamover. A path may have to be updated to
specify online=yes.
ANR1768E
Command: The device name provided

conflicts with a device name that is
already in use.
Explanation: The device name provided in the

command is already used by an existing path.
Processing for session session id found

destination new destination. Expected
current destination.
Explanation: While processing a remote image

operation, the specified session was working with the
current destination. But the server received a client
request with a new destination name.
User response: From the client, quit the current
remote image request. Reissue the request, if desired.
ANR1771E
ANR1767W
Command: Command failed - multiple

actions between commit actions not
allowed.
The path from remote server remote

server name to destination destination name
with the destination device type is not
valid.
Explanation: The library manager receives a command

to update the path for the remote server. The device
type field of the destination device is not valid. The
destination for update path from remote server must be
either drive or library.
User response: Determine why the device type field of
the destination device is not valid.
ANR1772E
The path from source source name to

destination drive name is taken offline.
Explanation: The path is now marked offline.

System action: The path is inaccessible.
User response: Determine the reason the path is
inaccessible, such as a hardware problem. Make any
needed corrections. Then, issue the the UPDATE PATH
command with the ONLINE=YES option to make the
path online.
System action: The command is not processed.
253
ANR1773W ANR1782W
ANR1773W
Unable to update the path in the

database path source name and drive drive
name .
Explanation: The system is unable to update the path

information in the database table.
System action: .
ANR1774E
The Query Status command failed, and

server initialization has not completed.
Allow server initialization to complete,
and then try the command again.
Explanation: The command Query Status failed

because server initialization has not completed.
v One of the parameters specified during datamover

update was incorrect: TCP/IP address of the file
server, user id, password, TCP/IP port
v File server is not accessible
v NDMP server limits the number of opened NDMP
sessions
System action: The data mover definition is updated.
User response: Check that the file server associated
with the data mover is accessible through the network;
check each of the attributes specified in the datamover
update command; check the number of open NDMP
sessions with the file server.
ANR1777I

User response: Allow server initialization to complete,
and then try the command again.
ANR1775I

defined, however a connection to the
data mover failed. Please check the
attributes of the file server specified in
the definition of the data mover.
Explanation: The data mover has been defined in the

server database, however the server cannot connect to
the file server associated with the data mover. The
connection failed because of one of the following
possible reasons:
definition was incorrect: TCP/IP address of the file
Explanation: The server reported a problem with the

specified object. See accompanying messages for further
information.
ANR1778E
User response: Check that the file server associated

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
with the file server.
Command: Invalid or missing parameter.

entered with an invalid parameter, or, is missing a
required parameter.
proper syntax.
ANR1779I

sessions
System action: The data mover is defined to the
server.
module(offset): Object object id hi.object id lo

is object name for node node name (node
id), filespace filespace name (filespace id ).
backupset process name process completed:

successful count backupset(s) were
generated or defined out of total count
backupset(s) requested by the
command's specifications.
Explanation: A GENERATE or DEFINE BACKUPSET

command has finished successfully, and the backupsets
described in previous messages have been created.
System action: The backupsets described have been
created.
ANR1776I

updated, however a connection to the
data mover failed. Please check the
attributes of the file server specified in
the update command.
Explanation: The data mover has been updated in the

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:
254
ANR1782W
ESTIMATE DBREORG process process

number started - server performance may
be degraded while this process is
running.
Explanation: The ESTIMAGE DBREORG process has

been started as the reported process number. This
process estimates the amount of space that the database
will reduced by if a database reorganization is
performed.
ANR1783E ANR1790W
System action: This process performs extensive
database I/O and may impact other server operations
and processes while it is running.
User response: This process may be monitored using
the QUERY PROCESS command. If this process needs
to be cancelled, issue the CANCEL PROCESS
command.
ANR1783E
ESTIMATE DBREORG process process

number failed and only evaluated pages
evaluated database pages.
Explanation: The ESTIMATE DBREORG process failed

to complete successfully. It only evaluated pages
evaluated database pages.
User response: If the has been cancelled, this message
will be issued. If this processed failed to process but
was not cancelled, it is likely that it failed because it
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
space recovered MB.
Explanation: The ESTIMATE DBREORGSTATS process

completed and determined that the database space
utilized would be reduced by space recovered megabytes
if a database reorganization were performed.
System action: Server operations continue normally,
and the ESTIMATE DBREORGSTATS process
completes.
User response: This message reports the estimated
database space recovered if a database reorganization
were to be performed. The Tivoli Storage Manager
administrator should evaluate this information relative
to their current database utilization, expected database
growth and changes, and determine whether or not a
database reorganization is needed for this server. To
reorganize the server database, refer to DSMSERV
UNLOADDB, DSMSERV LOADFORMAT, and
DSMSERV LOADDB in the Administrator's Reference.
ANR1785I
ESTIMATE DBREORG process is

already running.
Explanation: The ESTIMAGE DBREORG process is

already running. The server does not allow more than
one instance of this process to be running at a time.
ANR1786W
HBAAPI not able to get adapter name.
Explanation: The HBAAPI function getAdapterName

failed. The server will continue to access next adapter if
it exists.
discovery will not work with this Host Bus Adapter.
For the list of supported HBAs and required driver
levels by operating system go to http://
WWW.IBM.COM/SUPPORT.
ANR1787W
Unable to open adapter adapter name.
Explanation: The HBAAPI function to open the host

bus adapter (HBA) failed.
discovery will not work with this Host Bus Adapter.
ANR1788W
Unable to retrieve the adapter attributes

for adapter name.
Explanation: The HBAAPI function failed to retrieve

the adapter' attributes. This problem is caused by a
nonfunctional Fibre Channel adapter on the system.
Check this adapter to ensure it works properly. This
problem also can be caused by other non Fibre Channel
types of adapters on the system, such as, a SAS or a
parallel SCSI adapter. This message can be ignored if
you are using a non Fibre Channel adapter.
User response: SAN discovery does not work for this
adapter. For the list of supported HBAs and required
driver levels by operating system visit
http://WWW.IBM.COM/SUPPORT.
ANR1789W
Get HBA target mapping failed.
Explanation: The HBAAPI function to get the target

mapping failed.
User response: SAN discovery will not work for this
adapter. For the list of supported HBAs and required
driver levels by operating system go to
http://WWW.IBM.COM/SUPPORT.

to monitor the existing process. If the existing process
needs to be cancelled, issue the CANCEL PROCESS
command.
ANR1790W
SAN discovery failed.
Explanation: SAN discovery failed.

User response: SAN discovery failed. This may be a
255
ANR1791W ANR1796E
problem with the HBA firmware, HBA or the HBA
verdor's HBAAPI driver. For the list of supported
HBAs and required driver levels by operating system
go to http://WWW.IBM.COM/SUPPORT.
ANR1791W
HBAAPI wrapper library file name failed

to load or is missing.
Explanation: This library is provided by Tivoli Storage

Manager. It is required for discovery of devices on a
SAN.
v For windows, the HBAAPI wrapper library is
hbaapi.dll.
v For AIX, the HBAAPI wrapper library is
libHBAAPI.a.
ANR1793W
TSM SAN discovery is not supported on

this platform or this version of OS.
Explanation: SAN discovery for this platform is

currently not supported.
User response: SAN discovery will not work for this
platform.
v For AIX, we only support AIX5.2F and above
v For HP, we do not support this platform yet.
v For Linux, we do not support Linux-zOS yet.
v For Windows, we do not support Windows 2003 64
bit yet.
For Solaris, the HBAAPI wrapper library is

libhbaapi32.so for 32 bit application and
libhbaapi64.so for 64 bit application.

For Linux, the HBAAPI wrapper library is

libhbaapi32.so for 32 bit application and
libhbaapi64.so for 64 bit application.
ANR1794W

User response: Make sure the HBAAPI wrapper
library for this platform is in the same directory as the
IBM Tivoli Storage Manager server executable. AIX is
the only exception with HBAAPI wrapper library
libHBAAPI.a in /usr/lib.
ANR1792W
HBAAPI vendor library failed to load or

is missing.
Explanation: The HBAAPI vendor library failed to

load or is missing. This HBAAPI library is provided by
the Host Bus Adapter (HBA) vendor. It is required for
Tivoli Storage Manager server to discover devices on
the SAN.
Explanation: SAN discovery is disabled by option

SANDISCOVERY OFF or SANDISCOVERY
UNSCANNEDPATHOFF.
User response: SAN discovery is currently disabled
either by default by the SANDISCOVERY OFF option
depending on the platform or by the SANDISCOVERY
UNSCANNEDPATHOFF option. For the list of
supported HBAs and required driver levels by
operating system go to http://WWW.IBM.COM/
SUPPORT.
ANR1795I

User response: Ensure the HBAAPI file exists on the
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
supported HBAs and required driver levels by
operating system go to http://WWW.IBM.COM/
SUPPORT. The following is an example of some of the
HBA vendor's HBAAPI file:
v
For UNIX systems, This HBAAPI vendor library's

location is indicated in /etc/hba.conf. For example:
qla2x00
/usr/lib/libqlsdm.so
com.emulex.emulexapilibrary
/usr/lib/libemulexhbaapi.so
v For Windows systems, verify the location of the

HBAAPI vendor library by checking LibraryFile in:
HKEY_LOCAL_MACHINE
SOFTWARE
SNIA
HBA
<HBAAPI library>
256
TSM SAN discovery is disabled by

options.
The device driver has been updated

successfully for device old device name.
The new device name is new device name.

the CHANGE DEVDRIVER command. The device
driver for device old device name has been updated
successfully.
ANR1796E
Invalid device name device name.
Explanation: The device name is not in the form of

TAPEx or CHANGERx.
User response: Change the device name to TAPEx or
CHANGERx and retry the command.
ANR1797E ANR1804W
ANR1797E
Device device name is not supported by

the IBM Tivoli Storage Manager device
driver.
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
Manager device driver INF file, i.e. tsmlb.inf and
tsmmt.inf.
ANR1801E
Eventlog command: Invalid event or event

class - Event or event class name.
Explanation: An event logging command has been

entered which specifies an unknown event or event
class.
System action: The command is ignored for the
invalid event or event class. Any valid events or classes
specified are processed.
event or event class.
User response: Access the Tivoli Storage Manager

Web site at www.ibm.com/software/sysmgmt/
products/support/IBMTivoliStorageManager.html and
navigate to the device support information for the
server's operating system. Verify if the device is
supported. If the device is supported by the IBM Tivoli
Storage Manager device driver, contact your service
representative.
Explanation: The device was not found in the device

information set. The vendor ID and/or product ID, or
device name may be invalid, or the device has been
removed from the system.
ANR1798E

fails.
Device driver update failed for device

device name.
Explanation: The CHANGE DEVDRIVER operation

failed for device device name.
ANR1802E
Device device name was not found.

vendor ID and product ID, or device name.

fails.
ANR1803W
Explanation: The server attempted to load the SAN

discovery module, but the permissions or ownership of
the file are incorrect.
ANR1799E
The Tivoli Storage Manager device

driver is not installed, or one or more
device driver files are missing.
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.
User response: Make sure the Tivoli Storage Manager
device driver is installed. and the following files are not
missing. %WINDIR%\system32\drivers\tsmscsi.sys (or
tsmscsi64.sys for 64-bit Windows), %WINDIR%\inf\
tsmmt.inf, and %WINDIR%\inf\tsmlb.inf.
ANR1800E
Missing or invalid EVENTLOG

command parameter.
Explanation: The event logging command issued

contains an invalid parameter, or is missing a required
parameter.
User response: Reissue the command with the proper
parameters.
SAN discovery module module name is

not installed correctly.

without SAN discovery function.
User response: Ensure that the SAN discovery module
is executable, has the setuid bit turned on, and is
owned by root. The SAN discovery module is called
'dsmqsan' and must reside in the server or storage
agent executable directory.
ANR1804W
Command: Process process number

skipping volume volume name in storage
pool pool name because the volume is in
use by another process.
Explanation: The command shown specifies the

volume to be processed, but that volume is currently
being used by another operation.
System action: The server skips the volume and
processes the next available volume.
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
process the skipped volume.
257
ANR1805E ANR1814W
ANR1805E
command: Invalid value paths for

NUMDBDIRS parameter.
invalid receiver. Any valid receivers specified are

processed.
receiver.
Explanation: During processing of command EXTEND

DBSpace command, an invalid value is encountered for
the NUMDBDIRS parameter. The value should be from
1 to 3
ANR1811W

User response: Issue the command with a valid value.

ANR1806I
Table reorganizing and updating

statistics performed successfully for
processed table.
Explanation: Reorganize and Runstat successfully run

on that table.
User response: Your version of the HBA API file

might not be supported. Go to the HBA vendor's
website to obtain the latest version of the HBA API. For
a list of supported HBAs and required HBA API levels
by operating system, go to http://www-1.ibm.com/
support/docview.wss?uid=swg21193154.
ANR1812E

ANR1807I
Table updating statistics performed

successfully for processed table.
Explanation: Runstat successfully run on that table.

ANR1808E
Unable to open event log file file spec for

appending.
Explanation: The server cannot write to a file which

has been specified for event logging.
HBAAPI returned zero FC adapters from

the system.

node node name failed deletion because
of a replication in progress.
Explanation: The reported filespace belonging to the

reported node is currently being replicated as part of a
REPLICATE NODE command. A filespace cannot be
deleted while the replication is in progress.
System action: The DELETE FILESPACE ends with a
state of FAILURE.
to view active REPLICATE NODE processes. Either
wait for the replication to complete or cancel the
replication process with the CANCEL PROCESS or
CANCEL REPLICATION commands, and reissue the
DELETE FILESPACE command.
Filespace filespace name for node node
name is a replication replication role.
System action: No logging will be done to the file

receiver.
ANR1813W

permissions, or specify a different file for logging.
Explanation: The reported filespace is either the

source or target of a replicated node. The DELETE
FILESPACE command will delete the data on this
server, but will not delete the data on any other
replication servers.
ANR1809E
Insufficient memory to activate event

logging.
Explanation: A BEGIN EVENTLOGGING command

has been entered, but the server has insufficient
memory available to activate logging.
User response: If logging is required, make more
memory available to the server then restart the server.
ANR1810E
Eventlog command: Invalid receiver receiverName.

entered which specifies an unknown event log receiver
(maybe unknown just to this platform).
258
System action: The DELETE FILESPACE command

continues.
User response: If this message indicates this filespace
is the source of replicated data, then login to all servers
containing replicated data from this filespace and issue
the DELETE FILESPACE command to remove the data
from those servers. If this message indicates this
filespace is the target of replicated data, ensure that the
filespace on the source server is either deleted, or
updated to no longer replicate to this server.
ANR1814W
The database manager cannot load the

security plugin file name.
Explanation: The database manager cannot load the

security plugin. This plugin controls access to the
ANR1815W ANR1819E
database manager from the Tivoli Storage Manager
server.
User response: Inspect the DB2 diagnostic log file to
identify the reason the database manager cannot load
the security plugin. Correct the problem and restart the
server.
ANR1815W
Check target server for storage problems

during replication of node node list.
Explanation: During the replication process for the

specified nodes, there were problems storing data at
the replication target server.
filespace name that can be specified on a restore

command. The line consists of four fields, separated by
tabs:
v Node ID - a numeric identifier for the node that
owns the file.
v Node Name - the name of the node associated with
the node ID.
v Filespace ID - a numeric identifier for the file's
filespace.
v Filespace Name - the name of the filespace associated
with the filespace ID.
User response: Inspect the contents of the specified
log file. If necessary, use the information in the log file
to restore the files to their original name.

User response: Check the activity log of the target
server for specific error messages relating to data
storage during the replication process.
ANR1816W
The names of one or more files were

truncated. Examine log file log file name
for details.

attempted to insert a database row describing a file
whose path name is longer than the maximum path
name supported by Tivoli Storage Manager V6. The
Tivoli Storage Manager V5 server supported path
names of up to 8000 bytes, but the V6 server does not
allow path names to be longer than 6000 bytes.
System action: The name of the file was replaced by a
system-generated name. Information needed to restore
the file to its original name was written to the specified
log file.
The log file contains two sections. The first section lists
files whose names were truncated. The second section
identifies the node names and filespace names of the
truncated files.
ANR1817W
command: No valid nodes were

identified for import on target server
tgtServerName.
Explanation: During a server-to-server export, the

import process on the target server reported that none
of the node definitions in the export data were valid for
import. No node data was imported on the target
server.
User response: Check for warning or error messages
on the target server and handle as needed.
ANR1818W
command: No valid nodes were

identified for import.
Explanation: During a server import process none of

the node definitions in the import data were valid for
import. No node data was imported.
User response: Check for warning or error messages
during the import process on the server and handle as
needed.
The first section is identified by the header "-Truncated Files --". Each line of this section identifies
one file whose name was truncated. The line consists of
four fields, separated by tabs:
ANR1819E
v Node ID - a numeric identifier for the node that

owns the file.
Explanation: The operating system generic SCSI

device driver and IBM device driver require that users
have a root user ID in order to open the drive.
v Filespace ID - a numeric identifier for the file's

filespace.
v New Name - the system generated name that was
assigned to the file.
v Original Name - the original name of the file.
The second section is identified by the header "-- Node
and Filespace Names --". Each line in this section maps
the node ID and filespace ID associated with one or
more of the files in the first section to a node name and
A DB2 instance ID cannot be used to

open device file device name.

User response: To open this device, change the device
file attribute statements and then retry the operation.
See Technote 1321130 for details about resolving this
problem: https://www.ibm.com/support/
docview.wss?uid=swg21321130
259
ANR1820E ANR1827E
ANR1820E
The server could not connect to the

database manager by using TCP/IP port
port number.
Explanation: The server attempted to connect to the

database by using TCP/IP, but it was not able to do so.
User response: First, verify that the port number is
not already in use. Possible methods include:
v On Unix systems, inspect /etc/services for an
occurance of the port number.
v Use the netstat command to determine if a service is
listening on the port number.
If a conflict is detected, specify a different port number
on the DBMTCPPORT option in the server options file
If no conflict is found, use the "db2 get database
manager config" command to verify that the
SVCENAME configuration parameter is set to the port
number identified by the message. If not, then use the
"db2 update database manager config using
SVCENAME port number" command to manually
update the configuration parameter. Ensure that the
value specified is also specified on the DBMTCPPORT
server option. Restart the server.
Finally, use the "db2set" command to verify that the
DB2COMM environment variable is set to "TCPIP". If
not, then use the "db2set DB2COMM=TCPIP"
command to set the environment variable and restart
the server.
ANR1821W
Event logging is not started for the

receiverName receiver.
Explanation: In response to a BEGIN

EVENTLOGGING command, recording of event log
records to the specified receiver was attempted. The
event logging for the specified receiver is already
started because either the receiver is currently running
or the receiver was terminated previously and is still in
the process of writing the messages that were queued
up for processing.
User response: Check to see if the event log receiver is
already started by issuing the QUERY STATUS
command, and checking the Active Receivers field.
Some event log receivers such as FILETEXT,
FILETEXTEXIT, USEREXIT, and Tivoli receiver, can be
started during server initialization if they are
configured in the server options file.
v If the event log receiver is already started you do not
take any further action.
v If the event log receiver is not currently running then
wait and try to start it again after a short delay.
260
ANR1822I
Event logging ended for the receiverName

receiver.
Explanation: In response to an END

EVENTLOGGING command or because an error
occurred, event log records are no longer being output
to the specified receiver.
ANR1823I
Event logging ended for all receivers.
Explanation: In response to an END

EVENTLOGGING command, event log records are no
longer being output to any receiver.
ANR1824E
Event logging is inactive for the

specified receiver.
Explanation: An END EVENTLOGGING command

has been entered, but logging is not active for the
specified receiver.
User response: If logging is desired, use the ENABLE
EVENT and BEGIN EVENTLOGGING commands to
activate event logging.
ANR1825I
Event logging active for the receiverName

receiver.

EVENTLOGGING command, event log records are now
being output to the specified receiver.
ANR1826I
Event logging active for all receivers.

EVENTLOGGING command, event log records are now
being output to all receivers.
ANR1827E
Eventlog command: No valid receiver

specified.

entered, and no valid receivers were specified.
receiver.
ANR1828E ANR1851E
ANR1828E
Eventlog command: No valid event

specified.

entered and no valid events or event classes were
specified.
Eventlog command: Server events may not

be disabled for the activity log receiver.
Explanation: A DISABLE EVENT command has been

entered for the activity log receiver.
activity log receiver. Any valid receivers specified are
processed.
Explanation: Initialization is starting for the eventlog

receivers.
ANR1844I

User response: If any previous messages indicate that
parts of the command failed, reissue the command for
those parts only.
ANR1850E
receiverName receiver options not defined

in the server options file.
Explanation: A BEGIN EVENTLOGGING command

has been entered for a receiver, but the required
receiver options were not specified in the server
options file.
System action: Logging is not started for the specified
receiver.
User response: Enter the receiver options in the server
options file and restart the server.
ANR1831I
Event logging of client events ended for

ACTLOG receiver.
Explanation: An END EVENTLOGGING command

has been entered for the activity log receiver.
System action: The server no longer records client
events in the activity log. Server events continue to be
recorded in the activity log.
ANR1842E
An error occurred on the receiverName

receiver.
Explanation: An error occurred on the specified

receiver.
System action: The server no longer sends events to
the receiver.
User response: Issue a BEGIN EVENTLOGGING
command for the receiver to attempt to start logging
events to the receiver again.
Eventlog command command processed.
Explanation: The specified command was processed.

receiver.
ANR1830E
Event log receiver initialization in

progress.

events or event classes.
ANR1829E
ANR1843I
Circular event logging detected. The

event server has previously handled
event Event number from Source trail. To
prevent looping, events which have
already been logged by the event server
are not sent again. Please correct the
situation causing circular logging to
avoid wasting system resources.
Explanation: The server is attempting to log an event

which has previously been handled by the event server
that is currently defined.
System action: The event is not sent to the event
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
server to server event logging setup, and fix the
problem.
ANR1851E
The source trail for server to server

event logging has exceeded the
maximum length of Maximum sourcetrail
length bytes.
Explanation: While attempting to log an event to the

event server, the server has found that the source trail
length is too long.
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:
name1
...
name1>...>namex>namey
where,
is the originator of the event.
is where intervening server name(s)
have been left off the source trail.
User response: Most likely you are using very long

server names and/or have excessive hops from server
261
ANR1852E ANR1859W
to server. Either use shorter server names or change
your configuration to reduce the number of hops.
ANR1852E
Unable to send header to TEC at TEC

server rc return code
Explanation: A network error has occurred in

attempting to send the event header to the Tivoli
Enterprise Console.
User response: Verify network connections and
contact your service representative if this error persists.
ANR1853E
Unable to send data to TEC at TEC


attempting to send the event data to the Tivoli
Enterprise Console.
the command. If there was an error specifying a

parameter, re-issue the command with the parameter
corrected.
ANR1857I
AUDIT VOLUME will start count repair

processes.
Explanation: The AUDIT VOLUME command will

process a range of volumes due to one or more of the
following parameters having been specified:
FROMDATE, TODATE, or STGPOOL. The AUDIT
VOLUME processing will start a process for each
volume that qualifies and process an AUDIT VOLUME
for each volume with FIX=YES specified.
System action: One or more volumes are audited and
inconsistent data is discarded.
continue.
User response: Enter 'Y' to audit the volume or 'N' to

stop the process.

ANR1858I
AUDIT VOLUME will start count

inspect processes.
Explanation: The AUDIT VOLUME command will

process a range of volumes due to one or more of the
following parameters having been specified:
FROMDATE, TODATE, or STGPOOL. The AUDIT
VOLUME processing will start a process for each
volume that qualifies and process an AUDIT VOLUME
for each volume with FIX=NO specified.


continue.
ANR1855E

stop the process.
ANR1854E
Unable to flush data to TEC at TEC


attempting to flush data to the Tivoli Enterprise
Console .
Failure validating protocol between

client and server for node node on
session session number
Explanation: For a node having the "VALIDATE

PROTOCOL" option set to either "DATAONLY" or
"ALL", a validation error occurred. The transaction is
aborted and an indication is sent to the client indicating
the failure.
ANR1856W
Command: No volumes selected to

process.
Explanation: No volumes were eligible for processing

by the AUDIT VOLUME command based upon the
parameters specified.
System action: The AUDIT VOLUME process ends
without processing any volumes.
User response: Review the parameters specified for
262
ANR1859W
Node node on session session id received

CRC protocol validation information
when it is not configured to do so.
Explanation: The server received protocol validation

information for the session and node specified. The
settings for this node are not configured to perform
protocol validation and any CRC information received
will be ignored.
User response: The server administrator should
evaluate whether or not this node should perform
protocol validation. If so, issue the UPDATE NODE
command and specify the VALIDATEPROTOCOL
option with the appropriate setting to enable protocol
validation.
If this is a TYPE=SERVER node for the target of a
virtual volume operation and protocol validation is not
desired, the server definition on the source server
should be updated with VALIDATEPROTOCOL=NO
ANR1860E ANR1869W
set. Otherwise, if protocol validate is desired, the
SERVER type node on the target server should be
updated using the UPDATE NODE command with
VALIDATEPROTOCOL=ALL.
ANR1860E
Drive with serial serial element element

port port and target target lun lun does
not match with the library libraryPath .
ANR1866I

suspended with status status.

command command was suspended with a SUSPEND
command.
System action:

stops. Statistics on the number and type of objects
message.
User response:
Explanation:
ANR1861E
Drive with element element port port and

target target lun lun does not match with
the library libraryPath .
Explanation:
System action:
User response:
ANR1863E
library libraryPath and serial serial does

not support Read Element Status
command. It is very old and should be
replaced with newer model.
Explanation:
User response:
library libraryPath does not support Read
Element Status command and it does
not have a serial number. It is very old
and should be replaced with newer
model.
System action:
User response:
export command : Summary for
Restartable Export operation export
identifier :
Explanation: A summary of the total number of

objects transmitted in the restartable export operation
with export identifier is displayed following this
message.
System action: Export processing for the command
ends. Server operation continues.

has completed with status status. If the status is
INCOMPLETE, some files have been skipped due to
errors reading or writing the file.
command completes. Statistics on the number and type
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.
ANR1868I
Explanation:
ANR1865I

completed with status status.
System action:
ANR1864E
ANR1867I
Export/import command: Copied filespace

number file spaces archive number archive
files, backup number backup files, and
spacemg number space managed files.

copies filespace number client file space definitions,
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
actually moved if Preview=Yes is specified in the
command export/import command.
ANR1869W
Export/import command: Skipped archive

number archive files, backup number
backup files, and spacemg number space
managed files.

skipped 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
263
ANR1870I ANR1876W
database. Data is not actually moved if Preview=Yes is
User response: Check previous messages for the
names of the files that were not exported or imported,
and problem determination information.
ANR1870I

bytes of data.

copies number bytes of data from the server database
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
used during export preview processing to estimate the
number of removable media volumes needed to hold
the exported information from the server.
ANR1871I

kilobytes of data.

copies number kilobytes of data from the server
the server.
ANR1872I

megabytes of data.

copies number megabytes of data from the server
the server.
264
ANR1873I

gigabytes of data.

copies number gigabytes of data from the server
the server.
ANR1874I

terabytes of data.

copies number terabytes of data from the server
the server.
ANR1875I
Export/import command: Detected number

errors.

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
and data storage.
prior to this message to view the error. Use the QUERY
for messages.
ANR1876W
Export/import command: Detected an

unexpected value, value, for the
data-transfer path option setting for node
node name. The default value of 'ANY' is
used for the node.
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.
ANR1877E ANR1893E
User response: If the data-transfer path setting of
'ANY' is acceptable for the node, do nothing further. If
you must change the setting, use the UPDATE NODE
command.
ANR1877E
NAS backup process terminated - NAS

file server NAS file server name reported
illegal arguments.

User response: Verify the that the filespace exists on
the NAS file server. If backing up a NAS virtual
filespace verify that the path specified in the virtual
filespace exists.
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
the operation.
ANR1878E
A database manager configuration

parameter cannot be updated. The value
of the DIAGSIZE parameter is greater
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
the drive or the file system that containsing the
diagnostic data directory.
where new_size is the new value for DIAGSIZE in

megabytes. Valid values range from 2 and greater.
See the following topic in the information center:
http://publib.boulder.ibm.com/infocenter/tsminfo/
v6r3/topic/com.ibm.itsm.tshoot.doc/
r_pdg_db2logfilelocation.html
ANR1890W
Explanation: The backup operation failed because a

non-root user attempted the operation. A restriction is
in place to disallow backup operations by non-root
users for the indicated node.
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.
User response: Retry the backup operation as the root
user.
ANR1891I
v Specify a smaller value for DIAGSIZE.

v Change the location of the diagnostic data directory
to a drive or file system that has more free space.
v Increase the amount of free space on the drive or file
system containing the diagnostic data directory.
To check the current setting of the DIAGSIZE
configuration parameter, issue the following database
command:

ANR1892W
and search for "DIAGSIZE".

To change the value of the DIAGSIZE configuration
parameter, issue the following command:
db2 update dbm cfg using DIAGSIZE new_size

completed with a completion state of
SUCCESS but warning or more-severe
messages were issued.
Explanation: The process completed with a

completion state of SUCCESS but warning messages or
more-severe messages were issued by this process. This
process may not have completed all of the processing.
User response: Review the messages in the activity
and event logs that were issued by this process.
Determine if the conditions that caused these messages
to be issued had an affect on the operation.
ANR1893E
db2 get dbm cfg

SUCCESS.
Explanation: The process completed with a

completion state of SUCCESS without any warnings or
more-severe messages.
System action: The operation fails. Depending on the

configuration parameter that is being updated, the
server might stop.
User response: Complete one of the following options:
Backup operation for session session

number node client node name failed due
to root-only restriction.

FAILURE.
Explanation: The process completed with a state of

FAILURE.
User response: Review the messages in the activity
and event logs that were issued by this process.
265
ANR1894E ANR1908W
Determine the conditions that caused these messages to
be issued, resolve those issues and retry the operation.
ANR1894E
Replication for node node name, file

space file space name failed because of a
lock conflict.
Explanation: The server could not obtain a resource

that is required to replicate the indicated file space.
System action: The command continues, but
replication of the indicated file space fails.
User response: To increase the probability of acquiring
all the necessary resources for replication, run the
REPLICATE NODE command when server activity is
relatively low.
ANR1900E
Path between server server source and

library parm is not allowed.
Explanation: You must specify a path from the current

server to the library when you are defining the library.
You cannot specify a path from a different server.
User response: Ensure that an NFS ADDEXPORT

command was issued for the specified node.
ANR1904E
Missing or invalid value for option. A

valid directory needs to be defined for
this.
Explanation: The server detects a missing or invalid

value for a server option. A valid directory needs to be
defined for this option.
User response: Correct the error and restart the server.
ANR1905E
Path dir name for parm does not exist or

is not empty.
Explanation: The directory specified does not exist or

is not empty.
path name.

source or destination name or define a new path.
ANR1901I
The specified session is associated with

process name process process id and can
not be cancelled.
Explanation: The server can not cancel the session

because it is associated with a running process.
User response: The session can only be cancelled by
cancelling the associated process. Use the CANCEL
PROCESS command to cancel a process.
ANR1906E
Explanation: A failure occurred during the extend

database space. This occurred during the processing of
a 'EXTEND DBSPACE' command.
User response: Review error messages to determine
the cause of the failure and retry the 'EXTEND
DBSPACE' once the issue has been resolved. If unable
to determine the cause of the failure or to resolve it,
please contact your IBM service representative for
further assistance.
ANR1907E
ANR1902W
Node node name on server server name is

not enabled for replication. It will not
be replicated.
Explanation: The server is not able to replicate the

specified node because the node on the specified target
server is not enabled for replication.
System action: The node is not replicated to the
specified server. Server operation continues.
User response: Enable the node on the target server
for replication and rerun the replication command.
ANR1903E
Server failed to extend the database

space.
The server can not resolve absolute path

of directory dir name. That path might
not exist.
Explanation: The directory specified does not exist or

is not accessible.
path name.
ANR1908W
Export export name is not defined.
Invalid value for parameter parameter parameter valueMB. The default value
default valueMB is used for this
parameter.
Explanation: An NFS client attempted to mount the

specified name as a mount point. The specified name is
not currently being exported by the server.

the (parameter) parameter is not a valid. The server uses
the default value for this parameter.
System action: The server does not provide an export

of the specified directory.
System action: Processing of the command continues

by using the default value.
266
ANR1909W ANR1918I
User response: Verify that the correct value have been
used. Update the value, if necessary.
ANR1909W
Invalid value for option name option option valuetype . The default value
default valuetype is used for this option.
Explanation: The value (option value) specified for the

(option) option is not valid. The server uses the default
value for this parameter.
ANR1914I
System action: The server successfully ended the

indicated number of IDENTIFY processes.
User response: Review the status of the identify
processes using the QUERY ACTLOG command.
ANR1915I

ANR1910E
Directory directory name is already

defined for other path in the command.
Explanation: While processing the command

argument list, a duplicate path name has been
encountered.
ANR1911W
Invalid value for option name option option valuetype . The default value
default valuetype is used for this option.
Explanation: The value (option value) specified for the

(option) option is not valid. The server uses the default
value for this parameter.

ANR1916I
ANR1912I
Stopping the activity log because of a

server shutdown.
System action: Stopping the activity log because of a

server shutdown.
ANR1913I

ANR1917E
System action: The server successfully started the

indicated number of IDENTIFY processes.
User response: Review the status of the identify
processes using the QUERY PROCESS or QUERY
ACTLOG commands.
Autocopy process process ID failed for

storage pool storage pool name. Files
Backed Up: number of files,Bytes
BackedUp: number of bytes. Result code:
return code.
Explanation: An autocopy process to the named

active/copy storage pool has ended in failure.
User response: Check the activity log for messages
that were issued prior to completion. The messages
may give more information about the failure.
ANR1918I
command successfully started number of

processes IDENTIFY processes.
Autocopy process process ID ended

successfully for storage pool storage pool
name. Files Transferred: number of files,
Bytes Transferred: number of bytes.

active/copy storage pool has ended successfully.

Autocopy process process ID started

transferring data to target storage pool
storage pool name.

active-data or copy storage pool has started.

User response: Issue the command again, specifying a
directory that is not in the argument list.
command successfully ended number of

processes IDENTIFY processes.
Autocopy process process ID stopped for

storage pool Storage pool name because of
a server error.

active-data or copy storage pool has been disabled.
User response: Check the activity log for messages
that were issued before the process stopped. The
messages may give more information about the failure.
267
ANR1919W ANR1926W
ANR1919W
Autocopy process process ID was

disabled for storage pool Storage pool
name . At least one storage pool in the
hierarchy is enabled for deduplication.
Explanation: All autocopy processes have been

disabled because at least one target storage pool is
enabled for deduplication.
User response: Either disable deduplication for all
storage pools in the storage-pool hierarchy or remove
the deduplicated storage pool from the autocopy
storage-pool hierarchy.
ANR1920W
A query for the number of HBA

adapters has timed out with a current
value of timeout value.
Explanation: The HBAAPI function to get the number

of HBA adapters failed with a time out.
SANDISCOVERYTIMEOUT option is not set, set it with

a higher value.
ANR1923W
Explanation: The HBAAPI function to get the FC

adapter attribution failed with a time out.
User response: Check all of the HBA adapters on the
system and ensure that they are configured correctly. If
there is an FC adapter that is not functional, remove it
from the system and reconfigure the HBA driver. If
there is no device on an FC port, increase the
SANDISCOVERYTIMEOUT value and try again. If the
a higher value.
ANR1924W

system and ensure that they are configured correctly.
Increase the SANDISCOVERYTIMEOUT value and try
again. If the SANDISCOVERYTIMEOUT option is not
set, set it with a higher value.
ANR1921W
A query for the name of an HBA

adapter has timed out with a current
value of timeout value.
Explanation: The HBAAPI function to get a name

from an FC adapter failed with a time out.
a higher value.
ANR1922W
A request to open an HBA adapter

timed out with a current value of timeout
value.
Explanation: The HBAAPI function to open an FC

adapter failed with a time out.
268
A query for the FC adapter attribution

has timed out with a current value of
timeout value.
A query for the FC port attribution has

timed out with a current value of timeout
value.
Explanation: The HBAAPI function to get the FC port

attribution failed with a time out.
a higher value.
ANR1925W
A request for the HBA target mapping

timed out with a current timeout value
of timeout value.
Explanation: The HBAAPI function to get the target

mapping failed with a time out.
User response: There might be too many devices to be
discovered, given the allotted time. If the
SANDISCOVERYTIMEOUT option is set, increase
SANDISCOVERYTIMEOUT option is not set, please set
it with a higher value and try again.
ANR1926W
A SCSI inquiry has timed out with a

current value of timeout value.
Explanation: The HBAAPI function query SCSI

devices failed with a time out.
User response: Check all of the devices connected to
ANR1927W ANR1951W
the SAN and ensure that they are operational correctly.
Remove non-functional devices from the SAN and
reconfigure the devices on the system. If there is no
device on an FC port, increase the
a higher value.
ANR1927W
Autocopy process process ID stopped for

storage pool Storage pool name . The data
format or device type was not
compatible with the data format or
device type of the primary pool.

active-data or copy storage pool was disabled.
issued. After issuing the command, try the replication

operation again.
ANR1930E
Explanation: The specified node has no filespaces that

can be replicated.
User response: Check replication settings for the
filespaces belonging to the node and retry the
command.
ANR1931E

User response: Use the QUERY STGPOOL command
to check the data format of the storage pools. Use the
QUERY DEVCLASS command to check the device
types of the device classes associated with the storage
pools.
ANR1928W
The file descriptor table for the SAN

discovery process is full.
Explanation: There might be too many paths that

have been changed and updated by the SAN discovery
process.
User response: Use one of the following methods to
resolve this problem:
v
Use the SANREFRESHTIME option to increase the

amount of time elapsed before the cached SAN
discovery information is refreshed. For example:
setopt sanrefreshtime 600.
Increase the nofiles (descriptors) in ulimit and

restart the Tivoli Storage Manager server.
ANR1929E
Replication of node node name to target

replication server target server failed. The
replication mode of the source node is
SYNCSEND, and the node is not
defined on the target replication server.
Explanation: In order to replicate a node that is in

Sync Send mode the target node must exist on the
target replication server and be in Sync Receive mode.
command: There are no eligible

filespaces for node node name.
command: No replication-eligible data

was found for the specified nodes and
file spaces.
System action: The operation ends.

User response: Verify that the specified nodes have
data and file spaces. Verify that replication is enabled
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.
ANR1934W
REPLICATE NODE: Node node name is

disabled.
Explanation: The requested node is disabled for

replication, and has been skipped.
System action: The replication proceeds, but this node
is skipped.
User response: Enable the node for replication using
the UPDATE NODE command and retry the
REPLICATE NODE command.
ANR1950W
Device type device type in device class

device class is not supported during a
migration from z/OS to AIX, or from
z/OS to Linux on System z. The device
class will be skipped.
Explanation: During a migration from z/OS to AIX,

or from z/OS to Linux on System z, a device class
was encountered that had a device type that is not
supported on the target platform.
System action: The device class will not be added to
the target database.
System action: The replication of the node's data fails.

User response: No action is required..
User response: Issue the REMOVE REPLNODE

command for the node on the source server, and then
issue the UPDATE NODE command and specify
ENABLED or DISABLED. The replication mode of the
node on the source replication server is automatically
set to SEND after the UPDATE NODE command is
ANR1951W
Device class device class uses a recording

format format (format code) that is not
supported for device type device type.
FORMAT=DRIVE will be used instead.

or from z/OS to Linux on System z, a device class was
encountered that uses a recording format that is not
269
ANR1952I ANR1995E
supported by the device type on the target platform.
System action: The recording format will be replaced
with FORMAT=DRIVE.
User response: Verify whether FORMAT=DRIVE
supports your media type. If not, update the device
class, specifying a supported recording format.
ANR1952I
Library library name was added to the

definition of device class device class.

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.
System action: The device class will be modified to
use the new library.
ANR1953E
command: target platform cannot be the

target of a database upgrade from source
platform.
Explanation: A cross-platform database upgrade is not

supported between the indicated source and target
platforms.
System action: The INSERTDB command stops.
User response: Rerun the INSERTDB command on a
supported platform.
User response: To resolve the issue, complete the

following steps: :
v 1. Verify the level of DB2 installed on the system:
Run 'db2level'
v 2. Review the installation log files to determine the
problem that caused the DB2 upgrade failure.
v 3. Fix the problem and install the server again.
v Do not alter the DB2 software that is installed with
Tivoli Storage Manager installation packages and fix
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
Support.
ANR1992E
Command: The parameter parameter is

missing.

entered without all required parameters. At least the
named parameter is missing.
proper syntax.
ANR1993I
command has been removed.
Explanation: The specified command was a valid

server command, but is no longer needed due to new
capabilities in the TSM server. The command has been
removed.
ANR1954W
Library definition library was not sent to

downlevel storage agent stagent.
Explanation: The storage agent has requested a

definition for a library type that is not supported and
the server has not sent the definition.
System action: The storage agent does not process the
library definition.
User response: Upgrade the storage agent to a level
that supports the library type.
ANR1955E
The server detects that the following

DB2 level is installed on the system:
'current db2 level'. The installed DB2 level
is earlier than the required DB2 level:
'required db2 level'. The installed version
of DB2 must be at the required level or
later.
Explanation: The DB2 level on the system does not

meet the requirements for this server. The server
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
during the server upgrade process.
270

ANR1994I
Activity log pruning started: removing

delete megabytes M based on current size
current size megabytes M and retention
setting retention size megabytes M.
Explanation: Server activity log exceeds the retention

size by the delete megabytes specified. The activity log
pruning will delete as many records as necessary to
reduce the current activity log size by the delete
megabytes size.
ANR1995E
Command: Invalid Formatsize value formatsize value for device class Device
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
device class is associated with the storage pool
specified in the DEFINE VOLUME command and is a
FILE device type. The maximum capacity value of the
ANR1996E ANR2004E
device class is the limit of data that the server will
write to the volume.
command.
User response: Reissue the command with a
Formatsize value which is less than the maximum
capacity value of the storage pool. The maximum
capacity can be displayed with the QUERY DEVCLASS
classname F=D command.
ANR1996E
Command: Invalid volume name prefix volume name. Room for additional
characters is required.
Explanation: The command is being used for multiple

volume names. The suffix for the names is being
generated in the indicated command. When the suffix
is taken into account, the specified name is too long by
the indicated number of characters. Three characters
must be allowed for the suffix.
command.
User response: Reissue the command with a prefix
short enough to allow for the suffix. Three extra
characters are needed for the suffix.
ANR1997E
Command: The Formatsize parameter

must be specified when more than 1
volume is created.
Explanation: The command specified the createion of

more than one volume with the Numberofvolumes
parameter. When multiple volumes are created, the
Formatsize parameter must also be specified to provide
the size of the volumes. Each volume will be created
with the same size.
ANR1999I
Command completed successfully.
Explanation: Processing for the specified command

ANR2000E
Unknown command - command.
Explanation: The specified command is not a valid

server command.
User response: Reissue the correct command.
ANR2001E
Insufficient server memory to initiate

command.
Explanation: A command has been entered, but the

server cannot obtain enough internal memory to
process the command.
application.
ANR2002E
Missing closing quote character.
Explanation: A server command that contains a

quoted parameter has been entered, but a matching
closing quote is missing.
User response: Reissue the command with properly
matched quotes.

command.
ANR2003E
User response: Reissue the command with the

Formatsize parameter or define a single volume
without the Formatsize parameter.
Explanation: A server command contains the

parameter shown followed by an equal sign (=), but the
parameter is not a keyword parameter.
ANR1998E
Command: Invalid value for parameter

parameter - parameter value.

the (parameter) parameter in command command is not a
valid value for this parameter.
valid parameter value. For information on valid values
for the parameter for the command, refer to the
Illegal use of keyword parameter

character (=) - parameter.

proper syntax.
ANR2004E
Missing value for keyword parameter parameter.
Explanation: A server command containing a keyword

parameter has been entered, but the value for the
parameter is missing.
User response: Reissue the command and supply a
value for the keyword parameter.
271
ANR2005E ANR2013E
ANR2005E
Keyword parameter character (=) may

not be surrounded by blanks.
Explanation: A server command contains a keyword

parameter followed by an equal sign (=), but the equal
sign is preceded or followed by a blank, or both.
System action: The server stops updating the activity

log.
ANR2010W

User response: Reissue the command without blanks
next to the equal sign.
ANR2006E
Activity log process was not started, the

default output stream cannot be opened.

cannot access that output stream.
log.
ANR2007E
Activity log process was not started, due

to an internal error.

cannot start due to a server internal error.
log.
representative.
ANR2008E
Activity log process has stopped database transaction could not be

started.

cannot continue due to a server transaction failure. This
may be a memory shortage error.
log.
application.
ANR2009E
Activity log process has stopped database error.

cannot continue due to a server database error.
272
Server is out of LOG space in adding

entries to the Activity Log. Console
messages will not be logged until LOG
space is available.

cannot update the activity log due to a lack of recovery
log space.
log.
volumes are used.
ANR2011W
Server is out of DB space in adding

entries to the Activity Log. Console
messages will not be logged until DB
space is available.

cannot update the activity log due to a lack of database
space.
log.
ANR2012W
Activity log process has encountered

unexpected table data output in the
default output stream.

has detected invalid data in the console stream.
log.
ANR2013E
The activity log process has encountered

unexpected output data in the console
output stream. The process will be
restarted.
Explanation: The process that monitors console output

and maintains the activity log has detected invalid data
(unknown data type) in the console stream.
ANR2014E ANR2022E
System action: The server restarts the activity log
recording process. While the process is restarting, the
server may not be able to record some console
messages in the activity log.
application.
ANR2014E
Activity log pruning process could not

be started, due to an internal error.
Explanation: The process that removes expired records

from the server activity log cannot begin execution due
to a server internal error.
System action: The server does not prune the activity
log.
representative.
ANR2018E
Administrator Command: Unicode

conversion failed for argument Command
Argument
Explanation: The specified command argument could

not be converted to a Unicode string. Conversion can
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
issued a RENAME FILESPACE command, the new
filespace name might be too long.
System action: The server command fails.
User response: Ensure that the server locale is
configured correctly. If you issued a RENAME
FILESPACE command, consider specifying a shorter
name for the new filespace.
ANR2019I
Command: No nodes updated.
Explanation: An UPDATE NODE command has been

entered, but no objects were updated.
ANR2015E
Activity log failure - database

transaction could not be started.

from the server activity log has failed due to a database
transaction failure, which may be a memory shortage
error.
System action: The server ends activity log pruning.
application.
ANR2016E
Activity log failure - database error.

from the server activity log has failed due to a server
database error.
System action: The server ends activity log pruning.
ANR2017I
Administrator Administrator Name issued

command: Command
Explanation: This message records the fact that the

named administrator issued the command specified.
The messages is issued and logged to provide an audit
trail for administrative commands.
System action: Server operation continues
ANR2020E
Command: Invalid parameter - parameter.

entered with an invalid parameter.
proper syntax.
ANR2021E
Command: Missing subcommand

keyword.

entered without a valid subcommand (second
parameter).
proper syntax.
ANR2022E
Command: One or more parameters are

missing.

entered without all required parameters.
proper syntax.
273
ANR2023E ANR2031E
ANR2023E
Command: Extraneous parameter parameter.
Explanation: The specified server command contains

more positional parameters than is allowed.
proper syntax.
ANR2024E
Command: Too many parameters

specified.
Explanation: The specified server command contains

more positional parameters than is allowed.
proper syntax.
ANR2025E
Command: Command failed - server

thread resource not available.
Explanation: A server command, which has a

requirement to start a server thread, has been entered
but cannot be executed because no server thread is
available.
User response: Reissue the command. If the command
fails with the same error, wait for server activity to
decrease and try again.
ANR2026E
Command: Command failed - sufficient

server memory is not available.

cannot be processed because sufficient memory is not
command.
application.
ANR2027E

server recovery log space is not
available.

cannot be processed because sufficient recovery log

volumes are used.
ANR2028E

server database space is not available.

cannot be processed because sufficient database space
is not available. For certain operations, like SQL
commands, this message can be issued when the
database has space, but it is unusable for the current
request due to the DB allocation history. In this case,
the database query will show a Maximum Reduction of
0.
command.
new volumes are used. If the database has space, but
the Maximum Reduction is 0, then a database
reorganization can also be used to solve the problem.
See the IBM Tivoli Storage Manager Guide, Managing
the Database and Recovery Log for information on how
to reorganize the database.
ANR2029E
Command: Transaction failed; command

not executed.
Explanation: A command that is part of the current

transaction has failed; therefore, any additional
commands fail.
command.
User response: Stop the administrative session, restart
it, and try the command again. If this problem persists,
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.
COMMIT command.
User response: Stop the administrative session, restart
it, and try the command again. If this problem persists,
Command: At least one attribute must be
specified for update.

command.
ANR2031E

Explanation: The specified UPDATE command has

been entered, but no attributes have been specified for
updating.
274
ANR2032E ANR2039E
User response: Reissue the UPDATE command with
one or more attributes to be updated.
ANR2032E
Command: Command failed - internal

Explanation: An internal error has occurred during an

attempt to process a server command. This message
always accompanies another error message and
provides more detail about that error.
command.
representative.
User response: Examine previous messages for any

additional information. Issue the command from a
properly authorized administrator ID, or contact the
system administrator to have additional authority
granted to the current administrator ID.
ANR2036E
Explanation: A background process cannot be started

for the indicated command because sufficient memory
is not available to the server.
System action: A new process is not started to execute
this command.
application.
ANR2037E
ANR2033E
Command: Command failed - lock

conflict.
Explanation: A server command that requires the

server to lock a system resource has been entered. The
command cannot be executed because the resource is
already in use by another command or process.
command.
User response: Try the command again at a later time.
ANR2034E
Command: No match found using this

criteria.
Explanation: The specified command has been

entered, but no objects that match the criteria can be
found. In some cases when using the SELECT
command, this message is issued when there is
contention for a record.
User response: Verify that all the specified parameter
values are correct. If a mistake is found, correct it and
reissue the command. If you issued a SELECT
command, in some cases issuing the command again
will yield a match.
ANR2035E

name is not authorized to issue this
command.

have the proper authority necessary to run the
command. Note: This message can be issued as a result
of the server option REQSYSAUTHOUTFILE YES being
in effect.
command.
Command: Process could not be started sufficient memory is not available.
Command: Process could not be started lock conflict.

for the indicated command because a required system
resource is already locked by another command or
process.
this command. If other processes have been started for
this command, these processes may execute
successfully.
User response: If necessary, try the command again at
a later time.
ANR2038E
Command: Process could not be started server thread resource not available.

for the indicated command because no server thread is
available.
successfully.
User response: If necessary, reissue the command. If
the command fails with the same error, wait for server
activity to decrease and try again.
ANR2039E
Command: Process could not be started internal server error detected.

for the indicated command because an internal error
has occurred.
successfully.
275
ANR2040W ANR2047E
representative.
ANR2040W
This command attempts to restore all

files in storage pool storage pool which
have previously been found to be
damaged or which reside on a volume
with access mode "destroyed"; existing
references to files in storage pool storage
pool will be deleted from the database
after the files have been restored.
Explanation: Issuing the RESTORE STGPOOL

command will result in deletion of existing files in the
indicated primary storage pool after these files have
been restored from a copy storage pool. If a volume
with access mode destroyed becomes empty because all
files on the volume have been restored to another
location, the destroyed volume will be deleted from the
database.
continue.

COPIED parameter.
ANR2043E
Command: WAIT parameter not allowed

from server console.
Explanation: The WAIT parameter is not allowed for

commands issued from the server console.
User response: Either reissue the command without
the WAIT parameter or else reissue the command from
an administrator using an Administrative Client.
ANR2044E
Command: Invalid option's value Option's value.
Explanation: The set option command has been

entered with an invalid value.
command.
value.
User response: Enter 'Y' to restore the storage pool,

'N' otherwise.
ANR2045E
ANR2041W
Explanation: The server detects an error while

attempting a write operation.
This command attempts to restore all

files in storage pool storage pool which
reside on one of the volumes specified
in the command; existing references to
files on these volumes will be deleted
from the database after the files have
been restored.
Explanation: Issuing the RESTORE VOLUME

command causes the access mode of the specified
volumes to be updated to destroyed. Existing files will
be deleted from the specified volumes after these files
have been restored from a copy storage pool. If a
volume with access mode destroyed becomes empty
because all files on the volume have been restored to
another location, the destroyed volume will be deleted
from the database.
Command: An error (error code) occurred

during a write operation.

User response: Refer to the other displayed messages
to determine why the write operation has failed.
ANR2046I
optionset name: Optionset optionset name

defined.
Explanation: The requested option set has been added

to the system in response to a DEFINE OPTIONSET
command.

continue.
ANR2047E
User response: Enter 'Y' to restore the volumes, 'N'

otherwise.
Explanation: A DEFINE OPTIONSET command has

been entered that specifies an optionset name already
ANR2042E
Command: Copied parameter not valid

for pool type storage pool volume.
Explanation: The QUERY CONTENT server command

has been entered with an invalid parameter. COPIED is
not a valid parameter when the volume specified
belongs to a copy or active-data type storage pool.
276
Command: Optionset optionset name is

already defined.

command.
User response: To define the optionset, reissue the
command and specify a different optionset name.
ANR2048I ANR2058W
ANR2048I
Command: Optionset optionset name

deleted.
Explanation: The requested option set has been

deleted from the system in response to a DELETE
OPTIONSET command.
from the specified optionset in response to a DELETE

CLIENTOPT command.
ANR2054I

ANR2049E
Command: Optionset optionset name is not

defined.
Explanation: The command shown specifies an

optionset that is not defined in the server.
command.
Explanation: The requested option set has been

updated in the system in response to an UPDATE
OPTIONSET command.
ANR2055I

ANR2050I
Command: Option option name defined in

optionset option set name.
Explanation: The requested option has been added to

the specified optionset in response to a DEFINE
OPTIONSET command.
Command: Optionset optionset name

updated.
Command: Optionset source optionset name

copied to optionset target optionset name.

the COPY OPTIONSET command. The optionset
named source optionset name has been copied to the
optionset named target optionset name.
User response: None. The requested option set has
been added to the system in response to a COPY
OPTIONSET command.

ANR2056E
ANR2051E
Command: Option option name, sequence

number sequence number is already
defined in optionset option set name.
Explanation: The requested option already exists in

the optionset specified by the DEFINE CLIENTOPT
command.
command.
ANR2052E
Explanation: The requested option is not defined in

the optionset specified by the DELETE CLIENTOPT
command.
command.

command.
option name.

number sequence number, has been
deleted from optionset option set name.
Explanation: The requested option has been deleted
Command: Invalid option value - option

value.

option value.
command.
option value.
ANR2058W

ANR2053I

option name.
ANR2057E

number sequence number is not defined
in optionset option set name.
Command: Invalid option name - option

name. Retry using the full optionname.
Command: Options file Filespec not found

- user needs to update the file manually.
Explanation: The server options file cannot be opened

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
277
ANR2059W ANR2070I
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
the server restarts.
ANR2064I
Node node name locked.
Explanation: In response to a LOCK NODE command,

the indicated backup-archive node has been locked.
ANR2059W
Command: Error occurs when writing to

Filespec - user needs to update the file
manually.
Explanation: An error occurs when trying to write the

new value to the server options file.
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
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
the server restarts.
ANR2060I
Node node name registered in policy

domain domain name.
Explanation: The requested backup-archive node has

been added to the system in response to a REGISTER
NODE command and has been assigned to the policy
domain indicated.
ANR2061I
Node node name removed from policy

domain domain name.
Explanation: In response to a REMOVE NODE

command, the requested backup-archive node has been
ANR2062I
Node node name renamed to new node

name.
Explanation: In response to a RENAME NODE

renamed to the new name shown.
ANR2063I
Node node name updated.
Explanation: One or more attributes of a

backup-archive node have been updated by an
278

ANR2065I
Node node name is already locked.
Explanation: The indicated backup-archive node

referenced in the LOCK NODE command is already
locked.
ANR2066I
Node node name unlocked.
Explanation: In response to an UNLOCK NODE

command, the indicated backup-archive node is
unlocked.
ANR2067I
Node node name is already unlocked.
Explanation: The indicated backup-archive node

referenced in the UNLOCK NODE command is not
locked.
ANR2068I
Administrator administrator ID registered.
Explanation: In response to a REGISTER ADMIN

command, the requested administrator ID has been
added to the system.
ANR2069I
Administrator administrator ID removed.
Explanation: In response to a REMOVE ADMIN

ANR2070I
Administrator administrator ID renamed

to new administrator ID.
Explanation: In response to a RENAME ADMIN

changed to the new name shown.
ANR2071I ANR2082I
ANR2077I

ANR2071I
Administrator administrator ID updated.
Explanation: One or more attributes of an

administrative user have been updated by an UPDATE
ADMIN command.
Unrestricted policy privilege granted to

administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY

command, unrestricted policy privilege has been
granted to the indicated administrator.

ANR2078I

ANR2072I
Administrator administrator ID locked.
Restricted policy privilege granted to

administrator administrator ID - policy
domain domain name.
Explanation: In response to a LOCK ADMIN

command, the indicated administrator ID has been
locked.

command, restricted policy privilege for the specified
policy domain has been granted to the indicated
administrator.
ANR2073I
Administrator administrator ID is already

locked.
ANR2079I
Unrestricted storage privilege granted to

Explanation: The indicated administrator ID

referenced in the LOCK ADMIN command is already
locked.

command, unrestricted storage privilege has been
granted to the indicated administrator.
ANR2074I
Administrator administrator ID unlocked.
ANR2080I
Explanation: In response to an UNLOCK ADMIN

command, the indicated administrator ID is unlocked.

command, restricted storage privilege for the specified
storage pool has been granted to the indicated
administrator.

ANR2075I
Restricted storage privilege granted to

administrator administrator ID - storage
pool storage pool name.
Administrator administrator ID is already

unlocked.
Explanation: The indicated administrator ID

referenced in the UNLOCK ADMIN command is not
locked.

ANR2081I
Analyst privilege granted to


command, analyst privilege class has been granted to
the indicated administrator.
ANR2076I
System privilege granted to


command, system privilege class has been granted to

ANR2082I
Operator privilege granted to


command, operator privilege class has been granted to
279
ANR2083I ANR2093I
ANR2088I

ANR2083I
System privilege revoked for

Explanation: In response to a REVOKE AUTHORITY

command, system privilege class has been revoked
from the indicated administrator.

command, analyst privilege class has been revoked
ANR2089I

ANR2084I
Policy privilege revoked for


command, policy privilege class for all policy domains
has been revoked from the indicated administrator.
Restricted policy privilege revoked for

administrator administrator ID - policy
domain domain name.

command, restricted policy privilege for the specified
policy domain has been revoked from the indicated
administrator.
ANR2086I
Storage privilege revoked for


command, storage privilege class for all storage pools
has been revoked from the indicated administrator.
Operator privilege revoked for


command, operator privilege class has been revoked
ANR2090I

ANR2085I
Analyst privilege revoked for

Activity log retention set to value for

management by management style.
Explanation: The server activity log has been set to

the value indicated with the SET ACTLOGRETENTION
command for the indicated management style. If the
management style is DATE, the value is the number of
days that messages will be kept in the activity log
before being deleted. If the management style is SIZE,
the value is the size in megabytes that the activity log
will be allowed to occupy in the server database.
ANR2091I
Accounting parameter set to value.
Explanation: Accounting record generation has been

turned on or off as indicated with the SET
ACCOUNTING command.

ANR2092I
ANR2087I
Restricted storage privilege revoked for

administrator administrator ID - storage

command, restricted storage privilege for the storage
pool indicated has been revoked from the indicated
administrator.
Password expiration period set to

number of days days.
Explanation: The number of days that a password can

be used before it must be changed has been set to the
value indicated with the SET PASSEXP command.
ANR2093I
Registration parameter set to registration

method.
Explanation: Backup-archive node registration has

been set to the method indicated with the SET
REGISTRATION command.
280
ANR2094I ANR2104I
ANR2094I
Server name set to server name.
Explanation: The name that the server displays and

communicates to backup-archive nodes has been set to
the value indicated with the SET SERVERNAME
command.
ANR2100I
Activity log process has started.
Explanation: The automatic server process that

removes expired server activity log records has begun
processing.

ANR2101I
ANR2095I
Authentication parameter set to value.
Explanation: The requirement for a node or

administrator to enter a password when establishing a
session with the server has been turned on or off as
indicated with the SET AUTHENTICATION command.
Activity log process stopped, activity log

retention set to 0.
Explanation: A SET ACTLOGRETENTION 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
ANR2102I
Server now enabled for backup/archive

client access.
Activity log pruning started: removing

entries prior to date time.
Explanation: The server has been made available for

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.
ANR2097I
ANR2103I
Server now disabled for backup/archive

client access.
Activity log pruning completed: number

of records records removed.
Explanation: The server has been made unavailable

for use by backup-archive clients with the DISABLE
command.
Explanation: All expired (older than the log archive

retention value) server activity log records have been
removed; the number of records deleted is shown.
ANR2098E
Command: Invalid URL specification url.
Explanation: The specified URL is too long.

User response: Reissue the command and enter a URL
value that is 200 characters or less.
ANR2099I
Administrative userid admininstrator

name defined for OWNER access to node
node name.
ANR2104I
Activity log processing is now restarted.
Explanation: The process that records data in the

server activity log had suspended logging messages
because of insufficient space in the server recovery log
or database or because access to the database failed.
The condition that caused the activity log processing to
fail has been resolved and the activity log processing is
able to resume.
System action: Activity log processing resumes.
Explanation: An administrator with the specified

name was created having OWNER access to the client
node. This administrator is created for accessing the
client node from an interactive interface.
281
ANR2105W ANR2112E
ANR2105W
Command: Node was registered in excess

of license terms - node registration will
fail after 120% of the licensed quantity
of nodes have been registered.
Explanation: The server has detected the addition of a

node in excess of the terms under which the server is
licensed. The REGISTER NODE command will fail after
120% of the licensed number of nodes have been
registered.
compliance. You may remove nodes to reduce the
number of registered nodes or purchase additional
client node connections. If additional nodes have been
purchased, issue the AUDIT LICENSES command to
resynchronize the server configuration with license
terms.
ANR2106I
Server HALT command: Quiescing

database update activity.
Explanation: The server is quiescing transactions that

update the database so that the database is in a
consistent state when the server is halted. This action
occurs when HALT QUIESCE is specified to halt the
server with the database in a consistent state.
System action: When database update transaction
activity has been stopped, the server program ends.
ANR2107I
Server HALT command: Database update

activity is now quiesced.
Explanation: The server has stopped all database

update transaction activity. This action occurs when
HALT QUIESCE is specified to halt the server with the
database in a consistent state.
System action: The server program ends.
ANR2108I
Server HALT command: Reattempting to

quiesce database update activity.
Explanation: The server is quiescing transactions that

update the database so that the database is in a
consistent state when the server is halted. The previous
attempt at quiescing database activity failed because of
the current transaction load on the server. The quiesce
operation is being reattempted. This action occurs when
HALT QUIESCE is specified to halt the server with the
database in a consistent state.
System action: When database update transaction
activity has been stopped, the server program ends.
282
ANR2109I
Server HALT command: Database update

transaction activity could not be
successfully quiesced.
Explanation: After repeated attempts, server database

update transaction activity could not be quiesced. The
server is not halted with the HALT QUIESCE
command. Attempts to quiesce database update
transaction activity can fail if heavy transaction load is
on the server when a HALT QUIESCE command is
entered.
User response: You may disable the server, cancel all
client sessions accessing the server, cancel all processes,
and reenter the HALT QUIESCE command to stop
server processing. The HALT command may also be
used to stop server processing without quiescing
database transaction update activity. Server recovery
logic will be used when the server is restarted to
reconcile database transaction activity.
ANR2110I
Command started as process process ID.

to service the command command. The background
System action: The server processes the indicated
command.
number to specify this process.
ANR2111W
Command: There is no data to process for

storage pool.
Explanation: The indicated command does not have

any data to process. This can occur if the command
specifies a storage pool with no volumes, or with no
volumes that contain data. This can also occur if there
are no volumes in the storage pool with an access state
of READWRITE or READONLY.
System action: The command ends without starting a
background process.
User response: Issue the QUERY VOLUME F=D
command to verify that there is at least one volume in
the storage pool that contains data, and that the storage
pool volumes have an access state of READWRITE or
READONLY.
ANR2112E
Command: Volume volume name is not in

a primary storage pool.

name of a volume that does not belong to a primary
storage pool. The command syntax requires that a
volume in a primary storage pool be specified.
ANR2113E ANR2121W
command.
ANR2117E
User response: Reissue the command with a volume

in a primary pool.
ANR2113E
Command: Volume volume name does not

belong to the same storage pool (storage
pool name) as previously listed volumes.
Explanation: The indicated command accepts a list of

one or more volumes which belong to the same storage
pool. The named volume does not belong to the same
storage pool as the previously listed volumes.
command.
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
or is of a device class with a DEVTYPE of SERVER.
System action: The access mode for this volume is not
changed.
ANR2118E
User response: Issue the command with a list of

volumes that belong to the same storage pool.
ANR2114I
Command: Access mode for volume

volume name updated to "destroyed".
Explanation: A RESTORE VOLUME command has

updated the access mode of the indicated volume to
destroyed.
System action: Restore processing continues.
ANR2115E

volume name cannot be changed to
"destroyed" - volume is still online.
Explanation: A RESTORE VOLUME command cannot

change the access mode of the indicated volume to
destroyed because the volume is still online.
command.
User response: Issue the VARY OFFLINE command,
and reissue the RESTORE VOLUME command.
"destroyed" - volume does not belong to
a primary storage pool.
Explanation: The access mode for the indicated

volume cannot be changed to destroyed because the
volume does not belong to a primary storage pool.
System action: The access mode for this volume is not
changed.
Storage pool storage pool name specified

on the MOVE DATA command is not a
valid poolname and or pooltype for
volume volume name.
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
copy storage pool, then the specified storage pool must
be the same storage pool as that of the volume.
System action: The MOVE DATA process fails.
User response: Provide a valid primary storage pool
name if the volume belongs to a primary storage pool.
If the volume belongs to a copy storage pool, remove
the storage pool name from the command.
ANR2119I
The Option option has been changed in

the options file.
Explanation: The option is updated in the server

options file.
System action: Server continues.
ANR2120E
ANR2116E

"offsite" - volume either does not belong
to a copy storage pool or from a device
class of DEVTYPE=SERVER.
Command: Invalid platform name platform name.

platform name.
command.
platform name.
ANR2121W
ATTENTION: More than amount changed

unit megabytes, gigabytes or terabytes of the
database has changed and the last
database backup was more than hours
name hours ago. Use the BACKUP DB
command to provide for database
recovery.
283
ANR2122E ANR2130S
Explanation: The server issues this warning when a
significant amount of database change activity has
occurred and the server database has not been backed
up.
User response: To provide for server database
recovery should a hardware or software problem affect
your database, use the BACKUP DB command to back
up the database.
ANR2122E
command name: The DOMAINS

parameter cannot be specified when the
NODES parameter is specified.
Explanation: Both the NODES and DOMAINS

parameters were specified. The NODES parameter may
be specified, or the DOMAINS parameter may be
specified, but both should not be specified at the same
time.
User response: Reenter the command specifying either
the NODES parameter or the DOMAINS parameter, but
not both.
ANR2123E
command name: The NODES parameter

cannot be specified when the
DOMAINS parameter is specified.
Explanation: Both the NODES and DOMAINS

parameters were specified. The NODES parameter may
be specified, or the DOMAINS parameter may be
specfied, but both should not be specified at the same
time.
User response: Reenter the command specifying either
the NODES parameter or the DOMAINS parameter, but
not both.
ANR2124E
command name: Invalid Client authority

specified: authority.
Explanation: An invalid client authority was specified

in a GRANT AUTHORITY or REVOKE AUTHORITY
command when the CLASS=NODE parameter was
specified.
valid client authority.
ANR2125I
command name: Administrator

administrator name was granted OWNER
authority for client client name.
Explanation: The named administrator was granted

OWNER authority over the named client node as the
result of a GRANT AUTHORITY command.
284

ANR2126I
command name: Administrator

administrator name was granted ACCESS
authority for client client name.
Explanation: The named administrator was granted

ACCESS authority over the named client node as the
result of a GRANT AUTHORITY command.
ANR2127I
command name: Owner authority for node

client node was revoked for administrator
administrator.
Explanation: OWNER authority over the named client

node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command.
ANR2128I
command name: Access authority for node

client node was revoked for administrator
administrator.
Explanation: ACCESS authority over the named client

node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command.
ANR2129I

name defined ONLY for authority over
node node name has been removed.
Explanation: The specified administrator has been

removed because the client node was removed and the
administrator only had OWNER access to the specified
node.
ANR2130S
Early Product Version has Expired.

Server is HALTing.
Explanation: This server is pre-release version of the

server. The pre-release version's expiration date has
been reached.
User response: Install the product version of the
server.
ANR2131I ANR2141E
ANR2131I
Server password set.
ANR2137I
Explanation: The password that the server uses to

allow other servers to communicate with it has been
set, changed or removed with the SET
SERVERPASSWORD command.
Administrator administrator name already

has POLICY access for domain policy
domain name to which node node name
belongs.
Explanation: The named administrator already has

POLICY authority over the named policy domain. An
attempt to grant client authority for a client in this
domain is ignored.
System action: The client is skipped.
ANR2132I
Server hladdress set to hladdress.
Explanation: The high level address that other servers

use to communicate with this server has been set to the
value indicated with the SET SERVERHLADDRESS
command.
ANR2133I
ANR2138I
Minimum password length set to length.
Explanation: The minimum length of a password a

node or administrator may send to the server is
indicated with the SET MINPWLENGTH command.
Server lladdress set to lladdress.
Explanation: The low level address that other servers

use to communicate with this server has been set to the
value indicated with the SET SERVERLLADDRESS
command.

ANR2139E
Command: The value supplied for the

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.

ANR2134I

command.
Server url set to url.
Explanation: The url that other servers use to

communicate with this server has been set to the value
indicated with the SET SERVERURL command.

value.
ANR2140E

ANR2135I
Explanation: A SET ACTLOGRETENTION command

has been entered that specifies an invalid log retention
period.
Crossdefine set to state.
Explanation: The ability for another server to

automatically define itself to this server has been
turned on or off as indicated with the SET
CROSSDEFINE command.
ANR2136I
Command: Invalid activity log retention

period - retention value.

command.
retention period.
ANR2141E

has POLICY access for domain policy
domain name.
Explanation: The named administrator already has

POLICY authority over the named policy domain. An
attempt to grant client authority over this domain is
ignored.
Command: Invalid password expiration

period - days value.
Explanation: A SET PASSEXP command has been

entered that specifies an invalid days value.
command.
User response: Reissue the command with a password
expiration period.
System action: The policy domain is skipped.

285
ANR2142E ANR2151E
ANR2142E
Command: Invalid server name - server

name.
Explanation: A SET SERVERNAME command has

been entered that specifies an invalid server name.
command.
server name.
ANR2143E
Command: Invalid node name - node

name.

node name.
command.
node name.
ANR2144E
Command: Invalid password - password.
Explanation: The command specifies an invalid node

password.
command.
User response: Ensure that the password adheres to
naming convention rules and meets the required
minimum password length as set by your
administrator. Ensure that the new password is
different from the old password. Then, reissue the
command with a valid password.
ANR2145E
Command: Contact information exceeds

maximum characters characters.
Explanation: A REGISTER NODE or REGISTER

ADMIN command has been entered that specifies a
contact information value that is too long. The
maximum valid length is shown in the command.
command.
User response: Reissue the command with less contact
information.
ANR2146E
Command: Node node name is not

registered.
Explanation: The command shown specifies a node

that is not registered with the server.
command.
286
ANR2147E
Command: Node node name is already

registered.
Explanation: A REGISTER NODE command has been

entered that specifies a node name already registered
with the server.
command.
User response: To register the node, reissue the
command and specify a different node name.
ANR2148E
Command: Administrator administrator ID

is not registered.

administrator ID that is not registered with the server.
command.
ANR2149E

is already registered.
Explanation: A REGISTER ADMIN command has

been entered that specifies an administrator ID already
registered with the server.
command.
User response: To register the administrator, reissue
the command and specify a different administrator ID.
ANR2150E
Command: Node node name is currently

accessing the server.

that has an active session with the server.
command.
or if necessary, cancel the current session and reissue
the command.
ANR2151E

is currently accessing the server.
Explanation: An UPDATE ADMIN or REMOVE

ADMIN command has been entered that specifies an
administrator ID that is having an active session with
the server.
command.
the command.
ANR2152E ANR2161E
ANR2152E
Command: Inventory references still exist

for node node name.
Explanation: A REMOVE NODE command has been

entered for a node for which the server is still storing
backup or archive data, or both.
command.
User response: To remove the node, delete all of its
file spaces and any virtual file space mapping
definitions from the server and reissue the command.
ANR2153E
Command: Invalid file space name filespace name.
ANR2157E
Command: Other privileges cannot be

granted with system privilege.
Explanation: A GRANT AUTHORITY command has

been issued to grant system authority to an
administrator ID, and at the same time to grant other
privileges.
command.
User response: Reissue the GRANT AUTHORITY
command specifying only system privilege class.
ANR2158E
Command: Policy domains cannot be

specified for unrestricted policy

entered with a file space name that is longer than
allowed. Note that the maximum length of a unicode
file space name is eight characters less than the
maximum length of a non-unicode file space name.
Explanation: A REVOKE AUTHORITY command has

been issued to revoke an administrators policy
authority over a specific policy domain, but the
administrator has unrestricted policy authority.

command.

command.
User response: Reissue the command with a valid file

space name.

ANR2159E
ANR2154E
Command: Invalid administrator name administrator ID.

administrator ID.
command.
administrator ID.
Command: Storage pools cannot be

specified for unrestricted storage

been issued to revoke an administrators storage
authority over a specific storage pool, but the
administrator has unrestricted storage authority.
command.
ANR2155E
Command: Invalid privilege class privilege class.
Explanation: A command specifies an invalid

administrative privilege class.
command.
privilege class.
ANR2156E

has already been granted system
privilege.

been issued to grant system authority to an
administrator ID that already has system authority.
command.
ANR2160E
Command: No new privileges granted to


been issued to grant authority to an administrator ID,
but the administrator already has all privileges
specified.
command.
ANR2161E
Command: Only system privilege can be

revoked for administrator administrator
ID.

been issued to revoke one or more of an
administrators privileges, but the administrator has
system authority.

287
ANR2162E ANR2171E
command.

command.

begin time.
ANR2162E
Command: No privileges revoked for


been issued to revoke authority from an administrator
ID, but the administrator does not have any of the
privileges specified.
command.
ANR2163E
Command: Command is invalid for

administrator ID.
Explanation: The command specified cannot be issued

for the server console. For instance, the server console
administrator ID cannot be removed.
command.
ANR2164E
Command: Command rejected administrator ID is the only system

administrator.
Explanation: A REMOVE ADMIN or REVOKE

AUTHORITY command has been issued to remove or
revoke the authority of the last administrator who had
system authority.
command.
User response: To remove or revoke this ID, grant
system authority to another administrator ID before
reissuing the command.
ANR2165E
Command: Invalid begin date - date.
Explanation: A QUERY ACTLOG command has been

entered that specifies an invalid begin date as a search
criteria.
command.
begin date.
ANR2166E
Command: Invalid begin time - time.

entered that specifies an invalid begin time as a search
criteria.
288
ANR2167E
Command: Invalid end date - date.

entered that specifies an invalid end date as a search
criteria.
command.
User response: Reissue the command with a valid end
date.
ANR2168E
Command: Invalid end time - time.

entered that specifies an invalid end time as a search
criteria.
command.
User response: Reissue the command with a valid end
time.
ANR2169E
Command: Invalid message number message number.

entered that specifies an invalid message number as a
search criteria.
command.
message number.
ANR2170E
Command: Invalid message search string

argument - search string.

entered that specifies an invalid search string as a
search criteria.
command.
search string.
ANR2171E
Command: Invalid time range - Begin:

date time End: date time.

entered that specifies an invalid beginning and ending
date/time range. This error can occur when the
beginning date/time is not before the ending
date/time.
ANR2172E ANR2180W
command.
date/time range.
ANR2172E

User response: If desired, reissue the command with a
different administrator ID.
Command: Location information exceeds
Explanation: A DEFINE or UPDATE VOLUME

command has been entered that specifies a location
information value that is too long. The maximum valid
length is shown in the command.
command.
User response: Reissue the command with less
location information.
ANR2174E
Administrator administrator ID is not

registered. Schedule schedule name is not
processed and is marked as failed.

administrator ID that is not registered with the server.
The schedule and related command are not processed.
command.
User response: Update the command schedule with a
valid administrator ID which has the proper authority
to execute the scheduled command.
ANR2175I

command.
value.
Command: No matching administrators.
Explanation: The command shown specified an

administrator ID that does not match any administrator
ANR2173E
values are from 0 to 9999, inclusive.
Invalid password limit set to password

attempts limit attempts.
Explanation: The maximum number of consecutive

invalid passwords a node or administrator may send to
the server is indicated with the SET INVALIDPWLIMIT
command.
ANR2177I
node/admin name has count invalid

sign-on attempts. The limit is limit.
Explanation: The server detected an invalid password

for the specified node during sign-on processing. The
node currently has sent count consecutive invalid
passwords. The maximum allowed is limit. The server
will lock the node when limit is reached.
System action: The node or administrator session will
be refused.
must unlock the node or administrator with the
UNLOCK NODE or UNLOCK ADMIN command.
ANR2178E
node/admin name has been locked. Invalid

sign-on attempt limit (limit) reached.
Explanation: The specified node has been locked by

the server. The limit for consecutive invalid passwords
has been reached.
System action: The node or administrator session will
be refused.
must unlock the node or administrator with the
UNLOCK NODE or UNLOCK ADMIN command.
ANR2179E
Administrator administrator should have

been locked, but was not.
Explanation: The indicated administrator reached the

limit for consecutive invalid passwords and should
have been locked. If it were locked, there would be no
means to execute commands requiring system
authority.
System action: The administrator session will be
refused.
User response: Sign-on again using the correct
password.

ANR2180W

ANR2176E

invalid password attempts limit is not
valid - password attempts limit.
Explanation: A SET INVALIDPWLIMIT command has

been entered that specifies a value for the consecutive
invalid password attempts limit that is not valid. Valid
Unable to update last access date for

administrator administrator ID insufficient recovery log space.
Explanation: While establishing an administrative

session for the indicated ID, the server is unable to
update the administrators date of last access due to
insufficient recovery log space.
System action: The server establishes the
289
ANR2181W ANR2187W
administrative session, but the last access date is not
updated.
volumes are used.
ANR2181W

administrator administrator ID insufficient database space.

session for the indicated ID, the server cannot update
the administrators date of last access due to
insufficient database space.
updated.
ANR2182W

administrator administrator ID - internal
server error.

session for the indicated ID, the server cannot update
the administrators date of last access due to a server
internal error.
updated.
representative.
ANR2183W

was aborted.

commit that caused this transaction to be aborted. This
message may have been preceded by other messages
that give additional information about the failed
transaction.
fails.
transaction. If this was encountered while the server
was halting then this can be ignored. During server
290
HALT processing, existing in-flight transactions may be

aborted as a normal part of server shutdown
processing. If the error cannot be isolated and resolved,
ANR2184W

was aborted for command command.

commit for the specified server command. This
message should be preceded by other messages that
give additional information about the failed transaction.
fails.
ANR2185W
Transaction was aborted for command

command.

failed transaction.
fails.
ANR2186W
Transaction was aborted for session

platform).

failed transaction.
fails.
ANR2187W
Transaction was aborted for node/admin

name.
Explanation: An error is detected during a transaction

commit for the specified node or administrator name.
This message should be preceded by other messages
transaction.
ANR2188W ANR2196E
fails.
ANR2188W
A Transaction was aborted. The activity

is terminating.

failed transaction.
ends.
ANR2189W

was aborted for node/admin name.

commit for the specified node or administrator name.
This message should be preceded by other messages
transaction.
fails.
ANR2190E
command: Device class DISK cannot be

specified for this command.

valid list of volumes.
ANR2192E
Command: Unable to start background

process.
Explanation: The server command processor is not

able to start a background process to perform the
command command.
application.
ANR2193E
Command: Invalid option set name option set name.

option set name.
command.
option set name.
ANR2194E
Command: Invalid option set description

- too long.

description. The description is too long.
command.
description.
ANR2195E
Command: Invalid option sequence

number - option sequence number name.
Explanation: The DEVCLASS value DISK cannot be

specified for the command.

option sequence number.


command.

server.

option sequence number.
ANR2191E
command: Volume list contains defined

and undefined volumes.
Explanation: The list of volumes specified on the

SALVAGE VOLUME command must all be defined to
the server, or all not defined to the server.
ANR2196E
Command: Option name and/or Option

value is missing for define.
Explanation: The specified DEFINE command has

been entered, but no attributes have been specified for
the definition.
command.
User response: Reissue the DEFINE command with
one or more attributes to be defined
291
ANR2197E ANR2208I
ANR2197E

WEB authentication time out is not
valid - time-out value.

ANR2203I
Device class device class name defined.
Explanation: A SET WEBAUTHTIMEOUT command

has been entered that specifies a value that is not valid.
Valid values are from 0 to 9999, inclusive.
Explanation: A DEFINE DEVCLASS command has

created the device class indicated.

command.

value.
ANR2204I
ANR2198I
Command: Web authentication time-out

set to time-out value minutes.
Explanation: The time-out value that determines how

often WEB browser administrative users need to
re-authenticate with the server has been set with the
SET WEBAUTHTIMEOUT command to the value
displayed.
Device class device class name deleted.
Explanation: A DELETE DEVCLASS command has

deleted the device class indicated.
ANR2205I
Device class device class name updated.
Explanation: An UPDATE DEVCLASS command has

updated the device class indicated.

ANR2199I
Password expiration period for node

node name set to number of days days.
Explanation: The number of days that the node's

password can be used before it must be changed has
been set to the value indicated with the SET PASSEXP
command.
ANR2206I
Volume volume name defined in storage

pool storage pool name (device class device
class name).
Explanation: A DEFINE VOLUME command has

defined the volume indicated in the storage pool
shown that belongs to the device class shown.

ANR2200I
Storage pool storage pool name defined

(device class device class name).
Explanation: A DEFINE STGPOOL command has

created the storage pool indicated of the device class
shown.
ANR2201I
Storage pool storage pool name deleted.
ANR2207I
Volume volume name updated.
Explanation: An UPDATE VOLUME command has

updated the volume indicated.
ANR2208I
Volume volume name deleted from

Explanation: A DELETE STGPOOL command has

deleted the storage pool indicated.
Explanation: The volume indicated has been deleted

by one of the following:
v A DELETE VOLUME command was issued.
v The volume was empty and the volumes access

mode was updated to destroyed.
ANR2202I
Storage pool storage pool name updated.
Explanation: An UPDATE STGPOOL command has

updated the storage pool indicated.
292
v The volume was empty, scratch, and offsite, and the

access mode was changed to readwrite, readonly, or
unavailable.
v The volume was scratch, not offsite, and was
emptied by DELETE FILESPACE, RECLAMATION,
or RESTORE VOLUME/STGPOOL.
ANR2209W ANR2218E
v The volume was an empty scratch WORM FILE
volume and deleted by RECLAMATION since the
retention of the volume has expired.
Volume volume name contains no data.
Explanation: The AUDIT VOLUME or MOVE DATA

command entered specifies a volume that contains no
data.
command.
ANR2210I
Vary online initiated for disk volume

volume name.
ANR2215E
Command: Description text is too long.
Explanation: The specified description text is too long

for a command that allows description text to be
specified.

shorter description
ANR2216E
Command: Device class must be a

sequential device class.
Explanation: The device class specified on the

command is not a sequential device class.

System action: The command fails
Vary offline initiated for disk volume

volume name.
Explanation: A VARY OFFLINE command for the

volume shown is being processed and, if no errors
occur, the volume will be varied offline.
User response: Reissue the command specifying the

name of a sequential device class
ANR2217E
Command: Invalid backup set retention

Explanation: Server processing for the backup set

value) specified for the RETENTION parameter is not
valid.

ANR2212I

backup set name.
Explanation: A VARY ONLINE command for the

volume shown is being processed, and if no errors
occur the volume will be varied online.
ANR2211I
Command: Invalid backup set name backup set name.

backup set name.
ANR2209W
ANR2214E
Command: No volumes updated.
Explanation: An UPDATE VOLUME command has

been entered, but no objects were updated.

valid RETENTION value.

ANR2218E

ANR2213I

renamed to storage pool name.
Explanation: A RENAME STGPOOL command has

been entered. The rename of the storage pool was
successful.
Command: A device class must be

specified.
Explanation: The DEVCLASS parameter is not

specified in the command command name. A DEVCLASS
value must be specified.
server.
293
ANR2219I ANR2228W
ANR2219I
Discard Data process ended for volume

volume name - volume is not deleted
from storage pool storage pool name
because the volume access is offsite.
Explanation: The process that deleted data for the

volume shown has ended, but the volume has not been
deleted because the volume access is marked as offsite.
User response: To delete the volume, change the
volume access to readwrite, readonly, or unavailable.
ANR2220W
This command will delete volume

volume name from its storage pool after
verifying that the volume contains no
data.
Explanation: A DELETE VOLUME command with the

Discarddata=No option has been entered.
continue with the command.
User response: To process the DELETE VOLUME
process.

ANR2224W
Explanation: The process that was deleting data for

the volume shown, in preparation for deleting the
volume, has been canceled.
System action: The server does not delete the volume.
ANR2225W
This command will result in the

deletion of all inventory references to
the data on volume volume name, thereby
rendering the data unrecoverable.
Explanation: A DELETE VOLUME command with the

Discarddata=Yes option has been entered.
User response: To process the DELETE VOLUME
process.
ANR2222I
Discard Data process started for volume

volume name (process ID process ID).
Explanation: As a result of a DELETE VOLUME

command with the Discarddata=Yes option, the process
whose ID is displayed has begun to delete the data on
the volume shown.
System action: The server deletes the data on the
volume.
ANR2223I
Discard Data process ended for volume

volume name - volume deleted from
Explanation: The process that deleted data for the

volume shown has ended, and the volume has been
deleted.
294
Discard Data process terminated for

volume volume name - volume still
contains data.

volume, has ended. However, the volume contains
data.
ANR2226W
ANR2221W
Discard Data process terminated for

Discard data process terminated for


volume, has ended due to a shortage of recovery log
space.
volumes are used.
ANR2227W

is not available.

volume, has ended due to a shortage of memory.
application.
ANR2228W

volume volume name - lock conflict
detected.

ANR2229W ANR2237W
volume, has ended due to a locking conflict.
User response: Reissue the command at a later time. If
this problem persists, contact your service
representative.

continue.
User response: Enter 'Y' to halt the server or 'N' to
leave the server activated.
ANR2235W
ANR2229W

error detected.

volume, has ended due to a server internal error.
System action: The server does not delete the volume
ANR2232W
This command will move all of the data

stored on volume volume name to other
volumes within the same storage pool;
the data will be inaccessible to users
until the operation completes.
Explanation: A move data has been entered that will

move data from the indicated volume to other volumes
in the same storage pool. While the data is being
moved, it will not be available to users.
continue.
This command will remove

administrator adminName. This
administrator has defined or updated
schedules. Removing this authority
WILL cause these schedules to fail.
Explanation: A REMOVE ADMINISTRATOR

command has been entered for an administrator that
owns administrative schedules. If you confirm that you
want to proceed with this command, the schedules
owned by this administrator will fail when executed in
the future.
User response: To process the REMOVE
ADMINISTRATOR command, enter 'Y' to continue or
'N' to stop the process. To deal with schedules owned
by the administrator, use the QUERY SCHEDULE
command OR an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which
schedules were last updated by the administrator. Use
the UPDATE SCHEDULE command to update those
schedules under an administrator that has authority to
execute them, or use the DELETE SCHEDULE
command to remove the schedules.
ANR2236W
User response: Enter 'Y' to continue with the

command or 'N' to end the process.
This command has removed

schedules. This WILL cause these
schedules to fail in the future.
This command will move all of the data

stored on volume volume name to other
volumes in storage pool storage pool
name; the data will be inaccessible to
users until the operation completes.
Explanation: A REMOVE ADMINISTRATOR

command has been entered and the administrator
removed owns administrative schedules. The schedules
will fail when executed in the future because they do
not belong to a valid administrator.
Explanation: A move data has been entered that will

move data from the indicated volume to volumes in
the storage pool shown. While the data is being moved
it will not be available to users.
System action: The system removes the administrator.
ANR2233W
User response: Enter 'Y' to continue with the

command or 'N' to end the process.
User response: Use the QUERY SCHEDULE command

OR an SQL SELECT statement on the
ANR2234W
ANR2237W

continue.
This command will halt the server; if

the command is issued from a remote
client, it may not be possible to restart
the server from the remote location.
Explanation: A HALT command has been entered.
This command has revoked privileges

for administrator adminName. This
schedules. This may cause these
schedules to fail in the future.
295
ANR2238W ANR2248I
been entered.
the new volume to synchronize it with existing

volumes.
System action: The system removes the authority.
ANR2238W
ANR2243I
This command will result in the

deletion of all inventory references to
the data on filespaces that match the
pattern filespace name for node node name,
whereby rendering the data
unrecoverable.
Explanation: A DELETE FILESPACE command has

been entered.
Database volume volume name deleted.
Explanation: A DELETE DBVOLUME command has

deleted the database volume indicated.
ANR2244I

Delete process initiated for database

volume volume name (process id process
ID).
User response: To process the DELETE FILESPACE

command, enter 'Y'; otherwise, enter 'N'.
Explanation: In response to a DELETE DBVOLUME

command, the process with the process ID shown has
been started to delete the volume.
ANR2239W
This command will revoke privileges

for administrator adminName. This
schedules. Revoking this authority may
cause schedules to fail.

been entered.
User response: To process the REVOKE AUTHORITY
process.
ANR2240I

ANR2245I
Explanation: A VARY ONLINE command has put the

database volume indicated into an online state.
ANR2246I
Database volume volume name defined.
Explanation: A DEFINE DBVOLUME command has

defined the database volume indicated.

online.
Vary online process initiated for

database volume volume name (process
ID process ID).
Explanation: In response to a VARY ONLINE

been started to vary on the database volume indicated.

ANR2241I
Database volume copy volume name

defined.
Explanation: A DEFINE DBCOPY command has

defined the database volume indicated.
ANR2247I

offline.
Explanation: A VARY OFFLINE command has put the

indicated database volume into an offline state.

ANR2242I
Database volume copy volume name

defined; synchronization process started
(process ID process ID).

added the volume shown as a database copy volume.
The process whose ID is displayed will copy data to
296
ANR2248I
Database assigned capacity has been

extended.
Explanation: An EXTEND DB command has increased

the storage capacity of the database.
ANR2249I ANR2257E
ANR2254E
Command: The VOLUMENAMES

parameter must be specified when
SCRATCH=NO is specified.
Explanation: In response to an EXTEND DB

been started to extend the database.
Explanation: The SCRATCH parameter is specified as

NO for the command Command but the
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES
parameter must be specified to indicate the volumes
that can be used for the command.

valid VOLUMENAMES parameter.
ANR2249I
ANR2250I
Database extension process initiated

Database assigned capacity has been

reduced.
Explanation: A REDUCE DB command has decreased

the storage capacity of the database.
ANR2251I
Database reduction process initiated

Explanation: The VOLUMENAMES parameter must

be specified to indicate the volumes that can be used
for the command.

valid VOLUMENAMES parameter.
ANR2256E
Command: The RETENTION parameter

must be specified.
Explanation: The RETENTION parameter must be

specified to indicate the retention period to be used for
the command.

Database volume copy volume name is
larger than volume volume name by count
megabyte(s).

defined a database copy volume whose size is larger
than the volume it mirrors by the amount shown.
System action: The excess capacity is ignored.
ANR2253W
Command: The VOLUMENAMES

parameter must be specified.
Explanation: In response to a REDUCE DB command,

the process with the process ID shown has been started
to reduce the database.
ANR2252W
ANR2255E
The database volume copy to be defined

(volume name) is larger than volume
volume name; use of the volume will
result in count megabyte(s) of unusable
space.
Explanation: A DEFINE DBCOPY command is

attempting to define a database copy volume whose
size is larger than the volume it mirrors by the amount
shown. The excess capacity would not be used.
continue.
User response: Enter 'Y' to define the copy, 'N'
otherwise.

valid RETENTION parameter.
ANR2257E

command for node node name.

command for the indicated node. Note: This message
can be issued as a result of the server option
REQSYSAUTHOUTFILE YES being in effect.
command for the indicated node. If multiple nodes
were specified on the command, the server may
continue processing the command for the other nodes.
User response: Examine previous messages for any
additional information. Issue the command from a
properly authorized administrator ID, or contact the
system administrator to have additional authority
granted to the current administrator ID.
297
ANR2258E ANR2269I
ANR2258E
Command: Invalid summary retention

Explanation: A SET SUMMARYRETENTION

retention period.

ANR2264I
Delete process initiated for recovery log

volume volume name (process id process
ID).

command.
Explanation: In response to a DELETE LOGVOLUME

command, the process with process ID shown has been
started to delete the volume.

retention period.

ANR2259I
Summary retention period set to number

of days days.
Explanation: The number of days that activity sumary

records are kept in the server database has been set to
the value indicated with the SET
SUMMARYRETENTION command.
ANR2265I

online.
Explanation: A VARY ONLINE command has put the

recovery log volume indicated into an online state.

ANR2266I
ANR2260I
Recovery log volume volume name

defined.
Explanation: A DEFINE LOGVOLUME command has

defined the recovery log volume indicated.
Vary online process initiated for

recovery log volume volume name
Explanation: In response to a VARY ONLINE

command, the process with process ID shown has been
started to vary on the recovery log volume indicated.
ANR2261I
Recovery log volume copy volume name

defined.
Explanation: A DEFINE LOGCOPY command has

defined the recovery log volume indicated.
ANR2267I

offline.
Explanation: A VARY OFFLINE command has put the

recovery log volume indicated into an offline state.
ANR2262I

defined; synchronization process started
ANR2268I
Recovery log assigned capacity has been

extended.

added the volume shown as a log copy volume. The
process whose ID is displayed copied data to the new
volume to synchronize it with existing volumes.
Explanation: An EXTEND LOG command has

increased the storage capacity of the recovery log.

ANR2263I
Recovery log volume volume name

deleted.
Explanation: A DELETE LOGVOLUME command has

removed the recovery log volume indicated.
298
ANR2269I
Recovery log extension process initiated

Explanation: In response to an EXTEND LOG

been started to extend the recovery log.
ANR2270I ANR2279I
ANR2270I
Recovery log assigned capacity has been

reduced.
Explanation: A REDUCE LOG command has

decreased the storage capacity of the recovery log.
Recovery log reduction process initiated

Explanation: In response to a REDUCE LOG

been started to reduce the recovery log.
ANR2272W

is larger than volume volume name by
count megabytes.

defined a recovery log copy volume whose size is
larger than the volume it mirrors by the amount
shown.
System action: The excess capacity is ignored.
ANR2273W
Data Base Space trigger defined, but is

disabled.
Explanation: A database space trigger has been

defined, but because the space expansion percentage is
currently set to 0, the space trigger is disabled.

ANR2271I
ANR2275I
The recovery log volume copy to be

defined (volume name) is larger than
volume volume name; use of the volume
will result in count megabytes of
unusable space.
Explanation: A DEFINE LOGCOPY command is

attempting to define a recovery log copy volume whose
size is larger than the volume it mirrors by the amount
shown. The excess capacity would not be used.
continue.
User response: Enter 'Y' to define the copy or 'N' to
stop the process.
User response: To activate the space trigger, use the

UPDATE SPACETRIGGER command to set the space
expansion percentage to a value greater than 0.
ANR2276I
Data Base Space trigger updated and

enabled.
Explanation: An UPDATE SPACETRIGGER command

has successfully completed for the data base space
trigger. The updated parameters specified on the
command are used to automatically trigger space
expansion for the database.
ANR2277I
Database Space trigger updated, but

disabled.

has successfully completed for the data base space
trigger. However, the space expansion percentage is
currently set to 0, which disables the space trigger.
UPDATE SPACETRIGGER command with the
SPACEexpansion parameter to set a value greater than
zero.
ANR2278I
Database Space trigger deleted.
Explanation: A DELETE SPACETRIGGER command

has successfully completed for the database space
trigger. Space expansions are no longer triggered
automatically for the database.
ANR2274I
Data Base Space trigger defined and

enabled.
Explanation: The database space trigger has been

defined with a DEFINE SPACETRIGGER command.
The percentage of utilization specified with the
FULLPCT parameter is used to automatically expand
the database.
ANR2279I
Recovery Log Space trigger defined and

enabled.
Explanation: The recovery log space trigger has been

defined with a DEFINE SPACETRIGGER command.
The percentage of utilization specified with the
FULLPCT parameter is used to automatically expand
the recovery log.
299
ANR2280I ANR2288I
ANR2280I
Full database backup started as process

process ID.

backup the contents of the database. The full database
backup process was assigned the process ID shown.
System action: The database backup process starts
status of the database backup process by using the
QUERY PROCESS command, or cancel the process with
ANR2281I
Incremental database backup started as

process process ID.

backup the contents of the database. The incremental
database backup process was assigned the process ID
shown.
ANR2282I
Database backup trigger defined and

enabled.
Explanation: A database backup trigger has been

defined with a DEFINE DBBACKUPTRIGGER
command. The percentage of recovery log utilization
specified with the LOGFULLPCT parameter is used to
automatically trigger database backups.
ANR2284I
Explanation: An UPDATE DBBACKUPTRIGGER

command has successfully completed. The updated
parameters specified on the command are used to
automatically trigger database backups.
ANR2285I
ANR2283I
Database backup trigger defined, but is

disabled.
Explanation: A database backup trigger has been

defined, but because the recovery log mode is currently
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
LOGMODE command.
Database backup trigger updated, but

disabled.
Explanation: An UPDATE DBBACKUPTRIGGER

command has successfully completed, but because the
recovery log mode is currently 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 LOGMODE command.
User response: To activate the database backup
trigger, use the SET LOGMODE ROLLFORWARD
command.
ANR2286I
Database backup trigger deleted.
Explanation: A DELETE DBBACKUPTRIGGER

command has successfully completed. Database
backups are no longer triggered automatically by
recovery log utilization.
ANR2287I

Database backup trigger updated and

enabled.
Snapshot database backup started as

process process ID.

backup the contents of the database. The snapshot
database backup process was assigned the process id
shown.
started process by using the QUERY PROCESS
command, or may cancel the process using the

User response: To activate the database backup
trigger, use the SET LOGMODE ROLLFORWARD
command.
ANR2288I
Subfile set to state.
Explanation: The SET SUBFILE command has been

used to specify whether this server will allow clients to
back up subfiles. If a value of CLIENT is specified,
clients are given the option of backing up subfiles. If a
value of NO is specified, clients are not allowed to back
up subfiles.
300
ANR2289I ANR2296I
ANR2289I
ANR2293I

name defined for authority over node
node name has not been removed.
Explanation: The specified administrator was not

removed.
Only point-in-time database recovery is

now possible.
Explanation: An administrator has changed the

recovery log mode from ROLLFORWARD to NORMAL
with a SET LOGMODE command. Only point-in-time
database restores can be performed. ROLLFORWARD
database restores and individual database volume
restores are not possible.

ANR2290W
Changing the log mode to NORMAL

will prevent roll-forward recovery.
Explanation: The system has determined that

changing the recovery log mode from ROLLFORWARD
to NORMAL mode will cause the log records being
kept for ROLLFORWARD and single database volume
restore processing to be discarded. Without these log
records, only point-in-time database restores can be
performed.
continue.
User response: Enter 'Y' to change the LOGMODE, 'N'
otherwise.
ANR2294I
Log mode set to log mode.
Explanation: The mode for saving recovery log

records has been set as indicated by the SET
LOGMODE command. When set to NORMAL, only
those log records needed to resume database processing
if a system failure occurs are saved. When set to
ROLLFORWARD, all log records created since the last
database backup are saved. ROLLFORWARD mode
also enables the database backup trigger to be used to
automatically start database backups based on the
percentage of recovery log utilization.
ANR2291W
Changing the log mode to NORMAL

will disable the database backup trigger.
Explanation: Changing the recovery log mode from

ROLLFORWARD to NORMAL disables the setting
specified in the DEFINE DBBACKUPTRIGGER
command. Database backups can only be triggered
when the recovery log mode is set to ROLLFORWARD
with the SET LOGMODE command.
continue.
User response: Enter 'Y' to change the log mode, 'N'
otherwise. Responding 'Y' does not delete the DEFINE
DBBACKUPTRIGGER settings.
ANR2295I

records has been set to ROLLFORWARD, and a
previously defined database backup trigger has been
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
on the percentage of recovery log utilization.
ANR2296I
ANR2292W
Changing the log mode to

ROLLFORWARD will enable the
database backup trigger.
Explanation: Changing the recovery log mode from

NORMAL to ROLLFORWARD causes a previously
issued DEFINE DBBACKUPTRIGGER command to
become effective, and immediately start a full database
backup. Database backups can only be triggered when
the recovery log mode is set to ROLLFORWARD with a
SET LOGMODE command.
continue.
Log mode set to ROLLFORWARD;

database backup trigger enabled.
Log mode set to NORMAL; database

backup trigger disabled.

records has been set to NORMAL mode, and the
defined database backup trigger is disabled. Only those
log records needed to resume database processing if a
system failure occurs are saved in this mode. Database
backups can only be started using the BACKUP DB
command.
User response: Enter 'Y' to change the log mode, 'N'

otherwise.
301
ANR2297I ANR2306E
ANR2297I
Command: Optionset optionset name,

option option name, sequence number old
sequence number, has been changed to
new sequence number.
Explanation: The requested option sequence number

has been updated in response to an UPDATE
CLIENTOPT command.
ANR2298I
Command: Optionset optionset name,

option option name, sequence number old
sequence number, is not updated.
Explanation: The requested option sequence number

is not updated in response to an UPDATE CLIENTOPT
command.
User response: Reissue the UPDATE CLIENTOPT
command with a valid old sequence number.
ANR2299I
Password expiration period for

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
changed has been set to the value indicated with the
SET PASSEXP command.
ANR2302E
The argument operand is not valid for

the HELP command.
Explanation: The argument supplied on the HELP

command is not an integer or the name of a command.
System action: The server does not process the HELP
command.
User response: Issue the HELP command with no
operands and select from the numbered list displayed
in response.
ANR2303E
There is no help section numbered

section number.
Explanation: The numeric operand supplied on the

HELP command is either less than 1 or greater than the
highest-numbered entry in the help index.
command.
User response: Issue the HELP command with no
operands and select from the numbered list (help
index) displayed in response.
ANR2304E
I/O error reading "help file name" the file

of help text.
Explanation: An error is detected when reading help

text from the named file.
System action: The server ends display of the help
text.
User response: Contact the system administrator.

ANR2305E
ANR2300E
Could not open "file spec" the server help

file.
No such command/subcommand:
command subcommand.
Explanation: The named help file could not be

accessed.
Explanation: The operands you entered for the HELP

command do not match any named entry into the file
of help text.
System action: The requested help text is not

displayed.

command.
User response: Check your input for a misspelled

command or subcommand name.
ANR2301E
Errors were encountered while setting

up the index to the help text.
Explanation: Either insufficient memory or a help file

read failure has occurred during setup of the help
index.
System action: The server does not display the
requested help text.
ANR2306E
No help text could be found for this

command/subcommand: command.
Explanation: The operands you entered for the HELP

command, although valid command/subcommand
names, do not match any named entry into the file of
help text.
command.
302
ANR2307E ANR2313I
ANR2307E
No help text could be found for this

message: message ID.
ANR2310W
Explanation: The message ID you entered for the help

command does not match any message entry in the file
of help text.
System action: The help command is not processed.
ANR2308W
Audit Volume marking damaged file as

damaged on volume volume name: Node
node name, Type file type, File space
filespace name, fsId filespace id, File Name
file name is number version of total
versions versions.
Explanation: As the result of an AUDIT VOLUME

command that specified FIX=YES for the volume
shown, the file whose information is displayed is
marked as damaged in the server. The file is marked as
damaged because it can be recovered from a copy
known to exist in a COPY storage pool. If this file
belongs to an aggregate, the entire aggregate is marked
damaged, and this message will be issued for every file
in the aggregate. The version numbers for the file are
numbered from most recent (1) to least recent (n, where
n is the total number of versions.
System action: The file is marked as damaged in the
server database.
User response: To recover the damaged file use the
RESTORE STGPOOL or RESTORE VOLUME command.
ANR2309E
The server log mode is currently set to

roll-forward. You may run out of log
space when auditing the server in this
mode. Specify LOGMODE=NORMAL
to set the log mode to NORMAL for the
audit operation, or
LOGMODE=ROLLFORWARD to force
the audit operation with the logmode
set to roll-forward.
Explanation: An AUDITDB operation was specified

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
emergency extend of the recovery log to re-start the
server. The recommended log mode for executing an
AUDITDB operation is NORMAL.
System action: The AUDITDB operation fails
User response: To force the server log mode to
NORMAL for the AUDITDB operation, specify
LOGMODE=NORMAL on the AUDITDB command.
Specify LOGMODE=ROLLFORWARD on the
AUDITDB command to allow the audit to run with a
roll-forward log mode setting.
This command will compare all

inventory references to volume volume
name with the actual data stored on the
volume and will report any
discrepancies; the data will be
inaccessible to users until the operation
completes.
Explanation: During the execution of an AUDIT

VOLUME command, any data the volume named
would be unavailable to users.
continue.
stop the process.
ANR2311W
This command will discard any

inventory references to volume volume
name associated with missing or
inconsistent stored data, thereby
rendering the data unrecoverable; the
valid data on the volume will be
inaccessible to users until the operation
completes.
Explanation: During the execution of an AUDIT

VOLUME command, any data the volume named
would be unavailable to users. After the command has
ended, any inconsistent data found will be discarded.
continue.
stop the process.
ANR2312I
Audit Volume (Repair) process started

for volume volume name (process ID
process ID).

shown, the process whose ID is displayed has begun
auditing the volume.
System action: The volume is audited and
inconsistent data is discarded.
ANR2313I
Audit Volume (Inspect Only) process

started for volume volume name (process
ID process ID).

command that specified FIX=NO for the volume
shown, the process whose ID is displayed has begun
auditing the volume.
System action: The volume is audited and
inconsistent data is displayed.
303
ANR2314I ANR2320W
file are numbered from most recent (1) to least recent

(n, where n is the total number of versions.
ANR2314I
System action: The file is deleted.
Audit volume process ended for volume

volume name; file count files inspected, file
count damaged files deleted, file count
damaged files marked as damaged.
Explanation: The AUDIT VOLUME command

specifying FIX=YES for the volume shown has ended.
The number of files audited and the number of
inconsistent files deleted or marked as damaged are
displayed. The number of files marked as damaged
includes all files belonging to aggregates that were
marked damaged during the audit. Files are marked as
damaged in primary storage pools and not deleted
when backup copies for the files are known to exist in
COPY storage pools.
User response: To recover files that have been marked
as damaged on the volume, use the RESTORE
STGPOOL or RESTORE volume command.
ANR2315I

count damaged files found and marked
as damaged.

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
files marked damaged includes all files belonging to
aggregates that were marked damaged during the
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
of the files reside in a COPY storage pool. Another
AUDIT VOLUME command may be able to access the
files and reset the damaged indicator in the database if
the audit volume process cannot access the files due to
hardware problems (for example, dirty tape heads).
User response: If you suspect that files were
inaccessible because of hardware problems such as
dirty tape heads, correct the hardware problem and
reissue the AUDIT VOLUME FIX=NO command for
this volume. To remove damaged file references, issue
the AUDIT VOLUME command and specify FIX=YES.
ANR2316W
Audit Volume deleting damaged file on

fsId filespace id, File Name file name is
number version of total versions versions.

shown, the file whose information is displayed is
deleted from the server. The version numbers for the
304

ANR2317W
Audit Volume found damaged file on

fsId filespace id, File name file name is
number version of total versions versions.

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,
and this message will be issued for every file in the
aggregate. The version numbers for the file are
numbered from most recent (1) to least recent (n, where
n is the total number of versions.
ANR2318W
Audit volume process terminated for

Explanation: During processing of an AUDIT

VOLUME command for the volume shown, the process
performing the audit was canceled.
System action: The AUDIT VOLUME command is
ended.
ANR2319W

volume volume name - error reading
device.

VOLUME command for the volume shown, an
unrecoverable read error occurred on the volume.
ended.
User response: Attempt to correct the cause of the
read error, and reissue the command.
ANR2320W

volume volume name - data transfer
interrupted.

VOLUME command for the volume shown, a data
transfer operation has been interrupted and cannot be
continued.
ended.
ANR2321W ANR2332W
cause of the interruption, and reissue the command.
ANR2321W

volume volume name - storage media
inaccessible.

VOLUME command for the volume shown, a required
volume cannot be mounted.
ended.
ANR2325W

is not available.

VOLUME command for the volume shown, the server
does not have enough memory available to complete
the command.
ended.
User response: If necessary make more memory

ANR2326W
ANR2322W


does not have sufficient recovery log space to continue.
ended.
User response: If necessary, make more recovery log
space available to the server.
ANR2323W

volume volume name - sufficient database

does not have sufficient database space to continue.

volume volume name - lock conflict
detected.

cannot obtain a required lock.
ended.
User response: Reissue the command.
ANR2327W

error detected.

VOLUME command for the volume shown, an internal
server error occurs.
ended.

ended.
User response: If necessary, make more database

space available to the server.
ANR2332W
ANR2324W

volume volume name - thread resource
not available.

cannot start a thread for the audit process.
ended.
User response: Reissue the AUDIT VOLUME
command. If the error persists, it may indicate a
Object object.ID deleted by another

process during execution of an AUDIT
VOLUME command for volume volume
name.

VOLUME command, a data storage object was deleted
from the volume that was being audited. The AUDIT
VOLUME process was unable to locate this object on
the specified volume. Normally, this action is not
considered an error condition, because the object was
probably deleted by a process such as a DELETE
FILESPACE command.
System action: Processing of the AUDIT VOLUME
command continues.
User response: Check the activity log to verify that
some process (such as a DELETE FILESPACE
command) was in progress during the AUDIT
VOLUME command that would account for the deleted
object. If no such process can be identified, contact your
305
ANR2333W ANR2341E
ANR2333W
Missing or incorrect information

detected by AUDIT VOLUME for
volume volume name.
Explanation: An AUDIT VOLUME command detects

missing or incorrect information for the specified
volume.
User response: Reissue the audit command with
FIX=YES so that the information can be created or
corrected.
ANR2337W
Explanation: The header size for the specified object

was recalculated while anditing a volume.
System action: If FIX=YES was specified, the header
size for the object will be updated. Processing
continues.
ANR2338E
ANR2334W
Missing or incorrect information

detected by AUDIT VOLUME for
volume volume name - information will
be created or corrected.
Explanation: An AUDIT VOLUME process detects

missing or incorrect information for the specified
volume. Because FIX=YES has been specified for the
audit command, the information is created or corrected.
ANR2335W
Audit Volume has encountered an I/O

error for volume volume name while
attempting to read: Node node name,
Type file type, Filespace filespace name,
fsId filespace id, File Name file name.
Explanation: The AUDIT VOLUME process

encountered an I/O error for the specified volume
while attempting to read the specified file. If this file
belongs to an aggregate, the entire aggregate is marked
damaged, and this message will be issued for every file
in the aggregate.
User response: Identify and resolve the I/O error for
the volume if possible. Verify that the volumes device
is functioning properly and that the volume is usable.
For example, if the volume is a tape volume, make sure
the drive is clean or that the tape volume is usable by
testing it by using a different drive.
ANR2336W
Audit Volume terminated for volume

volume name - insufficient number of
media.
Header size is reset for object Object ID,

verb type (Verb Type), from (Header Size)
to (Verb Length).
Diagnostic(ID): Invalid header received

for object ObjectID, length Data Length.
Size (Header Size), pushed (Pushed
Length), skipped (Skipped Length), status
(New Retrieve). Found length (Verb
Length), type (Verb Type), size (Verb Size).
Explanation: An invalid header was detected for the

specified object while auditing a volume. Diagnostic
information is included in the message.
System action: If FIX=YES was specified, this object
will be marked damaged. Processing continues.
User response: Restore the volume or storage pool
that includes this object.
ANR2339E
Command: Object sets still exist for node

node name.
Explanation: A REMOVE NODE command has been

entered for a node for which the server is still storing
backup sets. To remove a node, the node must not have
any files or backup sets stored on the server.
command.
User response: To remove the node, delete all backup
sets from the server and reissue the command.
ANR2340E
Command: Invalid storage pool name storage pool name.
Explanation: The command indicated contains an

invalid storage pool name.
command.
storage pool name.
Explanation: During Audit Volume for the indicated

volume, the server could not allocate sufficient mount
points for the volume required.
ANR2341E
System action: Audit Volume stops.
Explanation: The command indicated requires a

storage pool name, but none has been entered.

available.
306
Command: Missing next storage pool

name.

command.
ANR2342E ANR2351E
User response: Reissue the command with a storage
pool name.
ANR2342E
Command: Storage pool description

exceeds maximum characters characters.
Explanation: The command indicated contains a

storage pool description that exceeds the maximum
length allowed.
command.
storage pool description.
ANR2343E
Command: Invalid device class name device class name.

volume name.
ANR2347E
Explanation: The command shown was entered with a

volume name pattern that matches more than one
volume. The command can only process a single
volume.
User response: Reissue the command with a more
specific volume name.
ANR2348E

invalid device class name.
command.
device class name.
ANR2344E
Command: The "option" option is not

valid for device class device class name.
Explanation: The command indicated specifies an

option shown that is not valid for a storage pool that
belongs to the device class shown.
command.
User response: Reissue the command with options
appropriate to the device class.
ANR2345E
Command: Invalid volume name - volume

name.

invalid volume name.
command.
volume name.
ANR2346E
Command: Volume name "volume name" is

not valid for device class device class
name.

name of a volume that cannot be used with the device
class shown.
command.
Command: Volume name "volume name" is

ambiguous; resolves to multiple defined
volume names.

valid for a volume assigned to a primary
storage pool.

option that is not valid for a volume in a primary
storage pool.
command.
User response: Reissue the command with valid
options for a volume in a primary storage pool.
ANR2349E

valid for a volume assigned to a copy
storage pool.

option that is not valid for a volume in a copy storage
pool.
command.
options for a volume in a copy storage pool.
ANR2350E
Command: Device class device class name

is already defined.
Explanation: The command indicated has attempted

to define a device class that already exists.
command.
ANR2351E

is not defined.
Explanation: The command indicated references a

device class that does not exist.
command.
307
ANR2352E ANR2360E
ANR2352E

may not be deleted.
Explanation: A DELETE DEVCLASS command

specifies the class name DISK, which is a
system-defined device class and may not be deleted.
command.
ANR2353E

may not be updated.
Explanation: An UPDATE DEVCLASS command

specifies the class name DISK, which is a
system-defined device class and may not be changed.
command.
ANR2354E

is still referenced by one or more
storage pools, or database backup, or
export volumes or backupset volumes.
Explanation: The DELETE DEVCLASS command has

attempted to delete a device class that has storage
pools assigned to it, or is referenced by database
backup, export volumes or backupset volumes.
command.
User response: Issue Q DEVCLASS to view the
storage pool reference count, Q STGPOOL to determine
which pool references the device class, and Q VOLHIST
to locate database backup or export volume or
backupset volume references.
ANR2355E
Command: Required parameter is

missing - missing parameter.

entered without the required parameter. The required
parameter is shown.
proper syntax.
ANR2356E
Command: Incompatible parameters

specified - first parameter, second
parameter.

proper syntax.
ANR2357E
Explanation: An attempt is made to define a copy

storage pool using a device of DISK. Copy storage
pools can only be assigned to a sequential device class.
command.
sequential device class.
ANR2358E

is still referenced in the volume history
file.
Explanation: The DELETE DEVCLASS command has

attempted to delete a device class that is associate with
entries in the volume history file. These entries are for
volumes that contain database backup or export data.
command.
User response: Use the DELETE VOLHIST command
to remove that entries before deleting the device class.
ANR2359E
Command: Volume name "volume name"

must be specified with a DISK or FILE
STGPOOL.

name of a volume that must be specified with a storage
pool associated with a device class of type DISK or
FILE.
command.
volume name and storage pool.
ANR2360E

may not be used for database backup.
Explanation: The command specifies the DISK device

class, which cannot be used for database backup,
backup trigger, or restore operations.
command.
device class.

entered with mutually exclusive parameters. The two
parameters are listed.
308
Command: The DISK device class is not

supported for copy storage pools.
ANR2361E ANR2369I
ANR2361E
Command: A full database backup is

required.
Explanation: A BACKUP DB command specified an

incremental backup, but a full backup is required.
command.
User response: Reissue the command specifying a full
backup.
ANR2362E
Command: Database backup is not

currently possible - compressed log
records exist in the current transaction
checkpoint.
Explanation: A BACKUP DB command was issued

but a database backup cannot be started. Log
compression has recently taken place, and the
compressed log records are still part of the current
transaction checkpoint. After these log records are no
longer part of the current checkpoint a backup can take
place.
command.
ANR2363E
Command: One of the following

parameter must be supplied but is
missing - missing parameter, missing
parameter, missing parameter, missing
parameter.

entered without one of the mutually exclusive required
parameters. One of the parameters from the list must
be specified.

ANR2366I
Backupset backup set name for node node

name (data type data type) would have
been deleted.
Explanation: The backup set would have been deleted

as the result of a DELETE BACKUPSET command, but
the PREVIEW=YES parameter was specified.
User response: If the backup set is to be deleted,
reissue the command without specifying
PREVIEW=YES.
ANR2367I
Retention period for backupset backup

set name for node node name (data type
data type) has been updated.
Explanation: The backup set's retention period has

been updated.
System action: The server has updated the
backupset's retention period.
ANR2368I
Retention period for backupset backup

set name for node node name (data type
data type) would have been updated.
Explanation: The backup set's retention period would

have been updated as the result of an UPDATE
BACKUPSET command, but the PREVIEW=YES
parameter was specified.
User response: If the backup set is to be updated,

reissue the command without specifying
PREVIEW=YES.

proper syntax.
ANR2369I
ANR2364E
Command: Missing reclaim-storage pool

name.
Explanation: The command indicated requires a

storage pool name, but none has been entered.
command.
User response: Reissue the command with a storage
pool name.
ANR2365I

name (data type data type) has been
deleted.
Explanation: The backup set has been deleted.

System action: The server has deleted the backupset.
Database backup volume and recovery

plan file expiration starting under
process process ID.
Explanation: The server has started expiration

processing to remove expired database backup volumes
and recovery plan files created on a remote server. This
message is issued only if DRM is licensed on the
server. The DB backup volumes expired is based on the
value specified on the SET
DRMDBBACKUPEXPIREDAYS. The recovery plan files
expired is based on the value specified on the SET
DRMRPFEXPIREDAYS. Server inventory expiration
processing deletes the DB backup volumes and
recovery plan files only if the volumes or plan files are
created on the server to server virtual volumes.
expiration process is cancellable.
309
ANR2370E ANR2379I
ANR2370E
Command: Database backup trigger is

already defined.
ANR2375E
Command: Recovery Log trigger is not

defined.
Explanation: The database backup trigger cannot be

defined because it is already defined.
Explanation: The recovery log space trigger cannot be

updated or deleted because it is not currently defined.

command.

command.
User response: Use the UPDATE

DBBACKUPTRIGGER command to modify the
database backup trigger parameters.
ANR2371E

not defined.
Explanation: The database backup trigger cannot be

command.
ANR2372E
Command: Database Space trigger is

already defined.
Explanation: The database space trigger cannot be

command.
User response: Use the UPDATE SPACETRIGGER
command to modify the indicated space trigger
parameters.
ANR2373E

not defined.
Explanation: The database space trigger cannot be

command.
ANR2374E
Command: Recovery Log Space trigger is

already defined.
Explanation: The recovery log space trigger cannot be

command.
parameters.
ANR2376I
Recovery Log Space trigger defined, but

is disabled.
Explanation: A recovery log space trigger has been

defined, but because the space expansion percentage is
currently set to 0, the space trigger is disabled.
ANR2377I
Recovery Log Space trigger updated and

enabled.

has successfully completed for the recovery log space
trigger. The updated parameters specified on the
expansion for the database.
ANR2378I
Recovery Log Space trigger updated, but

disabled.

trigger. However, the space expansion percentage is
currently set to 0, which disables the space trigger.
zero.
ANR2379I
Recovery Log Space trigger deleted.

trigger. Space expansions are no longer triggered
automatically for the recovery log.
310
ANR2380E ANR2388E
ANR2380E

is not defined.
Explanation: A nonexistent storage pool is specified

for the issued command.
command.
storage pool name. If you are using the MACRO
command to define and update the storage pool, you
must ensure that the DEFINE STGPOOL command is
committed before the UPDATE STGPOOL command is
issued. See the Administrator's Guide for more
information on processing commands in a macro.
ANR2381E

is already defined.
Explanation: A DEFINE STGPOOL command specifies

the name of a storage pool that already exists.
command.
ANR2382E

still contains at least one volume.
Explanation: A DELETE STGPOOL command specifies

a storage pool that has volumes assigned to it.
command.
User response: Delete the volume belonging to the
storage pool and reissue the command.
ANR2383E

is currently in use by clients and/or data
management operations.

storage pool that is in use.
command.
ANR2384E
Command: Next or Reclaim storage pool

storage pool name introduces a cycle into
the storage pool chain.
Explanation: A DEFINE STGPOOL or UPDATE

STGPOOL command specifies a next storage pool that
eventually points to the pool being processed.
command.
ANR2385E

is in use as the next or reclaim pool for
one or more other storage pools.

a pool that is the next pool or the reclaim pool for
other storage pools.
command.
User response: If necessary, update other storage
pools so that they do not reference the pool to be
deleted, and reissue the command.
ANR2386E
Command: High migration threshold

must be set greater than or equal to the
low migration threshold.
Explanation: A DEFINE or UPDATE STGPOOL

command has attempted to set the storage pool low
migration threshold (LOWMIG) parameter greater than
the high migration threshold (HIGHMIG).
command.
User response: Reissue the command with a low
migration threshold less than or equal to the high
migration threshold.
ANR2387E

is not a primary pool.

name of a storage pool which is not a primary pool.
The command syntax requires that a primary storage
pool name be specified.
command.
primary storage pool name.
ANR2388E

is not a copy or an active-data pool type
pool.

name of a storage pool which is not a copy pool or an
active-data pool. The command syntax requires that a
copy storage pool name or an active-data pool name be
specified.
command.
copy storage pool name or active-data pool name.

next pool value.
311
ANR2389E ANR2396E
ANR2389E

valid for a primary storage pool.

option that is not valid for a primary storage pool.
command.
appropriate for a primary storage pool.
ANR2393I
Command: Server device configuration

information was written to file name.

the BACKUP DEVCONFIG command and indicates
that device configuration information was successfully
written to the file name indicated.
System action: The server records device
configuration information to the file name specified
ANR2390E

valid for a pool type storage pool.

option that is not valid for either a copy or active-data
type storage pool.
command.
appropriate for the specified storage pool type.
ANR2391E
Command: Server could not write device

configuration information to file name.
Explanation: The BACKUP DEVCONFIG command

does not successfully complete because the server
ANR2394I

that device configuration information was successfully
written to all files that were specified in the server
options file.
System action: The server records device
configuration information to the device configuration
files.
ANR2395I

command.
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
file. On MVS, make sure that the data set has been
allocated and that the server has authority to write to
the data set.
ANR2392E
Command: An internal error was

encountered in writing device
configuration information to file name.

does not successfully complete because the server
command.
User response: Examine error messages on the server
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
file indicated and that sufficient space is available in
the file system for the file. On MVS, make sure that the
data set has been allocated and that the server has
authority to write to the data set.
Command: Server device configuration

information was written to all device
Command: Device configuration files

have NOT been defined for automatic
recording - specify a file name for
device configuration information.

that device configuration information cannot be written
because no files were specified in the options file.
System action: The device configuration information
is not written. Server operation continues.
User response: Reissue the BACKUP DEVCONFIG
command and specify the name of a file to which you
would like to have device configuration information
recorded. If desired, you may configure files that
should be automatically updated with the
DEVCONFIG option and restart the server.
ANR2396E
Command: An I/O error was encountered

in writing device configuration
information to one or more of the
defined device configuration files.

does not complete successfully because the server
cannot write to one or more of the defined device
command.
312
ANR2397E ANR2404E
ANR2397E
Command: An internal server error was

encountered in writing device
configuration information to one or
more of the defined device

cannot write to one or more of the defined device
command.
message and correct any problems, if possible. Contact
your service representative if you are unable to resolve
the problem.
ANR2398E
Command: The device configuration file

contains a statement with invalid
syntax.
Explanation: While processing the device

configuration information, an invalid statement has
been encountered.
System action: The server ends the operation being
performed.
message and correct any problems if you have
constructed the device configuration file manually.
Make sure the statements are in the proper order. If
you let the server construct the device configuration file
automatically, restart the server, refresh the device
configuration file by issuing the BACKUP DEVCONFIG
command, and reissue the operation. If the problem
persists, contact your service representative.
ANR2399E

is not a sequential pool.

name of a storage pool which is not a sequential pool.
All storage pools are either fixed disk or sequential
archival. All tape devices, as well as optical and file
device classes, are sequential.
command.
sequential storage pool name.
ANR2400E
Command: Volume volume name is already

defined in a storage pool or has been
used previously to store export, database
dump, or database backup information.

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
server volume history file.
command.
User response: Specify a volume that is not in use, is
not defined in a storage pool, and which has not been
previously used for an export, a database dump, or
volumes that have been used for export, a database
ANR2401E
Command: Volume volume name is not

defined in a storage pool.

name of a storage pool volume that does not exist.
command.
ANR2402E

online.
Explanation: A VARY ONLINE command specifies the

name of a volume that is already online.
command.
ANR2403E

online.

name of a volume that is not online.
command.
ANR2404E

available.
Explanation: The command indicated has attempted

to access a volume that cannot be found.
313
ANR2405E ANR2412E
command.
User response: Check the spelling of the volume name
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.
ANR2405E
Command: Volume volume name is

currently in use by clients and/or data
management operations.

name of a data storage volume that is currently in use.
command.
User response: Verify that the volume is unavailable
by issuing the QUERY VOLHISTORY command. If the
volume is listed in the command output, then it is
being used and unavailable. Wait until the conflicting
volume activity has completed, and then retry this
operation. If the volume is currently mounted, but idle,
dismount it using the DISMOUNT VOLUME
command, and then retry the operation.
ANR2406E
Command: Volume volume name still

contains data.
ANR2409E
Explanation: A define command for a database or log

volume or copy has specified a volume that is too
small to be used by the server for a database or log
volume. The minimum size for one of these volumes is
5 megabytes.
command.
volume that is at least 5 megabytes in size.
ANR2410E

ANR2407E
Command: Maximum number of

mirrored copies exceeded.
Explanation: A DEFINE LOGCOPY or DEFINE

DBCOPY command has attempted to add a mirror
volume, but the maximum number of mirrors for the
target volume already exists.
command.
ANR2408E
Command: Capacity of volume volume

name must be at least as large as
capacity of volume volume name.
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
than the size of the target volume.

command.
User response: If necessary, reset the status of the
volume and reissue the command.
ANR2411E
Command: Unable to access associated

volume volume name - access mode is set
to "unavailable".
Explanation: The command shown would require

access to the volume whose name is displayed (because
data from the volume specified in the command spans
into this volume); the volume shown cannot be
accessed because its status is unavailable.
command.
ANR2412E
Command: Audit operation already in

progress for volume volume name.
Explanation: The command specified a volume that is

currently in use by an audit volume operation.
System action: If the command is a MOVE
NODEDATA command the server will skip the volume
and continues moving node data on other volumes.
Other commands are not processed.
User response: Reissue the command after the audit
volume operation ends.

command.
User response: Use a larger mirror volume.
314
Command: Unable to access volume

volume name - access mode is set to
"unavailable".

volume whose name is displayed, but the volume
cannot be accessed because its status is unavailable.
Explanation: The indicated command tries to delete a

data storage volume that contains data.
command.
Command: Capacity of volume volume

name must be at least 5 megabytes.
ANR2413E ANR2420E
ANR2413E
Command: Audit operation already in

progress for associated volume volume
name.

accessed because it is in use by an audit volume
operation.
command.
User response: Reissue the command after the audit
ANR2417E

accessed because it is in use by a move data operation.
command.
User response: Reissue the command after the move
data operation ends.
ANR2418E
ANR2414E
Command: Deletion operation already in

progress for volume volume name.

currently in use by a delete volume operation.
User response: Reissue the command after the delete
Command: Deletion operation already in
progress for associated volume volume
name.

accessed because it is in use by a delete volume
operation.
command.
User response: Reissue the command after the delete
ANR2416E
Command: Move Data operation already

in progress for volume volume name.

currently in use by a move data operation.
User response: Reissue the command after the move
data process ends.
Command: Migration operation already

in progress for volume volume name.

currently in use by a migration operation.
User response: Reissue the command after the
migration ends.
ANR2419E
ANR2415E
Command: Move Data operation already

in progress for associated volume volume
name.
Command: Migration operation already

in progress for associated volume volume
name.

accessed because it is in use by a migration operation.
command.
migration ends.
ANR2420E
Command: Space reclamation operation

already in progress for volume volume
name.
Explanation: The command specified a volume is

currently in use by a reclamation operation.
reclamation ends.
315
ANR2421E ANR2430E
ANR2421E
Command: Space reclamation operation

already in progress for associated
volume volume name.

accessed because it is in use by a reclamation operation.

ANR2426I
Backupset backup set name defined for

node node name (data type data type).
Explanation: The backup set has been defined for the

indicated node.
System action: The server has defined the backupset.

command.

reclamation ends.
ANR2427E
ANR2422E
Command: Volume volume name is not a

defined disk volume.
Explanation: The command shown specifies a volume

name that does not match any known disk volume.
command.
volume name.
Explanation: The specified backup set was not deleted

because the device class used to generate it was not
found.
System action: The backup set is not deleted.
User response: If the device class was inadvertently
deleted, redefine it, then delete the backup set again.
ANR2428E
ANR2423E
Command: Volume volume name is still

online.
Explanation: An UPDATE VOLUME command

specifies access=unavailable for a disk volume that is
still online.

name (data type data type) was not
deleted. Device class device class name
was not found.

name (data type data type) has not been
deleted due to error error code.
Explanation: The backup set has not been deleted.

System action: The server has not deleted the
backupset.

command.
User response: Check related error messages.
User response: Issue the VARY OFFLINE command,

and reissue the UPDATE VOLUME command.
ANR2429E
ANR2424E

"destroyed".

cannot be accessed because its status is destroyed.
Command: Maximum database capacity

exceeded.
Explanation: Do not allocate any volume that would

cause the database to exceed 500GB. A subsequent
DEFINE DBVOLUME command for that volume would
fail.
command.

command.

ANR2430E
ANR2425E

"offsite".

cannot be accessed because its status is offsite.
Explanation: A DEFINE DBVOLUME command

specifies the name of a database volume that already
exists.
command.

command.
316

defined as a database volume.
ANR2431E ANR2440E
ANR2431E

defined database volume.
Explanation: A DELETE DBVOLUME command

specifies the name of a database volume that does not
exist.
command.
ANR2432E
Command: Maximum number of

database volumes exceeded.

command.
Command: A database define, delete,
extend, reduce, or backup operation is
already in progress.

command.
User response: Wait for other activity to end, and
reissue the command.
Command: Insufficient space on other
database volumes to delete volume
volume name.

been entered, but the data on the volume to be deleted
cannot be copied to other volumes due to insufficient
free space.
command.
User response: Make more database space available,
and reissue the command.
ANR2435E
Command: Insufficient space to extend

database by requested amount.
Explanation: An EXTEND DB command has been

entered, but not enough allocated, unused space is
available to the database to add the amount of space
requested.
User response: Make more database space available,

ANR2437E
Command: Output error encountered

while attempting to extend database.
Explanation: An EXTEND DB command has been

entered, but an I/O error occurs during the command.
command.

while a command that is modifying or backing up the
database is already active.
ANR2434E
ANR2436E

command.
Explanation: A DEFINE DBVOLUME command has

attempted to add more database volumes than the
server can manage.
ANR2433E
database volumes have been synchronized).
Command: Unable to delete database

volume volume name - mirrored copies
not synchronized.

been entered, but mirrors of the volume to be deleted
are not up to date.
command.
User response: Reissue the command. If the problem

persists, identify and remove or repair the volume that
caused the error.
ANR2438E
Command: Insufficient database space

would be available following a
reduction by the requested amount.
Explanation: A REDUCE DB command has been

entered, but the database does not have enough free
space to reduce by the amount specified.
command.
ANR2439E
Command: Unable to vary database

volume volume name offline - mirrored
copies not synchronized.
Explanation: A VARY OFFLINE command has been

entered, but mirrors of the volume to be varied are not
up to date.
command.
User response: Try the command at a later time (after
database volumes have been synchronized).
ANR2440E
Command: Unable to vary database

volume volume name offline - only copy.

entered, but the database volume has no mirrors and
therefore contains the only copy of the data on that
volume.

317
ANR2441E ANR2449E
command.

command.
User response: Make more recovery log space

available, and reissue the command.
ANR2441E

defined as a recovery log volume.
Explanation: A DEFINE LOGVOLUME command

specifies the name of a recovery log volume that
already exists.
command.
ANR2442E

defined recovery log volume.
Explanation: A DELETE LOGVOLUME command

specifies the name of a recovery log volume that does
not exist.
command.
ANR2443E
Command: Maximum number of recovery

log volumes exceeded.
Explanation: A DEFINE LOGVOLUME command

attempts to add more recovery log volumes than the
server can manage.
command.
ANR2444E
Command: A recovery log define, delete,

extend, or reduce operation is already in
progress.

while a command that is modifying the recovery log is
already active.
ANR2446E

are not up to date.
command.
recovery log volumes have been synchronized).
ANR2447E
ANR2445E
Command: Insufficient space on other

recovery log volumes to delete volume
volume name.

command.
User response: Make more recovery log space
available, and reissue the command.
ANR2448E
Command: Output error encountered

while attempting to extend recovery log.
Explanation: An EXTEND LOG command has been

entered, but an I/O error occurs during the command.
command.
User response: Reissue the command. If the problem
persists, identify and remove or repair the volume that
caused the error.
ANR2449E
Command: Insufficient recovery log space

would be available following a
reduction by the requested amount.
Explanation: A REDUCE LOG command has been

entered, but the recovery log does not have enough free
space to reduce by the amount specified.
command.

been entered, but the data on the volume to be deleted
cannot be copied to other volumes due to insufficient
free space.
318
Command: Insufficient space to extend

recovery log by requested amount.
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.

command.
User response: Wait for other activity to end, and
Command: Unable to delete recovery log

volume volume name - mirrored copies
not synchronized.
ANR2450E ANR2457E
ANR2450E
Command: Unable to vary recovery log

volume volume name offline - mirrored
copies not synchronized.

are not up to date.
command.
recovery log volumes have been synchronized).
ANR2451E
Command: Unable to vary recovery log

volume volume name offline - only copy.

entered, but the recovery log volume has no mirrors
and contains the only copy of the data on that volume.
command.
ANR2454E
Explanation: A REDUCE DB command has been

entered, but the recovery log mode of the server is
currently set to ROLLFORWARD. The database can
only be reduced when log mode is set to NORMAL
with the SET LOGMODE command.
command.
User response: Set the log mode to NORMAL with
the SET LOGMODE command, reissue the REDUCE
DB command, and reset the log mode to
ROLLFORWARD with the SET LOGMODE command.
If you change the log mode to NORMAL, you can only
recover your database to the time of the last complete
database backup.
ANR2455E

ANR2452E
Command: Maximum recovery log

capacity exceeded.
Explanation: Do not allocate any volume that would

cause the recovery log to exceed 13GB. A subsequent
DEFINE LOGVOLUME command for that volume
would fail.
command.
ANR2453E
Explanation: A REDUCE LOG command has been

entered, but the recovery log mode of the server is
currently set to ROLLFORWARD. The recovery log can
only be reduced when the log mode is set to NORMAL
with a SET LOGMODE command.
command.
User response: Set the log mode to NORMAL with
the SET LOGMODE command, reissue the REDUCE
LOG command, and set the log mode back to
ROLLFORWARD with the SET LOGMODE command.
If you change the log mode to NORMAL, you can only
recover your database to the time of the last complete
database backup.

to "destroyed".
Explanation: The specified command would require

accessed because its status is destroyed.
command.
ANR2456E
Command: Unable to reduce recovery log

- log mode must be set to NORMAL.
Command: Unable to reduce database LOGMODE must be set to NORMAL.

to "offsite".

accessed because its status is offsite.
command.
ANR2457E
Command: Backup of primary storage

pool primary pool name to copy storage
pool copy pool name already in progress.
Explanation: The command shown specifies a backup

operation that is already in progress.
command.
User response: Reissue the command after the current
backup operation ends.
319
ANR2458E ANR2465E
ANR2458E
Command: Restore of primary storage

pool primary pool name (or volumes in
that storage pool) already in progress.
Explanation: The command shown cannot be

processed because a restore operation involving the
indicated storage pool is already in progress. Either a
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
indicated storage pool.
command.
User response: Reissue the command after the current
restore operation ends.
ANR2459E
Command: Volume volume name cannot be

updated - a restore operation involving
that volume is in progress.
Explanation: The indicated volume has an access

mode of destroyed. Either a RESTORE STGPOOL
command or a RESTORE VOLUME command is in
progress to restore the contents of the indicated
volume.
command.
User response: If necessary, cancel the restore
processing and update the volume.
ANR2460E
Command: Server could not write

sequential volume history information
to File name.
Explanation: The BACKUP VOLHISTORY command

command.
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
file. On MVS, make sure that the data set has been
allocated and that the server has authority to write to
the data set.
ANR2461E
Command: An internal error was

encountered in writing sequential
volume history information to file name.


ANR2462I

the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
successfully written to the file name indicated.
System action: The server records sequential volume
history information to the file name specified.
ANR2463I
Command: Server sequential volume

history information was written to all
configured history files.

the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
successfully written to all files that were specified in
the server options file.
history information to the configured files.
ANR2464I
Command: Volume history files have

NOT been defined for automatic history
recording - specify a file name for
recording history information.

the BACKUP VOLHISTORY. It indicates that sequential
volume history information cannot automatically be
written because no files were defined in the server
options file for recording this information.
System action: The sequential volume history
information is not written. Server operation continues.
User response: Reissue the BACKUP VOLHISTORY
command and specify the name of a file for recording
sequential volume history information. If desired, you
may configure files that should be automatically
updated with the VOLUMEHISTORY parameter and
restart the server.
ANR2465E

command.
320
Command: Server sequential volume

history information was written to file
name.
Command: An I/O error was encountered

in writing sequential volume history
information to one or more of the
defined volume history files.
ANR2466E ANR2473I
cannot write to one or more of the defined volume
history files.
command.
ANR2466E

encountered in writing sequential
volume history information to one or
more of the defined volume history
files.
ANR2469E
Command: Invalid volume history type:

history type.
Explanation: The command failed because an invalid

sequential volume history type was specified for the
TYPE= parameter.
System action: The command fails, and server
User response: Refer to the Administrators Reference
for an explanation of the valid types for this command.
Reissue the command and specify a valid type value.
ANR2470I
Message output being re-directed to file

file name.
Explanation: The message output is being redirected

to the specified file instead of being displayed at the
console.

cannot write to one or more of the defined volume
history files.
ANR2471E

command.
Explanation: An error occurs while trying to open the

file. The message output will not be redirected to the
specified file.

message and correct any problems, if possible. Contact
your service representative if you are unable to resolve
the problem.
ANR2467I
Command: number of entries deleted

sequential volume history entries were
successfully deleted.
Explanation: The DELETE VOLHISTORY command

successfully deleted the number of entries specified.
ANR2468E
Message output re-direction to file file

name failed - unable to open file.

User response: Determine the cause of the file open
failure and take corrective action.
ANR2472E
Command: Invalid volume specified:

volume name.

sequential history volume specified is not a DB DUMP,
DB BACKUP, or EXPORT volume.
valid volume name.

encountered while deleting server
sequential volume history information.
Explanation: The DELETE VOLHISTORY command

fails because an internal server error has been
encountered.
System action: The DELETE VOLHISTORY command
fails, and server operation continues.
User response: Examine the messages in the activity
log or server console that were displayed prior to the
error to see if the error can be resolved. Contact your
service representative if this error cannot be resolved.
ANR2473I
Command for volume volume name

completed.
Explanation: The command completed and the

volume history file has been updated.
history information.
321
ANR2474E ANR2482E
ANR2474E
Command: Input volume names must be

specified with the VOLumenames=
parameter.
Explanation: The command failed because input

volume names were not specified with the
VOLumenames parameter.
User response: On some platforms, or with certain
device classes, the server cannot prompt to mount
input removable media volumes, so the names of the
required volumes must be specified in the command.
Reissue the command specifying the name(s) of
volumes that should be mounted for input.
ANR2475E
Command: File file name could not be

opened.
Explanation: The DSMSERV command could not be

completed successfully because the file specified (to
contain the list of volumes to be used) cannot be
opened.
ANR2478E
Command: Command cannot be executed

in this session.
Explanation: The command indicated is not supported

by the session in which it was invoked. For example, a
DEFINE CURSOR command can not be invoked from
the server's primary console.
command.
User response: The command must be issued from a
standard administrator session.
ANR2479E
Command: Invalid SQL cursor name SQL cursor name.

invalid SQL cursor name.
command.
SQL cursor name.
System action: The DSMSERV command fails.

User response: Examine the file name that was
specified in the DSMSERV command. Correct the
specification, if necessary, so that it specifies the name
of a file that exists and is accessible by the server
program. Reissue the DSMSERV command if this can
be corrected. Contact your service representative if this
error cannot be resolved.
ANR2476I
License storage auditing is disabled, no

output available.
ANR2480E
Command: SQL cursor name SQL cursor

name is already defined.
Explanation: The command indicated specifies an SQL

cursor name that has already been defined.
command.
different cursor name.
Command: SQL cursor name SQL cursor
Explanation: The license storage occupancy function is

currently disabled.
ANR2481E
Explanation: The command indicated specifies an SQL

cursor name that has not been defined.
User response: To obtain storage occupancy results,

remove the NOAUDITSTORAGE or AUDITSTORAGE
NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command.

command.
ANR2477I
License storage auditing is disabled,

storage values may be outdated and
should be ignored.
User response: Use the DEFINE CURSOR command

to first define the cursor.
ANR2482E
Command: SQL cursor SQL cursor name is

already open.
Explanation: The license storage occupancy function is

currently disabled.
Explanation: The command indicated failed because

an SQL cursor is already open.

command.
User response: To obtain storage occupancy results,

remove the NOAUDITSTORAGE or AUDITSTORAGE
NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command.
322
User response: Use the CLOSE CURSOR command to

first close the current cursor.
ANR2483E ANR2491I
ANR2483E
Command: No SQL cursor is currently

open.

no SQL cursor is currently open.
command.
User response: Use the OPEN CURSOR command to
first open a cursor.
ANR2484E
Command: Invalid SQL date-time display

format - SQL date-time display format
name.

invalid SQL date-time display format name.
command.
SQL date-time format name.
ANR2485E
Command: Invalid SQL display format SQL display format name.

invalid SQL display format name.
command.
SQL display format name.
ANR2486E
Command: Invalid SQL character

arithmetic mode - SQL arithmetic mode.

invalid SQL arithmetic mode name.
ANR2488W
List file list file name could not be

opened.
Explanation: While attempting to read or write a

sequential file list, the server was unable to open the
file name specified.
System action: The server does not use the list file.
problems, if possible. For OUTFILE files, make sure
that the server has proper authority to write to the file
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.
ANR2489W
An error was encountered writing to

volume list file volume list file name.
Explanation: While attempting to write to the

sequential file for a volume list an error occurs on the
file name specified. The volume list is not be complete
and should not be used for input.
System action: The server stops writing to the file.
On MVS, make sure that the server has authority to
write to the data set. Obtain the volume list from
console messages, the QUERY VOLHISTORY command
or the volume history file, if it is used.
ANR2490E
Command: NODENAMES and

SERVERNAMES parameters cannot
both be specified in the same command.

command.

both the nodenames parameter and the servernames
parameter were specified.

SQL arithmetic mode name.
ANR2487E
Command: An SQL expression is

required.
Explanation: The command indicated requires that an

SQL expression be provided through the SQL keyword
parameter.
command.
User response: Reissue the command specifying an
SQL expression.
User response: Determine whether you want the

action taken for one or more nodes or for one or more
servers and reenter the command with only the correct
parameter specified.
ANR2491I
Volume Creation Process starting for

volume name, Process Id process ID.
Explanation: As a result of a DEFINE VOLUME,

DEFINE DBVOLUME, or DEFINE LOGVOLUME
command with the SIZE=xxx parameter, a new volume
is being created. The process whose ID is displayed has
begun to create the volume shown.
System action: The server creates the volume and
adds it to the server.
323
ANR2500I ANR2508E
ANR2500I
Schedule schedule name defined in policy

domain domain name.

the DEFINE SCHEDULE command. The schedule
named schedule name has been defined in the policy
domain named domain name in the server database.
ANR2501I
Schedule schedule name deleted from


the DELETE SCHEDULE command. The schedule
named schedule name has been deleted from the policy
ANR2505I
number of schedules schedules were

defined for command.
Explanation: number of schedules were generated and

nodes successfully associated for the command issued.
User response: If the number is less than expected,
check the nodeList and domainList combination specified
to the DEFINE CLIENTACTION command. Schedules
are generated when at least one node in the nodeList
exists in a domain in the domainList.
ANR2506I
Node node name associated with

schedule schedule name in policy domain
domain name processed. rc=return code.

the DEFINE CLIENTACTION WAIT=YES command.
Node node name is associated with the schedule named
schedule name in policy domain domain name has been
processed. name The result is indicated in the return
code return code.
ANR2502I
Schedule schedule name updated in


the UPDATE SCHEDULE command. The schedule
named schedule name has been updated in the policy
User response: If the return code is non-zero, issue the

QUERY ACTLOG command to to view the activity log
and search for the error messages. After the error has
been resolved, restart the scheduled operations.
ANR2507I

ANR2503I
Schedule schedule name in domain domain

name copied to schedule new schedule
name in domain new domain name.

the COPY SCHEDULE command. The schedule named
schedule name in policy domain domain name has been
copied to the schedule named new schedule name in the
policy domain named new domain name. Node
associations have not been copied.
ANR2504I
Schedule schedule name deleted.

the DELETE SCHEDULE command. The schedule
named schedule name has been deleted from the server
database.
Explanation: The scheduled operation for the domain

name and schedule name specified was processed. It was
processed for node node name and completed
successfully at the indicated time.
User response: This message is intended to report the
completion state of a scheduled client action. This
message indicates that the scheduled action completed
successfully.
ANR2508E
Trace Tsmtrcfm failed: A tracefile name

is required.
Explanation: Trace Tsmtrcfm doesn't output to console

System action: Trace won't start without a tracefile
name for Trace Tsmtrcfm
User response: Issue the command with a tracefile
name.

324
Schedule schedule name for domain

domain name started at start timestamp for
node node name completed successfully
at timestamp.
ANR2509E ANR2518E
ANR2509E
Command: Invalid Virtual file space

name - vfs name.

entered with a virtual file space name that is longer
than allowed.
command.
virtual file space name.
ANR2510I
Node node name associated with

domain name.

the DEFINE ASSOCIATION command. Node node name
is associated with the schedule named schedule name in
policy domain domain name. Schedule schedule name is
now applied to node node name.
ANR2514E
Command: Virtual file space name vfs

name conflicts with file space on the
network attached storage (NAS) device.

entered with a virtual file space that has the same
name as a File space on the NAS device.
command.
User response: Ensure that no virtual file space
mappings for this NAS device have the same name as
an actual file space that exists on the NAS device.
ANR2515I
Command: A virtual file space mapping

named vfs name for node node name has
been defined.

VIRTUALFSMAPPING command, a virtual file space
mapping for the specified node has been defined in the
server database.

ANR2511I
Node node name disassociated from

domain name.
ANR2516E
Command: The specified file space, fs

name, does not exist on the NAS device
associated with the node node name.

the DELETE ASSOCIATION command. Node node name
is no longer associated with the schedule named

entered with a file space that does not exist on the
associate NAS device.
User response: Reissue the command with a valid file

space name from the NAS device.
ANR2512I
Event records deleted: record count.

the DELETE EVENT command. A total of record count
event records have been deleted from the database.
ANR2513I
Command: The virtual file space vfs name

is already defined for node node name.

with a virtual file space name that has already been
defined for the indicated node.
Schedule schedule name copied to

schedule new schedule name.

the COPY SCHEDULE command. The schedule named
schedule name has been copied to the schedule named
new schedule name.
ANR2517E
User response: Issue the command using a virtual file

space name that has not already been defined for this
node.
ANR2518E

already exists to the specified node, file
space and path.

with a node, file space and path for which there is
already a virtual file space mapping defined.
325
ANR2519E ANR2529I
User response: Issue the command using a file space
and path that does not already have a mapping
defined.
ANR2519E
Command: The file space, fs name, does

not exist on the NAS device associated
with the node node name.
Explanation: During a Backup of a virtual file space

mapping for a NAS device, the server detected that the
file space upon which the virtual file space resides does
not exist on the associated NAS device.
User response: Use QUERY VIRTUALFSMAPPING to
verify that the virtual file space mapping is defined
correctly.
ANR2524I
Schedule query period reset to value

determined by each client.

the SET QUERYSCHEDPERIOD command.
ANR2525I
Maximum number of command retries

set to retries.

the SET MAXCMDRETRIES command. It indicates the
maximum number of times the client scheduler retries
a command after a failed attempt to process a
scheduled command.
ANR2520I
Scheduled sessions set to percent

percent.

the SET MAXSCHEDSESSIONS command. It indicates
the percentage of total server sessions that can be used
for the processing of scheduled work.

ANR2526I
Maximum number of command retries

reset to value determined by each client.

the SET MAXCMDRETRIES command.
ANR2521I
Event record retention period set to days

days.

the SET EVENTRETENTION command. It indicates the
number of days for which event records are retained in
the database.
ANR2527I
Retry period set to minutes minutes.

the SET RETRYPERIOD command. It indicates the
number of minutes between attempts by the client
scheduler to retry, after a failed attempt, to contact the
server or to process a scheduled command.
ANR2522I
Randomization set to percent percent.

the SET RANDOMIZE command. It indicates the
percentage of the startup window over which the start
times for individual clients are distributed.
ANR2528I
Retry period reset to value determined

by each client.

the SET RETRYPERIOD command.
ANR2523I
Schedule query period set to hours

hour(s).

the SET QUERYSCHEDPERIOD command. It indicates
the number of hours between attempts by the client to
contact the server for scheduled commands.
326
ANR2529I
Scheduling mode set to POLLING.

the SET SCHEDMODES command. With client-polling
scheduling, a client queries the server at prescribed
time intervals to obtain scheduled work or to ensure
that the schedules the client is waiting to process have
not changed.
ANR2530I ANR2539E
ANR2530I
ANR2535E
Scheduling mode set to PROMPTED.

the SET SCHEDMODES command. With
server-prompted scheduling, the server contacts the
client when scheduled work needs to be performed and
a session is available.
Command: The node node name cannot be

removed or renamed because it has an
associated data mover.
Explanation: You attempted to remove or rename a

node that has an associated data mover.
System action: The server does not remove or rename
the node.
User response: To remove or rename the node, delete
the associated data mover and reissue the command.

ANR2536E
ANR2531I
Scheduling mode set to ANY.

valid with the storage pool's data
format.

the SET SCHEDMODES command. The server now
allows clients to run in either the client-polling or the
server-prompted scheduling mode.
Explanation: The command indicated includes an

option that is not valid with the specified (or defaulted)
data format for the storage pool.

command.

ANR2532I
Schedule schedule name updated.

the UPDATE SCHEDULE command. The schedule
named schedule name has been updated in the server
database.

appropriate for the desired data format of the storage
pool.
ANR2537E

has a device type that is not allowed for
this operation.
Explanation: The device class in the indicated

command has a device type that is not allowed for this
operation.
ANR2533I

command.
Client action schedule duration set to

days days.

the Set CLIENTACTDuration command. It indicates the
number of days for which schedules and associations
generated by the DEFine CLIENTAction are retained in
the database.
User response: Choose a different device class and

Explanation: Backup sets cannot be generated for

NAS nodes.
ANR2538E
Command: Backup set cannot be

generated for NAS node node name.

ANR2534I
Client action schedule schedule name was

not executed by node name in domain
name.
Explanation: Immediate client action schedule name

was not executed by node node name, which is in
domain domain name. The schedule is being deleted.

ANR2539E
Command: Storage pool Storage Pool Name

does not have a valid data format.
Explanation: The data format of the indicated storage

pool is not valid for the requested operation. The
storage pool must have NATIVE or NONBLOCK data
format. The server is unable to perform the requested
operation.
User response: Choose a different storage pool with
the appropriate data format and reissue the command.
327
ANR2540E ANR2548I
ANR2540E
Command: The "option" device class is not

valid with the storage pool's data
format.
Explanation: The command indicated specifies a

device class that is not valid with the specified (or
defaulted) data format for the storage pool.
command.
User response: Reissue the command with a data class
appropriate for the desired data format of the storage
pool.
ANR2541E
Command: The storage pool specified

with option "option" is not compatible
with the option's intended use.
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
operations such as reclaim or attributes such as copy,
active-data, or reclaim storage pools.
ANR2544E
Explanation: The server cannot start communication

with the device at the specified HLA.
System action: The transaction needing this device
fails.
User response: Verify that the hla specified in the
device class is correct, verify that the centera device is
operational.
ANR2545E
ANR2542E
Command: The storage pool is not

compatible with the operation's
intended use.
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
operations, such as reclaim, or attributes, such as copy
or reclaim storage pools.
command.
User response: Issue the command again with a
storage pool appropriate for the desired function.
ANR2543E
Command: The volume name is not

compatible with the operation's
intended use.
Explanation: The command specifies a volume that

resides in a storage pool whose device class is a
Centera device. Such volumes are not available for use
with data movement operations, such as reclaim, or
attributes, such as copy or reclaim storage pools.
command.
volume appropriate for the desired function.
328
The version of the centera library,

version, is not compatible with the
server.
Explanation: The centera library must be at least

version 2 to be able to be compatible with the server.
System action: The transaction fails.
ANR2546E

command.
storage pool appropriate for the desired function.
Unable to open the centera device at hla

hla.
The centera device is not capable of

performing the required operation,
version.
Explanation: The centera device must be capable of

reading, writing and deleting objects. The device is not
capable of performing at least one of these operations.
System action: The transaction fails.
ANR2547E
A Centera device (devclass) reported error

"message,error" during command Centera
command.
Explanation: The Centera device reported an error

while performing the specified command.
User response: Verify that the IP addresses specified
in the device class associated with the storage pool are
correct. Contact your service representative if the
problem persists.
ANR2548I
NAS command: Renaming file space

filespace name for node node name to file
space new filespace name.
Explanation: The NAS Backup process detected a

name conflict between the Virtual file space filespace
name and a file space on the NAS device associated
with the node node name. The Virtual file space is
renamed to the new filespace name. During a NAS
backup process, if the object to be backed up is a
Virtual file space, TSM will verify that this name does
not also exist as a file space on the NAS device. If a
name conflict exists, TSM will rename the existing
ANR2549E ANR2556W
Virtual file space and the associated file space
definition, if one exists.
command with the ACTIVE=YES parameter to activate

the schedule when the server is restarted.
System action: NAS Backup processing for the

command continues.
ANR2552I
User response: None; however, users should make

note of the original Virtual file space filespace name and
the new new filespace name so that they know where the
backup data for this Virtual file space is located. Note,
the RENAME FILESPACE command may be used to
rename the Virtual file space to a more appropriate
name.
ANR2549E
Command: Invalid virtual file space

name. A virtual file space mapping
name must have a forward slash as the
first character.

entered with a virtual file space name that is does not
have a forward slash as the first character.
Server now enabled for session type

access.
Explanation: The server has been made available for

use by the specified session types with the ENABLE
command.
ANR2553I
Server now disabled for session type

access.
Explanation: The server has been made unavailable

for use by the specified session types with the
DISABLE command.

command.

virtual file space name.
ANR2554I
ANR2550W
command name: Administrative schedule

schedule name does not have valid
activation information.
Explanation: This message is displayed during a

database audit and indicates that the 'ACTIVE=YES or
NO' information is not recorded correctly for an
administrative schedule in the server database.
System action: Server database audit operation
continues.
User response: Execute the AUDITDB operation
specifying FIX=YES so that the activation information
can be corrected.
ANR2551I
command name: Administrative schedule

schedule name does not have valid
activation information - activation
information will be deleted.

database audit and indicates that the 'ACTIVE=YES or
NO' information is not recorded correctly for an
administrative schedule in the server database. The
audit operation corrects this discrepancy by removing
the invalid activation information.
continues.
User response: The named administrative schedule
will now appear to be inactive in the server database
(as if ACTIVE=NO was specified). If you want this
schedule to be active, execute the UPDATE SCHEDULE
Format lfvolume process process id ended

for storage pool pool name, number of
volumes requested volumes requested,
number of volumes formatted volumes
formatted.
Explanation: The FORMAT LFVOLUME process for

the storage pool shown has ended. The number of
volumes requested to be formatted, and the number of
volumes actually formatted are displayed.
User response: If the number of volumes formatted is
less than the number of volumes requested to be
formatted, check the activity log for messages
indicating the reason for the difference. Possible
reasons include the process was canceled, no more
scratch volumes are allowed in the storage pool, or an
error occurred processing a scratch volume.
ANR2556W
The managed server server name is not

capable of using enhanced style client
name. The domain will not be
propagated to this server.
Explanation: The managed server server name is

subscribed to domain domain name that contains client
schedule schedule name that uses enhanced style syntax.
The managed server is not 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.
domain will not be propagated to the managed server.
User response: Consider upgrading the managed
329
ANR2557W ANR2565I
server to at least TSM Version 5 Release 3.
ANR2557W
The managed server server name is not

capable of using the enhanced style
administrative schedule schedule name.
The administrative schedule will not be
propagated to this server.
Explanation: The managed server server name is

subscribed to an administrative schedule that uses
enhanced style syntax. The managed server is not
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.
administrative schedule will not be propagated to the
managed server.
User response: Consider upgrading the managed
server to at least TSM Version 5 Release 3.
ANR2560I
Explanation: The schedule manager is started when

the server is initialized. The schedule manager
maintains entries of scheduled operations.
ANR2561I
command: One or more managed servers

that subscribe to domain domain name
which contains client schedule schedule
name are not capable of using an
enhanced style schedule.
Explanation: The client schedule schedule name uses

enhanced style schedule syntax. The schedule is in a
domain which is a managed object and one or more of
the managed servers that subscribe to it are not 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. During configuration refresh
processing, the domain will not be propagated to
managed servers that are not capable of using it.
User response: Consider upgrading managed servers
to at least TSM Version 5 Release 3.
ANR2559W
command: One or more managed servers

that subscribe to administrative
schedule schedule name are not capable of
using an enhanced style schedule.
Explanation: The administrative schedule schedule

name uses enhanced style schedule syntax. The
schedule is a managed object and one or more of the
managed servers that subscribe to it are not 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. During configuration refresh
processing, The schedule will not be propagated to
managed servers that are not capable of using it.
User response: Consider upgrading managed servers
to at least TSM Version 5 Release 3.
330
Schedule prompter contacting node name

(session session number) to start a
scheduled operation.
Explanation: The schedule prompter contacts the

client scheduler for node node name because a
scheduled operation should be started for that node.
ANR2562I
ANR2558W
Schedule manager started.
Automatic event record deletion started.
Explanation: A process has been started to delete

event records for which the retention period has
elapsed.
ANR2563I
Removing event records dated prior to

date time.
Explanation: Events that were scheduled to start prior

to date time are automatically deleted unless their
startup window has not yet elapsed.
ANR2564I
Automatic event record deletion ended record count records deleted.
Explanation: The event deletion process has ended. A

total of record count event records have been deleted
from the database.
ANR2565I
schedules schedules for immediate client

actions have been deleted.
Explanation: A total of schedules that were generated

by the DEFINE CLIENTACTION command have
expired and been deleted from the database.
ANR2566E ANR2572W
ANR2566E
An error occurred while deleting

immediate client action schedules.
Explanation: Processing did not complete for deleting

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
memory or space problems.
ANR2567W
Schedule prompter skipped contact

attempt with node name to start a
scheduled operation.
Explanation: The schedule prompter skipped the

contact attempt with the client scheduler for node node
name because the start-up window has passed for that
node, or the node was locked.
User response: Check the length of the schedule
start-up window to see if it needs to be increased.
Check the activity log for ANR2716E messages. These
messages are associated with failures to contact a client
scheduler. If there are an excessive number of these
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.
The contact attempt would be skipped for a locked
node.
ANR2568E
Request for node node to start schedule

schedule at startTime is denied. Current
time is now.
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
future.
System action: Server operation continues. The node
does not start the schedule.
User response: Check the client schedule and error
logs for problems with the network or the preschedule
command. Also, you may need to upgrade the client.
ANR2569E
Request by node node to report results

(result, code code) for schedule schedule at
startTime is denied. Current time is now.
Explanation: The client scheduler attempted to report

the results of executing the specified schedule.
However, the schedule occurs in the future. The results
will not be saved.
System action: Server operation continues. The results
will not be saved.
User response: Check the client schedule and error
logs for problems with the network or the preschedule

command. Also, you may need to upgrade the client.
ANR2570W
A scheduled session has been denied.

The schedule manager is not active.
Explanation: The client scheduler attempts to connect

with the server, but it is denied a session because the
schedule manager is not active.
System action: Server operation continues, but central
scheduling is not operational.
User response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
been specified in the server options file. If so,
scheduling can be enabled by updating the server
options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied
in the server options file, determine the source of the
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
central scheduler operations. If the error cannot be
isolated and resolved, contact your service
representative.
ANR2571W
Scheduled session from node node name

(platform name) has been denied,
scheduled sessions are not currently
available.
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
scheduled operations are already in use.
User response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
been specified in the server options file. If so,
scheduling can be enabled by updating the server
options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied
in the server options file, change the total number of
sessions by altering the MAXSESSIONS parameter in
the server options file and then restarting the server.
The percentage of sessions that are available for
scheduled operations can be increased by using the SET
MAXSCHEDSESSIONS command.
ANR2572W
Schedule prompter session to node node

name has been denied, scheduled
sessions are not currently available.
Explanation: The server attempts to prompt the client

scheduler for node node name, but all sessions that have
been allocated for scheduled operations are already in
use.
System action: The server continues to attempt
contact with the client scheduler until the startup
331
ANR2573W ANR2579E
window for the scheduled event has elapsed.
User response: To change the total number of
sessions, alter the MAXSESSIONS parameter in the
server options file and then restart the server. The
percentage of sessions that are available for scheduled
operations can be increased by using the SET
MAXSCHEDSESSIONS command.
ANR2573W
Sufficient memory is not available for

the central scheduler - will retry in
ANR2576W
An attempt was made to update an

event record for a scheduled operation
which has already been executed for
node node name.
Explanation: The server cannot update the event

record for the specified client node. The existing record
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
client has retried the operation after an error has
occurred.
Explanation: The server suspends central scheduler

processing because sufficient server memory is not
available.

existing event record is not modified. No further
processing is performed for this scheduled operation.

scheduler operation will be retried after the specified
delay.
User response: Contact the user for this client node,

and make sure that only one client scheduler is
running.

application.
ANR2577I
ANR2574W
Insufficient recovery log space available

for the central scheduler - will retry in

processing because sufficient recovery log space is not
available.
delay.
command, and can extend the size of the log by using
ANR2575W
Insufficient database space available for

the central scheduler - will retry in

processing because sufficient database space is not
available.
delay.
DEFINE DBVOLUME command, and can extend the
size of the database by using the EXTEND DB
command.
332
Schedule schedule name defined.

the DEFINE SCHEDULE command. The schedule
named schedule name in the server database.
ANR2578W

name for node node name has missed its
scheduled start up window.

scheduled startup window for this schedule has passed
and the schedule has not begun.
scheduled operation is not processed by the server.
User response: Ensure that a scheduled session for
node node name has been initiated from the client to the
server. Refer to Administrators Guide and Administrators
Reference for more information on setting up scheduling
operations.
ANR2579E

name for node node name failed (return
code return code).
Explanation: This message is displayed when a client

reports failure in executing a scheduled action. The
return code reported by the client is displayed.
User response: Examine the node's schedule log to
determine the cause for the failure.
ANR2580E ANR2586W
ANR2580E

name for node node name failed.

server finds that a scheduled start window has elapsed
for a client schedule and the client is not currently
running the schedule.
User response: Examine the node's schedule log to
determine the cause for the failure. Ensure that the
client scheduler is started.
ANR2581W
Schedule schedule name of an

administrative command has missed its
scheduled start up window.

scheduled startup window for this schedule has passed
and the schedule has not begun.
scheduled operation is not processed by the server.
User response: Ensure that the duration and period
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
up scheduling operations.
ANR2582E
Command: Specified device class cannot

be used with storage pools with
different reclamation types.
Explanation: Storage pools can be defined with

RECLAMATIONTYPE=THRESHOLD or
RECLAMATIONTYPE=SNAPLOCK. A device class can
only be used with either
RECLAMATIONTYPE=SNAPLOCK storage pools. An
attempt was made to define a storage pool with one
type of reclamation type with a device class that is
already associated with another storage pool of the
other reclamation type.
another device class that is referenced by storage pools
with the same reclamation type as your new storage
pool. You may need to define another device class.
ANR2583E

is not a LAN-free storage pool.

name of a storage pool which is not a LAN-free pool.
The command syntax requires that a LAN-free storage
poolname be specified.
command.

LAN-free storage pool name.
ANR2584E
Command: An email address exceeds

Explanation: A REGISTER NODE or REGISTER

ADMIN command has been entered that specifies a list
of email addresses, and one of those addresses is too
long. The maximum valid length for a single email
address is shown in the command.
command.
User response: Reissue the command with a shorter
email address.
ANR2585E
Command: An email address contains

invalid syntax.
Explanation: A REGISTER NODE, REGISTER

ADMIN, UPDATE NODE, or UPDATE ADMIN
email addresses. Email addresses must be in the format
"name@domain", where the name must be between 1
and 64 characters long, and the domain must be
between 1 and 255 characters long.
command.
User response: Reissue the command with a correct
email address.
ANR2586W
Setting the server name to serverName

can adversely affect or stop operations
that depend on communcations such as
for the following purposes:
administration from the Administration
Center, client operations from
backup-archive clients, library sharing
with the library manager or library
clients, or other server to server
operations such as virtual volumes,
event logging, or enterprise
configuration.See the administrator's
guide for more information about these
components and the impact of changing
the server name.
Explanation: The name that the server displays and

communicates with has been set to the value indicated
with the SET SERVERNAME command.
Communication with the Tivoli Storage Manager server
is based on the name assigned to the server. If this is a
source server for a virtual volume operation, changing
this value can impact the ability of the source server to
access and manage the data it has stored on the
corresponding target server. Windows clients use the
server name to identify which passwords belong to
which servers. Changing the server name after the
clients are connected forces the clients to re-enter the
333
ANR2587W ANR2595I
passwords. On a network where clients connect to
multiple servers, it is recommended that all of the
servers have unique names.
System action: Tivoli Storage Manager prompts the
user to continue.
User response: Enter 'Y' to change the server name.
Enter 'N' if you do not want to change the server name.
ANR2587W
TSM encountered a zero verb on

backupset volume Volume and skipped
to the next volume.
Explanation: TSM detected the problem described in

APAR PK12572. The server options file contains
SKIPONZEROVERBBACKUPSET ON. TSM verified
there was no further data on the volume, and skipped
to the next volume.
ANR2590E
Command failed - SET DBRECOVERY

command has not been issued.
Explanation: Backup DB command failed because a

SET DBRECOVERY command has not been issued to
define the device class used for automatic DB backup.
command.
command to define the device class for automatic DB
backup operation.
ANR2591I
Directory directory name is already

defined in the database space.
Explanation: This directory is already in the database

space .
User response: If the backupset volume was written

before TSM 5.2.7, or 5.3.3 was put on the system and
meets the PK12572 criteria, no action is required. If not,
the volume has encountered a read error, and should
read again on a server without the
SKIPONZEROVERBBACKUPSET ON option to get the
correct error messages for problem determination.

directory that is not defined in the server database
space.
ANR2588E
Command: Storage pool "StgPool" cannot

have CACHE set to YES with a non zero
SHRED attribute.
Explanation: Storage pools can be defined or updated

with a non zero SHRED attribute only if the storage
pool CACHE attribute is NO. Existing storage pools
with CACHE attribute of YES cannot be updated with
a non zero SHRED attribute. Likewise, existing storage
pools with a non zero SHRED attribute cannot be
updated with CACHE = YES. Existing storage pools
with CACHE set to YES cannot be updated with a non
zero SHRED attribute. New storage pools cannot be
define nor can existing storage pools be modified with
CACHE set to YES and a non zero SHRED value.
ANR2592I
Directory(ies) directory list has been

defined in the database space.
Explanation: Command 'EXTEND DBSPACE'

successfully added new directory(ies) dir list into the
server database space.
System action:
User response:
ANR2593E

exists but does not match the
storage-pool type that the server is
attempting to process with the
command.
Explanation: The storage pool specified does not

match the type being processed with the command.

command.

SHRED value of zero or CACHE = NO.
User response: Retry the command with a valid

storage pool type specified.
ANR2589E

name (data type data type) is in use and
cannot be deleted.
Explanation: The server attempted to delete the

backup set, but the operation could not be completed,
because the backup set was in use by another process.
command.
334
ANR2595I
Directory directory name is already in the

list to add to database space.
Explanation: While processing the command

argument list, a duplicate path name has been
encountered.
directory that is not in the argument list.
ANR2596E ANR2603E
ANR2596E
There is insufficient authority to create

the database files.
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
more of the database directories.
User response: Ensure that the user ID for the Tivoli
Storage Manager instance has write permission to all
database directories. No matter which user ID is
running the dsmserv process, the database files are
written by the database manager. The permissions on
these database directories must allow write access from
the database manager user ID. Change the ownership
of the database directories to the user ID for the Tivoli
Storage Manager instance.
ANR2597W
Node node name in domain domain name

began schedule schedule name at actual
start and is schedule state. The period
expired at expiration time.
Explanation: This message is displayed when a node

started a schedule, the period for the schedule expired,
and the node has not reported results for the schedule.
Possible causes are:
v processing for the action is taking longer than the
schedule period
v a problem occurred while the node was performing
the scheduled action
v the node completed the scheduled action but did not
report the results to the server
of the scheduled operation are unknown.
User response: Administrators should consult the
server activity log and the client scheduler log, then
take corrective action if needed.
ANR2598W
Administrative command schedule

schedule name started processing at actual
start and is schedule state. The period
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
schedule have not been reported. Possible causes are:
v processing for the action is taking longer than the
scheduled period
v a problem occurred while performing the scheduled
action
v a problem occurred reporting the schedule results
of the scheduled operation are unknown.
User response: Administrators should consult the
server activity log, then take corrective action if needed.

ANR2599W
The central scheduler is unable to

obtain a required lock and will retry in
Explanation: The server temporarily suspends central

scheduler processing because a required lock is not
available.
delay.
User response: The server workload is high. If this
condition persists, you may need to consider adjusting
the server workload.
ANR2600E
Command: Invalid schedule name schedule name.

with an invalid schedule name.
schedule name.
ANR2601E
Command: Schedule description exceeds

maximum length characters.

with a description that exceeds the maximum length.
description.
ANR2602E
Command: Invalid action - action.

with an invalid action.
action.
ANR2603E
Command: Options string exceeds


with an options string that exceeds the maximum
length.
options string.
335
ANR2604E ANR2614E
ANR2604E
Command: Objects string exceeds


with an objects string that exceeds the maximum
length.
objects string.
ANR2605E

priority.
Command: Invalid start date - date.

with an invalid start date.
start date.
ANR2607E
Command: Invalid start time - time.

with an invalid start time.
start time.
ANR2608E
ANR2610E
Command: Invalid period - period.

with an invalid period.
period.
Command: Invalid priority - priority.

with an invalid priority.
ANR2606E

value for duration units.
Command: Invalid duration - duration.

with an invalid duration.
ANR2611E
Command: Invalid period units - period

units.

with an invalid value for period units.
value for period units.
ANR2612E
Command: Invalid day of week - day of

week.

with an invalid value for day of the week.
value for day of the week.
ANR2613E
Command: Invalid expiration - date.

with an invalid expiration date.
expiration date.
ANR2614E

Command: Invalid combination of the

following parameters: duration, duration
units, period, period units.

with an invalid value for duration units.

with an invalid combination of the DURATION,
DURUNITS, PERIOD, and PERUNITS parameters. This
message may be displayed if the duration of the
startup window for the schedule is not shorter than the
period between windows. This message may also be
displayed if DURUNITS=INDefinite is specified, but
PERUNITS=Onetime is not specified.



duration.
ANR2609E
336
Command: Invalid duration units duration units.
ANR2615E ANR2624E
ANR2615E
Command: Expiration date date has

elapsed.

with an elapsed expiration date date.
User response: Issue the command and specify an
expiration date that has not already elapsed.
ANR2616E
Command: Start date start date must be

earlier than expiration date expiration.
User response: Issue the command and specify a new

period.
ANR2620E
Command: Currently defined duration

duration is invalid with updated
duration units.

with a value for duration units that is not allowed with
the existing duration.
User response: Issue the command and specify a new
duration.
ANR2621E
Command: No matching schedules.

with a start date that is not earlier than the expiration
date.

but no matching schedules have been found.


User response: Issue the command using a schedule

start date that is earlier than the expiration date.

different schedules.
ANR2617E
Command: Schedule schedule name is not


with a schedule name that has not been defined in the
indicated policy domain.
that has already been defined for this domain.
ANR2622E

but no new node associations are defined.
command has no effect.
different nodes.
ANR2623E
ANR2618E
Command: Schedule schedule name is

already defined in policy domain domain
name.

with a schedule name that has already been defined for
the indicated policy domain.
that has not already been defined for this domain.
ANR2619E
Command: Currently defined period

period is invalid with updated period
units.

with a value for period units that is not allowed with
the existing period.
Command: No new node associations

added.
Command: No node associations deleted.

but no node associations are deleted.
different nodes.
ANR2624E
Command: No matching nodes registered.
Explanation: No matching nodes are found for the

specified command.
different nodes.

337
ANR2625E ANR2635E
ANR2625E
Command: No matching nodes registered

in policy domain domain name.
Explanation: The specified command has been issued,

but no matching nodes are registered in the indicated
policy domain.
different nodes.
ANR2626E
Command: Invalid value for replace replace.
User response: Wait for event deletion to complete

before issuing the command.
ANR2631E
Command: Invalid begin date - date.

with an invalid begin date.
User response: Issue the command with a valid begin
date.
ANR2632E
Command: Invalid begin time - date.

with an invalid value for replace.

with an invalid begin time.


User response: Issue the command using a valid value

for replace.
User response: Issue the command with a valid begin

time.
ANR2627E
Command: Invalid value for format format.

with an invalid value for format.
User response: Issue the command using a valid value
for format.
ANR2633E

with an invalid end date.
User response: Issue the command with a valid end
date.
ANR2634E
ANR2628E
Command: Invalid date - date.

with an invalid date.
User response: Issue the command with a valid date.
ANR2629E
Command: Invalid time - time.

with an invalid time.
User response: Issue the command with a valid time.
ANR2630E
Command: Event deletion is already in

process.

while event deletion is already in progress.
Command: Invalid end time - time.

with an invalid end time.
User response: Issue the command with a valid end
time.
ANR2635E
Command: Invalid time range - Begin:

begin End: end.

with an invalid time range. This occurs if the date and
time for the beginning of the time range (begin) do not
precede the date and time for the end of the time range
(end).
User response: Issue the command with a valid time
range.

338
Command: Invalid end date - date.
ANR2636E ANR2645E
ANR2636E
Command: Invalid value for exceptions

only - exceptions only.

with an invalid value for exceptions only.
User response: Issue the command with a valid value
for exceptions only.
ANR2637E
There is insufficient authority to create

the recovery log files.
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
more of the log directories.
User response: Ensure that the user ID for the Tivoli
Storage Manager instance has write permission to all
active, mirror, archive, and failover archive log
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
directories must allow write access from the database
manager user ID. Change the ownership of the
recovery log directories to the user ID for the Tivoli
Storage Manager instance.
ANR2638W
This command will delete all user data

and log files, as well as any
backup/restore history for the TSM
server database. Are you sure you want
your database and all of its references
removed (y or n)?
Explanation: A REMOVEDB command has been

entered.
continue.
User response: Enter 'y' to remove the database or 'n'
to leave the server database.
ANR2639E
Command failed - no files have been

defined for storing sequential volume
Explanation: Sequential volume history information is

required to restore the server data base. Because no
files were configured for receiving this information, the
operation fails.
User response: To have the server automatically
record sequential volume history information to assist
in server recovery, use the VOLUMEHISTORY option
in the server options file to specify where history
information should be written. If you update the

options file, restart the server.
ANR2640E
Command: Invalid percentage of sessions

for scheduled processing - value.

with an invalid value.
ANR2641E
Command: Invalid event record retention

period - value.

ANR2642E
Command: Invalid percentage for

randomization - value.

ANR2643E
Command: Invalid schedule query period

- value.

ANR2644E
Command: Invalid maximum number of

command retries - value.

ANR2645E
Command: Invalid retry period - value.

339
ANR2646E ANR2654E
ANR2646E
Command: Invalid scheduling mode value.

ANR2647E
Command: Invalid type - type.
OBJECTS, and OPTIONS parameters. This message is

displayed when the CMD parameter is specified and
TYPE=CLIENT is not specified, or when
TYPE=ADMIN is specified, and one or more of the
following is specified: ACTION, OBJECTS, or
OPTIONS.
ANR2652E

with an invalid type.
User response: Issue the command with a valid type.
ANR2648E
Command: Type string exceeds maximum

length characters.
Command: Invalid combination of one or

more of the following parameters:
active, cmd, type.

with an invalid combination of the TYPE, CMD, or
ACTIVE parameters. This message is displayed when
TYPE=CLIENT is specified and one or more of the
following is specified: ACTIVE, CMD.

with a type string that exceeds the maximum length.


ANR2653W
User response: Issue the command with a valid type

string.
Command: Node node name cannot be

processed because it is not registered or
does not belong to the specified
domain.
Command: Schedule schedule name is not

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

with a schedule name that has not been defined.
User response: Issue the command with a schedule
that has already been defined.
ANR2650E
Command: Schedule schedule name is

already defined.

with a schedule name that has already been defined.
User response: Issue the command with a schedule
name that has not already been defined.
ANR2651E
Command: Invalid combination of one or

more of the following parameters: cmd,
type, action, objects, options.
System action: The indicated node is not processed,

but other nodes may be processed if specified by this
command.
User response: If the node name was entered
incorrectly, reissue the command with the correct node
name.
ANR2654E
Explanation: A QUERY SCHEDULE command has

been issued with TYPE=ADMINISTRATIVE and the
NODES parameter both specified. The NODES
parameter cannot be specified when querying
administrative schedules.
User response: Issue the command without the
NODES parameter.

with an invalid combination of the CMD, ACTION,
340
Command: The NODES parameter cannot

be used when querying administrative
schedules.
ANR2655E ANR2662I
ANR2655E
Command: Invalid client action schedule

duration - days.

with an invalid number of days. Valid values are 1 to
9999 inclusive. days specifies the length of time during
which a schedule defined by the DEFine CLIENTAction
command must be executed by an associated node.
After that, the schedule will be deleted from the
database.
number of days.
ANR2656E
Command: Invalid schedule style

schedStyle.
ANR2660E

with an invalid combination of the DAYOFMONTH,
WEEKOFMONTH, and DAYOFWEEK parameters.
WEEKOFMONTH and DAYOFWEEK cannot be
specified with DAYOFMONTH. WEEKEND or
WEEKDAY must be specified with the FIRST or LAST
week of month.
ANR2661E

with an invalid schedule style.
schedule style.
ANR2657E
Command: Invalid month month.

with an invalid month.
month.
ANR2658E
Command: Invalid day of month month.

with an invalid day of month.
day of month.
ANR2659E
Command: Invalid week of month month.

with an invalid week of month.
week of month.
Command: Invalid combination of

enhanced schedule parameters or their
values: parm1 and parm2.
Command: Invalid combination of

enhanced schedule parameters or their
values, parm1 and parm2, found for
schedule name.
Explanation: The specified update command has been

issued with either an invalid combination of
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.
User response: To see the options for the existing
schedule, issue: QUERY SCHEDULE
FORMAT=DETAILED for the client or administrative
schedule. Determine if the error was caused by one of
the following:
v a conflict between parameters to the update
command.
v a conflict between a parameter specified with the
update command and a value that already exists for
the schedule.
For the latter problem, also update the existing option
that is causing the problem. Correct the update
command and issue it again.
ANR2662I
(*) "Query schedule format=standard"

displays an asterisk in the day of week
column for enhanced schedules. The
period column is blank. Issue "query
schedule format=detailed" to display
complete information about an
enhanced schedule.
Explanation: This message explains the standard

display for an enhanced schedule.
User response: Issue "query schedule format=detailed"
341
ANR2663I ANR2670E
to display information about an enhanced schedule.
ANR2663I
Command: resetting existing options

options for schedule name to default
values.
Explanation: The update schedule command has reset

existing options for the schedule to default values. The
change is required by the parameters specified with the
update or audit commands.
ANR2664E
Command: Invalid parameter parm for

schedule style schedule style.
Explanation: A specified parameter is not valid for the

schedule style.
schedule, issue "q sched f=d" for the client or

administrative schedule. Determine the correct day and
month combinations. If the the command failed, issue
the update command again.
ANR2667W
Audit volume process has skipped

volume volume name due to an error.

VOLUME command for the volume shown, an
unrecoverable error occurred on the volume.
System action: The AUDIT VOLUME command has
skipped the volume shown.
User response: Examine messages that were
previously issued that explain the cause of the failure
and correct the error if possible. Once the error has
been corrected, reissue the command.

ANR2668I
User response: Issue the command and with

parameters valid for the schedule style.

server command SET DEDUPVERIFICATIONLEVEL is
issued. Setting the deduplication-verification level helps
ensure that the client is not making a security attack
against the server.
ANR2665W
Command: Invalid month and day, month

day, detected.

with an invalid combination of MONTH and
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,
the schedule will be defined and run on the valid
dates. The schedule will skip the invalid month and
day combinations.
User response: Determine the correct day and month
combinations. If the command failed, issue the define
command again. If the schedule was defined, use the
update command to change the month and day values.
ANR2666W
Command: Invalid month and day, month

day, detected for schedule name.
Explanation: The specified update command has been

issued with either an invalid combination of MONTH
and DAYOFMONTH, or a specified MONTH or
DAYOFMONTH value is incompatible with a MONTH
or DAYOFMONTH value that is not being updated for
the existing schedule. If there is just one month and
one day combination and that combination is invalid,
the command will fail. If there is at least one valid
month and day combination, the schedule will be
updated and run on the valid dates. The schedule will
skip the invalid month and day combinations.

ANR2669E
The specified deduplication-verification

level is invalid.

User response: Specify a value 0 - 100 for this
command.
ANR2670E

SCHEDSTYLE parameter detected while

SCHEDSTYLE parameter for schedule schedule name in
domain domain name.
exported data contains an unknown SCHEDSTYLE
default or existing SCHEDSTYLE value is used.
User response: Update the SCHEDSTYLE value for
value, and check and update the SCHEDSTYLE value
User response: To see the options for the existing
342
The deduplication-verification level is

set to &arg1;percent.
ANR2671E ANR2677E
ANR2671E

SCHEDSTYLE parameter detected while
ANR2674E

SCHEDSTYLE parameter in exported
data - existing SCHEDSTYLE value for

SCHEDSTYLE parameter for administrative schedule
schedule name.


exported data contains an unknown SCHEDSTYLE
server uses the default or existing SCHEDSTYLE value.

by using the existing SCHEDSTYLE value for this
schedule.
User response: Update the SCHEDSTYLE value for

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
performed.
ANR2672E

domain domain name.

default or existing SCHEDSTYLE value is used.
command, verify that the correct SCHEDSTYLE value
is used for this schedule.
ANR2673E

SCHEDSTYLE value.

by using the default SCHEDSTYLE value for this
schedule.
User response: Verify that the correct SCHEDSTYLE

ANR2675E

data for administrative schedule schedule
name.

schedule name.
imported, the default or existing SCHEDSTYLE value is
used.
command, verify that the correct SCHEDSTYLE value
is used for this schedule.
ANR2676E

data - administrative schedule schedule
name defined with default
SCHEDSTYLE value.

schedule name.
by using the default SCHEDSTYLE value for this
schedule.
ANR2677E

data - existing SCHEDSTYLE value for
administrative schedule schedule name
was not updated.

343
ANR2678E ANR2686I
schedule name.
by using the existing SCHEDSTYLE value for this
schedule.
ANR2678E
ANR2682E
Command: You cannot specify

MODE=DIFF when TYPE is
SNAPMIRROR.
Explanation: A SnapMirror backup was attempted

while specifying MODE=DIFF. Network Appliance
SnapMirror backups may only be full image backups.
User response: Reissue the command and do not
specifiy MODE=DIFF with TYPE=SNAPMIRROR.
Server database format failed.
Explanation: A failure occurred during the format of

the TSM server database. This occurred during the
processing of a 'DSMSERV FORMAT' command.
System action: Server format processing terminates.
User response: Review error messages to determine
the cause of the failure and retry the 'DSMSERV
FORMAT' once the issue has been resolved.
ANR2683I
Command: A Table of Contents will not

be created for a SnapMirror backup.
Explanation: A Netapp SnapMirror backup was

requested and the TOC parameter is set to
PREFERRED. The backup will continue, however no
Table of Contents will be created.
ANR2679E
Command: All of the nodes provided are

invalid.
ANR2684E
Explanation: While verifying the parameters of the

specified command, no valid node was found.
User response: Verify that the nodes specified are
correct and all are registered. Then, reissue the
command.
Command: SnapMirror operations are not

supported on NAS virtual filespace
definitions.
Explanation: A SnapMirror backup or restore was

attempted on a NAS virtual filespace. Network
Appliance SnapMirror backups do not support
directory level backup, therefore a virtual filespace may
not used with TYPE=SNAPMIRROR.
ANR2680E
Command: You cannot specify TOC=YES

when TYPE is SNAPMIRROR.
Explanation: A SnapMirror backup was attempted

while specifying TOC=YES. Network Appliance
SnapMirror backups do not support TOC creation.
User response: Reissue the command by specifying

TYPE=DUMPIMAGE.
ANR2685I

specifying TOC=YES.
ANR2681E
Command: The file server movername does

not support SnapMirror-to-Tape
operations or is not running NDMP
Version 4.
Explanation: A SnapMirror backup was specified with

a NAS device that does not Network Appliance
SnapMirror backup operations.
SnapMirror backup of NAS node

nodename, file system file system, started
as process process ID by administrator
administrator.
Explanation: A SnapMirror backup is started for the

indicated file system of a NAS node. The operation is
initiated by the administrator shown.
ANR2686I

User response: Reissue the command by specifying a
standard NDMP full or differential backup.
SnapMirror Restore of NAS node

nodename, file system filesystem, started as
process process ID by administrator
administrator. A full image for this file
system will be restored to destination
destination.
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
be performed using a full image of this file system. The
344
ANR2687E ANR2695E
file system will be restored to the indicated destination.
ANR2691E


ANR2687E
Command: You cannot specify a

FILELIST when TYPE is
SNAPMIRROR.
Explanation: A file level restore was attempted from a

SnapMirror backup. Network Appliance SnapMirror
backups do not support file level restore.
FILELIST parameter.
ANR2688E
Command: The SnapMirror Restore of

NAS node nodename, file system file
system, cannot be started. The
destination file system destination is not
set to "Restricted" on the NAS device.

command.
ANR2689W
Command: The dataformat of the

datamover data mover is incompatible
with the NAS device with host
identifier hostId.
Explanation: The dataformat provided in the

command is not compatible with the NAS device
which is associated with the high level address. was
found.
System action: The server completes the command.
User response: Determine the proper dataformat for
your NAS device and reissue the command.

command.
ANR2692E
Command: The file system file system is in

restricted state and cannot be used in an
NDMP backup or restore operation.
Explanation: A NAS file system that is in the

restricted state was specified for an NDMP backup or
restore operation. You cannot perform an NDMP
backup or restore of a file system in the restricted state.
User response: Refer to your NAS device's
documentation on how to unrestrict the file system.
Then, reissue the command.
Command: Invalid subaction - action.

with an invalid subaction.
subaction.
ANR2693E
Command: Invalid action and subaction

combination.

with an invalid combination of action and subaction
values.
subaction.
ANR2694E
Command: Action must be specifed with

subaction.

with a subaction and no action value.
subaction.
ANR2695E
ANR2690E
Command: All of the nodes provided are

invalid.
The deduplication mode for node node

name was set to SERVERONLY.
Explanation: The server detected a potential security

attack and disabled client-side deduplication.
System action: Server and client operations continue.
User response: Verify that the client workstation does
not have any applications that are attempting a security
attack on the server. If the client is secure, re-enable
client-side deduplication on the node by issuing the
server command UPDATE NODE with the
DEDUPLICATION=CLIENTORSERVER parameter.
345
ANR2696E ANR2702E
ANR2696E

SUBACTION parameter detected while

ACTION parameter for schedule schedule name in
domain domain name.
exported data will contain an unknown SUBACTION
default or existing SUBACTION value is used.
User response: Update the SUBACTION value for this
and update the SUBACTION value after import
ANR2697E

SUBACTION parameter in exported
SUBACTION value.

SUBACTION parameter for schedule schedule name in
by using the default SUBACTION value for this
schedule.
User response: Verify that the correct SUBACTION
ANR2698E

data - existing SUBACTION value for

by using the existing SUBACTION value for this
schedule.
User response: Verify that the correct SUBACTION
346
ANR2699E

domain domain name.

default or existing SUBACTION value is used.
command, verify that the correct SUBACTION value is
ANR2700E
Schedule manager aborted.
Explanation: The schedule manager has ended

because of an error condition and is not able to
maintain entries for scheduled operations.
central scheduler is not operational.
examine server messages issued prior to this message.
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
scheduler operations. If the error cannot be isolated and
ANR2701E
The schedule manager could not be

started: diagcode.
Explanation: The schedule manager cannot be started

during initialization because sufficient memory is not
available. Diagnostic code diagcode is issued.
application.
ANR2702E
The schedule prompter could not be

started: diagcode.
Explanation: The schedule prompter cannot be started

application.
ANR2703E ANR2715E
ANR2703E
Schedule prompter aborted.
ANR2712E
Explanation: The schedule prompter ends because of a

processing error.
prompted scheduling is not operational.
examine server messages issued prior to this message.
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
scheduler prompting operations. If the error cannot be
isolated and resolved, contact your service
representative.
ANR2707E
Out of server log space in central

scheduler.

transaction for the central scheduler because sufficient
database update fails.
User response: An authorized administrator can use
volumes are used.
Explanation: A request for pending scheduled

operations has been sent from the client scheduler for
node node1. However, the request is for scheduling
information concerning another node node2.
client scheduler for node node1 will not be able to
process pending operations.
User response: Try restarting the client scheduler for
node node1. If the problem persists, contact your service
representative to resolve the client program error.
ANR2713E
Node node1 trying to start scheduled

operation for node node2 - session
rejected.
Explanation: The client scheduler for node node1 has

attempted to execute a scheduled operation for another
node, node2.
scheduled operation is not processed.
representative to resolve client program error.
ANR2714E
ANR2708E
Node node1 requested scheduling

information for node node2 - session
rejected.
Out of server database space in central

scheduler.
Node node1 trying to report scheduled

operation results for node node2 session rejected.

transaction for the central scheduler because sufficient
Explanation: The client scheduler for node node1 has

attempted to report the results of a scheduled operation
using another node name, node2.


results that were sent from node node1 are not be stored
in the servers database.

for use by the database and can use the EXTEND DB

representative to resolve the client program error.
ANR2715E
ANR2709E
Schedule manager : Unable to start

event record deletion.
Explanation: Event record deletion cannot be started

because sufficient memory is not available.
System action: Server operation continues, but event
records are not automatically deleted after their
retention period has elapsed.
application.
Client node node id unable to register

valid address for server prompting: type
address type (high address low address).
Explanation: The client scheduler for node node id has

attempted to register an invalid address for
server-prompted central scheduling. The address was
type address type with high-level field high address and
low-level field low address. The only valid address type
is 1.
node node id will not be prompted to perform
scheduled operations.
User response: Verify that the address type and
347
ANR2716E ANR2722I
address are correct for this client. The only valid
address type is 1 (for TCP/IP). Make sure the client
scheduler is not using an invalid address obtained from
the clients options file or from the command line when
the client scheduler was started.
ANR2716E
Schedule prompter was not able to

contact client node name using type
address type (high address low address).
Explanation: The server has attempted to prompt the

client scheduler for node node name because a
scheduled operation should be started. The server is
unable to contact the client by using address type
address type, with high-level field high address and
low-level field low address.
System action: Server operation continues, but node
node name is not prompted to start the scheduled
operation. If operations should be started for other
nodes, the server will attempt to prompt the client
schedulers for these nodes. This error is usually caused
by network outages or the client scheduler program not
being run on the client node.
ANR2718W
Schedule manager disabled.
Explanation: The schedule manager has been disabled

because the DISABLESCHEDS YES option was
specified in the server options file.
central scheduler is not operational.
User response: To enable the schedule manager,
specify DISABLESCHEDS NO in the server options file
ANR2719E
Command: Invalid parameter parm for

ACTION=DEPLOY.
Explanation: A parameter that is specified is not valid

for ACTION=DEPLOY.
System action: Server operations will continue, but
the command is not processed.
ACTION=DEPLOY parameters.
being replicated.
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 that the
client scheduler is not using an invalid address,
obtained at the time the client scheduler was started,
from either the clients options file or from the
command line. Verify that the client scheduler for node
node name is running and that the necessary
communication links to that scheduler are operational.
Firewalls must allow traffic from the server to the client
and from the client to the server without the session
timing out. Ensure that the DNS configuration is
correct.
ANR2720E
ANR2717E
Schedule prompter cannot contact client

node name using address type (address
type).
Explanation: A non-replication SSL session to the

indicated address was attempted. Server-to-server SSL
sessions are supported for replication only.
Explanation: The server attempts to prompt the client

scheduler for node node name because scheduled work
should be started. However, either the server does not
support address type address type needed for
server-prompted scheduling, or the communication
method is not currently available. The only valid
address type is 1 (for TCP/IP).
System action: The server does not start the session.

server does not prompt node node name.
User response: If the server does not support the
address type specified, clients may only use the polling
mode of scheduling. If the communication method is
temporarily not available, prompted mode scheduling
will resume after the communication problem is fixed
and service restored. If the problem persists, contact
348

that is currently being replicated to another server.
command.
or if necessary, cancel the current replication and
ANR2721E
A non-replication SSL session to

address address is requested.
User response: If you want to configure the same

target server for both SSL and non-SSL
communications, you can configure multiple server
definitions when you issue the DEFINE SERVER
command. You can have multiple server definitions
with the same target address if the server names are
not the same.
ANR2722I
The server now accepts sessions that

originate from server server name
Explanation: The server can now accept sessions from

the named server.
ANR2723I ANR2752E
ANR2723I
The server is enabled to have outbound

sessions to server server name
Explanation: The server now allows sessions targeted

to the named server.
ANR2724I
The server does not accept sessions from

server server name
Explanation: The server rejects sessions from the

named server.
ANR2725I
User response: Verify that all of the nodes to be

replicated are in SEND or SYNCSEND mode. Reissue
the command, or, if necessary, cancel the replication
process and reissue the command.
This command will register the node to
new domain domainname. Changing the
domain will cause the node to be
disassociated from the schedule of
original domain.
Explanation: The schedule belongs to the domain. The

node will be disassociated from the schedule if the
node is registered to new domain.
System action: Tivoli Storage Manager prompts the
user to continue.
Command: None of the specified nodes

are configured for replication or they are
part of an active replication process.
Explanation: The replication command did not start

because data belonging to the specified nodes was
being replicated, or because the nodes are not
configured for replication.
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
replication process. A node is configured for replication
if the replication state is ENABLED or DISABLED. To
determine the replication state of a node, issue the
QUERY NODE FORMAT=DETAILED command. To
configure nodes for replication, issue the UPDATE
NODE command. After the situation has been
corrected, reissue the REPLICATE NODE command.
ANR2727E
System action: The server processes the command.

However the specified node is is skipped for this
operation.
The server is disabled for sessions with

server server name

replicated because it is not in the SEND
or SYNCSEND mode.
Explanation: The replication mode of a specified node

is RECEIVE or SYNCRECEIVE. To replicate, the
replication mode must be SEND or SYNCSEND.
ANR2729W
Explanation: The server cannot initiate sessions to the

named server.
ANR2726E
ANR2728E

accessing server server name.
User response: Enter 'Y' to change the domain. Enter

'N' if you do not want to change the domain.
ANR2750I
Starting scheduled command schedule

name ( scheduled command ).

server starts the execution of a scheduled command.
The name of the schedule and the actual command
scheduled is displayed.
scheduled command is processed.
ANR2751I
Scheduled command schedule name


server successfully completes processing of a scheduled
command.

that has an active session with the specified server.
System action: The local server does not process the

command.
ANR2752E

the command.

server encounters a failure in processing a scheduled
command.

failed.

349
ANR2753I ANR2761I
scheduled command is ended.
User response: Examine messages issued prior to this
message and use the UPDATE SCHEDULE command
to correct the scheduled command. The QUERY EVENT
command may also be used to determine the cause of
the failure for this scheduled command.
ANR2753I

User response: Issue the command without the
NODES parameter.
ANR2758E
(Schedule name):command response
Explanation: This message is used to display the

server response to a scheduled command. The name of
the command schedule is included at the beginning of
the message in parentheses.
scheduled command is ended.
Please specifiy a tracefile name with

less than 37 characters if it is fully
qualified or 26 characters if it is not
fully qualified.
Explanation: The .template file adds 9 more characters

to the end of the filename.
User response: Reduce the filename length to a
working range for s390 system

ANR2759I
ANR2754E
DEFINE SCHEDULE or UPDATE

SCHEDULE parameter CMD='command'
- Unknown command.
Explanation: The specified command is not a valid

server command.
System action: The DEFINE SCHEDULE or UPDATE
SCHEDULE command is not processed.
Command: The virtual file space

definition vfs name for node node name
has been deleted.

VIRTUALFSMAPPING command, the virtual file space
mapping vfs name for the node node name has been
deleted in the server database.
User response: Reissue the correct command.
ANR2755E
ANR2760E
DEFINE SCHEDULE or UPDATE

SCHEDULE parameter CMD='command'
- not eligible for scheduling.
Explanation: The specified command is not eligible for

scheduling.
System action: The DEFINE SCHEDULE or UPDATE
SCHEDULE command is not processed.
ANR2756I

started successfully.

server successfully starts processing of a background
process for a scheduled command.
Explanation: The DELETE VIRTUALFSMAPPING

command has been entered, but the specified virtual
file space mapping vfs name for the node node name has
an associated file space definition in server database.
command.
User response: To delete the virtual file space
definition, first delete the filespace definition with the
same name.
ANR2761I

ANR2757E
Command: The NODES parameter cannot

be used when querying events for
Explanation: A QUERY EVENT command has been

issued with TYPE=ADMINISTRATIVE and the NODES
parameter both specified. The NODES parameter
cannot be specified when querying events for
350
Command: Unable to delete the virtual

file space definition vfs name for node
node name. A file space definition exists
with the same name.
Audit command: auditing inventory

virtual file space mappings.

database audit and indicates that server information
about virtual file space mappings is currently being
examined by the database audit process.
ANR2762I ANR2770E
ANR2762I

named vfs name for node node name has
been updated.

VIRTUALFSMAPPING command, a virtual file space
mapping for the specified node has been updated in
name as a file space on the NAS device.

User response: Ensure that no virtual file space
mappings for this NAS device have the same name as
an actual file space that exists on the NAS device.
ANR2767E

ANR2763E
Command: The hexadecimal string

entered for the path parameter is not
valid.

invalid Hexadecimal value for the path parameter.
command.
User response: Check that the string representing the
path contains only valid hexadecimal characters and
contains an even number of characters. Reissue the
command with a valid Hex string for the path
parameter.
ANR2764E
command: Filespace filespace name cannot

be renamed to new filespace name; a
virtual file space with this name already
exists for node node name.
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
fails.
command fails.
target filespace name
ANR2765E
command: The node node name has an

invalid node type for virtual file space
definitions; the node type must be NAS.
Explanation: A Define VirtualFSMapping command

was entered with an invalid node type.
command.
User response: You might want to run this command
again, specifying a node of TYPE=NAS.
ANR2766W
Command: Virtual file space name vfs

name conflicts with file space on the
network attached storage (NAS) device.

entered with a virtual file space that has the same
Command: The data format of storage

pool Storage Pool Name does not match
the data format of storage pool Storage
Pool Name.
Explanation: The data format of the indicated storage

pools does not match. The requested operation failed.
User response: Use QUERY STGPOOL F=D to display
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
command.
ANR2768I
Process process ID will use data mover

datamover name for the operation.
Explanation: The indicated data mover is being used

by the indicated process.
System action: The indicated data mover is being
used by the indicated process.
ANR2769E
Command: Process process ID terminated data mover inaccessible.
Explanation: The indicated process terminated for the

indicated command because none of the data movers is
accessible.
System action: The indicated process terminates.
for possible reasons a remote session could not be
started.
ANR2770E
Command: Process process ID skipped

restoring data from volume volume name
in storage pool name storage pool - drive
path unavailable.
Explanation: The indicated process skipped restoring

data from the indicated volume because none of the
NAS type datamovers is available.
System action: The data in the indicated volume is
not restored.
User response: Use QUERY STGPOOL to obtain the
device class to which the indicated source storage pool
belongs. Use QUERY DEVCLASS to obtain the library
containing the source storage pool. Then, use the
QUERY DATAMOVER and QUERY PATH commands
351
ANR2771E ANR2778I
to verify that at least one NAS datamover has paths to
the drives in the library.
ANR2771E

volume volume name - data mover
inaccessible.
Explanation: Move data processing terminated for the

indicated volume because none of the data movers is
accessible.
System action: Move data ends for the indicated
volume.
for possible reasons a remote session could not be
started.
ANR2772E
v None of the data movers with paths to the drives in

the library containing the source storage pool is
available.
the library containing the target storage pool is
available.
device class to which the source or target storage pool
belongs. Use QUERY DEVCLASS to obtain the library
name that contains the source or target storage pool.
Then, use the QUERY DATAMOVER and QUERY
PATH commands to verify that at least one data mover
has paths to the drives in the library.
volume volume name - drive path or data
mover unavailable.
Explanation: MOVE DATA processing terminated for

the indicated volume for one of the following reasons:
the library containing the source storage pool is
available.
the library containing the target storage pool is
available.
device class to which the source or target storage pool
belong. Use QUERY DEVCLASS to obtain the library
name that contains the source or target storage pool.
Then, use the QUERY DATAMOVER and QUERY
PATH commands to verify that at least one data mover
has paths to the drives in the library.
352
Command: Process process ID terminated data format mismatch.
Explanation: During restore processing, a data format

mismatch occurred between the storage pool being
restored and the copy storage pool.
System action: The indicated restore process
terminates.
User response: Examine the previous error message to
determine the name of the copy storage pool used for
the restore. If possible, specify a copy storage pool that
has the same data format as the storage pool being
restored on the restore command.
ANR2775W
Command: Process process ID terminated drive path or data mover unavailable.
Explanation: The indicated process terminated for the

indicated command for one of the following reasons:
ANR2773E
ANR2774E
Command: Process Process id encountered

an output error. File on volume volume
name skipped - Node node name, type file
type, file space filespace name, file name
file name, fsId filespace id.
Explanation: During copy or move operation, an

output error was encountered. The indicated file was
skipped.
System action: The file will not be processed.
User response: If possible, correct the error and re-run
the command.
ANR2776I
Audit command: Inventory object

(object.ID) is part of an incomplete
group. The inventory entry will be
deleted.

inventory object that is part of an incomplete group.
Because FIX=YES has been specified for the command,
the inventory entry is deleted.
ANR2777I
Audit command: Inventory object

(object.ID) is part of an incomplete
group.

inventory object that is part of an incomplete group.
User response: Run the audit command again with
FIX=YES, so that the error can be corrected.
ANR2778I
Audit command: Storage entry for an

inventory object (object.ID) cannot be
found. The inventory entry will be
deleted.
Explanation: A database audit process cannot find the

storage entry for the specified inventory object. Because
ANR2779I ANR2788E
FIX=YES has been specified for the command, the
inventory entry is deleted.
ANR2779I
Audit command: Storage entry for an

inventory object (object.ID) cannot be
found.

storage entry for the specified inventory object.
ANR2783E
Explanation: A required keyword was not specified

for database format processing.
System action: Server database format processing
terminates.
User response: Reissue the format command with the
required parameters.
ANR2784E

User response: Run the audit command again with
FIX=YES, so that the error can be corrected.
ANR2780W
Command: Updates for nodes previously

processed during this command will be
rolled back.
Explanation: An error has occurred during an

UPDATE NODE operation. If the UPDATE NODE
command was processing more than one node, updates
for nodes which were previously processed will be
rolled back.
User response: Correct the error and reissue the
command.
ANR2781E
command name: keyword value longer than

max length characters.
Explanation: The directory specified for the indicated

keyword is too long. Specify a directory less than or
equal to the number of characters indicated. This is a
limitation of the underlying database.
System action: Server database format processing
terminates.
FORMAT: Required keyword keyword

not specified.
FORMAT: The mirror log diretory must

not be the same as the active log
directory.
Explanation: The server found an error when

processing the format command.
System action: Server stops the format.
User response: Select a different directory for mirror
log and reissue command.
ANR2785E
An error occurred when trying to access

path name.
Explanation: An access denied error occurred while

attempting to access a directory.
System action: The command stops.
User response: Verify permission for that directory is
set correctly then reissue the command.
ANR2786E
The server was unable to find path name.
Explanation: The server could not find the directory

specified.
User response: Verify the existence of that directory
User response: Specify a valid value for the indicated

keyword.
ANR2787E
ANR2782I
Explanation: The server failed to access the directory

specified.
SET DBRECOVERY completed

successfully and device class for
automatic DB backup is set to value.
The server failed with error code last

error when attempt to access path name.
Explanation: The device class requirement for

automatic database backup is set with the SET
DBRECOVERY command.
User response: Verify the existence of that directory

ANR2788E
The server failed with error code last

error when attempt to create files in path
name. The path is not empty. It might
contain data from your existing
database.
Explanation: The format operation requires an empty

directory to protect data from being overwritten.
System action: The format operation stops.
353
ANR2789W ANR2798E
User response: Verify the directory that was specified.
Delete any data in that directory if the data is not
needed, or create a new directory. Reissue the format
command.
ANR2789W
Command: Node node name is registered,

but the server cannot remove it because
it is reserved.

that is reserved by the server.
command.
ANR2790E
Too many symbolic links were found

while traversing file path path name.
ANR2795I
command: Repair failed processing

backup sets for node node name. backup
set count backup sets belonging to node
count nodes were successfully repaired
before the failure.
Explanation: The REPAIR BACKUPSET command

encountered an error processing backup sets for the
specified node. Some backup sets might have been
successfully repaired.
System action: The command failed. Some backup
sets might have been repaired.
activity log and search for messages. Correct the
problem and rerun the command.
System action: The server stops processing the

command.
ANR2796I
User response: Refer to your operating system's

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
Explanation: The REPAIR BACKUPSET command

completed after successfully repairing the retention
initiation date for the indicated number of backup sets.
command: Repair completed for backup set

count backup sets belonging to node
count nodes.
System action: The command completed.

ANR2791E
The file or volume name path name is

too long.

command.
ANR2797E
User response: Check your operating system's limits

on files and pathss length.Reissue the command with a
shorter file or volume name.
Explanation: One or more license values were skipped

due to the current system date not being valid for the
license. This message occurs when reading the
nodelock file. This can occur during server start-up,
license audit, or REGISTER LICENSE.
ANR2792E
A component of the path path name is

not a directory.
Explanation:
command.
The license value was skipped because

of a bad date range.
System action: Server operation fails.

User response: Verify the correct system date setting.
After you correct the system date, the licenses that are
registered with a quantity value will need to be
registered again.
User response: Verify all directories in the path of the

file or volume name. Reissue the command with a
valid file or volume path. command.
ANR2798E
ANR2793W
Explanation: The server refuses a server operation

because the server is not licensed with the appropriate
support.
An invalid value for MAXTXNBYTE is

found in the database value in bytes.
Explanation: The server detects an invalid value for

MAXTXNBYTE in the database. The server will use the
default value for MAXTXNBYTE and processing will
continue.

User response: Obtain and register the appropriate
license.
System action: Th server initialization continues.

User response: No action is required
354
Server operation is denied - server is not

licensed for License required.
ANR2799W ANR2811I
ANR2799W
Server operation is in violation of server

license terms - server is not licensed for
License required.
Explanation: The server warns about a server

operation because the server is not licensed with the
appropriate support.

add log volumes using the DEFINE LOGVOLUME
command, and can extend the size of the log using the
EXTEND LOG command.
ANR2806W
Insufficient database space available for

the license manager - will retry in
User response: Obtain and register the appropriate

license.
Explanation: The server suspends license manager

processing because sufficient database space is not
available.
ANR2800E
System action: Server operation continues; the license

manager operation will be retried after the specified
delay.
The license manager cannot be started:

diagcode.
Explanation: The license manager cannot be started

application.
ANR2803I
License manager started.
Explanation: The license manager is started when the

server is initialized. The license manager monitors
license compliance.
ANR2804W
Insufficient memory is available for the

license manager - will retry in number of
seconds seconds.

processing because sufficient server memory is not
available.
delay.
application.
ANR2805W
Insufficient recovery log space available

for the license manager - will retry in

processing because sufficient recovery log space is not
available.
delay.

DEFINE DBVOLUME command, and can extend the
size of the log using the EXTEND DB command.
ANR2807E
Out of server log space in license

manager.

transaction for the license manager because sufficient
recovery log space is not available on the server.
volumes are used.
ANR2808E
Out of server database space in license

manager.

transaction for the license manager because sufficient
for use by the database and can use the EXTEND DB
ANR2811I
Audit License completed - Server is in

Explanation: The results from the AUDIT LICENSES

command indicate the server is in compliance with the
terms of the current license.
355
ANR2812W ANR2821E
ANR2812W
License Audit completed - ATTENTION:

Server is NOT in compliance with
license terms.

command indicate the server is not in compliance with
the terms of the current license.
REGISTER NODE command or backup-archive
requests, or both, will fail.
REGISTER LICENSE command and the AUDIT

LICENSE process may not run at the same time.
ANR2817I
Command: License audit started as

process process ID.

to audit the server for license compliance.
System action: The server checks the existing
configuration for the server and compares it against the
values for which the server is licensed.

compliance.

PROCESS command, or cancel the process with the
ANR2813I
ANR2818I
Server is licensed for a capacity of

capacity gigabytes and number of clients
clients.
Command: Licensed capacity is capacity

GB with number of clients clients.
Explanation: This message is issued during server

startup.
Explanation: This message displays the license

information that existed before issuing the REGISTER
LICENSE command.
ANR2814I
Audit command: License audit period

changed to number of days days.

the SET LICENSEAUDITPERIOD command used to
change the interval in days between automatic license
audits.
ANR2815E
Command: Invalid value specified for

interval between license audits - value.

ANR2816E
Command: License audit or register

operation already in progress.
Explanation: The server is currently performing a

register license or license audit.
ANR2819I
Command: Licensed capacity changed to

capacity GB with number of clients clients.
Explanation: The license information has been

changed to the indicated values with the REGISTER
LICENSE command.
User response: To implement the changed license
information, issue an AUDIT LICENSES command or
wait until an automatic license audit occurs.
ANR2820I
Automatic license audit started as

process process ID.

System action: The server checks storage utilization
and registered nodes for the server and licensed factors,
comparing these against the values for which the server
is licensed.
status of the background process using the QUERY
PROCESS command.

specified command.
ANR2821E
User response: Reissue the command after the license

audit process or the register license command ends.
Only one REGISTER LICENSE command or AUDIT
LICENSE process can be running at a time. The
Explanation: The license manager cannot start an

automatic process to audit server licenses because
sufficient memory is not available. Diagnostic code
diagcode is issued.
356
Automatic license audit could not be

started: diagcode.
ANR2822I ANR2836I
application.

ANR2832I
ANR2822I
Cancel in progress
Explanation: The license audit operation has been

cancelled and will end when resources have been freed
for an AUDIT LICENSES operation.
ANR2823I
Explanation: While attempting to process the specified

license command, the server detects that the licensing
component of the server had not completed
initialization. The licensing facility used on some
platforms may require some time to initialize because
network calls are involved, and waits may occur.
Have audited number of nodes nodes
Explanation: An AUDIT LICENSES operation is in

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
Command: The License Manager has not

yet completed initialization - please
retry this command later.
User response: Reissue the command after waiting 10

minutes. If this message is displayed after a number of
retry attempts, contact your service representative.
ANR2833I
Command: Auditing license definitions.
Explanation: The server has started to audit database

definitions that describe licensing information.
continues.
License audit process process number

canceled - number of nodes nodes audited.
Explanation: A background server process to audit

server licenses has been canceled by using the
CANCEL PROCESS command. The number of nodes
that have been audited before the operation ended are
reported in the message.

ANR2834W
License Audit completed - WARNING:

Server is NOT in compliance with
license terms.

command indicate that the server is not in compliance
with the terms of the current license.
REGISTER NODE command fails.

server licenses has completed successfully after
auditing the specified number of nodes.

compliance. Remove nodes or purchase additional
client node connections. After these actions have been
taken, reissue the AUDIT LICENSES command to
resynchronize the server configuration with license
terms.

ANR2836I
ANR2825I

completed successfully - number of nodes
nodes audited.

ANR2826I

terminated in error - number of nodes
nodes audited.

server licenses encounters an error and is ended. The
number of nodes that have been audited before the
operation ended is reported in the message.
Command: License audit started as

process process ID.

System action: The server checks registered nodes for
the server and compares this against the value for
which the server is licensed.
status of the background process using the QUERY
357
ANR2839I ANR2902E
ANR2839I
Automatic license audit started as

process process ID.

System action: The server checks registered nodes and
compares them against the value for which the server
is licensed.
PROCESS command.
ANR2855I
Server is licensed to support Tivoli

Space Manager clients.

startup.
ANR2860I
Server is licensed to support Tivoli

Disaster Recovery Manager.

startup.
ANR2841W
Server is NOT IN COMPLIANCE with

license terms.
Explanation: This message is issued periodically when

the server configuration does not comply with the
terms for which it is licensed.
display the current server configuration with respect to
licensed terms to discover which factors of the
configuration do not conform to your license. Contact
your service representative to obtain more licenses, if
required.
ANR2852I
Current license information:
Explanation: This message is issued during a

REGISTER LICENSE command to display the current
licensing information for the server before the new
license has been interpreted by the command. Messages
appearing after this message display the factors under
which the server is currently licensed.
ANR2853I
New license information:
Explanation: This message is issued during a

REGISTER LICENSE command to display the updated
licensing information for the server after the new
license has been interpreted by the command. Messages
appearing after this message display the updated
factors under which the server is licensed.
User response: Check to make sure that the new
license information includes the updates that you
intended for the REGISTER LICENSE command. If the
license terms do not change, check the parameters and
reissue the command, if you find that it was not
entered correctly. If the REGISTER LICENSE command
does not produce the desired updates in terms of
licensing, contact your service representative.
358

ANR2900W
The character string 'string' was

truncated during assignment.
Explanation: Truncation occurred during assignment

of an SQL character string. For example, the expression
CAST( 'Hello' AS CHAR(2) ) will result in truncation
because the string 'Hello' (length 5) can not fit in the
target type CHAR(2) without loss of trailing characters.
System action: This warning can occur before or after
SQL query processing, but does not terminate query
processing.
ANR2901W
The result of character string

concatenation was truncated.
Explanation: Truncation occurred when the

concatenation of character strings resulted in a length
that exceeds the maximum character string length (250
for data type CHAR, and 2000 for data type
VARCHAR).
System action: This warning can occur before or after
SQL query processing, but does not terminate query
processing.
ANR2902E
Insufficient memory was available to

process the SQL statement.
Explanation: Sufficient memory was not available to

complete the processing of an SQL query.
System action: The SQL query is terminated.
ANR2903E ANR2913E
ANR2903E
An SQL parser stack overflow occurred

while processing token 'token'.
Explanation: The internal stack used by the SQL

query parser has overflowed. This typically occurs
when too many column names or expressions have
been specified in the SELECT clause.
Examples of SQL punctuation tokens are the period,

the comma, and the parenthesis.
ANR2909E

ANR2904E
Unexpected SQL key word token 'token'.
Explanation: A syntax error occurred because an SQL

key word was found that can not legally be used at the
specified position within the SQL statement. Examples
of SQL key words are SELECT, FROM, and WHERE.
The SQL statement is incomplete;

additional tokens are required.
Explanation: A syntax error occurred because,

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
syntactically-correct SQL statement.
ANR2910E
Explanation: An invalid SQL token was found. For

example, the token formed by the character sequence
"::!" is not a valid SQL token.
ANR2905E
Unexpected SQL identifier token 'token'.

identifier was found that can not legally be used at the
specified position within the SQL statement. Examples
of SQL identifiers are table names and column names.
Invalid SQL token - 'token'.

ANR2911E
Invalid SQL numeric literal token 'token'.
Explanation: An invalid SQL numeric literal token

was found. For example, the floating point literal
"1.456E" is not valid.
ANR2906E
Unexpected SQL literal token - 'token'.

literal token was found that can not legally be used at
the specified position within the SQL statement.
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
'G'.

ANR2907E
Unexpected SQL operator token - 'token'.
ANR2912E
Invalid character string literal token 'token'.

operator token was found that can not legally be used
at the specified position within the SQL statement.
Examples of SQL operator tokens are +, *, <, and =.
Explanation: An invalid SQL identifier token was

found. For example, the character sequence "ABC.123"
is not a valid identifier because the second part of the
identifier, "123", does not begin with a letter.

ANR2908E
Unexpected SQL punctuation token 'token'.
ANR2913E
Invalid SQL identifier token - 'token'.


punctuation token was found that can not legally be
used at the specified position within the SQL statement.
359
ANR2914E ANR2923E
ANR2914E
SQL identifier token 'token' is too long;

name or component exceeds 18
characters.
ANR2919E
The SQL data type of expression

'expression' is data type; expecting a
numeric expression.
Explanation: An SQL identifier token was found that

exceeds the maximum length of 18 characters per
component.
Explanation: An SQL expression of numeric data type

SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, or DOUBLE_PRECISION is expected.
ANR2915E
ANR2920E
The SQL token beginning with 'token' is

missing an ending delimiter.
Explanation: An SQL token was found that is missing

its ending delimiter. For example, each of the tokens
'abc, "abc, and X'abc is missing its ending delimiter.
ANR2916E
The SQL data types data type and data

type are incompatible for operator
'operator'.
Explanation: The data types of the operands are not

compatible when used with the specified operator. For
example, the expression 3 + 'abc' is not valid because
the operand data types INTEGER and CHAR(3) are not
compatible for the addition operator "+".

numeric or interval expression.
Explanation: An SQL expression of numeric data type

(SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, DOUBLE) or of interval data type (INTERVAL)
is expected.
ANR2921E

character string expression.
Explanation: An SQL expression of character string

type CHAR or VARCHAR is expected.

ANR2922E
ANR2917E

'expression' is data type; expecting an
integer expression.
Explanation: An SQL expression of data type

SMALLINT, INTEGER, or DECIMAL with scale zero is
expected.
ANR2918E

Boolean expression.
Explanation: An SQL expression of data type

BOOLEAN is expected.

'expression' is data type; expecting a date,
timestamp, character string date,
character string timestamp, or interval
expression.
Explanation: An SQL expression was expected of one

of the types DATE, TIMESTAMP, CHAR, VARCHAR,
or INTERVAL as the operand to the EXTRACT
function. In the case of CHAR or VARCHAR, the
expression must be a valid character string
representation of a date or a timestamp.
ANR2923E


'expression' is data type; expecting a time,
timestamp, character string time,
character string timestamp, or interval
expression.

of the types TIME, TIMESTAMP, CHAR, VARCHAR, or
INTERVAL as the operand to the EXTRACT function.
In the case of CHAR or VARCHAR, the expression
360
ANR2924E ANR2932E
must be a valid character string representation of a
time or a timestamp.
ANR2928E

ANR2924E

'expression' is data type; expecting a date
or character string date expression.

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.
A number can not be converted to SQL

data type INTERVAL if the interval
contains multiple date-time fields.
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
interval types INTERVAL YEAR, INTERVAL MONTH,
INTERVAL DAY, INTERVAL HOUR, INTERVAL
MINUTE, or INTERVAL SECOND can be specified.

ANR2929E

ANR2925E

'expression' is data type; expecting a time
or character string time expression.
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
that the precision and scale operands be integer
constants. A decimal constant such as 1.67 is not valid.

of the types TIME, CHAR, or VARCHAR. In the case of
CHAR or VARCHAR, the expression must be a valid
character string representation of a time.
ANR2930E

ANR2926E

'expression' is data type; expecting a date,
timestamp, character string date, or
character string timestamp expression.

of the types DATE, TIMESTAMP, CHAR, or
VARCHAR. In the case of CHAR or VARCHAR, the
expression must be a valid character string
representation of a date or a timestamp.
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
specifies two result columns (A and B).
ANR2931E
A subquery expression may not contain

a reference to a column name that is
contained in an outer query expression.
Explanation: A subquery contains a reference to a

column name in an outer query expression.
ANR2927E

'expression' is data type; expecting an
interval containing a single date-time
field.
Explanation: An SQL expression was expected of data

type INTERVAL YEAR, INTERVAL MONTH,
INTERVAL DAY, INTERVAL HOUR, INTERVAL
MINUTE, or INTERVAL SECOND, all of which contain
a single date-time field. Multi-field interval types (for
example, INTERVAL DAY TO SECOND) are not
allowed.

ANR2932E
The maximum nesting depth for

subquery expressions has been
exceeded.
Explanation: Too many nested subqueries were

specified.

361
ANR2933E ANR2941E
ANR2933E
The WHERE clause must not contain an

aggregate function.
Explanation: The use of the aggregate functions

COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
STDDEV in the WHERE clause is not allowed.
ANR2934E
The result data type of a CASE

expression can not be determined; at
least one non-null THEN or ELSE
expression must be specified.
Explanation: The result data type of a CASE

expression can not be determined because all of the
THEN expressions and the ELSE expression (if present)
specifies the NULL key word.
ANR2935E
The date-time field field is not present in

the expression 'expression' (data type data
type).
Explanation: The specified date-time field (YEAR,

MONTH, DAY, HOUR, MINUTE, or SECOND) is not
contained in the data type of the expression.
ANR2938E
The column 'column' is not allowed in

this context; it must either be named in
the GROUP BY clause or be nested
within an aggregate function.
Explanation: A column reference was specified that is

neither a column specified in a GROUP BY clause nor
is a column nested in one of the aggregate functions
STDDEV. The use of the column reference is prohibited
because either 1) the GROUP BY clause has been
specified, 2) the HAVING clause has been specified, or
3) at least one aggregate function is present.
ANR2939E
The reference 'reference' contains an

unknown SQL table name.
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
to obtain a list of all of the valid base tables.
User response: Retry the command using a table that
is defined by the Tivoli Storage Manager server
database.
ANR2940E
The command 'reference' contains an

unknown SQL column name.
Explanation: One of the aggregate functions COUNT,

MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was
found nested within another aggregate expression.
Explanation: A column name in the SQL command is

not one of the base table columns defined by the
server's database. The rows of the table
SYSCAT.COLUMNS can be selected to obtain a list of
all of the valid base table columns. If a two-part
(compound) column reference such as X.Y is specified,
then the correlation name X must be one of the active
correlation names for the query.
ANR2937E
ANR2941E
ANR2936E
The SQL aggregate function function can

not be nested within another aggregate
function.
An SQL subquery expression can not be

nested within an aggregate function.
The column reference 'column reference'

matches more than one SQL column
name.
Explanation: An expression containing a subquery

was found nested within one of the aggregate functions
STDDEV.
Explanation: The specified column reference is

ambiguous because it matches the columns associated
with multiple tables.
362
ANR2942E ANR2950E
ANR2942E
The column reference 'column reference' is

not allowed in this context because it is
part of an outer SQL query expression.
Explanation: The specified column reference is not

allowed because it names a columns of some outer
query expression. Such references are not allowed when
contained within the expressions of the HAVING and
SELECT clauses.
ANR2947E
Division by zero was detected for

operator 'operator'.
Explanation: An attempt to divide by the number zero

was detected for the specified SQL operator. The most
likely cause of the problem is that one of the values of
a column is zero, and that column is used in the
denominator of a division operation. To protect against
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
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.
Explanation: A duplicate column reference was

specified within the same GROUP BY or ORDER BY
list of columns.
ANR2944E
The reference 'reference' is an unknown

SQL scalar function name.
Explanation: The specified function reference is not

the name of a valid scalar function.

ANR2948E
The value 'value' can not be assigned or

converted to SQL data type data type.
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
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
target data type (for example, the decimal value
12345678.34 can not be assigned to data type
DECIMAL(3,2) because the precision of the target type
is exceeded); or 3) the syntax of a character string value
is not appropriate for the target data type (for example,
the string 'abc' can not be converted to data type
DATE).
ANR2945E
Too few arguments are specified for

SQL scalar function function.
Explanation: Too few function arguments were

specified. For example, the expression LEFT(x) is
invalid because the LEFT function requires at least two
arguments.
ANR2946E
Too many arguments are specified for

SQL scalar function function.

ANR2949E
Arithmetic overflow occurred for SQL

operator 'operator'.
Explanation: An arithmetic overflow occurred for the

specified operator. Examples of this include: 1) the
application of the unary negation operator to the
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.
Explanation: Too many function arguments were

specified. For example, the expression UPPER(x,y) is
invalid because the UPPER function requires exactly
one argument.
ANR2950E

Arithmetic or date-time overflow
occurred for SQL operator 'operator' for
values 'value' (data type data type) and
'value' (data type data type).
Explanation: An arithmetic or date-time overflow

occurred for the specified operator. The values that
caused the overflow (and their SQL data types) are
displayed.
363
ANR2951E ANR2958E
ANR2955E

ANR2951E
The value 'value' (data type data type) is

not a valid argument for operator
'operator'.
Explanation: An invalid value was specified as an

argument to an SQL operator. For example, the
expression SQRT(-1) is not valid because the argument
to the SQRT function is negative.
The SQL character string expression

'expression' must return a single
character.
Explanation: A single-character character string was

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
example, the string 'Hello' is invalid because it contains
multiple characters.

ANR2956E
ANR2952E

not a valid character string
representation of an SQL date or a
timestamp for operator 'operator'.
Explanation: An invalid character string

representation of a DATE or TIMESTAMP was
specified. For example, the string 'abc' is neither a valid
date nor a timestamp.
Explanation: An error occurred when attempting to

read rows from one of the SQL base tables. This
message is typically preceded by another error
describing the condition.
ANR2957E

ANR2953E

not a valid character string
representation of an SQL time or a
timestamp for operator 'operator'.
Explanation: An invalid character string

representation of a TIME or TIMESTAMP was
specified. For example, the string 'g pm' is neither a
valid time nor a timestamp.
Unable to access SQL base table 'table'.
An error occurred inserting a row in an

SQL temporary table. The server
database size may need to be increased
Explanation: An error occurred when attempting to

insert a row into a temporary table being used for an
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
store temporary tables created during the execution of
an SQL SELECT query.

ANR2958E
ANR2954E
An SQL subquery used in a scalar

expression must yield a table that
contains at most one row.
Explanation: This error results when a subquery used

in a scalar expression returns multiple rows, thereby
making it ambiguous as to which value should be
returned.
User response: Respecify the subquery (for example,
using the WHERE clause) so that the subquery returns
at most one row.
SQL temporary table storage has been

exhausted.
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
viewing the Maximum Reduction parameter, you can
determine the amount of space that is available for
temporary table storage space. If the parameter is less
than 4, the storage space becomes exhausted and the
SQL query can no longer run. Complex SQL queries
such as the ORDER BY clause, the GROUP BY clause,
and the DISTINCT operator can cause additional
temporary table space to be required.
User response: If your database is full, increase the
size of the database. If your database is fragmented
(Where the Available space parameter is greater than 4,
but the Maximum Reduction parameter is less than 4),
364
ANR2959E ANR2966E
you must either unload and load your database or add
avolume.

ANR2963W
ANR2959E
SQL temporary table row is too wide.
Explanation: A row could not be inserted into an SQL

temporary table because the row is too wide. This can
occur if 1) there are too many columns in the row being
inserted, or 2) the sum of the lengths of the columns in
the row is too wide. Temporary tables are used when 1)
the ORDER BY clause is specified; 2) the GROUP BY
clause is specified; or 3) the DISTINCT operator is
specified.
User response: Reduce the number of columns
specified in the ORDER BY and/or GROUP BY clauses.
Explanation: An SQL query has been posed that could

potentially cause a very large number of rows to be
returned and displayed, or may involve a large amount
of processing time before the first result table row can
be generated.
continue.
User response: Enter 'Y' to continue with SQL query
processing or 'N' to terminate the query.
ANR2964E
ANR2960E
Unexpected SQL enumerated type name

token - 'token'.

enumerated type name was found that can not legally
be used at the specified position within the SQL
statement. A list of all of the enumerated types declared
by the server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
This SQL query may produce a very

large result table, or may require a
significant amount of time to compute.
The reference 'reference' is not a column

of the SQL result table.
Explanation: The ORDER BY clause specified a

column that is not part of the result table for the SQL
query. Only those columns named in the select list are
part of the result table.

ANR2965E

ANR2961E
Invalid SQL enumerated type name 'name'.

enumerated type name was expected, but the specified
name is not one of the declared enumerated types. For
example, the literal expression XXX::YYYY is illegal
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
SYSCAT.ENUMTYPES.
An SQL temporary table cannot be

built. required columns columns are
needed. maximum columns is the
maximum.
Explanation: A temporary table required columns wide

is needed to complete processing for an SQL query. The
maximum degree of an SQL table is maximum columns.
The table will not be created.
User response: If the ORDER BY and/or GROUP BY
clauses were specified, reduce the number of columns
needed for the result table.

ANR2966E

ANR2962E
Unable to resolve SQL enumerated type

for value 'value'.
Explanation: A syntax error occurred because an

unqualified SQL enumerated value name was specified,
but, because that value name is a member of more than
one enumerated type, its type could not be resolved.
For example, the enumerated value name YES belongs
to more than one enumerated type, and so the result
type of the expression YES = YES can not be resolved.
A list of all of the enumerated types declared by the
server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
Command/process: Database temporary

table storage has been exhausted.
Explanation: The named command or operation could

not be completed because insufficient temporary table
storage space was available. Free space in the server
database is used to store temporary tables created
during the execution of the named command or
process.
System action: The named command or process is
terminated.
User response: Extend the server datbase (after
adding database volumes if necessary) and rerun the
commmand or process.

365
ANR2967I ANR2969E
ANR2967I

backup the contents of the database. The differential
database backup process was assigned the process ID
shown.
ANR2968E
Unix or Linux systems, verify that /etc/hosts has

an appropriate entry for "localhost".
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
the Tivoli Storage Manger API executables and the
dsm.sys configuration file. If the DSMI_DIR setting
is wrong, correct it for the DB2 instance, and then
restart the DB2 instance.
4.
137 - Ensure that the DB2-instance DSMAPIPW

command was run and that it specified nodename
$$_TSMDBMGR_$$ and the password TSMDBMGR.
5.
400 - Ensure that the options specified in the Tivoli

Storage Manager API options file are valid.
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
DSMI_CONFIG environment variable is pointing to
a valid options file for the Tivoli Storage Manager
API. If the DSMI_CONFIG setting is wrong, correct
it for the DB2 instance, and then restart the DB2
instance.
7.
For descriptions of other sqlerrmc values, look in

the dsmrc.h file that is installed with the Tivoli
Storage Manager API.
Database backup terminated. DB2

sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.

backup operation. Sources of the problem might
include:
1. Tivoli Storage Manager API configuration errors for
the DB2 instance in which the Tivoli Storage
Manager server database resides.
2. An error related to the DB2 backup operation.
3. Errors related to the target backup device.
System action: The database backup is terminated.
User response: If the message indicates DB2 sqlcode
2033, then the problem is probably the Tivoli Storage
Manager API configuration. The DB2 instance uses the
Tivoli Storage Manager API to copy the Tivoli Storage
Manager database-backup image to the Tivoli Storage
Manager server-attached storage devices. Common
sqlerrmc codes include:
1.
2.
50 - To determine whether an error created the API

timeout condition, look for any Tivoli Storage
Manager server messages that occurred during the
database-backup process and that were issued
before ANR2968E. Ensure that the Tivoli Storage
Manager API options file has the correct
TCPSERVERADDR and TCPPORT options specified
for the Tivoli Storage Manager server being backed
up. If the option settings are wrong, correct them
for the DB2 instance.
53 - Ensure that the NODENAME option in the
Tivoli Storage Manager API options files is set to
$$_TSMDBMGR_$$. Also verify the
TCPSERVERADDRESS setting. If the keyword
"localhost" is being used verify that this is being
resolved correctly by issuing the command "ping
localhost" from a system command window. If the
ping of localhost fails, consider changing the
TCPSERVERADDRESS to the explicit loopback
address of 127.0.0.1. As an alternative to setting the
explicit loopback address of 127.0.0.1, verify the
TCP/IP configuration and whether or not
"localhost" is configured correctly. For example, for
366
If this message is issued with a DB2 sqlcode that is not

2033, then look for more information about the error by
opening a DB2 command-line processor window and
typing: ? SQLsqlcode. For example, db2 => ? sql2428
ANR2969E
Database restore terminated. DB2

sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.

restore operation. Sources of the problem might
include:
1. Tivoli Storage Manager API configuration errors for
the DB2 instance in which the Tivoli Storage
Manager server database resides.
2. Errors related to the DB2 restore operation.
3. Errors related to the target backup device.
4. The Tivoli Storage Manager API client configuration
used by the current instance is not able to access the
backup image.
System action: The database restore operation is
terminated.
User response: If the message indicates DB2 sqlcode
2033, then the problem is most likely the Tivoli Storage
Manager API configuration. The DB2 instance uses the
Tivoli Storage Manger API to copy the Tivoli Storage
Manager database restore image from the Tivoli Storage
Manager server-attached storage devices to DB2.
Common sqlerrmc codes include:
1.
50 - To determine whether an error created the API

timeout condition, look for any Tivoli Storage
Manager server messages that occurred during the
backup DB process and that were issued before
ANR2970E ANR2974I
ANR2969E. Ensure that the Tivoli Storage Manager
API options file has the correct TCPSERVERADDR
and TCPPORT options specified for the Tivoli
Storage Manager server being backed up. If the
option settings are wrong, correct them for the DB2
instance.
2.
3.
4.
53 - Ensure that the NODENAME option in the

Tivoli Storage Manager API options files is set to
$$_TSMDBMGR_$$.
106 - Ensure that the DB2-instance DSMI_DIR
environment variable is pointing to the location of
the Tivoli Storage Manager API executables and the
dsm.sys configuration file. Ensure that you have the
correct permissions to access these locations. If the
DSMI_DIR setting is wrong, correct it for the DB2
instance, and then restart the DB2 instance.
137 - Ensure that the DB2-instance DSMAPIPW
command was run and that it specified the
nodename $$_TSMDBMGR_$$ and the password
TSMDBMGR.
5.
400 - Ensure that the options specified in the Tivoli

Storage Manager API options file are valid.
6.
406 - Ensure that the DB2 instance owner has at

least read access to the Tivoli Storage Manager API
options file. Ensure that the DB2 Instance
DSMI_CONFIG environment variable is pointing to
a valid options file for the Tivoli Storage Manager
API. If the DSMI_CONFIG setting is wrong, correct
it for the DB2 instance, and then restart the DB2
instance.
7.
For descriptions of other sqlerrmc values, look in

the dsmrc.h file that is installed with the Tivoli
Storage Manager API.
If the message indicates DB2 sqlcode 2542, then the

problem is probably because Tivoli Storage Manager
API version for database restore is not the same API
version for database backup. Check Tivoli Storage
Manager API version:
ANR2970E
Database rollforward terminated - DB2

sqlcode sqlcode sqlerrmc sqlerrmc
Explanation: There is a problem detected by DB2.

System action: The database rollforward is
terminated.
User response: More information about the error is
available by opening a DB2 command-line processor
window and typing: ? SQLsqlcode. For example, db2
=> ? sql2428
ANR2971E
Database backup/restore/rollforward
terminated - DB2 sqlcode sqlcode error.
Explanation: There is a problem detected by DB2.

System action: The database backup/restore/
rollforward is terminated.
User response: More information about the error is
available by opening a DB2 command-line processor
=> ? sql2428
ANR2972E
Restore DB Command: Database

restore/rollforward terminated - Not
able to clean up log directory directory
name.
Explanation: TSM tried to clean up this log directory

before PIT restore DB and not able to.
System action: The database restore/rollforward is
terminated.
User response: Please clean up this directory
manually before performing DB PIT restore.
ANR2973E
Restore DB Command: Database

restore/rollforward terminated - Log
directory is required and does not exist
directory name.
1.
AIX - /bin/sh -c "lslpp -lcq

tivoli.tsm.client.api.64bit"
2.
SUN- /bin/sh -c "cat /var/sadm/pkg/

TIVsmCapi/pkginfo | grep VERSION
3.
HP- /bin/sh -c "cat /var/adm/sw/products/

TIVsm64/CLIENT_API64/INDEX| grep ^revision
4.
Linux - rpm -q TIVsm-API64-* --qf

%{VERSION}.%{RELEASE}\\n
User response: Create the specified directory and

retry.
5.
Windows - reg query "HKEY_LOCAL_MACHINE\

SOFTWARE\IBM\ADSM\CurrentVersion\Api"
ANR2974I
If this message is issued with a DB2 sqlcode that is not

2033 or 2542, then look for more information about the
error by opening a DB2 command-line processor
=> ? sql2428
Explanation: The log direcotry is required and it does

not exist. PIT restore DB is terminated.
System action: The database restore/rollforward is
terminated.
Offline DB backup for database DB

Alias completed successfully.
Explanation: Offline DB backup completed

successfully.
367
ANR2975E ANR2984E
ANR2975E

Alias failed with sqlcode sqlcode and
sqlerrmc sqlerrmc.
ANR2981E
Explanation: The Offline Database backup failed.

System action:
User response:
ANR2976I

Alias started.
Database backup terminated due to

environment or setup issue related to
file access - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc.
Explanation: There is a problem related to

environment or setup detected by DB2.
file or directory name, correct the permissions, or
specify a new location and retry.
Explanation: Offline DB backup started.

ANR2982E

ANR2977E
Command: Command failed - Restore DB

failed with command error in device
config file.
Explanation: Restore DB failed due to error in device

configuration file.
User response: Correct the problem in device
configuration file and retry.
ANR2978E
Command: Invalid directory name directory name.
Explanation: Restore DB failed due to invalid target

directory name in device target directory file.

User response: If the TSM parameter
PASSWORDACCESS is set to GENERATE, ensure that
the system administrator has used the dsmapipw utility
to set the password. If PASSWORDACCESS is set to
PROMPT, ensure that the TSM_NODENAME and
TSM_PASSWORD database configuration parameters
have been set correctly.
ANR2983E

User response: Correct the problem in target directory
file and retry.

password - DB2 sqlcode sqlcode sqlerrmc
sqlerrmc.

DSMI_DIR - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc.

ANR2979E
Internal error - Control descriptor is

NULL.
Explanation: Something is wrong the control

descriptor is NULL.
User response: Ensure that DSMI_DIR points to a

directory containing the correct version of db2tca,
restart the instance, and execute the command again.
ANR2984E

ANR2980E
Database backup terminated TCPIP

failure - DB2 sqlcode sqlcode sqlerrmc
sqlerrmc.
Explanation: There is a TCPIP failure detected by

DB2.
User response: Correct the TCPIP setup problem
between TSM and DB2 and retry.
368

DSMI_CONFIG - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc.

User response: Ensure that the DSMI_CONFIG
environment variable points to a valid TSM options
file. Ensure that the instance owner has read access to
the dsm.opt file. Ensure that the DSMI_CONFIG
environment variable is set in the db2profile.
ANR2985E ANR2993E
ANR2985E
Database backup terminated due to I/O

error related to TCPIP - DB2 sqlcode
sqlcode sqlerrmc sqlerrmc.
Explanation: There is a TCPIP problem detected by

DB2 and caused the database backup to fail.
User response: The possible TCPIP problem are
connection time out, connection refused, bad host name
or network unreachable. Correct the TCPIP problem
between TSM and DB2 and retry.
added back in to the volume history.

ANR2989E
Explanation: Backup DB failed due to volume history

file is not defined in the dsmserv.opt.
User response: Correct the problem in dsmserv.opt file
and retry.
ANR2990E
ANR2986E
Database backup terminated due to I/O

error - DB2 sqlcode sqlcode sqlerrmc
sqlerrmc.
Explanation: There is a I/O problem detected by DB2

and caused the database backup to fail.
Database Database Name backup failed Missing volume history file.
Database restore is terminated due to an

invalid database path sqlerrmc and DB2
sqlcode sqlcode
Explanation: DB2 detected invalid database path.

System action: The database restore is terminated.
User response: Correct the I/O problem between TSM

and DB2 and retry.
User response: Ensure the path exists and permissions

are correct and issue restore DB command again or
issue restore DB command again with ON parameter to
specify a new valid database storage path.
ANR2987W
ANR2991E
Session ended because of machine

GUID or local host IP address
mismatch.
Explanation: Backup or Restore DB commands are

only allowed when the TSM database being backed up
or restored and the TSM api and the TSM server are on
the same machine. Either the GUID of the TSM api
client in use by the database manager does not match
the GUID of the TSM server or the local host IP
address indicated by the TSM client is not accepted.
System action: The database backup or restore
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
"DBMTRUSTEDIPADDR ipaddr" to set a local host
address that can be accepted.
ANR2988W
Attempt to add the last backup db

volume used entry back in to the
volume history was unsuccessful.
Explanation: Restore db operation was successful

however the attempt to add the last backup db volume
used back in to the volume history failed.
System action: The database restore operation is
successful. Entry for last backup db volume used in the
operation might be missing from volume history.
User response: Keep a copy of the volume history file
that was used to do the restore operation. After you
have verified the restore db operation do a backup db
type=full. Manually track the volume that was not
The Incremental Database backup was

terminated because a full database
backup is required - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc.
Explanation: The Incremental Database backup was

terminated. A FULL database backup is required before
an Incremental Database backup can be completed.
System action: The incremental database backup is
terminated.
User response: Complete a FULL database backup
first, then retry the incremental database backup.
ANR2992W
The total DB used in DB space is log

available in the DB space is log space
available megabytes. The ratio is log file
system used ratio.
Explanation: The DB space used exceeds the threshold

for DB space utilization, please define more DB space
using EXTend DBSpace command.
System action:
User response:
ANR2993E
The database backup terminated with a

log problem. DB2 sqlcode: sqlcode. DB2
sqlerrmc: sqlerrmc.
Explanation: The database backup was terminated by

DB2 because one or more of the log files needed could
not be retrieved.
369
ANR2994E ANR3003E
User response: If the message did not indicate which
log directory path caused the problem, look in the
db2diag.log for additional information. Common
problems are a missing directory or permission denied.
ANR2994E
The automatic database backup was

terminated.
Explanation: The operation was terminated because

the device class that is used for the automatic database
backup is not defined.
System action: The automatic database backup is
terminated.
command to define the device class for the automatic
database backup.
ANR2995E

is used for the automatic database
backup.
Explanation: The DELETE DEVCLASS command was

issued to delete a device class that is in use for the
automatic database backup.
ANR2998W
The server log is log full percentage

percent full. The server has cancelled
the oldest transaction in the log.
Explanation: The server log utilization is dangerously

high. In order to prevent the server log from becoming
exhausted, the server has cancelled the oldest
transaction in the log. Once the server activity
associated with this transaction is able to perform
cleanup processing, log space will be freed.
User response: Monitor server activity and log usage.
If possible, delay adding new work to the server load.
ANR3000E
Command: Command can only be issued

on a configuration manager.
Explanation: The command can only be issued on a

server that is a configuration manager.
User response: Issue this command from a

command.
ANR3001E

command to define a new device class for automatic
database backup before deleting this device class.
Explanation: The command can only be issued on a

managed server.
ANR2996I

percent full. The server is no longer
delaying transactions.
Command: Command can only be issued

on a managed server.

User response: Issue this command from a managed
server.
Explanation: The server log utilization was

dangerously high and the server was delaying
transactions. The log utilization is now at a lower level
and the server is no longer delaying transactions.
ANR3002E
Explanation: The profile name specified in the

command is longer than the maximum length allowed.
User response: Continue to monitor server activity

and log usage. If log usage is low enough, you may
consider reducing the amount of space allocated to the
log.
ANR2997W

percent full. The server will delay
transactions by delay time milliseconds.
Explanation: The server log utilization is very high. In

order to prevent the server log from becoming full, the
server will begin delaying transactions by the specified
amount of time.
User response: Monitor server activity and log usage.
If possible, delay adding new work to the server load.
370
Command: Profile name exceeds maximum

length characters.

User response: Select a profile name that does not
exceed the maximum length.
ANR3003E
Command: Profile description exceeds

Explanation: The profile description specified in the

command is longer than the maximum length allowed.
User response: Select a description that does not
exceed the maximum length.
ANR3004E ANR3012I
ANR3004E
Command: The configuration manager

name exceeds maximum length characters.
Explanation: The configuration manager name

specified in the command is longer than the maximum
length allowed.
User response: Select a configuration manager name
that does not exceed the maximum length.
ANR3005E
Command: The server name exceeds

Explanation: The configuration manager name

specified in the command is longer than the maximum
length allowed.
ANR3009E
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
database backup.
System action: Database restore processing terminates.
User response: Install a newer version of the Tivoli
Storage Manager client API and retry this database
restore operation. The client API version currently
available and used for this database restore operation is
not compatible with what was used to originally write
the database backup.
ANR3010W

User response: Select a configuration manager name
that does not exceed the maximum length.
ANR3006E
Command: The configuration refresh

interval value must be between minimum
value and maximum value.

with an invalid refresh interval.
refresh interval value.

User response: To process the command, enter 'Y' to
continue or 'N' to stop the process.
Command: The option option must be

specified.
Explanation: When the command is issued on a a

server that is neither a configuration manager nor a
managed server, the specified option must be supplied.
specified option.
ANR3008I
Database backup was written using

client API: API information.
Explanation: The database backup was written using

the indicated Tivoli Storage Manager Backup/Archive
API.
System action: Database restore processing continues.
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
be issued and the operation will fail.
This command will delete an object that

is associated with one or more profiles
on a configuration manager. Subsequent
configuration refresh processing will
delete the object on managed servers
that subscribe to a profile with which
the object is associated.
Explanation: A command has been entered that will

delete an object from a configuration manager. Since
this object is associated with one or more profiles on a
configuration manager, configuration refresh processing
will delete this object on subscribing managed servers.
ANR3011E
ANR3007E
Database restore not possible, client API

is not compatible: API information.
command: Subscription for profile profile

name was not deleted because one or
more objects could not be discarded.
Explanation: This message was issued because one or

more objects could not be discarded by the indicated
command. A previous message gives an explanation for
each object that could not be discarded.
System action: The system may discard some of the
managed objects that are associated with profile profile
name The subscription itself is not deleted.
determine the action that must be taken before
remaining objects can be discarded. Alternatively, you
can delete the subscription without using the
DISCARDOBJECTS=YES option.
ANR3012I
command: Configuration manager state

set to state.
Explanation: The command has successfully set the

configuration manager state.
System action: The command succeeded.
371
ANR3013W ANR3022E
ANR3013W
command: Configuration manager state

already set to state.
Explanation: The specified state is already in force on

the server.
ANR3017I
command: Profile profile name defined.
Explanation: The command has successfully define a

profile.

ANR3018E
User response: This server is already set to the

specified state. If the state should be set differently,
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.
Explanation: A configuration manager state cannot be

set to OFF is one or more subscription still exist. The
server still has a record of one or more subscriptions to
its profiles.
User response: Use the QUERY SUBSCRIBERS
command to determine which subscriptions still exist.
The DELETE SUBSCRIBER command can be used to
remove the record of these subscriptions. You may
instead want to delete the actual subscription(s) on the
managed server(s). When there are no more
subscriptions recorded on the configuration manager,
you must then delete all the profiles. Once the profiles
have been deleted, you can reissue the command.
ANR3015E
command: One or more profiles still

exist.
Explanation: A configuration manager state cannot be

set to OFF is one or more profiles still exist.
command: Profile profile name already

exists.

User response: Decide on another profile name and
ANR3019I
command: Profile profile name updated.
Explanation: The command has successfully updated

a profile.
ANR3020E
command: Profile profile name not found.
Explanation: The profile specified could not be found.

User response: Check to see if the profile name was
specified correctly on the command. Use the QUERY
PROFILE command to check to see if the profile exists
on the configuration manager. Reissue the command
with the correct profile name.

ANR3021I
User response: Use the QUERY PROFILE command to

determine which profiles still exist on the configuration
manager then use the DELETE PROFILE command.
After all the profiles have been deleted, reissue the
command.
Explanation: The command has successfully copied

the first profile to the newly created second profile. All
the profile associations were also copied.
command: Profile profile name copied to

profile profile name.

ANR3016I
command: Configuration refresh interval

set to interval.

configuration refresh interval to the specified value.
Automatic configuration refresh processing will
immediatly be attempted and then will again be
performed after the specified number of minutes of
elapsed.
372
ANR3022E
command: The profile lock timeout

interval value must be between minimum
value and maximum value.

with an invalid lock timeout interval.
lock timeout interval value.
ANR3023I ANR3032E
ANR3023I
command: Profile profile name locked.
Explanation: The command has successfully locked

the profile. No configuration information can be
propogated to the subscribers of the profile until it is
unlocked.
command: Profile profile name is locked.

command: Profile profile already locked

with timeout interval greater than
interval.
Explanation: An attempt was made to lock the

specified profile. The profile is already locked with a
timeout interval greater than the value specifed.
System action: The profile remains locked with the
original timeout interval.
User response: If you want to lower the timeout
interval, unlock the profile and then lock the profile
again specifying the lower value.
ANR3025I
ANR3028E
Explanation: The specifed command cannot be

performed on a locked profile.
ANR3024W
the managed server requests updates for that profile,

informing the managed server that the profile has been
deleted.
command: Profile profile name unlocked.
Explanation: The command has successfully unlocked

the profile. Configuration information can now be
propogated to the subscribers of the profile.
User response: Unlock the profile using the UNLOCK

PROFILE command and then reissue the command.
ANR3029E
command: Profile name not specified.
Explanation: A profile name must be specifed on this

command using the PROFILE= parameter.
profile name.
ANR3030I
command: Subscription defined for

Explanation: The command has successfully defined a

subscription to the specified profile. A refresh of the
configuration information has been initiated.

ANR3026I
command: Profile profile name deleted.
Explanation: The command has successfully deleted

the profile from the configuration manager.

name already exists.
Explanation: A subscription already exists for the

specified profile.

ANR3027E
ANR3031W

command: One or more subscriptions still

exist to profile profile name.
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
record of one or more subscriptions to the profiles.
User response: Use the QUERY SUBSCRIBERS
command to determine which subscriptions still exist.
Use the DELETE SUBSCRIPTION command on the
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
to delete the profile even if there are subscriptions to
the profile. In this case, messages will be issued when
User response: Check to make sure you specified the

correction profile name, and reissue the command if
needed.
ANR3032E
command: Server name not specified.
Explanation: A server name must be specifed on this

command using the SERVER= parameter. This
identifies the configuration manager.
server name.
373
ANR3033E ANR3041I
ANR3033E
command: Server server is not the

managed server's configuration manager.
Explanation: A server name was specified on the

command which does not match the current
configuration manager. A managed server may only
have one configuration manager.
User response: Reissue the command and leave off
the server parameter. It will default to use the current
configuration manager. A QUERY SUBSCRIPTION will
display the configuration manager currently in use.
ANR3034E
command: Server server cannot be used as

this server's configuration manager.

command which cannot be used as a configuration
manager.
User response: Find out the currect name for the
configuration manager and then reissue the command.
ANR3035I
command: Subscriber subscriber name

deleted.
Explanation: The command has successfully deleted a

subscriber from the record kept in the configuration
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.
ANR3037I
command: Subscription deleted for


subscription for the specified profile. A refresh of the
configuration information has been initiated.
ANR3038E

name not found.
Explanation: A subscription was not found for the

specified profile.
User response: Check to see that the profile name was
specified correctly. Issue the QUERY SUBSCRIPTION
command to check to see which profiles have
subscriptions. Reissue the command with the correct
profile name.
ANR3039E
command: No matching administrators

found in configuration.
Explanation: No administrator definitions were found

on the configuration manager that match the admin(s)
specified on the DEFINE PROFASSOCIATION
command.
User response: Use the QUERY ADMIN command to
check which administrators that are defined on the
server and then reissue to DEFINE
PROFASSOCIATION command.

ANR3040I
ANR3036E
command: Subscriber subscriber name not

found.
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 see that the subscriber
(managed server) name is correction. If you think the
name is correct, perhaps the managed server has not
yet successfully contacted the configuration manager to
inform it that the subscription exists.
command: All administrators associated

with profile profilename.
Explanation: The command has successfully

associated all the administrators with the specified
profile. All administrator definitions will be
automatically propogated to managed servers which
subscribe to the profile. If an administrator is added to
the configuration manager in the future, its definition
will also be automatically propogated to the managed
servers.
ANR3041I
command: Administrator admin associated


associated the administrator with the specified profile.
The administrator definition will be automatically
374
ANR3042W ANR3049I
propogated to managed servers which subscribe to the
profile.
ANR3046W

ANR3042W
command: No additional administrators

associated with profile profilename.
Explanation: No additional administrator were

associated with the profile. The administrator(s)
specified are already associated with the profile.
User response: Use the QUERY ADMIN command to
check which administrators are defined on the server
and then reissue to DEFINE PROFASSOCIATION
command. The QUERY PROFASSOCIATION
FORMAT=DETAILED can be used to see which
administrators are already associated with the profile.
ANR3043E
command: No matching domains found

in configuration.
Explanation: No domain definitions were found on

the configuration manager that match the domain(s)
command.
User response: Use the QUERY DOMAIN command
to check which domains that are defined on the server
and then reissue to DEFINE PROFASSOCIATION
command.
ANR3044I
command: All domains associated with

profile profilename.

associated all the domains with the specified profile.
All domain definitions will be automatically
profile. If a domain is added to the configuration
manager in the future, its definition will also be
automatically propogated to the managed servers.
command: No additional domains

Explanation: No additional domains were associated

with the profile. The domain(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
then reissue to DEFINE PROFASSOCIATION
command. The QUERY PROFASSOCIATION
FORMAT=DETAILED can be used to see which
domains are already associated with the profile.
ANR3047E
command: No matching admin schedules

Explanation: No admin schedule definitions were

found on the configuration manager that match the
admin schedule(s) specified on the DEFINE
User response: Use the QUERY SCHEDULE
TYPE=ADMIN command to check which admin
schedules are defined on the server and then reissue to
DEFINE PROFASSOCIATION command.
ANR3048I
command: All admin schedules


associated all the admin schedules with the specified
profile. All admin schedule definitions will be
subscribe to the profile. If an admin schedule is added
to the configuration manager in the future, its
definition will also be automatically propogated to the
managed servers.

ANR3049I

ANR3045I
command: Domain domain associated with


associated the domain with the specified profile. The
domain definition will be automatically propogated to
managed servers which subscribe to the profile.
command: Admin Schedule admin schedule


associated the admin schedule with the specified
profile. The admin schedule definition will be
subscribe to the profile.
375
ANR3050W ANR3057I
ANR3050W
command: No additional admin

scheduless associated with profile
profilename.
Explanation: No additional admin schedules were

associated with the profile. The admin schedule(s)
DEFINE PROFASSOCIATION command. The QUERY
PROFASSOCIATION FORMAT=DETAILED can be
used to see which admin schedules are already
ANR3051E
command: No matching scripts found in

configuration.
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 SCRIPT command to
check which scripts that are defined on the server and
command.
ANR3054W
Explanation: No additional scripts were associated

with the profile. The script(s) specified are already
User response: Use the QUERY SCRIPT command to
check which scripts are defined on the server and then
reissue to DEFINE PROFASSOCIATION command. The
QUERY PROFASSOCIATION FORMAT=DETAILED
can be used to see which scripts are already associated
with the profile.
ANR3055E
command: All scripts associated with

command: No matching client option sets

Explanation: No client option set definitions were

found on the configuration manager that match the
client option set(s) specified on the DEFINE
User response: Use the QUERY CLOPTSET command
to check which client option sets that are defined on
the server and then reissue to DEFINE
ANR3056I
ANR3052I
command: No additional scripts

command: All client option sets


associated all the scripts with the specified profile. All
script definitions will be automatically propogated to
managed servers which subscribe to the profile. If a
script is added to the configuration manager in the
future, its definition will also be automatically
propogated to the managed servers.

associated all the client option sets with the specified
profile. All client option set definitions will be
subscribe to the profile. If a client option set is added
definition will also be automatically propogated to the
managed servers.
ANR3053I
command: Script script associated with


associated the script with the specified profile. The
script definition will be automatically propogated to
ANR3057I
command: Client option set client option

set associated with profile profilename.

associated the client option set with the specified
profile. The client option set definition will be
376
ANR3058W ANR3065I
ANR3058W
command: No additional client option

sets associated with profile profilename.
ANR3062W
command: No additional servers

Explanation: No additional client option sets were

associated with the profile. The client option set(s)
Explanation: No additional servers were associated

with the profile. The server(s) specified are already


User response: Use the QUERY CLOPTSET command

to check which client option sets are defined on the
server and then reissue to DEFINE
PROFASSOCIATION command. The QUERY
used to see which client option sets are already
User response: Use the QUERY SERVER command to

check which servers are defined on the server and then
reissue to DEFINE PROFASSOCIATION command. The
QUERY PROFASSOCIATION FORMAT=DETAILED
can be used to see which servers are already associated
with the profile.
ANR3063E
ANR3059E
command: No matching servers found in

configuration.
Explanation: No server definitions were found on the

configuration manager that match the server(s)
command.
User response: Use the QUERY SERVER command to
check which servers that are defined on the server and
command.
Explanation: No server group definitions were found

on the configuration manager that match the server
group(s) specified on the DEFINE PROFASSOCIATION
command.
User response: Use the QUERY SERVERGROUP
command to check which server groups that are
defined on the server and then reissue to DEFINE
ANR3064I
ANR3060I
command: All servers associated with

command: No matching server groups

command: All server groups associated


associated all the servers with the specified profile. All
server definitions will be automatically propogated to
server is added to the configuration manager in the
propogated to the managed servers.

associated all the server groups with the specified
profile. All server group definitions will be
subscribe to the profile. If a server group is added to
will also be automatically propogated to the managed
servers.
ANR3061I
command: Server server associated with


associated the server with the specified profile. The
server definition will be automatically propogated to
ANR3065I
command: Server group server group


associated the server group with the specified profile.
The server group definition will be automatically
profile.
377
ANR3066W ANR3075I
ANR3066W
command: No additional server groups

Explanation: No additional server groups were

associated with the profile. The server group(s)
User response: Use the QUERY SERVERGROUP
command to check which server groups are defined on
the server and then reissue to DEFINE
PROFASSOCIATION command. The QUERY
used to see which server groups are already associated
with the profile.
User response: Use the QUERY PROFASSOCIATION

command to check which domains are associated with
the profile and then reissue to DELETE
ANR3071I

all domains associations from the specified profile. This
will automatically delete these domains from the
managed servers that are subscribed to this profile.
ANR3072I
ANR3067E

associated with profile profile.
Explanation: No matching administrator definitions

are associated with the specified specified profile.
command to check which administrators are associated
with the profile and then reissue to DELETE
ANR3068I
command: All administrator associations

deleted from profile profilename.

all administrators associations from the specified
profile. This will automatically delete these
administrators from the managed servers that are
subscribed to this profile.
ANR3069I
command: Administrator association

admin deleted from profile profilename.
command: All domain associations

command: Domain association domain


domain association from the specified profile. This will
automatically delete this domain from the managed
servers that are subscribed to this profile.
ANR3073E

Explanation: No matching admin schedule definitions

command to check which admin schedules are
associated with the profile and then reissue to DELETE
ANR3074I
command: All admin schedule

associations deleted from profile
profilename.

an administrator association from the specified profile.
This will automatically delete this administrator from
the managed servers that are subscribed to this profile.

all admin schedules associations from the specified
profile. This will automatically delete these admin
schedules from the managed servers that are subscribed
to this profile.
ANR3070E
command: No matching domains

Explanation: No matching domain definitions are

associated with the specified specified profile.
378
ANR3075I
command: Admin schedule association

admin schedule deleted from profile
profilename.

an admin schedule association from the specified
profile. This will automatically delete this admin
ANR3076E ANR3085E
schedule from the managed servers that are subscribed
to this profile.
profile. This will automatically delete these client

option sets from the managed servers that are
subscribed to this profile.

ANR3076E
command: No matching scripts associated

with profile profile.
ANR3081I
Explanation: No matching script definitions are

command to check which scripts are associated with
ANR3077I
command: All script associations deleted

from profile profilename.

all scripts associations from the specified profile. This
will automatically delete these scripts from the
ANR3078I
command: Script association script deleted


script association from the specified profile. This will
automatically delete this script from the managed
servers that are subscribed to this profile.
ANR3079E

client option set association from the specified profile.
This will automatically delete this client option set from
ANR3082E
command: No matching servers

Explanation: No matching server definitions are

command to check which servers are associated with
ANR3083I
command: All server associations deleted


all servers associations from the specified profile. This
will automatically delete these servers from the

Explanation: No matching clent option set definitions

command to check which client option sets are
ANR3080I
command: Client option set association

client option set deleted from profile
profilename.
command: All client option set

associations deleted from profile
profilename.

all client option sets associations from the specified

ANR3084I
command: Server association server


server association from the specified profile. This will
automatically delete this server definition from the
ANR3085E

Explanation: No matching server group definitions are

379
ANR3086I ANR3095W
command to check which server groups are associated
ANR3086I
command: All server group associations


all server groups associations from the specified profile.
This will automatically delete these server groups from
ANR3087I
command: Server group association server

group deleted from profile profilename.

server group association from the specified profile. This
will automatically delete this server group from the
ANR3088W
This command will cause the deletion

of objects on any managed server
subscribed to profile profile name.
Explanation: A DELETE PROFASSOCIATION

command option has been entered. This action will not
only delete the association from the profile, but it will
also result in the deletion of managed object(s) on any
managed server subscribing to this profile. The deletion
of these objects will occurr during the next
configuration refresh for that managed server.
up. If the problem persists, consult with your network

administrator.
ANR3090E
command: Server server name is not a

Explanation: The specified command failed because it

tried to contact the specified server, and discovered that
the server is not a configuration manager.
correct configuration manager name.
ANR3091E
command: Profile list not specified.
Explanation: The specified command failed because

you did not specify a profile list on the command.
profile list.
ANR3092I
command: Subscriber notification

processing has begun.
Explanation: A NOTIFY SUBSCRIBER process has

begun. The managed server(s) are being contacted,
asking them to immediately perform a configuration
refresh.
command succeeded.
ANR3093I
command: No matching profiles or

subscriptions were found.

Explanation: No subscriptions were found for the

profiles specified. Either the profiles do not exist, or
there are no subscriptions to the profiles.
User response: To process the DELETE

PROFASSOCATION command, enter 'Y' to continue or
'N' to stop the command.

ANR3089E
command: Command failed Server-to-server communication error

with server server name.
Explanation: The specified command failed while

attempting to communicate with the indicated server.
User response: Verify that the indicated server name
is correctly defined. Try reissuing the command. Use
the server PING command to see if the other server is
380
User response: Use the QUERY PROFILE and QUERY

SUBSCRIBER command to determine which profiles
exist and which profiles have subscribers. Reissue the
command specifying the correct profile name(s).
ANR3095W
Failure updating the database volume

history information with the volumes
used to perform this restore operation.
Explanation: At the end of database restore processing

for a point in time operation, the server database will
be updated to show the volumes that were used to
restore the database. This is done so that a future
restore has knowledge of this database backup and will
ANR3096I ANR3155E
be able to use this if it is the best possible candidate for
a future operation. Because the server failed to update
this information, a future restore database operation
may not select the best possible database backup to use
for the operation.
User response: Examine the activity log for other

messages that may explain why the configuration
refresh failed. The refresh will attempted again when
the configuration refresh interval is reached.
System action: Database restore processing completes.
ANR3152I
User response: Once the server is restarted after the

database restore is completed, a BACKUP DB
TYPE=FULL should be performed as soon as possible
and the volume history information backed up after
this backup is completed. This will set a new best
possible restore point if a future restore operation is
needed. If you use the Disaster Recovery Manager
feature to track database backup volume physical
location you will have to manually track the location of
the database backup volumes which were not updated.
Explanation: Configuration refresh processing has

started. A server-to-server session was opened to
receive configuration information from the
configuration manager. Updates will be sent for objects
associated with any subscribed-to profiles.
System action: Refresh processing continues.
ANR3153I
ANR3096I
The volumes used to perform this

restore operation were successfully
recorded in the server volume history.
Explanation: At the end of database restore processing

for a point in time operation, the server database will
be updated to show the volumes that were used to
restore the database. This is done so that a future
restore has knowledge of this database backup and will
be able to use this if it is the best possible candidate for
a future operation.
Configuration refresh started with

configuration manager server name.
Configuration refresh ended

successfully with configuration manager
server name.
Explanation: Configuration refresh processing ended

successfully. All updates have been made to managed
objects associated with any subscribed-to profiles.
System action: Server processing continues. The next
automatic refresh will start when the configuration
refresh interval is reached.
System action: Database restore processing completes.

ANR3154E

ANR3150E
Configuration refresh failed with

configuration manager server name. Will
retry in minutes minutes.
Explanation: While receiving configuration

information from the specified configuration manager,
processing failed because of a communications error.
configuration refresh process was stopped and will be
automatically retried.
User response: Perhaps the configuration manager is
not active. If the problem continues, contact the
administrator for the configuration manager, or contact
a network administrator. The refresh will automatically
retry several times and then give up until the
configuration refresh interval is reached again.
ANR3151E
Configuration refresh failed with

configuration manager server name.

processing failed.
Communication error on notify to

managed server server name. Will retry in
minutes minutes.
Explanation: While attempting a notify subscriber

request to the specified managed server, a
communications error was detected.
System action: Server operation continues. The notify
subscriber request was stopped and will be
automatically retried.
User response: Perhaps the managed server is not
active. If the problem continues, contact the
administrator for the managed server, or contact a
network administrator. The notify subscriber request
will automatically retry several times and then give up.
ANR3155E
Error attempting notify subscribers

request to managed server server.
System action: Server operation continues. The notify

subscriber request failed.
User response: Examine the activity log for other
messages that may explain why the notify subscriber
request failed.

configuration refresh process was stopped.
381
ANR3156E ANR3163E
ANR3156E
Configuration refresh failed for

managed server server name.
Explanation: While sending configuration information

to the specified managed server, processing failed.
situation, on the managed server delete the

subscription to the profile and define the subscription
again. This will cause the managed server to be
refreshed at the configuration manager's current level.

configuration refresh process ended.
ANR3160E
User response: Examine the activity log of both the

managed server and the configuration manager for
other messages that may explain why the configuration
refresh failed. The refresh will attempted again by the
managed server when its configuration refresh interval
is reached.

to the specified managed server, a communication error
occurred when trying to receive confirmation from the
managed server that information was processed
successfully.
ANR3157I
Configuration refresh started for

managed server server name.
Explanation: Configuration refresh processing has

started. A server to server session was opened by the
managed server to receive configuration information
from the configuration manager. Updates will be sent
for objects associated with any subscribed-to profiles.

Configuration refresh processing ended.
User response: Determine if communication can be
established with the managed server by using the
server PING command. Use the NOTIFY
SUBSCRIBERS command to force the configuration
refresh to retry.
ANR3161E
System action: Refresh processing continues.

ANR3158I
Configuration refresh ended

successfully for managed server server
name.
Explanation: Configuration refresh processing ended

successfully. All updates have been made to managed
objects associated with any subscribed-to profiles on
the managed server.
ANR3159E
Managed server server name has newer

version for profile profile name.

to the specified managed server, it has been detected
that the managed server has a newer version of
configuration information for the specified profile than
does the configuration manager. This condition can
happen if the configuration manager's database has
been restored to an earlier point in time. Another
possibility is that the profile was deleted on the
configuration manager and a new profile by the same
name was created.
System action: Server operation continues. No
configuration information for this profile will be sent to
the managed server until this condition is corrected.
User response: Before correcting the situation, you
may want to use QUERY PROFILE to examine the
profile associations defined on both the configuration
manager and the managed server. To correct the
382
Unable to receive confirmation of

refresh from managed server server name.
Premature end of configuration refresh

for managed server server server name.

to the specified managed server, processing ended
prematurely because of on error.
User response: Examine the activity log on the
managed server for any error messages that might
explain why the refresh failed. Use the NOTIFY
SUBSCRIBERS command on the configuration manager
to force the configuration refresh to retry.
ANR3162E
Managed server server name aborted

configuration refresh processing due to
a low memory condition.

prematurely because of a low memory condition on the
managed server.
User response: Make more memory available to the
managed server.
ANR3163E

an internal error.

prematurely because of an internal error on the
managed server.
ANR3164E ANR3171E
User response: Examine the activity log of the
managed server for messages that explain the cause of
the internal error.
ANR3164E

a lock conflict.

prematurely because of a lock conflict on the managed
server.
User response: Use the NOTIFY SUBSCRIBERS
command to retry the configuration refresh. If this
problem persists, contact your service representative.
ANR3165E

a protocol error.

prematurely because of a protocol error detected on the
managed server.
User response: Use the NOTIFY SUBSCRIBERS
command to retry the configuration refresh. If this
User response: Notify the administrator of the

ANR3168E

processing ended prematurely because of an internal
error on the configuration manager.
User response: Examine the activity log of the
configuration manager for messages that explain the
cause of the internal error.
ANR3169E

User response: Retry the configuration refresh by
issuing the SET CONFIGREFRESH command (using
the current refresh interval value). If this problem
Unable to receive configuration refresh

information from server server name.

processing ended prematurely because of a
communications error.
User response: Use the server PING command to see
if the configuration manager can be reached. If the
problem persists, contact your network administrator.
ANR3167E
Configuration manager server name

aborted configuration refresh processing
due to a low memory condition.

processing ended prematurely because of a low
memory condition on the configuration manager.

due to a lock conflict.

information from the specified managed server,
processing ended prematurely because of a lock conflict
on the configuration manager.
ANR3170E
ANR3166E

due to an internal error.

due to a protocol error.

processing ended prematurely because of a protocol
error detected on the configuration manager.
User response: Retry the configuration refresh by
issuing the SET CONFIGREFRESH command (using
the current refresh interval value). If this problem
ANR3171E
Configuration refresh with

configuration manager server name had
to skip processing for one or more
objects.

it became necessary to skip the creation or deletion of
one or more objects.
383
ANR3172W ANR3177W
User response: Examine the managed server's activity
log for earlier messages that identfy the object, and
take the actions identified in those messages.
Configuration refresh processing will not complete
successfully until the problem is clear up.
ANR3172W
Subscription exists for deleted profile

profile name.

information from the configuration manager, it has
been detected that the managed server has a
subscription to an profile that no longer exists on the
configuration manager. This condition can exist because
the profile was deleted with FORCE=YES on the
configuration manager. This out-of-synch condition can
also occur because one of the server's database was
regressed because of a restore db.
User response: The DELETE SUBSCRIPTION
command is used to correct this situation. You need to
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
the managed server as local objects, specify
DISCARD=NO.
ANR3173E
Server has newer version for profile

profile name than the configuration
manager server name.

information from the configuration manager, it has
been detected that the managed server has a newer
version of configuration information for the specified
profile than does the configuration manager. This
condition can happen if the configuration manager's
database has been restored to an earlier point in time.
Another possibility is that the profile was deleted on
the configuration manager with FORCE=YES and a
new profile by the same name was created.
configuration information for this profile will be sent to
the managed server until this condition is corrected.
User response: Before correcting the situation, you
may want to use QUERY PROFILE to examine the
profile associations defined on both the configuration
manager and the managed server. To correct the
situation, on the managed server delete the
subscription to the profile and define the subscription
again. This will cause the managed server to be
refreshed at the configuration manager's current level.
384
ANR3174E
Communication error with managed

server server name.
Explanation: While receiving or sending information

to the specified managed server, a communcations error
was experienced.
operation in progress fails.
User response: If this error happens often, consult
with your network administrator. Also check to see that
the managed server is up.
ANR3175W
Profile profile name is locked and could

not be refreshed from configuration
manager server name.
Explanation: While receiving configuration refresh

information from the specified managed server, it was
detected that a subscribed-to profile is locked.
System action: Server operation continues. Refresh
processings skips over this profile.
User response: Normally, the profile will later be
unlocked automatically, or by an administrator. If you
think that it should not be locked, have ask the
configuration manager admin to unlock it using the
UNLOCK PROFILE command.
ANR3176W
Profile profile name is locked and could

not be refreshed for managed server
server name.
Explanation: While sending configuration refresh

information to the specified managed server, it was
detected that a subscribed-to profile is locked.
processings skips over this profile.
User response: If the profile should no longer be
locked, use the UNLOCK PROFILE command to
unlock it.
ANR3177W
Server level does not support object in

Explanation: While receiving configuration refresh

information from the configuration manager, an object
was received that is not supported on this managed
server.
processings skips over this object. The refresh for the
profile fails.
User response: The configuration manager is at a
higher release level than the managed server. The
managed server subscribed to a profile that contains an
unsupported object. Delete the subscription to this
profile until service can be applied to the server to
bring it to a higher release level.
ANR3178E ANR3202E
ANR3178E
Communication error on session session

number with replication server server
name.

to the specified replication server, a communcations
error was experienced.
the replication server is up.
ANR3179E
Server server name does not support

replication or is not initialized for
replication.
Explanation: In response to a REPLICATE command,

the server attempted to establish a connection to the
replication target. But the target server does not
support replication, or has not been properly initialized
for replication.
replication fails.
User response: Make sure the replication target is at
the correct maintenance level and verify that the
globally unique ID (GUID) of the target server is
properly set. Use the tivguid utility to set the GUID if
not properly set.
ANR3180E
Replication cannot occur for node node

name, file-space filespace name and copy
type copytype name because the target
replication server is not set.
Explanation: In response to a REPLICATE NODE

command, the server was unable to establish a
connection to a target replication server because a
target server was not defined.
System action: Replication for the node and file space
is skipped. However, replication continues for other
nodes and file spaces.
User response: To replicate data, the target replication
server must be defined. Issue the SET REPLSERVER
command to set the target replication server name. The
name specified in the SET REPLSERVER command
must be associated with a valid server definition.
ANR3181E
Replication server server name has the

same replication key as this server.
Explanation: During replication initialization, the

server detected that the replication key of the target
server is the same as this server. Each server must have
a unique replication key.
System action: Replication to the specified server is
stopped.
User response: Issue the SET REPLSERVER command

to specify a different server for the target of the
replication.
ANR3199I
Server halt for stage stage initiated at

time.
Explanation: The server HALT processing is being

performed and each stage is reported with the time
when that stage was initiated.
User response: This message may not be logged to the
activity log. It is provided for informational purposes
only. The stages reported are for informational
purposes and only to denote progress. The sequence
and actual stages to be performed during halt may
vary and as such will cause this not to always report in
the same fashion. The primary consideration is that the
INIT stage and the COMPLETE stage can be used to
calculate the time used to halt the server. These
messages are only displayed if the halt command is
issued with the verbose parameter such as: "HALT
VERBOSE".
ANR3200E
command: Command cannot be executed

- domain domain name is a managed
object.
Explanation: The specified command cannot be

executed because it would alter the contents of the
indicated managed domain. With the exception of
policy set activation, a managed domain can only be
modified using configuration information propagated
from the configuration manager.
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.
User response: To delete this object, you can delete
the subscription to the configuration profiles with
which domain domain name is associated.
ANR3202E
command: Domain domain name is a

managed object and cannot be updated.
Explanation: The indicated domain is a managed

object and cannot be updated on the managed server.
385
ANR3203E ANR3210E
User response: To update this object, you can delete
ANR3203E
command: Policy set set name in domain

domain name is a managed object and
cannot be deleted.
Explanation: The indicated policy set is a managed

ANR3204E
command: Policy set set name in domain

domain name is a managed object and
cannot be updated.
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

managed object and cannot be deleted on the managed
server.
ANR3208E
command: Archive copy group group name

Explanation: The indicated policy set is a managed

Explanation: The indicated archive copy group is a

server.




ANR3205E
command: Management class class name in

domain domain name, policy set set name
is a managed object and cannot be
deleted.
ANR3209E
command: Backup copy group group name

Explanation: The indicated management class is a

server.
Explanation: The indicated backup copy group is a

managed object and cannot be updated on the
managed server.




ANR3206E
command: Management class class name in

domain domain name, policy set set name
is a managed object and cannot be
updated.
ANR3210E
command: Archive copy group group name

Explanation: The indicated management class is a

managed server.
Explanation: The indicated archive copy group is a

managed server.




386
ANR3211E ANR3218E
ANR3211E
command: Client schedule schedule name

in domain domain name is a managed
object and cannot be deleted.
Explanation: The indicated client schedule is a

server.
ANR3212E
command: Client schedule schedule name

in domain domain name is a managed
object and cannot be updated.
Explanation: The indicated client schedule is a

managed server.
ANR3213E
command: Administrative schedule

schedule name is a managed object and
cannot be deleted.
Explanation: The indicated administrative schedule is

a managed object and cannot be deleted on the
managed server.
ANR3215W
Explanation: This message is issued while processing

a DELETE SUBSCRIPTION command with
DISCARDOBJECTS=YES. The indicated domain cannot
be discarded on the managed server because it still
contains one or more nodes.
System action: Domain domain name is not deleted.
Policy sets, management classes, copy groups, and
client schedules belonging to this domain are also not
deleted.
User response: Before this domain can be deleted,
nodes in the domain must be removed or assigned
another domain.
ANR3216W
ANR3214E
command: Administrative schedule

schedule name is a managed object and
cannot be updated, except to activate or
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
schedule.
which the object is associated.
Managed administrative schedule

schedule name is active and cannot be
discarded.

DISCARDOBJECTS=YES. The indicated administrative
schedule cannot be discarded on the managed server
because it is in the active state.
System action: Administrative schedule schedule name
is not deleted.
User response: Before this administrative schedule can
be deleted, it must be deactivated using the Update
Schedule command.
ANR3217E

Managed domain domain name contains

at least one node and cannot be
discarded.
command: Administrator administrator

name is a managed object and cannot be
removed.
Explanation: The indicated administrator is a

managed object and cannot be removed on the
managed server.
User response: To remove this administrator, you can
delete the subscription to the configuration profiles
with which the object is associated.
ANR3218E

updated.

managed server.
User response: To update this administrator, you can
387
ANR3219E ANR3226E
ANR3219E

renamed.

managed object and cannot be renamed on the
managed server.
User response: To rename this administrator, you can
ANR3220E

name is a managed object - authority
cannot be granted.

managed object. Authority cannot be granted to this
administrator on the managed server.
User response: To grant authority to this
administrator, you can delete the subscription to the
configuration profiles with which the object is
associated.
ANR3221E

name is a managed object - authority
cannot be revoked.

managed object. Authority of this administrator cannot
be revoked on the managed server.
User response: To revoke authority of this
administrator, you can delete the subscription to the
associated.
ANR3222W
Managed administrator administrator

name is the only system administrator
and cannot be discarded.

DISCARDOBJECTS=YES. The indicated administrator
cannot be discarded on the managed server because it
is the only system administrator.
System action: Administrator administrator name is not
deleted.
User response: Before this administrator can be
388
deleted, another administrator must be given system

authority.
ANR3223W

name is currently accessing the server

DISCARDOBJECTS=YES. The indicated administrator
cannot be discarded on the managed server because it
has an active session with the server.
System action: Administrator administrator name is not
deleted.
User response: Quit or cancel all sessions for this
administrator before discarding the administrator
definition.
ANR3224E
command: Command script command

script name is a managed object and
cannot be deleted.
Explanation: The indicated command script is a

server.
User response: To delete this script, you can delete the
subscription to the configuration profiles with which
the object is associated.
ANR3225E

cannot be updated.

managed server.
User response: To update this script, you can delete
ANR3226E

cannot be renamed.

managed object and cannot be renamed on the
managed server.
User response: To rename this script, you can delete
ANR3227E ANR3235E
ANR3227E
command: Option set optionset name is a

ANR3232E
command: Server group group name is a

managed object and cannot be renamed.
Explanation: The indicated option set is a managed

Explanation: The indicated server group is a managed

object and cannot be renamed on the managed server.


User response: To delete this option set, you can

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

User response: To update this option set, you can
ANR3229E

- option set optionset name is a managed
object.

executed because it would alter the contents of the
indicated managed option set.
ANR3230E


User response: To delete this server group, you can
ANR3231E


User response: To update this server group, you can
ANR3233E

- server group group name is a managed
object.

executed because it would alter the membership of the
indicated managed server group.
ANR3234E
command: Server server name is a

Explanation: The indicated server is a managed object

and cannot be deleted on the managed server.
ANR3235E
command: Server server name is a

managed object - one or more specified
attributes cannot be updated.
Explanation: Because the indicated server is a

managed object, certain attributes cannot be updated
on the managed server. These attributes are:
SERVERPASSWORD, HLADDRESS, LLADDRESS,
COMMMETHOD, DESCRIPTION, URL, and
ALLOWREPLACE.
User response: You can restrict the update to
attributes that can be updated on the managed server.
For example, the PASSWORD, NODENAME,
FORCESYNC, and DELGRACEPERIOD attributes can
be updated, even if the server is a managed object.
Alternatively, you can delete the subscription to the
associated, so that the server is no longer a managed
object.
389
ANR3236W ANR3350W
ANR3236W
Server server name is currently in use


DISCARDOBJECTS=YES. The indicated server cannot
be discarded on the managed server because server
name is in use. This could occur if the managed server
has an active connection to server name or if the
managed server has a device class with
DEVTYPE=SERVER that refers to server name.
System action: Server server name is not deleted.
User response: Before server name can be deleted, the
managed server must not have a connection to that
server and the managed server cannot have any
device-class references to that server.
ANR3237W
Server server name is the event server


DISCARDOBJECTS=YES. The indicated server cannot
be discarded because it is the event server for the
managed server.
User response: Look in the device configuration file

for errors, and look at the activity log for any previous
error messagess that might help determine the location
of these errors in the device configuration file.
ANR3240W
Explanation: This message is issued when a the

NUMSTREAM parameter is being specified with a
value higher than the number of drives available to the
device class.
User response: The value will be updated as
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
performed using the number of online drives as the
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.
ANR3241W
System action: Server server name is not deleted.

DELETE EVENTSERVER command must be used to
remove the event server reference to server name.
ANR3238E
command: This object cannot be renamed

because it is associated with one or
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
configuration profiles. Associated objects cannot be
renamed because the enterprise configuration facility
does not support renaming of objects.
User response: If you must change the object name
you can delete the object, define it with a new name,
and then define a profile association to the new object
(unless a wildcard profile association already exists).
This will cause the object to be deleted and re-defined
on managed servers with subscriptions to the profiles
with which this object is associated.
ANR3239E
Error rc while creating device class device

class.
Explanation: This message is issued when a device

class could not be created, because there was an error
while processing the device configuration file.
390
The device class device class only has

number of drives drives while the number
of streams requested is number of streams.
The value specified for server option

option 1 is ignored due to the setting of
option option 2.
Explanation: The value specified for the first option is

ignored because the second option takes precedence.
System action: The default value of the option is
used. Server operation continues.
User response: Modify the values for one or both of
the server options so that they no longer conflict.
Restart the server.
ANR3350W
Locally defined domain domain name

contains at least one node and cannot be
replaced with a definition from the
Explanation: During configuration refresh processing

the indicated locally defined domain could not be
replaced with a definition from the configuration
manager. The domain definition was not replaced
because the domain still contains one or more assigned
nodes.
System action: Refresh processing continues, but this
domain is not replaced. The system will attempt to
replace the local domain during later configuration
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
domain. After the domain definition has successfully
been propagated from the configuration manager,
reassign the nodes to the new domain. Alternatively, if
you want to prevent further attempts to replace the
ANR3351W ANR3356I
local domain definition during configuration refresh
processing, delete the subscription to the profiles with
ANR3351W
Managed domain domain name contains

at least one node and cannot be deleted
during configuration refresh processing.
Explanation: During configuration refresh processing,

the enterprise configuration facility attempted to
remove the indicated domain because it has been
deleted from the configuration manager or because the
profile association no longer exists. The domain could
not be deleted on the managed server because it still
contains one or more nodes.
domain is not deleted. The system will attempt to
delete the domain during later configuration refresh
operations.
User response: Assign nodes in this domain to
another domain. Alternatively, you can delete the
subscription to the profiles with which domain domain
name is associated.
ANR3352I
Locally defined domain domain name

replaced during configuration refresh
processing.

a local domain definition was replaced with a
definition from the configuration manager. The system
also deleted all policy sets, management classes, copy
groups, and client schedules belonging to the locally
defined domain and added definitions from the
ANR3353I
Managed domain domain name deleted


the indicated managed domain was removed from the
managed server. This occurred either because the
domain has been deleted from the configuration
manager or because the profile association no longer
exists. The system also deleted all policy sets,
management classes, copy groups, and client schedules
belonging to the managed domain.
ANR3354W
Locally defined administrative schedule

replaced with a definition from the

the indicated locally defined administrative schedule
could not be replaced with a definition from the
configuration manager. The schedule definition was not
replaced because the schedule is in the active state.
administrative schedule is not replaced. The system
will attempt to replace the local administrative
schedule during later configuration refresh operations.
User response: If you want this administrative
schedule to be replaced with the schedule definition
from the configuration manager, deactivate the local
schedule using the Update Schedule command. After
the administrative schedule definition has successfully
been propagated from the configuration manager, you
can activate the new schedule. Alternatively, if you
want to prevent further attempts to replace the local
schedule definition during configuration refresh
which the schedule name is associated.
ANR3355W

deleted during configuration refresh
processing.

remove the indicated administrative schedule because it
has been deleted from the configuration manager or
because the profile association no longer exists. The
schedule could not be deleted on the managed server
because the schedule is in the active state.
schedule is not deleted. The system will attempt to
delete the administrative schedule during later
configuration refresh operations.
User response: If you want this administrative
schedule to be deleted in accordance with changes that
have been made on the configuration manager,
deactivate the managed schedule using the Update
Schedule command. Alternatively, if you want to
prevent further attempts to delete the managed
schedule definition during configuration refresh
which the schedule name is associated.
ANR3356I
Locally defined administrative schedule

schedule name replaced during
configuration refresh processing.

a local administrative schedule definition was replaced
with a definition from the configuration manager.
391
ANR3357I ANR3363W
ANR3357I

schedule name deleted during

the indicated managed administrative schedule was
removed from the managed server. This occurred either
because the schedule has been deleted from the
configuration manager or because the profile
association no longer exists.
ANR3358W
Locally defined administrator

administrator name is the only system
administrator and cannot be replaced
with a definition from the configuration
manager.

the indicated locally defined administrator could not be
replaced with a definition from the configuration
manager. The administrator definition was not replaced
because it is the only system administrator and the
definition from the configuration manager does not
include system authority.
administrator definition is not replaced. The system
will attempt to replace the local administrator
definition during later configuration refresh operations.
User response: If you want this administrator
definition to be replaced with a definition from the
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
which administrator administrator name is associated.
ANR3359W
Managed system administrator

administrator and cannot be deleted

remove the indicated administrator because it has been
profile association no longer exists. The administrator
could not be deleted on the managed server because it
is the only system administrator.
administrator is not deleted. The system will attempt to
delete the administrator during later configuration
refresh operations.
User response: Grant system authority to another
administrator. Alternatively, you can delete the
subscription to the profiles with which administrator
392
administrator name is associated.

ANR3360W
Managed system administrator

administrator - authority cannot be
revoked during configuration refresh
processing.

the enterprise configuration facility attempted to revoke
authority for the indicated administrator because
authority has been revoked on the configuration
manager. The authority of the administrator could not
be revoked on the managed server because this is the
only system administrator.
System action: Refresh processing continues, but
authority is not revoked for this administrator. The
system will attempt to revoke administrator during
later configuration refresh operations.
User response: Grant system authority to another
administrator. Alternatively, you can delete the
subscription to the profiles with which administrator
administrator name is associated.
ANR3361I
Locally defined administrator

administrator name replaced during

a local administrator definition was replaced with a
definition from the configuration manager.
ANR3362I

name deleted during configuration
refresh processing.

the indicated managed administrator was removed
from the managed server. This occurred either because
the administrator has been deleted from the
ANR3363W

name is currently accessing the server
and cannot be deleted during

remove the indicated administrator because it has been
profile association no longer exists. The administrator
ANR3364W ANR3371W
could not be deleted on the managed server because it
currently has an active session with the server.

administrator is not deleted. The system will attempt to
delete the administrator during later configuration
refresh operations.
ANR3367I
User response: Quit or cancel all sessions for the

indicated administrator. Alternatively, you can delete
the subscription to the profiles with which
administrator administrator name is associated.
Locally defined option set option set name

processing.

a local option set definition was replaced with a
ANR3364W
Administrator administrator name has

been removed. This administrator has
defined or updated administrative
schedules that will fail when executed.
Explanation: This message is issued during

configuration refresh processing or as a result of a
DELETE SUBSCRIPTION command with the
DISCARDOBJECTS=YES option. The indicated
managed administrator was removed from the server,
but this administrator owns one or more administrative
schedules. These schedules will fail when executed in
the future because they do not belong to a valid
administrator.
System action: The indicated administrator was
removed.
ANR3368I
Managed option set option set name

processing.

the indicated managed option set was removed from
the managed server. This occurred either because the
option set has been deleted from the configuration
exists.
ANR3369I
Locally defined server group group name

processing.

OR an SQL SELECT statement on the

a local server group definition was replaced with a
ANR3365I
ANR3370I
Locally defined command script

command script name replaced during

a local command script definition was replaced with a
ANR3366I
Managed command script command script

name deleted during configuration
refresh processing.

the indicated managed command script was removed
from the managed server. This occurred either because
the script has been deleted from the configuration
exists.

Managed server group group name
processing.

the indicated managed server group was removed from
the managed server. This occurred either because the
server group has been deleted from the configuration
exists.
ANR3371W
Server group group name cannot be

defined during configuration refresh
processing because a server already
exists with this name.

the enterprise configuration facility attempted to define
the indicated server group on a managed server. The
393
ANR3372I ANR3377W
server group could not be defined because a server
definition with the same name already exists on the
managed server.
server group is not defined. The system will attempt to
define the server group during later configuration
refresh operations.
User response: You can delete the subscription to the
profile with which the indicated server group is
associated or delete the conflicting server definition on
the managed server. Alternatively, you can rename the
server group on the configuration manager, after first
deleting the profile association for that server group.
ANR3372I
Locally defined server server name

processing.

a local server definition was replaced with a definition
from the configuration manager.
ANR3373I
Server server name deleted during


the definition for managed object server name was
removed from the managed server. This occurred either
because server name has been deleted from the
indicated server could not be deleted on the managed

server because server name is in use. This could occur if
the managed server has an active connection to server
name or if the managed server has a device class with
DEVTYPE=SERVER that refers to server name.
server definition is not deleted. The system will attempt
to delete the server during later configuration refresh
operations.
managed server must not have a connection to that
server and the managed server cannot have any
device-class references to that server.
ANR3376W
Server server name is the event server

and cannot be deleted during

remove the indicated server definition because it has
been deleted from the configuration manager or
indicated server could not be deleted on the managed
server because it is the event server for the managed
server.
server definition is not deleted. The system will attempt
to delete the server during later configuration refresh
operations.
DELETE EVENTSERVER command must be used to
remove the event server reference to server name.

ANR3374I
Server group group name replaced with

server server name during configuration
refresh processing.

a server group definition was replaced with a server
definition from the configuration manager. The server
has the same name as the deleted server group.
ANR3375W
Server server name is currently in use

cannot be deleted during configuration
refresh processing.

remove the indicated server definition because it has
been deleted from the configuration manager or
394
ANR3377W
Replacement of local server server name

with a definition from the configuration
manager is not allowed.

replace the indicated server definition with a definition
from the configuration manager. This operation could
not be performed because ALLOWREPLACE=NO for
the indicated server.
server definition is not replaced. The system will
attempt to replace the server definition during later
configuration refresh operations.
User response: Before the local server definition for
server name can be replaced with a definition from the
configuration manager, the UPDATE SERVER
command must be used to set the ALLOWREPLACE
attribute to ON.
ANR3470I ANR3478E
ANR3470I
Command: Auditing enterprise

configuration definitions.
Explanation: The server has started to audit database

definitions used by the enterprise configuration facility.
continues.
ANR3471E
Audit command: Enterprise configuration

global attributes are missing.
Explanation: A database audit process finds that the

global attributes used by the enterprise configuration
facility are missing.
FIX=YES specified so that the enterprise configuration
global attributes can be recreated.
ANR3472I

global attributes are missing - attributes
will be recreated using available
database information or default values.

facility are missing. Because FIX=YES has been
specified on the AUDIT command, these attributes will
be recreated using available information from the
database or default values.
User response: When the audit completes, you can
use the QUERY STATUS command to examine the
values set for the enterprise configuration global
attributes. Then use the appropriate SET command to
change the attributes, if desired.
ANR3473E

global attribute(s) are incorrect.
Explanation: A database audit process finds that

facility are incorrect.
FIX=YES specified so that the enterprise configuration
global attributes can be corrected.
ANR3474I

global attribute(s) are incorrect attributes will be corrected using
available database information or
default values.

facility are incorrect. Because FIX=YES has been
specified on the AUDIT command, these attributes will
be corrected using available information from the
database or default values.
values set for the enterprise configuration global
attributes. Then use the appropriate SET command to
change the attributes, if desired.
ANR3475E
Audit command: Extraneous profile

information found.
Explanation: A database audit process finds

extraneous configuration profile information.
FIX=YES so that the information is deleted.
ANR3476E

information found - information will be
deleted.

extraneous configuration profile information. Because
FIX=YES has been specified for the audit command, the
extraneous information will be deleted.
ANR3477E
Audit command: Profile information is

inconsistent.

inconsistent configuration profile information. This
information can be corrected.
FIX=YES so that the information can be corrected.
ANR3478E
Audit command: Profile information is

inconsistent - it will be corrected.

inconsistent configuration profile information. Because
information will be corrected.

395
ANR3479E ANR3500I
ANR3479E
Audit command: Profile association

information is missing.
Explanation: A database audit process detects missing

profile association information. This information can be
recreated.
FIX=YES so that the information can be recreated.
ANR3484E
Audit command: Profile subscription

information is inconsistent - it will be
corrected.

inconsistent profile subscription information. Because
information will be corrected.
ANR3480E
Audit command: Profile association

information is missing - it will be
recreated.

profile association information. Because FIX=YES has
been specified for the audit command, the information
will be recreated.
ANR3481E

association information found.

extraneous profile association information.
FIX=YES so that the information is deleted.
ANR3482E

association information found information will be deleted.

extraneous profile association information. Because
ANR3483E
Audit command: Subscription information

is inconsistent.

inconsistent profile subscription information. This
FIX=YES so that the information can be corrected.
396
ANR3485E
Audit command: Profile subscriptions

were found to more than one
Explanation: A database audit process determines that

a managed server has subscriptions to more than one
configuration manager. This may cause the enterprise
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
and then define the desired subscriptions.
ANR3486I
CANCEL SESSION ALL command

processing ended sooner than expected.
Explanation: It is possible that the server was unable

to cancel all sessions because a session was
encountered that could not be cancelled. Some sessions
may still remain active after the command completes.
System action: Server operation completes.
User response: Specify a session_number with the
CANCEL SESSION command to cancel a specific
CLIENT session. If a SERVER session is active, the
partner server must be quiesced for the session to end.
The SERVER session may be active with a Storage
Agent, Library Client, Library Server or Virtual Volume
server. To prevent new sessions from starting, see the
DISABLE SESSIONS command.
ANR3500I
Backup set for node node name as set

name (data type data type) being
generated.
Explanation: The named object set is being created for

the specified node.
System action: The server generates a backup set.
ANR3501I ANR3509E
ANR3501I
Backup set for node name as set name

(data type data type) completed
successfully - processed files files.
Explanation: The named object set was successfully

created for the specified node. The number of files
processed is specified.
ANR3502W

(data type data type) completed with file
processing errors - processed files files
with error files files skipped.

created for the specified node. However, during
processing errors were encountered accessing some files
- these files were skipped.
Generation of backup set for node name

as set name (data type data type) failed.
Explanation: The named object for the specified node

was not created. An error was encountered causing the
creation of this object set not to complete successfully.
User response: Evaluate other messages that were
issued and try to determine the cause of the failure.
After determining the cause of the failure, retry the
command. If the cause can not be determined, please
contact your local service representative.
If ANR3504W was received, than an error occurred
while logging the volumes used to the server volume
history. It is possible to issue a DEFINE BACKUPSET
listing these volumes. That would cause the server to
create the necessary entries for this backup set on this
server.
ANR3504W

determine which volumes where used for to generate
this backup set. The volumes can be inserted into the
server volume history for use by issuing a DEFINE
BACKUPSET and listing these volumes. This will also
allow this backup set to be queried from a client as
well since there is not a server entry for this backup
set. Only issue the DEFINE BACKUPSET if this
generate backup set operation completed successfully.
ANR3505I
Backup set for node name as set name was

not able to log the volumes used for this
operation to the server volume history.

was created. However, when the process attempted to
add the volumes, used for this operation to the volume
history for the server, an error occurred and this could
not be completed.

used volume volume name.

used the specified volume.
ANR3507I
User response: Evaluate other server messages for an

indication of why the files where skipped. Files can be
skipped because of failures locking those files, having
no files to process, or for other more serious problems.
First, retry the command and see if it completes
without any skipped files. If you are unable to generate
the backup set without skipping files, please contact
your local service representative for assistance.
ANR3503E
Cancel in progress

a QUERY PROCESS command, and indicates that a
generate backupset process has been canceled. The
process will end shortly.
System action: The process terminates and server
ANR3508W

as set name (data type data type) failed no filespaces to process.

was not created. No filespaces were available to
process.
User response: Reissue the command against a node
that has filespaces associated with it. If no filespaces
exist for a given node, than there is no file data to
write to the backupset.
ANR3509E

data storage - device class device class

an error occurred because the specified device class is
not defined.
User response: Make sure the specified device class is
defined.
397
ANR3510E ANR3517E
ANR3510E

data storage - disk volume specified.

an error occurred because a specified volume is a disk
volume rather than a tape volume.
User response: Make sure that all volumes specified
for the command command are tape volumes.
ANR3511E

data storage - invalid volume name
specified.

accessing data storage while processing command
command. The error occurred because an attempt has
been made to access a volume with an invalid name.
volume name.
ANR3512E

data storage - insufficient number of
media.

the server cannot allocate sufficient mount points.
available.
ANR3514E

command command operation failed because data
external event.
interrupted. Reissue the command command after the
problem is resolved.
ANR3515E


export, database dump, or database backup operation
(as recorded in the volume history) or is in use by
another process.
previously used for an export, database dump, or
volumes that have been used for export, database
ANR3516E
ANR3513E
Command: Data transfer was interrupted

Command: Output error encountered in


mounted.
v No storage space.

writing to the sequential media. Command command
media for storing data and SCRATCH=NO has been
specified on command command.

System action: Command command processing ends.


preceding this one to determine the cause of the error.
After the problem is corrected, the command can be
retried.

SCRATCH=YES or specify additional volume names on
the command.
Explanation: The command command operation ends

because an error has been encountered by the server in
writing to a device. Possible reasons include:
v I/O error writing to a device
ANR3517E

data storage - required volume was not
mounted.

required volume cannot be mounted. The mount
398
ANR3518I ANR3524W
request may have been canceled.


sure the necessary volumes are accessible.
ANR3518I

completion.

message.
ANR3519E
Command: Insufficient memory available

Explanation: The server encounters a memory

shortage in accessing data storage during command
command operation.
application.
ANR3520E
Command: Internal error encountered in

System action: The server ends the backup set

operation and continues operation.
ANR3522W

was deleted from data storage during
retrieval.

System action: The server ends the command and
ANR3523W
Backup set command: Retrieve failed error on input storage device.

in accessing data storage while processing command
command operation.
Explanation: The server ends a backup set operation

for the specified session because an I/O error has been
encountered by the server in reading from a device.
The object for which the I/O was issued is reported in
a later message.

System action: Backup set processing skips this file,


found and resolved, reissue the command command
operation. If the failure cannot be found, contact your
service representative for assistance in resolving the
problem.

to be shut down with the HALT command to correct
the hardware problem.
ANR3524W
ANR3521W
BackupSet command: Data storage retrieve

or restore failed - error detected.
Explanation: The server ends an backup set operation

because an error has been encountered on the server.
Some common reasons for the error are:
Backup set command: Transaction failed data transfer interrupted.

a backup set operation failed because data transfer to
or from data storage was interrupted by an external
event.
System action: The backup set operation is ended and

399
ANR3525W ANR3530E
interrupted. Attempt the backup set operation again
after problem is resolved.
ANR3525W
Backup set command: Transaction failed storage media inaccessible.

backup set operation because storage volumes are not
available in the storage pools in which the client files
are to be stored.
ANR3526E
Backup set command: Error encountered in

accessing data storage - volume cannot
be used.
Explanation: During backup set processing, a volume

has been mounted but cannot be used.
System action: The backup set operation is ended and
User response: Query the activity log for messages
preceding this one that give additional information.
Make sure a usable volume is specified and mounted.
ANR3527E
Backup set command operation terminated

- it is acting on an empty volume or
volume content is not as expected.
Explanation: The volume content this command is

acting upon is not as expected, the volume is empty, or
the volume cannot be found.
System action: The command operation is ended.
sure the expected content is in the volumes or the
volume is not empty and exists.
ANR3528E
Backup set command: Media not accessible

Explanation: The server ends a transaction for a

backup set operation because storage volumes are not
available in the storage pools in which the client files
are to be stored.

ANR3529W
Explanation: The backup set generation process

encountered a file that was previously found to be
damaged. The process encountered the file during a
sequential scan of all files on the storage pool volume;
the indicated file may or may not have been a
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
case, and if so, will reset the damaged state for the file.
System action: The damaged file is not added to the
backupset.
FIX=NO to determine if the file is actually damaged.
The audit will reset the file's damaged state if the file is
not damaged. (If the file is part of an aggregate, and
none of the files within the aggregate are damaged, the
audit will also reset the entire aggregate's damaged
state.)
If the file remains in the damaged state after the audit
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
primary storage pool that had been previously backed
up to a copy storage pool.
If the audit resets the file's damaged state, or the
damaged file was successfully restored using RESTORE
STGPOOL, and it is important for this file be included
in the backup set, then rerun the GENERATE
BACKUPSET command to generate a new backup set
containing the file.
ANR3530E
Audit command: A missing, incorrect, or,

invalid collocation group has been
detected.
Explanation: A database audit process found a

missing, incorrect, or invalid collocation group.
User response: Issue the audit command again, and
specify FIX=YES so that the error can be corrected.

400
Generate backupset skipping damaged

name, fsId filespace id, File name file name.
ANR3531E ANR3539E
ANR3531E
Audit command: A missing or incorrect

collocation group has been detected; it
will be corrected.

missing, incorrect, or invalid collocation group. Because
error will be corrected.

ANR3536E
Audit command: Inconsistent information

detected in collocation group
(Aggregate.ID).

inconsistent information for a collocation group. This
problem cannot be corrected by the audit process.

ANR3532E
Audit command: Missing or incorrect

collocation group identifier for
collocation group collocation group name
has been detected.
ANR3537E

collocation group member has been
detected for collocation group ID
collocation group ID.
Explanation: A database audit process detects an

invalid, missing, or incorrect collocation group
identifier.
Explanation: A database audit process detects a

missing or incorrect member for a collocation group.
User response: Issue the audit command again and


ANR3533E

collocation group id detected for
collocation group name - it will be
corrected.
ANR3538E

collocation group member has been
detected for collocation group id
collocation group id - it will be corrected.

or incorrect information for a collocation group.
Because FIX=YES has been specified for the audit
command, the error will be corrected.
Explanation: A database audit process detects a

missing or incorrect member for a collocation group.
ANR3534E

collocation group name for collocation
group id collocation group id has been
detected.
Explanation: A database audit process finds a missing

or incorrect collocation group name.
ANR3535E

collocation group name has been
detected for collocation group id
collocation group id - it will be corrected.

or incorrect information for a collocation group.
ANR3539E

as set name (data type data type) skipped
shreddable data object.

was included.
Data retrieved from a shreddable storage pool was
skipped because the ALLOWSHREDDABLE=YES
parameter was not specified.
System action: Server operation is terminated.
User response: Check with your Storage
Administrator to ensure data retrieved from a
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
be shredded. Check whether your Storage
Administrator allows shreddable data to be stored on
backupsets. Restart the operation and specify the
ALLOWSHREDDABLE=YES parameter.
A shreddable storage pool is a storage pool that has
401
ANR3540E ANR3550E
been defined with a non zero SHRED attribute.
Alternatively, the storage pool from which the
backupset data is retrieved can be updated as a non
shreddable storage pool. This requires the storage pool
SHRED attribute to have a value of zero. Backupsets
generated from data retrieved from non shreddable
storage pools do not require the
ANR3540E
Object set set node:set name:data type was

not found for session session number,
node.
Explanation: The indicated session id requested to

restore the object set. The object set was not found on
the server.
System action: The error is returned to the client.
ANR3541E
Error error code occurred opening object

set set node:set name:data type for session
session number, node.
Explanation: An error occurred while opening the

indicated object set.
ANR3544E
Explanation: The named data object for the specified

node was skipped while generating a backupset.
The data object resides in a shreddable storage pool
and will not be included in the backupset because the
ALLOWSHREDDABLE=YES parameter was not
specified.
System action: Backupset generation continues.
User response: Check with your Storage
Administrator to ensure data residing in a shreddable
storage pool is a allowed to be stored on a backupset.
Data stored on backupsets cannot be shredded. Only
data that resides in a shreddable storage pool can be
shredded. If your Storage Administrator allows
shreddable data to be stored on backupsets, then restart
the operation and specify the
ANR3547I
System action: An error is returned to the client.

User response: Correct the problem reported by
previous messages, if possible.

as set name (data type data type) skipped
shreddable data object in file space
filespace name (fsId filespace id), file name
file name, type file type.
Backup set set name used volume volume

name.
Explanation: The named object used the specified

volume.
ANR3542E
Error error code occurred reading object

set set node:set name:data type for session
session number, node.

ANR3548E
Explanation: An error occurred while reading the

indicated object set.
User response: Correct the problem reported by
previous messages, if possible.
ANR3543E
Error error code occurred while sending

entries from object set set node:set
name:data type for session session number,
node.
Explanation: An error occurred while sending entries

for the indicated object set.
User response: Correct the problem reported by other
prior or subsequent messages related to this session,
and try the operation again.

was moved or deleted from data storage
during retrieval.

moved or deleted from data storage by another process
before retrieval is complete.
if space reclamation, migration, DELETE FILESPACE,
DELETE VOLUME, MOVE DATA, or inventory
expiration processes are running; these processes can
move or delete data storage files during retrieval.
ANR3550E
Definition of backup set set name for

node name failed because it has an
unknown format.

was not defined. It was generated on a server that is at
a higher level than this server and contains data that
cannot be properly interpreted by this server.
402
ANR3551I ANR3607E
User response: Define the object on a server that is
compatible with the server that generated the object, or
upgrade this server to be compatible with the server
that generated the object.
ANR3551I
The server delete batch size has been set

to new batch size. Deletion operations
that start after this point will use the
new value.
Explanation: A SETOPT commmand was used to set

the value for the delete batch size value. This setting
determines the maximum number of files that are
deleted from the server in one database transaction.
The setting influences inventory expiration operations.
System action: The server uses this new setting for
deletion operations that are started after this message is
issued.
a database server, processing ended prematurely

because of a protocol error.
System action: Server operation continues. Policy is
loaded from the database server database.
User response: If this problem persists, contact your
ANR3604E
Explanation: A command was issued that is valid

under most circumstances, but not in the current server
environment.
User response: Issue commands which are allowed in
the current environment.
ANR3605E

ANR3601W
Policy Domain release failed for domain

domain id due to communications failure.
Explanation: The storage agent was attempting to

inform the database server that it was finished with the
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
server terminates or re-starts or when the database
server re-starts.
ANR3602E
Unable to communicate with database

server.

communicate with the database server but was unable
to do so.
System action: The storage agent operation fails.
User response: Check the configuration of the storage
agent and server to ensure that communication
parameters are correct. Ensure that the database server
is running and is accepting messages.
ANR3603E
Storage AgentStorage Agent name was

unable to load policy information due to
a protocol error.
Explanation: While receiving policy information from
Unable to communicate with storage

agent.
Explanation: The database server was attempting to

communicate with the storage agent but was unable to
do so.
System action: The database server operation fails.
parameters are correct.
ANR3606E
System action: The storage agent continues operation.

The policy information is deleted from the storage
agent policy cache.
User response: Policy caches are cleaned up on the
storage agent or server re-start. Network
communication between the storage agent and database
server should be checked.
This command is not supported in the

current operating environment.
The storage agent was communicating

with the database server on a restore
request with verb verb name and
received return code return code.
Explanation: The storage agent and database server

were coordinating a restore request. While
communicating using the indicated verb ( an internal
request mechanism between the storage agent and
database server ), an unexpected return code was
received. The verb name and return code are provided
for Tivoli support personnel.
System action: Database server and storage agent
continue. The restore request fails, but may be retried
by the client.
parameters are correct. If this problem persists, contact
ANR3607E

with the client on a restore request with
verb verb name and received return code
return code.
Explanation: The storage agent was communicating

with a client for a restore request. While
communicating using the indicated verb ( an internal
403
ANR3608E ANR3999E
request mechanism between the storage agent and
client ), an unexpected return code was received. The
verb name and return code are provided for Tivoli
support personnel.
continue. The restore request fails, but may be retried
by the client.
agent and client to ensure that communication
parameters are correct. If this problem persists, contact
ANR3608E

with the database server on a restore
request. An unexpected request (id verb )
was received from the database server.
is the result of starting a storage agent. The storage

agent requests that the server purge cached information
that it was using previously. It is possible that
information tracking policy caching has become stale.
In this case, no response is required. If the message
occurs without a storage agent connecting to the server,
ANR3611E
Storage Agent unable to contact server.

contact the server to start a session or run a command.
The storage agent was unable to contact the server to
start a transaction.
System action: The storage agent continues
processing. The server may be down or there may be a
communications problem.
Explanation: The storage agent and database server

were coordinating a restore request. While
communicating, the indicated verb ( an internal request
mechanism between the storage agent and database
server ), was unexpected. The verb number is provided
for Tivoli support personnel.
User response: No response is required if the message

is the result of stopping a server. Ensure that the server
with which the storage agent communicates is running
and that there is connectivity between the systems. The
server must be restarted before you can start a new
administrator session with the storage agent.

continue. The restore request may fail, but may be
retried by the client.
ANR3612E
This command is not supported in the

Express environment.
User response: If this problem persists, contact your

Explanation: A command was issued that is valid

under most circumstances, but not in the current server
environment.
ANR3609E
The storage agent was handling a

restore request. A failure occurred in
starting a new thread. The return code
return code from the failing routine may
be useful to Tivoli service.
Explanation: The storage agent was handling a restore

request. A new thread could not be started. Without the
new thread the request could not be handled.
continue. The restore request has failed.
User response: Ensure that there is sufficient system
memory for the storage agent to operate properly.
Insufficient memory or paging/swap space can cause
problems in starting threads. If this problem persists,
ANR3610I
User response: Issue commands which are allowed in

the current environment.
ANR3613W
Process process ID skipped Num Files

files on volume Volume name because of
a lock conflict with another process.
Explanation: A lock conflict was encountered while

moving files and the retries were exceeded.
System action: The operation skips the files without
making copies and continues.
User response: Retry the operation.
ANR3999E
Domain Identifier domain identifier was

not found.
Failure validating database load:

expected numRecs records and numBV bit
vectors - loaded actNumRecs records and
actNumBV bit vectors.
Explanation: The server was cleaning up cached

policy information after a restore request. A domain
with the indicated identifier was not found in an
internal list.
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
loaded, failed to validate.

continue.
System action: The LOAD DB process completes with

a failure. The server database is not in a usable state.
User response: No response is required if the message
User response: A number of possible causes exist. To
404
ANR4000I ANR4009E
recover from this situation, first retry the database load
process. If the error reoccurs, check the activity log or
other system logs to determine if there is a hardware or
media error. If a hardware or media error exists, correct
the error and retry the load process. If a hardware or
media error does not exist, it is likely the dump or
unload of the server database has encounted an error
resulting in the dump/unload server database image as
being unusable or that there is an error in the logic for
load db processing. Contact your service representative
for assistance.
ANR4000I
Dump command: Database dump process

started.
Explanation: The database dump process has started.

System action: The server dumps the contents of the
database to a file or removable media.
ANR4005E
Load command: Database load process

terminated due to error (error indicator).

prematurely due to an error.
System action: The server ends load processing.
User response: Examine previously issued messages
to determine if an error can be corrected, such as a
syntax error. If you cannot resolve the error, contact
ANR4006I
Command: Volume volume number written

by process is volume name.
Explanation: A sequential data process wrote to the

volume named in the series of one or more volumes
that were used to store output. The volumes position
in the series in indicated by the volume number
reported.
System action: The server ends processing.
ANR4001I

completed.
Explanation: The database dump process has ended.

ANR4007E
System action: The server completes processing.

ANR4002I

terminated due to error (error indicator).
Explanation: The database dump process has ended

prematurely due to an error.
System action: The server ends dump processing.
to determine if an error can be corrected, such as an
output error. If you cannot resolve the error, contact
ANR4003I

started.
Explanation: The database load process has started.

System action: The server loads the contents of the
database from a file or removable media.

completed.
Explanation: The database load process has ended.

System action: The server completes processing.
Explanation: The command process encounters a

database transaction error in recording the names of the
volumes used for the process in the server database.
System action: The server ends processing.
to determine if there is an error that can be corrected,
such as a syntax error. If you cannot resolve the error,
contact your service representative. The volumes used
by the process are valid for the corresponding input
process, but are not recorded in sequential volume
history lists generated by the server.
ANR4008W
Load command: Database object object

name does not exist.
Explanation: The database load process attempts to

delete a database object, but the object does not exist.
System action: Database processing continues.

ANR4004I
Command: A transaction error was

encountered in recording volume usage
history.
ANR4009E
Load command: Database object object

name cannot be deleted because it is in
Explanation: The database load process attempts to

delete a database object, but the object is currently
being used by another process.
System action: Database processing ends.
User response: Reissue the command. If it fails,
405
ANR4010E ANR4017E
ANR4010E
Dump/load command: Database dump/load

processing failed - insufficient memory.
Explanation: The database dump/load process fails

due to insufficient memory.
System action: Database processing ends.
User response: Allocate additional storage to the
server. There are two ways to do this:
v Increase the size of the servers virtual machine (for
VM), or region size (for MVS). For AIX, ensure that
there is sufficient paging space. You may also use
SMIT to determine if the number of applications is
causing a memory shortage. For OS/2, ensure that
there is sufficient space for the OS/2 SWAPPER.DAT
file. Check your CONFIG.SYS for the SWAPPATH
statement to determine where your SWAPPER.DAT
file is located and then determine how much space is
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
LOGPOOLSIZE parameters in the server options file
and restart the server. Note that each page causes an
additional 4K page to be allocated for the specified
buffer pool. Reducing the pool sizes requires more
I/O to service the same amount of data; some
performance degradation may result.
ANR4014E
Explanation: The specified volume does not contain a

dump created from the database dump command.
ANR4015E

error. On MVS or VM, the LOADDB command syntax
may be specified by using a ddname or by specifying a
device class name. You must use the same method that
was used when the database was originally dumped. If
you did not, this error message will be displayed. Try
loading the database by using the other method of
syntax (devclass). If the error cannot be isolated and
Dump command: Database page page

number is invalid - it will be skipped.
Explanation: The specified page is invalid, and it will

not be used during dump processing.
Load command: Invalid record format

(format code) detected.
Explanation: During processing of command load

command, an invalid record type is detected when
reading the dumped information from the dump
media.
ANR4016E
ANR4011W
Load command: The specified input

volume does not contain a server
database dump.
Load command: Invalid header sequence

number detected in database dump.
Expected expected sequence number; Actual
actual sequence number.
Explanation: During processing of command load

command, an invalid sequence number is detected when
reading the dumped information from the dump
media.
ANR4012W
Dump command: Database page page

number is damaged.
Explanation: The specified database page is damaged;

it will not be dumped.
User response: Examine previously issued server

messages to determine the source of the error. If the
error cannot be isolated and resolved, contact your
ANR4017E

ANR4013I
Dump command: Dumped number of

entries database entries (cumulative).
Explanation: This message indicates the number of

database entries that have been dumped so far during
database dump processing.
406
Load command: Invalid record type record

type read from database dump data.
Explanation: The server database load process

encounters an invalid record in reading data from the
dump media.
System action: The database load process ends.
User response: Examine previously issued server
messages to determine the source of the error. If the
ANR4018E ANR4028I
ANR4018E
Load command: Load processing failed insufficient recovery log space.
ANR4023E
Load command: Error (error code) occurred

during a read operation.
Explanation: The load process fails due to insufficient

recovery log space.
Explanation: The server database load process

encounters an error reading from the dump media.
System action: Database load processing ends.
System action: The database load operation ends.
User response: Reinstall the server and specify a

larger recovery log and reissue the database load
command.

to determine why the operation failed; correct the
problem and restart the process.
ANR4019E
Load command: Load processing failed insufficient database space.
ANR4025I
Explanation: The load process fails due to insufficient

database space.
System action: Load processing ends.
User response: Reinstall the server and specify a
larger database and reissue the database load
command.
ANR4020E
Load command: Batch database insert

failed.
Explanation: The database load process fails when it

attempts to insert a batch of rows into the database.
System action: Database load processing ends.
this one to determine if an error can be corrected. You
may wish to reinstall the server with a new recovery
log and database and reissue the load command. If the
Dumped number of pages database pages,

number of bit vectors bit vectors, and
number of database entries database entries;
number of bad pages bad database pages
have been encountered; number of bytes
copied.

a QUERY PROCESS command executed against an
online database dump process. The message displays
information about the progress of the dump.
System action: Database dump processing continues.
User response: None. You may cancel the dump
process with the CANCEL PROCESS command.
ANR4026I
Dump command: Process process number,

database dump has completed.
Explanation: The online server database dump process

started as process process number has completed.
System action: Database dump processing ends.
ANR4021E
Dump/load command: Error (error code)

occurred during an open operation.
Explanation: An error occurs while attempting an

open operation on the dump media for a database
dump/load operation.
ANR4027I
Explanation: The online server database dump process

started as process process number has been canceled
with the CANCEL PROCESS command.
System action: Database dump processing ends.
ANR4028I
ANR4022E
Dump command: Error (error code)

occurred during a write operation.

database dump was canceled.

Database dump terminated due to an
error (error code).
Explanation: The server database dump process

encounters an error while writing to the dump media.
Explanation: The online database dump process has

ended prematurely due to an error.
System action: Server processing continues, the dump

processing ends.
System action: The server ends dump processing.


this message to see if an error can be corrected, such as
output error. If you cannot resolve the error, contact
407
ANR4029I ANR4039I
ANR4029I
Dump command: Database checkpoint

started.
Explanation: The database dump process is flushing

updated database pages from the database buffer pool
to stable storage so that they can be dumped.
System action: Database dump or load processing

ends.
ANR4035I
System action: Database dump processing continues.

ANR4030I
Dump command: Database checkpoint

completed.
Explanation: The database dump process has flushed

all updated pages from the database buffer pool to
stable storage.
Dump/load command: Encountered number

of bad database records bad database
records.
Explanation: This message is displayed at the end of a

server database dump or load command to indicate the
number of invalid database records that have been
encountered.
ends.
System action: Database load processing continues.

ANR4031I
Dump/load command: Copied number of

pages database pages.

number of database pages copied.
ANR4036I

database entries database entries.

number of database entries that have been copied.
ends.

ends.
ANR4037I
ANR4032I

records database records.

number of database records copied.
Dump/load command: number of bytes

copied.

number of bytes that have been copied.
ends.

ends.
ANR4038I
ANR4033I
Dump/load command: Copied number of bit

vectors bit vectors.

number of database bit vectors copied.
ends.
Load command: Loading database

information dumped on dump date at
dump time.
Explanation: At the beginning of a server database

load process, this message indicates the date and time
that the dump took place for the database information
that is loaded into the server.

ANR4039I
ANR4034I

of bad database pages bad database pages.

number of invalid database pages that have been
encountered.
408
Load command: Loaded number of entries

database entries (cumulative).

database entries that have been loaded so far during
database load processing.
ANR4040I ANR4047I
ANR4040I
Audit command: Auditing client node and

administrator definitions.

database audit and indicates that the client node and
administrator definitions are being examined by the
database audit process.
you may want to check the domain assignment for this

node, and reassign the node to a different policy
domain, if desired.
ANR4044I

ANR4041I
Audit command: Node node name is

assigned to Domain domain name, but
not verified by server database policy
entries.
Explanation: A database audit process finds a node

assigned to a policy domain that is not recorded
properly in policy database entries.
Explanation: A database audit process cannot find an

appropriate policy domain for assigning the specified
node.
User response: When the audit command completes,
use the UPDATE NODE command to assign the
specified node to an appropriate policy domain.
ANR4045I

User response: If FIX=YES has not been specified for
the audit command, you may want to run this
command again, and specify FIX=YES so that the audit
process can correct the policy domain assignment for
the node.
ANR4042I
Audit command: Node node name is

assigned to Domain domain name, but
not found in server database policy
entries - attempting to assign the node
to domain domain name.

assigned to a policy domain that cannot be referenced
in database policy entries. Because FIX=YES has been
specified for the audit command, the audit function
will attempt to correct the policy domain assignment
for the node.
you may want to check the domain assignment for this
node, and reassign the node to a different policy
domain, if desired.
Audit command: Node node name
assignment failed - will attempt to
assign the node to domain domain name.

assigned to a policy domain that cannot be located in
database policy entries. Because FIX=YES has been
specified for the audit command, the audit function is
attempting to assign the node to an existing policy
domain. The function attempts to assign the node to
the domain name specified.
Audit command: Invalid compression

value encountered for node node name.
Explanation: A database audit process encounters an

invalid node compression value for the node indicated.
process can correct the problem.
ANR4046I
Audit command: Invalid compression

value encountered for node node name
the default value will be set.

invalid node compression value for the node indicated.
Because FIX=YES has been specified, the audit function
sets the nodes compression 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
default, use the UPDATE NODE command to change
the value after the audit command has completed.
ANR4047I
ANR4043I
Audit command: Could not assign Node

node name to a policy domain; use the
UPDATE NODE command to assign a
policy domain for this node.
Audit command: Invalid archive delete


invalid archive delete permission value for the node
indicated.

409
ANR4048I ANR4055I
ANR4048I
Audit command: Invalid archive delete


invalid archive delete permission value for the node
indicated. Because FIX=YES has been specified, the
audit function sets the nodes archive delete permission
value to the default value.
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
change the value after the audit command has
completed.
ANR4049I
Audit command: Invalid backup delete


invalid backup delete permission value for the node
indicated.
ANR4050I
Audit command: Invalid backup delete


invalid backup delete permission value for the node
audit function sets the nodes backup delete permission
value to the default value.
User response: If you want the backup delete value
for the specified node to be set to a value other than
the default, use the UPDATE NODE command to
completed.
ANR4051I
Audit command: Invalid lock state

encountered for node node name.

invalid lock state value for the node indicated.
ANR4052I

invalid lock state value for the node indicated. Because
FIX=YES has been specified, the audit function sets the
nodes 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,
use the LOCK NODE command to change the value
after the audit command has completed.
ANR4053I
Audit command: Invalid Node conversion

state encountered for node node name.

invalid Node conversion state value for the node
indicated.
process can correct the problem. However, next time
this node logs onto the server, the node conversion
state will be reset.
ANR4054I
Audit command: Invalid conversion state

encountered for node node name the
node will be reset.

invalid conversion state value for the node indicated.
resets the conversion state.
ANR4055I

encountered for administrator
administrator name.

invalid lock state value for the administrator indicated.

410

encountered for node node name the
node will be unlocked.
ANR4056I ANR4063E
ANR4056I

encountered for administrator
administrator name the administrator will
be unlocked.
ANR4060I
Audit command: Administrative ID

assignments are incorrect - value(s) will
be corrected.

invalid lock state value for the administrator indicated.
sets the administrators lock state to unlocked.

global attributes used for server administrative
activities are incorrect. Because FIX=YES has been
specified on the AUDIT command, the attribute value
will be corrected in the server database.
User response: If you want the lock state for the

specified administrator to be set to a value other than
unlocked, use the LOCK ADMIN command to change
the value after the audit command has completed.
ANR4057E
Audit command: Administrative global

attributes are missing.

activities are missing.
FIX=YES specified so that the administrative global
attributes can be recreated.
ANR4058I

attributes are missing - default values
will be used to recreate the attributes.

activities are missing. Because FIX=YES has been
specified on the AUDIT command, default attribute
values will be used to recreate the administrative global
attributes.
values set for the administrative global attributes, and
use the appropriate SET command to change the
attributes, if desired.
ANR4059E
Audit command: Administrative ID

assignments are incorrect.

activities are incorrect.
attributes can be corrected.
ANR4061E

attribute(s) are incorrect.

ANR4062I

attribute(s) are incorrect - default values
will be set.

activities are incorrect. Because FIX=YES has been
specified on the AUDIT command, default attribute
values will be used to correct the administrative global
attributes.
ANR4063E
Audit command: Client node node number

not found in the server database.
Explanation: A database audit process finds a client

node reference that is not defined correctly in the
server database.
User response: If the audit command has not been
issued with FIX=YES specified, reissue the audit
function specifying FIX=YES so that the error can be
corrected.
411
ANR4064I ANR4071I
ANR4064I
Audit command: Client node node number

created as node node name assigned to
policy domain domain name in the server
database.

node reference that is not defined correctly in the
server database. Because FIX=YES has been specified
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,
use the QUERY NODE command to examine the node
that was added. Use the RENAME NODE command to
rename the corrected node and the UPDATE NODE
command to set attributes for the corrected node, such
as its password. You can issue the QUERY FILESPACE
command for the node, to determine which node and
platform type was originally represented by the
corrected node.
ANR4065E
Audit command: Administrator

administrator number not found in the
server database.
Explanation: A database audit process finds an

administrator reference that is not defined correctly in
User response: Reissue the audit command and

ANR4068I
Audit command: Policy domain domain

name referenced by an administrator
authority does not exist - the authority
will be removed.
Explanation: A database audit process finds a policy

administrator reference to a policy domain that does
not exist. Because FIX=YES has been specified, the
authority will be removed.
User response: After the audit command completes,
review your administrator definitions with the QUERY
ADMIN command. You can then use the REGISTER
ADMIN, UPDATE ADMIN, and GRANT AUTHORITY
commands to change any definitions.
ANR4069E
Audit command: Storage pool storage pool

authority does not exist.
Explanation: A database audit process finds a storage

administrator reference to a storage pool that does not
exist.


ANR4070I
ANR4066I

administrator number not found in the
server database - reference will be
removed.

administrator reference that is not defined correctly in
the server database. The invalid reference will be
removed from the database.
ADMIN and UPDATE ADMIN commands to change
any definitions desired.
ANR4067E
Audit command: Domain domain name

referenced by an administrator authority
does not exist.

administrator reference to a policy domain that does
not exist.
412

authority does not exist - the authority
will be removed.

administrator reference to a storage pool that does not
exist. Because FIX=YES has been specified, the
authority will be removed.
ADMIN, UPDATE ADMIN, and GRANT AUTHORITY
commands to change any definitions.
ANR4071I
Audit command: Invalid sign-on attempts

is not valid for node/administrator name.

invalid sign-on attempts value that is not valid for the
node or administrator indicated.
ANR4072I ANR4081I

ANR4072I
Audit command: Invalid file aggregation

information encountered for node node
name.
Explanation: A database audit process encounters

invalid information used for controlling aggregation of
files for the node indicated.
ANR4077I
Audit command: Invalid client node count

detected for policy domain domain name
count will be corrected.

count of nodes recorded for the specified policy
domain do not match the actual number of nodes
assigned to the domain. Because FIX=YES has been
specified for the command, the node count will
automatically be corrected.
ANR4073I
Audit command: Invalid file aggregation

information encountered for node node
name - information will be corrected.
ANR4078E
Audit command: Invalid activation

indicators encountered for policy
domain domain name.

invalid information used for controlling aggregation of
files for the node specified. Because FIX=YES has been
specified, the audit function corrects the information.
Explanation: A database audit process finds incorrect

policy set activation entries for the specified policy
domain.

ANR4074I

of entries bad database entries.

number of invalid database entries that have been
encountered.
ends.
ANR4075I
Audit command: Invalid activation

indicators encountered for policy
domain domain name - entry will be
corrected.

policy set activation entries for the specified policy
domain. Because FIX=YES has been specified for the
audit command, the entry will be corrected.
Audit command: Auditing policy

definitions.

database audit and indicates that the server policy
information (domain, policy set, management classes,
and copy groups) are being examined by the database
audit process.

ANR4080E
Audit command: Invalid grace period

backup retention value encountered for

incorrect grace period retention value for the specified
policy domain.

ANR4076E
ANR4079I
Audit command: Invalid client node count

detected for policy domain domain name.

count of nodes recorded for the specified policy
domain do not match the actual number of nodes
assigned to the domain.

ANR4081I

backup retention value encountered for
policy domain domain name - default
value will be set.
413
ANR4082E ANR4089I
policy domain. Because FIX=YES has been specified for
the audit command, the default value will be set.
ANR4086E
Audit command: Invalid node node number

found assigned to domain domain name.

number assigned to a policy domain that does not
reference a valid client node definition.
ANR4082E

archive retention value encountered for

policy domain.
ANR4083I

archive retention value encountered for
policy domain domain name - default
value will be set.

policy domain. Because FIX=YES has been specified for
the audit command, the default value will be set.
ANR4084E
Audit command: Invalid administrator

update information encountered for

last updated information for the specified policy
domain.

ANR4087I

number assigned to a policy domain that does not
reference a valid client node definition. Because
reference will be deleted.
ANR4088E

ANR4089I

policy domain domain name - information
will be corrected.

last updated information for the specified policy
domain. Because FIX=YES has been specified for the
command, the information is corrected.
Audit command: Default management

class management class name specified for
policy set policy set name in domain
domain name does not exist - the
reference will be removed.

set with a default management class specified that does
not exist. Because FIX=YES has been specified for the
audit command, the reference will be removed from the
policy set.
examine the policy set specified, and set a new default
management class for the set. If the policy set is the
ACTIVE policy set, you must activate a new policy set
for the domain with a valid default management class.
414
Audit command: Default management

class management class name specified for
policy set policy set name in domain
domain name does not exist.

set with a default management class specified that does
not exist.
ANR4085I
Audit command: Invalid node node number

found assigned to domain domain name
ANR4090E ANR4098I
ANR4090E
Audit command: Active Policy set for

domain domain name does not contain a
valid default management class - policy
will fail for this domain. Correct the
ACTIVE policy set.
Explanation: A database audit process finds an active

policy set for the specified policy domain that does not
have a valid active management class specified.

information for the specified management class. The
audit process generates an identifier, because FIX=YES
has been specified for the audit command.
ANR4095E

you must activate a new policy set for the domain with
a valid default management class.
ANR4091E

policy set set name in policy domain
domain name.

last updated information for the specified policy set.

information for the specified management class.
ANR4096E

ANR4092I

policy set set name in policy domain
domain name - information will be
corrected.

last updated information for the specified policy set.
the information is corrected.
Audit command: An invalid management

class identifier (actual identifier) was
encountered for management class
management class name in policy set set
name, domain domain name (expected
expected identifier).

encountered for management class
management class name in policy set set
name, domain domain name (expected
expected identifier) - the correct identifier
will be stored.

information for the specified management class. The
audit process corrects the identifier, because FIX=YES
has been specified for the audit command.

ANR4097E

ANR4093E
Audit command: A management class

identifier is not defined for
in policy set set name, domain domain
name.

in policy set set name in policy domain
domain name.

last updated information for the specified management
class.

information for the specified 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.
ANR4098I

in policy set set name in policy domain
domain name - information will be
corrected.
415
ANR4099E ANR4106E
last updated information for the specified management
class. Because FIX=YES has been specified for the

ANR4103I

ANR4099E
Audit command: Copy group copy group

class name, policy set set name, domain
domain name has an invalid name or
type.
Explanation: A database audit process encounters a

copy group that has an invalid name or copy group
type.
the audit command, reissue the command specifying
FIX=YES so that the error can be corrected.
ANR4100I
Audit command: Attempting to reinsert

the copy group as a BACKUP copy
group.

type. The process attempts to reinsert the definition as
a backup copy group.
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
backup copy group already exists for the management
class. The copy group is deleted.
you may examine the server copy groups using the
QUERY COPYGROUP command, and correct them
with the DEFINE COPYGROUP and UPDATE
COPYGROUP commands if desired.
ANR4102I
Audit command: Attempting to reinsert

the copy group as an ARCHIVE copy
group.

type. The process attempts to reinsert the definition as
an archive copy group.
416
Audit command: An archive copy group

already exists - the invalid copy group
will be deleted.

type. While attempting to reinsert the copy group as an
archive copy group, the process discovers that a backup
copy group already exists for the management class.
The copy group is deleted.
you may examine the server copy groups using the
QUERY COPYGROUP command, and correct them
with the DEFINE COPYGROUP and UPDATE
COPYGROUP commands, if desired.
ANR4104E

encountered for a copy group in
management class management class name,
policy set set name, domain domain name
(expected expected identifier).

information for the specified copy group.
ANR4105E

(expected expected identifier) - the correct
identifier will be stored.

information for the specified copy group. The audit
process corrects the identifier, since FIX=YES has been
specified for the audit command.
ANR4106E
Audit command: An invalid copy group

identifier (actual identifier) was
(expected expected identifier).

information for the specified copy group.
ANR4107E ANR4113E


the audit command, reissue the command and specify
FIX=YES so that the inconsistency can be corrected.
ANR4107E
Audit command: An invalid copy group

identifier (actual identifier) was
encountered for copy group name copy
group name (expected expected identifier).
ANR4111I

information for the specified copy group name.
ANR4108E
Audit command: Invalid backup copy

group attributes encountered for copy
group copy group name in management
class management class name, policy set set
name, domain domain name.

invalid backup copy group attributes for the specified
copy group.

invalid archive copy group attributes for the specified
copy group. Because FIX=YES has been specified for
the command, the copy group will be corrected using
default values for the attributes found in error.
examine the copy group by using the QUERY
COPYGROUP command, and correct the attributes
with the UPDATE COPYGROUP command, if desired.
ANR4112W

the audit command, reissue the command specifying
FIX=YES so that the inconsistency can be corrected.
ANR4109I
Audit command: Invalid backup copy

name, domain domain name - the copy
group will be corrected using default
attributes.

invalid backup copy group attributes for the specified
copy group. Because FIX=YES has been specified for
the command, the copy group will be corrected using
default values for the attributes found in error.
examine the copy group by using the QUERY
COPYGROUP command, and correct attributes with
the UPDATE COPYGROUP command, if desired.
ANR4110E
Audit command: Invalid archive copy

name, domain domain name.

invalid archive copy group attributes for the specified
copy group.
Audit command: Invalid archive copy

name, domain domain name - the copy
group will be corrected using default
attributes.

name, specified as a destination for copy
name, domain domain name, does not
exist.

storage pool specified for the destination of the
specified copy group that is not defined in the server
database. If this copy group is used in an active policy
set, then backup or archive operations will fail when
attempting to put client data in the destination.
use the DEFINE STGPOOL command to define the
missing storage pool or the UPDATE COPYGROUP
command to update the copy group to refer to an
existing storage pool.
ANR4113E

copy group copy group name in
policy set set name, policy domain domain
name.

last updated information for the specified copy group.
417
ANR4114I ANR4122E
ANR4114I

copy group copy group name in
policy set set name, policy domain domain
name - information will be corrected.

last updated information for the specified copy group.
the information is corrected.
ANR4115E

name is referenced, but not formally
defined.
Explanation: A database audit process finds a

reference to the specified policy domain, but the
domain is not formally defined in the server database.
ANR4118I
Audit command: Policy set set name in

domain domain name is referenced, but
not formally defined - a policy set with
this name will be created.

reference to the specified policy set, but the set is not
formally defined in the server database. Because
FIX=YES has been specified, the audit process will
create a new policy set with this name.
User response: After the audit command has
completed, you can view the attributes for this policy
set by using the QUERY POLICYSET command, and
update attributes with the UPDATE POLICYSET
command, if desired.
ANR4119E
Audit command: Management class class

name in policy set set name, domain
domain name is referenced, but not
formally defined.

reference to the specified management class, but the
class is not formally defined in the server database.
ANR4116I

name is referenced, but not formally
defined - a policy domain with default
attributes will be defined with this
name.

reference to the specified policy domain, but the
domain is not formally defined in the server database.
Because FIX=YES has been specified, a new policy
domain with this name will be defined by the audit
processor.
completed, you can view the attributes for this policy
domain using the QUERY DOMAIN command, and
update attributes with the UPDATE DOMAIN
command, if desired.
ANR4117E
Audit command: Policy set set name in

domain domain name is referenced, but
not formally defined.

reference to the specified policy set, but the set is not
formally defined in the server database.

ANR4120I

reference to the specified management class, but the
class is not formally defined in the server database.
command, the audit process defines a management
class in the server with this name.
completed, you can view the attributes for this
management class by using the QUERY MGMTCLASS
command, and update attributes with the UPDATE
MGMTCLASS command, if desired.
ANR4122E

418

domain name is referenced, but not
formally defined - the management class
will be created.
Audit command: The instance count for

management class class name does not
agree with the actual management class
data (number of instances instances).

reference count for the specified management class that
did not match the actual number of instances for this
class.
ANR4123I ANR4131W
ANR4127I

ANR4123I

management class class name does not
agree with the actual management class
data (number of instances instances) - the
number will be corrected.

reference count for the specified management class that
does not match the actual number of instances for this
class. The audit process corrects the count because
FIX=YES has been specified for the audit command.
Explanation: A database audit process is not able to

locate the global attributes for policy information in the
for the audit command, the attributes will be
regenerated.
ANR4128E
Audit command: Policy global high-water

marks do not match the identifiers in
use.
Explanation: A database audit process finds the

attributes used to track policy identifiers are incorrect.

ANR4124E
Audit command: Policy global attributes

cannot be found - attributes will
recreated.

copy group copy group name does not
agree with the actual copy group data
(number of instances instances).

reference count for the specified copy group that does
not match the actual number of instances for this copy
group.

ANR4129E
Audit command: Policy global high-water

use - they will be corrected.

attributes used to track policy identifiers are incorrect.
command, the attributes will be corrected.
ANR4125I

copy group copy group name does not
agree with the actual copy group data
(number of instances instances) - the
number will be corrected.

reference count for the specified copy group that does
not match the actual number of instances for this copy
group. The audit process corrects the count because
FIX=YES has been specified for the audit command.

ANR4130W
Audit Volume updating object

information for volume volume name:
filespace name, fsId filespace id , File Name
file name.

shown, object information for the specified file will be
updated.
System action: The object information is updated.

ANR4126E
Audit command: Policy global attributes

cannot be found.

locate the global attributes for policy information in the
server database.
ANR4131W
Audit Volume found incorrect object

information for volume volume name:
filespace name, fsId filespace id, File name
file name.

shown, object information for the specified file is found
to be in error.
419
ANR4132I ANR4137I
ANR4132I

count damaged files deleted, file count
damaged files marked as damaged, file
count files previously marked as
damaged reset to undamaged, file count
objects updated.

specifying FIX=YES for the volume shown has ended.
The following information is displayed:
the database if the audit volume process cannot access

the files due to hardware problems (for example, dirty
tape heads).
User response: If you suspect that files were
inaccessible because of hardware problems such as
dirty tape heads, correct the hardware problem and
reissue the AUDIT VOLUME FIX=NO command for
this volume. To remove damaged file references and
update the object information, issue the AUDIT
VOLUME command and specify FIX=YES.
ANR4134I
v The number of files audited

v The number of inconsistent files deleted
v The number of inconsistent files marked as damaged
v The number of files previously marked as damaged
that were reset to undamaged
v The number of updated objects
The number of files marked as damaged includes all
files belonging to aggregates that were marked
damaged during the audit. Files are marked as
damaged in primary storage pools and not deleted
when backup copies for the files are known to exist in
COPY storage pools.
AUDITDB: Processed number of entries

entries in database tables and number of
blocks blocks in bit vectors. Elapsed time
is elapsed time.
Explanation: This message reports the progress of a

database audit operation. While auditing database
tables, the number of entries processed will increase,
but the number of blocks processed in bit vectors will
not increase. While auditing bit vectors, the number of
blocks processed will increase, but the number of
entries processed will not increase. The number of
entries and the number of blocks are cumulative for the
entire audit operation. The elapsed time of the audit
operation is reported in hours, minutes, and seconds.
System action: Database audit processing continues.
User response: To recover files that have been marked

as damaged on the volume, use the RESTORE
STGPOOL or RESTORE volume command.
ANR4135I
ANR4133I

database audit and indicates that the server scheduling
information is examined by the database audit process.

count damaged files found and marked
as damaged, file count files previously
marked as damaged reset to undamaged,
file count objects need updating.
Audit command: Auditing central

scheduler definitions.


specifying FIX=NO for the volume shown has ended.
ANR4136I
The following information is displayed:

about client file spaces is currently being examined by
the database audit process.
v The number of files audited

v The number of inconsistent files marked as damaged
v The number of files previously marked as damaged
that were reset to undamaged
v The number of objects need updating
The number of files marked damaged includes all files
belonging to aggregates that were marked damaged
during the 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 of the files reside in a COPY storage
pool. Another AUDIT VOLUME command may be able
to access the files and reset the damaged indicator in
420
Audit command: Auditing server

inventory.

ANR4137I
Audit command: Auditing inventory file

spaces.

about client file spaces is currently being examined by
the database audit process.
ANR4138I ANR4147E
ANR4143E

ANR4138I
Audit command: Auditing inventory

backup objects.

about client backup objects is currently being examined
by the database audit process.
Explanation: A database audit process cannot locate

the global attributes for scheduling information in the
server database.
ANR4144I

ANR4139I

archive objects.

about client archive objects is currently being examined
by the database audit process.
Audit command: Central scheduler global

attributes cannot be found.
Audit command: Central scheduler global

attributes cannot be found - attributes
will be recreated.
Explanation: A database audit process cannot locate

the global attributes for scheduler information in the
regenerated.

ANR4145E
ANR4140I
Audit command: Database audit process

started.

database audit and indicates that the audit process has
started.
ANR4141I

completed.

database audit and indicates that the database audit
has successfully completed.
System action: Audit processing ends.
ANR4142I

terminated in error.

database audit and indicates that the audit process
ended prematurely due to an internal server database
error.
System action: Audit processing ends.

global attributes used for server scheduling activities
are incorrect.
specify FIX=YES so that the administrative global
ANR4146I
Audit command: One or more central

scheduler global attribute(s) are
incorrect - default values will be set.

global attributes used for server scheduling activities
are incorrect. Because FIX=YES has been specified on
the AUDIT command, default attribute values will be
used to correct the scheduling global attributes.
ANR4147E

this one to see if the error can be corrected. If the
situation cannot be resolved, contact your service
representative.
Audit command: One or more central

scheduler attributes are incorrect.

name referenced by schedule schedule
name does not exist.

schedule that references a policy domain that is not
421
ANR4148I ANR4156I
ANR4152I

ANR4148I

name referenced by schedule schedule
name does not exist - the schedule will
be deleted.

schedule that references a policy domain that is not
defined in the server database. Because FIX=YES has
been specified for the audit command, the specified
schedule will be deleted from the server database.

schedule reference from a client node for a schedule
that is not defined in the server database. Because
schedule association will be deleted from the server
database.
ANR4153E

ANR4149E
Audit command: One or more attributes

for schedule schedule name in policy
domain domain name are incorrect.
Explanation: A database audit process finds one or

more invalid attributes for the specified schedule.
ANR4150I
Audit command: One or more attributes

for schedule schedule name in policy
domain domain name are incorrect default values will be set.
Explanation: A database audit process finds one or

more invalid attributes for the specified schedule.
command the invalid attributes will be set to default
values.
use the QUERY SCHEDULE command to examine the
values set for the schedule, and use the UPDATE
SCHEDULE command to change any attributes desired.
ANR4151E
Audit command: Schedule schedule name in

policy domain domain name not found,
but is referenced by a client node.

schedule reference from a client node for a schedule
that is not defined in the server database.
422

policy domain domain name references a
client node that does not exist.

schedule that references a client node that is not
ANR4154I

policy domain domain name references a
client node that does not exist - the
node reference will be deleted.

schedule that references a client node that is not
been specified for the audit command, the reference
will be removed from the server database.
ANR4155E

update information encountered for a
schedule assignment.

last updated information for a schedule-node
assignment.
ANR4156I


policy domain domain name not found,
but is referenced by a client node - the
schedule association will be deleted.

update information encountered for a
schedule assignment - information will
be corrected.
ANR4157E ANR4165I
last updated information for a schedule-node
assignment. Because FIX=YES has been specified for
the command, the information is corrected.
ANR4157E
Audit command: Scheduling callback

address is registered for a client node
that does not exist.

server-prompted-scheduling callback address for a node
that does not exist.
ANR4158I
Audit command: Scheduling callback

address is registered for a client node
that does not exist - callback

server-prompted-scheduling callback address for a node
that does not exist. Because FIX=YES has been specified
for the command, the callback information will be
deleted from the server database.
ANR4159I
Audit command: An inventory

authorization rule specifies an invalid
node (node ID) or file space (filespace ID)
- the rule will be deleted.

either a node ID or file space ID is invalid for an
authorization rule. Since FIX=YES has been specified,
the invalid authorization rule will be deleted.
ANR4160I
ANR4161I
Audit command: Inventory global

attributes could not be found - they will
be created.

inventory global attributes. Because FIX=YES has been
specified for the command, the information is corrected
by the creation of the global attributes.
ANR4162I
Audit command: Inventory global

attributes could not be found.

inventory global attributes.
ANR4163I
Audit command: Invalid object ID

high-water mark encountered for
inventory global attributes - the value
will be corrected.

object ID high-water mark for the inventory global
attributes is invalid. Because FIX=YES has been
specified for the command, the object ID high-water
mark is determined by the current inventory and set
accordingly.
ANR4164I
Audit command: Invalid object ID

high-water mark encountered for
inventory global attributes.

object ID high-water mark for the inventory global
attributes is invalid.
Audit command: An inventory

authorization rule specifies an invalid
node (node ID) or file space (filespace ID).

either a node ID or file space ID is invalid for an
authorization rule.

ANR4165I
Audit command: An inventory node

assignment entry was not found for
node node ID - an entry will be created.

node assignment entry corresponding to the specified
node. Since FIX=YES has been specified for the
command, the required inventory entry will be created
using default values.
423
ANR4166I ANR4175I
ANR4166I

node node ID.

node.
ANR4167I
Audit command: The file space

high-water mark for node node ID is
incorrect - the value will be corrected.

ANR4171I
Audit command: Primary backup entry for

an expiring object (object.ID) cannot be
found - the expiring object entry will be
deleted.

primary backup entry for the specified expiring object.
the information is corrected by deleting the expiring
object entry.
ANR4172I

found.
Explanation: A database audit process finds that a file

space high-water mark is incorrect for the specified
node ID. Since FIX=YES has been specified for the

primary backup entry for the specified expiring object.

ANR4168I

incorrect.
Explanation: A database audit process finds that a file

space high-water mark is incorrect for the specified
node ID.
ANR4173I
Audit command: Primary archive entry for

found - the expiring object entry will be
deleted.

primary archive entry for the specified expiring object.
object entry.
ANR4169I

incorrect - the value will be corrected.
Explanation: A database audit process finds that an

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.
ANR4170I
Audit command: The authorization rule

incorrect.

ANR4174I

primary archive entry for the specified expiring object.
ANR4175I

authorization rule high-water mark is incorrect for the
specified node ID.
424

found.
Audit command: Invalid copy type

encountered for an expiring objects
entry (object.ID) - the expiring object
entry will be deleted.

copy type for the specified expiring object is invalid.
ANR4176I ANR4184I
object entry. The entry will be recreated later if it is
necessary.
ANR4181I

ANR4176I

encountered for an expiring objects
entry (object.ID).

copy type for the specified expiring object is invalid.

encountered for object object.ID - object
found as a backup object - correcting
the invalid copy type

invalid copy type for the specified object ID but finds a
corresponding backup object for the entry. Because
invalid copy type is corrected.

ANR4177I

an object (object.ID) cannot be found entry will be deleted.

specified primary backup object. Because FIX=YES has
been specified for the command, the entry is deleted.
ANR4182I

found as an archive object - correcting
the invalid copy type

invalid copy type for the specified object ID but finds a
corresponding archive object for the entry. Because
invalid copy type is corrected.

ANR4183I
ANR4178I

an object (object.ID) cannot be found.

specified primary backup object.
ANR4179I

an object (object.ID) cannot be found entry will be deleted.

specified primary archive object. Because FIX=YES has
been specified for the command, the entry is deleted.
ANR4180I

an object (object.ID) cannot be found.

specified primary archive object.

encountered for object object.ID primary archive entry created for object

invalid copy type for the specified object ID and is
unable to find corresponding primary backup or
primary archive objects. Because FIX=YES has been
specified for the command, a primary archive entry is
created using default values.
ANR4184I

encountered for object object.ID.

invalid copy type for the specified object ID and is
unable to find corresponding primary backup or
primary archive objects.

425
ANR4185I ANR4194I
ANR4185I
Audit command: Object entry for backup

object object.ID not found - entry will be
created.

object entry for the specified backup object. Because
FIX=YES has been specified for the command, an object
entry is created using default values.
ANR4190I
Audit command: Expiring entry for

inactive backup object object.ID not
found.

expiring entry for the specified inactive backup entry.

ANR4191I
ANR4186I
Audit command: Object entry for backup

object object.ID not found.

object entry for the specified backup object.
Audit command: Object entry for archive

object object.ID not found - entry will be
created.

object entry for the specified archive object. Because
information is corrected by creating an object entry.
ANR4187I
Audit command: Inventory object fields

for object object.ID do not match the
primary backup entry - the object will
be updated.

the object fields for the specified object ID do not
match the fields for the corresponding primary backup
object. Because FIX=YES has specified for the
command, the incorrect object fields will be corrected.
ANR4192I
Audit command: Object entry for archive


object entry for the specified archive object.

ANR4188I

primary backup entry.

match the fields for the corresponding primary backup
object.
ANR4189I

inactive backup object object.ID not
found - the entry will be created.

expiring entry for the specified inactive backup entry.
an expiring entry will be created.
ANR4193I

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

primary archive entry.

match the fields for the corresponding primary archive
object.
426

primary archive entry - the object will
be updated.
ANR4195I ANR4204I
ANR4195I

archive object object.ID not found - the
entry will be created.

expiring entry for the specified archive object. Because
FIX=YES has been specified for the command, an
expiring entry will be created.
ANR4196I
ANR4200I
Audit command: Expiring entry node ID

and file space filespace ID does not match
the object entry for object ID object.ID the entry will be deleted.

the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
the expiring object entry is deleted.

archive object object.ID not found.

expiring entry for the specified archive object.

ANR4201I
Audit command: Expiring entry node ID

and file space filespace ID does not match
the object entry for object ID object.ID.

the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
ANR4197I
Audit command: File space entry filespace

ID not found for node node ID.
Explanation: A database audit process cannot find a

file space entry for the specified node.

ANR4202I

ANR4198I

ID not found for node node name - an
entry will be created.

file space entry for the specified node. Because
FIX=YES has been specified for the command, a file
space entry has been created.

the specified expiring object has a date that is not valid.
the expiring object entry is deleted.
ANR4203I

ANR4199I

ID not found for node node ID - unable
to create an entry.

file space entry for the specified node ID. Because
FIX=YES has been specified for the command, the audit
process has attempted to create a file space entry but is
not successful.
User response: Contact your system administrator.
Audit command: The base date for

expiration processing of entry object.ID is
not valid - the entry will be deleted.
Audit command: The base date for

expiration processing of object object.ID
is not valid.

the specified expiring object has a date value that is not
valid.
ANR4204I
Audit command: One or more date values

for a backup entry object.ID is not valid.

one or more of the date values is improperly formatted
or contains incorrect information for the specified
backup object.
427
ANR4205I ANR4214I
ANR4205I
Audit command: The insertion date value

for archive entry object.ID is not valid.

the insertion date for the specified archive object is
improperly formatted or contains incorrect information.
ANR4210I
Audit command: Auditing physical

volume repository definitions.

database audit and indicates that the physical volume
repository definitions are being examined by the
ANR4206I
Audit command: Object entry for expiring

object object.ID not found - expiring
object entry will be deleted.

object entry corresponding to the specified expiring
command, the expiring object entry for the specified
object ID is deleted.
ANR4211I
Audit command: Drive entry library name

for library drive name in the physical
volume repository is invalid.
Explanation: A database audit process finds that a

drive entry is missing a corresponding library entry.

ANR4212I
ANR4207I
Audit command: Object entry for expiring


object entry corresponding to the specified expiring
object.
Audit command: An object entry for

library library name and drive drive name
in the physical volume repository is
invalid - the entry will be deleted.

drive entry is missing a corresponding library entry.
the invalid drive entry is deleted.
ANR4208I

assignment entry is not valid for node
node ID - the entry will be deleted.
ANR4213I
Audit command: A device type for library

library name and drive drive name in the
physical volume repository is invalid.

node assignment entry for the specified node ID is not
valid. Since FIX=YES has been specified for the
command, the required inventory entry is deleted.

device type for the specified library and drive is
invalid.
User response: Contact the system administrator so

that appropriate action may be taken.
ANR4209I

node node ID.

node assignment entry for the specified node ID is not
valid.
ANR4214I
Audit command: A drive model for

library library name and drive drive name
in the physical volume repository is
invalid.

drive model for the specified library and drive is
invalid.
User response: Contact the system administrator so
that appropriate action may be taken.
428
ANR4215I ANR4222I
ANR4215I

library library name and volume volume
name in the physical volume repository
is invalid.

library inventory entry is missing a corresponding
library entry.
ANR4216I

is invalid - the entry will be deleted.

library inventory entry is missing a corresponding
library entry. Because FIX=YES has been specified for
the command, the invalid library inventory entry is
deleted.
ANR4219I
Audit command: A library type specified

for library library name in the physical
volume repository is invalid.

library type for the specified library is invalid.
ANR4220I
Audit command: A library type specified

for library library name in the physical
volume repository is invalid - the
library type has been changed to the
default of library type default.

library type for the specified library is invalid. Because
information is corrected by changing the library type to
the default type.

ANR4221I
ANR4217I
Audit command: The volume status for

is invalid.

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
indicating that it should have a volume status of
private.
ANR4218I
Audit command: The volume status for

is invalid - the volume status will be
changed to private.

volume status for the specified library and volume is
set to scratch. This is incorrect because storage agents
has a volume name for the library and volume which
indicates that it should have a volume status of private.
the incorrect volume status is set to private.
Audit command: An error (error code) was

found with archive description for node
(node identifier), description (description),
objects (old object count,new object count),
count (old directory count,new directory
count) - entry will be deleted or updated.
Explanation: A database audit process has found an

error with the specified archive description. Because
FIX=YES has been specified for the command, the entry
is deleted or updated.
ANR4222I

found with archive description for node
(node identifier), description (description),
objects (old object count,new object count),
count (old directory count,new directory
count).

error with the specified archive description.

429
ANR4223I ANR4231E
ANR4223I

found with converted archive object for
node (node identifier), description
(description identifier), object (object.ID),
filespace (filespace identifier) - entry will
be deleted.

error with the specified converted archive object.
the entry is deleted.
ANR4227E

inconsistent information for a file aggregate. This
problem cannot be corrected by the audit process, but
the file data is not deleted.
ANR4228E

ANR4224I

found with converted archive object for
node (node identifier), description
(description identifier), object (object.ID),
filespace (filespace identifier).

error with the specified converted archive object.
Audit command: table entry for archive

object (object.ID), node (node identifier),
description (description), filespace
(filespace identifier) not found - the entry
will be created.

converted table table entry for the specified archive
command, an entry will be created.
ANR4226I
Audit command: table entry for archive

object (object.ID), node (node identifier),
description (description), filespace
(filespace identifier) not found.

information detected for file aggregate
(Aggregate.ID).

or incorrect information for a file aggregate. This
ANR4229E

ANR4225I
Audit command: Inconsistent information

detected for file aggregate (Aggregate.ID).

information detected for file aggregate
(Aggregate.ID) - It will be corrected.

or incorrect information for a file aggregate. Because
ANR4230I
Audit command: Auditing data storage

definitions.

database audit and indicates that the data storage
definitions are being examined by the database audit
process.
Audit command: Invalid device class
strategy strategy for device class device
class name.

converted table table entry for the specified archive
object.
ANR4231E
Explanation: A database audit process finds a device

class with an invalid access strategy.


FIX=YES so that the access strategy can be corrected.
430
ANR4232E ANR4240E
ANR4232E

strategy strategy for device class device
class name - information will be
corrected.
Explanation: A database audit process finds a device

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.
FIX=YES so that the attribute can be corrected.

ANR4237E
Audit command: An invalid access

strategy was encountered for storage
pool storage pool name - the strategy will
be corrected.

invalid device access strategy for the specified storage
pool. Because FIX=YES has been specified for the
command, the storage pool access strategy will be
corrected.
ANR4233E
Audit command: Pool ID information is

missing or incorrect for storage pool
storage pool name.

pool whose pool ID information is missing or incorrect.

examine the storage pool using the QUERY STGPOOL
command, and verify that the correct information is
displayed for this storage pool.
ANR4238E

FIX=YES so that the access strategy can be corrected.
ANR4234E
Audit command: Pool ID information is

missing or incorrect for storage pool
storage pool name - information will be
created or corrected.

pool whose pool ID information is missing or incorrect.
command, the pool ID information will be created or
corrected for this storage pool.
Explanation: The specified storage pool references an

invalid pool ID as its next storage pool.
to update the next pool. Alternatively, if the audit
command is reissued with FIX=YES, the reference to
the next pool will be deleted.
ANR4239E

ANR4235E
Audit command: Device class ID

referenced by storage pool storage pool
name is not defined - data in this pool
may not be available.

pool which references a device class ID which is not
defined.
ANR4236E

strategy was encountered for storage

invalid device access strategy for the specified storage
pool.

name specifies an undefined pool ID for
its next storage pool.

name specifies an undefined pool ID for
its next storage pool - reference will be
deleted.
Explanation: The specified storage pool references an

invalid pool ID as its next storage pool. Because
reference is deleted. The specified storage pool will not
have a next pool.
use the UPDATE STGPOOL command to assign a next
storage pool, if desired.
ANR4240E
Audit command: An invalid attribute was

encountered for storage pool storage pool
name.

invalid attribute for the specified storage pool.

431
ANR4241E ANR4248E
ANR4241E
Audit command: An invalid attribute was

encountered for storage pool storage pool
name - the attribute will be assigned its
default value.

invalid attribute for the specified storage pool. Because
storage pool will be corrected using the default value
for the attribute.
ANR4245E

strategy was encountered for volume
volume name.

invalid device access strategy for the specified volume.
FIX=YES so that the strategy can be corrected.

examine the storage pool using the QUERY STGPOOL
command, and correct attributes with the UPDATE
STGPOOL command, if desired.
ANR4242E


information pertaining to the last update for the
specified storage pool.
ANR4246E

invalid device access strategy for the specified volume.
the access strategy will be corrected for this volume.
ANR4247E

ANR4243E

storage pool storage pool name information will be corrected.

information pertaining to the last update for the
specified storage pool. Because FIX=YES has been
specified for the command, the information is
corrected.
ANR4244E
Audit command: Storage pool ID

referenced by volume volume name is not
defined - data on this volume may not
be available.
Explanation: A database audit process finds a data

storage volume which references a storage pool ID that
is not defined.
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
redefine it. If this does not work, contact your service
representative.

strategy was encountered for volume
volume name - the strategy will be
corrected.
Audit command: Missing information for

volume volume name cannot be created.
Delete the volume after optionally
moving any files from the volume.

missing database information for the specified volume.
Since FIX=YES has been specified for the audit
command, an attempt is made to create the missing
information where possible. However, some of the
information cannot be created, and the volume must be
deleted.
System action: The access mode for the volume is set
to UNAVAILABLE to prevent further attempts to write
to this volume. Audit processing continues.
User response: After audit processing completes, an
administrator should take the following actions to
eliminate the volume
v (Optional) Use the UPDATE VOLUME command to
set the access mode for the volume to READWRITE.
It may then be possible to use the MOVE DATA
command to move files from the volume so that
these files can be accessed by the server.
v (Required) Use the DELETE VOLUME command to
delete the volume from the database.
ANR4248E

information for storage volume volume
name.

storage volume for which information is missing or
incorrect.
432
ANR4249E ANR4257E
corrected.
ANR4249E

information for storage volume volume
name - information will be created or
corrected.

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
corrected.
ANR4253E

locate the global attributes for data storage in the
regenerated.
ANR4254E

ANR4250E
Audit command: Extraneous reference

found.

reference to a nonexistent entity such as a storage pool
or volume.
Audit command: Data storage global

attributes cannot be found - attributes
will be recreated.
Audit command: Data storage high-water

use.

information used to track data storage identifiers is
incorrect.

FIX=YES so that the non-existant entity is recreated, if
possible. If recreation is not possible, the extraneous
reference is deleted.
ANR4251E
Audit command: Extraneous reference

found - information will be recreated or
deleted.

reference to a nonexistent entity such as a storage pool
or volume. Since FIX=YES has been specified for the
audit command, the nonexistant entity will be
recreated, if possible. If recreation is not possible, the
ANR4255E
Audit command: Data storage high-water

use - they will be corrected.

information used to track data storage identifiers is
incorrect. Because FIX=YES has been specified for the
audit command, the error will be corrected.
ANR4256I

definitions for disk volumes.

database audit and indicates that the database
information relating to data storage disk volumes is
being examined by the database audit process.
ANR4252E
Audit command: Data storage global

attributes cannot be found.

locate the global attributes for data storage in the
server database.

ANR4257E
Audit command: A correctable

data-integrity error was detected on
volume volume name.

data-integrity error for a file stored on the specified
volume. This error is correctable.
433
ANR4258E ANR4267E
ANR4258E
Audit command: A data-integrity error

was detected on volume volume name the error will be corrected.

correctable data-integrity error for a file stored on the
specified volume. Because FIX=YES has been specified
for the audit command, the error will be corrected.
ANR4259E
Audit command: Invalid data encountered

for a file in data storage - data can be
corrected.
Explanation: A database audit process finds invalid

data for a file in data storage. The error should be
correctable.

User response: After audit processing has completed,
use the UPDATE VOLUME command to set the access
information for this volume, if desired.
ANR4263I

definitions for sequential volumes.

database audit and indicates that the database
information relating to data storage sequential volumes
is being examined by the database audit process.
ANR4264I
Audit command: Auditing file

information.

database audit and indicates that information on stored
files is being examined by the database audit process.
ANR4260E
Audit command: Invalid data encountered

for a file in data storage - the error will
be corrected.

data for a file in data storage. Because FIX=YES has
been specified for the audit command, the error will be
corrected.

ANR4265I
Audit command: Auditing disk file

information.

database audit and indicates that information on files
stored on disk media is being examined by the

ANR4261E
Audit command: Invalid access

information was encountered for
volume volume name.

invalid access information for the specified volume.
User response: After audit processing has completed,
use the UPDATE VOLUME command to set the access
information for this volume. Or reissue the audit
command with FIX=YES, which sets access to the
default value.
ANR4266I

database audit and indicates that information on files
stored on sequential media is being examined by the
ANR4267E
ANR4262E
Audit command: Invalid access

information was encountered for
volume volume name - the information
will be corrected.

invalid access information for the specified volume.
the information will be corrected by setting the default
value.
434
Audit command: Auditing sequential file

information.
Audit command: A storage pool

containing file data cannot be located file data may not be accessible.

database audit and indicates that the storage pool
containing a files data cannot be located or is not
defined. This problem cannot be corrected by the audit
process, but the file data is not deleted.
ANR4268E ANR4277E
ANR4268E
Audit command: A storage volume


database audit and indicates that the storage volume
defined. This problem cannot be corrected by the audit
process, and the file data is deleted.
ANR4269E
Audit command: Extraneous file data

reference found.

reference to a file that no longer exists.
FIX=YES so that the information can be deleted.
ANR4270E
Audit command: Extraneous file data

reference found - information will be
deleted.

reference to a file that no longer exists. Because
ANR4273E

was detected on volume volume name Issue the AUDIT VOLUME command to
correct the error.

data-integrity error for a file stored on the specified
volume.
User response: Issue the AUDIT VOLUME command
on the specified volume to correct the data-integrity
error.
ANR4274E
Audit command: A correctable

data-integrity error was detected.

data-integrity error for a stored file. This error can be
corrected.
ANR4275E

was detected - it will be corrected.

data-integrity error for a stored file. Because FIX=YES
has been specified for the audit command, the error
will be corrected.

ANR4271E

occupancy information detected.

or incorrect occupancy information for a data storage
pool or a data storage volume.
corrected.
ANR4272E

occupancy information detected information will be created or corrected.

or incorrect occupancy information for a data storage
pool or a data storage volume. Because FIX=YES has
been specified for the audit command, the information
will be created or corrected.
ANR4276E
Audit command: Invalid file storage

information detected - file data is not
accessible.

file storage information for a stored file, and it cannot
be corrected.
on all your volumes to correct the data-integrity error.
ANR4277E

information detected.

file storage information for a stored file. This
435
ANR4278E ANR4284I
ANR4278E

information detected - It will be
corrected.

file storage information for a stored file. Because
ANR4279E

administrator number assigned to more
than just system authority class.

administrator is assigned to other authority classes.
Being assigned with 'SYSTEM' authority supersedes all
other classes and the other privilege class entries
should be deleted.
ANR4282I

specified administrator is assigned as an unrestricted
policy administrator. The specified administrator is also
assigned as the restricted administrator for the
specified policy domain. The unrestricted policy
administration class supersedes any restricted policy
class definitions for an administrator. Because FIX=YES
has been specified for the command, the restricted
administrator policy class will be deleted.
ANR4283E

ANR4280I

administrator number assigned to more
than just system authority class - the
other class entries will be deleted.

administrator is assigned to other authority classes.
Being assigned with 'SYSTEM' authority supersedes all
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
will be deleted.

administrator number assigned as an
unrestricted policy administrator is also
assigned as administrator for domain
domain name - restricted class entry will
be deleted.

unrestricted storage administrator is also
assigned as a restricted administrator for

storage administrator. The specified administrator is
also assigned as the restricted administrator for the
specified storage pool. The unrestricted storage
administration class supersedes any restricted storage
class definitions for an administrator. The
administrators authority needs to be corrected.

ANR4281E

unrestricted policy administrator is also
domain domain name.

policy administrator. The specified administrator is also
assigned as the restricted administrator for the
specified policy domain. The unrestricted policy
administration class supersedes any restricted policy
class definitions for an administrator. The
administrators authority needs to be corrected.
ANR4284I

storage administrator. The specified administrator is
also assigned as the restricted administrator for the
specified storage pool. The unrestricted storage
administration class supersedes any restricted storage
class definitions for an administrator. Because FIX=YES
has been specified for the command, the restricted
administrator storage class will be deleted.

436

unrestricted storage administrator is also
storage pool storage pool name - restricted
class entry will be deleted.
ANR4285E ANR4294I
ANR4285E

was detected on a storage volume for
object (Object.ID).

data-integrity error for a file stored on a storage
volume, but the specific volume name is not known. If
fix=yes was specified, the audit process will attempt to
correct the data-integrity error.
ANR4290I
Audit command: License global attributes

could not be found - they will be
created.

license global attributes. Because FIX=YES has been
specified for the command, the information is corrected
by the creation of the global attributes.

ANR4291I
ANR4286E
Audit command: A correctable storage

allocation error detected for volume
volume name.

block allocation information for the specified storage
volume; the error can be corrected.
ANR4287E
Audit command: Storage allocation error

detected for volume volume name - It will
be corrected.

block allocation information for the specified storage
volume; the error will be corrected.
ANR4288E

license global attributes.
ANR4292I
Explanation: A database audit process finds multiple

files allocated the same disk storage block on the
specified volume; this error cannot be corrected by the
audit process.
Audit command: Invalid table active

column encountered for license global
attribute - the value will be corrected.

active column license global attribute is invalid.
the active column is reset to a proper value.
ANR4293I
Audit command: Multiple files allocated

the same disk storage block on volume
volume name.
Audit command: License global attributes

could not be found.
Audit command: Invalid table active

column encountered for license global
attributes.

active column license global attribute is invalid.

ANR4289E
Audit command: Multiple files allocated

the same disk storage block on volume
volume name.
Explanation: A database audit process finds multiple

files allocated the same disk storage block on the
specified volume; this error cannot be corrected by the
audit process.
ANR4294I
Audit command: A license node

node node ID - an entry will be created.

node. Since FIX=YES has been specified for the
command, the required license entry will be created
437
ANR4295I ANR4304E
ANR4295I
Audit command: A license node

node node ID.

node.
ANR4296I
Audit command: An invalid license node

assignment entry was found for node
node ID - the entry will be deleted.

license node assignment entry is invalid. Because
FIX=YES has been specified for the command, the node
entry is deleted.
ANR4297I
Audit command: An invalid license node

assignment entry was found for node
node ID.

license node assignment entry is invalid.
ANR4298I
Expiration thread already processing unable to begin another expiration

process.

ANR4300I
Audit command: Invalid audit interval

encountered for license global
attributes.

audit interval license global attribute is invalid.
ANR4301I
Audit command: Invalid last audit date

encountered for license global attribute the value will be set to 0.

last audit date license global attribute is invalid.
the last audit date is set to 0. The next execution of
AUDIT LICENSES will set a new last audit date.
ANR4302I
Audit command: Invalid last audit date

encountered for license global attribute.

last audit date license global attribute is invalid.
ANR4303E
Audit command: Inventory references for

object(Object.ID) deleted.
Explanation: The expiration thread is already

processing. The processing expiration thread is either
an EXPIRE INVENTORY command or is the automatic
background expiration process. In either case, another
expiration process cannot be started until the current
expiration process completes or is canceled.
Explanation: A database audit process deleted all

inventory references for the specified object ID. This
process corrects a data-integrity error if FIX=YES was
specified.
System action: Current expiration process continues.

to determine the status of the current expiration
process.
ANR4304E
ANR4299I
Audit command: Invalid audit interval

encountered for license global attribute the value will be set to the default.

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.
438
Audit command: object name missing entry

for cluster cluster ID - cluster entries
deleted.
Explanation: A database audit process is missing a

corresponding entry for the specified comparison object
and cluster ID. This process indicates a data-integrity
error for the database cluster information. If FIX=YES
was specified, the invalid cluster information will be
deleted.
ANR4305E ANR4314I
ANR4305E
Audit command: object name missing entry

for cluster cluster ID.
Explanation: A database audit process is missing a

corresponding entry for the specified comparison object
and cluster ID. This indicates a data-integrity error for
the database cluster information.

ANR4310I

space-managed objects.

about space-managed client objects is currently being
ANR4306I
AUDITDB: Processed number of entries

database entries (cumulative).

database entries that have been processed during
database audit processing.
System action: Database audit processing continues.
ANR4311I
Audit command: Object entry for

space-managed object object.ID not
found - entry will be created.

object entry for the specified space-managed object.
an object entry is created by using default values.
ANR4307I

external space-managed objects.

about external space-managed client objects is currently
being examined by the database audit process.
ANR4308I

ANR4312I
Audit command: Object entry for

space-managed object object.ID not
found.

object entry for the specified backup object.
Audit command: External space-managed

entry for node node ID and file space
filespace ID is missing a corresponding
space-managed object entry - the
external space-managed entry will be
deleted.

external space-managed entry is missing a
corresponding space-managed entry. Because FIX=YES
has been specified, the orphaned external
space-managed entry is deleted.

ANR4313I
Audit command: Space-managed object

(object ID) for node node ID and file
space filespace ID has one or more
incorrect fields - the values will be
corrected.
Explanation: A database audit process determined

that one or more field values for the specified
space-managed object is not valid. Because FIX=YES
was specified the values are corrected.

ANR4309I

entry for node node ID and file space
filespace ID is missing a corresponding
space-managed object entry.

external space-managed entry is missing a
corresponding space-managed entry.
ANR4314I

space filespace ID has one or more
incorrect fields.

that one or more field values for the specified
space-managed object is not valid.
439
ANR4315I ANR4323E
ANR4315I

space filespace ID is missing the
corresponding external space managed
entry - the entry will be created.

the space-managed object entry is missing a
corresponding external space managed entry. Because
FIX=YES was specified, the missing entry will be
created.
ANR4319I

not found for object object.ID - object
entry will be deleted.

space-managed object entry for the specified object.
Because FIX=YES was specified the object entry will be
deleted.
ANR4320I

not found for object object.ID.

space-managed object entry for the specified object.
ANR4316I

space filespace ID is missing the
corresponding external space managed
entry.

ANR4321I

the space-managed object entry is missing a
corresponding external space-managed entry.
ANR4317I

object (object ID) for node node ID and
file space filespace ID has one or more
incorrect fields - the values will be
corrected.

that one or more field values for the specified external
space-managed object is not valid. Because FIX=YES
was specified, the values will be corrected.
ANR4318I

object (object ID) for node node ID and
file space filespace ID has one or more
incorrect fields.

invalid copy type for the specified object ID, but finds
a corresponding space-managed object for the entry.
the invalid copy type is corrected.
ANR4322E

440

domain name does not have a valid space
management technique defined.

management class that does not have a valid value
specified.
ANR4323E

that one or more field values for the specified external
space-managed object is not valid.

found as an space-managed object correcting the invalid copy type

domain name does not have a valid space
management technique defined - the
default value will be set.

specified. Because FIX=YES was specified for the
AUDITDB operation, the default space management
ANR4324E ANR4331E
technique value will be set for the management class
specified.
AUDITDB operation, the default MIGREQUIRESBKUP

value will be set for the management class specified.
User response: Refer to the DEFINE MGMTCLASS

command in the Administrators Reference for valid
values.

values.
ANR4324E

domain name does not have a valid
AUTOMIGNONUSE value specified.

specified.
ANR4325E

AUTOMIGNONUSE value defined - the

AUDITDB operation, the default AUTOMIGNONUSE
value will be set for the management class specified.
ANR4328W

storage pool specified for the space management
destination of the specified management class that is
not defined in the server database. If this management
class is used in an active policy set, then migration
operations will fail when attempting to put client data
in the destination.
missing storage pool or the UPDATE MGMTCLASS
command to update the management class to refer to
an existing storage pool.
ANR4329I

values.
ANR4326E

MIGREQUIRESBKUP value specified.

specified.
ANR4327E

MIGREQUIRESBKUP value defined the default value will be set.


name, specified as a space management
destination for management class
management class name, policy set set
exist.
Audit command: Inactive reference found

for active backup entry (Object.ID) - the
inactive reference will be deleted.
Explanation: A database audit process found that an

active backup entry for the specified object has a
corresponding inactive backup entry. Since FIX=YES
was specified for the command, the information is
corrected by deleting the inactive backup object entry.
ANR4330I
Audit command: Inactive reference found

for active backup entry (Object.ID).
Explanation: A database audit process found that an

active backup entry for the specified object has a
corresponding inactive backup entry.
ANR4331E
command process terminated, no

matching device classes.
Explanation: The server did not find any device class

names matching the specifications entered in the
RECONCILE VOLUMES command.
441
ANR4332W ANR4340W
User response: Use the QUERY DEVCLASS command
to determine which device classes are defined on the
server and reissue the RECONCILE VOLUMES
command.
the volumes associated with the given device class.

System action: The volumes are reconciled and
inconsistent volumes are displayed.
ANR4332W
This command will compare all volumes

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

process ID.
Explanation: The RECONCILE VOLUMES command

for the specified device class has ended.
Explanation: During the execution of a RECONCILE

VOLUMES command, any data a volume named
would be unavailable to users.
User response: For complete details on the results of

the RECONCILE VOLUMES command, examine the
previous messages.

continue.
ANR4337W
User response: Enter 'Y' to reconcile the volumes or

'N' to stop the process.
ANR4333W
This command will discard any

references to volumes used by the
specified device class(es) that are
missing from the associated server,
thereby rendering the data
unrecoverable; the valid volumes will
be inaccessible to users until the
Explanation: During the execution of a RECONCILE

VOLUMES command, any data on a volume being
reconciled would be unavailable to users. After the
command has ended, any inconsistent volumes found
will be discarded.
continue.
User response: Enter 'Y' to reconcile the volumes or
'N' to stop the process.
ANR4334I
command (Repair) process started,

process ID process ID.
Explanation: As the result of a RECONCILE

VOLUMES command that specified FIX=YES, the
process whose ID is displayed has begun reconciling
the volumes associated with the given device class.
invalid volumes are displayed.
ANR4335I
command (Inspect Only) process started,

process ID process ID.

VOLUMES command that specified FIX=NO, the
process whose ID is displayed has begun reconciling
442
command process terminated - process

canceled.
Explanation: During processing of a RECONCILE

VOLUMES command, the process performing the
reconcile was canceled.
System action: The RECONCILE VOLUMES
command is ended.
ANR4338W
command process terminated - sufficient

recovery log space is not available.

VOLUMES command, the source server does not have
sufficient recovery log space to continue.
command is ended.
User response: If necessary, make more recovery log
space available to the source server.
ANR4339W

database space is not available.

sufficient database space to continue.
command is ended.
User response: If necessary, make more database
space available to the source server.
ANR4340W
command process terminated - thread

resource not available.

VOLUMES command, the source server cannot start a
thread for the reconcile process.
command is ended.
ANR4341W ANR4354W
User response: Reissue the RECONCILE VOLUMES
command. If the error persists, it may indicate a
shortage of source server memory.
ANR4341W


enough memory available to complete the command.
command is ended.
User response: If necessary make more memory
available to the source server.
ANR4342W
command process terminated - lock

conflict detected.

VOLUMES command, the source server cannot obtain a
required lock.
command is ended.
User response: Reissue the RECONCILE VOLUMES
command.
ANR4343W
command process terminated - internal


VOLUMES command, an internal server error occurs
on the source server.
command is ended.
ANR4344I
command started for device class device

class (process ID process ID).
found or deleted are displayed.

the RECONCILE VOLUMES command for the shown
device class, examine the previous messages.
ANR4346I
command completed for device class

device class; (process ID process ID);
volume count volumes inspected, volume
count invalid volumes found.
Explanation: The RECONCILE VOLUMES process

whose ID is displayed has finished reconciling volumes
associated with the given device class. The number of
volumes reconciled and the number of invalid volumes
found are displayed.
the RECONCILE VOLUMES command for the shown
device class, examine the previous messages. If you
suspect that volumes were inaccessible because of
communications problems, correct the problems and
retry the RECONCILE VOLUMES command. If the
errors are valid, reissue the reconcile volumes
command with FIX=YES so that the source server can
attempt to correct the information.
ANR4352I
Contacting Server server name

reconciliation process is attempting to obtain volume
information from the shown server.
System action: The reconciliation process continues.
ANR4353I
Cancel in progress

whose ID is displayed has started reconciling volumes
associated with the given device class.

reconciliation process has been canceled. The process
will end shortly.

inconsistent volumes are displayed.
System action: The reconciliation process terminates

ANR4345I
command completed for device class

device class; (process ID process ID);
volume count volumes inspected, volume
count invalid volumes found, volume
count volumes deleted.

whose ID is displayed has finished reconciling volumes
associated with the given device class. The number of
volumes reconciled and the number of invalid volumes
ANR4354W
command: Source server not authorized

to reconcile target server server name.

VOLUMES command, the source server was not
permitted to reconcile volume on the shown target
server.
User response: If the source server should have
443
ANR4355W ANR4358W
permission to reconcile volumes on the shown target
server, issue the UPDATE SERVER command with
FORCESYNC=YES to cause the target server to accept
reconcile operations for the source server. Reissue the
RECONCILE VOLUMES command.
ANR4355W
command: Volume volume name not valid,

source server missing corresponding
entry for target server.

VOLUMES command, the volume shown was reported
by the target server and it has no matching volume on
the source server.
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
to the server. Investigate the action that caused one or
both of the databases to be regressed to there current
condition. If a newer database images exist for that
server, consider restoring the server to that point in
time. If the condition of the database on each server is
acceptable and the RECONCILE VOLUMES command
was issued with FIX=NO, reissue the RECONCILE
VOLUMES command with FIX=Yes to have the volume
ANR4356W

target server missing corresponding
entry for source server.

VOLUMES command, the volume shown was found on
the source server and it has no matching volume on the
target server.
target server has been regressed by either an RESTORE
condition. If a newer database images exist for that
time. If the RECONCILE VOLUMES command was
issued with FIX=Yes and the volume is defined in a
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
each server is acceptable, issue the DELETE VOLUME
or DELETE VOLHISTORY command on the source
server to remove the volume from the database.
ANR4357W

target server volume refers to device
class device class that does not exist on
the source server.

the target server and it is associated with the device
class shown. The source server has NO corresponding
device class.
both of the databases to be regressed to their current
condition. If a newer database image exist for that
time. In the case of a volume in the VOLHISTORY, the
device class may have been deleted from the source
server. If possible, issue the DEFINE DEVCLASS
command to correct the situation. If the condition of
the database on each server is acceptable and the
RECONCILE VOLUMES command was issued with
FIX=NO, reissue the RECONCILE VOLUMES
command with FIX=Yes to have the volume deleted
from the target server.
ANR4358W

both the source and target server, but the attributes
describing the volume does not match.
target server has been regressed by either a RESTORE
acceptable, additional actions will have to be taken
because RECONCILE VOLUMES FIX=YES is unable to
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
DELETE VOLHISTORY will remove the volume from
both the source and target servers. In the case of a
volume in a storage pool, an AUDIT VOLUME
FIX=NO will determine the integrity of the volume. If
errors are found, an AUDIT VOLUME FIX=YES may
make some data on the volume accessible. Otherwise,
issue the DELETE VOLUME command on the source
server to remove the volume from both the source and
target servers.
444

the attributes of the volume on target
server do not match the attributes on the
source server.
ANR4359W ANR4363W
ANR4359W

the size of the volume on target server
does not match the size on the source
server.

both the source and target server, but the size of the
volume does not match.
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
DELETE VOLHISTORY will remove the volume from
both the source and target servers. In the case of a
volume in a storage pool, an AUDIT VOLUME
FIX=NO will determine the integrity of the volume. If
errors are found, an AUDIT VOLUME FIX=YES may
make some data on the volume accessible. Otherwise,
issue the DELETE VOLUME command on the source
server to remove the volume from both the source and
target servers.
ANR4360W

the type of the volume on target server
does not match the type on the source
server.

both the source and target server, but the type of the
volume does not match. For example, the volume on
the target server is defined in a storage pool, but the
target server indicates that volume was used for a
DATABASE BACKUP.
condition. If a newer database image exists for that
correct this situation. These actions may have to be
performed on one or both servers. Use the QUERY
VOLHISTORY and QUERY VOLUME commands on

both servers to determine the volume type on each
server. In the case of a volume in the VOLHISTORY, a
DELETE VOLHISTORY on the appropriate server that
will remove the volume on that server. In the case of a
volume in a storage pool, the DELETE VOLUME
command on the appropriate server will remove the
volume on that server.
ANR4361W

the target server has reported damage to
all or part of the volume.

both the source and target server, but the target server
has reported damage to all or part of the volume.
User response: On the target server, an audit with
FIX=NO of the volumes in the storage pool used by the
source server will indicate what which volume on the
target server is damaged. This AUDIT VOLUME
command may be able to reset the damaged indicator
in the database if the damage was temporary due to
hardware problems (for example, dirty tape heads). If
the volume on the target server is in a primary storage
pool that has previously been backed up to a copy
storage pool, attempt to correct the damage by using
the RESTORE STGPOOL command. If attempts to
correct the damage on the target server fail, an AUDIT
VOLUME command FIX=YES from the source server
will mark as damaged in the source server database
each file that is inaccessible and those files will not be
accessed for future operations. If the files are part of an
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
operations involving the file.
ANR4362W
command: Invalid volume volume name

deleted from server server name for
device class device class.

volume shown whose information is displayed is
ANR4363W
command: Volume volume name access

changed to access mode.

access mode of the source volume has been changed to
the value shown.
System action: The volume's access mode is changed.
445
ANR4364W ANR4371E
User response: Review any additional messages
issued by the RECONCILE VOLUMES command and
correct the errors that set the volume to unavailable, or
use the DELETE VOLUME command to remove it from
the system.
FIX=YES and the server will attempt to recreate the

missing volume definition. If the server cannot recreate
the missing volume information, the server will delete
the inaccessible file data.
ANR4368I
ANR4364W
command: Unable to connect to target

server server name.
Explanation: During processing of indicated

command, the source server was unable to maintain
communications with the shown target server.
System action: The command process continues.
User response: Check both the source server and the
target server for any additional messages that might
further describe the communications problem.
ANR4365W
command: Prefix for volume volume name

does not match the device class prefix.

both the source and target server, but the beginning
portion of the high-level archive file name (the prefix)
on the target server does not match the prefix in the
device class on the source server.
User response: Verify that the prefix in the device
class on the source server is correct and update it if
necessary. Use the RECONCILE VOLUMES FIX=YES
command on the source server to rename the target
archive objects to match the device class on the source
server.
ANR4366I
command: Prefix for volume volume name

was changed to match the device class
prefix.

VOLUMES FIX=YES command, the beginning portion
of the high-level archive file name (the prefix) on the
target server was changed to match the prefix in the
device class on the source server.
System action: The prefix is corrected.
Audit command: Attributes for group

group.ID and member member.ID are not
correct - the attributes are corrected.

attributes for the specified group ID and member ID do
not match attributes for the corresponding primary
backup object. Because FIX=YES was specified for the
command, the incorrect attributes are corrected.
ANR4369I
Audit command: Attributes for group

group.ID and member member.ID are not
correct.

attributes for the specified group ID and member ID do
not match attributes for the corresponding primary
backup object.
User response: The AUDITDB process should be
re-issued with FIX=YES specified.
ANR4370E
The source server is not authorized to

create volumes on target server server
name.
Explanation: The source server has attempted to

create a volume on the shown target server, but the
operation failed because the source server does not
have the authority to create volumes.
User response: If the source server should have
permission to create volumes on the shown target
server, issue the UPDATE SERVER command with
FORCESYNC=YES to cause the target server to accept
volume create operations for the source server. Retry
the failing operation.

ANR4371E
ANR4367E
Audit command: A storage volume


database audit and indicates that the storage volume
defined.
446
Information on the source server does

not match information on target server
server name.
Explanation: The source server has determined that

information contained on the shown target server no
longer matches information contained on the source
server.
User response: Issue the RECONCILE VOLUMES
command to determine the problem. If possible, correct
ANR4372E ANR4378E
the problem and retry the failing operation.
ANR4372E
The password on the source server does

not match the password on target server
server name.

update both the source password and the target
password. An error occurred that prevented the source
server from updating the target server. The passwords
no longer match.
User response: On the target server, issue the
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
command to change the password to match the new
password on the target server. Retry the failing
operation.
ANR4373E
Session rejected by target server server

name, reason: rejection reason.
Explanation: The source server tried to open a session

with the target server. The session was rejected for the
indicated reason.
further describe the reason the session was rejected. For
a reason of AUTHENTICATION FAILURE, ensure that
both the source and target servers are using the same
password. For a reason of NO RESOURCE, ensure that
the target server is enabled, has sufficient DB, LOG,
session, and that the node name of the source server is
not locked or in use. If this is a routed command, check
to make sure that the administator id being used to
route the command is not locked or in use. For a
reason of LICENSE FAILURE, ensure that the target
server is properly licensed to support the source server
session. For a reason of DOWN LEVEL, ensure that the
target server program is a level new enough to support
the source server session. For a reason of NODE TYPE,
the source server is not allowed to establish a session
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.
The NODETYPE parameter of the registered node on
the target server is incorrect and should be
NODETYPE=SERVER. For a reason of INTERNAL
ERROR, use the messages on the target server to
determine the problem. For all reasons, if none of the
above are applicable, ensure that that the target server
has not disabled this server with the DISABLE
SESSIONS SERVER command. Retry the failing
operation.
ANR4374E
Session failure, source server detected

an internal error.
Explanation: The source server ends the session

because an internal logic error is detected.
System action: The source server ends the session and
the administrator can examine server messages issued
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,
ANR4375E
Session failure, source server has


available.
application.
ANR4376E
Session failure, target server server name

is locked on the source server.

because shown target server is locked from source
server access.
User response: Before the source server is permitted
to access the target server, a properly authorized
administrator must unlock the target server.
ANR4377E

is not defined on the source server.

because shown target server is not defined on the
source server.
User response: Before the source server is permitted
to access the target server, the target server must be
properly defined.
ANR4378E
For device class device class, the retry of a

session with target server server name has
timed out.

re-establish a session with the shown target server, but
447
ANR4379E ANR4385I
the RETRYPERIOD from the given device class has
been exceeded.
ANR4382E
System action: The source server ends the operation.
Session failure, policy information from

target server server name is incomplete,
missing policy object.
User response: Determine it the target server is

having a problem or considering increasing the
RETRYPERIOD value.

because the shown target server has provided policy
information which is incomplete. The missing policy
object is shown.
ANR4379E

The source server was unable to update

the password on target server server
name.

update the target password. An error occurred that
prevented the source server from updating the target
server.
User response: Use the appropriate commands on the

target server to complete the policy definitions being
used by the source server. Retry the failing operation.
ANR4383E

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 passwords with the
following actions. On the target server, issue the
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
command to change the password to match the new
password on the target server. Retry the failing
operation.
ANR4380E
The source server was unable to update

the server validation key on target
server server name.

has aborted current transaction; reason:
abort reason.

because the shown target server has aborted the current
transaction for the given reason.
further describe the reason the transaction was aborted.
Retry the failing operation.
ANR4384E
Node node name is not allowed to

establish a session as a target server.

update it's server validation key on the target server.
An error occurred that prevented the source server
from updating the target server.
Explanation: The node specified has attempted to

establish a session with this system and this is not
permitted due to the NODETYPE for this node.
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
following actions. On the source server, issue the
UPDATE SERVER command with FORCESYNC=YES to
cause an attempt to synchronize the keys on both the
source and target servers. Retry the failing operation.
User response: To allow the specified node to

establish a session as a target server, the node must be
registered with a NODETYPE of SERVER. Or else
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
NODETYPE=SERVER parameter specified.
ANR4381E
ANR4385I
The source server was unable to register

with target server server name.

register with the shown target server. An error occurred
that prevented the source server from registering with
the target server.
User response: Ask an authorized administrator to
submit the request on the use of the target server using
REGISTER NODE command. Retry the failing
operation.
448
Session retry in progress with target

server server name.
Explanation: The source server is attempting to

re-establish a session with the shown target server.
Session retry processing occurs when the source server
has lost the connection with a target server and a
RETRYPERIOD value is specified,
System action: The source server attempts to contact
the target server.
User response: Determine if the target server is
having a problem and considering canceling the
operation on the source server or correcting the
ANR4386I ANR4397E
PROCESS for that process number. This will cancel the
current expiration process.
problem with the target server.

ANR4386I
Session retry was successful for target

server server name.
ANR4391I
Explanation: The source server has re-establish a

session with the shown target server.
System action: Source server processing continues.
ANR4387E

name not registered as TYPE=CLIENT.

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
TYPE=SERVER using the REGISTER NODE command.
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
should be registered using the REGISTER NODE
TYPE=CLIENT command and specify a name that is
not in use by any other nodes or server defined to this
server.
ANR4388W
Expiration process cancelled.
Explanation: The CANCEL EXPIRATION command

was issued and successfully cancelled the current
process.
ANR4390E

ANR4395I
Audit command: Invalid node type

encountered for node node name.

invalid node type for the node indicated, and FIX=YES
was not specified.
User response: You may want to run this command
again, specifying FIX=YES so that the audit process can
correct the problem.
ANR4396I
Audit command: Invalid node type

encountered for node node name. The
default type will be set.

invalid node type for the node indicated. Because
nodes type to the default value.

ANR4389I
Explanation: Expiration processing is currently

evaluating information for the node, filespace, domain
name, and management class specified for the file type
indicated.
No expiration process to cancel.

was issued but there were no expiration processes
currently running.
Expiration processing node node name,

filespace filespace name, fsId filespace id,
domain domain name, and management
class management class name - for type
type files.
CANCEL EXPIRATION failed - unable

to cancel expiration process.

was issued but encountered an error. Due to this error,
the command was unable to cancel the process.
User response: If you want the node type for the

specified node to be other than the default, you must
remove and re-register the node with the correct type
ANR4397E
Audit command: An invalid data format

was encountered for storage pool storage
pool name.

invalid data format for the specified storage pool.

User response: Issue the command QUERY PROCESS
to determine the process number for the expiration
process and then issue the command CANCEL
449
ANR4398E ANR4409I
ANR4398E
Audit command: An invalid data format

was encountered for storage pool storage
pool name - the data format will be
assigned its default value.

invalid data format for the specified storage pool.
System action: Because FIX=YES has been specified
for the command, the audit process assigns the default
value to the data format. Audit processing continues.
User response: If you want the data format for the
specified storage pool to be other than the default, you
must delete and re-define the storage pool with the
desired type after the audit command has completed.
ANR4402I
Database Dump command: Database

update activity resumed
Explanation: Database update activities that were

suspended by the database dump process are restarted.
(AUDITDB) with FIX=YES is required to return the

database to a consistent state.
System action: Server database load processing
completes.
User response: To check the database for
inconsistencies and correct any inconsistencies, use the
database audit (AUDITDB) utility as described in the
Administrators Reference.
ANR4406I
Audit command: Client option Client

option name sequence number option
sequence number is not a member of an
optionset. The option will be deleted.
Explanation: A database audit process found that the

specified client option does not have a corresponding
optionset. The option is deleted.

ANR4403I
Database Load command: Database dump

image is consistent - a database audit
(AUDITDB) will NOT be required if
this load completes successfully.
Explanation: The database dump that is currently

being loaded by the LOADDB process is a consistent
database image. This process implies that a database
audit (AUDITDB) will not be required if the load
completes successfully.
continues.
ANR4407I

specified client option does not have a corresponding
optionset. The option is deleted.
ANR4408I
User response: None

ANR4404I
Database Load command: Loaded a

consistent dump image - a database
audit (AUDITDB) is NOT required.
Explanation: The database dump image loaded by the

LOAD command was consistent. A database audit
(AUDITDB) is not required. The server may be started
normally.
completes.
Database Load command: Loaded an

inconsistent dump image - a database
audit (AUDITDB) IS REQUIRED with
FIX=YES.
Explanation: The database dump image loaded by the

LOAD command was not consistent. A database audit
450

sequence number in optionset optionset
name is not a valid option. The option
will be deleted.

specified client option is not a valid option. The option
is deleted.
ANR4409I

ANR4405I

sequence number is not a member of an
optionset.

sequence number in optionset option set is
not a valid option.

specified client option is not a valid option.
ANR4410I ANR4418W
ANR4410I
Triggered space expansion will be

retried in number of seconds seconds.

during a triggered space expansion for the database
and/or recovery log, the current expansion stops but
will be retried after the time period shown.
period and then retries to expand the database and/or
recovery log.
stopped the expansion. If the problem persists, contact
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
database and/or recovery log.
System action: Space expansion begins.
ANR4412I
Data Base and Recovery Log Space

expansion triggered.

ANR4415I
Data Base and Recovery Log Space

Expansion Completed.
Explanation: A triggered space expansion had

completed.
System action: Normal operations resume.
ANR4416W
Unable to Determine Maximum Number

of Data Base Volume Copies, rc=return
code.
Explanation: The Data Base Space Trigger was in the

processing of expanding the data base by creating new
database volumes. In doing so, the maximum number
of copy volumes for any database volume is
determined. The process of determining this value
failed.
additional database copy volumes are created during
this database space expansion.
User response: Use the Query DBVOL command to
determine if your database volume configuration is
satisfactory. You may use the DEFINE DBCOPY
command to define additional database volume copies,
if necessary.
Explanation: A triggered space expansion had started.

ANR4417W

ANR4413I
Recovery Log Space expansion Is

Needed, megabytes needed Megabytes
needed.
Explanation: The recovery log is above the utilization

percentage defined in a DEFINE SPACETRIGGER LOG
command. An expansion of the indicated number of
megabytes are needed to be above the space trigger
utilization value.
System action: Space expansion begins if supported
on this platform.
ANR4414I
Data Base Space expansion Is Needed,

megabytes needed Megabytes needed.
Explanation: The database is above the utilization

percentage defined in a DEFINE SPACETRIGGER DB
command. An expansion of the indicated number of
megabytes are needed to be above the space trigger
utilization value.
System action: Space expansion begins if supported
on this platform.
Unable to Create Data Base Copy

Volume Data Base Copy Volume for
volume Data Base Volume.

database volumes. In doing so, database copy volumes
are created for mirroring. The indicated database copy
volume could not be created for the primary database
volume named.
System action: Server operation continues. A database
copy volume is not created for the indicated primary
volume.
command to define additional database volume copies,
if necessary.
ANR4418W
Unable to Define Data Base Copy

Volume Data Base Copy Volume for
volume Data Base Volume.

database volumes. In doing so, database copy volumes
are created for mirroring. The indicated database copy
volume was created for the primary database volume
451
ANR4419W ANR4425W
named, but could be registered with the server.
copy volumes is not registered for the indicated
primary volume. The database copy volume still exists
on the system.
command to retry the definition of the database
volume copy, if necessary.
ANR4419W
Unable to Determine Maximum Number

of Recovery Log Volume Copies,
rc=return code.
Explanation: The Recovery Log Space Trigger was in

the processing of expanding the recovery log by
creating new recovery log volumes. In doing so, the
maximum number of copy volumes for any recovery
log volume is determined. The process of determining
this value failed.
additional recovery log copy volumes are created
during this recovery log space expansion.
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
Unable to Create Recovery Log Copy

Volume Recovery Log Copy Volume for
volume Recovery Log Volume.

creating new database volumes. In doing so, recovery
log copy volumes are created for mirroring. The
indicated recovery log copy volume could not be
created for the primary recovery log volume named.
System action: Server operation continues. A recovery
log copy volume is not created for the indicated
primary volume.
command to define additional recovery log volume
copies, if necessary.
ANR4421W
Unable to Define Recovery Log Copy

Volume Recovery Log Copy Volume for
volume Recovery Log Volume.

creating new recovery log volumes. In doing so,
recovery log copy volumes are created for mirroring.
The indicated recovery log copy volume was created
452
for the primary recovery log volume named, but could

be registered with the server.
log copy volume is not registered for the indicated
primary volume. The recovery log copy volume still
exists on the system.
command to retry the definition of the recovery log
volume copy, if necessary.
ANR4422I
AUDITDB: Insufficient database space

to optimze audit processing.
Explanation: A database audit process found that

insufficient database space is available to optimize
audit processing. If the audit can process, it will take
much longer to complete than if the space was
available.
System action: Audit processing continues of possible,
but may terminate if very little space is available.
User response: Use the dsmserv extend db command
to increase the size of the server datbase and restart the
database audit function.
ANR4423I
AUDITDB: Insufficient database space

to continue audit processing.
Explanation: A database audit process found that

insufficient database space is available to continue
audit processing.
System action: Audit processing terminates.
User response: Use the dsmserv extend db command
to increase the size of the server datbase and restart the
database audit function.
ANR4424W
Database has reached Maximum Size in

Space Trigger.
Explanation: The Data Base Space Trigger was

specified with a maximum size for the data base. That
value has been reached for the size of the database.
additional database space expansion will occur as a
result of the database space trigger.
User response: None. You may review the space
trigger settings and use the UPDATE SPACETRIGGER
DB command to adjust space trigger values.
ANR4425W
Recovery Log has reached Maximum

Size in Space Trigger.
Explanation: The Recovery Log Space Trigger was

specified with a maximum size for the recovery log.
ANR4426W ANR4431I
That value has been reached for the size of the recovery
log.
additional recovery log expansion will occur as a result
of the recovery log space trigger.
LOG command to adjust space trigger values.
ANR4426W
Recovery Log can no longer be

Expanded by the Space Trigger.
Explanation: The Recovery Log Space Trigger was

going to automatically expand the recovery log.
Expanding the recovery log would cause the recovery
log's size to exceed 13GB, which is beyond the server
maximum limit for the recovery log.
recovery log is not automatically expanded. No
additional recovery log expansion will occur as a result
of the recovery log space trigger.
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
recovery log utilization and you then use the REDUCE
LOG and DELETE LOGVOLUME command to
decrease the size of the recovery log.
ANR4427W
One or more Recovery Log Volumes

differ in number of copy volumes.

creating new volumes. In doing so, copy volumes are
created for mirroring, and existing volumes are
examined for mirroring. One or more recovery log
volumes was found to have a different number of copy
volumes than other volumes of the same type. It is
recommended that the same number of copy volumes
be created for each volume of the same type (database
or log).
mirroring, and existing volumes are examined for

mirroring. One or more data base volumes was found
to have a different number of copy volumes than other
volumes of the same type. It is recommended that the
same number of copy volumes be created for each
volume of the same type (database or log).
determine if your volume configuration is satisfactory.
You may use the DEFINE DBCOPY command to define
additional copy volumes, if necessary. You may use the
DELETE DBCOPY command to delete unnecessary
copy volumes.
ANR4429W
Unable to Define Recovery Log Volume

Recovery Log Volume.

creating new recovery log volumes. The indicated
recovery log volume was created, but could not be
log volume is not registered with the server. The
recovery log copy volume still exists on the system.
User response: Use the Query LOGVOL command to
command to retry the definition 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.
ANR4430W
Unable to Define Data Base Volume

Data Base Volume.

database volumes. The indicated database volume was
created, but could not be registered with the server.
volume is not registered with the server. The database
volume still exists on the system.

determine if your volume configuration is satisfactory.
You may use the DEFINE LOGCOPY command to
define additional copy volumes, if necessary. You may
use the DELETE LOGCOPY command to delete
unnecessary copy volumes.

satisfactory. You may use the DEFINE DBVOLUME
command for the database volume named, to retry the
definition of the database volume copy, if necessary.
There will be an additional message in the activity log
prior to this message indicating the reason for the
failure.
ANR4428W
ANR4431I
One or more Data Base Volumes differs

in number of copy volumes.

volumes. In doing so, copy volumes are created for
Recovery Log now Eligible for

Expansion.
Explanation: The Recovery Log Space Trigger has

previously hit a point where expanding the recovery
log would have caused the recovery log's size to exceed
453
ANR4432W ANR4438E
13GB, which is beyond the server maximum limit for
the recovery log. This caused automatic recovery log
expansion to be halted. The recovery log size has
shrunk but once again needs expansion and is now
eligible for expansion.
System action: Server operation continues, and the
automatic recovery log expansion will proceed.
User response: None. None.
ANR4432W
Data Base can no longer be Expanded

by the Space Trigger.
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
exceed 500GB, which is beyond the server maximum
limit for the database.
database is not automatically expanded. No additional
database expansion will occur as a result of the
recovery log space trigger until the database size is less
than the maximum size and the trigger attributes allow
it to be expanded to a size less than the maxium.
DB command to adjust space trigger values. You may
also reduce the database size, if possible.
ANR4433I
Data Base now Eligible for Expansion.
Explanation: The Data Base Space Trigger has

previously hit a point where expanding the database
would have caused the size of the database to exceed
500GB, which is beyond the server maximum limit for
the database. This caused automatic database expansion
to be halted. The database size has shrunk or the space
trigger values have been adjusted to allow expansion.
System action: Server operation continues, and
automatic database expansion may proceed.
ANR4434E
Audit command: Password expiration

found for unknown client node node
name.

password expiration period for a client node, but the
client node is not defined correctly in the server
database.
corrected.
454
ANR4435I

period deleted for unknown client node
node name.

password expiration period for a client node, but the
client node is not defined correctly in the server
database. Because FIX=YES has been specified for the
audit command, the audit function deletes the
password expiration period.
ANR4436E
Audit command: Invalid password

expiration password expiration period for
Explanation: A database audit process finds an invalid

password expiration period for a client node.
corrected.
ANR4437I

expiration period password expiration
period deleted for client node node name.

password expiration period for a client node. Because
audit function deletes the password expiration period,
causing the default, global password expiration period
to take effect for the client node.
that was updated. Use the UPDATE NODE command
to set the correct password expiration period for the
node.
ANR4438E

found for unknown administrator
administrator name.

password expiration period for an administrator, but
the administrator is not defined correctly in the server
database.
corrected.
ANR4439I ANR4447E
ANR4439I

period deleted for unknown

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
audit command, the audit function deletes the
ANR4440E
ANR4443I

extended attribute type that is not supported. Because
audit function deletes extended attribute.
ANR4444W

expiration password expiration period for

password expiration period for an administrator.
corrected.
expiration period password expiration
period deleted for administrator
administrator name.

password expiration period for an administrator.
command, the audit function deletes the password
expiration period, causing the default, global password
expiration period to take effect for the administrator.
use the QUERY ADMIN command to examine the
administrator that was updated. Use the UPDATE
ADMIN command to set the correct password
expiration period for the administrator.
Command: Input volume volume name

cannot be processed.
Explanation: During a DSMSERV DISPLAY

DBBACKUPVOLUME command, the server cannot
display the necessary information about the specified
backup volume.
System action: The volume is not processed.
Processing continues for all the volumes in the given
volume list.
User response: Examine previous error messages for
the cause of failure.
ANR4445I
ANR4441I
Audit command: Invalid extended

attribute extended attribute type has been
deleted.
Context parameter set to value.
Explanation: Determines if context reporting will be

generated when an ANR9999D error occures. This is
turned on or off with the SET CONTEXT messaging
command.
ANR4446I
Audit command: Auditing address

definitions.

database audit and indicates that the name address
definitions are being examined by the database audit
process.
ANR4442E
Audit command: Extended attribute

extended attribute type is not a valid
attribute type.

extended attribute type that is not supported.
corrected.
ANR4447E
Audit command: An invalid data mover

type was encountered for data mover
name.

invalid data mover type for the specified data mover.
455
ANR4448E ANR4456E
ANR4448E

type was encountered for data mover
datamover name - the data mover entry
will be removed.

invalid data mover type for the specified data mover.
for the command, the data mover entry will be
removed. Audit processing continues.
User response: If you want the data mover entry to be
defined you must redefine this data mover after the
audit command has completed.
ANR4449E

attribute was encountered for data mover
name.
Explanation: A database audit process encountered an

invalid data mover attribute for the specified data
mover.
FIX=YES has been specified for the command, the disk

entry will be removed.
User response: If you want the disk entry to be
defined you must redefine this disk after the audit
command has completed.
ANR4453E

invalid source attribute in a path definiton with the
specified source name and destination name.
ANR4454E

ANR4450E

attribute was encountered for data
mover data mover name - the data mover

invalid data mover attribute for the specified data
mover.
for the command, the data mover entry will be
removed. Audit processing continues.
User response: If you want the data mover entry to be
defined you must redefine this data mover after the
ANR4451E
Audit command: An invalid disk attribute

was encountered for disk name.

invalid disk attribute for the specified disk.
Audit command: An invalid source

attribute was encountered for source
name and destination destination name
Audit command: An invalid source

name and destination destination name the path entry will be removed.

invalid source attribute in a path definition with the
specified source name and destination name. Because
FIX=YES has been specified for the command, the path
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
ANR4455E
Audit command: An invalid destination

name and destination destination name

invalid destination attribute in a path definiton with
the specified source name and destination name.

ANR4452E
Audit command: An invalid disk attribute

was encountered for disk name - the disk

invalid disk attribute for the specified disk. Because
ANR4456E
Audit command: An invalid destination

name and destination destination name the path entry will be removed.

invalid destination attribute in a path definition with
the specified source name and destination name.
the path entry will be removed.
456
ANR4457E ANR4464I
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
ANR4457E
Audit command: KEEPMP found for

unknown client node node name.

KEEPMP setting for a client node, but the client node is
not defined correctly in the server database.
corrected.
ANR4458I
Audit command: KEEPMP setting deleted

for unknown client node node name.

KEEPMP setting for a client node, but the client node is
not defined correctly in the server database. Because
audit function has deleted the KEEPMP setting.
ANR4461E
Audit command: TCP name, address and

GUID found for unknown client node
node name.
Explanation: A database audit process found a TCP

name, address and globally unique identifer for a client
node, but the client node is not defined correctly in the
server database.
corrected.
ANR4462I
Audit command: TCP name, address and

GUID deleted for unknown client node
node name.
Explanation: A database audit process found a TCP

name, address and globally unique identifer for a client
node, but the client node is not defined correctly in the
for the audit command, the audit function deletes the
TCP name, address and GUID.

ANR4463E
ANR4459E
Audit command: Invalid KEEPMP setting

KEEPMP setting for client node node
name.
Audit command: Invalid TCP name,

address or GUID length invalid length for

invalid KEEPMP setting for a client node.

invalid TCP name, address or globally unique identifer
length for a client node.

corrected.

corrected.
ANR4460I
Audit command: Invalid KEEPMP setting

KEEPMP setting deleted for client node
node name.

invalid KEEPMP setting for a client node. Because
audit function has deleted the KEEPMP setting, causing
the default, KEEPMP setting to take effect for the client
node.
to set the correct KEEPMP setting for the node.
ANR4464I
Audit command: Invalid TCP name,

address or GUID length invalid length
deleted for client node node name.

invalid TCP name, address or globally unique identifer
length for a client node. Because FIX=YES has been
specified for the audit command, the audit function
sets the TCP name, address and GUID to blank. The
values will be reset when the client signs on to the
server.
that was updated. The values should be blank.
457
ANR4465I ANR4474I
ANR4465I
Audit command: An incorrect transaction

group size was found for node node
name.

invalid information used for controlling the transaction
group size for the node indicated.
server-prompted scheduling..
corrected.

corrected.
ANR4466I
Audit command: An incorrect transaction

group was found for node node name.
This information will be corrected.

invalid information used for controlling the transaction
group size for the node specified. Because FIX=YES has
been specified, the audit function corrects the
information.
ANR4472I
Audit command: Invalid TCP name or

length for server-prompted
scheduling.invalid length deleted for

invalid TCP name or length for a client node's
server-prompted scheduling attributes. Because
audit function sets the TCP information to blank. The
values must be reset with the UPDATE NODE
command.
that was updated. The values should be blank.

ANR4473E
ANR4467E
Audit command: Data Path Type Path was

found for unknown client node node
name.
Explanation: A database audit process found a Data

Path setting for a client node, but the client node is not
defined correctly in the server database.
corrected.
Explanation: A database audit process found a session

initiation value for a client node's server-prompted
scheduling but the node definition was missing.
corrected.
ANR4474I
ANR4468I
Audit command: The Data Path Type Path

setting was deleted for unknown client
node node name.
Explanation: A database audit process found a Data

Path setting for a client node, but the client node is not
defined correctly in the server database. Because
audit function has deleted the KEEPMP setting.
ANR4471E
Audit command: Invalid TCP address (

server-prompted scheduling ) or length
invalid length for client node node name.
Audit command: Node missing from

session initiation value for
server-prompted scheduling. Attribute
Explanation: A database audit process found a value

for a client node's server-prompted session iniiating
attributes, but the node definition was mising. Because
audit function sets the value to the default. The
attribute must be redefined with the REGISTER or
UPDATE NODE commands.
that was updated.

invalid TCP address or length for a client node's
458

session initiation attribute for client
node node name.
ANR4475E ANR4483I
ANR4475E

client address attribute for client node
node name.
Explanation: A database audit process found client

node addressing information for a client node's
server-prompted scheduling but the node definition
was missing.
corrected.

to set the correct data path setting for the node.
ANR4479I
Explanation: An extraneous or incorrect entry was

found for a member of a backup group.
User response: Issue the AUDITDB command again,
using the FIX=YES parameter.
ANR4480I
ANR4476I

session initiation value for
server-prompted scheduling. Attribute
Explanation: A database audit process found client

node addressing information for a client node's
server-prompted scheduling but the node definition
was missing.
command, the audit function deletes the value. The
information must be redefined with the REGISTER or
UPDATE NODE commands.
ANR4477E
Audit command: An invalid data path type

path setting was found for client node
node name.

incorrect data path setting for a client node.
function, specifying FIX=YES so that the error can be
corrected.
ANR4478I
Audit command: An incorrect data path

type path setting was deleted for client
node node name.

invalid data path setting for a client node. Because
audit function has deleted the Data Path setting,
causing the default Data Path setting to take effect for
the client node.
Extraneous or incorrect entry fixed for a

backup group member.

found for a member of a backup group. If this was an
incorrect entry, it was fixed. If this was an extraneous
entry, it was deleted.
User response: None, becasue the AUDITDB
processing performed the necessary corrective action.
ANR4481I

that was updated.
Extraneous or incorrect entry found for a

backup group member.
Command: Extraneous or incorrect entry

found for a proxy association. Target:
node_id_1 Agent: node_id_2

found for a proxy association.
User response: Issue the AUDITDB command again,
using the FIX=YES parameter.
ANR4482I
Command: Extraneous or incorrect entry

found for a proxy association. Target:
node_id_1 Agent: node_id_2

found for a proxy association. The entry will be
removed.
User response: None, because the AUDITDB
processing performed the necessary corrective action.
ANR4483I
Node node name issued command: Set

Access copy type file space namehigh-level
addresslow-level address authorized node
name ,authorized owner name.
Explanation: The SET ACCESS command completed.


459
ANR4484I ANR4492I
ANR4484I
Node node name issued command: Delete

Access copy type file space namehigh-level
addresslow-level address authorized node
name ,authorized owner name.
Explanation: The DELETE ACCESS command

completed.
ANR4485I
A storage pool space trigger has been

defined and enabled for storage pool
storage pool name.
Explanation: A storage pool space trigger has been

defined with a DEFINE SPACETRIGGER command for
the specified storage pool.
ANR4486I
A default storage pool space trigger has

been defined and enabled.
Explanation: A default storage pool space trigger has

been defined and enabled. It will be effective for any
storage pools associated with a devtype=DISK device
class or a devtype=FILE device class.

ANR4489I

has successfully completed for the indicated storage
pool space trigger. Space expansions are no longer
triggered automatically for the specified storage pool. If
a default storage pool space trigger exists, it will apply
to the specified storage pool.
ANR4490I

ANR4491I

The storage pool space trigger is defined
for storage pool storage pool name, but is
disabled.
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
space trigger is disabled.
ANR4488I
The default storage pool space trigger is

defined, but it is disabled.
Explanation: A default storage pool space trigger has

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
expansion percentage is currently set to 0, the space
trigger is disabled.
The storage pool space trigger is

updated and enabled for storage pool
storage pool name.

has successfully completed for the specified storage
pool space trigger. The updated parameters specified
on the command are used to automatically trigger
space expansion for the storage pool.
ANR4492I

updated and enabled.

has successfully completed for the default storage pool
space trigger. The updated parameters specified on the
expansion for storage pools without a specific storage
pool space trigger and which are associated with a
devtype=FILE or devtype=DISK device class.

460
The default storage pool space trigger

has been deleted.

space trigger. Space expansions are no longer triggered
automatically for storage pool without a specific space
trigger.
ANR4487I
The storage pool space trigger has been

deleted for storage pool storage pool
name.
ANR4493I ANR4500I
ANR4493I
The storage pool space trigger is

updated, but disabled for storage pool
storage pool name.

has successfully completed for the specified storage
pool space trigger. However, the space expansion
percentage is currently set to 0, which disables the
space trigger.
zero.
ANR4494I

updated, but disabled.

space trigger. However, the space expansion percentage
is currently set to 0, which disables the space trigger.
zero.
ANR4495E
Command: Storage pool space trigger is

not defined.
ANR4497E
Command: EXPansionprefix not valid for

storage pool space trigger with storage
pool Storage Pool.
Explanation: The storage pool space trigger cannot be

defined with an EXPansionprefix parameter because the
specified storage pool is not associated with a
DISK-type device class. Sequential access storage pools
use their associated directories for creating space when
a space trigger is activated.
command.
command to create a space trigger without using the
EXPansionprefix parameter.
ANR4498E
Command: STGPOOL Storage Pool is not

eligible for a storage pool space trigger.
Explanation: The indicated storage pool cannot have a

space trigger defined, because it is not associated with
a DISK-type or a FILE-type device class, or it is a
RECLAMATIONTYPE=SNAPLOCK storage pool.
command.
User response: Use the DEFINE SPACETRIGGER
command to create a space trigger with a storage pool
whose device class is of type DISK or FILE, or is not a
RECLAMATIONTYPE=SNAPLOCK storage pool.
ANR4499E
Command: Base backup set name Backup

Set Name could not be found.

If a storage pool was not specified, an attempt was
made to delete the default storage pool space trigger,
but no default storage pool space trigger is defined.
Explanation: No full backup sets whose name begins

with the specified backup set name prefix could be
found.

command.

command.
User response: Use the QUERY BACKUPSET

command to list available full backup sets and reissue
the command with the backup set name prefix of an
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.

defined because it is already defined for the storage
pool. If a default storage pool trigger is being defined,
a default storage pool trigger already exists.
command.
parameters.
ANR4500I
Writing sequential volume history

information to defined files.
Explanation: The server is updating all sequential

volume history files defined in the server options file
with information on sequential volume usage
information. The files updated are those specified with
the VOLUMEHISTORY option in the server options
file.
461
ANR4501I ANR4511E
ANR4501I
Sequential volume history information

successfully written to file name.
Explanation: The server is updating all sequential

volume history files defined in the server options file
with information on sequential volume usage
information. Volume history information was
successfully written to the file specified.
ANR4502W
No files have been defined for

automatically storing sequential volume
Explanation: The server is attempting to update all

sequential volume history files defined in the server
options file with information on sequential volume
usage information. Because no files were configured for
receiving this information, the automatic operation
fails.
User response: To have the server automatically
record sequential volume history information to assist
in server recovery, use the VOLUMEHISTORY option
in the server options file to specify where history
information should be written. If you update the
options file, restart the server.
ANR4503W
The server current date current date is

earlier than the date in a server record
server date.
Explanation: The server has detected that the current

system date is an earlier date than the date in a server
record that is being processed. Possible causes for this
problem are the current system date is invalid, the
server was previously run with a future date, or there
is an error in the server record. If the server was run
with a future date, this message will continue to appear
until that date has passed, or all records with the future
date have been deleted from the server.
System action: Processing continues. The processing
for the current object may not occur as expected.
User response: On the machine on which the server is
running, verify that the system date is correct.
ANR4504E
Command: The specified point in time is

earlier than the point in time of the base
backup set.
Explanation: The point in time specified for the

differential backup set is earlier than the point in time
of its base backup set.
command.
462
User response: Reissue the command, specifying a

later point in time.
ANR4505E
Required table of contents could not be

created for backup set for node name as
set name (data type data type).
Explanation: A table of contents could not be created

for the named object set, but a table of contents was
required (TOC=YES was specified or implied).
System action: The backup set is deleted.
User response: Correct the problem that prevented the
table of contents from being created and generate the
backup set again.
ANR4506W

(data type data type) requires a table of
contents.
Explanation: The specified backup set requires a table

of contents, but TOC=YES was not specified.
System action: The server will attempt to create a
table of contents for the backup set. If the table of
contents creation fails, the backup set will be deleted.
ANR4510E
The server could not write sequential

volume history information to volume
history file name. To restore the database,
access to this file is required.
Explanation: While attempting to write sequential

volume history information to defined history files, the
server could not write to the specified file. The
database cannot be restored until this file can be
accessed.
System action: The server does not write volume
history information to the file specified
User response: Examine any error messages that may
have been displayed prior to this message and correct
any problems. Ensure that the server has permission to
write to the file indicated and that there is sufficient
space in the file system for the file. On MVS, ensure
that the data set has been allocated and that the server
has permission to write to the data set. After correcting
the problem, use the BACKUP VOLHISTORY
command to write sequential volume history
information to the file.
ANR4511E
Volume history file volume history file

name could not be opened. To restore the
database, access to this file is required.
Explanation: While attempting to read or write

sequential volume history information from defined
history files, the server was unable to open the
specified file name. The database cannot be restored
ANR4512E ANR4518E
until this file can be accessed.
ANR4515E
System action: The server does not read or write

volume history information from the specified file.
User response: Examine any error messages that may
have been displayed prior to this message and correct
any problems. Ensure that the server has permission to
write to the file indicated and that there is sufficient
space in the file system for the file. On MVS, ensure
that the data set has been allocated and that the server
has permission to write to the data set.
ANR4512E
A database transaction failure was

encountered in processing sequential
volume history information.
Explanation: While attempting to process sequential

volume history information, the server encountered a
database transaction error.
System action: The operation fails. Usage for a
sequential volume was not properly recorded for later
reference.
problems, if possible. If this does not resolve the
problem, contact your support representative.
ANR4513E
A database lock conflict was

encountered in processing sequential
volume history information.

volume history information, the server encountered a
database locking conflict.
System action: The operation fails. This usually means
that usage for a sequential volume was not properly
recorded for later reference
problems, if possible. If this does not resolve the
problem, contact your support representative.
ANR4514E
Sufficient database space is not

available for the server while processing

volume history information, the server found that
sufficient database space was not available for updates.
reference.
DEFINE DBVOLUME command, and extend the size of
the database by using the EXTEND DB command.
Sufficient recovery log space is not

available for the server while processing

volume history information, the server finds that
sufficient recovery log space is not available for
updates.
reference.
DEFINE LOGVOLUME command, and extend the size
of the database by using the EXTEND LOG command.
ANR4516E
Server could not read sequential volume

history information from any defined
files.
Explanation: While attempting to read sequential

volume history information from defined history files,
the server finds that it cannot open any of the files
defined in the server options file.
System action: The server does not read volume
history information. If the current server task requires
this information, the task ends.
proper authority to read from the defined volume
history files. If you are doing a database restore, issue
RESTORE DB DEVCLASS=VOL.
ANR4517E
No files have been defined for storing

sequential volume history information information cannot be read.
Explanation: The server is attempting to read from at

least one of the volume history files defined in the
server options file. Since no files were defined for this
information the read operation fails.
System action: Server operation ends.
User response: You can restore the database specifying
the volume names for each restore operation (in order)
up to the desired point-in-time. If a volume history file
is available, specify its name in the server options file
ANR4518E
Volume history file file name line line

number does not have the proper format
- read operation fails.
Explanation: The server is attempting to read from a

volume history file and encounters a record that does
not have the proper format.
463
ANR4519W ANR4525E
User response: Examine the file specified to determine
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
operation.
ANR4519W
Volume History File does not reflect

latest Storage Agent Updates
Explanation: The storage agent failed to have the

volume history file on the server updated with the
latest changes from the storage agent.
ANR4522E
Explanation: The LOG file is not associated with the

current log sequence.
System action: RESTORE DB terminates.
User response: Issue REMOVE DB first and retry the
RESTORE DB.
ANR4523I
System action: The storage agent continues

processing.
User response: To bypass the problem, a BACKUP
VOLHIST command can be issued from an admin
client connected to the server. The problem may be due
to a temporary loss of communication with the server.
ANR4520I
Storage Pool storage pool name is being

skipped during a space allocation. A
request for request amount megabytes
was made but only available amount
megabytes were available.
Explanation: A request for storage was made in the

indicated storage pool. The storage pool has a capacity
of the number of megabytes shown. The requested
amount can not be satisfied in the storage pool being
skipped. The next storage pool, if any, will be tried in
an attempt to satisfy the request.
System action: The storage server skips the indicated
storage pool and tries to allocate storage in a "next"
pool.
User response: More space can be created in the
storage pool by increasing the number of scratch
volumes allowed (use the UPDATE STGPOOL
poolname MAXSCRATCH=xx command), by creating
private volumes in the storage pool (use the DEFINE
VOLUME poolname volname command ), or by
creating a storage pool space trigger to monitor storage
in the storage pool. The storage pool space trigger can
also automatically create new FILE volumes when
space triggers are exceeded (use the DEFINE
SPACETRIGGER STG STGPOOL=poolname command).
ANR4521E
The number of volumes specified in the

BACK DB command is not sufficient
Backup failed.
Explanation: The backup volume provided in the

input parameter for BACKUP DB command is not
sufficient.
System action: BACKUP DB terminates.
User response: Provide more input volumes.
464
RESTORE DB failed with LOG file

error.
Storage Pool Space expansion triggered.

Storage Pool storage pool name with
capacity of capacity megabytes requires
percentage percent expansion for
expansion amount bytes of additional
space.
Explanation: A triggered space expansion has started

for the indicated storage pool. The storage pool has a
capacity of the number of megabytes shown. It is being
expanded by the indicated percentage as directed by
the storage pool space trigger for this storage pool, or
by the default storage space trigger if this storage pool
has no dedicated trigger of its own. The percentage is
represented by the additional amount of space
indicated.
ANR4524I
Volume volume name defined in Storage

Pool storage pool name as a result of
storage pool triggered space expansion.
Explanation: A triggered space expansion has caused

the indicated volume to be created in the storage
shown in the message. The volume definition is the
result of a storage pool space trigger definition which
allocates new space when the space trigger space
threshold is met.
ANR4525E
Failure to define volume volume name in

Storage Pool storage pool name. Return
codereturn code.
Explanation: A triggered space expansion has caused

an attempt to create the indicated in the storage pool
shown in the message. The volume creation failed with
the indicated return code. The volume was not added
to the storage pool. Additional messages with specific
information on the failure are displayed from the
volume creation process.
User response: It might be necessary to take action
based on the failure message from the volume creation
process. Such actions might include changing the
ANR4526E ANR4531I
storage space trigger definiton, ensuring that hardware
is function properly, or ensuring that the server is set
up with sufficient permissions to access and create files
on the file system to which Tivoli Storage Manager is
writing.
ANR4526E
Storage Pool Space trigger for storage

pool name is ended; the thread resource
not available.
Explanation: The server cannot start a thread to

handle storage pool expansion for the indicated storage
pool.
System action: Server processing continues but the
storage pool is not expanded.
application.

storage pool is not expanded. The storage pool space
trigger for the indicated storage pool remains disabled.
This message is re-issued periodically when expansion
is required but the storage pool space trigger remains
disabled.
User response: Allocate additional storage space to
the server. For storage pools of device type FILE,
additional directories may be added to the list of
directories that the associated device class uses for
storage. If this action is taken, the corresponding
storage agent directories should be added via the
UPDATE PATH command. The storage pool space
trigger may be re-enabled with the UPDATE
SPACETRIGGER STG STPOOL=xx command, where xx
is the storage pool for which expansion has failed ( no
space trigger parameters need be updated ).
ANR4529I
ANR4527W
Storage Pool Space trigger for storage

pool name is disabled after volume
definition failures expansion failures.
Insufficient space for pool expansion.
Explanation: The server failed to complete a storage

pool expansion for the indicated storage pool. The
number of failures in pool expansion is also displayed.
storage pool is not expanded. The storage pool space
trigger for the indicated storage pool is disabled.
User response: Allocate additional storage space to
the server. For storage pools of device type FILE,
additional directories may be added to the list of
directories that the associated device class uses for
storage. If this action is taken, the corresponding
storage agent directories should be added via the
UPDATE PATH command. The storage pool space
trigger may be re-enabled with the UPDATE
SPACETRIGGER STG STPOOL=xx command, where xx
is the storage pool for which expansion has failed ( no
space trigger parameters need be updated ).
ANR4528W
Storage Pool Space Expansion for storage

pool name is disabled due to previous
expansion failures. After addressing
space requirements, an UPDATE
SPACETRIGGER STG command must
be issued to allow automatic stgpool
expansion.
Explanation: The server failed to complete a storage

pool expansion for the indicated storage pool. The
storage pool space trigger is disabled due to previous
expansion failures. The storage pool space trigger may
be re-enabled with the UPDATE SPACETRIGGER STG
STPOOL=xx command, where xx is the storage pool for
which expansion has failed ( no space trigger
parameters need be updated ).
An automatic full or incremental

database backup will be started. The
active log space used is log space used is
available is log space available megabytes.
The ratio, active log used ratio, exceeds the
threshold log utilization threshold.

the log utilization threshold, a database backup is
started. If there has been at least one full database
backup, the backup is an incremental database backup.
Otherwise, a full database backup is started.
System action:
User response:
ANR4530I
An automatic full database backup will

be started. The total space used in log
file system is log space used megabytes,
and the total space available in the log
file system is log space available
megabytes. The ratio is log file system
used ratio and is greater than the
threshold log file system utilization
threshold.
Explanation: When the space used in the log file

system exceeds the threshold for log file system
utilization, a full database backup is started.
System action:
User response:
ANR4531I
An automatic full database backup will

be started. The last log number used is
last log used and the first log number
used is first log used. The log file size is
log file size megabytes. The maximum log
file size is maximum log file size
megabytes.
465
ANR4532W ANR4539E
Explanation: When the log space used since the last
database backup exceeds the maximum log file size, a
full database backup is started.
System action:
User response:
ANR4532W
The total DB used in DB space is log

available in the DB space is log space
available megabytes. The ratio is log file
system used ratio.
Explanation: The DB space used exceeds the threshold

for DB space utilization, please define more DB space
using EXTend DBSpace command.
ANR4535E
The active log directory active log

directory is not valid.
Explanation: The active log directory that is specified

in the DSMSERV FORMAT command does not exist.
System action: The database format operation failed.
User response: Verify that the file systems you have
specified for formatting the server database and
recovery log are valid. Reissue the DSMSERV FORMAT
command with a valid active log directory. For more
information, see the DSMSERV FORMAT command in
the Administrator's Reference.
System action:
File Processor Value Unit table xml file

could not be found or opened for read
access.
User response:
Explanation: The file could not be found or opened.
ANR4533E
Database database name is invalid and

cannot be created.
Explanation: Follow all of these rules when choosing

a database name or alias:
v Character strings that represent names of a database
can contain any of the following characters: a-z, A-Z,
0-9, @, #, and $.
v A database name or alias must be unique in the
database instance.
ANR4536E
System action: Contents of the file are not parsed and

loaded to the database.
User response: Verify that the file exists in either the
server instance directory or the server installation
directory. If the file does exist verify permissions for
read access. If the file does not exist obtain a copy from
the IBM Processor Value Unit website.
ANR4539E
v A database name or alias is one to eight characters in

length.
v The first character of the name must be an alphabetic
character, or a @, a #, or a $ character.
v The first three characters of the name cannot be any
of the following strings: SYS, DBM, or IBM.
System action: DSMSERV FORMAT processing stops.
User response: Choose a different database name
which meets the criteria indicated above and issue the
DSMSERV FORMAT command again.
ANR4534E
The active log size of active log size MB

exceeds the available space active log
space MB.
Explanation: There is not enough space for the active

log size specified in the DSMSERV FORMAT command.
User response: Ensure that the file systems you are
using for database and recovery log activities have
enough space. Reissue the DSMSERV FORMAT
command and specify a smaller value for the active log
size. For more information, see the DSMSERV FORMAT
command in the Administrator's Reference.
466
There is a mismatch in directory count

between Device Class device class name
and Path Definition for Server server
name. The device class has directory count
directories while the path definition has
path directory count directories.
Explanation: The server was assigning a shared FILE

library volume to a server or storage agent. Share FILE
libraries require a matching number of directories in
the PATH definition for the server or storage agent's
access to FILE drives and the server's device class
definition. For example, if the server has the following
device class definition: DEFINE DEVCLASS SFILE
DEVTYPE=FILE MOUNTL=10 SHARED=YES
DIR=D:\DIR1,E:\DIR2,F:\DIR3 a FILE library name
SFILE will be created along with 10 drives named
SFILE1 to SFILE10 in shared library SFILE. Each of
these drives might have scratch volumes created in
directories D:\DIR1, E:\DIR2 or F:\DIR3. (For UNIX
Platforms, substitute UNIX style names in the
example).
For library clients and storage agents, the appropriate
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
DIR=V:\DIR1,W:\DIR2,X:\DIR3 LIBRARY=SFILE
which means that server (or storage agent) STA1
accesses directory D:\DIR1 using V:\DIR1 from the
STA1 system, E:\DIR2 on the server is accessed using
W:\DIR2 on STA1, and that F:\DIR3 is accessed using
ANR4540E ANR4544E
X:\DIR3 on STA1. If the number of directories between
the PATH and DEVCLASS do not match, there could
be problem in accessing the resulting file in the future.
System action: Processing continues. Another
directory path is chosen. This might result in a
subsequent access failure by the storage agent.
User response: Use the QUERY DEVCLASS classname
F=D and the QUERY PATH pathname F=D commands
to compare the directory lists for the device class and
the path and ensure that they are synchronized.
ANR4540E

device class id found in DevClass.Dirs
table.

non-existent device class or a device class with an
invalid access strategy for a record in the
Devclasses.Dirs table.
User response: If the FIX=YES parameter was
specified, the data base record with the incorrect entry
will be deleted. Otherwise, reissue the audit command
with FIX=YES, so that the incorrect record can be
deleted. After records with incorrect entries have been
removed, review directories associated with Device
classes and Paths with the following commands:
QUERY DEVCLASS F=D QUERY PATH F=D
ANR4541E
Audit command: Invalid directory for

device class device class id in
DevClass.Dirs table.

directory entry whose length is longer than allowed for
the indicated device class id in the DevClass.Dirs table,
which relates directories to device classes and paths.
with FIX=YES so that the incorrect record can be
removed, review directories associated with device
classes and paths with the following commands:
ANR4542E
Audit command: Invalid server for device

class device class id in DevClass.Dirs
table. The server name in the table is
server name.

directory entry with a server which is either not
defined or has an invalid length in the DevClass.Dirs
table. This table relates directories to device classes and
paths. The class ID of the table entry is shown, along
with the server name. However, if the server name has
an invalid length, only blanks are shown.

ANR4543E
Audit command: Mismatched server for

device class device class id in
DevClass.Dirs table. Server ID in table
is server id. Server ID in data base is
found server id.

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
ID of the table entry is shown, along with the server ID
in the table and the ID that was found when searching
using the source name.
ANR4544E
Audit command: Invalid library for device

class device class id in the DevClass.Dirs
table.

directory entry with a DEST name where the associated
library can not be found. This record is in the
DevClass.Dirs table. This table relates directories to
device classes and paths. The class ID of the table entry
is shown.
specified, the database record with the incorrect entry
467
ANR4545E ANR4556W
ANR4545E
Audit command: Invalid drive for device

class device class id in the DevClass.Dirs
table.

directory entry with a DEST name where the associated
drive (DESTNAME ) can not be found. This record is in
the DevClass.Dirs table. This table relates directories to
device classes and paths. The class ID of the table entry
is shown.
specified, the database record with the incorrect entry
ANR4549I
Database dump command: A database

dump is already in progress.
Explanation: This message is issued in response to a

database dump command and indicates that a database
dump cannot be started because a dump is already in
progress.
requested database dump is not started.
User response: Only one database dump can be
started at one time. Use the QUERY PROCESS
command to monitor the dump that is in progress.
When completed, issue the database dump command
to start another database dump if required.
ANR4550I
Full database backup (process process ID)

completed.
Explanation: A full database backup process has

completed. The output volumes used in this backup
may be used during a database restore operation.
ANR4552I
Explanation: A background process, triggered by the

LOGFULLPCT parameter on a DEFINE
DBBACKUPTRIGGER command, was started to back
up the full contents of the database. The full database
backup process is assigned the process ID shown.
QUERY PROCESS command, or cancel the process by
using the CANCEL PROCESS command.
ANR4553I
Incremental database backup (process

process ID) completed.
Explanation: An incremental database backup process

has completed. The output volumes used in this
backup may be used in conjunction with any preceding
volumes in the backup series during a database restore
operation.

QUERY PROCESS command, or cancel the process by
using the CANCEL PROCESS command.
ANR4554I
Backed up number of pages backed up of

number of pages to back up in current
operation database pages.
Explanation: Periodically, during a database backup,

the server displays the number of pages backed up.
ANR4555I
Database backup process process ID

canceled.
Explanation: The database backup process was

canceled by an administrator with the CANCEL
PROCESS command.
System action: The database backup process is ended.
ANR4556W

468
Incremental database backup triggered;

Explanation: A background process, triggered by the

LOGFULLPCT parameter on a DEFINE
DBBACKUPTRIGGER command, was started to
incrementally back up the contents of the database. The
incremental database backup process was assigned the
process ID shown.

ANR4551I
Full database backup triggered; started

Attention: the database backup

operation did not free sufficient
recovery log space to lower utilization
below the database backup trigger. The
recovery log size may need to be
increased or the database backup trigger
parameters may need to be adjusted.
ANR4557I ANR4565E
Explanation: A database backup process has
completed. The server is running in roll-forward mode
and the recovery log utilization remains above that
specified in the database backup trigger.
System action: A database backup operation will be
triggered. Unless this situation is corrected, database
backups will be triggered rapidly, one after the other.
User response: If a database backup operation does
not free up enough recovery log space to reset
utilization below the database backup trigger, the
recovery log needs to be extended or the database
backup trigger updated to a higher log full percentage
or a higher log free percentage or a higher minimum
interval.
ANR4557I
Differential database backup (process

Explanation: A snapshot database backup process has

completed.

Snapshot database backup (process
Explanation: A differential database backup process

has completed. The output volumes used in this
backup may be used in conjunction with preceding
volumes in the full backup during a database restore
operation.
ANR4559I
Triggered database backup retry delay

ended; checking database backup trigger
criteria.
Explanation: Because a triggered database backup had

the system can now retry the database backup.
System action: Database backup begins.
ANR4562I
Database backup criteria is no longer

met; triggered database backup
canceled.
Explanation: Because a triggered database backup had

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.
ANR4558I
ANR4561I

ANR4563I
Unable to trigger database backup - a

database define, delete, extend, reduce,
or backup operation is already in
progress.
Explanation: A database backup was triggered, but a

command that is modifying or backing up the database
is already active.
System action: The backup stops and the server waits
for the retry period to expire and then tries the
database backup again.
Backup DB is in progress.
Explanation: The database backup in process.

ANR4564I

ANR4560I
Triggered database backup will be

retried in number of seconds seconds.

during a triggered database backup, the current backup
stops but will be retried after the time period shown.
period and then retries a database backup.
stopped the database backup. If the problem persists,
Unable to trigger database backup sufficient memory is not available.
Explanation: A database backup was triggered, but

there is not enough server memory available.
ANR4565E
Unable to trigger database backup thread resource not available.
Explanation: A database backup was triggered, but

the server cannot start a thread for the backup process.
469
ANR4570E ANR4576E
ANR4573E
User response: If the error persists, it may indicate a

shortage of server memory. Allocate additional server
memory.
Explanation: During database backup, write errors

ANR4570E
Database backup/restore terminated device class device class name not defined.
Explanation: During database backup or restore

processing, an error occurred because the specified
device class is not defined.
System action: If the database backup was started
with the BACKUP DB command, the database backup
is ended and server operation continues. If the database
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 terminated.
User response: For database backup, make sure the
specified device class is defined. For database restore
processing, make sure the device class has a definition
in a device configuration file that is pointed to in the
server options file.
ANR4571E
Database backup/restore terminated insufficient number of mount points

Explanation: During database backup or restore, the

server cannot allocate sufficient mount points for the
volumes required.
restore is ended.
User response: For database backup, make more
mount points available if necessary. For database
restore processing, make sure the device class has
sufficient mount points defined in the device
configuration information file that is pointed to in the
server options file.
ANR4572E
Database restore terminated - excessive

read errors encountered.
Explanation: During database restore, read errors


then tries the database backup again.
cause of the write errors. If the problem cannot be
corrected, contact your service representative.
ANR4574E
Database backup/restore terminated data transfer interrupted.
Explanation: During a database backup or restore

operation, a data transfer operation has been
interrupted and cannot be continued.
restore is ended.
cause of the interruption. If the problem cannot be
corrected, contact your service representative.
ANR4575E
Database backup/restore terminated sufficient recovery log space is not

available.

operation, the server runs out of recovery log space.
server recovery log space available, if necessary. For
database restore, contact your service representative.
ANR4576E
System action: Database restore processing stops.

User response: Use a different device for the restore
operation. If the problem persists, contact your service
representative.
Database backup terminated - excessive

write errors encountered.
Database backup/restore terminated sufficient database space is not

available.

operation, the server runs out of database space.
470
ANR4577E ANR4582E
then tries the database backup again. The database
restore process attempts to set the database capacity to
the required capacity to hold the database being
restored. If this fails, the restore operation is ended.
server database space available, if necessary. For
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

already in use.
Explanation: During a database backup operation, a

export, a database dump, or a database backup
operation (as recorded in the volume history) or is in
then tries the database backup again.
reissue the restore command. If you are restoring a

database backup with COMMIT=YES, restore the
complete backup series from the beginning.
ANR4579E
Database backup/restore terminated thread resource not available.

operation, the server cannot start a thread for the
backup process.
User response: Retry the command or wait for the
server to retry the backup if it was started by the
backup trigger. If the error persists, it may indicate a
ANR4580E
Database backup/restore terminated insufficient memory available.

operation, there was not enough server memory
available.

previously used for an export, a database dump, or a
volume history information. The QUERY VOLUME
command may be used to display the names of
volumes that are defined to server storage pools. The
QUERY VOLHISTORY command may be used to
display the names of volumes that have been used for
export, database dump, or database backup operations.

ANR4578E
ANR4581W
Database backup/restore terminated required volume was not mounted.

operation, a required volume cannot be mounted,
because the mount request was canceled.
User response: Issue the command again or wait for
the server to retry the backup and make sure the
necessary volumes are accessible. If you are restoring a
database to a given date or doing a roll-forward
restore, restart the entire restore operation. If you are
restoring a single database backup with COMMIT=NO,

Database backup/restore terminated internal server error detected.

operation, the server encounters an internal error.
ANR4582E
Database restore terminated - volume

cannot be used.
Explanation: During a database restore operation, a

volume has been mounted but cannot be used.
471
ANR4583E ANR4588E
System action: The restore operation is terminated.
User response: If a volume list was specified on the
command, make sure the correct volume is being
specified and mounted. If no volume list was specified,
ANR4583E
Database backup terminated - output

media full and scratch media could not
be mounted.
Explanation: During a database backup operation, an

out-of-space condition occurred writing to the
sequential media, and a scratch volume cannot be
mounted.
System action: The database backup is ended and
additional volume names on the command, or specify
SCRATCH=YES.
ANR4584E
Database restore terminated incomplete input volume list.
Explanation: The list of volumes needed for the

restore operation was incomplete. At least one volume
needed for the restore operation is missing from the
end of the list.
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
correct sequential order. For a restore with
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
DSMSERV RESTORE DB command with the TODATE
parameter specified, the server created a list of volumes
needed for the restore operation. Examine the volume
history files to try to determine the error or use a
different volume history file if available. You can also
restore the database by specifying the volume names
for each restore operation up to the desired point in
time.
ANR4585W
Volume History File does not exist Backup/Restore DB operation requires

volume history file.
Explanation: Volume history file is needed for the

backup/restore DB operation.
ANR4586E
Not able to get a DB2 connection.

Backup DB operation will be
terminated.
Explanation: DB2 connection is needed for the backup

DB operation.
System action: Backup DB operation is terminated.
User response: Verify database manager resources.
Submit command again.
ANR4587E
Database backup or restore

configuration is incorrect; client node
node name was attempted to be used for
this operation.
Explanation: A server database backup or restore

operation was attempted and failed. The indicated
client node was used for the operation which is
incorrect. The server database backup and restore
operations are a restricted protocol and require the
explicit use of client node name $$_TSMDBMGR_$$.
System action: Database backup or restore operation
failed and is terminated.
User response: Verify the configuration of the dsm.sys
file used by the TSM API for the system where the
server is installed. The dsm.sys must be configured
with the server TCP/IP address as loopback (127.0.0.1),
the appropriate TCP/IP port that the server is
configured to listen on, and the NODENAME stanza in
the file must specify $$_TSMDBMGR_$$. Refer to the
installation and configuration topics in the information
center for this release of the product. Specifically,
review the setup and configuration information for
performing a database backup for the server.
ANR4588E
A database backup configuration might

be incorrect.
Explanation: A server database backup operation

failed. The server database backup and restore
explicit use of the client node name
$$_TSMDBMGR_$$.
System action: The database backup operation fails
and is ended.
User response: Verify that the configuration of the
dsm.sys file used by the Tivoli Storage Manager API
for the system where the server is installed. The server
stanza in the dsm.sys for the database backup must be
configured as follows:
v The server TCP/IP address is loopback (127.0.0.1).
System action:
v The server is configured to listen on the appropriate

TCP/IP port.
User response: Please specify volume history file in

the dsmserv.opt.
v The NODENAME option must specify

$$_TSMDBMGR_$$.
472
ANR4590I ANR4595E
Refer to the installation and configuration topics in the
information center for this release. Specifically, review
the setup and configuration information for performing
a database backup for the server.
ANR4590I
Backup type backup series backup series

number operation backup operation in series
stream backup stream within operation
(always 1) sequence backup volume
sequence number in operation taken on date
at time.
ANR4593E
Restore database unable to find eligible

candidate to use for processing.
Explanation: The DSMSERV RESTORE DB command

evaluates the volume history file using the criteria
specified for the command to determine the best
candidate database backup to use. No eligible
candidate backup series was found.
Explanation: During a DSMSERV DISPLAY

DBBACKUPVOL command, the server displays the
necessary information about a backup volume.
User response: Evaluate the volume history file and

available volumes to use for restore of the database.
Manually add entries to the volume history file for a
backup series and corresponding volumes to consider
for restore database processing.
System action: Processing continues for all volumes in

the given volume list.
ANR4594E
User response: You can use this information to create

a list of volumes for a database restore when a volume
history backup file is not available.
ANR4591I
Selected backup series seriesId from date

and time as best candidate available for
restore database processing.

candidate database backup to use.
User response: Evaluate the backup series, date, and
time reported to determine if this meets the desired
restore objectives. If these do not meet the objectives,
re-issue the DSMSERV RESTORE DB with additional or
changed information in order to achieve the desired
recovery objectives.
ANR4592I
Restore database backup series seriesId

includes eligible operation opId with
volume volume name having sequence
sequence and using device class device
class.

candidate database backup to use. The opId and volume
name for the indicated device class are candidate
volumes that will be evaluated and used for the restore
database process.
User response: Evaluate the backup series, date, and
time reported to determine if this meets the desired
restore objectives. If these do not meet the objectives,
re-issue the DSMSERV RESTORE DB with additional or
changed information in order to achieve the desired
recovery objectives.
Restore database expects volume

volumeName for backup series seriesID
and operation operationID but it could
not be found in the available volume
history files.
Explanation: Once the DSMSERV RESTORE DB

command selects a candidate database backup series, it
will validate the information from the backup data
stream and compare it to the information available
from the volume history file. In this case, the database
backup requires the specified volume for restore
processing of this backup series but this volume was
not found in the available volume history file
information.
available volumes to use for restore of the database. If
the specified volume is available, than add an entry to
the volume history file for this volume and retry the
operation. If this volume is not available, than remove
all entries from the volume history that are assigned to
this backup series ID. Once those entries are removed,
retry the database restore operation and it will attempt
to select the next best candidate for processing.
ANR4595E
Restore database expects a stream

sequence stream for backup series
seriesID and operation operationID but it
could not be found in the available
volume history files.

backup has information for the indicated stream
sequence but it has been unable to find any
information about volumes used for that stream within
this backup series and operation.
473
ANR4596E ANR4601E
available volumes to use for restore of the database. If
additional volumes are available for this series and
operation, than add entries to the volume history file
for these volume and retry the operation. If no other
volumes are available, than remove all entries from the
volume history that are assigned to this backup series
ID. Once those entries are removed, retry the database
restore operation and it will attempt to select the next
best candidate for processing.
ANR4596E
Restore database is unable to validate

the selected database backup for series
seriesID and operation operationID against
the actual data from the database
backup stream.

backup is missing information which is needed in order
to perform a restore of the server database.
User response: This is likely caused by not having all
the necessary volumes available and specified in the
volume history file. Or this is caused by having the
wrong volume designated with sequence 10001. If a
volume in the volume history file for this backup series
and operation is assigned 10001, try assigning a
different volume as sequence 10001. The volume
assigned sequence 10001 is expected to have the
self-describing validation information and signatures
that are used by the restore processing for validation of
a given operation for a backup series. If this
information is not found or correct, this would result in
a restore failure.
ANR4597E
Operation operationId for backup series

seriesID does not reference volume
volumeName, the volume history
information is not correct.

from the volume history file. In this case, the volume
history information reports a volume assigned to a
given series and operation but that backup does not
reference that volume.
this value, it would be considered as a database backup

volume which would result in this error. Alternatively,
if this volume simply does not belong to this database
backup series or operation, that would result in this
failure as well. Removing this entry from the volume
history file to eliminate it from consideration for this
backup series and operation or correcting the operation
id and series id to an approprite value would also
resolve this. After considering the cases above and
taking action for one or the other of them, retry the
restore database operation.
ANR4598I
Validating database backup information

for selected backup series seriesId and
operation operationId using volume
volumeName.
Explanation: The database backup information for the

selected backup series selected from the volume history
will be validated against the information from the
database backup itself. The volume history information
will be cross-checked to insure that the backup series,
necessary volumes, and other attributes of the database
backup are correct and complete for this operation.
Note that if the database restore operation includes
incremental database backups, the validation will be
done using the volumes assigned to sequence number
10001 for operationId 0 and the operationId
representing the best candidate for restore of the
incremental database backup data.
User response: If the information is cross-checked and
validated successfully, the database restore will be
attempted using this database backup series and
corresponding volumes. If the information fails to
validate, additional messages will be issued indicating
what is missing or why the selected database backup
series and volumes can not be used. In the case that the
validation failed, review the other messages and take
the corrective action specified by those messages and
than retry the database restore operation.
ANR4600I
Processing volume history file file name.
Explanation: During a DSMSERV RESTORE DB

command with the TODATE parameter specified, the
server is processing the listed file in order to build a
list of volumes needed for the restore operation.

User response: This may be caused by one of two
possible cases. The first is that the transaction log
information recorded for this backup to make this
database referentially consistent required more than one
volume to store this information. This should be
referenced with a write sequence number greater than
10001. If this was assigned a sequence value less than
474
ANR4601E
Incomplete volume list found for

TODATE date time - retrying.
Explanation: During a DSMSERV RESTORE DB

command with the TODATE parameter specified, the
server created a list of volumes needed for the restore
operation, but the list was incomplete.
ANR4602E ANR4623I
System action: The server tries to build the list again
using a different volume history file specified in the
server options file. If no other volume history files are
available, the server stops processing.
User response: If the problem persists, examine the
volume history files to try and determine the error. You
can also restore the database by specifying the volume
names for each restore operation up to the desired
point in time.
ANR4602E
No volumes found for TODATE date

time.
Explanation: No volumes were found in the volume

history files that meet the date and time parameters
specified.
command.
date and time.
ANR4610E
Database volume DB volume name not

found in current configuration.
Explanation: The command specified the name of a

nonexistent database volume.
v No full backup was taken after setting the recovery

log mode to ROLLFORWARD with a SET
LOGMODE command.
v Only snapshot database backups were created.
command.
point in time (TODATE/TOTIME) for restore.
ANR4619I
Snapshot database backup series

snapshot database backup series using
device class device class.
Explanation: The device class used for the snapshot

database backup is shown.
ANR4620I
Database backup series Backup series

operation backup operation device class
device class.
Explanation: The device class used for the backup is

shown.

command.

database volume name.
ANR4621I
ANR4611E
Unable to restore database and roll

forward updates - log mode was not
previously set to ROLLFORWARD.
Explanation: The command specified that the database

be restored and all updates rolled forward to the most
current state. This process cannot be accomplished
because the server recovery log mode was not set to
ROLLFORWARD; therefore, no update information
exists.
command.
point in time (TODATE/TOTIME) for restore.
ANR4612E
Unable to restore database and roll

forward updates.
Explanation: The command specified that the database

be restored and all updates rolled forward to the most
current state. This process cannot be accomplished
because the internal list of volumes for the most recent
full/incremental backup series is not available. Possible
reasons include:
Database backup device class device class.
Explanation: The device class for the backup is

shown.
ANR4622I
Volume volume sequence number in backup

operation: volume name.
Explanation: The volume sequence and name for a

full or an incremental database backup are shown.
ANR4623I
Stream stream number in backup operation

volume volume sequence number in backup
stream: Volume name.
Explanation: The stream number, volume sequence

and name for a full or an incremental database backup
are shown.
475
ANR4624I ANR4634I
ANR4624I
Preview processing for a database

restore operation has completed.
Explanation: The database restore command was

issued with PREVIEW=YES specified. The server will
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
command that was specified. If the database restore
processing is unable to find a viable database backup to
use for restore or other errors occur during this
evaluation, these will also be reported.
determine the outcome of the database restore preview
operation.
ANR4625W
Database backup failure while

attempting to use number of streams
streams, backup will be retried using
one stream.
ANR4630I
Starting point-in-time database restore

(commit).
Explanation: A point-in-time database restore with a

specified list of volumes has started. When this restore
is complete, the database will be committed to the
point in time of this backup.
User response: If you inadvertently specified
COMMIT=YES, restart the restore process from the
beginning, starting with restoring the full backup
(backup operation 0).
ANR4631I
Point-in-time database restore (commit)

complete, restore date date time.

specified list of volumes is complete. The date shown is
the date to which the database has been restored.
Explanation: The database backup process failed

while attempting the operation with the specified
number of streams. The operation will be retried with a
single stream.
ANR4632I
System action: The database backup will be

automatically retried using a single stream.

specified list of volumes has started. When this restore
is complete, the database will not yet be usable.

determine the reason for the failure of the database
backup while using multiple output streams. Also
review the process completion and other message to
determine if the retry using a single stream was
successful.
ANR4626I
Database backup will use number of

streams streams for processing with the
number originally requested number
requested.

(no commit).

User response: To complete a database restore where
a volume list is specified, specify COMMIT=YES on the
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
COMMIT=YES.
ANR4633I
Point-in-time database restore (no

commit) complete.
Explanation: The database backup will be performed

using the specified number of streams. The original
number of streams requested, either through the
command or the NUMSTREAM setting for SET
DBRECOVERY, is also displayed.

specified list of volumes is complete. The database is
not yet usable.
System action: The database backup will be

performed with the indicated number of streams.
User response: To complete a database restore where

a volume list is specified, specify COMMIT=YES on the
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
COMMIT=YES.
User response: Note that if the number of streams

used for the database backup differs from the number
requested, this indicates either a configuration error or
that the device being used does not have as many
drives available as was previously considered and
planned for. Review the device class and
NUMSTREAM settings used for the database backup
command to determine if changes are needed or if
actions are needed to bring drives back online.
476
ANR4634I

to date date time.
Explanation: A point-in-time database restore with the

TODATE parameter specified has begun. When this
restore is complete, the database will be committed to
ANR4635I ANR4644I
the point in time of this backup.
ANR4640I

ANR4635I
Point-in-time database restore complete,

restore date date time.

TODATE parameter specified has completed. The
database is committed to the point in time of this
backup, which may be different than the TODATE
specified. If this is the case, an additional message will
be displayed.
ANR4636I
Restored number of database pages pages

from backup series backup series number
operation backup operation in series.
Explanation: At the end of each restored backup, the

server displays the number of database pages restored.
ANR4641I
Sequential media log redo pass in

progress.
Explanation: During a DSMSERV RESTORE DB, the

process of committing incomplete database updates has
begun.
Starting roll-forward database restore.
Explanation: A roll-forward database restore has

begun. When this restore is complete, the database will
be returned to its most recent state.

ANR4642I
Sequential media log undo pass in

progress.

process of rolling back incomplete transactions has
begun.


ANR4637I
Roll-forward database restore complete.
Explanation: A roll-forward database restore has

ended. All database backups in the most current
backup series have been restored, and all updates to
the database since the most recent backup have been
rolled forward. The database has been returned to its
most recent state.
ANR4638I

ANR4643I
Processed number of log records log

records.
Explanation: Periodically, during the commit of a

point-in-time restore or while rolling forward updates
during a roll forward restore, the server displays the
number of log records processed.
Restore of backup series backup series

number operation backup operation in series
in progress.

server displays the backup series and operation
currently being restored.

ANR4644I
A full backup will be required for the

next database backup operation.
Explanation: During a point-in-time restore of a

database, this message is displayed to notify the
administrator that the next database backup taken
during normal operation must be a full backup. This
process is normal for point-in-time database restores.
ANR4639I
Restored number of pages restored of

number of pages to restore from current
backup operation database pages.
User response: At the next server restart, do a full

database backup. A full database backup is started
automatically if a DBBACKUPTRIGGER is defined.
Explanation: Periodically, during a DSMSERV

RESTORE DB, the server displays the number of pages
restored from the current backup being restored.
477
ANR4645I ANR4652E
ANR4645I
The restore date reflects the most recent

backup available up to the specified
TODATE.
Explanation: During a DSMSERV RESTORE DB with

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
most recent backup series up to and including the
specified date.
ANR4649I
Reducing database assigned capacity to

number of megabytes megabytes.

database, the assigned capacity of the online database
is larger than that of the database being restored.
System action: The assigned capacity of the online
database is reduced to the size required for restore.

User response: Make sure the date of the restored
database is satisfactory. If it is not, restore the database
again by specifying a different TODATE or by restoring
individual database backups.
ANR4646I
Database capacity required for restore is


database, the size of the database being restored is
displayed. The available capacity of the online database
volumes must be at least this size.
ANR4647I
Database available capacity is number of

megabytes megabytes.

database, the available capacity of the online database
volumes is displayed. This capacity must be as large as
the size of the database being restored.
System action: If the available capacity of the online
database volumes is not at least this size, the restore
cannot continue.
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
again.
ANR4648I
Extending database assigned capacity to

ANR4650E
Restore of backup series current series

operation current operation is not in
sequence; last restored backup was
series previous series operation previous
operation.
Explanation: During a DSMSERV RESTORE DB, a

backup volume was mounted that is not in the correct
sequence.
User response: Ensure volume names are specified in
the correct sequential order. For a restore with
COMMIT=NO, reissue the last restore command. For a
restore with COMMIT=YES, restart the restore from the
beginning of the full backup.
ANR4651E
Restore of backup series current series

operation current operation is not in
sequence; backup is part of another log
epoch.
Explanation: During a DSMSERV RESTORE DB, a

backup volume was mounted that is not in the correct
sequence. The current backup operation cannot be
restored in this series because it belongs to the same
backup series from another point in time.
User response: Restart the database restore from the
beginning of the full backup. Omit all backups from the
offending backup and later from the restore.
ANR4652E
No system message queues available for

communications.

database, the assigned capacity of the online database
is smaller than that of the database being restored.
However, the available capacity of the online database
volumes is sufficient for restore.
Explanation: While Tivoli Storage Manager was trying

to establish a communications session, an attempt to
acquire a system message queue failed. This usually
means that the system-imposed limit on message
queues has been reached.
System action: The assigned capacity of the online

database is extended to the size required for restore.
System action: The communications session is not

initialized due to lack of system resources.
User response: Increase the maximum number of

message queues on the system and try the operation
again. This is normally accomplished by increasing the
value in the kernel's msgmni file.
478
ANR4653E ANR4660I
ANR4653E
Incremental backup DB failed. Can not

perform incremental DB backup without
a FULL DB backup performed first.
Explanation: A FULL DB backup has to be performed

at least once before any Incremental DB backup can be
performed.
System action: The incremental DB backup is
terminated.
User response: Reissue the backup db command with
type=FULL.
ANR4654I
The restore db to most current time can

not be done since contents of the active
or archive log directories have been
changed. The DB will be restored to the
last full or full plus incremental state.
Explanation: The restore DB can only restore to the

last FULL backup.
System action:
User response: Do not modify contents of active or
archive log directories before attempting a dsmserv roll
forward restore command.
ANR4655W
The restore DB is completed and active

log directory has been changed by DB2
from orginal active log directory to new
active log directory
Explanation: The active log directory has been

changed by DB2.
System action:
ANR4657E
SNMP: Failed to connect to server at

address address, port port.
Explanation: The SNMP client was attempting to run

a session with the server at the indicated address and
port number in response to an SNMP Get Request,
which causes a Server Script to be run. The subagent
failed to connect to the server.
System action: The SNMP subagent ends this attempt
to run the script and continues operation.
User response: Ensure that the indicated server is up
and able to initiate admin clients using the TCP/IP
protocol.
ANR4658I
No key-ring file password was found.
Explanation: Either a QUERY command was issued to

display the key-ring file password or a SET command
was issued to inform the server of a change to the
key-ring file password. A password was not recorded
by the server.
System action: None
User response: To create a key-ring file or to generate
a password, the server must run with secure sockets
layer (SSL) transmission control protocol (TCP) port
options. If the server did not run with SSL TCP port
options, start the server while the options file contains
the SSLTCPPORT or SSLTCPADMINPORT option. Then
issue the QUERY SSLKEYRINGPW command to
display the generated password. If you use an external
utility to change the key-ring file password after the
server creates the key-ring file and its password, issue
the SET SSLKEYRINGPW command to inform the
server of the change.
User response: the user can do the following: :

v Start DB2: db2start
ANR4659E
v Connect to TSMDB1: db2 connect to TSMDB1
SNMP: Communications failure: bad

verb received (verb type).
v Update the DB config: db2 update db cfg using

NEWLOGPATH (log path from server options, e.g.
/ALOG/tsminst1)
Explanation: The SNMP client encountered an invalid

communications verb during a session with the server
and is not able to continue processing the session.
v Terminate connection to TSMDB1: db2 terminate
System action: The SNMP session ends and subagent

v Recycle DB2: db2stop/db2start

v Verify new log path takes effect: db2 connect to
TSMDB1; db2 get db cfg | grep "Path to log files"
ANR4656E
Invalid key-ring file password Key Ring

password
Explanation: The specified key-ring file password

exceeds the maximum password length of 64
characters.
System action: None
User response: Specify a key-ring file password using
1-64 characters. Ensure that the password is the same
value that was specified with the key-ring file
password utility.

ANR4660I
Connected to SNMP subagent at SNMP

subagent address on port port number.
Explanation: The server has successfully connected to

the SNMP subagent at the indicated address and port.
System action: The server will now register with the
subagent.
479
ANR4661E ANR4667W
ANR4661E
SNMP communication with the

subagent failed because a thread
resource was not available.
Explanation: The server could not continue with

SNMP communication to the SNMP subagent because
sufficient memory is not available for starting
additional processes on the server.
System action: The server discontinues SNMP
application.
ANR4662W
Failure sending message to SNMP

subagent.
Explanation: The server experienced an error return

code from TCP/IP while sending to the SNMP
subagent. This message is also issued when the SNMP
subagent has an error sending a verb to the server
when acting as an SNMP client. This may be a normal
event if either side of 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 describes the error.
System action: The session is ended. Server operation
continues. If a message is being forwarded to an SNMP
managing node, the message is not sent. If a heartbeat
message was being sent to the subagent, this heartbeat
message is lost and the server attempts to re-start its
session with the SNMP subagent.
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
stack is functioning by using the tools that come with
the particular TCP/IP suite on the platform in use.
ANR4663W
Failure receiving message from SNMP

subagent.
stack is functioning by using the tools that come with

the particular TCP/IP suite on the platform in use.
ANR4664W
Failure in registering with SNMP

subagent.
Explanation: The server experienced a problem while

attempting to register with the SNMP subagent. This
may be due to problems with communication or the
SNMP subagent being unavailable.
System action: Heartbeat messaging will be disabled
until the server is re-started.
User response: Ensure that the subagent is running
and that the TCP/IP protocol stack is functioning by
using the tools that come with the particular TCP/IP
suite on the platform in use.
ANR4665W
Failure retrying registration with 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
unavailable.
System action: Registration is re-tried for a number of
attempts before giving up.
ANR4666W
Failure sending heartbeat message to

SNMP subagent.

attempting to send a heartbeat message to the SNMP
subagent. This may be due to problems with
unavailable.

code from TCP/IP while receiving data from the SNMP
subagent. This may be a normal event if either side of
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
describes the error.
System action: The server will attempt to contact the

SNMP subagent again and re-synchronize.

continues. If a heartbeat message was being sent to the
subagent, this heartbeat message is lost and the server
attempts to re-start its session with the SNMP
subagent. If the server was attempting to register to the
SNMP subagent, heartbeat messaging will be disabled
until the server is re-started.
ANR4667W

intentionally stopping either the subagent, no response
is required. Otherwise, ensure that the TCP/IP protocol
480

Failure retrying heartbeat message to
SNMP subagent.

subagent. This may be due to problems with
unavailable.
System action: The server attempted to contact the
SNMP subagent again and re-synchronize, but this too
ANR4668I ANR4676E
failed. Heartbeat functions are disabled until the server
is re-started.
suite on the platform in use. Re-start the server if the
heartbeat function is required.
ANR4668I
Connection successfully re-established

with SNMP subagent.

subagent.
System action: The server was able to successfully
resynchronize with the SNMP subagent.
ANR4669W
Heartbeat message was not accepted by

SNMP subagent.

subagent. The SNMP subagent was unable to accept the
heartbeat message. If the subagent was stopped and
re-started, this is a normal message.
System action: The server will attempt to contact the
SNMP subagent again and re-synchronize.
ANR4670W
Failure in opening session with SNMP

subagent.

attempting to open a session with the SNMP subagent.
subagent and re-start it. Then stop the server and

re-start it if heartbeat and message forwarding
functions are required.
ANR4672W
Explanation: The server could not continue with

SNMP communication to the SNMP subagent for
message forwarding because sufficient memory is not
available for starting additional processes on the server.
System action: The server discontinues SNMP
message processing and server operation continues.
application.
ANR4673E
ANR4671W
SNMP subagent did not accept

registration of this server.

attempting to open a session with the SNMP subagent.
The subagent is available but disallowed registration by
this server.
System action: Processing continues. Heartbeat and
message forwarding function will not be available.
Insufficient memory for subagent

initialization (the portion of initialization
where the allocation of memory failed).
Explanation: The SNMP subagent could not initialize

due to the inability to obtain the required memory.
System action: Initialization of the subagent fails.
User response: Allocate additonal storage to the
subagent.
ANR4674E
Error starting DPI thread - Return code:

Return code received from called routine.
Explanation: The SNMP subagent could not start the

DPI thread.
ANR4675E
System action: Processing continues. Heartbeat and

message forwarding function will not be available.
suite on the platform in use. If heartbeat and message
forwarding functions are required, re-start the server.
SNMP message forwarding to the

SNMP subagent was not started because
a thread resource was not available.
Server/subagent protocol violation invalid (where the protocol breakdown

occurred).
Explanation: The SNMP subagent received an

unexpected request from the server.
System action: The subagent will stop processing
requests from the server sending the invalid requests.
ANR4676E
Unable to register another server.
Explanation: The SNMP subagent received a request

to register a new server and was unable to allocate the
memory necessary to register the new server.
System action: The subagent will not register the new
server.
User response: It may be necessary to stop the

481
ANR4677I ANR4686E
ANR4677I
Session established with server name:

The name of the registered server..
Explanation: The SNMP subagent completed the

registration of the identified server.
System action: The subagent will wait for additional
requests from the server.
ANR4678I
Session closed with server name: The

name of the deregistered server..
ANR4682W
A SNMP agent connection error

occurred. Attempting to re-establish
connection.
Explanation: An error has occurred in the

communication between the subagent and the SNMP
agent.
System action: The subagent will attempt to
reconnect.
User response: Make sure that the SNMP daemon is
up, running and correctly configured.
Explanation: The SNMP subagent completed the

deregistration of the identified server.
ANR4683E
Explanation: An error occurred while opening the file

for writing trace data.

ANR4679W
Messages are no longer being forwarded

to the SNMP subagent.
Explanation: The server has encountered multiple

errors in forwarding messages to the SNMP subagent.
Messages are no longer being forwarded.
System action: The subagent continues operation

without tracing.
User response: Ensure there is adequate space on the
drive from which you are running the subagent and
retry the program.
ANR4684E
System action: The server continues operating, but

messages are no longer being forwarded.
User response: Message forwarding can be
re-initialized by either stopping the server and
re-starting it. Message forwarding will also be
re-started if the heartbeat function is in use and the
server re-synchronizes with the subagent. This
re-synchronization occurs if the subagent, dsmsnmp, is
stopped for longer than a single heartbeat interval (the
heartbeat interval is a server option and appears in the
output of the QUERY OPT command) and then
restarted.
ANR4680I
DPI subagent (The subagent name.):

"Connected" or "reconnected", ready to
receive requests.
Explanation: The subagent has successfully connected

or reconnected to the SNMP agent.
Unable to open trace file 'file name'.
Trap request failed - RC: Return code from

the trap request. Server index: Server index
number..

process a trap request from a server. data.
System action: The subagent processing continues.
ANR4685E
Insufficient memory for subagent

initialization.
Explanation: The SNMP subagent could not initialize

due to the inability to obtain the required memory.
User response: Allocate additional memory to the
subagent.
System action: The subagent is ready to receive

requests from servers.
ANR4686E
Explanation: The SNMP subagent trace could not

initialize due to the inability to obtain the required
memory.
ANR4681W
Connect to SNMP agent failed, will

keep trying.
Explanation: The subagent has failed in an attempt to

connect to the SNMP agent.

User response: Allocate additional memory to the
subagent.
System action: The subagent keeps retrying the

connection.
482
Insufficient memory for subagent trace

initialization.
ANR4687E ANR4695E
ANR4687E
Server/subagent protocol violation expecting registration request. Received

request: The value of the request that was
received.
Explanation: The SNMP subagent was expecting a

registration request. It actually received something
other than a registration request.
ANR4688E
Server/subagent protocol violation incorrect request header version.
Explanation: The SNMP subagent received a request

from a server that was not at the same maintenance
level as the subagent.
User response: Ensure the server and subagent are at
the same maintenance level. If they are, contact your
ANR4689E
Invalid request type received (The value

of the request that was received.).
ANR4692I

reconnected, ready to receive requests.
Explanation: The subagent has successfully

reconnected to the SNMP agent.
request from servers.
ANR4693I
Interface Driver information will be

loaded in quiet mode: Only warning
and error messages will be displayed.
Explanation: The server is loading information needed

for the Administrative WEB Interface. To minimize
message traffic, only error and warning messages will
be displayed.
System action: When the command completes, WEB
administrative information will be loaded into the
server.
ANR4694E
SNMP Subagent Port Confirmation Has

Failed.
Explanation: The SNMP subagent received an

unexpected request from the server.
Explanation: The server was communicating

configuration data to the SNMP subagent. An error
occurred in the exchange. The server could not
communicate interface information to the subagent.

System action: The server continues operation. The

SNMP administrative interface is inoperative.
User response: The most likely cause of this problem

is a temporary network failure. The server should be
re-started to retry the connection to the SNMP
subagent. If this problem occurs repeatedly, please
contact you service representative.
ANR4690E
Unexpected request type (The value of the

request that was received.) in trap data
header.
Explanation: The SNMP subagent received an invalid

trap request from a server.
ANR4691I

connected, ready to receive requests.
Explanation: The subagent has successfully connected

to the SNMP agent.
request from servers.
ANR4695E
SNMP: Communications Failure in

Receiving "verb type" verb.
Explanation: The SNMP client encountered a

communications error in using the verb type verb to
transfer information to or from the server and an
SNMP client.
System action: The SNMP session ends and server
User response: This may not be a problem if the
SNMP subagent was terminated while the session was
in progress. Otherwise, ensure that TCP/IP
communications is running normally.
483
ANR4697E ANR4704I
ANR4697E
SNMP: Failed to authenticate to server

at address address, port port.
Explanation: The SNMP client was attempting to run

a session with the server at the indicated address and
port number in response to an SNMP Get Request,
which causes a Server Script to be run. The subagent
connected to the indicated server, but failed in
authentication.
System action: The SNMP subagent ends this attempt
to run the script and continues operation.
User response: Ensure that the indicated server has an
an administrative id of SNMPADMIN and that this
adminstrative id has sufficient authority to run the
script and commands it contains.
ANR4698E
SNMP: Communications Failure in

Sending "verb type" verb (command).
Explanation: The SNMP client encountered a

communications error in using the verb type verb to
issue command command.
System action: The SNMP client session ends and
subagent operation continues.
ANR4699E
SNMP: Receive Buffer overflow.
Explanation: The SNMP client encountered an

overflow error in transferring information to or from
the server.
ANR4701I
The server move size threshold has been

set to new threshold. Move operations
new value.

the value for the move size threshold value. This
setting determines the maximum number of megabytes
that are moved on the server in one database
transaction, dependent also on the setting for the move
batch size. The setting influences file movement for
server migration, reclmation, storage pool backup, and
move data operations.
move operations that are started after this message is
issued.
ANR4702I
The server transaction group maximum

has been set to new value. Client sessions
that are started after this point will use
the new value.

the value for the maxmimum number of files that can
be sent from the client in a single database transaction.
client sessions that are started after this message is
issued.
Invalid key-ring filename Key Ring
Filename
System action: The SNMP client session ends and

subagent operation continues.
ANR4703E
Explanation: The key-ring filename specified did not

contain the .kyr extention.
ANR4700I
The server move batch size has been set

to new batch size. Move operations that
start after this point will use the new
value.

the value for the move batch size value. This setting
moved on the server in one database transaction,
dependent also on the setting for the move size
threshold. The setting influences file movement for
server migration, reclamation, storage pool backup, and
move data operations.
move operations that are started after this message is
issued.
User response: Rename your key-ring filename to

contain the .kyr extention. Reexcute the command with
the new filename.
ANR4704I
Explanation: The key-ring filename have been set to

the new value specified in the DEFINE KEYRING
command.
User response: Restart the server to use the new
key-ring information.
484
key-ring filename and password have

been set. Restart the server to use the
new settings
ANR4705I ANR4713E
ANR4705I
The server IDL definitions have not

been installed. These definitions will
need to be installed for the Web
Administrator interface to work.
Explanation: The server attempted to query the server

IDL interface and found no definitions defined. Because
of this error the HTTP engine returns a 404 not found
message.
User response:
1. Remove COMMMETHOD HTTPS from your option
file.
2. Install and configure the web proxy. See Quick Start
Appendices for more information on how to install
and configure the web proxy.
ANR4709W

User response: If you would like to use the server
web administrator interface you will need to:
1.
Halt the server.
2.
Issue the command DSMSERV RUNFILE

dsmserv.idl. For AS/400 command see next step.
3.
For AS/400, issue the command STRSVRADSM

SVRMODE(*PRPWEB).
4.
Restart the server.
ANR4706W
Unable to open file Filename to satisfy

web session Session ID.
Explanation: A web browser requested a file and the

server could not find the file on the local file system.
Special note, some files requested from the server are
not vaild and are caused by a browser error. For
example, a request for CommandLineBeanInfo.class is
not a valid file request. However, a request of a GIF
image or HTML page should not produce this error.
User response: Verify that permission for the file are
set correctly and file exists.
ANR4707E
Import/Loaddb command operation

terminated - incomplete input volume
list.
Explanation: The list of volumes needed to process

the command was incomplete. At least one volume
needed for the operation is missing from the end of the
list.
System action: The command operation is ended.
sure the necessary volumes are included in the volume
list.
Explanation: A volume mount is awaiting operator

intervention on the specified library manager server.
System action: The volume mount operation waits for
operator intervention.
User response: Refer to the server consol and/ir
activity log on the named library manaer server to
determine the action that needs to be performed to
complete the mount operation.
ANR4710W
Native SSL support has been disabled,

please use the web proxy.
Explanation: Starting in this version of this product

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.
Library manager Server Name could not

be contacted to control library Library
Name.
Explanation: The specified library manager server

could not be contacted for control of the named library.
System action: The server will continue to contact the
named library manager server. Volume mounts in the
library will fail until communication is successful.
User response: Determine why the named server is
not running or why the network prevents
communication with te named server.
ANR4712E
Command: The DEVCLASS parameter is

only valid for volume history types
DBBACKUP or DBSNAPSHOT.

volume history type was specified for the TYPE=
parameter.
User response: Re-issue the command and specify a
valid type value.
ANR4713E
ANR4708I
Intervention required to mount volume

Volume Name on Library Manager Server
Server Name.
Command: The "option" string is not valid

for the Hex Filespace Field.
Explanation: The command indicated specifies a value

that is not valid for the Hex Filespace parameter.
command.
entry for the Hex Filespace parameter.
485
ANR4714I ANR4724E
ANR4714I
Command filename for filespace filespace

name of node node name started as
process process ID.
Explanation: A file deletion process has started to

delete one or more files from the given filespace for the
for given node. The process is assigned the ID specified
in the message.
to perform the operation in response to the DELETE
FILE command entered by an administrator.
User response: To obtain status on the file deletion
process, issue the QUERY PROCESS command. The
process may be canceled with the CANCEL PROCESS
command.
ANR4715I
DELETE FILE file name (backup/archive

data) for filespace filespace name of node
node name started.

(on the server) to delete files from the given filespace
for the given node.
backup and archive objects that match the given file
name while server operation continues.
process may be canceled by an authorized
ANR4716I
DELETE FILE file name (backup data) for

filespace filespace name of node node name
started.

for the given node.
backup objects that match the given file name while

ANR4718I

been deleting files for the given fliespace of the given
node is canceled by the CANCEL PROCESS command.
The number of objects deleted before the cancel ended
the operation are reported in the message.
User response: No action is required. An authorized
administrator can issue the DELETE FILE command to
delete the remaining files desired.
ANR4719I
DELETE FILE file name (archive data) for

started.

for the given node.
archive objects that match the given file name while
486
DELETE FILE file name complete for

: number of objects objects deleted.
Explanation: A server process deleting file space data

for the node specified has completed. The total number
of objects deleted is reported in the message.
ANR4723E
Session rejected for down level storage

agent storage agent name.
Explanation: A down level storage agent attempted to

connect to this server. The server can not support all
previous versions of the storage agent.
System action: The server will not support
connections by storage agents at a specific lower
versions of the product. Review the README for an
explanation of supported storage agent levels for this
server. The storage agent will not startup and will
report ANR0454W indicating that it is down level.
ANR4724E
ANR4717I
DELETE FILE file name canceled for

: number of objects objects deleted.
During the backup of node node (Node

id) filespace filespace name (filespace id) a
deletion activity occurred.
Explanation: During full or incremental backup

processing, files were deleted from the file space. The
files were not deleted by expiration, but by some other
process. DELETE FILESPACE, DELETE VOLUME,
AUDIT VOLUME, or some other administrator
command can cause files to be deleted. The file space
image on the server will not be consistent with the
ANR4725E ANR4730E
client until an incremental backup is completed for the
node.
v An unsupported model of the filer server was

detected
System action: The server will continue processing.
v If the message specifies address 127.0.0.1 or the

address of the server system, the
NDMPCONTROLPORT and/or NDMPPORTRANGE
options may be set to port numbers or ranges which
are already in use.
User response: Perform an incremental backup for the

client node.
ANR4725E
Source file(line number): Server lock

Locktype, mode Lockmode failed.
Explanation: An internal error occurred in an attempt

to obtain a lock during processing.
fails.
User response: Retry the process. If the process fails
ANR4726I
The support module has been loaded.
Explanation: The module indicated has been

successfully loaded. Operations involving this module
may be performed by the server.
System action: Functions which depend on this
module may now be performed on the server.
System action: TSM server backup/restore of the file

server fails.
User response: Check if file server is accessible
through the network; check each of the attributes
specified during datamover definition; check NDMP
versions supported by the file server; check the number
of open NDMP sessions with the file server, verify that
file server model is supported by TSM server. If the
server's address is in the message ensure that the ports
specified or defaulted for options
NDMPCONTROLPORT and/or NDMPPORTRANGE
are available for use. Depending on the operating
system, the netstat operating system command may be
used to determine in-use port numbers.
ANR4729E

ANR4727E
Server Server name is incompatible with

this server. Please update the server to
the same level as this storage agent.
Server connection to file server File

server name failed. The level of the file
server operating system is unsupported
by TSM server. Please upgrade the file
server to the level of the operating
system supported by the server.
Explanation: The storage agent attempted to connect

to a downlevel server. The server version, release, and
fix level must exactly match, otherwise data corruption
may occur. For example, a version 4.2.0.0 storage agent
cannot connect to a version 4.1.0.0 server.
Explanation: The TSM server was trying to connect to

a file server with an unsupported level of the operating
system. The server can establish NDMP connection
only to a file server with supported level of the
operating system. Please check the following site for
supported levels of file server operating systems:
http://www.tivoli.com/storage
System action: Upgrade the TSM server to the same

level as the storage agent.
System action: The TSM server backup/restore of the

file server fails.
User response: Upgrade the file server to a supported

level of the operating system.
ANR4728E
Server connection to file server File

server name failed. Please check the
attributes of the file server specified
during definition of the datamover.
Explanation: The server attempted to connect to a file

server. The connection failed because of one of the
following possible reasons:
definition was incorrect: TCP/IP address of the file
v File server does not support requested NDMP
version
sessions
ANR4730E
Command: The number of pool type

storage pool names specified with the
parameter name parameter exceeds the
maximum number allowed for
simultaneous write.
Explanation: The number of copy storage pools

combined with the number of active-data pools for a
given primary storage pool is limited to three. Earlier
versions allowed up to ten copy storage pools in the
copy storage pool list.
total of three or fewer copy storage pool names and
active-data storage pool names.
487
ANR4731E ANR4737E
ANR4731E
Command: The pool type storage pool

storage pool name is not defined.

STGPOOL command contained a storage pool that is
not defined as either a copy storage pool or an
active-data storage pool.
User response: Verify that the copy or active-data
storage pool name stated in the error message is
correct. If using the COPYSTGPOOLS parameter,
correct the problem by using a copy storage pool that
already exists or define the copy storage pool. If using
the ACTIVEDATAPOOLS parameter, correct the
problem by using an active-data storage pool that
already exists or define the active-data storage pool.
Retry the command.
ANR4732E
Command: The storage pool storage pool

name is not a/an pool type storage pool.

STGPOOL command contained a storage pool name
that is not a copy or active-data type storage pool.
of an error. This removal is only for the session

indicated in the message and does not effect other
session operation.
User response: The error that occured could be one of
many failure. Look for the following items in the active
log or on the server console. 1. Is the named storage
pool currently unavailable? 2. Have any I/O error
occured on the destination devices (disk or tape
drives)? 3. Is the mount limit on the device class
correctly set? 4. Is the node's MAXNUMMP value
sufficient to satisfy the request?
ANR4735W
Server-free processing is not available.

Initialization failed.
Explanation: An error occurred while initializing

server-free processing. Server-free data transfer is not
available to backup and restore images.
System action: Client backup and restore image
requests will use lan-based data transfer.
User response: Check for messages during server
initialization and correct the error.

User response: Verify that the copy or active-data
storage pool name stated in the error message is correct
or remove the storage pool name from the list. If using
the COPYSTGPOOLS parameter, correct the problem by
using a copy storage pool that already exists or define
the copy storage pool. If using the
ACTIVEDATAPOOLS parameter, correct the problem
by using an active-data storage pool that already exists
or define the active-data storage pool. Retry the
command.
ANR4733E
Command: The pool type storage pool

contains a pool type storage pool name
that introduces a cycle into the storage
pool chain.
ANR4736E
Set serverfree is not allowed when

server-free is not available.
Explanation: Server-free processing did not initialize.

Changing the status is not allowed.
User response: Server-free status may be changed
when the status is ON or OFF.
ANR4737E

platform) - the copy continue attribute for
storage pool storage pool name prevented
further retries.

STGPOOL command contained a copy or active-data
storage pool that eventually points to the storage pool
being processed.
Explanation: During a backup session one or more

copy storage pools associated with the indicated
storage pool had a failure. The operation was halted
because the copy continue option for the indicated
storage pool caused the process to stop.
User response: Remove the storage pool name from

the copy or active-data storage pool list and retry the
command.
User response: Verify the following: 1. Does the

device class(es) have enough mount points to satisfy
the request? 2. Was the node's MAXNUMMP value
sufficient to satisfy the request? 3. Were there any
errors reported during the transaction regarding I/O or
related issues?
ANR4734W
The pool type storage pool pool name was

removed from the storage pool list
because of a failure for session Session
Id.
Explanation: The named storage pool was removed

from the storage pool list for the current session
backup/archive/space management operation because
488
ANR4738E ANR4742W
ANR4738E

is in use as a copy or active-data storage
pool by one or more other storage pools.

a pool that is a copy storage pool and listed as one of
the copy storage pools of other storage pool via the
DEFINE STGPOOL or UPDATE STGPOOL's
COPYSTGPOOL parameter, or, a DELETE STGPOOL
command specifies a pool that is an active-data storage
pool and listed as one of the active-data storage pools
of other storage pools via the DEFINE STGPOOL or
UPDATE STGPOOL's ACTIVEDATAPOOLS parameter.
HLADDRESS and LLA parameters with correct address

information.
User response: Both the high level address and low
level address are required for an address to be valid.
Issue the UPDATE NODE command for this node with
complete addressing information through the
HLADDRESS parameter for the node address, and the
LLADDRESS parameter for the node listen port
information.
ANR4741W

command.
User response: If necessary, issue the UPDATE
STGPOOL command to update other storage pools so
that they do not reference the pool to be deleted, and
ANR4739E
Either the high-level address (hladdress),

low-level address (lladdress), or both
were entered in error.
Explanation: The high-level or low-level addresses

supplied are incorrect.
command.
User response: Both the high-level address and
low-level address are required for an address to be
valid. For an update, both high-level address and
low-level address are required for the update to
succeed. For a new definition, both high-level address
and low-level address are required when
SESSIONINIT=SERVERONLY. Either the high-level
address or low-level address is missing from this
command. Issue the command again and supply the
missing address represented by a "?" in this message.
ANR4740W
Either the high level address, low level

address, or both were never entered for
the specified node( nodename ) and the
session initiation status is being
changed.
Explanation: When the session initiation status of a

node is changed by using the SESSIONINIT parameter
on the UPDATE NODE command, the scheduling table
is updated to reflect the address specified with HLA
and LLA keywords of the UPDATE NODE command.
If one or both of these keywords have never been used
to provide addressing information for the node,
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
This command will rename

schedules. Renaming this administrator
will cause these schedules to fail.
Explanation: A RENAME ADMINISTRATOR

command has been entered for an administrator that
owns administrative schedules. If you confirm that you
want to proceed with this command, the schedules
owned by this administrator will fail when executed in
the future.
User response: To process the RENAME
ADMINISTRATOR command, enter 'Y' to continue or
'N' to stop the process. To deal with schedules owned
by the administrator, use the QUERY SCHEDULE
command, or an SQL SELECT statement on the
schedules contolled by an administrator that has
authority to execute them, or use the DELETE
SCHEDULE command to remove the schedules.
ANR4742W
This command has renamed

administrator adminName to
newAdminName. This administrator has
defined or updated schedules. This will
cause these schedules to fail in the
future.
Explanation: A RENAME ADMINISTRATOR

command has been entered and the administrator
renamed owns the administrative schedules. The
schedules will fail when executed in the future because
they do not belong to the administrator's new name.
System action: The system renames the administrator.
or an SQL SELECT statement on the
schedules controlled by an administrator that has
authority to execute them, or use the DELETE
SCHEDULE command to remove the schedules.
489
ANR4743W ANR4749I
ANR4743W
An insufficient number of mount points

are available in device class device class
name.
Explanation: During simultaneous write processing,

the server cannot allocate sufficient mount points for
the specified device class. Possible reasons include:
ANR4746E
Session rejected for up level storage

agent storage agent name.
Explanation: An up level storage agent attempted to

connect to this server. The storage agent can not be at
higher level than the server.
v The drives that service the device class are

inaccessible.
System action: The server will not support

connections by storage agents at a higher version, at
the same version with a higher release, or at the same
version and release with a higher modification level.
The storage agent will not startup and will report
ANR0454W indicating that no resources are available.
v The mount limit specified for the device class does

not provide a sufficient number of mount points to
support the simultaneous write operation.
User response: Ensure that:

v The mount limit specified for the device class
provides a sufficient number of mount points to
support the simultaneous write operation.
ANR4747W
v Enough drives are defined and on-line for the library

that services the device class.
Explanation: The web administrative interface is no

longer supported. It has been replaced by an
administrative interface based on the Integrated
Solutions Console.
ANR4744W
The server cannot acquire a sufficient

number of mount points.
Explanation: During simultaneous write processing,

the server cannot acquire a sufficient number of mount
points to satisfy the request.
User response: Examine error messages that might
have been displayed prior to, and after this message.
Correct any problems, if possible.
ANR4745E
Server server name

(version.release.modification level.fix level) is
not compatible with storage agent
storage agent name
(version.release.modification level.fix level).
Explanation: The server and storage agent are not

compatible. The storage agent must be at the same
version and release as the server. It must also be at the
same modification level, or the same modification level
minus one. For example, a server at version 5.2.1
would allow connections from a storage agent at
version 5.2.1 or version 5.2.0.
System action: If the storage agent and server are not
at the same version and release, update the storage
agent to the same version and release as the server.
Once the storage agent is at the same version and
release as the server, upgrade it to either the same
modification level or the same modification level minus
one.
The web administrative interface is no

longer supported. Begin using the
Integrated Solutions Console instead.
System action: The web administrative interface's web

page is not displayed.
User response: Install the IBM Tivoli Storage Manager
support for the Integrated Solutions Console and begin
using it to manage your servers.
ANR4748E
A NAS operation requiring NDMP

Version 4 was attempted for file server
File server name , however the current
NDMP session uses NDMP Version 3.
Please verfiy that file server supports
NDMP version 4.
Explanation: A NAS operation which requires NDMP

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
other operation on the file server fails.
User response: Verify that the file server supports
NDMP Version 4. Verify that the file server is
configured to accept connections using NDMP Version
4.
ANR4749I
Key-ring filename and password have

been deleted from the server database.
Explanation: The key-ring filename and password

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
and the keyring files cert.kdb,cert.crl,cert.rdb do not
exist.
User response: Before restarting the server you should
490
ANR4752I ANR4759E
delete the corresponding cert.kdb,cert.crl,cert.rdb and
cert.arm files from the server execution directory if they
exist. Restart the server to generate and use the new
key-ring information.
ANR4752I
REPAIR STGVOL process process number

started for number of volumes volumes.
Explanation: The REPAIR STGVOL process has been

started as the reported process number. This will
evaluate and if needed repair the indicated number of
volumes.
User response: This process may be monitored using
the QUERY PROCESS command. If this process needs
to be cancelled, issue the CANCEL PROCESS
command.
ANR4753E

ended, processed volumes processed of
total volumes total volumes with repaired
volumes repaired and failed volumes
failures.
Explanation: The REPAIR STGVOL process has ended.

It processed volumes processed out of total volumes total
volumes to be processed. The repaired volumes indicates
the number of volumes that needed database repairs
and were repaired. The failed volumes are volumes that
either failed during evaluation or during database
repair if it was needed.
User response: If there were failed volumes, review the
activity log for more information about the failure.

and were repaired.
User response: If the volumes processed is less than the
total volumes, this may be because the process was
cancelled before it could process all the needed
volumes. Review the activity log to determine if this is
the case and re-issue the command to complete this
processing. Or if volumes were reclaimed or deleted
while this process was running, there may have been
fewer actual volumes to process than what was
calculated when the process started. If this is the case
no further action is necessary.
ANR4756I
REPAIR STGVOL selected volume

volume name.
Explanation: The REPAIR STGVOL selected volume

name volume to process. This volume will be evaluated
for database reference errors and if any are
encountered, they will be corrected.
ANR4757I
REPAIR STGVOL finished evaluating

volume volume name, no repair was
needed.
Explanation: The REPAIR STGVOL finished

evaluating volume name volume. No repair actions were
taken for the database because there were no errors
detected.
ANR4754I

volumes repaired.
ANR4758W
REPAIR STGVOL repaired volume

volume name, database reference errors
were found and corrected.

and were repaired.
Explanation: The REPAIR STGVOL evaluated volume

name volume and determined that repair actions were
needed. The necessary repairs were done successfully.

ANR4755W
ANR4759E

volumes repaired.

REPAIR STGVOL failed to process

volume name.
Explanation: The REPAIR STGVOL failed for volume

name volume. This process either failed while
evaluating this volume or it had determined that repair
actions were needed and it failed performing those
actions.
User response: Review the activity log for an
491
ANR4760I ANR4766E
indication of why processing for this volume failed. Try
issuing "REPAIR STGVOL VOLNAME=volume name" to
process this volume again. If this volume was deleted
from the server, this message can be ignored.
FORMATSIZE parameter is valid when using z/OS

Media library for sequential FILE storage. The z/OS
Media server formats each FILE volume as it is being
filled.
ANR4760I
ANR4764E
REPAIR STGVOL reset processing

history.
Explanation: The REPAIR STGVOL command was

issued with RESET=YES. This resets the processing
history. Resetting the processing allows the command
to be rerun and causes previously evaluated volumes to
be re-evaluated.
User response: An administrator may want to
periodically reset the processing history and re-evaluate
all volume in the server as a means of validating the
server database.
Explanation: The length for (parameter value) specified

for the (parameter) parameter in command command
exceeds the maximum allowed length.
valid length for the parameter. For information on valid
values for the parameter for the command, refer to the
ANR4765I
ANR4761E
REPAIR STGVOL reset processing

history failed.
Explanation: The REPAIR STGVOL command was

issued with RESET=YES. This resets the processing
history. However, the reset of the processing history
failed.
User response: The server is likely out of memory or
resources. This command should be re-issued after
either halting and restarting the server or after halting
the server, rebooting the server machine, and than
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
for active data storage pool volumes.
Explanation: The QUERY CONTENT server command

has been entered with an invalid type parameter. The
SPACEMANAGED or ARCHIVE parameters are not
valid when the volume specified belongs to an
active-data type storage pool.
User response: Reissue the command with correct
TYPE parameter for active data storage pool.
ANR4763E
Command: Invalid parameter - parameter.

entered with an invalid parameter that is not applicable
when using z/OS Media library for sequential FILE
storage.
The key-ring file password was set.

Restart the server to use the new
password.
Explanation: The password that is used by the server

for the key-ring file was set to a value that was
specified in the SET SSLKEYRINGPW command. This
is typically done after the key-ring file's password is
changed using an external utility.
User response: Restart the server to use the new
key-ring file password.
ANR4766E
The server could not access the key-ring

file using the password specified in the
SET SSLKEYRINGPW command.
Explanation: The password used by the server for the

key-ring file was checked for validity but was not
valid.
System action: None
User response: The QUERY SSLKEYRINGPW
command will show you the key-ring file password
that the server is currently using. If the password was
changed with an external utility, ensure that the
password is the same as that which was specified in
the SET SSLKEYRINGPW command. If the password
was lost, issue the DELETE KEYRING command to
delete the current key-ring file. When you restart the
server it will generate a new key-ring file, password,
and self-signed certificate. Issue the QUERY
SSLKEYRINGPW command to obtain the new
password. Then use an external utility to import
additional certificates again and designate one as the
new default. Restart the server to use the additional
certificates.

proper syntax. Neither NUMBEROFVOLUMES nor
492
Command: Invalid length for parameter

parameter - parameter value.
ANR4767E ANR4786E
ANR4767E
The server was unable to change the

key-ring file password using the new
password specified on the SET
SSLKEYRINGPW command along with
the old password that the server has
stored.
Explanation: The previous key-ring file password

remains in effect.
System action: None
User response: The QUERY SSLKEYRINGPW
command will display the key-ring file password that
the server is currently using. If the SET
SSLKEYRINGPW password UPDATE=YES command is
unable to update the key-ring file password, the
key-ring file and it's password can be deleted and
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
files cert.* in the server's instance directory. 4.
Restarting the server so that the key-ring file and it's
password are regenerated by the server.
ANR4768E
Command: Invalid volume name - volume

name.

invalid FILE volume name for a ZOSMEDIA library
volume.
command.
volume name that does not exceed 44 valid characters.
to the Administrators Reference.

ANR4782E

command fails because the description specified is
longer than the length limit number of characters
allowed.
database.
a shorter description.
ANR4783E
Node group node group name defined.
Command: Node group node group name is

not defined.

command fails because the node group name node group
name specified does not refer to a defined node group
database.
node group name that is defined in the server database.
For a list of the names of defined node groups in the
server database, issue the QUERY NODEGROUP
command.
ANR4784I
ANR4780I
Command: Description exceeds maximum

length of length limit characters.
Node group node group name updated.
Explanation: A DEFINE NODEGROUP command has

created the node group indicated.

NODEGROUP command, the node group node group
name has been updated in the server database.
ANR4781E
Command: Invalid node group name node group name.

ANR4785I
Node group node group name deleted.

NODEGROUP command, the node group node group
name has been deleted from the server database.

database.

a node group name that conforms to the name
length specifications for valid node group names, refer

command command fails because the node group node
group name specified refers to a node group that still
contains at least one node. A node group cannot be
ANR4786E
Command: Node group node group name

still contains at least one node.
493
ANR4787I ANR4794E
deleted if one or more client nodes are still assigned to
the node group.
database.
node group, issue the DELETE NODEGROUPMEMBER
command. After all nodes are removed, issue the delete
command again.
ANR4787I
Command: number of nodes members

defined in the node group node group
name.
Explanation: A DEFINE NODEGROUPMEMBER

command has created the specified number of members
in the indicated node group.
ANR4791E

name specified refers to a node group that is already
database.
node group name that is not defined in the server
database. For a list of the names of defined node
groups in the server database, issue the QUERY
NODEGROUP command.
ANR4792E

ANR4788I

deleted from node group node group
name.
Explanation: A DELETE NODEGROUPMEMBER

command has deleted the specified number of
members from the indicated node group.
ANR4789I
Node node name associated to node

group node group name.

the DEFINE NODEGROUPMEMBER command. Node
node name is associated with the node group name node
group name.
ANR4790I
Node node name disassociated from node

group node group name.

the DELETE NODEGROUPMEMBER command. Node
node name is no longer associated with the node group
name node group name.
Command: Node group node group name is

already defined.
NDMP Tape server unable to initialize

due to error in LISTENing on port Port
Explanation: The server failed in attempting to listen

for session requests on the server's internal tape server.
System action: Server operation continues, but NDMP
operations may fail.
User response: Ensure that the
NDMPCONTROLPORT option defaults to or is set to a
port number which is available in the system. The
QUERY OPTION command can be used to determine
the port number associated with the
NDMPCONTROLPORT option. If this value requires
change, the server will have to be restarted after setting
the option in the server options file.
ANR4793E
NDMP Tape server is terminating due to

an error in accepting a new session on
Port Port
Explanation: The server failed in attempting to accept

a new session on the server's internal tape server.
System action: Server operation continues, but NDMP
operations may fail.
User response: Ensure that the
NDMPCONTROLPORT option defaults to or is set to a
port number which is available in the system. The
QUERY OPTION command can be used to determine
the port number associated with the
NDMPCONTROLPORT option. If this value requires
change, the server will have to be restarted after setting
the option in the server options file.
ANR4794E
The NAS file server File server name

failed to open an NDMP data
connection to the TSM tape server.
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
494
ANR4795E ANR4800E
TSM server failed. This may occur because a firewall
exists between the file server and the TSM server and
is preventing outbound network connections on the file
server. This may also occur if the network configuration
of the system running the TSM server is reporting an
invalid TCP/IP host address, for example "127.0.0.1".
defined for the drive. Also verify that the information

contained in the paths is correct.
System action: The TSM server backup operation on

the file server fails.
Server-free operation type operation had a

target failure. Please refer to
accompanying messages and Message
Reference Manual for further
information.
User response: Verify that the NAS file server is

capable of starting outbound network connections to
the TSM server. Verify that the file server supports
NDMP 3-way operations. Verify that the network
configuration of the system running the TSM server is
reporting a valid TCP/IP host address.
Explanation: The server-free operation encountered a

target failure. This is typically due to one of three
conditions: 1. A SCSI error was encountered in either
the source, target or datamover. 2. There was a problem
with the HBA issuing the SCSI command 3. An I-O
error caused the operation to time out.
ANR4795E
System action: The server does not complete the

server-free operation and attempts to trigger a failover
operation by the client.
The TSM tape server failed to open an

NDMP data connection to the NAS file
server File server name .
Explanation: During a NAS filer-to-server restore

operation the data connection from the TSM server to
the NAS file server failed. This may occur if the NAS
file server is not properly configured to support NDMP
3-way restore operations.
System action: The TSM server restore operation on
User response: Verify that the file server supports
NDMP 3-way restore operations.
ANR4796E
The TSM tape server failed to open a

listening socket for accepting an NDMP
data connection from a NAS file server
using the network interface network host
name .
Explanation: During a NAS filer-to-server backup

operation the TSM tape server failed to open a TCP/IP
socket in order to listen for NDMP data connections
from a NAS file server. This may occur if the network
interface chosen for NDMP data connections is not
running or does not support IP Version 4.
System action: The TSM server backup operation of
User response: Verify that the network interface
specified in the NDMPPREFDATAINTERFACE server
option is properly configured and running.
ANR4798E
User response: If a SCSI error was encountered, please

refer to the sense information and correct for the
indicated problem. If the HBA had an error while
issuing command, please refer to the accompanying
message for appropriate action. If the operation timed
out, please verify the datamover operation and SAN
connections.
ANR4799E
Explanation: The server-free operation failed after

issuing the SCSI command. This might be because the
value for the HBA (host bus adapter) scatter-gather list
is not large enough.
System action: The server does not perform the
server-free operation. The server will attempt either a
LAN-free or classic LAN operation.
User response: Perform either, or both, of the
following steps to allow server-free operations:
v Change the serverfree batchsize to a lower value.
v Change the MAXIMUMSGLIST value for the HBA
within the Windows registry, or run the DSMMAXSG
utility to change the MaximumSGList value to
0x41(65) for all HBAs.
ANR4800E
ANR4797E
Drive driveName is missing path

information. Please check that all
related paths are defined properly.
Explanation: A drive does not have sufficient path

information for the operation to complete. This is
typically due to a path not being defined.
The server-free operation type from device

source name through data mover data
mover name to device target name failed
after issue.
The server-free operation from device

mover name to device target name
encountered an I/O error. The following
information was returned from sense
device name: KEY=Key value ASC=Asc
value ASCQ=Ascq value SENSE=Sense info
System action: The server fails the storage operation.
Explanation: The server-free process did not complete

due to an I/O error.
User response: Verify that all applicable paths are
System action: The server will attempt to recover
495
ANR4801E ANR4809I
from the error and if possible retry the server-free data
transfer.
ANR4805I
User response: The device reference manual provided

with the device usually contains tables that explain the
values of the KEY, ASC, and ASCQ fields. If the
problem persists, contact your device service
representative and provide the internal code values and
sense data from this message.
Explanation: The administrator's password expiration

period is currently set to the common password
expiration period.

uses the common password expiration
period.

ANR4801E
The server-free operation from device

mover name to device target name
encountered an error. This sense
information is typically generated by
configuration issues, please verify the
device definitions.

due to the target being unreachable.
System action: The server will fail the transfer.
User response: For the devices involved in this
operation, please verify that the device and path
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
data mover can see both target devices.
ANR4802I
Password expiration period for node

node name has been reset.
Explanation: The node's password expiration period

has been reset to the common password expiration
period.
ANR4806W
The password expiration period for node

name cannot be reset to the common
Explanation: The node's password expiration period

could not be reset to the common password expiration
period at this time.
User response: Attempt to reset the node's password
expiration period at a later time.
ANR4807W
The server is unable to reset

administrator name password expiration
period to the common password
expiration period.

period could not be reset to the common password
expiration period at this time.
User response: Attempt to reset the node's password
expiration period at a later time.

ANR4803I
Password expiration period for

administrator administrator name has
been reset.

period has been reset to the common password
expiration period.
ANR4804I
Node node name already uses the

common password expiration period.
Explanation: The node's password expiration period is

currently set to the common password expiration
period.
ANR4808W
The password expiration period for all

administrators and nodes has been reset
to the common password expiration
period.
Explanation: All administrators not managed by a

profile and nodes on this server have had their
password expiration period reset to the common
ANR4809I
Audit command: Node group node group

name has the same name as a node. The
node group entry must be corrected.
Explanation: During Audit processing, a node group

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.

496
ANR4810I ANR4818E
ANR4810I
Audit command: Nodeid nodeid found for

missing node group node group name.
The node group entry must be corrected.
ANR4815I
Audit command: Nodeid Node Id in node

group node group name does not exist.
The node group entry will be corrected.
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
group entry is not corrected.

found in a node group, but the node does not exist.
the node group entry is deleted.
ANR4811I
Audit command: Nodeid Node Id in node

group node group name does not exist.
ANR4816I
Audit command: Nodeid nodeid found in

inconsistent node group node group name.

found in a node group, but the node does not exist.
the node group entry is not corrected.

found in a node group that is inconsistent. Because
group entry is deleted.
ANR4812I

inconsistent node group node group name.

found in a node group that is inconsistent. Because
FIX=NO has been specified for the command, the node
group entry is not corrected.
ANR4813I
Audit command: Node group node group

name has the same name as a node. The
node group entry will be corrected.
Explanation: During Audit processing, a node group

was found with the same name as an existing node.
the node group entry is deleted.
ANR4817E
Command Command: Administrator

admin is not allowed to issue this
command while the system date is
suspect. Correct the system date or use
the ACCEPT DATE command to
establish the current date as valid.
Explanation: The server has noted that the current

system date is suspect. An admin client session may
issue the ACCEPT DATE command to establish the
current date as valid. No other commands are allowed
until the system date is corrected or the current date is
established as valid.
User response: If the current system date is not valid,
reset the date. Otherwise, use the ACCEPT DATE
command to establish the current date as valid on the
server. Reissue the command.
Accepting an invalid date can cause any of the

following problems:
v Premature deletion of data

v Excessive retention of data
ANR4814I

missing node group node group name.

found for a node group that does not exist. Because
group entry is deleted.
v Scheduling problems
v Event record problems
v Password expiration problems
ANR4818E
The text cannot be formatted and

written to the server console. The text is
text. Try setting a wider screen width.
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.
497
ANR4819E ANR4827E
System action: The server will not write the output to
the console. The server continues operation.
System action: The TOC loading or reading is ended

User response: Increase the width of your window

and try the command again.

application.
ANR4819E

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
authorization. The server will not perform the request.
System action: The server will not perform the
request.
User response: Complete the work using a node with
proper authorization.
ANR4820E
Command The creation date and creation

time are both required to be specified.

due to the target being unreachable.
ANR4824E
Explanation: The server ends a table of contents

(TOC) loading or reading for the specified node and
file space because the requested resource is already in
User response: Try the operation again at a later time.
ANR4825E

User response: Reissue the command, specifying both
creation date and creation time, or neither of them.
ANR4821E
Command: The creation date - date. is not

valid

with an invalid creation date.
creation date.
ANR4822E
Command: The creation time date is not

valid.

with an invalid creation time.
creation time.
ANR4823E
The loading or reading of a table of

file space name failed because sufficient

file space because sufficient memory is not available on
the server.
498

file space name failed because of a lock
conflict.
More than one table of contents is

requested but they are not for the same
node node name and same file space file
space name.

(TOC) loading for the requested TOCs. The requested
TOCs have to be for the same file space in the same
node name.
User response: Try the TOC loading specifying the
TOCs in the same node for the same filespace.
ANR4826E
The object for the table of contents is

not found in the server for node node
name, file space file space name.

(TOC) loading or reading for the object in the specified
node and file space, because the server cannot find the
object for the TOC.
and server operation continues. The TOC object could
be deleted from the server during server expiration or
volume deletion operation.
User response: Make sure a correct TOC object is
specified.
ANR4827E
The loading of a table of contents for

node node name, file space file space name
failed because a thread resource not
available.

(TOC) loading for the specified node and file space
because sufficient memory is not available for starting
additional processes on the server.
ANR4828E ANR4834E
System action: The TOC loading is ended and server
application.
ANR4828E

file space name failed because an internal
server error was detected.

file space because an internal logic error is detected.
ANR4831E
Explanation: During the TOC loading or reading

operation, the requested input volume is already in use
by another process.
User response: Try the operation again at a later time.
ANR4832E

representative.
ANR4829E

file space name failed. The transaction is
stopped.

failed transaction.
System action: The table of contents (TOC) loading or
reading is ended and server operation continues.
ANR4830E

file space name failed. Insufficient mount
points are available to satisfy the
request.

sufficient mount points to read the table of contents
(TOC).
available.
The loading or reading of a Table of

Contents for node node name, file space
file space name failed. The input volume
is already in use.

file space name failed. The required
volume was not mounted.
Explanation: During the table of contents (TOC)

loading or reading operation, a required volume cannot
be mounted. The mount request may have been
canceled.
User response: Try the TOC loading or reading again
and make sure the necessary volumes are accessible.
ANR4833W

file space name failed. The file was
deleted from server storage.
Explanation: During the table of contents (TOC)

loading or reading operation the file has been deleted
from server storage by another process before the
loading or reading is complete.
processes can delete files in server storage during TOC
loading or reading.
ANR4834E

file space name failed. The data transfer is
interrupted.

file space because data transfer to or from data storage
was interrupted by an external event.
System action: The TOC reading is ended and server
499
ANR4835E ANR4842E
interrupted. Attempt the operation again if the problem
can be resolved.
ANR4835E
The reading of a table of contents for

failed. A data integrity error was
detected.
Explanation: The server stops reading a table of

contents (TOC) for the specified node and file space
because a data integrity has been encountered on the
server.
this message and contact your service representative.
ANR4836E
The reading of a table of contents for

failed. There was an error in reading
from a device.

(TOC) reading for the specified node and file space
because an I/O error has been encountered by the
server in reading from a device.
this message that specify the device that is failing. The
server may need to be shut down with a HALT
command to correct the hardware problem.
ANR4837I
The loading for the table of contents for

started.
Explanation: The loading for the table of contents

(TOC) in the specified node and file space has been
started.
ANR4838I

was successful: total entries loaded
number of entries.

successfully finished.
ANR4839E

(TOC) in the specified node and file space has failed.
System action: The TOC loading is ended and the
this message to determine the source of the problem.
ANR4840I

was cancelled.

cancelled by the user.
ANR4841E

failed. An invalid object type detected.

(TOC) in the specified node and file space failed
because the object type given is different than the one
User response: Re-try the Table of Contents loading,
specifying a valid object type.
ANR4842E
The loading of a table of contents for

node node name failed. The file space
name was not found.

(TOC) loading for the specified node because the server
could not find the file space name for the TOC object to
be loaded.
System action: The TOC loading is ended and server
User response: The file space could be deleted during
the TOC loading operation. Issue QUERY FILESPACE
command to verify if the file space is deleted. Make
sure the correct file space name is specified. You can
issue a QUERY FILESPACE to ensure that the file space
exists. Re-issue the request with the correct file space
name.
500

failed. See previous messages.
ANR4843I ANR4850I
ANR4843I
Command: Displayed number of objects

objects, number of errors errors were
encountered.
Explanation: QUERY TOC has completed. The

number of objects displayed and the error count are
displayed.
System action: The QUERY TOC command ends and
User response: If the error count is not equal to 0,
examine the object name displayed. The error count
represents the number of objects that have their names
displayed as '...'. This is because the conversion from a
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
displayed in a hexadecimal format when the
FORMAT=DETAILED is specified. The file may contain
an invalid character and may need to be renamed. A
new backup copy has to be made for the renamed file
so that the file can be displayed correctly and restored
later.
ANR4846E
Operation process process ID terminated The server is unable to create a table of

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.
System action: The operation fails because TOC
creation is set to YES.
User response: Look for previous messages giving a
specific reason for the failure. Take corrective action as
appropriate.
ANR4847I
Audit command: Invalid nodeid nodeid

found during email address audit. The
email entry must be corrected.
Explanation: During Audit processing, a non-existent

nodeid was found associated with an email address.
the email address entry is not corrected.
ANR4844I
Command: The specified table of

file space name contains no entries.
Explanation: The specified table of contents (TOC)

exists, but it is empty. No entries are displayed.

ANR4848I

ANR4845E
The writing of the of the table of

file space name failed: a directory path
exceeds max characters bytes in length.
File: lowLevel name, NDMP Node ID:
node id hi .node id lo, NDMP Parent Node
ID:Parent id hi. Parent id lo.
Explanation: During a backup of a NAS filesystem,

the server received a file history record from the NAS
device with a directory path length which exceeded the
maximum length supported by ITSM. The server is
unable to create a TOC for a NAS filesystem which
contains directory that is longer than 1024 bytes. If the
TOC parameter on the BACKUP NODE command is
PREFERRED, the backup continues. If the TOC
parameter was YES, the backup fails.
System action: The TOC creation is ended and server
User response: If TOC=YES was specified on the
BACKUP NODE command, retry the command with
TOC=NO.
Audit command: An email address

associated with node node name is
invalid. The email entry must be
corrected.
Explanation: During Audit processing, an invalid

email address was found for the specified node.
ANR4849I
Audit command: Invalid nodeid nodeid

email entry will be corrected.

nodeid was found associated with an email address.
the email address entry is deleted.
ANR4850I

associated with node node name is
invalid. The email entry will be
corrected.

email address was found for the specified node.
501
ANR4851I ANR4858I
ANR4855I

ANR4851I
Audit command: Invalid adminid admin id

email entry must be corrected.

adminid was found associated with an email address.
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
Center.
ANR4856I

ANR4852I

associated with administrator
administrator is invalid. The email entry
must be corrected.

email address was found for the specified
administrator. Because FIX=NO has been specified for
the command, the email address entry is not corrected.
Command command subcommand is no

longer supported and there is no direct
replacement for this capability.

longer supported. The following
commands provide similar functions:
newcommand. See the Tivoli Storage
Manager Information Center for details
on commands, or issue HELP command
for the replacement commands.
Explanation: The functions formerly provided by this

command are now provided by one or more new
commands
Center.

ANR4857I
ANR4853I
Audit command: Invalid adminid adminid

email entry will be corrected.

adminid was found associated with an email address.

longer supported. The following options
provide similar functions: newoptions.
See the Tivoli Storage Manager
Information Center for details on the
options or issue the HELP command for
the replacement options.
Explanation: The functions formerly provided by this

command are now provided by one or more new
options
ANR4854I

associated with administrator
administrator is invalid. The email entry
will be corrected.

email address was found for the specified
administrator. Because FIX=YES has been specified for
the command, the email address entry is deleted.
502

Center.
ANR4858I
Option option name is no longer

supported and there is no direct
replacement for this capability.
Explanation: The funtions formerly provided by this

option are no longer necessary
Center.
ANR4859I ANR4865W
ANR4859I
Parameter parameter name on the

command command name is no longer
supported.
ANR4862W
Explanation: The function that was provided by this

parameter is no longer necessary
Center.
ANR4860W
The correct value of ARCHRETENTION

for domain domain name will not be sent
to the managed servers. Please upgrade
the managed servers to be at least the
same level as that of the configuration
manager.
Explanation: The configuration manager has an

ARCHRETENTION value that is greater than the
managed server can manage. This is because the
managed server is at a lower level than the
configuration manager. The value of the
ARCHRETENTION for the indicated domain is set to
the maximum value that the managed server can
process.
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
as that of the configuration manager.
ANR4861W
The correct value of RETVER for the

archive copy group domain name policy set
name mgmt class name cg name will not be
sent to the managed servers. Upgrade
the managed servers to at least the same
level as that of the configuration
manager.
Explanation: The configuration manager has a

RETVER value that is greater than what the managed
server can process. This is because the managed server
is at a lower level than the configuration manager. The
value of the RETVER for the indicated copy group is
set to NOLIMIT in the managed server.
User response: To correctly send the value of RETVER
for the copy group to the managed servers, please
upgrade the managed servers to at least the same level
as that of the configuration manager.
The value of the

ACTIVEDESTINATION parameter for
domain domain name will not be sent to
the managed server server name because
the release level of the managed server
is earlier than the release level of the
Explanation: The configuration manager has a value

for the ACTIVEDESTINATION parameter that contains
active-data storage pool names that cannot be managed
by the managed server. The problem is that the release
level of the managed server is earlier than release level
of the configuration manager.
User response: Upgrade the managed server to the
same release level or later than that of the configuration
manager.
ANR4863W
The value of the

ACTIVEDESTINATION parameter for
domain domain name that was received
from the configuration manager will not
be used on the managed server.
Explanation: The received value of the

ACTIVEDESTINATION parameter contains active-data
storage pool IDs that cannot be managed by the
managed server. The problem is that the release level of
the configuration manager is earlier than the release
level of the managed server.
User response: Upgrade the configuration manager to
the same release level or later than that of the managed
server.
ANR4864E
The module name support module was

not loaded.
Explanation: The indicated support module was not

loaded.
System action: The server cannot perform functions
that require this module.
User response: Restart the Tivoli Storage Manager
server and retry the operation. If the support module
does not load, contact your service representative.
ANR4865W
The server name has been changed.

Windows clients that use
"passwordaccess generate" may be
unable to authenticate with the server.
Explanation: After the name of a Tivoli Storage

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
503
ANR4866I ANR4875I
is stored in the Windows registry in a key that contains
the server name, such as the following:
HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\
BackupClient\Nodes\<NODENAME>
\<SERVERNAME>\Password If the backup-archive
client is not able to authenticate with the Tivoli Storage
Manager server then scheduled operations for that
client will not run.
System action: Until the password is reset, the
Windows backup-archive clients that use
"passwordaccess generate" are unable to authenticate
with the Tivoli Storage Manager server.
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
NODE command to a known password and then use
dsm, dsmc, or dsmcutil to manually set the password
on all Windows backup-archive clients that use
"passwordaccess generate".
ANR4866I
Node node name is not a member of a

domain that is configured to use active
data pool active data pool name.
Explanation: The primary storage pool to which the

client node will write data is capable of using an active
data pool. However the client node is not a member of
a domain that is authorized to write to the active data
pool.
System action: Data from the node is not written to
the active data pool.
User response: If the client node data must be written
to an active data pool, move the client node to a
domain that is authorized for this action or update the
current domain for active data pool processing.
ANR4870W

name, specified as a Table of Contents
(TOC) destination for copy group copy
group name in management class
management class name, policy set set
exist.

pool specified for the Table of Contents (TOC)
destination of the specified copy group that is not
defined in the server database. If this copy group is
used in an active policy set, then the NDMP backup
with a TOC creation operation may fail when
attempting to put TOC entries in the destination.
ANR4871I
Collocation group collocation group name

defined.
Explanation: A DEFINE COLLOCGROUP command

has created the collocation group indicated.
ANR4872E
Command: Invalid collocation group

name - collocation group name.

command fails because the collocation group name
collocation group name specified does not contain valid
characters or contains too many characters.
database.
a collocation group name that conforms to the name
length specifications for valid collocation group names,
refer to the Administrators Reference.
ANR4873E
Command: Collocation group description

exceeds maximum length of length limit
characters.

command fails because the collocation group description
characters allowed.
database.
a shorter collocation group description.
ANR4874I

updated.

COLLOCGROUP command, the collocation group
collocation group name has been updated in the server
database.

missing storage pool, or the UPDATE COPYGROUP
command to update the copy group to refer to an
existing storage pool.
504
ANR4875I

deleted.

COLLOCGROUP command, the collocation group
ANR4876W ANR4883I
collocation group name has been deleted from the server
database.
ANR4876W

processed because it is not registered.
Explanation: This command cannot be processed for

the indicated node. The node is not registered. The
other nodes can be processed if specified by the
command.
but other nodes can be processed if specified by this
command.
incorrectly, issue the command again with the correct
node name.
ANR4877E
Command: Collocation group collocation

group name is not defined.

collocation group name specified does not refer to a
defined collocation group in the server database.
database.
collocation group name that is defined in the server
database. For a list of the names of defined collocation
COLLOCGROUP command.
ANR4878I

defined in the collocation group
collocation group name.
Explanation: A DEFINE COLLOCMEMBER command

has created the specified number of members in the
indicated collocation group.
ANR4880I

collocation group collocation group name.

the DELETE COLLOCMEMBER command. Node node
name is no longer associated with the collocation group
name collocation group name.
ANR4881E

group name is already defined.

collocation group name specified refers to a collocation
group that is already defined in the server database.
database.
collocation group name that is not defined in the server
database. For a list of the names of defined collocation
COLLOCGROUP command.
ANR4882E

group name still contains at least one
node.

command command fails because the collocation group
collocation group name specified refers to a collocation
group that still contains at least one node. A collocation
group cannot be deleted if one or more client nodes are
still assigned to the collocation group.
database.
collocation group, issue the DELETE
COLLOCMEMBER command. After all nodes are
removed, issue the delete command again.

ANR4883I
ANR4879I

deleted from collocation group collocation
group name.
Explanation: A DELETE COLLOCMEMBER command

has deleted the specified number of members from the
indicated collocation group.
Node node name associated to collocation

group collocation group name.

the DEFINE COLLOCMEMBER command. Node node
name is associated with the collocation group name
collocation group name.

505
ANR4884W ANR4892I
ANR4884W
Node node name already associated to

collocation group collocation group name.

the DEFINE COLLOCMEMBER command. Node node
name is already associated with the collocation group
name collocation group name. The indicated node is not
processed. The other nodes can be processed if
specified by the command.
attribute used to track collocation group identifiers are

incorrect.
ANR4889E

incorrectly, issue the command again with the correct
node name.
ANR4885E
Command: Either node name or

collocation group name must be
specified.

neither node name nor collocation group name is
specified or the node name and the collocation group
name both are specified.

attributes used to track collocation group identifiers are
incorrect. Because FIX=YES has been specified for the
audit command, the attributes will be corrected.
ANR4890I
System action: The indicated command fails. The

User response: Issue the command again, by
specifying either the node name or the collocation
group name.
ANR4886E

collocation group id has been detected
for node node id.

or incorrect collocation group identifier for the specified
node member.

ANR4891I

collocation group id has been detected
for node node id - it will be corrected.

or incorrect collocation group identifier for the specified
node member. Because FIX=YES has been specified for
the audit command, the error will be corrected.

ANR4892I

Audit command: Collocation group global
high-water mark does not match the
identifier in use.
506
Audit command: Inventory name reverse

lookup object (name.ID) belonging to
node NodeId and filespace FilespaceId has
a missing database element. It will be
corrected if FIX=YES was specified for
the DSMSERV AUDITDB command.

inventory name object that is incomplete. If FIX=YES
has been specified for the command, the inventory
ANR4888E
Audit command: Inventory name object

(name.ID) belonging to node NodeId and
filespace FilespaceId has a missing
database element. It will be corrected if
FIX=YES was specified for the
DSMSERV AUDITDB command.

inventory name object that is incomplete. If FIX=YES
has been specified for the command, the inventory
ANR4887E
Audit command: Collocation group global

high-water mark does not match the
identifiers in use; it will be corrected.
Audit command: Inventory name object

(name.ID) belonging to node NodeId and
filespace FilespaceId has a missing parent
element. If FIX=YES was specified for
the DSMSERV AUDITDB command,
the name entry will be related to the
root directory for the file space.

inventory name object that has no parent entry. To
ensure that the object is restorable, the entry will be
ANR4893I ANR4912I
linked to the root directory for the file space if FIX=YES
was specified for the DSMSERV AUDITDB command.
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
with the correct path name.
command to delete the volume, then backup the

primary storage pool again.
To see what files may have been marked as damaged,
use the QUERY CONTENT DAMAGED=YES
command.
ANR4896I

ANR4893I
Audit command: An inventory backup

object corresponding to name ID nameId
belonging to node NodeId and filespace
FilespaceId has a missing name. If
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.

inventory backup object that has no name entry. To
ensure that the object is restorable, the entry will be
linked to the root directory for the file space if FIX=YES
was specified for the DSMSERV AUDITDB command.
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
with the correct path name.
ANR4894I
Explanation: The server is in the process of restarting

a previously cancelled expiration process.
System action: The server will continue expiring
eligible objects.
ANR4897I
Database restore of operation operation

ID will use device class device class name
and attempt to use number of streams
streams.
Explanation: The server restore database process for

the operation ID will be performed for the device class
and number of streams indicated.
System action: The server performs the database
restore operation.
ANR4911E

names.

about client backup object names is currently being
Inventory client file expiration is

restarting process process num from
startdate.
File name is too long, the server is

unable to build a table of contents for
node node name, file space file space name,
file name file name, node identifier node
id, parent node identifier parent node id.
Table of contents creation fails.
Explanation: The file name must be 512 bytes or less.

If the size is larger than 512 bytes, the Tivoli Storage
Manager server cannot create a table of contents (TOC)
for a Network Appliance file server.
System action: The TOC creation fails.
ANR4895E
Deduplicated bitfile bitfile id on volume

volname has invalid links.
Explanation: While reading a deduplicated bitfile, the

server detected invalid deduplication information.
System action: If the operation is a server data
movement, the inconsistent bitfile is marked invalid
and skipped, but the operation continues. If, however,
the operation is a client restore or retrieve, the bitfile is
marked as damaged.
User response: If the volume is in a primary storage
pool, run a RESTORE VOLUME command to fix the
invalid bitfile. If the volume is in a copy storage pool,
run a DELETE VOLUME DISCARDDATA=YES
User response: Rename the file with a shorter name.

For more information about the file name or the node
identifier, including locating and correcting the file or
directory, refer to Network Appliance documentation.
Once the problem has been corrected, try the operation
again.
ANR4912I
Database restore type byte count.
Explanation: A database restore is in progress.

507
ANR4913I ANR4921E
ANR4913I
Database restore completed for restore

to date date time. No backup volume
found.
ANR4918W
Explanation: A point-in-time database restore has been

completed without finding any backup volumes.
ANR4914I
Point-in-time database restore

completed, no backup volume found for
restore date date time.

TODATE parameter specified has completed without
finding any backup volumes.
Explanation: Data from the filespace will not be

included in the backupset because the filespace was not
created by the backup/archive client and it cannot be
restored from the backupset.
ANR4919W

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
finding any snapshot volumes.

snapshot to date date time.

TODATE parameter and source snapshot specified has
begun. When this restore is complete, the database will
be committed to the point in time of this backup.
ANR4917I
Point-in-time database restore with

snapshot complete, restore date date time.

TODATE parameter specified has completed. The
database is committed to the point in time of this
backup, which may be different than the TODATE
specified. If this is the case, an additional message will
be displayed.
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 is not a
supported application type.

included in the backupset because the filespace does
not belong to a supported application type.
ANR4920E

ANR4916I

in the backupset backupset name (data
type data type) because it was not created
by the backup/archive client and cannot
be restored from the backupset.

command for storage pool pool name.

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
migrated or reclaimed.
command.
ANR4921E
Command: Primary storage pool pool name

does not have a target pool.
Explanation: The specified primary storage pool does

not have a target storage pool for the specified
operation.
command.
User response: Define a target storage pool for the
pool specified on the command and re-issue the
command.
508
ANR4922E ANR4931I
ANR4922E
Command: Migration is currently

running for the storage pool pool name.
Explanation: The migration operation is already

running for the specified storage pool.
command.
User response: Re-issue the command when migration
is not running.
ANR4927W

volume, the duration for the reclamation has been
exceeded.
System action: The volume reclamation is terminated.
ANR4928E
ANR4923E
Command: Reclamation is currently

running for the storage pool pool name.
Reclamation terminated for volume

volume name - duration exceeded.
Command: Reclamation is not allowed

for the storage pool pool name.
Explanation: The reclamation operation is already

running for the specified storage pool.
Explanation: The high reclamation threshold

(percentage) is set to 100 to prevent reclamation for the

command.

command.
User response: Re-issue the command when

reclamation is not running.

is needed for the pool.
ANR4924I
Command: Migration is not needed for

the storage pool pool name.
Explanation: Either the current percentage utilization

of the specified storage pool is less than the low
migration threshold or the number of volumes
containing data has not reached the low migration
threshold.
command.
ANR4929E
Explanation: The specified storage pool is not a

sequential-access storage media for the specified
operation. The specified operation only applies to a
sequential-access storage media.
command.
User response: Re-issue the command for a
sequential-access storage media.
ANR4930I
ANR4925W

for storage pool storage pool name duration exceeded.

storage pool, a process performing the migration has
been terminated because the migration duration has
exceeded.
System action: The migration process is terminated.
ANR4926W
Migration terminated for volume volume

name - duration exceeded.

volume, the duration for the migration has been
exceeded.
System action: The volume migration is terminated.
Command: The storage pool pool name is

not a sequential-access pool.
Reclamation process process ID started

for primary storage pool storage pool
name automatically or manually,
threshold=threshold value,
duration=duration.
Explanation: Because the high reclamation threshold

for the storage pool shown has been exceeded, a
process has been started to reclaim files from the
storage pool. Note: a duration value of None means
that the duration is not specified and hence the
reclamation runs without duration.
to the same pool or to the reclaim storage pool.
ANR4931I
Reclamation process process ID started

for copy storage pool storage pool name
automatically or manually,
threshold=threshold value,
offsiteRclmLimit=limit value,
duration=duration.
Explanation: Because the high reclamation threshold

509
ANR4932I ANR4939E
for the storage pool shown has been exceeded, a
process has been started to reclaim files from the
storage pool. Note: a duration value of None means
that the duration is not specified and hence the
reclamation runs without duration.
to the same pool or to the reclaim storage pool.
ANR4936I
Reclamation of storage pool pool name

has ended. Files reclaimed: number of
files, Bytes reclaimed: number of bytes,
Files reconstructed: number of
reconstructed files, Unreadable files:
number of unreadable files.
Explanation: Reclamation processing for the specified

ANR4932I
Reclamation process process ID ended for

Explanation: A reclamation process for the named

storage pool ends. This action can occur because the
threshold for the storage pool has been reached or
because the duration has been exceeded.
ANR4933I
Space reclamation ended for offsite

volume volume name.
Explanation: Space reclamation for the named offsite

volume is complete.

determine whether all reclamation processes ended
successfully.
ANR4937E
Command: Reclamation will not run delete filespace is currently running.
Explanation: A delete filespace operation is running.

To Avoid the resource contention, reclamation will not
run when delete filespace is running.
command.
User response: Re-issue the command when delete
filespace is not running.

ANR4934I
Offsite reclamation ended for storage

pool pool name, Number Processes
number of processes, Number Volumes
Reclaimed number of volume reclaimed,
Elapsed Time seconds seconds.
Explanation: Offsite reclamation ended successfully.

ANR4935I
Migration of primary storage pool

primary pool name has ended. Files
migrated: number of files, Bytes migrated:
number of bytes, Unreadable Files: number
of unreadable files.
Explanation: Migration processing for the specified

determine whether all migration processes ended
successfully.
510
ANR4938E

command for target storage pool pool
name.

command for the indicated pool. The indicated pool is
the pool that to which files are migrated or reclaimed.
command.
ANR4939E

valid for a DISK storage pool.

option that is not valid for a DISK storage pool.
command.
appropriate for a DISK storage pool.
ANR4940E ANR4946W
ANR4940E
Reclamation is ended for storage pool

storage pool name. There is an insufficient
removable media.
ANR4942E

defined. The file name does not exist or
has no space.

storage pool the server could not allocate sufficient
mount points in the storage pool.
Explanation: A define volume command was issued

for the indicated volume name. The volume name was
specified without the FORMATSIZE parameter, but it
either does not exist or exists as a file of size 0.
System action: Reclamation stops.
System action: The volume definition fails.

available.
User response: Use the FORMATSIZE parameter to

have the server pre-allocate space for the new volume.
ANR4941E
ANR4943E
The server is unable to translate the

Unicode name while building table of
file space name, Unicode name unicode
name node identifier node id, parent node
identifier parent node id. Table of
contents creation fails.
Explanation: While creating a table of contents (TOC)

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
failed.
Command: Volumes cannot be deleted

from
RECLAMATIONTYPE=SNAPLOCK
storage pools.
Explanation: Deleting volumes from

RECLAMATIONTYPE=SNAPLOCK storage pools is
not allowed. Rather, deletion of empty volumes occurs
automatically during reclamation processing.
User response: Allow deletion of empty volumes to
be done automatically during reclamation processing.

User response: Verify that the required support for
translations between UCS-2 and UTF-8 is properly
installed and configured on the system where the Tivoli
Storage Manager is running.
Verify that the reported Unicode name is valid. Note
that the Unicode name is encoded in little-endian
UCS-2 and is reported in hexadecimal notation. If the
Unicode name is not valid, the problem may usually be
corrected by deleting or renaming the corresponding
file or directory on the Network Appliance file server.
The node identifier and parent node identifier are
provided by the Network Appliance NDMP server.
Their values are NDMP-server implementation
dependent but will typically be the inode number of
the file or directory. For more information about the
Unicode name or the node identifiers, including using
them to locate and correct the invalid file or directory,
contact Network Appliance for support.
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
:cit.ADSM Administrators Guide:ecit. for your
Once the problem has been corrected, try the operation
again.
ANR4944E
Command: Volumes cannot be defined in

RECLAMATIONTYPE=SNAPLOCK
storage pools.
Explanation: Defining volumes on

RECLAMATIONTYPE=SNAPLOCK storage pools is
not allowed. Rather, the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands is
used to make storage pool space available for these
storage pools.
User response: Use the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands to
create space in the storage pool.
ANR4945E
Command:The volume named volume

name is larger than is allowed for a
volume on your system.
Explanation: While attempting to define a volume on

volume name the server detected that the volume size
exceeds the maximum allowed.
User response: Consider defining 2 smaller volumes.
ANR4946W
The character encoding of NDMP file

history messages for node node name, file
system file system name is unknown. The
Tivoli Storage Manager server will use
the UTF-8 encoding to build a table of
contents.
511
ANR4947E ANR4952E
Explanation: While initializing a backup with a table
of contents (TOC) for the specified node and file
system, the TSM server determines that the character
encoding of file history information from the NAS file
server is unknown. The Tivoli Storage Manager server
will assume file history information is encoded as
UTF-8 in order to build a TOC.
If the character encoding is not UTF-8 and non-English
characters are present, the names will be improperly
displayed and probably unreadable, making recovery
difficult.
User response: Ensure that sufficient temporary space

is available in the server's database. To increase the
amount of database space available to the server, an
authorized administrator can add database volumes by
using the DEFINE DBVOLUME command, and extend
the size of the database by using the EXTEND DB
command.
ANR4950E

User response: Verify that the encoding of file history
information is UTF-8. For Network Appliance NAS file
servers, verify that the volume language for the
specified node and file space is UTF-8, or a subset of
UTF-8 (for example 7-bit ASCII).
ANR4947E
The server is unable to translate the

Unicode path name while building table
of contents for node node name, file
space file space name. Table of contents
creation fails.
Explanation: While creating a table of contents (TOC),

the server attempted to translate the Unicode path
name in the file history message from UCS-2 to UTF-8.
The translation failed.
User response: Verify that the required support for
translations between UCS-2 and UTF-8 is properly
installed and configured on the system where the Tivoli
Storage Manager is running. Try the operation again.
ANR4948E
The list file named list file name contains

more than max entry count entries.
Explanation: While reading a list file, the server

detects that the number of entries exceeds the
maximum allowed.
User response: Consider breaking up the operation
into multiple commands, each handling a subset of the
required entries.
ANR4949E
The server is unable to write to table

table name because there is not enough
temporary space in the database. Table
of contents operation for node node
name, file space file space name fails.
Explanation: While operating on a table of contents

(TOC), the server attempted to insert data into the
specified temporary database table, but there is not
enough temporary space in the servers database.
System action: The TOC operation fails.
512
The server is unable to retrieve NDMP

file history information while building
table of contents for node node name, file
space file space name. NDMP node ID is
NDMP node ID. Table of contents
creation fails.
Explanation: While creating a table of contents (TOC),

the server attempted to retrieve information contained
in a previous NDMP file history message. The
information was not found. This could be caused by a
problem with the NAS file server that is sending file
history messages. The NDMP node ID reported in the
message is the node ID referenced in the current
NDMP file history message.
User response: Verify that the NDMP server is
properly sending file history information. Otherwise,
ANR4951E
The writing of a table of contents for

failed. The object is excluded from
storage pool pool name and all successor
pools because of its size.

(TOC) creation for the specified node. The size of the
TOC is larger than that allowed in the storage pool
specified by the TOC destination attribute of the
assigned management class backup copy group. No
successor storage pools to the one specified on the copy
group can accept the large TOC.
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
can increase the MAXSIZE parameter by issuing the
UPDATE STGPOOL command.
ANR4952E

failed. No space is available in storage
pool pool name and all successor pools.

(TOC) creation for the specified node. The storage pool
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.
ANR4953E ANR4958E
No successor storage pools to the one specified on the
copy group contain enough free space.
or more storage pools in the storage hierarchy. This
action may also involve creating storage space by using
an operating system-specific utility.
ANR4953E

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.
preceding this one that specify the failing device.
the VARY command), or the server may need to be
halted to correct the hardware problem. After the
problem is corrected, try the operation again.
ANR4954E

failed. The data transfer was
interrupted.

make them available for TOC storage.
ANR4956E

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

(TOC) creation for the specified node because sufficient
volumes are used.
ANR4957E

sufficient database space.


(TOC) creation for the specified node because data
external event.

for use by the database. Also,an administrator can issue
the EXTEND DB command to extend the size of the
database so that the new volumes are used.

ANR4958E

interrupted. Attempt the operation again if the problem
can be resolved.
ANR4955E

failed. The storage media is not
available.

(TOC) creation for the specified node because storage
volumes are not available in the storage pools in which
the TOC is to be stored.

failed. The server is unable to start a
new thread.

application.

513
ANR4959E ANR4966E
ANR4959E

sufficient memory.

application.
ANR4960E

failed. The server detected an internal
error.

(TOC) creation for the specified node because an
internal logic error is detected.
representative.
ANR4961E

failed. The server could not commit the
transaction.

failed transaction.
System action: The table of contents (TOC) creation is
ANR4962E

sufficient mount points available to
satisfy the request.

sufficient mount points to write the table of contents
(TOC).

available.
ANR4963E

failed. See previous messages.

(TOC) creation for the specified node because a
previous error has occurred.
representative.
ANR4964I
Space reclamation deleted number of

volumes WORM FILE volumes for

storage pool, the server deleted the indicated number
of empty WORM FILE volumes that have exceeded
their retention date.
System action: Reclamation and server operations
continue.
ANR4965E
operation is ended for storage pool storage

pool name. Sufficient database space is
not available.
Explanation: Insufficient server database space has

been encountered during the indicated operation for
the indicated storage pool.
System action: Either the Migration or Reclamation
stops, or the operation specified in the message stops.
DEFINE DBVOLUME command and can extend the
size of the database using the EXTEND DB command.
ANR4966E
operation is ended for storage pool storage

pool name; sufficient recovery log space
is not available.
Explanation: Insufficient server recovery log space has

been encountered during the indicated operation for
the indicated storage pool.
System action: Either the Migration or Reclamation
514
ANR4967W ANR4972I
stops, or the operation specified in the message stops.
User response: To increase the amount of recovery log
administrator can add log volumes using the DEFINE
LOGVOLUME command and can extend the size of the
log volumes using the EXTEND LOG command.
ANR4967W
Expired WORM FILE volume volume

name still contains valid data; data will
not be protected.
Explanation: During space reclamation, the server

detected the retention of the indicated WORM FILE
volume has expired but the volume still contains valid
data. The data on the volume will not be protected.
System action: Reclamation continues.
ANR4970E
Reclamation failed on WORM FILE

volume volume name.
Explanation: During space reclamation, server failed

to move the files from the indicated WORM FILE
volume. The files on the volume might not be protected
if the reclamation period is exceeded.
System action: Reclamation continues on other
volumes.
User response: Examine the server activity logs to
find out why the reclamation does not move the valid
data to another WORM FILE volume for protection. To
determine when the reclamation period is expired,
issue a QUERY VOLUME command for the indicated
volume.
Explanation: The indicated audit process finds a

WORM FILE storage volume for which the reclamation
retention date is missing or incorrect. To fix the missing
or incorrect date, issue the AUDIT VOLUME with
FIX=YES command for the indicated volume. During
AUDIT VOLUME processing, the server will indeed
have interface to the Network Appliance filer to obtain
the retention date of the SnapLock Log Volume for
correction of the missing or incorrect date.

with FIX=YES, so that the reclamation retention date
can be created or corrected.
ANR4971E
Conversion from the server code page to

UTF-8 fails. Verify the installation of the
UTF-8 code page and tools for your
operating system.
Explanation: Converting the command results from

the server's code page to UTF-8 fails. Problems with
operating system conversion tool or missing code page
conversion tool might cause this problem. The server
will attempt to recover from the situation. However, the
recovery might result in unreadable characters or no
output to appear on the web interface or interfaces that
use the administrative API. Consult the language
support information of the operating system for
information on how to install UTF-8 code page,
conversion tool support, and ICONV support.
System action: The server operation continues without
converting the command output from the server's code
page to UTF-8.

reclamation retention date for WORM
FILE volume volume name. The
reclamation retention date will be
created or corrected.
Explanation: The indicated audit process finds a

WORM FILE storage volume for which the reclamation
retention date is missing or incorrect. Since FIX=YES
has been specified for the audit command, the date will
be created or corrected.
ANR4972I
ANR4969W

reclamation retention date for WORM
FILE volume volume name; run AUDIT
VOLUME FIX=YES for correction.
User response: Examine the server activity logs to

find out why the reclamation does not move the valid
data to another WORM FILE volume for protection.
ANR4968W
installing the UTF-8 locale for your language.
Command: Migration is not needed for

the storage pool pool name.
Explanation: Migration is not needed for the specified

storage pool because of one of the following reasons:
v The high migration threshold (percentage) is set to
100 to prevent migration.
v If the specified storage pool uses random-access disk
or sequential-access disk, the data capacity utilization
is less than the low migration threshold.
v If the specified storage pool uses tape or optical
media, the ratio of volumes that contain data to the
total number of volumes in the storage pool is less
than the low migration threshold.
command.
User response: Install the UTF-8 code page support on

the operating system. This is normally available by
515
ANR4973I ANR4981E
ANR4973I
Command: Reclamation is not allowed

for the storage pool pool name.
ANR4977W
Explanation: The high reclamation threshold

(percentage) is set to 100 to prevent reclamation for the
command.
ANR4974W

was cancelled.

included in the backupset because the filespace was not
created by the backup/archive client and it cannot be
restored from the backupset.
ANR4978W

(TOC) creation for the specified node because the
process was cancelled.
ANR4975E
No Tcp port available for backup from

NAS node to server.
Explanation: The server was unable to set up a

TCP/IP port for use in backing up or restoring from or
to NAS nodes and the server. The server uses a range
of ports as defined by the NDMPPORTRANGE option.
If none of these ports can be set up for use, backups or
restores from or to NAS nodes and server native
storage pools will fail. If the NDMPPORTRANGE
option is not specified, the server uses ephemeral ports
( ports that the operating system assigns from a
dynamic pool ). If the system runs out of usable ports,
operations to or from NAS nodes and server native
storage pools will fail.
System action: The specific operation is ended and
User response: Operating specific utilities, e.g. netstat,
may be used to examine ports which are in use. It may
be necessary to specify the NDMPPORTRANGE option
( which requires a server restart ), to provide a
sufficient number of ports.

in the backupset because it was not
created by the backup/archive client and
cannot be restored from the backupset.

in the backupset because it is not a
supported application type.

included in the backupset because the filespace does
not belong to a supported application type.
ANR4979W
Use of environment variable

DSMSERV_DIR is no longer supported.
Explanation: The DSMSERV_DIR environment

variable was required in prior versions of TSM to find
loadable modules and language files. Now, however,
the directory is determined automatically and this
variable is ignored.
System action: Server operation continues, using the
directory containing the server executable as the base
server directory.
ANR4980I
Auditing Interface Driver definitions.
Explanation: The server is beginning an audit of the

definitions for Web interface.
System action: The server will audit all definitions for
the Web interface and report any problems.
ANR4976W
The device class DevClassName is not the

same as device class DevClassName
defined for the serverbackup node
$$_TSMDBMGR_$$.
Explanation: The device class in this command is not

the same as the device class defined in the server
backup node.
System action: The server will still process the
command.
User response:
516
ANR4981E
Interface Driver audit completed Inconsistencies were found.
Explanation: The server found errors during the audit

of the definitions for Web interface.
System action: The Web Interface is not correctly
installed. The Web Admin will not work correctly, but
the server may be run without any problems.
User response: Ensure you are using the correct IDL
file for the server level you are running. Examine error
ANR4982I ANR4992I
messages that may have been displayed before and/or
after this message and correct any problems, if possible.
If the cause of this can not be determined or resolved,
contact your support representative.
ANR4982I
Interface Driver audit completed definitions are consistent.
Explanation: The server successfully completed the

installation of the definitions for the Web interface.
ANR4987E
Audit processing failed: sufficient

memory is not available for processing.
Explanation: At RUNFILE time, the server is unable

to process the IDL data due to insufficient memory.
System action: Server runfile stops.
User response: Restart the server runfile process with
more memory available.
System action: The Web Interface is now installed.

The server may be run without any problems.
ANR4988I
Explanation: The server is auditing the driver class

containers.
ANR4983I
System action: The server will audit the driver class

containers and proceed to the next step.
Auditing Interface Driver Groups.
Explanation: The server is auditing the driver groups.

System action: The server will audit the driver groups
and proceed to the next step.
ANR4984E

ANR4989I
Auditing Interface Driver Complex

Class containers.
Auditing Interface Driver Operations.
Explanation: The server is auditing the driver

operations.
Error description
Explanation: The server found errors during the audit

of the definitions for Web interface.
System action: The server will audit the driver

operations and proceed to the next step.
System action: The audit will fail.

User response: Ensure you are using the correct IDL
file for the server level you are running. Examine error
messages that may have been displayed before this
message and correct any problems, if possible. If the
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
should be reported.
ANR4990I
Auditing Interface Driver Operation

Parameters.
Explanation: The server is auditing the driver

operation parameters.
System action: The server will audit the driver
operation parameters and proceed to the next step.
ANR4985I
Auditing Interface Driver Group

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.
ANR4991I
Auditing Interface Driver Tasks.
Explanation: The server is auditing the driver tasks.

System action: The server will audit the driver tasks

ANR4992I
ANR4986I
Auditing Interface Driver Classes.
Explanation: The server is auditing the driver classes.

System action: The server will audit the driver classes
Auditing Interface Driver Task

Members.
Explanation: The server is auditing the driver task

members.
System action: The server will audit the driver task
members and proceed to the next step.
517
ANR4993E ANR6206I
ANR4993E
The client platform platform name is

currently not supported by the TSM
Storage Agent.
Explanation: At this point in time the storage agent

does not accept the incomming client platform.
ANR4994E
Query whether the volume volume name

is in the library library name failed.
Explanation: An attempt to query if the indicated

volume is in the specified library failed. It could be the
library is offline or the library manager is down in a
library sharing environment.
System action: The requested operation failed.
ANR6203I
Explanation: A compression audit is starting to check

qualifying candidates from the candidates list for the
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
command.
System action: The audit operation continues.
User response: The compression candidate list can be
displayed with the QUERY COMPRESSION command.
The QUERY PROCESS command can be used to
monitor the progress of the audit operation.
ANR6204I
User response: Re-attempt the request when the

library is brought up or when the library manager is
up and running in a library sharing environment.
ANR6200I
Command name: Level compression audit

level compression audit started as
process process ID.
Command name: Starting level audit level

compression audit from qualifying
entries in the candidates list.
Command name: Process process ID, level

audit level audit, ended successfully compression suspects = total number of
compression suspects.
Explanation: A compression audit ended and is

reporting the total number of suspect client files that
have been found.
System action: The audit operation completes.
Explanation: A compression audit at the specified

level has been started as a background server process
with the process identifier reported.


background audit attempts to identify client files that
may be affected by the client compression problem.
ANR6205I

ANR6201I
Command name: Level compression audit

level compression audit starting as
background process process ID.
Explanation: A compression audit at the specified

level was started as a background server process
having the process identifier reported.
background audit attempts to identify client files that
may be affected by the client compression problem.
Command name: Process process ID,

continuing Level 1 compression audit
with object object ID high order
number.object ID low order number.
Explanation: A level 1 compression audit is starting to

evaluate client files for signs that they may be affected
by the client compression problem. Since a previous
level 1 audit has been executed, this audit will continue
where the last audit stopped starting with the object
whose identifier is specified.

ANR6206I
ANR6202I
Command name: Verifying candidates

from last audit.
Explanation: A compression audit has started to verify

the client file candidates that were identified in a
previous compression audit execution. The verification
process eliminates compression candidates that are now
found to be expired by policy on the server.
518

starting base level 1 compression audit.
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
with the first client file found on the server, even if
previous level 1 audits have been executed.
System action: The audit operation continues
ANR6207I ANR6213I
ANR6207I

audit level analysis detected candidate
file high-level object name low-level object
name in file space client filespace name for
node client node name.
Explanation: A compression audit has found a

candidate file at the audit level specified. The name of
the client node, file space, and file are displayed. This
message is issued whenever a candidate file is detected
during a compression audit that was started with the
VERBOSE=YES parameter specified.
ANR6208I
Command name: Process process ID, was

cancelled - number of candidate files
candidate files were found in number of
files examined files examined prior to
cancellation.
Explanation: A compression audit operation was

canceled with the CANCEL PROCESS command before
completion. The number of candidate files that were
found prior to the cancellation are displayed.
System action: The audit operation ends.
User response: The compression audit may be
restarted with the AUDIT COMPRESSION command.
The compression candidate list can be displayed with
the QUERY COMPRESSION command.
ANR6209I

audit level audit completed successfully number of candidate files candidate files
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.
ANR6210I

audit level audit completed successfully number of candidate files candidate files
were found.

that have been found are displayed.

ANR6211I

audit level analysis detected candidate
file object name in file space client filespace
name for node client node name.
Explanation: A compression audit has found a

candidate file at the audit level specified. The name of
the client node, file space, and file are displayed. This
message is issued whenever a candidate file is detected
during a compression audit that was started with the
ANR6212I

audit level analysis eliminated level
candidate level candidate file object name
in filespace client filespace name for node
client node name from candidate status.
Explanation: A compression audit at the level

specified has eliminated a candidate file through
further analysis. The name of the client node, file space,
and file are displayed. This message is issued whenever
a candidate file is eliminated from consideration during
a compression audit that was started with the
ANR6213I
Command name: Process process ID, was

cancelled - number of files promoted
candidate files were promoted as
candidates at level audit level, number of
files eliminated files were eliminated as
candidates, and number of files expired
candidates were eliminated because they
were found to be expired on the server.
Explanation: A compression audit operation was

cancelled with the CANCEL PROCESS command
before completion. The number of candidate files that
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
reported.
519
ANR6214I ANR6225I
User response: The compression audit can be restarted
with the AUDIT COMPRESSION command. The
compression candidate list can be displayed with the
QUERY COMPRESSION command.
ANR6214I

completed successfully - number of files
promoted candidate files were promoted
as candidates at level audit level, number
of files eliminated files were eliminated as
candidates, and number of files expired
candidates were eliminated because they
were found to be expired on the server.

that were promoted as candidates at this level of audit,
found to be expired are reported.
ANR6221I
Force backup operation started as

process process ID.
Explanation: A force backup operation was started as

a background server process with the indicated
identifier.
ANR6222I
Command name: Process process ID was

cancelled - number of files files were
processed prior to cancellation.
Explanation: The indicated process was cancelled

prior to completion. This message displays the
indicated number of files that were processed before
the operation was cancelled.
System action: The process ends.
User response: The operation may be restarted by

reissuing the indicated command.

ANR6223I
ANR6215I
Command name: Backup for file high-level

object name low-level object name in
filespace client filespace name for node
client node name could not be forced.
Delete compression process process ID

has completed - number of files files were
deleted.
Explanation: The indicated process has completed

processing. All database references have been deleted
for the indicated number of files.
Explanation: It is not possible to force a backup for

the specified file using the FORCE BACKUP command.
This file was either backed up using an API client or by
an ADSM version 2 client or higher.
System action: The force backup operation continues,

the state of the compression record for this file is
updated.
ANR6224I
User response: If the file was backed up using a

Version 2 client, or higher, you may remove this entry
as a candidate, using the REMOVE COMPRESSION
command. If the file was backed up using an API
client, notify the client owner to again back this file up.
Do not remove this entry until it becomes an "inactive"
entry.
Explanation: The indicated process has completed

processing. The indicated number of files have been
marked for forced backup. These files will be backed
up during the next incremental backup.
ANR6220I
ANR6225I
Delete compression operation started as

process process ID.

Force backup process process ID has
completed - number of files files were
marked for forced backup.

File identifier removed as a suspect for
compression errors.
Explanation: The file with the specified identifier has

been removed from the database information
concerning files with possible compression errors.
Other database information concerning the file is not
affected.
Explanation: A compression deletion operation was

started as a background server process with the
indicated identifier.
520
ANR6226I ANR6303E
ANR6226I
Command name: Started as background

process process ID.
Explanation: A compression cleanup operation has

been started to remove compression candidate
information and temporary database entries from the
server database. Client files are not affected by this
operation.
machine size, paging space available on the system, or

relocating the memory swap file, depending upon the
platform on which the server is executing. Additional
memory may also be made available by limiting server
activity (sessions, migration, and other activities) while
this operation is processing.
ANR6301E

User response: The CANCEL PROCESS command can
be used to cancel the compression cleanup operation.
The QUERY PROCESS command may be used to query
the status of the operation.
ANR6227I
cleanup process name operation starting as

process process ID.

been started to remove compression candidate
information and temporary database entries from the
server database. Client files are not affected by this
operation.
User response: The CANCEL PROCESS command can
be used to cancel the compression cleanup operation.
The QUERY PROCESS command may be used to query
the status of the operation.
ANR6228W
Cleanup process name: Process process ID

has been cancelled - cleanup processing
is incomplete.

been cancelled prior to successful completion.
Command name: Invalid LEVEL specified.

This command only supports a value of
1 or 2 for the LEVEL parameter.
Explanation: An invalid LEVEL= parameter has been

specified for the command.
value of 1 or 2 for the LEVEL parameter.
ANR6302E
Command name: Process process ID, failed

- number of candidate files candidate files
were found in number of files examined
files examined prior to failure.
Explanation: A compression audit operation failed

were found prior to the failure are displayed.
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
be corrected, re-execute the compression audit. If the
failure cannot be determined or corrected, contact your
service representative. The compression candidate list
can be displayed with the QUERY COMPRESSION
command.

User response: The CLEANUP COMPRESSION
command can be used to restart the cleanup operation.
ANR6229I


successfully completed.
System action: The cleanup process ends.
ANR6300E
Command name: Insufficient server

memory available for the operation.
Explanation: A compression testing routine cannot

continue because sufficient memory is not available on
the server.
User response: Increase the memory available to the
server by increasing the server region size, virtual
ANR6303E
Command name: Process process ID, failed

- number of files promoted candidate files
were promoted as candidates at level
audit level, number of files eliminated files
were eliminated as candidates, and
number of files expired candidates were
eliminated because they were found to
be expired on the server.
Explanation: A compression audit operation failed

were promoted as candidates at this level of audit,
found to be expired before the audit failure are
reported.
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
be corrected, re-execute the compression audit. If the
failure cannot be determined or corrected, contact your
service representative. The compression candidate list
521
ANR6304E ANR6606E
can be displayed with the QUERY COMPRESSION
command.
ANR6304E
Command name: Command cannot be

processed until compression audit is
performed.
Explanation: The indicated command cannot be

processed until a compression audit is performed using
the AUDIT COMPRESSION command.

command.
a valid description.
ANR6602E
Command: Recovery instructions file

name exceeds maximum length characters.
Explanation: The recovery instructions file name

specified in the command exceeds the maximum length
of allowable characters.
User response: Issue the AUDIT COMPRESSION

command and then repeat the attempted operation.

command.
ANR6305E
Command name: File identifier is not a

suspect for compression errors.
Explanation: The file with the specified identifier is

not listed in the database as a suspect for compression
errors. The file cannot be removed from the suspect list.
User response: Use the QUERY COMPRESSION
command to obtain the correct identifier for the file to
be removed.
ANR6306E

failed due to server error - cleanup
processing is incomplete.

failed before successful completion.
System action: The cleanup process ends.
User response: Examine messages that appear on the
server console or in the server activity log prior to this
message to determine the cause of the error. If the error
can be identified and corrected, restart the cleanup
operation with the CLEANUP COMPRESSION
command. If the error cannot be corrected, contact your
ANR6600E
Command: Invalid machine name machine name.
Explanation: The machine name specified in the

command is invalid.
command.
a valid machine name.
ANR6601E
Command: Description information

exceeds maximum length characters.
Explanation: The description specified in the

command exceeds the maximum length of allowable
characters.
522

a valid recovery instructions file name.
ANR6603E
Command: Characteristics file name

Explanation: The characteristics file name specified in

the command exceeds the maximum length of
allowable characters.
command.
a valid characteristics file name.
ANR6604E
Command: Invalid building identifier building.
Explanation: The building identifier specified in the

command is invalid.
command.
a valid building identifier.
ANR6605E
Command: Invalid floor identifier - floor.
Explanation: The floor identifier specified in the

command is invalid.
command.
a valid floor identifier.
ANR6606E
Command: Invalid room identifier - room.
Explanation: The room identifier specified in the

command is invalid.
command.
a valid room identifier.
ANR6607E ANR6617W
ANR6607E
Command: Machine machine name is

already defined.
Explanation: The machine specified in the command

is already defined to the server.
ANR6612I
Machine machine name updated.
Explanation: An UPDATE MACHINE command has

updated one or more attributes of a machine.

command.

another machine.
ANR6613I
ANR6608E
Command: A machine containing a server

is already defined.
Machine machine name deleted.
Explanation: A DELETE MACHINE command has

deleted the requested machine from the server.
Explanation: The ADSMSERVER=YES parameter

specified in the command is invalid because another
machine has already been defined with this parameter.
Only one machine can be defined to the server as
containing a server.

command.

is not defined to the server.
User response: Issue the command again and do not

specify ADSMSERVER=YES as a parameter.

command.
ANR6609I
Machine machine name defined.
Explanation: A DEFINE MACHINE command has

added the requested machine to the server.
Command: Machine machine name is not

defined.

a valid machine.
ANR6615E
Command: Failed to open input file - file

name.
Explanation: The input file specified in the command

cannot be opened by the server.

ANR6610E
ANR6614E
Command: Invalid recovery media name recovery media name.

command.
Explanation: The recovery media name specified in

the command is invalid.

an input file that is in a file system accessible by the
server.

command.
ANR6616E

a valid recovery media name.
ANR6611E
Command: Location information exceeds

Command: Invalid sequence number sequence number.
Explanation: The sequence number specified in the

command is invalid.
command.
Explanation: The location specified in the command

exceeds the maximum length of allowable characters.

a valid sequence number.

command.
ANR6617W

a valid location.

processed because it is not registered.
Explanation: The node indicated in the message

cannot be processed because it is not registered.
but another node can be processed if specified by this
command.
523
ANR6618E ANR6627I
a valid registered node.
ANR6618E
Command: No matching node registered.
Explanation: The node specified in the command does

not match any node registered to the server.
command.
a valid node.
ANR6623W
Explanation: The machine indicated in the message is

not defined to the server.
System action: The indicated machine is not
processed, but another machine can be processed if
specified by this command.
a valid machine.
ANR6624E
ANR6619I
Node node name associated with machine

machine name.
Explanation: A DEFINE MACHNODEASSOCIATION

command has associated the specified node with the
specified machine. The node node name is associated
with the machine machine name.
Command: Machine machine name cannot

be processed because it is not defined.
Command: No matching machine

defined.

does not match any machine defined to the server.
command.
a valid machine.

ANR6625I
ANR6620E
Command: Machine and node association

is already defined.
Explanation: The machine and node association

specified in the command is already defined to the
server.
System action: The server operation continues, but the
a valid node.
Explanation: A DEFINE
RECOVERYMEDIAMACHASSOCIATION command
has associated the specified machine with the specified
recovery media. The machine machine name is
associated with the recovery media recovery media name.
ANR6626E
ANR6621I

machine machine name.
Explanation: A DELETE MACHNODEASSOCIATION

command has deleted the requested association from
the server. The node node name is not associated with
the machine machine name.
ANR6622E
Command: Recovery media recovery media

Explanation: The recovery media specified in the

command is not defined to the server.
command.
a valid recovery media.
Machine machine name associated with

recovery media recovery media name.
Command: Recovery media/machine

association is already defined.
Explanation: The recovery media/machine association

specified in the command is already defined to the
server.
a valid machine.
ANR6627I
Machine machine name disassociated

from recovery media recovery media name.
Explanation: A DELETE
RECOVERYMEDIAMACHASSOCIATION command
has deleted the requested association from the server.
Machine machine name is not associated with the
recovery media recovery media name.
524
ANR6628E ANR6637E
ANR6628E
Command: Volume list exceeds maximum

length characters.
ANR6633I
Recovery media recovery media name

updated.
Explanation: The volume list specified in the

characters.
Explanation: An UPDATE RECOVERYMEDIA

command has updated one or more attributes of the
recovery media.

command.

a valid volume list.
ANR6629E
Command: Product name exceeds

Explanation: The product name specified in the

characters.
command.
a valid product name.
ANR6630E
Command: Product information exceeds

Explanation: The product information specified in the

characters.
command.

ANR6634I
Explanation: A DELETE RECOVERYMEDIA

command has deleted the requested recovery media
from the server.
ANR6635E
Command: Missing volume list for boot

recovery media.
Explanation: Boot recovery media cannot be defined

to the server without specifying a volume list.
command.
the volume list for the boot recovery media.
ANR6632I

defined.
Explanation: A DEFINE RECOVERYMEDIA command

has defined the recovery media to the server.
Command: Recovery media recovery media

name is already defined.
Explanation: The recovery media specified in the

command is already defined to the server.
command.
a different recovery media.
ANR6636E

valid product information.
ANR6631E

deleted.
Command: The characteristics specified

for machine machine name exceeds
Explanation: The characteristics specified in the

characters.
command.
valid characteristics.
ANR6637E
Command: The recovery instructions

specified for machine machine name
Explanation: The recovery instructions specified in the

characters.
command.
valid recovery instructions.
525
ANR6638E ANR6646I
ANR6638E
Command: The characteristics for

machine machine name are already
defined.
Explanation: The characteristics for the machine

specified in the command are already defined to the
server.
command.
User response: If the specified machine is defined to
the server, issue an UPDATE MACHINE command to
update the existing characteristics. If the machine is not
defined to the server, run AUDIT DRM FIX to delete
the characteristics.
ANR6639E
Command: The recovery instructions for

machine machine name are already
defined.
ANR6642E
Command: No association found for

recovery media and machine pair
specified.
Explanation: No association found for the recovery

media and machine pair specified in the command.
a valid recovery media and machine pair.
ANR6643E
Command: Invalid parameter value parameter value.
Explanation: The parameter issued in the command is

invalid.
command.
Explanation: The recovery instructions for the

machine specified in the command are already defined
to the server.

a valid parameter.

command.
ANR6644E
User response: If the specified machine is defined to

the server, issue an UPDATE MACHINE command to
update the existing recovery instructions. If the
machine is not defined to the server, run AUDIT DRM
FIX to delete the recovery instructions.
Explanation: The INSERT command is invalid. A

character string must be specified.
ANR6640E
Command: Cannot delete volume list for

boot recovery media.
Explanation: A volume list cannot be deleted for boot

recovery media. A volume list must exist for each boot
recovery media defined to the server.
command.
User response: To delete the volume list, issue an
UPDATE RECOVERYMEDIA command and specify a
recovery media type of OTHER and VOLUMES="". To
change the recovery media type to BOOT, issue an
UPDATE RECOVERYMEDIA command and specify the
volume list containing the boot recovery media and
TYPE=BOOT.
ANR6641E
Command: No association found for

machine and node pair specified.
Explanation: No association found for the machine

and node pair specified in the command.
a valid machine and node pair.
526
Command: A character string must be

specified.

command.
a valid character string.
ANR6645W
Node node name has already been

associated with machine machine name.
Explanation: The node specified in the DEFINE

MACHNODEASSOCIATION command is invalid. The
node is already associated with another machine shown
in the message. A node can only be associated with one
machine.
but another node can be processed if specified by the
command.
a valid node name.
ANR6646I
Audit command: Auditing disaster

recovery manager definitions.

database audit and indicates that the disaster recovery
manager definitions are being examined by the
ANR6647E ANR6656I
ANR6647E
Audit command: DRM global attributes

are missing.

global attributes used for server DRM activities are
missing.
FIX=YES to recreate the DRM global attributes.
ANR6648I
Audit command: DRM global attributes

are missing - default values will be used
to recreate the attributes.

global attributes used for server DRM activities are
missing. Because FIX=YES has been specified on the
AUDIT command, default attribute values will be used
to recreate the administrative global attributes.
ANR6652I
Audit command: Invalid priority value

encountered for machine machine name the default value will be set.

invalid machine priority value for the machine
audit function sets the machine priority value to the
default value.
User response: To override the default value, issue an
UPDATE MACHINE command to change the value
ANR6653I
Audit command: Invalid building value

encountered for machine machine name.

invalid building value for the machine indicated.

FIX=YES to correct the building value. Or, issue an
UPDATE MACHINE command and specify a new
building value.
ANR6649E
Audit command: DRM machine ID


global attributes machine ID used for server DRM
FIX=YES specified so that the DRM global attributes
can be corrected.
ANR6654I
Audit command: Invalid building value

encountered for machine machine name the building value will be removed.

invalid building value for the machine indicated.
removes the machine building value.
ANR6650I

Assignments are incorrect - values will
be corrected.

global attributes machine ID used for server DRM
activities are incorrect. Since FIX=YES has been
ANR6655I
Audit command: Invalid floor value


invalid floor value for the machine indicated.
User response: None

ANR6651I
User response: To set the building value to another

value, issue an UPDATE MACHINE command after the
Audit command: Invalid priority value


invalid priority value for the machine indicated.
FIX=YES to correct the priority. Or, issue an UPDATE
MACHINE command and specify a new priority value.

FIX=YES to correct the floor value. Or, issue an
UPDATE MACHINE command and specify a new floor
value.
ANR6656I
Audit command: Invalid floor value

encountered for machine machine name the floor value will be removed.

invalid floor value for the machine indicated. Because
527
ANR6657I ANR6665I
FIX=YES has been specified, the audit function removes
the machine floor value.
ANR6661I

User response: To set the floor value to another value,
issue an UPDATE MACHINE command after the audit
command has completed.
ANR6657I
Audit command: Invalid room value


invalid room value for the machine indicated.
FIX=YES to correct the room value. Or, issue an
room value.
ANR6658I
Audit command: Invalid room value

encountered for machine machine name the room value will be removed.
Audit command: Multiple machines are

indicated as servers. Only one machine
should have the server indicator set to
YES.

more than one machine with the server indicator set to
YES.
User response: For a list of machines with the server
indicator set to YES, issue a QUERY MACHINE
ADSMSERVER=YES command. Issue an UPDATE
MACHINE command for each machine that is not a
server.
ANR6662I
Audit command: Characteristics for

machine machine name not found.

characteristics reference from a machine for
characteristics that are not in the server database.

invalid room value for the machine indicated. Because
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
ANR6663I
User response: To set the room value for the specified

machine to another value, use the UPDATE MACHINE
command after the audit command has completed.
ANR6659I
Audit command: Invalid server value


invalid server value for the machine indicated.
FIX=YES to correct the server value. Or, issue an
server value.
ANR6660I
Audit command: Invalid server value

encountered for machine machine name the default value will be set.

invalid server value for the machine indicated. Because
machine server value to the default value.
Audit command: Recovery instructions for

machine machine name not found.

recovery instructions reference from a machine for
recovery instructions that are not in the server
database.
User response: Issue an UPDATE MACHINE
command to load the recovery instructions into the
database after the audit command has completed.
ANR6664I
Audit command: Invalid access value

encountered for recovery media recovery
media name.

invalid access value for the recovery media indicated.
FIX=YES to correct the access value. Or, issue an
new access value.
ANR6665I

UPDATE MACHINE command to change the value
Audit command: Invalid access value

media name - the default value will be
set.
528
ANR6666I ANR6673I
invalid access value for the recovery media indicated.
sets the recovery media access value to the default
value.
UPDATE RECOVERYMEDIA command to change the
value after the audit command has completed.
ANR6666I
Audit command: Invalid type value

media name.

invalid type value for the recovery media indicated.

ANR6670E
Explanation: A database audit process finds a machine

that references recovery media that is not defined in the
server database.
FIX=YES to correct the recovery media attributes.
ANR6671I

FIX=YES to correct the type value. Or, issue an
new type value.
ANR6667I
Audit command: Invalid type value

media name - the default value will be
set.

invalid type value for the recovery media indicated.
sets the recovery media type value to the default value.
UPDATE RECOVERYMEDIA command to change the
ANR6668E
Audit command: Machine is not found for

internal machine ID machine ID, which
is referenced by recovery media.
Explanation: A database audit process finds recovery

media that references a machine that is not defined in
FIX=YES to correct recovery media attributes.
ANR6669I
Audit command: Machine is not found for

is referenced by recovery media - the
machine reference will be deleted.

media that references a machine that is not defined in
the server database. Because FIX=YES has been
specified for the audit command, the reference will be
removed from the server database.
Audit command: Recovery media not

found for internal recovery media ID
recovery media ID, which is referenced by
a machine.
Audit command: Recovery media not

found for internal recovery media ID
recovery media ID, which is referenced by
a machine - the recovery media
Explanation: A database audit process finds m

machine that references recovery media that is not
will be deleted from the server database.
ANR6672E
Audit command: Client node not found

for internal node ID node ID, which is
referenced by a machine.

that references a client node that is not defined in the
server database.
FIX=YES to correct the machine attributes.
ANR6673I
Audit command: Client node not found

for internal node ID node ID, which is
referenced by a machine - the client
node reference will be deleted.

that references a client node that is not defined in the
for the audit command, the reference will be removed
from the server database.
529
ANR6674E ANR6683I
ANR6674E
Audit command: Machine not found for

is referenced by a client node.

node that references a machine that is not defined in
ANR6675I

is referenced by a client node - the

node that references a machine that is not defined in
the server database. Because FIX=YES has been
ANR6676E

is referenced by characteristics.

ANR6679I

instructions that reference a machine that is not defined
in the server database. Because FIX=YES has been
ANR6680E

Audit command: Missing or invalid

internal database attribute encountered
for machine machine name.

attribute for the specified machine.
ANR6681I

characteristics that reference a machine that is not

is referenced by recovery instructions the machine reference will be deleted.
Audit command: Missing or invalid

internal database attribute encountered
for machine machine name - the attribute
will be corrected.

attribute for the specified machine. Because FIX=YES
has been specified for the audit command the invalid
attribute will be corrected.
ANR6677I

is referenced by characteristics - the

characteristics that reference a machine that is not
will be removed from the server database.

ANR6682I
Command command ended: number of

volumes volumes processed.
Explanation: The indicated command ended. The total

number of volumes successfully processed is shown in
the message.
System action: The indicated command ends.

ANR6683I
ANR6678E

is referenced by recovery instructions.
Command: Volume volume name was

moved from from state state to to state.
Explanation: Volume volume name is successfully

moved from state1 to state2 by the indicated command.

instructions that reference a machine that is not defined
System action: The indicated volume is moved to the

destination state.
530
ANR6684I ANR6694E
ANR6684I
Command: Volume volume name was

deleted.
Explanation: The MOVE DRMEDIA *

WHERESTATE=COURIERRETRIEVE command
displays the message. Volume volume name is deleted
from the server database. For database backup volume,
after its expiration days have elapsed, the volume
history record is deleted when it is returned onsite. For
an empty scratch copy storage pool volume, or
active-data storage pool volume, the volume record is
deleted when it is returned onsite.
System action: The volume record is deleted from the
server database.
User response: Issue the CHECKIN LIBVOLUME
command for each volume returned onsite if the
volume is reused by the server.

a valid executable command with the CMD parameter.
ANR6688E
Explanation: The indicated operation has failed

because the entry/exit port of the specified library is
full.
User response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
any remaining eligible volumes.
ANR6690E
ANR6685E
Command: Volume volume name not

defined.
Explanation: Volume volume name is not defined to the

server.
System action: The indicated command is not
processed if the volume name is explicitly specified on
the command. If a volume pattern is specified on the
command, the volume shown is not processed, but the
other volumes are processed.
valid volume name.
ANR6686E
Command: Volume volume name in use.
Explanation: The MOVE DRMEDIA *

WHERESTATE=MOUNTABLE command displays the
message. Volume volume name is used for another
operation.
command: The specified command 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 name command.
Command: Copy storage pool cstgp name

not defined for Offsite Recovery Media.
Explanation: The MOVE DRMEDIA or QUERY

DRMEDIA command displays the message. The
indicated command was issued with a copy storage
pool name specified, but the specified pool name is not
defined to DRM for Offsite Recovery Media.
System action: The indicated command is not
processed.
User response: Reissue the command, after defining
the specified copy storage pool to DRM for Offsite
Recovery Media.
ANR6691E
Command: No match is found for this

move.
Explanation: The indicated command was issued, but

no matching volumes are defined to the server or the
volume specified is not managed by the command.
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
indicated volume is not processed, but the other
volumes are processed.
User response: Wait until the conflicting volume

activity has completed, and then reissue the command.
If the volume is currently mounted, but idle, dismount
the volume by using a DISMOUNT VOLUME
command and then retry this operation.
ANR6694E
ANR6687E
Command: Executable command string

Explanation: The length of the executable command

string specified with the CMD parameter exceeds the
maximum length of allowable characters (255).
command.
User response: Reissue the command specifying the

valid volume.
Command: The ORM state state is invalid
for a volume with access mode access
mode.
Explanation: The indicated command specifies an

Offsite Recovery Media state that is invalid for a
volume with the access mode shown. Specify
COURIER or COURIERRETRIEVE for a volume that
has access mode of OFFSITE.
command.
COURIER or COURIERRETRIEVE as the state for a
volume that has access mode of OFFSITE.
531
ANR6695E ANR6704E
ANR6695E

not defined for volume volume name.
Explanation: The MOVE DRMEDIA or QUERY

DRMEDIA command displays the message. The
volume being processed has associated with the device
class name shown that is not defined to the server.
ANR6699I
Cancel in progress.
Explanation: The MOVE DRMEDIA command has

been canceled and will end when resources have been
freed for the background process. This message may be
for a MOVE DRMEDIA command.
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
indicated volume is not processed, but the other
volumes not associated with the indicated class are
processed.

indicated device class is defined to the server.
Explanation: The indicated command completed

successfully.

ANR6700I
Command command completed

successfully.

ANR6696I
command: operation for volume volume

name in library library name starting.
Explanation: The indicated operation is being started

for the volume shown in the given library.
ANR6701E
System action: The server starts the operation in

response to the indicated command entered by an
administrator.
Explanation: The indicated command has been

entered with an invalid courier name.
User response: For SCSI library users, remove the

volume from the slot and issue a REPLY command,
along with the request ID, to tell the server the volume
was removed from the library.
ANR6697I

name in library library name completed
successfully.
Explanation: The indicated operation has completed

successfully for the volume shown in the given library.
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).
ANR6698E

name in library library name failed.
Explanation: The indicated operation has failed for the

volume shown in the given library. This message
should be preceded by another error message which
provides more detail about the error.
User response: Check for additional message and
eliminate the condition that caused the failure, then
retry the command.
Command: Invalid courier name - courier

name.

command.
courier name.
ANR6702E
Command: Invalid expiration days value

- days value.

entered that specifies an invalid expiration days value.
command.
expiration days value.
ANR6703E
Command: Invalid recovery plan prefix prefix.

entered with an invalid recovery plan prefix.
command.
recovery plan prefix.
ANR6704E
Command: Invalid plan instructions

prefix - prefix.

entered with an invalid plan instructions prefix.
command.
532
ANR6705E ANR6712I
plan instructions prefix.
ANR6705E
Command: Invalid character for volume

postfix - postfix character.

entered with an invalid character that is to be added to
the volumes names in the recovery plan file.
command.
character.
ANR6706E
Command: Invalid vault name - vault

name.

entered with an invalid vault name.
command.
vault name.
ANR6707W
Command: The state, access and location

attributes of the copy storage pool
volume volume name were not updated.
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
operation.
System action: If the volume was in an automated
library, the MOVE DRMEDIA command may have
checked the volume out of the library.
If a volume pattern is specified on the command, the
server continues processing the other volumes.
activity has completed, and then reissue the MOVE
DRMEDIA command.
ANR6708W
Command: Copy pool volume volume

name was not processed. The volume
was in use.
Explanation: The MOVE DRMEDIA command did not

process volume volume name because it was in use by
another server operation.
System action: The indicated command ends, if the
volume was explicitly specified in the command. If a
volume pattern was specified in the command, the
server continues processing other volumes that match
the pattern.
DRMEDIA command.
ANR6709W
Command: Active-data pool volume

volume name was not processed. The
volume was in use.
Explanation: The MOVE DRMEDIA command did not

process volume volume name because it was in use by
another server operation.
System action: The indicated command ends, if the
volume was explicitly specified in the command. If a
volume pattern was specified in the command, the
server continues processing other volumes that match
the pattern.
DRMEDIA command.
ANR6710W
Command: The state, access and location

attributes of the active-data storage pool
volume volume name were not updated.
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
operation.
System action: If the volume was in an automated
library, the MOVE DRMEDIA command may have
checked the volume out of the library.
If a volume pattern is specified on the command, the
server continues processing the other volumes.
DRMEDIA command.
ANR6711E
Audit command: An invalid database

backup series expiration days
encountered.

invalid value for database backup series expiration
days.
FIX=YES to correct the expiration days. Or, issue an
SET DRMDBBACKUPEXPIREDAYS command and
specify a new expiration days value.
ANR6712I
Audit command: An invalid database

backup series expiration days
encountered - the default value will be
set.

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
value.
533
ANR6713E ANR6721E
User response: To override the default value, issue a
SET DRMDBBACKUPEXPIREDAYS command to
completed.
ANR6717E
Audit command: Extraneous DRM global

attribute encountered.

nonexistent DRM global attribute.
ANR6713E
Audit command: An invalid check label

value encountered.

invalid check label value.

FIX=YES to delete the extraneous attribute.
ANR6718I

FIX=YES to correct the check label value. Or, issue a
SET DRMCHECKLABEL command and specify a new
check label value.
Audit command: Extraneous DRM global

attribute encountered - the attribute will
be deleted.

nonexistent DRM global attribute. Since FIX=YES has
been specified, the extraneous attribute will be deleted.
ANR6714I
Audit command: An invalid check label

value encountered - the default value
will be set.

invalid check label value. Because FIX=YES has been
specified, the audit function sets the check label value
to the default value.
SET DRMCHECKLABEL command to change the value
ANR6715E
Audit command: An invalid file process

value encountered.

invalid file process value.
FIX=YES to correct the file process value. Or, issue a
SET DRMFILEPROCESS command and specify a new
file process value.
ANR6716I
Audit command: An invalid file process

value encountered - the default value
will be set.

invalid file process value. Because FIX=YES has been
specified, the audit function sets the file process value
to the default value.
SET DRMFILEPROCESS command to change the value
534

ANR6719E

assignments not found.
Explanation: A database audit process finds no entries

in server database for DRM internal machine ID
assignments.
FIX=YES to correct the error.
ANR6720I

assignments not found - entry will be
created.

in server database for DRM internal machine ID
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry
in the server database for the machine ID assignments.
ANR6721E
Audit command: DRM recovery media ID

assignments not found.

in server database for DRM internal recovery media ID
assignments.
FIX=YES to correct the error.
ANR6722I ANR6730I
ANR6722I

assignments not found - entry will be
created.

in server database for DRM internal recovery media ID
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry
in the server database for the recovery media ID
assignments.
the recovery plan instructions file prefix.

SET DRMPLANINSTRPREFIX command to change the
ANR6727E
Audit command: Postfix for DRM

replacement volumes names not found.

in server database for DRM postfix definitions for
replacement volumes names.
ANR6723E
Audit command: Prefix for DRM recovery

plan not found.

in server database for DRM recovery plan prefix
definitions.

specify FIX=YES to correct the error.
ANR6728I

ANR6724I

plan not found - entry will be created.

in server database for DRM recovery plan prefix
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
recovery plan file prefix.
SET DRMPLANFILEPREFIX command to change the
ANR6725E

plan instructions not found.

in server database for DRM recovery plan instructions
prefix definitions.
ANR6726I

plan instructions not found - entry will
be created.

in server database for DRM recovery plan instructions
prefix 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
Audit command: Postfix for DRM

replacement volumes names not found entry will be created.

in server database for DRM postfix definitions for
replacement volumes names. 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 replacement volumes postfix.
SET DRMPLANVPOSTFIX command to change the
ANR6729E
Audit command: Primary storage pools to

be restored by DRM not found.

in server database for primary storage pools to be
restored by DRM.
ANR6730I
Audit command: Primary storage pools to

be restored by DRM not found - entry
will be created.

in server database for primary storage pools to be
restored by DRM. Because FIX=YES has been specified
the primary storage pools to be restored by DRM.
SET DRMPRIMSTGPOOL command to change the
535
ANR6731E ANR6739E
ANR6731E
Audit command: Copy storage pools to be

managed by DRM not found.

in server database for copy storage pools to be
managed by DRM.

ANR6736I

ANR6732I
Audit command: Copy storage pools to be

managed by DRM not found - entry
will be created.

in server database for copy storage pools to be
managed by DRM. Because FIX=YES has been specified
the copy storage pools to be managed by DRM.

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
server database for the courier name definitions.
SET DRMCOURIERNAME command to change the
ANR6737E

SET DRMCOPYSTGPOOL command to change the
Audit command: Courier information for

ORM not found - entry will be created.
Audit command: Vault name for ORM not

found.

in server database for vault name definitions used by
DRM Offsite Recovery Media (ORM).
ANR6733E
Command: Cannot complete initialization

for process name process.
Explanation: The indicated process fails during

process initialization.
System action: The indicated command is ended and
server processing continues.

ANR6738I
Audit command: Vault name for ORM not

found - entry will be created.

in server database for vault name definitions used by
server database for the vault name definitions.
ANR6734E

processed: library library name not
defined.
Explanation: The indicated volume is not processed

since the designated library has not been defined or has
been deleted.
User response: Reissue the command using a different
library name, or define the library before retrying the
command.

SET DRMVAULTNAME command to change the value
ANR6739E
Audit command: Database backup series

expiration days for ORM not found.

in server database for database backup series expiration
days definitions used by DRM Offsite Recovery Media
(ORM).
ANR6735E
Audit command: Courier information for

ORM not found.


in server database for courier name definitions used by
536
ANR6740I ANR6749I
ANR6740I
Audit command: Database backup series

expiration days for ORM not found entry will be created.

in server database for database backup series expiration
days definitions used by DRM Offsite Recovery Media
(ORM). Because FIX=YES has been specified for the
database backup series expiration days definitions.
SET DRMDBBACKUPEXPIREDAYS command to
completed.
ANR6741E
Audit command: Check label indicator for

ORM not found.

in server database for check label definitions used by
ANR6742I
Audit command: Check label indicator for


in server database for check label definitions used by
DRM Offsite Recovery Media (ORM ). Because
audit function creates an entry using the default value
in the server database for the check label definitions.
SET DRMCHECKLABEL command to change the value
ANR6743E
Audit command: File process indicator for

ORM not found.

in server database for file process definitions used by
ANR6744I
Audit command: File process indicator for


in server database for file process definitions used by
server database for the file process definitions.
SET DRMFILEPROCESS command to change the value
ANR6745E


global attributes recovery media id used for server
DRM activities are incorrect.
FIX=YES specified so that the DRM global attributes
can be corrected.
ANR6746I

assignments are incorrect - values will
be corrected.

global attributes recovery media ID used for server
DRM activities are incorrect. Since FIX=YES has been
ANR6747I
Number of volumes processed: number

processed the number of volumes displayed. This
PROCESS command for a MOVE DRMEDIA command.
ANR6749I
Command: process process ID terminated

before completion - process canceled.
Explanation: The indicated background process

performing the command shown has been canceled.
System action: If other processes are executing, these
processes continue.
537
ANR6750E ANR6758E
ANR6750E
Disaster recovery manager operation

command being processed is denied - server
is not in compliance with license terms.
Explanation: The server refuses a disaster recovery

manager operation because the current server
configuration is not in compliance with the license
terms.
System action: Server operation continues. Disaster
recovery operations cannot be performed until the
server is licensed for the Tivoli Disaster Recovery
Manager product.
User response: Issue a QUERY LICENSE command to
determine which license terms are not in compliance.
is in compliance with license terms. Start an AUDIT

LICENSES process to adjust server license information.
When this process completes, start the session again. If
the problem persists, contact your service
representative.
ANR6754I

deleted the requested characteristics from the server.
ANR6755I
ANR6751E

command being processed is denied - server
is not licensed for disaster recovery
manager support.

manager operation because the server is not licensed to
support the disaster recovery manager.
Machine machine name characteristics

deleted.
Machine machine name recovery

instructions deleted.

deleted the requested recovery instructions from the
server.

Machine machine name characteristics not
User response: Obtain the license to support the

disaster recovery manager from your service provider
or reseller. Issue the REGISTER LICENSE command
with this license to enable the disaster recovery
manager support.
ANR6756E
ANR6752W


Command being processed is in violation of
server license terms - server is not
licensed for disaster recovery manager
support.
Explanation: The server warns about a disaster

recovery manager operation because the server is not
licensed to support disaster recovery manager.
User response: Obtain the license to support disaster
recovery manager from your service provider or
reseller. Issue the REGISTER LICENSE command with
this license to enable disaster recovery manager
support.
ANR6753E
command being processed encountered an

internal server error while checking
license compliance.

in determining whether the server is in compliance
with license terms.
User response: Issue the QUERY LICENSE and
QUERY STATUS commands to determine if the server
538
Explanation: A DELETE MACHINE command cannot

delete the requested characteristics from the server. The
characteristics for the specified machine are not defined
to the server.

a machine that has characteristics defined to the server.
ANR6757E
Machine machine name recovery

instructions not defined to the server.
Explanation: A DELETE MACHINE command cannot

delete the requested recovery instructions from the
server. The recovery instructions for the specified
machine are not defined to the server.
a machine that has recovery instructions defined to the
server.
ANR6758E
Command: Only one character string can

be specified.
Explanation: The INSERT command is invalid. Either

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
command at the same time.
ANR6759E ANR6765E
command.
Pattern-matching for volume names is only allowed

when the WHERESTATE parameter is specified.

one valid character string.

command.
ANR6759E

command being processed is denied disaster recovery manager support is not
available for server platform platform.

manager operation because disaster recovery manager
support is not available for the indicated server
platform.
ANR6760E
Command: Executable command line

exceeds maximum length characters for
volume volume name.
Explanation: While writing to a command file, one of

the following conditions occurred:
v The length of the command line written to the
command file exceeds the LRECL specified for MVS
or exceeds the default length for the command line
written (255).
v The length of the command created after replacing
the substitution variables &VOL, &VOLDSN, &NL,
and &LOC exceeds the server allowable command
line length (1500).
command.
a valid executable command with the CMD parameter.
In the case where volumes are being ejected from the
library, it is possible the server database does not reflect
the true state of the volume. For MOVE DRMEDIA,
rerun the command after determining the cause of the
error. For MOVE MEDIA, an update volume command
should be issued setting the access of the volume to
read only.
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
MOVE or QUERY DRMEDIA commands to create the
command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6761E
Command: WHERESTATE parameter is

required.
Explanation: The indicated command specifies a

volume name containing a pattern matching character
and the TOSTATE parameter. The WHERESTATE
parameter is not specified. The specification is invalid.

specific volume name or by specifying the
WHERESTATE parameter along with the TOSTATE
parameter.
ANR6762E
Command: The specified destination state

tostate is invalid for volume volume name
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.
a valid destination state for the volume name shown.
ANR6763I
Command: The specified command has

been written to file 'file name'.
Explanation: The command string specified with the

CMD parameter on the command shown is written to
the indicated file for each volume successfully
processed.
User response: Execute the commands written to the
file.
ANR6764E
command: Command file name exceeds

Explanation: The file name specified for containing

the executable commands generated by DRM exceeds
the maximum valid length shown.
command.
valid file name.
ANR6765E
Command: Invalid not mountable

location name - not mountable name.

entered with an invalid not mountable location name.
command.
User response: Reissue the command with a valid not
mountable location name.
539
ANR6766E ANR6774E
ANR6766E
Command: No command string is

specified for FORMAT=CMD.

entered with a FORMAT=CMD to write a command
string to a file, but no command string is specified.
command.
command string to be written to a file.

SET DRMNOTMOUNTABLENAME command to
completed.
ANR6771E
Audit command: Command file name

information for ORM not found.

in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM).
ANR6767E
Command: Invalid command file name command file name.

entered with an invalid command file name.

ANR6772I

command.
command file name.
ANR6768E
command: Prefix exceeds maximum

characters characters.
Explanation: The prefix specified for recovery plan

files or for plan instructions files exceeds the maximum
valid length. The maximum valid length is shown in
the message.
command.
valid prefix.
ANR6769E
Audit command: Not mountable name

information for ORM not found.

in server database for not mountable location name
definitions used by DRM Offsite Recovery Media
(ORM).
ANR6770I
Audit command: Not mountable name

information for ORM not found - entry
will be created.

in server database for not mountable location name
definitions used by DRM Offsite Recovery Media
(ORM). Because FIX=YES has been specified for the
courier name definitions.
540
Audit command: Command file name

information for ORM not found - entry
will be created.

in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM). Because
audit function creates an entry using the default value
in the server database for the command file name
definitions.
SET DRMCMDFILENAME command to change the
ANR6773E
Command: Unable to open file 'command

file name' for output.

command file name shown. The file name shown in the
message is specified with the indicated command, the
SET command, or the default name generated by the
indicated command.
indicated command.
proper authority to write to the file indicated. In AIX,
make sure that the file name specified in the command
or in the SET command is a full path file name, not a
directory path name. In MVS, make sure that the file
name specified in the command or in the SET
command is a valid MVS file name. Reissue the
command after determining the cause of the error.
ANR6774E
Command: Invalid volume transition

states - from 'specified WHERESTATE'
state to 'specified TOSTATE' state.
Explanation: The TOSTATE specified is an invalid
ANR6775E ANR6782E
destination state for the WHERESTATE specified.
ANR6778E

command.

processed: device type device type not
supported.

a valid destination state.

because the device type shown is not supported by the
function.
Command: Error writing to file 'file name'

for volume volume name.
System action: The indicated volume is not processed.
ANR6775E

file name shown for the indicated volume.

ANR6779E

command.
proper authority to write to the file indicated. Reissue
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
the true state of the volume. For MOVE DRMEDIA,
rerun the command after determining the cause of the
error. For MOVE MEDIA, an update volume command
should be issued setting the access of the volume to
read only.
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
MOVE or QUERY DRMEDIA commands to create the
command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6776E
Command: Could not delete file: file name

manager operation because disaster recovery manager
support is not available for the server platform.
ANR6780E
Audit command: An invalid recovery plan

file expiration days encountered.

invalid value for recovery plan file expiration days.
FIX=YES to correct the expiration days. Or, issue an
SET DRMRPFEXPIREDAYS command and specify a
new expiration days value.
ANR6781I
Explanation: The indicated command failed but the

file created could not be deleted.
Audit command: An invalid recovery plan

file expiration days encountered - the

invalid value for recovery plan file expiration days.
sets the expiration days value to the default value.

User response: Delete the file shown.
ANR6777E

command being processed is denied disaster recovery manager support is not
available for server platform.
Command: Command file 'file name'

already in use.

command file name that is in use. The command file
name shown is selected for use by the server in the
following order:
v The file name specified on the indicated command.
v The file name specified on the SET command.
v The file name generated by the server (AIX only).
command.
User response: Reissue the command at a later time
or reissue the command specifying a different
command file name.

SET DRMRPFEXPIREDAYS command to change the
ANR6782E
Audit command: Recovery plan file

expiration days not found.

in server database for recovery plan file expiration days
definitions.
541
ANR6783I ANR6905I
ANR6783I
Audit command: Recovery plan file

expiration days not found - entry will
be created.

in server database for recovery plan file expiration days
definitions. Because FIX=YES has been specified for the
recovery plan file expiration days definitions.
ANR6901I
Number of plan stanzas processed:

number.
Explanation: The PREPARE command has processed

the number of stanzas displayed. This message may be
for a PREPARE command.

SET DRMRPFEXPIREDAYS command to change the
ANR6784I

volumes processed. Volumes sent to library
library name for checkout: number volumes
sent.

processed the number of volumes shown. Currently, the
MOVE DRMEDIA command has sent for processing
the number of volumes shown to the library shown.
This message may be displayed in response to a
QUERY PROCESS command for a MOVE DRMEDIA
command.
ANR6902I
Number of plan stanzas processed:

number. Currently processing stanza:
recovery plan stanza name.
Explanation: The PREPARE command displays the

number of stanzas already processed and the name of
the stanza currently being processed. This message may
be displayed in response to a QUERY PROCESS
command for a PREPARE command.
ANR6903I
Cancel in progress.
Explanation: The PREPARE command has been

for a PREPARE command.
ANR6785W
Warning: The ADSM V3 Disaster

Recovery Manager Disk Image Dump
function is not supported in the Tivoli
Disaster Recovery Manager. The ADSM
V3 DRM Disk Image Restore function
has been stabilized with no new
maintenance or hardware support
planned.
Explanation: None.
System action: DRM Disk Image Dump and Restore
function continues.
ANR6900I
Command: The recovery plan file file

name was created.
Explanation: The recovery plan file was created.

ANR6904I
Sending recovery plan file to target

server.
Explanation: The PREPARE command is sending the

recovery plan file to the target server. This message
may be displayed in response to a QUERY PROCESS
command for a PREPARE command.
ANR6905I
Command: Recovery plan file RPF volume

name was created. Specified device class
device class name.
Explanation: The recovery plan file was created on the

target server.

542
ANR6912W ANR6922W
ANR6912W
Command: The database was not backed

up.
Explanation: No backups have been made of the

server data base.
System action: Stanzas in the recovery plan do not
include database recovery information.
User response: Backup the server data base by issuing
the BACKUP DB command.
ANR6913W
Command: No volumes with backup data

exist in copy storage pool storage pool
name.
Explanation: A copy storage pool does not contain

any volumes with usable data.
User response: Define copy storage pools in the

server.
ANR6918W
Explanation: A source file for recovery instructions

was not found.
System action: The recovery plan will not contain
recovery instructions.
User response: To get recovery instructions in the
recovery plan, ensure the corresponding instructions
source file exists. If it does, check authorizations to the
file.
ANR6920W

include recovery information for any volumes in the
storage pool.
User response: Determine why this storage pool has
no volumes with usable data.
ANR6914W
Command: No volumes with active data

exist in the active-data storage pool
storage pool name.
Explanation: An active-data storage pool does not

contain any volumes with usable data.
include recovery information for any volumes in the
storage pool.
User response: Determine why this storage pool has
no volumes with usable data.
ANR6915W

storage pool type is not defined to the
server.
Explanation: A storage pool that is not defined to the

server was specified by SET DRMPRIMSTGPOOL, SET
DRMCOPYSTGPOOL, or on the PREPARE command
line.
Command: Recovery instructions file file

name not found.
Command: S volume name is not valid for

server device type device type. Original
volume name: volume name. Stanza is
stanza name.
Explanation: Appending the replacement volume

name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name
has created a name that is not valid for the server
device type shown.
System action: Replacement volume name is used in
the recovery plan stanza.
User response: Devise a naming convention that
allows the use of the replacement volume name postfix
or at restore time manually update the generated
recovery plan with a legal replacement name. For
additional information and related commands, refer to
the Administrator's Reference for your particular
platform.
ANR6921W
Command: Cannot locate server options

file 'file name'.
Explanation: The Prepare command cannot open the

specified server options file.
System action: VOLHISTORY and DEVCONFIG
options are added to the recovery plan file stanza
DSMSERV.OPT.FILE.

include recovery information for the storage pool.
User response: Correct the storage pool specification

or define the storage pool to the server.
ANR6922W
ANR6916W
Command: No copy storage pools are

defined.
Explanation: The server has no copy storage pools

defined.
System action: Recovery plan file will not contain
copy storage pool information.
Command: No machine information was

defined for the machine that contains
server server name.
Explanation: The machine information has not been

saved in the server data base.
System action: The recovery plan file does not contain
the machine and recovery media information stanzas.
User response: If you want to include the machine
information in the recovery plan file, issue the DEFINE
MACHINE command to save the machine information
543
ANR6923W ANR6929W
in the server data base and reissue the PREPARE
command.
ANR6923W
Command: No recovery media defined

for machine machine name.
Explanation: No recovery media has been defined to

the server for the specified machine.
the machine recovery media stanza.
recovery media information in the recovery plan file,
issue the DEFINE RECOVERYMEDIA command.
Reissue the PREPARE command after the appropriate
commands have been issued to define the recovery
media. For additional information and related
commands, refer to the Administrator's Reference for
ANR6924W
Command: No recovery instructions

defined for machine machine name.
Explanation: No recovery instructions have been

defined to the server for the specified machine.
the machine recovery instructions stanza.
recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command
after the appropriate commands have been issued to
define the recovery media. For additional information
and related commands, refer to the Administrator's
has created a name that is not valid for the server

device type shown.
User response: Devise a naming convention that
allows the use of the replacement volume name postfix
or at restore time manually update the generated
recovery plan with a legal replacement name. For
additional information and related commands, refer to
the Administrator's Reference for your particular
platform.
ANR6927W
Command: Primary storage pool storage

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
NDMP. DRM does not manage a storage pool with this
data format.
User response: Correct the storage pool specification.
ANR6928W
Command: No eligible primary storage

pools match the specified storage pool
name storage pool name .
Explanation: The storage pool specified by the SET

DRMPRIMSTGPOOL or on PREPARE command does
not match any eligible primary storage pool. Possible
reasons include:
v Primary storage pools were not defined.
ANR6925W
Command: No machine characteristics

defined for machine machine name.
Explanation: No characteristics have been defined to

the server for the specified machine.
the machine characteristics stanza.
recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command
after the appropriate commands have been issued to
define the recovery media. For additional information
and related commands, refer to the Administrator's
ANR6926W
Command: There is at least one invalid

generated volume name associated with
storage pool storage pool server device
type device type in stanza stanza name.

name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name
544
v Primary storage pools were defined, but their data

formats are for NAS file servers, or their device
classes use the CENTERA device type.
v The name specified does not match eligible primary
storage pool names.
include recovery information for the storage pools.
User response: Correct the storage pool specification
or define eligible storage pools to the server.
ANR6929W
Command: No eligible primary storage

pools are defined to the server.
Explanation: The server has no eligible primary

storage pools defined.
System action: Recovery plan file will not contain
primary storage pool information.
User response: Define eligible primary storage pools
to the server.
ANR6930W ANR6945E
ANR6930W
Command: Primary storage pool storage

pool name, whose device class uses the
CENTERA device type, is not managed
by DRM.
Explanation: The SET DRMPRIMSTGPOOL or the

PREPARE command specified a primary storage pool
whose device class uses the CENTERA device type.
DRM does not manage storage pools that use the
CENTERA device type.
User response: Correct the storage pool specification.
ANR6937E
command: parameter name parameter not

allowed from the command line.
Explanation: The parameter shown is not allowed

from the command line interface.
command.
parameter from the web.
ANR6938I
No information found for stanza stanza

name.
Explanation: No information found for recovery plan

file stanza shown.
System action: The server does not display the
information for the stanza.
ANR6941E
Query recovery plan file content is

waiting for mount point in device class
device class name.
Explanation: Query recovery plan file content has

begun to wait for a mount point that can be used for a
volume in the device class shown.
System action: The function waits for the mount
point.
ANR6942E

waiting for access to input volume
volume name.

begun to wait for availability of the input volume
shown.
System action: The function waits for the volume to
become available.
ANR6943E

waiting for mount of input volume
volume name.

begun to wait for the mount of the input volume
shown.
System action: The function waits for mount.
User response: None

ANR6944E
ANR6939E
Command: Invalid recovery plan file

stanza name - stanza name.
Explanation: The specified recovery plan file stanza

name is invalid.
command.
a valid recovery plan file stanza name.
Explanation: The recovery plan file name specified in

the command is invalid.
command.
a valid recovery plan file name.
ANR6945E
ANR6940E
command command not allowed from

server console.
Explanation: The indicated command is not allowed

to be issued from the server console.
User response: Reissue the command from an
administrator using an Administrative Client.
Command: Invalid recovery plan file

name - recovery plan file name.
Command: Cannot find filespace filespace

name for recovery plan file recovery plan
file name.
Explanation: The server cannot find the filespace

(ADSM.SERVER) for recovery plan file specified in the
server.
System action: The retrieve operation ends, and the
User response: Issue QUERY FILESPACE command
on the target server to see if there is any filespaces
created for the recovery plan file. The filespace name
for the recovery plan file is ADSM.SERVER.
545
ANR6946E ANR6954E
ANR6946E
Command: Retrieve failed for recovery

plan file name - error on input storage
device.
Explanation: The server ends an retrieve operation

because an I/O error has been encountered by the
server in reading from a device.
The server may need to be shut down with the HALT
command to correct the hardware problem.
ANR6947E
Command: Data storage retrieve failed

for recovery plan file name - error detected.
Explanation: The server ends the retrieve operation

because an error has been encountered on the server.
Some common reasons for the error are:
ANR6948E
Command: Cannot find the recovery plan

file for Recovery plan file name.

a valid device class.
ANR6950E
Command: The recovery plan file was not

created.
Explanation: Due to a processing error, a recovery

plan file was not created.
System action: Recovery plan file not created.
problems, if possible. Reissue the command, after
determining the cause of the error.
ANR6951E
Command: Recovery plan file file name

was not created.

plan file was not created.
Reissue the command, after determining the cause of
the error.
ANR6952E
Command: File name file name already

exists.
Explanation: File already exits.

User response: Determine why file already exists. If
possible, delete it. Reissue the command, after
Explanation: The server cannot find the specified

recovery plan file.
ANR6953E

command.

recovery plan file.

a valid recovery plan file name. Use the QUERY
RPFILE command to view the name of the recovery
plan file that you are interested in displaying its
content.
System action: The recovery plan file was not created.
ANR6949E
Command: No matching device class

defined.
Explanation: The device class specified in the

command does not match any device class defined to
the server.
command.
Command: File write error.

problems, if possible. Make sure that there is sufficient
space in the file system for the file. Reissue the
command after determining the cause of the error.
ANR6954E
Command: Unable to open file 'file name'

for output.

recovery plan file for output.
546
ANR6959E ANR6969E
proper authority to write to the file indicated. Reissue
the command after determining the cause of the error.
ANR6959E
Command: Plan instructions prefix

'instructions prefix' is not valid.
Explanation: The prefix specified for recovery

instructions is not valid.
valid prefix.
ANR6960E
Command: Recovery plan prefix 'plan

prefix ' is not valid.
Explanation: The prefix specified for the recovery plan

file is too long.
valid prefix.
ANR6965E
Explanation: An server database query error occurred.

This message always accompanies another error
message and provides more detail about that error.
User response: Issue a QUERY ACTLOG command to
view the activity log and search for messages. If the
ANR6966E
Command: Query database failed.
Explanation: A server database query error occurred.


Command: Query log failed.


Command: Query storage pool failed.

Command: Query volume history failed.

ANR6969E
ANR6964E
Command: Query log volume failed.

ANR6968E
ANR6963E
Command: Query database volume failed.

ANR6967E
ANR6962E
Command: Query volume failed.
Command: Query device class failed.

547
ANR6970E ANR6978E
ANR6970E
Command: A recovery plan file is already

being created.
Explanation: The server command processor will not

start a background process to execute another
PREPARE command.
User response: Reissue the command after the first
PREPARE command has completed.
ANR6971E
Command: Could not delete plan file plan

file name.
ANR6975E
Explanation: An error occurred while PREPARE was

attempting to read 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.
problems, if possible. Reissue the command after
ANR6976E
Explanation: Prepare command failed but the plan file

created could not be deleted.
User response: Delete the plan file.
Command: Unable to read file file name.
Command: The recovery plan file was not

stored on another server and the local
copy file name cannot be deleted.

plan file was not stored on target server and the local
copy of the plan file cannot be deleted.
System action: PREPARE processing ends.
ANR6972E
Command: Query machine failed.
Explanation: A server machine query error occurred.

ANR6973E
Command: Query recovery media failed.
Explanation: A server recovery media query error

occurred. This message always accompanies another
error message and provides more detail about that
error.

problems, if possible. After determining the cause of
the error, re-issue the PREPARE command and delete
the local recovery plan file.
ANR6977E
Command: Device class name device class

name exceeds maximum characters
characters.
Explanation: The command shown has been entered

and specifies a device class name that is too long. The
maximum valid length for a device class name is
shown in the message.
command.

valid device class name.

ANR6978E
ANR6974E
Command: Unable to open file file name.
Command: Invalid device class device class

name.
Explanation: The specified device class cannot be used

by the command shown. Possible reasons include:
v The device class is not defined.
Explanation: An error occurred while PREPARE was

attempting to open the local recovery plan file copy in
order to send it to the target server.
v The device class is defined but not of type SERVER.
System action: The recovery plan file is not stored on

the target server.

command.

problems, if possible. Reissue the command after

device class.
548
v The name specified is an invalid device class name.
ANR6979E ANR7800I (Windows)

ANR6979E
Command: Recovery plan file was not

created. Specified device class device class
name.
Explanation: A recovery plan file cannot be not

created using the specified device class.
problems, if possible. Reissue the command, after
ANR6980E
Command: Prefix prefix exceeds maximum

Explanation: The command shown has been entered

and specifies a plan or instructions prefix that is too
long. The maximum valid length is shown in the
message.
command.
shorter prefix.
ANR6984E

mounted. Specified device class device
class name; maximum capacity: number of
bytes bytes.
Explanation: During command PREPARE processing,

writing to the sequential media. Command PREPARE
media for storing data.
System action: Command PREPARE processing ends.
User response: Increase the device class maximum
capacity and reissue the PREPARE command. If an
object was created on the target server, issue the
RECONCILE VOLUMES FIX=YES to delete the object
from the target server.
ANR6985E


export, database dump, database backup, or DRM
prepare operation or is in use by another process.
User response: Re-issue the PREPARE command.
ANR6986E
Command: The DELETELATEST

parameter is only valid for volume
history types RPFILE or
RPFSNAPSHOT.

volume history type was specified for the TYPE=
parameter.
User response: Re-issue the command and specify a
valid type value.
ANR7800I (AIX) DSMSERV generated at time on date.
Explanation: The server module was generated at the
indicated date and time.
ANR7800I (HP-UX) DSMSERV generated at time on
date.
ANR7800I (Linux) DSMSERV generated at time on
date.
ANR7800I (Solaris) DSMSERV generated at time on
date.
ANR7800I (Windows) DSMSERV generated at time
on date.
549
ANR7801I (AIX) ANR7804E (HP-UX)

ANR7801I (AIX) Subsystem process ID is process
identifier.
Explanation: The server process has the indicated
process identifier.
ANR7801I (HP-UX) Subsystem (master) process ID is
process identifier.
Explanation: The server's master HP-UX process has
the indicated process identifier.
ANR7803E (AIX) Attempt to overwrite a shared

memory segment, as directed with the -F
parameter, FAILED.
Explanation: The server has been started with the -F
parameter and unsuccessfully attempted to overwrite
existing shared memory segments. This error occurs
when the user that starts the server with -F parameter
is not the owner of the shared memory segments and
lacks the required authority.
System action: Server terminates.
User response: Resolve the authorization problem and
restart the server.

ANR7801I (Linux) Subsystem process ID is process
identifier.
process identifier.
ANR7801I (Solaris) Subsystem process ID is process
identifier.
process identifier.
ANR7802E (AIX) Shared memory segments for a
server running in the current directory
already exist. The -F parameter can be
used to overwrite.
Explanation: Shared memory segments are created for
each instance of the server based on the current
directory. This message indicates that the shared
memory segments already exist. A server is presently
running from the current directory or a server running
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
-F parameter to force the existing shared memory
segments to be overwritten. If you want to run
multiple instances of the server, each instance must be
run from a separate directory with a separate
dsmserv.dsk file and have separate log, database, and
storage volumes.
550
ANR7804E (AIX) Error reason.

Explanation: The server attempted to open,lock, or
write to the specified file The open, lock, or write
operation failed. These are some common reasons for
the failure. Another server is already running from this
directory and has the file open or locked. The instance
user ID does not have enough write access to the file.
The file system is full.
User response: Examine the contents of the lock file.
The process ID for the server that is running is
recorded in this file. Two servers cannot be started from
the same directory. You can remove the lock file and
attempt to start the server only if the recorded process
ID is not currently running dsmserv. The 'ps -e' AIX
command can be used to display processes that are
currently running. Check the permissions of the
directory and file system and ensure that there is
appropriate permission for the instance user ID to write
to the file. Check that there is enough space in the file
system.
ANR7804E (HP-UX) Error reason.
ID is not currently running dsmserv. The 'ps -e'
ANR7804E (Linux) ANR7805E (Linux)

system.
ANR7804E (Linux) Error reason.
system.
ANR7804E (Solaris) Error reason.
system.
ANR7804E (Windows) Error reason.

ID is not currently running dsmserv. Check the
permissions of the directory and file system and ensure
that there is appropriate permission for the instance
user ID to write to the file. Check that there is enough
space in the file system.
ANR7805E (AIX) Volume volume name is in use by
another server.
Explanation: The server has attempted to open a disk
volume but has discovered that the volume is in use by
another server.
System action: The open operation fails for the
volume.
User response: To prevent concurrent RAW volume
access by more than one server, files are created in the
/tmp directory to 'lock' these volumes. The names of
these temporary files are /tmp/
adsm.disk.dev.<volumename> where <volumename> is
the name of the RAW volume defined in the /dev
directory. Please note that the name for the logical
volume as defined in SMIT is represented in the /dev
directory with a leading 'r' character (for example, a
raw volume defined in SMIT as dsmstg1 will be
represented in the /dev directory as the file
/dev/rdsmstg1).
You may use the AIX 'ps -e' command to determine if
other dsmserv processes are running. You may remove
the temporary lock files and attempt to re-start the
server ONLY if there are no other dsmserv processes
running
ANR7805E (Linux) Volume volume name is in use by
another server.
another server.
volume.
directory. Please note that the name for a RAW logical
volume as defined in Solaris is in the /dev directory
with a leading 'r' character (for example, a raw volume
defined in Solaris on a regular SCSI drive as
dsk/c0t0d0s0 will be represented in the /dev directory
as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
551
ANR7805E (Solaris) ANR7806W (Windows)

volume, the server automatically locks/unlocks a
volume. Different linked file names pointing to the
same volume will cause this message since the server
locks the linked volume, not the link name itself.
You may use the Solaris 'ps -ef | grep dsmserv'
command to determine if other dsmserv processes are
running. You may remove the temporary lock files for
RAW volumes and attempt to re-start the server ONLY
if there are no other dsmserv processes are running.
ANR7805E (Solaris) Volume volume name is in use by
another server.
another server.
ANR7806W (HP-UX) Unable to open file file.

Explanation: The server was unable to open the
indicated file.
System action: The operation that was to use the
indicated file fails. A subsequent unnumbered message
had details from the system.
User response: Determine the reason for being unable
to open the file and re-attempt the operation. Common
reasons for being unable to open the file include
providing the wrong name, having insufficient
authorization to open the file and not being the file's
owner.
ANR7806W (Linux) Unable to open file file.

volume.

indicated file.

directory. Please note that the name for a RAW logical
volume as defined in Solaris is in the /dev directory
with a leading 'r' character (for example, a raw volume
defined in Solaris on a regular SCSI drive as
dsk/c0t0d0s0 will be represented in the /dev directory
as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
volume, the server automatically locks/unlocks a
volume. Different linked file names pointing to the
same volume will cause this message since the server
locks the linked volume, not the link name itself.

You may use the Solaris 'ps -ef | grep dsmserv'

command to determine if other dsmserv processes are
running. You may remove the temporary lock files for
RAW volumes and attempt to re-start the server ONLY
if there are no other dsmserv processes are running.
ANR7806W (AIX) Unable to open file file.
indicated file.
owner.
552

owner.
ANR7806W (Solaris) Unable to open file file.
indicated file.
owner.
ANR7806W (Windows) Unable to open file file.
indicated file.
owner. The file may be already opened by the server or
another program.
ANR7807W (AIX) ANR7810W (AIX)

ANR7807W (AIX) Unable to get information for file
file.
Explanation: The server was unable to get information
about the indicated file.
indicated file fails. A subsequent, unnumbered message
has details from the system.
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
owner.
ANR7807W (HP-UX) Unable to get information for
file file.
owner.
ANR7807W (Linux) Unable to get information for
file file.
authorization to open the file, not being the file's
owner, or too many soft links to the file. If trying to
access a RAW partition, the server must be started with
superuser privileges.
ANR7807W (Solaris) Unable to get information for
file file.

authorization to open the file, not being the file's
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
loaded.
Explanation: The module indicated has been
successfully loaded. Operations involving this module
may now be performed by the server.
System action: The server now supports ACSLS
functions that depend on this module.
ANR7808W (AIX) root user authority required for
non-default scheduling policy.
Explanation: The server was unable to use the
scheduling policy specified in the options file. The
server must be running with root authority to use any
scheduling policy other than the default.
System action: Operation continues but with the
default scheduling policy.
User response: Run the server with root authority or
don't specify a scheduling policy in the options file.
ANR7808W (Windows) Sun Microsystems Library
Attach module module name is not
available from the system.
Explanation: The server attempted to load the Library
Attach module. However, this module is not installed
to the system.
without ACSLS function.
User response: Ensure that the Library Attach module
is installed to the system.
ANR7809I (AIX) Using scheduling policy policy.
Explanation: All threads in the server will use the
specified scheduling policy.
System action: Operations continue.
User response: None
ANR7810W (AIX) Unable to create a new child
process.
Explanation: The server cannot create a new child
thread.
System action: Server processing continues. Other
553
ANR7810E (HP-UX) ANR7812E (Solaris)

error messages from the server component are
displayed.
User response: Ensure that sufficient paging space is
available for AIX. If the server has been started from a
non-root user ID, ensure that the AIX process limit per
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
operation. Each thread started by the server is an AIX
process. To change the number of processes per user,
use the SMIT menus for System Environment, and
choose Change / Show Characteristics of Operating
System. You may also use SMIT to determine if the
number of applications is causing a memory shortage.
It may be necessary to decrease the maximum number
of client sessions by changing the MAXSESSIONS
option in the server options file.
ANR7810E (HP-UX) Error creating console input
thread.
Explanation: Unable to start console input thread.
User response: See other issued messages.
ANR7810E (Linux) Error creating console input
thread.
maximum number of client sessions by changing the

MAXSESSIONS option in the server options file.
ANR7811E (Linux) Insufficient memory for console
initialization.
Explanation: The server is unable to allocate enough
memory for console initialization.
User response: Ensure that there is sufficient paging
space. It may be necessary to reduce the maximum
number of client sessions by changing the
ANR7811E (Solaris) Insufficient memory for console
initialization.
space for Solaris. It may be necessary to reduce the
ANR7812E (HP-UX) Insufficient memory to buffer
console input. The following input line
was discarded: discarded console input.
Explanation: An error occurs during an attempt to
allocate a buffer to hold the specified console input.
System action: The console input is discarded.
ANR7810E (Solaris) Error creating console input

thread.

space for HP-UX. It may be necessary to reduce the

ANR7811I (AIX) Using instance directory instance
directory.
Explanation: The server is operating out of the
indicated directory.
ANR7811E (HP-UX) Insufficient memory for console
initialization.
space for HP-UX. It may be necessary to reduce the
554
ANR7812E (Linux) Insufficient memory to buffer

space. It may be necessary to reduce the maximum
ANR7812E (Solaris) Insufficient memory to buffer
ANR7813W (AIX) ANR7820E (AIX)

space for Sun Solaris. It may be necessary to reduce the
ANR7813W (AIX) The server mode-bit server is not
supported on a kernel mode-bit kernel.
Explanation: The 32-bit server is supported only when
running with the 32-bit kernel, and the 64-bit server is
supported only when running the 64-bit kernel.
User response: You must match the server mode with
the kernel mode by either switching the kernel mode or
installing the correct server fileset.
is running by executing 'mkfile' and then 'swap -a'. See

the Solaris man pages on 'mkfile' and 'swap' for more
details. If the server has been started from a non-root
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
number of number of users that can be on the system
at one time. This will also force the kernel to allocate
more memory/swap for user-processes. A system
reboot with the 'reconfigure' option is required for the
new user settings to take effect. It may be necessary to
decrease the maximum number of client sessions by
changing the MAXSESSIONS option in the server
options file.
ANR7814I (HP-UX) Using instance directory instance
directory.
ANR7813W (Linux) Unable to create a new child

thread.


thread.

displayed.
User response: Ensure that sufficient swap space is
available for Solaris. The amount of swap available can
be obtained by executing 'swap -l'. If the number of
free blocks is low, you can add swap files while the
system is running by executing 'mkfile' and then 'swap
-a'. See the Solaris man pages on 'mkfile' and 'swap' for
more details.
If the server has been started from a non-root user ID,
ensure that the process limit per user is sufficient to
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
more memory/swap for user-processes.
A system reboot with the 'reconfigure' option is
required for the new user settings to take effect. It may
be necessary to decrease the maximum number of
client sessions by changing the MAXSESSIONS option
in the server options file.
ANR7813W (Solaris) Unable to create a new child
thread.
thread.
displayed.

ANR7814I (Linux) Using instance directory instance
directory.
ANR7814I (Solaris) Using instance directory instance
directory.
ANR7820E (AIX) Insufficient memory to buffer
console input; the following input line
allocate a buffer large enough to read console input.
available for AIX. You may also use SMIT to determine
if the number of applications is causing a memory
shortage. It may be necessary to decrease the maximum
User response: Ensure that sufficient swap space is

available for Solaris. The amount of swap available can
be obtain by executing 'swap -l'. If the number of free
blocks is low, you can add swap files while the system
555
ANR7820S (HP-UX) ANR7822I (Linux)

ANR7820S (HP-UX) Server thread thread ID
terminated in response to program
abort.
Explanation: The thread has ended due to a program
abort.
System action: The server completes termination
processing.
User response: Note the associated messages and
ANR7820S (Linux) Thread thread ID terminated in
response to program abort.
abort.
processing.
User response: Note the associated messages and call
ANR7820S (Solaris) Server thread thread ID
terminated in response to program
abort.
abort.
processing.
User response: Note the associated messages and call
ANR7821I (Linux) Thread thread ID terminated in

response to external signal.
Explanation: The thread has ended due to an external
signal.
processing.
ANR7821I (Solaris) Server thread thread ID
terminated in response to external
signal.
signal.
processing.
ANR7821W (Windows) Unable to create directory
when creating volume file name.
Explanation: The server was attempting to create a file
with the indicated name. A new directory was being
created as well, but its creation failed.
System action: Server processing continues. The file
creation request fails.
User response: Specify a file name in an existing
directory or change the name request to specify a
different directory name.
ANR7822E (AIX) Error creating console input thread.
ANR7820W (Windows) Insufficient Space Available

for file file name.
with the indicated name. There was insufficient space
for the file on the disk.
User response: Free additional space on the drive to
accomodate the file, specify a file name on a drive with
sufficient space, or change the space request to a value
consistent with the drive. Retry the operation.

ANR7822I (HP-UX) Server thread thread ID
terminated in response to server
shutdown.
Explanation: The thread has ended due to a server
shutdown.
processing.
ANR7821I (HP-UX) Server thread thread ID

terminated in response to external
signal.

signal.
ANR7822I (Linux) Thread thread ID terminated in

response to server shutdown.

processing.

shutdown.

processing.
556
ANR7822I (Solaris) ANR7824W (Windows)

ANR7823W (Windows) Unable to create file file name.
ANR7822I (Solaris) Server thread thread ID

shutdown.
shutdown.
processing.

with the indicated name. The system reported an error
in creating the file.
System action: The server continues processing. The
file creation request fails.
User response: Specify a new file name.
ANR7824E (AIX) Error loading Async I/O support
module.

ANR7822W (Windows) File Already exists when
creating volume file name.
with the indicated name. The file already exists.
Explanation: The server attempted to load the Async

I/O support module, but the load failed. Refer to
accompanying error message for details on the load
failure.
without Async I/O support.
User response: Specify a new file name. The server

will not use an existing file name when creating a file.
User response: Ensure that the correct support

module exists in the server bin directory and that the
aio subsystem has been configured on AIX, and that
AIX was rebooted after the configuration.
ANR7823E (AIX) Insufficient memory for console

initialization.
ANR7824S (HP-UX) Server operation terminated.
Explanation: Unable to allocate enough memory for

console initialization.
Explanation: An error occurs that causes server

operation to stop.


ANR7824S (Linux) Server operation terminated.
operation to stop.
ANR7823S (Linux) Internal error internal error

detected.
Explanation: An internal error is detected during

server initialization or operation.
ANR7824S (Solaris) Server operation terminated.

operation to stop.
User response: Try the failing operation again. If the

operation fails again, review additional information
that is available for this message in the problem
determination section of the Tivoli Storage Manager
information center. Go to the Tivoli Storage Manager
information center (http://publib.boulder.ibm.com/
infocenter/tsminfo/v6r3/topic/com.ibm.itsm.nav.doc/
t_probdeterm.html) and type the message ID in the
Search field. Select a topic from the problem
determination section.

ANR7824W (Windows) Unable to write volume file
name.
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
system.
557
ANR7825E (Linux) ANR7831E (Solaris)

User response: Specify a new file name where there is
sufficient space.
ANR7825E (Linux) Server unable to allocate a shared
memory segment of size Client requested
shared memory size.
ANR7830E (Linux) 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.
Explanation: A shared memory client has requested a

shared memory segment size that Solaris is unable to
fulfill.
System action: Inform the user to use the right RAW

partition specification.
System action: Client is not allowed to logon
User response: Have user reenter the RAW partition

with the proper partition name.
User response: See the shared memory tuning guide

for Solaris (a Sun document). You may need to increase
the number/size of shared memory segments and/or
message queues.
ANR7825E (Solaris) Server unable to allocate a
shared memory segment of size Client
requested shared memory size.
Explanation: A shared memory client has requested a
shared memory segment size that Solaris is unable to
fulfill.
System action: Client is not allowed to logon
User response: See the shared memory tuning guide
for Solaris (an Oracle document). You may need to
increase the number/size of shared memory segments
and/or message queues.
ANR7825W (Windows) Unable to create volume file
name. Return code= return code.
with the indicated name. The attempt failed with the
indicated return code. The return code is an internal
code from the server.
User response: Specify a new file name. The return
code may also be provided to your service
representative for interpretation.
ANR7826W (Windows) Creation of Volume file name
failed. Process was cancelled.
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.
System action: Inform the user to use the right RAW
partition specification.
User response: Have user reenter the RAW partition
with the proper partition name.
ANR7831E (Linux) raw partition name has an existing
filesystem.
Explanation: The RAW partition specified has an
existing Solaris file system on it. Writing to this
Partition may/and most likely will destroy this
filesystem.
System action: Warn the user that an existing
filesystem for the raw partition specified may be
destroyed if written to.
User response: Determine if user still wants the valid
filesystem data. If not, user needs to destroy the
filesystem by either formatting the partition, create a
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
and ending blocks of a partition by using the Solaris
format() command. The user can read the format()
function in the Sun manuals for further details on
filesystems.

with the indicated name. The attempt was cancelled by
a cancel process command.
ANR7831E (Solaris) raw partition name has an existing

filesystem.


existing Solaris file system on it. Writing to this
partition will most likely destroy this filesystem.
User response: The DEFINE command may be

re-entered.
System action: Warn the user that an existing

filesystem for the raw partition specified may be
destroyed if written to.
User response: Determine if user still wants the valid
filesystem data. If not, user needs to destroy the
558
ANR7832I (AIX) ANR7834E (Solaris)

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
and ending blocks of a partition by using the Solaris
format() command. The user can read the format()
function in the Sun manuals for further details on
filesystems.
ANR7833E (Linux) symbolic links has too many

symbolic links - the maximum
allowable is 10.
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

indicated exit code. This error is due to the problem
caused and indicated by a preceding message.
processing.
ANR7832E (Linux) raw partition name corresponds to a
protected filesystem, such as / or /usr.
existing file system on it. This filesystem is the / or
/usr partition. If the SERVER writes to it, it will most
likely crash the whole operating system.
Explanation: The file specified has too many symbolic

links. The server will follow at most 10 links before
ending this symbolic link name resolution.
User response: Have the user specify the actual file,

where the file is not a symbolic link. Using ls -l, one
can see if the file is a symbolic link.
ANR7833E (Solaris) symbolic links has too many
symbolic links - the server only
supports a maximum of 10.
Explanation: The file specified has too many symbolic
links. The server will follow at most 10 links before
ending this symbolic link name resolution.
System action: Disallow access to this file
User response: Have the user specify the actual file,
where the file is not a symbolic link. Using ls -l, one
can see if the file is a symbolic link.
System action: Disallow access to this raw partition.

User response: Have user specify another RAW
partition that is not the / or /usr. It may be possible
that this is not the actual / or /usr partition of the boot
disk. Check, using the Solaris format() command, if
your partition name tag is labeled incorrectly as / or
/usr.
ANR7834I (AIX) The thread thread ID terminated in

signal.
processing.
ANR7832E (Solaris) raw partition name corresponds to

a protected filesystem, such as / or /usr.

existing file system on it. This filesystem is the / or
/usr partition. If the SERVER writes to it, it will most
likely crash the whole operating system.
ANR7834E (Linux) Specified raw partition name raw

partition cannot contain the 0th disk
cylinder.

User response: Have user specify another RAW
partition that is not the / or /usr. It may be possible
that this is not the actual / or /usr partition of the boot
disk. Check, using the Solaris format() command, if
your partition name tag is labeled incorrectly as / or
/usr.
ANR7833S (AIX) The process thread ID terminated in
response to program abort.
abort.
processing.
Explanation: The raw partition specified has the 0th

disk cylinder. The server should not be allowed to
write into the 0th cylinder. If allowed, the disk label
would be corrupted.
User response: Have the system administrator change
the starting cylinder of this partition to a number
greater than 0.
ANR7834E (Solaris) Specified raw partition name raw
partition cannot contain the 0th disk
cylinder.
Explanation: The raw partition specified has the 0th
disk cylinder. The server should not be allowed to
write into the 0th cylinder. It allowed, the disk label
would be corrupted.
559
ANR7834I (Windows) ANR7837S (Windows)

System action: Disallow access to this raw partition
the starting cylinder of this partition to a number
greater than 0.
ANR7834I (Windows) The server thread thread ID (tid
Windows NT thread ID) terminated in
Explanation: The thread has terminated due to an
external signal.
processing.
ANR7835I (Windows) The server thread thread ID (tid

Windows NT thread ID) terminated in
response to server shutdown.
Explanation: The thread has terminated due to a
server shutdown.
processing.
ANR7836S (AIX) Server initialization terminated.
initialization to end.
ANR7835I (AIX) The server thread thread ID

shutdown.
shutdown.
processing.
ANR7835E (Linux) Specified raw partition name raw
partition is too big for this operating
system to handle.
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
handle files natively more than 2GB. For operating
system that is at Solaris 2.6 or above, the limit is 1TB.
the RAW partition size to be less than 2GB (4194303
512-byte disk blocks) for Solaris 2.5.1 or below, less
than 1TB (2147483647 512-byte disk blocks) for Solaris
2.6 and above.

ANR7837S (AIX) Internal error internal error was
detected.
User response: You must extend the log file when you
receive ANR7837S, LOGSEG871 errors.
Try the failing operation again. If the operation fails
again, review additional information that is available
for this message in the problem determination section
of the Tivoli Storage Manager information center. Go to
the Tivoli Storage Manager information center
(http://publib.boulder.ibm.com/infocenter/tsminfo/
v6r3/topic/com.ibm.itsm.nav.doc/t_probdeterm.html)
and type the message ID in the Search field. Select a
topic from the problem determination section.
ANR7837S (Windows) Internal error internal error was
detected.
ANR7835E (Solaris) Specified raw partition name raw

partition is too big for this operating
system to handle.
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
handle files natively more than 2GB. For operating
system that is at Solaris 2.6 or above, the limit is 1TB.
System action: Disallow access to this raw partition
the RAW partition size to be less than 2GB (4194303
512-byte disk blocks) for Solaris 2.5.1 or below, less
than 1TB (2147483647 512-byte disk blocks) for Solaris
2.6 and above.
560
User response: You must extend the log file when you
receive ANR7837S, LOGSEG871 errors.
Review additional information that is available for this
message in the problem determination section of the
Tivoli Storage Manager information center. Go to the
Tivoli Storage Manager information center
(http://publib.boulder.ibm.com/infocenter/tsminfo/
v6r3/topic/com.ibm.itsm.nav.doc/t_probdeterm.html)
and type the message ID in the Search field. Select a
topic from the problem determination section.
ANR7838S (AIX) ANR7849I (AIX)

ANR7838S (AIX) Server operation terminated.
operation to stop.
ANR7841S (AIX) Insufficient kernel memory
available.
Explanation: An error occurs due to insufficient kernel
memory.
ANR7843W (Linux) Unable to determine real

memory size.
Explanation: The server checks the amount of real
memory in the system to optimize use of storage in the
database buffer pool. The server uses Object Data
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
size.
System action: Server operation continues. The server
allows the data base buffer pool size to grow withoug
taking into account real memory.
User response: The server may need to run as a root

user to obtain this information.
ANR7842S (AIX) Monitor kernel extension not

initialized.
ANR7843W (Solaris) Unable to determine real

memory size.
Explanation: The monitor kernel extension is not

initialized.

database buffer pool. The routines used to obtain this
information returned a failing return code or were
unable to return the real memory size.
ANR7843W (AIX) Unable to determine real memory

size.


database buffer pool. The server uses Object Data
Manager (ODM) to determine how much real memory
is installed on the system. The routines used to call
ODM failed or were unable to return the real memory
size.

ANR7843W (Windows) Unable to determine real
memory size.


ANR7843W (HP-UX) Unable to determine real

memory size.


ANR7849I (AIX) Server operation terminated - kernel

extension has been reset.

Explanation: The kernel extension has been

reinitialized by the server in response to a previous
condition for which a message has been issued.
561
ANR7850I (AIX) ANR7859W (Linux)

ANR7850I (AIX) The process process ID has
terminated on signal signal number (signal
name).
ANR7856W (Windows) The affinity mask (0xNT

return code.) was set to a value other than
what was requested
Explanation: The specified process has ended due to

the specified signal.
Explanation: A new affinity mask was set but on

verification it was found not to match what was
requested.


ANR7851S (AIX) Error resetting handler for signal

signal number (signal name).
ANR7859W (AIX) Error reading from standard input.
Explanation: An error occurs resetting the specified

signal handler.

read from standard input.
System action: The console input thread is terminated.
User response: This is normal if the server is running

as part of the installation, in a cron job, or is started in
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
unintended, stop the server and restart in the
foreground.
ANR7852I (Windows) The current process affinity

mask is: 0xThe process affinity mask..
Explanation: The server is running on the processors
indicated by the mask.
ANR7853W (Windows) Could not obtain the current
process affinity mask. Reason: NT return
code..
Explanation: A problem was encounterd while
obtaining the current process affinity.
ANR7854W (Windows) The process affinity mask
(0xAffinity mask.) specified in
dsmserv.opt is out of range.
Explanation: The affinity mask value was out of
range.
ANR7855W (Windows) Could not set new process
affinity mask. Reason: NT return code.
Explanation: A problem was encounterd in setting a
new process affinity mask.
ANR7859W (HP-UX) Error reading from standard

input.
foreground.
ANR7859W (Linux) Error reading from standard
input.
foreground.
562
ANR7859W (Solaris) ANR7861W (Solaris)

ANR7859W (Solaris) Error reading from standard
input.
ANR7860W (Solaris) Insufficient Space Available for

file file name.


for the file in the filesystem.

foreground.
ANR7860W (AIX) Insufficient Space Available for
file file name.
ANR7860W (HP-UX) Insufficient Space Available for
file file name.

ANR7861W (AIX) Unable to create directory when
directory or or change the name request to specify a
ANR7861W (HP-UX) Unable to create directory when
ANR7861W (Linux) Unable to create directory when
ANR7860W (Linux) Insufficient Space Available for

file file name.






ANR7861W (Solaris) Unable to create directory when

563
ANR7862W (AIX) ANR7864W (HP-UX)

ANR7862W (AIX) File Already exists when creating
volume file name.
ANR7863W (HP-UX) Unable to create file file name.

ANR7863W (Linux) Unable to create file file name.
ANR7862W (HP-UX) File Already exists when


ANR7863W (Solaris) Unable to create file file name.




ANR7862W (Linux) File Already exists when creating

volume file name.
ANR7862W (Solaris) File Already exists when
ANR7864W (AIX) Unable to write volume file name.

system.
sufficient space.

ANR7864W (HP-UX) Unable to write volume file

name.



ANR7863W (AIX) Unable to create file file name.

system.
sufficient space.

564
ANR7864W (Linux) ANR7866W (Linux)

ANR7864W (Linux) Unable to write volume file name.
system.
sufficient space.
ANR7864W (Solaris) Unable to write volume file
name.
system.
sufficient space.
ANR7865W (AIX) Unable to create volume file name.
Return code=return code.
indicated return code. The return code is an the server
internal code.
ANR7865W (HP-UX) Unable to create volume file
name. Return code=return code.
indicated return code. The return code is a server
internal code.
ANR7865W (Linux) Unable to create volume file

ANR7865W (Solaris) Unable to create volume file
indicated return code. The return code is a server
internal code.
ANR7866W (AIX) Creation of Volume file name
re-entered.
ANR7866W (HP-UX) Creation of Volume file name
re-entered.
ANR7866W (Linux) Creation of Volume file name
re-entered.

indicated return code. The return code is an internal
code from the server.
565
ANR7866W (Solaris) ANR7871W (AIX)

ANR7866W (Solaris) Creation of Volume file name
re-entered.
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
random access file with the indicated name. The usable
space was rounded down to the indicated value so that
the amount of space is an even multiple of the disk
block size. This facilitates improved performance in
reading and writing the file.
System action: The server continues processing. Some
space in the file will go unused.
User response: No action is required. To use all space
in the file, server utilities can be used to offload
existing data to other volumes. The volume can then be
deleted and re-created using a multiple of the disk's
block size.
ANR7867I (HP-UX) file name is not a multiple of disk
usable file size.
block size.
ANR7867I (Linux) file name is not a multiple of disk
usable file size.
566

block size.
ANR7867I (Solaris) file name is not a multiple of disk
usable file size.
block size.
ANR7870W (AIX) Unable to initialize odm query.
Error message from odm is odm message.
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
real memory is installed on the system. The routine
used to initialize an ODM query failed. ODM returned
an error message as indicated.
makes assumptions concerning information it could not
obtain.
ANR7871W (AIX) Unable to complete odm query.
Error message from odm is odm message.
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
real memory is installed on the system. The routine
used to perform and ODM query failed. ODM returned
an error message as indicated.
makes assumptions concerning information it could not
obtain.
ANR8195I (AIX) ANR8198E (Windows)

ANR8195I (AIX) The SSL TCP/IP Version 4 driver is
ready for 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
port number.
User response: If necessary, restart the server with a

smaller window size in the options file. To determine
the setting of the server window size
(TCPWindowsize), issue the QUERY OPTION
command.
ANR8198E (AIX) The SSL environment was not
established. The GSK module gsk module
return code is gsk return code.
Explanation: Initialization of the SSL environment has
failed. Connections to SSL ports are not possible.
ANR8195I (Windows) The SSL TCP/IP Version 4

driver is ready for connection with
clients on port port number.
port number.
User response: Stop and restart the server.

ANR8198E (HP-UX) The SSL environment was not

ANR8196I (AIX) The SSL TCP/IP administrative
administrative clients using the SSL TCP/IP protocol
on the indicated port number.
ANR8198E (Linux) The SSL environment was not

ANR8196I (Windows) The SSL TCP/IP

administrative driver is ready for
connection with clients on port port
number.
ANR8198E (Solaris) The SSL environment was not


ANR8197W (HP-UX) A TCP/IP driver is unable to set
the window size to TCPWindowsize for a
master socket on which the server
listens. The server will use the default
window size for listening to sessions.
Explanation: The reason that the window size cannot
be set to the requested size might be due to a lack of
memory for TCP/IP buffers.

ANR8198E (Windows) The SSL environment was not
System action: Server operation continues with the

default window size.
567
ANR8199E (AIX) ANR8201W (AIX)

ANR8199E (AIX) The SSL TCP/IP driver was not
initialized on port port number.
Explanation: A problem with the SSL environment
prevents Tivoli Storage Manager from establishing the
SSL protocol on the indicated port number.
User response: None
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
with clients using the TCP/IP Version 4 protocol on the
indicated port number.
ANR8199E (HP-UX) The SSL TCP/IP driver was not

User response: None
ANR8199E (Linux) The SSL TCP/IP driver was not
User response: None
ANR8200I (Linux) TCP/IP Version 4 driver ready for

number.
clients using the TCP/IP Version 4 protocol on the
ANR8200I (Solaris) TCP/IP Version 4 driver ready
number.
ANR8199E (Solaris) The SSL TCP/IP driver was not

User response: None
ANR8199E (Windows) The SSL TCP/IP driver was
not initialized on port port number.

ANR8200I (Windows) TCP/IP Version 4 driver ready
number.
ANR8201W (AIX) Unable to initialize TCP/IP driver
- insufficient memory.
User response: None
Explanation: Because the operating system rejects a

memory allocation request, the server cannot start
communications through TCP/IP.
ANR8200I (AIX) TCP/IP Version 4 driver ready for

number.

server cannot accept sessions from clients using the
TCP/IP protocol.



568
ANR8201E (HP-UX) ANR8202E (Linux)

ANR8201E (HP-UX) Unable to initialize TCP/IP
driver - socket creation failed; error error
code.
ANR8202W (AIX) Unable to initialize TCP/IP driver

- error creating acceptor socket. Reason
code reason code.
Explanation: The server is unable to initialize the

TCP/IP driver due to a socket creation error.
Explanation: Because TCP/IP rejects a request for a

socket on which to listen, the server cannot start

TCP/IP support is inoperative.
User response: Ensure that TCP/IP is operational on
your system by using the ping command with your
TCP/IP address as a target. If TCP/IP is not active on
your system, you must activate it; then halt and restart
the server.
ANR8201E (Linux) Unable to initialize TCP/IP driver
- socket creation failed; error error code.
the server.
ANR8201E (Solaris) Unable to initialize TCP/IP
driver - socket creation failed; error error
code.
the server.
ANR8201W (Windows) Unable to initialize TCP/IP
driver - insufficient memory.
Explanation: The server is unable to communicate by
way of TCP/IP. A memory allocation request has been
rejected by the operating system.
TCP/IP protocol.
User response: Ensure that there is sufficient space for
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
instructions on how to increase the amount of virtual
memory.

TCP/IP protocol.
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.
driver - socket bind operation for port
TCP port number failed; error error code.
TCP/IP driver due to a socket binding error.
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
dsmserv.opt file TCPPort option is different for each
server.
ANR8202E (Linux) TCP/IP driver unable to initialize
due to error in using port TCP port
number; error error code.
server. Make sure TCPPORT and TCPADMINPORT do
not specify or default to the same values.
569
ANR8202E (Solaris) ANR8204W (AIX)

driver - socket bind operation for port
TCP port number failed; error error code.

the server.


- listen operation failed; error error code.

server.

TCP/IP driver due to a socket listen error.
ANR8202W (Windows) Unable to initialize TCP/IP

driver - error creating acceptor socket.
Reason code reason code.
Explanation: The server is unable to communicate by
way of TCP/IP. TCP/IP has rejected a request for a
socket on which the server listens.
TCP/IP protocol.
issue the HALT command to stop the server, and then
restart the server.
ANR8203W (AIX) Unable to establish TCP
connection - accept error.
Explanation: The server cannot accept a client session
due to a failure in TCP/IP.
TCP/IP protocol.
use the HALT command from a server prompt to
terminate the server and restart it.
driver - listen operation failed; error
error code.
570

the server.
driver - listen operation failed; error
error code.
the server.
ANR8203W (Windows) Unable to establish TCP
connection - accept error.
due to failure in TCP/IP.
TCP/IP protocol.
issue the HALT command to stop the server, and then
restart the server.
connection - insufficient memory.
due to a memory allocation request failure.
session request for this session fails.
ANR8204E (HP-UX) ANR8205W (Windows)

shortage. You may also decrease the maximum number
of sessions that the server can accept with the

connection - server HALT in progress.
due to server HALT processing that is in progress.

driver - thread creation failed.


TCP/IP driver due to an error creating a server thread.

ANR8205E (HP-UX) Terminating TCP/IP driver accept operation failed; error error code.
User response: This error often results from a lack of

memory. Ensure that your system has sufficient paging
space to support the current activities.

TCP/IP driver due to a socket accept error.

- thread creation failed.
driver - thread creation failed.
Explanation: The server is unable to accept a client
session due to a memory allocation request failure.
User response: Ensure that there is sufficient space for
the Windows paging file. Click on the system icon in
the Windows control panel and then click on the
memory. You may also wish to cut down on the
maximum number of sessions that the server can
accept with the MAXSESSIONS option in the server
options file.

the server.
ANR8205E (Linux) Terminating TCP/IP driver socket accept operation failed; error error
code.
the server.
ANR8205E (Solaris) Terminating TCP/IP driver socket accept operation failed; error error
code.
the server.
Explanation: The server is unable to accept a client
session due to server HALT processing that is in
progress.
571
ANR8206W (AIX) ANR8207E (Solaris)

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.
session is ended.
ANR8206I (Windows) TCP/IP Version 4

administrative driver ready for
number.
administrative clients using the TCP/IP Version 4
protocol on the indicated port number.
ANR8207W (AIX) TCP/IP driver unable to initialize

due to socket initialization error. Reason
code reason code.
ANR8206E (HP-UX) Unable to establish TCP/IP

session - invalid host address IP host
address (port port number).
Explanation: While initializing TCP/IP

communications, the server fails to set up an interface
with TCP/IP.
Explanation: The server is unable to establish a

session because the designated address or port number
is not valid.

TCP/IP protocol.
User response: Ensure that TCP/IP has been started

and is active on your system. You may issue the
TCP/IP ping command to your own address to verify
that TCP/IP is both started and active.
User response: Ensure that the specified host name is

valid and is accessible over the network. If the
TCPCLIENTPort option is specified for the remote
system, ensure it does not conflict with another
application.
ANR8206E (Linux) Unable to establish TCP/IP
is not valid.
application.
ANR8206E (Solaris) Unable to establish TCP/IP
is not valid.
application.
572

session with IP host address due to
memory shortage.
session because of a memory shortage condition.
User response: Ensure that your system has sufficient
paging space to support the current level of system
activities.
memory shortage.
activities.
memory shortage.
ANR8207W (Windows) ANR8209W (AIX)

activities.
ANR8207W (Windows) TCP/IP driver unable to
initialize due to socket initialization
error. Reason code reason code.
communications, the server has failed to set up an
interface with TCP/IP for Windows.
TCP/IP protocol.
User response: Ensure that TCP/IP is properly
installed on your system. Ensure that TCP/IP has been
started on your system. Issue the TCP/IP ping
command to your own address to verify that TCP/IP is
both installed and active.
due to error in using port port, reason
code reason code.
communications, the server fails to connect to a master
socket on which to listen for clients. The reason code is
the return code from the TCP/IP bind API.
TCP/IP protocol.
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.
session with IP host address - socket
creation failed; error error code.
session because of a socket creation error.
the server.

the server.
the server.
initialize due to error in using Port port,
reason code reason code.
communications, the server has failed to connect to a
master socket on which to listen for clients. The reason
code is the return code from the TCP/IP bind API.
TCP/IP protocol.
file with the TCPPORT option. If the server is brought
down and then started immediately, you may be within
the TCP/IP one minute timeout period for port
reusage. Bring down the server, wait one minute, and
then restart the server. If that does not work, it may be
necessary to restart Windows.
due to error in LISTENing on the
specified Port, reason code reason code.
Explanation: While attempting to listen for session
requests from clients using TCP/IP, TCP/IP returns an
error. The reason code is the return code from the
TCP/IP listen API.
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
possible to bring the server down and restart it to
573

allow additional client sessions to start.
session with IP host address - connection
refused.
session because the remote system refused the
connection request.
User response: Ensure that the specified remote
system is operational and is properly configured to run
TCP/IP. Ensure that the client options file specifies the
correct TCPServeraddress and TCPPort of the server
you are attempting to contact.
refused.
connection request.

properly. This may be done by issuing the TCP/IP
netstat -s and ping commands to other nodes on your
network. It may be possible to correct this condition by
restarting the server.
ANR8210W (AIX) TCP/IP driver is terminating due
to error in accepting a new session,
Explanation: While attempting to accept a session
request from a client using TCP/IP, TCP/IP returns an
TCP/IP accept API.
network. It may be possible to bring the server down
and restart it to allow additional client sessions to start.
request timed out.
session because the remote system did not respond to
the connection request.

refused.
connection request.
initialize due to error in LISTENing on
the specified Port, reason code reason
code.
TCP/IP listen API.
574
User response: Ensure the following:

v The specified remote system is operational and is
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.
request timed out.
properly.
ANR8210E (Solaris) ANR8212W (AIX)

request timed out.
properly.
ANR8210W (Windows) TCP/IP driver is terminating
due to error in accepting a new session,
request from a client using TCP/IP, TCP/IP returns an
TCP/IP accept API.

TCP/IP. Also, ensure that necessary gateways and
routers are functioning properly.
session with IP host address system/network unreachable.
session because the remote system or network is
unreachable.
unreachable.
ANR8211W (Windows) TCP/IP driver is terminating
due to error in creating a new thread.
ANR8211W (AIX) TCP/IP driver is terminating due

to error in creating a new thread.
Explanation: The server cannot initialize due its

inability to create a new thread of execution.
Explanation: The server cannot initialize due to the


TCP/IP communications is inoperative.

TCP/IP communications is inoperative.
User response: The most likely cause is a lack of

memory. Ensure that there is sufficient space for the
Windows paging file. Click on the system icon in the
Windows NT control panel and then click on the
options file.

memory. Ensure that sufficient paging space is available
for AIX. You may also use SMIT to determine if the
You may also decrease the maximum number of
sessions that the server can accept with the
ANR8212W (AIX) Unable to resolve address for node

name.

unreachable.
Explanation: The server attempts to obtain a TCP/IP

address for the indicated node name. The attempt is
unsuccessful.
575
ANR8212E (HP-UX) ANR8213W (Windows)

System action: The attempt to communicate with the
indicated node fails. Server operation continues.
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 - connect
failed; error error code.
session because of a connection error.
TCP/IP.
TCP/IP.
ANR8213W (AIX) Session open with node name timed

out.
Explanation: The server attempts to contact the
indicated node name. The attempt is unsuccessful.
indicated node fails.
ANR8213E (HP-UX) Session Session identifier aborted
due to send error; error error code.
Explanation: The session between the server and the
specified client system experienced a disruptive error
sending data.
System action: The session with the remote system is
ended.
TCP/IP.
ANR8213E (Linux) Socket Socket identifier aborted due
to send error; error error code.
specified client system experienced a fatal error sending
data.


ended.


TCP/IP.

TCP/IP.
ANR8212W (Windows) Unable to resolve address for
node name.
unsuccessful.
ANR8213E (Solaris) Socket Socket identifier aborted

due to send error; error error code.
specified client system experienced a fatal error sending
data.
ended.
TCP/IP.
ANR8213W (Windows) Session open with node name
timed out.
indicated node name. The attempt is unsuccessful.
576
ANR8214E (AIX) ANR8215E (Linux)

ANR8214E (AIX) Session open with IP host address
failed due to connection refusal.
connection request.
ANR8214E (HP-UX) The session stopped when no
data was read on socket socket number.
Explanation: The server is unable to read data on the
indicated socket. This might be a normal event if either
side of the connection is abruptly ended.
continues.
intentionally stopping either the client or server, no
response is required. Otherwise, ensure that the client
and server can communicate through such means as
Telnet or FTP applications, which are part of the
TCP/IP suite.
ANR8214E (Linux) Session terminated when no data
was read on socket socket number.
indicated socket. This may be a normal event if either
continues.
TCP/IP suite.
ANR8214E (Solaris) Session terminated when no
data was read on socket socket number.
continues.

TCP/IP suite.
ANR8214E (Windows) Session open with IP host
address failed due to connection refusal.
connection request.
ANR8215W (AIX) Session open with IP host address
failed as unreachable.
session because the remote system is unreachable.
User response: Ensure that the IP host address is
properly specified and that it is accessible over the
network. Use the TCP/IP ping command for this
purpose.
ANR8215E (HP-UX) Session Session identifier aborted
due to receive error; error error code.
specified client system experienced a disruptive error
receiving data.
ended.
TCP/IP.
ANR8215E (Linux) Session Session identifier aborted
specified client system experienced a fatal error
receiving data.
ended.
TCP/IP.

577
ANR8215E (Solaris) ANR8217W (HP-UX)

ANR8215E (Solaris) Session Session identifier aborted
specified client system experienced a fatal error
receiving data.
ended.
TCP/IP.
ANR8215W (Windows) Session open with IP host
address failed as unreachable.
session because the remote system is unreachable.
User response: Ensure that the IP host address is
properly specified and that it is accessible over the
network. Use the TCP/IP ping command for this
purpose.
ANR8216W (AIX) The server experienced a TCP/IP
error while sending data on socket socket
number. Reason return code.
Explanation: A communication error occurred on the
continues.
action is required. Otherwise, ensure that the client and
server can communicate using Telnet or FTP
applications, which are part of the TCP/IP suite.
session with IP host address due to thread
creation error.
session because of an error creating a thread.
activities.
creation error.

activities.
creation error.
activities.
ANR8216W (Windows) Error sending data on socket
socket number. Reason return code.
Explanation: The server experiences an error return
code from TCP/IP while sending data over the
continues.
TCP/IP suite.
error while receiving data on socket
socket number. Reason return code.
Explanation: A communication error occurred on the
continues.
ANR8217W (HP-UX) TCP/IP driver is unable to set
the window size to TCPWindowsize for
client client. The default value will be
used.

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
indicated session. There may be a lack of memory for
TCP/IP buffers.
System action: Server operation continues and the
578
ANR8217W (Linux) ANR8218W (Solaris)

session continues with the default window size.
User response: Retry the session with a smaller
window size in the options file. Issue the QUERY
OPTION command to determine the setting of the
server TCPWindowsize.
ANR8217W (Linux) Unable to initialize TCP/IP
TCP/IP protocol.
available for Solaris. You may also use ps -ef to
determine if the number of applications is causing a
memory shortage. It may be necessary to decrease the
ANR8217W (Solaris) Unable to initialize TCP/IP
TCP/IP protocol.
available for Solaris. You may also use ps -ef to
ANR8217W (Windows) Error receiving data on
socket socket number. Reason return code.
code from TCP/IP while receiving data on the
continues.
TCP/IP suite.
ANR8218W (AIX) Session terminated when no data

was read on socket socket number.
continues.
TCP/IP suite.
ANR8218W (HP-UX) TCP/IP driver is unable to use
the TCP/IP NODELAY option for client
client.
Explanation: The server cannot set TCP/IP NODELAY
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.
session continues with the delay processing on.
User response: Further details for use in contacting
your service representative can be obtained by issuing
the following trace commands from an administrative
session or from the server console (proper
administrative authority is required): TRACE ENABLE
TCPINFO TRACE BEGIN tcptrace.out. After a session
starts and displays message ANR8218W, issue the
following commands: TRACE FLUSH TRACE END.
This will create trace data in file tcptrace.out and will
terminate the trace. This file should be supplied to your
server representative on request.
ANR8218W (Linux) Unable to resolve address for
node name.
unsuccessful.
ANR8218W (Solaris) Unable to resolve address for
node name.
unsuccessful.
579

ANR8218W (Windows) Session terminated when no
data read on socket socket number.
Explanation: The server cannot read on the indicated
socket. This may be a normal event if either side of the
connection is abruptly ended.
continues.
TCP/IP suite.
ANR8219W (AIX) TCP/IP driver is unable to accept a
new session with client at address
TCP/IP address due to an error in creating
a new thread.
with the client at the indicated address due to an
inability to create a new thread.
System action: Server operation continues, the session
request fails.
User response: The most likely cause is lack of
for AIX. You may also use SMIT to determine if the
ANR8219W (HP-UX) Unable to initialize TCP/IP
TCP/IP protocol.
available for HP-UX. You may also use SMIT to
ANR8219W (Linux) Unable to establish TCP

available for Solaris. You may also use 'swap -l' to
determine the amount of swap available. You may also
decrease the maximum number of sessions that the
server can accept with the MAXSESSIONS option in
ANR8219W (Solaris) Unable to establish TCP
available for Solaris. You may also use 'swap -l' to
determine the amount of swap available. You may also
decrease the maximum number of sessions that the
ANR8219W (Windows) TCP/IP driver is unable to
accept a new session due to error in
creating a new thread.
due to the inability to create a new thread.
request fails.
memory. You may also wish to to cut down on the
options file.
ANR8220W (AIX) TCP/IP driver is unable to set the
window size to TCPWindowsize for client
client. The default value will be used.
TCP/IP buffers.
580
ANR8220W (HP-UX) ANR8221W (Linux)

ANR8220W (HP-UX) Unable to establish TCP
available for HP-UX. You may also use SMIT to
memory shortage. You may also decrease the maximum
number of sessions that the server can accept with the
ANR8220W (Linux) TCP/IP driver is unable to set
used.
TCP/IP buffers.
ANR8220W (Solaris) TCP/IP driver is unable to set
used.
TCP/IP buffers.

contact node name due to an output
socket initialization error. Reason code
reason code
indicated node name. The attempt is unsuccessful due
to the inability to initialize a local socket.
User response: Ensure that TCP/IP is operating
properly on this node and that it can communicate
remotely. Use the TCP/IP ping command for this
purpose.
ANR8221W (AIX) TCP/IP driver is unable to use the
TCP/IP NODELAY option for client
client.
TCPINFO TRACE BEGIN. After a session starts and
displays message ANR8221W, issue the commands
TRACE FLUSH TRACE END. This will create trace
data in file tcptrace.out and will terminate the trace.
This file should be supplied to your service
representative on request.
ANR8221I (HP-UX) TCP/IP Version 4 administrative
driver ready for connection with clients
on port port number.
ANR8221W (Linux) TCP/IP driver is unable to use
client.
TCP/IP delay processing in effect. This causes TCP/IP
session continues with delay processing on.
581
ANR8221W (Solaris) ANR8222W (Windows)

User response: Further details for use when
contacting your service representative can be obtained
by issuing the following trace commands from an
administrative session or from the console (proper
TCPINFO TRACE BEGIN tcptrace.out. After a session
following commands: TRACE FLUSH TRACE END.
service representative on request.
ANR8221W (Solaris) TCP/IP driver is unable to use
client.
TCPINFO TRACE BEGIN tcptrace.out After a session
following commands: TRACE FLUSH TRACE END
window size for listening for sessions. There may be a

lack of memory for TCP/IP buffers.
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.
ANR8222W (HP-UX) The TCP/IP administrative
driver was unable to initialize due to
error using Port port, reason code reason
code.
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
bind API.
server cannot accept administrative sessions from
clients using the TCP/IP protocol. This also includes
server-server sessions, storage agent to server sessions,
and library client to server sesssions.
file with the TCPADMINPORT option. If the server was
brought down and client sessions were active, it can be
necessary to end the client sessions on the client
systems before the port can be freed.
ANR8222W (Linux) Unable to establish TCP

set the window size to TCPWindowsize
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.

memory for TCP/IP buffers. You may retry with a
smaller TCP window size in the options file. You can
issue the QUERY OPTION command to display the
current setting of the TCP window size.
window size to TCPWindowsize for the
server master socket. The default value
will be used.
for the socket on which the server listens to the
requested size shown. The server uses the default
582

ANR8222W (Solaris) Unable to establish TCP

use the TCP/IP NODELAY option for
client client.
ANR8223W (AIX) ANR8224W (AIX)

TCPINFO TRACE BEGIN tcptrace.out After a session
following commands: TRACE FLUSH TRACE END
ANR8223W (AIX) Unable to connect to remote
system RemoteSystem due to unexpected
return code ReturnCode
Explanation: The server was unable to connect to a
remote system due to an unexpected return code from
the connect Application Programming Interface.
Common return code are handled with specific
messages. This return code was unexpected.
System action: Server operation continues but the
connection to the remote system fails.
User response: TCP/IP return code are listed in file
/usr/include/sys/errno.h and may provide a pointer
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
accept a new session with the client at
address TCP/IP address, due to an error
in creating a new thread.
session request fails.
User response: The cause is probably lack of memory.
Ensure that sufficient paging space is available for AIX.
You might also use SMIT to determine if the number of
applications is causing a memory shortage. You might
also decrease the maximum number of sessions that the
ANR8223W (Linux) TCP/IP driver is unable to accept
a new session with client at address
TCP/IP address due to an error in creating
a new thread.

request fails.
for Solaris. You may also use ps -ef to determine if the
ANR8223W (Solaris) TCP/IP driver is unable to
accept a new session with client at
address TCP/IP address due to an error in
creating a new thread.
request fails.
for Solaris. You may also use ps -ef to determine if the
ANR8223W (Windows) Failed to connect to system at
address address port port.
Explanation: The server attempted to contact the
indicated node name at the specified port. The attempt
is unsuccessful. The target port is not valid at the target
node.
User response: Ensure that the node name still has
TCP/IP running and that the client is active in
SCHEDULE mode. If the server is attempting contact
with the SNMP subagent, ensure that the hostname and
port number for the subagent is correct in the server
options file.
ANR8224W (AIX) TCP/IP Administrative driver was
unable to initialize due to error in using
port port, reason code reason code.
has failed to connect to a master socket on which to
listen for clients. The reason code is the return code
from the TCP/IP bind API.
server to server sessions, storage agent to server
sessions, and library client to server sesssions.
583
ANR8224E (HP-UX) ANR8225W (Linux)

file with the TCPADMINPORT or TCPPORT options. 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.
ANR8224E (HP-UX) The server is unable to open the
file due to the system limit .
Explanation: An error occurs when the server
attempts to open a file.
System action: Server operation continues, but files
cannot be opened until the problem is fixed.
User response: Use the System Administrator
Manager (SAM) program to increase the value of the
maxfiles parameter. This value determines the
maximum number of files a process is allowed to open
at one time. For proper server operation, increase the
maxfiles value to at least 512.
ANR8224W (Linux) TCP/IP driver is unable to set
the server master socket. The default
value will be used.
ANR8224W (Solaris) TCP/IP driver is unable to set
the server master socket. The default
value will be used.
584
ANR8224W (Windows) TCP/IP Administrative driver

was unable to initialize due to error in
using Port port, reason code reason code.
sessions, and library client to server sessions.
file with the TCPADMINPORT option. If the server is
brought down and then started immediately, you can
be within the TCP/IP one minute timeout period for
port reusage. Bring down the server, wait one minute,
and then restart the server. If that does not work, it
may be necessary to restart Windows.
ANR8225I (AIX) TCP/IP Version 4 administrative
ANR8225W (Linux) TCP/IP Administrative driver
using port port, reason code reason code.
active, it may be necessary to terminate the client
freed.
ANR8225I (Solaris) ANR8227W (Linux)

ANR8225I (Solaris) TCP/IP Version 4 administrative
ANR8225I (Windows) TCP/IP Version 6 driver ready
number.
ANR8226E (AIX) Error errno detecting version of
HBA-API library.
Explanation: The server attempted to determine the
level of the devices.common.IBM.fc.hba-api fileset and
encountered an error.
without accurate SAN device mapping.
ANR8226I (Linux) TCP/IP Version 4 administrative
ANR8226W (Solaris) TCP/IP Administrative driver
using port port, reason code reason code.
Explanation: The TCP/IP administrative driver was
unable to initialize due to an error in running the BIND
API to port port, reason code reason code.
server-server sessions, storage agent to server sessions,

and library client-server sesssions.
active, it can be necessary to terminate the client
freed.
ANR8226W (Windows) Unable to initialize
NETBIOS driver on adapter network
adapter number.
Explanation: The server cannot obtain sufficient
NETBIOS resources to initialize communications on the
indicated network adapter.
server will not accept sessions from clients that use the
NETBIOS protocol.
User response: Ensure that NETBIOS is configured on
the system. Ensure that all NETBIOS resources are not
already in use. If the LAN Server or LAN Requester
application is running, you have NETBIOS configured.
In that case, starting the server prior to starting LAN
Server or LAN Requester may allow the server to
obtain the necessary NETBIOS resources.
ANR8227E (AIX) Fileset devices.common.IBM.fc.hbaapi is not at the required level.
Explanation: The specified fileset is at a level that is
incompatible with TSM operations. Install the latest
maintenance for this fileset if you use SAN devices.
without accurate SAN device mapping.
ANR8227W (Linux) Unable to connect to remote
/usr/include/asm/errno.h and may provide a pointer
to the underlying problem.

585
ANR8227W (Solaris) ANR8230W (Windows)

ANR8227W (Solaris) Unable to connect to remote
is the presence of another system on the network that

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
options file and restarting the server may allow this
adapter to be used with NETBIOS communications.

ANR8230I (AIX) TCP/IP Version 6 driver ready for

number.

/usr/include/sys/errno.h and may provide a pointer
to the underlying problem.

ANR8227W (Windows) NETBIOS connection

terminated - insufficient memory,
network adapter network adapter number.
Explanation: The server cannot listen for client
sessions on the specified network adapter due to a
memory allocation request failure.
sessions will not be accepted on the specified adapter.
Other network adapters remain unaffected.
memory.
ANR8228W (Windows) NETBIOS connection
terminated - server HALT in progress.

ANR8230I (HP-UX) The TCP/IP Version 6 driver is
port port number.
with clients using the TCP/IP Version 6 protocol on the
ANR8230I (Linux) TCP/IP Version 6 driver ready for
number.
ANR8230I (Solaris) TCP/IP Version 6 driver ready

number.
ANR8229W (Windows) Unable to add server name

server name to adapter network adapter
number.

Explanation: The server cannot initialize

communications processing using the NETBIOS
protocol on the indicated network adapter because the
server name cannot be added as a NETBIOS name on
the adapter.
System action: Server operation continues, but client

sessions from clients using the NETBIOS protocol will
not be accepted on this adapter. Other adapters are not
affected.
User response: The most likely cause for this message
586

ANR8230W (Windows) Insufficient memory to start
NETBIOS session on adapter network
adapter number.
due to a memory allocation request failure on the
specified adapter.
ANR8231W (Windows) ANR8233E (Solaris)

accept with the MAXSESSIONS or the
NETBIOSSESSIONS option, or both, in the server
options file.
ANR8231W (Windows) Unable to create thread to
accept NETBIOS sessions.
NETBIOS communications is inoperative.
options file.
listen for NETBIOS sessions on adapter
network adapter number.
inability to create a new thread of execution to monitor
the indicated network adapter.
NETBIOS communications is inoperative on the
indicated adapter. Other adapters remain unaffected.
options file.
ANR8233E (AIX) Unable to acquire local port

information. getaddrinfo return code
return code.
Explanation: The server or storage agent used the
system getaddrinfo API to determine which TCP/IP
protocols could be used. A failure occurred, as
indicated by the system error code that is shown. The
server was initializing TCP/IP communications.
System action: TCP/IP communications is inoperatve.
User response: System information concerning return
codes from the getaddrinfo system API should be
consulted. Ensure that TCP/IP networking for either
TCP/IP version 4 or version 6 is operating correctly.
ANR8233E (HP-UX) Unable to acquire local port
return code.
ANR8233E (Linux) Unable to acquire local port
return code.
ANR8233E (Solaris) Unable to acquire local port
return code.
587
ANR8233W (Windows) ANR8236W (Windows)

handle NETBIOS session session number
on adapter network adapter number.
Explanation: The server cannot start a new client
session on the indicated adapter due to an inability to
start a separate thread of execution for the indicated
session.
System action: Server operation continues, but this
options file.
ANR8234I (AIX) TCP/IP Version 6 administrative
ANR8234I (HP-UX) The TCP/IP Version 6
administrative driver is ready for
number.
ANR8234I (Linux) TCP/IP Version 6 administrative
588
ANR8234I (Solaris) TCP/IP Version 6 administrative

ANR8234I (Windows) TCP/IP Version 6
administrative driver ready for
number.
ANR8235W (Windows) Requested number of
NETBIOS sessions are not available on
adapter network adapter number,
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
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.
User response: Ensure that the required number of
NETBIOS resources are not already in use. If the LAN
Server or LAN Requester application is running, you
have NETBIOS configured. In that case, starting the
server prior to starting LAN Server or LAN Requester
may allow the server to obtain the requested NETBIOS
resources.
ANR8236W (Windows) Failure while listening for
NETBIOS sessions on adapter network
adapter number, NETBIOS listen return
code=listen return code.
Explanation: The server cannot listen for NETBIOS
sessions on the indicated adapter. The indicated listen
return code was received from the NETBIOS listen API.
If the return code is 24, (hex 18), the listen is retried.
System action: Server operation continues. If the
return code is 24 (hex 18), a new listen is setup because
return code 24 indicates a temporary failure. Otherwise,
no additional NETBIOS sessions will start using the
ANR8237E (Windows) ANR8264W (Windows)

indicated adapter until the problem is corrected and the
server is restarted.
System action: Server operation continues. Named

Pipes communications is inoperative.
User response: A NETBIOS listen failure is an

indication of a network problem, an adapter problem,
or a NETBIOS configuration problem. The following
system configuration and system environment listen
return codes (in hex) and resolution actions for a listen
failure are found in the IBM Local Area Network
Technical Reference:

options file.
Return Code Description

11
The local session table is full. The
maximum number of sessions are in
use. Change NETBIOS configuration to
increase the maximum number of
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.
The maximum number of sessions are in
use. Change NETBIOS configuration to
increase the maximum number of
sessions.
35
The operating system resources are
exhausted. A reboot is probably
required.
ANR8237E (Windows) Unable to acquire local port

return code.
server was initialize TCP/IP communications.
ANR8260I (Windows) Named Pipes driver ready for
connection with clients.
with clients using the Named Pipes protocol.
ANR8261W (Windows) Named Pipes connection
terminated - insufficient memory.
ANR8262W (Windows) Named Pipes driver is

terminating due to error in creating a
new thread.
System action: Server operation continues, but Named
Pipes communications is inoperative.
options file.
ANR8263W (Windows) Error sending data on Named
Pipes, session session number.WriteFile
Return code is return code.
code from the WriteFile Windows NT API while
writing data to Named Pipes over the indicated
session. This may be a normal event if either side of the
connection is abruptly ended.
continues.
ANR8264W (Windows) Error reading data on Named
Pipes, session session number. ReadFile
return code is return code.
code from the ReadFile Windows API while reading
data from Named Pipes in the indicated session. This
may be a normal event if either side of the connection
is ended abruptly.
continues.
589

ANR8265W (Windows) Error open Named Pipes
Named Pipes name, CreateNamedPipe
return code return code.
code when trying to open the indicated Named Pipes
name for Named Pipes communication with a client.
The return code shown is returned by the Windows
CreateNamedPipe API.
continues. Named Pipes communications is inoperative.
User response: The server may have run out of file
handles. Stop and restart the server to reenable Named
Pipes communications. It is not normal to run out of
file handles. A system or logic error may be the
underlying cause.
ANR8266W (Windows) Error accepting connection
on Named Pipes Named Pipes name,
ConnectNamedPipe return code return
code.
code when trying to complete a connection on the
indicated Named Pipes name for Named Pipes
communication with a client. The return code shown is
returned by the Windows ConnectNamedPipe API.
User response: A system problem may be preventing
use of Named Pipes. Stop and restart the server to
reenable Named Pipes communications.
ANR8267W (Windows) Error initializing a security
descriptor for Named Pipes Named Pipes
name, reason: System message.
code when trying to initialize the indicated Named
Pipe for Named Pipes communication with a client.
The reason shown is returned by the Windows
FormatMessage API.
User response: Administrator Privileges are required.
Login using an account wit h Administrator privileges
and restart the server to reenable Named Pipes
communications.
ANR8268W (Windows) Named Pipe communications

were not enabled due to an error
looking up the following Windows
group name: Windows group name. Use
the Windows User manager to add the
specified group. Members of the group
will then use Windows unified logon to
access the server over Named pipes.
code when trying to initialize the indicated Named
Pipe for Named Pipes communication with a client.
The system could not find the Windows Account name
User response: To use Windows unified logon specify
the name of a valid Windows account or group name.
Restart the server to reenable Named Pipes
communications.
ANR8269W (Windows) Error opening Named Pipe
Named Pipes name, reason: System message.
code when trying to open the indicated Named Pipe
name for Named Pipes communication with a client.
The reason shown is returned by the Windows
FormatMessage API.
User response: Consider the reason text and take
appropriate action. Stop and restart the server to
reenable Named Pipes communications.
ANR8273I (Windows) Shared memory driver ready
number.
with clients using the shared memory protocol on the
indicated port.
ANR8274W (Windows) Shared memory
communications driver is terminating
due to error in creating a new thread.
System action: Server operation continues, but shared
memory communications is inoperative.
590
ANR8275W (Windows) ANR8283W (Linux)

memory.
ANR8275W (Windows) Shared memory connection
System action: Server operation continues. Shared
memory communications is inoperative.
options file.
ANR8276W (Windows) Shared memory connection
terminated - unable to initialize. Key
channel key, Reason: reason code.
due being unable to initialize shared memory.
memory communications are inoperative.
User response: Try a different shared memory session.
ANR8277E (Windows) Shared memory unable to
initialize - Port: shm port number, Reason:
reason code.
because it could not intialize a communication channel.
Make sure no other server or storage agent running on
the same machine is using the same shm port number.
memory communications are inoperative.
User response: Try a different shared memory session.
ANR8282I (HP-UX) SNMP driver ready for
connection with subagent on port port
number.
SNMP subagents on the indicated port number.
ANR8282I (Linux) SNMP driver ready for connection

with subagent on port port number.
ANR8282I (Solaris) SNMP driver ready for
number.
ANR8283W (HP-UX) SNMP driver unable to
initialize due to error in using Port port,
master TCP/IP socket on which to listen to SNMP
subagents. The reason code is the return code from the
TCP/IP bind API.
server cannot accept sessions from SNMP subagents to
run macro commands.
file with the SNMPSUBAGENT PORT option. If
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
be done by issuing the TCP/IP netstat command.
ANR8283W (Linux) SNMP driver unable to initialize
due to error in BINDing to Port port,
TCP/IP bind API.
run macro commands.
file with the PORT option. If TCP/IP is also in use for
client sessions, ensure that the same port number is not
specified for TCP/IP and SNMP communications.
591
ANR8283W (Solaris) ANR8285I (Windows)

ANR8283W (Solaris) SNMP driver unable to
initialize due to error in BINDing to
Port port, reason code reason code.
ANR8284E (Solaris) The Shared Memory

Communications Protocol could not
initialize.

TCP/IP bind API.
Explanation: The server was unable to initialize the

Shared Memory Communications Protocol due to an
error.

run macro commands.
specified for TCP/IP communications and SNMP
communications.
ANR8284E (AIX) The Shared Memory
initialize.
error.
System action: Server operation continues without
Shared Memory Communications.
the cause of the failure.
ANR8284E (HP-UX) The Shared Memory
initialize.

ANR8285I (AIX) Shared Memory driver ready for
with clients using the Shared Memory protocol.
ANR8285I (HP-UX) Shared Memory driver ready for
ANR8285I (Linux) Shared Memory driver ready for

error.

ANR8285I (Solaris) Shared Memory driver ready for



ANR8284E (Linux) The Shared Memory

initialize.


error.
ANR8285I (Windows) SNMP driver ready for

number.



592
ANR8286W (AIX) ANR8287W (HP-UX)

ANR8286W (AIX) Unable to initialize Shared
Memory driver - insufficient memory.
Explanation: Because the operating system rejected a
communications through the Shared Memory protocol.
Shared Memory protocol.
space for AIX. You may also use SMIT to determine if
the number of applications is causing a memory
shortage. It may be necessary to cut down on the
ANR8286W (HP-UX) Unable to initialize Shared
space for HP-UX. You may also use SAM to determine
shortage. It may be necessary to cut down on the
ANR8286W (Linux) Unable to initialize Shared
User response: Ensure that there is sufficient swap
space for Solaris. It may be necessary to cut down on
the maximum number of client sessions by changing
the MAXSESSIONS option in the server options file.
ANR8286W (Solaris) Unable to initialize Shared
space for Solaris. It may be necessary to cut down on

the maximum number of client sessions by changing
the MAXSESSIONS option in the server options file.
ANR8286W (Windows) SNMP driver unable to
TCP/IP bind API.
run macro commands.
specified for TCP/IP communications and SNMP
communications. This may be done by issuing the
TCP/IP netstat -s command. If the server is brought
down and then started immediately, you may be within
the TCP/IP one minute timeout period for port
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.
ANR8287W (AIX) Unable to initialize Shared
Memory driver - error creating acceptor
socket. Reason code reason code.
Explanation: Because TCP/IP rejected a request for a
communications through Shared Memory.
User response: If TCP/IP is not started, use the HALT
command from any server prompt to stop the server,
and restart it.
ANR8287W (HP-UX) Unable to initialize Shared
and restart it.

593
ANR8287W (Linux) ANR8289W (HP-UX)

ANR8287W (Linux) Unable to initialize Shared
command from any prompt to stop the server, and
restart it.
ANR8287W (Solaris) Unable to initialize Shared
and restart it.
ANR8288W (AIX) Unable to establish Shared
Memory connection - insufficient
memory.
space for 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
options file.
ANR8288W (HP-UX) Unable to establish Shared
memory.
space for HP-UX. You may also use SAM to determine
shortage. You may also wish to cut down on the
594

options file.
ANR8288W (Linux) Unable to establish Shared
memory.
space for Solaris. You may also wish to cut down on
the maximum number of sessions that the server can
options file.
ANR8288W (Solaris) Unable to establish Shared
memory.
space for Solaris. You may also wish to cut down on
the maximum number of sessions that the server can
options file.
ANR8289W (AIX) Shared Memory driver is
new thread.
System action: Server operation continues, but Shared
Memory communications is inoperative.
memory. Ensure that there is sufficient paging space for
AIX. You may also use SMIT to determine if the
You may also wish to cut down on the maximum
ANR8289W (HP-UX) Shared Memory driver is
new thread.
ANR8289W (Linux) ANR8291W (AIX)

memory. Ensure that there is sufficient paging space for
HP-UX. You may also use SAM to determine if the
You may also wish to cut down on the maximum
ANR8289W (Linux) Shared Memory driver is
new thread.
memory. Ensure that there is sufficient swap space for
Solaris. You may also wish to cut down on the
options file.
ANR8289W (Solaris) Shared Memory driver is
new thread.

is abruptly ended.
continues.
ANR8290W (Linux) Error sending data through
Shared Memory. Reason return code.
code while sending data through shared memory. This
is abruptly ended.
continues.
ANR8290W (Solaris) Error sending data through


is abruptly ended.


continues.

memory. Ensure that there is sufficient swap space for
Solaris. You may also wish to cut down on the
options file.

ANR8290W (AIX) Error sending data through Shared

Memory. Reason return code.
is abruptly ended.
continues.
ANR8290W (HP-UX) Error sending data through
ANR8290I (Windows) IPX/SPX driver ready for

connection with clients on socket IPX
socket number.
with clients using the IPX/SPX protocol on the
indicated socket number.
ANR8291W (AIX) Error receiving data through
code while receiving data through the Shared Memory
protocol. This may be a normal event if either side of
the connection is abruptly ended.
continues.
595
ANR8291W (HP-UX) ANR8292W (Solaris)

ANR8291W (HP-UX) Error receiving data through
continues.
ANR8291W (Linux) Error receiving data through
case if the return code is zero. Also ensure that the

number of SPX sessions (as specified in your NET.CFG
file) has not been exceeded through other applications
using the IPX/SPX protocol.
ANR8292W (AIX) Session terminated when no data
was read through Shared Memory.
Explanation: The server is unable to read data from
Shared Memory. This may be a normal event if either
continues.
ANR8292W (HP-UX) Session terminated when no
data was read through Shared Memory.

continues.

continues.


ANR8291W (Solaris) Error receiving data through

ANR8292W (Linux) Session terminated when no data

was read through Shared Memory.



continues.
ANR8291W (Windows) Unable to bind to IPX/SPX
master socket. Return code = return code.
Explanation: The server cannot initiate
communications on the socket number designated for
its use.
communications using the IPX/SPX protocol is
inoperative.
User response: Ensure that SPX has been configured
to run on this system through the requester
configuration program. Ensure that there is no other
instance of the server running on the same system that
is using the same socket number. This is likely to be the
596

continues.
ANR8292W (Solaris) Session terminated when no
data was read through Shared Memory.
continues.
ANR8292W (Windows) ANR8294W (HP-UX)

ANR8292W (Windows) IPX/SPX connection
options file.
ANR8293W (AIX) Shared Memory driver unable to
error.
Explanation: While initializing Shared Memory
communications, the server failed to set up an interface
with TCP/IP.

ANR8293W (Solaris) Shared Memory driver unable
to initialize due to socket initialization
error.
with TCP/IP.
ANR8293W (Windows) IPX/SPX driver unable to
the master socket, return code = return
code.
requests from clients using IPX/SPX, the server
encountered an error.


using the IPX/SPX protocol.
ANR8293W (HP-UX) Shared Memory driver unable

to initialize due to socket initialization
error.
User response: Ensure that IPX/SPX is still running

properly and that it has not been intentionally or
unintentionally stopped. This may be done by using
the getipxad command to determine if an endpoint can
still be opened and bound; also determine if you can
still connect to a NetWare server.

with TCP/IP.
ANR8293W (Linux) Shared Memory driver unable to
error.
with TCP/IP.
ANR8294W (AIX) Shared Memory session unable to

initialize.
Explanation: While initializing a Shared Memory
communications session, an error occurred during
initial setup.
session is terminated.
User response: Contact your service representative for
assistance in resolving the error.
ANR8294W (HP-UX) Shared Memory session unable
to initialize.
initial setup.
597

ANR8294W (Linux) Shared Memory session unable
to initialize.
initial setup.
the SHMPORT 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.
to initialize due to error in using Port
port, reason code reason code.


communications, the server failed to connect to a
ANR8294W (Solaris) Shared Memory session unable

to initialize.


initial setup.
ANR8294W (Windows) Unable to establish IPX/SPX
connection - accept error. Return code =
tli error.
due to a failure in accepting the connection from
IPX/SPX.
System action: Server operation continues, but this
User response: Ensure that SPX has been configured
to run on this system through the requester
configuration program. Ensure that there is no other
instance of the server running on the same system that
is using the same socket number. Also ensure that the
number of SPX sessions has not been exceeded through
other applications using the IPX/SPX protocol, such as
NetWare applications.
User response: Ensure that no application is using the

port number specified in the server options file with
can be freed.
can be freed.


to initialize due to error in BINDing to






598

can be freed.
ANR8295W (Windows) Error sending data on session
session number. Reason return code.
code from IPX/SPX while sending data on the
indicated session. This may be a normal event if either
continues.
response is required. Otherwise, ensure that IPX/SPX is
still active.
code.
TCP/IP listen API.
using the Shared Memory protocol.
to initialize due to error in LISTENing
on the specified Port, reason code reason
code.
TCP/IP listen API.

code.
TCP/IP listen API.
to initialize due to error in LISTENing
on the specified Port, reason code reason
code.
TCP/IP listen API.
ANR8297W (AIX) Shared Memory driver is
terminating due to error in accepting a
new session, reason code reason code.
request from a client using the Shared Memory
protocol, TCP/IP returns an error. The reason code is
the return code from the TCP/IP accept API.
599
ANR8297W (HP-UX) ANR8298W (Solaris)

ANR8297W (HP-UX) Shared Memory driver is
ANR8297W (Linux) Shared Memory driver is

continues.
ANR8298W (HP-UX) The server experienced a
TCP/IP error while writing data on
Explanation: An error occurred during negotiation for
a shared memory session. This may be a normal event
if either side of the connection is abruptly ended.
continues.
ANR8298W (Linux) The server experienced a TCP/IP
error while writing data on socket socket
continues.
ANR8297W (Solaris) Shared Memory driver is



ANR8298W (Solaris) The server experienced a

TCP/IP error while writing data on




continues.

error while writing data on socket socket


600
ANR8299W (AIX) ANR8301E

error while reading data on socket socket
if either side of the connection is abruptly ended or if
the client is configured incorrectly.
continues.
Check the client options file to ensure that the server's
shared memory port is set up and is not being
confused with the server's TCP/IP port. The shared
memory port is a TCP/IP port that the server uses to
initiate communications, then switches to shared
memory communications.
ANR8299W (HP-UX) The server experienced a
TCP/IP error while reading data on
continues.

ANR8299W (Solaris) The server experienced a
TCP/IP error while reading data on
continues.
ANR8300E

ANR8299W (Linux) The server experienced a TCP/IP
error while reading data on socket socket
continues.
I/O error on library library name

(OP=internal code, CC=internal code,
KEY=internal code, ASC=internal code,
ASCQ=internal code, SENSE= sense data,
Description=error description). Refer to
the Tivoli Storage Manager
documentation on I/O error code
descriptions.
Explanation: An I/O error has occurred while

operating on the specified library.
User response: Ensure that the DEVICE parameter
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.
ANR8301E

(OP=internal code, SENSE=internal code).

601
ANR8302E ANR8308I
access door, make sure it is closed.
ANR8302E
I/O error on drive drive name with

volume volume name (OP=internal code,
Error Number=internal code, CC=internal
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.

operating on the specified drive.
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
manual usually contains tables that explain the values
of the KEY, ASC, and ASCQ fields.
ANR8303E
I/O error on drive drive name

(OP=internal code, SENSE=internal code).

and ready for automated operations. Further

initialization attempts for the given library will usually
be postponed until the next attempt is made to access
the library for an automated operation. During server
startup, however, initialization may be retried after a
short waiting period.
ANR8306I
Explanation: A CHECKIN LIBVOLUME or a LABEL

LIBVOLUME command is in progress, and the
specified volume is needed. The server expects the
volume to be inserted into the slot with the specified
element number of the given library within the time
limit specified in the message. For the slot and element
number diagram of your library, refer to the
documentation provided with the current ptf level or
refer to the Administrator's Guide for your release and
platform.
System action: The server waits until a REPLY
command is issued, or until the time limit expires.
User response: Insert the volume into the slot and
issue a REPLY command, along with the request ID, to
tell the server that the volume has been inserted.
ANR8307I

currently powered on and ready.
ANR8304E
Time out error on drive drive name in

library library name.
Explanation: A time out condition occurred while

waiting for the given drive to become ready so that
automated library operations could be performed.
DEFINE PATH command, and that the device is
currently powered on and ready.
ANR8305E
Library library name is not ready or not

operational.
Explanation: The specified automated library device is

either not ready or not in an operational state.
602
Request number: Remove device type

volume volume name from slot with
element number slot name of library
library name; issue 'REPLY' along with
the request ID when ready.
Explanation: A CHECKOUT LIBVOLUME command

has completed. You can remove the volume from the
slot with the specified element number and store it
outside the library. For the slot and element number
diagram of your library, refer to the documentation
provided with the current ptf level or refer to the
Administrator's Guide manual for your release and
platform.
command is issued.
User response: Remove the volume from the slot and
store it in a safe place. Issue a REPLY command, along
with the request ID, to tell the server that the volume
has been removed. The volume can be returned to the
library with the CHECKIN LIBVOLUME command.
ANR8308I
System action: Initialization of the library device fails.

User response: Ensure that the library is powered on
Request number: Insert device type volume

volume name mount mode into the slot
with element number slot element of
library library name within time limit
minutes; issue 'REPLY' along with the
request ID when ready.
Request number: device type volume volume

name is required for use in library library
name; CHECKIN LIBVOLUME required
within time limit minutes.
Explanation: A mount request has been made for a

volume that is defined in a storage pool, but which is
ANR8309E ANR8316E
currently checked out of the given library.
ANR8312E
System action: The server waits until it detects that

the volume has been checked into the library, or the
time limit expires.
User response: Obtain the required volume, and insert
it into the library by issuing a CHECKIN LIBVOLUME
command. Use the SWAP=YES option of the CHECKIN
LIBVOLUME command if the library is currently full;
this process allows the server to select an appropriate
volume to be swapped out in order to make room for
the required volume.
Explanation: The designated volume cannot be found

at its expected location in the given library.
User response: Perform an AUDIT LIBRARY
operation on the designated library, which forces the
server to reevaluate its inventory information for
volumes in the library.
ANR8313E
ANR8309E
Mount attempt failed - library library

Explanation: An attempt has been made to mount a

volume, but the attempt fails because the specified
library is not defined.
User response: Ensure that the LIBRARY attribute of
the device class associated with the mount operation
identifies a defined library. If not, correct the value of
the LIBRARY attribute, or define the specified library
ANR8310E
An I/O error occurred while accessing

Volume volume name could not be

located in library library name.
Volume volume name is not present in

Explanation: A mount request is made for the given

volume in the specified library, but the volume is not
currently checked into the library.
System action: The mount operation fails. If the
volume is being mounted for storage pool I/O (as
opposed to import/export I/O), its ACCESS attribute is
changed to UNAVAILABLE to prevent further mount
requests.
User response: Issue a CHECKIN LIBVOLUME
command to return the volume into the library, and
update the volumes ACCESS attribute to READONLY
or READWRITE using the UPDATE VOLUME
command. Retry the mount request.
Explanation: An I/O error occurs while accessing the

designated library.
ANR8314E
Explanation: A library operation fails because all of

the librarys storage locations are occupied.

associated with the library is identified correctly in the
DEFINE PATH command, and that the library is
access door, make sure it is closed. After checking and
correcting these potential problems, retry the operation.

User response: Issue a CHECKOUT LIBVOLUME
command to make room in the library. Retry the library
operation.
ANR8315E
ANR8311E

drive drive name for low-level operation
operation, errno = drive errno, rc = return
code.
Explanation: An I/O error occurs while performing

the operation on the specified drive.
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
Library library name is full.
Command: The device type of drive drive

name is not supported in library type
libraries.
Explanation: Drives of the type identified in the

command are not supported in the given type of
library.
User response: Determine whether the drive and
library combination is supported by the installed level
of the server. If so, contact your service representative.
ANR8316E
Selecting swap volume to be checked

out of library library name.
Explanation: A CHECKIN LIBVOL command was

issued for a library that has no empty slots to hold the
new cartridge. The SWAP=YES parameter was included
in the command.
603
ANR8317I ANR8323I
System action: A CHECKOUT LIBVOL command will
be automatically be issued, specifying either a scratch
volume or, if there are none, a volume with the lowest
number of mounts.
User response: Use a supported type of drive. volume
from the library and store it in a safe place. Issue a
REPLY command to tell the server that the volume has
been removed. The volume can be introduced back into
the library with the CHECKIN LIBVOLUME command.
ANR8317I
The volume in device type drive drive

name must be manually ejected.
Explanation: This device type does not automatically

eject the volume when it is dismounted and requires
that the volume be manually ejected from the drive.
User response: Physically eject the volume from the
drive.
ANR8318I
Request number: Mount side side of device

type volume volume name mount mode in
drive drive name of library library name
within time limit< minutes.
Explanation: The server requires that the specified

volume be mounted as requested. Since the volume is
two-sided, this message specifies which side (A or B) is
needed by the server for I/O operations.
System action: The server waits for the volume to be
mounted.
User response: Mount the volume in the specified
drive.
ANR8319I

volume name mount mode into library
library name within time limit minute(s).
Explanation: A CHECKIN LIBVOLUME command is

in progress, and the specified volume is needed. The
server expects the volume to be inserted into the
library with the convenience I/O station mechanism.
System action: The server waits until the volume is in
the library, or until the time limit expires.
User response: Insert the specified volume into the
library. If the volume has already been inserted into the
library, no user action is necessary.
ANR8320I

volume name mount mode in drive drive
name of library library name within time
limit minute(s); issue 'REPLY ' along
with the request ID when ready.

specified volume is needed. The server expects the
604
volume to be inserted in the designated drive of the

given library within the time limit specified in the
message.
User response: Insert the volume into the drive, and
then issue a REPLY command, along with the request
ID, to tell the server that the volume has been inserted.
ANR8321I

volume volume name from drive drive
name of library library name; issue
'REPLY' along with the request ID when
ready.
Explanation: A CHECKOUT LIBVOLUME or a

LABEL LIBVOLUME command has completed. You can
remove the specified volume from the designated drive
and store it outside the library.
command is issued.
User response: Remove the volume from the drive
and store it in a safe place. Issue a REPLY command,
along with the request ID, to tell the server that the
volume has been removed. The volume can be returned
to the library with the CHECKIN LIBVOLUME
command.
ANR8322I

volume volume name from entry/exit port
of library library name; issue 'REPLY'
along with the request ID when ready.

has completed. You can remove the specified volume
from the entry/exit port of the given library and store
it elsewhere.
command is issued.
User response: Remove the volume from the library
and store it in a safe place. Issue a REPLY command,
along with the request ID, to tell the server that the
volume has been removed. The volume can be returned
to the library with the CHECKIN LIBVOLUME
command.
ANR8323I

volume name mount mode into entry/exit
port of library library name within time
limit minute(s); issue 'REPLY' along with

specified volume is needed. Mount the volume in the
entry/exit port of the given library within the time
limit specified in the message.
ANR8324I ANR8332I
System action: The volume is accessed for reading or

writing, or both.
User response: Insert the volume into the librarys

entry/exit port; and 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

mounted in the near future so the server can access it
for reading or writing.
User response: If the volume is stored offline, retrieve
it so that it is readily accessible when the server
requests that it be mounted.
ANR8325I
Dismounting volume volume name mount retention period minute mount

retention expired.
Explanation: The specified volume is dismounted

because the given mount retention period has expired.
System action: The volume is dismounted.
ANR8329I

mounted mount mode in drive drive name,
status: IDLE.
Explanation: In response to a QUERY MOUNT

command, the server indicates that the given volume is
mounted in the specified drive. The volume is currently
idle, meaning no active operations are being performed.
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.
ANR8330I

status: IN USE.

in use, meaning that read or write operations, or both,
are being performed.
ANR8326I
Request number: Mount device type volume

volume name mount mode in drive drive
name of library library name within time
limit minutes.
Explanation: If the volume name includes the names

EXP, IMP, DUMP, or DBBK, the request is for a scratch
volume.
System action: The server waits for the volume to be
mounted.
User response: Mount the volume in the specified
drive.

ANR8331I

status: DISMOUNTING.

being dismounted by the server.
ANR8327E
Command: Cannot cancel request request

number.
Explanation: The request, whose number is specified

by the given command, cannot be canceled. The
requested operation must be completed.
System action: The cancel request command is not
processed.
User response: Proceed with the requested operation.
ANR8328I

name mounted in drive drive name.
ANR8332I

mounted mount mode, status: IDLE.

mounted for I/O operations. The volume is currently
period, it will be automatically dismounted.
Explanation: The server verifies that a requested

volume has been mounted properly in the given drive.
605
ANR8333I ANR8342I
ANR8333I

mounted mount mode, status: IN USE.

mounted for I/O operations. The volume is currently in
use, meaning that read or write operations, or both are
being performed.
ANR8334I
Number of matches matches found.
Explanation: This is a summary message for the

QUERY MOUNT command. It indicates the total
number of mount points that have been reported in the
command output.
ANR8335I
Request number: Verifying label of device

type volume volume name in drive drive
name.
Explanation: The server verifies the label of the

volume that has been requested by an earlier mount
message. This is done to ensure that the correct volume
has been mounted by the operator.
ANR8338E
Device type volume volume name cannot

be overwritten by EXPORT operation.
Explanation: The specified volume already exists or

contains data, so that the server cannot allow new
export data to be written to it.
System action: The server detects that the given
volume already contains some data that would be
overwritten by the requested export operation.
User response: If the specified volume does not
contain any valuable data, delete it and retry the export
operation.
ANR8339E
Device type volume intended volume name

in drive drive name was replaced with
volume incorrect volume name.
Explanation: The server detects that a previously

mounted and verified volume (the desired volume) has
been replaced with a different volume (the incorrect
volume). No further read or write operations, or both,
can occur on the given drive, because data corruption
may occur.
System action: The server dismounts the volume from
the drive.
User response: Mount the correct volume again if it is
in a manual library and retry the operation.
Device type volume volume name
mounted.
System action: The server reads the volume label and

checks it for validity.
ANR8340I
Explanation: The server has mounted the given

volume.
ANR8336I
Verifying label of device type volume

volume name in drive drive name.
Explanation: The server verifies the label of a volume

that is needed for read or write operations, or both.
This is done to ensure that the correct volume has been
mounted.
System action: The server reads the volume label and
checks it for validity.
ANR8337I
Device type volume volume name mounted

in drive drive name.
Explanation: The server verifies that the specified

mount request has been completed properly. Read or
write operations, or both, can be performed on the
volume.
System action: The label of the volume has been
verified.
System action: Read or write operations, or both, will

commence for the volume.
ANR8341I
End-of-volume reached for device type

volume volume name.
Explanation: The server has detected an

end-of-volume condition for the given volume.
System action: The volume is marked full. If more
data must be stored, the server will access another
volume for it.
ANR8342I
Request request number for volume

volume name canceled by administrator
name.
Explanation: A mount request is canceled by the given

administrator.
System action: The system cancels the mount request.
606
ANR8343I ANR8353E
ANR8343I
Request request number for volume

volume name canceled (PERMANENT) by
administrator name.
User response: If it is necessary to dismount the

volume, cancel the session or process that is using the
Explanation: A mount request is successfully canceled

with the PERMANENT option.
ANR8349E
System action: The system cancels the mount request

and marks the volume as unavailable.
Explanation: A DISMOUNT DEVICE command has

been issued, but the device to be dismounted cannot be
found.

ANR8344E
Command: Device device not found.
Command: Invalid request number request number.
User response: Ensure that the correct device has been

specified.
Explanation: A command has been entered with an

incorrect request number.
ANR8350E

command.
Explanation: A DISMOUNT DEVICE command has

been issued, but the device is still in use and cannot be
dismounted.
User response: Issue the command with the correct

request number.
ANR8345E
Command: No match found for this

request number.
Explanation: The request number specified by the

command is not in the list of outstanding mount
requests.
command.
User response: Issue the command with the correct
request number.
ANR8346I
Command: No requests are outstanding.
Explanation: A QUERY REQUEST or CANCEL

REQUEST command has been entered although no
mount requests are outstanding.
ANR8347E
Command: Volume volume not found.
Explanation: A DISMOUNT VOLUME command is

issued, but the volume to be dismounted cannot be
found.
User response: Ensure that the correct volume name is
entered.
ANR8348E
Command: Volume volume is not "Idle".
Explanation: A DISMOUNT VOLUME command has

been issued, but the volume is still in use and cannot
be dismounted.
Command: Device device is not "Idle".
User response: If it is necessary to dismount the

device, cancel the session or process that is using the
device, and reissue the command.
ANR8351E
Request number: Mount request for

volume volume name has timed out.
Explanation: The mount request has not been satisfied

in the requested time.
System action: The server fails the mount request.
User response: Retry the mount request and ensure
that the volume is mounted within the time limit for
the manual library. For an automated library, retry the
mount request and increase the mount wait time for
the device class.
ANR8352I
Requests outstanding:
Explanation: This message provides a list of currently

outstanding mount requests.
System action: The server lists all outstanding mount
requests or the one specified on the QUERY REQUEST
command.
ANR8353E
Request number: I/O error reading label

of volume in drive drive name.
Explanation: The server detects an error while reading

the volume label from the volume in the specified
drive.
System action: The volume is ejected, and the server
continues to wait for the requested volume to be
mounted.
607
ANR8354E ANR8360I
v The requested volume is properly inserted in the
designated drive.
force the library to reevaluate its inventory of volumes.
v The volume has been labeled by using the

DSMLABEL utility program before you attempt to
use it with the server.
ANR8357I
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.
After checking and correcting these potential problems,
ANR8354E
Request number: Incorrect volume (volume

name) mounted in drive drive name.
Explanation: The user has inserted the named volume

into the indicated drive, but it is not the one requested
by the server.
mounted.
User response: Ensure that the requested volume is
inserted properly into the designated drive.
ANR8355E
I/O error reading label for volume

volume name in drive drive name.
Error reading label of volume from

slot-element element address in drive drive
name of library library name.
Explanation: While processing a search-mode

CHECKIN LIBVOLUME command for the designated
library, the server finds a volume whose label cannot be
read.
System action: The volume is dismounted and is not
checked into the library.
and ensure that it is properly labeled. After doing so,
the volume can be checked into the library.
ANR8358E
Audit operation is required for library

library name.
Explanation: The server encounters a problem

managing the given library, and determines that an
AUDIT LIBRARY operation should be performed.
System action: The server may continue to access the
library, but some volumes may not be accessible until
an AUDIT LIBRARY command is issued against the
library.

reading/verifying the volume label for the volume in
the specified drive.
User response: Issue an AUDIT LIBRARY command

against the library.
System action: The volume is dismounted by the

server.
ANR8359E

v Check the integrity of the data on the volume by
issuing an AUDIT VOLUME command. If this error
occurs on a volume that is stored inside a VTL or
SCSI library, the library itself may need to be audited
by using the AUDIT LIBRARY command.
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.
After checking and correcting these potential problems,
ANR8356E
Incorrect volume mounted volume name

was mounted instead of volume expected
volume name in library library name.
Explanation: The incorrect volume has been mounted

in the designated library. This error can occur if the
library inventory has been altered due to manual
intervention or movement of volumes, or both.
System action: The volume is dismounted; the
expected volume may be marked unavailable if this
error occurs during normal volume mount activity.
Explanation: The server encounters a media fault

while accessing the given volume using the specified
drive.
System action: The operation that is attempting to
access the volume will fail, and the volume will be
immediately dismounted from the drive.
User response: In some cases, the server will
automatically mark the volume readonly. This will
prevent the server from trying to write to the volume.
Issue an AUDIT VOLUME command to determine if
any data has been lost due to the media failure.
ANR8360I
Volume volume name has been deleted

from MANUAL library library name.
Explanation: The specified volume has been deleted

by the server. It can be returned to a scratch pool by
the mount operator if desired.
System action: The volume is removed from the
servers inventory.
User response: Use the AUDIT LIBRARY command to
608
Media fault detected on device type

volume volume name in drive drive name
of library library name.
ANR8361E ANR8370I
ANR8361E
Command: Device type not specified.
Explanation: The specified command requires that the

DEVTYPE parameter be supplied.
User response: Reissue the command, and specify a
valid DEVTYPE parameter.
ANR8362E

invalid for device type device type.
Explanation: The specified parameter is not valid for a

device class with the given device type.
parameter.
ANR8363E

required for device type device type.
ANR8366E
Command: Invalid value for parameter

parameter.
Explanation: An invalid value has been provided for

the specified parameter.
valid parameter value. If this is for the ELEMENT
parameter on DEFINE DRIVE with AUTODETECT, this
message can be issued because the library doesn't
support the ability to determine the element number
dynamically. In this case, supply the actual element
number instead of using AUTODETECT for the
ELEMENT parameter. If this is for the
SCALECAPACITY parameter on a 3592 device class,
verify that this device class has the attribute
WORM=NO as WORM and SCALECAPACITY are not
compatible.
ANR8367E
Command: Multiple parameter values are

not allowed.

given parameter be supplied when the indicated device
type is used.
Explanation: The designated parameter is specified

more than once in the command; this is not allowed.
User response: Reissue the command, providing the

required parameter value.
User response: Reissue the command, but specify the

given parameter only once.
ANR8364E
Command: Cannot reduce MOUNTLIMIT

below number of volumes currently
mounted.
Explanation: The MOUNTLIMIT value cannot be

reduced below the number of currently mounted
volumes.
User response: Wait until the server finishes using
some of the mounted volumes, or force the server to
dismount idle volumes using the DISMOUNT
VOLUME command, then retry this command.
ANR8368E
Explanation: The user inserted the wrong side of the

requested volume into the indicated drive.
continues to wait for the requested side of the volume
to be mounted.
User response: Insert the correct side of the requested
volume into the designated drive.
ANR8369E
ANR8365E
Command: The parameter parameter

cannot be changed.
Explanation: The specified parameter cannot be

changed from the value that was provided with the
associated DEFINE command.
User response: If it is necessary to use a different
value for the given parameter, the associated object
must be deleted and then redefined using the new
parameter value.
Request number: Incorrect side (side) of

volume volume name mounted in drive
drive name.
Library library name is not defined.
Explanation: The designated library is not defined,

but has been referenced in a mount request.
System action: The mount request is rejected.
User response: Define the given library, or update the
LIBRARY parameter of the device class that references
it.
ANR8370I

mounted mount mode, status: RETRY.

RETRY, meaning an attempt is being made to
609
ANR8371I ANR8378I
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
operation will fail and the volume will be automatically
dismounted.
System action: The server continues, but cannot use

the mountpoint for removable file support until the
directory is unmounted.
User response: It may be necessary to run the server
as a root user to mounted directories to be unmounted.

ANR8371I
I/O is being bypassed for volume volume

name.
Explanation: The indicated volume is mounted but

the server is bypassing actual I/O operations for the
volume. The pool associated with the volume matches
the NULLPOOLNAME option in the options file or
NULLFILEDEVCLASS YES has been specified in the
options file.
ANR8372I

volume volume name from drive drive
name of library library name.
Explanation: A LABEL LIBVOLUME command has

completed. You can remove the specified volume from
the designated drive and store it outside the library.
User response: Remove the volume from the drive
and store it in a safe place.
ANR8375E

backup set data to be written to it.
overwritten by the requested backup set operation.
contain any valuable data, delete it and retry the
backup set operation.
ANR8376I
Request number: Fill the bulk entry/exit

port of library library name with all device
type volumes to be processed within time
limit minute(s); issue 'REPLY' along with
Explanation: A CHECKIN LIBVOLUME or LABEL

LIBVOL command with SEARCH=BULK is in progress.
Load all volumes to be processed into the multi-slot
entry/exit port of the given library within the time
limit specified in the message.

mounted mount mode, status:
DISMOUNTING.

currently being dismounted.
ANR8378I

User response: Insert the volumes into the librarys
entry/exit port; and issue a REPLY command, along
with the request ID, to tell the server that the volumes
have been inserted.
Mount point reserved in device class

Device class name, status: RESERVED.

command, the server indicates that there is a mount
point reserved for future I/O operations in the given
device class.
ANR8377I
ANR8373I

be overwritten by BACKUPSET
operation.

mounted mount mode, status: RETRY
DISMOUNT FAILURE.

command, the server indicates that it is currently
retrying the dismount of the given volume because of a
failure during the previous dismount.
ANR8374E
Unable to unmount mountpoint

mountpoint name.
Explanation: A removable file device class mountpoint

had to be unmounted using the operating system
unmount function. The server did not have permission
to unmount the directory specified.
610
ANR8379I ANR8386W
ANR8379I
Mount point in device class Device class

name is waiting for the volume mount to
complete, status: WAITING FOR
VOLUME.

point in the given device class waiting for the volume
mount to complete.
ANR8380I

status: RETRY DISMOUNT FAILURE.
Explanation: Because of the failure of a previous

dismount, the server is retrying the dismount of the
specified volume from the specified drive. In response
to a QUERY MOUNT command, the server indicates
that the volume is mounted in the drive.
ANR8381E
storage pool with RECLAMATIONTYPE=SNAPLOCK

must be Snaplock directories.
System action: If you are trying to define a storage
pool with RECLAMATIONTYPE=SNAPLOCK, the
command fails. If you are trying to update a device
class that is pointed to by a
RECLAMATIONTYPE=SNAPLOCK storage pool, the
command fails.
User response: If you are trying to define a storage
pool with RECLAMATIONTYPE=SNAPLOCK, you
need to specify a device class which has all directories
which are NetApp SnapLock WORM Volumes. You
may select another device class which has all SnapLock
directories specified in it. Or you may use the UPDATE
DEVCLASS command to remove non-SnapLock
directories from the device class DIR list. If you modify
an existing device class, you need to ensure that no
data is stored in directories that are to be removed
from the device class. If this message is issued when
you are trying to update a device class, ensure that all
directories specified in the directory are SnapLock
directories.
ANR8384E
Device type volume volume name could

not be mounted in drive drive name.
Explanation: The server could not complete the

specified mount request due to an error. Examine
previous messages for additional information regarding
the specified volume and the operation.
User response: Examine previous messages for
additional information regarding the specified volume
and the operation.
Explanation: The user has inserted the named volume

into the indicated library, but it is not the one requested
by the server.
System action: The volume is skipped, and the server
inserted.
User response: Ensure that the requested volume is
inserted properly into the designated location in the
library.
ANR8385E
ANR8382W
Library library name is now full.
Explanation: During a library check-in operation from

a multi-slot entry/exit station, the last storage location
was filled before checking the remainder of the
entry/exit slots.
System action: The operation stops, but is considered
successful if at least one volume is checked in.
User response: If more volumes remain to be checked
in, issue a CHECKOUT LIBVOLUME command to
make room in the library. Retry the library operation.
Device class device class name directory
directory name is not a SnapLock
directory.
Explanation: When processing the named device class,

it was discovered that a directory was specified for the
device class that is not a NetApp SnapLock WORM
Volume. All directories used by a device class for a
All entry/exit ports of library library

name are empty.
Explanation: The entry/exit ports of the library do not

contain a volume that can be processed.
User response: Ensure that the volume is inserted
properly into the entry/exit port of the library and that
the library indicates the volume is inserted and issue
the command again. Contact the hardware vendor if
the volume is inserted correctly and this error occurs.
ANR8386W
ANR8383E
Request number: Incorrect volume (volume

name) inserted into library library name.
Slot element number of library library

Explanation: The slot in the library could not be

physically accessed at this time.
System action: The slot is skipped and processing
continues with the next slot.
User response: If there is a volume in the slot that
611
ANR8387I ANR8390W
needs to be processed, verify that the Entry/Exit door
is closed, the slot is accessible, and the device has not
logged any device errors before trying the command
again. Contact the hardware vendor if slots are
incorrectly being reported as inaccessible.
ANR8387I
Request number: All entry/exit ports of

library library name are full or
inaccessible. Empty the entry/exit ports,
close the entry/exit port door, and make
the ports accessible.

cannot find an empty and available entry/exit port to
place the volume to be removed.
System action: The server waits until the operator
performs the actions requested.
User response: Make at least one entry/exit port
empty and accessible. Check the entry/exit ports or the
library. Make sure the entry/exit door is closed. If all
the entry/exit ports are full remove at least one volume
from the entry/exit port. If any of entry/exit are empty
then the empty entry/exit ports are inaccessible. Check
the library's documentation on how to make the
entry/exit port accessible. If the library is incorrectly
reporting the status of the entry/exit port contact the
library vendor.
ANR8388E
Device class device class name has no

directories specified.

which is referenced by a storage pool of type
RECLAMATIONTYPE=SNAPLOCK, it was discovered
that there were no directories specified for it. One or
more directories must be specified for a device class
that is used by a storage pool with
RECLAMATIONTYPE=SNAPLOCK, and all directories
must be NetApp SnapLock WORM Volumes.
User response: A device class that is referenced by a
storage pool of type
RECLAMATIONTYPE=SNAPLOCK needs to specify
one or more directories which are NetApp SnapLock
WORM Volumes. Use the UPDATE DEVCLASS
command to define appropriate directories to the
device class and retry your request.
ANR8389E
Device class device class name has storage

pools using it with inconsistent
RECLAMATIONTYPE parameters, or
invalid directories specified in it.

it was discovered that it was not configured properly. A
device class can be referenced by storage pools of type
RECLAMATIONTYPE=SNAPLOCK. For storage pools
of type RECLAMATIONTYPE=SNAPLOCK, all
612
directories specified in the device class must be on

NetApp SnapLock WORM Volumes.
System action: If the Tivoli Storage Manager server is
starting, the server continues; however, attempts made
to read from or write to that storage pool will fail until
the storage pools referencing the device class and the
device class are properly configured.
User response: Check the activity log for ANR8502,
ANR8383E, and ANR8388E messages. If these messages
have been issued, follow the instructions in the User
Response section of those messages to resolve the
issues.
If the problem is not resolved, use the QUERY
DEVCLASS command with the FORMAT=DETAILED
option to obtain the specified directories for the device
class. Verify that each directory is available to the Tivoli
Storage Manager server, e.g., on-line, in read-write
mode, configured properly, etc.
If the problem is not resolved, for a device class used
by RECLAMATIONTYPE=SNAPLOCK storage pools,
check that each directory is a NetApp SnapLock
WORM Volume. If not, use the UPDATE DEVCLASS
command to update the device class directory structure
appropriately.
If the problem is not resolved, use the QUERY
STGPOOL command with the FORMAT=DETAILED
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
that only one type of storage pool uses the device class.
If you wish to have storage pools of both reclamation
types pointing to the same directory structure, you may
create two device classes with the same directory
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.
If you have made updates to the storage pools and
device classes and the problem is not resolved, you
may need to restart the Tivoli Storage Manager server.
ANR8390W
Failure connecting to library client

library client to manage volume volume.
Explanation: The library manager failed to contact the

designated library client for a management operation
for the specified volume.
System action: The library management operation
fails.
User response: Review the other messages in the
activity log relating to this library client and this
volume to determine which operations were affected by
this failure.
ANR8391E ANR8398E
ANR8391E
The external library manager file name

can not be found. The library library
name is not available.
ANR8395E
Command: The parameters specified are

only valid for a device class defined
with a ZosMedia library.
Explanation: The external library manager listed for

this library was not found. The path or the file name is
not correct.
Explanation: The specified parameter is not valid for a

device class unless a ZosMedia library is specified in
the Library parameter of the device class.

fails.
User response: Verify the path and the name of the

external library mentioned. If it is correct, verify that
the file is present on the system and that file
permissions allow the server to invoke the file.
ANR8392E
The external library manager file name

does not have executable permission.
The library library name is not available.
Explanation: The external library manager listed for

this library was not found. The path or the file name is
not correct.
fails.
User response: Verify the path and the name of the
external library mentioned. If it is correct, verify that
the file is present on the system and that the file
permissions allow the server to invoke the file.

parameter.
ANR8396E
Explanation: The PERFORM LIBACTION command

failed. Either the library lacks the SCSI capability to
determine the serial and element numbers of its own
drives, or SAN Discovery failed to translate the serial
number to the drive's special file name.
User response: Correct any issues with SAN
Discovery and reissue the PERFORM LIBACTION
command. If the command cannot be processed, drive
and drive path definitions for this library will need to
be defined manually, one drive at a time.
ANR8397E
ANR8393E
Failed to communicate with the external

library library name through it's defined
external library manager path.
Explanation: The external library manager executable

file did not start or exited immediately.
fails.
User response: Verify the path and the file name of
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.
The path and file name can be found by using the
QUERY PATH command.
The device class,device class
name,directory parameter is too long.
Explanation: The directory parameter for the define

device class command is too long.
User response: Reissue the command, specifying a
valid DIRECTORY parameter. The directory parameter
must be between 0 and 1400 characters.
Library name (library name) is too long to

use as the default PREFIX value. An
explicit PREFIX value is required.
Explanation: The PREFIX value must be specified

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
cannot be used for the PREFIX parameter. Instead, the
PREFIX value must be specified explicitly.
User response: Reissue the PERFORM LIBACTION
command and specify the PREFIX parameter with a
value that contains 25 characters or less.
ANR8398E
ANR8394E
Command: Library library name is not

capable of discovering the drives that it
owns.
The REMOVE=UNTILEEFULL option is

not supported with the MOVE
DRMEDIA command for librarylibrary
name with library type library type.
Explanation: The MOVE DRMEDIA command does

not support the option as REMOVE=UNTILEEFULL for
this library type.
System action: The operation will fail.
User response: This option is only supported with the
library type SCSI. Remove the
REMOVE=UNTILEEFULL option and perform the
operation again.
613
ANR8399E ANR8409E
ANR8399E
The TSM server receives a status as acsls

statuse from ACSLS server.
Explanation: The ACSLS CSI media server does not

receive a response from TSM server.
User response: This is a communication problem.
Check configurations of the network adapter and its
driver and then perform the operation again.
ANR8400I
System action: The library is defined and recorded in

the database.
Command: Invalid library name library
name.
Explanation: The designated library name is invalid;

either it contains too many characters, or some of the
characters are invalid.
User response: Reissue the command using a valid
library name.
ANR8402E
Command: Library library name is already

defined.
Explanation: The designated library cannot be defined

because it already exists.
User response: If you want to define an additional
library, reissue the command with a different library
name.
ANR8403E
Command: Operation not allowed for

library type libraries.
Explanation: The requested operation is not allowed

for libraries of the given type.
ANR8404I
ANR8405E
Explanation: The designated drive name is invalid;

either it contains too many characters, or some of the
characters are invalid.
drive name.
Drive Drive name defined in library

library name.
ANR8406E
Command: Drive drive name is already

defined in library library name.
Explanation: The designated drive cannot be defined

because it has already been defined for the specified
library.
drive, reissue the command with a different drive
name.
ANR8407E
Command: The MODEL parameter is

required for this command.
Explanation: The MODEL parameter has not been

provided; it is required.
User response: Reissue the command using the
MODEL parameter.
ANR8408E
Command: The DEVICE parameter is

Explanation: The DEVICE parameter has not been

provided; it is required.
User response: Reissue the command using the
DEVICE parameter.
ANR8409E

defined.
Explanation: The designated library has not been

defined.
command.
Explanation: The designated drive has been

successfully defined as a member of the specified
library.
System action: The drive is defined and recorded in
the database.
614
Command: Invalid drive name drive name.
Library library name defined.
Explanation: The designated library has been

successfully defined.
ANR8401E
ANR8410I ANR8420E
ANR8410I
Library library name deleted.
ANR8416E
Explanation: The designated library has been deleted

successfully.
System action: The library is deleted.

invalid for library type library type.
Explanation: The specified parameter is not valid for

libraries of the given type. The scratch category must
be at lest 2 less than the private category for 349x
libraries.
ANR8411E
Command: One or more drives are still

Explanation: The command failed because there are

drives defined to the designated library. For the
DELETE LIBRARY and PERFORM LIBACTION
(ACTION=DEFINE) commands, the specified library
cannot have drives currently defined within the library.
User response: Delete all drives from the library, and
ANR8412I
Drive drive name deleted from library

library name.
Explanation: The designated drive has been deleted

successfully from the specified library.
System action: The drive is deleted.
User response: Reissue the command, using only the

proper parameters. If using the scratch category make
sure it is at least 2 less than the private category.
ANR8417E

invalid for drives in library type libraries.
Explanation: The specified parameter is not allowed

when defining or updating drives in a library of the
given type.
User response: Reissue the command, using only the
proper parameters.
ANR8418E
Command: An I/O error occurred while

accessing library library name.

designated library.

ANR8413E
Command: Drive drive name is currently

in use.

associated with the library is identified correctly in the
DEFINE PATH command, and that the library is
access door, make sure it is closed. After checking and
User response: Wait until the drive is no longer in

use, and reissue the command.
ANR8419E
Explanation: The designated drive cannot be deleted

or updated because it is currently in use.
ANR8414E
Command: Drive drive name is not

Explanation: The designated drive has not been

defined in the given library.
drive name. If appropriate, define the drive before
retrying the command.
ANR8415E

Command: The drive or element conflicts

with an existing drive in library library
name.
Explanation: Either there are no more physical drives

in the library, or the specified ELEMENT parameter
conflicts with an existing defined drive in the given
library.
User response: Specify a valid ELEMENT parameter
that is not used by any other drive in the library.
ANR8420E
Command: An I/O error occurred while

accessing drive drive name.
Explanation: The specified parameter must be

provided when processing the given command.

specified drive.
User response: Reissue the command, providing the

required parameter value.

615
ANR8421E ANR8429E
correcting these potential problems, retry the command.
ANR8421E
Command: Unable to start a process for

this command.
Explanation: The server cannot start a background

process to carry out the designated command.
ANR8425I
Checking in volumes in search mode in

Explanation: In response to a QUERY PROCESS

command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. Volumes
are being checked into the given library automatically
using a search for previously-unknown volumes.
System action: The background process operation

continues.
User response: Check for and correct memory

shortages or other server resource constraints, and
User response: None. The process may be canceled by

an authorized administrator using the CANCEL
PROCESS command.
ANR8422I
Command: Operation for library library

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
LIBVOLUME command entered by an administrator.
User response: To obtain status on the process, issue
the QUERY PROCESS command. The process may be
canceled with the CANCEL PROCESS command.
ANR8423I
CHECKIN LIBVOLUME process for

library library name has been canceled.

been working to check in one or more volumes for the
given library is canceled by the CANCEL PROCESS
command.
ANR8424I
Checking in volume volume name in


CHECKIN LIBVOLUME process on the server. The
given volume is being checked in to the designated
library.
ANR8426E
CHECKIN LIBVOLUME for volume

volume name in library library name failed.
Explanation: The background process for a CHECKIN

LIBVOLUME command has failed.
System action: The background process ends, but the
volume has not been checked into the library.
User response: Make sure the library and drive
devices associated with this command are powered on
and ready, and then reissue the command.
ANR8427I
CHECKIN LIBVOLUME for volume

volume name in library library name
Explanation: The specified volume was successfully

checked in to the library during processing of a
CHECKIN LIBVOLUME or LABEL LIBVOLUME
command.
System action: The volume is made available for
mounting in the given library.
ANR8428E
Command: The STATUS parameter is

Explanation: The STATUS parameter must be

provided with the given command.
User response: Reissue the command, and provide a
valid STATUS parameter value.

continues.
ANR8429E

PROCESS command.
Explanation: The command cannot be issued until at

least one drive has been defined in the given library.
Command: No drives are currently


User response: Define a drive in the library, using the
DEFINE DRIVE command, as well as a path to the
616
ANR8430I ANR8438I
drive, using the DEFINE PATH command. Then retry
the failed command.
ANR8430I
Volume volume name has been checked

into library library name.
Explanation: A search-mode CHECKIN LIBVOLUME

process has found the given volume and automatically
checked it into the library.
to perform the operation in response to the

CHECKOUT LIBVOLUME command entered by an
administrator.
ANR8435I
System action: The volume is added to the given

librarys inventory.
ANR8431I
CHECKIN LIBVOLUME process

completed for library library name; volume
count volume(s) found.
Explanation: A search-mode CHECKIN LIBVOLUME

process is completed. The specified number of volumes
have been successfully added to the librarys inventory.
System action: The volumes are made available for
use by the server.

present in library library name.
Explanation: The specified volume cannot be checked

into the given library because it is already present.
User response: Provide the name of a volume that is
not already present in the given library. Use the
QUERY LIBVOLUME command to obtain a full list of
volumes that have already been checked into the
library.
ANR8433E

been working to check out the volume from the given
library is canceled by the CANCEL PROCESS
command.
ANR8436I
Checking out volume volume name from


CHECKOUT LIBVOLUME process on the server.

ANR8432E
CHECKOUT LIBVOLUME for volume

volume name in library library name has
been canceled.

present in library library name.
Explanation: The specified volume cannot be checked

out of the given library because it is not present.

continues.
PROCESS command.
ANR8437E

volume name in library library name failed.
Explanation: The background process for a

CHECKOUT LIBVOLUME command has failed.
volume has not been checked out of the library.
and ready, then retry the command.

User response: Provide the name of a volume that is
present in the given library. Use the QUERY
LIBVOLUME command to obtain a full list of volumes
that reside in the library.
ANR8434I
Command: Operation for volume volume

name in library library name started as
process process ID.
Explanation: A volume check-out process has been

started to handle the removal of a volume from the
given library. The process is assigned the ID specified
in the message.
ANR8438I

volume name in library library name
Explanation: The background process for a

CHECKOUT LIBVOLUME command has completed
successfully.
librarys inventory (if its status is something other than

617
ANR8439I ANR8447E
ANR8439I
library type library library name is ready

for operations.
Explanation: The initialization process for the given

library has completed successfully, and the library is
ready for use.

User response: Reissue the command, specifying that
the volume be assigned a status of PRIVATE.
ANR8444E
System action: The library is made ready for use.

ANR8440E
Initialization failed for library type

library library name; will retry in delay
time minute(s).

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

Command: Library library name is

currently unavailable.
Explanation: The requested operation cannot be

completed because the specified library is unavailable
for I/O operations. The library may still be carrying
out its initialization operations.
User response: Wait until the library initialization
completes or the library becomes ready.
ANR8445I
Volume volume name in library library

name updated.
Explanation: The specified library volume has been

updated successfully.
System action: The library volume inventory is
updated.

library has failed, and will not be retried until the next
time the server needs to access the library.
ANR8446W
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

library name is currently in use.
Explanation: The command cannot be processed

because the specified volume is already being used for
another operation.
activity has completed, and then reissue the command.
If the volume is currently mounted, but idle, you can
dismount it with the DISMOUNT VOLUME command
and then retry this operation.
ANR8443E

library name cannot be assigned a status
of SCRATCH.
Explanation: The volume cannot be assigned to the

given librarys scratch pool because there is a storage
pool volume defined or a volume in the volume history
file with this volume name. Such a volume may still
contain valid data. Assigning the volume to the
librarys scratch pool might result in a destructive
overwrite of the volumes data.
618
Manual intervention required for library

library name.
User response: If the library has an access door, make

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
been taken; it will then continue its operations.
ANR8447E
No drives are currently available in

Explanation: The attempted operation cannot be

completed on the specified library because there are no
available drives. A drive may be unavailable because
an application other than the server may have the
driver opened. This message may also be issued if a
CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
because all the drives are mounted by other processes
or sessions, or the device type was incorrectly specified.
System action: The attempted operation is terminated.
User response: Use the QUERY DRIVE command to
check the online status of the drives. Drives that are
marked "Unavailable since hh:mm yy/mm/dd" are
drives taken offline by the server at the time specified
because of hardware failures or the inability to open
the drive. If the attempted operation is a CHECKIN or
ANR8448E ANR8456E
LABEL command, use the QUERY MOUNT command
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
DISMOUNT VOLUME command to free its drive, and
retry the original operation.
ANR8448E
Scratch volume volume name from library

library name rejected - volume name is
already in use.
Explanation: The designated volume has been used to

satisfy a scratch mount, but the volume is already
defined in a storage pool, or has been used to store
server export, database dump, or database backup
information as recorded in the server volume history
file.
System action: The volume is rejected.
User response: Use a volume that is not in use, or
check out and relabel the rejected volume, assigning it
a new name in the process, or delete the existing
volume that caused the name conflict.
ANR8452E

library has failed. It is retried automatically after the
specified amount of time has elapsed.
powered on and ready.
ANR8453E

unavailable.
Scratch volume volume name rejected volume name is already in use.
Explanation: The designated volume has been used to

satisfy a scratch mount, but the volume is already
defined in a storage pool, or has been used to store
server export, database dump, or database backup
information as recorded in the server volume history
file.
User response: Use a volume that is not in use, or

rename the rejected volume or delete the existing
volume that caused the name conflict.
Command: Library library name is
currently in use.
Explanation: The designated library cannot be deleted

or updated because it is currently in use for an I/O
operation.
User response: Wait until the library is no longer in
use, and then retry the command.
ANR8451I
349X library library name is ready for

operations.

ready for use.
Mismatch detected between external

label (volume name from external label) and
media label (volume name from media label)
in 349X library library name.
Explanation: The external label of a volume was

found to differ from its media label in the designated
library.
System action: The volume will not be accessed.
and ensure that it is properly labeled.
ANR8450E
Initialization failed for 349X library

library name.

library has failed and will not be retried until the next
ANR8454E
ANR8449E
Initialization failed for 349X library

library name; will retry in delay time
minute(s).
ANR8455E

located during audit of library library
name. Volume has been removed from
the library inventory.
Explanation: While processing an AUDIT LIBRARY

command for the given library, the server cannot find
the given volume in the library.
System action: The volume is removed from the
library inventory.
User response: If the volume is needed, it should be
located and checked into the library using the
CHECKIN LIBVOLUME command.
ANR8456E
Multiple volumes named volume name

were found during audit of library
library name.
Explanation: While processing an AUDIT LIBRARY

command for the given library, multiple physical
volumes are found to have the same name.
System action: The first instance of the volume is
619
ANR8457I ANR8465I
retained in the server inventory; all other instances are
ignored.
User response: Remove all of the redundant instances
of the volume from the library. If the volume which the
server retained is found to be the incorrect one, it can
be checked out with the CHECKOUT LIBVOLUME
command; then the correct instance can be checked into
the library with a CHECKIN LIBVOLUME command.
ANR8461I
AUDIT LIBRARY process for library

library name completed successfully.
Explanation: The background process for an AUDIT

LIBRARY command has completed successfully.
System action: The library inventory is updated to
match the contents of the library as found during the
audit operation.
ANR8457I

Explanation: A library audit process has been started

for the given library. The process is assigned the ID
specified in the message.
to perform the operation in response to the AUDIT
LIBRARY command entered by an administrator.
ANR8458I

library name has been canceled.

been working to audit the given library is canceled by
ANR8459I
Auditing volume inventory for library

library name.

command, this message displays the status for an
AUDIT LIBRARY process on the server.
PROCESS command.
ANR8460E

library name failed.
Explanation: The background process for an AUDIT

LIBRARY command has failed.
System action: The background process ends.
and ready, then reissue the command.
ANR8462I
End-of-side reached for device type

volume volume name.
Explanation: The server has detected an end-of-side

condition for the given two sided volume.
System action: The server will access the second side
of the volume.
ANR8463E
Device type volume volume name is write

protected.
Explanation: The server has detected a write-protect

condition for the given volume.
System action: The server will dismount the volume
and continue processing with another volume.
User response: Adjust the write-protect switch on the
volume so that writing is allowed. If the volume is an
optical volume and the write-protect switch is already
set to allow writing, use the MOVE DATA command to
move the data off of the volume. Rewritable volumes
may be reformatted and reused after the data is moved
to another volume.
ANR8464E
command: Invalid update request for

Explanation: An invalid update request has been

made for the given library. This can occur if a new
device name is given and the characteristics of the
device do not match the characteristics of the original
device.
command.
User response: If a different type of library device has
been installed, the old library definition must be
deleted with a DELETE LIBRARY command, and a
new library must be defined. The UPDATE LIBRARY
command cannot be used in this case.
ANR8465I
Library library name updated.
Explanation: An UPDATE LIBRARY request has been

successfully processed for the given library.
System action: The server updates its information
about the library.
620
ANR8466E ANR8472I
ANR8466E
ANR8470W

drive drive name in library library name.
Explanation: An invalid update request has been

made for the given drive. This can occur if a new
device name is given and the characteristics of the
device do not match the characteristics of the original
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
defined. The UPDATE DRIVE command cannot be
used in this case.
ANR8467I
Drive drive name in library library name

updated.
Explanation: An UPDATE DRIVE request has been

successfully processed for the given drive.
about the drive.
ANR8468I
device type volume volume name

dismounted from drive drive name in
Initialization failure on drive drive name

in library library name.
Explanation: The specified drive could not be

initialized at this time.
System action: The initialization of the specified
library continues.
User response: An internal validation of the specified
drive and its path failed. Ensure that the drive's path
definition to the local server is correct. Examine all
previous messages for information regarding the
specified drive. If necessary, delete and redefine the
path from the local server to the specified drive. After
redefining the path or correcting any issues that were
reported by related error messages, the drive's
initialization is retried on the next attempt to mount the
specified drive.
ANR8471E
Server no longer polling drive drive name

in library library name - path path will be
marked off-line.
Explanation: The server is unable to use the

mentioned drive via the specified path. This may be for
the following reasons:
v The drive cannot be opened.
v In the case of a 3494 or a library that can be
partitioned, the drive may be unavailable to the
library manager, may be in use by another
application, or may be loaded with a cartridge not
labeled for server use.
Explanation: The specified volume has been

dismounted from the given drive.
System action: The path to the drive is offline and is

not used for tape operations.
User response: Determine the reason the path to the

drive is inaccessible, such as hardware errors reported
in the system logs. Render any needed corrections to
the hardware. Then the path may be made online by
issuing the UPDATE PATH command with the
ONLINE=YES option.
User response: If the type of the given library is

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
libraries, this message is purely informational.
ANR8469E
Dismount of device type volume volume

name from drive drive name in library
Explanation: An attempt to dismount the designated

volume failed due to an I/O error.
User response: If the type of the given library is
MANUAL, the volume can be manually ejected and
removed from the drive. For automated libraries,
manual intervention may be required to correct the
problem.
ANR8472I
Error reading label of volume in drive

drive name of library library name.
Explanation: While processing a search-mode

CHECKIN LIBVOLUME command for the designated
library, the server finds a volume whose label cannot be
read.
System action: The volume is dismounted and is not
checked into the library.
and ensure that it is properly labeled. After doing so,
the volume can be checked into the library.
621
ANR8473I ANR8480E
ANR8473I
Volume volume name was found in

storage element slot element address in
library library name. It may still be in the
drive.
Explanation: The specified volume was found in the

storage slot of a cleaner cartridge. After it was loaded
into a drive for cleaning, TSM determined that it is not
a cleaner cartridge. TSM encountered an error trying to
move the cartridge back to the storage slot of the
cleaner cartridge. If the volume is a storage pool
volume, TSM already attempted to make it unavailable.
Review the output of the QUERY VOLUME F=D
command for storage pool volumes. Review the output
of the QUERY VOLHISTORY command for non-storage
pool volumes.
User response: Verify all other cleaner cartridges are
in the correct storage slots. Issue the QUERY
LIBVOLUME command to obtain the storage slots of
all the cartridges currently checked into TSM. Remove
the cartridge in the storage slot identified in the
ANR8911W message. Remove the specified volume
from the drive. Issue an AUDIT LIBRARY command
against the library.
ANR8474E
Command: One or more paths are still

defined to library library name.

User response: Use a different libtype such as
MANUAL to perform the operation.
ANR8477E
Device type device type is incorrect for

drive drive name.
Explanation: The device type of the specified drive on

the library client is not compatible with the device type
for the same drive on the library manager.
User response: Delete the drive definition on the
library client, and re-define the drive specifying the
correct device. If this does not correct the problem,
contact your service representative for assistance.
ANR8478W
Invalid home slot address in inventory

for library library name; volume = volume
name;slot = slot number.
Explanation: The specified volume's home slot in the

library inventory does not match the database
inventory.
User response: Run 'audit library' against the
specified library.

because there are still paths defined to it.
ANR8479W
Explanation: The library audit process was unable to

audit storage slot with the specified element address.
This is probably due to no drive device being available
into which to load the cartridge. It can also be due to
library or drive I/O errors occurring during the audit
process.
User response: Delete all paths to this library, and

ANR8475I
Dismount of volume volume name failed.

It may still be in the drive.
Explanation: The specified volume could not be

dismounted. TSM encountered an error trying to
dismount the volume. If the volume is a storage pool
volume, TSM already attempted to make it unavailable.
Review the output of the QUERY VOLUME F=D
command for storage pool volumes. Review the output
of the QUERY VOLHISTORY command for non-storage
pool volumes.
System action: The AUDIT LIBRARY command fails.

User response: Verify that for every type of cartridge
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
to hardware failure and repair.
ANR8480E

User response: Review message ANR8469E in the
activity log. Check if the volume is still loaded in the
drive. If the volume is not in the drive, determine
where the volume is located in the library.
ANR8476E
Operation is not supported for the

libtype of library library name.
The drive Drive Name was not found for

library Library Name.
Explanation: The missing drive needs to be defined to

successfully run the current 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
could indicate a server internal error.
Explanation: The operation failed because the libtype

of the library is not supported for the operation.
622
Unable to audit slot-element slot-element

of library library name.
ANR8481I ANR8488I
ANR8481I
The library library name already has an

AUDIT LIBRARY operation pending
mount activity.
Explanation: Libraries of type SHARED can only have

one AUDIT LIBRARY operation waiting on mount
activity. All subsequent AUDIT LIBRARY operations
will be canceled.
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.
Explanation: The indicated operation has failed

because the entry/exit port of the specified library is
full.
User response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
any remaining eligible volumes.
ANR8483W
A device class can not be found for the

Explanation: A library client audits a SHARED type

Library, but there is no device class defined for that
library.
System action: The AUDIT LIBRARY command fails.
User response: Define or update a device class for the
library using the DEFINE DEVCLASS or UPDATE
DEVCLASS command.

the drive. Use the QUERY MOUNT command to query
mounted drives and their mount mode. If there are
DISMOUNT VOLUME command to free the drive, and
retry the original operation.
ANR8485E
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
caused by an inexistent device, a device with powered
off, or a device with firmware/hardware problems.
System action: The transaction needing the drive fails.
User response: Make sure the device is online and
connected to the host system. If the device is not
removed or is powered off, do a power cycle to
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.
ANR8486I

No drives are available to be mounted

in MODE mode with format FORMAT in
library LIBRARY NAME.

completed on the specified library. Either there are no
available drives with the specified format, or the
volume has the wrong access mode. A drive can be
unavailable because another application opened the
drive. This message can also be issued if a CHECKIN
or LABEL command is issued and no drive is available
to service the operation. This can occur when all drives
are mounted by other processes or sessions, or the
device type was incorrectly specified.

name is reserved -- owning server: owner
name, status: RESERVED (session: session
ID, process: process number).

point reserved for future I/O operations in the given
device class. The session and process values are relative
to the server that owns this mount point.
ANR8487I
ANR8484E
Unable to open a SCSI device drive

name, error code=error value set by server.

name is waiting for the volume mount to
complete -- owning server: owner name,
status: WAITING FOR VOLUME
(session: session ID, process: process
number).

point in the given device class waiting for the volume
mount to complete. The session and process values are
relative to the server that owns this mount point.
System action: The attempted operation ends.

ANR8488I

mounted mount mode in drive drive name
-- owning server: owner name, status: IN
USE (session: session ID, process: process
number).
623
ANR8489I ANR8495E
in use, meaning that read or write operations, or both,
are being performed. The session and process values
are relative to the server that owns this mount point.
ANR8489I

-- owning server: owner name, status:
IDLE (session: session ID, process: process
number).

period, it will be automatically dismounted. The
session and process values are relative to the server
that owns this mount point.
ANR8490I

DISMOUNTING (session: session ID,
process: process number).

being dismounted by the server. The session and
process values are relative to the server that owns this
mount point.
ANR8492I

RETRY, meaning an attempt is being made to
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
operation will fail and the volume will be automatically
dismounted. The session and process values are relative
to the server that owns this mount point.
ANR8493I
ANR8491I

RETRY DISMOUNT FAILURE (session:
session ID, process: process number).

command, the server indicates that it is currently
retrying the dismount of the given volume because of a
failure during the previous dismount from the specified
drive. The session and process values are relative to the
server that owns this mount point.

User response: For automated libraries, this message
is purely informational.
ANR8494E
Command: An option specified is not

valid for library type libraries.
Explanation: A requested option is not valid for

libraries of the given type for the specified command.
ANR8495E

be written by BACKUP DB operation.

BACKUP DB data to be written to it. Or there is no
space available on the destination filespace to write this
backup to.
overwritten by the requested BACKUP DB command,
or that there is not enough space available.
BACKUP DB command.

624
device type volume volume name mounted

in drive drive name in library library
name.
Explanation: The specified volume has been mounted

in the specified drive.


RETRY (session: session ID, process:
process number).
ANR8496E ANR8502E
ANR8496E
Device class device class not defined in

device configuration information file.
Explanation: The command that has been issued

requires that the specified device class be defined in the
device configuration information file. This definition
was not found or the statements in the file are in the
wrong order.
valid device class. Refresh your device configuration
information file by issuing the BACKUP DEVCONFIG
command.
ANR8497E
Library library not defined in device

configuration information file.

specified library be defined in the device configuration
information file. This definition was not found or the
statements in the file are in the wrong order.
User response: Refresh your device configuration
command. Make sure a library is defined for the device
class. Reissue the command.
ANR8498E
Drive not defined for library library in

device configuration information file.

specified drive be defined in the device configuration
information file for the specified library. This definition
was not found or the statements in the file are in the
wrong order.
command. Make sure a drive is defined for the library
associated with the device class. Reissue the command.
ANR8499I
Command accepted.
Explanation: The command is accepted and processed

by the server.
System action: The server processes the command.
ANR8500E
No valid path is defined for library

library name or any of its drives in device
configuration information file.
Explanation: The specified command requires that a

path be defined in the device configuration information
file for the specified library and its drive. This valid
definition was not found, or the statements in the file

are in the wrong order.
command. Make sure a path is defined for the library
and its drive associated with the device class. Verify the
correct source is used in these path definitions. If the
default server name is not used as the source, a SET
SERVERNAME command is required in the device
configruation information file. Reissue the command.
ANR8501E
System return code return code received

opening volume server volume name with
file name file name
Explanation: The server or storage agent attempted to

access the file name indicated but failed to open the
volume. The indicated system return code was
received. The actual volume name corresponds to the
file name that the server uses. The server volume name
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: The server or storage agent can
recover from some failures by requesting access to
different volumes. If there is a directory definition
problem, this message may be displayed multiple times
during retries with different volumes. The directory
names associated with the device class definition in the
server should be checked for correctness in the number
and names of directory entries. PATH definitions for
each of the FILE drives should be checked that the
number of directories in the PATH definition match the
number in the server's device class definition and that
directories exist and are accessible to servers and
storage agents accessing server directories via their
own path names. For example, if the server has the
following definition:
DEFINE DEVCLASS FILE DEVTYPE=FILE
DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a
storage agent has the following PATH definition:
DEFINE PATH STA FILE1 SRCTYPE=SERVER
DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE
DIR=X:\DIR1,X:\DIR2 then system STA must have
drive X set to access directory L:\FILECLASS on the
server so that directories DIR1 and DIR2 correspond to
the correct destinations on the storage agent and that
the number of directories match between the PATH and
the DEVCLASS definitions.
ANR8502E
Errno errno received checking WORM

directory directory name on Filer.
Explanation: The server attempted to access the

named directory on the NetApp SnapLock Filer, but the
attempt failed with the indicated error code.
System action: If you were trying to define a storage
625
ANR8503E ANR8504E
pool or update a device class associated with a storage
pool, the command fails. If this error is encountered
during server initialization, server initialization
continues, but operations involving this storage pool
will not be allowed until the issue is resolved.
User response: This may be caused by an error in the
NetApp Filer or with the communications between
your server and the NetApp Filer. Verify that the
network is operational, that the SnapLock Filer is
accessible from your server, and consult NetApp
SnapLock Filer documentation to resolve the issue;
then, retry the command.
ANR8503E
A failure occurred in writing to volume

server volume name.
Explanation: The server or storage agent was writing

to the indicated volume name when a failure occurred.
System action: The server or storage agent stops
writing to the specified volume.
and names of directory entries.
The permissions associated with newly created files
should be checked to ensure the server and storage
agent can write to newly created files. Depending on
the system, a mask value may need to be adjusted. The
system error or event log should be checked for
indications of hardware or software errors from file
systems.
For a remotely mounted file system, as when SANergy
is used, ensure that the remote file system is mounted
and useable to the storage agent. The file system
should be checked to ensure that sufficient space is
available. While the server checks space, multiple
device classes or servers using the same file system can
cause the server's space checking to underestimate
available space.
For storage agents, PATH definitions for each of the
FILE drives should be checked to ensure that the
number of directories in the PATH definition matches
the number in the server's device class definition and
that directories exist and are accessible to servers and
626

ANR8504E
A failure occurred in flushing data to

volume server volume name.
Explanation: The server or storage agent was writing

to the indicated volume name when a failure occurred.
The failure occurred during a flush operation when the
server was attempting to synchronize its progress of
data written with that of the file system. If the file
system becomes full, it is possible to receive no error
indications until the flush operation is attempted.
System action: The server or storage agent stops
writing to the specified volume. The transaction in
progress is rolled back.
and names of directory entries.
The permissions associated with newly created files
should be checked to ensure the server and storage
agent can write to newly created files. Depending on
the system, a mask value may need to be adjusted. The
system error or event log should be checked for
indications of hardware or software errors from file
systems.
For a remotely mounted file system, as when SANergy
is used, ensure that the remote file system is mounted
and useable to the storage agent. The file system
should be checked to ensure that sufficient space is
available. While the server checks space, multiple
device classes or servers using the same file system can
cause the server's space checking to underestimate
available space.
For storage agents, PATH definitions for each of the
FILE drives should be checked to ensure that the
number of directories in the PATH definition matches
the number in the server's device class definition and
that directories exist and are accessible to servers and
ANR8505I ANR8510E
ANR8505I
Verifying path definitions for library

library name between storage agent
storage agent and library manager primary
library manager. Processing library count
out of total library count libraries.
Explanation: The specified library path definition is

being verified for storage agent initialization.
System action: The server processes the verification
for the specified library.
User response: If the server does not finish
verification for all the counted shared libraries, verify
connectivity and configuration of the primary library
manager paths. Check the library manager of the last
storage agent displayed in the library path verification
message.
ANR8506E
The library library name is not

compatible with stand-alone, utility
operations.
Explanation: The specified library cannot operate in

stand-alone mode such as DUMP DB or RESTORE DB.
User response: If this is a FILE library, use a device
class that does not use a FILE library. A FILE device
class does not need a library, and thus, can be updated
with LIBRARY="" and SHARED=NO. Update your
device configuration file appropriately for the
stand-alone operation, and then if needed, return the
device class to its original state using a FILE library or
with SHARED=YES when the server is running.
ANR8508E

archive log data to be written to it. Or there is no space
available on the destination filespace to write this
backup to.
overwritten by the DB's archive log operation, or that
there is not enough space available.
contain any valuable data, delete it.
ANR8509E
Volume volume name is using an

encryption key that is not unique and
therefore is not secure.
Explanation: Each volume should have a unique

encryption key. This volume inappropriately shares an
encryption key with other volumes.
System action: The operation completes.
User response: Moving the data from this volume to
new volume will create a unique encryption key for the
new volume and make the data more secure. Before
moving the data, mark this volume READONLY to
prevent Tivoli Storage Manager from appending data to
the volume. Then, use the MOVE DATA command to
move the data from this volume to a new volume in
your encryption storage pool.
No compatible drives are available for

device class devclass name.

completed for the specified device class because there
are no available drives. This message can indicate an
invalid FORMAT or DEVTYPE value for the specified
device class. The message can also indicate that the
FORMAT and DEVTYPE values are valid, but no
compatible drives are online.
System action: The attempted operation fails.
User response: Use the QUERY DEVCLASS command
to check the device class's FORMAT and DEVTYPE
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
that are compatible with the device class attempting
this operation. If there are no compatible drives, correct
this configuration and retry the operation.
ANR8510E
ANR8507W

be written by DB2's archive log
operation.
No valid path is defined for the

ZOSMEDIA library library name .
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
resolve the z/OS Media server name.
System action: The mount request is not processed.
User response: Define a library path and specify the
z/OS Media server with the ZOSMEDIASERVER
parameter. For instance: consider a ZOSMEDIA library
named ZLIB1 and a TSM server name of SERVER1. The
z/OS Media server that is accessible using IP address
of 9.8.7.6 and is listening on port 1492 and is named is
ZMEDSRV1. The following commands properly
configure server SERVER1 for accessing ZLIB1. .
DEFINE LIBRARY ZLIB1 LIBTYPE=ZOSMEDIA
DEFINE SERVER ZMEDSRV1 SERVERPASS=SECRET
HLA=9.8.7.6 LLA=1492 DEFINE PATH SERVER1 ZLIB1
SRCTYPE=SERVER DESTTYPE=LIBRARY
ZOSMEDIASERVER=ZMEDSRV1 .
627
ANR8511E ANR8516W
ANR8511E
Unable to resolve ZOSMEDIASERVER

mediaservername from the library path.
Explanation: The storage operation requires that a

server defintion exist that matches the
ZOSMEDIASERVER name of the library path. Without
a SERVER defined, the storage operation can not be
completed because the request is unable to determine
the z/OS Media servers HLA and LLA.
System action: The mount request is not processed.
User response: Determine the High Level Address (
HLA ) and Low Level Address ( LLA ) of the z/OS
Media server and use DEFINE SERVER command to
build a server definition that represents the z/OS
Media server. The servername that is used to define the
z/OS Media server must match the
ZOSMEDIASERVER name of the library PATH. For
instance: consider a ZOSMEDIA library named ZLIB1
and a TSM server name of SERVER1. The z/OS Media
server that is accessible using IP address of 9.8.7.6 and
is listening on port 1492 and is named is ZMEDSRV1.
The following commands properly configure server
SERVER1 for accessing ZLIB1. . DEFINE LIBRARY
ZLIB1 LIBTYPE=ZOSMEDIA DEFINE SERVER
ZMEDSRV1 SERVERPASS=SECRET HLA=9.8.7.6
LLA=1492 DEFINE PATH SERVER1 ZLIB1
SRCTYPE=SERVER DESTTYPE=LIBRARY
ZOSMEDIASERVER=ZMEDSRV1
ANR8512E
and specify a SERVERPASSWORD that does not exceed

16 characters and ensure it contains characters that
match the passphrase option on the z/OS Media server.
ANR8514W
Explanation: The z/OS Media server made an attempt

to EXTEND the VSAM LDS FILE volume using the
SECONDARYALLOCATION value from the FILE
device class and failed.
System action: The WRITE operation fails and the
FILE volume is marked "read-only".
User response: Allow TSM for z/OS Media server to
create EA-enabled VSAM linear data set volumes. 1.
Use SMS to manage the VSAM Linear data sets that are
associated with the prefix attribute of the FILE device
class. 2. Associate the data sets with a data class (an
SMS construct) that specifies the extended format and
extended addressability options. To make this
association between data sets and the data class, use an
automatic class selection (ACS) routine to assign the
TSM for z/OS Meida VSAM linear data sets to the
relevant SMS data class. The ACS routine does the
assignment based on the data set name.
ANR8515W
Cannot specify RETENTION with

EXPIRATION during DEFINE or
UPDATE DEVCLASS.
Explanation: The DEFINE DEVCLASS cannot specify

both RETENTION and EXPIRATION, they are conflict
parameters.
System action: The command request is not
processed.
User response: If a device class has an existing
EXPIRATION value, the devclass cannot update if
RETENTION is specified. If a device class has existing
RETENTION value, the device class cannot update if
EXPIRATION is specified. The two parameters
(RETENTION and EXPIRATION ) are mutually
exclusive.
zOS Media Server (server name)
password is too long to use for
authentication with TSM for z/OS
Media. The password cannot exceed 16
characters.
Explanation: The SERVERPASSWORD must be

specified with 16 characters or less. The password must
match the passphrase option on the target z/OS Media
server.
System action: The volume is not deleted on the z/OS

Media server.
User response: Deremine why the z/OS Media server
cannot be contacted. Examine the TSM activity log for
message ANR8515W and carefully consider removing
the associated dataset on the z/OS system.
The z/OS Media server is unreachable at
HLA and LLA .
Explanation: The z/OS Media server cannot be

reached during a ZOSMEDIA library request. The TSM
server may continue the operation even though the
z/OS Media server cannot be reached.
System action: The operation likely fails.
User response: Determine why the z/OS Media server
cannot be contacted.
System action: The operation is not processed.

User response: Issue the UPDATE SERVER command
628
The deletion of volume belonging to

z/OS Media library is imminent,
however the z/OS Media server is
unreachable resulting in the TSM Server
volume inventory reflecting the deleted
volume.
Explanation: The z/OS Media server cannot be

reached during a volume deletion request. The TSM
server continues the operation even though the z/OS
Media server cannot be reached.
ANR8516W
ANR8513E
TSM for z/OS Media server (server name)

could not extend the FILE volume
volume name.
ANR8517E ANR8524W
ANR8517E
The z/OS Media server is reachable at

HLA and LLA however fails to connect
because of an authentication failure..
Explanation: The z/OS Media server could be reached

during a ZOSMEDIA library request. However,
authentication could not be completed. The TSM server
will not continue the operation because the z/OS
Media server connection can be authenticated.
connection cannot be authenticated. Check to ensure
the PASSPHRASE option on the TSM z/OS Media
server matches the serverpassword of the media server
definiton on the TSM Server. The password cannot
exceed 16 characters.
ANR8518E
ANR8521E
Unable to allocate dataset dynalloc rc =

dynalloc error = Hex and dynalloc info
=.
Explanation: The z/OS Media server cannot allocate a

dataset during a ZOSMEDIA library request and the
TSM server fails the operation.
cannot allocate the volume. Examine the z/OS Media
server joblog for ANZ5031I messages for a summary of
dynalloc related info and error messages. Review the
z/OS SYSLOG for error conditions associated with the
failed allocation request.
ANR8522E

drive drive name in library library name.
The z/OS Media server is unreachable at

HLA with LLA and fails to complete a
connection because of a protocol
violation.
Explanation: An invalid request has been made for

the specified drive. This drive is part of a virtual tape
library(VTL). The requested operation does not apply
for drives in a VTL.
Explanation: The z/OS Media server may not be

listening on the target LLA port. The TSM server will
not continue the operation because the z/OS Media
server connection can be established.

command.
User response: Do not attempt to change cleaning

settings for virtual drives. If this library is not a VTL,
use the UPDATE LIBRARY command to change the
library type to SCSI and retry the operation.
ANR8519E
The z/OS Media server is unable to

open volume using dataset name .
Explanation: The z/OS Media server cannot OPEN a

volume during a ZOSMEDIA library request and the
TSM server fails the operation.
cannot OPEN the volume. Examine the z/OS Media
server joblog, and the z/OS SYSLOG for error
conditions associated with the volume or dataset name.

connection cannot be established. Check to ensure the
z/OS Media server is listening on the target IP address
and port address. The protocol violation indicates an
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
definition.
ANR8523E
The path from the source server to the

destination library is taken offline.
Explanation: Ensure the z/OS Media server is running

and listening on the appropriate port address. If the
z/OS Media server is listening on the intended port
address and the authentication is configured properly,
there could a problem with the z/OS Media server
version that requires the library path be taken offline.
System action: The library path is offline.
ANR8520E
Command: StorageTek Automated

Cartridge System Library Software
(ACSLS) API module is not available
from the system for ACSLS libraries.
Explanation: The operatios of the ACSLS type library

require the ACSLS API module loaded to the system. If
this module is not loaded to the system, define ACSLS
library will fail.
User response: Ensure that ACSLS API module is
installed to the system.
User response: Determine the service level the z/OS

Media server. Check the current README for the
installed TSM Server by searching for z/OS Media
server prerequisite specifications.
ANR8524W
The element address of the drive drive

name might be incorrect in the library
library name.
Explanation: The element=autodetect parameter on

the DEFINE DRIVE command is not supported for a
network attached SCSI (NAS) drive. An invalid element
address will be assigned to the device if the option is
used.
629
ANR8525E ANR8551E (HP-UX)

System action: The move tape volume operation fails.
v Refer to the other displayed messages to determine

why the open operation has failed. Correct the
User response: Issue the QUERY DRIVE f=d

command to verify the value in the Element field. If
field is empty, issue the UPDATE DRIVE command and
specify a value for the element=address paramenter.
v If you have entered a file name ensure that the file

name is correct and that it exists.
ANR8525E
ANR8550E (Solaris) Error opening file name.
Unable to allocate the device specified

by unit value
Explanation: The z/OS media server cannot allocate

the specified device during a ZOSMEDIA library
request because the UNIT value in the device class that
is associated with the volume mount request specifies a
device address that is already allocated.
System action: The Tivoli Storage Manager server fails
the operation.
User response: Verify that the MOUNTLIMIT
parameter value in the device class is 1 if the UNIT
value specifies a device address. Additionally, you can
update the MOUNTRETENTION parameter value to 0.
This will ensure that the mounted volume is
dismounted after each use.
ANR8550E (AIX) Error opening filespec.
Explanation: An error occurs while attempting an
open operation.
User response:
Explanation: An error occurs while the server

attempts a file open operation.
User response:
ANR8550E (Windows) Error opening filespec.
attempting an open operation.
User response:
ANR8551E (AIX) An error (error code) occurred during
a write operation.
Explanation: An error occurs while attempting a write
operation.
ANR8550E (HP-UX) Error opening file name.


to determine why the write operation failed; correct the

User response:
ANR8550E (Linux) Error opening file name.
ANR8551E (HP-UX) An error (error code) occurred

attempts a write operation.
to determine why the write operation failed. Correct
the problem and restart the process.

User response:
630
ANR8551E (Linux) ANR8553E (HP-UX)

ANR8551E (Linux) An error (error code) occurred
ANR8552E (Linux) An error (error code) occurred



attempts a read operation.

to determine why the write operation failed; correct the

to determine why the read operation failed; correct the
ANR8551E (Solaris) An error (error code) occurred

ANR8552E (Solaris) An error (error code) occurred




to determine why the write operation failed. Correct

to determine why the read operation failed. Correct the
ANR8551E (Windows) An error (error code) occurred



attempting a write operation.

attempting a read operation.

to determine why the write operation has failed.
Correct the problem and restart the process.

to determine why the read operation has failed. Correct
ANR8552E (AIX) An error (error code) occurred during

a read operation.
ANR8553E (AIX) Device type volume volume name

cannot be overwritten by DUMPDB
operation.
Explanation: An error occurs while attempting a read

operation.
to determine why the read operation failed; correct the
ANR8552E (HP-UX) An error (error code) occurred
to determine why the read operation failed. Correct the

DUMPDB data to be written to it.
System action: The server has detected that the given
overwritten by the requested DUMPDB operation.
DUMPDB operation.
ANR8553E (HP-UX) Device type volume volume name
operation.
volume already contains data that would be
631
ANR8553E (Linux) ANR8554W (Solaris)

DUMPDB operation, or specify a different volume
name.
ANR8553E (Linux) Device type volume volume name
operation.
process assumes the device class is devtype=FILE and

writes to or reads from a file.
to determine why the device class is not defined.
Correct the problem and restart the command if you do
not wish to write to or read from a file.

ANR8554W (HP-UX) Dump/load command: Device

class device class name not defined.
Devtype of FILE is assumed.

Explanation: The specified device class name is not

defined with the DUMPLOADDB DEVCLASS option,
to the server in the server options file or the server is
not able to define the specified device class.

name.
ANR8553E (Solaris) Device type volume volume name
operation.
name.
ANR8553E (Windows) Device type volume volume
name cannot be overwritten by
DUMPDB operation.
DUMPDB operation.
ANR8554W (AIX) Dump/load command: Device class
device class name not defined. Devtype of
FILE is assumed.
System action: Processing continues. The dump/load

ANR8554W (Linux) Dump/load command: Device class
device class name not defined. Devtype of
FILE is assumed.
ANR8554W (Solaris) Dump/load command: Device
class device class name not defined.
Devtype of FILE is assumed.
632
ANR8555E (AIX) ANR8556E (Windows)

ANR8555E (AIX) Error error code (error string)
occurred during a read operation from
disk disk name.
ANR8556E (AIX) Error error code (error string)

occurred during a write operation to
disk disk name.
Explanation: An error occured while attempting a

read from disk.

write to disk.
User response: Correct the problem and start the

process again.
User response: Correct the problem and restart the

process.
ANR8555E (HP-UX) An error (error code, error string)

disk disk name.
ANR8556E (HP-UX) An error (error code, error string)

disk disk name.

read from disk.

write to disk.

process.

process.
ANR8555E (Linux) An error (error code, error string)

disk disk name.
ANR8556E (Linux) An error (error code, error string)

disk disk name.

read from disk.

write to disk.

process.

process.
ANR8555E (Solaris) An error (error code, error string)

disk disk name.
ANR8556E (Solaris) An error (error code, error string)

disk disk name.

read from disk.

write to disk.

process.

process.

during a read operation from disk disk
name.

during a write operation to disk disk
name.

read from disk.

write to disk.

process.

process.
633
ANR8557W (AIX) ANR8577E (Windows)

ANR8557W (AIX) Retrying failed I/O operation for
disk disk name, error number number.
Explanation: An error occured while attempting an
I/O operation on a disk volume. The request will be
retried.
System action: The failed I/O operation is attempted
again.
User response: Correct the problem being reported to
avoid more errors in the future, or contact AIX support
for assistance.
ANR8558E (AIX) I/O vector element bufP: buffer
address, len: buffer length, offset: file offset,
errno: errno.
Explanation: This is a diagnostic message showing
details of an AIO request which had an error. This
message is normally proceeded by ANR8555E or
ANR8556E and offers additional information related to
the I/O error.
User response: Correct the problem and start the
process again.
ANR8577E (AIX) Tivoli Storage Manager was not
able to open the SSL key-ring file file
name. The GSKit return code is return
code.
Explanation: Initialization of the SSL environment
User response: Verify that the correct SSL key-ring file
is in the server instance directory. If the password was
changed with an external utility, use the SET
SSLKEYRINGPW command to resynchronize the
key-ring file password with the value that the server
uses. If the problem persists then delete the key-ring
file and run the DELETE KEYRING server command so
that the server can generate a new key-ring file.
ANR8577E (HP-UX) Tivoli Storage Manager was not
code.
634

ANR8577E (Linux) Tivoli Storage Manager was not
code.
ANR8577E (Solaris) Tivoli Storage Manager was not
code.
ANR8577E (Windows) Tivoli Storage Manager was
not able to open the SSL key-ring file
file name. The GSKit return code is return
code.
ANR8578E (AIX) ANR8579E (Windows)

ANR8578E (AIX) The Tivoli Storage Manager
database does not have a password for
the SSL key-ring file.
ANR8579E (AIX) The SSL key ring file does not

exist, but the Tivoli Storage Manager
database contains a password for it.


User response: Delete the key-ring file so that TSM

can generate a new one.
User response: Restore a copy of the key ring file or

use DELETE KEYRING so that Tivoli Storage Manager
can generate a new keyring file and password.
ANR8578E (HP-UX) The Tivoli Storage Manager

ANR8578E (Linux) The Tivoli Storage Manager
ANR8579E (HP-UX) The SSL key ring file does not

ANR8579E (Linux) The SSL key ring file does not


ANR8578E (Solaris) The Tivoli Storage Manager

ANR8578E (Windows) The Tivoli Storage Manager
User response: Delete the keyring file so that TSM can
generate a new one.

ANR8579E (Solaris) The SSL key ring file does not
ANR8579E (Windows) The SSL key ring file does
not exist, but the Tivoli Storage
Manager database contains a password
for it.
635
ANR8580E (AIX) ANR8582E (HP-UX)

ANR8580E (AIX) An SSL write error occurred on
session session. The GSKit return code is
gsk return code.
ANR8581E (HP-UX) An SSL read error occurred on

gsk return code.
Explanation: An error occurred during an SSL write

operation.
Explanation: An error occurred during an SSL read

operation.
ANR8580E (HP-UX) An SSL write error occurred on

gsk return code.
ANR8581E (Linux) An SSL read error occurred on

gsk return code.

operation.

operation.
ANR8580E (Linux) An SSL write error occurred on

gsk return code.
ANR8581E (Solaris) An SSL read error occurred on

gsk return code.

operation.

operation.
ANR8580E (Solaris) An SSL write error occurred on

gsk return code.
ANR8581E (Windows) An SSL read error occurred on

gsk return code.

operation.

operation.
ANR8580E (Windows) An SSL write error occurred

on session session. The GSKit return
code is gsk return code.
ANR8582E (AIX) An SSL open-socket error occurred

on session session. The GSKit return
code is gsk return code.

operation.
Explanation: An error occurred during an SSL

socket-open operation.
ANR8581E (AIX) An SSL read error occurred on

gsk return code.
ANR8582E (HP-UX) An SSL open-socket error

occurred on session session. The GSKit

operation.

636
ANR8582E (Linux) ANR8584I (Linux)

ANR8582E (Linux) An SSL open-socket error
User response: Verify that the client is properly

configured for SSL and retry the operation.
ANR8583E (Solaris) An SSL socket-initialization
error occurred on session session. The
GSKit return code is gsk return code.
handshake process.
ANR8582E (Solaris) An SSL open-socket error


ANR8583E (Windows) An SSL socket-initialization

handshake process.
ANR8582E (Windows) An SSL open-socket error


ANR8583E (AIX) An SSL socket-initialization error

port port number.
port number.

handshake process.
User response: None
ANR8584I (HP-UX) The SSL TCP/IP Version 6 driver

is ready for connection with clients on
port port number.

ANR8583E (HP-UX) An SSL socket-initialization

port number.

handshake process.
User response: None
ANR8584I (Linux) The SSL TCP/IP Version 6 driver

port port number.

ANR8583E (Linux) An SSL socket-initialization error
handshake process.

port number.
User response: None
637
ANR8584I (Solaris) ANR8586E (Linux)

ANR8584I (Solaris) The SSL TCP/IP Version 6 driver
port port number.
port number.
User response: None

is ready for connection with
administrative clients on port port
number.

port number.
User response: None
ready for connection with administrative
number.
number.

number.
ANR8586E (AIX) The server was not able to create
the key-ring file file name. The GSKit
key-management return code is return
code.
User response: Verify that permissions to the server
instance directory are correct.
ANR8586E (HP-UX) The server was not able to create
code.
ANR8586E (Linux) The server was not able to create
code.
638
ANR8586E (Solaris) ANR8588E (Linux)

ANR8586E (Solaris) The server was not able to create
code.
ANR8587E (Solaris) The server was not able to create

the SSL self-signed certificate. The
GSKit key management return code is
return code.



User response: Check the GSKit return code and take

appropriate action.
ANR8586E (Windows) The server was not able to

create the key-ring file file name. The
GSKit key-management return code is
return code.

create the SSL self-signed certificate.
The GSKit key management return code
is return code.




appropriate action.
ANR8587E (AIX) The server was not able to create

return code.
ANR8588E (AIX) The server was not able to export

to the SSL public certificate file file
name. The GSKit key-management

Explanation: The certificate export file could not be

generated for use by the Tivoli Storage Manager clients.

appropriate action.

ANR8587E (HP-UX) The server was not able to create

return code.
ANR8588E (HP-UX) The server was not able to

export to the SSL public certificate file
file name. The GSKit key-management



appropriate action.

ANR8587E (Linux) The server was not able to create

return code.
ANR8588E (Linux) The server was not able to export

to the SSL public certificate file file
name. The GSKit key-management



appropriate action.

639
ANR8588E (Solaris) ANR8590I (Linux)

ANR8588E (Solaris) The server was not able to
ANR8589E (AIX) The server was not able to
initialize the GSKit key-management
environment. The GSKit
code.
Explanation: The GSKit key-management subsystem
could not be initialized.

User response: Verify that permissions to execute the
GSKit key management dynamic-link libraries are
correct.
ANR8589E (Solaris) The server was not able to
code.
correct.
code.
correct.

correct.
ANR8589E (HP-UX) The server was not able to
code.
correct.
ANR8590I (AIX) Session session connection is using

SSL version SSL version, cipher
specification cipher specification.
Explanation: An SSL connection was established using
the listed SSL version and cipher specification.
User response: None
ANR8590I (HP-UX) Session session connection is
using SSL version SSL version, cipher
User response: None
ANR8589E (Linux) The server was not able to

code.
ANR8590I (Linux) Session session connection is using



640
ANR8590I (Solaris) ANR8593E (AIX)

User response: None
ANR8590I (Solaris) Session session connection is
ANR8592I (Linux) Session session connection is using

specification cipher specification certificate
serial number certificate serial number.
the listed SSL version, cipher specification and
ceritificate serial number.
User response: None
User response: None

ANR8590I (Windows) Session session connection is
ANR8592I (Solaris) Session session connection is

specification cipher specification,
certificate serial number certificate serial
number.

the listed SSL version, cipher specification, and
cerificate serial number.
User response: None

ANR8591E (Windows) IBM GSKit version 8 must be

installed on the system.
Explanation: The server requires IBM GSKit version 8.
User response: To install IBM GSKit version 8, you
must install the server and restart it.
ANR8592I (AIX) Session session connection is using
number.
certificate serial number.
ANR8592I (HP-UX) Session session connection is
number.
certificate serial number.
ANR8592I (Windows) Session session connection is

number.
cerificate serial number.
ANR8593E (AIX) Failure to update key-ring file
password.
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
new password. The server's record of the password
may be incorrect or the specified new password may
not be acceptable as a new password.
User response: To have the server generate a new
key-ring file password, issue the DELETE KEYRING
command; then halt and restart the server. Any 3rd
pary certificates which had been imported to the
key-ring file previously must be re-imported.

641
ANR8593E (HP-UX) ANR8594I (Solaris)

ANR8593E (HP-UX) Failure to update key-ring file
password.


ANR8594I (AIX) Session to address session is using

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.

ANR8594I (HP-UX) Session to address session is


ANR8593E (Solaris) Failure to update key-ring file
password.
User response: None

User response: None
ANR8594I (Linux) Session to address session is using
User response: None
ANR8594I (Solaris) Session to address session is
User response: None
ANR8593E (Windows) Failure to update key-ring file

password.
642
ANR8594I (Windows) ANR8596E (Linux)

ANR8594I (Windows) Session to address session is
User response: None
ANR8595I (AIX) Session to address session is using
number.
Explanation: An SSL connection is being established
to the indicated address using the listed SSL version,
cipher specification, and cerificate serial number.
ANR8595I (HP-UX) Session to address session is
number.
ANR8595I (Linux) Session to address session is using
number.
ANR8595I (Solaris) Session to address session is
number.

ANR8595I (Windows) Session to address session is
number.
ANR8596E (AIX) The certificate identity could not be
verified.
Explanation: The server was unable to open an SSL
connection to the server at address address because the
certificate identity could not be verified. Lack of
verification happens when the certificate ownership
information does not match the domain name or IP
address.
System action: The session ends.
User response: Ensure that the server domain name or
the IP address (the value of the HLADDRESS
parameter of the DEFINE SERVER command) is
correct. If you are using a self-signed certificate, ensure
that it was created on a server at the same address as
specified in the DEFINE SERVER command.
ANR8596E (HP-UX) The certificate identity could not
be verified.
address.
ANR8596E (Linux) The certificate identity could not
be verified.
address.
643
ANR8596E (Solaris) ANR8597E (Windows)

ANR8596E (Solaris) The certificate identity could not
be verified.
address.
ANR8596E (Windows) The certificate identity could
not be verified.
address.
ANR8597E (AIX) Certificate information could not
be retrieved.
Explanation: The server was unable to obtain
certificate inforamtion for an SSL connection to the
server at address address.
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
session to the target server's SSL port with a browser
such as Firefox.
644
ANR8597E (HP-UX) Certificate information could not

be retrieved.
such as Firefox.
ANR8597E (Linux) Certificate information could not
be retrieved.
such as Firefox.
ANR8597E (Solaris) Certificate information could not
be retrieved.
such as Firefox.
ANR8597E (Windows) Certificate information could
not be retrieved.
such as Firefox.
ANR8598I (AIX) ANR8675E (Windows)

ANR8598I (AIX) Outbound SSL Services were
loaded.
Explanation: The server is enabled to run SSL sessions
from the server to other servers during node
replication.
User response: None. The server can communicate via
SSL to other servers. Prior to starting the server,
certificates must be loaded in the server's keyring file
(cert.kdb).

(cert.kdb).
ANR8675E (AIX) File name: File already exists for File
or Filetext Exit.
Explanation: The specified file already exists and the
file-exit option was set to PRESERVE.
System action: Server continues running.
User response: Specify a non-existent file.
ANR8598I (HP-UX) Outbound SSL Services were

loaded.
replication.
(cert.kdb).
ANR8598I (Linux) Outbound SSL Services were
loaded.
replication.
(cert.kdb).
ANR8598I (Solaris) Outbound SSL Services were
loaded.
replication.
ANR8675E (HP-UX) File name with environment variable

DSMSERV_DIR: File already exists for
File or FileText Exit.
file-exit option was set to PRESERVE.
ANR8675E (Linux) File name with environment variable
File/FileText Exit, overwrite option not
set to YES.
overwrite option was not set to Yes.
User response: Specify another file or set the
overwrite option to YES in the server options file.
ANR8675E (Solaris) File name with environment variable
File/FileText Exit, overwrite option not
set to YES.
overwrite option was not set to Yes.
User response: Specify another file or set the
overwrite option to YES in the server options file.

(cert.kdb).
ANR8675E (Windows) File name with path within

registry.: File already exists for File or
FileText Exit.
ANR8598I (Windows) Outbound SSL Services were

loaded.

File/FileText exit option was set to PRESERVE.

replication.

645
ANR8677E (AIX) ANR8678E (HP-UX)

ANR8677E (AIX) User specified module: Cannot load
into server, AIX system error number
number.
Explanation: The server was unable to load the
module specified. The module is not a properly
C-compiled and linked dynamic module.
System action: Server initialization stops or server
continues running if already up.
User response: Use the server supplied sample
makefile and export files to compile-link the user-exit
module. Make sure the export.ref file contains the
server-defined function name, and the module actually
contains the server-defined function name, with one
void parameter declared.
ANR8677E (HP-UX) User specified module, with
environment variable DSMSERV_DIR:
Cannot load into server, system errno =
Error number generated by HP-UX.
void parameter declared.
ANR8677E (Linux) User specified module, with
Error number generated by Solaris.
User response: Use the supplied sample makefile, c ,
and h files to generate the user-exit module. Make sure
the module contains product-defined function name
adsmV3UserExit, and the module actually contains the
product-defined function name, with one void *
parameter declared, and returns void.
ANR8677E (Solaris) User specified module, with
Error number generated by Solaris.

makefile, c, and h files to generate the user-exit
module. Make sure the module contains server-defined
function name adsmV3UserExit, and the module
actually contains the server-defined function name,
with one void * parameter declared, and returns void.
ANR8677E (Windows) User specified module, with path
within registry: Cannot load into server,
system errno = Error number generated by
Windows.
makefile compile-link the user-exit module.
ANR8678E (AIX) Cannot bind User specified module
into server. AIX system error number.
Explanation: The server was unable to bind with the
module specified.
contains the server-defined function name, with 1 void
parameter declared. The module may contain a global
variable name that conflicts with the server's.
ANR8678E (HP-UX) Cannot bind User specified
module, with environment variable
DSMSERV_DIR into server, system errno
= Error number generated by HP-UX.
module specified.
void parameter declared. The module may contain a
global variable name that conflicts with the server's.

646
ANR8678E (Linux) ANR8680W (AIX)

ANR8678E (Linux) Cannot bind User specified module,
with environment variable DSMSERV_DIR
into server, system errno = Error number
generated by Solaris.
module specified. The server could not find a function
named adsmV3UserExit in the module.
User response: Use the supplied sample makefile, c
and header files to create the user exit module. Make
sure the shared library module contains a function
named adsmV3UserExit of type void, with one
parameter of a void *.
ANR8678E (Solaris) Cannot bind User specified module,
with environment variable DSMSERV_DIR
into server, system errno = Error number
module specified. The server could not find a function
named adsmV3UserExit in the module.
ANR8679W (HP-UX) There is already an user-exit

loaded.
Explanation: There was a previous successful load of
an user-exit module, thus server cannot load another
one.
User response: To load a new user-exit module, the
server must be halted and then restart the server with
the new user-exit module.
ANR8679W (Linux) Unable to unload user exit
module: system errno = Error number
Explanation: The server was not able to unload the
user-exit module.
User response: The server should be stopped at the
earliest possible time before the user exit is to be
reactivated.

makefile, c and header files to create the user exit
module. Make sure the shared library module contains
a function named adsmV3UserExit of type void, with
one parameter of a void *.
ANR8679W (Solaris) Unable to unload user exit

module: system errno = Error number
Explanation: The server was not able to unload the
user-exit module.
ANR8678E (Windows) Cannot find/set User specified

function name within DLL. in User specified
DLL library name, with registry path,
system errno = Error number generated by
Windows.
User response: The server should be stopped at the

earliest possible time before the user exit is to be
reactivated.
Explanation: The server was unable to find and/or

bind with the function name in the DLL specified.
ANR8679W (Windows) There is already an user-exit

loaded.
Explanation: There was a previous successful load of

an user-exit module, thus server cannot load another
one.

makefile to compile-link the user-exit module. Make
sure there is a function name in the DLL as specified in
the server options file. Make sure the function only
accepts one argument, a void pointer.
ANR8679W (AIX) A user-exit module is already
loaded.
Explanation: A user-exit module was loaded
previously. Another user-exit module cannot be loaded.
System action: Server initilization stops or server
User response: To load a new user-exit module, halt
the server and then restart the server with the new
user-exit module.

User response: To load a new user-exit module, halt
the server and then restart the server with the new
user-exit module.
ANR8680W (AIX) A file used for the file or filetext
exit is already opened.
Explanation: A file for the file or filetext exit was
previously opened. The server cannot open another
one.
User response: To start a new file for the file or
647
ANR8680W (HP-UX) ANR8682E (AIX)

filetext exit, halt the server, then restart the server with
the new file name.
ANR8680W (HP-UX) There is already a file used for
the file or filetext exit.
Explanation: There was a previous file open for the
file or filetext exit. The server cannot open another one.
ANR8681I (HP-UX) Connected to Tivoli event server

at node name on port port.
Explanation: The server successfully established a
connection with the Tivoli event server on the specified
node name and port.
System action: The server sends events to the Tivoli
event server using this connection.

User response: To start a new file for the file or

a new file name.
ANR8681I (Linux) Connected to Tivoli event server

ANR8680W (Linux) There is already a file used for

the file or filetext exit.
User response: To start a new file for the exit, halt the
server, then restart the server with a new file name.
ANR8680W (Solaris) There is already a named file
used for the file or filetext exit.
User response: To start a new file for the file or the
a new file name.
ANR8680W (Windows) There is already a file used
for the file or filetext exit.

node name and port.
ANR8681I (Solaris) Connected to Tivoli event server
node name and port.
ANR8681I (Windows) Connected to Tivoli event
server at node name on port port.
node name and port.

User response: To start a new file for the exit, halt the
server, then restart the server with a new file name.
ANR8681I (AIX) Connected to Tivoli event server at
node name on port port.
node name and port.
648
ANR8682E (AIX) Unable to determine port of Tivoli

event server on node node name.
Explanation: The server was unable to determine the
TCP/IP port for the Tivoli event server on node node
name.
System action: Event logging to the Tivoli event
server is disabled.
User response: Ensure that the Tivoli event server is
running on the specified system. If the system on
which the event server is running does not support the
TCP/IP Portmapper, then ensure that TECPORT is
ANR8682E (HP-UX) ANR8683E (Solaris)

ANR8682E (HP-UX) Unable to determine port of
Tivoli event server on node name.
TCP/IP port on which the Tivoli event server on node
name is listening.
server is disabled.
ANR8682E (Linux) Unable to determine port of
name is listening.
server is disabled.
ANR8682E (Solaris) Unable to determine port of
ANR8683E (AIX) Unable to connect to the Tivoli

event server at node node name on port
port.
Explanation: The server was unable to establish a
TCP/IP connection with the Tivoli event server on
node node name at port port.
server is disabled.
TCP/IP Portmapper, then ensure that the value
specified for TECPORT in the server options file is
correct.
ANR8683E (HP-UX) Unable to connect to the Tivoli
event server at node name on port port.
TCP/IP connection with the Tivoli event server on node
name at port port.
server is disabled.
correct.

name is listening.
ANR8683E (Linux) Unable to connect to the Tivoli


server is disabled.

name at port port.

ANR8682E (Windows) Unable to determine port of
name is listening.
server is disabled.

server is disabled.
correct.
ANR8683E (Solaris) Unable to connect to the Tivoli
name at port port.
server is disabled.
649
ANR8683E (Windows) ANR8684E (Windows)

correct.
ANR8683E (Windows) Unable to connect to the
Tivoli event server at node name on port
port.
name at port port.
server is disabled.
correct.
ANR8684E (AIX) Unable to connect to the Tivoli
event server because TCP/IP is not
available.
TCP/IP connection with the Tivoli event server because
TCP/IP services were not available.
server is disabled.
User response:
v Ensure that COMMMETHOD TCPIP is specified in
v If COMMMETHOD TCPIP was specified, use the
BEGIN EVENTLOGGING TIVOLI command to
manually start event logging to the Tivoli event
server once server initialization has completed.
ANR8684E (HP-UX) Unable to connect to the Tivoli
available.
server is disabled.
User response:
v Ensure that COMMMETHOD=TCPIP is specified in
the server options file, or that
COMMMETHOD=NONE is not specified.
v If COMMMETHOD=TCPIP was specified, use the
650
ANR8684E (Linux) Unable to connect to the Tivoli

available.
server is disabled.
User response:
ANR8684E (Solaris) Unable to connect to the Tivoli
available.
server is disabled.
User response:
ANR8684E (Windows) Unable to connect to the
Tivoli event server because TCP/IP is
not available.
server is disabled.
User response:
ANR8685I (AIX) ANR8746E

ANR8685I (AIX) Core dump being generated to file
core dump file
Explanation: The server has started generating a
coredump to the specified file as a result of a user
request.
volume mount operation cannot be processed because

the server is not licensed to support the required device
type.
User response: Contact your service representative to
update the server license terms so that support for the
required device type is enabled.

ANR8743E
ANR8686I (AIX) Core dump successfully generated
Explanation: The server has successfully generated the
requested core dump.
This server is not licensed to support

library device name. Device Support
Module module number is required.
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.
ANR8687E (AIX) Error generating core dump, errno

system errno.
Explanation: The server was unable to generate the
requested core dump. The errno indicates the reason
AIX was unable to complete the request.

given library device is enabled.
ANR8744E
Command: Current license terms do not

permit this operation.
Explanation: The specified command failed because

the current license terms do not permit it.
ANR8740W
Number of automated library slots (slots

in use) exceeds license terms (slots
licensed).
Explanation: The number of slots in use within

automated libraries exceeds the licensed value.

update the server license terms so that the requested
operation can be processed.
System action: The operation completes.
ANR8745E
Support for the 3590 device type is

disabled for library library name.

update license values for slots in automated libraries,
or reduce the number of slots in use by issuing
CHECKOUT LIBVOLUME commands as necessary.
Explanation: The requested operation fails because

support for the 3590 device type is not currently
enabled for the specified library.
ANR8741E
CHECKIN LIBVOLUME not permitted

with current license terms.
Explanation: The CHECKIN LIBVOLUME operation is

not permitted because the current license terms do not
allow it.
User response: Make sure the ENABLE3590LIBRARY

option is specified in the server options file, and that
the scratch category number for 3590 volumes does not
conflict with the private category or the CARTRIDGE
volume scratch category.

update license values for slots in automated libraries,
or reduce the number of slots in use by issuing
CHECKOUT LIBVOLUME commands as necessary.
ANR8746E
Device type device type is not supported

in this release.
Explanation: The specified device type cannot be used

by this release/platform of the server.
System action: The device cannot be used.
ANR8742E

the device type device type. Device
Support Module module number is
required.
User response: Contact your sales or service

representative to upgrade to the latest release of the
server.
Explanation: A DEFINE DRIVE command or a

651
ANR8747I ANR8753W
ANR8747I
Checking in volume volume name in

library library name- CANCEL
PENDING.

CHECKIN LIBVOLUME process on the server. The
given volume was being checked in to the designated
library, but the process was canceled by an
administrator.
System action: The background process operation is in
a wait queue. When the process comes off the queue, it
will be terminated.
ANR8748I
Checking in volumes in search mode in

library library name- CANCEL
PENDING.

CHECKIN LIBVOLUME process on the server. Volumes
were being checked into the given library in search
mode, but the process was canceled by an
administrator.
System action: The background process operation is
being terminated.
ANR8749E
Library order sequence check on library

library name.
Explanation: An attempt has been made to mount or

demount a volume, but the attempt fails for one of the
following reasons:
v Mount is already in progress or a volume is already
mounted.
drive (For example, attempting to mount a 3590

cartridge on a 3490 drive).
User response: Ensure the DEVTYPE parameter on
the CHECKIN command matches the device type of
the drive. Retry the operation.
ANR8751W

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
is to warn you that you are not in compliance with
registered license terms.
ANR8752W

library device type. Managed Library
license is required.

LIBRARY command or a volume mount operation uses
a device class that is not licensed on the server.
v Mount is already pending.

v Demount is already pending.
ANR8753W
v Demount was requested but no volume is mounted.

User response: This error usually occurs when a
demount fails and a cartridge is left in the drive. All
subsequent mounts fail while attempting to insert
another cartridge into the same drive. Demount the
cartridge using the library manager or perform an
AUDIT LIBRARY operation on the designated library.
Retry the operation.
ANR8750E
Volume is incompatible with specified

device type in library library name.

LIBRARY command or library initialization for a
library that requires library sharing and library sharing
is not licensed on the server.
Explanation: An attempt has been made to mount or

check in a volume, but the attempt fails because the
cartridge being mounted is not compatible with the
652

library library name. Library Sharing is
required.
ANR8754E ANR8763E
ANR8754E
Command: There is already a request to

delete library libary name.

or updated because there is a request to delete the
library already.
ANR8755E

update library library name.

because there is a request to update the library already.
mount retry if the selected drive does not have a valid,

online path defined.
User response: Evaluate all drive path definitions.
Define drive paths for any drives that lack a path
definition for any applicable source (for example
storage agents). Validate that all drive path definitions
are online. If a drive path is offline for a hardware
reason, resolve the hardware issue and update the path
so that it is back online.
ANR8760I
Cancel in progress.
Explanation: The MOVE MEDIA command has been

for a MOVE MEDIA command.
ANR8756E
For optical libraries, you must specify

CHECKLABEL=YES.

ANR8761I
Explanation: Optical libraries require the

CHECKLABEL parameter to be set to YES
CHECKLABEL=YES option.
Explanation: The MOVE MEDIA command has

processed the number of volumes displayed. This
PROCESS command for a MOVE MEDIA command.
ANR8757W

library device type. Extended Edition
license is required.

ANR8762E

LIBRARY command or a volume mount operation uses
a device class that is not licensed on the server.
ANR8758W
The number of online drives in the VTL

library library name does not match the
number of online drive paths for source
source name.
Explanation: If the number of online drives in the

library does not match the number of online paths to
drives in the library for any applicable source, it might
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
The drive drive name in the library library

name was unable to obtain an encryption
key from the encryption key
management.
Explanation: The encryption key manager did not

respond to the drive or library that is managed by the
Tivoli Storage Manager server. Since Tivoli Storage
Manager is not managing the encryption keys, there is
an issue with the encryption key manager, the drive, or
the library.
User response: This is most likely a problem with the
encryption key manager (for example, a timeout or
communication failure between the encryption key
manager and the drive or library). Correct any issues
with the encryption key manager and try the operation
again. If the problem persists, contatct IBM hardware
support.
ANR8763E

processed: library library name not
defined.

since the designated library has not been defined or has
been deleted.
653
ANR8764E ANR8770W
ANR8767I

command.
ANR8764E

processed: the operation is not allowed
for library type library type.

since the requested operation is not allowed for
libraries of the given type.

volumes processed. Volumes sent to library
library name for checkout: number volumes
sent.
Explanation: The MOVE MEDIA command has

processed the number of volumes shown. Currently, the
MOVE MEDIA command has sent for processing the
number of volumes shown to the library shown. This
PROCESS command for a MOVE MEDIA command.

ANR8768E
ANR8765I

name in location location name is required
for use in library library name; CHECKIN
LIBVOLUME required within time limit
minutes.
Explanation: A mount request has been made for a

volume that is defined in a storage pool, but which is
currently checked out of the given library 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
time limit expires.
User response: Obtain the required volume from the
indicated location, and insert it into the library by
issuing a CHECKIN LIBVOLUME command. Use the
SWAP=YES option of the CHECKIN LIBVOLUME
command if the library is currently full; this process
allows the server to select an appropriate volume to be
swapped out in order to make room for the required
volume.
ANR8766I
MOVE MEDIA command: CHECKOUT

LIBVOLUME command for volume volume
successfully; Place the ejected volume in
location location name.
Explanation: The CHECKOUT LIBVOLUME operation

has completed successfully for the indicated volume in
the given library. Place the ejected volume in the
indicated location.
File file name on volume drive name could

not be found.
Explanation: The server was unable to find the

specified file name on the indicated volume. For
removable file device classes, each volume maintains
data using a file name which is the same as the volume
name and the label value on the volume.
User response: Ensure that the proper volume has
been placed into the drive. If you are creating a
removable file device class volume by copying data
from a FILE device class volume, the media must have
a label which is the same as the volume name. The file
which is copied to the volume must be renamed to
have the same name as the label.
ANR8769E
External media management function

request type returned result=result.
Explanation: A request of the indicated function type

was sent to the external library manager program,
which returned a result code which was not SUCCESS.
System action: The server continues, but the server
operation that was being attempted fails.
User response: Consult the documentation for the
external media management program to determine how
to recover from the error condition. Then attempt the
server operation again.
ANR8770W
Unable to load external library manager

filespec.

library inventory (if its status is something other than
Explanation: A library of LIBTYPE=EXTERNAL is

defined but the server cannot load the external library
manager.
User response: If an *UNKNOWN* location is

displayed, issue UPDATE STGPOOL OVFLOCATION
command to define an overflow location name to be
used on the subsequent MOVE MEDIA command. For
the volumes ejected with an *UNKNOWN* location,
use UPDATE VOLUME LOCATION command to
update its location to your overflow location name.
System action: The server continues, but the external

library cannot be accessed.
654
User response: Verify that the EXTERNALMANAGER

parameter for the external library is specified correctly
on the DEFINE LIBRARY or UPDATE LIBRARY
command.
ANR8771E ANR8777E
ANR8771E
Volume volume name in library library

name is deleted. External Library is not
synchronized with the server. Audit
required.
Explanation: The server deleted a volume from its

inventory, and its attempt to inform the external library
manager has failed.
System action: The server may continue to access the
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
synchronize it with the server.
ANR8772I
Moving volume volume name (if known)

from drive drive name to slot slot element
number in library library name.
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
to the slot.
Incompatible options
CHECKLABEL=NO and SEARCH=YES
for library type library.
Explanation: If a barcode reader is not installed and

detected by the server, the server requires the ability to
check the tape label when searching for new volumes
in a VTL or SCSI tape library. The CHECKLABEL=NO
and SEARCH=YES parameters on the CHECKIN
LIBVOL command are not compatible.
User response: Reissue the CHECKIN LIBVOL
command and specify CHECKLABEL=YES.
ANR8774W
ANR8775I
Volume volume name not checked into

library library name but is using category
category number.
Explanation: While processing a DEFINE LIBRARY or

AUDIT LIBRARY command for the given library, the
server found a volume that was not checked into the
library (with the CHECKIN LIBVOL command), but is
assigned to one of the categories in use by that library.
System action: If the volume category equals the
value of the library SCRATCHCAT the category is
changed to the value of the library PRIVATECAT. This
is to prevent the library from loading the volume when
a scratch volume is requested.
User response: If the volume is to be used by the
server, it does not have to be reassigned but it must be
checked into the library with the CHECKIN LIBVOL
Drive drive name unavailable at library

manager.
Explanation: The specified drive availability status at

the library manager has changed from available to
unavailable.
System action: The drive status on the server is
updated to reflect the availability to that of the library
manager. The drive will not be considered as a
candidate for the mount or demount request.
determine the cause of the drive becoming unavailable.
Once the service representative has determined the
cause and changed the availability status to available at
the library manager, the server will resume use of the
drive.
ANR8776W

ANR8773E
command. If the volume is not to be used by the

server, use the mtlib program to reassign the volume to
its correct category. For details about the mtlib
program, refer to the documentation provided with the
library device.
Volume volume name in drive drive name

contains lost VCR data; performance
may be degraded.
Explanation: The Vital Cartridge Records of the

cartridge in the drive are lost or corrupted. This results
in the inability of the drive to do fast locates to file
positions on the cartridge, which causes the locate
performance for read or append operations to become
degraded.
System action: The server continues the operation.
User response: There are two methods to restore the
VCR data. The first method uses the MOVE DATA
command to move the data off the tape and to return
the tape to scratch or empty status. The VCR data is
rebuilt when the empty tape is rewritten from the
beginning-of-tape. The second method rebuilds the
VCR by loading the tape and locating directly to the
end-of-data. This is done by the server in normal use
when new data is appended to the end of the tape. It
can also be done independent of the server by loading
the tape in an unused drive and using the tapeutil
program. Select the tapeutil option "Space to
End-of-Data".
ANR8777E
Mount for volume volume name failed;

media performance is degraded.
Explanation: The VCR data on the volume is lost or

corrupted, resulting in degraded tape positioning. The
mount fails because the tape drive was configured to
fail mounts that indicate this condition.
System action: The client command fails and the
transaction is rolled back.
User response: Until the VCR data can be restored,
655
ANR8778W ANR8783E
the user can issue the UPDATE VOLUME command to
make the volume unavailable. There are two methods
to restore the VCR data. The first method uses the
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
from the beginning-of-tape. The second method
rebuilds the VCR by loading the tape and locating
directly to the end-of-data. This is done by the server in
normal use whenever data is appended to the end of
the tape. It can also be done independent of the server
by loading the tape in an unused drive and using the
tapeutil program. Select the tapeutil option "Space to
End-of-Data".
ANR8780E
Explanation: The volume in the indicated drive does

not have a label. The server requires that all media be
uniquely labeled.
System action: The volume is rejected and the server
prompts for a new volume.
User response: Use the appropriate labeling utility to
label the media. In OS/2 and Windows NT, the LABEL
command is used to label removable disk cartridges,
diskettes and other media which appear as drive
letters.
ANR8781E
ANR8778W
Scratch volume volume name changed to

Private Status to prevent re-access.
Explanation: The scratch volume encountered an error

during mount processing that makes it unusable. The
status of the volume is changed to private so that it is
not selected for future scratch mounts. (Although the
status has become private, it is not defined to a storage
pool.)
System action: Processing continues with another
scratch volume.
User response: See previous error messages to
determine the cause of the mount failure, and correct
the problem. If the problem is a mislabeled volume or
unreadable label, relabel the scratch volume using the
dsmlabel utility with the "-overwrite" option. If the
volume is missing from its home slot, issue the AUDIT
LIBRARY command against the library. If the volume
has lost or corrupted VCR-data, relabel the volume.
(This reinitializes the VCR-data by writing to the
volume from beginning-of-tape.) Once the problem is
corrected, update the status of the volume to scratch by
using the UPDATE LIBVOL command.
ANR8779E
Unable to open drive drive name, error

number= errno value from open system call.
Explanation: The drive cannot be opened by the

server. On UNIX and Linux systems, an error number
is a value of an errno returned by the operating system.
On Windows, an error number is a Windows error
message number.
System action: The transaction that needs the drive
fails.
User response: Use the error number in conjunction
with operating system documentation to narrow the
scope of the cause. Inspect the drive. Ensure that the
drive is powered on and ready, that the cables are
properly connected and terminated, and that the device
is properly configured to the operating system.
Volume in drive drive name has no label.
Volume in drive drive name has invalid

label label.
Explanation: The volume in the indicated drive has

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
label with file naming conventions. The label found
exceeded the maximum label size for removable media
or did not conform to server labeling requirements. If
????? is shown for the label, it indicates that server was
unable to read the label.
letters. This label must still conform to server
requirements.
ANR8782E

accessed by library library name.
Explanation: The designated volume is in the

inventory of the Library Manager, but the physical
location is either inaccessible or unknown.
System action: The operation fails. The access mode of
the volume is changed to UNAVAILABLE.
User response: Ensure that the cartridge is physically
in the library, and reinventory the library. If the volume
location is resolved, restore the access mode of the
volume to its previous value using the UPDATE
VOLUME command.
ANR8783E
Label on volume in drive drive name

could not be read.
Explanation: The server was unable to read the label

on the indicated drive.
656
ANR8784E ANR8791E
letters. This label must still conform to server
requirements.
ANR8784E
File file name on volume drive name could

not be created.
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.
User response: Ensure that the media is not defective,
and is properly formatted. Ensure that there are not
large numbers of files already in the root of the file
system. Some file systems have limits on the number of
files that may be created in the root directory.
ANR8785E
Out-of-space in file system for device

type volume volume name.
Explanation: The server detected an out-of-space

condition for the file system in which the given volume
resides.
User response: The file system must be expanded to
accommodate volume growth.
ANR8786I

volume from entry/exit port; insert
volume volume name mount mode into
entry/exit port of library library name
within time limit minute(s); issue 'REPLY'
along with the request ID when ready.
Explanation: A CHECKIN LIBVOLUME command is

in progress, and the specified volume is needed.
However, there is a volume awaiting to be removed
from the entry/exit port before the specified volume is
inserted into the port of the given library.
command is issued.
and insert the correct volume into the entry/exit port.
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
Unable to read the barcode label(s) in

Explanation: A command is issued with the

CHECKLABEL=BARCODE option. The library is
unable to detect that the cartridges have valid barcode
labels. The barcode reader is disabled or it is unable to
read the labels.
System action: Unless the command is checking in
cleaning cartridges, the process continues by loading

the cartridges into the library's drives and reading the
label from the tape. Cleaning cartridges have no
internal label that can be checked by loading it in the
drive.
User response: Cancel the process if you do not want
to load all of the cartridges into the library's drives.
Examine the cartridges to ensure they have barcode
labels and they are compatible with the barcode reader.
Not all vendors' labels are readable by all libraries.
Check that the barcode reader is configured and
functioning properly, if necessary.
ANR8788W
Unable to read the barcode of cartridge

in slot-id Element number of slot in library
library name; loading in drive to read
label.
Explanation: The library barcode reader is unable to

read the label of a tape cartridge. The cartridge is
found in the slot with the given element number.
System action: The cartridge is loaded into a drive
and its label will be read from the tape.
User response: Cancel the process if you do not want
to load any cartridges into the library's drives. Examine
the cartridge to ensure it has a barcode label and that it
is compatible with the barcode reader. Not all vendors'
labels are readable by all libraries. Check that the
barcode reader is configured and is functioning
properly, if necessary.
ANR8789W
Dynamic drive recovery being attempted

on device type volume volume name due to
errors.
Explanation: Due to a drive or media fault, the server

is moving the volume to a new drive.
System action: Read or write operations resume on
the volume once it is remounted.
ANR8790I
device type volume volume name

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.
System action: The label of the volume has been
verified.
ANR8791E
Unable to move device type volume

volume name to another drive.
Explanation: Dynamic drive recovery was being

attempted on the volume, but was unable to move the
volume to another drive.
657
ANR8792E ANR8798W
System action: The originating process terminates.
determine the cause of the DDR failure, and correct the
problem. If the problem is an unreadable label, any
data on the volume may be lost.
ANR8792E
Unrecoverable drive failures on drive

drive name; drive is now marked offline.
Explanation: The drive has been determined to be

faulty because of recurrent failures.
System action: The drive is now marked offline.
User response: Service the drive for failures. Delete
and redefine the drive to bring it back online.
ANR8793E
Dynamic drive recovery failed for device

type volume volume name because not
enough drives are available.
Explanation: To recover a volume on another drive,

there must be at least one other drive available that is
not associated with the transaction which is driving the
recovery. In addition, the maximum number of drives
that can have dynamic drive recovery performed at the
same time is one less than the number of drives. This is
to prevent deadlock from occurring between two
recovering transactions. One of these criteria has failed.
System action: No DDR is performed and the
transaction fails.
User response: Restart the transaction.
ANR8794E
Retry of operation name operation failed

for device type volume volume name.
Explanation: After successfully mounting the volume

on another drive, due to an I/O error, the original
operation fails when retried.
System action: No further recovery is performed and
the transaction fails.
User response: Restart the transaction.
ANR8795I
Retry of operation name operation for

device type volume volume name is
successful.
Explanation: After mounting the volume on another

drive, due to an I/O error, the operation is tried
successfully.
System action: The transaction continues from the
point of interruption from the failure.
658
ANR8796W
Drive drive name of library library name is

not online; UPDATE DRIVE required.
Explanation: During the initialization of a library, the

server finds that the drive was updated to be offline.
System action: The drive will not be accessible by the
library during tape operations.
User response: The drive may be made online by
issuing the UPDATE DRIVE command with the
ONLINE=YES option.
ANR8797W
command: Drive drive name of library

library name is inaccessible.

mentioned drive. This may be for the following
reasons:
v The drive cannot be opened.
System action: The drive is temporarily made offline
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
again, the drive is brought online.
User response: Determine the reason the drive is
inaccessible, such as hardware errors reported in the
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
accessible.
ANR8798W
Drive drive name in library library name is

busy; some transactions may fail.
Explanation: The drive being made offline is currently

mounted with an open tape volume. If the transaction
using the volume requires subsequent tape mounts and
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.
This may be any drive in the library, but if all other
library drives are currently busy and are still busy at
the time the new tape must be mounted, the
transaction will fail.
User response: If possible, make the drive online until
the transaction using it ends. If there is an idle volume
on the drive, dismount the volume first.
ANR8799I ANR8807W
ANR8799I

Explanation: A LABEL process has been started to

write the label on the specified volume in the given
library. The process is assigned the ID specified in the
message.

ANR8804I
Labeling volume volume name in library

library name.

to perform the operation in response to the LABEL
command entered by an administrator.

LABEL process on the server.

System action: The background process continues.
ANR8800I
LABEL LIBVOLUME for volume volume

successfully.
Explanation: The background process to LABEL a

volume has succeeded.

PROCESS command.
ANR8805I
Labeling volumes in library library name;

volume count volume(s) labeled.
System action: The volume's label has been rewritten.

command, this message displays the status of a LABEL
process with the SEARCH option.
System action: The background process continues.
ANR8801I
LABEL LIBVOLUME process process Id

for library library name completed; count
of labeled volumes volume(s) labeled, count
of checked in volumes volume(s)
checked-in.
Explanation: A search-mode process to LABEL

volumes has succeeded.
System action: The volumes have been labeled.
ANR8802E
LABEL LIBVOLUME process process Id

for library library name failed.
Explanation: The Label process terminated with a

failure.

PROCESS command.
ANR8806E
Could not write volume label volume

name on the tape in library library name.
Explanation: The Label process could not write the

label on the tape specified.
System action: For a LABEL operation with
SEARCH=YES, the background process continues to the
next volume. For an individual volume, the process
ends. The volume is not labeled and is not checked into
the library.

determine the cause of the failure, and correct the
problem.
ANR8803I
LABEL VOLUME process process Id for

library library name has been canceled;
count of labeled volumes volume(s) labeled,
count of checked in volumes volume(s)
checked-in.

been working to label the volumes for the given library
is canceled by the CANCEL PROCESS command. The
counts provided are for any volumes processed prior to
the cancel.
ANR8807W
Could not write label volume name on

the volume in drive drive name of library
library name because volume is already
labeled existing volume name.
Explanation: The check in or label process could not

write the label on the tape specified because the
volume is already labeled.
System action: The check in process will not overwrite
volumes that are already labeled, and the label process
will only overwrite volumes when OVERWRITE=YES
is specified. The volume is not labeled and cannot be
checked in to the library. If SEARCH=YES, the process
continues to the next volume. For an individual
volume, the process ends.
659
ANR8808E ANR8815I
parameters.
ANR8808E
Could not write label label name on the

volume in drive drive name of library
library name because that volume is
already labeled with volume name which
is still defined in a storage pool or
volume history.
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
volume may still contain valid data.
User response: It is usually not necessary to re-label
volumes. If the volume must be relabeled, that volume
must first be removed from the storage pool or volume
history file where it is defined.
ANR8809I
Request number: Please provide the label

name for the volume in slot element slot
element number of library library name by
issuing REPLY n LABEL=xxx within time
limit minutes, where n is the request ID
and xxx is the desired label name.
ANR8812E
Command: The SEARCH parameter is

required when using LABELSOURCE
with this command.
Explanation: When using the LABELSOURCE option

with this command, the SEARCH parameter must be
also provided.
valid SEARCH parameter value.
ANR8813W
Unable to read the barcode of cartridge

in slot element Element number of slot in

read the label of a tape cartridge. The cartridge is
found in the slot with the given element number.
System action: When LABELSOURCE=BARCODE is
specified on the LABEL LIBVOLUME command,
volumes without a barcode cannot be labeled. When
the VOLRANGE or VOLLIST option is specified on the
CHECKIN LIBVOLUME command, volumes without a
barcode cannot be checked in.
Explanation: A LABEL LIBVOLUME command is in

progress, and the name of the next volume is needed.
User response: Examine the cartridge to ensure it has

a barcode label and that it is compatible with the
barcode reader. Not all vendors' labels are readable by
all libraries. Check that the barcode reader is
configured and is functioning properly, if necessary.

command is issued.
ANR8814I
User response: Issue a REPLY command, along with

the request ID, and the volume name for the next
cartridge.
ANR8810I
Volume volume name has been labeled in

Explanation: The Label process with the search option

has found and labeled a volume.
ANR8811E
Command: The LABELSOURCE

parameter is required when using
SEARCH with this command.
Remove volume Volume name from slot

element Slot element number of library
Library name.
Explanation: LABEL LIBVOLUME has ended for the

specified volume and that volume must be removed
from the library because either it was not checked in or
there was an error.
System action: The server continues normal operation.
User response: Remove the specified volume from the
library.
ANR8815I
Remove volume Volume name from port

element Port element number of library
Library name.
Explanation: The LABELSOURCE parameter must be

provided with the given command.
Explanation: LABEL LIBVOLUME has ended for the

specified volume and that volume must be removed
from the library because either it was not checked in or
there was an error.
System action: The server continues normal operation.

valid LABELSOURCE parameter value.
User response: Remove the specified volume from the

library.
660
ANR8816E ANR8823E
ANR8816E
command: Volume Volume name in library

Library name cannot be labeled because
it is currently defined in a storage pool
or in the volume history file.

volume cannot be used because there is a storage pool
volume defined or a volume in the volume history file
with this volume name. Such a volume may still
contain valid data. Applying the volume name to the
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
export, database dump, database backup operation, or
by a library client (as recorded in the volume history).
System action: If the SEARCH=YES option was
specified, the current volume is skipped and command
processing continues with the next volume found. If
SEARCH=NO was specified, command processing
terminates.
User response: If the volume is present in an
automated library, it should either be removed or
checked into the library's inventory in the PRIVATE
category.
ANR8817E
Name length for volume "Volume name"

invalid; max is Maximum name length.
Explanation: During LABEL LIBVOL processing, the

volume name provided to be written on the label
exceeds the maximum length for the type of cartridge.
System action: The label process fails for that
cartridge.
User response: Reissue the LABEL LIBVOL command
and provide a volume name that is not longer than the
maximum listed.
ANR8818E
I/O Error on library library name; request

for op. operation/function to the 3494
Library Manager has timed out.
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.
User response: Verify that communications with the
library is operational, that it is online and ready for
commands. Increase the time-out limit of the Library
Manager Control Point device driver. If the problem
persists, provide your service representative with the
3494 Library Manager transaction logs.
labels or the library did not have a barcode reader. If a

barcode reader is present the reader might be disabled
or it is unable to read the labels.
System action: Examine the cartridges to ensure they
have barcode labels and they are compatible with the
configured and functioning properly.
ANR8820W
Explanation: The Vital Cartridge Records of the

cartridge in the drive are lost or corrupted, which
results in the inability of the drive to do fast locates to
file positions on the cartridge. The VCR is being rebuilt
during the volume dismount process in order to avoid
performance degradation on future mounts of the
volume.
System action: The server continues the dismount
operation. There may be a long delay because the VCR
is rebuilt by spacing the tape forward to the
end-of-data.
ANR8821E
Unable to read the barcode label(s) in

Explanation: A LABEL command was issued with the

LABELSOURCE=BARCODE option. The library was
unable to detect that the cartridges had valid barcode
Barcode of element slot element address,

'hardware barcode string', exceeds maximum
length characters in length.
Explanation: A barcode is encountered that was

longer than a valid volume name.
System action: The barcode is not considered valid
and will not be used for the server process.
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.
ANR8822E
'Volume name' is not a valid volume

name.
Explanation: The specified string is not a valid

volume name.
System action: The program prompts for a new
volume name.
User response: Enter a volume name that is within
the length constraints for the media type being labeled,
and which contains only alphanumeric characters.
ANR8823E
ANR8819E
Repairing VCR data for Volume volume

name in drive drive name; dismount may
be delayed.
Hardware configuration error in library

library name: number of drives drives,
number of storage slots storage slots.
Explanation: The library device returned a count of

zero for either the drives or the slots. The drives may
661
ANR8824E ANR8831W
have not yet been configured to the operating system,
or to the library. The library must have at least one
drive and multiple slots when properly configured in
order to be defined to the server.
User response: Configure the drives to the operating
system, and reinitialize the library.
ANR8824E
I/O Error on library library name; request

request id for operation operation/function
to the 3494 Library Manager been lost.
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.
User response: Verify that communications with the
library is operational, that it is online and ready for
commands. If the problem persists, provide your
service representative with the 3494 Library Manager
transaction logs and the request id from the failed
operation.
ANR8825E
'Volume range' is not a valid volume

range.
ports are accessible, and try the command again.

ANR8828E
Explanation: The slot in the library could not be

physically accessed at this time.
User response: Verify that the Entry/Exit door is
closed and the device has not logged any device errors
before trying the command again.
ANR8829I
User response: Enter the volume names in the range

that is within the length constraints for the media type
being labeled, and which contains only alphanumeric
characters. The volume names of the beginning and
ending volume must be the same in length and the
incrementals must be in digits.
ANR8826E
No Entry/Exit found on library library

name.
Explanation: A CHECKIN LIBVOLUME

SEARCH=BULK command was issued on a library that
has no Entry/Exit ports.

User response: Remove the volume from the
entry/exit slot.
ANR8830E
ANR8827E
No Entry/Exit port is available on

Explanation: A CHECKOUT LIBVOL command was

issued on a library where all its Entry/Exit Ports were
found to be full or inaccessible.
User response: Empty all the entry/exit ports on the
library, close the entry/exit port door, make sure the
662
Internal Device type drive diagnostics

detect excessive media failures for
volume Volume name (MIM MIM Code).
Access mode is now set to "read-only".
Explanation: The tape drive's microcode performed an

analysis of the media during the prior mount of the
volume and determined that the number of temporary
errors and other indicators exceed the threshold for
reliable data recording.
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
recommended to move the data off the volume in order
to minimize the impact of future errors and further
damage to the media.
ANR8831W

Remove volume volume name from slot

element number of library library name at
your convenience.
Explanation: A volume has been checked out from the

library and placed in a multiple entry/exit port library.
The volume needs to be removed from the library, but
the operation is not critical.

volume range.
volume range.
Slot element number of library library

Because of media errors for volume

Volume name, data should be removed as
soon as possible.
Explanation: Errors previously encountered on the

volume leave the access to the data in a questionable
state. The errors may be permanent temporary media
failures such as the corruption of the Volume Control
Region of a Magstar drive.
User response: Move the data off the volume. This
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
relative to media errors. If the errors cannot be isolated
ANR8832E ANR8839W
ore resolved, contact your support representative.
Return the tape to scratch or dispose of it.
ANR8832E
CHECKIN LIBVOLUME for volumes in

search mode in library library name
failed.
Explanation: The background process for a CHECKIN

LIBVOLUME command has failed.
System action: The background process ends, but
volumes have not been checked into the library.
ANR8833E

library name is currently being checked
in or checked out.
Explanation: The command cannot be processed

because the specified volume is being checked in or
checked out of the library.
User response: Wait until the conflicting checkin or
checkout has completed, and then reissue the
command.
ANR8834E
Library volume volume name is still

present in library library name drive drive
name, and must be removed manually.
Explanation: Library operations cannot be performed

using the drive because a volume is still mounted in it.
This may be due to a prior dismount failure that
occurred on the drive.
System action: The command fails. The drive may be
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
be required. If necessary, remove the volume manually
and place it in its storage cell. If the storage cell is
unknown, place the volume in any cell and issue the
AUDIT LIBRARY command. Use the QUERY DRIVE
command to determine the online status of the drive. If
the drive is still functioning, change the status with the
UPDATE DRIVE command.
ANR8835W
Error returning volume volume name to

scratch.
Explanation: The server external library manager sent

a RELEASE request to the external agent for the named
volume, but the external agent was unable comply with
the request. The server, however, marked the volume
scratched in its inventory; consequently, the server
inventory and the external agent inventory are not

consistent. This message is issued to inform the
customer that the external agent inventory must be
made consistent with the server inventory using the
facilities of the external agent.
System action: The server has returned the volume to
scratch status.
User response: Consult the documentation for the
external agent and take the appropriate action to make
the agent inventory consistent with the server
inventory.
ANR8836E
Function RSM_function failed in

server_function processing, return return
code, call call number.
Explanation: The library function that uses the API to

the Windows NT Removable Storage Manager failed
with a return code from the API. The call number
represents the exact API call issued in the program.
System action: The function fails.
User response: Use the RSM documentation to
determine the source of the problem.
ANR8837E
RSM Library Library Name not supported

on this Windows platform.
Explanation: The libtype=RSM was used on a

Windows platform that does not support RSM.
System action: The function fails.
User response: Use another library type to define the
library.
ANR8838E
I/O error on drive drive name: excessive

unit attentions received from device.
Explanation: An operation to the drive failed with a

device unit attention. These are normally cleared when
the operation is retried, but in this case subsequent
recover and retry attempts persistently fail with unit
attention. This indicates a device failure.
User response: See accompanying error messages and
the system error logs to determine any reason for the
drive failure. Hardware diagnostics may be required. It
may be necessary to manually unload the volume and
mark the drive offline with the UPDATE DRIVE
command.
ANR8839W

accessible.
Explanation: The server is now able to use the

mentioned drive that was inaccessible. However, the
administrator has marked the drive offline while the
drive was being polled.
663
ANR8840E ANR8846E
System action: The drive is left offline and is not used
for tape operations.
User response: Issue the UPDATE DRIVE command
to bring the drive back online.
ANR8840E
Unable to open device device name with

error number error number and PVRRC
return code.
Explanation: The library is not accessible. As a result,

an open request failed. This in turn causes the pending
request to fail.
System action: A drive is marked inaccessible. The
server polls the drive to determine if both the library
and drive are inaccessible. In most case, the library had
a temporary failure and recovers. When the server
determines that the library is available, the drive is
brought back on-line.
User response: Use the error number in conjunction
with operating system documentation to narrow the
scope of the cause. Inspect the library. Ensure that the
library is powered on and ready, that the cables are
properly connected, and that the device is properly
configured to the system.
ANR8841I
Remove volume from slot element number

of library library name at your
convenience.
Explanation: A volume has been placed in a multiple

entry/exit port library because the volume should be
placed back in the entry/exit port as result of the
successful completion of a server command, or there
was a problem during a server command. The volume
needs to be removed from the library, but the operation
is not critical.
entry/exit slot. Examine previous messages for
and the command.
ANR8842E
The Device type drive detected a

marginal sector and could not reallocate
the sector for volume Volume name.
Access mode is now set to "read-only".
Explanation: The optical drive detected a marginal

sector (media error) while reading the volume. The
drive read the sector successfully but could not
reallocate the sector because of a previous media error.
ANR8843E

library library name - the library will be
inaccessible.

library has failed. The server is unable to use the
library. This may be for the following reasons:
v The library is defined without a path.
v The device for the library is removed by a DELETE
PATH command.
v The data mover controlling the library is offline.
v The path to the library is offline.
System action: The library is made offline and will
not be used for any library operations.
User response: Determine the reason the library is
inaccessible. Render any needed corrections to the
library, shut down the server, and re-bring up the
server so that the library can be completely initialized.
ANR8844E
Unable to open remote drive drive name,

error code=error value from server plugin.
Explanation: The indicated remote drive cannot be

opened by the server. The error code displayed is the
return code from server plugin routine.
System action: The transaction needing the drive fails.
User response: Use the return code displayed to
determine the cause of the open failure or any other
reason the drive cannot be opened. Hardware
diagnostics may be required. Inspect the drive. Ensure
that the drive is powered on and ready, the cables are
properly connected and terminated, and the device is
properly configured to the operating system.
ANR8845E
Loadable module module name is

required for remote operation.
Explanation: The indicated loadable module is

required by the server to perform an operation on a
remote drive or library, but the module has not loaded.
Message ANR4726I is issued during server initialization
when the module is loaded.
System action: The remote operation fails.
User response: Check the server activity log for
message ANR4726I, indicating if the module was
loaded. If you see this message during server
initialization for this module, please contact your
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
recommended to move the data off the volume in order
to minimize the impact of future errors and further
damage to the media.
664
ANR8846E
Volume volume name is assigned to a

category that does not belong to library
library name.
Explanation: The attempted operation on the volume
ANR8847E ANR8852E
cannot proceed because it is assigned to a category
other than the insert, private, or scratch category used
by the library.
User response: Use the mtlib utility to query the
volume's category. If the volume is not in use by
another library, use mtlib to reassign the category or
choose another volume that is assigned to the proper
category.
ANR8847E
No device type-type drives are currently

available in library library name.

completed on the specified library because there are no
available drives of the specified type. A drive may be
unavailable because a different application has the
drive opened. This message may also be issued if a
CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
because all the drives are mounted by other processes
or sessions, or the device type was incorrectly specified.
This can also be issued when incorrect barcode labels
are placed on the wrong type of media (e.g. LTO2
barcode label on an LTO1 cartridge).
the drive. If the attempted operation is a CHECKIN or
LABEL command, use the QUERY MOUNT command
to determine if all the drives in the library are mounted
and wait until one of these is available. If there are
DISMOUNT VOLUME command to free its drive, and
retry the original operation. Finally, the DEVTYPE
parameter is required for CHECKIN and LABEL
commands specifying 3590 volumes in a 349X library
that also contains 3490 drives. This is because this
library also supports 3490 volumes, and the default
device type on CHECKIN and LABEL commands is
CART (3490).
ANR8848W

inaccessible; server has begun polling
drive.

system logs. Render any needed corrections to the
accessible.
ANR8849E

delete drive drive name.

or updated because there is a request to delete the
drive already.
ANR8850I
ACSLS library library name is ready for

operations.

ready for use.
ANR8851E
Initialization failed for ACSLS library

library name; will retry in delay time
minute(s).

library has failed. It is retried automatically after the
specified amount of time has elapsed.
powered on and ready.
ANR8852E
Initialization failed for ACSLS library

library name.

library has failed and will not be retried until the next

mentioned drive. This may be for the following
reasons:

unavailable.
v The drive cannot be opened

665
ANR8853E ANR8861I
ANR8853E
Incompatible options
CHECKLABEL=NO and SEARCH=YES
for ACSLS libraries.
Explanation: The CHECKLABEL=NO and

SEARCH=YES parameters on the CHECKIN LIBVOL
command are not compatible.
command and specify CHECKLABEL=YES.
ANR8854E
ACSAPI(command name) invocation

failed, status= acs status.
ANR8857I
ACS access control set to user_id - user

id, status= acs status.
Explanation: The ACSLS ACCESSID structure for

command and volume access control is set the user_id
as indicated.
User response: Ensure the indicated user_id is the
same as specified in the environment variable
ACSAPI_USER_ID.
ANR8858W
Unable to lock drive drive id,drive id,

drive id,drive id, status= acs status.
Explanation: The ACSLS library API invocation for

the given command failed.
Explanation: The ACSLS library function

acs_lock_drive failed for the specified drive.
System action: Depends on the server function and

command, library may be unavailable.

command, library drive may be unavailable. or may be
temporary unavailable in a shared library environment.
User response: Contact your ACS System

Administrator and perform ACSLS library problem
determination.
ANR8855E
ACSAPI(command name) response with

unsuccessful status, status=acs status.
Explanation: The ACSLS library API responded with

an unsuccessful status as indicated.
User response: If the status indicates
STATUS_CAP_IN_USE, it might be CAP priorities not
set to non-zero. It might also be CAPs are not set to
automatic mode, or CAPs are in manual mode during
manual checkin. If CAP mode and priorities are set
correctly, contact your ACS System Administrator and
perform ACSLS library problem determination.
ANR8856E
ACSAPI sequence(sequence number)

request (request number) timed out,
elapse time=hours: minutes:seconds.
Explanation: The ACSLS client has received no

response from the ACSLS server for the period as
indicated in the elapsed time. The ACSLS library API
function with the associated sequence number is
canceled if the request number is non-zero.
determination.

determination if the problem persists.
ANR8859W
Unable to lock volume volume id, status=

acs status.
Explanation: The ACSLS library function

acs_lock_volume failed for the specified volume.
command, library volume is unavailable.
determination if the problem persist.
ANR8860W
Volume volume id is already locked by

user id.
Explanation: The specified volume is already locked

by other user or has a different lock id.
System action: Depends on the function, the volume
maybe bypassed or the process maybe terminated.
User response: This may not be an error in a shared
configuration. However, if the existing volume lock is
not needed. contact your ACSLS system administrator
to clear the lock the volume.
ANR8861I
Wait and monitor the ACSSA console

message to remove volume volume id
from CAP.
Explanation: The specified volume is about to put into

CAP for removal. Monitor the ACSSA console and
removed the volume after it has been placed into the
CAP as indicated in the ACSSA message.
666
ANR8862I ANR8872E
User response: Monitor the ACSSA console and wait.
ANR8862I
Unable to access ACS volume volume id.
Explanation: The specified ACSLS volume can not be

accessed in the library. The possible reasons might be
the volume is in use, the user is not authorized, the
volume does not exist in the library.
ANR8867I
Processing volume volume id for the

command command.
Explanation: The specified volume is being processed

for the specified command.

command, library volume is unavailable.
ANR8868E

determination if the problem persist..
Explanation: The volume is failed to be ejected from

the library due to the status as indicated
Ejecting Volume volume name Failed,

status = acs_status .

ANR8863I
Unlocking library library name volumes

from the ACSLS server.
Explanation: The volumes of the specified library are

being unlocked from the ACSLS server.
System action: The operation continues. The process
may take a while depends on the number of volumes
in the library.
ANR8864I
ACSLS library library name is being

re-initialized.
System action: The operation continues. The process

may take a while depends on the number of volumes
in the library. All volumes in the library are being
locked.
Volume volume name bypassed for
command, status=acs_status.
Explanation: The specified volume is bypassed. The

volume is not in a valid status for the specified
function.
User response: Determine the volume status from the
ACSSA and re-issue the command if necessary.
ANR8866E
ANR8869E

update drive drive name.

because there is a request to update the drive already.
Explanation: The specified ACSLS library is being

re-initialized.
ANR8865W
User response: Determine the volume status from the

message and do something as needed
Incompatible option REMOVE=BULK

for ACSLS libraries.
Explanation: The REMOVE=BULK option is not

supported for ACSLS libraries. The final response of
ACSAPI acs_eject does not return to the application
until the volume is removed from CAP.
User response: Reissue the CHECKOUT LIBVOL
command and specify REMOVE=YES or NO.

ANR8870E
The path to the library library name is

unavailable.
Explanation: There is no path to the given library, or

the path to the library is offline, or the source entity of
the path to the library is offline.
System action: The library is inaccessible.
User response: Ensure that a path is defined to the
library. If there is path defined to the library, make sure
the path is online and the source entity of the path is
also online.
ANR8871I
The device name device name specified

has been changed to device name.
Explanation: The specified device name on the

DEFINE PATH or UPDATE PATH command has been
changed to recommended device name.
ANR8872E
No path is available for drive drive name

- could not unload volume volume name
from drive.
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
still on the drive.
System action: The drive is inaccessible.
667
ANR8873E ANR8879E
User response: Ensure that a path is defined to the
drive. If there is a path defined to the drive, make sure
that the path is online and that the source of the path is
also online. Run the AUDIT LIBRARY command after
the problem is corrected.
ANR8873E
The path from source source name to

destination drive name is taken offline.
Explanation: There is problem using the indicated

path. The path is now marked offline.
System action: The path is inaccessible.
User response: Determine the reason the path is
inaccessible, such as hardware problem. Render any
needed corrections. Then, the path may be made online
by issuing the UPDATE PATH command with the
ONLINE=YES option.
ANR8874E
The type of device used by the media in

element element number of library library
name cannot be determined by the
hardware. Volume is not processed.
Explanation: The library's mechanism for determining

the type of media in a slot or EE port failed. This is
usually the barcode reader or some other sensor that is
part of the robotics.
ANR8876E
The media in element element number of

library library name is a cleaner.
Explanation: The library hardware has determined

that the media in the stated slot is a cleaner cartridge.
It cannot be processed by the CHECKIN command
without the STATUS=CLEANER parameter, and it
cannot be labeled by the LABEL command.
System action: The process skips the media, or if it is
the only media being processed the process fails.
User response: Issue the AUDIT LIBRARY command,
ANR8877E
Volume volume name is incompatible

type with device class devclass name in
Explanation: An attempt has been made to service a

mount request, but the attempt fails because the media
type of the cartridge being mounted is not compatible
with the devclass requesting the mount. This is usually
a conflict between WORM and Read-Write
characteristics.
User response: Determine the reason the library could

not determine the media type, such as deteriorated
barcode, scanner failure, or other hardware problem as
determined by system engineer. If the barcode label is
replaced on a private volume containing data, it must
be with a label having the volume name. Scratch
volumes or empty private volumes can be replaced
with any barcode but they must be re-labeled if the
barcode name changes.
User response: If this is not a 3592 device or media,

The volume was probably not checked in with the
CHECKLABEL=YES parameter of the CHECKIN
command. Check the volume out (the REMOVE=NO
may be useful) and check the volume back into the
library with this parameter to ensure that the
mediatype is determined and saved. If this is a 3592
device or media, the volume probably has an incorrect
barcode label indicating that it had the wrong WORM
property. The label needs to be swapped for the
opposite WORM type (e.g. WORM to non-WORM or
non-WORM to WORM) or simply removed entirely
from the library.
ANR8875E
ANR8878E
System action: The volume is skipped by the process.
An illegal move was attempted

involving the media in element element
number of library library name. Its type is
incompatible with the destination
element element number.
Explanation: The server tried to move one type of

volume into a drive or slot of another type that is
incompatible. This is most likely because another
volume has taken its slot, or the server's information
for this volume has otherwise been corrupted.
Explanation: An attempt to close a remote Library

device attached to a NAS File Server failed.
additional information regarding the specified library.
ANR8879E
System action: The process fails.

User response: Issue the AUDIT LIBRARY command,
Failed to close the remote library library

name (device name).
Failed to close the SCSI session for the

remote library library name(device name).
Explanation: An attempt to close a SCSI session for a

remote Library device attached to a NAS File Server
failed.
additional information regarding the specified library.
668
ANR8880W ANR8886E
ANR8880W
Device type of drive Drive name in

library Library name was determined to
be GENERIC_TAPE.
Explanation: The device type of a drive is determined

when the path for that drive is defined. If the wrong
device file was used in the device parameter of
DEFINE PATH the device type of the drive will often
be GENERIC_TAPE. If you are using the TSM device
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
using the native OS device driver.
System action: .
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
in or removed from this library.
ANR8884W

User response: Verify that GENERIC_TAPE is the
desired device type for this drive. While the device
type GENERIC_TAPE is valid, it is often a mistake, and
thus, should be verified that it is the intended device
type. If GENERIC_TAPE is not the intended device
type, all paths for this drive and the drive itself will
have to be deleted and redefined.
ANR8881W
Insufficient space for new volume in

directory directory for device class device
class name.
Explanation: The server found that the indicated

directory had insufficient space in which to create a
new volume.
System action: Other directories available to the
device class are used, if any. If no directories with
space are available, the operation fails. This message is
issued periodically as requests are made for space in
this directory.
User response: The file system must be expanded to
accommodate volume growth.
ANR8882I
Request number: Please provide the label

name for the volume in drive drive name
of library library name by issuing REPLY
n LABEL=xxx within time limit minutes,
where n is the request ID and xxx is the
desired label name.
Explanation: A mount is in progress with

AUTOLABEL, and the name of the volume is needed.
command is issued.
User response: Issue a REPLY command, along with
the request ID, and the volume name for the cartridge.
ANR8883W
The volume volume name in slot element

number is in the library library name but
not in the TSM's inventory database.
Please either check in this volume or
remove it from the library.
Explanation: .
Attempted to label a written WORM

medium in the drive drive name with
code, KEY=internal code, ASC=internal
code, ASCQ=internal code, SENSE=sense
data, Description=error description). Refer
to the Tivoli Storage Manager
descriptions.
Explanation: An I/O error has occurred while labeling

on the written WORM medium.
User response: Ensure the WORM medium in the
drive is not a written WROM medium.
ANR8885W
The device type of drive Device Name is

determined to be GENERICTAPE.
Explanation: You have specified GENERICTAPE=Yes

when defining a path to this drive. The tape drive is
supported and we recommend using with the Tivoli
Storage Manager tape format instead of the generic
tape format. To use the Tivoli Storage Manager tape
format, do not specify GENERICTAPE=Yes when
defining a path to the drive.
User response: Verify that GENERICTAPE is the
desired device type for this drive. While the
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
the intended device type, delete all paths to this drive
and delete the drive itself. Then redefine the drive and
a path without specifying GENERICTAPE=Yes.
ANR8886E
Element address mismatch: Element

element number of library library name is
reported by the library to be element
element number.
Explanation: The library configuration appears to

have changed. Verify that no other management
interfaces are modifying the library inventory.
and the command that was issued. Retry the operation.
It may be necessary to audit the library using the
AUDIT LIBRARY command
669
ANR8901E ANR8908I
ANR8901E
Command: Incompatible options

STATUS=CLEANER and
CHECKLABEL=YES.
Explanation: Cleaner cartridges do not have internal

labels that can be checked by loading them into the
drive.
command and include the parameter,
CHECKLABEL=BARCODE (with SEARCH=YES
specified), or include the parameter
CHECKLABEL=NO (with the required volume name
specified in the CHECKIN command).

ANR8905I
Explanation: A background server process is has been

working to clean the specified drive and is canceled by
System action: The cleaning process is ended.
ANR8906I
ANR8902W
Unable to read the barcode of cleaner

cartridge in slot-id Element number of slot
in library library name; cleaner not
checked in.

read the label of a cartridge that is checked in as a
cleaner. The cartridge is found in the slot with the
given element number.
System action: The cartridge is not checked in. If the
library is being searched, the checkin process continues
with the next volume.
User response: Examine the cartridge to ensure it has
a barcode label and that it is compatible with the
configured and is functioning properly. The cleaner
cartridge can be checked in without use of the barcode
label by issuing the CHECKIN LIBVOL command.
ANR8903E
Command: Missing CLEANINGS

parameter for cleaner cartridge checkin.
Explanation: When checking in a cleaner cartridge, the

CLEANINGS parameter is required.
CLEAN DRIVE process for drive drive

name in library library name is been
canceled.
Cleaning drive drive name in library

library name.

CLEAN DRIVE process on the server. The given
volume is being checked in to the designated library.
continues. The process may be canceled by an
authorized administrator using the CANCEL PROCESS
command.
PROCESS command.
ANR8907E
CLEAN DRIVE for drive drive name in

library library name failed.
Explanation: The background process for a CLEAN

DRIVE fails.
drive is not cleaned.
and ready. Reissue the command.

command and specify a value for the CLEANINGS
parameter which is used to determine the number of
times a cleaner can be mounted to clean a drive.
ANR8904I
Command: Cleaning operation for drive

drive name in library library name started
Explanation: A command-driven process is started to

clean the specified drive. The process is assigned the ID
that is in the message.
ANR8908I
Explanation: The specified drive is successfully

cleaned in the library during processing of a CLEAN
DRIVE command.
System action: The drive is available for normal
library operations.
System action: In response to the CLEAN DRIVE

command that is issued by an administrator, the server
starts a background process to perform the operation.
670
CLEAN DRIVE for drive drive name in

library library name completed
successfully.
ANR8909I ANR8916I
ANR8909I
Cleaning drive drive name in library

library name- CANCEL PENDING.

CLEAN DRIVE process on the server.
terminated.
ANR8913I

ANR8910I
No cleaner, or no cleaner with cleanings

left, found in library library name.
Explanation: A drive is selected to be loaded with a

cleaner cartridge, but no cleaner, or cleaner with
cleanings left, is found in the library's inventory.
library operations.
User response: A cleaner should be checked in to the
library by issuing the CHECKIN LIBVOL command.
ANR8911W
The cartridge in storage element slot

element address in library library name is
not a cleaner cartridge as was expected.
Explanation: The cartridge is listed in the library's

inventory with a cleaner volume status. After loading
the cartridge in the specified storage cell into a drive
for cleaning, it is determined that it is not a cleaner
cartridge.
library operations.
User response: Verify all other cleaner cartridges are
in the correct storage cells. Issue the QUERY
LIBVOLUME command to obtain the storage cells of all
the cartridges currently checked into TSM. The
cartridge should be checked out of the library by
issuing the CHECKOUT LIBVOL command if the
cartridge is still listed in the library's inventory with a
cleaner volume status. If necessary a cleaner cartridge
should be checked in to replace it.
ANR8912E
cartridge is a cleaner, issue the QUERY LIBVOL

command to get the correct storage slot for the cleaner
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
bad volume from the reported slot and run Audit
Library again.
Unable to verify the label of volume

from slot-element element-address in drive
drive name in library library name.
Explanation: The volume from the slot that is

identified by the element address is loaded into a drive.
The drive cannot be opened following the load. The
label cannot be read to process the volume.
System action: The volume is stored, and processing
continues with the next available slot.
User response: Check the system error logs for errors
reported by the drive that are related to this volume.
Make sure that the cartridge is not a cleaner cartridge
that would have been loaded by mistake. If the
Drive drive name in library library name is

currently busy; Cleaning is scheduled.
Explanation: A background process to clean the drive

is unable to acquire the drive because the drive is busy.
completes. The drive is scheduled to be cleaned when
it is unloaded.
ANR8914I

needs to be cleaned.
Explanation: The drive has returned indicating to the

server that it needs to be cleaned.
System action: The server marks the drive to be
cleaned. If the drive is enabled for server-managed
cleaning, and a cleaner cartridge is checked into the
library, the server will load the cleaner into the drive
after the current volume is dismounted. See the
DEFINE DRIVE and QUERY DRIVE commands for
information on enabling server-managed cleaning. See
the CHECKIN LIBVOL command for checking a
cleaner into the library.
ANR8915I
Cleaning cartridge cleaner name in library

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.
User response: As the cleaner is used, monitor the
number of cleanings that remain with the QUERY
LIBVOL command. Remove the cleaner when all
cleanings are exhausted. A new cleaner may be checked
in so that the library is not left without a useful cleaner
when the old cleaner is exhausted.
ANR8916I
Drivemapping for drive Drive name in

library library name on storage agent
storage agent name defined.
Explanation: A drive mapping has been successfully

defined for the specified drive.
System action: The drivemapping is defined and
recorded in the database.
671
ANR8917I ANR8926W
defined or when the server is first initialized.

ANR8917I
Drive mapping for drive Drive name in

storage agent name updated.
Explanation: An UPDATE DRIVEMAPPING request

has been successfully processed for the given drive.
User response: Since the polling thread did not start,

the user must restart the server in order for library
sharing to correctly work. Failure to restart the server
and get these polling services running can cause
unusual results for library clients.

about the drive mapping.
ANR8922I

ANR8918I
Drive mapping for drive Drive name in

storage agent name deleted.
Explanation: The drive mapping for the specified

storage agent, library, and drive has been deleted
successfully.
A device class for library library name

was not found.
Explanation: A library client request a mount

operation to be performed by the library manager. The
library manager is missing a device class definition for
that library.
User response: Define a device class for the library
using the DEFINE DEVCLASS command.
System action: The drive mapping is deleted.

ANR8919I
Initialization and recovery has started

for shared library library name.
Explanation: The shared library has started to

initialize or recover to resynchronize the library
manager and library client.
User response: This process should resynchronize all
of the drives that are currently being used by this
library client. This process might also start after a
communication error or if the library client has not
been able to verify drive status with the library
manager.
ANR8920I
Initialization and recovery has ended for

shared library library name.
Explanation: Initialization or recovery has ended the

library manager and library client should be
synchronized.
User response: The drives previously owned by the
library client should now indicate they are free on the
library manager. Verify this with the QUERY DRIVE
command on the library manager. If ownership of the
drives is still in question restart the library client and
library manager.
ANR8923I
Explanation: A library client attempted to dismount a

drive that was not currently owned by the library
client.
ANR8925W

User response: Verify that the library client with the
above server name is still running. Verify that the
sessions have not been 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 library client are correct.
Unable to start library polling thread.
Explanation: Library sharing requires that this polling

thread starts. This thread keeps the library manager
and library client synchronized with regards to drive
ownership. These thread are started when the library is
672

has not been confirmed for use by
server server name for over elapsed time
seconds. Drive will be reclaimed for use
by others.
Explanation: The library server was unable to contact

the library client for the given interval to verify that the
library client is still using the drive. At this point the
error recovery logic of the library manager will reclaim
the drive (including dismounting the client's volume if
possible) and allow other to use the drive.
ANR8926W
ANR8921E
Dismount failed because drive drive

name in library library name is not
currently owned by drive owner name.
An Error was encountered while

confirming the use of drive drive name in
shared library library name.
Explanation: The library client was unable to confirm

the usage of the drive to the with the library manager.
ANR8927W ANR8932W
User response: Verify that the sessions have not been
disabled and the network is still working between the
two host machines. Verify that the server definition
(QUERY SERVER) on both the library manger and the
library client are correct.
ANR8927W
This library client has been unable to

contact the library manager for elapsed
time seconds. Releasing ownership of all
drives in the shared library library name.
Explanation: The library client was unable to confirm

the usage of the drive with the library manager. The
library client will now dismount all volumes that it
currently owns.
User response: Verify that the sessions have not been
disabled and the network is still working between the
two host machines. Verify that the server definition
(QUERY SERVER) on both the library manger and the
library client are correct.
ANR8928W
Library library name specified for shared

file device class device class name was not
defined as shared. The device class will
not be shareable unless the library is
updated.
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
shared.
ANR8930W
Explanation: When a shared device class is created or

updated, an attempt is made to define additional file
drives in the associated library up to the mount limit, if
the number of drives is less than the mount limit. One
or more failures occurred in defining additional drives.
The number of drives does not correspond to the
mount limit for the associated device class. This can
cause resource balancing problems between the server
and storage agents.
System action: The server continues operation.
get the names of the drives associated with the library.
Use the QUERY DEVCLASS deviceclass F=D command
to find the mount limit of the associated device class.
Use the DEFINE DRIVE command along with the
DEFINE PATH command for this new drive with
DEVICE=FILE to define additional drives in the file
library to match the mountlimit of the associated device
class.
ANR8931W

User response: Issue the UPDATE LIBRARY libname
SHARED=YES command to make the library shared.
ANR8929E
Library library name specified for shared

file device class device class name was not
defined as a FILE library.
Explanation: A pre-existing library was specified for a

new shared file device class. However, the existing
library was not created with the LIBTYPE=FILE
parameter.
System action: None. The device class is not created.
User response: Specify a library name that was
created with the LIBTYPE=FILE and SHARED=YES
parameters, or specify a library name which does not
exist, in which case, the library will be created. You can
also not specify the LIBRARY parameter, a library name
will be created.
An attempt to define drives to create

drives failed for library library name. The
device class has a mount limit of mount
limit but the number of drives in the
associated library is less than the mount
limit.
An attempt to delete drives to delete

drives failed for library library name. The
device class has a mount limit of mount
limit but the number of drives in the
associated library is greater than the
mount limit.
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
attempt is made to delete drives so that there are as
many drives as the mount limit. One or more failures
occurred in deleting drives. The number of drives does
not correspond to the mount limit for the associated
device class. This can cause resource balancing
problems between the server and storage agents.
get the names of the drives associated with the library.
Use the QUERY DEVCLASS deviceclass F=D command
to find the mount limit of the associated device class.
Use the DELETE DRIVE command to delete drives
until the number of drives in the library corresponds to
the device class's mount limit.
ANR8932W
The drive map for server servername,

library library name, drive name drive
name has directory directory which is
different than other drive maps for
drives within the same library.
Explanation: A shared file was about to be created. In

673
ANR8933W ANR8939E
doing so, it was determined that there are differing
definitions for the directories associated with the drive
maps between the indicated drive map and other drive
maps for drives in the same library. This could cause
data to be written in unanticipated locations or may
prevent data from being written.
System action: The server continues operation using
the indicated directory.
User response: Use the QUERY DRIVEMAP command
with the F=D parameter to list the directories
associated with drive maps for drives in the indicated
library and ensure that the directories are correct and
identical. Use the UPDATE DRIVEMAP command to
update any incorrect directory entries.
ANR8933W
File volumename in library library does

not exist in the expected directory.
Explanation: A FILE volume was being dismounted

from a file drive. The file does not exist in the directory
in which it was expected to be found.
User response: It is possible that a drive mapping is
incorrect and that a storage agent is using a valid, but
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
parameter to list the directories associated with drive
maps for drives in the indicated library and ensure that
the directories are correct and identical. Use the
UPDATE PATH command to update any incorrect
directory entries. To move the file into the correct
directory, use the Windows move command or the
Unix mv command, depending on your platform.
ANR8934W
File volumename in library library

associated with device class device class
could not be inserted into the library
inventory.
ANR8935E
A compatible device class for shared

library library name on server server name
was not found.
Explanation: The library client server has a device

class definition that is not compatible with the device
class definition on this server. The device type and
recording format need to be the same on both servers
or one of the servers can have a device type of generic
tape.
ANR8936W
The path conversion of drive drive name

in library library name with device name
device name failed. UPDATE DRIVE
required.
Explanation: During the initialization of a library, the

server finds that the drive path was removed.
library during tape operations.
User response: The drive may be made accessible by
DEVICE= option.
ANR8937W
The device name for drive drive name in

library library name is missing. UPDATE
DRIVE required.
Explanation: The device name for a drive was found

to be missing.
server for tape operations.
User response: The drive may be made accessible by
DEVICE= option.
ANR8938E
Initialization failed for Shared library

library name; will retry within delay time
minute(s).
Explanation: A FILE volume was being inserted into

the library inventory. The file was not found in the
directory associated with the device class that
references the library. However, an entry for the
indicated file name is already in the library inventory.

library has failed. It will be retried automatically in the
specified time.
User response: Ensure that the library manager server

is running, and the library is initialized.
User response: It is possible that a drive mapping is

incorrect and that a storage agent is using a valid, but
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
the F=D parameter to list the directories associated
with drive maps for drives in the indicated library and
ensure that the directories are correct and identical. Use
the UPDATE DRIVEMAP command to update any
incorrect directory entries. To move the file into the
correct directory, use the Windows move command or
the Unix mv command, depending on your platform.
674
ANR8939E
The adapter for tape drive drive name

cannot handle the block size needed to
use the volume.
Explanation: The adapter cannot read and write the

block size need for the volume because the
MAXIMUMSGLIST parameter of the adapter is set to
less than hex 41.
System action: The volume will not be mounted in
the drive.
ANR8940E ANR8945W
User response: The adapter must be updated to
handle a larger block size. The setting is usually
MAXIMUMSGLIST in the Windows registry under:
HKEY_LOCAL_MACHINE->SYSTEM->Current Control
Set->Services->{vendor device name}->Parameters>Device
Note that "{vendor device name}" should be substituted
with the name of the vendors device. For example, the
Qlogic 2200 would use "Ql2200" for the respective
vendor device name.
ANR8942E
Explanation: Could not move volume from slot to

slot.
System action: Move volume operation failed.
ANR8943E
MAXIMUMSGLIST should be set to hex 41 to work

properly with Tivoli Storage Manager.
You can also run the DSMMAXSG utility to set the
MaximumSGList value to 0x41(65) for all HBAs.
For additional information, see the HBA documentation
or contact the vendor for the HBA.
For additional questions, contact IBM support.
ANR8940E
Path definition for file drive drive name

in library library name for server server or
storage agent name does not have a
matching directory in the device class
directory attribute for volume volume
name.
Explanation: A library client or storage agent

requested a mount of a file volume in a drive that is
contained in a file library but the path definition does
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,
from the perspective of the specific server or storage
agent. The list of directories must have entries for each
directory in which file volumes are to be read or
written by the specified server or storage agent.
User response: Ensure that DIRECTORY attribute of
the above path definition contains matching directories
for each of the directories in the server's device class
definition.
ANR8941W
The volume from slot-element

element-address in drive drive name in
library library name is blank.
Explanation: The volume in the slot is not labeled and

is blank.
System action: The volume is skipped, and processing
continues with the next available slot. If the volume is
checked in, it is removed from the inventory.
User response: Label the volume using LABEL
LIBVOL, and check it in using CHECKIN LIBVOL.
Could not move volume volume name

from slot-element element-address to
slot-element element-address.
Hardware or media error on library

library name (OP=internal code,
CC=internal code, KEY=internal code,
ASC=internal code, ASCQ=internal code,
code descriptions.
Explanation: A hardware or media error has occurred

while operating on the specified library.
the DEFINE PATH command and that the library
device is currently powered on and ready. If the library
has an access door, make sure it is closed. The library
ANR8944E
Hardware or media error on drive drive

name with volume volume
name(OP=internal code, Error Number=
internal code, CC=internal code,
ASCQ=internal code, SENSE=sense data,
descriptions.

while operating on the specified drive.
ANR8945W
Scratch volume mount failed volume

name.
Explanation: Scratch volume mount failed.

System action: Scratch volume mount operation
failed.
675
ANR8946W ANR8952E
ANR8946W
There were more labels in the vollist

than volumes available to label.
Explanation: Label Libvolume command still finishes

without error, but the last labels provided were not
used. Labeling finished when there were no more
volumes available.
System action: All available volumes were labeled,
but additional volume names were not utilized from
the vollist.
ANR8947W
There were less labels in the vollist than

volumes available.
Explanation: Label Libvolume command still finishes

without error, but volumes are left unlabeled.
System action: Additional volumes were left
unlabeled.
User response: Proper response may be indicated in

the text of the TapeAlert. The context of the TapeAlert
may need to be determined from other activity log
messages in order to follow its recommendations.
ANR8950W
Device device, volume volume has issued

the following Warning TapeAlert:
alertmessage
Explanation: The specified device without the volume

name has issued a TapeAlert Warning message. This
message is a feature of the hardware and is from the
device, not the TSM server. It is surfaced at the
termination of the current operation but is independent
of the operation.
System action: The operation will fail. See other
messages related to the device or volume in the activity
log.

ANR8951I
ANR8948S
Device device, volume volume name has

issued the following Critical TapeAlert:
alertmessage
Explanation: The specified device while loaded with

the named volume has issued a TapeAlert critical
message. This message is a feature of the hardware and
is from the device, not the TSM server. It is surfaced at
the termination of the current operation but is
independent of the operation.
System action: The operation may or may not fail,
depending on other error indications such as check
conditions from the device. The TapeAlert message
does not by itself indicate failure. See other messages
related to the device or volume in the activity log.
Explanation: The specified device while loaded with

the named volume has issued a TapeAlert information
message. This message is a feature of the hardware and
is from the device, not the TSM server. It is surfaced at
the termination of the current operation but is
independent of the operation.
System action: The operation may or may not fail,
depending on other error indications such as check
conditions from the device. The TapeAlert message
does not by itself indicate failure. See other messages
related to the device or volume in the activity log.
ANR8952E
ANR8949E

the following Critical TapeAlert:
alertmessage
Explanation: The specified device regardless loaded or

not without the named volume has issued a TapeAlert
critical message. This message is a feature of the
hardware and is from the host interface, not the TSM
server. It is surfaced at the termination of the current
operation but is independent of the operation.
System action: The operation will fail. The TapeAlert
message does not by itself indicate failure. See other
messages related to the device or volume in the activity
log.
676

the following Information TapeAlert:
alertmessage
Library serial number does not match

that defined for library name .
Explanation: The serial number defined for the

specified library does not match the serial number
discovered. The pending operation will fail.
System action: The library is taken offline when the
mismatch is discovered. Verify the serial number and
the device name for the library against those defined. If
they do not match, the definitions for the library are
incorrect and need updated. Once the serial number is
updated, the library will be brought back online.
User response: Update the serial number or device
name for the specified library with the correct values.
ANR8953I ANR8961E
ANR8953I
Library library name with serial number

serial number is updated with the newly
discovered serial number serial number.
Explanation: The serial number for the library defined

does not match with the serial number discovered. The
newly discovered serial number will replace the
existing definition for this library since autodetect is on.
System action: The existing serial number for the
specified library is replaced by the newly discovered
serial number.
ANR8954E
Failed to obtain a path for drive drive

name for library library name.
Explanation: An attempt to acquire a path for the

drive failed. This most likely means that a path is not
defined for this drive.
User response: Ensure that a path is defined for this
drive. If one is defined, make sure it is defined
correctly with the correct source and destination type.
If the drive is in a shared FILE library:
for library and the newly discovered serial number is

detected.
User response: Update the serial number for the
specified library with the correct values.
ANR8957E
Explanation: The serial number of the library in the

database did not match the serial number of the library
found using the device special file specified. UPDATE
PATH cannot be used to change libraries, and thus, the
new device must have the same serial number as
stored in the database unless the serial number in the
database is empty.
valid DEVICE parameter value. If this is a new or
different library with a different serial number, a new
library and path should be defined with DEFINE
LIBRARY and DEFINE PATH.
ANR8958E
Ensure that the number of paths defined for the storage

agent is the same as the number of drives within the
library.
Ensure that the directories are correct in the server
device-class definition and the storage-agent path
definitions.
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
directory definition.
ANR8955I

with serial number serial number is
updated with the newly discovered
serial number serial number.
Explanation: The serial number for the drive defined

does not match with the serial number discovered. The
newly discovered serial number will replace the
existing definition for this drive since autodetect is on.
System action:
Command: The serial number reported

by the library did not match the serial
number in the library definition.
Command: Autodetect is OFF and the

serial number reported by the drive did
not match the serial number in the drive
definition.
Explanation: An invalid value has been provided for

the specified parameter.
valid parameter value.
ANR8959W
Path to the library or the device does

not exist.
Explanation: A path to the library or the device does

not exist yet.
System action: This may not be an error.
ANR8960I
Command: The display of Tape Alerts

from SCSI devices is status.
Explanation: Whether the status of Tape Alerts from

SCSI devices will be display.
System action: The command is processed.

ANR8956E
Serial number defined for library library

name does not match the discovered
serial number.
Explanation: The serial number for the library defined

does not match the serial number discovered due to
autodetect is set to NO. The pending operation will fail.
System action: A mismatch between the serial number

ANR8961E
Serial number defined for library library

name and drive drive name is blank and
does not match the discovered drive
serial number serial number.
Explanation: A device has been swapped and we are
677
ANR8962E ANR8968E
not able to get the new path.
ANR8965W
System action: .
ANR8962E
Unable to find path to match the serial

number defined for library library name.
Explanation: Either a device has hardware problems

or a device path has been changed and the TSM server
cannot find the new path with the SAN Discovery
option set to ON.
System action:
ANR8963E
Unable to find path to match the serial

number defined for drive drive name in
Explanation: A device may have hardware problems

or a device path may have been changed and the TSM
server cannot find the new path with the SAN
Discovery option set to ON. The TSM server cannot get
device information when it cannot open the device.
Therefore, the TSM server cannot validate the drive
serial number to see if this drive with the failed open
operation is the same drive as it previously used. The
causes of this failed open device may be a bad cable, a
bad drive or a bad HBA card. However, if an incorrect
drive is used (for example, an incorrect device path)
and with the SAN discovery option set to OFF or
UNSCANNEDPATHOFF, the TSM server will not
search the SAN environment to get a proper device.
System action: The TSM server may mark this device
offline for SAN Discovery option ON or
UNSCANNEDPATHOFF.
User response: Users should check the TSM server
option file first. If SAN discovery option is set to OFF
or UNSCANNEDPATHOFF, set it to ON and check for
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.
ANR8964W
Unable to update the path in the

database path source name and drive drive
name.
Explanation: The system is not able to update the

path information in the database.
System action: .
The server is unable to obtain the serial

number of the SCSI device device name.
Explanation: The server cannot detect a device serial

number from the HBAAPI or the device itself, so the
server is not able to automatically correct the path for
the device.
User response: Verify the following:
v The device name in the path definition is correct.
v The correct version of the HBAAPI is installed to the
system.
v The SANdiscovery option is set to ON in the options
file.
ANR8966E
Cannot get device number for the drive

drive name.
Explanation: The server is unable to obtain the device

number for the specified drive. This could occur if an
invalid device name is specified for the drive or if there
is hardware errors.
system logs or an invalid device name was specified
for the drive. Render any needed corrections to the
accessible.
ANR8967E
Command: The drive serial conflicts with

an existing drive in library library name.
Explanation: The serial number already exists in the

drives in the given library.
User response: Specify a valid serial parameter for
this drive.
ANR8968E
Unable to create path for device device.
Explanation: An attempt to contact the drive with a

given device name failed. This probably means the
device name is incorrect, but this attempt can also fail
for other reasons.
System action: Operation failed.
User response: The device parameter is probably not
valid. This could be temporary, but not necessarily. If
this occurs while upgrading from Tivoli Storage
Manager Version 4.1 or previous (where paths were not
used), then the drive needs to be deleted, redefined,
678
ANR8969E ANR8976E
and a new path needs to be defined with a valid device
parameter. If this occurs on a Tivoli Storage Manager
server that already has paths (Version 4.2 or higher),
then just update the drive to online. The device
parameter on the drive path can also be updated before
the drive is turned online, if you know the device
parameter should be changed.
User response: Make sure the serial number entered

for the drive is correct if AUTODETECT is not active. If
AUTODETECT is active, the drive serial number might
be incorrect or the library reported an incorrect
serial/element number map. Contact your service
representative.
ANR8973E
ANR8969E
The owner of volume Volume name can

not be updated to owner Owner name.
Explanation: A command was issued updating

ownership of a volume. The owner of this particular
volume can not be changed.
ANR8970E
Unable to open special file specialfile for

tracing parameter device driver; errno =
errno.
Explanation: The special file created by the device

driver for tracing purposes could not be opened by the
server. This file should be created when the device
driver is configured on the system
System action: Device driver tracing could not be
started.
User response: Make sure that the special file exists
and can be accessed by the server. If the device driver
has not been completely configured and special files
created for all devices, do so. The device driver can
also be traced by specifying the name of a library or
drive that has been defined to the TSM Server.
ANR8971E
Unable to validate directory name

directory name for parameter command.
Explanation: The specified directory name was being

used in the indicated command. The server attempted
to validate that the directory was accessible so that it
could be used in the command definition. The server
was unable to validate that the directory was
accessible.
System action: The command fails. The server
continues.
User response: Make sure that the directory exists and
can be accessed by the server.
ANR8972E
command: Unable to find the element

number for drive drive name in library
library name.
Explanation: Because the drive serial number does not

match any drive serial number in the serial/element
number map reported by the library, the element
number cannot be determined.
Reset has failed to break the reservation

set by another system for device device
name with path path name.
Explanation: The attempt to reset the device

reservation set by another system has failed.
System action: .
User response: If this tape device is a Fibre Channel
direct attached device on Windows 2003, please make
sure the HBA driver is a StorPort driver by checking
the HBA vendor's support web site. The device reset
(LUN Reset) on Windows 2003 requires StorPort driver.
Otherwise, the device may have to be rebooted to reset
the reservation. If not rebooted, this device will not be
accessible. If "RESETDrive" keyword for the update
library command is set to NO, device reset will not be
attempted.
ANR8974I
Found new path for path source name and

target name target name old path old path
name new path new path name. Path
information will be updated remotely.
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.
System action: .
User response: The path change may be caused by
system reboot or cable swap or device addition or
removal.
ANR8975I
Found new path for path source name and

target name target name old path old path
name new path new path name. Path
information is updated.
Explanation: A new path has been found for the

device and the path information has been updated.
System action: .
User response: The path change may be caused by
system reboot or cable swap or device addition or
removal.
ANR8976E
Unable to open special file specialfile for

LUN reset with errno = errno.
Explanation: The special file created by the device

driver for LUN reset purposes could not be opened by
the server. This file should be created when the device
driver is configured on the system
679
ANR8977W ANR8984E
System action: LUN reset could not be started.
User response: Make sure that the special file exists
and can be accessed by the server. If the device driver
has not been completely configured with special files
created for all devices, resolve the device driver
configuration.
ANR8977W
The volume loaded into library library

name did not have a valid label. Please
load a scratch volume with a valid label.
ANR8980I
SCAN LIBRARY process for library

library name has been canceled.

been working to scan the given library is canceled by
Explanation: During normal operations a MANUAL

library will prompt the user for the desired volume
name if the volume does not have a valid label and the
AUTOLABEL parameter is turned on. However, the
utility mode of DUMPDB cannot prompt the user for a
desired volume name.
ANR8981I
System action: The server unloads the volume and

asks for a new scratch volume with a valid label.

PROCESS command.
User response: The user needs to insert scratch

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
The number of drives in library library

name has been increased from original
drive count to new drive count Please
restart the TSM server to update the
configuration;
Explanation: The number of drives in the library has

been increased. The new configuration will be recorded
if TSM server is restarted.
System action: .
User response: Number of drives in the library has
been increased. The user needs to restart the TSM
server to capture the new configuration.
ANR8979I

Explanation: A sacn library process has been started

for the given library. The process is assigned the ID
specified in the message.
to perform the operation in response to the SCAN
LIBRARY command entered by an administrator.
680
Scanning for library library name.

command, this message displays the status for an
SCAN LIBRARY process on the server.
ANR8982E

Explanation: The background process for an SCAN

LIBRARY command has failed.
System action: The background process ends.
and ready, then reissue the command.
ANR8983I

library name completed successfully.
Explanation: The background process for an SCAN

LIBRARY command has completed successfully.
System action: The library has been scaned.
ANR8984E
The drive drive name in library library

name is incapable of performing any
drive encryption operations.
Explanation: The server queried the drive's encryption

capability, and the query failed or the query showed
that the drive does not have encryption capabilities.
System action: The mount operation fails.
User response: If this message occurs on a scratch
mount and drive encryption has not been utilized yet,
you can turn drive encryption off by updating the
DRIVEENCRYPTION parameter on the device class.
Otherwise, verify your hardware configuration. First,
verify that all the drives in this logical library support
drive encryption. Second, verify that the device driver
controlling all of the drives in this library also supports
drive encryption. If both the drives and the device
ANR8985E ANR8990E
driver support drive encryption, call your drive
hardware support.
ANR8985E
The drive drive name in library library

name is using an encryption method that
is incompatible with the current server
settings.
Explanation: The server requires the drive to use

various drive encryption methods based on the
DRIVEENCRYPTION device class parameter for empty
volumes or based on the previous encryption method
used for filling volumes. The server is unable to
properly handle the volume's encryption key without
resolving this conflict.
User response: If this message occurs while mounting
an empty volume the encryption method setup in your
hardware environment is incompatible with the
DRIVEENCRYPTION setting in your device class.
Either update the device class or your hardware's
encryption method such that these setting no longer
conflict. If this message occurs while mounting a filling
volume, either update your hardware configuration to
the same method used while originally backing up this
volume, which can be determined by the QUERY
VOLUME FORMAT=DETAIL command, or update this
volume's access to UNAVAILABLE.
ANR8986E
The server currently doesn't allow AES

encryption which is required for drive
encryption support with the
DRIVEENCRYPTION=ON parameter on
the device class.
Explanation: Without AES encryption support the

server cannot generate adequately strong enough
encryption keys for drive encryption.
User response: Update the DRIVEENCRYPTION
parameter on the device class to a value other than
ON.
ANR8987W
The server will not encrypt the volume

volume name.
Explanation: Drive encryption with the device class

parameter setting of DRIVEENCRYPTION=ON will
only encrypt storage pool volumes. Thus, backupsets,
DB backups, and export volumes will not be encrypted.
System action: The mount continues, but encryption is
not used.
User response: If encryption is needed for this volume
or other backupsets, DB backups, or export volumes,
use a different method of encryption: use a device class
parameter of DRIVEENCRYPTION=ALLOW and a
hardware method of 'Library' or 'System' (do not use
the 'Application' method).
ANR8988W
Library Library Name failed to relabel

volume Volume Name after it returned to
scratch.
Explanation: The RELABELSCRATCH option is

enabled, and while attempting to relabel the volume
the operation failed.
User response: This warning may be issued if the
relabeling operation attempts to relabel the same
volume as another library volume operation: LABEL
LIBVOLUME, CHECKIN LIBVOLUME, CHECKOUT
LIBVOLUME, or another relabeling operation. For
example, suppose two relabeling operations run on the
same volume. If the first relabeling operation succeeds
and the second operation fails, no action is required.
Verify the volume is still checked into the library with
the QUERY LIBVOL command. If it is not checked in,
use LABEL LIBVOL or CHECKIN LIBVOL to check the
volume back into the library.
ANR8989E
Unable to establish a communication

session with the primary library
manager.
Explanation: The requested operation required that a

communication session be established with a library
manager. The library manager was found to be
unavailable at this time.
User response: Verify the primary library manager is
up and operational. Once the server is verified to be
operational, retry the operation.
ANR8990E
Device Device Name is not supported by

the Tivoli Storage Manager server.
Explanation: The device product identification is not

recognized by the Tivoli Storage Manager server.
User response: Determine if the installed level of the
server supports the device by visiting the Tivoli Storage
Manager Supported Devices web site at
http://www.ibm.com/software/sysmgmt/products/
support/
IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.
html.
If the device is a tape drive and is not supported, you
can use it with the generic tape format. To use the
drive, specify GENERICTAPE=Yes when defining a
path to the drive. If the device is supported and this
message is received, search the Tivoli Storage Manager
Support Web site for known solutions:
support/IBMTivoliStorageManager.html
681
ANR8991E ANR8998W
If no solution is found, report the issue to Tivoli
Storage Manager Support.
ANR8991E
The GENERICTAPE format is not

supported with drive Device Name.
Explanation: The device driver does not support all

features required for the GENERICTAPE format.
User response: Make sure the tape drive is controlled
by the native device driver. The Tivoli Storage Manager
device driver does not support the generic tape format.
If the drive is controlled by the Tivoli Storage Manager
device driver and you intend to use the Tivoli Storage
Manager tape format with the drive, do not specify
GENERICTAPE=Yes when defining a path to the drive.
ANR8992E
The library state refresh for library name

failed.
Explanation: The operation to re-initialize the library's

state failed.

assistance.
ANR8996W
Explanation: The server was unable to query or

enable append-only mode on the tape drive.
System action: The server will not enable append-only
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
CHECKTAPEPOS is set to Yes or DRIVEonly.
User response: If the problem persists, contact your
service representative for assistance. If you do not want
the server to use append-only mode for data overwrite
protection, you can set the server option
CHECKTAPEPOS to No or TSMonly.
ANR8997W

User response: To refresh the library state, halt and
restart the Tivoli Storage Manager server.
ANR8993I
The library state refresh for library name

was successful.
Explanation: The server successfully re-initialized the

library's state.
Unable to query or enable append-only

mode on drive Drive Name.
The current version of the device driver

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

meet the version requirement to support append-only
mode.
mode on the tape drive for data overwrite protection.
User response: Upgrade the device driver for the
drive to the required version.

ANR8998W
ANR8994W
Append-only mode is not supported on

drive Drive Name.
Encryption has been disabled for drive

drive name in library library name.
Explanation: The server attempted to enable

Append-Only mode on the tape drive for data
overwrite protection. However, the tape drive does not
support Append-Only mode.
Explanation: The server determined that the drive's

encryption method was Application Managed
Encryption (AME). Since the server is assumed
responsibility for encryption settings when device class
uses DRIVEENCRYPT=ALLOW and the drive uses
AME, encryption has been disabled.

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
you do not wish the server to use append-only mode
for data overwrite protection on the tape drives that
support append-only mode.
User response: If encryption is intended to be used

for this operation, with TSM managing the encryption
keys, then the DRIVEENCRYPT parameter should be
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
AME encryption solutions without TSM managing
encryption), then the DRIVEENCRYPT parameter
should be set to EXTERNAL. In either of these
situations, data on the volume used in this operation
will need to be moved to a new volume with the
correct settings to encrypt the data.
ANR8995E
Unable to write to volume Volume Name

in drive Drive Name.
Explanation: The server is unable to write to the

volume because the drive is in append-only mode and
the volume is write-protected.
682
ANR8999E ANR9580W (Solaris)

ANR8999E
Directory name directory name has been

duplicated in parameter command.
Explanation: When defining or updating multiple

directories for a device class, you can only specify a
directory name once in the command.
User response: Restart the operation to try the volume

in a different drive. If the problem persists, check the
hardware connections and the tape drive.
ANR9579W (HP-UX) Command: The file file name
cannot be found.
System action: The command fails. The server

continues.
Explanation: The specified file cannot be found.
User response: Ensure that the directory name is

specified only once in the command.
System action: For the default server executable file,

the PREPARE command uses /opt/IBMadsm-s/bin/
dsmserv.
ANR9000E
Drive drive name does not support

logical block protection.
Explanation: The LBPROTECT parameter associated

with the device class is set to enable logical block
protection. However, the tape drive does not support
User response: Update drive firmware to the level
that supports logical block protection.
ANR9001W
Volume volume name does not have

Explanation: The server cannot enable logical block

protection for this volume. Data that is already on the
volume does not have logical block protection, or the
media type is not compatible with logical block
protection.
System action: The operation will continue without
logical block protection enabled on the volume.
User response: If the media type supports logical
block protection, mark the volume access to
READONLY so that the server cannot write to the
volume.
ANR9002E
The version of the device driver for

drive Drive Name is Driver Version. Driver
version Required Version or later is
required for logical block protection.
Explanation: The device driver for the drive does not

meet the version requirement for logical block
protection.
User response: Upgrade the device driver for the
drive to the required version.
ANR9003E
The block CRC validation failed on

volume volume name in drive drive name.
Explanation: The data block was corrupted while it

was transferred to or from the drive.
User response: Determine why the file does not exist

and create it if necessary.
ANR9579W (Linux) Command: The file file name
cannot be found.
dsmserv.
ANR9579W (Solaris) Command: The file file name
cannot be found.
dsmserv.
ANR9580W (Linux) Command: Generated replacement
volume name volume name may not be a
valid raw partition name. Original
volume name:volume name. Stanza is
stanza name.
name postfix to the original volume name has created a
name that may not be a valid raw partition name.
User response: Manually update the generated
recovery plan stanza with a legal replacement name.
The replacement name can be another raw partition
name or a regular file name.
ANR9580W (Solaris) Command: Generated
replacement volume name volume name
may not be a valid raw partition name.
Original volume name:volume name.
Stanza is stanza name.
683
ANR9581W (HP-UX) ANR9583E (HP-UX)

name postfix to the original volume name has created a
name that may not be a valid raw partition name.
valid prefix. The following commands are used to

specify the prefix:

v SET DRMINSTRPREFIX
User response: Manually update the generated

recovery plan stanza with a legal replacement name.
The replacement name can be another raw partition
name or a regular file name.
ANR9581W (HP-UX) Command: Volume file name not
found while building stanza recovery
plan stanza name.
Explanation: This volume is defined to the server but
does not exist. The device class associated with the
volume is DISK or the device class device type is FILE.
System action: The entry for the volume is not
included in the recovery plan stanza.
User response: Determine why file does not exist;
create if necessary.
v SET DRMPLANPREFIX
v PREPARE
ANR9582E (Linux) command: Generated file name too
long. Length of directory or prefix
'prefix' plus 'name' exceeds maximum
Explanation: The file name generated is too long. The
maximum valid length is shown in the message.
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9581W (Linux) command: Volume file name not

plan stanza name.
ANR9582E (Solaris) Command: Generated file name

too long. Length of directory or prefix



ANR9581W (Solaris) Command: Volume file name not
plan stanza name.

specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9583E (HP-UX) Command: Cannot generate fully
qualified file name for 'name'.
Explanation: A failure occurred expanding the
specified file name.


specify the prefix:
ANR9582E (HP-UX) Command: Generated file name

too long. Length of directory or prefix
v SET DRMPLANPREFIX
v PREPARE

684
ANR9583E (Linux) ANR9586E (Solaris)

ANR9583E (Linux) command: Cannot generate fully
ANR9585E (HP-UX) Command: Cannot generate a

volume history file name.

Explanation: A failure occurred generating the volume

history file name.

specify the prefix:

information.
v SET DRMPLANPREFIX
ANR9585E (Linux) command: Cannot generate a

v PREPARE

history file name.
ANR9583E (Solaris) Command: Cannot generate fully


specify the prefix:
v SET DRMPLANPREFIX

information.
ANR9585E (Solaris) Command: Cannot generate a
history file name.

information.
v PREPARE
ANR9584E (HP-UX) command: Cannot generate server
options file name.
Explanation: A failure occurred generating the server
options file name.
information.
ANR9584E (Linux) command: Cannot generate server
options file name.
options file name.
information.
ANR9584E (Solaris) Command: Cannot generate
server options file name.
options file name.
information.
ANR9586E (HP-UX) Command: Cannot generate a

device configuration file name.
Explanation: A failure occurred generating the device
configuration file name.
information.
ANR9586E (Linux) command: Cannot generate a
information.
ANR9586E (Solaris) Command: Cannot generate a
information.
685
ANR9600E (AIX) ANR9604E (AIX)

ANR9600E (AIX) Invalid information passed to
NETLS license interface.
ANR9602E (AIX) Invalid JOB information passed to

the NETLS Interface.
Explanation: The server licensing functions

encountered an internal error in accessing license
information for the server storage capacity and number
of registered clients.

System action: Server operation continues. New

licensing information is not used by the server.



ANR9600E (Solaris) Failed to allocate memory for

shared memory communications. Error:
error text.
ANR9602E (Solaris) Error errno while attaching

memory segment for shared memory
communications.
Explanation: An error has occurred when attempting

to get memory for the shared communications option.

attach a shared memory segment for a shared
communications session.
System action: Shared memory communications will

not be activated.
User response: The maximum shared memory is, most
likely, too small. To increase on SUN, update
"/etc/system" with "set
shmsys:shminfo_shmmax=268435456" (a recommended
size).
System action: The shared memory communications

session does not initialize.
User response: Check the SUN documentation for the
shmat subroutine and determine what the errno
indicates, and take the appropriate action to correct the
error.
ANR9601E (AIX) The NETLS license interface was

not initialized properly.
ANR9603E (AIX) The NETLS Nodelock file could

not be created.

Explanation: The server was not able to create the file

/usr/lib/netls/conf/nodelock which is used for storing
license password information.

ANR9601E (Solaris) Failed to allocate message queue
for the shared memory communications
Error: error text.
not be activated.
User response: If the error given is "ENOSPC", the
maximum number of system message queue have
likely been exceeded. update "/etc/system" with "set
shmsys:msginfo_msgmni=100". Any other error
suggests an internal problem and shoud be reported.

User response: If the server is not running with root
authority, make sure that directory authorities in the
/usr/lib/netls/conf path are set so that the user ID
under which the server is running can create, read, and
write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your
service representative for assistance in resolving this
problem.
ANR9604E (AIX) The NETLS license interface
encountered an internal error.
686
ANR9605E (AIX) ANR9611E (AIX)

ANR9605E (AIX) An invalid vendor ID was passed
to NETLS.
ANR9606E (AIX) NETLS failed to find socket
families to contact a server.
REGISTER LICENSE command. Be sure to correctly

enter the license information.
ANR9610E (AIX) Unable to create directory: directory.
Explanation: The REGISTER LICENSE command is
unable to either create or verify the specified directory
structure.
problem.
ANR9610E (Linux) Unable to create directory:
directory.
structure.
ANR9607E (AIX) No NETLS Servers found.

ANR9608E (AIX) A NETLS Security Breach was
encountered.
ANR9609E (AIX) Incorrect license entered: Password
entered = password Annotation entered =
annotation.
Explanation: The license information entered for a
REGISTER LICENSE command is not correct.
User response: Register the license again with the

given directory path are set so that the user under
which the server is running can create, read, and write
to the server's license file. If the server is running with
root authority, contact your service representative for
assistance in resolving this problem.
ANR9610E (Solaris) Unable to create directory:
directory.
structure.
given directory path are set so that the user under
which the server is running can create, read, and write
to the server's license file. If the server is running with
root authority, contact your service representative for
assistance in resolving this problem.
ANR9611E (AIX) Unable to open NODELOCK file:
file.
unable to either create or open the nodelock file.
687
ANR9612E (AIX) ANR9614E (Linux)

problem.
ANR9612E (AIX) Error writing to NODELOCK file.
Explanation: The REGISTER LICENSE command fails
writing to the nodelock file.
problem.
ANR9613W (AIX) Error loading modname for
Licensing function: error string.
Explanation: The server cannot load file module
modname to initialize licensing functions due to error
error string.
System action: Server operation continues. Default
licensing values are in effect for running the server.
User response: The dsmreg.lic module is accessed as
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
DSMSERV_DIR environment variable. The dsmreg.lic
module is only installed when you purchase the
product.
ANR9613W (HP-UX) Error loading modname for
error string.
User response: The dsmreg.lic module is accessed as
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
DSMSERV_DIR environment variable. The dsmreg.lic
module is only installed when you purchase the
product.
688
ANR9613W (Linux) Error loading modname for

Licensing function.
modname to initialize licensing functions.
User response: dsmreg.lic is accessed as part of the
load process for licensing. It should be in the same
directory as the dsmserv executable file or it must be in
a directory that is pointed to by the DSMSERV_DIR
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9613W (Solaris) Error loading modname for
error string.
User response: dsmreg.lic is accessed as part of the
load process for licensing. It should be in the same
directory as the dsmserv executable file or it must be in
a directory that is pointed to by the DSMSERV_DIR
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9614E (AIX) Unable to open license file: file.
unable to create or open the server license file.
User response: Make sure that the user ID under
which the server is running has the authority required
to create or write, or both, to the license file in the
directory in which the server is running. If this does
not resolve the problem, contact your service
ANR9614E (Linux) Unable to open license file: file.
unable to either create or open the server license file.
ANR9614E (Solaris) ANR9617I (AIX)

ANR9614E (Solaris) Unable to open license file: file.
unable to either create or open the server license file.
ANR9615E (AIX) Error writing to adsmserv.licenses
file.
ANR9616I (AIX) Invalid license record record value

found in license file - it will be
skipped.
Explanation: The license manager found an invalid
record in the server license file (adsmserv.licenses). The
record is ignored.
System action: The invalid record is ignored.
User response: Erase the adsmserv.licenses file and
reregister your licenses.
ANR9616W (Linux) Invalid license record record value
found in license file - it will be ignored.

writing to the server license file.

record is ignored.

directory in which the server is running. Also, ensure
that free space is available in the file system so that the
license information can be written to the file. If this
does not resolve the problem, contact your service

reregister your licenses. Refer to the licenses provided
to you to ensure that only valid licenses are specified
with the REGISTER LICENSE command.
ANR9616W (Solaris) Invalid license record record
value found in license file - it will be
ignored.
ANR9615E (Linux) Error writing to adsmserv.licenses

file.

record is ignored.


reregister your licenses. Refer to the licenses provided
to you to ensure that only valid licenses are specified
with the REGISTER LICENSE command.
User response: Make sure that the userid under which

the server is running has the authority required to
create and/or write to the license file in the directory in
which the server is running. Also ensure that there is
free space available in the filesystem so that the license
information can be written to the file. If this does not
resolve the problem contact your service representative
for assistance.
Explanation: The license authorization specified for a

REGISTER LICENSE command is not valid.
ANR9615E (Solaris) Error writing to

adsmserv.licenses file.
System action: Server operation continues; licensing

terms are not changed by the REGISTER LICENSE
command.

User response: Make sure that the userid under which
the server is running has the authority required to
create and/or write to the license file in the directory in
which the server is running. Also ensure that there is
free space available in the filesystem so that the license
information can be written to the file. If this does not
resolve the problem contact your service representative
for assistance.
ANR9617I (AIX) Invalid license authorization:

authorization string.
User response: Examine the license authorization

string that was entered with the REGISTER LICENSE
command. Reenter the command if the license
authorization was not specified correctly. If the license
authorization has been specified correctly, contact your
689
ANR9617W (Linux) ANR9623I (AIX)

ANR9617W (Linux) Invalid license authorization:
command.
User response: Examine the license authorization that
was entered using the REGISTER LICENSE command.
Reenter the command if the license authorization was
not specified correctly. If the license authorization has
been specified correctly, contact your service
representative.
ANR9617W (Solaris) Invalid license authorization:
command.
User response: Examine the license authorization that
was entered using the REGISTER LICENSE command.
Reenter the command if the license authorization was
not specified correctly. If the license authorization has
been specified correctly, contact your service
representative.
ANR9618E (AIX) License registration is not
supported on this server.
because the license authorization module cannot be
found.
command.
User response: The license authorization file is
required for formal licensing for the AIX/6000 server.
The file is delivered when the product is purchased,
but it is not available in the product service stream or
with demonstration copies of the server. If you have
purchased the server, contact your service
representative for assistance in resolving this problem.
ANR9618E (Linux) License registration is not
Explanation: The REGISTER LICENSE command
failed because the license authorization module could
not be found.
command.
690

required for formal licensing for the server. The file is
delivered when the product is purchased, but is not
available in the product service stream or with
demonstration copies of the server. If you have
purchased the server, please contact your service
representation for assistance in resolving this problem.
ANR9618E (Solaris) License registration is not
Explanation: The REGISTER LICENSE command
failed because the license authorization module could
not be found.
command.
delivered when the server is purchased, but is not
purchased the server, please contact your service
representation for assistance in resolving this problem.
ANR9622I (AIX) An EVALUATION LICENSE for
support of Tivoli Space Management
will expire on expiration date.
Explanation: The AIX/6000 server is distributed with
an evaluation license for Tivoli Space Management
support. If no formal license is found for the server and
the evaluation period has not lapsed, this message is
displayed each time the server checks the server license
terms.
System action: The Tivoli Space Management license
allows clients to utilize the server for storing files
migrated during space management. The server checks
this license when files are migrated to the server from
client nodes to ensure that the server is licensed to
perform this function.
User response: If you are interested in using the
server, contact your service representative to obtain
formal licenses for the server before the evaluation
period has elapsed. Without formal licenses, the server
will not support Tivoli Space Management after the
expiration date shown.
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
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.
ANR9624E (AIX) ANR9624I (Windows)

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
machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked
and when a data base backup or storage pool backup
to a device class of type server are performed to ensure
that the server is licensed to perform this function.
will not support Tivoli Disaster Recovery Manager after
the expiration date shown.
ANR9624E (AIX) Unexpected error encountered in
iFor/LS (SystemView License Use
Management) routine license interface
name status=xreported status code.
Explanation: The server encountered an unexpected
error in accessing the SystemView License Use
Management function specified.

ANR9624I (Linux) An EVALUATION LICENSE for
Explanation: The server is distributed with an
evaluation license for Tivoli Space Management
terms.
System action: The server license monitoring

operation fails
ANR9624I (Solaris) An EVALUATION LICENSE for

User response: The SystemView License Use

Management product is installed during normal AIX
server installation. Check to make sure that server was
installed correctly. If the installation was successful,
re-boot your AIX system and re-start the server. If this
message continues to be issued, contact your service
representative.

terms.
ANR9624I (HP-UX) An EVALUATION LICENSE for



terms.

ANR9624I (Windows) An EVALUATION LICENSE
for support of Tivoli Space Management
terms.
691
ANR9625E (AIX) ANR9625I (Solaris)

ANR9625E (AIX) Could not open file file name.
Explanation: The server could not open the license
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
evaluation license for Tivoli Disaster Recovery Manager
terms.
692
ANR9625I (Linux) An EVALUATION LICENSE for

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.
stores information in the server for server recovery, and
when PREPARE or MOVE DRMMEDIA are invoked,
ANR9625I (Solaris) An EVALUATION LICENSE for
terms.
ANR9625I (Windows) ANR9631E (Windows)

ANR9625I (Windows) An EVALUATION LICENSE
for support of Tivoli Disaster Recovery
terms.
ANR9626E (AIX) Invalid license certificate file: file
name.
Explanation: The specified file does not contain valid
license certificate information.
System action: The license registration command
ignores the contents of the file.
ANR9627E (AIX) Cannot access node license lock
file: file name.
Explanation: The server was not able to access the
specified file. The node lock file contains licensing
information for the server.
System action: The license function fails.
User response: Examine the file specification
displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is
either in the directory from which the server is started,
or in the directory specified by the DSMSERV_DIR
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
specified for the file. If the problem persists after these

corrections have been made, contact your service
representative.
ANR9628E (Windows) Unexpected error encountered
in iFor/LS (SystemView License Use
operation fails
Management product is installed during normal server
installation. Check to make sure that the product was
re-boot your system and re-start the server. If this
representative.
ANR9629E (Windows) Could not open file file name.
ANR9630E (Windows) Invalid license certificate file:
file name.
ANR9631E (Windows) Cannot access node license
lock file: file name.
693
ANR9632I (Windows) ANR9635E (HP-UX)

environment variable. Re-specify the DSMSER-DIR
representative.
ANR9632I (Windows) Cannot load licensing DLL
library: DLL file name : the server will
assume evaluation licensing mode.
Explanation: The server was not able to load the
specified dynamic link library.
System action: Server licensing asumes Try and Buy
mode with licenses for 180 days.
User response: The named DLL library(ies) are
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
libraries are installed and this message continues to be
issued, contact a support representative for assistance.
ANR9634E (AIX) command name: No license certificate
files were found with the file name
specification specification.
Explanation: The server did not find any license
certificate file(s) with the file name specification
entered.
the license certificate file(s) you intended to use. The
file name specification indicates the fully qualified file
name the server was trying to read. The directory used
to locate the license certificate files when no explicit
path is provided is determined as follows:
v The directory path pointed by the environmental
variable DSMSERV_DIR if this variable is defined
v The current working directory of the server process if
the DSMSERV_DIR variable is not defined
If an error is found, re-try the command with the
corrected specification. If an error cannot be found,
ANR9634E (HP-UX) command name: No license
certificate files were found with the file
name specification specification.
entered.
694

ANR9634E (Linux) command name: No license
entered.
ANR9634E (Solaris) command name: No license
entered.
ANR9634E (Windows) command name: No license
entered.
ANR9635E (HP-UX) Invalid license certificate file:
file name.
ANR9635E (Linux) ANR9637E (HP-UX)

ANR9635E (Linux) Invalid license certificate file: file
name.
ANR9635E (Solaris) Invalid license certificate file: file
name.
ANR9635E (Windows) Invalid license certificate file:
file name.
ANR9636E (HP-UX) Could not open file file name.

ANR9636E (Linux) Could not open file file name.
ANR9636E (Solaris) Could not open file file name.
ANR9636E (Windows) Could not open file file name.
ANR9637E (HP-UX) Cannot access node license lock
file: file name.
695
ANR9637E (Linux) ANR9638W (Solaris)

representative.
ANR9637E (Linux) Cannot access node license lock
file: file name.
environment variable. Re-specify the DSMSERV-DIR
representative.
ANR9637E (Solaris) Cannot access node license lock
file: file name.
environment variable. Re-specify the DSMSERV-DIR
representative.
ANR9637E (Windows) Cannot access node license
lock file: file name.
environment variable. Re-specify the DSMSER-DIR
696

representative.
ANR9638W (HP-UX) License registration is not
found.
command.
required for formal licensing for the HP-UX server. The
file is delivered when the server is purchased, but it is
not available in the product service stream or with
ANR9638W (Linux) License registration is not
found.
command.
delivered when the product is purchased, but it is not
ANR9638W (Solaris) License registration is not
found.
command.
required for formal licensing for the Solaris server. The
file is delivered when the server is purchased, but it is
not available in the product service stream or with
ANR9638W (Windows) ANR9641W (HP-UX)

ANR9638W (Windows) License registration is not
found.
ANR9640E (HP-UX) Unable to load procedure

address from shared library shared
library.
Explanation: The server module is unable to load the
address of a routine in the indicated shared library.

command.

function that requires the shared library will be
inoperative.

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
with demonstration copies of the server. If you have
User response: Ensure that the shared library is

accessible. If the problem persists, contact your service
representative.
ANR9639W (HP-UX) Unable to load shared library

shared library.
indicated shared library.
inoperative.
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"
mode with sample licensed options for a period of
time.
ANR9639W (Linux) Unable to load Shared License
File shared library.
Explanation: The server was unable to loaded the
shared library.
functions that require the shared library will be
inoperative.
ANR9640E (Linux) Unable to load procedure address

from shared library shared library license
module.
address of a routine in the indicated shared library for
license loading.
inoperative.
accessible. If the problem persists, contact your
Customer Service Representative.
ANR9640E (Solaris) Unable to load procedure
address from shared library shared library
license module.
address of a routine in the indicated shared library for
license loading.
inoperative.
accessible. If the problem persists, contact your
customer service representative.
User response: Make sure the shared library is

accessible/readable. This message is normal for those
servers in the Try-N-Buy mode.
ANR9641W (HP-UX) One or more EVALUATION

LICENSES will expire on expiration date.
ANR9639W (Solaris) Unable to load Shared License

File shared library.
Explanation: Although you are running with a

purchased version of the server, there are one or more
licenses registered that will expire on the date specified.
This is usually the case when you have been using
evaluation licenses prior to purchasing the product.
Explanation: The server was unable to loaded the

shared library.
functions that require the shared library will be
inoperative.
User response: Make sure the shared library is
accessible/readable. This message is normal for those
servers in the Try and Buy mode.

User response: Halt the server and erase the nodelock
file in the server startup directory. After restarting the
server, use the REGISTER LICENSE command to define
the licensed features that you have purchased with
your server. These licenses should NOT have an
expiration date, so this message should not appear after
697
ANR9641W (Linux) ANR9654E (Solaris)

re-registering the proper licenses. If this message
ANR9641W (Linux) One or more EVALUATION
ANR9641W (Solaris) One or more EVALUATION
ANR9653E (HP-UX) Unexpected error encountered in

operation fails
representative.
ANR9653E (Solaris) Unexpected error encountered in
operation fails
Explanation: The license authorization code which

you entered using the REGISTER LICENSE command is
invalid.

representative.
System action: No additional licenses are registered.

ANR9654E (HP-UX) Could not open file file name.
User response: Obtain a valid license authorization

code and try the command again.

ANR9642E (HP-UX) The specified license

authorization code (license authorization
code) is invalid.

ANR9642E (Linux) The specified license
authorization code (license authorization
code) is invalid.
Explanation: The license authorization code which
you entered using the REGISTER LICENSE command is
invalid.

System action: No additional licenses are registered.

ANR9654E (Solaris) Could not open file file name.
User response: Obtain a valid license authorization

code and try the command again.

698

ANR9655E (HP-UX) Invalid license certificate file:
file name.
ANR9655E (Solaris) Invalid license certificate file: file
name.
ANR9656E (HP-UX) Cannot access node license lock
file: file name.

representative.
ANR9676E (AIX) Error errno attaching memory
segment for shared memory
communications.
User response: Check the AIX documentation for the
shmat subroutine and determine what the error
number indicates. On AIX, if the error number is
EMFILE, make sure the EXTSHM environment variable
is set to ON before starting the server. This allows the
server to support more than 3 concurrent shared
memory sessions.
ANR9676E (HP-UX) Error errno attaching memory
communications.
memory sessions.

representative.
ANR9676E (Linux) Error errno attaching memory

communications.
ANR9656E (Solaris) Cannot access node license lock

file: file name.



699
ANR9677E (AIX) ANR9680W (AIX)

memory sessions.
ANR9677E (AIX) Failed to allocate memory for
error text.
not be activated.
ANR9677E (HP-UX) Failed to allocate memory for
error text.
not be activated.
ANR9678E (Linux) Failed to allocate message queue

Error: error text.
not be activated.
ANR9678W (Windows) File name used for server
executable. A server is currently running
as a service.
Explanation: The name of the executable used when
the server is running as a service cannot be used in the
plan file.
System action: PREPARE uses file name identified in
the message within the plan file and generation of the
plan file continues.
ANR9679W (AIX) Command: The file file name cannot
be found.
ANR9677E (Linux) Failed to allocate memory for

error text.
not be activated.

dsmserv.
ANR9679W (Windows) Command: Unable to locate
file file name.
ANR9678E (AIX) Failed to allocate message queue

Error: error text.
not be activated.
ANR9678E (HP-UX) Failed to allocate message queue
Error: error text.
not be activated.
System action: PREPARE uses the following default

file names in the plan file:
v For the server executable the default is
c:\progra~1\tivoli\tsm\server\dsmserv.
ANR9680W (AIX) Command: Could not obtain AIX
logical volume information for volume
name while building stanza recovery plan
stanza name.
PREPARE can not obtain AIX logical volume
information for it from the AIX Object Data Manager
(ODM).
User response: This message should be preceded by
700
ANR9680W (HP-UX) ANR9683E (AIX)

another error message which contains the ODM error
code.
ANR9680W (HP-UX) Command: Could not obtain
stanza name.
PREPARE can not obtain logical volume information
for it.
another error message which contains an error code.
ANR9680W (Solaris) Command: Could not obtain
stanza name.
ANR9681W (Windows) Command: Volume file name

not found while building stanza recovery
plan stanza name.
ANR9682E (AIX) Command: Generated file name too
long. Length of directory or prefix

PREPARE can not obtain logical volume information
for it.

specify the prefix:

v SET DRMPLANPREFIX

another error message which contains an error code.
v PREPARE
ANR9680W (Windows) Unable to locate path for

component in registry.
Explanation: The path to the component could not be
found in the registry.
System action: PREPARE uses the following default
path names in the plan file:
v For the components installation directory the default
is c:\progra~1\tivoli\tsm\server\
v For the administrative command line client the
default is c:\progra~1\tivoli\tsm\baclient\
v For the disk formatting utility the default is
c:\progra~1\tivoli\tsm\utils\
User response: Determine why path does not exist;
install components if necessary.
ANR9681W (AIX) Command: Volume file name not
plan stanza name.
User response: Determine why the file does not exist;
create it if necessary.
ANR9682E (Windows) Command: Generated file

name too long. Length of directory or
prefix 'prefix' plus 'name' exceeds
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9683E (AIX) Command: Cannot generate fully
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
701
ANR9683E (Windows) ANR9712E

ANR9683E (Windows) Command: Cannot generate
fully qualified file name for 'name'.
ANR9686E (AIX) Command: Cannot generate a device




specify the prefix:

information.
v SET DRMPLANPREFIX
ANR9686E (Windows) Command: Cannot generate a

v PREPARE

ANR9684E (AIX) Command: Cannot generate server

options file name.

options file name.
information.
ANR9684E (Windows) Command: Cannot generate
server options file name.
options file name.

information.
ANR9687W (Windows) Cannot load the Microsoft
dll NTMSAPI.DLL. Removable Media
Support will not be available.
Explanation: The Microsoft dll NTMSAPI.DLL is
required for removable media. It is usually found in the
Windows System32 directory but can be removed if the
Windows feature called Removable Media is turned off.
In Windows 2008, Removable Media is off by default.

information.
User response: Ignore this message if storing to a

drive or turn on the Removable Media feature in
Windows.
ANR9685E (AIX) Command: Cannot generate a

ANR9710E

history file name.
Explanation: There is not enough memory to operate

the label utility program.
System action: The program is halted.

information.
User response: Provide more memory for the program

to use.
ANR9685E (Windows) Command: Cannot generate a

ANR9711E

history file name.
information.
Insufficient memory to continue

operations.
Unrecognized argument 'argument'.
Explanation: The specified argument is not recognized

as one that is supported by the label utility program.
User response: Retry the label utility program with
the correct argument syntax.
ANR9712E
Argument has invalid value 'argument'.
Explanation: The value specified for the given

argument is not valid.
702
ANR9713E ANR9723I
User response: Retry the operation, specifying a valid

supported drive.
ANR9713E
ANR9719E
Only one library can be specified.
Too many drives were specified.
Explanation: Only one library can be specified in the

argument list for the label utility program.
Explanation: The number of drives specified on the

command line exceeds the limits of the program.

User response: Retry the operation, specifying only up

to the maximum number of supported drives. The
program can be invoked with the -help argument to
determine this maximum value.
ANR9714E
No drives were specified.
Explanation: At least one drive must be specified for

use by the label utility (DSMLABEL) program.
ANR9720I
Volume 'volume name' was labeled

successfully using drive 'drive name'.
Explanation: The volume is successfully labeled.

System action: The program continues operation.

ANR9715E
Error starting label activity for drive

drive name.
Explanation: The label utility is unable to start its

activity for the given drive.
User response: Increase the number of allowed
threads or processes in the system, then retry the
operation.
ANR9716E
Device 'library name' is not accessible, or

is not recognized as a supported library
type.
ANR9721E

volume name.
volume name.
User response: Enter a volume name that is within
the length constraints for the media type being labeled,
and which contains only alphanumeric characters.
ANR9722I
Explanation: The device specified for the library

cannot be accessed or is not recognized as a supported
device.
supported library.
ANR9717E
Element address element address is not

valid for drive 'drive name'.
Explanation: The specified element address does not

represent a valid drive location in the associated library.
element address for the drive.
ANR9718E
Device 'drive name' is not recognized as a

supported drive type.
Explanation: The device specified for the drive is not

recognized as a supported device.
'Volume name' is not a valid volume

name.
Insert a new volume in drive 'drive

name', then enter the name (1-maximum
length characters) to be used for its label;
or just press ENTER to quit this
program:
Explanation: The program prompts for a new volume

to be mounted in the given drive so that a label can be
written to it.
System action: The program waits for the volume
name to be entered.
User response: Mount a new volume, then type a
volume name for it and press ENTER; or, if you want
to quit the program, press ENTER without entering a
volume name.
ANR9723I
Insert side A of a new volume in drive

'drive name', then enter the name
(1-maximum length characters) to be used
for its label; or just press ENTER to quit
this program:

written to it.
703
ANR9724I ANR9732I
name to be entered.
User response: Mount side A of a new volume, then
type a volume name for it and press ENTER; or, if you
want to quit the program, press ENTER without
entering a volume name.
ANR9724I
Flip the volume in drive 'drive name' to

side B, then press ENTER.
Explanation: The program prompts for a two-sided

volume to be flipped so that its second side can be
labeled.
System action: The program waits for the ENTER key
to be pressed.
User response: Flip the volume in the drive, and press
ENTER.
ANR9725E
The volume in drive 'drive name' is

already labeled (volume name).
Explanation: The volume in the specified drive cannot

be labeled because it already contains a valid label with
the given name.
System action: The volume is not labeled.
User response: If an overwrite of the existing label
with a new label is desired, restart the DSMLABEL
utility program by using the -overwrite argument.
ANR9726E
I/O error writing label for volume

'volume name' in drive 'drive name'.
Explanation: An I/O error occurs while attempting to

write the label for the specified volume in the given
drive.
ANR9728E
Explanation: An error occurs while ejecting the

volume from the given drive.
System action: All further activity on the given drive
is suspended.
User response: Ensure that the drive is in proper
operating condition before resuming its use.
ANR9729E
Media fault detected on volume 'volume

name' in drive 'drive name'.
I/O error formatting volume 'volume

name' in drive 'drive name'.
Explanation: An I/O error occurs while attempting to

format the media for the specified volume in the given
drive.
User response: Ensure that the volume is not write
protected, that the drive is powered on and ready, and
that the media is not damaged.
ANR9730I
Manual intervention required for library

device 'library device name'.
Explanation: The specified library device requires

manual intervention before it can be accessed for
normal operations.
System action: The operation will be retried
periodically until either the required action is
performed or a timeout occurs.
User response: If the library has an access door, make
sure it is in the closed position. If it has a cartridge
carousel, make sure the carousel is installed.
ANR9731I
User response: Ensure that the volume is not write

protected, the drive is powered on and ready, and the
device parameter has the correct value.
ANR9727E
Error ejecting volume from drive 'drive

name'.
Insert a new volume into the entry/exit

port of library 'library device name', then
enter the name (1-maximum length
characters) to be used for its label; or
just press ENTER to quit this program:

to be mounted in the entry/exit port of the given
library so that a label can be written to it.
Explanation: A media fault condition is detected for

the specified volume in the given drive.

name to be entered.
User response: Insert a new volume into the

entry/exit port, then type a volume name for it and
press ENTER; or, if you want to quit the program,
press ENTER without entering a volume name.
User response: Remove the volume from use, since

the media is questionable. If the media in question
requires formatting, such as an unformatted optical
disk, retry the operation by starting the program with
the '-format' argument.
704
ANR9732I
Insert a new volume in the entry/exit

port of library 'library device name' with
side A facing up, then enter the name
this program:
ANR9733I ANR9740E
to be mounted in the entry/exit port of the given
library so that a label can be written to it.
name to be entered.
User response: Insert a new volume into the
entry/exit port, then type a volume name for it and
ANR9733I
Insert a new volume in drive 'drive name'

of library 'library device name', then enter
the name (1-maximum length characters)
to be used for its label; or just press
ENTER to quit this program:
ANR9736E

library device 'library device name'.
Explanation: An attempted I/O operation for the

given library failed.
System action: If the error is noncritical, operation
continues; otherwise, the program is halted.
powered on and ready, any access doors are closed, the
device parameter has the correct value, and then retry
the operation that was in progress when the error
occurred.
ANR9737I
Remove the volume from drive 'drive

name' in library 'library device name', then
press ENTER.

written to it.
Explanation: All activity associated with the volume

in the given drive is complete, so it should be removed.

name to be entered.
System action: The program waits until the ENTER

key is pressed.
User response: Mount a new volume, close the library

access door, and then type a volume name for it and
User response: Remove the volume from the specified

drive, then close the library access door and press
ENTER.
ANR9738I
ANR9734I
Insert side A of a new volume in drive

'drive name' of library 'library device name',
then enter the name (1-maximum length
characters) to be used for its label; or
just press ENTER to quit this program:

written to it.
name to be entered.
User response: Mount side A of a new volume, close
the library access door, and then type a volume name
for it and press ENTER; or, if you want to quit the
program, press ENTER without entering a volume
name.
Remove the volume from the entry/exit

port of library 'library device name', then
press ENTER.

in the entry/exit port is complete, so it should be
removed.
key is pressed.
entry/exit port, and press ENTER.
ANR9739I
Initializing library device 'library device

name'.
Explanation: The specified library device is being

initialized for use by the labeling utility program.
System action: The library device is prepared for use.
ANR9735I
Enter the name (1-maximum length

characters) for the next volume to label
in library 'library device name'; or just
press ENTER to quit this program:
Explanation: The program prompts for the name of

the next volume to be labeled in the given library.
name to be entered.
User response: Type the name for the next volume to
be labeled and then press ENTER; or, if you want to
quit the program, press ENTER without entering a
volume name.

ANR9740E
Volume 'volume name' is not in the

INSERT category.
Explanation: The specified volume cannot be labeled

because it is not in the librarys insert category. This
restriction is provided as a safeguard against labeling
volumes that are in use, and possibly destroying valid
data.
User response: If you are sure the volume contains no
705
ANR9741E ANR9749I
valid data, it can be removed from the library and then
reinserted with the librarys convenience I/O station.
This will cause the volumes category code to be
changed to the INSERT category, and thus allow the
labeling operation to work.
ANR9741E
Drives 'drive name' and 'drive name'

cannot use the same element address.
User response: Retry the program, specifying at most

one trace argument.
ANR9746E
Unable to open trace file 'file name'.
Explanation: An error occurs while opening the

specified file for writing trace data.
Explanation: The element addresses specified for the

given drives are the same. This is not allowed, since the
element address is the only way in which the robot can
distinguish between different drives in a VTL or SCSI
library.
User response: Retry the program, specifying a valid

file name for the trace file.
System action: The program is stopped.
Explanation: An error occurs while writing data to the

trace file.
User response: Restart the program, providing valid

and unique element addresses. Appropriate values can
be determined with the worksheets in Administrator's
Guide.
System action: The program continues, but trace data

may be lost.
ANR9742E
The element address for drive 'drive

name' is missing or invalid.
Explanation: The element address value for the

specified drive is omitted, or an illegal value has been
provided.
ANR9747I
User response: Make sure the disk that contains the

trace file is not full or defective and then retry the
operation.
ANR9748I
System action: The program is stopped.

User response: Restart the program, providing a valid
element address. Appropriate values can be determined
with the worksheets in Administrator's Guide.
ANR9743I
Attempting to label volume 'volume

name' using drive 'drive name'...
Explanation: The specified volume is in the process of

being labeled in the given drive.
System action: Labeling activity continues.
ANR9744E
Volume 'volume name' is not present in

library 'library name'.
Explanation: The specified volume is not present in

the given library, so it cannot be labeled.

name to be entered.
User response: Insert a new volume, close the library
access door, type a volume name for it, and press
ENTER; or, if you want to quit the program, press
ENTER without entering a volume name.
ANR9749I
User response: Insert the volume into the library, then

Only one trace argument is allowed.
Explanation: More than one trace argument has been

encountered, but only one is allowed.
706
Insert a new volume into slot with

element number 'slot element address' of
library 'library device name', then enter
the name (1-maximum length characters)
to be used for its label; or just press
ENTER to quit this program:

to be inserted into the given slot with the specified
element number so that a label can be written to it. For
the slot and element number diagram of your library,
refer to the documentation provided with the current
PTF level or refer to the Administrator's Guide for your
release and platform.
System action: Labeling activity continues for other

volumes.
ANR9745E
Unable to write to trace file.
Insert a new volume into slot with

element number 'slot element address' of
library 'library device name' with side A
facing up, then enter the name
this program:

to be inserted into the slot with the specified element
number so that a label can be written to it. For the slot
and element number diagram of your library, refer to
the documentation provided with the current PTF level
or refer to the Installing the Server and Administrative
Client manual for your release and platform.
ANR9750I ANR9758W
name to be entered.
User response: Insert side A of a new volume, close
the library access door, type a volume name for it, and
ANR9750I
Remove the volume from slot with

element number 'slot element address' in
library 'library device name', then press
ENTER.

in the given slot with the specified element number is
complete, so it should be removed. For the slot and
element number diagram of your library, refer to the
documentation provided with the current PTF level or
refer to the Administrator's Guide for your release and
platform.
key is pressed.
User response: Remove the volume from the specified
slot, close the library access door, and press ENTER.
ANR9754I
Explanation: A barcode is encountered that was

longer than a valid volume name.
System action: The barcode is not considered valid
and will not be used for the server process.
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.
ANR9755E
The volume in drive 'drive name' is not

compatible with the drive.
Explanation: The volume cannot be used in the drive.

It is most likely an outdated media type that the drive
cannot write.
User response: Remove the volume; replace it with a
different type known to work in the drive, or press
ENTER to end the program.
System action: The program terminates without

attempting to label any cartridges.
User response: Make sure the hardware supports
barcodes, or that barcode labels have been affixed to
the cartridges.
Could not access drive 'drive name'. It

may be in use by another application.
Explanation: The specified drive cannot be accessed.
System action: The program terminates normally.

User response: Insert cartridges into the library. For a
349x ATL, this may involve changing the category of
previously inserted cartridges to be relabeled.
ACS drive id ACS drive id is not valid
for drive 'drive name'.
Explanation: The specified ACS drive id does not

represent a valid drive location in the associated library.

User response: Ensure that the drive name is correct
and the device is not in use by another application,
then retry the operation.

drive id for the drive.
ANR9758W
ANR9753E
No volumes were found.
Explanation: No volumes are found in the library.

This means that in a 349x ATL, no volumes were found
in the insert category (xFF00), and that in a SCSI
autochanger, no cartridges were loaded into the library.
ANR9757E
ANR9752E
There are no barcodes available.
Explanation: The hardware did not return any valid

barcode data for any cartridge.
ANR9756I
ANR9751E
Barcode of element slot element address,

'hardware barcode string', exceeds maximum
length characters in length.
Skipping slot element address 'slot

element address', which has no barcode.
Explanation: The cartridge in the indicated slot will

not be labeled, since it does not have a valid barcode.
System action: The program attempts to label the next
cartridge.
User response: Examine the cartridge to see if it has a
barcode. Add a barcode if required.
Error mounting volume 'volume name'.
Explanation: An error occurs while mounting the

volume to the drive. This may not be an error since the
volume or drive maybe in use or locked in a shared
environment.
System action: The specified volume is bypassed for
labeling.
User response: Ensure that the volume is not locked
or in use if label is required.
707
ANR9759E ANR9776I
ANR9759E
unsuccessful ACSAPI response,

status=acs status.
Explanation: The ACSLS library API responded with

an unsuccessful status as indicated.
System action: Depends on the ACS API for labeling,
the process may continue as the error may not be a
problem.
User response: If the label process terminates, contact
your ACS System Administrator and perform ACSLS
library problem determination.
ANR9760I
Wait and monitor the ACSSA console

message to remove volume volume id
from CAP.
Explanation: The specified volume is about to put into

CAP for removal. Monitor the ACSSA console and
removed the volume after it has been placed into the
CAP as indicated in the ACSSA message.
User response: Monitor the ACSSA console and wait.
ANR9761E
The path of drive drive name in library

library name has been changed from
original drive path to new drive path The
new path will not be updated because
we can not get the model type using
new path.
Explanation: The drive's new path can not be updated

because we detect a different device type compared to
the Database using this new path. The problem may be
the new path has an incorrect format for the device
driver.
System action: .
User response: The user needs to check if there are
two device special file names for the same drive. For
AIX, please make sure the IBM drive is /dev/rmt and
TSM drive is /dev/mt. For Solaris, please make sure
the Solaris native device driver is not installed.
ANR9771E
Volume volume name has an incorrect

barcode label describing the volume's
WORM type.
Explanation: In an attempt to CHECKIN or LABEL a

volume it was discovered that the volume's true
WORM characteristic didn't match that described by its
barcode label.
System action: The volume is not checked in.
User response: The volume was probably mislabeled.
Find the volume in the library. Simply remove the
volume, or swap the barcode label with a label of the
opposite WORM characteristic (WORM for non-WORM
or vice versa) and retry the check in command.
708
ANR9773E
Hardware configuration error in library

library name: number of drives drives,
number of storage slots storage slots.
Explanation: The library device returned a count of

zero for either the drives or the slots. The drives may
have not yet been configured to the operating system,
or to the library. The library must have at least one
drive and multiple slots when properly configured in
order to be defined to the server.
User response: Configure the drives to the operating
system, and reinitialize the library.
ANR9774W
Volume volume name should be freed of

data as soon as possible.
Explanation: The server has received an indication

from the 3995 that the indicated volume is out of spare
sectors for re-allocation. Spare sectors are reserved to
take the place of sectors that experience I/O problems.
The re-allocation can take place on either a read or
write.
System action: The indicated volume is marked
read-only by the server.
User response: A MOVE DATA command should be
used as soon as possible to move the data from this
cartridge to other cartridges in the library. This
cartridge should NOT be marked read-write again
through the UPDATE VOLUME command.
ANR9775E
Error while writing on volume volume

name (RC=internal code).
Explanation: An I/O error has occurred while writing

on the specified volume.
User response: Ensure that the 3995 volume is
accessible and that the media is usable. Diagnostics
may have to be run on the 3995 with the specified
volume. If the problem persists, contact your service
representative and provide the internal code values
from this message. The internal code is returned to the
server from the OS/2 operating system.
ANR9776I
File file name is being erased and

deleted. Data erasure may take several
minutes.
Explanation: A file is being deleted from an optical

library cartridge. The file is deleted when a LAN3995
device class volume is deleted. File deletion includes
erasure of data. The erasure process can take several
minutes to complete.
ANR9778E ANR9786E
ANR9778E
Unable to establish a communication

session with the primary library
manager.
Explanation: The requested operation required that a

communication session be established with a library
manager. The library manager was found to be
unavailable at this time.
User response: Verify the primary library manager is
up and operational. Once the server is verified to be
operational, retry the operation.
ANR9779E
Unable to acquire a drive for volume

volume name from the library manager.
Explanation: The library manager was unable to

assign a drive to the library client. There are a couple
of situations that can cause this error.
v All drives are currently allocated to other library
clients or the library manager.
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.
v A communication error occurred during the request
to mount a volume.
v The requested volume was not present in the library
manager's inventory
User response: Verify that a drive is available on the
library manager side and the drive is currently not
busy or marked offline on the library client. Set the
mount retention on the device class on the library
manager and the library clients to a lower value. Using
a lower mount retention value can free up drives.
ANR9780E
Volume volume name is not mounted in

drive from the library drive name.
Explanation: A communication error occurred while

dismount the volume.
User response: Verify that the volume has been

dismounted.
ANR9782E
Primary Library Manager primary library

manager name is NOT defined as a
server.
Explanation: The primary library manager server has

not be defined to this server.
User response: Define the server to this server using
the DEFINE SERVER command.
ANR9783E
Primary Library Manager does not

contain a valid value.
Explanation: The primary library manager server has

not be defined to this server.
ANR9784E
Secondary Library Manager secondary

library manager name is NOT defined as a
server.
Explanation: The secondary library manager server

name has not be defined to this server.
ANR9785E
Drive drive name, is not defined on the

library manager.
Explanation: A drive is being defined that does not

exist or is being managed by the library manager.
User response: Verify drive name with the library
manager.
ANR9786E
User response: Verify the library manager is up and

operational. Verify that the library manager and library
client can communicate using command routing.
Explanation: A communication error occurred.
ANR9781E
Volser volume name was not found to be

mounted on the library manager.
Explanation: According to the library manager the

requested volume is no longer mounted. The can
occurred if the library manager forced the volume to be
dismounted because of a communication error.
A communication error has occurred.

Operation ending.

User response: Verify the library manager is up and
operational. Verify that the library manager and library
client can communicate using command routing.
709
ANR9787E ANR9796E
ANR9787E
The owner name specified is not

defined to this server.
Explanation: A command was issued specifying

ownership of a volume. The name of the owner given
was not defined to this server.
ANR9788E

defined - the primary library manager
not defined.
Explanation: The designated library is not defined

because the primary library manager is not defined as a
server to this server.
ANR9789E

defined - the secondary library manager
not defined.
Explanation: The designated library is not defined

because the secondary library manager is not defined
as a server to this server.
ANR9790W
Request to mount volume Volume Name

for library client Library Client Name
failed.
Explanation: A library client requested a volume to be

mount by the library manager, which in turn failed.
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
needed.
ANR9791I
Volume Volume Name in library Library

Name ownership is changing from
Current volume owner to New Volume
owner.
Explanation: In a shared library, the volume

ownership has been changed from current owner to
new owner.
710
ANR9792E
Library Library Name on library manager

Library Manager Name is currently not
being shared.
Explanation: A define library command attempted to

define a shared library that was not being shared by
the library manager.
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.
ANR9793I
process name in library library nameCANCEL PENDING.

process on the server. The command was started, but
the process was canceled by an administrator.
being terminated.
ANR9794E
Unable to load the RSM dynamic link

library dynamic link library.

indicated dynamic link library.
function that requires the dynamic link library will be
inoperative.
User response: Ensure that the installed Windows
version supports RSM. Ensure that the Removable
Storage Manager is installed and the system DLL is
accessible.
ANR9795E
Command: Invalid storage agent name

storage agent name.
Explanation: The designated storage agent name is

invalid; either it contains too many characters, or some
of the characters are invalid.
storage agent name.
ANR9796E
Command: Drive mapping is already

defined for drive drive name in library
library name on storage agent storage agent
name.
Explanation: The designated drive mapping cannot be

defined because it has already been defined for the
specified drive, library, and storage agent.
ANR9797E ANR9900W (HP-UX)

drive mapping, reissue the command with a different
drive name.
ANR9797E
Command: Drive mapping for drive drive

name is not defined in library library
name on storage agent storage agent name.
Explanation: The designated drive map has not been

defined for the given drive in the given library on the
given storage agent.
drive name. If appropriate, define the drive before
retrying the command.
ANR9798E
Command: One or more paths are still

defined for drive drive name in library
library name.

because there are still paths defined for it.
User response: Delete all paths for the drive, and
ANR9799E
Command: Library Library Name is

currently not being shared.
Explanation: The command attempted to perform an

operation that is not allowed unless the library is
allowed to be shared.

ANR9803W (Windows) ANR9803: ERROR!
Insufficient free memory to initialize
driver.
Explanation: The server device driver is unable to
initialize due to an inability to acquire dynamic storage.
System action: Processing continues. The device
driver is not available to process requests from the
server.
User response: For minimum storage requirements,
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.
ANR9810I (Windows) ANR9810: SCSI Tape Device
Driver Initializing...
Explanation: The server SCSI tape device driver has
been invoked by the system and is initializing.
ANR9820I (Windows) ANR9820: SCSI Autochanger
Device Driver Initializing...
Explanation: The server SCSI automatic changer
device driver has been invoked by the system and is
initializing.

shared, update the library shared parameter to yes.
ANR9800E
Library Library Name is currently not

being shared and attempted an
operation only allowed for shared
libraries.
Explanation: The command attempted to perform an

operation that is not allowed unless the library is
allowed to be shared.
shared, update the library shared parameter to yes.

ANR9900W (AIX) Attention -- Accounting records
could not be written to the file: filespec.
Explanation: The server detects an error while trying
to open the accounting file.
User response: Ensure that there is sufficient disk
space and that the accounting file is not marked as
read-only.
ANR9900W (HP-UX) Attention -- Accounting records
could not be written to the file: file name.
ANR9801I (Windows) ANR9801: Ready for

operations.
System action: Server processing continues, but no

accounting records are written.
Explanation: The device driver has successfully

initialized and is ready to accept requests from the
server.

read-only.
711
ANR9900W (Linux) ANR9902W (HP-UX)

ANR9900W (Linux) Attention -- Accounting records



to write an accounting record.


read-only.
ANR9900W (Solaris) Attention -- Accounting records
read-only.
ANR9900W (Windows) Attention -- Accounting
records could not be written to the file:
filespec.
read-only.
read-only.
read-only.
712

read-only.
read-only.
filespec.
read-only.
to close the accounting file.
User response: Ensure that sufficient disk space is
available and that the accounting file is not marked as
read-only.
read-only.

ANR9904W (HP-UX) Create thread failed. Try the

operation again later.

Explanation: The server is unable to create a new

thread due to resource constraints.

read-only.
User response: Try the operation again later.

read-only.
filespec.
read-only.
ANR9903W (HP-UX) Create thread failed. Your
system is configured for a maximum of
thread count threads. Consider
configuring a maximum of 1024 threads.
Explanation: The server is unable to create a new
thread.
User response: Consider increasing the maximum
thread count on the system.
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.
User response: Ensure to login as root for TSM tape
failver function to open HBA.
ANR9905W (AIX) Unable to open file file. Error

message generated by AIX
indicated file.
indicated file fails.
owner.
ANR9905W (HP-UX) Unable to open file file. Error
message generated by HP-UX.
indicated file.
owner.
ANR9905W (Linux) Unable to open file file. Error
message generated by Linux.
indicated file.
owner.
ANR9905W (Solaris) Unable to open file file. Error
message generated by Solaris.
indicated file.
713

owner.
ANR9905W (Windows) Unable to open file file. Error
message generated by Windows.
ANR9953E (Windows) Command: Invalid value

specified for number of licensed clients
- value.
User response: Issue the command using a valid
value.

indicated file.
ANR9955W (Windows) Unable to load dynamic link

library dynamic link library.


indicated dynamic link library.

owner.

inoperative.
ANR9950W (Windows) Attention -- License option

to write to the options file.
space and that the options file is not marked as
read-only.
ANR9951W (Windows) Attention -- License option
to close the options file.
space and that the options file is not marked as
read-only.
ANR9952E (Windows) Command: Invalid value
specified for licensed storage capacity value.
User response: Issue the command using a valid
value.
714
User response: Ensure that the dynamic link library

directories are accessible. If this is an evaluation copy
of the server, then this message is normal for the
DSMREG library, since the library is only provided
with purchased Windows servers. The server licensing
will assume "Try and Buy" mode with sample licensed
options for a period of time.
ANR9956E (Windows) Unable to load procedure
address from dynamic link library
dynamic link library.
address of a routine in the indicated dynamic link
library.
inoperative.
User response: Ensure that the dynamic link library
directories are accessible. If the problem persists,
contact you service representative.
ANR9957W (Windows) One or more EVALUATION
Explanation: Although you are running with a
purchased version of the server, there are one or more
licenses registered that will expire on the date specified.
This i usually the case when you have been using
evaluation licenses prior to purchasing the server for
Windows.
your Windows server. These licenses should NOT have
ANR9958W (Windows) ANR9966I (Windows)

an expiration date, so this message should not appear
after re-registering the proper licenses. If this message
ANR9958W (Windows) Node entry node name was
removed from this server's definition in
Active Directory.
removed from this server's definition in Active
Directory.
not removed from this server's
definition in Active Directory.
command, the requested backup-archive node has not
been removed from this server's definition in Active
Directory.
User response: To remove a node entry in the Active
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
Configuration wizard can be used to manually update
the server definition.

renamed in this server's definition in
Active Directory.
renamed to the new name shown.
not renamed in this server's definition
in Active Directory.
command, the requested backup-archive node has not
been renamed.
User response: To Rename Node in the Active
Directory, the options "adregister" and "adunregister"
have to be set to "yes" in the server options file. A
domain controller must also be available. The Active
Directory Configuration wizard can be used to
manually update the server definition.
ANR9964W (Windows) Failed to access Active
Directory. RC: return code
Explanation: Could not communicate with an Active
Directory server.
ANR9960W (Windows) Node entry node name has

been added to this server's definition in
Active Directory.
Explanation: The requested backup-archive node entry
has been added to this server's definition in Active
Directory in response to a REGISTER NODE command.
ANR9961W (Windows) Node entry node name has not
been added to this server's definition in
Active Directory.
Explanation: The requested backup-archive node entry
has not been added to this server's definition in Active
Directory in response to a REGISTER NODE command.
User response: To register a node entry in the Active
Directory, the option "adregister" has to be set to "yes"
in the server options file. A domain controller must also
be available. The Active Directory Configuration wizard
can be used to manually update the server definition.
User response: Try using the option "adsetdc" in the

server options file to explicitly provide the TCP/IP
address of the domain controller where Active
Directory is located.
ANR9965W (Windows) Could not create the inital
node list in Active Directory for this
server.
Explanation: At startup the server's registered nodes
could not be added to the server definition in Active
Directory
User response: Try using the option "adsetdc" in the
server options file to explicitly provide the TCP/IP
address of the domain controller where Active
Directory is located.
ANR9966I (Windows) NodeName node name.
Explanation: The NodeName is registered in Active
Directory.
715
ANR9967I (Windows) ANR3614E

ANR9967I (Windows) Server server name was defined
in Active Directory.
Explanation: The server is registered in Active
Directory.
ANR9968I (Windows) Success accessing Active
Directory.
Explanation: Active Directory Server could be
contacted.
System action:
ANR9969E (Windows) Unable to open volume
volume name. The most likely reason is
that another TSM server is running and
has the volume allocated.
Explanation: Only one TSM server can have a given
volume open at a time.
User response: See if another TSM server is already

running and if so use it.
ANR9999D
(component)(code):(text)
Explanation: The diagnostic text of this message is

related to a server process or algorithm. The
information is intended for reporting processing
exceptions and other non-standard situations that occur
on the server. The (component), (code), and (text) vary,
and server processing may continue, depending upon
the cause of the message and the server process or
algorithm issuing the message.
System action: Issue the SET CONTEXTMESSAGING
command and set the message context reporting to ON.
This allows you to receive additional information when
the server produces its message. See the Administrators
Reference for more information.
User response: Examine any error messages that were
displayed before or after this message and correct any
problems, if possible. If you cannot determine or
resolve the cause of this message, contact your support
representative. Report the entire text of this message
when contacting your support representative.
System action: The TSM server does not start.
Version 6.3.1 ANR new and changed messages

ANR1889W
Session session number was terminated

during backup for node node name (client
platform), with file space filespace id or
name because a restore operation is in
progress.
Explanation: During a file backup operation, the

server ends a node session because one or more files
are locked by a restore operation.
System action: The backup session is terminated by
the server.
User response: Issue the QUERY RESTORE command
with FORMAT=DETAILED to determine if the restore
operation is active or is in a restartable state. A
restartable restore operation keeps files locked until the
amount of time that is specified for the
RESTOREINTERVAL server option is reached. You can
lower this value to free up locked files. Issue the
QUERY OPTION command to display the current
setting for the RESTOREINTERVAL option.
If you received this message due to a client backup
operation, restart the operation after the restore
operation has completed in order to move any
remaining files. You can also cancel the restartable
restore session with the CANCEL RESTORE command.
716
ANR1936E
Replication of data type data for file

space file space name (fsId file space ID) on
node node name failed with reason: reason
Explanation: The server could not replicate the

specified file space for the reason indicated in the
message text.
System action: The command continues, but
replication of the file space fails.
User response: Review the reason for the failure and
correct the problem, if possible. Then rerun the
REPLICATE NODE command.
ANR3614E
The server failed to connect to the

database.
Explanation: The server was unable to establish or

validate a connection to the database.
System action: The server will shutdown.
User response: Examine the messages that were
issued before this message to determine the cause of
the failure. Start the server after the issue has been
resolved.
ANR3615E ANR3617E
ANR3615E
The value of the DATAFORMAT

parameter for the datamover is not
compatible with the NAS file server.
Explanation: The datamover was defined with the

NDMPDump DATAFORMAT. This data format is not
compatible with an EMC NAS file server.
System action: The NDMP operation fails.
User response: Update the datamover to use the
CELERRADump dataformat.
ANR4537I
The active log space used is used space

available is available space megabytes.
The ratio, ratio, exceeds the threshold log
utilization threshold.

the log utilization threshold, the active log space must
be increased.
caused the error. Review the messages logged by this

session to determine alternate causes.
ANR8311E
Explanation: An I/O error occurs while performing

the operation on the specified drive.
For more information on I/O error codes, search on
I/O error code descriptions for server messages in the
Tivoli Storage Manager Information Center.
ANR8526W
User response: Increase the size of the active log

space. For more information, search the Tivoli Storage
Manager Information Center on increasing the size of
the active log.
ANR4867I

name (client platform) terminated - session
retry failed.
Explanation: The specified client session is ended by

the server because a previous error has been detected
on the server. Retry attempts were not able to resume
the session.
System action: The session is ended and server
User response: If the session is a proxied LAN-Free
session for a storage agent, this error might be the
result of a mount point or volume preemption on the
storage agent. Review the messages logged by the
storage agent to determine if a storage agent action

drive drive name for low-level operation
operation, errno = drive errno, rc = return
code.
The IBM Tape Device Driver settings

have been updated and need to be
restarted. The device driver can be
restarted by either restarting windows
or reinstalling the IBM Tape Device
Driver
Explanation: The IBM Tape Device Driver settings

have been changed to not automatically reserve the
drive. By allowing TSM to manage the reservations this
will elminate some reservation warnings and potential
mount failures. This is a one time change that requires
the device driver to be re-initalized. Reinitalizing the
device driver can be accomplished by either restarting
windows or reinstalling the IBM Tape Device Driver.
Restarting windows is simpler; reinstalling the IBM
Tape Device Driver is less disruptive.
System action: Possible reservation conflicts between
hosts.
User response: Restart windows or reinstall the IBM
Tape Device Driver to cause the IBM Device Driver to
detect the registry change.

ANR3616E
An error occurred. More information

might be available in the dsmserv.err
file.
The dsmserv.err file is located in the server working

directory. Correct any problems that are identified.
ANR3617E
Explanation: None.
User response: Review the dsmserv.err file for
messages that occurred at the same time as the error.
The server failed to start with return

code rc because of an issue with the
database environment handle.
Explanation: The server was unable to allocate a

handle to the database environment.
717
ANR8195I (HP-UX) ANR8990E

User response: The error might be caused by a
mismatch between the /etc/hosts file and the
~/sqllib/db2nodes.cfg file. If the host name was
recently updated, ensure that the systems hostname in
/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 for more information.
For information about the db2nodes.cfg file, see the
DB2 documentation.
port port number.
port number.
port port number.
port number.
port port number.
port number.
ANR8196I (HP-UX) The SSL TCP/IP administrative
ANR8196I (Linux) The SSL TCP/IP administrative

ANR8196I (Solaris) The SSL TCP/IP administrative
ANR8942E
Could not move volume volume name

from slot-element element-address to
slot-element element-address.
Explanation: Could Not move volume from slot to

slot.
System action: Move volume operation failed.
User response: This message indicates a hardware
failure. For assistance, contact IBM hardware support. If
the volume was physically removed from the library,
you can re-insert the volume into the drive after it is
fixed or replaced and issue the AUDIT LIBRARY
command. This command restores the library volume
inventory to a consistent state with the volumes that
physically reside in the library. If the volume was not
removed from the library, no further action is necessary.
ANR8990E
Device device name is not supported by

Explanation: The device product identification is not

recognized by the Tivoli Storage Manager server.
User response: Determine if the installed level of the
server supports the device by visiting the Tivoli Storage
Manager Supported Devices documents.
For devices supported on AIX, HP-UX, Solaris, and
Windows, see the Tivoli Storage Manager Supported
Devices for AIX, HP-UX, Solaris, and Windows
document at http://www.ibm.com/software/
sysmgmt/products/support/
html.
For devices supported on Linux, see the Tivoli Storage
Manager Supported Devices for Linux document at
718
ANR9004E ANR1881E
support/IBM_TSM_Supported_Devices_for_Linux.html
.
If the device is a tape drive and is not supported, you
can use it with the generic tape format. To use the
drive, specify GENERICTAPE=Yes when defining a
path to the drive. If the device is supported and this
message is received, search the Tivoli Storage Manager
Support Web site for known solutions:
support/IBMTivoliStorageManager.html
If no solution is found, report the issue to Tivoli
ANR9004E
The server has detected that drive name

can also be accessed by other
applications through the st device
special file device name. All st device
special files for this drive must be
deleted.
Explanation: When more than one device driver can

access a drive, tape labels or other data can be
overwritten. To prevent possible data integrity issues,
you must delete all st device special files for this tape
drive.
System action: The operation fails or the drive is
temporarily taken offline and is not available for tape
operations. The server polls the drive at thirty second
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
root user to locate and delete the st device special files.
Then, retry the operation. For more information about
this issue, see the Administrator's Guide in the
Information Center.

for version 6.3.3.
Version 6.3.3 ANR new messages

The following Tivoli Storage Manager server ANR messages are new for version
6.3.3. All elements of the message are documented, including message ID, message
text, explanation, system action, and user response. The messages are listed in
ascending numerical order.
ANR0361I
Recovery is in progress following a

database failure.
Explanation: During server initialization, the database

manager indicated that the database requires failure
recovery. A database failure can occur in the event of a
power outage or other abnormal termination of the
database manager. Failure recovery can take extensive
time, depending on how many transactions in the log
require examination.
System action: The server initialization is delayed
while the database is recovered.
System action: The server will continue to operate;

however, until the lock conflict is resolved, no new
reorganizations will be started.
User response: Review the server activity log and
determine whether a critical server operation was
canceled that should be restarted. If so, restart the
server operation.
ANR1881E

ANR1880W
multiple times as server processes are forced to stop. In

addition, other server application error messages might
be displayed as the lock conflicts are resolved.
Server transaction was canceled because

of a conflicting lock on table table name.

referenced table could not be completed because of a
lock conflict between the reorganization process and a
server process. The server process was canceled to
allow the reorganization process to be completed. In
some cases, the server might need to cancel multiple
server processes to resolve the lock conflict.
Consequently, this message might be displayed
Command or operation: Failure because the

LDAPUSER password is expired.
Explanation: The password credentials for the user

account specified as the LDAPUSER are expired and
need to be updated.
User response: The administrator for the LDAP
directory server must update the password for the
LDAPUSER account in the LDAP directory server.
Then, after the LDAP administrator updates the
password, issue the LDAPPASSWORD command to
719
ANR1882E ANR1887E
match the new password. Reissue the command that
failed.
ANR1882E
Command or operation: A password was

reset and must change while accessing
the LDAP administrator or node entry
admin or node name with administrator/node
name or LDAPUSER credentials.
Explanation: The password credentials used for this

operation were reset and you must update the
password on the LDAP directory server.
System action: The operation requires a password
update.
User response: If the operation used the LDAPUSER
credentials, update the password for the user account
specified as the LDAPUSER in the LDAP directory
server. If the operation used node or administrator
credentials, a password expiration status is issued to
force a password update.
ANR1883E
Command or operation: An access failure

occurred while accessing the LDAP
administrator or node entry admin or node
name with administrator/node name or
LDAPUSER credentials.
Explanation: The command failed after the Tivoli

Storage Manager server accessed an entry in the LDAP
directory server and received a locked account error.
User response: If the operation used the LDAPUSER
credentials, unlock the user account specified as the
LDAPUSER in the LDAP directory server. If the
operation used a node or administrator credentials,
unlock the node or administrator by issuing the
UPDATE NODE or UPDATE ADMIN command with a
password or directly unlock the node or administrator
account in the LDAP directory server.
ANR1884E
Command or operation: An authentication

failure occurred with the LDAP
directory server when the LDAPUSER
credentials were used.
Explanation: The Tivoli Storage Manager server tried

to authenticate and access was denied.
User response: Validate that the LDAPUSER, the
LDAPPASSWORD, and the LDAPURL are set to the
correct values. Correct any invalid setting and reissue
the command or operation.
ANR1885E
Command or operation: Permission was

denied when the LDAP administrator or
node entry admin or node name was
accessed as administrator/node name or
LDAPUSER.
Explanation: The command failed after the Tivoli

Storage Manager server authenticated with the LDAP
directory server as the LDAPUSER. Permission was
denied when the server tried to add, modify or delete
an entry in the LDAP directory server.
User response: The user specified by the LDAPUSER
needs full access control over the distinguished name
(DN) specified in the LDAPURL server option. Correct
the access control rights of the LDAPUSER or provide a
different LDAPUSER who has full access control rights
over the Tivoli Storage Manager server's DN.
ANR1886E
Entry entry name was not found in the

LDAP directory server.
Explanation: The command failed because the Tivoli

Storage Manager server tried an operation on an LDAP
entry that was not found on the LDAP directory server.
User response: The Tivoli Storage Manager server
tried an operation with the LDAP directory server and
the operation failed because the entry could not be
found. To insert a new entry for this node or
administrator, issue an UPDATE NODE or UPDATE
ADMIN command and provide a password.
ANR1887E
Command or operation: Failure when

working with the LDAP directory
server.
Explanation: The command or operation failed

because of an error returned by the LDAP directory
sterver.
User response: The Tivoli Storage Manager server ran
an operation with the LDAP directory server and the
operation failed. Specific error details are contained in
previous messages. The common causes of LDAP
failures are as follows:
v A communication error occurred with the LDAP
directory server
v The LDAPURL is invalid or missing (wrong
hostname or base DN)
v The LDAPUSER is invalid or missing (wrong value
or locked)
v The LDAPPASSWORD is invalid or missing (wrong
value or expired)
720
ANR1888W ANR1932I
Update the LDAP directory server settings or contact
your LDAP administrator to resolve this issue.
ANR1888W

name (client platform) refused - client
requires SSL connection with this
server.
Explanation: No SSL connection was established,

therefore the server did not start a client session
because the client node or admin requires an SSL
connection.
User response: Configure the client to use SSL or
update the node or admin definition on the server such
that SSL is not required (update SSLREQUIRED
parameter). If the node is created with
SSLREQUIRED=SERVERONLY, a corresponding admin
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
ADMIN command.
ANR1895W
Command or operation: The password for

the node node name now uses
case-sensitive passwords.
Explanation: The node is authenticating with an

LDAP directory server. The LDAP authentication
password policy is dictated by the LDAP directory
server and this usually requires passwords to be
case-sensitive.
ANR1896E
Unable to allocate volume volume name

because it is still referenced in the
volume history.
Explanation: The volume cannot be allocated because

the active volume history record shows the volume as
being in use.
System action: The active volume history record
shows the volume as being in use.
User response: The volume is being managed by the
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
status, issue the QUERY VOLHISTORY command. If
there is an invalid volume history record, use the
DELETE VOLHISTORY command to remove the
record. If the DELETE VOLHISTORY command fails,
contact IBM Software Support to remove the record.
ANR1897I
LDAP password removed.

authenticate with the LDAP server was removed by the
SET LDAPPASSWORD command.
ANR1898I
LDAP user name removed.
Explanation: The LDAP user distinguished name

(DN) that the server uses to authenticate with the
LDAP server was removed by the SET LDAPUSER
command.
ANR1899W
Command or operation: Unable to work

with the LDAP directory server.
Explanation: The command or operation finished, but

the Tivoli Storage Manager server did not work with
the LDAP directory server because the LDAP directory
server configuration is incomplete. If a node or
administrator was being created or updated on the
LDAP server, you cannot use it to logon until the
server is able to use LDAP directory server
information.
System action: The operation finished, but
information was not added to the LDAP directory
server.
User response: An operation was run on the Tivoli
Storage Manager server with the LDAP directory
server. The operation succeeded, but information was
not added to the LDAP directory server because the
LDAP directory server configuration is incomplete.
Common incomplete configuration scenarios are as
follows:
v LDAPURL values were not provided in the server
options file
v The LDAPUSER is invalid (wrong value or locked)
v The LDAPPASSWORD is invalid (wrong value or
expired)
Update the LDAP directory server information or
contact your LDAP administrator to resolve this issue.
After completing the LDAP configuration, when you
add a node or admin with LDAP authentication, you
are required to submit a new password when you log
on to the Tivoli Storage Manager server.
ANR1932I
command: A NAS backup image for node

node name, file space filespace name was
skipped for replication.
Explanation: The replication process has determined

that a NAS backup image is not eligible for replication
721
ANR1956W ANR2733W
because the image, or one of its dependent files is
stored in a non-native storage pool.
communication with the LDAP server specified in the

LDAPURL option.
System action: Replication processing continues.

ANR1956W
The BF_AGGREGATED_BITFILES table

has a clustered index, which might
cause unexpected database growth.
Explanation: At server startup, a clustered index was

detected on the BF_AGGREGATED_BITFILES table. In
certain scenarios, this might cause unexpected database
growth.
ANR2730I
Default authentication set to defaultAuth.

the Set DEFAULTAUTHentication command. It
indicates the current default AUTHENTICATION value
for the REGISTER NODE and REGISTER ADMIN
commands.

This message is issued only once, when the server
starts.
ANR2731E
User response: For additional details and instructions

to resolve the issue, see the description of APAR
IC82886 at http://www.ibm.com/support/entry/
portal/. Type IC82886 in the Search field.
Explanation: The specified server command was

issued prior to another required command.
ANR1957W
Command or operation: The password for

the administrator administrator name now
uses case-sensitive passwords.
Explanation: The administrator is authenticating with

an LDAP directory server. The LDAP authentication
password policy is dictated by the LDAP directory
server and this usually requires passwords to be
case-sensitive.
ANR1958I

is already registered and locked.
Explanation: An import process is trying to import an

administrator ID that is already registered and locked
on the server.
System action: The process will continue without
importing the ID.
application.
ANR2594I
LDAP user name set to LDAP user name.
Explanation: The LDAP user distinguished name that

the server uses to authenticate with the LDAP server
has been set to the value indicated with the SET
LDAPUSER command.
User response: The SET LDAPPASSWORD command
is required to provide the password that correlates to
the LDAPUSER just set. This is required for
722
An invalid command was issued: issued

command. The command prerequisite
command must be issued first.

User response: Issue the required command and then
reissue the command that caused the error.
ANR2732E
Unable to communicate with the

external LDAP directory server.
Explanation: The server tried to communicate with

the external LDAP directory server but was unable to
do so.
User response: Validate that the external LDAP
directory server is actively running. Also, validate that
the LDAPURL option is set appropriately and refers to
a valid LDAP directory server.
ANR2733W
Unable to authenticate with the external

LDAP directory server to process the
SET LDAPUSER command.
Explanation: The LDAPUSER value or the

LDAPPASSWORD value or both are invalid.
System action: The server command continues.
User response: During the SET LDAPUSER command,
the Tivoli Storage Manager server tried to authenticate
to the external LDAP directory server. If the
LDAPPASSWORD is not set or is invalid, the
authentication fails, but the SET LDAPUSER command
succeeds. The LDAPUSER value and the
LDAPPASSWORD value both must be set correctly
before the server can communicate with the external
LDAP directory server. The SET LDAPPASSWORD
command fails if authentication with the external
LDAP directory server fails with the current
LDAPUSER and new LDAPPASSWORD.
You can validate the current LDAPUSER by issuing the
QUERY STATUS command. The LDAPUSER and
ANR2734E ANR2745I
LDAPPASSWORD commands can be corrected with the
appropriate SET commands. If there is still an
authentication error, validate that the user and
password are set correctly in the external LDAP
directory server.
ANR2737E
Command: All of the admins provided

are invalid.

specified command, no valid admin was found.
ANR2734E
Unable to authenticate with the external

LDAP directory server to process the
SET LDAPPASSWORD command.

LDAPPASSWORD value or both are invalid.
User response: Verify that the admins specified are

command.
ANR2738W
System action: The server command fails.

User response: You can validate the current
LDAPUSER by issuing the QUERY STATUS command.
The LDAPUSER and LDAPPASSWORD commands can
be corrected with the appropriate SET commands. If
there is still an authentication error, validate that the
user and password are set correctly in the external
LDAP directory server.
ANR2735W
Renamed node node name must be

updated with the current password.

command to a node that uses LDAP authentication, the
node was renamed in the Tivoli Storage Manager
database, but an LDAP entry does not exist for the new
name in the LDAP directory server. This can happen
because the SYNCLDAPDELETE=NO parameter was
used or an LDAP entry did not exist for the original
name.
User response: Issue the UPDATE NODE command to
the renamed node using the current password, before
attempting any sessions with the node.
Explanation: Conflicting parameters were specified in

the command.
System action: The server bypasses the conflicting
parameter and processing continues.
User response: Verify which parameter you want to
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.
ANR2739I
Renamed administrator admin name must

be updated with the current password.
Explanation: In response to a RENAME ADMIN

command with an admin that uses LDAP
authentication, the admin was renamed in the Tivoli
Storage Manager database, but an LDAP entry does not
exist for the new name in the LDAP directory server.
This can happen because the SYNCLDAPDELETE=NO
parameter was used or an LDAP entry did not exist for
the original name.
User response: Issue the UPDATE ADMIN command
to the renamed admin using the current password,
before attempting any sessions with the admin.
Audit LDAP directory started as process

process ID.

audit the LDAP directory entries. The audit was
assigned the process ID shown.
System action: The audit process starts and server
status of the audit process by using the QUERY
ANR2745I
ANR2736W
Command: parameter conflicts with

parameter - conflicting parameter.
AUDIT LDAPDIRECTORY command

finished: admin only LDAP administrator
entries are only in the LDAP directory
server (not in the Tivoli Storage
Manager server), admin only TSM
administrator entries are only in the
Tivoli Storage Manager server (not in
the LDAP directory server), node only
LDAP node entries are only in the
LDAP directory server (not in the Tivoli
Storage Manager server), node only TSM
node entries are only in the Tivoli
Storage Manager server (not in the
LDAP directory server), and total deleted
entries entries were deleted from the
LDAP server in total.
Explanation: The inconsistencies between the LDAP

directory server and the Tivoli Storage Manager server
are displayed as a result of the AUDIT
LDAPDIRECTORY command.
723
ANR2746W ANR3094E
ANR2746W
Node node name was located in the

database but not in the LDAP directory
server.
Explanation: An inconsistency between the LDAP

directory server and the Tivoli Storage Manager
database was discovered. A node 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 node is inaccessible
until action is taken. See the user response for
recommended action.
User response: To make the node accessible, you need
to add the node to the LDAP directory server. Issue the
UPDATE NODE command with a password to create
an LDAP node entry in the LDAP directory server.
ANR2747W
Administrator admin name was located in

the database but not in the LDAP
directory server.

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.

ANR2749W
Administrator admin name was located in

the LDAP directory server but not in the
database.

database was discovered. An unexpected administrator
entry was found in the LDAP directory server. An extra
entry in the LDAP directory server does not affect
Tivoli Storage Manager server operations. If the LDAP
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
servers.
System action: If the AUDIT LDAPDIRECTORY
command is issued with FIX=YES, the server deletes
the administrator entry from the LDAP directory server.
If the command is issued with FIX=NO, the server does
not delete the entry.
ANR2794I
LDAP password set.

authenticate with the LDAP server has been set,
changed or removed with the SET LDAPPASSWORD
command.

User response: To make the administrator accessible,
you need to add the administrator to the LDAP
directory server. Issue the UPDATE ADMIN command
with a password to create an LDAP administrator entry
in the LDAP directory server.
ANR2748W
Node node name was located in the

LDAP directory server but not in the
database.

database was discovered. An unexpected node entry
was found in the LDAP directory server. An extra entry
in the LDAP directory server does not affect Tivoli
Storage Manager server operations. If the LDAP
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
servers.
System action: If the AUDIT LDAPDIRECTORY
command is issued with FIX=YES, the server deletes
the node entry from the LDAP directory server. If the
command is issued with FIX=NO, the server does not
delete the entry.
724
ANR2829E
Command: parameter - parameter is not

allowed.
Explanation: The UPDATE NODE command has been

entered with a parameter that is not allowed.
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
processing that prevents unintended updates. The
syntax processing is strictly enforced and in many
cases, it might be necessary to issue other commands
prior to using UPDATE NODE. Refer to the
Administrators Reference in the Tivoli Storage Manager
Information Center for a complete description of the
command restrictions for UPDATE NODE.
ANR3094E
The distinguished name "DN" that is

specified in the LDAPURL option does
not exist on the LDAP directory server.
Explanation: The distinguished name (DN) that is

specified in the LDAPURL server option is not found
on the LDAP directory server.
ANR3097W ANR3104E
ANR3101I
User response: Create the directory entry that is

associated with the DN, specify a DN in the LDAPURL
that already exists, or specify another directory server
that contains the DN that is defined in the LDAPURL
server option. Choose one of these options and restart
the IBM Tivoli Storage Manager server.
Successfully initialized LDAP directory

services.
Explanation: The server was successfully configured

to use LDAP directory services.
System action: Server operations continue and LDAP
directory services are available.
ANR3097W
LDAPUSER must be set before you can

use LDAP password authentication.
Explanation: The LDAPURL server option is set,

however LDAP password authentication cannot
complete until LDAPUSER and LDAPPASSWORD are
set.
System action: Server operations continue without
LDAP authentication.
User response: Issue the SET LDAPUSER and SET
LDAPPASSWORD commands, in that order.
ANR3098W
LDAPPASSWORD must be set before

you can use LDAP password
authentication.
Explanation: The LDAPURL server option is set,

however LDAP password authentication cannot
complete until the LDAPUSER and LDAPPASSWORD
are set.
System action: Server operations continue without
LDAP authentication.
User response: Issue the SET LDAPPASSWORD
command.
ANR3099E
The distinguished name "DN" specified

in the LDAPURL option does not have
the proper syntax.
Explanation: The distinguished name (DN) in the

LDAPURL server option does not have the proper
syntax. The LDAP URL must use the RFC 2255 format
with the restriction that the LDAPURL server option
can only contain ASCII characters. The DN must
conform to the requirements of the directory server.
Directory servers typically support RFC 2253 or 4514
for the DN format.
User response: Correct the LDAPURL server option
and restart the IBM Tivoli Storage Manager server.
ANR3100I
ANR3102E
An authentication failure occurred

during LDAP directory services
initialization as user LDAP user.

LDAPPASSWORD value, or both, are incorrect.
System action: Server operations continue. LDAP
directory services are not available.
User response: Correct the values for the LDAP user
and LDAP password by issuing the SET LDAPUSER
and SET LDAPPASSWORD commands. After you issue
these commands, LDAP directory services initialization
is attempted.
ANR3103E
Failure occurred while initializing

LDAP directory services.
Explanation: An error occurred while the server

initialized LDAP directory services.
System action: Server operations fail. If the server is
already started, LDAP directory services are no longer
available. The server cannot start if it was in the middle
of trying to start.
the activity log file and search for messages. Check for
network problems. Check for problems with the
certificate used by the directory server or the key
database containing the certificates. Check the access
rights of the LDAPUSER. Check the status of the
directory server and examine the log files provided by
the directory server. Use LDAP utilities such as
ldapsearch or ldp to isolate the problem.
If the server does not start, remove the LDAPURL
server option to allow the server to start temporarily
without directory services. If the server is running,
issue the SET LDAPUSER or SET LDAPPASSWORD
commands to try initializing LDAP directory services
again.
Initializing LDAP directory services.
Explanation: The server started the initialization

process with the LDAP directory server.
ANR3104E
The LDAP directory service is not

successfully configured.
Explanation: The IBM Tivoli Storage Manager server

must be configured correctly in order to use LDAP
directory services, before accounts can be placed in the
LDAP directory server to authenticate access requests.
725
ANR3105E ANR3112E
System action: Server operations fail.
User response: To configure LDAP directory services,
set the LDAPURL server option, add the appropriate
certificate to the IBM Tivoli Storage Manager server key
database, and issue the SET LDAPUSER and SET
LDAPPASSWORD commands.
If the Tivoli Storage Manager server is already
configured to use LDAP directory services, an
authentication failure might have occurred or another
error might have occurred during configuration.
Examine the server messages that were issued prior to
this message to determine the source of the error. Issue
the QUERY ACTLOG command to view the activity log
and search for messages.
ANR3105E
The LDAP directory service was not

found by using Domain Name System
(DNS).
Explanation: An LDAP directory server could not be

located using the system's current DNS server
configuration and DNS suffix search list.
User response: Check the system's DNS configuration,
the status of the DNS servers, the DNS server log files,
and the DNS server configuration. Verify that the DNS
server configuration complies with RFCs 2052, 2219, or
2782.
ANR3106E
Failed to parse the LDAPURL option

value LDAP URL.
Explanation: The LDAPURL server option value

cannot be parsed. The LDAP URL must use the RFC
2255 format with the restriction that the LDAPURL
server option contain only ASCII characters.
value and restart the server.
ANR3107E
LDAPS is not allowed for the

LDAPURL option value LDAP URL.
Explanation: LDAPS represents using a Secure Sockets

Layer (SSL) connection and sending LDAP data over an
existing SSL connection. The server only supports
LDAP connections secured by using the standard
LDAPv3 "StartTLS" operation to establish a secure TLS
exchange on an existing LDAP connection.
User response: Use the standard ldap:// scheme for
the LDAPURL server option and restart the IBM Tivoli
Storage Manager server.
726
ANR3108E
The distinguished name is missing from

the LDAPURL server option value LDAP
URL.
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.
value and restart the IBM Tivoli Storage Manager
server.
ANR3109E
The LDAPURL server option value

LDAP URL does not contain a host
address and cannot be used because
another LDAPURL option value
specifies a host address.
Explanation: You cannot have multiple LDAPURL

server option values if one of the values does not
specify a host address.
server.
ANR3110E
The distinguished names "DN" and

"DN" specified with the LDAPURL
server option do not match.
Explanation: The distinguished names (DN) specified

on each LDAPURL server option value must be the
same.
server.
ANR3111E
The LDAPURL server option value

LDAP URL is missing the ldap:// prefix.
Explanation: When updating the LDAP URL

information, use the RFC 2255 format.
User response: Use the standard ldap:// scheme
prefix for the LDAPURL server option and restart the
IBM Tivoli Storage Manager server.
ANR3112E
The password cannot be reset, the

LDAP directory server requires you to
provide the current password.
Explanation: The LDAP directory server requires that

the user who is specified in the SET LDAPUSER
command provide the current password when
changing another user's password. The LDAPUSER
ANR3113E ANR3118I
needs to be able to reset passwords to allow IBM Tivoli
Storage Manager administrators to reset passwords for
Tivoli Storage Manager nodes and administrators.
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
command to change passwords for LDAP users who
are managed by the IBM Tivoli Storage Manager server.
ANR3113E
The password cannot be added or

changed, the LDAP user does not have
sufficient access rights to add or change
the password.
Explanation: If the current password was not

provided for the operation, a password reset is
performed on the LDAP directory server by the user
specified in the SET LDAPUSER command. If the
current password was provided for the operation, for
example, in the SET PASSWORD client command, the
user's password is changed on the LDAP directory
server by the user. However, if the user's password
expired, preventing access to the directory server, the
password is changed by the user specified in the SET
LDAPUSER command.
User response: Change the password policy and
access rights on the LDAP directory server to allow
users to change their own passwords, and to allow the
user specified in the SET LDAPUSER command to add
or reset passwords for the users that are being
managed by the IBM Tivoli Storage Manager server.
ANR3114E
LDAP error LDAP error code (error

description) occurred during operation.
Explanation: The LDAP operation failed with an

unexpected error.
around the same time as this message to determine the
cause and impact of the error. Issue the QUERY
for messages. Check the status of the LDAP directory
server and examine its log files. Use LDAP utilities
such as ldapsearch or ldp to isolate the problem.
ANR3115E
The LDAP directory server returned the

following error message (LDAP server
message) with the LDAP error.
Explanation: The LDAP directory server returned an

error message associated with an LDAP error that
occurred, providing addition information to assist in
determining the cause of the problem.

for messages. Check the status of the LDAP directory
such as ldapsearch or ldp to isolate the problem.
ANR3116E
LDAP SSL/TLS error GSKIT error code

(error description) occurred during
operation.
Explanation: An SSL/TLS error code was reported by

the GSKit component along with the LDAP error that
occurred.
for messages. Check for network problems. Check for
problems with the certificate used by the LDAP
directory server or the key database containing the
certificates. Check the status of the LDAP directory
such as ldapsearch or ldp to isolate the problem using
a TLS connection to the LDAP server.
ANR3117E

administrator node/admin name (client
platform) refused - the level of the client
does not meet the minimum required
level for LDAP authentication.
Explanation: The server refuses the client session

because the client program version level is not 6.4 or
later. Only version 6.4 and later clients can use LDAP
authentication.
System action: The session is refused and server
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.
ANR3118I
The LDAP entry for node node 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
specified FIX=YES, the LDAP entry for the node was
deleted to correct this inconsistency.

727
ANR3119I ANR3124W
ANR3119I
The LDAP entry for administrator admin

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
specified FIX=YES, the LDAP entry for the
administrator was deleted to correct this inconsistency.
ANR3120I
The administrator admin name was

updated because the parameter parameter
for a node with the same name was
changed.
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.
If the AUTHENTICATION parameter changed from
LDAP to LOCAL, the password was also updated.
When this happens, the password is updated to the
same password that is used for the node.
System action: The server updated the
AUTHENTICATION or SSLREQUIRED parameter of
the specified administrator.
ANR3121I
The node node name was updated

because the parameter parameter for an
administrator with the same name was
changed.

node or administrator sharing the same name will be
If the AUTHENTICATION parameter changed from
LDAP to LOCAL, the password was also updated.
When this happens, the password is updated to the
same password that is used for the administrator.
System action: The server updated the
AUTHENTICATION or SSLREQUIRED parameter of
the specified node.
728
ANR3122E
command: System level authority is

required because the server needs to
update a node or administrator that
shares the same name.

node or administrator sharing the same name will be
User response: Reissue the command using an
administrator that has system level authority.
Alternatively, rename either the node or the
administrator associated with the command such that
they do not share the same name.
ANR3123W
An LDAP entry for node node name was

not found in the LDAP directory server.
Explanation: The REGISTER NODE command was

issued with AUTHENTICATION=LDAP but without
providing a password. This combination is valid.
However, this combination will not create an LDAP
entry, which is required to access the node.
User response: An LDAP entry must be created before
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
shared with another Tivoli Storage Manager server, the
LDAP entry can be created by the other Tivoli Storage
Manager server instead.
ANR3124W
An LDAP entry for administrator admin

name was not found in the LDAP
directory server.
Explanation: The REGISTER ADMIN command was

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.
User response: An LDAP entry must be created before
this administrator can be accessed. To create a new
LDAP entry for this administrator issue the UPDATE
ADMIN command and provide a password. If the
LDAP directory server is shared with another Tivoli
Storage Manager server, the LDAP entry can be created
by the other Tivoli Storage Manager server instead.
ANR3125I ANR3378I
ANR3125I
command: Successfully updated successful

updates nodes out of total update attempts
nodes that were targeted for updating.
Explanation: The command updated a node or nodes

and produced summary statistics stating how many
nodes were updated successfully and how many
attempts were made.
ANR3126I
command: Successfully updated successful

updates administrators out of total update
attempts administrators that were
targeted for updating.
Explanation: The command updated an administrator

or administrators and produced summary statistics
stating how many administrators were updated
successfully and how many attempts were made.
ANR3183W
Explanation: During import processing, an

administrator ID was detected that authenticates
passwords with an LDAP directory server at the target,
but with the Tivoli Storage Manager server (LOCAL) at
the source. Import processing does not change an
administrator's password authentication method from
LDAP to LOCAL.
System action: Import processing continues. The
password authentication method did not change from
LDAP to LOCAL.
User response: You can change the password
authentication method for the target administrator from
LDAP to LOCAL by issuing the UPDATE ADMIN
command with the AUTHENTICATION=LOCAL
parameter.
ANR3184E

ANR3127W
You must change the password for

"LDAP user" within number day(s).
The password authentication method for

administrator admin name did not
change.
Server server name cannot replicate with

this server
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
cannot support replication with this server.
Explanation: The password is due to expire, and must

be changed to prevent failures.
System action: Server operations continue. The

replication fails.
User response: Make sure that the replication target

server is at a maintenance level that supports
replication with this server.
User response: Change the password on the LDAP

directory server and issue the SET LDAPPASSWORD
command with the new password.
ANR3198E
ANR3182W
The password authentication method for

node node name did not change.
Explanation: During replication or import processing,

a node that uses an LDAP directory server to
authenticate passwords at the target was detected, but
the source node authenticates passwords with the
Tivoli Storage Manager server (LOCAL). The
Replication and Import process does not change the
node password authentication method from LDAP to
LOCAL.
System action: Replication or Import processing
continues. The node password authentication method
did not change from LDAP to LOCAL.
User response: Change the node password
authentication method from LDAP to LOCAL by
issuing the UPDATE NODE command with the
AUTHENTICATION=LOCAL parameter.
command: The server server name

definition could not be retrieved.The
database is in an inconsistent state.
Explanation: An error occurred while accessing the

server information.
User response: For details and instructions to resolve
the issue, see Technote 1598476 at http://
www.ibm.com/support/entry/portal/. Type 1598476 in
the Search field.
ANR3378I
Administrator administrator name added


the indicated administrator definition was created
based on information from the configuration manager.
729
ANR3618W ANR4589W
ANR3618W
bad adapter number of total adapter number

host bus adapters cannot be opened.
ANR3629W
Explanation: The SAN discovery function is not able

to open all of the host bus adapters (HBAs) on the
system.
User response: Tivoli Storage Manager SAN discovery
may only be getting partial device information from the
SAN. Verify that all HBAs are configured and working
properly.
ANR3619W
The user limit for limit is below the

recommended minimum value of value.
Explanation: A user limit that is below the

recommended minimum value might cause unexpected
behavior.
User response: Set the user limit so that it is equal to
or greater than the recommended minimum value.
ANR3625I
Host bus adapter (HBA) API functions

are not supported by adapter adapter
name.
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
adapter might be a Serial Attached SCSI adapter.
Therefore, SAN discovery does not work.
System action: The system is unable to retrieve the
attributes of the adapter.
User response: Validate whether this adapter is a
Fibre Channel SCSI adapter or not, and if it is, contact
hardware support for the adapter.
ANR3626W
A check condition occurred during a

small computer system interface (SCSI)
inquiry at Fibre Channel port WWN=fc
port wwn, KEY=sense key, ASC=asc,
ASCQ=ascq.
All administrators with system level

authority use LDAP authentication.
Administrator admin was the most recent
administrator with system level
authority that used LOCAL
authentication.
Explanation: All administrator with system level

authority use LDAP authentication. This situation has
risks, based on the availability of the LDAP server. If
required, make sure that the LDAP server has high
availability configurations implemented. For example:
clustering, mirroring, or replication. Having one
system-level administrator with LOCAL authentication
gives that administrator the ability to update other
administrators and nodes to LOCAL authentication if
the LDAP server is down unusable for an extended
period of time.
System action: The only administrator with system
level authority uses LDAP authentication.
User response: Consider having one administrator
with system authority and LOCAL authentication. If
this is not possible, validate that the high availability
configurations for the LDAP server are sufficient.
ANR4589W
The DB2 connection was lost following

a database restore operation.
Explanation: The server database was restored, but

the DB2 connection failed. For this reason, if the path
to the DB2 log directory was changed as part of a DB
restore operation, the database path to the log directory
was not updated automatically.
System action: The server database is restored.
User response: If the path to the DB2 log directory
did not change, no action is needed. If the path to the
DB2 log directory changed, you must manually update
the path when the server is started. To update the path,
connect to the DB2 database and change the
configuration, as described in the following example:
v Start DB2: db2start
v Connect to TSMDB1: db2 connect to TSMDB1
v Update the DB2 database configuration: db2 update
db cfg using NEWLOGPATH (log path from server
options, e.g. /ALOG/tsminst1)
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
bus reset might have occurred during the operation.
v Terminate the connection to TSMDB1: db2 terminate
System action: The HBAAPI inquiry function was

unable to retrieve the SCSI device information from this
port.
v Verify that the new log path is in takes effect: db2

connect to TSMDB1; db2 get db cfg | grep "Path to
log files ( on UNIX ) "
User response: Verify that the adapter, device, and

Fibre Channel are connected. For more information
about the values of the KEY, ASC, and ASCQ fields, see
the SCSI specification.
730
v Recycle DB2: db2stop/db2start
v Verify that the new log path is in takes effect: db2

connect to TSMDB1; db2 get db cfg | find "Path to
log files ( on Windows ) "
ANR4603I ANR4608E
ANR4603I
The volume history file that existed

before the upgrade to Version 6.3 or
later was saved under another name: file
name.
Explanation: After an upgrade of Tivoli Storage

Manager server to V6.3 or later, if you want to revert to
the previous release, you must have the original
volume history file. The reason is that the V6.3 or later
volume history file has a different format than the
earlier volume history file. The newer volume history
file cannot be used to restore the Tivoli Storage
Manager database to the previous release.
System action: The system saves the previous volume
history file under another name to ensure that it is not
overwritten.
User response: To restore the Tivoli Storage Manager
database, use the saved volume history file.
ANR4604E
Restore database volume header magic

number magic does not match the
expected volume header magic number
of expected magic. This volume cannot be
used to restore the database.
Explanation: Each volume contains a Tivoli Storage

Manager volume header that begins with a header
magic number. A bad magic number indicates that this
volume is either corrupted or not suitable for restoring
the database.
User response: Check the volume history file to make
sure that this volume is a valid database backup
volume. If the volume is corrupted, restore the
database to a different time using a different set of
backup volumes.
ANR4605E
Restore database volume header version

number version does not match the
expected volume version number of
expected version. This volume cannot be
Explanation: Each database backup volume contains a

Tivoli Storage Manager version number in the volume
header. A mis-matched version number indicates that
this volume is either corrupted or not suitable for
restoring the database. This volume may be a pre
Version 6.3.0 database backup volume. It cannot be
used to restore a Tivoli Storage Manager V6.3 database.
sure that this volume is a valid database backup
volume. If this volume is corrupted, restore the
backup volumes.
ANR4606E
Restore database volume header backup

series number series does not match the
expected backup series number of
expected series. This volume cannot be

Tivoli Storage Manager backup series number in the
volume header. A mis-matched backup series number
indicates that this volume is either corrupted or not
suitable for restoring the database.
sure this volume is valid for a database backup
operation. If the volume is valid, the volume history
file can be modified to match this series number and
you can reissue the DSMSERV RESTORE DB command.
If the problem persists, this volume may be corrupted.
Restore the database to a different time using a
different set of backup volumes.
ANR4607E

operation number operation does not
match the expected backup operation
number of expected operation. This
volume cannot be used to restore the
database.

Tivoli Storage Manager backup operation number in
the volume header. A mis-matched backup operation
number indicates that this volume is either corrupted
or not suitable for restoring the database.
operation. If the volume is valid, the volume history
file can be modified to match this operation number
and you can reissue the DSMSERV RESTORE DB
command. If the problem persists, this volume may be
corrupted. Restore the database to a different time
using a different set of backup volumes.
ANR4608E

type backup type is invalid. This volume
cannot be used to restore the database.

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
restoring the database.
731
ANR4609I ANR8528E
operation. If this volume is corrupted, restore the
backup volumes.
used to test or evaluate new features, but it can neither

be used for any commercial purpose nor placed into
production.
System action: No action is taken.
ANR4609I
Restore database process found backup

type database backup timestamp backup
timestamp from database backup media.
Explanation: This is the backup timestamp that is

used for a database restore operation.
System action:
User response:
ANR4613E

backup volumes.
The database backup timestamp of
backup timestamp on media on database
backup media with backup type backup
type does not match the backup
timestamp backup timestamp from volhist
from the volume history file. This
volume cannot be used to restore the
database.
Explanation: Mis-matched timestamps indicates that

backup volumes.
ANR4898W
This is a pre-release server_version Tivoli

Storage Manager server (driver
driver_number, build build_id). It is not
supported for commercial or production
use.
Explanation: The Tivoli Storage Manager server is

running a pre-release program. The program can be
732
ANR4899E
Meta data for restore database volume

backup volume is not valid. This volume
cannot be used to restore the database.
Explanation: Backup volumes contain Tivoli Storage

Manager meta data. Invalid meta data indicates that
ANR4614E
User response: If the Tivoli Storage Manager server is

being used to evaluate new features, no action is
required. If the server will be used in a production
environment or for a commercial purpose, contact your
IBM sales representative or authorized business partner
to obtain a fully-supported, released version.
The server database was formatted
using a pre-release server_version Tivoli
Storage Manager server (driver
driver_number, build build_id). The server
is not supported for commercial or
production use.
Explanation: The server database was created using

an unsupported, pre-release version of the Tivoli
Storage Manager server. The server can be used to test
or evaluate new features, but it can neither be used for
any commercial purpose nor placed into production.
System action: No action is taken.
User response: If the server is being used to evaluate
new features, no action is required. If the server will be
used in a production environment or for a commercial
purpose, remove the database. Create a new database
using a fully-supported, released version.
ANR8527E
The default cartridge access port (CAP)

ID is invalid for library library name.
Explanation: The default CAP ID was specified in the

CHECKOUT LIBVOLUME command. If the default
CAP ID is specified, the CAP priority value must be set
to a nonzero value.
System action: The system failed to eject the tape
volumes.
User response: To verify the CAP priority value, issue
the QUERY CAP command. If the priority value is 0,
set the CAP priority to a nonzero value and reissue the
CHECKOUT LIBVOLUME command.
ANR8528E
The slot element address slot element

address is invalid for the library name
library.
Explanation: The slot element address is no longer

valid. This issue might occur when a library is turned
off or during a hardware malfunction. For a virtual
library, this problem also might occur after the library
is reconfigured or its firmware is updated.
System action: The slot in this library is unavailable.
User response: Ensure that the library is turned on
and that no hardware problems are evident. To verify
ANR8529E ANR9008E
the slot element address, use the device driver tool or
virtual library configuration tool.
ACSLS library to ensure that no tapes are lodged there.

ANR9007E
ANR8529E
Command: Unable to open library library

name by using an open system call.
Explanation: Tivoli Storage Manager cannot open the

library.
System action: The transaction that requires this
library fails.
User response: Inspect the library. Ensure that the
library is turned on and ready. Ensure that the library
is configured correctly for the host system.
ANR9005E
Command: Library library name has an

active relabel process and can not be
deleted.
Explanation: The designated library can not be

deleted or updated because it is currently in use for a
relabel operation.
User response: Wait until the relabel operation
completes, and then retry the command.
ANR9006E
Tape volumes must be physically

removed from an ACSLS cartridge
access port (CAP).
Explanation: Tape volumes are located in the ACSLS

CAP. The ACSLS server requires users to physically
remove these volumes from the CAP within 30
minutes. When REMOVE=YES is set for the
CHECKOUT LIBVOLUME command, a tape ejection
operation is scheduled. If the user fails to remove the
tape from the CAP within 30 minutes, the ACSLS
server sets a failure status for the tape ejection
operation.
System action: The ACSLS library ejected tape
volumes and relocated them to a CAP.
User response: Remove the volumes from the CAP. If
there are no tape cartridges in the CAP, check the
Command: The library cartridge access

port (CAP) ID is invalid for library
library name.
Explanation: Tape volumes were not ejected from the

ACSLS library because the library CAP ID was not
specified in the CHECKOUT LIBVOLUME command.
By default, all CAPs initially have a priority value of 0,
which means that the ACSLS server does not
automatically select a CAP.
System action: The system failed to eject the tape
volumes.
User response: To verify the CAP priority value, issue
the QUERY CAP command. If the priority value is 0,
reissue the CHECKOUT LIBVOLUME command with a
CAP ID. Alternatively, set the CAP priority to a
non-zero value and reissue the CHECKOUT
LIBVOLUME command.
ANR9008E
Unable to determine the drive type for

Device of type Device Inquiry String.
Explanation: The drive could not be opened. This

version of Tivoli Storage Manager may not support the
drive type.
System action: The system failed to identify the drive
type.
User response: Verify that the drive type is supported.
For devices supported on AIX, HP-UX, Solaris, and
Windows, see the Tivoli Storage Manager Supported
Devices for AIX, HP-UX, Solaris, and Windows
document at http://www.ibm.com/software/
sysmgmt/products/support/
html.
For devices supported on Linux, see the Tivoli Storage
Manager Supported Devices for Linux document at
support/IBM_TSM_Supported_Devices_for_Linux.html
.
Version 6.3.3 ANR changed messages

The following Tivoli Storage Manager server ANR messages are changed for
version 6.3.3. The messages are listed in a summary table and all elements of the
message are documented.
Table 6. Version 6.3.3 changed messages summary
Message
What is changed
ANR0151W
Message text, explanation, system action,

user response
ANR0238E
Explanation
ANR0263I
Message text
ANR0264E
Explanation
733
Table 6. Version 6.3.3 changed messages summary (continued)
734
Message
What is changed
ANR0340E
User response
ANR0381I
User response
ANR0393I
Message text
ANR0425W
ANR0428W
Explanation
ANR0430W
ANR0431W
ANR0454E
User response
ANR0470W
Message text
ANR0502E
User response
ANR0553E
ANR0836W
User response
ANR1630W
Explanation
ANR2144E
ANR3016I
Explanation
ANR3023I
Explanation
ANR3024W
Explanation
ANR3025I
Explanation
ANR3028E
Explanation
ANR3029E
Explanation
ANR3032E
Explanation
ANR3034E
User response
ANR3040I
Explanation
ANR3041I
Explanation
ANR3044I
Explanation
ANR3045I
Explanation
ANR3048I
Explanation
ANR3049I
Explanation
ANR3050W
Message text
ANR3052I
Explanation
ANR3053I
Explanation
ANR3056I
Explanation
ANR3057I
Explanation
ANR3060I
Explanation
ANR3061I
Explanation
ANR3064I
Explanation
ANR3065I
Explanation
ANR3067E
Explanation
ANR3070E
Explanation
ANR3073E
Explanation
ANR0151W ANR0238E
Table 6. Version 6.3.3 changed messages summary (continued)
Message
What is changed
ANR3076E
Explanation
ANR3079E
Explanation
ANR3082E
Explanation
ANR3085E
Explanation
ANR3088W
Explanation
ANR3171E
User response
ANR3174E
Explanation
ANR3178E
Message text, explanation, system action,

user response
ANR3239E
User response
ANR3502W
User response
ANR3504W
User response
ANR3551I
Explanation
ANR3999E
User response
ANR4588E
Message text
ANR8220W (AIX)
ANR8300E
Message text
ANR8302E
Message text
ANR8463E
User response
ANR8884W
Message text
ANR8943E
ANR8944E
Message text
All elements of the message are documented, including message ID, message text,
explanation, system action, and user response. The messages are listed in
ascending numeric order.
ANR0151W
Database manager fails to start. For

more information about the failure,
issue the db2start command.

database manager. The following are possible causes:
v The database manager license key is invalid or
missing.
v The server instance password was changed.
User response: For more information about the failure,
try to start the database manager by issuing the
db2start command, as in this example:
C:\Users\admin>db2start. You might receive messages
similar to the following ones: SQL1397N The DB2
service failed to logon. SQL1032N No start database
manager command was issued. SQLSTATE=57019. To
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.

If you are starting a DB2 server on a Windows
platform, you can set the logon account for a DB2
service by using the Services dialog box from the
Control Panel.
ANR0238E
A database recovery task is prohibiting

dbCode.

an error occurred because the database was busy
performing a BACKUP, RESTORE or was in
ROLLFORWARD pending state. Examine the sqlcode to
determine the condition that is preventing the database
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
( -1116 ) indicates a database BACKUP is pending and
must complete prior to activating the database. Once
the database BACKUP is complete, the database can be
735
ANR0263I ANR0340E
SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates a
database Roll Forward operation is pending and must
complete before activating the database. After the Roll
Forward recovery step is complete, the database can be
SQLE_RC_BKP_INPROG ( -1118 ) occurs when an
attempt to activate the database fails because a
database BACKUP was in progress. Prior to activating
the database, it is necessary to rerun database BACKUP.
Once the database BACKUP completes successfully, the
database can be activated by starting the server.
SQLE_RC_RST_INPROG ( -1119 ) shows that a
database RESTORE was in progress when the database
failed to activate. The RESTORE database must be
restarted and allowed to complete successfully before
activating the database. Once the database RESTORE in
complete, the database can be activated by starting the
server. SQLE_RC_BR_INPROG ( -1120 ) means that
either a database BACKUP or RESTORE must complete
before activating the database. Ensure that either a
BACKUP or RESTORE operation completes successfully
before activating the database.
User response: See message explanation for more
information.
or deleting a database file or a directory for the

database. The system cannot locate the database
subdirectory or database configuration file during
connect. Problem causes are ordered in terms of their
frequency of occurrence: A log file cannot be found in
the active log path directory. There may be a problem
with the database directory the operation is being
attempted on. There may be inadequate disk space to
complete the operation. The database cannot be used.
User response: Appropriate responses for the problem
causes described above are: To verify if a log file is
missing, check the db2diag.log for the presence of a
logging error (return code contains SQLO_FNEX). If
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
roll-forward the database to an earlier point in time
referenced in a log file preceding the missing log file
(use a timestamp that is earlier than that of the missing
file). There may be a problem with the database
directory. Check the integrity of the directory. Examples
of potential problems include: permissions issues,
mount point problems, corruption. Increase filesystem
size.
ANR0340E
ANR0263I
Database restart/recover area

successfully converted to compatible
format.
Explanation: The server converted the

restart/recovery areas of its database and recover log
volumes to a format compatible with the
restart/recovery area written by other versions of the
server. This is a one time conversion, and will only be
performed if the restart/recovery area was not already
in the compatible format.
System action: The restart/recovery area was
successfully converted.
ANR0264E
A database file IO error is prohibiting

dbCode.

an IO error occurred when processing a database file.
The problem may have occurred in one of the
following situations: The system cannot open, read
from, or write to a database file. The system cannot
create the database because an error occurred while the
system was creating a database file or a directory for
the database. The system cannot drop the database
because an error occurred while the system was
deleting a database file or a directory for the database.
The system cannot create the database because an
interrupt was received while the system was creating
736
command: Outbound replication

operations are disabled because the
database was restored.
Explanation: The database for this server was

restored. Data that was on this server but that is not
referenced by the restored database is no longer
accessible. To prevent this server from deleting copies
of data that might exist on the target replication
servers, replication operations originating from this
server are disabled.
User response: Disabling replication after a database
restore is a precautionary step to alert the user of the
potential that a restored database might contain node
inventory that could result in the loss of filespace data
on a target replication server that is using node
replication. If replication was not used on this server
before the database restore, issue the ENABLE
REPLICATION command to resume replication
operations.
To preserve the data that exists on target replication
servers, determine whether copies of data that are on
the target replication server are needed. If they are, you
must replicate data that is on the target replication
server to the source replication server. After the
replication is complete, issue the ENABLE
REPLICATION command to resume replication
operations.
For example, suppose that PRODSRV is the source
replication server. The data belonging to client node
ANR0381I ANR0428W
NODE1 was replicated from PRODSRV to DRSRV, the
target replication server. The database on PRODSRV
was restored.
To resume replication, complete the following steps:
2. Update NODE1 definitions. When replication
occurs, DRSRV will send the data to PRODSRV that
was lost because of the database restore.
REMEMBER: To replicate data that was on DRSRV, you

set the target replication server to PRODSRV. In your
original configuration, if you were replicating data from
DRSRV to another server, for example, BKUPDRSRV,
you must reset the target replication server. To reset the
target replication server, issue the following command
on DRSRV: SET REPLSERVER BKUPDRSRV.
ANR0381I
Buffer pool statistics were successfully

reset.
a. On DRSRV, issue the following command:

UPDATE NODE NODE1
REPLSTATE=ENABLED
REPLMODE=SYNCSEND.
Explanation: Buffer pool statistics, such as the Cache

Hit Ratio, have been reset. The RESET BUFPOOL
command and the ESTIMATE DBREORGSTATS
command will reset the buffer pool statistics.
b. On PRODSRV, issue the following command:

UPDATE NODE NODE1
REPLSTATE=ENABLED
3. On DRSRV, set the replication rules to match those

on PRODSRV. For example, if only archive data was
being replicated from PRODSRV to DRSRV, set the
rules on DRSRV to replicate only archive data from
DRSRV to PRODSRV. Backup and space-managed
data will not be replicated to PRODSRV.
4. On DRSRV, set the target replication server by
issuing the following command: SET REPLSERVER
PRODSRV.
5. On DRSRV, replicate data belonging to NODE1 by
issuing the following command: REPLICATE NODE
NODE1. Replication processing changes the
replication mode of NODE1 to SEND on DRSRV
and to RECEIVE on PRODSRV.
7. Update NODE1 definitions:
a. On PRODSRV, issue the following command:
UPDATE NODE NODE1
REPLSTATE=ENABLED
REPLMODE=SYNCSEND.
b. On DRSRV, issue the following command:
UPDATE NODE NODE1
REPLSTATE=ENABLED
8. On PRODSRV, enable replication by issuing the
following command: ENABLE REPLICATION.
9. On PRODSRV, replicate data belonging to NODE1
by issuing the following command: REPLICATE
NODE NODE1. Replication processing changes the
replication mode of NODE1 to SEND on PRODSRV
and to RECEIVE on DRSRV.
The original replication configuration is restored.
PRODSRV has all the data that was lost because of the
database restore.

current values for the buffer pool statistics.
ANR0393I

operations is enabled for LAN-free data
transfer for node node name using
Explanation: The storage pool is capable of LAN-free

data transfer operations for node node name using
ANR0425W


because the client nodes password has expired.
NODE command.
ANR0428W

down-level with this server version.
Explanation: The server refuses the client session

because the client program version level is older than
that supported by the server program. For certain
problems (such as the compression fix), once a node
connects to the server using the newer client, the server
737
ANR0430W ANR0502E
records this fact and will not let this node back off this
client version to a version that does not include the fix.
User response: Apply service to the client program to
make it compatible with the newer server program.
ANR0430W

name is locked.

session because the node is locked from server access
(with the LOCK NODE command or by the LDAP
directory server).
must unlock the node. Nodes using LOCAL
authentication can be unlocked with the UNLOCK
NODE command. Nodes using LDAP authentication
can be unlocked from within the LDAP directory
server.
ANR0431W
Session session number refused administrator administrator ID (client

platform) is locked.
Explanation: The server refuses the specified

administrative session because the administrator is
locked from server access (with the LOCK ADMIN
command or by the LDAP directory server).
User response: Before the administrator is permitted
to access the server, a properly authorized
administrator must unlock the administrator.
Administrators using LOCAL authentication can be
unlocked with the UNLOCK ADMIN command.
Administrators using LDAP authentication can be
unlocked from within the LDAP directory server.
ANR0454E
Session rejected by server server name,

reason: rejection reason.
Explanation: The server tried to open a session with

the named server. The session was rejected for the
indicated reason.
User response: Check both the servers for any
additional messages that might further describe the
reason the session was rejected. For a reason of
AUTHENTICATION FAILURE, ensure that all
passwords have been set correctly on both servers. The
password for the server (set by SET
SERVERPASSWORD on server X) and the password in
the server definition (set by DEFINE or UPDATE
SERVER X SERVERPASSWORD=) are the same
738
password. For a reason of VERIFICATION FAILURE,

use the QUERY SERVER command to determine that
the HLADDRESS and LLADDRESS of the target server
are correct. If they are not, correct them with the
UPDATE SERVER command. If they are correct,
resynchronize with the target server by issuing the
UPDATE SERVER FORCESYNC=YES. For a reason of
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,
session. For a reason of INTERNAL ERROR, use the
messages on the target server to determine the
problem. For all reasons, if none of the above are
applicable, ensure that the shown server has not
disabled this server with the DISABLE SESSIONS
SERVER command.
ANR0470W

administrator name refused administrator password has expired.

because the administrators password has expired.
ADMIN command.
ANR0502E

platform) - A storage pool for the target
destination is associated with a device
class that has a Centera device type.

management class has been specified. Centera device
types may be used only for archive objects.
User response: Ensure that Centera device types are
associated with device classes that are used only for
archive operations. The UPDATE COPYGRP command
can be used to update copy groups associated with
space management and/or backup storage pools so
that they point to valid destinations.
ANR0553E ANR3028E
ANR0553E

session number - administrator
administrator name does not have
adequate authority over node node name.
Explanation: The specified administrator does not

have the proper authority necessary to perform this
operation on the specified node.
administrator. Ensure that the new password is

different from the old password. If you are
authenticating to an LDAP directory server ensure that
the new password meets all other password policy
rules specified by the LDAP directory server. Reissue
the command with a valid password.
ANR3016I
System action: The server does not perform the query.

ANR0836W
No query restore processing session

session id for node node name and filespace
name failed to retrieve file high-level file
namelow-level file name - file being
skipped.
Explanation: The no query restore processing for the

session listed relating to the specified node name and
filespace failed to retrieve the specified file. An error
occurred while retrieving this file so it will be skipped.
System action: The no query restore operation
continues.
User response: Determine the cause of the file retrieve
failure and correct it. After this situation is correct, the
client can do a restore of the specific file that was
skipped.
ANR1630W
command: node name is not configured for

replication.
Explanation: The node specified in the command is

not configured for replication. A node is configured for
replication if the replication state of the node is
ENABLED or DISABLED. To determine the replication
state, issue the QUERY NODE FORMAT=DETAILED
command.
System action: The operation continues but the node
is skipped for this operation.
User response: Verify that the nodes specified in the
command are configured for replication and try the
command again. Nodes may be configured for
replication with the UPDATE NODE command.
ANR2144E
Command: Invalid password - password.
Explanation: The command specifies an invalid node

or administrator password.
command.
User response: Ensure that the password adheres to
naming convention rules and meets the minimum
password length requirement as set by your
command: Configuration refresh interval

set to interval.

configuration refresh interval to the specified value.
Automatic configuration refresh processing will
immediately be attempted and then will again be
performed after the specified number of minutes of
elapsed.
ANR3023I
command: Profile profile name locked.
Explanation: The command has successfully locked

the profile. No configuration information can be
propagated to the subscribers of the profile until it is
unlocked.
ANR3024W
command: Profile profile already locked

with timeout interval greater than
interval.
Explanation: An attempt was made to lock the

specified profile. The profile is already locked with a
timeout interval greater than the value specified.
System action: The profile remains locked with the
original timeout interval.
User response: If you want to lower the timeout
interval, unlock the profile and then lock the profile
again specifying the lower value.
ANR3025I
command: Profile profile name unlocked.
Explanation: The command has successfully unlocked

the profile. Configuration information can now be
propagated to the subscribers of the profile.
ANR3028E
command: Profile profile name is locked.

performed on a locked profile.
739
ANR3029E ANR3050W
User response: Unlock the profile using the UNLOCK
PROFILE command and then reissue the command.

ANR3044I
ANR3029E
command: Profile name not specified.
Explanation: A profile name must be specified on this

command using the PROFILE= parameter.
profile name.
command: All domains associated with


associated all the domains with the specified profile.
All domain definitions will be automatically
propagated to managed servers which subscribe to the
profile. If a domain is added to the configuration
manager in the future, its definition will also be
automatically propagated to the managed servers.
ANR3032E
command: Server name not specified.
Explanation: A server name must be specified on this

command using the SERVER= parameter. This
identifies the configuration manager.
server name.

ANR3045I
command: Domain domain associated with


associated the domain with the specified profile. The
domain definition will be automatically propagated to
ANR3034E
command: Server server cannot be used as

this server's configuration manager.

command which cannot be used as a configuration
manager.
User response: Find out the correct name for the
configuration manager and then reissue the command.
ANR3040I
command: All administrators associated


associated all the administrators with the specified
profile. All administrator definitions will be
automatically propagated to managed servers which
subscribe to the profile. If an administrator is added to
will also be automatically propagated to the managed
servers.

ANR3048I
command: All admin schedules


associated all the admin schedules with the specified
profile. All admin schedule definitions will be
subscribe to the profile. If an admin schedule is added
definition will also be automatically propagated to the
managed servers.
ANR3049I
command: Admin Schedule admin schedule


associated the admin schedule with the specified
profile. The admin schedule definition will be
ANR3041I
command: Administrator admin associated


associated the administrator with the specified profile.
The administrator definition will be automatically
profile.
740

ANR3050W
command: No additional admin

schedules associated with profile
profilename.
Explanation: No additional admin schedules were

associated with the profile. The admin schedule(s)
ANR3052I ANR3065I


DEFINE PROFASSOCIATION command. The QUERY
used to see which admin schedules are already
ANR3060I
ANR3052I
command: All scripts associated with


associated all the scripts with the specified profile. All
script definitions will be automatically propagated to
script is added to the configuration manager in the
propagated to the managed servers.
command: All servers associated with


associated all the servers with the specified profile. All
server definitions will be automatically propagated to
server is added to the configuration manager in the
propagated to the managed servers.
ANR3061I
command: Server server associated with


associated the server with the specified profile. The
server definition will be automatically propagated to
ANR3053I
command: Script script associated with


associated the script with the specified profile. The
script definition will be automatically propagated to
ANR3056I
command: All client option sets


associated all the client option sets with the specified
profile. All client option set definitions will be
subscribe to the profile. If a client option set is added
definition will also be automatically propagated to the
managed servers.
ANR3057I
command: Client option set client option

set associated with profile profilename.

ANR3064I
command: All server groups associated


associated all the server groups with the specified
profile. All server group definitions will be
subscribe to the profile. If a server group is added to
will also be automatically propagated to the managed
servers.
ANR3065I
command: Server group server group


associated the server group with the specified profile.
The server group definition will be automatically
profile.

associated the client option set with the specified
profile. The client option set definition will be
741
ANR3067E ANR3171E
ANR3067E

Explanation: No matching administrator definitions

are associated with the specified profile.

command to check which client option sets are
command: No matching servers

ANR3082E

command to check which administrators are associated
Explanation: No matching server definitions are

associated with the specified profile.
ANR3070E
command: No matching domains

Explanation: No matching domain definitions are


command to check which servers are associated with

ANR3085E

command to check which domains are associated with
Explanation: No matching server group definitions are

ANR3073E

Explanation: No matching admin schedule definitions

command to check which admin schedules are
ANR3076E
command: No matching scripts associated

with profile profile.
Explanation: No matching script definitions are

command to check which scripts are associated with
ANR3079E

Explanation: No matching client option set definitions

742

command to check which server groups are associated
ANR3088W
This command will cause the deletion

of objects on any managed server
subscribed to profile profile name.
Explanation: A DELETE PROFASSOCIATION

command option has been entered. This action will not
only delete the association from the profile, but it will
also result in the deletion of managed object(s) on any
managed server subscribing to this profile. The deletion
of these objects will occur during the next configuration
refresh for that managed server.
User response: To process the DELETE
PROFASSOCATION command, enter 'Y' to continue or
'N' to stop the command.
ANR3171E
Configuration refresh with

configuration manager server name had
to skip processing for one or more
objects.

it became necessary to skip the creation or deletion of
one or more objects.
ANR3174E ANR3999E
User response: Examine the managed server's activity
log for earlier messages that identify the object, and
take the actions identified in those messages.
Configuration refresh processing will not complete
successfully until the problem is clear up.
ANR3174E
Communication error with managed

server server name.

to the specified managed server, a communications
error was experienced.
the managed server is up.
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
no files to process, or for other more serious problems.
First, retry the command and see if it completes
without any skipped files. If you are unable to generate
the backup set without skipping files, please contact
your local service representative for assistance.
ANR3504W
Backup set for node name as set name was

not able to log the volumes used for this
operation to the server volume history.

was created. However, when the process attempted to
add the volumes, used for this operation to the volume
history for the server, an error occurred and this could
not be completed.
ANR3178E
A communication error occurred during

session session number with replication
server server name.
Explanation: The communication error occurred while

the system was receiving information from or sending
information to the specified replication server. This
error can occur on a target replication server if a
CANCEL REPLICATION command is issued on the
source replication server.

determine which volumes were used to generate this
backup set. The volumes can be inserted into the server
volume history for use by issuing a DEFINE
BACKUPSET and listing these volumes. This will also
allow this backup set to be queried from a client as
well since there is not a server entry for this backup
set. Only issue the DEFINE BACKUPSET if this
generate backup set operation completed successfully.
System action: The server is running, but the

operation that was in progress failed.
ANR3551I
User response: If this error occurs frequently, consult

your network administrator. Also review the activity
log on the target and source replication servers for
messages that are related to replication.
ANR3239E
Error rc while creating device class device

class.
The server delete batch size has been set

to new batch size. Deletion operations
new value.
Explanation: A SETOPT command was used to set the

value for the delete batch size value. This setting
deleted from the server in one database transaction.
The setting influences inventory expiration operations.
Explanation: This message is issued when a device

class could not be created, because there was an error
while processing the device configuration file.

deletion operations that are started after this message is
issued.
User response: Look in the device configuration file

for errors, and look at the activity log for any previous
error messages that might help determine the location
of these errors in the device configuration file.
ANR3999E
ANR3502W

(data type data type) completed with file
processing errors - processed files files
with error files files skipped.

created for the specified node. However, during
processing errors were encountered accessing some files
- these files were skipped.
Failure validating database load:

expected numRecs records and numBV bit
vectors - loaded actNumRecs records and
actNumBV bit vectors.

and the number of records, the number of bit vectors,
or both the number of records or number of bit vectors
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
recover from this situation, first retry the database load
process. If the error reoccurs, check the activity log or
743
ANR4588E ANR8463E
other system logs to determine if there is a hardware or
media error. If a hardware or media error exists, correct
the error and retry the load process. If a hardware or
media error does not exist, it is likely the dump or
unload of the server database has encountered an error
resulting in the dump/unload server database image as
being unusable or that there is an error in the logic for
load db processing. Contact your service representative
for assistance.
ANR4588E
A database backup configuration might

be incorrect.
Explanation: A server database backup operation

failed. The server database backup and restore
explicit use of the client node name
$$_TSMDBMGR_$$.
System action: The database backup operation fails
and is ended.
User response: Verify that the configuration of the
dsm.sys file used by the Tivoli Storage Manager API
for the system where the server is installed. The server
stanza in the dsm.sys for the database backup must be
configured as follows:
ANR8300E

access door, make sure it is closed. The library
ANR8302E
v The server TCP/IP address is loopback (127.0.0.1).

v The server is configured to listen on the appropriate
TCP/IP port.
v The NODENAME option must specify
$$_TSMDBMGR_$$.
Refer to the installation and configuration topics in the
information center for this release. Specifically, review
the setup and configuration information for performing
a database backup for the server.
window size to TCPWindowsize for client
session. The default value will be used.

(OP=internal code, CC=internal code,
ASCQ=internal code, SENSE= sense data,
descriptions.
I/O error on drive drive name with

code, rc = return code, KEY= internal code,
ASC=internal code, ASCQ= internal code,
code descriptions.


for the indicated session to the requested size shown or
cannot set the rfc1323 attribute when the window size
is greater than 65535 bytes. The server uses the default
window size for the indicated session. There may be a
Explanation: The server has detected a write-protect

condition for the given volume.



User response: Adjust the write-protect switch on the

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
write permissions, at the operating system layer, for the
user who is starting the dsmserv process. If the volume
is an optical volume and the write-protect switch is
already set to allow writing, use the MOVE DATA
command to move the data off of the volume.
Rewritable volumes may be reformatted and reused
after the data is moved to another volume.
744
ANR8463E
Device type volume volume name is write

protected.
ANR8884W ANR8944E
ANR8884W
Attempted to label a written WORM

medium in the drive drive name with
code, KEY=internal code, ASC=internal
code, ASCQ=internal code, SENSE=sense
data, Description=error description). Refer
to the Tivoli Storage Manager
descriptions.
Explanation: An I/O error has occurred while labeling

on the written WORM medium.
User response: Ensure the WORM medium in the
drive is not a written WROM medium.
ANR8943E
A hardware or media error occurred

during an operation on library library
name (OP=internal code, CC=internal code,
description.
Explanation: A hardware or media error occurred

during an operation on the specified library.

that is associated with the library is identified correctly
in the DEFINE PATH command and that the library
device is turned on and ready. If the library has an
access door, make sure it is closed. If a cleaning
threshold is exceeded for a tape drive in this library,
clean the tape drive. For more information about the
values of the KEY, ASC, and ASCQ fields, see the
library and drive reference manuals.
ANR8944E
Hardware or media error on drive drive

name with volume volume
name(OP=internal code, Error Number=
internal code, CC=internal code,
descriptions.

while operating on the specified drive.

No ANR messages are deleted at version 6.3.3.
745
746
Chapter 4. Descriptions of I/O codes in server messages

Tivoli Storage Manager messages can contain I/O (input/output) codes. The codes
can be operation codes, completion codes, ASC and ASCQ codes.
This section contains code descriptions for I/O error messages from the Tivoli
Storage Manager server for the AIX, HP-UX, Solaris, Linux, and Windows
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 FSF (forward space file)
v WEOF (write end of file mark)
v A string of hex digits
See Device drivers operation codes: Tape library devices on page 752
for a list of operation codes.
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.
747
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

Tivoli Storage Manager device drivers provide operation codes and completion
codes. 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 performing the recommended action,
try the failing operation again.
Table 7. Completion code values common to all device classes
Decimal
Hexadecimal
200
748
Description
Recommended Action
X'C8'
The device indicated a failure condition,

but sense data was unavailable
Try the failing operation again.
201
X'C9'
Device driver failure
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.
204
X'CC'
Recovered from an I/O error; for your

information only
No action necessary.
205
X'CD'
SCSI adapter failure
Check for loose cables, bent pins, bad

cables, bad SCSI adapters, improper
termination, or bad terminators.
206
X'CE'
General SCSI failure
Check for loose cables, bent pins, bad

cables, bad SCSI adapters, improper
termination, or bad terminators.
207
X'CF'
Device cannot perform the requested

action
Ensure that the device is on and ready.

Ensure that the DEFINE DRIVE and
DEFINE DEVCLASS have been issued
properly.
208
X'D0'
Command stopped

Support.
Table 7. Completion code values common to all device classes (continued)

Decimal
Hexadecimal
Description
Recommended Action
209
X'D1'
Device microcode failure is detected
Check the microcode level of the drive.

Contact the drive manufacturer and
request the latest level.
210
X'D2'
The device was reset due to device

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.
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 8. Completion code values for media changers
Decimal
Hexadecimal
Description
Recommended Action
300
X'12C'
Cartridge entry/exit error
Check the entry/exit ports for a

jammed volume.
301
X'12D'
Cartridge load failure
Check the drive for jammed volumes.

On AIX, display the errpt to check for
hardware errors.
302
X'12E'
Cartridge in failed drive
Check the drive for jammed volumes.

hardware errors.
303
X'12F'
Carousel not loaded
Ensure that the carousel is correctly in

place and the door is shut.
304
X'130'
Changer failure

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

hardware errors.
307
X'133'
Entry/exit failure

Support.
308
X'134'
Entry/exit port not present

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.
Chapter 4. I/O code descriptions in server messages
749
Table 8. Completion code values for media changers (continued)

Decimal
Hexadecimal
Description
Recommended Action
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

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

an attempt to move a volume
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.
316
X'13C'
Cleaner cartridge installed

support.
317
X'13D'
Media not ejected

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

Support.
319
X'13F'
First destination empty

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

Support.
322
X'142'
Initialize range failed

Support.
Device drivers completion codes: Tape and optical drives

Tivoli Storage Manager device drivers provide completion codes that are specific to
tape and optical drives.
The following table shows completion code values for Tivoli Storage Manager
device drivers for tape and optical drives. 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 9. Completion code values for tape and optical drives
Decimal
400
750
Hexadecimal
X'190'
Description
Recommended Action
Physical end of media encountered
Ensure that the heads are clean on the

drive.
Table 9. Completion code values for tape and optical drives (continued)
Decimal
Hexadecimal
Description
Recommended Action
401
X'191'
End of data detected

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 requested is invalid
Internal server error. ContactTivoli

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
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'
Beginning of media encountered
414
X'19E'
Erase failure
Clean the drive heads.
415
X'19F'
Attempted to overwrite written WORM

media
Internal server error. ContactTivoli

416
X'1A0'
An incorrect length block was read.

hardware errors.
417
X'1A1'
Open read only
418
X'1A2'
Open write only
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'
Optical media error
Check operating system error logs for

hardware errors. Check for bad media.
424
X'1A8'
Encryption related error has occurred
Check your encryption setting on your

device class and tape drive.
425
X'1A9'
Decryption related error has occurred
Check your encryption setting on your

device class and tape drive.
425
X'1AA'
An external, encryption-related error has Check the encryption setting on your

occurred
device and tape drive.
751
Device drivers operation codes: Tape library devices

Tivoli Storage Manager device drivers provide operation codes for tape library
devices.
The following table shows the operation code values for tape library devices. The
table provides the two least significant bytes of the operation code. See the Tape
Library System Calls chapter in the IBM TotalStorage Tape Device Drivers Installation
and User's Guide for detailed information about operation codes.
Table 10. Operation code values for tape library devices
Hexadecimal
Name
Description
X'6D31'
MTIOCLM
Mount a volume on a specified drive.
X'6D32'
MTIOCLDM
Demount a volume on a specified drive.
X'6D34'
MTIOCLSVC
Change the category of a specified volume.
X'6D37'
MTIOCLQ
Return information about the tape library and its

contents.
X'6D38'
MTIOCLQMID
Query the status of the operation for a message ID.
X'6D38'
MTIOCLQMID
Query the status of the operation for a message ID.
X'6D39'
MTIOCLSDC
Assign a category to the automatic cartridge loader for a

specified device.
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 11. Descriptions of standard ASC and ASCQ codes
752
ASC
ASCQ
Description
0x00
0x00
No additional sense
0x00
0x01
Filemark detected
0x00
0x02
End-of-medium detected
0x00
0x03
Setmark detected
0x00
0x04
Beginning of medium
0x00
0x05
End of data
0x00
0x06
I/O process terminated
0x02
0x00
No seek complete
0x03
0x00
Device write fault
0x03
0x01
No write current
Table 11. Descriptions of standard ASC and ASCQ codes (continued)

ASC
ASCQ
Description
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

753
754
ASC
ASCQ
Description
0x24
0x00
Invalid field in CDB
0x25
0x00
LUN not supported
0x26
00
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
Invalid field in parameter list

ASC
ASCQ
Description
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.
755
756
Chapter 5. Device error codes in the AIX system error log

Tivoli Storage Manager logs some device errors in the AIX system error log.
This section describes the device codes in the AIX system error log. See AIX
Problem Solving Guide and Reference for a detailed description of the AIX error
logging facility and of the information contained in an error report.
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.
757

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.
758
Appendix. 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 following list includes the major accessibility features in the Tivoli Storage
Manager family of products:
v Keyboard-only operation
v Interfaces that are commonly used by screen readers
v Keys that are discernible by touch but do not activate just by touching them
v Industry-standard devices for ports and connectors
v The attachment of alternative input and output devices
The Tivoli Storage Manager Information Center, and its related publications, are
accessibility-enabled. For information about the accessibility features of the
information center, see the following topic: http://pic.dhe.ibm.com/infocenter/
tsminfo/v6r3/topic/com.ibm.help.ic.doc/iehs36_accessibility.html.
Keyboard navigation
On Windows, the Tivoli Storage Manager product family follows Microsoft
conventions for all keyboard navigation and access. Drag and Drop support is
managed by using the Microsoft Windows Accessibility option known as
MouseKeys. For more information about MouseKeys and other Windows
accessibility options, see the Windows online help, citing the keyword
MouseKeys.
On other operating systems, these products follow the operating-system
conventions for keyboard navigation and access.
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.
759
760
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
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 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 Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
761
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
762
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.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the

United States, other countries, or both and is used under license therefrom.
Notices
763
764
Glossary
This glossary includes terms and definitions for IBM Tivoli Storage Manager and IBM Tivoli Storage
FlashCopy Manager products.
To view glossaries for other IBM products, go to
http://www.ibm.com/software/globalization/
terminology/.
The following cross-references are used in this
glossary:
v See refers the reader from a term to a preferred
synonym, or from an acronym or abbreviation
to the defined full form.
v See also refers the reader to a related or
contrasting term.
A
absolute mode
In storage management, a backup
copy-group mode that specifies that a file
is considered for incremental backup even
if the file has not changed since the last
backup. See also modified mode.
access control list (ACL)
In computer security, a list associated
with an object that identifies all the
subjects that can access the object and
their access rights. For example, an access
control list is associated with a file that
identifies the users who can access that
file and their access rights.
access mode
An attribute of a storage pool or a storage
volume that specifies whether the server
can write to or read from the storage pool
or storage volume. The access mode can
be read/write, read-only, or unavailable.
Volumes in primary storage pools can
also have an access mode of destroyed.
Volumes in copy storage pools can also
have an access mode of offsite.
acknowledgment
The transmission of acknowledgment
characters as a positive response to a data
transmission.
ACL
See access control list.
activate
To validate the contents of a policy set
and then make it the active policy set.
active-data pool
A named set of storage pool volumes that
contain only active versions of client
backup data.
active file system
A file system to which space management
has been added. With space management,
tasks for an active file system include
automatic migration, reconciliation,
selective migration, and recall. Contrast
with inactive file system.
active policy set
The activated policy set that contains the
policy rules in use by all client nodes that
are assigned to the policy domain. See
also policy domain and policy set.
active version
The most recent backup copy of a file
stored. The active version of a file cannot
be deleted until a backup process detects
that the user has either replaced the file
with a newer version or has deleted the
file from the file server or workstation.
Contrast with inactive version.
activity log
A log that records normal activity
messages that are generated by the server.
These messages include information about
server and client operations, such as the
start time of sessions or device I/O errors.
adaptive subfile backup
A type of backup that sends only changed
portions of a file to the server, instead of
sending the entire file. Adaptive subfile
backup reduces network traffic and
increases the speed of the backup.
administrative client
A program that runs on a file server,
workstation, or mainframe that
administrators use to control and monitor
Contrast with backup-archive client.
administrative command schedule
A database record that describes the
765
planned processing of an administrative

command during a specific time period.
See also client schedule.
administrative privilege class
See privilege class.
administrative session
A period of time during which an
administrator user ID communicates with
a server to perform administrative tasks.
Contrast with client node session.
administrator
A user who is registered to the server as
an administrator, and who is authorized
to perform tasks and issue commands
through the assignment of an
administrative privilege class.
Advanced Program-to-Program Communication
(APPC)
An implementation of the SNA LU 6.2
protocol that allows interconnected
systems to communicate and share the
processing of programs.
archive copy
A file or group of files that was archived
to server storage.
archive copy group
A policy object containing attributes that
control the generation, destination, and
expiration of archived files.
archive-retention grace period
The number of days that the storage
manager retains an archived file when the
server is unable to rebind the file to an
appropriate management class. See also
bind.
association
(1) The defined relationship between a
client node and a client schedule. An
association identifies the name of a
schedule, the name of the policy domain
to which the schedule belongs, and the
name of a client node that performs
scheduled operations.
(2) On a configuration manager, the
defined relationship between a profile and
an object such as a policy domain. Profile
associations define the configuration
information that is distributed to a
managed server when it subscribes to the
profile.
agent node
A client node that has been granted proxy
authority to perform operations on behalf
of another client node, which is the target
node.
aggregate
An object, stored in one or more storage
pools, consisting of a group of logical files
that are packaged together. See also logical
file and physical file.
audit
aggregate data transfer rate

A performance statistic that indicates the
average number of bytes that were
transferred per second while processing a
given operation.
APPC See Advanced Program-to-Program
Communication.
application client
A program that is installed on a system to
protect an application. The Tivoli Storage
Manager server provides backup services
to an application client.
archive
To copy programs, data, or files to other
storage media, usually for long-term
storage or security. Contrast with retrieve.
766
To check for logical inconsistencies

between information that the server has
and the actual condition of the system.
The storage manager can audit
information about items such as volumes,
libraries, and licenses. For example, when
a storage manager audits a volume, the
server checks for inconsistencies between
information about backed-up or archived
files that are stored in the database and
the actual data that are associated with
each backup version or archive copy in
server storage.
authentication
The process of checking a user's password
before permitting user access to the Tivoli
Storage Manager server. Authentication
can be turned on or off by an
administrator with system privilege.
authentication rule
A specification that another user can use
to either restore or retrieve files from
storage.
authority
The right to access objects, resources, or
functions. See also privilege class.
authorization rule
A specification that permits another user
to either restore or retrieve a user's files
from storage.
authorized user
A user who has administrative authority
for the Tivoli Storage Manager client on a
workstation. This user changes
passwords, performs open registrations,
and deletes file spaces.
AutoFS
See automounted file system.
automatic detection
A feature that detects, reports, and
updates the serial number of a drive or
library in the database when the path
from the local server is defined.
automatic migration
The process that is used to automatically
move files from a local file system to
storage, based on options and settings
that are chosen by a root user on a
workstation. See also threshold migration
and demand migration.
automatic reconciliation
The process that is used to reconcile file
systems at regular intervals. The intervals
are set by a user with root user authority.
See also reconciliation.
automounted file system (AutoFS)
A file system that is managed by an
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. Contrast with administrative client.
backup copy group
control the generation, destination, and
expiration of backup versions of files. A
backup copy group belongs to a
management class.
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 server storage. More than
one backup version can exist in server
storage, but only one backup version is
the active version. See also active version
and inactive version.
bind
To associate all versions of a file with a

management class name. See rebind.
bindery
A database that consists of three system
files for a NetWare server. The files
contain user IDs and user restrictions.
C
cache
To place a duplicate copy of a file on

random access media when the server
migrates a file to another storage pool in
the hierarchy.
cache file
A snapshot of a logical volume created by
Logical Volume Snapshot Agent. Blocks
are saved immediately before they are
modified during the image backup and
their logical extents are saved in the cache
files.
CAD
See client acceptor.
central scheduler
A function that permits an administrator
to schedule client operations and
administrative commands. The operations
can be scheduled to occur periodically or
on a specific date. See client schedule and
administrative command schedule.
Glossary
767
client
A software program or computer that

requests services from a server.
client acceptor
An HTTP service that serves the applet
for the web client to web browsers. On
Windows systems, the client acceptor is
installed and run as a service. On AIX,
UNIX, and Linux systems, the client
acceptor is run as a daemon, and is also
called the client acceptor daemon (CAD).
client acceptor daemon (CAD)
See client acceptor.
client domain
The set of drives, file systems, or volumes
that the user selects to back up or archive
data, using the backup-archive client.
client node
A file server or workstation on which the
backup-archive client program has been
installed, and which has been registered
to the server.
client node session
A session in which a client node
communicates with a server to perform
backup, restore, archive, retrieve, migrate,
or recall requests. Contrast with
administrative session.
client options file
An editable file that identifies the server
and communication method, and
provides the configuration for backup,
archive, hierarchical storage management,
and scheduling.
client option set
A group of options that are defined on
the server and used on client nodes in
conjunction with client options files.
client-polling scheduling mode
A method of operation in which the client
queries the server for work. Contrast with
server-prompted scheduling mode.
client schedule
A database record that describes the
planned processing of a client operation
during a specific time period. The client
operation can be a backup, archive,
restore, or retrieve operation, a client
operating system command, or a macro.
See also administrative command schedule.
distributed data processing in which a

program on one computer sends a request
to a program on another computer and
awaits a response. The requesting
program is called a client; the answering
program is called a server.
client system-options file
A file, used on AIX, UNIX, or Linux
system clients, containing a set of
processing options that identify the
servers to be contacted for services. This
file also specifies communication methods
and options for backup, archive,
hierarchical storage management, and
scheduling. This file is also called the
dsm.sys file. See also client user-options file.
client user-options file
A file that contains the set of processing
options that the clients on the system use.
The set can include options that
determine the server that the client
contacts, and options that affect backup
operations, archive operations,
hierarchical storage management
operations, and scheduled operations.
This file is also called the dsm.opt file.
For AIX, UNIX, or Linux systems, see also
client system-options file.
closed registration
A registration process in which only an
administrator can register workstations as
client nodes with the server. Contrast
with open registration.
collocation
The process of keeping all data belonging
to a single-client file space, a single client
node, or a group of client nodes on a
minimal number of sequential-access
volumes within a storage pool.
Collocation can reduce the number of
volumes that must be accessed when a
large amount of data must be restored.
collocation group
A user-defined group of client nodes
whose data is stored on a minimal
number of volumes through the process
of collocation.
commit point
A point in time when data is considered
consistent.
client/server
Pertaining to the model of interaction in
768
Common Programming Interface for

Communications (CPI-C)
A call-level interface that provides a
consistent application programming
interface (API) for applications that use
program-to-program communications.
CPI-C uses LU 6.2 architecture to create a
set of interprogram services that can
establish and end a conversation, send
and receive data, exchange control
information, and notify a partner program
of errors.
communication method
The method by which a client and server
exchange information. See also
Transmission Control Protocol/Internet
Protocol.
communication protocol
A set of defined interfaces that permit
computers to communicate with each
other.
compression
A function that removes repetitive
characters, spaces, or strings of characters
from the data being processed and
replaces the repetitive characters with
control characters. Compression reduces
the amount of storage space that is
required for the data.
configuration manager
A server that distributes configuration
information, such as policies and
schedules, to managed servers according
to their profiles. Configuration
information can include policy and
schedules. See also managed server and
profile.
conversation
A connection between two programs over
a session that allows them to
communicate with each other while
processing a transaction.
copy backup
A full backup in which the transaction log
files are not deleted so that backup
procedures that use incremental or
differential backups are not disrupted
copy group
control how backup versions or archive
copies are generated, where backup
versions or archive copies are initially
located, and when backup versions or

archive copies expire. A copy group
belongs to a management class. See also
archive copy group, backup copy group,
backup version, and management class.
copy storage pool
A named set of volumes that contain
copies of files that reside in primary
storage pools. Copy storage pools are
used only to back up the data that is
stored in primary storage pools. A copy
storage pool cannot be a destination for a
backup copy group, an archive copy
group, or a management class (for
space-managed files). See also primary
storage pool and destination.
CPI-C See Common Programming Interface for
Communications.
D
daemon
A program that runs unattended to
perform continuous or periodic functions,
such as network control.
damaged file
A physical file in which Tivoli Storage
Manager has detected read errors.
data access control mode
A mode that controls whether a command
can access a migrated file, see a migrated
file as zero-length, or receive an
input/output error if it attempts to access
a migrated file. See also execution mode.
database backup series
One full backup of the database, plus up
to 32 incremental backups made since
that full backup. Each full backup that is
run starts a new database backup series.
A number identifies each backup series.
database snapshot
A complete backup of the entire database
to media that can be taken off-site. When
a database snapshot is created, the current
database backup series is not interrupted.
A database snapshot cannot have
incremental database backups associated
with it. See also database backup series.
Contrast with full backup.
data deduplication
A method of reducing storage needs by
eliminating redundant data. Only one
instance of the data is retained on storage
Glossary
769
media. Other instances of the same data

are replaced with a pointer to the retained
instance.
data manager server
A server that collects metadata
information for client inventory and
manages transactions for the storage
agent over the local area network. The
data manager server informs the storage
agent with applicable library attributes
and the target volume identifier.
data mover
A device that moves data on behalf of the
server. A network-attached storage (NAS)
file server is a data mover.
data storage-management applicationprogramming interface (DSMAPI)
A set of functions and semantics that can
monitor events on files, and manage and
maintain the data in a file. In an HSM
environment, a DSMAPI uses events to
notify data management applications
about operations on files, stores arbitrary
attribute information with a file, supports
managed regions in a file, and uses
DSMAPI access rights to control access to
a file object.
deduplication
See data deduplication.
default management class
A management class that is assigned to a
policy set. This class is used to govern
backed up or archived files when a file is
not explicitly associated with a specific
management class through the
include-exclude list.
demand migration
The process that is used to respond to an
out-of-space condition on a file system for
which hierarchical storage management
(HSM) is active. Files are migrated to
server storage until space usage drops to
the low threshold that was set for the file
system. If the high threshold and low
threshold are the same, one file is
migrated.
desktop client
The group of backup-archive clients that
includes clients on Microsoft Windows,
Apple, and Novell NetWare operating
systems.
770
destination
A copy group or management class
attribute that specifies the primary storage
pool to which a client file will be backed
up, archived, or migrated.
device class
A named set of characteristics that are
applied to a group of storage devices.
Each device class has a unique name and
represents a device type of disk, file,
optical disk, or tape.
device configuration file
(1) For a server, a file that contains
information about defined device classes,
and, on some servers, defined libraries
and drives. The information is a copy of
the device configuration information in
the database.
(2) For a storage agent, a file that contains
the name and password of the storage
agent, and information about the server
that is managing the SAN-attached
libraries and drives that the storage agent
uses.
device driver
A program that provides an interface
between a specific device and the
application program that uses the device.
disaster recovery manager (DRM)
A function that assists in preparing and
using a disaster recovery plan file for the
server.
disaster recovery plan
A file that is created by the disaster
recovery manager (DRM) that contains
information about how to recover
computer systems if a disaster occurs and
scripts that can be run to perform some
recovery tasks. The file includes
information about the software and
hardware that is used by the server, and
the location of recovery media.
domain
A grouping of client nodes with one or
more policy sets, which manage data or
storage resources for the client nodes. See
policy domain or client domain.
DRM
See disaster recovery manager.
DSMAPI
See data storage-management
application-programming interface.
dynamic serialization
A type of copy serialization in which a
file or folder is backed up or archived on
the first attempt regardless of whether it
changes during a backup or archive.
E
EA
See extended attribute.
EB
See exabyte.
EFS
See Encrypted File System.
exabyte (EB)
For processor storage, real and virtual
storage, and channel volume, 1 152 921
504 606 846 976 bytes. For disk storage
capacity and communications volume, 1
000 000 000 000 000 000 bytes.
exclude
The process of identifying files in an
include-exclude list. This process prevents
the files from being backed up or
migrated whenever a user or schedule
enters an incremental or selective backup
operation. A file can be excluded from
backup and space management, backup
only, or space management only.
Encrypted File System (EFS)

A file system that uses file system-level
encryption.
enterprise configuration
A method of setting up servers so that the
administrator can distribute the
configuration of one of the servers to the
other servers, using server-to-server
communication. See also configuration
manager, managed server, profile, and
subscription.
enterprise logging
The process of sending events from a
Tivoli Storage Manager server to a
designated event server. The event server
routes the events to designated receivers,
such as to a user exit. See also event.
error log
A data set or file that is used to record
error information about a product or
system.
estimated capacity
The available space, in megabytes, of a
storage pool.
event
(1) An administrative command or a

client operation that is scheduled to be
run using Tivoli Storage Manager
scheduling.
(2) A message that an Tivoli Storage
Manager server or client issues. Messages
can be logged using Tivoli Storage
Manager event logging.
event record
A database record that describes actual
status and results for events.
event server
A server to which other servers can send
events for logging. The event server
routes the events to any receivers that are
enabled for the sending server's events.
exclude-include list
See include-exclude list.
execution mode
A mode that controls the
space-management related behavior of
commands that run under the dsmmode
command.
expiration
The process by which files, data sets, or
objects are identified for deletion because
their expiration date or retention period
has passed.
expiring file
A migrated or premigrated file that has
been marked for expiration and removal
from storage. If a stub file or an original
copy of a premigrated file is deleted from
a local file system, or if the original copy
of a premigrated file is updated, the
corresponding migrated or premigrated
file is marked for expiration the next time
reconciliation is run.
extend
To increase the portion of available space
that can be used to store database or
recovery log information.
extended attribute (EA)
Names or value pairs that are associated
with files or directories. There are three
classes of extended attributes: user
attributes, system attributes, and trusted
attributes.
extent The part of a file that is created during
the data-deduplication process. Extents
are compared with other file extents to
identify duplicates.
Glossary
771
external library
A type of library that is provided by
Tivoli Storage Manager that permits
LAN-free data movement for StorageTek
libraries that are managed by Automated
Cartridge System Library Software
(ACSLS). To activate this function, the
Tivoli Storage Manager library type must
be EXTERNAL.
F
file access time
On AIX, UNIX, or Linux systems, the
time when the file was last accessed.
file age
For migration prioritization purposes, the
number of days since a file was last
accessed.
file device type
A device type that specifies the use of
sequential access files on disk storage as
volumes.
management support that is required. If

no space management support is
required, the operation is passed to the
operating system, which performs its
normal functions. The file system
migrator is mounted over a file system
when space management is added to the
file system.
file system state
The storage management mode of a file
system that resides on a workstation on
which the hierarchical storage
management (HSM) client is installed. A
file system can be in one of these states:
native, active, inactive, or global inactive.
frequency
A copy group attribute that specifies the
minimum interval, in days, between
incremental backups.
FSID
See file space ID.
FSM
See file system migrator.
file server
A dedicated computer and its peripheral
storage devices that are connected to a
local area network that stores programs
and files that are shared by users on the
network.
full backup
The process of backing up the entire
server database. A full backup begins a
new database backup series. See also
database backup series and incremental
backup. Contrast with database snapshot.
file space
A logical space in server storage that
contains a group of files that have been
backed up or archived by a client node,
from a single logical partition, file system,
or virtual mount point. Client nodes can
restore, retrieve, or delete their file spaces
from server storage. In server storage,
files belonging to a single file space are
not necessarily stored together.
fuzzy backup
A backup version of a file that might not
accurately reflect what is currently in the
file because the file was backed up at the
same time as it was being modified.
file space ID (FSID)

A unique numeric identifier that the
server assigns to a file space when it is
stored in server storage.
file state
The space management mode of a file
that resides in a file system to which
space management has been added. A file
can be in one of three states: resident,
premigrated, or migrated. See also resident
file, premigrated file, and migrated file.
file system migrator (FSM)
A kernel extension that intercepts all file
system operations and provides any space
772
fuzzy copy
A backup version or archive copy of a file
that might not accurately reflect the
original contents of the file because it was
backed up or archived the file while the
file was being modified. See also backup
version and archive copy.
G
General Parallel File System
A high-performance shared-disk file
system that can provide data access from
nodes in a cluster environment.
gigabyte (GB)
In decimal notation, 1 073 741 824 when
referring to memory capacity; in all other
cases, it is defined as 1 000 000 000.
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. When space
management is globally deactivated,
hierarchical storage management (HSM)
cannot perform migration, recall, or
reconciliation. However, a root user can
update space management settings and
add space management to additional file
systems. Users can access resident and
premigrated files.
Globally Unique Identifier (GUID)
An algorithmically determined number
that uniquely identifies an entity within a
system.
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
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.
hierarchical storage management (HSM) client
A client program that works with the
Tivoli Storage Manager server to provide
for a system. See also hierarchical storage
management and space manager client.
HSM
See hierarchical storage management.
HSM client
See hierarchical storage management client.
I
ILM
See information lifecycle management.
image A file system or raw logical volume that

is backed up as a single object.
image backup
A backup of a full file system or raw
logical volume as a single object.
inactive file system
A file system for which space
management has been deactivated.
Contrast with active file system.
inactive version
A backup version of a file that is either
not the most recent backup version, or
that is a backup version of a file that no
longer exists on the client system. Inactive
backup versions are eligible for expiration
processing according to the management
class assigned to the file. Contrast with
active version.
include-exclude file
A file containing statements to determine
the files to back up and the associated
management classes to use for backup or
archive. See also include-exclude list.
include-exclude list
A list of options that include or exclude
selected files for backup. An exclude
option identifies files that should not be
backed up. An include option identifies
files that are exempt from the exclusion
rules or assigns a management class to a
file or a group of files for backup or
archive services.
incremental backup
(1) A copy of all database data that has
changed since the most recent successful
full backup operation. An incremental
backup is also known as a cumulative
backup image because each incremental
backup includes the contents of the
previous incremental backup.
(2) The process of backing up information
in the database that is new or changed
since the last full backup. Contrast with
full backup. See also database backup series.
(3) For Data Protection for Microsoft
Exchange Server, a backup in which the
transaction logs are backed up and then
cleared.
individual mailbox restore
See mailbox restore.
information lifecycle management (ILM)
GPFS policy-based file management for
storage pools and file sets.
Glossary
773
inode The internal structure that describes the

individual files on AIX, UNIX, or Linux
systems. An inode contains the node,
type, owner, and location of a file.
inode number
A number specifying a particular inode
file in the file system.
IP address
A unique address for a device or logical
unit on a network that uses the IP
standard.
LAN-free data transfer

See LAN-free data movement.
leader data
Bytes of data, from the beginning of a
migrated file, that are stored in the file's
corresponding stub file on the local file
system. The amount of leader data that is
stored in a stub file depends on the stub
size that is specified.
library
(1) A repository for demountable recorded
media, such as magnetic disks and
magnetic tapes.
J
job file
A generated file that contains
configuration information for a migration
job. The file is XML format and can be
created and edited in the hierarchical
storage management (HSM) client for
Windows client graphical user interface.
journal-based backup
A method for backing up Windows clients
and AIX clients that exploits the change
notification mechanism in a file to
improve incremental backup performance
by reducing the need to fully scan the file
system.
journal daemon
On AIX, UNIX, or Linux systems, a
program that tracks change activity for
files residing in file systems.
(2) A collection of one or more drives, and

possibly robotic devices (depending on
the library type), which can be used to
access storage volumes.
library client
A server that uses server-to-server
communication to access a library that is
managed by another storage management
server. See also library manager.
library manager
A server that controls device operations
when multiple storage management
servers share a storage device. See also
library client.
local
journal service
In Microsoft Windows, a program that
tracks change activity for files residing in
file systems.
K
kilobyte (KB)
For processor storage, real and virtual
storage, and channel volume, 210 or 1 024
bytes. For disk storage capacity and
communications volume, 1 000 bytes.
L
LAN
See local area network.
LAN-free data movement

The movement of client data between a
client system and a storage device on a
storage area network (SAN), bypassing
the local area network. This process is
also referred to as LAN-free data transfer.
(1) Pertaining to a device, file, or system

that is accessed directly from a user
system, without the use of a
communication line.
(2) For HSM products, pertaining to the
destination of migrated files that are
being moved.
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.
local shadow volumes
Data that is stored on shadow volumes
localized to a disk storage subsystem.
LOFS See loopback virtual file system.
logical file
A file that is stored in one or more server
storage pools, either by itself or as part of
an aggregate. See also aggregate and
physical file.
logical occupancy
The space that is used by logical files in a
774
storage pool. This space does not include

the unused space created when logical
files are deleted from aggregate files, so it
might be less than the physical
occupancy.
logical unit (LU)
An access point through which a user or
application program accesses the Systems
Network Architecture (SNA) network to
communicate with another user or
application program.
logical unit number (LUN)
In the Small Computer System Interface
(SCSI) standard, a unique identifier that is
used to differentiate devices, each of
which is a logical unit (LU).
logical volume
A portion of a physical volume that
contains a file system.
logical volume backup
A backup of a file system or logical
volume as a single object.
Logical Volume Snapshot Agent (LVSA)
Software that can act as the snapshot
provider for creating a snapshot of a
logical volume during an online image
backup.
loopback virtual file system (LOFS)
A file system that is created by mounting
a directory over another local directory,
also known as mount-over-mount. A
LOFS can also be generated using an
automounter.
LU
See logical unit.
LUN
See logical unit number.
LVSA See Logical Volume Snapshot Agent.

M
macro file
A file that contains one or more storage
manager administrative commands,
which can be run only from an
administrative client using the MACRO
command. Contrast with Tivoli Storage
Manager command script.
mailbox restore
A function that restores Microsoft
Exchange Server data (from IBM Data
Protection for Microsoft Exchange
backups) at the mailbox level or
mailbox-item level.
managed object
In Tivoli Storage Manager, a definition in
the database of a managed server that
was distributed to the managed server by
a configuration manager. When a
managed server subscribes to a profile, all
objects that are associated with that
profile become managed objects in the
database of the managed server. In
general, a managed object cannot be
modified locally on the managed server.
Objects can include policy, schedules,
client option sets, server scripts,
administrator registrations, server
definitions, and server group definitions.
managed server
A Tivoli Storage Manager server that
receives configuration information from a
configuration manager using a
subscription to one or more profiles.
Configuration information can include
definitions of objects such as policy and
schedules. See also configuration manager,
subscription, and profile.
management class
A policy object that users can bind to each
file to specify how the server manages the
file. The management class can contain a
backup copy group, an archive copy
group, and space management attributes.
See also copy group, space manager client,
bind, and rebind.
maximum transmission unit
The largest possible unit of data that can
be sent on a given physical medium in a
single frame. For example, the maximum
transmission unit for Ethernet is 1500
bytes.
MB
See megabyte.
media server
In a z/OS environment, a program that
provides access to z/OS disk and tape
storage for Tivoli Storage Manager servers
that run on operating systems other than
z/OS.
megabyte (MB)
(1) 1 048 576 bytes (2 to the 20th power)
when used in this publication.
(2) For processor storage, real and virtual
storage, and channel volume, 2 to the
power of 20 or 1 048 576 bits. For disk
Glossary
775
storage capacity and communications

volume, 1 000 000 bits.
metadata
Data that describes the characteristics of
data; descriptive data.
migrate
To move data from one storage location to
another. In Tivoli Storage Manager
products, migrating can mean moving
data from a client node to server storage,
or moving data from one storage pool to
the next storage pool defined in the
server storage hierarchy. In both cases the
movement is controlled by policy, such as
thresholds that are set. See also migration
threshold.
migrated file
A file that has been copied from a local
file system to Tivoli Storage Manager
storage. For HSM clients on UNIX or
Linux systems, the file is replaced with a
stub file on the local file system. On
Windows systems, creation of the stub file
is optional. See also stub file and resident
file. For HSM clients on UNIX or Linux
systems, contrast with premigrated file.
migrate-on-close recall mode
A mode that causes a migrated file to be
recalled back to its originating file system
temporarily. Contrast with normal recall
mode and read-without-recall recall mode.
migration job
A specification of files to migrate, and
actions to perform on the original files
after migration. See also job file.
migration threshold
High and low capacities for storage pools
or file systems, expressed as percentages,
at which migration is set to start and
stop.
mirroring
The process of writing the same data to
multiple locations at the same time.
Mirroring data protects against data loss
within the recovery log.
mode
A copy group attribute that specifies

whether to back up a file that has not
been modified since the last time the file
was backed up. See modified mode and
absolute mode.
modified mode
In storage management, a backup
copy-group mode that specifies that a file
is considered for incremental backup only
if it has changed since the last backup. A
file is considered a changed file if the
date, size, owner, or permissions of the
file have changed. See also absolute mode.
mount limit
The maximum number of volumes that
can be simultaneously accessed from the
same device class. The mount limit
determines the maximum number of
mount points. See also mount point.
mount point
On the Tivoli Storage Manager server, a
logical drive through which volumes in a
sequential access device class are
accessed. For removable-media device
types, such as tape, a mount point is a
logical drive that is associated with a
physical drive. For the file device type, a
mount point is a logical drive that is
associated with an I/O stream. The
number of mount points for a device class
is defined by the value of the mount limit
attribute for that device class. See also
mount limit.
mount retention period
The maximum number of minutes that
the server retains a mounted
sequential-access media volume that is
not being used before it dismounts the
sequential-access media volume.
mount wait period
The maximum number of minutes that
the server waits for a sequential-access
volume mount request to be satisfied
before canceling the request.
MTU
N
Nagle algorithm
An algorithm that reduces congestion of
TCP/IP networks by combining smaller
packets and sending them together.
named pipe
A type of interprocess communication
that permits message data streams to pass
between peer processes, such as between
a client and a server.
NAS
776
See maximum transmission unit.
See network-attached storage.
NAS node
A client node that is a network-attached
storage (NAS) file server. Data for the
NAS node is transferred by a NAS file
server that is controlled by the network
data management protocol (NDMP). A
NAS node is also called a NAS file server
node.
native file system
A file system that is locally added to the
file server and is not added for space
management. The hierarchical storage
manager (HSM) client does not provide
space management services to the file
system.
native format
A format of data that is written to a
storage pool directly by the Tivoli Storage
Manager server. Contrast with non-native
data format.
NDMP
See Network Data Management Protocol.
NetBIOS
See Network Basic Input/Output System.
network-attached storage (NAS) file server
A dedicated storage device with an
operating system that is optimized for
file-serving functions. A NAS file server
can have the characteristics of both a
node and a data mover.
Network Basic Input/Output System (NetBIOS)
A standard interface to networks and
personal computers that is used on local
area networks to provide message,
print-server, and file-server functions.
Application programs that use NetBIOS
do not have to handle the details of LAN
data link control (DLC) protocols.
Network Data Management Protocol (NDMP)
A protocol that allows a network
storage-management application to
control the backup and recovery of an
NDMP-compliant file server, without
installing vendor-acquired software on
that file server.
network data-transfer rate
A rate that is calculated by dividing the
total number of bytes that are transferred
by the data transfer time. For example,
this rate can be the time that is spent
transferring data over a network.
node
A file server or workstation on which the

backup-archive client program has been
installed, and which has been registered
to the server.
node name
A unique name that is used to identify a
workstation, file server, or PC to the
server.
node privilege class
A privilege class that gives an
administrator the authority to remotely
access backup-archive clients for a specific
client node or for all clients in a policy
domain. See also privilege class.
non-native data format
A format of data that is written to a
storage pool that differs from the format
that the server uses for operations.
normal recall mode
A mode that causes a migrated file to be
copied back to its originating file system
when it is accessed.
O
offline volume backup
A backup in which the volume is locked
so that no other system applications can
access it during the backup operation.
online volume backup
A backup in which the volume is
available to other system applications
during the backup operation.
open registration
A registration process in which users can
register their workstations as client nodes
with the server. Contrast with closed
registration.
operator privilege class
administrator the authority to disable or
halt the server, enable the server, cancel
server processes, and manage removable
media. See also privilege class.
options file
A file that contains processing options. On
Windows and NetWare systems, the file is
called dsm.opt. On AIX, UNIX, Linux,
and Mac OS X systems, the file is called
dsm.sys.
originating file system
The file system from which a file was
Glossary
777
migrated. When a file is recalled using

normal or migrate-on-close recall mode, it
is always returned to its originating file
system.
orphaned stub file
A file for which no migrated file can be
found on the Tivoli Storage Manager
server that the client node is contacting
for space management services. For
example, a stub file can be orphaned
when the client system-options file is
modified to contact a server that is
different than the one to which the file
was migrated.
out-of-space protection mode
A mode that controls whether the
program intercepts out-of-space
conditions. See also execution mode.
P
mover (such as a network-attached

storage [NAS] file server), and an
example of a destination is a tape drive.
pattern-matching character
See wildcard character.
physical file
A file that is stored in one or more
storage pools, consisting of either a single
logical file, or a group of logical files that
are packaged together as an aggregate.
See also aggregate and logical file.
physical occupancy
The amount of space that is used by
physical files in a storage pool. This space
includes the unused space that is created
when logical files are deleted from
aggregates. See also physical file, logical file,
and logical occupancy.
plug-in
A self-contained software component that
modifies (adds, or changes) the function
in a particular system. When a plug-in is
added to a system, the foundation of the
original system remains intact.
pacing
In SNA, a technique by which the
receiving system controls the rate of
transmission of the sending system to
prevent overrun.
packet In data communication, a sequence of
binary digits, including data and control
signals, that is transmitted and switched
as a composite whole.
page
A defined unit of space on a storage

medium or within a database volume.
partial-file recall mode

A recall mode that causes the hierarchical
storage management (HSM) function to
read just a portion of a migrated file from
storage, as requested by the application
accessing the file.
password generation
A process that creates and stores a new
password in an encrypted password file
when the old password expires.
Automatic generation of a password
prevents password prompting. Password
generation can be set in the options file
(passwordaccess option). See also options
file.
path
778
An object that defines a one-to-one

relationship between a source and a
destination. Using the path, the source
accesses the destination. Data can flow
from the source to the destination, and
back. An example of a source is a data
policy domain
A grouping of policy users with one or
more policy sets, which manage data or
storage resources for the users. The users
are client nodes that are associated with
the policy domain.
policy privilege class
administrator the authority to manage
policy objects, register client nodes, and
schedule client operations for client
nodes. Authority can be restricted to
certain policy domains. See also privilege
class.
policy set
A group of rules in a policy domain. The
rules specify how data or storage
resources are automatically managed for
client nodes in the policy domain. Rules
can be contained in management classes.
See also active policy set and management
class.
premigrated file
A file that has been copied to Tivoli
Storage Manager storage, but has not
been replaced with a stub file on the local
file system. An identical copy of the file
resides both on the local file system and
in Tivoli Storage Manager storage.

Premigrated files occur on UNIX and
Linux file systems to which space
management has been added. Contrast
with migrated file and resident file.
premigrated files database
A database that contains information
about each file that has been premigrated
to Tivoli Storage Manager storage. The
database is stored in a hidden directory
named .SpaceMan in each file system to
which space management has been
added.
premigration
The process of copying files that are
eligible for migration to Tivoli Storage
Manager storage, but leaving the original
file intact on the local file system.
premigration percentage
A space management setting that controls
whether the next eligible candidates in a
file system are premigrated following
threshold or demand migration.
primary storage pool
A named set of volumes that the server
uses to store backup versions of files,
archive copies of files, and files migrated
from client nodes. See also destination and
copy storage pool.
privilege class
A level of authority that is granted to an
administrator. The privilege class
determines which administrative tasks the
administrator can perform. See also node
privilege class, operator privilege class, policy
privilege class, storage privilege class, and
system privilege class.
profile
A named group of configuration
information that can be distributed from a
configuration manager when a managed
server subscribes. Configuration
information can include registered
administrator IDs, policies, client
schedules, client option sets,
administrative schedules, storage manager
command scripts, server definitions, and
server group definitions. See also
configuration manager and managed server.
Q
amount of data that can be migrated and

premigrated from a file system to server
storage.
(2) For HSM on Windows systems, a
user-defined limit to the space that is
occupied by recalled files.
R
randomization
The process of distributing schedule start
times for different clients within a
specified percentage of the schedule's
startup window.
raw logical volume
A portion of a physical volume that is
comprised of unallocated blocks and has
no journaled file system (JFS) definition.
A logical volume is read/write accessible
only through low-level I/O functions.
read-without-recall recall mode
A mode that causes hierarchical storage
management (HSM) to read a migrated
file from storage without storing it back
on the local file system. The last piece of
information read from the file is stored in
a buffer in memory on the local file
system. Contrast with normal recall mode
and migrate-on-close recall mode.
rebind
To associate all backed-up versions of a
file with a new management class name.
For example, a file that has an active
backup version is rebound when a later
version of the file is backed up with a
different management class association.
See also bind.
recall
In Tivoli Storage Manager, to copy a

migrated file from server storage back to
its originating file system using the space
management client. See also transparent
recall, selective recall, and recall mode.
recall mode
A mode that is assigned to a migrated file
with the dsmattr command that
determines how the file is processed
when it is recalled. It determines whether
the file is stored on the local file system,
is migrated back to Tivoli Storage
Manager storage when it is closed, or is
read from Tivoli Storage Manager storage
without storing it on the local file system.
quota (1) For HSM on AIX, UNIX, or Linux

systems, the limit (in megabytes) on the
Glossary
779
receiver
A server repository that contains a log of
server and client messages as events. For
example, a receiver can be a file exit, a
user exit, or the Tivoli Storage Manager
server console and activity log. See also
event.
reclamation
The process of consolidating the
remaining data from many
sequential-access volumes onto fewer,
new sequential-access volumes.
reclamation threshold
The percentage of space that a
sequential-access media volume must
have before the server can reclaim the
volume. Space becomes reclaimable when
files are expired or are deleted.
reconciliation
The process of synchronizing a file system
with the Tivoli Storage Manager server,
and then removing old and obsolete
objects from the Tivoli Storage Manager
server.
recovery log
A log of updates that are about to be
written to the database. The log can be
used to recover from system and media
failures. The recovery log consists of the
active log (including the log mirror) and
archive logs.
register
To define a client node or administrator
ID that can access the server.
registry
A repository that contains access and
configuration information for users,
systems, and software.
remote
(1) Pertaining to a system, program, or
device that is accessed through a
communication line.
(2) For HSM products, pertaining to the
origin of migrated files that are being
moved.
resident file
On a Windows system, a complete file on
a local file system that might also be a
migrated file because a migrated copy can
exist in Tivoli Storage Manager storage.
On a UNIX or Linux system, a complete
780
file on a local file system that has not

been migrated or premigrated, or that has
been recalled from Tivoli Storage Manager
storage and modified. Contrast with stub
file and premigrated file. See migrated file.
restore
To copy information from its backup
location to the active storage location for
use. For example, to copy information
from server storage to a client
workstation.
retention
The amount of time, in days, that inactive
backed-up or archived files are kept in the
storage pool before they are deleted.
Copy group attributes and default
retention grace periods for the domain
define retention.
retrieve
To copy archived information from the
storage pool to the workstation for use.
The retrieve operation does not affect the
archive version in the storage pool.
roll back
To remove changes that were made to
database files since the last commit point.
root user
A system user who operates without
restrictions. A root user has the special
rights and privileges needed to perform
administrative tasks.
S
SAN
See storage area network.
schedule
A database record that describes client
operations or administrative commands to
be processed. See administrative command
schedule and client schedule.
scheduling mode
The type of scheduling operation for the
server and client node that supports two
scheduling modes: client-polling and
server-prompted.
scratch volume
A labeled volume that is either blank or
contains no valid data, that is not defined,
and that is available for use.
script
A series of commands, combined in a file,

that carry out a particular function when
the file is run. Scripts are interpreted as
they are run. Contrast with Tivoli Storage

Manager command script.
Secure Sockets Layer (SSL)
A security protocol that provides
communication privacy. With SSL,
client/server applications can
communicate in a way that is designed to
prevent eavesdropping, tampering, and
message forgery.
selective backup
The process of backing up certain files or
directories from a client domain. The files
that are backed up are those that are not
excluded in the include-exclude list. The
files must meet the requirement for
serialization in the backup copy group of
the management class that is assigned to
each file. Contrast with incremental backup.
selective migration
The process of copying user-selected files
from a local file system to Tivoli Storage
Manager storage and replacing the files
with stub files on the local file system.
Contrast with threshold migration and
demand migration.
selective recall
The process of copying user-selected files
from Tivoli Storage Manager storage to a
local file system. Contrast with transparent
recall.
serialization
The process of handling files that are
modified during backup or archive
processing. See dynamic serialization, static
serialization, shared static serialization, and
shared dynamic serialization.
server A software program or a computer that
provides services to other software
programs or other computers.
server options file
A file that contains settings that control
various server operations. These settings
affect such things as communications,
devices, and performance.
server-prompted scheduling mode
A client/server communication technique
where the server contacts the client node
when tasks must be done. Contrast with
client-polling scheduling mode.
server storage
The primary, copy, and active-data storage
pools that are used by the server to store

user files such as backup versions, archive
copies, and files migrated from space
manager client nodes (space-managed
files). See also active-data pool, primary
storage pool, copy storage pool, storage pool
volume, and volume.
session
A logical or virtual connection between
two stations, software programs, or
devices on a network that allows the two
elements to communicate and exchange
data.
session resource usage
The amount of wait time, processor time,
and space that is used or retrieved during
a client session.
shared dynamic serialization
A value for serialization that specifies that
a file must not be backed up or archived
if it is being modified during the
operation. Tivoli Storage Manager retries
the backup or archive operation a number
of times; if the file is being modified
during each attempt, Tivoli Storage
Manager will back up or archive the file
on its last try. See also serialization.
Contrast with dynamic serialization, shared
static serialization, and static serialization.
shared library
A library device that is used by multiple
storage manager servers.
shared static serialization
A copy-group serialization value that
specifies that a file must not be modified
during a backup or archive operation.
Tivoli Storage Manager attempts to retry
the operation a number of times. If the
file is in use during each attempt, the file
is not backed up or archived. See also
serialization. Contrast with dynamic
serialization, shared dynamic serialization,
and static serialization.
snapshot
An image backup type that consists of a
point-in-time view of a volume.
space-managed file
A file that is migrated from a client node
by the space manager client. The space
manager client recalls the file to the client
node on demand.
Glossary
781
during a backup or archive operation. If

the file is in use during the first attempt,
the storage manager cannot back up or
archive the file. See also serialization.
Contrast with dynamic serialization, shared
dynamic serialization, and shared static
serialization.
space management
The process of keeping sufficient free
storage space available on a local file
system for new data by migrating files to
server storage. Synonymous with
hierarchical storage management.
space manager client
A program that runs on a UNIX or Linux
system to manage free space on the local
file system by migrating files to server
storage. The program can recall the files
either automatically or selectively. Also
called hierarchical storage management
(HSM) client.
space monitor daemon
A daemon that checks space usage on all
file systems for which space management
is active, and automatically starts
threshold migration when space usage on
a file system equals or exceeds its high
threshold.
sparse file
A file that is created with a length greater
than the data it contains, leaving empty
spaces for the future addition of data.
special file
On AIX, UNIX, or Linux systems, a file
that defines devices for the system, or
temporary files that are created by
processes. There are three basic types of
special files: first-in, first-out (FIFO);
block; and character.
SSL
storage agent
A program that enables the backup and
restoration of client data directly to and
from storage attached to a storage area
network (SAN).
storage area network (SAN)
A dedicated storage network that is
tailored to a specific environment,
combining servers, systems, storage
products, networking products, software,
and services.
storage hierarchy
(1) A logical order of primary storage
pools, as defined by an administrator. The
order is typically based on the speed and
capacity of the devices that the storage
pools use. The storage hierarchy is
defined by identifying the next storage
pool in a storage pool definition. See also
storage pool.
(2) An arrangement of storage devices
with different speeds and capacities. The
levels of the storage hierarchy include:
main storage, such as memory and
direct-access storage device (DASD)
cache; primary storage (DASD containing
user-accessible data); migration level 1
(DASD containing data in a space-saving
format); and migration level 2 (tape
cartridges containing data in a
space-saving format).
See Secure Sockets Layer.
stabilized file space

A file space that exists on the server but
not on the client.
stanza A group of lines in a file that together
have a common function or define a part
of the system. Each stanza is identified by
a name that occurs in the first line of the
stanza. Depending on the type of file, a
stanza is ended by the next occurrence of
a stanza name in the file, or by an explicit
end-of-stanza marker. A stanza can also
be ended by the end of the file.
startup window
A time period during which a schedule
must be initiated.
static serialization
A copy-group serialization value that
specifies that a file must not be modified
782
storage pool
A named set of storage volumes that are
the destination that is used to store client
data. A storage pool contains backup
versions, archive copies, and files that are
migrated from space manager client
nodes. A primary storage pool is backed
up to a copy storage pool. See also
primary storage pool, copy storage pool, and
active-data pool.
storage pool volume
A volume that has been assigned to a
storage pool. See also volume, active-data
pool, copy storage pool, and primary storage
pool.
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 Tivoli Storage Manager
storage. It also contains additional
information that can be used to eliminate
the need to recall a migrated 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 Tivoli Storage Manager
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 Tivoli environment, the process of
identifying the subscribers that the
profiles are distributed to. For Tivoli
Storage Manager, a subscription is the
process by which a managed server
receives configuration information
associated with a particular profile on a
configuration manager. See also managed
server, configuration manager, and profile.
system privilege class
administrator the authority to issue all
server commands. See also privilege class.
Systems Network Architecture (SNA)
The description of the logical structure,
formats, protocols, and operational
sequences for transmitting information
through and controlling the configuration
and operation of networks.
T
tape library
A set of equipment and facilities that
support an installation's tape
environment. The tape library can include
tape storage racks, mechanisms for
automatic tape mounting, a set of tape
drives, and a set of related tape volumes
mounted on those drives.
tape volume prefix
The high-level-qualifier of the file name
or the data set name in the standard tape
label.
target node
A client node for which other client nodes
(called agent nodes) have been granted
proxy authority. The proxy authority
allows the agent nodes to perform
operations such as backup and restore on
behalf of the target node, which owns the
data.
TCA
See trusted communications agent.
TCP/IP
See Transmission Control Protocol/Internet
Protocol.
threshold migration
The process of moving files from a local
file system to Tivoli Storage Manager
storage based on the high and low
thresholds that are defined for the file
system. Contrast with demand migration,
selective migration, and migration job.
throughput
In storage management, the total bytes in
the workload, excluding overhead, that
are backed up or restored, divided by
elapsed time.
timeout
A time interval that is allotted for an
event to occur or complete before
operation is interrupted.
timestamp control mode
A mode that determines whether
commands preserve the access time for a
file or set it to the current time.
Tivoli Storage Manager command script
A sequence of Tivoli Storage Manager
administrative commands that are stored
in the database of the Tivoli Storage
Manager server. The script can run from
any interface to the server. The script can
Glossary
783
include substitution for command

parameters and conditional logic.
tombstone object
A small subset of attributes of a deleted
object. The tombstone object is retained
for a specified period, and at the end of
the specified period, the tombstone object
is permanently deleted.
Transmission Control Protocol/Internet Protocol
(TCP/IP)
An industry-standard, nonproprietary set
of communication protocols that provides
reliable end-to-end connections between
applications over interconnected networks
of different types.
transparent recall
The process that is used to automatically
recall a file to a workstation or file server
when the file is accessed. See also recall
mode. Contrast with selective recall.
trusted communications agent (TCA)
A program that handles the sign-on
password protocol when clients use
password generation.
systems. The CCSID value for data in

UTF-8 format is 1208.
Universal Naming Convention (UNC) name
The server name and network name
combined. These names together identify
the resource on the domain.
Universally Unique Identifier (UUID)
The 128-bit numeric identifier that is used
to ensure that two components do not
have the same identifier.
UTF-8 See Unicode transformation format 8.
UUID See Universally Unique Identifier.
V
validate
To check a policy set for conditions that
can cause problems if that policy set
becomes the active policy set. For
example, the validation process checks
whether the policy set contains a default
management class.
version
A backup copy of a file stored in server
storage. The most recent backup copy of a
file is the active version. Earlier copies of
the same file are inactive versions. The
number of versions retained by the server
is determined by the copy group
attributes in the management class.
U
UCS-2 A 2-byte (16-bit) encoding scheme based
on ISO/IEC specification 10646-1. UCS-2
defines three levels of implementation:
Level 1-No combining of encoded
elements allowed; Level 2-Combining of
encoded elements is allowed only for
Thai, Indic, Hebrew, and Arabic; Level
3-Any combination of encoded elements
are allowed.
UNC
See Universal Naming Convention name.
Unicode
A character encoding standard that
supports the interchange, processing, and
display of text that is written in the
common languages around the world,
plus some classical and historical texts.
The Unicode standard has a 16-bit
character set defined by ISO 10646.
Unicode-enabled file space
Unicode file space names provide support
for multilingual workstations without
regard for the current locale.
Unicode transformation format 8
Unicode Transformation Format (UTF),
8-bit encoding form, which is designed
for ease of use with existing ASCII-based
784
virtual file space

A representation of a directory on a
network-attached storage (NAS) file
system as a path to that directory.
virtual volume
An archive file on a target server that
represents a sequential media volume to a
source server.
volume
A discrete unit of storage on disk, tape or
other data recording medium that
supports some form of identifier and
parameter list, such as a volume label or
input/output control. See also scratch
volume, and storage pool volume.
volume history file
A file that contains information about
volumes that have been used by the
server for database backups and for
export of administrator, node, policy, or
server data. The file also has information
about sequential-access storage pool
volumes that have been added, reused, or

deleted. The information is a copy of
volume information that is recorded in
Volume Shadow Copy Service
A set of Microsoft applicationprogramming interfaces (APIs) that you
can use to create shadow copy backups of
volumes, exact copies of files, including
all open files, and so on.
VSS
See Volume Shadow Copy Service.
VSS Backup
A backup operation that uses Microsoft
Volume Shadow Copy Service (VSS)
technology. The backup operation
produces an online snapshot
(point-in-time consistent copy) of
Microsoft Exchange data. This copy can
be stored on local shadow volumes or on
Tivoli Storage Manager server storage.
VSS Fast 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
local shadow volumes.
VSS Instant Restore
A volume-level hardware-assisted
Microsoft Volume Shadow Copy Service
(VSS) function where target volumes that
contain the snapshot are copied back to
the original source volumes.
VSS offloaded backup
A backup operation that uses a Microsoft
Volume Shadow Copy Service (VSS)

hardware provider (installed on an
alternate system) to move IBM Data
Protection for Microsoft Exchange data to
the Tivoli Storage Manager server. This
type of backup operation shifts the
backup load from the production system
to another system.
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.
W
wildcard character
A special character such as an asterisk (*)
or a question mark (?) that can be used to
represent one or more characters. Any
character or set of characters can replace
the wildcard character.
workload partition (WPAR)
A partition within a single operating
system instance.
workstation
A terminal or personal computer at which
a user can run applications and that is
usually connected to a mainframe or a
network.
worldwide name
A 64-bit, unsigned name identifier that is
unique.
Glossary
785
786

Product Number: 5608-E01

5608-E02
5608-E03
5608-E07
Printed in USA
SC27-2877-03

TSM Error Codes

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

TSM Error Codes

Cargado por

Copyright:

Formatos disponibles

IBM Tivoli Storage Manager

Server Messages and Error Codes

IBM Tivoli Storage Manager

Server Messages and Error Codes

Chapter 1. Introduction to messages . . 1

Chapter 2. ANE: Client events logged to

Version 6.3.0 ANR messages . . . . . . . .

Chapter 4. Descriptions of I/O codes

Chapter 5. Device error codes in the

Chapter 3. ANR: Server common and

Changes from version 6.2.0 to version 6.3.0 .

Copyright IBM Corp. 1995, 2012

IBM Tivoli Storage Manager: Server Messages and Error Codes

Tivoli Storage Manager server publications

Copyright IBM Corp. 1995, 2012

Completion code values common to all

IBM Tivoli Storage Manager: Server Messages and Error Codes

About this publication

Who should read this publication

Tivoli Storage Manager publications

IBM Tivoli Storage Manager for AIX Installation Guide

IBM Tivoli Storage Manager for AIX Administrator's Guide

IBM Tivoli Storage Manager for AIX Administrator's Reference

Copyright IBM Corp. 1995, 2012

Table 1. Tivoli Storage Manager server publications (continued)

IBM Tivoli Storage Manager for HP-UX Installation Guide

IBM Tivoli Storage Manager for HP-UX Administrator's Guide

IBM Tivoli Storage Manager for HP-UX Administrator's Reference

IBM Tivoli Storage Manager for Linux Installation Guide

IBM Tivoli Storage Manager for Linux Administrator's Guide

IBM Tivoli Storage Manager for Linux Administrator's Reference

IBM Tivoli Storage Manager for Oracle Solaris Installation Guide

IBM Tivoli Storage Manager for Oracle Solaris Administrator's Guide

IBM Tivoli Storage Manager for Oracle Solaris Administrator's Reference

IBM Tivoli Storage Manager for Windows Installation Guide

IBM Tivoli Storage Manager for Windows Administrator's Guide

IBM Tivoli Storage Manager for Windows Administrator's Reference

IBM Tivoli Storage Manager Upgrade and Migration Guide for V5

IBM Tivoli Storage Manager Integration Guide for Tivoli Storage

Table 2. Tivoli Storage Manager storage agent publications

Table 3. Tivoli Storage Manager client publications

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive

IBM Tivoli Storage Manager for Windows: Backup-Archive Clients

IBM Tivoli Storage Manager Using the Application Programming

IBM Tivoli Storage Manager: Server Messages and Error Codes

Table 4. Tivoli Storage Manager data protection publications

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data

IBM Tivoli Storage Manager for Virtual Environments Installation and

IBM Tivoli Storage Manager for Microsoft SharePoint Guide

Table 5. IBM Tivoli Storage Manager troubleshooting and tuning publications

IBM Tivoli Storage Manager Problem Determination Guide

IBM Tivoli Storage Manager Performance Tuning Guide

IBM Tivoli Storage Manager Client Messages and Application

IBM Tivoli Storage Manager Server Messages and Error Codes

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data

About this publication

Getting technical training

Searching knowledge bases

Searching the Internet

IBM Tivoli Storage Manager: Server Messages and Error Codes

Using IBM Support Assistant

About this publication

Finding product fixes