Tivoli Messages

Tivoli Storage Manager
Messages
Version 5 Release 1
GC32-0767-00
Tivoli Storage Manager
Messages
Version 5 Release 1
GC32-0767-00
Note!
Before using this information and the product it supports, be sure to read the general information under “Appendix E.
Notices” on page 817.
First Edition (March 2002)

This edition applies to Version 5 Release 1 of the Tivoli® Storage Manager for AIX®, HP-UX, Sun Solaris,
Windows®, OS/390® and z/OS (5698-ISE, 5698-ISM, 5697-ISM); Tivoli Data Protection for NDMP, Tivoli Data
Protection for Lotus® Notes™, Tivoli Data Protection for Oracle, Tivoli Data Protection for Microsoft® SQL, Tivoli
Data Protection for Microsoft Exchange, Tivoli Space Manager , Tivoli Data Protection for R/3, Tivoli Data
Protection for EMC Symmetrix for R/3, Tivoli Data Protection for IBM® ESS for R/3, Tivoli Data Protection for
WebSphere® Application Server and to any subsequent releases until otherwise indicated in new editions or
technical newsletters.
Order publications through your sales representative or the branch office serving your locality.
Your feedback is important in helping to provide the most accurate and high-quality information. If you have
comments about this book or any other Tivoli Storage Manager documentation, please see “Contacting Customer
Support” on page xi.
© Copyright International Business Machines Corporation 1993, 2002. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Preface . . . . . . . . . . . . . . . v Part 4. Tivoli Data Protection
Messages Not Appearing in This Publication . . . v
Products Messages. . . . . . . . 653
Softcopy Publications . . . . . . . . . . . viii
Tivoli Storage Manager Publications . . . . . . viii
Referenced OS/390 and z/OS™ System Publications x Chapter 5. Tivoli Data Protection for
Related IBM Hardware Products Publications . . . x Lotus Domino (ACD0000–ACD9999). . 655
IBM International Technical Support Center
Publications (Redbooks) . . . . . . . . . . xi Chapter 6. Tivoli Data Protection for
Referenced Publications . . . . . . . . . . xi Microsoft Exchange Server
Tivoli Storage Manager Web Site . . . . . . . xi
Contacting Customer Support . . . . . . . . xi
(ACN0000–ACN9999) . . . . . . . . 673
Reporting a Problem . . . . . . . . . . xii
Translations . . . . . . . . . . . . . . xii Chapter 7. Tivoli Data Protection for
Microsoft SQL Server
Summary of Changes for Tivoli (ACO0000–ACO9999) . . . . . . . . 689
Storage Manager Version 5. . . . . . xiii
Technical Changes for Version 5 Release 1—March Chapter 8. Tivoli Data Protection for
2002 . . . . . . . . . . . . . . . . xiii Oracle (ANU0000–ANU9999) . . . . . 705
Part 1. Introduction . . . . . . . . . 1 Chapter 9. Tivoli Data Protection for

R/3 (BKI0000–BKI9999) . . . . . . . 717
Chapter 1. Introduction . . . . . . . . 3
Understanding Messages . . . . . . . . . . 4 Chapter 10. Tivoli Data Protection for
Message Format . . . . . . . . . . . . 4 R/3 File Manager . . . . . . . . . . 725
Chapter 2. Obtaining Help for Tivoli Chapter 11. Tivoli Data Protection for
Storage Manager . . . . . . . . . . . 7 R/3 for DB2 UDB (BKI0000–BKI9999) . 727
Internet and IBMLink Assistance . . . . . . . 7
Internet . . . . . . . . . . . . . . . 7
IBMLink/ServiceLink . . . . . . . . . . 7
Chapter 12. Tivoli Data Protection for
Describing the Error with Keywords . . . . . . 7 R/3 for Oracle (BKI0000–BKI9999) . . 737
Component Identification Keyword . . . . . . 8
Type-of-Failure Keyword . . . . . . . . . 8 Chapter 13. Tivoli Data Protection for
Command Keyword . . . . . . . . . . . 8 EMC Symmetrix for R/3
Function Keyword . . . . . . . . . . . 9 (IDS0000–IDS0999) . . . . . . . . . 749
Obtaining Online HELP (Get Help on Error
Messages) . . . . . . . . . . . . . . . 9
Contacting Your Service Representative . . . . . 9 Chapter 14. Tivoli Data Protection for
Running Trace Commands. . . . . . . . . 9 IBM ESS for R/3 (IDS1000–IDS1999). . 755
Messages That Do Not Appear in This Publication. . 9
Chapter 15. Tivoli Data Protection for
Part 2. Server Messages . . . . . . 11 WebSphere Application Server
(DKP0000–DKP0999) . . . . . . . . 763
Chapter 3. Common and Platform
Specific Messages Part 5. Appendixes . . . . . . . . 777
(ANR0100–ANR9999). . . . . . . . . 13
Appendix A. API Return Codes with
Chapter 4. Client Events Logged to Explanations. . . . . . . . . . . . 779
Server (ANE4000—4999). . . . . . . 519
Appendix B. Allocating Additional
Part 3. Client Messages . . . . . . 525 Server Memory. . . . . . . . . . . 803
© Copyright IBM Corp. 1993, 2002 iii

Appendix C. I/O Error Code Appendix D. Device Errors in AIX
Descriptions for Server Messages . . 805 System Error Log . . . . . . . . . 815
Completion Code and Operation Code Values . . 806
Completion Code Values Common to All Device Appendix E. Notices . . . . . . . . 817
Classes . . . . . . . . . . . . . . 806 Programming Interface . . . . . . . . . . 818
Completion Code Values for Media Changers 807 Trademarks . . . . . . . . . . . . . . 819
Completion Code Values for Tape and Optical
Drives . . . . . . . . . . . . . . . 808
Glossary . . . . . . . . . . . . . 821
Operation Code Values for Tape Library Devices 809
Common Values for ASC and ASCQ Codes . . . 809
Windows NT Event Log Entries . . . . . . 812
iv Tivoli Storage Manager: Messages

Preface
Tivoli Storage Manager (TSM) is a client/server program that provides storage
management services to customers in a multivendor computer environment. TSM
provides an automated, centrally scheduled, policy-managed backup, archive, and
space management facility for file servers and workstations.
This publication contains explanations and suggested actions for messages issued
by the Tivoli Storage Manager server program for storage management services,
the administrative client graphical user interface, administrative command line
client, and backup-archive client.
Messages Not Appearing in This Publication

Message numbers in the range ANR0100–0120, and any with 9999 are not
published in this manual. They are considered severe errors and should be
recorded and included in a problem report when contacting the service
representative. The following messages are not published in this manual:
Common AIX Specific MVS™ Specific Windows HP-UX Specific Sun Solaris
Messages Specific Specific
ANR0628I ANR7837S ANR5400E ANR7830E ANR7823S ANR7823S

ANR0680E ANR7845S ANR5401E ANR7831I
ANR0702E ANR7846S ANR5402E ANR7832E
ANR0703E ANR7847S ANR5403E ANR7833I
ANR0704E ANR7848S ANR7836S
ANR0896I ANR8924E ANR7837S
ANR0897I
ANR0898I
ANR0899W
ANR0906I
ANR0907I
ANR0908W
ANR0912I
ANR0913I
ANR1601E ANR7838S
ANR2337W
ANR2338E
ANR2704E ANR7839E
ANR2705E ANR7850S
ANR2706E ANR7851S
ANR2710E ANR9620I ANR9620I ANR9620I
ANR2711E ANR9621I AND9621I
ANR2801E ANR9622I ANR9622I
ANR2809I ANR9626I ANR9626I ANR9626I
ANR2827I
ANR2828I
ANR2830W
ANR2831I
ANR2835I
© Copyright IBM Corp. 1993, 2002 v

ANR2837I
ANR2838I
ANR2840I
ANR2842I
ANR2843I
ANR2844I
ANR2845I
ANR2846I
ANR2847W
ANR2848E
ANR2849W
ANR2850E
ANR2851W
ANR2854I
ANR2856E
ANR2857E
ANR2858W
ANR2859I
ANR2861I
ANR2862W
ANR2863I
ANR2864I
ANR2865W
ANR2866W
ANR2867E
ANR2868E
ANR2869I
ANR2870E
ANR2871W
ANR2872E
ANR2873I
ANR2874W
ANR2875E
ANR2876E
ANR2877E
ANR2878I
ANR2879I
ANR2880I
ANR2881I
ANR2882I
ANR2883I
ANR2884I
ANR2885I
ANR2886E
ANR2887W
ANR2888E
ANR2889W
ANR2890E
ANR2891W
ANR2892E
ANR2893W
ANR2894E
ANR2895W
vi Tivoli Storage Manager: Messages

ANR2896E
ANR2897W
ANR2898E
ANR2899W
ANR4024I
ANR4392I
ANR4393I
ANR4394I
ANR4400I
ANR4401I
ANR4507E
ANR4508E
ANR4509I
ANR4696E
ANR4711I
ANR8924E
ANR9619I
ANR9621I
ANR9628I ANR9628I
ANR9629I
ANR9630I ANR9630I ANR9630I
ANR9631I ANR9631I
ANR9632I
ANR9639I ANR9639I
ANR9640I ANR9640I
ANR9641I ANR9641I
ANR9652I
Message number ANR7831I and numbers in the range ANR7900–8199 are AS/400®
platform specific messages and are not published in this manual. You can obtain
the explanation for these messages using AS/400 commands such as WRKMSGD
to get to the "Work with Message Descriptions" panel. The unpublished messages
are:
ANR7831I ANR7918I ANR7937I ANR7980E ANR7998E ANR8066E ANR8124E

ANR7900E ANR7919E ANR7938E ANR7981E ANR7999E ANR8067E ANR8125E
ANR7901E ANR7920E ANR7939E ANR7982E ANR8050E ANR8068E ANR8126I
ANR7902E ANR7921E ANR7940E ANR7983E ANR8051I ANR8069E ANR8127E
ANR7903E ANR7922E ANR7941E ANR7984E ANR8052I ANR8070E ANR8128E
ANR7904E ANR7923E ANR7943E ANR7985I ANR8053I ANR8071E ANR8129E
ANR7905E ANR7924E ANR7944E ANR7986E ANR8054E ANR8072E ANR8130E
Preface vii
ANR7906E ANR7925E ANR7946I ANR7987I ANR8055I ANR8095E ANR8131E
ANR7907E ANR7926E ANR7947I ANR7988I ANR8056E ANR8100I ANR8132E
ANR7908E ANR7927E ANR7950E ANR7989E ANR8057E ANR8101E ANR8133W
ANR7909E ANR7928E ANR7951E ANR7990E ANR8058E ANR8102E ANR8134W
ANR7910I ANR7930I ANR7952E ANR7991E ANR8059E ANR8103I ANR8135E
ANR7911I ANR7931I ANR7955I ANR7992E ANR8060E ANR8110I ANR8136I
ANR7912S ANR7932I ANR7959E ANR7993I ANR8061E ANR8111I ANR8137I
ANR7913S ANR7933I ANR7960E ANR7994I ANR8062E ANR8120I ANR8138I
ANR7914E ANR7934I ANR7961E ANR7995I ANR8063E ANR8121I ANR8139I
ANR7915E ANR7935I ANR7962E ANR7996E ANR8064E ANR8122I ANR8140E
ANR7916E ANR7936I ANR7963E ANR7997E ANR8065E ANR8123I ANR8141I
Message numbers in the range ANE4000–4999 are client event logging messages.
These messages (or events) are sent to the server for distribution to various event
logging receivers. The client may send statistics to the server providing
information about a backup or restore. These statistics are informational and
self-explanatory messages that may be enabled or disabled to the various event
logging receivers. The following messages are not published in this manual:
ANE4950 ANE4951 ANE4952 ANE4953 ANE4954 ANE4955 ANE4956

See “Internet and IBMLink Assistance” on page 7 for additional information.
Note: You may receive other messages that are not documented in this manual.
Those messages may have been created after this manual was published.
Use the online help facility to display the help text specific to the message.
Softcopy Publications
The TSM library is available in softcopy on the following CD-ROM:
Title Order Number

Tivoli Storage Manager Publications Version 4 CD-ROM SK3T-1417
Tivoli Storage Manager Publications

The following table lists Tivoli Storage Manager server publications.
Publication Title Order Number

Tivoli Storage Management Products License Information GH09-4572
Tivoli Storage Manager Messages GC32-0767
Tivoli Storage Manager for AIX Administrator’s Guide GC32-0768
Tivoli Storage Manager for AIX Administrator’s Reference GC32-0769
Tivoli Storage Manager for AIX Quick Start GC32-0770
Tivoli Storage Manager for HP-UX Administrator’s Guide GC32-0772
Tivoli Storage Manager for HP-UX Administrator’s Reference GC32-0773
Tivoli Storage Manager for HP-UX Quick Start GC32-0774
viii Tivoli Storage Manager: Messages

Tivoli Storage Manager for OS/390 and z/OS Administrator’s Guide GC32-0775
Tivoli Storage Manager for OS/390 and z/OS Administrator’s Reference GC32-0776
Tivoli Storage Manager for OS/390 and z/OS Quick Start GC32-0777
Tivoli Storage Manager for Sun Solaris Administrator’s Guide GC32-0778
Tivoli Storage Manager for Sun Solaris Administrator’s Reference GC32-0779
Tivoli Storage Manager for Sun Solaris Quick Start GC32-0780
Tivoli Storage Manager for Windows Administrator’s Guide GC32-0782
Tivoli Storage Manager for Windows Administrator’s Reference GC32-0783
Tivoli Storage Manager for Windows Quick Start GC32-0784
The following table lists Tivoli Storage Manager storage agent publications.

Tivoli Storage Manager for AIX Managed System for SAN Storage Agent GC32-0771
User’s Guide
Tivoli Storage Manager for HP-UX Managed System for SAN Storage GC32-0727
Agent User’s Guide
Tivoli Storage Manager for Sun Solaris Managed System for SAN Storage GC32-0781
Tivoli Storage Manager for Windows Managed System for SAN Storage GC32-0785
The following table lists the Tivoli Storage Manager client publications.

Tivoli Space Manager for UNIX: Using the Hierarchical Storage GC32-0794
Management Clients
Tivoli Storage Manager for Macintosh: Backup-Archive Installation and GC32-0787
User’s Guide
Tivoli Storage Manager for NetWare: Backup-Archive Installation and GC32-0786
User’s Guide
Tivoli Storage Manager for UNIX: Backup-Archive Installation and User’s GC32-0789
Guide
Tivoli Storage Manager for Windows: Backup-Archive Installation and GC32-0788
User’s Guide
Tivoli Storage Manager Trace Facility Guide GC32-0792
Tivoli Storage Manager Using the Application Program Interface GC32-0793
The following table lists Tivoli Data Protection publications.
Order
Publication Title Number
Tivoli Data Protection for EMC Symmetrix for R/3 Installation and User’s Guide SC33-6386
Tivoli Data Protection for IBM ESS for Oracle Databases DB2 UDB Installation SH26-4125
and User’s Guide
Tivoli Data Protection for IBM ESS for R/3 Installation and User’s Guide SC33-6387
Preface ix
Order
Publication Title Number
Tivoli Data Protection for Informix Installation and User’s Guide SH26-4095
Tivoli Data Protection for Lotus Domino for UNIX Installation and User’s Guide SH26-4088
Tivoli Data Protection for Lotus Domino for Windows Installation GC26-7320
Tivoli Data Protection for Lotus Domino, S/390 Edition Licensed Program GC26-7305
Specifications
Tivoli Data Protection for Lotus Notes on AIX Installation and User’s Guide SH26-4067
Tivoli Data Protection for Lotus Notes on Windows NT Installation and User’s SH26-4065
Guide
Tivoli Data Protection for Microsoft Exchange Server Installation and User’s Guide SH26-4110
Tivoli Data Protection for Microsoft SQL Server Installation and User’s Guide SH26-4111
Tivoli Data Protection for Oracle for UNIX Installation and User’s Guide SH26-4112
Tivoli Data Protection for Oracle for Windows Installation and User’s Guide SH26-4113
Tivoli Data Protection for R/3 Installation and User’s Guide for Oracle SC33-6340
Tivoli Data Protection for R/3 Installation and User’s Guide for DB2 UDB SC33-6341
Tivoli Data Protection for R/3 Installation and User’s Guide SC33-6389
Tivoli Data Protection for WebSphere Application Server Installation and User’s SC33-6399
Guide
Tivoli Data Protection for Workgroups for NetWare User’s Guide GC32-0444
Referenced OS/390 and z/OS™ System Publications

The following table lists referenced OS/390 and z/OS publications.

DFSMS/MVS DFSMSrmm Guide and Referencee SC26-4931
DFSMS/MVS DFSMSrmm Implementation and Customization Guide SC26-4932
OS/390 Security Server (RACF) Security Administrator’s Guide SC28-1915
z/OS SecureWay Security Server RACF Security Administrator’s Guide SA22-7683
Related IBM Hardware Products Publications

The following table lists related IBM hardware products publications.
Title Order Number

IBM Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279
IBM 3490E Model E01 and E11 User’s Guide GA32-0298
IBM 3495 Tape Library Dataserver Models L20, L30, L40, and L50 GA32-0235
Operator’s Guide
IBM Magstar MP 3570 Tape Subsystem Operator’s Guide GA32-0345
IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: GC35-0154
Installation and User’s Guide
IBM TotalStorage Enterprise Tape System 3590 Operator Guide GA32-0330
IBM Magstar 3494 Tape Library Dataserver Operator Guide GA32-0280
x Tivoli Storage Manager: Messages

IBM International Technical Support Center Publications (Redbooks)
The International Technical Support Center (ITSC) publishes redbooks, which are
books on specialized topics such as using TSM to back up databases. You can
order publications through your IBM representative or the IBM branch office
serving your locality. You can also search for and order books of interest to you by
visiting the IBM Redbooks™ home page on the World Wide Web at this address:
http://www.redbooks.ibm.com/redbooks
Referenced Publications
The following table lists other publications referenced in this manual:
Title Order Number

IBM 3494 Tape Library Dataserver User’s Guide: Media Library Device Driver GC35-0153
for AS/400
IBM Local Area Network Technical Reference SC30-3383
LAN Technical Reference IEEE 802.2 & NETBIOS APIs SC30-3587
AS/400 System API Reference SC41-3801
Tivoli Storage Manager Web Site

TSM publications are available on the TSM home page on the World Wide Web at
the following address:
http://www.tivoli.com/support/storage_mgr/tivolimain.html
By accessing the TSM home page, you can keep up-to-date with the newest
product information.
Contacting Customer Support

For support for this or any Tivoli product, you can contact Tivoli Customer
Support in one of the following ways:
v Visit the Tivoli Storage Manager technical support Web site at
http://www.tivoli.com/support/storage_mgr/tivolimain.html.
v Submit a problem management record (PMR) electronically at
IBMSERV/IBMLINK. You can access IBMLINK at
http://www2.ibmlink.ibm.com.
v Submit a problem management record (PMR) electronically at
http://www.tivoli.com/support. See “Reporting a Problem” on page xii for
details.
v Send e-mail to support@tivoli.com.
Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). For
product numbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511.
International customers should consult the Web site for customer support
telephone numbers.
You can also review the Customer Support Handbook, which is available on our Web
site at http://www.tivoli.com/support/handbook/.
Preface xi
When you contact Tivoli Customer Support, be prepared to provide identification
information for your company so that support personnel can readily assist you.
Company identification information may also be needed to access various online
services available on the Web site.
The support Web site offers extensive information, including a guide to support
services (the Customer Support Handbook); frequently asked questions (FAQs);
and documentation for all Tivoli products, including Release Notes, Redbooks, and
Whitepapers. The documentation for some product releases is available in both
PDF and HTML formats. Translated documents are also available for some product
releases.
You can order documentation by e-mail at swdist@tivoli.com. Please provide the

publication number, part number, or order number of the desired document.
Alternatively, you can provide the document title, version number, and date of
publication.
We are very interested in hearing about your experience with Tivoli products and
documentation. We also welcome your suggestions for improvements. If you have
comments or suggestions about our documentation, please contact us in one of the
following ways:
v Send e-mail to pubs@tivoli.com.
v Complete our customer feedback survey at
http://www.tivoli.com/support/feedback/.
Reporting a Problem
Please have the following information ready when you report a problem:
v The Tivoli Storage Manager server version, release, modification, and service
level number. You can get this information by entering the QUERY STATUS
command at the TSM command line.
v The Tivoli Storage Manager client version, release, modification, and service
level number. You can get this information by entering dsmc at the command
line.
v The communication protocol (for example, TCP/IP), version, and release number
you are using.
v The activity you were doing when the problem occurred, listing the steps you
followed before the problem occurred.
v The exact text of any error messages.
Translations
Selected TSM publications have been translated into languages other than
American English. Contact your service representative for more information about
the translated publications and whether these translations are available in your
country.
xii Tivoli Storage Manager: Messages

Summary of Changes for Tivoli Storage Manager Version 5
This section summarizes changes that have been made to the Tivoli Storage
Manager product and this publication. Refer to the Tivoli Storage Manager
Administrator’s Guide and the Tivoli Storage Manager Administrator’s Reference for
details.
Technical Changes for Version 5 Release 1—March 2002

The following changes have been made to the product for this edition:
Tivoli Storage Manager Device Driver
The Tivoli Storage Manager Server device driver is now available on
HP-UX. It replaces the use of the SCSI Pass-through driver for
autochangers, and can be used to optimally support SCSI tape and optical
drives.
See Administrator’s Guide and Quick Startfor more information.
LAN-Free Data Movement
Tivoli Storage Manager supports LAN-free data movement in storage area
network (SAN) environments. The support allows client data to move
directly from the client system to a server-managed storage device on the
SAN. This enhancement reduces data movement on the LAN so that more
bandwidth is available to other applications.
See Tivoli Storage Manager Managed System for SAN Storage Agent User’s
Guide for more information.
Changes in Defining Drives and Libraries
v Device special file names and External Library managers are now
specified in the DEFINE PATH and UPDATE PATH commands, rather
than in the DEFINE DRIVE, UPDATE DRIVE, DEFINE LIBRARY, and
UPDATE LIBRARY commands.
See Administrator’s Guide for more information.

Moving Data by Node
You can use the MOVE NODEDATA command to move data in a
sequential-access storage pool for one or more nodes, or move data in a
single node with selected file spaces. You can also use MOVE NODEDATA
to consolidate data for offsite disaster recovery storage, or move data to
another storage pool.
Support for Simultaneous Writes to Primary and Copy Storage Pools
You can specify copy storage pools in a primary storage pool definition.
When a client backs up, archives, or migrates a file, the file is written to
the primary storage pool and is simultaneously stored into each copy
storage pool.
High Availability Cluster Multiprocessing
Tivoli Storage Manager can now use High Availability Cluster
Multiprocessing (HACMP). HACMP provides the leading AIX-based
© Copyright IBM Corp. 1993, 2002 xiii

clustering solution, which allows automatic system recovery during system
failure detection. By using HACMP together with Tivoli Storage Manger,
you can ensure server availability.
Tivoli Data Protection for New Network Data Management Protocol Support
The new Tivoli Data Protection for NDMP product now supports NDMP
backup and restore for IBM network-attached storage (NAS) file servers.
Previously only Network Appliance NAS file servers were supported. TDP
for NDMP is a separately priced and licensed product.
New Network Data Management Protocol (NDMP) support now extends
to the AIX (32-bit and 64-bit) Tivoli Storage Manager server platform. The
new Tivoli Data Protection for NDMP product supports NDMP backup
and restore for network-attached storage (NAS) file servers from IBM and
Network Appliance. NDMP allows a network storage-management
application to control the backup and restore of an NDMP-compliant file
server without installing third-party software on that server. The NAS file
server does not require installation of TSM software. The TSM server uses
NDMP to connect to the NAS file server to initiate, control, and monitor a
file system backup or restore operation. The NDMP support for NAS file
servers enables higher performance backup to tape devices without
moving the data over the LAN. TDP for NDMP is a separately priced and
licensed product.
to the Sun Solaris (32-bit and 64-bit) Tivoli Storage Manager server
platform. The new Tivoli Data Protection for NDMP product supports
NDMP backup and restore for network-attached storage (NAS) file servers
from IBM and Network Appliance. NDMP allows a network
storage-management application to control the backup and restore of an
NDMP-compliant file server without installing third-party software on that
server. The NAS file server does not require installation of TSM software.
The TSM server uses NDMP to connect to the NAS file server to initiate,
control, and monitor a file system backup or restore operation. The NDMP
support for NAS file servers enables higher performance backup to tape
devices without moving the data over the LAN. TDP for NDMP is a
separately priced and licensed product.
to the HP-UX (32-bit and 64-bit) Tivoli Storage Manager server platform.
The new Tivoli Data Protection for NDMP product supports NDMP
backup and restore for network-attached storage (NAS) file servers from
IBM and Network Appliance. NDMP allows a network
storage-management application to control the backup and restore of an
NDMP-compliant file server without installing third-party software on that
server. The NAS file server does not require installation of TSM software.
The TSM server uses NDMP to connect to the NAS file server to initiate,
control, and monitor a file system backup or restore operation. The NDMP
support for NAS file servers enables higher performance backup to tape
devices without moving the data over the LAN. TDP for NDMP is a
separately priced and licensed product.
Data Validation with Cyclic Redundancy Checking
Tivoli Storage Manager provides the option of specifying whether a cyclic
redundancy check (CRC) is performed during a client session with the
xiv Tivoli Storage Manager: Messages

server, or for storage pools. The server validates the data by using a cyclic
redundancy check which can help identify data corruption. Data validation
can be enabled for one or all of the following:
v Tivoli Storage Manager client nodes at Version 5.1
v Tivoli Storage Manager storage agents at Version 5.1
v Storage pools
See Administrator’s Guide and TSM Managed System for SAN Storage Agent
User’s Guide for more information.
New Licensing Method
The new licensing method enables you to register the exact number of
licenses that are required, rather than in increments of 1, 5, 10, and 50.
Server Performance Enhancements
There are two new Tivoli Storage Manager performance enhancements:
v AIX Asynchronous I/O Support. This feature is available via a new
option in the server options file.
v AIX Direct I/O Support. This feature is available via a new option in the
server options file.

Support for Windows XP/2002 Tivoli Storage Manager Backup-Archive Clients
Support is now added for Windows XP and Windows 2002 Tivoli Storage
Manager backup-archive clients that run in 64-bit mode. These two
Windows platforms are a Unicode-only version of the client.
Communication Method
Tivoli Storage Manager for Windows no longer supports the Internetwork
Packet Exchange (IPX)/SPX and NETBIOS communication methods. The
COMMETHOD server option is updated to reflect this change.
Summary of Changes for Tivoli Storage Manager Version 5 xv

xvi Tivoli Storage Manager: Messages
Part 1. Introduction
© Copyright IBM Corp. 1993, 2002 1

2 Tivoli Storage Manager: Messages
Chapter 1. Introduction
Tivoli Storage Manager (TSM) is an enterprise-wide storage management
application for the network. It provides automated storage management services to
multivendor workstations, personal computers, and local area network (LAN) file
servers. TSM includes the following components:
Server Allows a server system to provide backup, archive, and space management
services to workstations. The server maintains a database and recovery log
for TSM resources, users, and user data.
The server controls the TSM server’s storage, called storage pools. These
are groups of random and sequential access media that store backed up,
archived, and space-managed files.
You can set up multiple servers in your enterprise network to balance
storage, processor, and network resources. TSM allows you to manage and
control multiple servers from a single interface that runs in a web browser
(the enterprise console).
Administrative client
Allows administrators to control and monitor server activities, define
management policies for client files, and set up schedules to provide
services at regular intervals. Administrative functions are available from an
administrative client command line and from a web browser interface.
Backup-archive client
Allows users to maintain backup versions of their files, which they can
restore if the original files are lost or damaged. Users can also archive files
for long-term storage and retrieve the archived files when necessary. Users
or administrators can register workstations and file servers as client nodes
with a TSM server.
Tivoli Space Manager (Hierarchical storage management (HSM) client)
Provides space management services for workstations on some platforms.
TSM users can free workstation storage by migrating less frequently used
files to server storage. These migrated files are also called space-managed
files. Users can recall space-managed files automatically simply by
accessing them as they normally would.
Application programming interface (API)
Allows users to enhance existing applications with backup, archive, restore,
and retrieve services. When users install the TSM API client on their
workstations, they can register as client nodes with a TSM server.
Tivoli Data Protection
This chapter contains information to help you understand the messages issued by
these components.
Messages can appear on the server console, the administrative client, an operator
terminal, the administrative graphical user interface, the backup-archive client, the
space-management client, or the application clients.
TSM provides an activity log to help the administrator track server activity and
monitor the system. The activity log contains messages generated by the server,
and is stored in the database. The server automatically deletes messages from the

activity log after they have passed the specified retention period. Any messages
sent to the server console are stored in the activity log. Examples of the types of
messages stored in the activity log include:
v When client sessions start or end
v When migration starts or ends
v When backed up files are expired from server storage
v Any output generated from background processes
See the Tivoli Storage Manager Administrator’s Guide.
Understanding Messages
The following examples illustrate the format used in this publication to describe
TSM messages:
v Messages that begin with prefix ANE and are in range 4000–4999 originate from
the backup-archive client. These messages (or events) are sent to the server for
distribution to various event logging receivers.
v The client may send statistics to the server providing information about a
backup or restore. These statistics are informational messages that may be
enabled or disabled to the various event logging receivers. These messages are
not published in this manual.
v Messages that begin with prefix ANR originate from the server.
v Messages that begin with prefix ANS are from one of the following clients:
– TSM administrative clients
– Application program interface clients
– Backup–archive
– Tivoli Space Manager (HSM) clients
– TDP for Lotus Notes
v Messages that begin with prefix ACD are from TDP for Lotus Domino™.
v Messages that begin with prefix ACN are from TDP for Microsoft Exchange
Server.
v Messages that begin with prefix ACO are from TDP for Microsoft SQL Server.
v Messages that begin with prefix ANU are from TDP for Oracle.
v Messages that begin with prefix BKI are from TDP for R/3, TDP for R/3 for
DB2® UDB, TDP for R/3 for Oracle.
v Messages that begin with prefix DKPand are in range 0001–9999 are from TDP
for WebSphere Application Server.
v Messages that begin with prefix IDS and are in range 0000–0999 are from TDP
for EMC Symmetrix for R/3.
v Messages that begin with prefix IDS and are in range 1000–1999 are from TDP
for IBM ESS for R/3.
Message Format
The following examples describe the TSM message format:

The callouts to the right identify each part of the format.
Message Prefix
Message Number
Message Type*
ANR 0992 I
Server installation complete. Message Text
Explanation: The server installation procedure

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

processing.
User Response: None. User Response
* I = Information
E = Error
S = Severe Error
W = Warning
K = Kernel message that originates from the
hierarchical storage management (HSM) client
Message variables in the message text appear in italics. The server and client
messages fall into the following categories:
v Common messages that pertain to all TSM server platforms
v Platform specific messages that pertain to each operating environment for the
server and the client
v Messages that pertain to application clients
How to Read a Return Code Message

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.
Example One for QUERY EVENT Command:
Chapter 1. Introduction 5
Example Two for DEFINE VOLUME Command:

Chapter 2. Obtaining Help for Tivoli Storage Manager
This section describes the following:
v How to obtain help with processing errors by using Internet and
IBMLink™/ServiceLink
v How to describe errors with keywords
v How to obtain online message help
v What information to have available when you contact your service
representative
Internet and IBMLink Assistance

TSM message help explanations may suggest that you contact your service
representative for additional help with processing errors.
Online help is available through Internet and IBMLink/ServiceLink.
Internet
You can get additional information through an anonymous FTP server,
ftp.software.ibm.com. Tivoli Storage Manager information is in the
/storage/tivoli-storage-management directory.
A newsgroup, listserv@marist.edu, is implemented by a third party. IBM supports

this newsgroup on a best-effort basis only.
IBMLink/ServiceLink
If your installation has access to IBMLink/ServiceLink, an interactive online
database program, you can:
v Search for an existing authorized program analysis report (APAR) that is similar
to your problem.
v Search for an available program temporary fix (PTF) for the existing APAR.
v Order the PTF if it is available.
v Create an Electronic Technical Response (ETR) problem report to get assistance
from an TSM service representative.
Describing the Error with Keywords

When you use IBMLink/Servicelink or call your service representative, accurately
describe the problem so that the service representative may quickly help you solve
the problem. Identify the processing error with a full set of keywords whenever
possible. A keyword is a word or an abbreviation used to describe a single aspect
of a program failure. Each keyword describes an aspect of a processing error.
The following example displays the necessary set of keywords:

56480200n R312 type command function
Where Represents
56480200n Component identification keyword

Where Represents
R312 Release level keyword
type Type-of-failure keyword
command Command keyword
function Function keyword
Component Identification Keyword

The component identifiers for TSM are listed below:
Component Component ID
AIX 5698-TSM
HP-UX 5698-TSM
OS/390 and z/OS 5697-DRS, 5697-TS9, 5698-TSM
Sun Solaris 5698-TSM
Windows 5698-TSM, 5698-DPA
DRM 5698-DRM
Type-of-Failure Keyword
The following keywords identify the type of failure that may occur:
Keyword Description
ABENDxxx Use this keyword when the system ends abnormally.
INCORROUT Use this keyword when incorrect output is received or expected
output is missing.
LOOP Use this keyword if a part of the program code runs endlessly;
include situations in which a part of the output repeats
continuously.
MSGANRnnnnt (or) Use this keyword when a message:
MSGANSnnnnt v Indicates an internal program error
v Is issued in a set of conditions that should not cause it to be
issued
v Contains invalid or missing data
See “Understanding Messages” on page 4 for a description of the
message format.
WAIT Use this keyword when you receive no response within a
reasonable time that can be perceived as poor response or poor
performance.
xxxxxxxxxx Use this keyword when a programming problem appears to be
(Documentation) caused by incorrect, missing, or ambiguous information in one of
the TSM publications. Enter the order number of the publication in
place of xxxxxxxxxx. Include the letter prefix and version number,
but omit all hyphens, for example, GC35040500. Refer to “Tivoli
Storage Manager Publications” on page viii for a list of the TSM
publications.
PERFM Use this keyword as a closing code for an APAR.
Command Keyword
Build keywords based on TSM commands. Refer to Administrator’s Reference for a
list of the commands.

Function Keyword
Use keywords that refer to basic TSM functions such as backup, retrieve, archive,
recover, migrate, and export-import.
Obtaining Online HELP (Get Help on Error Messages)

Use the HELP command on the server console or administrative command line
client to display information about server and administrative command line client
messages. Use the HELP command on the backup-archive client to display
information about backup-archive client messages.
The Help error message number command displays the help text specific to the error
message. You can get help information on server messages (prefixed by ANR), and
administrative command line and backup-archive client messages (prefixed by
ANS or ANE) except those specific to the administrative graphical user interface
client.
Contacting Your Service Representative

When you contact your service representative after the proper diagnostic
procedures have been followed and user specifications have been checked for
accuracy, you should have on hand the information listed in “Reporting a
Problem” on page xii.
Running Trace Commands

Your service representative may request that you run trace commands to perform
diagnostic functions. The output from the trace commands is classified as
Diagnosis, Modification, and Tuning Information.
Messages That Do Not Appear in This Publication

See “Messages Not Appearing in This Publication” on page v for information about
messages that appear online but are not documented in this publication.
Chapter 2. Obtaining Help for Tivoli Storage Manager 9

Part 2. Server Messages

Chapter 3. Common and Platform Specific Messages
(ANR0100–ANR9999)
This chapter contains the common and platform-specific server messages. The
organization of the messages are grouped by the message prefix ANR and
documented in ascending numeric order. If a message is platform specific and a
duplicate, the appropriate platform name is added after the message number and
it is also documented alphabetically by platform name.
ANR0100E Source file(line number): Error error code ANR0104E Source file(line number): Error error code
creating table ″table name″. deleting row from table ″table name″.
Explanation: An internal error has occurred in an Explanation: An internal error has occurred in an
attempt to create a server database table. This message attempt to remove data from a server database table.
always accompanies another error message and This message always accompanies another error
provides more detail about that error. message and provides more detail about that error.
System Action: The activity that generated this error System Action: The activity that generated this error
fails. fails.
User Response: Contact your service representative. User Response: Contact your service representative.
ANR0101E Source file(line number): Error error code ANR0105E Source file(line number): Error setting
opening table ″table name″. search bounds for table ″table name″.
Explanation: An internal error has occurred in an Explanation: An internal error has occurred in an
attempt to access a server database table. This message attempt to access data in a server database table. This
always accompanies another error message and message always accompanies another error message
provides more detail about that error. and provides more detail about that error.
System Action: The activity that generated this error System Action: The activity that generated this error
fails. fails.
User Response: Contact your service representative. User Response: Contact your service representative.
ANR0102E Source file(line number): Error error code ANR0106E Source file(line number): Unexpected error
inserting row in table ″table name″. error code fetching row in table ″table
name″.
Explanation: An internal error has occurred in an
attempt to add data to a server database table. This Explanation: An internal error has occurred in an
message always accompanies another error message attempt to access data in a server database table. This
and provides more detail about that error. message always accompanies another error message
and provides more detail about that error.
System Action: The activity that generated this error
fails. System Action: The activity that generated this error
fails.
User Response: Contact your service representative.
ANR0103E Source file(line number): Error error code
updating row in table ″table name″. ANR0107W Source file(line number): Transaction
transaction ID was not committed due to
Explanation: An internal error has occurred in an
an internal error.
attempt to update data in a server database table. This
message always accompanies another error message Explanation: An internal error was detected during
and provides more detail about that error. transaction commit. This message should be preceded
by another error message which provides more detail
about that error.
fails.

ANR0108E • ANR0202W
System Action: The activity that generated this error administrator can add database volumes by using the
fails. DEFINE DBVOLUME command, and extend the size of
the database by using the EXTEND DB command.
ANR0132E DiagnosticID: Memory allocation failed:

ANR0108E Source file(line number): could not start a
object object name, size size.
new transaction.
Explanation: The server cannot obtain enough
Explanation: An error occurred while attempting to
memory to create the object named.
start a new transaction. Possibly there is not enough
memory. System Action: The activity that generated this error
fails.
fails. User Response: Allocate additional storage to the
server. For details, issue HELP MEMORY to display the
User Response: Allocate additional storage to the
information online or see “Appendix A. Allocating
Additional Server Memory”.
ANR0133E Error loading module modname: error
string
ANR0110E An unexpected system date has been
detected; the server is disabled. Use the Explanation: The error specified by error string
ACCEPT DATE command to establish occurred when the server attempted to load module
the current date as valid. modname
Explanation: The server has noted that the current System Action: Server operation continues, but the
system date is suspect. It is earlier than the server function provided by the module is not available.
install date or has suddenly moved into the future by
User Response: Refer to the error string and correct
30 days or more.
the condition causing the load to fail.
System Action: The server is disable for client access.
Server expiration will not execute.
ANR0200I Recovery log assigned capacity is size
User Response: If the current system date is not valid, megabytes.
reset the date. Use the ACCEPT DATE command to
Explanation: The amount of space allocated to the
establish the current date as valid on the server. After
recovery log is shown.
executing this command, you can use the ENABLE
SESSIONS command to enable the server for client System Action: None.
sessions.
User Response: None.
ANR0130E DiagnosticID: Server LOG space

exhausted. ANR0201I Database assigned capacity is size
megabytes.
Explanation: There is no space to write data to the
server recovery log. Explanation: The amount of space allocated to the
database is shown.
fails. System Action: None.
User Response: To increase the amount of log space User Response: None.
available to the server, an authorized administrator can
add log volumes by using the DEFINE LOGVOLUME ANR0202W Database volume volume name varied
command, and extend the size of the log by using the offline due to excessive read errors.
EXTEND LOG command.
Explanation: The database volume shown has been
varied offline because too many read errors have been
ANR0131E DiagnosticID: Server DB space exhausted. encountered.
Explanation: There is no space to write data to the System Action: If available, a mirrored copy of the
server database. volume is used.
System Action: The activity that generated this error User Response: Correct the cause of the read errors.
fails.
User Response: To increase the amount of database
space available to the server, an authorized

ANR0203W • ANR0212E
ANR0203W Database volume volume name varied ANR0208W Partial write detected on recovery log
offline due to excessive write errors. volume volume name, logical page logical
page number (physical page physical page
Explanation: The database volume shown has been
number).
varied offline because too many write errors have been
encountered. Explanation: During a write of a recovery log page,
an error occurs so that the page is not completely
System Action: If available, a mirrored copy of the
written to disk.
volume is used.
System Action: The failed I/O operation is retried on
User Response: Correct the cause of the write errors.
a mirrored volume.
User Response: See accompanying messages for
ANR0204W Recovery log volume volume name varied
information about the volume in error.
offline due to excessive read errors.
Explanation: The recovery log volume shown has
ANR0209E Page address mismatch detected on
been varied offline because too many read errors have
recovery log volume volume name, logical
been encountered.
page logical page number (physical page
System Action: If available, a mirrored copy of the physical page number); actual: logical page
volume is used. number.
User Response: Correct the cause of the read errors. Explanation: During a read of a recovery log page, the
page does not contain the expected page address.
ANR0205W Recovery log volume volume name varied System Action: The failed I/O operation is retried on
offline due to excessive write errors. a mirrored volume.
Explanation: The recovery log volume shown has User Response: See accompanying messages for
been varied offline because too many write errors have information about the volume in error.
been encountered.
System Action: If available, a mirrored copy of the ANR0210S Inconsistency found in LVM data page
volume is used. page number - partial write detected.
User Response: Correct the cause of the write errors. Explanation: During a write of an LVM internal page,
an error occurs so that the page is not completely
written to disk.
ANR0206W Partial write detected on database
volume volume name, logical page logical System Action: The failed I/O operation is retried on
page number (physical page physical page a mirrored volume.
number).
Explanation: During a write of a database page, an information about the volume in error.
error occurred so that the page was not completely
written to disk.
ANR0211S Inconsistency found in LVM data page
System Action: The failed I/O operation is retried on page number - page address mismatch
a mirrored volume. (actual page number).
User Response: See accompanying messages for Explanation: During a read of an LVM internal page,
information about the volume in error. the page does not contain the expected page address.
ANR0207E Page address mismatch detected on a mirrored volume.
database volume volume name, logical
page logical page number (physical page
physical page number); actual: logical page
number.
ANR0212E Unable to read disk definition file file
Explanation: During a read of a database page, the
specification.
page does not contain the expected page address.
Explanation: At startup, the server cannot read the
indicated file in order to obtain a list of disk volumes
a mirrored volume.
to mount.
System Action: Server initialization fails.
Chapter 3. Common and Platform Specfic Messages 15

User Response: Use a text editor to recreate the file; it
ANR0218I Unable to install database volume
should contain one line with the name of a single log
volume name - capacity must be at least 5
or database volume. Then restart the server.
megabytes.
Explanation: An attempt has been made to add a
ANR0213W Unable to rewrite disk definition file.
database volume that is smaller than the server
Explanation: An error occurs trying to update the disk minimum.
definition file.
System Action: The volume is not added.
System Action: None.
User Response: Increase the size of the volume or
User Response: Attempt to determine the cause of the supply another larger volume.
write error and correct it.
ANR0219I Unable to install recovery log volume
ANR0214W Database volume volume name is in the volume name - capacity must be at least 5
offline state - VARY ON required. megabytes.
Explanation: At system startup, the server finds that Explanation: An attempt has been made to add a
the specified database volume is in the offline state. recovery log volume that is smaller than the server
minimum.
System Action: The volume is not accessed.
System Action: The volume is not added.
User Response: Determine the reason for the volume
being offline; if possible, vary it online. User Response: Increase the size of the volume or
supply another larger volume.
ANR0215W Recovery log volume volume name is in
the offline state - VARY ON required. ANR0220I Synchronization of database volume
volume name started as process process ID.
Explanation: At system startup, the server finds that
the recovery log volume shown is in the offline state. Explanation: A background process was started to
synchronize the contents of the database volume shown
System Action: The volume is not accessed. with its copy volume. The background process was
User Response: Determine the reason for the volume assigned the process ID shown.
being offline; if possible, vary it online. System Action: The background process starts to
synchronize the volume and server operation continues.
ANR0216I Database volume volume name is in the User Response: The administrator may query the
″stale″ state - synchronization process status of the background process by using the QUERY
started. PROCESS command, or cancel the process by using the
Explanation: At system startup, the server finds that CANCEL PROCESS command.
the database volume shown is not synchronized.
System Action: A process is started to synchronize the ANR0221I Synchronization of recovery log volume
volume. volume name started as process process ID.
User Response: None. Explanation: A background process was started to

synchronize the contents of the recovery log volume
shown with its copy volume(s). The background
ANR0217I Recovery log volume volume name is in process was assigned the process ID shown.
the ″stale″ state - synchronization
process started. System Action: The background process starts to
synchronize the volume and server operation continues.
Explanation: At system startup, the server finds that
the recovery log volume shown is not synchronized. User Response: The administrator may query the
status of the background process by using the QUERY
System Action: A process is started to synchronize the PROCESS command, or cancel the process by using the
volume. CANCEL PROCESS command.
ANR0222E Error action disk definition file file
specification.
Explanation: An error occurred creating or changing
the disk definition file.

ANR0223E • ANR0242I
User Response: Attempt to determine the cause of the
ANR0233I Synchronization process canceled for
write error and correct it.
recovery log volume volume name.
Explanation: The process that was attempting to
ANR0223E Error writing list of disks to disk
synchronize the database volume shown has been
definition file.
canceled.
Explanation: The disk definition file cannot be
System Action: The volume is in the stale state.
written.
User Response: If desired, issue a VARY ONLINE
System Action: Installation ends.
command to start another synchronize process.
User Response: Determine the cause of the write error
and correct it.
ANR0234I Synchronization complete for database
volume volume name.
ANR0224E Volume volume name is specified more
Explanation: The synchronization process for the
than once - server installation failed.
database volume named has finished successfully.
Explanation: The specified volume name was
System Action: The volume is varied online.
specified more than once in the server installation
execution. User Response: None.
System Action: Installation ends.
ANR0235I Synchronization complete for recovery
User Response: Reinitialize the server install
log volume volume name.
specifying a unique name for each database and
recovery log volume. Explanation: The synchronization process for the
recovery log volume named has finished successfully.
ANR0230E Synchronization process failed for System Action: The volume is varied online.
database volume volume name.
synchronize the database volume shown has failed.
ANR0240E Deletion process failed for database
System Action: The volume is in the stale state. volume volume name.
User Response: See accompanying messages for more Explanation: The process that was attempting to
information. delete the database volume shown has failed.
System Action: The volume is not deleted.
ANR0231E Synchronization process failed for
User Response: See accompanying messages for more
information.
synchronize the recovery log volume shown has failed.
ANR0241E Deletion process failed for recovery log
System Action: The volume is in the stale state. volume volume name.
User Response: See accompanying messages for more Explanation: The process that was attempting to
information. delete the recovery log volume shown has failed.
ANR0232I Synchronization process canceled for
database volume volume name.
information.
synchronize the database volume shown has been
ANR0242I Deletion process canceled for database
canceled.
volume volume name.
System Action: The volume is in the stale state.
User Response: If desired, issue a VARY ONLINE delete the database volume shown has been canceled.
command to start another synchronize process.

ANR0243I • ANR0251E
ANR0243I Deletion process canceled for recovery ANR0248E Unable to read database page logical page
log volume volume name. number from any alternate copy.
Explanation: The process that was attempting to Explanation: After a read error, the server is unable to
delete the recovery log volume shown has been read the desired page from another mirrored volume
canceled. because no other mirrored volume is 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
ANR0244I Deletion complete for database volume
halting the server and correcting the volume errors.
volume name.
Explanation: The delete process for the database
ANR0249E Error reading logical page logical page
volume named has finished successfully.
number (physical page physical page
System Action: The volume is deleted. number) from recovery log volume
volume name.
Explanation: An error has been encountered when
attempting to read a page from the specified recovery
ANR0245I Deletion complete for recovery log log volume.
volume volume name.
Explanation: The delete process for the recovery log a mirrored volume, if available.
volume named has finished successfully.
System Action: The volume is deleted. information about the volume in error. If the error
User Response: None. 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.
ANR0246E Error reading logical page logical page
number) from database volume volume ANR0250I Recovery log page logical page number
name. successfully read from an alternate copy
on volume volume name.
Explanation: An error has been encountered when
attempting to read a page from the specified database Explanation: After a read error, the server is able to
volume. read the desired page from another synchronized
mirrored volume.
a mirrored volume, if available. System Action: Processing continues.
User Response: See accompanying messages for User Response: None.

information about the volume in error. If the error
persists and another mirrored copy of the volume is ANR0251E Unable to read recovery log page logical
available, the failing volume should be taken offline by page number from any alternate copy.
using the VARY OFF command, and repaired.
Otherwise, halt the server and repair the volume. Then Explanation: After a read error, the server is unable to
restart the server. read the desired page from another mirrored volume
because no other mirrored volume was in the
synchronized state. This message is normally preceded
ANR0247I Database page logical page number by a message indicating which volume failed.
successfully read from an alternate copy
on volume volume name. System Action: Processing is ended.
Explanation: After a read error, the server is able to User Response: You can repair the failed volume by
read the desired page from another synchronized halting the server and correcting the volume errors.
mirrored volume.
System Action: Processing continues.

ANR0252E • ANR0259E
ANR0252E Error writing logical page logical page ANR0256E Error writing physical page physical page
number (physical page physical page number to restart/checkpoint area on
number) to database volume volume name. database volume volume name.
Explanation: An error has been encountered when Explanation: An error has been encountered when
attempting to write a page to the specified database attempting to write a page to the specified database
volume. volume.
System Action: If a mirrored volume is available then System Action: If a mirrored volume is available, the
the failing volume is forced into the offline state. failing volume is forced into the offline state.
User Response: Repair the failing volume, and then User Response: Repair the failing volume, and then
use the VARY ON command to bring the volume back use the VARY ON command to bring the volume back
online. online.
ANR0253E Unable to write database page logical ANR0257E Error writing physical page physical page
page number to any alternate copy. number to restart/checkpoint area on
Explanation: After a write error, the server is unable
to write the desired page to another mirrored volume Explanation: An error has been encountered when
because no other mirrored volume is in the attempting to write a page to the specified database
synchronized state. This message is normally preceded volume.
by a message indicating which volume failed.
System Action: If a mirrored volume is available, the
System Action: Processing is ended. failing volume is forced into the offline state.
User Response: Repair the failed volume. User Response: Repair the failing volume, and then
use the VARY ON command to bring the volume back
online.
ANR0254E Error writing logical page logical page
number) to recovery log volume volume ANR0258E Unable to write complete
name. restart/checkpoint information to disk.
Explanation: An error has been encountered when Explanation: While writing restart/checkpoint
attempting to write a page to the specified recovery log information to disk, the server encounters an error
volume. writing to a database or recovery log volume for which
no synchronized mirrored copy is available. This
System Action: If a mirrored volume is available, the
message is normally preceded by a message indicating
failing volume is forced into the offline state.
which volume failed.
User Response: Repair the failing volume, and then
System Action: Processing is ended.
use the VARY ON command to bring the volume back
online. User Response: Repair the failing volume.
ANR0255E Unable to write recovery log page logical ANR0259E Unable to read complete
page number to any alternate copy. restart/checkpoint information from any
database or recovery log volume.
Explanation: After a write error, the server is unable
to write the desired page to another mirrored volume Explanation: During server restart, the server is
because no other mirrored volume is in the unable to read a complete set of restart/checkpoint
synchronized state. This message is normally preceded information from any of the defined database or
by a message indicating which volume failed. recovery log volumes.
System Action: Processing is ended. System Action: Server restart is ended.
User Response: You can repair the failed volume by User Response: Ensure that all defined database and
halting the server and correcting the volume errors. recovery log volumes are available for use by the
server.

ANR0260I • ANR0285I
unavailable, andcorrect the problem. Restart the server.
ANR0260I Database page logical page number
successfully resynchronized.
ANR0269E Process for Log volume volume name
Explanation: After detecting a partially-written
terminated - thread resource not
database page, the server is able to rewrite the page by
available.
using a synchronized mirror copy.
Explanation: During installation for the indicated
volume, the server cannot start a thread to service I/O
User Response: None. requests.
System Action: Server installation stops.
ANR0261I Recovery log page logical page number
successfully resynchronized.
Explanation: After detecting a partially-written information online or see “Appendix A. Allocating
recovery log page, the server is able to rewrite the page Additional Server Memory”. Restart the server
by using a synchronized mirror copy. installation process.
ANR0270E Process for Database volume volume
name terminated - thread resource not
available.
ANR0265E Log disk processing failed: sufficient
Explanation: During installation for the indicated
memory is not available.
volume, the server cannot start a thread to service I/O
Explanation: At server installation, the server is requests.
unable to process the server log disks due to
insufficient memory.
User Response: Restart the server installation process information online or see “Appendix A. Allocating
with more memory available. Additional Server Memory”. Restart the server
installation process.
ANR0266E Database disk processing failed:

sufficient memory is not available. ANR0271E Maximum number of recovery log
volumes exceeded.
Explanation: At server installation, the server is
unable to process the server database disks due to Explanation: More recovery log volumes have been
insufficient memory. specified than the server can manage.
System Action: Server installation stops. System Action: Server installation stops.
User Response: Restart the server installation process User Response: Reduce the number of recovery log
with more memory available. volumes specified. Restart the server installation
process.
ANR0267E Log volume volume name is not available.
ANR0272E Maximum number of database volumes
Explanation: The specified volume cannot be found exceeded.
during installation.
Explanation: More database volumes have been
System Action: Server installation stops. specified than the server can manage.
User Response: Determine the reason the disk is System Action: Server installation stops.
unavailable, and correct the problem. Restart the server
installation process. User Response: Reduce the number of database
volumes specified. Restart the server installation
process.
ANR0268E Database volume volume name is not
available.
ANR0285I Database page shadowing started using
Explanation: The specified volume cannot be found file file name.
during installation.
Explanation: The database page shadowing function
System Action: Server installation stops. was started. The file specified is used to store the
User Response: Determine the reason the disk is shadowed database pages.

ANR0286W • ANR0300I
ANR0289W Damaged database pages were
User Response: None. successfully replaced using contents of
page shadow file.
ANR0286W Database page shadowing using file file Explanation: The damaged database pages were
name failed to start. replaced using the corresponding pages from the page
shadow file. The pages were successfully replaced.
Explanation: The database page shadowing function
could not start. An error has been encountered System Action: The server continues to restart.
accessing the page shadow file specified.
User Response: Verify that there is enough space for ANR0290W Failure occurred attempting to replace
the page shadow file. That page shadow file requires one or more damaged database pages
approximately 65 kilobytes of space, if this space is not using the contents of the page shadow
available a new location for the file should be specified. file.
Explanation: The damaged database pages could not
ANR0287W Contents of the page shadow file file be replaced using the corresponding pages from the
name are not valid. page shadow file.
Explanation: The database page shadowing function System Action: The server continues to restart.
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
ANR0291E Error writing to db page shadow file -
having the database page shadow file available.
restart will be attempted.
User Response: The database page shadow file
Explanation: The server encountered an error writing
contents are not valid. This can be caused by: a partial
to the database page shadow file. The page shadowing
write to the page shadow file itself, the file being
for the server is currently disabled.
manipulated by a process outside of the server, the file
being overlayed by a different file, or the file could System Action: The server will attempt to restart the
have been erased. database page shadowing for the server once a minute
until it is restarted or until the server is halted.
ANR0288W One or more database pages in the last User Response: Check the file specified as the
batch written is corrupt - contents of database page shadow file. It may be that there is not
database page shadow file will be used enough space for the file. If enough space is available,
to fix the page or pages. check the filesystem, drive, or disk that it resides on for
an indication of the error. Once the error preventing the
Explanation: One or more pages from the last batch of
server from writing to the page shadow file has been
pages written to the server database has been detected
resolved, the server will recovery and begin writing to
to be corrupt. The server will attempt to use the
the page shadow file again.
contents of database page shadow file and replace the
corrupted database page.
ANR0292W Database page shadow file file name does
System Action: Server startup continues.
not exist.
User Response: A corruption of a database page
Explanation: The server attempted to use the page
within the server database, is typically caused by a
shadow file referenced but was unable to open the file.
partial write. A partial write may occur when the
The file does not exist.
server is brought down external to normal server
processing. If the server terminated without a halt System Action: The server will continue to operate
command being issued or if the machine the server is and will attempt to create this as a new database page
running on crashed unexpectedly, this may account for shadow file.
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 ANR0300I Recovery log format started; assigned
appropriate action to prevent this from occurring in the capacity count megabytes.
future.
Explanation: Initial formatting of the server recovery
log has started.

ANR0301I • ANR0314W
System Action: The log is formatted for use by the
ANR0307I Recovery log extend in progress; count
server.
megabytes of count formatted.
Explanation: As a result of an EXTEND LOG
command, the additional recovery log pages are being
ANR0301I Recovery log format in progress; count formatted.
megabytes of count.
System Action: Formatting continues.
Explanation: The amount of the server recovery log
shown has been successfully formatted.
System Action: Formatting continues.
ANR0309I Recovery log extend terminated -
User Response: None. process canceled.
Explanation: The process started as a result of an
ANR0302I Recovery log formatting took mseconds EXTEND LOG command and has been canceled.
milliseconds.
System Action: The EXTEND command is ended.
Explanation: Formatting of the recovery log has
completed and took the number of milliseconds shown.
ANR0311I Recovery log reduce in progress; count
User Response: None. megabytes of count moved.
Explanation: As a result of a REDUCE LOG
ANR0303I Format rate: rate pages/second. command, the amount of data from the recovery log
shown has been moved.
Explanation: During formatting, the formatter
processed the number of pages indicated each second. System Action: The REDUCE LOG command
continues.
ANR0313I Recovery log reduce terminated -

ANR0304I Page service time: rate ms. process canceled.
Explanation: During formatting, the formatter Explanation: The process started as a result of a
required the number of milliseconds indicated to REDUCE LOG command and has been canceled.
process each page.
System Action: The REDUCE command is ended.
ANR0314W Recovery log usage exceeds utilization

ANR0305I Recovery log format complete. percentage % of its assigned capacity.
Explanation: Formatting of the server recovery log Explanation: This message is issued to notify the
completed successfully. administrator that the server recovery log utilization
System Action: None. exceeds 90% or more of its assigned capacity.
User Response: None. System Action: Server operation continues.

User Response:
ANR0306I Recovery log volume mount in progress. v If the server is operating in NORMAL log mode,
depending upon the size of your recovery log, add
Explanation: During restart, the server is mounting recovery log volumes, or extend the recovery log, or
required recovery log volumes. both, before it fills completely. Refer to the DEFINE
System Action: None. LOGVOL, and EXTEND LOG commands for more
information on these operations.
User Response: None. 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
ANR0356I Recovery log compression started.
defined
Explanation: The process of removing unneeded data
Refer to the DEFINE DBBACKUPTRIGGER or
from the server recovery log has begun.
UPDATE DBBACKUPTRIGGER commands.
ANR0350I Recovery checkpoint started. User Response: None.
Explanation: During server initialization, the process
of bringing the server database back to a state of ANR0357I Recovery log compression ended.
consistency has begun.
Explanation: The process of removing unneeded data
System Action: None. from the server recovery log has completed.
User Response: None. System Action: None.
ANR0351I Recovery checkpoint complete.
Explanation: During server initialization, the process ANR0358E Database initialization failed: sufficient
of bringing the server database back to a state of memory is not available.
consistency has completed successfully.
Explanation: During server initialization, the server
System Action: None. database fails initialization because sufficient server
System Action: Initialization fails.
ANR0352I Transaction recovery complete. User Response: Make more memory available to the
server.
of recovering any incomplete transactions has
completed successfully. ANR0359E Database initialization failed: unable to
read database restart record.
Explanation: During server initialization, the server
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
User Response: None. size mismatch; LVM size = size, expected
size = size.
ANR0354I Recovery log redo pass in progress. Explanation: During server initialization, the server
database initialization fails because the size of the
Explanation: During server initialization, the process database does not match its prior size.
of committing incomplete transactions has begun.
ANR0361E Database initialization failed: error

ANR0355I Recovery log undo pass in progress. initializing database page allocator.
Explanation: During server initialization, the process Explanation: During server initialization, the server
of rolling back incomplete transactions has begun. database initialization fails because the page allocator
System Action: None. cannot be started.
User Response: None. System Action: Initialization fails.


additional kilobytes of buffer pool space that are
ANR0362W Database usage exceeds utilization
required are indicated in the message.
percentage % of its assigned capacity.
System Action: Server operation continues; the
Explanation: This message is issued to notify the
additional buffer pool space is obtained from available
administrator that the server database utilization
server memory.
exceeds 80% or more of its assigned capacity.
User Response: If the current server load is typical,
System Action: Server operation continues.
consider increasing the size specified for your
User Response: Depending upon the size of your BUFPOOLSIZE option by the number of kilobytes
database, add database volumes, or extend the specified in the message. To do this, you must halt the
database, or both, before it fills completely. The server server, change the options file, and then restart the
expiration process may also free up database space server.
making it available to other server processes. Refer to
the EXPIRE INVENTORY, DEFINE DBVOL, and
ANR0381I Bufferpool statistics were successfully
EXTEND DB commands for more information on these
reset.
operations.
Explanation: Bufferpool statistics, such as the Cache
Hit Ratio, have been reset by the RESET BUFPOOL
ANR0363I Database was automatically upgraded to
command.
the server program level.
Explanation: This message is issued to notify the
administrator that the server database was User Response: The QUERY DB command
automatically upgraded to the current server program (FORMAT=DETAILED) can be used to to display the
level. The upgrade is performed when the current values for the buffer pool statistics.
UPGRADEDB parameter is specified at server start-up
and the server is started over a database that was
written by a down-level version of the server program. ANR0382I The database maximum utilization
statistic was successfully reset.
Explanation: The database maximum utilization
User Response: None. The UPGRADEDB parameter statistic has been reset by the RESET
does not need to be specified during future server DBMAXUTILIZATION command to the current
start-ups. utilization.
ANR0364W Server has detected a zero bit mismatch
error. User Response: The QUERY DB command
(FORMAT=DETAILED) can be used to display the
Explanation: This message is issued to notify the current value for the maximum utilization.
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 ANR0383I The recovery log maximum utilization
a process that includes a DSMSERV FORMAT. Either statistic was successfully reset.
the data base volumes must be formatted then a Explanation: The recovery log maximum utilization
DSMSERV RESTORE DB performed from a data base statistic has been reset by the RESET
backup that does not have this problem, or a LOGMAXUTILIZATION command to the current
DSMSERV UNLOADDB followed by the formatting, utilization.
then a DSMSERV LOADDB. Do not use DSMSERV
DUMPDB on the data base for this recovery. System Action: Server operation continues.
System Action: Server RESTORE DB continues. User Response: The QUERY LOG command
(FORMAT=DETAILED) can be used to display the
User Response: Perform one of the data base recovery current value for the maximum utilization.
actions after the RESTORE DB completes.
ANR0384I The recovery log consumption statistic

ANR0380W The database buffer pool recovered was successfully reset.
from an overcommit of number of pages
pages. Consider increasing your buffer Explanation: The recovery log consumption statistic
pool size by kilobytes needed kilobytes has been reset by the RESET LOGCONSUMPTION
under current server load. command.
Explanation: During normal processing, additional System Action: Server operation continues.
buffer pool space is required beyond that specified in User Response: The QUERY LOG command
the BUFPOOLSIZE in the server options file. The

(FORMAT=DETAILED) can be used to display the platform type and communication method used by this
current value for recovery log consumption. session are included in the message.
System Action: The server begins a communications
ANR0385I Could not free sufficient buffers to session to service the client node.
reach reduced BUFPoolsize.
Explanation: A reduction in the database buffer pool
size was requested. However, too many buffers were in
ANR0401I Session session number started for node
use to reach the lower buffer pool size.
node name (client platform) (communication
System Action: Server operation continues. Whatever method) (WDSF client).
buffer pool size reduction that could be achieved is in
Explanation: A new WDSF client session has been
effect. The new bufpoolsize is written to the options file
initiated by the specified node. The session number,
for use on the next server startup.
client platform type and communication method used
User Response: None. by this session are included in the message.
ANR0386I The BUFPoolsize has been changed to session to service the client node.
buffer pool size.
Explanation: The BUFPoolsize option has been
changed to the indicated value.
ANR0402I Session session number started for
System Action: Server operation continues. administrator administrator ID
(administrator’s platform) (communication
method).
Explanation: A new administrator client session has
ANR0390W A server database deadlock situation has
been initiated by the specified administrator. The
been encountered: lock request for
session number, administrator’s platform type and
transaction transaction ID will be denied
communication method used by this session are
to resolve the deadlock.
included in the message.
Explanation: The server detected a deadlock situation
between a number of processes attempting to access
session to service the administrator client.
database information. A lock request for one of the
processes will be denied to resolve the database User Response: None.
deadlock. When server processes encounter a database
deadlock, they usually reattempt the function that was
ANR0403I Session session number ended for node
in progress when the deadlock was encountered. Not
node name (client platform).
all process can explicitly re-try an operation. For
example, migration and reclamation will eventually Explanation: A client session has completed normally.
retry. However, something like a delete volume run in a
macro will only retry if the delete command is reissued System Action: Server operation continues.
either in the macro or the command line. User Response: None.
System Action: A lock request fails for one of the
deadlocked processes. Server operation continues. ANR0404I Session session number ended for node
User Response: If a process can retry (like migration), node name (client platform) (WDSF client).
then monitor the re-try attempt to see if it succeeds or Explanation: A WDSF client session has completed
not. If it fails, contact a service representative. If the normally.
process or command is not able to retry on it’s own,
then reissue the command or macro that caused the System Action: Server operation continues.
action to occur. If it fails again, contact a service User Response: None.
representative for further assistance to better isolate the
deadlock condition.
ANR0405I Session session number ended for
administrator administrator ID (client
ANR0400I Session session number started for node platform).
method). Explanation: An administrative client session has
completed normally.
Explanation: A new client session has been initiated
by the specified node. The session number, client System Action: Server operation continues.

User Response: None. does not have sufficient authority to perform the
import operation on the target server.
ANR0406I Session session number started for node System Action: Server operation continues.
method communication address).
Explanation: A new client session has been initiated
ANR0411I Session session number for administrator
by the specified node. The session number, client
administrator name logged in as node node
platform type, communication method and address
name restored or retrieved object type
used by this session are included in the message.
object: node node name, filespace filespace
System Action: The server begins a communications name, object object name.
session to service the client node.
Explanation: This message logs information about an
User Response: None. object that was restored or retrieved by an
administrator logged in for a node.
ANR0407I Session session number started for System Action: Server operation continues.
administrator administrator ID
(administrator’s platform) (communication
method communication address).
ANR0412I Session session number for node node
Explanation: A new administrator client session has
name restored or retrieved object type
been initiated by the specified administrator. The
object: node node name, filespace filespace
session number, administrator’s platform type,
name, object object name.
communication method and address used by this
session are included in the message. Explanation: This message logs information about an
object that was restored or retrieved by an
administrator logged in for a node.
ANR0408I Session session number started for server
server name (server’s platform) ANR0413I Session session number for administrator
(communication method) for purpose. administrator name logged in as node node
name is restoring backup set: node node
Explanation: A new server session has been initiated
name, set filespace name.
by the specified server for the specified purpose. The
session number, server’s platform type and Explanation: This message logs information about a
communication method used by this session are backup set restored by an administrator logged in for a
included in the message. node.
System Action: The server begins a communications System Action: Server operation continues.
ANR0414I Session session number for node node

ANR0409I Session session number ended for server name is restoring backup set: node node
server name (client platform). name, set filespace name.
Explanation: A server has completed normally. Explanation: This message logs information about a
backup set restored by a node.
ANR0410E EXPORT operation to server server name
rejected - administrator administrator is ANR0418W Session session number for administrator
not authorized to perform the import administrator name (client platform) refused
operation on the target server. - invalid password submitted.
Explanation: An export operation to the named server Explanation: The server refuses a request to start a
was rejected, because the administrator issuing the client session because an invalid password has been
export command is not defined on the target server or submitted by the client during sign-on processing. The

ANR0419W • ANR0425W
server will continue to deny access attempts by this User Response: Register the node name with the
client until a valid password is submitted. 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
User Response: Enter the proper password. If the registers the client with the server. If CLOSED
password has been forgotten by the user, an authorized registration is in effect on the server, an authorized
administrator can assign a new password by using the administrator must use the REGISTER NODE
UPDATE ADMIN command. command to register the client node name with the
server.
ANR0419W Administrative client userid

administrative ID cannot be used when ANR0423W Session session number for administrator
authentication is on. administrator ID (client platform) refused -
administrator name not registered.
Explanation: The server refuses a request for a client
(administrative) session because the user ID specified Explanation: The server refuses a request to start an
cannot be used when authentication of IDs is in effect. administrative session because the administrator name
SERVER_CONSOLE is an administrative ID that has is not registered in the server database.
this restriction.
User Response: Register the administrator name with
User Response: Use an administrative ID that was the server before establishing a session. An authorized
registered for this server and that has a password. administrator must use the REGISTER ADMIN
command to register the administrator with the server.
ANR0420W Session session number for node node

name (client platform) refused - server ANR0424W Session session number for node node
disabled for user access. name (client platform) refused - invalid
password submitted.
Explanation: The server refuses a request for a client
(backup-archive) session because the server is currently Explanation: The server refuses a request to start a
disabled for client access. client session because an invalid password has been
submitted by the client during sign-on processing. The
System Action: Server operation continues. server will continue to deny access attempts by this
Administrative clients are permitted access to the client until a valid password is submitted.
server.
User Response: An authorized administrator must
issue the ENABLE command before client nodes are User Response: Enter the proper password. If the
permitted access to the server. password has been forgotten by the user, an authorized
administrator can assign a new password by using the
UPDATE NODE command.
name (client platform) refused - sign-on
protocol violation. ANR0425W Session session number for node node
name (client platform) refused - password
Explanation: The server refuses a request for a client has expired.
session because sign-on protocol has been violated.
Explanation: The server refuses the specified session
System Action: Server operation continues. because the administrator or client node’s password
User Response: This error is usually the result of a has expired.
client programming error in which the sign-on verb has System Action: Server operation continues.
been incorrectly formatted and delivered to the server.
This error can also result when the server is contacted User Response: Upon receipt of this error condition,
by an application that is not a part of this product. the client program immediately reconnects to the server
specifying a password update session and prompts the
user for a new password. After the user enters a new
ANR0422W Session session number for node node password, the client reconnects to the server for normal
name (client platform) refused - node operations. Alternatively, an authorized administrator
name not registered. can update the client password using the UPDATE
Explanation: The server refuses a request to start a NODE or UPDATE ADMIN command.
client session because the client node name is not
registered in the server database.

ANR0426W Session session number for node node ANR0430W Session session number for node node
name (client platform) refused - open name (client platform) refused - node
registration not permitted. name is locked.
Explanation: The server refuses a client session Explanation: The server refuses the specified client
because an open registration action has been attempted session because the node is locked from server access
and the server is running with CLOSED registration. (with the LOCK NODE command).
System Action: Server operation continues. System Action: Server operation continues.
User Response: Ask an authorized administrator to User Response: Before the client node is permitted to
submit the request using the REGISTER NODE or access the server, a properly authorized administrator
REGISTER ADMIN command. must unlock the node with the UNLOCK NODE
command.
name (client platform) refused - server ANR0431W Session session number refused -
version is down-level with this client. administrator administrator ID (client
platform) is locked.
Explanation: The server refuses a client session
because the client program version level is newer than Explanation: The server refuses the specified
that supported by the server program. administrative session because the administrator is
locked from server access (with the LOCK ADMIN
command).
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. User Response: Before the administrator is permitted
to access the server, a properly authorized
administrator must unlock the administrator with the
UNLOCK ADMIN command.
name (client platform) refused - client is
down-level with this server version.
name (client platform) refused -
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 Explanation: The server ends the specified session
connects to the server using the newer client, the server because sufficient memory (virtual memory) is not
records this fact and will not let this node back off this available.
client version to a version that does not include the fix.
System Action: The server ends the session and
System Action: Server operation continues. continues operation.
User Response: Apply service to the client program to User Response: Allocate additional storage to the
make it compatible with the newer server program. server. For details, issue HELP MEMORY to display the
name (client platform) refused - maximum
server sessions (max sessions allowed) ANR0433W Session session number for node or
exceeded. administrator ID (client platform) refused -
insufficient recovery log space.
Explanation: The server refuses the specified client or
administrative session because the maximum number Explanation: The server ends the specified client or
of concurrent client sessions has been exceeded. administrative session because sufficient log space is
not available to complete a database transaction.
User Response: If necessary, increase the maximum
continues operation.
number of permitted sessions. To do this, update the
value for the MAXSESSIONS parameter in the server User Response: To increase the amount of log space
options file and restart the server with the updated available to the server, an authorized administrator can
options file. Note that increasing the MAXSESSIONS add log volumes using the DEFINE LOGVOLUME
value requires additional memory resource by the command, and extend the size of the log using the
server. You may want to retry the connection at a later EXTEND LOG command.
time.

User Response: Use the QUERY LICENSE and
ANR0434W Session session number for node or
QUERY STATUS commands to determine if the server
administrator ID (client platform) refused -
is in compliance with license terms. Start an AUDIT
insufficient database space.
LICENSES process to re-adjust server license
Explanation: The server ends the specified client or information. When this process completes you may
administrative session because sufficient database space restart the session. If the problem persists, contact your
is not available to complete a database transaction. service representative.
continues operation. ANR0438W Session session number archive operation
for client client node name (client platform)
has been denied - Server is not in
compliance with license terms.
administrator can add database volumes using the
DEFINE DBVOLUME command, and extend the size of Explanation: The server refuses a client archive
the database using the EXTEND DB command. operation because the current server configuration is
not in compliance with license terms.
ANR0435W Session session number for node node System Action: Server operation continues. Clients
name (client platform) refused - internal may perform any action except backup or archive.
error detected.
User Response: Use the QUERY LICENSE command
Explanation: The server ends the specified session to determine the license terms that are no longer in
because an internal logic error is detected. compliance.
continues operation. ANR0439W Session session number backup operation
for client client node name (client platform)
User Response: To determine the source of the error,
has been denied - Server is not in
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 Explanation: The server refuses a client backup
messages. If the error cannot be isolated and resolved, operation because the current server configuration is
contact your service representative. not in compliance with license terms.
System Action: Server operation continues. Clients
ANR0436W Session session number refused - a WDSF may perform any action except backup or archive.
client is attempting to access the server
using client name client node name (client
to determine the license terms that are no longer in
platform), associated with a non-WDSF
compliance.
client.
ANR0440W Protocol error on session session number
because a Workstation DataSave Facility (WDSF) client
for node client node name (client platform) -
is attempting to access the server using a node name
invalid verb header received.
associated with a non-WDSF client. When converting
from WDSF, WDSF client programs cannot be used to Explanation: The server detects a protocol error on the
access the server with a specific node name once the specified session because an invalid verb header has
non-WDSF client program has been used to access the been received from the client. Verb headers always
server with that node name. precede communication sent to the server from the
client or from the server to the client.
System Action: The server ends the client session.
User Response: Access the server using a non-WDSF
client program for the node name. User Response: Correct the programming error in the
client program if it has been written by your
installation using WDSF verbs. Otherwise, contact your
ANR0437W Session session number for node client
service representative.
node name (client platform) encountered an
internal server error while checking
license compliance. ANR0441W Protocol error on session session number
for node client node name (client platform) -
Explanation: The server encountered an internal error
invalid data length received.
in determining if the server is in compliance with
license terms. Explanation: The server detects a protocol error on the
specified session because an invalid verb length has
System Action: The client session is ended.

been received from the client.
System Action: The server ends the client session. for node client node name (client platform) -
maximum group transaction size
User Response: Correct the programming error in the exceeded.
client program if it has been written by your
installation using WDSF verbs. Otherwise, contact your Explanation: The server detects a protocol error on the
service representative. specified session because the client has attempted to
group more than the maximum database update
operations in a single database transaction.
for node client node name (client platform) - System Action: The server ends the client session.
excessively large verb received.
User Response: Correct the programming error in the
Explanation: The server detects a protocol error on the client program if it has been written by your
specified session because an invalid verb length has installation using WDSF verbs. Otherwise, contact your
been received from the client. service representative.

ANR0446W Session session number client client node
User Response: Correct the programming error in the name compression method unsupported -
client program if it has been written by your Compression forced OFF. Please obtain
installation using WDSF verbs. Otherwise, contact your the latest level of the client code.
Explanation: The client is using a compression
method that is no longer supported by the Server.
for node client node name (client platform) - System Action: Server operation continues. The
invalid ″field name″ field found in ″verb client’s backup operation continues, without
name″ verb (offset offset position). compressing the data.
Explanation: The server detects a protocol error on the User Response: The compression method used by the
specified session because an invalid field has been client is no longer supported. In order to use
found in a verb sent from the client node. compression, the client needs to be upgraded to a client
service level that supports the newer compression
System Action: The server ends the client session. method.
User Response: Correct the programming error in the
client program if it has been written by your ANR0447W Session session number space
installation using WDSF verbs. Otherwise, contact your management migration operation for
service representative. client client node name (client platform) has
been denied - Server is not in
ANR0444W Protocol error on session session number compliance with license terms.
for node client node name (client platform) - Explanation: The server refuses a client space
out-of-sequence verb (type verb name) management migration operation because the current
received. server configuration is not in compliance with license
Explanation: The server detects a protocol error on the terms.
specified session because a verb has been received that System Action: Server operation continues. Clients
does not adhere to the client-server exchange sequence. may perform any action except backup, archive, or
System Action: The server ends the client session. space-managed file migration.
User Response: If the client generating the error is not User Response: Use the QUERY LICENSE command
an API client, contact your service representative. If the to determine the license terms that are no longer in
client generating the error is an API client, contact the compliance.
owner of the API client. If the client generating the
error is a client that you have created using WDSF ANR0448W Session session number space
verbs, correct the programming error in your client management migration operation for
program. client client node name (client platform) has
been denied - server is not licensed for
space management support.
Explanation: The server refuses a client space
management migration operation because the server is
not licensed to support space-managed clients.

ANR0452W Session for server server name refused -
User Response: Licenses to support space-managed server name not defined for server to
clients can be obtained from your service provider or server communications.
reseller. The REGISTER LICENSE command can be
Explanation: The server refuses a request to start a
used with these licenses to enable space management
server to server session because a server name is not
support.
defined in the server database, or the server definition
does not have a SERVERPASSWORD. Server to server
ANR0449W Session session number space communications using the serverpassword requires that
management migration operation for the each server has had a server definition for the other
client client node name (client platform) is server.
in violation of server license terms -
server is not licensed for space
management support. User Response: Register the server names on both
both servers before establishing a session, or update the
Explanation: The server warns about a client space
server’s existing server definition and set a
management migration operation because the server is
SERVERPASSWORD. An authorized administrator
not licensed to support space-managed clients.
must use the DEFINE SERVER or UPDATE SERVER
System Action: Server operation continues. command register the servers and set the passwords.
User Response: Licenses to support space-managed

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

session. For a reason of INTERNAL ERROR, use the
ANR0459W Signon for administrator administrator
messages on the target server to determine the problem
name refused - invalid administrator
and contact your service representative. Retry the
name and/or password submitted.
failing operation.
Explanation: The server refuses a request to start an
administrative session because an invalid administrator
ANR0455W Invalid Command command name for
name and/or password has been submitted by the user
SNMP session.
during sign-on processing. The server will continue to
Explanation: An SNMP administrative session deny access attempts by this administrator until a valid
attempted to run a command which is not an macro password is submitted, or until the administrator is
invocation. SNMP administrative sessions are only locked due to maximum number of invalid password
allowed to issue macro commands. attempts being exceeded.
System Action: The server ends the client session. System Action: Server operation continues.
User Response: Enter commands through the SNMP User Response: Enter the proper password. If the
administrative interface which are macros defined on password has been forgotten by the user, an authorized
the server. administrator can assign a new password by using the
UPDATE ADMIN command.
ANR0456W Session rejected for server name server

name at High level address Low level ANR0460W Open registration failed for session
address does not match. 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 Explanation: The server refuses a client session during
connection is not established. 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, User Response: The client program user must specify
and that the servername on the server being contacted a different node name for the client in the client
matches the name used in the DEFINE SERVER options file.
command.
ANR0461W Open registration failed for session
ANR0457W Session for server server name refused - session number for node node name (client
crossdefine is not allowed on this platform) - policy domain STANDARD
server. does not exist.
Explanation: The server refuses a request to start a Explanation: The server refuses a client session during
server to server session for crossdefine because it is not open registration because the STANDARD policy
allowed on this server. The server will deny any domain does not exist. All nodes added to the server
sessions for crossdefine until crossdefine is allowed on database under open registration are automatically
this server. assigned to the STANDARD policy domain. This policy
domain must be defined and have an active policy set
System Action: Server operation continues. to support open registration.
User Response: An authorized administrator must use System Action: Server operation continues.
the SET CROSSDEFINE ON command to allow cross
registration of servers. User Response: If you want to support open
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and
ANR0458S Server server name does not support activate a valid policy set in the domain. You can issue
access by the Storage Agent. the UPDATE NODE command to move nodes to
Explanation: The storage agent attempted to contact a different policy domains after the nodes have registered
Database Server, but the server contacted was not at themselves through open registration.
the correct level.
System Action: The Storage Agent terminates. ANR0462W Open registration failed for session
session number for node node name (client
User Response: Specify a correct Database Server in platform) - invalid node name.
the devconfig file for the Storage Agent.
Explanation: The server refuses a client session during
open registration because the node name specified by
the client is not valid.

ANR0466E The SETSTORAGESERVER command
User Response: Specify a node name in the options did not complete successfully.
file of the client program that contains valid characters
Explanation: The SETSTORAGESERVER command
and does not exceed the maximum length in size. Refer
encountered an error and did not complete successfully.
to Backup-Archive Installation and User’s Guide for a
description of the node name restrictions. System Action: Storage agent operation terminates.
User Response: Please review prior error messages
ANR0463W Open registration failed for session and take the necessary corrective actions.
platform) - invalid password.
ANR0467I The SETSTORAGESERVER command
Explanation: The server refuses a client session during completed successfully.
open registration because the password name specified
Explanation: The SETSTORAGESERVER command
by the user is not valid.
has completed successfully, and the appropriate device
System Action: Server operation continues. configuration files have been updated.
User Response: Specify a password that uses valid System Action: Storage agent operation terminates.
characters and is less than the maximum length in size.
User Response: None
Refer to Backup-Archive Installation and User’s Guide for a
description of the password restrictions.
ANR0478W Session request refused. Server is
running in standalone mode.
session number for node node name (client Explanation: A client has requested a session with the
platform) - exceeded number of nodes server. The server is running in a mode in which it
available under license terms. cannot start client sessions.
Explanation: The server detected an attempt to System Action: The session request is refused. The
register more nodes than allowed by the terms of the server operation continues.
current license.
User Response: No response is required. To reduce or
System Action: Server operation continues, but the disable the display of this message, you can update the
REGISTER NODE command fails, and the node is not server options before running in standalone mode with
registered. the COMMMETHOD NONE option. This will allow the
server to run without enabling client connections.
compliance. ANR0479W Session session number for server server
name (server platform) terminated -
connection with server severed.
session number for node node name (client Explanation: If server A has opened a connection with
platform) - policy domain STANDARD server B, server B’s session is ended because the
does not have an ACTIVE policy set. communications link has been closed by a network
error or by server A’s program.
Explanation: The server refuses a client session during
open registration because the STANDARD policy System Action: Server A continues operation.
domain does not have an active policy set. All nodes
added to the server database under open registration User Response: If server B halts operation or in some
are automatically assigned to the STANDARD policy way stops communicating with server A, this message
domain. This policy domain must be defined and have will be displayed on server A indicating that the
an active policy set to support open registration. connection was closed suddenly by server B. A network
failure can also cause this message to be displayed. If a
System Action: Server operation continues. large number of these messages occur simultaneously,
check the network for failure and correct any problems.
User Response: If you want to support open
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and ANR0480W Session session number for node node
activate a valid policy set in the domain. You can issue name (client platform) terminated -
the UPDATE NODE command to move nodes to connection with client severed.
different policy domains after the nodes have registered
themselves through open registration. Explanation: The specified client 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 name (client platform) terminated - forced
program, this message will be displayed on the server by administrator.
as the connection is suddenly closed by the client. A
Explanation: The server ends a client session in
network failure can also cause this message to be
response to a CANCEL SESSION command issued by
displayed. If a large number of these messages occur
an authorized administrator.
simultaneously, check the network for failure and
correct any problems. System Action: The server rolls back any transactions
in progress for the terminated client session.
ANR0481W Session session number for node node User Response: None.
name (client platform) terminated - client
did not respond within commtimeout
seconds seconds.
name (client platform) terminated -
Explanation: The server ends a client session because protocol violation detected.
the client has been holding database locks (a
Explanation: The server ends the specified session
transaction was in progress) and the client has not
because a communications protocol error by the client
responded in the number of seconds specified by the
has been detected.
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: Examine the client message to
Server operation continues. determine the problem. Correct the programming error
in the client program. If the error cannot be isolated
User Response: If a large number of these messages
and resolved, contact your service representative.
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 ANR0485W Session session number for node node
takes for a client to respond is dependent upon the name (client platform) terminated -
speed and processor load for the client and the network sufficient memory is not available.
load.
Explanation: The server ends the specified session
because sufficient memory (virtual memory) is not
ANR0482W Session session number for node node available.
name (client platform) terminated - idle for
more than idletimeout minutes minutes. System Action: The server ends the session and
Explanation: The server ends a client session because
it has been idle for more minutes than specified in the User Response: Allocate additional storage to the
IDLETIMEOUT parameter in the server options file. server. For details, issue HELP MEMORY to display the
The client program will automatically attempt to information online or see “Appendix A. Allocating
reconnect to the server when necessary. Additional Server Memory”.

User Response: If the problems persists, increase the name (client platform) terminated -
value specified for the IDLETIMEOUT parameter in the internal error detected.
server options file and restart the server. Many times,
the client program is idle while waiting for the user to Explanation: The specified client session is ended by
choose an action to perform (for example, backup, the server because an internal processing error has been
archive, restore, or retrieve files). If a user starts the detected on the server. A programming error may have
client program and does not choose an action to occurred in the server program.
perform, the session will eventually time out. The client System Action: The session is ended and server
program automatically reconnects to the server when operation continues.
the user chooses an action that requires server
participation. Note that a large number of idle sessions User Response: Contact your service representative.
can inadvertently prevent other users from connecting
to the server, so care should be used when increasing ANR0487W Session session number for node node
the IDLETIMEOUT parameter. 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 System Action: The session is canceled and server
was using. operation continues.
System Action: The server rolls back any transactions User Response: None.
in progress for the terminated client session.
User Response: Reissue the operation. If this message ANR0491I No matching session(s) found to cancel.
appears frequently, consider increasing the mountlimit
Explanation: The server cannot find any sessions to
value for the affected device class.
cancel matching the specifications entered in the
CANCEL SESSION command.
transfer rate is less than (transfer rate) User Response: Use the QUERY SESSION command
and more than (elapsed time since first data to ensure that the session you wish to cancel is
transfer) minutes have elapsed since first connected. Reissue the command using the appropriate
data transfer. session number to cancel the client session.
Explanation: The server is canceling client session
number session number. Depending on the state of the ANR0492I All drives in use. Session session number
session, it may take a while for the session to be for node node name (client platform) being
canceled. The server ends a client session because it has preempted by higher priority operation.
been active for more minutes than specified in the
THROUGHPUTTIMETHRESHOLD parameter in the Explanation: When a high priority operation
server options file and the data transfer rate is less than attempted to find an available drive, all the drives were
the amount specified with the being used. To free up a drive for this operation, the
THROUGHPUTDATATHRESHOLD parameter in the client session identified is being cancelled by the
server options file. The client is transferring data to the system.
server at an abnormally slow rate and may have System Action: The lower priority client session is
become a bottleneck for handling data from other cancelled to free up a mount point (drive).
clients. If the client has caused log records to be
written, it is possible that this client will prevent log User Response: When a drive again becomes
space reclamation. available, restart the session that was cancelled. This
session was most likely a backup/archive session and
System Action: The session is canceled and server you may just want to let it restart automatically during
operation continues. its next scheduled backup window. If this message
User Response: If a low data transfer rate is not a appears frequently, you may want to increase the
problem, the THROUGHPUTTIMETHRESHOLD or number of drives available. See the MOUNTLIMIT
THROUGHPUTDATATHRESHOLD parameters in the parameter on the UPDATE DEVCLASS command.
server options file can be set to zero - this will disable
the throughput check. The change can be made without ANR0493I Restore session session number canceled.
taking down the server and restarting it by using the
SETOPT THROUGHPUTTIMETHRESHOLD or the Explanation: The specified session was canceled with
SETOPT THROUGHPUTDATATHRESHOLD the CANCEL RESTORE command.
commands. If a low data transfer rate is not expected, System Action: The restore session is canceled and
external causes should be investigated. This would server operation continues.
include network problems and problems in accessing
data on the client node. The client program may User Response: None.
automatically reconnect to the server, so this message
may appear on subsequent sessions until the data ANR0494I Volume volume name in use. Session
transfer problem is resolved. The default server session number for node node name (client
operation is not to perform a throughput check. platform) being preempted by higher
priority operation.
ANR0490I Canceling session session number for Explanation: When a high priority operation
node node name (client platform) . attempted to acquire a specific volume, it was being
Explanation: The server is canceling client session used. To free the volume for this operation, the client
number session number. This message is displayed in session identified is being cancelled by the system.
response to the CANCEL SESSION command. System Action: The lower priority client session is
Depending on the state of the session, it may take a cancelled to free up the volume.
while for the session to be canceled.
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
ANR0521W Transaction failed for session session
most likely a backup/archive session and you may just
number for node node name (client
want to let it restart automatically during its next
platform) - object excluded by size in
scheduled backup window.
storage pool pool name and all successor
pools.
Explanation: The server ends a database update
transaction for the specified session because the size of
platform) - invalid password submitted.
a file sent from the client node is larger than that
Explanation: The server ends a password update allowed in the storage pool specified in the client’s
transaction because the user has not correctly specified management class copy group. No successor storage
the current password. pools to the one specified on the copy group can accept
the large file.
System Action: The specified session is ended and
User Response: Update your password by correctly server operation continues.
specifying the current password. If the current
password has been misplaced, the administrator can User Response: If the client is not using compression
reassign a password for the client by using the to send files to the host, turn compression on for the
UPDATE NODE or UPDATE ADMIN command. 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
ANR0501W Transaction failed for session session hierarchy can be increased to accommodate the file. An
number for node node name (client authorized administrator can increase the MAXSIZE
platform) - invalid policy binding parameter by issuing the UPDATE STGPOOL
specified. command.
transaction for the specified session because an invalid ANR0522W Transaction failed for session session
management class has been specified for a file or number for node node name (client
directory object. platform) - no space available in storage
System Action: The specified session is ended and pool pool name and all successor pools.
server operation continues. Explanation: The server ends a database update
User Response: Correct the programming error in the transaction for the specified session because the storage
client program if it has been written by your pool specified in the client’s management class copy
installation using WDSF verbs. Otherwise, contact your group does not contain enough free space to hold the
service representative. files sent from the client. Successor storage pools to the
one specified on the copy group do not contain enough
free space.
number for node node name (client System Action: The specified session is ended and
platform) - storage pool pool name is not server operation continues.
defined. User Response: An authorized administrator can issue
Explanation: The server rolls back a database update the DEFINE VOLUME command to add storage to one
transaction for the specified session because the or more storage pools in the storage hierarchy. This
destination specified for a management class copy action may also involve creating storage space by using
group specifies the named storage pool, but that an operating system specific utility.
storage pool does not exist.
System Action: Server operation continues. ANR0523W Transaction failed for session session
User Response: An administrator with policy platform) - error on output storage
authority over the client policy domain must correct device.
management class definitions so that copy group
destinations refer to defined storage pools, or the Explanation: The server ends a database update
specified storage pool must be created by an authorized transaction for the specified client because an I/O error
administrator. has been encountered by the server in writing to a
device.
server operation continues.
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
platform) - sufficient database space is
problem is corrected, the client should retry the
not available.
operation.
transaction for the specified session because sufficient
database space is not available on the server.
platform) - data transfer interrupted. System Action: The server ends the specified session
and server operation continues.
Explanation: The database transaction associated with
session session number was aborted because data User Response: An authorized administrator can issue
transfer to or from data storage was interrupted by an the DEFINE DBVOLUME command to add volumes
external event. for use by the database, and can issue the EXTEND DB
command to extend the size of the database so that the
System Action: The session is canceled and server
new volumes are used.
operation continues.
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
platform) - thread resource not available.
problem can be resolved.
transaction for the specified session because sufficient
memory is not available for starting additional
processes on the server.
platform) - storage media inaccessible.
System Action: The server ends the specified session
Explanation: The server ends a transaction for the
specified session because storage volumes are not
available in the storage pools in which the client’s files User Response: Allocate additional storage to the
are to be stored. server. For details, issue HELP MEMORY to display the
User Response: An authorized administrator can issue
the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy. The
platform) - insufficient memory.
VARY ONLINE command can be used to vary offline
storage volumes online in the storage hierarchy to Explanation: The server ends a database update
make them available to client nodes for file storage. transaction for the specified session because sufficient
memory is not available on the server.
ANR0526W Transaction failed for session session System Action: The server ends the specified session
number for node node name (client and server operation continues.
platform) - sufficient recovery log space
is not available.
Explanation: The server ends a database update information online or see “Appendix A. Allocating
transaction for the specified session because sufficient Additional Server Memory”.
log space is not available on the server.
System Action: The server ends the specified session ANR0530W Transaction failed for session session
and server operation continues. number for node node name (client
platform) - internal server error detected.
the DEFINE LOGVOLUME command to add volumes Explanation: The server ends a database update
for use by the log, and can issue the EXTEND LOG transaction for the specified session because an internal
command to extend the size of the log so that the new logic error is detected.
volumes are used.
User Response: Examine the server messages 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. If the error cannot
be isolated and resolved, contact your service
platform) - size estimate exceeded and
representative.
server is unable to obtain additional
space in storage pool pool name.
transaction for the specified session because the size
platform) - invalid file space identifier
estimate provided by the client is too small. The server
specified by client.
has attempted to obtain additional space in the
Explanation: The server ends a database update indicated storage pool, but was unable to do so.
transaction for the specified session because the file
space identified by the client for the transaction does
server operation continues. If pool name is a random
not exist.
access storage pool with caching enabled, it is also
System Action: This action usually occurs when a possible that additional space can be made available in
client is operating on a file space that is currently being this storage pool by eliminating cached files. When the
deleted as a result of an administrative command or server allocates space based on the size estimate
client action. The server ends the specified session and provided by the client, it frees space occupied by
server operation continues. cached files if this space is needed to obtain the
estimated space. However, if the server later determines
User Response: Use the QUERY PROCESS command that the file size estimate was too low, it attempts to
to monitor and wait for any file space deletion obtain additional space that is not utilized, but does not
processes to complete, or cancel the process if you do delete cached files to do so. If the client sending the
not want to delete the file space. Try the client action data has the option COMPRESSALWAYS YES set, it is
again after this action has been taken. possible that a file grew during the compression
operation and when the client sent it to the server it
ANR0532W DiagnosticID: Transaction transaction ID exceeded the space available in storage pool pool name.
was aborted for session session number User Response: This message may indicate that there
for node node name (client platform). is no additional space in pool name. The following are
Explanation: An error has been detected during a possible circumventions:
transaction commit for the specified session. This An authorized administrator can issue the DEFINE
message should be preceded by other messages that VOLUME command to add storage to this pool.
give additional information about the failed transaction.
If the suspected cause of the failure is that pool name is
System Action: The activity that generated this error a DISK storage pool and that space in use by cached
fails. files was not freed, turn off caching for the storage pool
User Response: Check for additional messages and and issue the MOVE DATA command for the volumes
eliminate the condition that caused the failed in pool pool name.
transaction. If the error cannot be isolated and resolved, If the suspected cause of the failure is that a file grew
contact your service representative. in size during compression on the client, another
possible circumvention is to set the
ANR0533W Transaction failed for session session COMPRESSALWAYS option in the client options file to
number - compression method used by NO and retry the operation. This may allow the client
client not supported. Please obtain the to accurately report the file size and possibly avoid the
latest level of the client code. out of space condition in the storage pool.
Explanation: The server ends the transaction for the

specified session because the compression method that ANR0535W Transaction failed for session session
is used by the client is no longer supported by the number for node node name (client
server. platform) - insufficient mount points
available to satisfy the request.
and server operation continues. 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 System Action: The operation is ended and server
client that supports the newer compression method. If operation continues.
the client is a WDSF client, upgrade to a non-WDSF User Response: If necessary, make more mount points
client in order to use the compression performed by the available.
client.

ANR0536W Transaction failed for session session ANR0542W Retrieve or restore failed for session
number for node node name (client session number for node node name (client
platform) - downlevel client does not platform) - storage media inaccessible.
support format of stored files.
Explanation: The server ends a client retrieval or
Explanation: A client attempts to perform an restore operation for the specified session because a
operation involving files that are stored in a format that needed storage pool volume has been varied offline.
is not supported by that client level.
System Action: The operation is ended and server and server operation continues.
User Response: Use the VARY ONLINE command to
User Response: Upgrade the client to a later level. vary offline storage volumes online in the storage
hierarchy, and make them available to client nodes for
file storage.
ANR0537E Transaction failed for session session
platform) - filespace name cannot be ANR0543W Retrieve or restore failed for session
renamed from or to a unicode name. session number for node node name (client
platform) - data transfer interrupted.
transaction for the specified session because a file space Explanation: The database transaction associated with
was attempted to be renamed to or from unicode. session session number was aborted because data
transfer to or from data storage was interrupted by an
System Action: The server ends the specified
external event.
transaction and server operation continues.
System Action: The session is canceled and server
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. User Response: Examine the messages issued prior to
interrupted. Attempt the client operation again, if the
ANR0540W Retrieve or restore failed for session
problem can be resolved.
platform) - data integrity error detected.
Explanation: The server ends a file retrieval operation
for the specified session because an internal database
platform) - thread resource not available.
integrity error has been encountered on the server.
Explanation: The server ends a file retrieval or restore
operation for the specified session because sufficient
and continues operation.
memory is not available for starting additional
User Response: Contact your service representative. processes on the server.
ANR0541W Retrieve or restore failed for session and server operation continues.
platform) - error on input storage device.
Explanation: The server ends a client retrieval or information online or see “Appendix A. Allocating
restore operation for the specified session because an Additional Server Memory”.
I/O error has been encountered by the server in
reading from a device.
System Action: The server ends the specified session session number for node node name (client
and server operation continues. platform) - insufficient memory.
User Response: Query the activity log to find Explanation: The server ends a file retrieval or restore
messages preceding this one that specify the device that operation for the specified session because sufficient
is failing. Storage pool volumes can be varied offline memory is not available on the server.
(by using 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 User Response: Allocate additional storage to the
again. server. For details, issue HELP MEMORY to display the

ANR0546W Retrieve or restore failed for session platform) - no existing restore session
session number for node node name (client found.
platform) - internal server error detected.
Explanation: A client attempted to start an additional
Explanation: The server ends a file retrieval or restore no query restore session to increase restore throughput,
operation for the specified session because an internal but the original restore session was not found.
logic error is detected in the server program.
System Action: The operation is ended and server
System Action: The server ends the specified session operation continues.
User Response: Check the status of the original
User Response: Examine the server messages issued restore. It may have already completed or been
prior to this message to determine the source of the cancelled. The QUERY SESSION command and the
error. Use the QUERY ACTLOG command to view the QUERY RESTORE commands can provide information
activity log and search for messages. If the error cannot about existing sessions and restore sessions which are
be isolated and resolved, contact your service restartable.
representative.
ANR0550E The client operation failed for session
ANR0547E Invalid data was encountered in the session number for node node name (client
command processor output stream: platform) - see previous error messages.
output formatting terminated for the last
Explanation: The indicated operation has failed. This
command entered.
message is always preceded by one or more other error
Explanation: The server console session encounters an messages which provide more detail about why the
error in formatting output from a command. command failed.
System Action: The command output is discarded System Action: The operation is ended and server
and server operation continues. operation continues.
User Response: Use the server QUERY command to User Response: Examine the previous error messages
determine if the command you entered had the desired to determine the source of the error. Use the QUERY
affect in the server. Use the QUERY ACTLOG ACTLOG command to view the activity log and search
command to see if a server error condition (like out of for messages if needed. Correct the problem and try the
memory) occurred prior to the command. Resolve the command again.
error if it is found. Contact your service representative
if you cannot resolve the error, or if an error is not
ANR0551E The client operation failed for session
found.
platform) - lock conflict.
Explanation: An operation that requires the server to
lock a system resource has been initiated. The operation
platform) processing file space filespace
cannot be executed because the resource is already in
filespace id for file file name stored as
use by another command or process.
storage repository - data integrity error
detected. System Action: The server does not process the
command.
Explanation: The server ends a file retrieval operation
for the specified session because an internal database User Response: Try the command again at a later
integrity error has been encountered on the server. time.
and continues operation. ANR0552E Client operation failed for session
User Response: Re-try the restore or retrieve operation
platform) - destination storage pool
and if the file is also backed up in a copy storage pool,
storage pool was skipped.
the operation will attempt to read the file from the
alternate location. 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.

System Action: The operation fails.
ANR0556E command name: DATES=RELATIVE
User Response: Ensure that the destination storage parameter value cannot be specified
pool is available, has an adequate MAXSIZE setting, when merging imported files using the
and has adequate space. The MAXSIZE setting may be MERGE=YES parameter value.
changed using the UPDATE STGPOOL command.
Explanation: When importing files and merging them
Space may be added to the storage pool by checking in
into existing file spaces, the DATES=RELATIVE
scratch volumes or defining new volumes in the
parameter value cannnot be specified.
storage pool. If volumes in the destination storage pool
are offline, use the VARY ONLINE command to vary System Action: The command fails and server
them online and make them available for use. Correct operation continues.
the problem and try the command again.
User Response: Reissue the command and omit the
DATES=RELATIVE parameter. For information on valid
ANR0553E Client operation failed for session values for the parameter for the command, refer to the
session number - Administrator :cit.ADSM Administrator’s Reference:ecit. for your
administrator name does not have particular platform.
adequate authority over node node name.
Explanation: The specified administrator does not ANR0566W Retrieve or restore failed for session
have the proper authority necessary to perform this session number for node node name (client
operation on the specified node. platform) - file was deleted from data
storage during retrieval.
System Action: The server does not perform the
query. Explanation: The server ends a file retrieval operation
for the specified session because the file has been
User Response: Issue the command from a properly
deleted from data storage by another process before
authorized administrator ID, or contact the system
retrieval is complete.
administrator to have additional authority granted to
the current administrator ID. System Action: The server ends the specified session
ANR0554E command name: The parameter name User Response: Contact your administrator to find
parameter is only valid if the out if DELETE FILESPACE, DELETE VOLUME, or
TOSERVER parameter is specified. inventory expiration processes are running; these
processes can delete data storage files during retrieval.
Explanation: The command failed because the
Reissue the restore or retrieve operation and specify a
TOSERVER parameter was not specified.
different file version.
System Action: The command fails and server
ANR0567W Retrieve or restored failed for session
User Response: Reissue the command and specify the session number for node node name (client
TOSERVER parameter. For information on valid values platform) - insufficient mount points
for the command parameter,refer to the :cit.ADSM available to satisfy the request.
Administrator’s Reference:ecit. for your particular
Explanation: The server was unable to allocate
platform.
sufficient mount points to process the retrieve or
restore operation.
ANR0555E command name: The parameter name
parameter cannot be specified when the
TOSERVER parameter is specified.
User Response: If necessary, make more mount points
Explanation: The command failed because the
available.
TOSERVER parameter was not specified.
ANR0568W Session session number for admin admin
User Response: Reissue the command and omit the connection with client severed.
TOSERVER parameter. For information on valid values
Explanation: The specified admin session is ended
for the parameter for the command parameter, refer to
because the communications link has been closed by a
the :cit.ADSM Administrator’s Reference:ecit. for your
network error or by the client program.
particular platform.
User Response: If a user breaks out of a client

program, this message will be displayed on the server
ANR0572E Export command: Invalid value for
as the connection is suddenly closed by the client. A
DAYOFWEEK parameter detected while
network failure can also cause this message to be
exporting administrative schedule
displayed. If a large number of these messages occur
schedule name - default or existing value
simultaneously, check the network for failure and
is used during import.
correct any problems.
Explanation: During processing of command export
command, an invalid value is encountered for the
ANR0569I Object not processed for node name:
DAYOFWEEK parameter for administrative schedule
type=type, file space=filespace name,
schedule name.
object=object name.
System Action: Export processing continues, but the
Explanation: An error occurred. The object for node
exported data contains an unknown DAYOFWEEK
name, identified by type, file space and object name was
value for this schedule. If this data is imported, the
not processed.
server uses the default or existing DAYOFWEEK value.
System Action: Server action is defined by the error
User Response: Update the DAYOFWEEK value for
that occurred.
this schedule and restart the export command.
User Response: Issue QUERY ACTLOG to determine Alternatively, use the export data with the unknown
the source of the error. value, and check and update the DAYOFWEEK value
after import processing has been performed.

DURUNITS parameter detected while ANR0573I Export/import command: Processing
exporting administrative schedule administrative schedule schedule name.
schedule name - default or existing value
Explanation: The background export or import
is used during import.
process to service the command export/import command
Explanation: During processing of command export is currently processing the schedule definition
command, an invalid value is encountered for the information for administrative schedule schedule name.
DURUNITS parameter for administrative schedule
System Action: Export or import processing for the
schedule name.
command continues.
exported data contains an unknown DURUNITS value
for this schedule. If this data is imported, the server
uses the default or existing DURUNITS value. ANR0574E Import command: Invalid value for
DURUNITS or PERUNITS parameter in
User Response: Update the DURUNITS value for this
exported data for administrative
schedule and restart the export command. Alternatively,
schedule schedule name.
the export data with the unknown value can be used,
and the DURUNITS value can be checked and updated Explanation: During preview processing of command
after import processing has been performed. import command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for administrative
PERUNITS parameter detected while System Action: Processing of the command continues.
exporting administrative schedule If a later command is issued that causes the data to be
schedule name - default or existing value imported, the default or existing values are used for
is used during import. DURATION, DURUNITS, PERIOD, and PERUNITS.
Explanation: During processing of command export User Response: If the data is imported with a later
command, an invalid value is encountered for the command, verify that the correct values for
PERUNITS parameter for administrative schedule DURATION, DURUNITS, PERIOD, and PERUNITS are
schedule name. used for this schedule.
exported data will contain an unknown PERUNITS ANR0575E Import command: Invalid value for
value for this schedule. If this data is imported, the DAYOFWEEK parameter in exported
server uses the default or existing PERUNITS value. data for administrative schedule schedule
name.
User Response: Update the PERUNITS value for this
schedule and restart the export command. Alternatively, Explanation: During preview processing of command
use the export data with the unknown value, and check import command, an invalid value is encountered for the
and update the PERUNITS value after import DAYOFWEEK parameter for administrative schedule
processing has been performed. schedule name.

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

exported data contains an unknown value for this class management class name, in policy domain domain
management class. If this data is imported, the default name, policy set policy set name.
or existing MIGREQUIRESBKUP value is used.
User Response: Update the MIGREQUIRESBKUP by using the existing SPACEMGTECHNIQUE value for
value for this copy group and restart the export. this management class.
User Response: Verify that the correct
value, and check and update the MIGREQUIRESBKUP
SPACEMGTECHNIQUE value has been used for this
value after import processing has been performed.
management class. Update this value, if necessary.

SPACEMGTECHNIQUE parameter in
MIGREQUIRESBKUP parameter in
exported data for management class
exported data for management class
management class name in domain domain
name, set policy set name.
name, set policy set name.
Explanation: During preview processing of command
import command, an invalid value is encountered for the
SPACEMGTECHNIQUE parameter for management
class management class name, in policy domain domain
management class name, in policy domain domain name,
name, policy set policy set name.
System Action: Processing of the command continues.
If a later command is issued that causes the data to be
If a later command causes the data to be imported, the
imported, the default or existing
default or existing MIGREQUIRESBKUP value is used.
SPACEMGTECHNIQUE value is used.
User Response: None. If the data is imported with a
later command, verify that the correct
later command, verify that the correct
MIGREQUIRESBKUP value is used for this
SPACEMGTECHNIQUE value is used for this
management class.
management class.

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

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

System Action: Processing of the command continues, valid FILELIST parameter. For information on valid
by using the existing MIGREQUIRESBKUP value for values for the FILELIST parameter for the command,
this management class. refer to the Administrator’s Reference for your particular
platform.
MIGREQUIRESBKUP parameter has been used for this
management class. Update this value, if necessary. ANR0592E Export/import command: Invalid value for
TOC parameter - parameter value.
ANR0588E Import command: Server is down-level Explanation: The value (parameter value) specified for
compared to export data version version the TOC parameter in command export/import command
number. is not a valid value for this parameter.
Explanation: An attempt is made to import data to a System Action: The command fails and server
down-level server. The server on which the import is operation continues.
performed must be at the same or later level than the
User Response: Reissue the command and specify a
server from which the data was exported.
valid TOC parameter. For information on valid values
System Action: The import process ends and server for the TOC parameter for the command, refer to the
operation continues. Administrator’s Reference for your particular platform.
User Response: Import to a server that is at the same
or later level than the server from which the export ANR0593E Export/import command: Invalid value for
was performed. NOSPAN parameter - parameter value.
Explanation: The value (parameter value) specified for
ANR0589E Import command: Preview processing the NOSPAN parameter in command export/import
terminated abnormally - server is command is not a valid value for this parameter.
down-level.
Explanation: Processing for the command import operation continues.
command in preview mode ends when it is determined
that the server is down-level compared to the export
valid NOSPAN parameter. For information on valid
data.
values for the NOSPAN parameter for the command,
System Action: Import processing ends and server refer to the Administrator’s Reference for your particular
operation continues. platform.
or later level than the server from which the export ANR0594E device class: NOSPAN parameter can only
was performed. be used with a 3590 device class.
Explanation: The device class specified must be a 3590
ANR0590E Import command: Processing terminated device class when NOSPAN is set to True.
abnormally - server is down-level.
Explanation: Processing for the command import operation continues.
command ends when it is determined that the server is
down-level compared to the export data.
valid NOSPAN/Device Class parameter. For
System Action: Import processing ends and server information on valid values for the NOSPAN parameter
operation continues. for the command, refer to the Administrator’s Reference
for your particular platform.
or later level than the server from which the export
was performed. ANR0596W Space-managed object object name for
client node node name, filespace filespace
name already exists on the server - it will
ANR0591E Export/import command: Invalid value for
be skipped.
FILELIST parameter - parameter value.
Explanation: While attempting to import a
spaced-managed object, the server discovers that the
the FILELIST parameter in command export/import
object already exists. The space-managed object is
command is not a valid value for this parameter.
skipped.

ANR0597W IMPORT: Space management attributes ANR0600I Export command: No matching policy
in management class management class domains found for exporting.
name for domain domain name is not
Explanation: The background export process does not
defined - default management class will
find any policy domains that match the specification
be used.
entered in the export command.
Explanation: During import processing, the server
System Action: The export process continues and no
finds that the space management attributes for a
policy domains are exported from the server.
space-managed file being imported does not exist in
the active policy set for the domain to which the node User Response: None.
is assigned.
System Action: The default management class for the ANR0601I Export command: No policy sets found in
node’s policy domain is bound to the space-managed policy domain domain name for
file and import processing continues. exporting.
User Response: If you want to define the missing Explanation: The background export process does not
management class, an authorized administrator may find any policy sets defined in domains matching
cancel the import operation, define the missing space domain name.
management attributes or management class for the
domain, and process the import operation again. System Action: The export process continues and no
policy sets are exported from the domain.
ANR0598W IMPORT: Space management attributes User Response: None.

not found for default management class
in domain domain name - space managed ANR0602I Export command: No management classes
files bound to management class were found in policy domain domain
management class name in this domain name for exporting.
cannot be imported.
Explanation: During import processing, the server find any management classes defined in policy
finds that a management class bound to a domains matching domain name.
space-managed file being imported does not exist in
the active policy set for the domain to which the node System Action: The export process continues and no
is assigned. When trying to rebind the space-managed management classes are exported from the domain.
file to the default management class for the domain, User Response: None.
the server finds that the space-managed attributes are
not defined for the default management class.
ANR0603I Export command: No copy groups were
System Action: The file is not imported; import found in policy domain domain name for
processing continues. exporting.
User Response: If you want to define the missing Explanation: The background export process does not
copy group, an authorized administrator may cancel find any copy groups defined in policy domains
the import operation, define the missing space matching domain name.
management attributes or management class for the
domain, and process the import operation again. System Action: The export process continues and no
copy groups are exported from the domain.
ANR0599E Export/import command: Invalid volume User Response: None.

name volume name specified for device
class device class name. ANR0604I Export command: No schedules were
Explanation: One of the volume names specified in found in policy domain domain name for
the VOLUMENAMES parameter for an import or exporting.
export command is not a valid volume name for the Explanation: The background export process does not
device class specified in the DEVCLASS parameter. find any schedules defined for policy domains
System Action: The export or import command fails. matching domain name.
User Response: Specify volume names in the System Action: The export process continues and no
VOLUMENAMES parameter that are valid for the schedules are exported for the domain.
device class specified in the DEVCLASS parameter. User Response: None.

ANR0605I Export command: No schedule ANR0610I Command started by administrator name as

associations were found in policy process process ID.
domain domain name for exporting.
Explanation: A background process has started to
Explanation: The background export process does not service the command command entered by administrator
find any schedule node associations defined for policy administrator name. The background process is defined
domains matching domain name. as process process ID.
System Action: The export process continues and no System Action: Server operation continues.
schedule associations are exported for the domain.
User Response: To query the progress of the
User Response: None. background process, use the QUERY PROCESS
command. To cancel the background process, use the
CANCEL PROCESS command. Use the process ID
ANR0606I Export command: No node definitions
number to specify this specific process.
were found for exporting.
ANR0611I Command started by administrator name as
find any node definitions to export as specified in the
process process ID has ended.
command export command.
Explanation: The background process to service the
System Action: The export process continues.
command command by administrator administrator name
User Response: None. has completed processing.
System Action: The specified process ends, and server
ANR0607I Export command: No administrator operation continues.
definitions were found for exporting.
find any administrator definitions to export as specified
ANR0612I Import command: Reading EXPORT
in the command export command.
SERVER data from server server name
System Action: The export process continues. exported export date export time.
User Response: None. Explanation: The background import process to

service the command import command is importing
information exported from server server name with the
ANR0608I Export command: No file spaces were EXPORT SERVER command on export date at export
found for exporting. time.
Explanation: The background export process does not System Action: Import processing continues.
find any file space definitions to export as specified in
the command export command. User Response: None.
System Action: The export process continues.

User Response: None. POLICY data from server server name
exported export date export time.
ANR0609I Command started as process process ID. Explanation: The background import process to
Explanation: A background process has been started service the command import command is importing
to service the command command. The background information exported from server server name with the
process is defined as process process ID. EXPORT POLICY command on export date at export
time.
System Action: Import processing continues.
background process, use the QUERY PROCESS User Response: None.
command. To cancel the background process, use the
CANCEL PROCESS command. Use the process ID ANR0614I Import command: Reading EXPORT
number to specify this specific process. ADMIN 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 ADMIN command on export date at export number of bytes copied, are displayed on the server
time. console following this message.
System Action: Import processing continues. User Response: None.
ANR0619I Command: Processing canceled before
completion.
NODE data from server server name Explanation: The background process to service the
exported export date export time. command command has been canceled with the
CANCEL PROCESS command.
Explanation: The background import process to
service the command import command is importing System Action: Processing for the command command
information exported from server server name with the ends. Statistics on the number and type of objects
EXPORT NODE command on export date at export time. moved, together with the total number of bytes copied,
are displayed on the server console following this
System Action: Import processing continues.
message.
ANR0616I Export/import command: Preview

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

completed with status status.
policy sets.
has completed with status status. If the status is
copies number policy set definitions from the server
INCOMPLETE, some files have been skipped due to
database to export media or from export media into the
errors reading or writing the file.
server database. Data is not actually moved if
System Action: Export or import processing for the Preview=Yes is specified in the command export/import
command completes. Statistics on the number and type command.
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. User Response: None.
management classes.
ANR0618I Export/import command: Preview
processing canceled before completion. Explanation: The background export or import
copies number management class definitions from the
in preview (Preview=Yes) mode has been canceled with
into the server database. Data is not moved if
the CANCEL PROCESS command.
Preview=Yes is specified in the command export/import
System Action: Export or import processing for the command.
command ends. Statistics on the projected number and
type of objects moved, together with the projected total

command completes. Server operation continues. User Response: None.
ANR0627I Export/import command: Copied filespace
number file space archive number archive
files, fsIdfilespace id, backup number
copy groups.
backup files, and spacemg number space
Explanation: The background export or import managed files.
copies number copy group definitions from either the
copies filespace number client file space definitions,
archive number archive file copies, backup number backup
file copies, and spacemg number space-managed files
command.
from either the server database to export media or from
System Action: Export or import processing for the import media into the server database. Data is not
command completes. Server operation continues. actually moved if Preview=Yes is specified in the
command export/import command.
schedules. User Response: None.

process to service the command export/import command ANR0629I Export/import command: Copied number
copies number schedule definitions from either the bytes of data.
copies number bytes of data from the server database
command.
and data storage to the export media or from the
System Action: Export or import processing for the export media to the server database and data storage.
command completes. Server operation continues. Data is not moved if Preview=Yes is specified in the
command export/import command. This figure can be
User Response: None. used during export preview processing to estimate the
number of removable media volumes needed to hold
ANR0625I Export/import command: Copied number the exported information from the server.
administrators. System Action: Export or import processing for the
Explanation: The background export or import command completes. Server operation continues.
process to service the command export/import command User Response: None.
copies number administrator definitions from either the
into the server database. Data is not moved if ANR0630I Export/import command: Copied number
Preview=Yes is specified in the command export/import kilobytes of data.
command.
System Action: Export or import processing for the process to service the command export/import command
command completes. Server operation continues. copies number kilobytes of data from the server
database and data storage to the export media or from
User Response: None. the export media to the server database and data
storage. This figure can be used during export preview
ANR0626I Export/import command: Copied number processing to estimate the number of removable media
node definitions. volumes needed to hold the exported information from
the server.
process to service the command export/import command System Action: Export or import processing for the
copies number client node definitions from the server command completes. Server operation continues.
database to export media or from export media into the User Response: None.
server database. Data is not moved if Preview=Yes is
specified in the command export/import command.

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

definition information for management class class name
belonging to policy set set name in policy domain
administrator administrator name.
domain name.
command continues.
is currently processing the administrator definition
information for administrator administrator name. User Response: None.
command continues. ANR0643I Export/import command: Processing
archive copy group in domain domain
name, set set name, management class
class name.
Explanation: The background export process to
domain domain name.
service the command export/import command is currently
Explanation: The background export or import processing the archive copy group definition
process to service the command export/import command information for management class class name belonging
is currently processing the policy domain definition to policy set set name in policy domain domain name.
information for domain domain name.
System Action: Export processing for the command
System Action: Export or import processing for the continues.
command continues.
ANR0644I Export command: Processing copy group
ANR0640I Export/import command: Processing policy of unknown type in domain domain
set set name in policy domain domain name, set set name, management class
name. class name.
Explanation: The background export or import Explanation: The background export or import
process to service the command export/import command process to service the command export command is
is currently processing the policy set definition currently processing copy group definition information
information for policy set set name belonging to policy for management class class name belonging to policy set
domain domain name. set name in policy domain domain name. The type of
copy group being processed is unknown.
command continues. System Action: Export or import processing for the
command continues. The import or export process
assumes that the copy group is a backup copy group.
User Response: After policy definitions are imported,
use the QUERY MGMTCLASS and QUERY
management class class name in domain
COPYGROUP commands to query the server
domain name, set set name.
definitions for management class class name to ensure
Explanation: The background export or import that the copy groups defined have the desired
process to service the command export/import command attributes and types. Alternatively, the copy group can
is currently processing the management class definition be deleted and defined with the correct type, and then
information for management class class name belonging the export command can be issued again.
to policy set set name in policy domain domain name.
System Action: Export or import processing for the ANR0645I Export/import command: Processing
command continues. schedule schedule name in domain domain
name.
ANR0642I Export/import command: Processing is currently processing the schedule definition
backup copy group in domain domain information for schedule schedule name belonging to
name, set set name, management class policy domain domain name.
class name.
Explanation: The background export or import command continues.
is currently processing the backup copy group User Response: None.

ANR0646I Export/import command: message ANR0650W IMPORT: Archive copygroup copy group
name in management class management
class name for domain domain name is not
defined, default management class will
has received the message message from the server.
be used.
command continues, but errors may have been
finds that a management class or copy group bound to
encountered.
an archive file being imported does not exist in the
User Response: Examine the documentation for the active policy set for the domain to which the node is
message message and resolve the problem reported. assigned.
System Action: The default management class for the
ANR0647I Cancel in progress node’s policy domain is bound to the archive file and
import processing continues.
Explanation: The export or import operation has been
canceled and will end when resources have been freed User Response: If you want to define the missing
for the background process. This message may be management class, an authorized administrator may
displayed in response to a QUERY PROCESS command cancel the import operation, define the missing
for an export or import operation. management class or copy group for the domain, and
process the import operation again.
User Response: None. ANR0651W IMPORT: Backup copygroup copy group
ANR0648I Have copied the following: class name for domain domain name is not
defined, default management class will
Explanation: The export or import operation has be used.
copied the number and types of objects displayed. This
message may be displayed in response to a QUERY Explanation: During import processing, the server
PROCESS command for an export or import operation. finds that a management class or copy group bound to
a backup file being imported does not exist in the
System Action: Server operation continues. active policy set for the domain to which the node is
User Response: None. assigned.
System Action: The default management class for the
ANR0649I Import command: Domain domain name node’s policy domain is bound to the backup file copy
does not exist - the system will attempt and import processing continues.
to import node node name to domain User Response: If you want to define the missing
STANDARD. management class, an authorized administrator may
Explanation: The background import process to cancel the import operation, define the missing
service the command import command is currently management class or copy group for the domain, and
processing client node node name. This node was process the import operation again.
assigned to domain domain name at the time of export.
However, domain domain name does not exist on the ANR0652W IMPORT: Archive copygroup not found
server to which the import is being performed. for default management class in domain
System Action: Import processing continues, but node domain name - archive files bound to
node name will be assigned to domain STANDARD management class management class name
during import unless one of the following conditions in this domain cannot be imported.
exist: Explanation: During import processing, the server
v Preview=Yes finds that a management class or copy group bound to
v Node node name is already registered and an archive file being imported does not exist in the
Replacedefs=No active policy set for the domain to which the node is
v Domain STANDARD does not exist assigned. When trying to rebind the archive file to the
User Response: If Preview=Yes, consider defining default management class for the domain, the server
domain domain name before nodes are actually finds that an archive copy group is not defined for the
imported. Otherwise, domain domain name can be default management class.
created after the node is imported and the UPDATE System Action: The file is not imported; import
NODE command can be used to assign the node to processing continues.
domain domain name.
User Response: If you want to define the missing
copy group, an authorized administrator may cancel

the import operation, define the missing management User Response: Check previous messages for the
class or copy group for the domain, and process the names of the files that were not exported or imported,
import operation again. and problem determination information.
ANR0653W IMPORT: Backup copygroup not found ANR0657W Export command: Invalid authorization
for default management class in domain rule type rule type encountered for file
domain name - backup files bound to space filespace name fsId filespace id in
management class management class name node node name - both backup and
in this domain cannot be imported. archive will be assumed during import.
Explanation: During import processing, the server Explanation: During import processing, the server
finds that a management class or copy group bound to encounters an invalid file space authorization rule type
a backup file being imported does not exist in the for the indicated file space and node.
active policy set for the domain to which the node is
assigned. When trying to rebind the backup file to the
default management class for the domain, the server User Response: After import processing is completed,
finds that a backup copy group is not defined for the ask the user of node node name to query the access rules
default management class. and ensure that they are specified as desired. The user
should correct any rules that grant access to objects that
System Action: The file is not imported; import
the user does not want others to access.
processing continues.
User Response: If you want to define the missing
ANR0658W Export command: The password for
copy group, an authorized administrator may cancel
administrator administrator name could
the import operation, define the missing management
not be obtained. The value ’password
class or copy group for the domain, and process the
value’ will be assumed: The system
import operation again.
administrator may wish to change this
password after importing administrator
ANR0655W Command: Retrieve or restore failed - file administrator name.
was deleted from data storage during
retrieval.
command, the export processor cannot obtain the
Explanation: The server ends a file retrieval operation password for administrator administrator name. The
for the specified command because the file has been value password value is assigned as the password for the
deleted from data storage by another process before administrator on the export media.
System Action: The server ends the command and
User Response: After the administrative definition has
been imported to another server, an authorized
User Response: Contact your administrator to find administrator should use the UPDATE ADMIN
out if DELETE FILESPACE, DELETE VOLUME, or command to set a password for the administrator
inventory expiration processes are running; these administrator name.
processes can delete data storage files during retrieval.
Reissue the command after these processes have been
ANR0659W Export command: The password for node
completed or canceled.
node name could not be obtained. The
value ’password value’ will be assumed:
ANR0656W Export/import command: Skipped archive The system administrator may wish to
number archive files, backup number change this password after importing
backup files, and spacemg number space node node name.
managed files.
Explanation: The background export or import command, the export processor cannot obtain the
process to service the command export/import command password for client node node name. The value password
skipped archive number archive file copies, backup value is assigned as the password for the client node on
number backup file copies, and spacemg number the export media.
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: After the client node definition has
specified in the command export/import command. been imported to another server, an authorized
administrator should use the UPDATE NODE
command to set a password for the node node name.

interrupted. Reissue the command command after the
ANR0660E Command: Insufficient memory available
problem is resolved.
in accessing data storage.
Explanation: The server encounters a memory
ANR0664E Export/import command: Media not
shortage in accessing data storage during command
accessible in accessing data storage.
command operation.
Explanation: The server ends a transaction for an
System Action: The command command operation
export or import operation because storage volumes are
ends and server operation continues.
not available in the storage pools in which the client
User Response: Allocate additional storage to the files are to be stored.
System Action: The server ends the export or import
operation and server operation continues.
ANR0661E Command: Internal error encountered in
accessing data storage.
Explanation: The server encounters an internal error storage volumes online in the storage hierarchy to
in accessing data storage while processing command make them available for file storage.
command operation.
System Action: The command command operation is ANR0665W Import command: Transaction failed -
ended and server operation continues. storage pool pool name is not defined.
User Response: Use the QUERY ACTLOG command Explanation: The server rolls back a database update
to examine messages prior to this error to determine transaction for an import operation because the
the cause of the data storage failure. If the failure can destination specified for a management class copy
be found and resolved, reissue the command command group specifies the named storage pool, but that
operation. If the failure cannot be found, contact your storage pool does not exist.
service representative for assistance in resolving the
System Action: The import operation is ended and
problem.
User Response: An administrator with policy
ANR0662E Command: Output error encountered in
authority over the client policy domain must correct
management class definitions so that copy group
Explanation: The command command operation ends destinations refer to defined storage pools, or the
because an error has been encountered by the server in specified storage pool must be created by an authorized
writing to a device. Possible reasons include: administrator.
v I/O error writing to a device
v No storage space. ANR0666W Import command: Transaction failed -
v Incompatible storage pool data format. object excluded by size in storage pool
pool name and all successor pools.
ends and server operation continues. Explanation: The server ends a database update
transaction for an import operation because the size of
User Response: Query the activity log to find an imported file is larger than that allowed in the
messages preceding this one to determine the cause of storage pool specified in the bound management class
the error. After the problem is corrected, the command copy group for the file. No successor storage pools to
can be retried. the one specified on the copy group can accept the
large file.
ANR0663E Command: Data transfer was interrupted System Action: The import operation is ended and
in accessing data storage. server operation continues.
Explanation: The database transaction associated with User Response: The maximum file size for one or
command command operation failed because data more of the storage pools in the storage hierarchy can
transfer to or from data storage was interrupted by an be increased to accommodate the file. An authorized
external event. administrator can increase the MAXSIZE parameter by
System Action: The command command operation is issuing the UPDATE STGPOOL command.
ended and server operation continues. Alternatively, the appropriate copygroup definition can
be updated so that a different destination storage pool
User Response: Examine the messages issued prior to 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 storage volumes online in the storage hierarchy to
because the storage pool specified in a management make them available for file storage.
class copy group does not contain enough free space to
hold the files being imported. Successor storage pools
ANR0671W Export/import command: Transaction failed
to the one specified on the copy group do not contain
- sufficient recovery log space is not
enough free space.
available.
System Action: The import operation is ended and
transaction for an export or import operation because
User Response: An authorized administrator can issue sufficient log space is not available on the server.
or more storage pools in the storage hierarchy.
the DEFINE LOGVOLUME command to add volumes
- error on output storage device.
for use by the log, and the EXTEND LOG command to
Explanation: The server ends an export or import extend the size of the log so that the new volumes are
operation for the specified session because an I/O error used.
has been encountered by the server in writing to a
device.
System Action: The server ends the export or import - sufficient database space is not
operation and server operation continues. available.
User Response: Query the activity log to find Explanation: The server ends a database update
messages preceding this one that specify the device that transaction for an export or import operation because
is failing. Storage pool volumes can be varied offline sufficient database space is not available on 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 be able to try the User Response: An authorized administrator can issue
operation again. the DEFINE DBVOLUME command to add volumes
for use by the database, and the EXTEND DB
command to extend the size of the log so that the new
volumes are used.
- data transfer interrupted.
ANR0673W Export/import command: Data storage
an export or import operation failed because data
retrieve or restore failed - data integrity
error detected.
external event.
Explanation: The server ends an export or import
System Action: The export or import operation is
operation because an internal database integrity error
ended and server operation continues.
has been encountered on the server.
operation and continues operation.
interrupted. Attempt the export/import operation again
after problem is resolved. User Response: Contact your service representative.
ANR0670W Export/import command: Transaction failed ANR0674W Export command: Retrieve failed - error
- storage media inaccessible. on input storage device.
Explanation: The server ends a transaction for an Explanation: The server ends an export operation for
export or import operation because storage volumes are the specified session because an I/O error has been
not available in the storage pools in which the client encountered by the server in reading from a device.
files are to be stored. The object for which the I/O was issued is reported in
a later message.

System Action: Export processing skips this file, and
ANR0679E EXPORT/IMPORT: Communications
Failure in Receiving ″verb type″ verb.
Explanation: The server export/import process
messages preceding this one that specify the device that
encounters a communications error in using the verb
is failing. Storage pool volumes can be varied offline
type verb to transfer information to or from the server.
may need to be shut down with the HALT command to System Action: The export or import process ends
correct the hardware problem. and server operation continues.
ANR0675E EXPORT/IMPORT: Error starting the
Export/Import Session.
ANR0681E EXPORT/IMPORT: Authentication
Explanation: The server export/import process is not Failure.
able to start the session to export information from the
server or import information into the server.
encounters an authentication error in transferring
System Action: The export or import process ends information to or from the server.
System Action: The export or import process ends
User Response: Allocate additional storage to the and server operation continues.
Failure in Sending ″verb type″ verb
ANR0676E EXPORT/IMPORT: Invalid
(command).
Communications Buffer State in SEND.
encounters a communications error in transferring
type verb to issue command command.
information to or from the server.
ANR0683E EXPORT/IMPORT: Receive Buffer

ANR0677E EXPORT/IMPORT: Invalid
overflow.
Communications Buffer State in
RECEIVE. Explanation: The server export/import process
encounters an overflow error in transferring
information to or from the server.
encounters a communications error in transferring
information to or from the server. System Action: The export or import process ends
and server operation continues. User Response: Contact your service representative.
failure: bad verb received (verb type).
Failure in Sending ″verb type″ verb. Explanation: The server encounters an invalid
communications verb during export or import
processing and is not able to continue processing.
type verb to transfer information to or from the server. System Action: The export or import process ends
and server operation continues. User Response: Contact your service representative.

ANR0685E EXPORT/IMPORT: Internal error: ANR0689W Import command: Client platform type
Invalid table output handle detected. (platform type) for imported node node
name conflicts with an existing node
with the same name - the node will not
encounters an internal error in transferring information
be imported.
to or from the server.
encounters an imported node definition that has the
same name as an existing node, but has a different
User Response: Contact your service representative. 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.
ANR0686E Export/import command: Transaction
failure - could not start database System Action: Import processing continues, and the
transaction. named node is skipped by import processing.
Explanation: During processing of command User Response: If you want to import the named
export/import command, a database transaction cannot be node, cancel the import process, rename the existing
started in the server database. node to a new name by using the RENAME NODE
command, and run the import again. After you have
System Action: Processing of the command imported the node, use the RENAME NODE command
terminates. to set the node names as you desire.
prior to this message to determine the source of the ANR0690E Export/import command: Transaction
error. Use the QUERY ACTLOG command to view the failure - server aborted the transaction
activity log and search for messages. If the error cannot (abort code).
representative. Explanation: During processing of command
export/import command, a database transaction cannot be
committed in the server database. The reason code abort
ANR0687E Export/import command: Transaction code is returned.
failure - could not commit database
transaction. System Action: Processing of the command ends.
Explanation: During processing of command User Response: Examine the server messages issued
export/import command, a database transaction cannot be prior to this message to determine the source of the
committed to the server database. error. Use the QUERY ACTLOG command to view the
System Action: Processing of the command ends. be isolated and resolved, contact your service
User Response: Examine the server messages issued representative.
error. Use the QUERY ACTLOG command to view the ANR0691E Export command: Error abort code writing
activity log and search for messages. If the error cannot export data.
representative. Explanation: During processing of command export
command, an input/output error occurs when writing
the exported information to the export media.
ANR0688E Export/import command: Transaction
failure - commit called when no System Action: Processing of the command ends.
transaction started.
Explanation: During processing of command prior to this message to determine the source of the
export/import command, a database transaction cannot be error. Use the QUERY ACTLOG command to view the
started in the server database. activity log and search for messages. If the error cannot
System Action: Processing of the command ends. representative.
prior to this message to determine the source of the ANR0692E Command: Out of space on sequential
error. Use the QUERY ACTLOG command to view the media, scratch media could not be
activity log and search for messages. If the error cannot mounted.
representative. 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
ANR0696E Export command: Output table error
media for storing data and SCRATCH=NO has been
encountered - 0 columns reported in the
specified on command command.
table.
System Action: Command command processing ends.
Server processing continues.
command, an unexpected error is detected.
User Response: Reissue the command and specify
System Action: Processing of the command ends.
SCRATCH=YES or specify additional volume names on
the command. User Response: Examine the server messages issued
error. Use the QUERY ACTLOG command to view the
ANR0693E Import command: Error abort code reading
export data.
Explanation: During processing of command import representative.
command, an input/output error occurs when reading
the exported information from the export media.
ANR0697E Export command: Output table error
System Action: Processing of the command ends. encountered - not positioned to the first
column in the table.
prior to this message to determine the source of the Explanation: During processing of command export
error. Use the QUERY ACTLOG command to view the command, an unexpected error is detected.
representative. User Response: Examine the server messages issued
ANR0694E Import command: Invalid record format
(format code) detected on import.
Explanation: During processing of command import representative.
command, an invalid record type is detected when
reading the exported information from the export
media.
FILEDATA parameter - parameter value.
User Response: Examine the server messages issued the FILEDATA parameter in command export/import
prior to this message to determine the source of the command is not a valid value for this parameter.
representative. User Response: Reissue the command and specify a
valid FILEDATA parameter. For information on valid
values for the FILEDATA parameter for the command,
ANR0695E Export command: Unexpected error error
refer to the Administrator’s Reference for your particular
code encountered in receiving table
platform.
output data.
ANR0699E Export/import command: Device class
command, an unexpected error is detected.
DISK cannot be specified for this
System Action: Processing of the command ends. command.
User Response: Examine the server messages issued Explanation: The DEVCLASS value DISK cannot be
prior to this message to determine the source of the specified for the command export/import command.
representative. User Response: Reissue the command and specify a
valid device class. Issue the QUERY DEVCLASS
command for a list of valid device classes for the
server.

PREVIEW parameter - parameter value.
server.
the PREVIEW parameter in command export/import
ANR0707E Export command: The FILESPACE
parameter cannot be specified.
Explanation: The FILESPACE parameter is specified
for the command export command, but the FILEDATA
User Response: Reissue the command and specify a parameter is specified as NONE, or is not specified and
valid PREVIEW parameter. For information on valid defaults to NONE. File spaces are only copied if the
values for the PREVIEW parameter for the command, FILEDATA parameter is specified with a value other
refer to the Administrator’s Reference for your particular than NONE.
platform.
SCRATCH parameter - parameter value.
valid FILEDATA parameter. For information on valid
Explanation: The value (parameter value) specified for parameter values for the command, refer to the
the SCRATCH parameter in command export/import Administrator’s Reference for your particular platform.
System Action: The command fails and server ANR0708E Import command: The FILESPACE
operation continues. parameter cannot be specified unless the
FILEDATA parameter specifies that files
should be imported.
valid SCRATCH parameter. For information on valid
values for the SCRATCH parameter for the command, Explanation: The FILESPACE parameter is specified
refer to the Administrator’s Reference for your particular for the command import command, but the FILEDATA
platform. 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
ANR0705E Export command: The VOLUMENAMES
than NONE.
parameter must be specified when
SCRATCH=NO is specified. System Action: The command fails and server
Explanation: The SCRATCH parameter is specified as
NO for the command export command but the User Response: Reissue the command and specify a
VOLUMENAMES parameter is not specified. When valid FILEDATA parameter. For information on valid
scratch volumes are not allowed, the VOLUMENAMES parameter values for the command, refer to the
parameter must be specified to indicate the volumes Administrator’s Reference for your particular platform.
that can be used for the command.
System Action: The command fails and server ANR0709E Command: No matching nodes registered
operation continues. in the specified domains.
User Response: Reissue the command and specify a Explanation: The DOMAIN parameter has been
valid VOLUMENAMES parameter. For information on specified for this command, but no nodes matching the
valid parameter values for the command, refer to the node name specification are found in the domains
Administrator’s Reference for your particular platform. specified.
ANR0706E Export command: A device class must be operation continues.
specified unless PREVIEW=YES is
specified.
valid combination of node and domain names. Use the
Explanation: The DEVCLASS parameter is not QUERY NODE command to view the names of nodes
specified in the command export command. Unless in the domains that you are interested in exporting.
PREVIEW=YES is specified, a DEVCLASS value must
be specified.

ANR0710E Command: Unable to start background ANR0714E Import command: The EXTFILE device
process. class cannot be specified when the
VOLUMENAMES parameter is
Explanation: The server command processor is not
specified.
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
System Action: The command process ends and
EXTFILE device class cannot be used in combination
with the VOLUMENAMES parameter.
Additional Server Memory”. User Response: Reissue the command with the correct
syntax.
ANR0711E Import command: Unable to start import
process. ANR0715E 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 Explanation: The command import command has been
import operation. specified, but does not include specification of the
DEVCLASS parameter. The DEVCLASS parameter
must be specified for this command.
information online or see “Appendix A. Allocating User Response: Reissue the command and specify a
Additional Server Memory”. valid device class. For a list of valid device classes for
the server, issue the QUERY DEVCLASS command.
DATES parameter - parameter value. ANR0716E Import command: Invalid export data
detected.
the DATES parameter in command import command is Explanation: The command import command
not a valid value for this parameter. encounters invalid data on the export media while
trying to import server information.
operation continues. System Action: The command fails and server
valid DATES parameter. For information on valid User Response: Ensure that the mounted export tapes
values for the DATES parameter for the command, are in the correct order (mounted in the same order as
refer to the Administrator’s Reference for your particular they were mounted during export). Reissue the
platform. 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.
REPLACEDEFS parameter - parameter
value.
ANR0717E Export/import command: Preview
processing terminated abnormally -
the REPLACEDEFS parameter in command import
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
User Response: Reissue the command and specify a server.
valid REPLACEDEFS parameter. For information on
System Action: Export/import processing is ended
valid values for the REPLACEDEFS parameter for the
command, refer to the Administrator’s Reference for your
particular platform. User Response: Examine the server messages issued

activity log and search for messages. If the error cannot User Response: Examine the server messages issued
be isolated and resolved, contact your service prior to this message to determine the source of the
representative. error. Use the QUERY ACTLOG command to view the
ANR0718E Export/import command: Processing
representative.
terminated abnormally -
communications send or receive failed.
terminated abnormally - unexpected
command ends when an internal communications error
verb received from server.
is encountered in the server.
command ends when an internal communications error
System Action: Export/import processing ends and
representative. error. Use the QUERY ACTLOG command to view the
representative.
command in preview mode is ended because sufficient
transaction failure.
memory is not available on the server.
command in preview mode ends when a database
transaction error is encountered in the server.
Additional Server Memory”. User Response: Examine the server messages issued
ANR0720E command: Processing terminated
abnormally - insufficient memory.
Explanation: Processing for the command ends representative.
because sufficient memory is not available on the
server.
System Action: Command processing is ended and terminated abnormally - transaction
server operation continues. failure.
User Response: Allocate additional storage to the Explanation: Processing for the command export/import
server. For details, issue HELP MEMORY to display the command ends when a database transaction error is
information online or see “Appendix A. Allocating encountered in the server.
unexpected verb received from server.
Explanation: Processing for the command export/import activity log and search for messages. If the error cannot
command in preview mode ends when an internal be isolated and resolved, contact your service
communications error is encountered in the server. representative.


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

ANR0732E Import command: Invalid value for ANR0736E Import command: Invalid value for
ARCHDELETE parameter in exported BACKDELETE parameter in exported
data for node node name. data - node node name registered with
default BACKDELETE value.
import command, an invalid value is encountered for the Explanation: During processing of command import
ARCHDELETE parameter for node node name. command, an invalid value is encountered for the
BACKDELETE parameter for node node name.
If a later command causes the data to be imported, the System Action: Processing of the command continues,
default or existing ARCHDELETE value is used. by using the default BACKDELETE value for this node.
User Response: None. If the data is imported with a User Response: Verify that the correct BACKDELETE
later command, verify that the correct ARCHDELETE value has been used for this node. Update this value, if
value is used for this node. necessary.
BACKDELETE parameter in exported COMPRESSION parameter in exported
data for node node name. data - existing COMPRESSION value
for node node name was not updated.
BACKDELETE parameter for node node name. command, an invalid value is encountered for the
COMPRESSION parameter for node node name.
default or existing BACKDELETE value is used. by using the existing COMPRESSION value for this
node.
later command, verify that the correct BACKDELETE User Response: Verify that the correct
value is used for this node. COMPRESSION value has been used for this node.
Update this value, if necessary.
COMPRESSION parameter in exported ANR0738E Import command: Invalid value for
data - node node name registered with ARCHDELETE parameter in exported
default COMPRESSION value. data - existing ARCHDELETE value for
node node name was not updated.
command, an invalid value is encountered for the Explanation: During processing of command import
COMPRESSION parameter for node node name. command, an invalid value is encountered for the
ARCHDELETE parameter for node node name.
by using the default COMPRESSION value for this System Action: Processing of the command continues,
node. by using the existing ARCHDELETE value for this
node.
COMPRESSION value has been used for this node. User Response: Verify that the correct ARCHDELETE
Update this value, if necessary. value has been used for this node. Update this value, if
necessary.
ARCHDELETE parameter in exported ANR0739E Import command: Invalid value for
data - node node name registered with BACKDELETE parameter in exported
default ARCHDELETE value. data - existing BACKDELETE value for
node node name was not updated.
command, an invalid value is encountered for the Explanation: During processing of command import
ARCHDELETE parameter for node node name. command, an invalid value is encountered for the
by using the default ARCHDELETE value for this node. System Action: Processing of the command continues,
by using the existing BACKDELETE value for this
User Response: Verify that the correct ARCHDELETE
node.
value has been used for this node. Update this value, if
necessary. User Response: Verify that the correct BACKDELETE

value has been used for this node. Update this value, if
necessary.
MODE parameter in exported data for
archive copy group copy group name in
ANR0740E Import command: Invalid value for TYPE domain domain name, set policy set name,
parameter in exported data for copy management class management class name.
group copy group name in domain domain
name, set policy set name, management
class management class name - backup is
MODE parameter for archive copy group copy group
assumed.
name, in policy domain domain name, policy set policy set
Explanation: During processing of command import name, management class management class name.
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
default or existing MODE value is used.
class management class name.
later command, verify that the correct MODE value is
Based upon other copy group parameters, a copy group
used for this archive copy group.
type of backup is assigned.
User Response: Verify that the assigned TYPE value
of backup for this copy group is correct.
MODE parameter in exported data for
backup copy group copy group name in
ANR0741E Import command: Invalid value for TYPE domain domain name, set policy set name,
parameter in exported data for copy management class management class name.
class management class name - archive is
MODE parameter for backup copy group copy group
assumed.
Explanation: During processing of command import name, management class management class name.
command, an invalid value is encountered for the TYPE
parameter for copy group copy group, in policy domain
default or existing MODE value is used.
later command, verify that the correct MODE value is
Based upon other copy group parameters, a copy group
used for this backup copy group.
type of archive is assigned.
User Response: Verify that the assigned TYPE value
of archive for this copy group is correct.
SERIALIZATION parameter in exported
data for archive copy group copy group
ANR0742E Import command: Invalid value for TYPE name in domain domain name, set policy
parameter in exported data for copy set name, management class management
group copy group name in domain domain class name.
class management class name - this copy
group will not be imported.
SERIALIZATION parameter for archive copy group
Explanation: During processing of command import copy group name, in policy domain domain name, policy
command, an invalid value is encountered for the TYPE set policy set name, management class management class
parameter for copy group copy group, in policy domain name.
System Action: Processing of the command continues. default or existing SERIALIZATION value is used.
However, this copy group is not imported because a
TYPE value cannot be assigned.
later command, verify that the correct SERIALIZATION
User Response: Manually define this copy group, if value is used for this archive copy group.
necessary.

SERIALIZATION parameter in exported SERIALIZATION parameter in exported
data for backup copy group copy group data - archive copy group copy group
name in domain domain name, set policy name in domain domain name, set policy
set name, management class management set name, management class management
class name. class name defined with default
SERIALIZATION value.
SERIALIZATION parameter for backup copy group command, an invalid value is encountered for the
copy group name, in policy domain domain name, policy SERIALIZATION parameter for archive copy group
set policy set name, management class management class copy group name, in policy domain domain name, policy
name. set policy set name, management class management class
name.
default or existing SERIALIZATION value is used. by using the default SERIALIZATION value for this
archive copy group.
later command, verify that the correct SERIALIZATION User Response: Verify that the correct
value is used for this backup copy group. SERIALIZATION value has been used for this copy
group. Update this value, if necessary.
MODE parameter in exported data - ANR0750E Import command: Invalid value for
archive copy group copy group name in SERIALIZATION parameter in exported
domain domain name, set policy set name, data - backup copy group copy group
management class management class name name in domain domain name, set policy
defined with default MODE value. set name, management class management
class name defined with default
SERIALIZATION value.
MODE parameter for archive copy group copy group Explanation: During processing of command import
name, in policy domain domain name, policy set policy set command, an invalid value is encountered for the
name, management class management class name. SERIALIZATION parameter for backup copy group
copy group name, in policy domain domain name, policy
set policy set name, management class management class
by using the default MODE value for this archive copy
name.
group.
User Response: Verify that the correct MODE value
by using the default SERIALIZATION value for this
has been used for this copy group. Update this value, if
backup copy group.
necessary.
SERIALIZATION value has been used for this copy
group. Update this value, if necessary.
MODE parameter in exported data -
backup copy group copy group name in
domain domain name, set policy set name, ANR0751E Import command: Invalid value for
management class management class name MODE parameter in exported data -
defined with default MODE value. existing MODE value for archive copy
class management class name was not
updated.
name, management class management class name. Explanation: During processing of command import
MODE parameter for archive copy group copy group
by using the default MODE value for this backup copy
group.
name, management class management class name.
by using the existing MODE value for this archive copy
necessary.
group.

User Response: Verify that the correct MODE value System Action: Processing of the command continues,
has been used for this copy group. Update this value, if by using the existing SERIALIZATION value for this
necessary. backup copy group.
ANR0752E Import command: Invalid value for SERIALIZATION value has been used for this copy
MODE parameter in exported data - group. Update this value, if necessary.
existing MODE value for backup copy
ACTION parameter in exported data for
class management class name was not
schedule schedule name in domain domain
updated.
name.
ACTION parameter for schedule schedule name in policy
domain domain name.
name, management class management class name.
by using the existing MODE value for this backup copy
default or existing ACTION value is used.
group.
User Response: If the data is imported with a later
command, verify that the correct ACTION value is
used for this schedule.
necessary.

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

ACTION parameter in exported data - ACTION parameter in exported data -
schedule schedule name in domain domain existing ACTION value for schedule
name defined with default ACTION schedule name in domain domain name was
value. not updated.
Explanation: During processing of command import Explanation: During processing of command import
command, an invalid value is encountered for the command, an invalid value is encountered for the
ACTION parameter for schedule schedule name in policy ACTION parameter for schedule schedule name in policy
domain domain name. domain domain name.
System Action: Processing of the command continues, System Action: Processing of the command continues,
by using the default ACTION value for this schedule. by using the existing ACTION value for this schedule.
User Response: Verify that the correct ACTION value User Response: Verify that the correct ACTION value
has been used for this schedule. Update this value, if has been used for this schedule. Update this value, if
necessary. necessary.
DURUNITS or PERUNITS parameter in DURUNITS or PERUNITS parameter in
exported data - schedule schedule name in exported data - existing values for
domain domain name defined with DURATION, DURUNITS PERIOD, and
default values for DURATION, PERUNITS for schedule schedule name in
DURUNITS, PERIOD, and PERUNITS. domain domain name were not updated.
DURUNITS or PERUNITS parameter for schedule DURUNITS or PERUNITS parameter for schedule
schedule name in policy domain domain name. schedule name in policy domain domain name.
by using the default values for DURATION, by using the existing values for DURATION,
DURUNITS, PERIOD, and PERUNITS. DURUNITS, PERIOD, and PERUNITS.
User Response: Verify that the correct values have User Response: Verify that the correct values have
been used for DURATION, DURUNITS, PERIOD, and been used for DURATION, DURUNITS, PERIOD, and
PERUNITS. Update these values, if necessary. PERUNITS. Update these values, if necessary.
DAYOFWEEK parameter in exported DAYOFWEEK parameter in exported
data - schedule schedule name in domain data - existing DAYOFWEEK value for
domain name defined with default schedule schedule name in domain domain
DAYOFWEEK value. name was not updated.
DAYOFWEEK parameter for schedule schedule name in DAYOFWEEK parameter for schedule schedule name in
policy domain domain name. policy domain domain name.
by using the default DAYOFWEEK value for this by using the existing DAYOFWEEK value for this
schedule. schedule.
User Response: Verify that the correct DAYOFWEEK User Response: Verify that the correct DAYOFWEEK
value has been used for this schedule. Update this value has been used for this schedule. Update this
value, if necessary. value, if necessary.
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.

System Action: Processing of the command continues, this copy group. If this data is imported, the default or
but the node is not locked. existing MODE value is used.
User Response: An administrator with the proper User Response: Update the MODE value for this copy
authorization must issue the LOCK NODE command, if group and restart the export command. Alternatively,
necessary. use the export data with the unknown value, and check
and update the MODE value after import processing
has been performed.
ANR0765E Import command: Invalid lock status
detected while importing administrator
administrator name - this administrator ANR0768E Export command: Invalid value for
will not be locked. SERIALIZATION parameter detected
while exporting copy group copy group
name in domain domain name, set policy
command, an invalid value is encountered for the lock
set name, management class management
status for administrator administrator name.
class name - default or existing value is
System Action: Processing of the command continues, used during import.
but the administrator is not locked.
User Response: An administrator with the proper command, an invalid value is encountered for the
authorization must issue the LOCK ADMIN command, SERIALIZATION parameter for copy group copy group
if necessary. name, in domain domain name, policy set policy set name,
management class management class name.
ANR0766E Export command: Invalid value for TYPE System Action: Export processing continues, but the
parameter detected while exporting copy exported data contains an unknown SERIALIZATION
group copy group name in domain domain value for this copy group. If this data is imported, the
name, set policy set name, management default or existing SERIALIZATION value is used.
class management class name - system will
User Response: Update the SERIALIZATION value
attempt to assign value during import.
for this copy group and restart the export command.
Explanation: During processing of command export Alternatively, use the export data with the unknown
command, an invalid value is encountered for the TYPE value, and check and update the SERIALIZATION
parameter for copy group copy group name, in domain value after import processing has been performed.
System Action: Export processing continues, but the ACTION parameter detected while
exported data contains an unknown TYPE value for exporting schedule schedule name in
this copy group. If this data is imported, the system domain domain name - default or existing
attempts to assign a TYPE value based upon values for value is used during import.
other copy group parameters.
User Response: Delete and define this copy group to command, an invalid value is encountered for the
eliminate the invalid data, and then restart the export ACTION parameter for schedule schedule name in
command. Alternatively, use the export data with the domain domain name.
unknown value, and the system will attempt to assign
a TYPE during import processing.
exported data will contain an unknown ACTION value
for this schedule. If this data is imported, the default or
ANR0767E Export command: Invalid value for existing ACTION value is used.
MODE parameter detected while
User Response: Update the ACTION value for this
exporting copy group copy group name in
schedule and restart the export command. Alternatively,
domain domain name, set policy set name,
use the export data with the unknown value, and check
management class management class name
and update the ACTION value after import processing
- default or existing value is used
has been performed.
during import.
MODE parameter for copy group copy group name in
domain domain name, policy set policy set name,
management class management class name.
exported data contains an unknown MODE value for

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

import processing has been performed. System Action: The command command is ended and
ANR0776E Export command: Invalid value for User Response: Make sure that all volumes specified
ARCHDELETE parameter detected for the command command are tape volumes.
while exporting node node name - default
ANR0780E Export/import command: Process aborted -
Explanation: During processing of command export a server communications session could
command, an invalid value is encountered for the not be established.
ARCHDELETE parameter for node node name.
System Action: Export processing continues, but the encounters an internal error in establishing an
exported data contains an unknown ARCHDELETE intermemory communications session with other server
value for this node. If this data is imported, the default components.
or existing ARCHDELETE value is used.
User Response: Update the ARCHDELETE parameter and server operation continues.
for this node and restart the export command.
value, and check and update the ARCHDELETE value
Additional Server Memory”. If the error is not resolved,
contact your service representative.
BACKDELETE parameter detected while
exporting node node - default or existing
server sign on failed.
value is used during import.
encounters an internal error in establishing an
intermemory communications session with other server
components.
exported data contains an unknown BACKDELETE
value for this node. If this data is imported, the default
or existing BACKDELETE value is used. User Response: Contact your service representative.
User Response: Update the BACKDELETE parameter
for this node and restart the export command. ANR0782E Export/import command: Process aborted -
Alternatively, use the export data with the unknown a server data storage session could not
value, and check and update the BACKDELETE value be established (rc return code).
encounters an internal error in establishing a session
ANR0778E Command: Error encountered in accessing with the data storage services.
data storage - device class device class
name is not defined. System Action: The export or import process ends
Explanation: During command command processing,
an error occurred because the specified device class is User Response: Examine the server messages issued
not defined. prior to this message to determine the source of the
System Action: The command command is ended and activity log and search for messages. If the error cannot
server operation continues. be isolated and resolved, contact your service
representative.
User Response: Make sure the specified device class is
defined.
a server data storage Export/Import
ANR0779E Command: Error encountered in accessing
stream could not be established (rc
data storage - disk volume specified.
return code).
an error occurred because a specified volume is a disk
encounters an internal error in establishing a session
volume rather than a tape volume.
with the data storage services.

ANR0787E Import command: Import of file space
filespace name in node node name aborted
User Response: Examine the server messages issued by server (abort reason).
Explanation: The server import process encounters an
internal error in importing file space filespace name for
client node node name. The reason code abort reason is
encountered.
representative.
internal error detected with the User Response: Examine the server messages issued
Export/Import level: level number. prior to this message to determine the source of the
encounters an internal error in evaluating the
export/import level (SERVER, NODE, ADMIN,
representative.
POLICY).
ANR0788E Import command: Error error code during
import of data storage data.
internal data storage error. The error code error code is
encountered.
be isolated and resolved, contact your service System Action: The export or import process ends
representative. and server operation continues.
ANR0785E Import command: Invalid record type prior to this message to determine the source of the
xrecord type read from export data. error. Use the QUERY ACTLOG command to view the
encounters an internal error in reading data from the
representative.
export media. An invalid record type of record type is
encountered during the read operation.
ANR0789E Import command: Failure in normalizing
transaction identifier for sending to the
server.
internal database transaction error in importing
information into the server database.
be isolated and resolved, contact your service System Action: The export or import process ends
representative. and server operation continues.
ANR0786E Import command: Invalid export version prior to this message to determine the source of the
version number in exported data. error. Use the QUERY ACTLOG command to view the
internal error in reading data from the export media.
representative.
An invalid export version number (version number) is
encountered during the read operation.
ANR0790E Import command: Error in absorbing data
records.
internal error in importing information into the server
database.
activity log and search for messages. If the error cannot System Action: The export or import process ends
be isolated and resolved, contact your service and server operation continues.
representative.

User Response: Examine the server messages issued to examine messages prior to this error to determine
prior to this message to determine the source of the the cause of the data storage failure. If you find and
error. Use the QUERY ACTLOG command to view the resolve the error, retry the export or import operation.
activity log and search for messages. If the error cannot If you cannot find the error, contact your service
be isolated and resolved, contact your service representative for assistance in resolving the problem.
representative.
ANR0791E Export/import command: Protocol error - terminated abnormally - error accessing
verb ″verb type″ with length verb length data storage.
received, expected ″expected type″.
Explanation: The server export or import process in accessing data storage while executing an import or
encounters an internal protocol error in exporting export operation.
information from or importing information into the
System Action: The export or import operation is
server database. The verb verb type is encountered with
a length of verb length when a verb type of expected type
was expected. User Response: Use the QUERY ACTLOG command
to examine messages prior to this error to determine
the cause of the data storage failure. If you find and
resolve the error, retry the export or import operation.
User Response: Examine the server messages issued If you cannot find the error, contact your service
prior to this message to determine the source of the representative for assistance in resolving the problem.
data storage - invalid volume name
representative.
specified.
Explanation: The server encounters an error in
ANR0792E Import command: Invalid copy type
accessing data storage while processing command
encountered in an imported file space
command. The error occurred because an attempt has
authorization rule for node node name,
been made to access a volume with an invalid name.
file space filespace name - a type of
BACKUP will be assumed. System Action: The command command operation is
Explanation: During import processing for command
import command, an invalid copy type is encountered User Response: Issue the command with a valid
for an authorization rule that grants access for file volume name.
space filespace name on node node name. Authorization
rules typically specify copy types of backup or archive,
depending on whether backup file access or archive file ANR0796E Command: Error encountered in accessing
access is granted by the file space owner to other users. data storage - insufficient number of
Because the imported information for the rule is mount points available for removable
ambiguous, the server assumes that the rule is for media.
backup data. Explanation: During command command processing,
System Action: The import process continues. the server cannot allocate sufficient mount points.
User Response: The user for node node name should System Action: The command command operation is
query the access rules for the specified node name after ended and server operation continues.
the import process has completed, and correct or delete User Response: If necessary, make more mount points
any access rules that are in error or not needed. available.
ANR0793E Export/import command: Preview ANR0797E Command: Error encountered in accessing

processing terminated abnormally - data storage - required volume was not
error accessing data storage. mounted.
Explanation: The server encountered an internal error Explanation: During command command processing, a
in accessing data storage while executing an import or required volume cannot be mounted. The mount
export preview operation. request may have been canceled.
System Action: The export or import operation is System Action: The command command operation is
ended and server operation continues. ended and server operation continues.
User Response: Use the QUERY ACTLOG command

User Response: Issue the command again and make
ANR0801I DELETE FILESPACE filespace name for
sure the necessary volumes are accessible.
node node name started as process process
ID.
ANR0798E Import command: Error encountered in
Explanation: The specified client node has started a
accessing data storage - volume cannot
file space deletion process (on the server) to delete one
be used.
or more file spaces. The process has been assigned the
Explanation: During import processing, a volume has ID specified in the message.
been mounted but cannot be used.
System Action: The server starts a background
System Action: The import operation is ended and process to perform the operation in response to a
server operation continues. request from the client node.
User Response: Query the activity log for messages User Response: To obtain status on the file space
preceding this one that give additional information. deletion process, issue the QUERY PROCESS command.
Make sure a usable volume is specified and mounted. The process may be canceled by an authorized
administrator using the CANCEL PROCESS command.

data storage - volume already in use. ANR0802I DELETE FILESPACE filespace name
(backup/archive data) for node node name
Explanation: During command command processing, a started.
volume cannot be used because it is already defined in
a storage pool, or has been previously used by an Explanation: A background server process has started
export, database dump, or database backup operation (on the server) to delete the specified file space
(as recorded in the volume history) or is in use by belonging to the node indicated. If a file space name is
another process. not included in the message, all file spaces belonging to
the node are deleted.
System Action: The command command operation is
ended and server operation continues. System Action: The background process deletes
backup and archive objects for the specified file space
User Response: Specify a volume that is not in use or while server operation continues.
defined in a storage pool, and that has not been
previously used for an export, database dump, or User Response: To obtain status on the file space
database backup operation as recorded in the server deletion process, issue the QUERY PROCESS command.
volume history information. Use the QUERY VOLUME The process may be canceled by an authorized
command to display the names of volumes that are administrator using the CANCEL PROCESS command.
defined to server storage pools. Use the QUERY
VOLHISTORY command to display the names of
ANR0803I DELETE FILESPACE filespace name
volumes that have been used for export, database
(backup data) for node node name
dump, or database backup operations.
started.
Explanation: A background server process has started
ANR0800I Command command for node node name
(on the server) to delete backup objects in the specified
started as process process ID.
file space belonging to the node indicated. If a file
Explanation: A file space deletion process has started space name is not included in the message, then the
to delete one or more file spaces for the specified node. backup objects for all file spaces that belong to the
The process is assigned the ID specified in the message. node are deleted.
System Action: The server starts a background System Action: The background process deletes
process to perform the operation in response to the backup objects for the specified file space while server
DELETE FILESPACE command entered by an operation continues.
administrator.
User Response: To obtain status on the file space
User Response: To obtain status on the file space deletion process, issue the QUERY PROCESS command.
deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized
The process may be canceled with the CANCEL administrator using the CANCEL PROCESS command.
PROCESS command.
(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
ANR0812I Inventory file expiration process process
node are deleted.
ID completed: examined number of objects
System Action: The background process deletes objects, deleting number of backup objects
archive objects for the specified file space while server backup objects, number of archive objects
operation continues. archive objects, number of DB backup
volumes DB backup volumes, and number
User Response: To obtain status on the file space of recovery plan files recovery plan files.
deletion process, issue the QUERY PROCESS command. error count errors were encountered.
The process may be canceled by an authorized
administrator using the CANCEL PROCESS command. Explanation: Server roll-off processing has completed.
The number of client objects examined and deleted,
based on management class policy, are displayed in the
ANR0805I DELETE FILESPACE filespace name message. A total error count is also displayed. The
canceled for node node name: number of number of DB backup volumes deleted is based on the
objects objects deleted. value specified on the SET
Explanation: A background server process that has DRMDBBACKUPEXPIREDAYS. The number of
been deleting file space data for the indicated node is recovery plan files deleted is based on the value
canceled by the CANCEL PROCESS command. The specified on the SET DRMRPFEXPIREDAYS. Server
number of objects deleted before the cancel ended the roll-off processing deletes the DB backup volumes and
operation are reported in the message. recovery plan files only if DRM is licensed on the
server and the volumes or plan files are created on the
System Action: The server process is ended and server to server virtual volumes.
System Action: The roll-off process is ended and
User Response: No action is required. An authorized server operation continues.
administrator can issue the DELETE FILESPACE
command to delete remaining objects in the file space. 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.
complete for node node name: number of
objects objects deleted. ANR0813I Inventory file expiration process process
ID canceled prior to completion:
Explanation: A server process deleting file space data examined number of objects objects,
for the node specified has completed. The total number deleting number of backup objects backup
of objects deleted is reported in the message. objects, number of archive objects archive
System Action: The server process is ended and objects, number of DB backup volumes DB
server operation continues. backup volumes, and number of recovery
plan files recovery plan files. error count
User Response: None. errors were encountered.
Explanation: The inventory file expiration process was
ANR0811I Inventory client file expiration started as canceled by an administrator. The number of objects
process process ID. examined and deleted prior to the cancelation are
Explanation: The server has started roll-off processing reported. A total error count is also displayed.
to remove expired client backup and archive file copies, System Action: The server ends the file expiration
based on the management class policy that is bound to process.
the files. The copy group retention and version
parameters for each file’s copy group are used by the User Response: None.
server to determine if copies are to be deleted from the
server. The expiration process was started as process ANR0814I Expiration retry retry number of maximum
number process ID, and may be queried or canceled retries in number of seconds seconds.
with the QUERY PROCESS or CANCEL PROCESS
commands, respectively. Explanation: Server roll-off processing has
encountered an error in attempting to remove expired
System Action: The expiration process is now client file copies from the server database. The
cancellable. Server operation continues. operation will be tried again in the number of seconds
User Response: None. 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 expiration process. Correct the shortage.
sufficient server memory is not available to continue
processing. Use the QUERY ACTLOG command to look
ANR0819I Cancel in progress
for messages issued prior to this one that indicate the
type of error encountered. If the server is out of Explanation: This message is displayed in response to
database space, issue the DEFINE DBVOLUME and a QUERY PROCESS command, and indicates that an
EXTEND DB commands to add volumes to the server inventory expiration process has been canceled. The
database and extend the database size. If the server is process will end shortly.
out of log space, issue the DEFINE LOGVOLUME and
EXTEND LOG commands to add volumes to the server System Action: The expiration process terminates and
log and extend the log size. If the server is low on server operation continues.
memory, allocate additional storage to the server. For User Response: None.
details, issue HELP MEMORY to display the
Additional Server Memory”. ANR0820I Sorting information for number objects
has been deleted.
ANR0815I Expiration retry in progress. Explanation: A background server process has deleted
sorting information for number files from the server
Explanation: The server is retrying an operation database. This process is started during initialization to
during client file roll-off processing. Expiration retry remove any sorting information which is left over from
processing occurs when the server database is full, the previous export operations.
log is full, or sufficient server memory is not available
to continue processing. System Action: The actual backup or archive objects
were not deleted, but only information used to sort
System Action: The roll-off operation is retried. these objects during the previous export operation.
User Response: Use the QUERY ACTLOG command User Response: None.
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 ANR0821E Filespace identifier fsId is not valid.
and EXTEND DB commands to add volumes to the Explanation: The identifier assigned for a filespace is
server database and extend the database size. If the out of range.
server is out of log space, issue the DEFINE
LOGVOLUME and EXTEND LOG commands to add System Action: The file space is not added.
volumes to the server log and extend the log size. If the User Response: Contact your service representative.
server is low on memory, allocate additional storage to
the server. For details, issue HELP MEMORY to display
the information online or see “Appendix A. Allocating ANR0822I command: Filespace filespace name
Additional Server Memory”. (fsId=filespace id) successfully renamed
to new filespace name for node node name.
ANR0816I Expiration retry was successful. Explanation: The file space specified was renamed to
the new name specified for the node. This message is
Explanation: In accordance with management class displayed in response to successful completion of the
policy, server roll-off processing has been successful in RENAME FILESPACE command.
retrying a client file expiration.
System Action: The system renames the file space for
System Action: Server roll-off processing continues. the node as indicated
User Response: None. User Response: None.
ANR0818I Waiting to retry expiration because of ANR0823E command: Filespace filespace name cannot
insufficient resources. be renamed to new filespace name, a
Explanation: The server inventory expiration process filespace with this name already exists
is waiting to retry expiration processing that failed for node node name.
because of insufficient memory, database, or log Explanation: The file space name specified as a target
resources on the server. name for the command was found to already exist for
System Action: Server operation continues. The the node specified. The command fails.
expiration processing is reattempted automatically. System Action: Server operation continues, the
User Response: Use the QUERY ACTLOG command command fails.
to examine messages issued prior to this one, which
indicated the resource that is not available to the

User Response: Reissue the command with a different The number of objects deleted before the operation
target filespace name ended are reported in the message.
System Action: The server process is ended and
ANR0824I Delete Filespace filespace name server operation continues.
(space-managed data) for node node name
User Response: Termination of this process because of
started.
transaction failure usually indicates that a database
Explanation: A background server process has started deadlock was detected during file space deletion. These
(on the server) to delete space-managed objects in the deadlock conditions are sometimes encountered when
specified file space belonging to the node indicated. If a multiple file space deletion processes are running at the
file space name is not included in the message, then the same time. The command should be started again
space-managed objects for all file spaces that belong to when fewer file space deletion processes are active. An
the node are deleted. authorized administrator can issue the DELETE
FILESPACE command to delete remaining files in the
System Action: The background process deletes
file space(s).
space-managed objects for the specified file space while
ANR0829E Command: Invalid combination of TYPE
User Response: To obtain status on the file space
and DATA parameters.
deletion process, issue the QUERY PROCESS command.
The process may be canceled by an authorized Explanation: The specified command has been issued
administrator using the CANCEL PROCESS command. with an invalid combination of the TYPE and DATA
parameters. DATA=IMAGES can only be specified if
TYPE=ANY or TYPE=BACKUP.
ANR0826I DELETE FILESPACE filespace name for
node node name encountered a System Action: Server operation continues, but the
transaction failure. command is not processed.
Explanation: A background server process that has User Response: Issue the command and specify a
been deleting file space data for the indicated node valid combination of parameters.
encountered a transaction failure.
System Action: The server process is retried if the ANR0830W Management class class name in domain
maximum number of retry attempts have not been domain name used by node node name in
exceeded. file space filespace name is no longer
active, or no longer has a BACKUP copy
User Response: Transaction failure usually indicates
group: DEFAULT management class
that a database deadlock was detected during file space
attributes will be used for expiration.
deletion. These deadlock conditions are sometimes
encountered when multiple file space deletion Explanation: During policy roll-off processing, the
processes are running at the same time. No action is server has found a client file copy whose management
required unless the DELETE FILESPACE terminates class or backup copy group no longer exists.
without completing the deletion process (see message
System Action: The server obtains the DEFAULT
ANR0828).
management class for the specified domain and uses its
backup copy group version and retention parameters to
ANR0827I DELETE FILESPACE filespace name will determine if file copies need to be expired.
be retried for node node name.
User Response: No action is required. A policy
Explanation: A file space deletion process for the node administrator with authority over the specified domain
indicated is being retried because an error was may use the DEFINE COPYGROUP, DEFINE
encountered. MGMTCLASS, and ACTIVATE POLICY commands to
define and activate a policy set that contains definitions
System Action: The server process is retried.
for the missing management class or copy group.
ANR0831W The DEFAULT management class class
ANR0828W DELETE FILESPACE filespace name for name in domain domain name does not
node node name terminated before have a BACKUP copy group: GRACE
completion due to transaction failure: PERIOD will be used for expiration.
number of objects objects deleted.
Explanation: During policy roll-off processing, the
Explanation: A background server process that has server found a client file copy whose management class
been deleting file space data for the indicated node is or backup copy group no longer exists. The DEFAULT
terminated prematurely because of transaction failure. 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 may use the DEFINE COPYGROUP, DEFINE
the specified policy domain to determine if client file MGMTCLASS, and ACTIVATE POLICYSET commands
copies need to be expired and removed from the server to define and activate a policy set that contains
database. definitions for the missing management class or backup
copy group.
System Action: The server obtains the GRACE
PERIOD retention values for the specified domain and
then determines if backup file copies need to be ANR0834W Inventory client file expiration cannot
expired. start because of insufficient memory -
will retry in number of seconds seconds.
User Response: No action is required. A policy
administrator with authority over the specified domain Explanation: The server inventory expiration process
may use the DEFINE COPYGROUP, DEFINE is pausing to retry an operation that failed because
MGMTCLASS, and ACTIVATE POLICY commands to sufficient memory is not available on the server.
define and activate a policy set that contains definitions
for the missing management class or backup copy
expiration process will be retried after the stated delay.
group.
ANR0832W Management class class name in domain
domain name used by node node name in
filespace filespace name is no longer
active, or no longer has an ARCHIVE
copy group: DEFAULT management ANR0835W Management class class name in domain
class attributes will be used for domain name is no longer active, or no
expiration. longer has a BACKUP copy group, or no
longer has an ARCHIVE copy group.
DEFAULT management class used to
server found a client file copy whose management class
delete number of backup files backup files
or archive copy group no longer exists.
and number of archive files archive files.
System Action: The server obtains the DEFAULT Retention grace period used to delete
management class for the specified domain and uses its number of backup files backup files and
archive copy group retention parameter to determine if number of archive files archive files.
file copies need to be expired.
User Response: No action is required. A policy server found a management class or backup copy
administrator with authority over the specified domain group or archive copy group that no longer exists.
may use the DEFINE COPYGROUP, DEFINE When a management class or backup copy group no
MGMTCLASS, and ACTIVATE POLICY commands to longer exists, the number of backup client file copies
define and activate a policy set that contains definitions that have been deleted using the default management
for the missing management class or copy group. 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
ANR0833W The DEFAULT management class class
files that have been deleted using the default
name in domain domain name does not
management class or the retention grace period is
have an ARCHIVE copy group: GRACE
displayed in the message.
PERIOD will be used for expiration.
System Action: The server obtains the DEFAULT
management class for the specified domain and uses its
server found a client file copy whose management class
backup copy group or archive copy group version and
or archive copy group no longer exists. The DEFAULT
retention parameters to determine if file copies need to
management class for the indicated policy domain does
be expired. If, however, the needed backup copy group
not contain an archive copy group; therefore, the server
or archive copy group does not exist in the DEFAULT
uses the GRACE PERIOD retention value defined for
management class, the server will use the retention
the specified policy domain to determine if client file
grace period for the domain.
copies need to be expired and removed from the server
database. User Response: No action is required. This message is
only issued when expiration processing has been
System Action: The server obtains the GRACE
started with the QUIET option to suppress detailed
PERIOD retention values for the specified domain and
messages. Expiration processing can be started without
then determines if archive file copies need to be
the QUIET option to see the detailed messages which
expired.
will indicate specific node and filespaces and will
User Response: No action is required. A policy further distinguish between backup and archive copy
administrator with authority over the specified domain groups. A policy administrator with authority over the

specified domain may use the DEFINE COPYGROUP,
ANR0840I Command: Archive directory cleanup job
DEFINE MGMTCLASS, and ACTIVATE POLICY
Job ID started as foreground process
commands to define and activate a policy set that
process ID.
contains definitions for the missing management class
or copy group. Explanation: An archive directory cleanup job started
under the indicated foreground server process with the
indicator process identifier.
ANR0836W No query restore processing session
session id for node node name and filespace System Action: Server processing continues.
name failed to retrieve file high-level file
namelow-level file name - file being
skipped.
ANR0841I ( Job ID ): Skipping node node ID; node
Explanation: The no query restore processing for the
being cleaned by job Other Job ID.
session listed relating to the specified node name and
filespace failed to retrieve the specified file. An error Explanation: The indicated archive directory cleanup
occurred while retrieving this file so it will be skipped. job is skipping the indicated node because a different
archive directory cleanup job ( as specified ) is working
System Action: The no query restore operation
on the same node.
continues.
System Action: Server processing continues.
User Response: Determine the cause of the file retieve
failure and correct it. After this situation is correct, the User Response: None.
client can do a restore of the specific file that was
skipped.
ANR0842I Command: ( Job ID ): Archive cleanup
was cancelled - number of nodes nodes
ANR0837I The expire inventory running duration processed, last node was last node.
of number of minutes minutes has
expired. The expire inventory process Explanation: The indicated archive directory cleanup
ends. job was cancelled. Prior to cancellation, the indicated
number of nodes were processed. The last processed
Explanation: An ADSM Administrator or schedule node is also displayed.
issued the command EXPIRE INVENTORY ...
DURATION=xxx, where xxx is the number of minutes System Action: .The archive cleanup operation ends.
for the expire inventory process to run. That xxx Server processing continues.
number of minutes has been reached, so the expire User Response: The archive directory cleanup may be
inventory process ends. restarted by specifying the JOBID parameter on the
System Action: The expire inventory process ends. CLEAN ARCHDIRectories command.

ANR0843I Command: Archive directory cleanup job
Job ID completed successfully. number of
ANR0838I Command: Archive directory cleanup job nodes nodes were processed.
Job ID started as background process
process ID. Explanation: An archive directory cleanup job
completed successfully. The job identifier and the
Explanation: An archive directory cleanup job started number of nodes that were processed are displayed.
under the indicated background server process with the
indicated process identifier. System Action: The archive directory cleanup
operation ends.
ANR0844E Job ID : Skipping node node name - node
ANR0839E Command: There are no restartable jobs. not found.
Job Job ID not found.
Explanation: The indicated nodename was not
Explanation: A QUERY ARCHDIRCLEAN command processed by the indicated archive directory cleanup
was issued but no archive directory cleanup jobs were job. The node was not found by the time the job got
found. The jobid is 0 if a specific job id was specified around to working on it.
on the Query command.
System Action: The node is skipped. Other nodes are
System Action: Server processing continues. processed.

subsequent expiration attempt the file still is not
ANR0845I Job ID : Skipping node node name - is not
deleted, please contact your service representative.
a backup/archive node.
Explanation: The indicated nodename was not
ANR0849E Command: Not permitted for node Node
processed by the indicated archive directory cleanup
Name - node of type SERVER.
job. The node was not a backup/archive client node.
Explanation: The indicated DELETE FILESPACE
System Action: The node is skipped. Other nodes are
process is not started because the node specified is of
processed.
NODETYPE=SERVER. A DELETE FILESPACE may
User Response: None. only be processed for nodes of this type with the
TYPE=SERVER parameter specified.
ANR0846I Job ID : Deleted ( objIdHi.objIdHi ) for System Action: The DELETE FILESPACE command is
node ( Node name ) fsId( File Space Id hl( ended and server processing continues.
Dir Name Part 1 ) ll( Dir Name Part 2 )
User Response: If this filespace must be deleted,
descr( Dir Description ).
Reissue the command with the TYPE parameter set to
Explanation: The indicated archive directory cleanup TYPE=SERVER. Please use caution when using the
job deleted a duplicate directory entry. Information TYPE=SERVER parameter as this can impact the
from the database about the duplicate entry is availability of data for the server that owns these files.
displayed, including the two part object identifier, node
name, file space identifier, two part directory name and
ANR0850E Command: Cannot Start process name
the description from the archive information.
Process.
System Action: The entry is deleted. Processing
Explanation: The indicated DELETE FILESPACE
continues.
process cannot be started on the server.
System Action: The DELETE FILESPACE command is
ended and server processing continues.
ANR0847I Job ID : Found directory ( objIdHi.objIdHi
User Response: This usually indicates that sufficient
) for node ( Node name ) filespace( File
server memory is not available on the server. Allocate
Space hl( Dir Name Part 1 ) ll( Dir Name
additional storage to the server. For details, issue HELP
Part 2 ) descr( Dir Description ).
MEMORY to display the information online or see
Explanation: The indicated archive directory cleanup “Appendix A. Allocating Additional Server Memory”.
job found a duplicate directory entry. Information from
the database about the duplicate entry is displayed,
ANR0851E Cannot start delete file space thread for
including the two part object identifier, node name, file
node node name.
space name, two part directory name and the
description from the archive information. The duplicate Explanation: The indicated DELETE FILESPACE
directory will be deleted if the FIX=YES parameter of process cannot be started on the server. Sufficient
the CLEAN ARCHDIR command is specified. Since memory on the server may not be available.
FIX=NO was specified or defaulted, the duplicate
directory is not removed. System Action: The DELETE FILESPACE command is
ended and server processing continues.
System Action: The entry is not deleted. Processing
continues. User Response: Allocate additional storage to the
User Response: None. information online or see “Appendix A. Allocating
ANR0848W Expiration failed to delete file type file
file name for node node name and ANR0852E Command: No matching file spaces
filespace filespace name - file will be found for node node name.
skipped.
Explanation: The server did not find any file spaces
Explanation: The expiration process was unable to for the node indicated matching the names specified in
delete the indicated file. The file will be skipped by the command.
expiration.
System Action: The server ends the command.
System Action: The expiration process continues.
User Response: Enter the command with file space
User Response: Re-try expiration to determine if the names that refer to defined file spaces for the specified
cause of the deletion failure was an intermittent node. Note that file space names are case sensitive.
problem or if it is a permanent problem. If after a Enter them by using exactly the same uppercase and

lowercase characters that match the file space name administrator can add log volumes using the DEFINE
defined on the server. Use the QUERY FILESPACE DBVOLUME command and can extend the size of the
command to determine which file spaces are defined database using the EXTEND DB command.
for a node on the server.
ANR0857E Data storage session failure, DELETE
ANR0853E Transaction failed in file space deletion, FILESPACE process aborted.
DELETE FILESPACE process aborted.
Explanation: The server encounters an error accessing
Explanation: A database transaction fails while the data storage during file space deletion processing.
server is deleting file space data.
System Action: The server ends the file space deletion
System Action: The server ends the file space deletion process.
process.
User Response: Examine the server messages issued prior to this message to determine the source of the
prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the
error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot
activity log and search for messages. If the error cannot be isolated and resolved, contact your service
be isolated and resolved, contact your service representative.
representative.
ANR0858E Inventory object search failure, DELETE
ANR0854E Inventory file space query failure, FILESPACE process aborted.
Explanation: The server encounters an error accessing
Explanation: The server encounters an error in the inventory database during file space deletion
querying the inventory database during a file space processing.
deletion process.
System Action: The server ends the file space deletion process.
process.
User Response: Examine the server messages issued prior to this message to determine the source of the
prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the
error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot
activity log and search for messages. If the error cannot be isolated and resolved, contact your service
be isolated and resolved, contact your service representative.
representative.
ANR0859E Data storage object erasure failure,
ANR0855E Server LOG space exhausted, DELETE DELETE FILESPACE process aborted.
FILESPACE process aborted.
Explanation: Insufficient server log space has been removing file copies from data storage during file space
encountered during file space deletion processing. deletion processing.
System Action: The server ends the file space deletion System Action: The server ends the file space deletion
process. process.
User Response: To increase the amount of log space User Response: Examine the server messages issued
available to the server, an authorized administrator can prior to this message to determine the source of the
add log volumes by using the DEFINE LOGVOLUME error. Issue the QUERY ACTLOG command to view the
command, and can extend the size of the log by using activity log and search for messages. If the error cannot
the EXTEND LOG command. be isolated and resolved, contact your service
representative.
ANR0856E Server database space exhausted,
Explanation: Insufficient server database space has
been encountered during file space deletion processing.
process.

ANR0860E Expiration process process ID terminated
administrator can add database volumes by using the
due to internal error: examined number of
DEFINE DBVOLUME command and can extend the
objects objects, deleting number of backup
size of the database using the EXTEND DB command.
objects backup objects, number of archive
objects archive objects, number of DB
backup volumes DB backup volumes, and ANR0864E Expiration processing suspended -
number of recovery plan files recovery plan insufficient LOG space.
files. error count errors were encountered.
Explanation: The server ends policy roll-off processing
Explanation: The server encounters an internal error because sufficient server log space is not available.
during file expiration processing. The number of files
examined and deleted prior to the error are reported. A System Action: The server ends policy roll-off
total error count is also displayed. processing and server operation continues.
System Action: The server ends the expiration User Response: To increase the amount of log space
process. available to the server, an authorized administrator can
add log volumes by using the DEFINE LOGVOLUME
User Response: Examine the server messages issued command and can extend the size of the log by using
prior to this message to determine the source of the the EXTEND LOG command.
be isolated and resolved, contact your service ANR0865E Expiration processing failed - internal
representative. server error.
Explanation: Server retry processing during policy
ANR0861E Transaction failed in expiration, roll-off fails.
inventory expiration aborted. System Action: The server ends policy roll-off
Explanation: The server encounters a database processing.
transaction failure during policy roll-off processing. User Response: Examine the server messages issued
System Action: The server ends roll-off processing. prior to this message to determine the source of the
User Response: Examine the server messages issued activity log and search for messages. If the server is out
prior to this message to determine the source of the of database space, issue the DEFINE DBVOLUME and
error. Issue the QUERY ACTLOG command to view the EXTEND DB commands to add volumes to the server
activity log and search for messages. If the error cannot database and extend the database size. If the server is
be isolated and resolved, contact your service out of log space, issue the DEFINE LOGVOLUME and
representative. EXTEND LOG commands to add volumes to the server
log and extend the log size. If the server is low on
memory, allocate additional storage to the server. For
ANR0862E Expiration processing suspended -
Explanation: The server ends policy roll-off processing Additional Server Memory”. If the error cannot be
because sufficient server memory is not available. isolated and resolved, contact your service
representative.
System Action: The server ends policy roll-off
processing and server operation continues.
ANR0866E Expiration processing retries failed - no
success after maximum retries retries.
information online or see “Appendix A. Allocating Explanation: Server policy roll-off processing ends
Additional Server Memory”. because retry processing has not been successful in
expiring client file copies from the server database.
ANR0863E Expiration processing suspended - System Action: The server ends policy roll-off
insufficient DB space. processing and server operation continues.
Explanation: The server ends policy roll-off processing User Response: Examine the server messages issued
because sufficient server database space is not prior to this message to determine the source of the
available. error. Issue the QUERY ACTLOG command to view the
activity log and search for messages. If the server is out
System Action: The server ends policy roll-off
of database space, issue the DEFINE DBVOLUME and
EXTEND DB commands to add volumes to the server
User Response: To increase the amount of database database and extend the database size. If the server is
out of log space, issue the DEFINE LOGVOLUME and

EXTEND LOG commands to add volumes to the server
ANR0870E Cannot find node name for node node
log and extend the log size. If the server is low on
ID.
memory, allocate additional storage to the server. For
details, issue HELP MEMORY to display the Explanation: Policy roll-off processing on the server
information online or see “Appendix A. Allocating encounters a database error in obtaining information
Additional Server Memory”. If the error cannot be for a client node.
isolated and resolved, contact your service
System Action: The server ends roll-off processing
representative.
ANR0867E Unable to open policy domain for node
node name during expiration processing.
Explanation: Policy roll-off processing on the server activity log and search for messages. If the error cannot
encounters an error while obtaining policy information be isolated and resolved, contact your service
related to the specified node. representative.
and server operation continues. ANR0871E Cannot find file space name for node
node ID, file space file space ID.
prior to this message to determine the source of the Explanation: Policy roll-off processing on the server
error. Issue the QUERY ACTLOG command to view the encounters a database error in obtaining information
activity log and search for messages. If the error cannot for a client node.
representative.
ANR0868E Cannot find management class name for
ID management class ID.
Explanation: Policy roll-off processing on the server activity log and search for messages. If the error cannot
encounters an error while obtaining policy information. be isolated and resolved, contact your service
representative.
ANR0872E Grace Period retention for domain
domain name could not be obtained.
error. Issue the QUERY ACTLOG command to view the Explanation: Policy roll-off processing on the server
activity log and search for messages. If the error cannot encounters a database error in obtaining GRACE
be isolated and resolved, contact your service PERIOD values for the specified policy domain.
representative.
ANR0869E Cannot find policy domain for node
node ID.
Explanation: Policy roll-off processing on the server error. Issue the QUERY ACTLOG command to view the
encounters an error while obtaining policy information activity log and search for messages. If the error cannot
related to the specified node. be isolated and resolved, contact your service
representative.
ANR0873E Invalid copy type encountered in
expiring files: copytype ID
error. Issue the QUERY ACTLOG command to view the Explanation: Policy roll-off processing on the server
activity log and search for messages. If the error cannot encounters a database error in obtaining copy group
be isolated and resolved, contact your service information.
representative.

representative. error. Issue the QUERY ACTLOG command to view the
ANR0874E Backup object object.ID not found during
representative.
inventory processing.
Explanation: Inventory processing on the server
ANR0878E Entry for backup object object.ID not
encounters a database error in obtaining backup
found.
information in data storage.
Explanation: Policy roll-off processing on the server
System Action: The server ends roll-off processing, or
encounters a database error in accessing inventory
client session(s) and server operation continues.
information.
ANR0875E Archive object object.ID not found
representative.
during expiration processing.
ANR0879E Error opening inventory file space
encounters a database error in obtaining archive
query.
information in data storage.
information.
ANR0876E Data storage erasure failed during
representative.
expiration processing.
ANR0880E Filespace command: No matching file
encounters a database error while deleting information
spaces.
from data storage.
Explanation: The server did not find any file space
names matching the specifications entered in the
filespace command.
error. Issue the QUERY ACTLOG command to view the User Response: Use the QUERY FILESPACE
activity log and search for messages. If the error cannot command to determine which file spaces are defined
be isolated and resolved, contact your service on the server. Note, that file space names are case
representative. sensitive. Reissue the file space command and specify
the proper file space name (in proper case).
ANR0877E Copy type not backup for object
object.ID. ANR0881E Policy Error : the GRACE PERIOD
archive retention value could not be
obtained for domain domain ID during
client inventory processing.
information.
Explanation: The server encounters an internal error
in accessing policy information.

System Action: The operation is ended and server imported under the name new management class name.
operation continues. 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
ANR0882E Policy Error: Unable to open policy processing is then able to import file data by using the
domain for node node name during client renamed management class.
inventory query processing.
System Action: Import processing for the command
Explanation: The server encounters an internal error continues.
in accessing policy information.
User Response: None. However, an administrator may
System Action: The client operation is ended and want to examine the policy definitions for new
server operation continues. management class name so they are aware of the
management classes that may be used if the policy set
User Response: Contact your service representative. containing this management class is activated.
ANR0883E Cannot obtain node name for node node ANR0886E Management class class name in domain
ID. domain name used by node node name in
Explanation: The server encounters an internal error file space filespace name has no BACKUP
in accessing client node information. copy group with id copy group id;
Expiration will not be performed for
System Action: The operation is ended and server files from this node and filespace that
operation continues. are bound to this management class and
User Response: Contact your service representative. copy group id.
ANR0884E Error code during deletion of sorting server finds a client file copy with a management class
information for number objects. or a backup copy group that no longer exists.
Explanation: A background server process System Action: The server skips the files in error.
encountered an internal error after deleting sorting User Response: For programming support, contact
information for number files from the server database. your service representative.
This process is started during initialization to remove
any sorting information which is left over from
previous export operations. ANR0887E Management class class name in domain
domain name used by node node name in
System Action: The backup or archive objects were file space filespace name has no
not deleted. Only the information used to sort these ARCHIVE copy group with id copy group
objects during the previous export operation was id; Expiration will not be performed for
deleted. The background process was terminated before files from this node and filespace that
all sorting information had been deleted. The system are bound to this management class and
will not perform further export processing of file data copy group id.
until this problem has been resolved.
User Response: Examine the server messages issued server finds a client file copy with a management class
prior to this message to determine the source of the or an archive copy group that no longer exists.
activity log and search for messages. Then restart the System Action: The server skips the files in error.
server. If the error cannot be isolated and resolved, User Response: For programming support, contact
contact your service representative. your service representative.
ANR0885I Import command: Processing management ANR0888E SQL commands cannot be issued from
class management class name for domain the server console.
domain name and policy set policy set
name as management class new Explanation: An SQL command was issued from the
management class name. server console. SQL commands cannot be issued from
the server console because they may require a long
Explanation: The background import process to time complete and the server console should be
service the command import command is currently available to control other server functions.
processing the policy information for management class
management class name in domain domain name and System Action: The server ignores the command and
policy set policy set name. The management class is continues processing.

User Response: Issue the SQL command from an
ANR0893I Are you sure that you want to accept the
administrative client.
current system date as valid ?
Explanation: This message is displayed when the
ANR0889E The server is not licensed for Central
ACCEPT DATE command has been issued to confirm
Administration functions. This includes
that you want to accept the date on the system as
the ability to issue SQL commands.
valid.
Explanation: An SQL command was issued but the
System Action: The command waits for you to
server is not licensed to support Central Administrative
confirm the action.
functions, including SQL query support.
User Response: Specify Yes if you want to accept the
System Action: The server ignores the command and
system date as valid, or No if you do nt want to
continues processing.
execute the command.
User Response: If you have purchased the Central
Administration license, use the REGISTER LICENSE
ANR0894I Current system has been accepted as
command to enable the license on the server. If you
valid.
have not purchased the license and wish to do so,
contact your service representative. Explanation: This messages is displayed when the
ACCEPT DATE command has been issued and the date
has been accepted as valid by the server.
optionset optionset name. System Action: The current system date is accepted as
valid by the server
process to service the command export/import command User Response: None.
is currently processing optionset definition information.
System Action: Export or import processing for the ANR0895E Command: Cannot Start process name
command continues. Process.
User Response: None. Explanation: The indicated process cannot be started
on the server.
ANR0891I Export/import command: Copied number System Action: The specified command is ended and
optionset definitions. server processing continues.
Explanation: The background export or import User Response: This usually indicates that sufficient
process to service the command export/import command server memory is not available on the server. Allocate
copies number client optionset definitions from the additional storage to the server. For details, issue HELP
server database to export media or from export media MEMORY to display the information online or see
into the server database. Data is not moved if “Appendix A. Allocating Additional Server Memory”.
command.
ANR0900I Processing options file filespec.
Explanation: At server initialization, the server is
reading the server options file whose name is shown in
User Response: None. the message.
System Action: The server reads and processes the
ANR0892I Export command: No matching optionsets options in this file.
found for exporting.
find any client optionsets for export command.
ANR0901W Invalid option statement found in file
System Action: The export process continues and no filespec.
optionsets from the server.
Explanation: While processing the server options file
User Response: None. named, the server has encountered an invalid
statement. The invalid statement type is shown in the
message. The lines following this message provide
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
ANR0909E Insufficient memory to process options
correct the error and restart the server.
file.
Explanation: At server initialization, the server is
ANR0902W Unsupported keyword found in file
unable to process the server options file due to
filespec.
Explanation: While processing the server options file
System Action: Server initialization ends.
named, the server has encountered an invalid keyword
on an option statement. The lines following this User Response: Restart the server with more memory
message provide more information. available. Refer to the Administrator’s Guide for your
particular platform.
System Action: The server ignores the option
statement in error. Server initialization continues. The
default value is used for any missing or ignored ANR0910W Archive entries for nodeName are already
options. converted.
User Response: Ignore the error, or use a text editor to Explanation: Archive entries for nodeName have
correct the error and restart the server. already been converted to the description tables. They
will not be converted again.
ANR0903W Excessive option statement found in file System Action: Server operation continues.
filespec.
User Response: To force the reconversion of the
Explanation: While processing the specified server archive entries for nodeName, use the FORCE=Yes
options file, the server has encountered more of the option to the CONVERT ARCHIVE command.
named statement type than can be processed.
System Action: The server ignores the extra statement. ANR0911I Conversion for node name completed
Server initialization continues. (result). The description tables have
object count directories and files, object set
count object sets. Conversion inserted
object count directories and files, and
object set count object sets.
ANR0904W Duplicate option statement found in file
Explanation: CONVERT ARCHIVE was issued for the
filespec.
specified node. If processing completed successfully, the
Explanation: While processing the server options file node can now query for archive objects specifying a
named, the server has encountered a duplicate non-wildcarded description.
statement of the type shown.
System Action: The server ignores the duplicate
statement. Server initialization continues.
ANR0914E Diagnostic(ID): a request failed because
object (object name), size (size), exceeds
the maximum size of maximum size.
ANR0905W Options file filespec not found.
Explanation: The size of the specified object exceeds
Explanation: At server initialization, the server is the maximum size defined for that object. The server
unable to locate the server options file named. cannot handle the new object.
System Action: The server uses the default values for System Action: The activity that generated this error
all options. Server initialization continues. fails.
User Response: If the default values are acceptable, User Response: Determine why the new object’s
ignore the error. Otherwise, move a valid server length exceeds the maximum specified for the object.
options file to the proper location, rename a valid Reduce the length of the object.
options file to the proper name, or use a text editor to
build the proper server options file, and then restart the
ANR0915E Unable to open language language name
server.
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 User Response: If tracing is desired, use the TRACE
specified in the LANGUAGE option of the server ENABLE and TRACE START commands to activate
options file. If a change is made to the options file, server tracing.
restart the server to activate changes.
ANR0924E Tracing is already active to file file spec.
ANR0916I Product Name distributed by Company is
Explanation: A TRACE BEGIN command has been
now ready for use.
entered, but tracing is already active to the file named.
Explanation: The server has completed startup
System Action: The command is ignored.
processing and is now ready for use.
User Response: If the current trace output file is
acceptable, no action is required. Otherwise use the
User Response: None. TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
name (client platform) - in domain domain ANR0925E Tracing is already active to standard
name failed because of policy length. output.
Explanation: The client cannot handle very long Explanation: A TRACE BEGIN command has been
policies. entered, but tracing is already active to the standard
output destination (usually the server console).
System Action: The client operation is ended and
server operation continues. System Action: The command is ignored.
User Response: Upgrade the client to the latest level, User Response: If the current trace output destination
or activate a policy set with fewer management classes. is acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
ANR0920I Tracing is now active to standard
output.
ANR0926E Missing or invalid TRACE command
Explanation: In response to a TRACE START
parameter.
command, server trace records are being written to the
standard output destination (usually the server Explanation: The TRACE command issued contains
console). an invalid parameter, or is missing a required
parameter.
User Response: Reissue the command with the proper
parameters.
ANR0921I Tracing is now active to file file spec.
Explanation: In response to a TRACE START
ANR0927E Unknown trace class keyword - class.
command, server trace records are being written to the
file named. Explanation: A TRACE ENABLE command has been
entered which specifies an unknown trace class.
User Response: Reissue the TRACE command with
the correct class.
ANR0922I Trace ended.
Explanation: In response to a TRACE END command,
ANR0928E Unable to open trace file file spec for
server trace records are no longer being written.
appending.
Explanation: A TRACE BEGIN command specifies an
User Response: None. output file, but the server cannot write to that file.
ANR0923E Tracing is inactive.
User Response: Check the file for proper access
Explanation: A TRACE END command has been permissions, or reissue the TRACE command
entered, but tracing is not active. specifying a different output file.

ANR0929E Insufficient memory to activate tracing. ANR0945W DiagnosticID: Transaction transaction ID

was aborted for process process ID.
Explanation: A TRACE BEGIN command has been
entered, but the server has insufficient memory Explanation: An error is detected during transaction
available to activate tracing. commit for the specified process. This message should
be preceded by other messages that give additional
information about the failed transaction.
User Response: If tracing is required, make more
memory available to the server then restart the server.
fails.
User Response: Check for additional messages and
ANR0940I Cancel request accepted for process
eliminate the condition that caused the failed
process ID.
transaction. If the error cannot be isolated and resolved,
Explanation: A CANCEL PROCESS command has contact your service representative.
been entered for the specified process.
System Action: None. 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
ANR0941I Command: Cancel for process process ID volume in the device class shown.
is already pending.
System Action: The process waits for the mount point.
Explanation: A CANCEL PROCESS command has
been entered for the specified process, but a cancel is User Response: Respond to any mount requests.
already pending for that process.
System Action: The server ignores the command. ANR0961I Process process ID waiting for multiple
mount points in device class device class
User Response: None. name.
ANR0942E Command: Process process ID cannot be begun to wait for multiple mount points that can be
found. used for a volume in the device class shown.
Explanation: A CANCEL PROCESS command has System Action: The process waits for the mount
been entered for the specified process, but the process points.
is not active. Either the process has already ended or
the wrong process number has been entered. User Response: Respond to any mount requests.
System Action: The server ignores the command.
ANR0962I Process process ID waiting for mount
User Response: If the wrong process number has been points in device classes device class name
entered, reissue the command with the correct process and device class name.
number.
begun to wait for mount points that can be used for a
ANR0943E Command: Process process ID could not be volume in the two device classes shown.
canceled.
System Action: The process waits for the mount
Explanation: A CANCEL PROCESS command has points.
been entered for the specified process, but the process
specified is an automatic process, such as migration or User Response: Respond to any mount requests.
reclamation, that cannot be canceled.
System Action: The server ignores the command. ANR0963I Process process ID waiting for mount of
input volume volume name.
begun to wait for the mount of the input volume
ANR0944E Command: No active processes found. shown.
Explanation: A QUERY PROCESS command has been System Action: The process waits for the mount.
entered, and no processes are active.
User Response: Respond to any mount requests.

ANR0964I Process process ID waiting for mount of ANR0980E The server database must be audited
output volume volume name. with FIX=YES before the server can be
started.
begun to wait for the mount of the output volume Explanation: The server has been restarted after a
shown. DSMSERV LOADDB command processed a database
image that was known to have inconsistencies. In order
System Action: The process waits for the mount.
to bring the database back to a consistent state, you
User Response: Respond to any mount requests. must run the AUDITDB command.
System Action: Server initialization stops.
ANR0965I Process process ID waiting for mount of
User Response: Issue the DSMSERV AUDITDB
scratch volume.
FIX=YES command. For complete details on this
Explanation: The process whose ID is shown has command, refer to the Administrator’s Reference.
begun to wait for the mount of a scratch volume.
System Action: The process waits for the mount. ANR0981E The server database must be restored
before the server can be started.
Explanation: The server has been restarted after an
incomplete RESTORE DB. In order to start the server,
ANR0966I Process process ID waiting for access to you must restore to the database to a consistent state
input volume volume name. using the DSMSERV RESTORE DB command.
Explanation: The process whose ID is shown has System Action: Server initialization stops.
begun to wait for availability of the input volume
shown. User Response: Issue the DSMSERV RESTORE DB
command. For complete details on this command, refer
System Action: The process waits for the volume to to the Administrator’s Reference.
become available.
User Response: None. ANR0982E The server database must be initialized
before the database can be loaded.
ANR0967I Process process ID waiting for access to Explanation: The server database must be initialized
output volume volume name. before it can be loaded with the LOADDB parameter,
Explanation: The process whose ID is shown has by issuing the DSMSERV LOADFORMAT command.
begun to wait for availability of the output volume The server database is not currently in the initialized
shown. state.
System Action: The process waits for the volume to System Action: Server LOADDB processing stops.
become available. User Response: Issue the DSMSERV LOADFORMAT
User Response: None. command. For complete details on this command, refer
to the Administrator’s Reference.
ANR0969E The server database must be formatted

and loaded or restored before the server ANR0983W The server database was recorded by a
can be started. down-level version of the server
program. The UPGRADEDB parameter
Explanation: The server has been restarted after is required to start the server and
toleration of a zero bit mismatch error. In order to start automatically upgrade the database
the server, you must recover the database with a contents to the current server version.
process that includes a DSMSERV FORMAT. Either the Please refer to installation instructions
volumes must be formatted then a DSMSERV for precautionary backup procedures
RESTORE DB performed, or a DSMSERV UNLOADDB prior to doing this.
followed by the formatting, then a DSMSERV
LOADDB. Do not use DSMSERV DUMPDB on the data Explanation: At server startup, the server has
base for this recovery. discovered that the database information was written
by an earlier version of the server program and is not
System Action: Server initialization stops. compatible with this version. To automatically upgrade
User Response: Perform one of the data base recovery the server database to this version of the server
actions. program, the UPGRADEDB parameter must be
specified when starting the server.
System Action: The server ends.

User Response: Refer to installation instructions for
ANR0987I Process process ID for process name
specific information on precautionary measures that
running in the process state processed
you may want to take to back up the database prior to
items processed items with a completion
upgrading it to the current server level. After you have
state of completion state at process start
taken these measures, start the server and specify the
time.
UPGRADEDB parameter. This parameter only needs to
be specified once to start the server, and should NOT Explanation: The process whose ID is shown that was
be included in any automated programs that start the running for the process indicated by the process name
server. running in the indicated state has completed processing
the stated number of items with the completion state
indicated.
ANR0984I Process process ID for process name started
in the process state at process start time. System Action: None.
Explanation: The process whose ID is shown has been User Response: If the completion state was SUCCESS
started for the process indicated by the process name then no action is necessary. However, if the completion
running in the indicated state. state is FAILURE then the user should review the
activity log and/or event log to try to determine the
cause of the failure.
ANR0985I Process process ID for process name running in the process state processed
running in the process state completed bytes processed bytes with a completion
with completion state completion state at state of completion state at process start
process start time. time.
Explanation: The process whose ID is shown that was Explanation: The process whose ID is shown that was
running for the process indicated by the process name running for the process indicated by the process name
running in the indicated state has completed with the running in the indicated state has completed processing
completion state indicated. the stated number of bytes with the completion state
indicated.
User Response: If the completion state was SUCCESS
then no action is necessary. However, if the completion User Response: If the completion state was SUCCESS
state is FAILURE then the user should review the then no action is necessary. However, if the completion
activity log and/or event log to try to determine the state is FAILURE then the user should review the
cause of the failure. activity log and/or event log to try to determine the
cause of the failure.

running in the process state processed ANR0989E The server database must be loaded or
items processed items for a total of bytes restored before the server can be started.
processed bytes with a completion state
Explanation: The server is restarted after the
of completion state at process start time.
LOADFORMAT command is run. To start the server,
Explanation: The process whose ID is shown that was you must load the database by issuing the DSMSERV
running for the process indicated by the process name LOADDB or the DSMSERV RESTORE DB command.
running in the indicated state has completed processing
System Action: Server initialization stops.
the stated number of items and total number of bytes
with the completion state indicated. User Response: Issue the DSMSERV LOADDB or
DSMSERV RESTORE DB command. For complete
details on these commands, refer to the Administrator’s
User Response: If the completion state was SUCCESS Reference.
then no action is necessary. However, if the completion
state is FAILURE then the user should review the
ANR0990I Server restart-recovery in progress.
activity log and/or event log to try to determine the
cause of the failure. 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.
System Action: Server initialization continues.

ANR0996W The information on disk was recorded
by a down-level version of the server
ANR0991I server shutdown complete. program; re-installation is required to
use this version.
Explanation: In response to a HALT command, the
server or storage agent has completed its termination Explanation: At server startup, the server has
processing. discovered that the disk information was written by an
earlier version of the server program and is not
System Action: The server or storage agent ends. compatible with this version.
User Response: None. System Action: The server ends.
User Response: Install this version of the server to
ANR0992I Server installation complete. bring the information up to the level of the program
Explanation: The server installation procedure has being used.
completed successfully. The server is now available for
normal operation. ANR1000I Migration process process ID started for
System Action: Server completes installation storage pool storage pool name.
processing. Explanation: Because the high migration threshold for
User Response: None. the storage pool shown has been exceeded, a process
has been started to migrate files from the storage pool.
ANR0993I Server initialization complete. System Action: Data is moved from this storage pool
to the next (target) pool.
Explanation: The server has been restarted after a halt
or system failure. It is now ready to resume normal User Response: None.
operation.
System Action: Server completes initialization. ANR1001I 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
ANR0994W This server has not been properly low migration threshold for the storage pool has been
installed. reached or because there are no more nodes with files
Explanation: The server was started for normal to be migrated.
operation, but had not yet been installed. System Action: None.
System Action: The server ends. User Response: None.
User Response: Install the server properly before
starting it. ANR1002I Migration for storage pool storage pool
name will be retried in number of seconds
ANR0995W This version of the server program is seconds.
down-level with respect to the Explanation: Because of a problem encountered
information recorded on disk; a newer attempting migration for the named storage pool,
version of the program should be used. migration is delayed but will be retried after the time
Explanation: At server startup, the server has period shown.
discovered that the disk information was written by a System Action: The server waits for the specified
later version of the server program. This version of the period and then retries migration for the storage pool.
server program should not be used. This delay applies to a single migration process. After a
System Action: The server ends. number of unsuccessful retries, the server will
automatically cancel the process. If other migration
User Response: Start a version of the server program processes are executing for the named storage pool,
that is at the same level as the prior server program these processes will continue migration.
used.
User Response: If possible, correct the condition that
has caused delayed migration.

ANR1003I Migration retry delay ended; checking ANR1022W Migration process process ID terminated
migration status for storage pool storage for storage pool storage pool name -
pool name. excessive read errors encountered.
Explanation: Because migration for the indicated Explanation: During migration for the indicated
storage pool had been delayed due to a problem, the storage pool, read errors occur that prevented the
system waited before retrying. The retry wait period migration from continuing.
has ended, and the system will now retry migration.
System Action: The indicated migration process ends.
System Action: Migration processing for the storage The server waits for the retry period to expire and then
pool resumes. tries the migration again. If other migration processes
are executing for the named storage pool, these
processes will continue migration.
User Response: If possible, correct the cause of the
ANR1004I Server formatting complete, database
read errors.
ready for loading.
Explanation: The server formatting procedure has
ANR1023W Migration process process ID terminated
completed successfully. The server is ready to be
for storage pool storage pool name -
loaded by issuing the DSMSERV LOADDB or the
excessive write errors encountered.
DSMSERV RESTORE DB command.
Explanation: During migration for the indicated
System Action: Server completes formatting
storage pool, write errors occur that prevent the
processing.
migration from continuing.
User Response: The DSMSERV LOADDB or the
DSMSERV RESTORE DB command is required to load
The server waits for the retry period to expire and then
the database before the server will be ready for use. For
tries the migration again. If other migration processes
complete details on these commands, refer to the
Administrator’s Reference.
write errors.
process canceled.
for storage pool storage pool name - data
storage pool, a process performing the migration has
transfer interrupted.
been canceled.
System Action: The migration process is terminated. If
storage pool, a data transfer operation was interrupted
other migration processes are executing for the named
and could not be continued.
storage pool, these processes will continue migration.
ANR1021W Migration process process ID terminated are executing for the named storage pool, these
for storage pool storage pool name - processes will continue migration.
storage media inaccessible.
Explanation: During migration for the indicated interruption.
storage pool, a required volume could not be mounted.
System Action: The indicated migration process ends. ANR1025W Migration process process ID terminated
The server waits for the retry period to expire and then for storage pool storage pool name -
tries the migration again. If other migration processes insufficient space in subordinate storage
are executing for the named storage pool, these pool.
User Response: None. storage pool, the server cannot move the data from the
storage pool, because there is not enough space on the
next storage pool to hold it.
tries the migration again.

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

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

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

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

System Action: The indicated migration process ends. period and then retries space reclamation for the
The server waits for the retry period to expire and then storage pool.
has stopped reclamation.
ANR1043I Space reclamation retry delay ended;
checking volume reclamation status for
transaction.
Explanation: Because space reclamation for the
ANR1034W Files stored on volume volume name
indicated storage pool had been stopped due to a
cannot be migrated - volume is offline
problem, the system waited before retrying. The retry
or access mode is ″unavailable″ or
wait period has ended, and the system can now retry
″destroyed″.
space reclamation.
Explanation: During migration, files on the indicated
System Action: Reclamation for the pool begins.
volume cannot be migrated either because the volume
has been varied offline or because of the volume’s User Response: None.
access mode.
System Action: The server continues migration ANR1044I Removable volume volume name is
processing, but skips files stored on the indicated required for space reclamation.
volume.
Explanation: During space reclamation processing, the
User Response: If necessary, use the VARY ON or server determines that a removable volume is required
UPDATE VOLUME command for this volume. in order to complete processing.
System Action: The server attempts to mount the
ANR1040I Space reclamation started for volume removable volume.
volume name, storage pool storage pool
name (process number process ID). User Response: Respond to any mount request for the
indicated volume.
Explanation: The percentage of reclaimable space on
the volume shown has reached the reclaim percentage
specified for the storage group; as a result, data from ANR1060W Error initiating space reclamation for
the volume is moved to another volume so that the storage pool storage pool name - lock
volume can be reclaimed. conflict.
System Action: The server starts volume space Explanation: While attempting to initiate space
reclamation. 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
ANR1041I Space reclamation ended for volume reclamation again.
volume name.
Explanation: Space reclamation for the volume named reclamation.
is complete.
System Action: None. ANR1061W Error initiating space reclamation for
storage pool storage pool name - sufficient
Explanation: During an attempt to initiate space
ANR1042I Space reclamation for storage pool
reclamation for the indicated storage pool, there is not
storage pool name will be retried in
enough server memory available.
number of seconds seconds.
Explanation: Because of a problem encountered
attempting space reclamation for the named storage
reclamation again.
pool, reclamation stops but will be retried after the
time period shown. After a number of unsuccessful User Response: If necessary, make more memory
retries, the process will be automatically cancelled. available to the server.
System Action: The system waits for the specified

ANR1062W Error initiating space reclamation for ANR1066I Restore of NAS node nodename, file
storage pool storage pool name - internal system file system, started as process
server error detected. process ID by administrator administrator.
A full image plus a differential image
Explanation: During an attempt to initiate space
for this file system will be restored to
reclamation for the indicated storage pool, an internal
destination destination.
server error is encountered.
Explanation: A restore is started for the indicated file
system of a NAS node. The operation is initiated by the
will wait for the retry period to expire and then tries
administrator shown. The restore will be performed
the reclamation again.
using a full image plus a differential image of this file
User Response: Contact your service representative. system. The file system will be restored to the indicated
destination.
ANR1063I Full backup of NAS node nodename, file System Action: The indicated process is started.
system file system, started as process
process ID by administrator administrator.
Explanation: A full backup is started for the indicated
ANR1067I Operation process process ID completed.
file system of a NAS node. The operation is initiated by
the administrator shown. Explanation: The indicated operation completed.
System Action: The indicated process is started. System Action: The indicated process ends.
ANR1064I Differential backup of NAS node ANR1068W Operation process process ID terminated -
nodename, file system file system, started process cancelled.
as process process ID by administrator
Explanation: During the indicated operation, a
administrator.
background process was cancelled.
Explanation: A differential backup is started for the
System Action: The indicated process ends.
indicated file system of a NAS node. Only files that
have changed since the last full backup will be User Response: None.
processed. The operation is initiated by the
administrator shown.
ANR1069E Operation process process ID terminated -
System Action: The indicated process is started. insufficient number of mount points
available for removable media.
Explanation: During the indicated operation, the
server could not allocate sufficient mount points for the
ANR1065I Restore of NAS node nodename, file
volumes required.
system file system, started as process
process ID by administrator administrator. System Action: The indicated process ends.
A full image for this file system will be
restored to destination destination. User Response: If necessary, make more mount points
available.
Explanation: A 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 ANR1070E Operation process process ID terminated -
using a full image of this file system. The file system write errors encountered.
will be restored to the indicated destination. Explanation: During the indicated operation, write
System Action: The indicated process is started. errors prevent the operation from continuing.
User Response: None. System Action: The indicated process ends.

errors and restart the operation.

available to the server, and then restart the operation.
read errors encountered.
Explanation: During the indicated operation, read
errors prevent the operation from continuing.
transaction aborted.
User Response: If possible, correct the cause of the server detected an error while attempting to commit a
errors and restart the operation. transaction. This message should be preceded by other
messages that give additional information about the
failed transaction.
insufficient space in destination storage System Action: The indicated process ends.
pool.
Explanation: During the indicated operation, there is eliminate the condition that caused the failed
not enough space available in the destination storage transaction.
pool.
System Action: The indicated process ends. ANR1078E Operation process process ID terminated -
User Response: Make more space available in the
storage pool and restart the operation. Explanation: During the indicated operation, the
server encounters an internal error.
ANR1073E Operation process process ID terminated - System Action: The indicated process ends.
available.
ANR1079I Server-free backup of node nodename,
server runs out of recovery log space.
file system file system, started as process
System Action: The indicated process ends. process ID by administrator administrator.
User Response: If necessary, make more server Explanation: The administrator initiates a server-free
recovery log space available. backup of the node’s file system.
System Action: The indicated process is started.
available.
ANR1080W Space reclamation terminated for
volume volume name - process canceled.
server runs out of database space.
Explanation: During space reclamation for the
indicated volume, the process performing the
User Response: If necessary, make more server reclamation has been canceled.
ANR1075E Operation process process ID terminated - reclamation again.
lock conflict.
server needs to obtain a lock that is not available.
System Action: The indicated process ends. volume volume name - storage media
inaccessible.
User Response: Restart the operation.
indicated volume, a required volume cannot be
mounted.
Explanation: During the indicated operation, not
enough server memory is available.
reclamation again.

ANR1082W Space reclamation terminated for ANR1086W Space reclamation terminated for
volume volume name - insufficient volume volume name - insufficient space
number of mount points available for in storage pool.
removable media.
Explanation: During space reclamation for the indicated volume, the server determines that data
indicated volume, the server could not allocate cannot be moved from the volume due to insufficient
sufficient mount points for the volumes required. space on other volumes in the storage pool.
System Action: Space reclamation stops. The server System Action: Space reclamation stops. The server
waits for the retry period to expire and then tries the waits for the retry period to expire and then tries the
reclamation again. reclamation again.
User Response: If necessary, make more mount points User Response: Make more space available on other
available. volumes in the storage pool.
volume volume name - excessive read volume volume name - sufficient recovery
errors encountered. log space is not available.
Explanation: During space reclamation for the Explanation: During space reclamation for the
indicated volume, read errors occur that prevent indicated volume, the server runs out of recovery log
reclamation from continuing. space.
User Response: If possible, determine and correct the User Response: If necessary, make more server
cause of the read errors. recovery log space available.
volume volume name - excessive write volume volume name - sufficient database
errors encountered. space is not available.
Explanation: During space reclamation for the Explanation: During space reclamation for the
indicated volume, write errors occur that prevent indicated volume, the server runs out of database
reclamation from continuing. space.
User Response: If possible, determine and correct the User Response: If necessary, make more server
cause of the write errors. database space available.
volume volume name - data transfer volume volume name - lock conflict.
interrupted.
Explanation: During space reclamation for the indicated volume, the server needed to obtain a lock
indicated volume, a data transfer operation has been that is not available.
interrupted and cannot be continued.
System Action: Space reclamation stops. The server waits for the retry period to expire and then tries the
waits for the retry period to expire and then tries the reclamation again.
reclamation again.
User Response: If possible, determine and correct the reclamation.
cause of the interruption.

ANR1090W Space reclamation terminated for ANR1094E Invalid destination storage pool storage
volume volume name - thread resource pool name specified for storage of an
not available. object using data mover data mover.
Explanation: During space reclamation for the Explanation: While attempting to store an object using
indicated volume, the server cannot start a thread for the indicated data mover, the server determined that
the reclamation process. 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.
reclamation again.
This storage pool could be invalid for any of the
following reasons:
reclamation. If the error persists, it may indicate a
shortage of server memory. 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
volume volume name - sufficient memory
is not available. 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
indicated volume, there was not enough server
memory available. v The data format of the storage pool does not match
the data format of the data mover
waits for the retry period to expire and then tries the System Action: The operation fails.
reclamation again. User Response: This message usually indicates a
User Response: If necessary, make more memory configuration problem with either the storage pool or
available to the server. the policy. Ensure that the destination storage pool has
appropriate attributes, including data format, for this
operation. Check the copy group of the assigned
ANR1092W Space reclamation terminated for management class. If the destination is incorrect, either
volume volume name - internal server assign a new management class, or change the
error detected. destination in the copy group and activate the changed
Explanation: During space reclamation for the policy. Also, consider whether you must define a new
indicated volume, the server encounters an internal storage pool or data mover.
error.
System Action: Space reclamation stops. The server ANR1095E Data mover operation for node node
waits for the retry period to expire and then tries the name and file space filespace name cannot
reclamation again. be started - an operation involving this
node and file space is already in
User Response: Contact your service representative. progress.
Explanation: A request has been made to use a data
ANR1093W Space reclamation terminated for mover to perform an operation involving the indicated
volume volume name - transaction node and file space. The indicated file space was either
aborted. 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
indicated volume, the server detected an error while
space is already in progress; the indicated file space is
attempting to commit a transaction.
either the source for a currently running backup
System Action: Space reclamation stops. The server operation or is the destination for a currently running
waits for the retry period to expire and then tries the restore operation. To avoid possible conflicts, the new
reclamation again. operation is not performed.
User Response: Check for additional messages and System Action: The operation fails.
User Response: Allow the current operation to
transaction.
complete before starting a new operation for this node
and file space.

storage media inaccessible. User Response: None.
Explanation: During the indicated operation, a
required volume cannot be mounted. ANR1102I Removable volume volume name is
required for migration.
Explanation: During migration processing, the server
User Response: If possible, correct the problem and
determines that a removable volume is required in
restart the operation.
order to complete processing.
removable volume.
data transfer interrupted.
User Response: Respond to any mount request for the
Explanation: During the indicated operation, a data
indicated volume.
transfer operation is interrupted and cannot be
continued.
NDMP session errors encountered.
User Response: If possible, correct the problem and
restart the operation.
NDMP session with the NAS file server reported errors
which prevent the operation from continuing.
file deleted from data storage during
retrieval. User Response: Check the NDMP logs for the NAS
file server and, if possible, correct the cause of the
Explanation: During the indicated operation, a file
errors and restart the operation.
was deleted from data storage during retrieval.
ANR1115W Error initiating migration for storage
User Response: None. pool storage pool name - lock conflict.
Explanation: While trying to start migration for the
ANR1099E Operation process process ID terminated - indicated storage pool, the server needs to obtain a lock
thread resource not available. that is not available.
Explanation: During the indicated operation, the System Action: Migration stops. The server waits for
server cannot start a thread. the retry period to expire and then tries the migration
again.
User Response: The problem may indicate a shortage
migration.
of memory. If necessary, make more memory available
to the server, and then restart the operation.
pool storage pool name - sufficient
ANR1100I Migration started for volume volume
name, storage pool storage pool name
(process number process ID). Explanation: While trying to start migration for the
indicated storage pool, there is not enough server
Explanation: Because the high migration threshold for
memory available.
the indicated storage pool has been exceeded,
migration of files from the volume shown begins. System Action: Migration stops. The server waits for
the retry period to expire and then tries the migration
System Action: The system moves the data from this
again.
volume to the next (target) pool.
ANR1101I 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.

read errors.
pool storage pool name - internal server
error detected.
ANR1124W Migration terminated for volume volume
Explanation: While trying to start migration for the
name - excessive write errors
indicated storage pool, the server encounters an
encountered.
internal error.
System Action: Migration stops. The server waits for
volume, write errors occurred that prevent the
migration from continuing.
again.
again.
name - process canceled.
write errors.
volume, the process performing the migration has been
canceled.
name - data transfer interrupted.
System Action: The migration process is terminated. If
other migration processes are executing for the named
volume a data transfer operation was interrupted and
storage pool, these processes will continue migration.
could not be continued.
ANR1121W Migration terminated for volume volume again.
name - storage media inaccessible.
User Response: If possible, determine and correct the
Explanation: During migration for the indicated cause of the interruption.
volume a required volume cannot be mounted.
System Action: Migration stops. The server waits for ANR1126W Migration terminated for volume volume
the retry period to expire and then tries the migration name - insufficient space in subordinate
again. storage pools.
User Response: None. Explanation: During migration for the indicated
volume, the server cannot move the data from the
volume because there is not enough space on the next
storage pool to hold it.
name - insufficient number of mount
points available for removable media. System Action: Migration stops. The server waits for
again.
volume the server could not allocate sufficient mount
points for the volumes required. 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.
again.
name - unable to move file to
available.
subordinate storage pool due to
exclusion by size.
name - excessive read errors encountered.
volume, the server cannot move the data from the
Explanation: During migration for the indicated volume because a file size is larger than allowed on the
volume, read errors occurred that prevent the migration next storage pool.
from continuing.
System Action: Migration stops. The server waits for the retry period to expire and then tries the migration
the retry period to expire and then tries the migration again.
again.

file size or to change the next storage pool target.
name - sufficient memory is not
available.
name - sufficient recovery log space is
volume, there is not enough server memory available.
not available.
volume, the server runs out of recovery log space.
again.
again.
name - internal server error detected.
volume, the server encounters an internal error.
name - sufficient database space is not
available. System Action: Migration stops. The server waits for
again.
volume pool, the server runs out of database space.
again. ANR1134W Migration terminated for storage pool
storage pool name - insufficient number of
mount points available for removable
media.
storage pool the server could not allocate sufficient
name - lock conflict.
mount points in the next storage pool.
volume, the server needs to obtain a lock that is not
available.
again.
available.
again.
migration.
name - transaction aborted.
volume, the server detected an error while attempting
name - thread resource not available.
to commit a transaction.
volume, the server cannot start a thread for the
migration process.
again.
again.
transaction.
migration. If the error persists, it may indicate a
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.

ANR1146W Move data process terminated for
volume volume name - excessive read
ANR1141I Move data process ended for volume errors encountered.
volume name.
Explanation: During move data processing for the
Explanation: The MOVE DATA command for the indicated volume, read errors occurred that prevented
volume shown completes. the move from continuing.
System Action: None. System Action: The server ends the MOVE DATA
command.
read errors and then reissue the MOVE DATA
ANR1142I Moving data for collocation cluster command.
cluster number of total clusters on volume
volume name.
Explanation: As a result of a MOVE DATA command, volume volume name - excessive write
data moves from the volume indicated to new volumes; errors encountered.
the message shows the total number of clusters (data
objects) on the volume and the current cluster being Explanation: During move data processing for the
processed. indicated volume, write errors occurred that prevented
the move from continuing.
System Action: The server ends the MOVE DATA
User Response: None. command.
ANR1143W Move data process terminated for write errors and then reissue the MOVE DATA
volume volume name - process canceled. command.
indicated volume, the process performing the move ANR1148W Move data process terminated for
data was canceled. volume volume name - data transfer
System Action: The server ends the MOVE DATA interrupted.
command. Explanation: During move data processing for the
User Response: None. indicated volume a data transfer operation was
interrupted and could not be continued.
ANR1144W Move data process terminated for System Action: The server ends the MOVE DATA
volume volume name - storage media command.
inaccessible. User Response: If possible, determine and correct the
Explanation: During move data processing for the cause of the interruption.
indicated volume, a required volume cannot be
mounted. ANR1149W Move data process terminated for
System Action: The server ends the MOVE DATA volume volume name - insufficient space
command. in target storage pool.
User Response: None. Explanation: During move data processing for the
indicated volume, the server cannot move the data
from the volume, because there is not enough space on
ANR1145W Move data process terminated for the destination storage pool to hold it.
volume volume name - insufficient
number of mount points available for System Action: The server ends the MOVE DATA
removable media. command.
Explanation: During move data processing for the User Response: Make more space available in the next
indicated volume, the server could not allocate storage pool, or specify a storage pool with more space,
sufficient mount points for the volumes required. and reissue the MOVE DATA command.

command.
available.

ANR1150W Move data process terminated for ANR1154W Move data process terminated for
volume volume name - unable to move volume volume name - thread resource
file to target storage pool due to not available.
exclusion by size.
Explanation: During move data processing for the indicated volume, the server cannot start a thread for
indicated volume, the server cannot move the data the migration process.
from the volume because a file size is larger than
allowed on the next storage pool.
command.
User Response: Reissue the MOVE DATA command.
command.
If the error persists, it may indicate a shortage of server
User Response: Use the UPDATE STGPOOL memory.
file size or to change the next storage pool target, and
then reissue the MOVE DATA command.
is not available.
volume volume name - sufficient recovery
indicated volume, there is not enough server memory
log space is not available.
available.
indicated volume, the server runs out of recovery log
command.
space.
available to the server, and then reissue the MOVE
command.
DATA command.
volume volume name - internal server
ANR1152W Move data process terminated for error detected.
volume volume name - sufficient database
space is not available.
indicated volume, the server encounters an internal
Explanation: During move data processing for the error.
indicated volume, the server runs out of database
space.
command.
command.
ANR1157I Removable volume volume name is
required for move process.
Explanation: During move data or move node data
processing, the server determines that the indicated
volume volume name - lock conflict.
removable volume is required in order to complete
Explanation: During move data processing for the processing.
indicated volume, the server needs to obtain a lock that
was not available.
removable volume.
command.
indicated volume.
User Response: Reissue the MOVE DATA command.
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.

ANR1163W Offsite volume volume name still
fails.
contains files which could not be
User Response: Check for additional messages and 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
ANR1161W Move Data skipping damaged file on be copied from the other available volumes.
volume volume name: Node node name,
Type file type, File space filespace name,
File name file name. User Response: Check for messages indicating reasons
why files could not be moved. To complete the move
Explanation: During move data, a file is encountered
operation, you have several options:
that was previously found to be damaged. If this file is
part of an aggregate, the entire aggregate was v Bring the volume back on site and reissue a MOVE
previously marked damaged, possibly because an DATA command to reclaim the volume.
integrity error was detected for some other file within v Make the primary volumes available and reissue a
the aggregate. MOVE DATA command to reclaim the volume.
System Action: The damaged file is not moved. v Delete the files by using the DELETE VOLUME
command.
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 ANR1165E Data-integrity error detected for file in
undamaged during the audit. If the file is part of an storage pool storage pool name: Node node
aggregate, the audit will reset the aggregate status if name, Type file type, File space filespace
the entire aggregate is found to be undamaged. If this name, fsId filespace id, File name file name.
volume is in a primary storage pool that has previously Explanation: The server has detected a data-integrity
been backed up to a copy storage pool, attempt to error for the indicated file.
restore damaged files by using the RESTORE
STGPOOL command. 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
ANR1162W Space reclamation skipping damaged aggregate will be marked damaged. If a usable copy of
file on volume volume name: Node node the file exists in another storage pool, that copy may be
name, Type file type, File space filespace accessed for future operations involving the file.
name, File name file name.
User Response: If the indicated storage pool is a
Explanation: During reclamation, a file is encountered primary pool, and a usable copy of the file exists in a
that was previously found to be damaged. If this file is copy storage pool, you can recreate the file in the
part of an aggregate, the entire aggregate was primary pool using the RESTORE STGPOOL command.
previously marked damaged, possibly because an If the indicated storage pool is a copy storage pool, it is
integrity error was detected for some other file within possible that the primary copy of the file is usable, but
the aggregate. was not accessed because the access mode for the
System Action: The damaged file is not moved. primary storage pool or volume is unavailable. If this is
the case, the primary copy of the file may be made
User Response: Audit the indicated volume with accessible by changing the access mode of the primary
FIX=NO to verify that the file is damaged. The audit pool or volume.
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 ANR1166E Move Data for offsite volume cannot
the entire aggregate is found to be undamaged. If this copy damaged file in storage pool
volume is in a primary storage pool that has previously storage pool name: Node node name, Type
been backed up to a copy storage pool, attempt to file type, File space filespace name, fsId
restore damaged files by using the RESTORE filespace id, File name file name.
STGPOOL command. 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
ANR1169W Lock conflict on movement of offsite
moved from the offsite volume.
file - file is skipped.
User Response: The indicated storage pool is a
Explanation: During migration, reclamation, or move
primary pool that contains a damaged copy of the file.
data processing of a volume that is offsite, a copy of
The only usable copy of the file may now only reside
the file that resides in a primary disk storage pool is
on the offsite volume that was involved in the move
locked by another process.
data process. If you bring this volume back onsite, you
can recreate the file in the primary pool by using the System Action: The file is skipped and the process
RESTORE STGPOOL command. After the restore, you will try to find another copy of the file in a copy
can reissue the MOVE DATA command. storage pool. If another copy cannot be used, the move
operation on the volume may be incomplete.
ANR1167E Space reclamation for offsite volume(s) User Response: If a move operation was incomplete,
cannot copy damaged file in storage try repeating the operation.
pool storage pool name: Node node name,
Type file type, File space filespace
ANR1170E Out of Space in target copy storage
name,fsId filespace id , File name file name.
pool: copy storage pool name.
Explanation: A reclamation process of offsite volumes
Explanation: During reclamation, or move data
cannot locate an undamaged copy of the specified file
processing of a volume that is offsite, there was no
in any storage pool accessible by the server. If this file
volume available in the specified target copy storage
is part of an aggregate, the process could not locate an
pool.
undamaged copy of the aggregate to which the file
belongs. System Action: The operation is terminated.
System Action: The file is skipped and will not be User Response: Define volumes to the copy storage
moved from the offsite volume. pool or raise the MAXSCRATCH value.
User Response: The indicated storage pool is a
primary pool that contains a damaged copy of the file. ANR1171W Unable to move files associated with
The only usable copy of the file may now only reside node node name, filespace filespace name
on an offsite volume that was involved in the fsId filespace id on volume volume name
reclamation process, but was not totally reclaimed. If due to restore in progress.
you bring this volume back onsite, you can recreate the
file in the primary pool by using the RESTORE Explanation: During movement of data (migration,
STGPOOL command. reclamation, move data) from a sequential volume, one
or more files were encountered that were locked by a
restore operation.
ANR1168W Migration skipping damaged file on
volume volume name: Node node name, System Action: The files are not moved, but are
Type file type, File space filespace name, skipped.
fsId filespace id, File name file name. User Response: Use the QUERY RESTORE
Explanation: During migration, a file is encountered FORMAT=DETAILED command to determine if the
that was previously found to be damaged. If this file is restore operation is active or is in restartable state. A
part of an aggregate, the entire aggregate was restartable restore operation will keep the files locked
previously marked damaged, possibly because an from movement until the RESTOREINTERVAL is
integrity error was detected for some other file within reached. QUERY OPTION will display this interval.
the aggregate. You may wish to lower the RESTOREINTERVAL to
cause a restartable restore operation to be removed and
System Action: The damaged file will not be moved. free up the locked files. The RESTOREINTERVAL is a
server option.
will reset the file status if the file is found to be ANR1172E Move Data for offsite volume cannot
undamaged during the audit. If the file is part of an copy file in storage pool storage pool
aggregate, the audit will reset the aggregate status if name: Node node name, Type file type, File
the entire aggregate is found to be undamaged. If this space filespace name, fsId filespace id, File
volume is in a primary storage pool that has previously name file name.
been backed up to a copy storage pool, you can also
attempt to restore damaged files by using the Explanation: A move data process for an offsite
RESTORE STGPOOL command. 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
ANR1175W Volume volume name contains files which
volume.
could not be reclaimed.
System Action: The file will skipped and will not be
Explanation: After reclamation of the indicated
moved from the offsite volume.
volume, it still contains one or more files that could not
User Response: The indicated storage pool is a be reclaimed. These files were skipped because of read
primary pool that should contain a primary copy of the errors, or because the files are marked damaged.
file. Perhaps the volume on which that file resides is on
System Action: The volume is marked unavailable so
a destroyed volume. The only usable copy of the file
it will not be chosen again for reclamation.
may now only reside on the offsite volume that was
involved in the move data process. If you bring this User Response:
volume back onsite, you can recreate the file in the v Use the UPDATE VOLUME command to set the
primary pool by using the RESTORE STGPOOL volume access to readonly.
command. After the restore, you can reissue the MOVE
v Try using the MOVE DATA command to manually
DATA command.
reclaim the volume.
v If files still exist on the volume, audit the volume
ANR1173E Space reclamation for offsite volume(s) using AUDIT VOLUME FIX=YES.
cannot copy file in storage pool storage
v Try using the MOVE DATA command again.
pool name: Node node name, Type file type,
File space filespace name, fsId filespace id, v Use the RESTORE VOLUME command to restore
File name file name. files marked damaged.
Explanation: A reclamation process of offsite volumes

cannot locate a copy of the specified file in any storage ANR1180W Access mode for volume volume name
pool accessible by the server. If this file is part of an has been set to ″unavailable″ due to file
aggregate, the process could not locate a copy of the read or integrity errors.
aggregate to which the file belongs on an accessible Explanation: During processing of a storage pool
volume. volume, input/output or other errors occur that force
System Action: The file is skipped and will not be the server to mark the volume unavailable for further
moved from the offsite volume. processing.
User Response: The indicated storage pool is a System Action: The server sets the volume status to
primary pool that should contain a copy of the file. unavailable.
Perhaps the volume on which that file resides is on a User Response: Correct the errors that set the volume
destroyed volume. The only usable copy of the file may to unavailable, or use the DELETE VOLUME command
now only reside on an offsite volume that was involved to remove it from the system.
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 ANR1181E DiagnosticID: Data storage transaction
RESTORE STGPOOL command. transaction ID was aborted.
Explanation: A database transaction failed because of
ANR1174W One or more cached files were not an error that was detected during data storage
deleted on volume volume name. processing. This message should be preceded by other
Explanation: The MOVE DATA command could not failed transaction.
delete one or more cached files on the disk volume
shown. Migration was probably running at the same System Action: The server operation that encountered
time, creating cached files while the MOVE DATA this error during data storage processing fails.
command was trying to delete them.
System Action: The MOVE DATA command ran to eliminate the condition that caused the failed
completion. transaction.
User Response: If you want the remaining cached files

removed from the disk volume, reissue the MOVE ANR1186I Restore of node nodename, file system file
DATA command. 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
ANR1213I Backup process process ID terminated for
will be restored to the indicated destination.
storage pool storage pool name - process
System Action: The indicated process is started. canceled.
User Response: None. Explanation: During backup of the indicated primary

storage pool, a process performing the backup has been
canceled.
required for audit process. System Action: If other backup processes are
executing for the named storage pool, these processes
Explanation: During audit volume processing for the continue.
indicated volume, the server determines that a
removable volume is required in order to complete User Response: None.
processing.
System Action: The server attempts to mount the ANR1214I Backup of primary storage pool primary
removable volume. pool name to copy storage pool copy pool
name has ended. Files Backed Up:
User Response: Respond to any mount request for the number of files, Bytes Backed Up: number
indicated volume. of bytes, Unreadable Files: number of
unreadable files, Unreadable Bytes: number
ANR1210I Backup of primary storage pool primary of bytes in unreadable files.
pool name to copy storage pool copy pool Explanation: Backup processing for the specified
name started as process process ID. storage pool has ended with the results shown.
Explanation: A process has been started to back up a System Action: None.
primary storage pool to the indicated copy storage
pool. User Response: Examine previous messages to
determine whether all backup processes ended
System Action: For every noncached file in the successfully.
primary pool, a backup copy is made in the copy pool,
if a copy of that file does not already exist.
ANR1215I Backup preview of primary storage pool
User Response: None. primary pool name to copy storage pool
copy pool name has ended. Files Backed
ANR1211I Backup preview of primary storage pool Up: number of files, Bytes Backed Up:
primary pool name to copy storage pool number of bytes.
copy pool name started as process process Explanation: Backup preview processing for the
ID. specified storage pool has ended with the results
Explanation: A preview process has been started to shown.
back up a primary storage pool to the indicated copy System Action: None.
storage pool.
System Action: Preview information about the backup
operation is collected and displayed, but files are not
backed up. ANR1216E Command: Process process ID terminated -
Explanation: During backup processing, a required
volume could not be mounted.
ANR1212I Backup process process ID ended for
storage pool storage pool name. System Action: The indicated backup process ends.
Explanation: A backup process for the named primary User Response: None.
storage pool has ended.
System Action: None. ANR1217E Command: Process process ID terminated -
insufficient number of mount points
User Response: None. available for removable media.
Explanation: During backup processing, the server
could not allocate sufficient mount points for the
volumes required.
System Action: The indicated backup process ends.

ANR1223E Command: Process process ID terminated -
available.
available.
excessive read errors encountered.
runs out of database space.
Explanation: During backup processing, read errors
occur that prevent the backup from continuing.
read errors and reissue the backup command.
lock conflict.
excessive write errors encountered.
Explanation: During backup processing, write errors
occur that prevent the backup from continuing.
User Response: Reissue the backup command.
write errors and reissue the backup command.
thread resource not available.
cannot start a thread.
Explanation: During backup processing, a data
transfer operation was interrupted and could not be User Response: Reissue the backup command. If the
continued. error persists, it may indicate a shortage of server
memory.
interruption and reissue the backup command.
Explanation: During backup processing, not enough
server memory is available.
insufficient space in target copy storage
pool. System Action: The indicated backup process ends.
Explanation: During backup processing, the server User Response: If necessary, make more memory
cannot copy data to the copy storage pool because not available to the server, and then reissue the backup
enough space is available in the copy storage pool. command.
copy storage pool and reissue the backup command, or
reissue the backup command and specify another copy Explanation: During backup processing, the server
storage pool with more space. encounters an internal error.
available.
required for storage pool backup.
runs out of recovery log space.
Explanation: During processing of a BACKUP
STGPOOL command, the server determines that a
User Response: If necessary, make more server removable volume is required.
System Action: Unless this is a preview process, the
server attempts to mount the removable volume.

User Response: Respond to any mount request for the User Response: None.
indicated volume.
ANR1233I Restore preview of volumes in primary
ANR1229W Volume volume name cannot be backed storage pool primary pool name started as
up - volume is offline or access mode is process process ID.
″unavailable″ or ″destroyed″.
Explanation: A preview process has been started to
Explanation: During storage pool backup, a volume restore one or more volumes in the indicated primary
cannot be backed up either because it has been varied storage pool.
offline or because of the volume’s access mode.
System Action: Preview information about the restore
System Action: The server continues backup operation is collected and displayed, but files are not
processing, but skips the indicated volume. restored. The restore preview includes noncached files
that reside on selected volumes in the primary storage
User Response: If necessary, use the VARY ON or
pool.
UPDATE VOLUME command for this volume and
restart the backup command. User Response: None.
ANR1230I Restore of primary storage pool primary ANR1234I Restore process process ID ended for
pool name started as process process ID. storage pool storage pool name.
Explanation: A process has been started to restore the Explanation: A restore process for the named primary
indicated primary storage pool. storage pool has ended.
System Action: Non-cached files that reside in the System Action: None.
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 Restore process process ID ended for
volumes in storage pool storage pool
v The primary file has been identified as having
name.
data-integrity errors during a previous operation
Explanation: A restore process for volumes in the
named primary storage pool has ended.
ANR1231I Restore preview of primary storage pool
primary pool name started as process User Response: None.
process ID.
Explanation: A preview process has been started to ANR1236I Restore process process ID terminated for
restore a primary storage pool. storage pool storage pool name - process
canceled.
System Action: Preview information about the restore
operation is collected and displayed, but files are not Explanation: During restore of the indicated primary
restored. The restore preview includes noncached files storage pool, a process performing the restore has been
that reside in the specified primary storage pool and canceled.
that meet either of the following conditions:
System Action: If other restore processes are executing
v The file is stored on a volume whose access mode is for the named storage pool, these processes continue.
destroyed
v The primary file has been identified as having User Response: None.
data-integrity errors during a previous operation
User Response: None. ANR1237I Restore process process ID terminated for
volumes in storage pool storage pool name
- process canceled.
ANR1232I Restore of volumes in primary storage
pool primary pool name started as process Explanation: During restore of volumes in the
process ID. indicated primary storage pool, a process performing
the restore has been canceled.
Explanation: A process has been started to restore one
or more volumes in the indicated primary storage pool. System Action: If other restore processes are executing
for the volumes, these processes continue.
System Action: Noncached files that reside on
selected volumes in the primary storage pool are User Response: None.
restored.

ANR1238I Restore of primary storage pool primary ANR1242E Command: Process process ID terminated -
pool name has ended. Files Restored: storage media inaccessible.
number of files, Bytes Restored: number of
Explanation: During restore processing, a required
bytes, Unreadable Files: number of
volume could not be mounted.
unreadable files, Unreadable Bytes: number
of bytes in unreadable files. System Action: The indicated restore process ends.
Explanation: Restore processing for the specified User Response: None.
storage pool has ended with the results shown.
User Response: Examine previous messages to
determine whether all restore processes ended
successfully. Explanation: During restore processing, the server
could not allocate sufficient mount points for the
volumes required.
ANR1239I Restore preview of primary storage pool
primary pool name has ended. Files System Action: The indicated restore process ends.
Restored: number of files, Bytes Restored:
number of bytes. User Response: If necessary, make more mount points
available.
Explanation: Restore preview processing for the
specified storage pool has ended with the results
shown. ANR1244E Command: Process process ID terminated -
excessive read errors encountered.
Explanation: During restore processing, read errors
User Response: None. occur that prevent the restore from continuing.
System Action: The indicated restore process ends.
ANR1240I Restore of volumes in primary storage
pool primary pool name has ended. Files User Response: If possible, correct the cause of the
Restored: number of files, Bytes Restored: read errors and reissue the restore command.
number of bytes, Unreadable Files: number
of unreadable files, Unreadable Bytes: ANR1245E Command: Process process ID terminated -
number of bytes in unreadable files. excessive write errors encountered.
Explanation: Restore processing for volumes in the Explanation: During restore processing, write errors
specified storage pool has ended with the results occur that prevent the restore from continuing.
shown.
User Response: Examine previous messages to write errors and reissue the restore command.
determine whether all restore processes ended
successfully.
ANR1241I Restore preview of volumes in primary
storage pool primary pool name has Explanation: During restore processing, a data transfer
ended. Files Restored: number of files, operation was interrupted and could not be continued.
Bytes Restored: number of bytes. System Action: The indicated restore process ends.
Explanation: Restore preview processing for volumes User Response: If possible, correct the cause of the
in the specified storage pool has ended with the results interruption and reissue the restore command.
shown.
User Response: None. insufficient space in target primary
storage pool.
Explanation: During restore processing, the server
cannot copy data to the target primary storage pool,
because not enough space is available in the target
pool.

target primary storage pool, and then reissue the
restore command.
encounters an internal error.
sufficient recovery log space is not System Action: The indicated restore process ends.
available.
runs out of recovery log space.
System Action: The indicated restore process ends. required for restore processing.
User Response: If necessary, make more server Explanation: During processing of a RESTORE
recovery log space available. STGPOOL or RESTORE VOLUME command, the server
determines that a removable volume is required.
ANR1249E Command: Process process ID terminated - System Action: Unless this is a preview process, the
sufficient database space is not server attempts to mount the removable volume.
available.
Explanation: During restore processing, the server indicated volume.
runs out of database space.
System Action: The indicated restore process ends. 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
lock conflict.
of the volume’s access mode.
System Action: The server continues restore
processing, but skips the indicated volume.
User Response: If the volume is stored at an offsite
User Response: Reissue the restore command. location, bring the volume onsite. Use the UPDATE
VOLUME command to change the access mode for the
volume and restart the restore command.
ANR1256W Volume volume name contains files that
Explanation: During restore processing, the server could not be restored.
cannot start a thread.
Explanation: During processing of a RESTORE
System Action: The indicated restore process ends. STGPOOL or RESTORE VOLUME command, the server
User Response: Reissue the restore command. If the determines that the indicated volume contains one or
error persists, it may indicate a shortage of server more files that could not be restored. If this is a
memory. 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
ANR1252E Command: Process process ID terminated - restore operation, this message could result if any of
sufficient memory is not available. the following conditions exist for a file on the indicated
Explanation: During restore processing, there is not volume:
enough server memory available. v A restorable backup copy cannot be found for the
file.
v A restorable backup copy of the file exists, but is
User Response: If necessary, make more memory located on a copy storage pool volume whose access
available to the server; and then reissue the restore mode is unavailable or offsite.
command.
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 System Action: The server continues reclamation, but
volume while the restore was in progress. 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
User Response: If this was an actual restore operation,
available, use the UPDATE VOLUME command to
check for messages indicating that files could not be
change the access mode for the volume and initiate
restored because a copy storage pool volume was
reclamation again by updating the reclamation
unavailable or offsite. Check to see if a move data,
threshold for the copy storage pool.
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 ANR1260W Volume volume name contains one or
the situation and reissue the restore command. more damaged, primary files.
Explanation: This message is issued during RESTORE
ANR1257W Storage pool backup skipping damaged STGPOOL processing. The indicated volume contains
file on volume volume name: Node node one or more primary, noncached files that have
name, Type file type, File space filespace previously been found to be damaged.
name, fsId filespace id, File name file name.
System Action: If this is not a preview operation, the
Explanation: During storage pool backup, a file is restore processing attempts to restore the damaged files
encountered that was previously found to be damaged. from copies located in a copy storage pool. If this is a
If this file is part of an aggregate, the entire aggregate preview operation, no system action is taken.
was previously marked damaged, possibly because an
User Response: You can take the following actions:
integrity error was detected for some other file within
the aggregate. v Issue the QUERY CONTENT command with
DAMAGED=YES to obtain a list of damaged files on
System Action: The damaged file will not be backed the indicated volume.
up.
v Audit the indicated volume with FIX=NO to verify
User Response: Audit the indicated volume with that the files are damaged; the audit will reset the
FIX=NO to verify that the file is damaged. The audit status of any files that are found to be undamaged
will reset the file status if the file is found to be during the audit.
undamaged during the audit. If the file is part of an v If this message was issued during a restore preview
aggregate, the audit will reset the aggregate status if operation, attempt to restore the damaged files using
the entire aggregate is found to be undamaged. If this the RESTORE STGPOOL command.
file has previously been backed up to a copy storage
v Audit the indicated volume with FIX=YES to delete
pool, you can also attempt to restore damaged files
the damaged files from the database.
using the RESTORE STGPOOL command.
ANR1263I command: Processing completed

ANR1258W Files on volume volume name needed for
successfully.
move data cannot be accessed - access
mode is ″unavailable″ or ″offsite″. Explanation: The background process to service the
command command has completed successfully.
Explanation: During a move data operation on an
offsite volume, files on a storage pool volume cannot System Action: Processing for the command
be copied because of the volume’s access mode. completes. Statistics on the number and type of objects
moved, together with the total number of bytes copied,
System Action: The server continues move data
processing, but one or more files were not moved from
message.
the offsite 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 ANR1264I Command: Processing canceled before
MOVE DATA command. completion.
ANR1259W Files on volume volume name needed for command command has been canceled with the
offsite reclamation cannot be accessed - CANCEL PROCESS command.
access mode is ″unavailable″ or ″offsite″.
System Action: Processing for the command command
Explanation: During reclamation processing of an ends. Statistics on the number and type of objects
offsite volume, files on a storage pool volume cannot moved, together with the total number of bytes copied,
be copied because of the volume’s access mode.

ANR1269I Salvage volume command: Recovered
message.
number file(s).
command Salvage volume command recovered number
ANR1265E Salvage volume command: Processing files.
terminated abnormally - error accessing
System Action: Salvage processing for the command
data storage.
completes. Server operation continues.
in accessing data storage while executing a salvage
volume operation.
ANR1270I Salvage volume command: File (internal file
identifierinternal file identifier) recovered.
User Response: Use the QUERY ACTLOG command
command Salvage volume command recovered a file. The
new file was given a new, system generated name
the cause of the data storage failure. If you find and
based on the internal file identifier and the name of the
resolve the error, retry the operation. If you cannot find
volume from which the file was recovered. The internal
the error, contact your service representative for
file identifier is the identifier by which the file was
assistance in resolving the problem.
known to the server before the file was deleted.
ANR1266E Salvage volume command: Processing
terminated abnormally - volume not a
storage pool volume. User Response: None.
in accessing data storage while executing a salvage ANR1271I Salvage volume command: * number bytes
volume operation.The error occurred because an recovered from volume volume.
attempt has been made to access a volume that was not
a storage pool volume.
command Salvage volume command recovered a file from
System Action: The command command operation is the volume volume. The number of bytes recovered from
ended and server operation continues. the volume is listed.
User Response: Issue the command with a valid System Action: Salvage processing for the command
volume name. completes. Server operation continues.
ANR1267I Salvage volume command: Processed
number volume(s).
ANR1272I Salvage volume command: * File is
Explanation: The background process to service the complete - it began and ended on
command Salvage volume command inspected number volume volume.
input volumes.
System Action: Salvage processing for the command command Salvage volume command recovered a file from
completes. Server operation continues. the volume volume. The file was completely contained
on volume.
ANR1268I Salvage volume command: Recovered
number byte(s). User Response: None.
command Salvage volume command recovered number ANR1273I Salvage volume command: * File is
bytes worth of data. incomplete - it began on volume volume
but did not end.
completes. Server operation continues. Explanation: The background process to service the
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.

ANR1278I Occupancy is incorrect for storage pool
storage pool name. Occupancy is being
User Response: None. reset.
Explanation: The server has detected incorrect
ANR1274I Salvage volume command: * File is occupancy information.
incomplete - it ended on volume volume
System Action: The server recalculates the occupancy
but did not begin there.
value based on current storage pool information.
contained on volume. Although the file ended on this ANR1279I Occupancy is incorrect for volume name
volume, it spanned in from a different volume. volume name. Occupancy is being reset.
System Action: Salvage processing for the command Explanation: The server has detected incorrect
completes. Server operation continues. occupancy information.
User Response: None. System Action: The server recalculates the occupancy
value based on current sequential volume information.
ANR1275I Salvage volume command: * File is User Response: None.
incomplete - it did not began or end on
volume volume.
Explanation: The background process to service the transaction aborted.
detected an error while attempting to commit a
contained on volume. It spanned in from one volume
transaction. This message should be preceded by other
and spanned out to a another.
System Action: Salvage processing for the command failed transaction.
ANR1276E Command: Process terminated - sufficient transaction.
Explanation: During salvage processing, not enough ANR1281E Command: Process process ID terminated -
server memory is available. transaction aborted.
System Action: The salvage process ends. Explanation: During restore processing, the server
detected an error while attempting to commit a
transaction. This message should be preceded by other
available to the server, and then reissue the salvage
command.
failed transaction.
ANR1277E Command: Process terminated - the
default management class in the active User Response: Check for additional messages and
policy set in policy domain domain name eliminate the condition that caused the failed
does not contain an archive copy group. transaction.
Unable to continue with salvage.
Explanation: The background process to service the ANR1282I Logical occupancy is incorrect for
command Salvage volume command was unable to storage pool storage pool name. Logical
recover any files because the default management class occupancy is being reset.
in the active policy set in policy domain does not contain
Explanation: The server has detected incorrect logical
an archive copy group.
occupancy information.
System Action: The salvage process ends.
System Action: The server recalculates the logical
User Response: Add an archive copy group to the occupancy value based on current storage pool
default management class in the active policy set of the information.
specified domain, and then reissue the salvage
command.

ANR1283I File count is incorrect for storage pool ANR1300I VARY ONLINE command initiated for
storage pool name - file count is being disk volume volume name.
reset.
Explanation: A VARY ONLINE command has caused
Explanation: The server has detected an incorrect a vary-on process to be started for the volume
count of the number of files within this storage pool. specified.
System Action: The server will correct this System Action: The volume is varied online.
information.
ANR1301I VARY OFFLINE command initiated for
ANR1284I Move node data started as process disk volume volume name.
process ID.
Explanation: A VARY OFFLINE command has caused
Explanation: A process has been started to move data a vary-off process to be started for the volume
by node. specified.
System Action: The indicated process has started. System Action: The volume is varied offline.
User Response: To query the progress of the process, User Response: None.
use the QUERY PROCESS command. To cancel the
background process, use the CANCEL PROCESS
ANR1302E Disk volume volume name is already
command. Use the process ID number to specify this
online.
process.
Explanation: A VARY ONLINE command specified a
volume that was already online.
ANR1288I Move node data process process ID
ended for storage pool storage pool name. System Action: None.
Explanation: A move node data process for the named User Response: None.
storage pool has ended.
System Action: None. ANR1303E Disk volume volume name is already
offline.
Explanation: A VARY OFFLINE command specified a
volume that was already offline.
ANR1289I Move node data process process ID
terminated for the storage pool storage System Action: None.
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. ANR1304E Disk volume volume name is currently in
use.
System Action: If other move node data processes are
executing for the storage pool, these processes continue. Explanation: A VARY OFFLINE command specified a
volume that is currently in use and cannot be varied
User Response: None. offline at this time.
ANR1290I Move node data from storage pool
storage pool name to storage pool storage User Response: Try the command again at a later
pool name has ended. Files Moved: time, or attempt to determine how it is currently being
number of files, Bytes Moved: number of used and free it.
bytes, Unreadable Files: number of
unreadable files, Unreadable Bytes: number ANR1305I Disk volume volume name varied online.
of bytes in unreadable files.
Explanation: The specified volume has been varied
Explanation: Move node processing for the specified online as the result of a VARY ONLINE command.
storage pool has ended with the displayed results.
User Response: Examine previous messages to
determine whether all move node data processes ended
successfully.

User Response: Reformat the disk with a block size
ANR1306I Disk volume volume name varied online
that is an evenly divisible by 4096.
(read-only).
Explanation: The specified volume has been varied
ANR1314E Vary-on failed for disk volume volume
online in read-only mode as the result of a VARY
name - reduced capacity (was count
ONLINE command.
blocks, now count blocks.
Explanation: A VARY ONLINE command has been
User Response: None. issued for the disk volume specified, but the size of the
volume does not match the size expected.
ANR1307I Disk volume volume name varied offline. System Action: The volume is not varied online.
Explanation: The specified volume has been varied User Response: Restore the volume or otherwise
offline as the result of a VARY OFFLINE command. correct the disk volume size, and reissue the command.
name - invalid label block.
issued for the disk volume specified, but the label block
name - insufficient memory.
of the volume is invalid or cannot be read.
System Action: The volume is not varied online.
issued for the disk volume specified, but sufficient
memory is not available to process the command. User Response: Restore or reformat the disk volume.
User Response: Reissue the command at a later time,
name - internal error detected.
or make more memory available to the server.
issued for the disk volume specified, but fails due to an
internal server error.
name - unable to access disk device.
issued for the disk volume specified, but the server is User Response: Contact your service representative.
unable to access the disk.
System Action: The volume is not varied online. ANR1320W Vary-on not possible for disk volume
volume name - access state is
″unavailable″.
inability to access the volume and correct the problem.
issued for the disk volume specified, but the status of
the volume is unavailable.
name - error reading disk.
issued for the disk volume specified but the server User Response: If necessary, use the UPDATE
encounters an error reading the disk. VOLUME command to change the status of the
volume, and reissue the command.
ANR1321W Vary-on not possible for disk volume
read error and correct the problem.
volume name - access state is ″destroyed″.
issued for the disk volume specified, but the status of
name - unsupported block size (block
the volume is destroyed.
size).
issued for the disk volume specified, but the volume is User Response: If necessary, use the UPDATE
formatted with a block size that cannot be used. VOLUME command to change the status of the

WORM (Write Once - Read Many) characteristics of the
ANR1340I Scratch volume volume name is now
media.
defined in storage pool storage pool name.
System Action: The volume will have a state where
Explanation: The scratch volume specified has been
the access mode is READONLY, the status is FULL and
added to the storage pool shown.
the percent utilized is 0.0. The volume is considered
System Action: None. empty for storage pool occupancy and utilization fields.
User Response: None. User Response: If the volume is in a library, it must
first be removed using the CHECKOUT LIBVOLUME
command prior to manually deleting the volume. Use
ANR1341I Scratch volume volume name has been
the DELETE VOLUME command to remove the
deleted from storage pool storage pool
volume from server storage.
name.
Explanation: The scratch volume specified is no
ANR1360I Output volume volume name opened
longer in use and has been removed from the indicated
(sequence number sequence number).
storage pool.
Explanation: During a sequential data operation, the
volume specified has been opened for output as the
User Response: None. volume number shown.
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 ANR1361I Output volume volume name closed.
has elapsed.
Explanation: All files have been deleted from the volume specified has been closed because the export or
indicated scratch volume. The volume will not be dump is complete.
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 User Response: None.
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 ANR1362I Output volume volume name closed
the tape, or it will be removed from the storage pool (full).
after it is no longer required. Explanation: During a sequential data operation, the
System Action: None. volume specified has been closed because the volume is
full.
ANR1343I Unable to delete scratch volume volume User Response: None.

name.
Explanation: A scratch volume cannot be deleted from ANR1363I Input volume volume name opened
the server and returned to scratch at this time because (sequence number sequence number).
all the locks have not be released. A number of retries Explanation: Because of a sequential data operation,
have been attempted. the volume specified has been opened for input as the
System Action: None volume number shown.
User Response: The scratch volume will be System Action: None.

automatically deleted when the server is restarted. Or, User Response: None.
you may manually delete this volume later, using the
DELETE VOLUME command.
ANR1364I Input volume volume name closed.
ANR1344I Volume volume name cannot be reused, Explanation: During a sequential data operation, the
remove from server storage. volume specified has been closed because the operation
is complete.
Explanation: A volume that was full and is now
empty cannot be reused by the server due to the System Action: None.

System Action: The volume is not used. The operation
ANR1365I Volume volume name closed (end
is terminated.
reached).
User Response: Make sure you specified the correct
volume for the operation. A Version 1 database dump
volume specified has been closed because processing of
may not be loaded into a Version 2 server. The Version
the volume is complete.
1 database dump must only be loaded into a Version 1
System Action: None. server.
ANR1370E Insufficient number of mount points
available in device class device class name.
ANR1366W Input volume volume name contains an
invalid identifier. Explanation: During IMPORT or EXPORT processing,
the server cannot allocate sufficient mount points for
the device class specified. The device class associated
volume specified has been mounted but contains an
with the EXPORT or IMPORT drive only has a mount
invalid identifier.
limit of one. The operation needs to read or write file
System Action: The volume is not used. data from or to the same device class because file data
is being imported or exported.
User Response: Make sure you specified the correct
volume for the operation. If a LOADDB operation was System Action: The IMPORT or EXPORT command is
being performed on MVS, the command syntax may be ended and server operation continues.
specified by using a ddname or by specifying a device
User Response: Make more mount points available.
class name. You must use the same method that was
used when the database was originally dumped. If you
did not, this error message will be displayed. Try ANR1400W Mount request denied for volume
loading the data base by using the other method of volume name - mount canceled.
syntax (ddname).
Explanation: The volume shown cannot be mounted
because the mount request has been canceled.
ANR1367W Import volume volume name was written
System Action: The volume is not mounted.
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 ANR1401W Mount request denied for volume
process. volume name - mount failed.
System Action: The volume is not used. Explanation: The volume shown cannot be mounted
because the mount request cannot be completed
User Response: Supply a volume created by the
successfully. Possible reasons include, an error in device
proper export process.
specifications to the server or the mount request timed
out.
ANR1368W Input volume volume name contains
sequence number sequence number;
volume sequence number sequence User Response: If the device specifications (DEFINE
number is required. DEVCLASS and so forth) are in error, correct them and
reissue the command that requested the volume to be
mounted.
volume specified has been mounted but contains the
wrong volume sequence number.
ANR1402W Mount request denied for volume
System Action: The volume is not used.
volume name - volume unavailable.
User Response: Supply the volume with the proper
Explanation: The volume shown cannot be mounted
sequence number. The volume history file can help you
because it is not available.
choose the correct volume.
ANR1369E Input volume volume name contains User Response: None.
Version 1 dump.
volume specified has been mounted but appears to
contain a version 1 database dump.

ANR1403W Scratch volume mount request denied - ANR1410W Access mode for volume volume name
mount canceled. now set to ″unavailable″.
Explanation: A scratch volume cannot be mounted Explanation: The status of the volume shown has
because the mount request has been canceled. been set to unavailable.
System Action: The scratch volume is not mounted. System Action: None.
ANR1404W Scratch volume mount request denied - ANR1411W Access mode for volume volume name
mount failed. now set to ″read-only″ due to write
error.
Explanation: A scratch volume cannot be mounted
because the mount request cannot be completed Explanation: Because of an unrecoverable write error
successfully. Possible reasons include, an error in device on the volume shown, the status of the volume has
specifications to the server or the mount request timed been set to read-only.
out.
System Action: The scratch volume is not mounted.
User Response: If the device specifications (for
example, DEFINE DEVCLASS) are in error, correct
ANR1412W Volume volume name access mode is
them and reissue the command that requested the
″unavailable″.
volume to be mounted.
Explanation: At server startup, the status of the
indicated volume is unavailable.
ANR1405W Scratch volume mount request denied -
no scratch volume available. System Action: None.
Explanation: A scratch volume cannot be mounted User Response: None.
because no scratch volume is available.
System Action: The scratch volume is not mounted. ANR1413W Volume volume name access mode is
″read-only″.
indicated volume is read-only.
ANR1409W Volume volume name already in use -
skipped. System Action: None.
Explanation: During an export or database backup, a User Response: None.
volume cannot be used because it is already defined in
a storage pool, or has already been used by the current
operation, or has been previously used by an export or ANR1414W Volume volume name access mode is
database backup operation (as recorded in the volume ″read-only″ due to previous write error.
history) or is in use by another process. Explanation: At server startup, the status of the
System Action: The operation continues and the indicated volume is read-only due to an unrecoverable
volume is skipped. write error, or because an administrator used the
UPDATE VOLUME command to set the volume access
User Response: Use the QUERY VOLUME command mode to read-only.
to display the names of volumes that are defined to
server storage pools. Use the QUERY VOLHISTORY System Action: None.
command to display the names of volumes that have User Response: None.
been used for export or database backup operations. If
no volume names are displayed using the query
commands described above, ensure that the volume ANR1415W Volume volume name access mode is
identified in this message has not been specified or ″destroyed″.
used more than once in the operation being performed. Explanation: At server startup, the status of the
indicated volume is destroyed.

ANR1416W Volume volume name access mode is ANR1420W Read access denied for volume volume
″offsite″. name - volume access mode =
″unavailable″.
indicated volume is offsite. 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 Access mode for volume volume name
now set to ″read-only″ due to excessive
read error.
ANR1421W Read access denied for volume volume
Explanation: Because of an numerous read errors on
name - volume offline.
the volume shown, the status of the volume has been
set to read-only. Explanation: An attempt to access the named volume
for reading failed because the volume is offline.
System Action: The volume is not used.
User Response: Use QUERY VOLUME
FORMAT=DETAILED for the volume to view the User Response: None.
access mode and number of read errors. You may want
to use the MOVE DATA command to move the
ANR1422W Read access denied for volume volume
retrievable data from this volume to another volume.
name - volume access mode=″offsite″.
For the damaged files, use the RESTORE VOLUME
command to restore a readable copy of the file to the Explanation: An attempt to access the named volume
storage pool. for reading failed because the volume status is offsite.
System Action: The volume is not used for read
ANR1418E command name: Export commands that access.
target another server cannot be issued
from the server console. User Response: None.
Explanation: An EXPORT command that targets

another server was issued from the server console. This ANR1423W Scratch volume volume name is empty
command cannot be issued from the server console but will not be deleted - volume access
because it requires authentication of the issuing mode is ″offsite″.
administrator on the target server. Explanation: The named scratch volume is empty but
System Action: The server ignores the command and will not be deleted at this time because the access mode
continues processing. is offsite.
User Response: Issue the command from an System Action: The volume is not deleted.
administrative client. User Response: After bringing the volume onsite,
change the access mode to read-only so the volume will
ANR1419E command name : FROMDATE must be be deleted.
specified when FROMTIME is
specified. ANR1424W Read access denied for volume volume
Explanation: A command that supports the name - volume access mode=″destroyed″.
FROMDATE and FROMTIME parameters was issued Explanation: An attempt to access the named volume
with the FROMTIME parameter specified, but without for reading failed because the volume status is
the FROMDATE parameter. When the FROMTIME destroyed.
parameter is used, the FROMDATE parameter must be
specified. System Action: The volume is not used for read
access.
System Action: The server ignores the command and
continues processing. User Response: None.
User Response: Reissue the command with both the

FROMDATE and FROMTIME parameters specified.

ANR1425W Scratch volume volume name is empty ANR1433I Device configuration information
but will not be deleted - volume state is successfully written to file name.
″mountablenotinlib″.
Explanation: Device configuration information was
Explanation: The named scratch volume is empty but successfully written to the file specified.
will not be deleted at this time because the state of the
volume is MOUNTABLENOTINLIB.
User Response: When the volume is moved by MOVE
ANR1434W No files have been identified for
MEDIA WHERESTATE=MOUNTABLENOTINLIB, the
automatically storing device
scratch empty volume is deleted.
configuration information.
Explanation: The server is unable to automatically
ANR1430W Retrieval request denied for storage
update device configuration file. No files were
pool storage pool name - access
identified using the DEVCONFIG option in the server
mode=″unavailable″.
options file.
Explanation: An attempt was made to retrieve a file
from the storage pool shown, but the access mode of
the storage pool is unavailable. User Response: If you would like to have the server
automatically record device configuration information
System Action: The file is not retrieved from this
to assist in server recovery, use the DEVCONFIG
storage pool. If possible, the file is retrieved from
option in the server options file to specify where device
another storage pool.
configuration information should be written. If you
User Response: Consider changing the access mode update the options file, halt and then restart the server
for the storage pool. so the changes can take effect.
ANR1431E An error occurred while writing to side ANR1435E Server could not write device
A of volume volume name. An attempt configuration information to devconfig
will be made to write to side B of this file name.
volume.
Explanation: While attempting to write device
Explanation: An error occurred while writing to side configuration information to defined files, the server
A of a two-sided volume. cannot write to the file name specified.
System Action: No additional data will be written to System Action: The server cannot write device
side A of this volume. Any remaining space on side A configuration information to the specified file.
will not be used. An attempt will be made to use the
User Response: Examine error messages that may
reverse side (side B) of the volume.
have been displayed prior to this message and correct
User Response: None required if the side B can be any problems, if possible. Make sure that the server has
used successfully. However, the administrator should proper authority to write to the file indicated and that
investigate the cause of the error and may want to there is sufficient space in the file system for the file.
move data from this volume. 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
ANR1432I Updating device configuration
BACKUP DEVCONFIG command to write device
information to defined files.
configuration information to the file.
Explanation: The server is updating device
configuration information for the files or data sets
ANR1436E Device configuration file devconfig file
specified with the DEVCONFIG option in the server
name cannot be opened.
options file.
Explanation: While attempting to write device
configuration information to device configuration files,
User Response: None. the server cannot open the file name specified.
System Action: The server does not write device
configuration information to the file specified.
any problems, if possible. Make sure that the server has

proper authority to write to the file indicated and that have been displayed prior to this message for more
there is sufficient space in the file system for the file. information.
On MVS, make sure that the data set has been allocated
ANR1440I All drives in use. Process process number
set. After the problem has been corrected, use the
being preempted by higher priority
BACKUP DEVCONFIG command to write device
operation.
configuration information to the file.
Explanation: When a high priority operation
attempted to find an available drive, all the drives were
ANR1437E No device configuration files could be
in use. To make a drive available for this operation, the
used.
indicated process is being cancelled by the system.
Explanation: The server attempts to read device
System Action: The lower priority process is cancelled
configuration information from defined files and cannot
to make a mount point (drive) available.
open any of the files.
User Response: When a drive again becomes
System Action: The operation is ended.
available, restart the process that was cancelled. If the
User Response: Examine error messages that may process was a migration or reclamation process, it will
have been displayed prior to this message and correct be automatically restarted when needed. If this message
any problems, if possible. Ensure that the defined appears frequently, you may want to increase the
device configuration files have been created. If you can number of drives available. See the MOUNTLIMIT
start the server, you can create the files by using the parameter on the UPDATE DEVCLASS command.
BACKUP DEVCONFIG command. If you cannot start
the server, you will need to create a device
ANR1441I Volume volume name is in use. Process
configuration file by editing the file and adding the
process number being preempted by
appropriate DEFINE commands for the device class,
higher priority operation.
drive, and library definitions. The contents and
requirements for this file are described in the Explanation: When a high priority operation
Administrator’s Guide. Make sure that the server has attempted to use a volume, it was in use. To make a
proper authority to read from the defined device volume available for this operation, the indicated
configuration files. process is being cancelled by the system.
System Action: The lower priority process is cancelled
ANR1438W Skipping device configuration file: to the volume available.
devconfig file name.
User Response: Restart the process that was cancelled.
Explanation: While attempting to read device It will wait until the higher priority process is finished
configuration information from a defined device with the volume. If the cancelled process was a
configuration file, the server encounters problems in migration or reclamation process, it will be
processing the definitions included in the file. automatically restarted when needed.
System Action: The specified file is skipped, and the
next one specified in the server options file will be ANR1442E Invalid storage pool for store operation:
used. storage pool.
User Response: Examine error messages that may Explanation: The storage pool selected for a store
have been displayed prior to this message to operation (for example, backup or archive) was not a
understand why the file could not be used. When you NATIVE or NONBLOCK data format storage pool. This
can start the server again, you can refresh this file by may be caused by an incorrect management class being
using the BACKUP DEVCONFIG command. assigned to an object.
ANR1439E Allocate prohibited - transaction failed.
User Response: Ensure that the copy group
Explanation: While attempting to preallocate storage destination storage pool of the assigned management
on a storage pool, the server detected that the class has the appropriate NATIVE or NONBLOCK data
transaction for this operation has previously failed. This format.
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 ANR1450E command name: Invalid command script
the file. name: command script name.
System Action: An internal error is reported by the Explanation: An invalid script name was specified for
server and the operation being performed is ended. a DEFINE, UPDATE, or DELETE SCRIPT command.
User Response: Examine error messages that may System Action: The operation fails.

User Response: Reenter the command specifying a
ANR1457I command name: Command script command
valid command name.
script name deleted.
Explanation: The script name specified in a DELETE
ANR1451E command name: Invalid command:
COMMAND command was successfully deleted.
command.
System Action: None
Explanation: An invalid command was specified for a
DEFINE, UPDATE, or DELETE SCRIPT command. User Response: None
ANR1458I command name: Line line number was
deleted from command script command
valid server command.
script name.
Explanation: The specified line number was deleted
ANR1452E command name: Invalid line number: line
from the command script as a result of a DELETE
number.
SCRIPT command.
Explanation: An invalid line number was specified for
System Action: None
a DEFINE, UPDATE, or DELETE SCRIPT command.
User Response: None
ANR1459E command name: Command script command
valid line number.
script name, line line number does not
exist.
Explanation: The line in command script name
script name already exists.
specified in a UPDATE, or DELETE SCRIPT command
Explanation: The script name specified in a DEFINE does not exist.
SCRIPT command already exists.
User Response: Reenter the command specifying a different line number.
different command name.
ANR1454I command name: Command script command script name copied to new command script
script name defined. name.
Explanation: The script name specified in a DEFINE Explanation: The specified command script was
SCRIPT command was successfully defined. copied to a new script with the COPY SCRIPT
command.
System Action: None
System Action: None
User Response: None
User Response: None
script name does not exist. ANR1461I command name: Executing command
script command script name.
Explanation: The script name specified in a DEFINE,
UPDATE, or DELETE SCRIPT command does not exist. Explanation: The specified command script is being
executed as a result of a RUN command.
System Action: None
different command name. User Response: None
ANR1456I command name: Command script command ANR1462I command name: Command script command
script name updated. script name completed successfully.
Explanation: The script name specified in an UPDATE Explanation: The specified command script, started
SCRIPT command was successfully updated. with a RUN command, has successfully completed.
System Action: None System Action: None
User Response: None User Response: None

ANR1463E command name: Command script command ANR1468E command name: Command script command
script name completed in error. script name, continued line is too long
Explanation: The specified command script, started Explanation: The specified command script with
with a RUN command, encountered errors. continuation lines is too long to be executed.
System Action: Part or all of the command lines in System Action: The command fails.
the script ended in error. Command processing is
User Response: Correct the specified command script
terminated.
so that it is shorter.
User Response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
command script and reissue the command.
script name, Line line number is an
INVALID command : command line.
Explanation: The specified line for the command
script name, line line number, parameter
script is not a valid server command. This message is
parameter number was not specified:
displayed when a RUN command is executed with the
command line.
PREVIEW=YES parameter specified.
Explanation: All parameters required to execute a
System Action: Command Preview processing fails
command script were not specified in the RUN
command. User Response: Correct the script and reenter the
RUN command.
System Action: The command fails.
User Response: Reenter the RUN command specifying
all required parameters.
script name completed successfully
(PREVIEW mode).
Explanation: The specified command script, started
script name, line line number, parameter is
with a RUN command, has successfully completed.
invalid: command line.
Explanation: An invalid parameter was encountered
in a command script. User Response: None.
User Response: Correct the script definition and
script name completed in error
reexecute the RUN command.
(PREVIEW mode).
Explanation: The specified command script, started
with a RUN command, encountered errors.
script name, Line line number : command
line. System Action: Part or all of the command lines in
the command script ended in error. Command
Explanation: The specified line for the command
processing is terminated.
script is being executed. The contects of the line being
executed are displayed. User Response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
System Action: None
script and reissue the command.
User Response: None
ANR1467E command name: Command script command script name renamed to new command
script name, did not end in a script name.
non-continued line command line.
Explanation: The specified command script was
Explanation: The specified command script did not renamed with the RENAME SCRIPT command.
end in a line that had no continuation character (-).
User Response: Correct the specified script so that it
ends in a line that is not continued to the next line.

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

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

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

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

ANR1502I Policy domain domain name updated.
Explanation: In response to the UPDATE DOMAIN
command, the policy domain domain name has been
updated in the server database. ANR1513I Policy set set name copied to set new set
name in policy domain domain name.
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
ANR1503I Policy domain domain name copied to domain name. All management classes and copy groups
domain target domain. are also copied to the policy set new set name.
Explanation: In response to the COPY DOMAIN System Action: Server operation continues.
command, the policy domain domain name has been
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. ANR1514I 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
ANR1504I Command: No matching domains. management class and copy group definitions in the
policy set will be used by clients that start sessions
Explanation: The server cannot find any policy
after this command is committed. Clients that currently
domains with names that match the specification
have sessions established with the server will use the
entered in the command command.
policy definitions in the previously active policy set for
System Action: Server operation continues. the domain.
User Response: Reissue the command with a System Action: The server replaces the active
specification that matches an existing policy domain management class and copy group definitions for the
name. Use the QUERY DOMAIN command to obtain a policy domain with the definitions found in the
list of the names of existing policy domains. specified policy set. These values are returned to client
nodes that start a session with the server after this
command is committed to the server database.
ANR1510I Policy set set name defined in policy
domain domain name. User Response: None.
Explanation: In response to the DEFINE POLICYSET

command, the policy set named set name has been ANR1515I Policy set set name validated in domain
defined in the policy domain named domain name in the domain name (ready for activation).
server database.
Explanation: This message may be displayed in
System Action: Server operation continues. response to a VALIDATE POLICYSET command. The
policy set set name has been checked in the domain
User Response: None. domain name to see if the management class and copy
group definitions are adequate for activating the policy
ANR1511I Policy set set name deleted from policy set. This message indicates that the policy set may be
domain domain name. activated. Warning messages may be issued prior to
this message if there are discrepancies in the policy set
Explanation: In response to the DELETE POLICYSET with respect to the set that is currently active in the
command, the policy set set name has been deleted from policy domain.
the policy domain domain name in the server database.
System Action: The server checks its definitions to
System Action: Server operation continues. determine the policy set’s qualifications for activation.
User Response: None. The server does not activate the policy set.
User Response: If you are satisfied with any warning
ANR1512I Policy set set name updated in policy messages that may have been issued prior to this
domain domain name. message concerning any possible discrepancies in the
policy set, issue the ACTIVATE POLICYSET command
Explanation: In response to the UPDATE POLICYSET to activate the policy set in the policy domain.
command, the policy set set name has been updated in Otherwise, correct the discrepancies prior to activating
the policy domain domain name in the server database. the policy set. Before the ACTIVATE POLICYSET

command is used to activate the policy set, use the named class name in the policy set set name belonging to
validate command to check policy set contents. policy domain domain name.
ANR1520I Management class class name defined in
policy domain domain name, set set name.
Explanation: In response to the DEFINE
ANR1531I Backup copy group group name deleted
MGMTCLASS command, the management class named
from policy domain domain name, set set
class name has been defined in the policy set set name
name, management class class name.
belonging to the policy domain named domain name.
Explanation: In response to the DELETE
COPYGROUP command, the backup copy group
User Response: None. 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.
ANR1521I Management class class name deleted
from policy domain domain name, set set System Action: Server operation continues.
name.
Explanation: In response to a DELETE MGMTCLASS
command, the management class named class name has
ANR1532I Backup copy group group name updated
been deleted from the policy set set name belonging to
in policy domain domain name, set set
the policy domain domain name. All copy groups
defined for the management class are also removed.
Explanation: In response to the UPDATE
COPYGROUP command, the backup copy group
User Response: None. named group name has been updated in the
ANR1522I Management class class name updated in
policy domain domain name, set set name. System Action: Server operation continues.
Explanation: In response to the UPDATE User Response: None.
MGMTCLASS command, the management class named
class name has been updated in the policy domain
ANR1535I Archive copy group group name defined
domain name, policy set set name.
in policy domain domain name, set set
System Action: Server operation continues. name, management class class name.
User Response: None. Explanation: In response to the DEFINE
COPYGROUP command, an archive copy group named
group name has been defined for the management class
ANR1523I Management class class name copied to
named class name in the policy set set name belonging to
class new class name in policy domain
policy domain domain name.
Explanation: In response to the COPY MGMTCLASS
command, the management class named class name has User Response: None.
been copied to a new management class named new
class name in policy set set name belonging to policy
ANR1536I Archive copy group group name deleted
domain domain name. All copy groups defined for
from policy domain domain name, set set
management class class name are also copied to
management class new class name.
Explanation: In response to the DELETE
COPYGROUP command, the archive copy group
User Response: None. named group name has been deleted from the
ANR1530I Backup copy group group name defined
in policy domain domain name, set set System Action: Server operation continues.
Explanation: In response to the DEFINE
COPYGROUP command, a backup copy group named
group name has been defined for the management class

ANR1537I Archive copy group group name updated ANR1551W BACKUP copygroup group name in
in policy domain domain name, set set management class class name is NOT
name, management class class name. defined in policy set set name but is
defined in the ACTIVE policy set for
Explanation: In response to the UPDATE
domain domain name: files bound to this
COPYGROUP command, the archive copy group
management class will no longer be
named group name has been updated in the
backed up if/when set name is activated.
name belonging to policy domain domain name. Explanation: This message may be returned from the
VALIDATE POLICYSET or ACTIVATE POLICYSET
command. During policy set validation processing, the
User Response: None. 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
ANR1538I Default management class set to class the management class in the policy set being validated
name for policy domain domain name, set or activated (set name). If policy set set name is
set name. activated, files bound to management class class name in
Explanation: The default management class for the domain domain name will no longer be eligible for
policy set set name in policy domain domain name has backup processing.
been set to the management class named class name. System Action: Server operation continues.
System Action: If this policy set is activated, clients User Response: If you want files bound to this
use this management class for backup-archive management class to be eligible for backup processing,
processing by default, or if other management classes define an archive copy group for management class
specified for binding do not exist in the policy set. class name by using the DEFINE COPYGROUP
ANR1550W Management class class name is NOT ANR1552W ARCHIVE copygroup group name in
defined in policy set set name but IS management class class name is NOT
defined in the ACTIVE policy set for defined in policy set set name but is
domain domain name: files bound to this defined in the ACTIVE policy set for
management class will be REBOUND to domain domain name: files bound to this
the default management class if/when management class will no longer be
this set is activated. archived if/when set name is activated.
Explanation: This message may be returned from the Explanation: This message may be returned from the
VALIDATE POLICYSET or ACTIVATE POLICYSET VALIDATE POLICYSET or ACTIVATE POLICYSET
command. During policy set validation processing, the command. During policy set validation processing, the
server has found a management class named class name server has found an archive copy group named group
in the currently active policy set, but not defined in the name for management class class name in the currently
policy set being validated or activated (set name). If active policy set, but the copy group is not defined for
policy set set name is activated, files bound to this the management class in the policy set being validated
management class in domain domain name are or activated (set name). If policy set set name is
automatically rebound to the default management class activated, files bound to management class class name in
in policy set set name. domain domain name will no longer be eligible for
archive processing.
User Response: If you do not want files to be rebound
to the default management class, define a management User Response: If you want files bound to this
class with the name specified in the message for the management class to be eligible for archive processing,
policy set. To define the proper copy group attributes, define an archive copy group for management class
reference the management class definition in the class name by using the DEFINE COPYGROUP
ACTIVE policy set or copy the management class class command.
name from the ACTIVE policy set to policy set set name
using the COPY MGMTCLAS command.

ANR1553W DEFAULT Management class class name ANR1555W The BACKUP copy group in
in policy set domain name set name does management class management class name
not have a BACKUP copygroup: files specifies a destination that does not
will not be backed up by default if this refer to a defined storage pool: storage
set is activated. pool name. If this pool does not exist
when policy set policy set name is
Explanation: This message may be returned from the
activated, clients will fail when using
this management class to backup files to
command. During policy set validation for policy set
the server.
set name in policy domain domain name, the server has
found that the default management class named class Explanation: This message may be returned from the
name does not have a backup copy group. This message VALIDATE POLICYSET or ACTIVATE POLICYSET
warns the administrator that activation of this policy command. During policy set validation for set name, the
set results in client files not being backed up, unless server has found a backup copy group destination that
they are bound to a management class (which has a references an undefined storage pool named pool name.
copy group) other than the default. 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
User Response: To define a backup copy group for the copy groups reference this pool.
management class, issue the DEFINE COPYGROUP
command. To assign a different default management
class for the domain, issue the ASSIGN User Response: To locate the copy groups that refer to
DEFMGMTCLASS command. Take either action if you the undefined storage pool, issue the QUERY
want files to be backed up by default. COPYGROUP command. To change the destination to
refer to an existing storage pool, issue the UPDATE
COPYGROUP command. To define the storage pool, an
ANR1554W DEFAULT Management class class name
authorized administrator can issue the DEFINE
in policy set domain name set name does
STGPOOL command.
not have an ARCHIVE copygroup: files
will not be archived by default if this
set is activated. ANR1556W The ARCHIVE copy group in
specifies a destination that does not
refer to a defined storage pool: storage
command. During policy set validation for policy set
pool name. If this pool does not exist
set name in policy domain domain name, the server has
when policy set policy set name is
found that the default management class named class
activated, clients will fail when using
name does not have an archive copy group. This
this management class to archive files to
message warns the administrator that activation of this
the server.
policy set will result in client files not being allowed
archive processing unless they are bound to a Explanation: This message may be returned from the
management class (which has an archive copy group) VALIDATE POLICYSET or ACTIVATE POLICYSET
other than the default. command. During policy set validation for set name, the
server has found a archive copy group destination that
references an undefined storage pool named pool name.
User Response: To define a backup copy group for the If this storage pool is undefined when the policy set is
management class, issue the DEFINE COPYGROUP activated, backup or archive operations will fail for
command. To assign a different default management clients with files bound to the management class whose
class for the domain, issue the ASSIGN copy groups reference this pool.
DEFMGMTCLASS command. Take either action if you
want files to be eligible for archive processing by
default. User Response: To locate the copy groups that refer to
the undefined storage pool, issue the QUERY
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.

command. During policy set validation for set name, the
ANR1557W The space management migration
server has found a copy group destination that
destination in management class
references a copy storage pool named pool name.
management class name does not refer to a
defined storage pool: storage pool name. If System Action: Server operation continues. The policy
this pool does not exist when policy set set is not activated.
policy set name is activated, clients will
fail when using this management class User Response: To locate the management class that
to migrate space-managed files to the refers to the copy storage pool, issue the QUERY
server. MGMTCLASS command. To change the destination to
refer to a non-copy storage pool, issue the UPDATE
Explanation: This message may be returned from the MGMTCLASS command.
command. During policy set validation for set name, the
server has found a space management migration ANR1560E Command: Invalid policy domain name -
destination that references an undefined storage pool domain name.
named pool name. If this storage pool is undefined Explanation: Server processing for the command
when the policy set is activated, space management command fails because the policy domain name domain
migration operations will fail for clients with files name specified does not contain valid characters or
bound to the management class that references this contains too many characters.
pool.
System Action: Database changes for the command
System Action: Server operation continues. are rolled back and server operation continues. The
User Response: To locate the management class that command is not successful in changing the server
refers to the undefined storage pool, issue the QUERY database.
MGMTCLASS command. To change the destination to User Response: Reissue the command and specify a
refer to an existing storage pool, issue the UPDATE policy domain name that conforms to these name
MGMTCLASS command. To define the storage pool, an requirements. For information on the character and
authorized administrator can issue the DEFINE length specifications for valid policy domain names,
STGPOOL command. refer to the Administrator’s Reference for your particular
platform.
ANR1558E The space management migration
destination in management class ANR1561E Command: Missing policy domain name.
management class name in policy set policy
set name refers to copy storage pool: Explanation: Server processing for the command
storage pool name. Copy storage pools are command fails because the required policy domain
not a valid migration destination. parameter has not been specified.
Explanation: This message may be returned from the System Action: Database changes for the command
VALIDATE POLICYSET or ACTIVATE POLICYSET are rolled back and server operation continues. The
command. During policy set validation for set name, the command is not successful in changing the server
server has found a space management migration database.
destination that references a copy storage pool named User Response: Reissue the command and specify a
pool name. valid policy domain name.
System Action: Server operation continues. The policy
set is not activated. ANR1562E Command: Policy domain description
User Response: To locate the management class that exceeds length limit characters.
refers to the copy storage pool, issue the QUERY Explanation: Server processing for the command
MGMTCLASS command. To change the destination to command fails because the policy domain description
refer to a non-copy storage pool, issue the UPDATE specified is longer than the length limit number of
MGMTCLASS command. characters allowed.
ANR1559E The copy group destination for type are rolled back and server operation continues. The
copy group type in management class command is not successful in changing the server
management class name in policy set policy database.
set name refers to copy storage pool:
storage pool name. Copy storage pools are User Response: Reissue the command and specify a
not a valid copy group destination. shorter policy domain description.


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

requirements. For information on the character and
ANR1573E Command: Invalid copy type - type value.
length specifications for valid copy group names, refer
to the Administrator’s Reference for your particular Explanation: Server processing for the copy group
platform. command command fails because the value (type value)
specified for the TYPE parameter is not valid.
ANR1570E Command: Invalid copy frequency - System Action: Database changes for the command
frequency value. are rolled back and server operation continues. The
database.
command command fails because the value (frequency
value) specified for the FREQUENCY parameter is not User Response: Reissue the command and specify a
valid. valid TYPE value. For valid TYPE values for the
DEFINE COPYGROUP or UPDATE COPYGROUP
commands, refer to the Administrator’s Reference for
your particular platform.
database.
ANR1574E Command: Invalid version count for
VEREXISTS parameter - version value.
valid FREQUENCY value. For valid FREQUENCY
values for the DEFINE COPYGROUP or UPDATE Explanation: Server processing for the copy group
COPYGROUP commands, refer to the Administrator’s command command fails because the value (version
Reference for your particular platform. value) specified for the VEREXISTS parameter is not
valid.
ANR1571E Command: Invalid copy destination - pool System Action: Database changes for the command
name. are rolled back and server operation continues. The
database.
command fails because the storage pool name pool name
specified for the copy group destination does not User Response: Reissue the command and specify a
contain valid characters or contains too many valid VEREXISTS value. For valid VEREXISTS values
characters. for the DEFINE COPYGROUP or UPDATE
COPYGROUP commands, refer to the Administrator’s
Reference for your particular platform.
database. ANR1575E Command: Invalid version count for
VERDELETED parameter - version value.
storage pool name that conforms to valid name Explanation: Server processing for the copy group
requirements. For information on the character and command command fails because the value (version
length specifications for valid storage pool names, refer value) specified for the VERDELETED parameter is not
to the Administrator’s Reference for your particular valid.
platform. For a list of names of defined storage pools,
issue the QUERY STGPOOL command.
ANR1572E Command: Missing copy destination. database.
Explanation: Server processing for the copy group User Response: Reissue the command and specify a
command command fails because the required copy valid VERDELETED value. For valid VERDELETED
group destination is not specified. values for the DEFINE COPYGROUP or UPDATE
database. ANR1576E Command: Invalid retention period for
RETEXTRA parameter - retention value.
User Response: Reissue the command and specify the
required copy group destination (DEST). Explanation: Server processing for the copy group
value) specified for the RETEXTRA parameter is not
valid.

ANR1580E Command: Invalid copy serialization
mode - serialization value.
database.
command command fails because the value (serialization
valid RETEXTRA value. For valid RETEXTRA values
value) specified for the SERIALIZATION parameter is
for the DEFINE COPYGROUP or UPDATE
not valid.
Reference for your particular platform. System Action: Database changes for the command
ANR1577E Command: Invalid retention period for
database.
RETONLY parameter - retention value.
valid SERIALIZATION value. For valid
SERIALIZATION values for the DEFINE COPYGROUP
value) specified for the RETONLY parameter is not
or UPDATE COPYGROUP commands, refer to the
valid.
Administrator’s Reference for your particular platform.
ANR1581E Command: The option option is valid only
for backup copy groups.
database.
Explanation: Server processing for the archive copy
group command command fails because the option
valid RETONLY value. For valid RETONLY values for
specified is only valid for backup copy group
the DEFINE COPYGROUP or UPDATE COPYGROUP
definitions.
your particular platform. System Action: Database changes for the command
ANR1578E Command: Invalid version count for
database.
RETVER parameter - retention value.
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
value) specified for the RETVER parameter is not valid.
valid archive copy group options, refer to the
System Action: Database changes for the command Administrator’s Reference and Administrator’s Guide for
are rolled back and server operation continues. The your particular platform.
database.
ANR1582E Command: The option option is valid only
User Response: Reissue the command and specify a for archive copy groups.
valid RETVER value. For valid RETVER values for the
Explanation: Server processing for the backup copy
group command command fails because the option
specified is only valid for archive copy group
definitions.
ANR1579E Command: Invalid copy mode - mode
value.
Explanation: Server processing for the copy group database.
command command fails because the value (mode value)
User Response: Reissue the command specifying valid
specified for the MODE parameter is not valid.
backup copy group options, or specifying
System Action: Database changes for the command TYPE=ARCHIVE if the intent is to operate on an
are rolled back and server operation continues. The archive copy group. For valid backup copy group
command is not successful in changing the server options, refer to the Administrator’s Reference and
database. Administrator’s Guide for your particular platform.

valid MODE value. For valid MODE values for the

the COPY POLICYSET command. Then to activate the
ANR1583E Command: Copy frequency for archive
changes, issue the ACTIVATE POLICYSET command.
copy groups must be CMD - frequency
value is not valid.
ANR1586E Command: Invalid migration destination
Explanation: Server processing for the archive copy
- pool name.
group command command fails because a value other
than CMD has been specified for the FREQUENCY Explanation: Server processing for the command
parameter. The only value that may be specified for the command fails because the storage pool name pool name
archive copy group FREQUENCY parameter is CMD. specified for the migration destination is a copy pool. A
copy pool is not a valid migration destination.
are rolled back and server operation continues. The System Action: Database changes for the command
command is not successful in changing the server are rolled back and server operation continues. The
database. command is not successful in changing the server
database.
User Response: Reissue the command specifying
CMD for the FREQUENCY parameter, or omitting the User Response: Reissue the command using a storage
FREQUENCY parameter because the default value for pool name that is not a copy pool. For a list of names
FREQUENCY is CMD for archive copy groups. For of defined storage pools, issue the QUERY STGPOOL
valid archive copy group options, refer to the command.
Administrator’s Reference and Administrator’s Guide for
ANR1587E Command: Invalid copy group
destination - pool name.
ANR1584E Command: Copy mode for archive copy
groups must be ABSOLUTE - mode value Explanation: Server processing for the command
is not valid. command fails because the storage pool name pool name
specified for the copy group destination is a copy pool.
Explanation: Server processing for the archive copy A copy pool is not a valid copy group destination.
group command command fails because a value other
than ABSOLUTE has been specified for the MODE System Action: Database changes for the command
parameter. The only value that may be specified for the are rolled back and server operation continues. The
archive copy group MODE parameter is ABSOLUTE. command is not successful in changing the server
database.
are rolled back and server operation continues. The User Response: Reissue the command using a storage
command is not successful in changing the server pool name that is not a copy pool. For a list of names
database. of defined storage pools, issue the QUERY STGPOOL
command.
ABSOLUTE for the MODE parameter, or omitting the
MODE parameter because the default value for MODE ANR1590E Command: Policy domain domain name is
is ABSOLUTE for archive copy groups. For valid not defined.
archive copy group options, refer to the Administrator’s Explanation: Server processing for the command
Reference and Administrator’s Guide for your particular command fails because the policy domain name domain
platform. name specified does not refer to a defined policy
domain in the server database.
ANR1585E Command: Policy set ACTIVE cannot be System Action: Database changes for the command
modified. are rolled back and server operation continues. The
Explanation: Server processing for the command command is not successful in changing the server
command fails because the policy set name ACTIVE is database.
specified. Objects in the ACTIVE policy set for a User Response: Reissue the command specifying a
domain may only be changed through activation of policy domain name that is defined in the server
another policy set. database. For a list of the names of defined policy
System Action: Database changes for the command domains in the server database, issue the QUERY
are rolled back and server operation continues. The DOMAIN command.
database. ANR1591E Command: Policy domain domain name is
User Response: Reissue the command specifying a already defined.
policy set other than ACTIVE. To copy the ACTIVE Explanation: Server processing for the command
policy set for a policy domain to another name so that command fails because the policy domain name domain
commands may be used to change its contents, issue

name specified refers to a policy domain that is already command is not successful in changing the server
defined in the server database. database.
System Action: Database changes for the command User Response: To activate a policy set for the
are rolled back and server operation continues. The specified policy domain, issue the ACTIVATE
command is not successful in changing the server POLICYSET command. After a policy set has been
database. activated, client nodes may be assigned to the policy
domain.
User Response: Reissue the command specifying a
policy domain name that is not defined in the server
database. For a list of the names of defined policy ANR1595E Command: Policy set set name is not
domains in the server database, issue the QUERY defined in policy domain domain name.
DOMAIN command.
command fails because the policy set name set name
ANR1592E Command: Policy domain domain name specified does not refer to a defined set in policy
still contains at least one policy set. domain domain name in the server database.
Explanation: Server processing for the delete System Action: Database changes for the command
command command fails because the policy domain are rolled back and server operation continues. The
name domain name specified refers to a policy domain command is not successful in changing the server
that still contains at least one policy set. database.
System Action: Database changes for the command User Response: Reissue the command specifying a
are rolled back and server operation continues. The policy set name that is defined in the policy domain.
command is not successful in changing the server For a list of the names of defined policy sets in the
database. policy domain, issue the QUERY POLICYSET
command.
User Response: To delete the policy set from the
policy domain, issue the DELETE POLICYSET
command. ANR1596E Command: Policy set set name is already
defined in policy domain domain name.
ANR1593E Command: Policy domain domain name Explanation: Server processing for the command
still contains at least one node. command fails because the policy set name set name
specified refers to a policy set that is already defined in
Explanation: Server processing for the delete
command command fails because the policy domain
name domain name specified refers to a policy domain System Action: Database changes for the command
that still contains at least one node. A policy domain are rolled back and server operation continues. The
cannot be deleted if one or more client nodes are still command is not successful in changing the server
assigned to the domain. database.
System Action: Database changes for the command User Response: Reissue the command specifying a
are rolled back and server operation continues. The policy set name that is not defined in the policy
command is not successful in changing the server domain. For a list of the names of defined policy sets in
database. the policy domain, issue the QUERY POLICYSET
command.
User Response: To remove remaining nodes from the
policy domain, issue the REMOVE NODE command.
After all nodes are removed, issue the delete command ANR1597E policy set command: Policy set set name in
again. domain domain name still contains at
least one management class.
ANR1594E Command: Policy domain domain name Explanation: The policy set command failed because the
has no active policy set. set still contains at least one management class
definition.
Explanation: Server processing for the update or
register node command command fails because the System Action: The command fails and server
policy domain name domain name specified refers to a operation continues.
policy domain that does not have an active policy set
User Response: Remove the remaining management
defined. Nodes cannot be assigned to policy domains
classes from the policy set and reissue the command.
that do not have an active policy set.

ANR1598E Command: No default management class ANR1602E Command: Backup copy group group name
has been assigned for policy set set name is not defined in policy domain domain
in domain domain name. name, set set name, management class
class name.
command fails because the policy set set name in policy Explanation: Server processing for the command
domain domain name does not have a default command fails because the backup copy group named
management class assigned. 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. System Action: Database changes for the command
User Response: To assign a default management class
in the policy set, issue the ASSIGN DEFMGMTCLASS
database.
command.
copy group name that is defined. For a list of the
ANR1599E Command: Management class class name
names of defined copy groups and management classes
is not defined in policy domain domain
in the policy domain or policy set, issue the QUERY
name, set set name.
COPYGROUP command.
command fails because the management class name class
ANR1603E Command: Backup copy group group name
name specified does not refer to a defined management
is already defined in policy domain
class in policy set set name belonging to policy domain
domain name, set set name, management
domain name.
class class name.
command fails because the specified backup copy group
named group name refers to a copy group that is
database.
already defined for management class (class name) in
User Response: Reissue the command specifying a policy set set name belonging to policy domain domain
policy set name that is defined in the policy domain. name.
For a list of the names of defined policy sets in the
policy domain, issue the QUERY POLICYSET
command.
database.
ANR1600E Command: Management class class name
is already defined in policy domain
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
Explanation: Server processing for the command management classes in the policy domain and policy
command fails because the specified management class set, issue the QUERY COPYGROUP command.
name class name refers to a management class that is
already defined in policy set set name belonging to
ANR1604E Command: Archive copy group group
name is not defined in policy domain
System Action: Database changes for the command domain name, set set name, management
are rolled back and server operation continues. The class class name.
database.
command fails because the archive copy group named
User Response: Reissue the command specifying a group name specified for management class class name
management class name that is not defined in the does not refer to a defined archive copy group in policy
policy set. For a list of the names of defined set set name belonging to policy domain domain name.
management classes in the policy domain and policy
set, issue the QUERY MGMTCLASS command.
database.
copy group name that is defined. For a list of the

names of defined copy groups and management classes
ANR1608E Error fetching entry for domain domain
in the policy domain or policy set, issue the QUERY
name, set set name.
COPYGROUP command.
Explanation: An internal server database error occurs
while retrieving policy information for policy set set
ANR1605E Command: Archive copy group group
name in domain domain name.
name is already defined in policy
domain domain name, set set name, System Action: The policy operation is ended and
management class class name. server operation continues.
Explanation: Server processing for the command User Response: Examine the server messages issued
command fails because the specified archive copy group prior to this message to determine the source of the
named group name refers to a copy group that is error. Use the QUERY ACTLOG command to view the
already defined for management class class name in activity log and search for messages. If the error cannot
policy set set name belonging to policy domain domain be isolated and resolved, contact your service
name. representative.
are rolled back and server operation continues. The ANR1609E Policy error: unable to find management
command is not successful in changing the server class ID for class class name in policy set
database. set name belonging to domain domain
name.
copy group that is not defined in the policy set. For a Explanation: An internal server database error has
list of the names of defined copy groups for been encountered while retrieving policy information
management classes in the policy domain and policy for management class class name in policy set set name
set, issue the QUERY COPYGROUP command. belonging to policy domain domain name.
System Action: The policy operation is ended and
ANR1606E Out of server LOG space in accessing server operation continues.
policy tables.
Explanation: The server ends a database update prior to this message to determine the source of the
transaction for policy information because sufficient log error. Use the QUERY ACTLOG command to view the
space is not available on the server. activity log and search for messages. If the error cannot
representative.
ANR1610E Internal Server error: invalid copy type
copy type integer encountered in policy
for use by the log and can issue the EXTEND LOG
set validation.
volumes are used. Explanation: An internal server database error has
been encountered while validating a policy set in
response to the VALIDATE POLICYSET or ACTIVATE
ANR1607E Out of server DB space in accessing
POLICYSET command.
policy tables.
transaction for policy information because sufficient
database space is not available on the server. User Response: Examine the server messages issued
User Response: An authorized administrator can issue be isolated and resolved, contact your service
the DEFINE DBVOLUME command to add volumes representative.
for use by the database and can issue the EXTEND DB
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.

ANR1643I Command: All file spaces for node node
name, will be moved.
database.
Explanation: The server will attempt to move data for
all the file spaces for the specified node name based on
another management class name.
the criteria entered in the MOVE NODEDATA
command.
ANR1612E Command: Management class management
System Action: Server moves data for the indicated
class name in policy set set name, domain
node.
domain name specifies
MIGREQUIRESBKUP=YES, but User Response: None.
contains no backup copy group.
Explanation: During policy set validation or activation ANR1644E Command: Move node data operation
for policy set set name in policy domain domain name, already in progress for storage pool
the server has found that the management class named storage pool.
class name specifies the MIGREQUIRESBKUP=YES
Explanation: A command has been issued to move
parameter but does not contain a backup copy group.
node data for the specified storage pool but there is
Policy set validation or activation fails in this case
already a move node data operation in progress for one
because it would not be possible to ensure that
or more nodes that have been specifed for that same
space-managed client files are backed up prior to being
storage pool.
migrated to the server.
command.
command is not successful in changing the server User Response: Check the activity log for a previous
database. MOVE NODEDATA command to determine what
processes for moving node data are in progress for the
User Response: To define a backup copy group within
storage pool. Reissue the command for the node(s) and
the management class, issue the DEFINE COPYGROUP
storage pool you desire that are not already in progress,
command. To change the MIGREQUIRESBKUP
or, reissue the command after the move node data
parameter, issue the UPDATE MGMTCLASS command.
process ends.
ANR1640E There is no data mover defined for node

ANR1645I Command: Data for node node name,
node name.
filespace filespace name, FSID filespace ID
Explanation: To perform the requested operation, the will be moved.
specified node must have an associated data mover
Explanation: The server will move data for the
defined.
specified filespace name and node name based on the
System Action: The requested operation fails. criteria entered in the MOVE NODEDATA command.
User Response: Define a data mover for the node and System Action: The server moves data for the
retry the operation. specified node and filespaces.
ANR1641E command: The node node name has a type
that is not allowed for this command.
ANR1646I Command: Node Node name, no filespaces
Explanation: The node is not the correct type to be found to move for this node.
used with this command.
Explanation: A node and filespace were entered in a
System Action: The command fails. MOVE NODEDATA command but no filespaces were
found for the specifed node.
User Response: Re-run the command with a node of
the correct type. System Action: The server continues to move other
filespaces for any other nodes specified in the MOVE
NODEDATA command.
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.

entry created using the DEFINE SERVER command.
ANR1647E Cannot find file space name for node
node ID, file space file space ID.
ANR1651E Server information for server name is not
Explanation: The server could not obtain filespace
available.
information for that node.
Explanation: The information for server name was not
System Action: The server operation continues.
available.
System Action: The current server action fails.
error. Issue the QUERY ACTLOG command to view the User Response: Please review any other messages
activity log and search for messages. If the error cannot prior to this message to determine the cause of the
be isolated and resolved, contact your service failure.
representative.
ANR1652E Server information for server name could

ANR1648W Command:This command will move data not be read from a device configuration
for nodes stored in volumes in storage file.
pool source storage pool to other volumes
within the same storage pool; the data Explanation: An attempt to a server definition for
will be inaccessible to users until the server name from any device configuration files failed.
operation completes. System Action: The current action for the device class
Explanation: A MOVE NODEDATA command has referring to this server fails.
been entered that will move data to other volumes in User Response: Please verify the existence of a device
the same storage pool. While the data is being moved, configuration file and the DEFINE SERVER stanza
it will not be available to users. within that file.
System Action: The administrator is asked whether to
continue. ANR1653E Resource lock acquisition for server
User Response: Enter 'Y' to continue or 'N' to end the server name failed.
process. Explanation: The acquisition of the resource lock for
server server name failed.
ANR1649W Command:This command will move data System Action: The current action for the device class
for nodes stored in storage pool source referring to this server fails.
storage pool to storage pool destination
storage pool; the data will be inaccessible User Response: Retry the action referring to the
to users until the operation completes. device class that refers to this server name. If the lock
failure persists, please contact your service
Explanation: A MOVE NODEDATA command has representative.
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 ANR1654E Server server name will not be written to
to users. a device configuration file.
System Action: The administrator is asked whether to Explanation: An error occurred accessing the
continue. information for server name while trying to write this
information to a device configuration file.
User Response: Enter 'Y' to continue or 'N' to end the
process. System Action: This DEFINE SERVER entry is not
processing.
ANR1650E Server server name is not defined. User Response: Verify that the necessary DEFINE
SERVER entries were written to a device configuration
Explanation: The server name was not created using file. If this error persists, please contact your service
the DEFINE SERVER command. This entry was created representative.
using the REGISTER NODE NODETYPE=SERVER
command and is not a valid reference.
ANR1655E Failure processing password for Server
System Action: The current action for the device class server name when writing a device
referring to this server fails. configuration file.
User Response: The device class referring to this node Explanation: An error occurred processing the
as the SERVERNAME should be updated to refer to a password for server name while trying to write this
valid server entry. Specifically, it should refer to an information to a device configuration file.

System Action: This DEFINE SERVER entry is written
ANR1660I Server server name defined successfully.
to the device configuration file without the password.
Explanation: The requested server has been defined to
User Response: The password needs to be specified
the system in response to a DEFINE SERVER
after PASSWORD= for this DEFINE SERVER entry in
command.
the device configuration file.
ANR1656E Failure writing server definitions to a User Response: None.
device configuration file.
Explanation: An error occurred writing the server ANR1661I Server server name deleted.
information to a device configuration file.
Explanation: In response to a DELETE SERVER
System Action: The BACKUP DEVCONFIG action command, the requested server has been removed from
fails. the system.
User Response: Check that the device configuration System Action: None.
file exists and that the file system the file resides on is
not out of space.
ANR1662I Server server name updated.

ANR1657E Command: Invalid server or group name
- server or group name. Explanation: One or more attributes of a server have
been updated by an UPDATE SERVER command.
Explanation: The command shown specifies an invalid
server or server group name. System Action: None.
System Action: The server does not process the User Response: None.
command.
User Response: Reissue the command with a valid ANR1663E command: Server server name not defined
name.
Explanation: The server server name is not defined to
the system.
ANR1658E Command: Failure determining
NODENAME for server server name. System Action: The command fails.
Explanation: The command shown was unable to User Response: None.

determine a node name either from the NODENAME=
parameter on this command or from the server name ANR1664W Command: Server server name is currently
previously set using the SET SERVERNAME command. in use.
System Action: The server does not process the Explanation: The command shown specifies a server
command. that is currently in use. The server is referenced by one
User Response: Reissue the command with a valid or more of the following: a device class of
node name parameter or else update the server name DEVTYPE=SERVER that specifies this server for the
using the SET SERVERNAME command so that a valid ’SERVERNAME=’ parameter, it is defined as the event
name is available. server, or a connection with this server is currently
open and in use.
ANR1659E Command: Server or server group server System Action: The server does not process the
or group name is already defined. command.
Explanation: A DEFINE SERVER or DEFINE User Response: Reissue the command at a later time.
SERVERGROUP command has been entered that In order to delete the server specified, it must not be
specifies a server or server group name that already currently connected to the server, it may not be
exists. The name specified must be a unique name. It referenced in a device class, and it can not be defined
must not duplicate a node name used by a registered to be the event server.
node, a server name used by a defined server, or a
server group name used by a defined server group. ANR1665E command: Failure updating password for
System Action: The server does not process the server server name.
command. Explanation: An error occurred updating the
User Response: To define the server or server group, password for server name.
reissue the command and specify a different name. System Action: The command fails.

User Response: Re-try the command specifying a
ANR1671I The event server definition has been
different password.
deleted.
Explanation: The event server definition has been
ANR1666E command: FILEAGGR not allowed with
deleted.
NODETYPE=SERVER.
Explanation: The FILEAGGR= parameter may not be
specified with the NODETYPE=SERVER parameter also User Response: If an event server definition is
being specified. desired, use the DEFINE EVENTSERVER command.
ANR1672I No event server is currently defined.
User Response: Reissue the command command
without the FILEAGGR= parameter if this is a Explanation: A query was issued to get the name of
NODETYPE=SERVER. the event server; however, no event server is currently
defined.
ANR1667E command: Action not permitted against System Action: None.
node node name.
User Response: If an event server definition is
Explanation: The command is not permitted against desired, use the DEFINE EVENTSERVER command.
the entry for node node name. This node entry has a
NODETYPE of SERVER.
ANR1673I Server group group name defined
System Action: The command fails. successfully.
User Response: None. Explanation: The requested server group is defined to
the system in response to a DEFINE SERVERGROUP
command.
ANR1668E command: Not allowed for server server
name. System Action: None.
Explanation: The DELETE SERVER command is not User Response: None.
permitted for server server name. The specified server is
either the event server or else it is a node entry rather
ANR1674I Member member name defined
than a server definition.
successfully in server group group name.
Explanation: The requested member is defined in the
User Response: If the specified server is the event server group in response to a DEFINE GRPMEMBER
server, and you want to delete it, issue the DELETE command.
EVENTSERVER command and then reissue the
DELETE SERVER command. To remove a node entry,
issue the REMOVE NODE command for the specified User Response: None.
name.
ANR1675I Server group server group name deleted.

ANR1669I Server event server name is defined as the
event server. Explanation: The requested server is removed from
the system in response to a DELETE SERVERGROUP
Explanation: The specified server is defined. command.
System Action: None. System Action: None.
ANR1670E Server event server name is already ANR1676I Member member name deleted from
defined as the event server. You must server group server group name.
issue the DELETE EVENTSERVER
command before defining a new event Explanation: The requested member is removed from
server. the server group in response to a DELETE
GRPMEMBER command,
Explanation: An event server is already defined.
User Response: Delete the existing Event Server and
try the command again.

ANR1677I Server group server group name updated. ANR1683E Command: Member member name not
defined.
Explanation: One or more attributes of a server group
is updated by an UPDATE SERVERGROUP command. 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
ANR1678I Server group original server group name
existing server or group.
renamed new server group name.
Explanation: A server group is renamed by a
ANR1684E Route:command: Routed commands
RENAME SERVERGROUP command. The original
cannot be routed.
name is not valid.
Explanation: The command part of a routed command
may not contain route information itself. The allowable
User Response: None. syntax for routed commands is “:”. The command may
not contain route information. Only one level of routing
is allowed.
ANR1679E Command: Server group server group name
not defined. System Action: Routed commands where the
command portion contains additional routing
Explanation: The server server group name is not information are not processed.
defined to the system.
User Response: Reissue the command without
System Action: The command fails. specifying route information in the command portion
User Response: Retry the command specifying an of this routed command.
existing group.
ANR1685I Server group server group copied to
ANR1680E Command: Member member name not server group new server group.
defined in server group server group Explanation: This message is displayed in response to
name. the COPY SERVERGROUP command. The server group
Explanation: The member member name is not defined named server group is copied to the server group named
in server group server group name. new server group.
System Action: The command fails. System Action: None.
User Response: Retry the command specifying an User Response: None.

existing member of the group.
ANR1686I Member member name moved from
ANR1681E Command: Member member name is server group group name to server group
already in server group server group new group name.
name. Explanation: The requested member member name is
Explanation: The member member name is defined in moved from server group group name to the server
server group server group name. group new server group in response to a MOVE
GRPMEMBER command.
User Response: Retry the command and specify a
new member name. User Response: None.
ANR1682E A group cannot be a member of itself. ANR1687I Output for command ’command’ issued
against server server name follows:
Explanation: The member and group name are the
same. A group may not be a member of itself. Explanation: The output for the command issued
against the indicated server follows this message.
User Response: Retry the command and specify
another member name. User Response: None.

User Response: Please contact your local service
ANR1688I Output for command ’command’ issued
representative.
against server server name completed.
Explanation: This message marks the end of the
ANR1693E Unable to issue command ’command’
output for the command specified that was issued
against server server name - failure
against the indicated server.
starting thread.
Explanation: A thread could not be started to issue
User Response: None. the specified command against the server indicated.
System Action: This command is not issued against
ANR1689E Output for command ’command’ issued the server specified. The process will attempt to issue
against server server name terminated. the command against any other servers that were
specified for the command routing information.
Explanation: An error condition occurred causing the
output for the command issued against the specified User Response: Examine the server messages issued
server to be terminated. prior to this message to determine the source of the
error. Retry routing this command to the indicated
server after the cause of the error has been determined
User Response: Retry the command against the and resolved. If the error cannot be isolated and
requested server once the error condition has been resolved, contact your service representative.
resolved. If the cause of the error can not be
determined, please contact your local service
ANR1694I Server server name processed command
representative.
’command’ and completed successfully.
Explanation: The server indicated processed the
ANR1690E Error sending command ’command’ to
command successfully.
server server name.
Explanation: An error was encountered sending the
specified command to the server indicated. User Response: None.
ANR1695W Server server name processed command
User Response: Retry the command against the
’command’ but completed with warnings.
requested server once the error condition has been
resolved. If the cause of the error can not be Explanation: The server indicated processed the
determined, please contact your local service command but encountered warnings. However, the
representative. warnings did not prevent the execution of the
command.
ANR1691E Error receiving response from server System Action: None.
server name for command ’command’.
Explanation: An error was encountered receiving the
response from the server indicated for the command
ANR1696E Server server name attempted to process
that was issued against it.
command ’command’ but encountered
System Action: None. errors.
User Response: Retry the command against the Explanation: The server indicated processed the
requested server once the error condition has been command but encountered errors. These errors
resolved. If the cause of the error can not be prevented the successful completion of the command.
determined, please contact your local service
representative.
User Response: Examine any error messages issued
on either the server sending the command or else the
ANR1692E Response for command ’command’ from
server executing the command to determine the cause
server server name contains invalid data.
of the failure. Reissue the command once these errors
Explanation: The output returned from the specified are corrected.
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.

ANR1697I Command ’command’ processed by total ANR1701E Command: No matching servers defined.
number for servers server(s): number of
Explanation: No matching servers are found for the
successful servers successful, number of
specified command.
servers with warnings with warnings, and
number of servers with errors with errors. System Action: Server operation continues, but the
command is not processed.
Explanation: The indicated command was processed
by the number of servers specified. For the total User Response: Issue the command and specify
number of servers, the number indicated were different servers.
successful, the number indicated encountered a
warning condition but processed anyway, and finally,
the number indicated encountered errors and could not ANR1702W Skipping ’server name’ - unable to
process. resolve to a valid server name.
System Action: None. Explanation: The server name specified is being

skipped because it could not be resolved to a valid
User Response: None. server name.
ANR1698I Command ’command’ was not issued
against any other servers. User Response: Reissue the command providing the
correct server name.
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 ANR1703E Failure resolving server names.
occurred issuing the command against the required Explanation: An error occurred while resolving the
servers. indicated number of server. server names. Specifically, the resolution of the server
System Action: None. names has terminated because of a significant failure.
User Response: Check to see that valid route System Action: None.
information was provided for the command or else User Response: Check the activity log and server
check the activity log for error messages that indicate console for other messages about the cause of the
why the command was not issued to the other server. failure. Once the cause has been resolved, reissue the
command.
ANR1699I Resolved route information to number of
servers server(s) - issuing command ANR1704E Failure obtaining credentials for
command against server(s). administrator admin name.
Explanation: The route information was resolved to Explanation: An error occurred obtaining the
the number of servers indicated. The specified credentials for the administrator referenced.
command will be issued against those servers.
User Response: Check the activity log and server
User Response: None. console for other messages about the cause of the
failure. Once the cause has been resolved, reissue the
ANR1700E Unable to resolve ’route information’ to command.
any server(s).
Explanation: The route information provided for this ANR1705W Ping for server ’server name’ was not able
command did not resolve to any server names or group to establish a connection.
names. Because of this, the command will not be Explanation: The ping command was unable to
issued. establish a connection to the server specified. This
System Action: None. could indicate a problem on the server issuing the ping,
a problem with the communication connection between
User Response: Examine the route information the two servers, or else it is a problem with the other
provided. Reissue the command providing correct route server.
information.
User Response: Check the activity log and server
console for messages that indicate a failure or problem
on the server issuing this command. Next, check the
communication connection between the two servers.

Also, check the server definition and password on both
ANR1710E Command.: Name Name not valid for this
the server issuing the command and the server
command.
specified. And finally, verify that the server specified is
running. 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
ANR1706I Ping for server ’server name’ was able to
server group name. The other case is where a server
establish a connection.
group name was specified for a command requiring a
Explanation: The ping command was able to establish server name.
a connection to the server specified.
User Response: Retry the command specifying the
User Response: Check the activity log and server proper name.
console for messages that indicate a failure or problem
on the server issuing this command. Next, check the
ANR1711E Error accessing the server or server
communication connection between the two srevers.
group name Name.
And finally, verify the operation of the server specified.
Explanation: A server operation attempted to access
the server name or server group name specified. An
ANR1707I Server information not complete,
error occurred while trying to access the information
crossdefine not allowed.
for this server name or server group name.
Explanation: The SERVERHLADDRESS,
System Action: The server opteration fails.
SERVERLLADDRESS or SERVERPASSWORD has not
been set for this server. These are required for the User Response: Review the activity log to try to
CROSSDEFINE option on the define server command. determine the cause of the failure. If a cause can not be
determines, please contact your local service
representative.
User Response: Use the QUERY STATUS command to
find what values need to be set. An authorized
ANR1712W Command routing not allowed from
administratormust issue the SET SERVERHLADDRESS,
server console.
SET and SERVERLLADDRESS or SET
SERVERPASSWORD command to set the missing Explanation: Command routing is not allowed from
values. the server console.
System Action: The command is not executed.
ANR1708I Define server for Server name failed
User Response: Reissue the command from an
because the crossdefine failed.
Administrative client.
Explanation: The define server command failed
because the crossdefine parameter was included, and
ANR1713I Command ’command’ issued against
the crossdefine was not successful.
server server name.
Explanation: The specified command has been sent to
User Response: Check this server, and the server the indicated server. The command is to terminate the
being defined for other messages indicating the reason specified server, no confirmation will be recieved.
for the failure.
ANR1709E Command.: Failure determining current
usage for server or group name Server
name. ANR1714W The password for administrator
administartor name has expired. The
Explanation: The specified command failed to
password for this administrator must be
determine the current use of the server name or server
updated on the configuration manager
group specified.
server server name.
Explanation: The password for the named
User Response: Retry the command. If it continues to administrator has expired, but the administrator is a
fail and the cause of the failure can not be determined, managed object on this server. The password must be
please contact your local service representative. updated on the named configuration manager server.
System Action: The administrator is allow access to
the server.

User Response: Change the administrator’s password
ANR1719E Storage pool storage pool name specified
on the named configuration manager server.
on the MOVE NODEDATA command is
not a valid pool name or pool type.
ANR1715E Event server cannot be deleted - it is
Explanation: If the source storage pool specified in the
currently active.
command is a primary storage pool, then the
Explanation: The event server cannot be deleted since destination storage pool specified must also be a
it is currently active for event logging. primary storage pool. If the source storage pool is a
copy storage pool, then the specified destination
System Action: The server does not delete the event storage pool must be the same storage pool as the
server entry. source storage pool.
User Response: In order to delete the event server, it System Action: The MOVE NODEDATA process fails.
must not be currently active for event logging. To stop
event logging to the event server issue END User Response: Provide a valid primary storage pool
EVENTLOGGING EVENTSERVER. Then reissue the name as the destination storage pool if the source pool
DELETE EVENTSERVER command. is a primary storage pool. If the source pool is a copy
storage pool do not specify a destination pool, or,
specify the same copy storage pool as the destination
ANR1716I Server cannot be crossdefined to itself, pool.
crossdefine not allowed.
Explanation: An attempt was made to crossdefine the ANR1720I A path from source name to destination
server to itself. name has been defined.
System Action: The command fails. Explanation: In response to the DEFINE PATH
User Response: None. command, the path from the source name to the
destination name has been defined in the server
database.
ANR1717E Command: Command failed -
Non-Compatible Filespace name types System Action: Server operation continues.
have been specified. User Response: None.
Explanation: A server command has been entered but
cannot be processed because Non-Compatible Filespace ANR1721I A path from source name to destination
name types have been specified. name has been deleted.
System Action: The server does not process the Explanation: In response to the DELETE PATH
command. command, the path from the source name to the
User Response: Specify compatible filespace names. destination name has been deleted in the server
Unicode to Unicode or Non-Unicode to Non-Unicode. database.
ANR1718E Command: Reconstruction of file User Response: None.
aggregates is supported only for
movement in which the source and
target storage pools are ANR1722I A path from source name to destination
sequential-access. name has been updated.
Explanation: The indicated command specifies that Explanation: In response to the UPDATE PATH
file aggregates be reconstructed during a move command, the path from the source name to the
operation for which reconstruction is not supported. destination name has been updated in the server
Aggregates are reconstructed only when both the database.
source storage pool and the target storage pool are
sequential-access.
command.
ANR1723E A path is already defined using source
User Response: Reissue the command without
name and destination name.
specifying that aggregates should be reconstructed.
Alternatively, specify a move operation involving Explanation: In response to the DEFINE PATH
transfer of data within a sequential-access storage pool command, the server determines that a path with the
or between two sequential-access storage pools. same source name and the same destination name
already exists in the server database.

ANR1730I Data mover mover name has been
User Response: Correct the source name or defined.
destination name and re-enter this command.
Explanation: The data mover has been defined in the
server database.
ANR1725E resource name is not defined.
Explanation: In response to the DEFINE PATH
command, a resource name was provided that has not
been defined.
ANR1731I Data mover mover name has been
deleted.
User Response: Define the source name or the
Explanation: The data mover has been deleted in the
destination name and re-enter this command.
server database.
ANR1726E A operation using the path from
sourcename to destname is currently being User Response: None.
used.
Explanation: This path was in use when the command ANR1732I Data mover mover name has been
was entered. The attributes of a path may not be updated.
changed while it is being used.
Explanation: The data mover has been updated in the
System Action: The server ignores the command. server database.
User Response: Wait until the operation using this System Action: Server operation continues.
path is complete, or cancel the operation using this
path, and then reissue the command.
ANR1733E Data mover mover name is already

ANR1727E A path from sourcename to destname does
defined.
not exist.
Explanation: A DEFINE DATAMOVER command was
Explanation: The path being updated or deleted does
entered for a data mover that already exists in the
not exist.
server database.
User Response: Reissue the command with a different
User Response: Use the UPDATE DATAMOVER to
source or destination name or define a new path.
change the attributes in this data mover. Otherwise use
a different data mover name.
ANR1728E The library libname is not a SCSI library.
Explanation: A drive that is to be used by a NAS data ANR1734E Data mover mover name is not defined.
mover must be attached to a SCSI library.
Explanation: An UPDATE DATAMOVER command
System Action: The server ignores the command. was entered for a data mover that does not exist in the
server database.
drive name. System Action: Server operation continues.
User Response: Correct the data mover name or use
ANR1729E A path using the data mover source name the DEFINE DATAMOVER command to define a new
still exists. data mover.
Explanation: In the DELETE DATAMOVER command,
the data mover name supplied is either the source or ANR1735E Data mover data mover is currently being
the destination in a path that still exists in the server used.
database.
Explanation: A data mover was in use when the
System Action: Server operation continues. command was entered. The attributes of a data mover
may not be changed while it is being used.
User Response: Delete the existing path and reissue
this command. System Action: The server ignores the command.
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. representative for assistance in resolving the problem.
ANR1736E Command: Parameter parameter length is ANR1751I Disk disk name has been defined.
too long.
Explanation: In response to the DEFINE DISK
Explanation: The specified server command has been command, the disk has been defined in the server
entered with a parameter that is longer in length than database.
the maximum allowed length.
User Response: Reissue the command and enter the
proper syntax.
ANR1752E Disk disk name is already defined.
Explanation: A DEFINE DISK command was entered
ANR1737E Command: Device name device specified
for a disk that already exists in the server database.
is invalid.
Explanation: The specified command has been entered
with an invalid device name. User Response: Use the UPDATE DISK command to
change the attributes of this disk. Otherwise, use a
System Action: The command failed.
different disk name.
User Response: Reissue the command with a valid
device name.
ANR1753E Disk disk name is currently being used.
Explanation: A disk was in use when the command
ANR1740E For the path defined from disk node
was entered. The attributes of a disk may not be
name disk name received lun actual lun
changed while it is being used.
from client, expected expected lun.
Explanation: A client attempted to backup the disk,
but the server path definition was different than that User Response: Wait until the operation using this
which was detected by the client. disk is complete, or cancel the operation using this
disk, and then reissue the command.
User Response: Correct the path definition from the
ANR1754E Disk disk name is not defined.
disk to a datamover.
Explanation: An UPDATE DISK command was
entered for a disk name that does not exist in the
ANR1741E For the path defined from disk node
server database.
name disk name received serial number
actual serial from client, expected expected System Action: Server operation continues.
serial.
User Response: Correct the disk name or use the
Explanation: A client attempted to backup the disk, DEFINE DISK command to define a new disk.
but the server path definition was different than that
which was detected by the client.
ANR1755I Disk disk name has been updated.
Explanation: In response to the UPDATE DISK
User Response: Correct the path definition from the command, the disk attributes have been updated in the
disk to a datamover. server database.
ANR1750E The server detected an internal error,
return code = return code. User Response: None.
Explanation: An unexpected error occured during

server operation. ANR1756I Disk disk name has been deleted.
System Action: Server operation continues. Explanation: In response to the DELETE DISK
command, the disk has been deleted in the server
User Response: Use the QUERY ACTLOG command database.
the cause of the data storage failure. If the failure can System Action: Server operation continues.
be found and resolved, retry the operation. If the User Response: None.
failure cannot be found, contact your service

ANR1757E A path using the disk disk name still ANR1761E Command: Command failed for node
exists. 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 Explanation: The indicated command failed because
the server database. required storage media is unavailable.
System Action: Server operation continues. System Action: The operation fails.
User Response: Delete the existing path using the User Response: Ensure that there are sufficient
DELETE PATH command and re-enter the DELETE volumes available for storing backups and that any
DISK command. 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.
ANR1762E Command: Command failed for node
Explanation: During a backup operation a path from
node name, filespace filespace name -
the disk cannot be found.
mount point unavailable.
Explanation: The indicated command failed because
User Response: Define a path from the disk to a sufficient mount points are not available.
datamover.
User Response: Ensure that sufficient mount points
ANR1759E Command: A device with SCSI
are available and working correctly. Correct the
datamover capabilities was not found in
problem and try the command again.
the system configuration for datamover
datamover name.
ANR1763E Command: Command failed - see
Explanation: The scsi address could not be
previous error messages.
determined for a device that is capable of performing
datamover operations. Explanation: The indicated server command has
failed. This message is always preceded by one or more
System Action: The requested operation fails.
other error messages which provide more detail about
User Response: Verify that the hardware that can why the command failed.
perform SCSI datamover operations is installed and
powered on.
User Response: Examine the previous error messages
to determine the source of the error. Use the QUERY
ANR1760E Command: Command failed for node
ACTLOG command to view the activity log and search
node name, filespace filespace name -
for messages if needed. Correct the problem and try the
destination storage pool storage pool was
command again.
skipped.
Explanation: The indicated command failed because
ANR1764E Command: Command failed - loadable
the destination storage pool was skipped. A storage
module module name is not available.
pool may be skipped because it does not have enough
available space, or because it has a MAXSIZE value Explanation: The indicated server command has failed
that is less than the size of the object to be inserted. because it requires the availability of the specified
loadable module, but the module is not loaded.
User Response: Ensure that the destination storage
pool is available, has an adequate MAXSIZE setting, User Response: Make sure the necessary loadable
and has adequate space. The MAXSIZE setting may be module is available for your platform. Not all modules
changed using the UPDATE STGPOOL command. are available on all platforms. If the module is available
Space may be added to the storage pool by checking in for your platform and is installed, contact your service
scratch volumes or defining new volumes in the representative for assistance.
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.

ANR1770E Processing for session session id found ANR1810E Eventlog command: Invalid receiver -
destination new destination. Expected receiverName.
current destination.
Explanation: An event logging command has been
Explanation: While processing a remote image entered which specifies an unknown event log receiver
operation, the specified session was working with the (maybe unknown just to this platform).
current destination. But the server received a client
System Action: The command is ignored for the
request with a new destination name.
invalid receiver. Any valid receivers specified are
System Action: Server operation continues. processed.
User Response: From the client, quit the current User Response: Reissue the command with the correct
remote image request. Reissue the request, if desired. receiver.
ANR1800E Missing or invalid EVENTLOG ANR1822I Event logging ended for the receiverName
command parameter. receiver.
Explanation: The event logging command issued Explanation: In response to an END
contains an invalid parameter, or is missing a required EVENTLOGGING command or because an error
parameter. occurred, event log records are no longer being output
to the specified receiver.
User Response: Reissue the command with the proper
parameters. User Response: None.
ANR1801E Eventlog command: Invalid event or event ANR1823I Event logging ended for all receivers.
class - Event or event class name.
Explanation: In response to an END
Explanation: An event logging command has been EVENTLOGGING command, event log records are no
entered which specifies an unknown event or event longer being output to any receiver.
class.
System Action: The command is ignored for the
invalid event or event class. Any valid events or classes
specified are processed.
ANR1824E Event logging is inactive for the
User Response: Reissue the command with the correct
specified receiver.
event or event class.
Explanation: An END EVENTLOGGING command
has been entered, but logging is not active for the
ANR1808E Unable to open event log file file spec for
specified receiver.
appending.
Explanation: The server cannot write to a file which
has been specified for event logging. User Response: If logging is desired, use the ENABLE
EVENT and BEGIN EVENTLOGGING commands to
System Action: No logging will be done to the file
activate event logging.
receiver.
User Response: Check the file for proper access
ANR1825I Event logging active for the receiverName
permissions, or specify a different file for logging.
receiver.
Explanation: In response to a BEGIN
ANR1809E Insufficient memory to activate event
EVENTLOGGING command, event log records are now
logging.
being output to the specified receiver.
Explanation: A BEGIN EVENTLOGGING command
has been entered, but the server has insufficient
memory available to activate logging. User Response: None.
User Response: If logging is required, make more
memory available to the server then restart the server.

ANR1826I Event logging active for all receivers. ANR1831I Event logging of client events ended for
ACTLOG receiver.
Explanation: In response to a BEGIN
EVENTLOGGING command, event log records are now Explanation: An END EVENTLOGGING command
being output to all receivers. has been entered for the activity log receiver.
System Action: None. System Action: The server no longer records client
events in the activity log. Server events continue to be
recorded in the activity log.
ANR1827E Eventlog command: No valid receiver
specified.
ANR1842E An error occurred on the receiverName
receiver.
entered, and no valid receivers were specified.
Explanation: An error occurred on the specified
receiver.
User Response: Reissue the command with the correct
System Action: The server no longer sends events to
receiver.
the receiver.
User Response: Issue a BEGIN EVENTLOGGING
ANR1828E Eventlog command: No valid event
command for the receiver to attempt to start logging
specified.
events to the receiver again.
entered and no valid events or event classes were
ANR1843I Event log receiver initialization in
specified.
progress.
Explanation: Initialization is starting for the eventlog
User Response: Reissue the command with the correct receivers.
events or event classes.
ANR1829E Eventlog command: Server events may not
be disabled for the activity log receiver.
ANR1844I Eventlog command command processed.
Explanation: A DISABLE EVENT command has been
entered for the activity log receiver. Explanation: The specified command was processed.
System Action: The command is ignored for the System Action: None.
activity log receiver. Any valid receivers specified are
User Response: If any previous messages indicate that
processed.
parts of the command failed, reissue the command for
User Response: Reissue the command with the correct those parts only.
receiver.
ANR1850E Circular event logging detected. The
ANR1830E receiverName receiver options not defined event server has previously handled
in the server options file. event Event number from Source trail. To
prevent looping, events which have
Explanation: A BEGIN EVENTLOGGING command
already been logged by the event server
has been entered for a receiver, but the required
are not sent again. Please correct the
receiver options were not specified in the server
situation causing circular logging to
options file.
avoid wasting system resources.
System Action: Logging is not started for the specified
Explanation: The server is attempting to log an event
receiver.
which has previously been handled by the event server
User Response: Enter the receiver options in the that is currently defined.
server options file and restart the server.
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
ANR1855E Failure validating protocol between
problem.
client and server for node node on
session session number
ANR1851E The source trail for server to server
Explanation: For a node having the ″VALIDATE
event logging has exceeded the
PROOTOCOL″ option set to either ″DATAONLY″ or
maximum length of Maximum sourcetrail
″ALL″, a validation error occurred. The transaction is
length bytes.
aborted and an indication is sent to the client indicating
Explanation: While attempting to log an event to the the failure.
event server, the server has found that the source trail
length is too long.
User Response: Verify network connections and
System Action: The server continues to try to send the
contact your service representative if this error persists.
event to the event server, but the source trail may be
truncated and appear something like:
ANR1856W Command: No volumes selected to
name1>...>namex>namey process.
where,
Explanation: No volumes were eligible for processing
name1 is the originator of the event.
by the AUDIT VOLUME command based upon the
... is where intervening server name(s)
parameters specified.
have been left off the source trail.
System Action: The AUDIT VOLUME process ends
without processing any volumes.
User Response: Most likely you are using very long
server names and/or have excessive hops from server User Response: Review the parameters specified for
to server. Either use shorter server names or change the command. If there was an error specifying a
your configuration to reduce the number of hops. parameter, re-issue the command with the parameter
corrected.
ANR1852E Unable to send header to TEC at TEC
server rc return code ANR1857I AUDIT VOLUME will start count repair
processes.
Explanation: A network error has occurred in
attempting to send the event header to the Tivoli Explanation: The AUDIT VOLUME command will
Enterprise Console. process a range of volumes due to one or more of the
following parameters having been specified:
FROMDATE, TODATE, or STGPOOL. The AUDIT
User Response: Verify network connections and VOLUME processing will start a process for each
contact your service representative if this error persists. volume that qualifies and process an AUDIT VOLUME
for each volume with FIX=YES specified.
ANR1853E Unable to send data to TEC at TEC System Action: One or more volumes are audited and
server rc return code inconsistent data is discarded.
Explanation: A network error has occurred in System Action: The administrator is asked whether to
attempting to send the event data to the Tivoli continue.
Enterprise Console.
User Response: Enter 'Y' to audit the volume or 'N' to
System Action: None. stop the process.
User Response: Verify network connections and
contact your service representative if this error persists. ANR1858I AUDIT VOLUME will start count
inspect processes.
ANR1854E Unable to flush data to TEC at TEC Explanation: The AUDIT VOLUME command will
server rc return code process a range of volumes due to one or more of the
following parameters having been specified:
Explanation: A network error has occurred in FROMDATE, TODATE, or STGPOOL. The AUDIT
attempting to flush data to the Tivoli Enterprise VOLUME processing will start a process for each
Console . volume that qualifies and process an AUDIT VOLUME
System Action: None. for each volume with FIX=NO specified.
User Response: Verify network connections and System Action: The administrator is asked whether to
contact your service representative if this error persists. continue.

User Response: Enter 'Y' to audit the volume or 'N' to
ANR2002E Missing closing quote character.
stop the process.
Explanation: A server command that contains a
quoted parameter has been entered, but a matching
ANR1859W Node node on session session id received
closing quote is missing.
CRC protocol validation information
when it is not configured to do so. System Action: The server ignores the command.
Explanation: The server received protocol validation User Response: Reissue the command with properly
information for the session and node specified. The matched quotes.
settings for this node are not configured to perform
protocol validation and any CRC information received
ANR2003E Illegal use of keyword parameter
will be ignored.
character (=) - parameter.
System Action: The server operation continues.
Explanation: A server command contains the
User Response: The server administrator should parameter shown followed by an equal sign (=), but the
evaluate whether or not this node should perform parameter is not a keyword parameter.
protocol validation. If so, issue the ″UPDATE NODE″
command and specify the VALIDATEPROTOCOL
option with the appropriate setting to enable protocol User Response: Reissue the command and enter the
validation. proper syntax.
If this is a TYPE=SERVER node for the target of a
virtual volume operation and protocol validation is not ANR2004E Missing value for keyword parameter -
desired, the server definition on the source server parameter.
should be updated with VALIDATEPROTOCOL=NO
set. Otherwise, if protocol validate is desired, the Explanation: A server command containing a keyword
SERVER type node on the target server should be parameter has been entered, but the value for the
updated using the ″UPDATE NODE″ command with parameter is missing.
″VALIDATEPROTOCOL=ALL″. System Action: The server ignores the command.
User Response: Reissue the command and supply a
ANR1999I Command completed successfully. value for the keyword parameter.
Explanation: Processing for the specified command
completed successfully. ANR2005E Keyword parameter character (=) may
System Action: Server processing continues. not be surrounded by blanks.
User Response: None. 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.
ANR2000E Unknown command - command.
Explanation: The specified command is not a valid
server command. User Response: Reissue the command without blanks
next to the equal sign.
User Response: Reissue the correct command. ANR2006E Activity log process was not started, the
default output stream cannot be opened.
ANR2001E Insufficient server memory to initiate Explanation: The process that monitors the default
command. (console) output stream and maintains the activity log
cannot access that output stream.
Explanation: A command has been entered, but the
server cannot obtain enough internal memory to System Action: The server does not update the
process the command. activity log.
System Action: The server ignores the command. User Response: Contact your service representative.
server. For details, issue HELP MEMORY to display the ANR2007E Activity log process was not started, due
information online or see “Appendix A. Allocating to an internal error.
Explanation: The process that monitors the default
(console) output stream and maintains the activity log
cannot start due to a server internal error.

System Action: The server does not update the
ANR2011W Server is out of DB space in adding
activity log.
entries to the Activity Log. Console
User Response: Examine the server messages issued messages will not be logged until DB
prior to this message to determine the source of the space is available.
cannot update the activity log due to a lack of database
representative.
space.
System Action: The server does not update the
ANR2008E Activity log process has stopped -
activity log.
database transaction could not be
started. User Response: An authorized administrator can issue
the DEFINE DBVOLUME command to add volumes
for use by the database, and can issue the EXTEND DB
cannot continue due to a server transaction failure. This
may be a memory shortage error.
System Action: The server stops updating the activity
ANR2012W Activity log process has encountered
log.
unexpected table data output in the
User Response: Allocate additional storage to the default output stream.
has detected invalid data in the console stream.
ANR2009E Activity log process has stopped -
log.
database error.
cannot continue due to a server database error. ANR2013E The activity log process has encountered
unexpected output data in the console
output stream. The process will be
log.
restarted.
Explanation: The process that monitors console output
and maintains the activity log has detected invalid data
ANR2010W Server is out of LOG space in adding (unknown data type) in the console stream.
entries to the Activity Log. Console
System Action: The server restarts the activity log
messages will not be logged until LOG
recording process. While the process is restarting, the
space is available.
server may not be able to record some console
Explanation: The process that monitors the default messages in the activity log.
User Response: The server may be low on available
cannot update the activity log due to a lack of recovery
memory. Allocate additional storage to the server. For
log space.
System Action: The server does not update the information online or see “Appendix A. Allocating
activity log. Additional Server Memory”.

the DEFINE LOGVOLUME command to add volumes ANR2014E Activity log pruning process could not
for use by the log, and can issue the EXTEND LOG be started, due to an internal error.
Explanation: The process that removes expired records
volumes are used.
from the server activity log cannot begin execution due
to a server internal error.
System Action: The server does not prune the activity
log.

ANR2020E Command: Invalid parameter - parameter.
be isolated and resolved, contact your service Explanation: The specified server command has been
representative. entered with an invalid parameter.
ANR2015E Activity log failure - database
transaction could not be started.
proper syntax.
from the server activity log has failed due to a database
ANR2021E Command: Missing subcommand
transaction failure, which may be a memory shortage
keyword.
error.
Explanation: The specified server command has been
System Action: The server ends activity log pruning.
entered without a valid subcommand (second
User Response: Allocate additional storage to the parameter).
Additional Server Memory”. User Response: Reissue the command and enter the
proper syntax.
ANR2016E Activity log failure - database error.
ANR2022E Command: One or more parameters are
missing.
from the server activity log has failed due to a server
database error. Explanation: The specified server command has been
entered without all required parameters.
System Action: The server ends activity log pruning.
proper syntax.
ANR2017I Administrator Administrator Name issued
command: Command
ANR2023E Command: Extraneous parameter -
Explanation: This message records the fact that the
parameter.
named administrator issued the command specified.
The messages is issued and logged to provide an audit Explanation: The specified server command contains
trail for administrative commands. more positional parameters than is allowed.
System Action: Server operation continues System Action: The server ignores the command.
User Response: None. User Response: Reissue the command and enter the
proper syntax.
ANR2018E Administrator Command: Unicode
conversion failed for argument Command ANR2024E Command: Too many parameters
Argument specified.
Explanation: The specified command argument could Explanation: The specified server command contains
not be converted to a Unicode string. Conversion can more positional parameters than is allowed.
fail if the string includes characters that are not
available in the server code page, or if the server has a System Action: The server ignores the command.
problem accessing system conversion routines. User Response: Reissue the command and enter the
System Action: Server command fails proper syntax.
User Response: Make sure that the server’s locale is

properly configured. ANR2025E Command: Command failed - server
ANR2019I Command: No nodes updated. Explanation: A server command, which has a

requirement to start a server thread, has been entered
Explanation: An UPDATE NODE command has been but cannot be executed because no server thread is
entered, but no objects were updated. available.
System Action: None. System Action: The command is not executed.
User Response: None. User Response: Reissue the command. If the

command fails with the same error, wait for server
ANR2030E Commit not accepted; transaction failed.
activity to decrease and try again.
Explanation: A command that is part of the current
transaction has failed; therefore, a COMMIT command
ANR2026E Command: Command failed - sufficient
cannot be processed.
server memory is not available.
Explanation: A server command has been entered but
COMMIT command.
cannot be processed because sufficient memory is not
available to the server. User Response: Stop the administrative session,
restart it, and try the command again. If this problem
persists, contact your service representative.
command.
ANR2031E Command: At least one attribute must be
specified for update.
Additional Server Memory”. Explanation: The specified UPDATE command has
been entered, but no attributes have been specified for
updating.
server recovery log space is not System Action: The server ignores the command.
available.
User Response: Reissue the UPDATE command with
Explanation: A server command has been entered but one or more attributes to be updated.
cannot be processed because sufficient recovery log
space is not available.
ANR2032E Command: Command failed - internal
System Action: The server does not process the server error detected.
command.
Explanation: An internal error has occurred during an
User Response: An authorized administrator can issue attempt to process a server command. This message
the DEFINE LOGVOLUME command to add volumes always accompanies another error message and
for use by the log, and can issue the EXTEND LOG provides more detail about that error.
volumes are used.
command.
server database space is not available.
Explanation: A server command has been entered but activity log and search for messages. If the error cannot
cannot be processed because sufficient database space be isolated and resolved, contact your service
is not available. representative.
command. ANR2033E Command: Command failed - lock
conflict.
the DEFINE DBVOLUME command to add volumes Explanation: A server command that requires the
for use by the database, and can issue the EXTEND DB server to lock a system resource has been entered. The
command to extend the size of the database so that the command cannot be executed because the resource is
new volumes are used. already in use by another command or process.
ANR2029E Command: Transaction failed; command command.
not executed.
User Response: Try the command again at a later
Explanation: A command that is part of the current time.
transaction has failed; therefore, any additional
commands fail.
ANR2034E Command: No match found using this
System Action: The server does not process the criteria.
command.
Explanation: The specified command has been
User Response: Stop the administrative session, entered, but no objects that match the criteria can be
restart it, and try the command again. If this problem found.

User Response: None. User Response: If necessary, reissue the command. If
the command fails with the same error, wait for server
activity to decrease and try again.
ANR2035E Command: Administrator administrator
name is not authorized to issue this
command. ANR2039E Command: Process could not be started -
the indicated command, but this administrator does not Explanation: A background process cannot be started
have the proper authority necessary to run the for the indicated command because an internal error
command. Note: This message can be issued as a result has occurred.
of the server option REQSYSAUTHOUTFILE YES being
System Action: A new process is not started to
in effect.
execute this command. If other processes have been
System Action: The server does not process the started for this command, these processes may execute
command. successfully.
User Response: Examine previous messages for any User Response: Examine the server messages issued
additional information. Issue the command from a prior to this message to determine the source of the
properly authorized administrator ID, or contact the error. Issue the QUERY ACTLOG command to view the
system administrator to have additional authority activity log and search for messages. If the error cannot
granted to the current administrator ID. be isolated and resolved, contact your service
representative.
ANR2036E Command: Process could not be started -
sufficient memory is not available. ANR2040W This command attempts to restore all
files in storage pool storage pool which
Explanation: A background process cannot be started
have previously been found to be
for the indicated command because sufficient memory
damaged or which reside on a volume
is not available to the server.
with access mode ″destroyed″; existing
System Action: A new process is not started to references to files in storage pool storage
execute this command. pool will be deleted from the database
after the files have been restored.
server. For details, issue HELP MEMORY to display the Explanation: Issuing the RESTORE STGPOOL
information online or see “Appendix A. Allocating command will result in deletion of existing files in the
Additional Server Memory”. 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
ANR2037E Command: Process could not be started - files on the volume have been restored to another
lock conflict. location, the destroyed volume will be deleted from the
Explanation: A background process cannot be started database.
for the indicated command because a required system System Action: The administrator is asked whether to
resource is already locked by another command or continue.
process.
User Response: Enter 'Y' to restore the storage pool,
System Action: A new process is not started to 'N' otherwise.
execute this command. If other processes have been
started for this command, these processes may execute
successfully. ANR2041W This command attempts to restore all
files in storage pool storage pool which
User Response: If necessary, try the command again reside on one of the volumes specified
at a later time. in the command; existing references to
files on these volumes will be deleted
ANR2038E Command: Process could not be started - from the database after the files have
server thread resource not available. been restored.
Explanation: A background process cannot be started Explanation: Issuing the RESTORE VOLUME
for the indicated command because no server thread is command causes the access mode of the specified
available. volumes to be updated to destroyed. Existing files will
be deleted from the specified volumes after these files
System Action: A new process is not started to have been restored from a copy storage pool. If a
execute this command. If other processes have been volume with access mode destroyed becomes empty
started for this command, these processes may execute because all files on the volume have been restored to
successfully.

another location, the destroyed volume will be deleted User Response: None.
from the database.
System Action: The administrator is asked whether to ANR2047E Command: Optionset optionset name is
continue. already defined.
User Response: Enter 'Y' to restore the volumes, 'N' Explanation: A DEFINE OPTIONSET command has
otherwise. been entered that specifies an optionset name already
defined to the server.
ANR2042E Command: Copied parameter not valid System Action: The server does not process the
for copy storage pool volume. command.
Explanation: The QUERY CONTENT server command User Response: To define the optionset, reissue the
has been entered with an invalid parameter. COPIED is command and specify a different optionset name.
not a valid parameter when the volume specified
belongs to a copy storage pool.
ANR2048I Command: Optionset optionset name
System Action: The server ignores the command. deleted.
User Response: Reissue the command without the Explanation: The requested option set has been
COPIED parameter. deleted from the system in response to a DELETE
OPTIONSET command.
ANR2043E Command: WAIT parameter not allowed System Action: None.
from server console.
Explanation: The WAIT parameter is not allowed for
commands issued from the server console.
ANR2049E Command: Optionset optionset name is not
System Action: The command is not executed. defined.
User Response: Either reissue the command without Explanation: The command shown specifies an
the WAIT parameter or else reissue the command from optionset that is not defined in the server.
an administrator using an Administrative Client.
command.
ANR2044E Command: Invalid option’s value -
Option’s value.
Explanation: The set option command has been
ANR2050I Command: Option option name defined in
entered with an invalid value.
optionset option set name.
Explanation: The requested option has been added to
command.
the specified optionset in response to a DEFINE
User Response: Reissue the command with a valid OPTIONSET command.
value.
ANR2045E Command: An error (error code) occurred
during a write operation.
ANR2051E Command: Option option name, sequence
Explanation: The server detects an error while
number sequence number is already
attempting a write operation.
defined in optionset option set name.
Explanation: The requested option already exists in
User Response: Refer to the other displayed messages the optionset specified by the DEFINE CLIENTOPT
to determine why the write operation has failed. command.
ANR2046I optionset name: Optionset optionset name command.
defined.
Explanation: The requested option set has been added
to the system in response to a DEFINE OPTIONSET
command.

ANR2052E Command: Option option name, sequence ANR2057E Command: Invalid option value - option
number sequence number is not defined value.
in optionset option set name.
Explanation: The requested option is not defined in option value.
the optionset specified by the DELETE CLIENTOPT
command.
command.
command.
option value.
ANR2058W Command: Options file Filespec not found
ANR2053I Command: Option option name, sequence - user needs to update the file manually.
number sequence number, has been
Explanation: The server options file cannot be opened
deleted from optionset option set name.
or found.
Explanation: The requested option has been deleted
System Action: The command is processed but the
from the specified optionset in response to a DELETE
option is not updated in the options file.
CLIENTOPT command.
User Response: Use a text editor to update the server
options file if the user wants to use this value when the
User Response: None. 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.
ANR2054I Command: Optionset optionset name
updated.
ANR2059W Command: Error occurs when writing to
Explanation: The requested option set has been
Filespec - user needs to update the file
updated in the system in response to an UPDATE
manually.
OPTIONSET command.
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.
ANR2055I Command: Optionset source optionset name
User Response: Use a text editor to update the server
copied to optionset target optionset name.
options file if the user wants to use this value when the
Explanation: This message is displayed in response to server restarts later. If the user does not update the file,
the COPY OPTIONSET command. The optionset the current value in the options file will be used when
named source optionset name has been copied to the the server restarts.
optionset named target optionset name.
System Action: Server operation continues. ANR2060I Node node name registered in policy
domain domain name.
User Response: None. The requested option set has
been added to the system in response to a COPY Explanation: The requested backup-archive node has
OPTIONSET command. been added to the system in response to a REGISTER
NODE command and has been assigned to the policy
domain indicated.
ANR2056E Command: Invalid option name - option
name. Retry using the full optionname. System Action: None.
Explanation: The command shown specifies an invalid User Response: None.

option name.
System Action: The server does not process the ANR2061I Node node name removed from policy
command. domain domain name.
User Response: Reissue the command with a valid Explanation: In response to a REMOVE NODE
option name. command, the requested backup-archive node has been
removed from the system.

ANR2062I Node node name renamed to new node
name. User Response: None.
Explanation: In response to a RENAME NODE
command, the requested backup-archive node has been ANR2069I Administrator administrator ID removed.
renamed to the new name shown.
Explanation: In response to a REMOVE ADMIN
System Action: None. command, the requested administrator ID has been
removed from the system.
ANR2063I Node node name updated. User Response: None.
Explanation: One or more attributes of a
backup-archive node have been updated by an ANR2070I Administrator administrator ID renamed
UPDATE NODE command. to new administrator ID.
System Action: None. Explanation: In response to a RENAME ADMIN
command, the requested administrator ID has been
changed to the new name shown.
ANR2064I Node node name locked.
Explanation: In response to a LOCK NODE command,
the indicated backup-archive node has been locked.
ANR2071I Administrator administrator ID updated.
Explanation: One or more attributes of an
administrative user have been updated by an UPDATE
ADMIN command.
ANR2065I Node node name is already locked.
Explanation: The indicated backup-archive node
referenced in the LOCK NODE command is already
locked.
ANR2072I Administrator administrator ID locked.
Explanation: In response to a LOCK ADMIN
command, the indicated administrator ID has been
locked.
ANR2066I Node node name unlocked.
Explanation: In response to an UNLOCK NODE
command, the indicated backup-archive node is
unlocked.
ANR2073I Administrator administrator ID is already
locked.
Explanation: The indicated administrator ID
referenced in the LOCK ADMIN command is already
ANR2067I Node node name is already unlocked. locked.
Explanation: The indicated backup-archive node System Action: None.
referenced in the UNLOCK NODE command is not
locked.
ANR2074I Administrator administrator ID unlocked.
Explanation: In response to an UNLOCK ADMIN
command, the indicated administrator ID is unlocked.
ANR2068I Administrator administrator ID registered.
Explanation: In response to a REGISTER ADMIN
command, the requested administrator ID has been
added to the system.

ANR2075I Administrator administrator ID is already
unlocked. User Response: None.
Explanation: The indicated administrator ID
referenced in the UNLOCK ADMIN command is not ANR2081I Analyst privilege granted to
locked. administrator administrator ID.
System Action: None. Explanation: In response to a GRANT AUTHORITY
command, analyst privilege class has been granted to
the indicated administrator.
ANR2076I System privilege granted to
administrator administrator ID. User Response: None.
Explanation: In response to a GRANT AUTHORITY
command, system privilege class has been granted to ANR2082I Operator privilege granted to
the indicated administrator. administrator administrator ID.
System Action: None. Explanation: In response to a GRANT AUTHORITY
command, operator privilege class has been granted to
the indicated administrator.
ANR2077I Unrestricted policy privilege granted to
administrator administrator ID. User Response: None.
command, unrestricted policy privilege has been ANR2083I System privilege revoked for
granted to the indicated administrator. administrator administrator ID.
System Action: None. Explanation: In response to a REVOKE AUTHORITY
command, system privilege class has been revoked
from the indicated administrator.
ANR2078I Restricted policy privilege granted to
administrator administrator ID - policy User Response: None.
domain domain name.
Explanation: In response to a GRANT AUTHORITY ANR2084I Policy privilege revoked for
command, restricted policy privilege for the specified administrator administrator ID.
policy domain has been granted to the indicated
administrator. Explanation: In response to a REVOKE AUTHORITY
command, policy privilege class for all policy domains
System Action: None. has been revoked from the indicated administrator.
ANR2079I Unrestricted storage privilege granted to
administrator administrator ID.
ANR2085I Restricted policy privilege revoked for
Explanation: In response to a GRANT AUTHORITY administrator administrator ID - policy
command, unrestricted storage privilege has been domain domain name.
granted to the indicated administrator.
Explanation: In response to a REVOKE AUTHORITY
System Action: None. command, restricted policy privilege for the specified
policy domain has been revoked from the indicated
administrator.
ANR2080I Restricted storage privilege granted to
administrator administrator ID - storage User Response: None.
pool storage pool name.
command, restricted storage privilege for the specified
storage pool has been granted to the indicated
administrator.

ANR2086I Storage privilege revoked for
ANR2092I Password expiration period set to
number of days days.
command, storage privilege class for all storage pools
has been revoked from the indicated administrator. 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.
ANR2087I Restricted storage privilege revoked for
administrator administrator ID - storage
pool storage pool name. ANR2093I Registration parameter set to registration
method.
command, restricted storage privilege for the storage Explanation: Backup-archive node registration has
pool indicated has been revoked from the indicated been set to the method indicated with the SET
administrator. REGISTRATION command.
ANR2088I Analyst privilege revoked for ANR2094I Server name set to server name.
Explanation: The name that the server displays and
Explanation: In response to a REVOKE AUTHORITY communicates to backup-archive nodes has been set to
command, analyst privilege class has been revoked the value indicated with the SET SERVERNAME
from the indicated administrator. command.
ANR2089I Operator privilege revoked for ANR2095I Authentication parameter set to value.
Explanation: The requirement for a node or
Explanation: In response to a REVOKE AUTHORITY administrator to enter a password when establishing a
command, operator privilege class has been revoked session with the server has been turned on or off as
from the indicated administrator. indicated with the SET AUTHENTICATION command.
ANR2090I Activity log retention period set to ANR2096I Server now enabled for backup/archive
number of days days. client access.
Explanation: The number of days that activity records Explanation: The server has been made available for
are kept in the server activity log has been set to the use by backup-archive clients with the ENABLE
value indicated with the SET ACTLOGRETENTION command.
command.
ANR2097I Server now disabled for backup/archive
ANR2091I Accounting parameter set to value. client access.
Explanation: Accounting record generation has been Explanation: The server has been made unavailable
turned on or off as indicated with the SET for use by backup-archive clients with the DISABLE
ACCOUNTING command. command.

ANR2098E Command: Invalid URL specification - ANR2104I Activity log process restarted - recovered
url. from an insufficient space condition in
the Log or Database.
Explanation: The specified URL is too long.
Explanation: The process that records data in the
server activity log has failed because of insufficient
User Response: Reissue the command and enter a space in the server recovery log or database; space is
shorter URL value now available and the process is again recording data.
System Action: Activity logging resumes.
ANR2099I Administrative userid admininstrator
name defined for OWNER access to node
node name.
ANR2105W Command: Node was registered in excess
Explanation: An administrator with the specified
of license terms - node registration will
name was created having OWNER access to the client
fail after 120% of the licensed quantity
node. This administrator is created for accessing the
of nodes have been registered.
client node from an interactive interface.
Explanation: The server has detected the addition of a
node in excess of the terms under which the server is
User Response: None. licensed. The REGISTER NODE command will fail after
120% of the licensed number of nodes have been
registered.
ANR2100I Activity log process has started.
Explanation: The automatic server process that
removes expired server activity log records has begun User Response: Use the QUERY LICENSE command
processing. to determine the license terms that are no longer in
compliance. You may remove nodes to reduce the
System Action: None. number of registered nodes or purchase additional
User Response: None. client node connections. If additional nodes have been
purchased, issue the AUDIT LICENSES command to
resynchronize the server configuration with license
ANR2101I Activity log process stopped, activity log terms.
retention set to 0.
Explanation: A SET ACTLOGRETENTION command ANR2106I Server HALT command: Quiescing
has set the retention period to zero days. As a result, database update activity.
activity logging stops.
Explanation: The server is quiescing transactions that
System Action: The activity log process stops update the database so that the database is in a
recording console output in the server activity log. consistent state when the server is halted. This action
User Response: None. occurs when HALT QUIESCE is specified to halt the
server with the database in a consistent state.
ANR2102I Activity log pruning started: removing System Action: When database update transaction
entries prior to date time. activity has been stopped, the server program ends.
Explanation: Server activity log records older than the User Response: None.
date and time indicated are being removed from the
activity log. ANR2107I Server HALT command: Database update
System Action: None. activity is now quiesced.
User Response: None. Explanation: The server has stopped all database
update transaction activity. This action occurs when
HALT QUIESCE is specified to halt the server with the
ANR2103I Activity log pruning completed: number database in a consistent state.
of records records removed.
System Action: The server program ends.
Explanation: All expired (older than the log archive
retention value) server activity log records have been User Response: None.
removed; the number of records deleted is shown.

ANR2108I Server HALT command: Reattempting to
quiesce database update activity.
ANR2112E Command: Volume volume name is not in
Explanation: The server is quiescing transactions that
a primary storage pool.
update the database so that the database is in a
consistent state when the server is halted. The previous Explanation: The command indicated specifies the
attempt at quiescing database activity failed because of name of a volume that does not belong to a primary
the current transaction load on the server. The quiesce storage pool. The command syntax requires that a
operation is being reattempted. This action occurs when volume in a primary storage pool be specified.
HALT QUIESCE is specified to halt the server with the
database in a consistent state. System Action: The server does not process the
command.
System Action: When database update transaction
activity has been stopped, the server program ends. User Response: Reissue the command with a volume
in a primary pool.
ANR2113E Command: Volume volume name does not

ANR2109I Server HALT command: Database update belong to the same storage pool (storage
transaction activity could not be pool name) as previously listed volumes.
successfully quiesced.
Explanation: The indicated command accepts a list of
Explanation: After repeated attempts, server database one or more volumes which belong to the same storage
update transaction activity could not be quiesced. The pool. The named volume does not belong to the same
server is not halted with the HALT QUIESCE storage pool as the previously listed volumes.
command. Attempts to quiesce database update
transaction activity can fail if heavy transaction load is System Action: The server does not process the
on the server when a HALT QUIESCE command is command.
entered. User Response: Issue the command with a list of
System Action: Server operation continues. volumes that belong to the same storage pool.
User Response: You may disable the server, cancel all

client sessions accessing the server, cancel all processes, ANR2114I Command: Access mode for volume
and reenter the HALT QUIESCE command to stop volume name updated to ″destroyed″.
server processing. The HALT command may also be Explanation: A RESTORE VOLUME command has
used to stop server processing without quiescing updated the access mode of the indicated volume to
database transaction update activity. Server recovery destroyed.
logic will be used when the server is restarted to
reconcile database transaction activity. System Action: Restore processing continues.
ANR2110I Command started as process process ID.
Explanation: A background process has been started ANR2115E Command: Access mode for volume
to service the command command. The background volume name cannot be changed to
process is defined as process process ID. ″destroyed″ - volume is still online.
System Action: The server processes the indicated Explanation: A RESTORE VOLUME command cannot
command. change the access mode of the indicated volume to
destroyed because the volume is still online.
background process, use the QUERY PROCESS System Action: The server does not process the
command. To cancel the background process, use the command.
CANCEL PROCESS command. Use the process ID User Response: Issue the VARY OFFLINE command,
number to specify this process. and reissue the RESTORE VOLUME command.
ANR2111W Command: No data to process. ANR2116E Command: Access mode for volume
Explanation: The indicated command does not have volume name cannot be changed to
any data to process. This can occur if the command ″destroyed″ - volume does not belong to
specifies an empty volume or pool. The command ends a primary storage pool.
without starting a background process. Explanation: The access mode for the indicated
System Action: None. 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
ANR2121W ATTENTION: More than amount changed
not changed.
unit megabytes, gigabytes or terabytes of the
User Response: None. database has changed and the last
database backup was more than hours
name hours ago. Use the BACKUP DB
ANR2117E Command: Access mode for volume command to provide for database
volume name cannot be changed to recovery.
″offsite″ - volume either does not belong
to a copy storage pool or from a device Explanation: The server issues this warning when a
class of DEVTYPE=SERVER. significant amount of database change activity has
occurred and the server database has not been backed
Explanation: The access mode for the indicated up.
volume cannot be changed to offsite because the
volume either does not belong to a copy storage pool System Action: Server operation continues.
or is of a device class with a DEVTYPE of SERVER.
User Response: To provide for server database
System Action: The access mode for this volume is recovery should a hardware or software problem affect
not changed. your database, use the BACKUP DB command to back
up the database.
ANR2122E command name: The DOMAINS

ANR2118E Storage pool storage pool name specified parameter cannot be specified when the
on the MOVE DATA command is not a NODES parameter is specified.
valid poolname and or pooltype for
volume volume name. Explanation: Both the NODES and DOMAINS
parameters were specified. The NODES parameter may
Explanation: If the volume belongs to a primary be specified, or the DOMAINS parameter may be
storage pool, then the storage pool specified must also specified, but both should not be specified at the same
be a primary storage pool. If the volume belongs to a time.
copy storage pool, then the specified storage pool must
be the same storage pool as that of the volume. System Action: The command fails.
System Action: The MOVE DATA process fails. User Response: Reenter the command specifying
either the NODES parameter or the DOMAINS
User Response: Provide a valid primary storage pool parameter, but not both.
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. ANR2123E command name: The NODES parameter
cannot be specified when the
DOMAINS parameter is specified.
ANR2119I The Option option has been changed in
the options file. Explanation: Both the NODES and DOMAINS
parameters were specified. The NODES parameter may
Explanation: The option is updated in the server be specified, or the DOMAINS parameter may be
options file. specfied, but both should not be specified at the same
System Action: Server continues. time.
User Response: None. System Action: The command fails.

User Response: Reenter the command specifying
ANR2120E Command: Invalid platform name - either the NODES parameter or the DOMAINS
platform name. parameter, but not both.

platform name. ANR2124E command name: Invalid Client authority
specified: authority.
command. Explanation: An invalid client authority was specified
in a GRANT AUTHORITY or REVOKE AUTHORITY
User Response: Reissue the command with a valid command when the CLASS=NODE parameter was
platform name. specified.
valid client authority.

ANR2125I command name: Administrator ANR2130S Early Product Version has Expired.
administrator name was granted OWNER Server is HALTing.
authority for client client name.
Explanation: This server is pre-release version of the
Explanation: The named administrator was granted server. The pre-release version’s expiration date has
OWNER authority over the named client node as the been reached.
result of a GRANT AUTHORITY command.
System Action: The server halts.
User Response: Install the product version of the
User Response: None. server.
ANR2126I command name: Administrator ANR2131I Server password set.

administrator name was granted ACCESS
Explanation: The password that the server uses to
authority for client client name.
allow other servers to communicate with it has been
Explanation: The named administrator was granted set, changed or removed with the SET
ACCESS authority over the named client node as the SERVERPASSWORD command.
result of a GRANT AUTHORITY command.
ANR2132I Server hladdress set to hladdress.
ANR2127I command name: Owner authority for node
Explanation: The high level address that other servers
client node was revoked for administrator
use to communicate with this server has been set to the
administrator.
value indicated with the SET SERVERHLADDRESS
Explanation: OWNER authority over the named client command.
node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command.
ANR2133I Server lladdress set to lladdress.
Explanation: The low level address that other servers
ANR2128I command name: Access authority for node
use to communicate with this server has been set to the
client node was revoked for administrator
value indicated with the SET SERVERLLADDRESS
administrator.
command.
Explanation: ACCESS authority over the named client
node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command. User Response: None.
ANR2134I Server url set to url.
Explanation: The url that other servers use to
communicate with this server has been set to the value
ANR2129I Administrative userid admininstrator
indicated with the SET SERVERURL command.
name defined ONLY for authority over
node node name has been removed. System Action: None.
Explanation: The specified administrator has been User Response: None.
removed because the client node was removed and the
administrator onyly had OWNER access to the
specified node. ANR2135I Crossdefine set to state.
System Action: None. Explanation: The ability for another server to

automatically define itself to this server has been
User Response: None. turned on or off as indicated with the SET
CROSSDEFINE command.

ANR2136I Administrator administrator name already ANR2141E Command: Invalid password expiration
has POLICY access for domain policy period - days value.
domain name.
Explanation: A SET PASSEXP command has been
Explanation: The named administrator already has entered that specifies an invalid days value.
POLICY authority over the named policy domain. An
attempt to grant client authority over this domain is
command.
ignored.
User Response: Reissue the command with a
System Action: The policy domain is skipped.
password expiration period.
ANR2142E Command: Invalid server name - server
ANR2137I Administrator administrator name already name.
has POLICY access for domain policy
Explanation: A SET SERVERNAME command has
domain name to which node node name
been entered that specifies an invalid server name.
belongs.
Explanation: The named administrator already has
command.
POLICY authority over the named policy domain. An
attempt to grant client authority for a client in this User Response: Reissue the command with a valid
domain is ignored. server name.
System Action: The client is skipped.
ANR2143E Command: Invalid node name - node
name.
ANR2138I Minimum password length set to length.
node name.
Explanation: The minimum length of a password a
node or administrator may send to the server is
command.
indicated with the SET MINPWLENGTH command.
node name.
ANR2144E Command: Invalid password - password.
ANR2139E Command: The value supplied for the
minimum password length is not valid -
node password.
length.
Explanation: A SET MINPWLENGTH command has
command.
been entered that specifies a value for the length is not
valid. Valid values are from 0 to 64, inclusive. User Response: Reissue the command with a valid
password.
command.
ANR2145E Command: Contact information exceeds
maximum characters characters.
value.
Explanation: A REGISTER NODE or REGISTER
ADMIN command has been entered that specifies a
ANR2140E Command: Invalid activity log retention
contact information value that is too long. The
period - retention value.
maximum valid length is shown in the command.
Explanation: A SET ACTLOGRETENTION command
has been entered that specifies an invalid log retention
command.
period.
User Response: Reissue the command with less
contact information.
command.
retention period.

ANR2146E Command: Node node name is not ANR2151E Command: Administrator administrator ID
registered. is currently accessing the server.
Explanation: The command shown specifies a node Explanation: An UPDATE ADMIN or REMOVE
that is not registered with the server. ADMIN command has been entered that specifies an
administrator ID that is having an active session with
the server.
command.
command.
User Response: Reissue the command at a later time,
ANR2147E Command: Node node name is already
or if necessary, cancel the current session and reissue
registered.
the command.
Explanation: A REGISTER NODE command has been
entered that specifies a node name already registered
ANR2152E Command: Inventory references still exist
with the server.
for node node name.
Explanation: A REMOVE NODE command has been
command.
entered for a node for which the server is still storing
User Response: To register the node, reissue the backup or archive data, or both.
command and specify a different node name.
command.
ANR2148E Command: Administrator administrator ID
User Response: To remove the node, delete all of its
is not registered.
file spaces from the server and reissue the command.
Explanation: The command shown specifies an
administrator ID that is not registered with the server.
ANR2153E Command: Invalid file space name -
System Action: The server does not process the filespace name.
command.
User Response: None. entered with a file space name that is longer than
allowed.
ANR2149E Command: Administrator administrator ID System Action: The server does not process the
is already registered. command.
Explanation: A REGISTER ADMIN command has User Response: Reissue the command with a valid file
been entered that specifies an administrator ID already space name.
registered with the server.
System Action: The server does not process the ANR2154E Command: Invalid administrator name -
command. administrator ID.
User Response: To register the administrator, reissue Explanation: The command shown specifies an invalid
the command and specify a different administrator ID. administrator ID.
ANR2150E Command: Node node name is currently command.
accessing the server.
Explanation: The command shown specifies a node administrator ID.
that has an active session with the server.
System Action: The server does not process the ANR2155E Command: Invalid privilege class -
command. privilege class.
User Response: Reissue the command at a later time, Explanation: A command specifies an invalid
or if necessary, cancel the current session and reissue administrative privilege class.
the command.
command.
privilege class.

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

specified for unrestricted storage administrator ID is the only system
administrator administrator ID. administrator.
Explanation: A REVOKE AUTHORITY command has Explanation: A REMOVE ADMIN or REVOKE
been issued to revoke an administrator’s storage AUTHORITY command has been issued to remove or
authority over a specific storage pool, but the revoke the authority of the last administrator who had
administrator has unrestricted storage authority. system authority.
command. command.
User Response: None. User Response: To remove or revoke this ID, grant
system authority to another administrator ID before
reissuing the command.
ANR2160E Command: No new privileges granted to
ANR2165E Command: Invalid begin date - date.
been issued to grant authority to an administrator ID, Explanation: A QUERY ACTLOG command has been
but the administrator already has all privileges entered that specifies an invalid begin date as a search
specified. criteria.
command. command.

ANR2171E Command: Invalid time range - Begin:
begin date.
date time End: date time.
Explanation: A QUERY ACTLOG command has been
ANR2166E Command: Invalid begin time - time.
entered that specifies an invalid beginning and ending
Explanation: A QUERY ACTLOG command has been date/time range. This error can occur when the
entered that specifies an invalid begin time as a search beginning date/time is not before the ending
criteria. date/time.
command. command.
User Response: Reissue the command with a valid User Response: Reissue the command with a valid
begin time. date/time range.
ANR2167E Command: Invalid end date - date. ANR2172E Command: No matching administrators.
Explanation: A QUERY ACTLOG command has been Explanation: The command shown specified an
entered that specifies an invalid end date as a search administrator ID that does not match any administrator
criteria. registered with the server.
System Action: The server does not process the System Action: The command is not executed.
command.
User Response: If desired, reissue the command with
User Response: Reissue the command with a valid a different administrator ID.
end date.
ANR2173E Command: Location information exceeds
ANR2168E Command: Invalid end time - time. maximum characters characters.
Explanation: A QUERY ACTLOG command has been Explanation: A DEFINE or UPDATE VOLUME
entered that specifies an invalid end time as a search command has been entered that specifies a location
criteria. information value that is too long. The maximum valid
length is shown in the command.
command. System Action: The server does not process the
command.
end time. User Response: Reissue the command with less
location information.
ANR2169E Command: Invalid message number -

message number. ANR2174E Administrator administrator ID is not
registered. Schedule schedule name is not
Explanation: A QUERY ACTLOG command has been processed and is marked as failed.
entered that specifies an invalid message number as a
search criteria. Explanation: The command shown specifies an
administrator ID that is not registered with the server.
System Action: The server does not process the The schedule and related command are not processed.
command.
User Response: Reissue the command with a valid command.
message number.
User Response: Update the command schedule with a
valid administrator ID which has the proper authority
ANR2170E Command: Invalid message search string to execute the scheduled command.
argument - search string.
Explanation: A QUERY ACTLOG command has been ANR2175I Invalid password limit set to password
entered that specifies an invalid search string as a attempts limit attempts.
search criteria.
Explanation: The maximum number of consecutive
System Action: The server does not process the invalid passwords a node or administrator may send to
command. the server is indicated with the SET INVALIDPWLIMIT
User Response: Reissue the command with a valid command.
search string. System Action: None.

ANR2180W Unable to update last access date for
administrator administrator ID -
ANR2176E Command: The value supplied for the insufficient recovery log space.
invalid password attempts limit is not
Explanation: While establishing an administrative
valid - password attempts limit.
session for the indicated ID, the server is unable to
Explanation: A SET INVALIDPWLIMIT command has update the administrator’s date of last access due to
been entered that specifies a value for the consecutive insufficient recovery log space.
invalid password attempts limit that is not valid. Valid
System Action: The server establishes the
values are from 0 to 9999, inclusive.
administrative session, but the last access date is not
System Action: The server does not process the updated.
command.
User Response: Reissue the command with a valid the DEFINE LOGVOLUME command to add volumes
value. for use by the log, and can issue the EXTEND LOG
volumes are used.
ANR2177I node/admin name has count invalid
sign-on attempts. The limit is limit.
ANR2181W Unable to update last access date for
Explanation: The server detected an invalid password administrator administrator ID -
for the specified node during sign-on processing. The insufficient database space.
node currently has sent count consecutive invalid
passwords. The maximum allowed is limit. The server Explanation: While establishing an administrative
will lock the node when limit is reached. session for the indicated ID, the server cannot update
the administrator’s date of last access due to
System Action: The node or administrator session will insufficient database space.
be refused.
System Action: The server establishes the
User Response: Before the client node is permitted to administrative session, but the last access date is not
access the server, a properly authorized administrator updated.
must unlock the node or administrator with the
UNLOCK NODE or UNLOCK ADMIN command. User Response: An authorized administrator can issue
for use by the database, and can issue the EXTEND DB
ANR2178E node/admin name has been locked. Invalid command to extend the size of the database so that the
sign-on attempt limit (limit) reached. new volumes are used.
Explanation: The specified node has been locked by
the server. The limit for consecutive invalid passwords ANR2182W Unable to update last access date for
has been reached. administrator administrator ID - internal
System Action: The node or administrator session will server error.
be refused. Explanation: While establishing an administrative
User Response: Before the client node is permitted to session for the indicated ID, the server cannot update
access the server, a properly authorized administrator the administrator’s date of last access due to a server
must unlock the node or administrator with the internal error.
UNLOCK NODE or UNLOCK ADMIN command. System Action: The server establishes the
administrative session, but the last access date is not
ANR2179E Administrator administrator should have updated.
been locked, but was not. User Response: Examine the server messages issued
Explanation: The indicated administrator reached the prior to this message to determine the source of the
limit for consecutive invalid passwords and should error. Issue the QUERY ACTLOG command to view the
have been locked. If it were locked, there would be no activity log and search for messages. If the error cannot
means to execute commands requiring system be isolated and resolved, contact your service
authority. representative.
System Action: The administrator session will be

refused. ANR2183W DiagnosticID: Transaction transaction ID
was aborted.
User Response: Sign-on again using the correct
password. Explanation: An error was detected during transaction
commit. This message should be preceded by other

ANR2187W Transaction was aborted for node/admin
failed transaction.
name.
Explanation: An error is detected during a transaction
fails.
commit for the specified node or administrator name.
User Response: Check for additional messages and This message should be preceded by other messages
eliminate the condition that caused the failed that give additional information about the failed
transaction. If the error cannot be isolated and resolved, transaction.
fails.
ANR2184W DiagnosticID: Transaction transaction ID
was aborted for command command.
Explanation: An error was detected during transaction transaction. If the error cannot be isolated and resolved,
commit for the specified server command. This contact your service representative.
message should be preceded by other messages that
give additional information about the failed transaction.
ANR2188W A Transaction was aborted. The activity
System Action: The activity that generated this error is terminating.
fails.
User Response: Check for additional messages and commit. This message should be preceded by other
eliminate the condition that caused the failed messages that give additional information about the
transaction. If the error cannot be isolated and resolved, failed transaction.
ends.
ANR2185W Transaction was aborted for command
command.
commit. This message should be preceded by other contact your service representative.
failed transaction.
ANR2189W DiagnosticID: Transaction transaction ID
System Action: The activity that generated this error was aborted for node/admin name.
fails.
User Response: Check for additional messages and commit for the specified node or administrator name.
eliminate the condition that caused the failed This message should be preceded by other messages
transaction. If the error cannot be isolated and resolved, that give additional information about the failed
contact your service representative. transaction.
ANR2186W Transaction was aborted for session fails.
platform).
commit. This message should be preceded by other contact your service representative.
failed transaction.
ANR2190E command: Device class DISK cannot be
System Action: The activity that generated this error specified for this command.
fails.
Explanation: The DEVCLASS value DISK cannot be
User Response: Check for additional messages and specified for the command.
server.

ANR2191E command: Volume list contains defined ANR2196E Command: Option name and/or Option
and undefined volumes. value is missing for define.
Explanation: The list of volumes specified on the Explanation: The specified DEFINE command has
SALVAGE VOLUME command must all be defined to been entered, but no attributes have been specified for
the server, or all not defined to the server. the definition.
System Action: The command fails and server System Action: The server does not process the
operation continues. command.
User Response: Reissue the command and specify a User Response: Reissue the DEFINE command with
valid list of volumes. one or more attributes to be defined
ANR2192E Command: Unable to start background ANR2197E Command: The value supplied for the
process. WEB authentication time out is not
valid - time-out value.
Explanation: The server command processor is not
able to start a background process to perform the Explanation: A SET WEBAUTHTIMEOUT command
command command. has been entered that specifies a value that is not valid.
Valid values are from 0 to 9999, inclusive.
System Action: The command process ends and
server operation continues. System Action: The server does not process the
command.
server. For details, issue HELP MEMORY to display the User Response: Reissue the command with a valid
information online or see “Appendix A. Allocating value.
ANR2198I Command: Web authentication time-out
ANR2193E Command: Invalid option set name - set to time-out value minutes.
option set name.
Explanation: The time-out value that determines how
Explanation: The command shown specifies an invalid often WEB browser administrative users need to
option set name. re-authenticate with the server has been set with the
SET WEBAUTHTIMEOUT command to the value
displayed.
command.
option set name. User Response: None.
ANR2194E Command: Invalid option set description ANR2199I Password expiration period for node
- too long. node name set to number of days days.
Explanation: The command shown specifies an invalid Explanation: The number of days that the node’s
description. The description is too long. password can be used before it must be changed has
been set to the value indicated with the SET PASSEXP
command.
command.
description. User Response: None.
ANR2195E Command: Invalid option sequence ANR2200I Storage pool storage pool name defined
number - option sequence number name. (device class device class name).
Explanation: The command shown specifies an invalid Explanation: A DEFINE STGPOOL command has
option sequence number. created the storage pool indicated of the device class
shown.
command. System Action: None.
User Response: Reissue the command with a valid User Response: None.
option sequence number.

ANR2201I Storage pool storage pool name deleted. 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.
User Response: None. v The volume was empty and the volume’s access
mode was updated to destroyed.
v The volume was empty, scratch, and offsite, and the
ANR2202I Storage pool storage pool name updated. access mode was changed to readwrite, readonly, or
Explanation: An UPDATE STGPOOL command has unavailable.
updated the storage pool indicated. v The volume was scratch, not offsite, and was
emptied by DELETE FILESPACE, RECLAMATION,
System Action: None. or RESTORE VOLUME/STGPOOL.
ANR2203I Device class device class name defined.
Explanation: A DEFINE DEVCLASS command has ANR2209W Volume volume name contains no data.
created the device class indicated.
Explanation: The AUDIT VOLUME or MOVE DATA
System Action: None. command entered specifies a volume that contains no
User Response: None. data.
ANR2204I Device class device class name deleted. command.
Explanation: A DELETE DEVCLASS command has User Response: None.

deleted the device class indicated.
System Action: None. ANR2210I Vary online initiated for disk volume
volume name.
Explanation: A VARY ONLINE command for the
volume shown is being processed, and if no errors
ANR2205I Device class device class name updated. occur the volume will be varied online.
Explanation: An UPDATE DEVCLASS command has System Action: None.
updated the device class indicated.
User Response: None. ANR2211I Vary offline initiated for disk volume
volume name.
ANR2206I Volume volume name defined in storage Explanation: A VARY OFFLINE command for the
pool storage pool name (device class device volume shown is being processed and, if no errors
class name). occur, the volume will be varied offline.
Explanation: A DEFINE VOLUME command has System Action: None.
defined the volume indicated in the storage pool
shown that belongs to the device class shown. User Response: None.

ANR2212I Command: No volumes updated.
Explanation: An UPDATE VOLUME command has
been entered, but no objects were updated.
ANR2207I Volume volume name updated.
Explanation: An UPDATE VOLUME command has
updated the volume indicated. User Response: None.


ANR2213I Command: Storage pool storage pool name
renamed to storage pool name.
Explanation: A RENAME STGPOOL command has server.
been entered. The rename of the storage pool was
successful.
ANR2219I Discard Data process ended for volume
System Action: None. 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
ANR2214E Command: Invalid backup set name -
volume shown has ended, but the volume has not been
backup set name.
deleted because the volume access is marked as offsite.
backup set name.
User Response: To delete the volume, change the
volume access to readwrite, readonly, or unavailable.
backup set name.
ANR2220W This command will delete volume
volume name from its storage pool after
ANR2215E Command: Description text is too long. verifying that the volume contains no
data.
Explanation: The specified description text is too long
for a command that allows description text to be Explanation: A DELETE VOLUME command with the
specified. Discarddata=No option has been entered.
System Action: The command fails System Action: The system asks whether you wish to
continue with the command.
shorter description User Response: To process the DELETE VOLUME
command, enter 'Y' to continue or 'N' to stop the
process.
ANR2216E Command: Device class must be a
sequential device class.
ANR2221W This command will result in the
Explanation: The device class specified on the deletion of all inventory references to
command is not a sequential device class. the data on volume volume name, thereby
System Action: The command fails rendering the data unrecoverable.
User Response: Reissue the command specifying the Explanation: A DELETE VOLUME command with the
name of a sequential device class Discarddata=Yes option has been entered.
System Action: The system asks whether you wish to
ANR2217E Command: Invalid backup set retention continue with the command.
period - retention value. User Response: To process the DELETE VOLUME
Explanation: Server processing for the backup set command, enter 'Y' to continue or 'N' to stop the
command command fails because the value (retention process.
value) specified for the RETENTION parameter is not
valid. ANR2222I Discard Data process started for volume
System Action: The command fails volume name (process ID process ID).
User Response: Reissue the command specifying a Explanation: As a result of a DELETE VOLUME
valid RETENTION value. command with the Discarddata=Yes option, the process
whose ID is displayed has begun to delete the data on
the volume shown.
ANR2218E Command: A device class must be
specified. System Action: The server deletes the data on the
volume.
Explanation: The DEVCLASS parameter is not
specified in the command command name. A DEVCLASS User Response: None.
value must be specified.

System Action: The server does not delete the
ANR2223I Discard Data process ended for volume
volume.
volume name - volume deleted from
storage pool storage pool name. User Response: Allocate additional storage to the
Explanation: The process that deleted data for the
volume shown has ended, and the volume has been
deleted.
ANR2228W Discard data process terminated for
User Response: None. volume volume name - lock conflict
detected.
ANR2224W Discard Data process terminated for Explanation: The process that was deleting data for
volume volume name - process canceled. the volume shown, in preparation for deleting the
volume, has ended due to a locking conflict.
Explanation: The process that was deleting data for
the volume shown, in preparation for deleting the System Action: The server does not delete the
volume, has been canceled. volume.
System Action: The server does not delete the User Response: Reissue the command at a later time.
volume. If this problem persists, contact your service
representative.

ANR2225W Discard Data process terminated for
volume volume name - volume still
error detected.
contains data.
the volume shown, in preparation for deleting the
volume, has ended due to a server internal error.
volume, has ended. However, the volume contains
data. System Action: The server does not delete the volume
System Action: The server does not delete the User Response: Contact your service representative.
volume.
User Response: Contact your service representative. 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
volume volume name - sufficient recovery
until the operation completes.
log space is not available.
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
volume, has ended due to a shortage of recovery log
moved, it will not be available to users.
space.
System Action: The server does not delete the
continue.
volume.
User Response: Enter 'Y' to continue with the
command or 'N' to end the process.
for use by the log, and can issue the EXTEND LOG
command to extend the size of the log so that the new ANR2233W This command will move all of the data
volumes are used. stored on volume volume name to other
volumes in storage pool storage pool
name; the data will be inaccessible to
users until the operation completes.
is not available. 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.
volume, has ended due to a shortage of memory.

System Action: The administrator is asked whether to schedules were last updated by the administrator. Use
continue. the UPDATE SCHEDULE command to update those
schedules under an administrator that has authority to
User Response: Enter 'Y' to continue with the
execute them, or use the DELETE SCHEDULE
command or 'N' to end the process.
command to remove the schedules.
ANR2234W This command will halt the server; if

ANR2237W This command has revoked privileges
the command is issued from a remote
for administrator adminName. This
client, it may not be possible to restart
administrator has defined or updated
the server from the remote location.
schedules. This may cause these
Explanation: A HALT command has been entered. schedules to fail in the future.
System Action: The administrator is asked whether to Explanation: A REVOKE AUTHORITY command has
continue. been entered.
User Response: Enter 'Y' to halt the server or 'N' to System Action: The system removes the authority.
leave the server activated.
ANR2235W This command will remove

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

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

User Response: Use the QUERY SCHEDULE
command OR an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which

ANR2241I Database volume copy volume name ANR2247I Database volume volume name varied
defined. offline.
Explanation: A DEFINE DBCOPY command has Explanation: A VARY OFFLINE command has put the
defined the database volume indicated. indicated database volume into an offline state.
ANR2242I Database volume copy volume name ANR2248I Database assigned capacity has been
defined; synchronization process started extended.
(process ID process ID).
Explanation: An EXTEND DB command has increased
Explanation: A DEFINE DBCOPY command has the storage capacity of the database.
added the volume shown as a database copy volume.
The process whose ID is displayed will copy data to
the new volume to synchronize it with existing User Response: None.
volumes.
System Action: None. ANR2249I Database extension process initiated
Explanation: In response to an EXTEND DB
command, the process with the process ID shown has
ANR2243I Database volume volume name deleted.
been started to extend the database.
Explanation: A DELETE DBVOLUME command has
deleted the database volume indicated.
ANR2250I Database assigned capacity has been
reduced.
ANR2244I Delete process initiated for database
Explanation: A REDUCE DB command has decreased
volume volume name (process id process
the storage capacity of the database.
ID).
Explanation: In response to a DELETE DBVOLUME
command, the process with the process ID shown has User Response: None.
been started to delete the volume.
System Action: None. ANR2251I Database reduction process initiated
Explanation: In response to a REDUCE DB command,
the process with the process ID shown has been started
ANR2245I Database volume volume name varied
to reduce the database.
online.
Explanation: A VARY ONLINE command has put the
database volume indicated into an online state. User Response: None.
ANR2252W Database volume copy volume name is
larger than volume volume name by count
megabyte(s).
ANR2246I Vary online process initiated for
Explanation: A DEFINE DBCOPY command has
database volume volume name (process
defined a database copy volume whose size is larger
ID process ID).
than the volume it mirrors by the amount shown.
Explanation: In response to a VARY ONLINE
System Action: The excess capacity is ignored.
been started to vary on the database volume indicated. User Response: None.

command for the indicated node. Note: This message
ANR2253W The database volume copy to be defined
can be issued as a result of the server option
(volume name) is larger than volume
REQSYSAUTHOUTFILE YES being in effect.
volume name; use of the volume will
result in count megabyte(s) of unusable System Action: The server does not process the
space. command for the indicated node. If multiple nodes
were specified on the command, the server may
Explanation: A DEFINE DBCOPY command is
continue processing the command for the other nodes.
attempting to define a database copy volume whose
size is larger than the volume it mirrors by the amount User Response: Examine previous messages for any
shown. The excess capacity would not be used. additional information. Issue the command from a
properly authorized administrator ID, or contact the
system administrator to have additional authority
continue.
granted to the current administrator ID.
User Response: Enter 'Y' to define the copy, 'N'
otherwise.
ANR2258E Command: Invalid summary retention
period - retention value.
ANR2254E Command: The VOLUMENAMES
Explanation: A SET SUMMARYRETENTION
parameter must be specified when
command has been entered that specifies an invalid
SCRATCH=NO is specified.
retention period.
Explanation: The SCRATCH parameter is specified as
NO for the command Command but the
command.
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES User Response: Reissue the command with a valid
parameter must be specified to indicate the volumes retention period.
that can be used for the command.
System Action: The command fails. ANR2259I Summary retention period set to number
of days days.
valid VOLUMENAMES parameter. Explanation: The number of days that activity sumary
records are kept in the server database has been set to
the value indicated with the SET
ANR2255E Command: The VOLUMENAMES
SUMMARYRETENTION command.
parameter must be specified.
Explanation: The VOLUMENAMES parameter must
be specified to indicate the volumes that can be used User Response: None.
for the command.
System Action: The command fails. ANR2260I Recovery log volume volume name
defined.
valid VOLUMENAMES parameter. Explanation: A DEFINE LOGVOLUME command has
defined the recovery log volume indicated.
ANR2256E Command: The RETENTION parameter System Action: None.
must be specified.
Explanation: The RETENTION parameter must be
specified to indicate the retention period to be used for
the command. ANR2261I Recovery log volume copy volume name
defined.
Explanation: A DEFINE LOGCOPY command has
User Response: Reissue the command and specify a defined the recovery log volume indicated.
valid RETENTION parameter.
ANR2257E Command: Administrator administrator User Response: None.

name is not authorized to issue this
command for node node name.
the indicated command, but this administrator does not
have the proper authority necessary to run the

ANR2262I Recovery log volume copy volume name ANR2268I Recovery log assigned capacity has been
defined; synchronization process started extended.
Explanation: An EXTEND LOG command has
Explanation: A DEFINE LOGCOPY command has increased the storage capacity of the recovery log.
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. User Response: None.
ANR2269I Recovery log extension process initiated
Explanation: In response to an EXTEND LOG
ANR2263I Recovery log volume volume name
deleted.
been started to extend the recovery log.
Explanation: A DELETE LOGVOLUME command has
removed the recovery log volume indicated.
ANR2270I Recovery log assigned capacity has been
reduced.
ANR2264I Delete process initiated for recovery log
Explanation: A REDUCE LOG command has
volume volume name (process id process
decreased the storage capacity of the recovery log.
ID).
Explanation: In response to a DELETE LOGVOLUME
command, the process with process ID shown has been User Response: None.
started to delete the volume.
System Action: None. ANR2271I Recovery log reduction process initiated
Explanation: In response to a REDUCE LOG
ANR2265I Recovery log volume volume name varied
been started to reduce the recovery log.
online.
Explanation: A VARY ONLINE command has put the
recovery log volume indicated into an online state. User Response: None.
ANR2272W Recovery log volume copy volume name
is larger than volume volume name by
count megabytes.
ANR2266I Vary online process initiated for
Explanation: A DEFINE LOGCOPY command has
recovery log volume volume name
defined a recovery log copy volume whose size is
larger than the volume it mirrors by the amount
Explanation: In response to a VARY ONLINE shown.
command, the process with process ID shown has been
System Action: The excess capacity is ignored.
started to vary on the recovery log volume indicated.
ANR2273W The recovery log volume copy to be
defined (volume name) is larger than
ANR2267I Recovery log volume volume name varied volume volume name; use of the volume
offline. will result in count megabytes of
unusable space.
Explanation: A VARY OFFLINE command has put the
recovery log volume indicated into an offline state. Explanation: A DEFINE LOGCOPY command is
attempting to define a recovery log copy volume whose
size is larger than the volume it mirrors by the amount
User Response: None. shown. The excess capacity would not be used.

ANR2278I Database Space trigger deleted.
continue.
Explanation: A DELETE SPACETRIGGER command
User Response: Enter 'Y' to define the copy or 'N' to
has successfully completed for the database space
stop the process.
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 ANR2279I Recovery Log Space trigger defined and
FULLPCT parameter is used to automatically expand enabled.
the database.
Explanation: The recovery log space trigger has been
System Action: None. defined with a DEFINE SPACETRIGGER command.
The percentage of utilization specified with the
FULLPCT parameter is used to automatically expand
the recovery log.
ANR2275I 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. ANR2280I Full database backup started as process
process ID.
Explanation: A background process was started to
User Response: To activate the space trigger, use the
backup the contents of the database. The full database
UPDATE SPACETRIGGER command to set the space
backup process was assigned the process ID shown.
expansion percentage to a value greater than 0.
System Action: The database backup process starts
ANR2276I Data Base Space trigger updated and
enabled. User Response: The administrator may query the
status of the database backup process by using the
Explanation: An UPDATE SPACETRIGGER command
QUERY PROCESS command, or cancel the process with
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. ANR2281I Incremental database backup started as
process process ID.
Explanation: A background process was started to
backup the contents of the database. The incremental
database backup process was assigned the process ID
ANR2277I Database Space trigger updated, but shown.
disabled.
Explanation: An UPDATE SPACETRIGGER command and server operation continues.
has successfully completed for the data base space
User Response: The administrator may query the
trigger. However, the space expansion percentage is
currently set to 0, which disables the space trigger.
QUERY PROCESS command, or cancel the process with
System Action: None. the CANCEL PROCESS command.

UPDATE SPACETRIGGER command with the ANR2282I Database backup trigger defined and
SPACEexpansion parameter to set a value greater than enabled.
zero.
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.

User Response: None. System Action: The database backup process starts
ANR2283I Database backup trigger defined, but is User Response: The administrator may query the
disabled. started process by using the QUERY PROCESS
command, or may cancel the process using the
Explanation: A database backup trigger has been
CANCEL PROCESS command.
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 ANR2288I Subfile set to state.
the log mode is set to ROLLFORWARD with a SET
Explanation: The SET SUBFILE command has been
LOGMODE command.
used to specify whether this server will allow clients to
System Action: None. back up subfiles. If a value of CLIENT is specified,
clients are given the option of backing up subfiles. If a
User Response: To activate the database backup
value of NO is specified, clients are not allowed to back
trigger, use the SET LOGMODE ROLLFORWARD
up subfiles.
command.
ANR2284I Database backup trigger updated and User Response: None.
enabled.
Explanation: An UPDATE DBBACKUPTRIGGER ANR2289I Administrative userid admininstrator
command has successfully completed. The updated name defined for authority over node
parameters specified on the command are used to node name has not been removed.
automatically trigger database backups.
Explanation: The specified administrator was not
System Action: None. removed.
ANR2285I Database backup trigger updated, but
disabled.
ANR2290W Changing the log mode to NORMAL
Explanation: An UPDATE DBBACKUPTRIGGER will prevent roll-forward recovery.
command has successfully completed, but because the
Explanation: The system has determined that
recovery log mode is currently set to NORMAL, the
changing the recovery log mode from ROLLFORWARD
database backup trigger is disabled. Database backups
to NORMAL mode will cause the log records being
can only be triggered when the log mode is set to
kept for ROLLFORWARD and single database volume
ROLLFORWARD with a SET LOGMODE command.
restore processing to be discarded. Without these log
System Action: None. records, only point-in-time database restores can be
performed.
User Response: To activate the database backup
trigger, use the SET LOGMODE ROLLFORWARD System Action: The administrator is asked whether to
command. continue.
User Response: Enter 'Y' to change the LOGMODE,
ANR2286I Database backup trigger deleted. 'N' otherwise.
Explanation: A DELETE DBBACKUPTRIGGER
command has successfully completed. Database ANR2291W Changing the log mode to NORMAL
backups are no longer triggered automatically by will disable the database backup trigger.
recovery log utilization.
Explanation: Changing the recovery log mode from
System Action: None. 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
ANR2287I Snapshot database backup started as with the SET LOGMODE command.
process process ID.
Explanation: A background process was started to continue.
backup the contents of the database. The snapshot
User Response: Enter 'Y' to change the log mode, 'N'
database backup process was assigned the process id
otherwise. Responding 'Y' does not delete the DEFINE
shown.
DBBACKUPTRIGGER settings.

ANR2292W Changing the log mode to ANR2296I Log mode set to NORMAL; database
ROLLFORWARD will enable the backup trigger disabled.
database backup trigger.
Explanation: The mode for saving recovery log
Explanation: Changing the recovery log mode from records has been set to NORMAL mode, and the
NORMAL to ROLLFORWARD causes a previously defined database backup trigger is disabled. Only those
issued DEFINE DBBACKUPTRIGGER command to log records needed to resume database processing if a
become effective, and immediately start a full database system failure occurs are saved in this mode. Database
backup. Database backups can only be triggered when backups can only be started using the BACKUP DB
the recovery log mode is set to ROLLFORWARD with a command.
SET LOGMODE command.
continue.
User Response: Enter 'Y' to change the log mode, 'N'
ANR2297I Command: Optionset optionset name,
otherwise.
option option name, sequence number old
sequence number, has been changed to
ANR2293I Only point-in-time database recovery is new sequence number.
now possible.
Explanation: The requested option sequence number
Explanation: An administrator has changed the has been updated in response to an UPDATE
recovery log mode from ROLLFORWARD to NORMAL CLIENTOPT command.
with a SET LOGMODE command. Only point-in-time
database restores can be performed. ROLLFORWARD
database restores and individual database volume User Response: None.
restores are not possible.
System Action: None. ANR2298I Command: Optionset optionset name,
option option name, sequence number old
sequence number, is not updated.
Explanation: The requested option sequence number
ANR2294I Log mode set to log mode.
is not updated in response to an UPDATE CLIENTOPT
Explanation: The mode for saving recovery log command.
records has been set as indicated by the SET
LOGMODE command. When set to NORMAL, only
those log records needed to resume database processing User Response: Reissue the UPDATE CLIENTOPT
if a system failure occurs are saved. When set to command with a valid old sequence number.
ROLLFORWARD, all log records created since the last
database backup are saved. ROLLFORWARD mode
also enables the database backup trigger to be used to ANR2299I Password expiration period for
automatically start database backups based on the administrator administrator name set to
percentage of recovery log utilization. number of days days.
System Action: None. Explanation: The number of days that the

administrator’s password can be used before it must be
User Response: None. changed has been set to the value indicated with the
SET PASSEXP command.
ANR2295I Log mode set to ROLLFORWARD; System Action: None.
database backup trigger enabled.
Explanation: The mode for saving recovery log
records has been set to ROLLFORWARD, and a
previously defined database backup trigger has been ANR2300E Could not open ″file spec″ the server help
enabled. All log records created since the last database file.
backup are saved in this mode. The database backup Explanation: The named help file could not be
trigger will automatically start a database backup based accessed.
on the percentage of recovery log utilization.
System Action: The requested help text is not
System Action: None. displayed.
User Response: None. User Response: Contact the system administrator.

ANR2301E Errors were encountered while setting ANR2306E No help text could be found for this
up the index to the help text. command/subcommand: command.
Explanation: Either insufficient memory or a help file Explanation: The operands you entered for the HELP
read failure has occurred during setup of the help command, although valid command/subcommand
index. names, do not match any named entry into the file of
help text.
System Action: The server does not display the
requested help text. System Action: The server does not process the HELP
command.
User Response: Contact the system administrator.
User Response: Contact the system administrator.
ANR2302E The argument operand is not valid for
the HELP command. ANR2307E No help text could be found for this
message: message ID.
Explanation: The argument supplied on the HELP
command is not an integer or the name of a command. Explanation: The message ID you entered for the help
command does not match any message entry in the file
System Action: The server does not process the HELP
of help text.
command.
System Action: The help command is not processed.
User Response: Issue the HELP command with no
operands and select from the numbered list displayed User Response: Contact the system administrator.
in response.
ANR2308W Audit Volume marking damaged file as
ANR2303E There is no help section numbered damaged on volume volume name: Node
section number. node name, Type file type, File space
filespace name, fsId filespace id, File Name
Explanation: The numeric operand supplied on the
file name is number version of total
HELP command is either less than 1 or greater than the
versions versions.
highest-numbered entry in the help index.
Explanation: As the result of an AUDIT VOLUME
System Action: The server does not process the HELP
command that specified FIX=YES for the volume
command.
shown, the file whose information is displayed is
User Response: Issue the HELP command with no marked as damaged in the server. The file is marked as
operands and select from the numbered list (help damaged because it can be recovered from a copy
index) displayed in response. 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
ANR2304E I/O error reading ″help file name″ the file in the aggregate. The version numbers for the file are
of help text. numbered from most recent (1) to least recent (n, where
Explanation: An error is detected when reading help n is the total number of versions.
text from the named file. System Action: The file is marked as damaged in the
System Action: The server ends display of the help server database.
text. User Response: To recover the damaged file use the
User Response: Contact the system administrator. RESTORE STGPOOL or RESTORE VOLUME command.
ANR2305E No such command/subcommand: ANR2309E The server log mode is currently set to
command subcommand. roll-forward. You may run out of log
space when auditing the server in this
Explanation: The operands you entered for the HELP mode. Specify LOGMODE=NORMAL
command do not match any named entry into the file to set the log mode to NORMAL for the
of help text. audit operation, or
System Action: The server does not process the HELP LOGMODE=ROLLFORWARD to force
command. the audit operation with the logmode
set to roll-forward.
User Response: Check your input for a misspelled
command or subcommand name. 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
ANR2313I Audit Volume (Inspect Only) process
AUDITDB operation is NORMAL.
started for volume volume name (process
System Action: The AUDITDB operation fails ID process ID).
User Response: To force the server log mode to Explanation: As the result of an AUDIT VOLUME
NORMAL for the AUDITDB operation, specify command that specified FIX=NO for the volume
LOGMODE=NORMAL on the AUDITDB command. shown, the process whose ID is displayed has begun
Specify LOGMODE=ROLLFORWARD on the auditing the volume.
AUDITDB command to allow the audit to run with a
System Action: The volume is audited and
roll-forward log mode setting.
inconsistent data is displayed.
ANR2310W This command will compare all
inventory references to volume volume
name with the actual data stored on the ANR2314I Audit volume process ended for volume
volume and will report any volume name; file count files inspected, file
discrepancies; the data will be count damaged files deleted, file count
inaccessible to users until the operation damaged files marked as damaged.
completes.
Explanation: The AUDIT VOLUME command
Explanation: During the execution of an AUDIT specifying FIX=YES for the volume shown has ended.
VOLUME command, any data the volume named The number of files audited and the number of
would be unavailable to users. inconsistent files deleted or marked as damaged are
displayed. The number of files marked as damaged
includes all files belonging to aggregates that were
continue.
marked damaged during the audit. Files are marked as
User Response: Enter 'Y' to audit the volume or 'N' to damaged in primary storage pools and not deleted
stop the process. when backup copies for the files are known to exist in
COPY storage pools.
ANR2311W This command will discard any System Action: None.

inventory references to volume volume
User Response: To recover files that have been
name associated with missing or
marked as damaged on the volume, use the RESTORE
inconsistent stored data, thereby
STGPOOL or RESTORE volume command.
rendering the data unrecoverable; the
valid data on the volume will be
inaccessible to users until the operation ANR2315I Audit volume process ended for volume
completes. volume name; file count files inspected, file
count damaged files found and marked
Explanation: During the execution of an AUDIT
as damaged.
VOLUME command, any data the volume named
would be unavailable to users. After the command has Explanation: The AUDIT VOLUME command
ended, any inconsistent data found will be discarded. specifying FIX=NO for the volume shown has ended.
The number of files audited and the number of
inconsistent files found are displayed. The number of
continue.
files marked damaged includes all files belonging to
User Response: Enter 'Y' to audit the volume or 'N' to aggregates that were marked damaged during the
stop the process. audit. Inconsistent files are marked as damaged in the
database and can be recovered by using the RESTORE
STGPOOL or RESTORE VOLUME command if copies
ANR2312I Audit Volume (Repair) process started of the files reside in a COPY storage pool. Another
for volume volume name (process ID AUDIT VOLUME command may be able to access the
process ID). files and reset the damaged indicator in the database if
Explanation: As the result of an AUDIT VOLUME the audit volume process cannot access the files due to
command that specified FIX=YES for the volume hardware problems (for example, dirty tape heads).
shown, the process whose ID is displayed has begun System Action: None.
auditing the volume.
User Response: If you suspect that files were
System Action: The volume is audited and inaccessible because of hardware problems such as
inconsistent data is discarded. dirty tape heads, correct the hardware problem and
User Response: None. reissue the AUDIT VOLUME FIX=NO command for
this volume. To remove damaged file references, issue
the AUDIT VOLUME command and specify FIX=YES.

ANR2316W Audit Volume deleting damaged file on ANR2320W Audit volume process terminated for
volume volume name: Node node name, volume volume name - data transfer
Type file type, File space filespace name, interrupted.
fsId filespace id, File Name file name is
Explanation: During processing of an AUDIT
number version of total versions versions.
VOLUME command for the volume shown, a data
Explanation: As the result of an AUDIT VOLUME transfer operation has been interrupted and cannot be
command that specified FIX=YES for the volume continued.
shown, the file whose information is displayed is
System Action: The AUDIT VOLUME command is
deleted from the server. The version numbers for the
ended.
file are numbered from most recent (1) to least recent
(n, where n is the total number of versions. User Response: If possible, determine and correct the
cause of the interruption, and reissue the command.
System Action: The file is deleted.
ANR2321W Audit volume process terminated for
volume volume name - storage media
ANR2317W Audit Volume found damaged file on inaccessible.
volume volume name: Node node name,
Type file type, File space filespace name,
VOLUME command for the volume shown, a required
fsId filespace id, File name file name is
volume cannot be mounted.
number version of total versions versions.
ended.
command that specified FIX=NO for the volume
shown, the file whose information is displayed is found User Response: None.
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 ANR2322W Audit volume process terminated for
aggregate. The version numbers for the file are volume volume name - sufficient recovery
numbered from most recent (1) to least recent (n, where log space is not available.
n is the total number of versions. Explanation: During processing of an AUDIT
System Action: None. VOLUME command for the volume shown, the server
does not have sufficient recovery log space to continue.
ended.
volume volume name - process canceled. User Response: If necessary, make more recovery log
space available to the server.
VOLUME command for the volume shown, the process
performing the audit was canceled. ANR2323W Audit volume process terminated for
volume volume name - sufficient database
System Action: The AUDIT VOLUME command is space is not available.
ended.
User Response: None. VOLUME command for the volume shown, the server
does not have sufficient database space to continue.
ANR2319W Audit volume process terminated for System Action: The AUDIT VOLUME command is
volume volume name - error reading ended.
device.
User Response: If necessary, make more database
Explanation: During processing of an AUDIT space available to the server.
VOLUME command for the volume shown, an
unrecoverable read error occurred on the volume.
System Action: The AUDIT VOLUME command is volume volume name - thread resource
ended. not available.
User Response: Attempt to correct the cause of the Explanation: During processing of an AUDIT
read error, and reissue the command. VOLUME command for the volume shown, the server
cannot start a thread for the audit process.

System Action: The AUDIT VOLUME command is User Response: Check the activity log to verify that
ended. some process (such as a DELETE FILESPACE
command) was in progress during the AUDIT
User Response: Reissue the AUDIT VOLUME
VOLUME command that would account for the deleted
command. If the error persists, it may indicate a
object. If no such process can be identified, contact your

ANR2333W Missing or incorrect information
detected by AUDIT VOLUME for
is not available.
volume volume name.
Explanation: An AUDIT VOLUME command detects
VOLUME command for the volume shown, the server
missing or incorrect information for the specified
does not have enough memory available to complete
volume.
the command.
System Action: Audit processing continues.
ended. User Response: Reissue the audit command with
FIX=YES so that the information can be created or
User Response: If necessary make more memory
corrected.
ANR2334W Missing or incorrect information

detected by AUDIT VOLUME for
volume volume name - lock conflict
volume volume name - information will
detected.
be created or corrected.
Explanation: An AUDIT VOLUME process detects
VOLUME command for the volume shown, the server
missing or incorrect information for the specified
cannot obtain a required lock.
volume. Because FIX=YES has been specified for the
System Action: The AUDIT VOLUME command is audit command, the information is created or corrected.
ended.
User Response: Reissue the command.

ANR2335W Audit Volume has encountered an I/O
error for volume volume name while
error detected.
attempting to read: Node node name,
Explanation: During processing of an AUDIT Type file type, Filespace filespace name,
VOLUME command for the volume shown, an internal fsId filespace id, File Name file name.
server error occurs.
Explanation: The AUDIT VOLUME process
System Action: The AUDIT VOLUME command is encountered an I/O error for the specified volume
ended. while attempting to read the specified file. If this file
belongs to an aggregate, the entire aggregate is marked
User Response: Contact your service representative. damaged, and this message will be issued for every file
in the aggregate.
ANR2332W Object object.ID deleted by another System Action: None.
process during execution of an AUDIT
VOLUME command for volume volume User Response: Identify and resolve the I/O error for
name. the volume if possible. Verify that the volume’s device
is functioning properly and that the volume is usable.
Explanation: During processing of an AUDIT For example, if the volume is a tape volume, make sure
VOLUME command, a data storage object was deleted the drive is clean or that the tape volume is usable by
from the volume that was being audited. The AUDIT testing it by using a different drive.
VOLUME process was unable to locate this object on
the specified volume. Normally, this action is not
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.

ANR2336W Audit Volume terminated for volume ANR2343E Command: Invalid device class name -
volume name - insufficient number of device class name.
Explanation: The command indicated contains an
media.
invalid device class name.
Explanation: During Audit Volume for the indicated
volume, the server could not allocate sufficient mount
command.
points for the volume required.
System Action: Audit Volume stops.
device class name.
available.
ANR2344E Command: The ″option″ option is not
valid for device class device class name.
ANR2339E Command: Object sets still exist for node
Explanation: The command indicated specifies an
node name.
option shown that is not valid for a storage pool that
Explanation: A REMOVE NODE command has been belongs to the device class shown.
entered for a node for which the server is still storing
backup sets. To remove a node, the node must not have
command.
any files or backup sets stored on the server.
User Response: Reissue the command with options
appropriate to the device class.
command.
User Response: To remove the node, delete all backup
ANR2345E Command: Invalid volume name - volume
sets from the server and reissue the command.
name.
ANR2340E Command: Invalid storage pool name -
invalid volume name.
storage pool name.
command.
invalid storage pool name.
volume name.
command.
ANR2346E Command: Volume name ″volume name″ is
storage pool name.
not valid for device class device class
name.
ANR2341E Command: Missing next storage pool
Explanation: The command indicated specifies the
name.
name of a volume that cannot be used with the device
Explanation: The command indicated requires a class shown.
storage pool name, but none has been entered.
System Action: The server does not process the command.
command.
User Response: Reissue the command with a storage volume name.
pool name.
ANR2347E Command: Volume name ″volume name″ is
ANR2342E Command: Storage pool description ambiguous; resolves to multiple defined
exceeds maximum characters characters. volume names.
Explanation: The command indicated contains a Explanation: The command shown was entered with a
storage pool description that exceeds the maximum volume name pattern that matches more than one
length allowed. volume. The command can only process a single
volume.
command. System Action: The command is not executed.
User Response: Reissue the command with a valid User Response: Reissue the command with a more
storage pool description. specific volume name.

ANR2348E Command: The ″option″ option is not ANR2353E Command: Device class device class name
valid for a volume assigned to a primary may not be updated.
storage pool.
Explanation: An UPDATE DEVCLASS command
Explanation: The command indicated specifies an specifies the class name DISK, which is a
option that is not valid for a volume in a primary system-defined device class and may not be changed.
storage pool.
command.
User Response: Reissue the command with valid
options for a volume in a primary storage pool.
ANR2354E Command: Device class device class name
is still referenced by one or more
ANR2349E Command: The ″option″ option is not storage pools, or database backup or
valid for a volume assigned to a copy export volumes.
storage pool.
Explanation: The DELETE DEVCLASS command has
Explanation: The command indicated specifies an attempted to delete a device class that has storage
option that is not valid for a volume in a copy storage pools assigned to it, or is referenced by database
pool. backup or export volumes.
command. command.
User Response: Reissue the command with valid User Response: Issue Q DEVCLASS to view the
options for a volume in a copy storage pool. storage pool reference count, Q STGPOOL to determine
which pool references the device class, and Q VOLHIST
to locate database backup or export volume references.
is already defined.
ANR2355E Command: Required parameter is
Explanation: The command indicated has attempted
missing - missing parameter.
to define a device class that already exists.
entered without the required parameter. The required
command.
parameter is shown.
proper syntax.
is not defined.
Explanation: The command indicated references a
ANR2356E Command: Incompatible parameters
device class that does not exist.
specified - first parameter, second
System Action: The server does not process the parameter.
command.
User Response: None. entered with mutually exclusive parameters. The two
parameters are listed.
ANR2352E Command: Device class device class name System Action: The server ignores the command.
may not be deleted.
Explanation: A DELETE DEVCLASS command proper syntax.
specifies the class name DISK, which is a
system-defined device class and may not be deleted.
ANR2357E Command: The DISK device class is not
System Action: The server does not process the supported for copy storage pools.
command.
Explanation: An attempt is made to define a copy
User Response: None. storage pool using a device of DISK. Copy storage
pools can only be assigned to a sequential device class.
command.

User Response: Reissue the command specifying a compression has recently taken place, and the
sequential device class. 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.
is still referenced in the volume history
file. System Action: The server does not process the
command.
Explanation: The DELETE DEVCLASS command has
attempted to delete a device class that is associate with User Response: Reissue the command at a later time.
entries in the volume history file. These entries are for
volumes that contain database backup or export data.
ANR2363E Command: One of the following
System Action: The server does not process the parameter must be supplied but is
command. missing - missing parameter, missing
parameter, missing parameter, missing
User Response: Use the DELETE VOLHIST command
parameter.
to remove that entries before deleting the device class.
entered without one of the mutually exclusive required
ANR2359E Command: Volume name ″volume name″
parameters. One of the parameters from the list must
must be specified with a DISK
be specified.
STGPOOL.
name of a volume that must be specified with a disk User Response: Reissue the command and enter the
storage pool. proper syntax.
command. ANR2364E Command: Missing reclaim-storage pool
name.
volume name and storage pool. Explanation: The command indicated requires a
storage pool name, but none has been entered.
ANR2360E Command: Device class device class name System Action: The server does not process the
may not be used for database backup. command.
Explanation: The command specifies the DISK device User Response: Reissue the command with a storage
class, which cannot be used for database backup, pool name.
backup trigger, or restore operations.
System Action: The server does not process the ANR2365I Backupset backup set name for node node
command. name has been deleted.
User Response: Reissue the command with a valid Explanation: The backup set has been deleted.
device class.
System Action: The server has deleted the backupset.
ANR2361E Command: A full database backup is
required.
ANR2366I Backupset backup set name for node node
Explanation: A BACKUP DB command specified an
name would have been deleted.
incremental backup, but a full backup is required.
Explanation: The backup set would have been deleted
as the result of a DELETE BACKUPSET command, but
command.
the PREVIEW=YES parameter was specified.
full backup.
User Response: If the backup set is to be deleted,
reissue the command without specifying
ANR2362E Command: Database backup is not
PREVIEW=YES.
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

ANR2367I Retention period for backupset backup ANR2371E Command: Database backup trigger is
set name for node node name has been not defined.
updated.
Explanation: The database backup trigger cannot be
Explanation: The backup set’s retention period has updated or deleted because it is not currently defined.
been updated.
System Action: The server has updated the command.
backupset’s retention period.
ANR2372E Command: Database Space trigger is
ANR2368I Retention period for backupset backup already defined.
set name for node node name would have
Explanation: The database space trigger cannot be
been updated.
defined because it is already defined.
Explanation: The backup set’s retention period would
have been updated as the result of an UPDATE
command.
BACKUPSET command, but the PREVIEW=YES
parameter was specified. User Response: Use the UPDATE SPACETRIGGER
command to modify the indicated space trigger
parameters.
User Response: If the backup set is to be updated,
reissue the command without specifying
ANR2373E Command: Database backup trigger is
PREVIEW=YES.
not defined.
Explanation: The database space trigger cannot be
ANR2369I Database backup volume and recovery
updated or deleted because it is not currently defined.
plan file expiration starting under
process process ID. System Action: The server does not process the
command.
Explanation: The server has started expiration
processing to remove expired database backup volumes User Response: None.
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 ANR2374E Command: Recovery Log Space trigger is
value specified on the SET already defined.
DRMDBBACKUPEXPIREDAYS. The recovery plan files Explanation: The recovery log space trigger cannot be
expired is based on the value specified on the SET defined because it is already defined.
DRMRPFEXPIREDAYS. Server inventory expiration
processing deletes the DB backup volumes and System Action: The server does not process the
recovery plan files only if the volumes or plan files are command.
created on the server to server virtual volumes. User Response: Use the UPDATE SPACETRIGGER
System Action: Server operation continues. The command to modify the indicated space trigger
expiration process is cancellable. parameters.

ANR2375E Command: Recovery Log trigger is not
defined.
ANR2370E Command: Database backup trigger is
already defined. Explanation: The recovery log space trigger cannot be
updated or deleted because it is not currently defined.
Explanation: The database backup trigger cannot be
defined because it is already defined. System Action: The server does not process the
command.
command. User Response: None.
User Response: Use the UPDATE

DBBACKUPTRIGGER command to modify the ANR2376I Recovery Log Space trigger defined, but
database backup trigger parameters. 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.

System Action: None. User Response: None.
UPDATE SPACETRIGGER command to set the space ANR2382E Command: Storage pool storage pool name
expansion percentage to a value greater than 0. still contains at least one volume.
Explanation: A DELETE STGPOOL command specifies
ANR2377I Recovery Log Space trigger updated and a storage pool that has volumes assigned to it.
enabled.
Explanation: An UPDATE SPACETRIGGER command command.
has successfully completed for the recovery log space
User Response: Delete the volume belonging to the
trigger. The updated parameters specified on the
storage pool and reissue the command.
command are used to automatically trigger space
expansion for the database.
ANR2383E Command: Storage pool storage pool name
is currently in use by clients and/or data
User Response: None. management operations.
Explanation: The command indicated references a
ANR2378I Recovery Log Space trigger updated, but storage pool that is in use.
disabled.
Explanation: An UPDATE SPACETRIGGER command command.
User Response: Reissue the command at a later time.
trigger. However, the space expansion percentage is
currently set to 0, which disables the space trigger.
ANR2384E Command: Next or Reclaim storage pool
storage pool name introduces a cycle into
User Response: To activate the space trigger, use the the storage pool chain.
UPDATE SPACETRIGGER command with the
Explanation: A DEFINE STGPOOL or UPDATE
SPACEexpansion parameter to set a value greater than
STGPOOL command specifies a next storage pool that
zero.
eventually points to the pool being processed.
ANR2379I Recovery Log Space trigger deleted.
command.
Explanation: A DELETE SPACETRIGGER command
next pool value.
trigger. Space expansions are no longer triggered
automatically for the recovery log.
is in use as the next or reclaim pool for
User Response: None. one or more other storage pools.
Explanation: A DELETE STGPOOL command specifies
ANR2380E Command: Storage pool storage pool name a pool that is the next pool or the reclaim pool for
is not defined. other storage pools.
Explanation: The command indicated specifies the System Action: The server does not process the
name of a nonexistent storage pool. command.
System Action: The server does not process the User Response: If necessary, update other storage
command. pools so that they do not reference the pool to be
deleted, and reissue the command.
storage pool name.
ANR2386E Command: High migration threshold
must be set greater than or equal to the
low migration threshold.
is already defined.
Explanation: A DEFINE or UPDATE STGPOOL
Explanation: A DEFINE STGPOOL command specifies
command has attempted to set the storage pool low
the name of a storage pool that already exists.
migration threshold (LOWMIG) parameter greater than
System Action: The server does not process the the high migration threshold (HIGHMIG).
command.

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

configuration information to file name.
does not successfully complete because the server

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

ANR2401E Command: Volume volume name is not
command.
defined in a storage pool.
name of a storage pool volume that does not exist.
ANR2407E Command: Maximum number of
mirrored copies exceeded.
command.
Explanation: A DEFINE LOGCOPY or DEFINE
DBCOPY command has attempted to add a mirror
volume, but the maximum number of mirrors for the
ANR2402E Command: Volume volume name is already target volume already exists.
online.
Explanation: A VARY ONLINE command specifies the command.
name of a volume that is already online.
command.
ANR2408E Command: Capacity of volume volume
User Response: None. name must be at least as large as
capacity of volume volume name.
ANR2403E Command: Volume volume name is not Explanation: A DEFINE LOGCOPY or DEFINE
online. 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.
name of a volume that is not online.
command.
command.
User Response: Use a larger mirror volume.
ANR2409E Command: Capacity of volume volume

ANR2404E Command: Volume volume name is not
name must be at least 5 megabytes.
available.
Explanation: A define command for a database or log
Explanation: The command indicated has attempted
volume or copy has specified a volume that is too
to access a volume that cannot be found.
small to be used by the server for a database or log
System Action: The server does not process the volume. The minimum size for one of these volumes is
command. 5 megabytes.
User Response: Check the spelling of the volume System Action: The server does not process the
name to ensure it is correct. If the volume does not command.
exist, preallocate it with the appropriate mechanism for
the operating system on which the server is running.
volume that is at least 5 megabytes in size.
ANR2405E Command: Volume volume name is

ANR2410E Command: Unable to access volume
currently in use by clients and/or data
volume name - access mode is set to
management operations.
″unavailable″.
Explanation: The command shown specifies the
name of a data storage volume that is currently in use.
volume whose name is displayed, but the volume
System Action: The server does not process the cannot be accessed because its status is unavailable.
command.
User Response: If necessary, reset the status of the
ANR2406E Command: Volume volume name still volume and reissue the command.
contains data.
Explanation: The indicated command tries to delete a
data storage volume that contains data.

ANR2411E Command: Unable to access associated ANR2415E Command: Deletion operation already in
volume volume name - access mode is set progress for associated volume volume
to ″unavailable″. name.
Explanation: The command shown would require Explanation: The command shown would require
access to the volume whose name is displayed (because access to the volume whose name is displayed (because
data from the volume specified in the command spans data from the volume specified in the command spans
into this volume); the volume shown cannot be into this volume); the volume shown cannot be
accessed because its status is unavailable. accessed because it is in use by a delete volume
operation.
command.
User Response: If necessary, reset the status of the
volume and reissue the command. User Response: Reissue the command after the delete
volume operation ends.
ANR2412E Command: Audit operation already in
progress for volume volume name. ANR2416E Command: Move Data operation already
in progress for volume volume name.
Explanation: The command shown specifies the
volume whose name is displayed, but that volume is Explanation: The command shown specifies the
currently in use by an audit volume operation. volume whose name is displayed, but that volume is
currently in use by a move data operation.
command.
User Response: Reissue the command after the audit
volume operation ends. User Response: Reissue the command after the move
data process ends.
ANR2413E Command: Audit operation already in
progress for associated volume volume ANR2417E Command: Move Data operation already
name. in progress for associated volume volume
name.
Explanation: The command shown would require
access to the volume whose name is displayed (because Explanation: The command shown would require
data from the volume specified in the command spans access to the volume whose name is displayed (because
into this volume); the volume shown cannot be data from the volume specified in the command spans
accessed because it is in use by an audit volume into this volume); the volume shown cannot be
operation. accessed because it is in use by a move data operation.
command. command.
User Response: Reissue the command after the audit User Response: Reissue the command after the move
volume operation ends. data operation ends.
ANR2414E Command: Deletion operation already in ANR2418E Command: Migration operation already
progress for volume volume name. in progress for volume volume name.
Explanation: The command shown specifies the Explanation: The command shown specifies the
volume whose name is displayed, but that volume is volume whose name is displayed, but that volume is
currently in use by a delete volume operation. currently in use by a migration operation.
command. command.
User Response: Reissue the command after the delete User Response: Reissue the command after the
volume operation ends. migration ends.

ANR2419E Command: Migration operation already
command.
in progress for associated volume volume
name. User Response: Issue the VARY OFFLINE command,
and reissue the UPDATE VOLUME command.
Explanation: The command shown would require
access to the volume whose name is displayed (because
data from the volume specified in the command spans ANR2424E Command: Unable to access volume
into this volume); the volume shown cannot be volume name - access mode is set to
accessed because it is in use by a migration operation. ″destroyed″.
System Action: The server does not process the Explanation: The command shown specifies the
command. volume whose name is displayed, but the volume
cannot be accessed because its status is destroyed.
User Response: Reissue the command after the
migration ends. System Action: The server does not process the
command.
ANR2420E Command: Space reclamation operation User Response: If necessary, reset the status of the
already in progress for volume volume volume and reissue the command.
name.
Explanation: The command shown specifies the ANR2425E Command: Unable to access volume
volume whose name is displayed, but that volume is volume name - access mode is set to
currently in use by a reclamation operation. ″offsite″.
System Action: The server does not process the Explanation: The command shown specifies the
command. volume whose name is displayed, but the volume
cannot be accessed because its status is offsite.
reclamation ends. System Action: The server does not process the
command.
ANR2421E Command: Space reclamation operation User Response: If necessary, reset the status of the
already in progress for associated volume and reissue the command.
volume volume name.
Explanation: The command shown would require ANR2426I Backupset backup set name defined for
access to the volume whose name is displayed (because node node name.
data from the volume specified in the command spans
into this volume); the volume shown cannot be Explanation: The backup set has been defined for the
accessed because it is in use by a reclamation operation. indicated node.
System Action: The server does not process the System Action: The server has defined the backupset.
command. User Response: None.
reclamation ends. ANR2427E Backupset backup set name for node node
name was not deleted. Device class device
ANR2422E Command: Volume volume name is not a class name was not found.
defined disk volume. Explanation: The specified backup set was not deleted
Explanation: The command shown specifies a volume because the device class used to generate it was not
name that does not match any known disk volume. found.
System Action: The server does not process the System Action: The backup set is not deleted.
command. User Response: If the device class was inadvertently
User Response: Reissue the command with the correct deleted, redefine it, then delete the backup set again.
volume name.
ANR2428E Backupset backup set name for node node
ANR2423E Command: Volume volume name is still name has not been deleted due to error
online. error code.
Explanation: An UPDATE VOLUME command Explanation: The backup set has not been deleted.
specifies access=unavailable for a disk volume that is System Action: The server has not deleted the
still online. backupset.

User Response: Check related error messages.
ANR2434E Command: Insufficient space on other
database volumes to delete volume
ANR2429E Command: Maximum database capacity volume name.
exceeded.
Explanation: A DELETE DBVOLUME command has
Explanation: Do not allocate any volume that would been entered, but the data on the volume to be deleted
cause the database to exceed 500GB. A subsequent cannot be copied to other volumes due to insufficient
DEFINE DBVOLUME command for that volume would free space.
fail.
command.
User Response: Make more database space available,
User Response: None. and reissue the command.
ANR2430E Command: Volume volume name is already ANR2435E Command: Unable to delete database
defined as a database volume. volume volume name - mirrored copies
not synchronized.
Explanation: A DEFINE DBVOLUME command
specifies the name of a database volume that already Explanation: A DELETE DBVOLUME command has
exists. been entered, but mirrors of the volume to be deleted
are not up to date.
command.
User Response: Try the command at a later time (after
database volumes have been synchronized).
ANR2431E Command: Volume volume name is not a
defined database volume.
ANR2436E Command: Insufficient space to extend
Explanation: A DELETE DBVOLUME command database by requested amount.
specifies the name of a database volume that does not
exist. Explanation: An EXTEND DB command has been
entered, but not enough allocated, unused space is
System Action: The server does not process the available to the database to add the amount of space
command. requested.
User Response: None. System Action: The server does not process the
command.
ANR2432E Command: Maximum number of User Response: Make more database space available,
database volumes exceeded. and reissue the command.
Explanation: A DEFINE DBVOLUME command has
attempted to add more database volumes than the ANR2437E Command: Output error encountered
server can manage. while attempting to extend database.
System Action: The server does not process the Explanation: An EXTEND DB command has been
command. entered, but an I/O error occurs during the command.
command.
ANR2433E Command: A database define, delete, User Response: Reissue the command. If the problem
extend, reduce, or backup operation is persists, identify and remove or repair the volume that
already in progress. caused the error.
Explanation: The specified command has been entered
while a command that is modifying or backing up the ANR2438E Command: Insufficient database space
database is already active. would be available following a
System Action: The server does not process the reduction by the requested amount.
command. Explanation: A REDUCE DB command has been
User Response: Wait for other activity to end, and entered, but the database does not have enough free
reissue the command. space to reduce by the amount specified.

command.
User Response: None. ANR2444E Command: A recovery log define, delete,
extend, or reduce operation is already in
progress.
ANR2439E Command: Unable to vary database
volume volume name offline - mirrored Explanation: The specified command has been entered
copies not synchronized. while a command that is modifying the recovery log is
already active.
Explanation: A VARY OFFLINE command has been
entered, but mirrors of the volume to be varied are not System Action: The server does not process the
up to date. command.
System Action: The server does not process the User Response: Wait for other activity to end, and
command. reissue the command.
database volumes have been synchronized). ANR2445E Command: Insufficient space on other
recovery log volumes to delete volume
volume name.
ANR2440E Command: Unable to vary database
volume volume name offline - only copy. Explanation: A DELETE LOGVOLUME command has
been entered, but the data on the volume to be deleted
Explanation: A VARY OFFLINE command has been
cannot be copied to other volumes due to insufficient
entered, but the database volume has no mirrors and
free space.
therefore contains the only copy of the data on that
volume. System Action: The server does not process the
command.
command. User Response: Make more recovery log space
available, and reissue the command.
ANR2446E Command: Unable to delete recovery log

volume volume name - mirrored copies
defined as a recovery log volume.
not synchronized.
Explanation: A DEFINE LOGVOLUME command
Explanation: A DELETE LOGVOLUME command has
specifies the name of a recovery log volume that
been entered, but mirrors of the volume to be deleted
already exists.
are not up to date.
command.
command.
recovery log volumes have been synchronized).
ANR2442E Command: Volume volume name is not a
defined recovery log volume.
ANR2447E Command: Insufficient space to extend
Explanation: A DELETE LOGVOLUME command recovery log by requested amount.
specifies the name of a recovery log volume that does
Explanation: An EXTEND LOG command has been
not exist.
entered, but there is not enough allocated, unused
System Action: The server does not process the space available to the recovery log to add the amount
command. of space requested.
command.
ANR2443E Command: Maximum number of recovery User Response: Make more recovery log space
log volumes exceeded. available, and reissue the command.
Explanation: A DEFINE LOGVOLUME command

attempts to add more recovery log volumes than the
server can manage.
command.

ANR2448E Command: Output error encountered ANR2453E Command: Unable to reduce recovery log
while attempting to extend recovery log. - log mode must be set to NORMAL.
Explanation: An EXTEND LOG command has been Explanation: A REDUCE LOG command has been
entered, but an I/O error occurs during the command. 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
command.
with a SET LOGMODE command.
User Response: Reissue the command. If the problem
persists, identify and remove or repair the volume that
command.
caused the error.
User Response: Set the log mode to NORMAL with
the SET LOGMODE command, reissue the REDUCE
ANR2449E Command: Insufficient recovery log space
LOG command, and set the log mode back to
would be available following a
ROLLFORWARD with the SET LOGMODE command.
reduction by the requested amount.
If you change the log mode to NORMAL, you can only
Explanation: A REDUCE LOG command has been recover your database to the time of the last complete
entered, but the recovery log does not have enough free database backup.
space to reduce by the amount specified.
System Action: The server does not process the ANR2454E Command: Unable to reduce database -
command. LOGMODE must be set to NORMAL.
User Response: None. Explanation: A REDUCE DB command has been
entered, but the recovery log mode of the server is
currently set to ROLLFORWARD. The database can
ANR2450E Command: Unable to vary recovery log only be reduced when log mode is set to NORMAL
volume volume name offline - mirrored with the SET LOGMODE command.
copies not synchronized.
Explanation: A DELETE LOGVOLUME command has command.
been entered, but mirrors of the volume to be deleted
are not up to date. User Response: Set the log mode to NORMAL with
the SET LOGMODE command, reissue the REDUCE
System Action: The server does not process the DB command, and reset the log mode to
command. ROLLFORWARD with the SET LOGMODE command.
User Response: Try the command at a later time (after If you change the log mode to NORMAL, you can only
recovery log volumes have been synchronized). recover your database to the time of the last complete
database backup.
ANR2451E Command: Unable to vary recovery log

volume volume name offline - only copy. ANR2455E Command: Unable to access associated
volume volume name - access mode is set
Explanation: A VARY OFFLINE command has been to ″destroyed″.
entered, but the recovery log volume has no mirrors
and contains the only copy of the data on that volume. Explanation: The specified command would require
access to the volume whose name is displayed (because
System Action: The server does not process the data from the volume specified in the command spans
command. into this volume); the volume shown cannot be
User Response: None. accessed because its status is destroyed.
ANR2452E Command: Maximum recovery log command.
capacity exceeded. User Response: If necessary, reset the status of the
Explanation: Do not allocate any volume that would volume and reissue the command.
cause the recovery log to exceed 13GB. A subsequent
DEFINE LOGVOLUME command for that volume ANR2456E Command: Unable to access associated
would fail. volume volume name - access mode is set
System Action: The server does not process the to ″offsite″.
command. Explanation: The command shown would require
User Response: None. 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 offsite. User Response: Make sure that the server has proper
authority to write to the file indicated and that
sufficient space is available in the file system for the
command.
file. On MVS, make sure that the data set has been
User Response: If necessary, reset the status of the allocated and that the server has authority to write to
volume and reissue the command. the data set.
ANR2457E Command: Backup of primary storage ANR2461E Command: An internal error was
pool primary pool name to copy storage encountered in writing sequential
pool copy pool name already in progress. volume history information to file name.
Explanation: The command shown specifies a backup Explanation: The BACKUP VOLHISTORY command
operation that is already in progress. does not complete successfully because the server
command.
current backup operation ends. User Response: Examine error messages on the server
message and correct any problems, if possible. Make
ANR2458E Command: Restore of primary storage sure that the server has proper authority to write to the
pool primary pool name (or volumes in file indicated and that sufficient space is available in
that storage pool) already in progress. the file system for the file. On MVS, make sure that the
Explanation: The command shown cannot be data set has been allocated and that the server has
processed because a restore operation involving the authority to write to the data set.
indicated storage pool is already in progress. Either a
RESTORE STGPOOL command is in progress for the ANR2462I Command: Server sequential volume
indicated storage pool or a RESTORE VOLUME history information was written to file
command is in progress for volumes that belong to the name.
indicated storage pool.
System Action: The server does not process the the BACKUP VOLHISTORY command and indicates
command. that sequential volume history information was
User Response: Reissue the command after the successfully written to the file name indicated.
current restore operation ends. System Action: The server records sequential volume
history information to the file name specified.
ANR2459E Command: Volume volume name cannot be User Response: None.
updated - a restore operation involving
that volume is in progress.
ANR2463I Command: Server sequential volume
Explanation: The indicated volume has an access history information was written to all
mode of destroyed. Either a RESTORE STGPOOL configured history files.
command or a RESTORE VOLUME command is in
progress to restore the contents of the indicated Explanation: This message is displayed in response to
volume. the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
System Action: The server does not process the successfully written to all files that were specified in
command. the server options file.
User Response: If necessary, cancel the restore System Action: The server records sequential volume
processing and update the volume. history information to the configured files.
ANR2460E Command: Server could not write
sequential volume history information
to File name. ANR2464I Command: Volume history files have
NOT been defined for automatic history
Explanation: The BACKUP VOLHISTORY command recording - specify a file name for
does not complete successfully because the server recording history information.
System Action: The server does not process the the BACKUP VOLHISTORY. It indicates that sequential
command.

volume history information cannot automatically be User Response: None.
written because no files were defined in the server
options file for recording this information.
ANR2468E Command: An internal server error was
System Action: The sequential volume history encountered while deleting server
information is not written. Server operation continues. sequential volume history information.
User Response: Reissue the BACKUP VOLHISTORY Explanation: The DELETE VOLHISTORY command
command and specify the name of a file for recording fails because an internal server error has been
sequential volume history information. If desired, you encountered.
may configure files that should be automatically
System Action: The DELETE VOLHISTORY command
updated with the VOLUMEHISTORY parameter and
fails, and server operation continues.
restart the server.
User Response: Examine the messages in the activity
log or server console that were displayed prior to the
ANR2465E Command: An I/O error was encountered
error to see if the error can be resolved. Contact your
in writing sequential volume history
service representative if this error cannot be resolved.
information to one or more of the
defined volume history files.
ANR2469E Command: Invalid volume history type:
Explanation: The BACKUP VOLHISTORY command
history type.
does not complete successfully because the server
cannot write to one or more of the defined volume Explanation: The command failed because an invalid
history files. sequential volume history type was specified for the
TYPE= parameter.
command. System Action: The command fails, and server
console that may have been displayed prior to this User Response: Refer to the Administrator’s Reference
message and correct any problems, if possible. Make for an explanation of the valid types for this command.
sure that the server has proper authority to write to the Reissue the command and specify a valid type value.
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 ANR2470I Message output being re-directed to file
authority to write to the data set. file name.
Explanation: The message output is being redirected
ANR2466E Command: An internal server error was to the specified file instead of being displayed at the
encountered in writing sequential console.
volume history information to one or System Action: None.
more of the defined volume history
files. User Response: None.
Explanation: The BACKUP VOLHISTORY command

does not complete successfully because the server ANR2471E Message output re-direction to file file
cannot write to one or more of the defined volume name failed - unable to open file.
history files. Explanation: An error occurs while trying to open the
System Action: The server does not process the file. The message output will not be redirected to the
command. specified file.
User Response: Examine error messages on the server System Action: None.
console that may have been displayed prior to this User Response: Determine the cause of the file open
message and correct any problems, if possible. Contact failure and take corrective action.
your service representative if you are unable to resolve
the problem.
ANR2472E Command: Invalid volume specified:
volume name.
ANR2467I Command: number of entries deleted
sequential volume history entries were Explanation: The command failed because the
successfully deleted. sequential history volume specified is not a DB DUMP,
DB BACKUP, or EXPORT volume.
Explanation: The DELETE VOLHISTORY command
successfully deleted the number of entries specified. System Action: The command fails, and server

ANR2477I License storage auditing is disabled,
valid volume name.
storage values may be outdated and
should be ignored.
ANR2473I Command for volume volume name
Explanation: The license storage occupancy function is
completed.
currently disabled.
Explanation: The command completed and the
volume history file has been updated.
User Response: To obtain storage occupancy results,
System Action: The server records sequential volume
remove the NOAUDITSTORAGE or AUDITSTORAGE
history information.
NO option from the server options file, then restart the
User Response: None. server and issue the AUDIT LICENSES command.
ANR2474E Command: Input volume names must be ANR2478E Command: Command cannot be executed
specified with the VOLumenames= in this session.
parameter.
Explanation: The command indicated is not supported
Explanation: The command failed because input by the session in which it was invoked. For example, a
volume names were not specified with the DEFINE CURSOR command can not be invoked from
VOLumenames parameter. the server’s primary console.
System Action: The command fails. System Action: The server does not process the
command.
User Response: On some platforms, or with certain
device classes, the server cannot prompt to mount User Response: The command must be issued from a
input removable media volumes, so the names of the standard administrator session.
required volumes must be specified in the command.
Reissue the command specifying the name(s) of
ANR2479E Command: Invalid SQL cursor name -
volumes that should be mounted for input.
SQL cursor name.
ANR2475E Command: File file name could not be
invalid SQL cursor name.
opened.
Explanation: The DSMSERV command could not be
command.
completed successfully because the file specified (to
contain the list of volumes to be used) cannot be User Response: Reissue the command with a valid
opened. SQL cursor name.
System Action: The DSMSERV command fails.
ANR2480E Command: SQL cursor name SQL cursor
User Response: Examine the file name that was
name is already defined.
specified in the DSMSERV command. Correct the
specification, if necessary, so that it specifies the name Explanation: The command indicated specifies an SQL
of a file that exists and is accessible by the server cursor name that has already been defined.
program. Reissue the DSMSERV command if this can
be corrected. Contact your service representative if this
command.
error cannot be resolved.
different cursor name.
ANR2476I License storage auditing is disabled, no
output available.
ANR2481E Command: SQL cursor name SQL cursor
Explanation: The license storage occupancy function is
name is not defined.
currently disabled.
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
command.
NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command. User Response: Use the DEFINE CURSOR command
to first define the cursor.

ANR2482E Command: SQL cursor SQL cursor name is ANR2487E Command: An SQL expression is
already open. required.
Explanation: The command indicated failed because Explanation: The command indicated requires that an
an SQL cursor is already open. SQL expression be provided through the SQL keyword
parameter.
command.
User Response: Use the CLOSE CURSOR command
to first close the current cursor. User Response: Reissue the command specifying an
SQL expression.
ANR2483E Command: No SQL cursor is currently
open. ANR2488W Volume list file volume list file name
could not be opened.
Explanation: The command indicated failed because
no SQL cursor is currently open. Explanation: While attempting to read or write a
sequential file for volume list information, the server
cannot open the file name specified.
command.
System Action: The server does not use the volume
User Response: Use the OPEN CURSOR command to
list file.
first open a cursor.
ANR2484E Command: Invalid SQL date-time display
any problems, if possible. For OUTFILE files, make
format - SQL date-time display format
sure that the server has proper authority to write to the
name.
file indicated and that there is sufficient space in the
Explanation: The command indicated contains an file system for the file. On MVS, make sure that the
invalid SQL date-time display format name. server has authority to write to the data set.

command. ANR2489W An error was encountered writing to
volume list file volume list file name.
SQL date-time format 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
ANR2485E Command: Invalid SQL display format - and should not be used for input.
SQL display format name.
System Action: The server stops writing to the file.
invalid SQL display format name. User Response: Examine error messages that may
System Action: The server does not process the any problems, if possible. Make sure that the server has
command. proper authority to write to the file indicated and that
User Response: Reissue the command with a valid there is sufficient space in the file system for the file.
SQL display format name. 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
ANR2486E Command: Invalid SQL character or the volume history file, if it is used.
arithmetic mode - SQL arithmetic mode.
Explanation: The command indicated contains an ANR2490E Command: NODENAMES and
invalid SQL arithmetic mode name. SERVERNAMES parameters cannot
System Action: The server does not process the both be specified in the same command.
command. Explanation: The command indicated failed because
User Response: Reissue the command with a valid both the nodenames parameter and the servernames
SQL arithmetic mode name. parameter were specified.
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 User Response: None.
parameter specified.
ANR2504I Schedule schedule name deleted.
ANR2491I Volume Creation Process starting for
volume name, Process Id process ID.
the DELETE SCHEDULE command. The schedule
Explanation: As a result of a DEFINE VOLUME, named schedule name has been deleted from the server
DEFINE DBVOLUME, or DEFINE LOGVOLUME database.
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. User Response: None.
System Action: The server creates the volume and
adds it to the server. ANR2505I number of schedules schedules were
defined for command.
Explanation: number of schedules were generated and
nodes successfully associated for the command issued.
ANR2500I Schedule schedule name defined in policy
domain domain name. System Action: Server operation continues.
Explanation: This message is displayed in response to User Response: If the number is less than expected,
the DEFINE SCHEDULE command. The schedule check the nodeList and domainList combination specified
named schedule name has been defined in the policy to the DEFINE CLIENTACTION command. Schedules
domain named domain name in the server database. 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
ANR2501I Schedule schedule name deleted from domain name processed. rc=return code.
Explanation: This message is displayed in response to the DEFINE CLIENTACTION WAIT=YES command.
the DELETE SCHEDULE command. The schedule Node node name is associated with the schedule named
named schedule name has been deleted from the policy schedule name in policy domain domain name has been
domain named domain name in the server database. processed. name The result is indicated in the return
code return code.
User Response: If the return code is non-zero, issue
the QUERY ACTLOG command to to view the activity
ANR2502I Schedule schedule name updated in
log and search for the error messages. After the error
has been resolved, restart the scheduled operations.
the UPDATE SCHEDULE command. The schedule
ANR2507I Schedule schedule name for domain
named schedule name has been updated in the policy
domain name started at start timestamp for
domain named domain name in the server database.
node node name completed successfully
System Action: Server operation continues. at timestamp.
User Response: None. Explanation: The scheduled operation for the domain
name and schedule name specified was processed. It was
processed for node node name and completed
ANR2503I Schedule schedule name in domain domain successfully at the indicated time.
name copied to schedule new schedule
name in domain new domain name. System Action: Server operation continues.
Explanation: This message is displayed in response to User Response: This message is intended to report the
the COPY SCHEDULE command. The schedule named completion state of a scheduled client action. This
schedule name in policy domain domain name has been message indicates that the scheduled action completed
copied to the schedule named new schedule name in the successfully.
policy domain named new domain name. Node
associations have not been copied.

ANR2510I Node node name associated with ANR2521I Event record retention period set to days
schedule schedule name in policy domain days.
domain name.
Explanation: This message is displayed in response to the SET EVENTRETENTION command. It indicates the
the DEFINE ASSOCIATION command. Node node name number of days for which event records are retained in
is associated with the schedule named schedule name in the database.
policy domain domain name. Schedule schedule name is
now applied to node node name.
ANR2522I Randomization set to percent percent.
ANR2511I Node node name disassociated from
the SET RANDOMIZE command. It indicates the
schedule schedule name in policy domain
percentage of the startup window over which the start
domain name.
times for individual clients are distributed.
the DELETE ASSOCIATION command. Node node name
is no longer associated with the schedule named User Response: None.
schedule name in policy domain domain name.
System Action: Server operation continues. ANR2523I Schedule query period set to hours
hour(s).
the SET QUERYSCHEDPERIOD command. It indicates
ANR2512I Event records deleted: record count.
the number of hours between attempts by the client to
Explanation: This message is displayed in response to contact the server for scheduled commands.
the DELETE EVENT command. A total of record count
event records have been deleted from the database.
ANR2524I Schedule query period reset to value
determined by each client.
ANR2513I Schedule schedule name copied to
schedule new schedule name.
the SET QUERYSCHEDPERIOD command.
the COPY SCHEDULE command. The schedule named
schedule name has been copied to the schedule named User Response: None.
new schedule name.
System Action: Server operation continues. ANR2525I Maximum number of command retries
set to retries.
the SET MAXCMDRETRIES command. It indicates the
ANR2520I Scheduled sessions set to percent
maximum number of times the client scheduler retries
percent.
a command after a failed attempt to process a
Explanation: This message is displayed in response to scheduled command.
the SET MAXSCHEDSESSIONS command. It indicates
the percentage of total server sessions that can be used
for the processing of scheduled work. User Response: None.
ANR2526I Maximum number of command retries
reset to value determined by each client.
the SET MAXCMDRETRIES command.

ANR2532I Schedule schedule name updated.
ANR2527I Retry period set to minutes minutes.
the UPDATE SCHEDULE command. The schedule
Explanation: This message is displayed in response to named schedule name has been updated in the server
the SET RETRYPERIOD command. It indicates the database.
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. User Response: None.
ANR2533I Client action schedule duration set to
days days.
ANR2528I Retry period reset to value determined
the Set CLIENTACTDuration command. It indicates the
by each client.
number of days for which schedules and associations
Explanation: This message is displayed in response to generated by the DEFine CLIENTAction are retained in
the SET RETRYPERIOD command. the database.
ANR2529I Scheduling mode set to POLLING. ANR2534I Client action schedule schedule name was
not executed by node name in domain
Explanation: This message is displayed in response to name.
the SET SCHEDMODES command. With client-polling
scheduling, a client queries the server at prescribed Explanation: Immediate client action schedule name
time intervals to obtain scheduled work or to ensure was not executed by node node name, which is in
that the schedules the client is waiting to process have domain domain name. The schedule is being deleted.
not changed.
ANR2535E Command: The node node name cannot be
ANR2530I Scheduling mode set to PROMPTED. removed or renamed because it has an
associated data mover.
the SET SCHEDMODES command. With Explanation: You attempted to remove or rename a
server-prompted scheduling, the server contacts the node that has an associated data mover.
client when scheduled work needs to be performed and
System Action: The server does not remove or rename
a session is available.
the node.
User Response: To remove or rename the node, delete
User Response: None. the associated data mover and reissue the command.
ANR2531I Scheduling mode set to ANY. ANR2536E Command: The ″option″ option is not
valid with the storage pool’s data
Explanation: This message is displayed in response to format.
the SET SCHEDMODES command. The server now
allows clients to run in either the client-polling or the Explanation: The command indicated includes an
server-prompted scheduling mode. option that is not valid with the specified (or defaulted)
data format for the storage pool.
User Response: Reissue the command with options
appropriate for the desired data format of the storage
pool.

User Response: Execute the AUDITDB operation
specifying FIX=YES so that the activation information
has a device type that is not allowed for
can be corrected.
this operation.
Explanation: The device class in the indicated
ANR2551I command name: Administrative schedule
command has a device type that is not allowed for this
schedule name does not have valid
operation.
activation information - activation
System Action: The server does not process the information will be deleted.
command.
Explanation: This message is displayed during a
User Response: Choose a different device class and database audit and indicates that the ’ACTIVE=YES or
reissue the command. NO’ information is not recorded correctly for an
administrative schedule in the server database. The
audit operation corrects this discrepancy by removing
ANR2538E Command: Backup set cannot be
the invalid activation information.
generated for NAS node node name.
System Action: Server database audit operation
Explanation: Backup sets cannot be generated for
continues.
NAS nodes.
User Response: The named administrative schedule
will now appear to be inactive in the server database
User Response: None. (as if ACTIVE=NO was specified). If you want this
schedule to be active, execute the UPDATE SCHEDULE
command with the ACTIVE=YES parameter to activate
ANR2539E Command: Storage pool Storage Pool Name the schedule when the server is restarted.
does not have a valid data format.
Explanation: The data format of the indicated storage ANR2560I Schedule manager started.
pool is not valid for the requested operation. The
storage pool must have NATIVE or NONBLOCK data Explanation: The schedule manager is started when
format. The server is unable to perform the requested the server is initialized. The schedule manager
operation. maintains entries of scheduled operations.
System Action: The command fails. System Action: Server operation continues.
User Response: Choose a different storage pool with User Response: None.
the appropriate data format and reissue the command.
ANR2561I Schedule prompter contacting node name
ANR2540E Command: The ″option″ device class is not (session session number) to start a
valid with the storage pool’s data scheduled operation.
format.
Explanation: The schedule prompter contacts the
Explanation: The command indicated specifies a client scheduler for node node name because a
device class that is not valid with the specified (or scheduled operation should be started for that node.
defaulted) data format for the storage pool.
command.
User Response: Reissue the command with a data
ANR2562I Automatic event record deletion started.
class appropriate for the desired data format of the
storage pool. Explanation: A process has been started to delete
event records for which the retention period has
elapsed.
ANR2550W command name: Administrative schedule
schedule name does not have valid System Action: Server operation continues.
activation information.
database audit and indicates that the ’ACTIVE=YES or
ANR2563I Removing event records dated prior to
NO’ information is not recorded correctly for an
date time.
administrative schedule in the server database.
Explanation: Events that were scheduled to start prior
to date time are automatically deleted unless their
continues.
startup window has not yet elapsed.

ANR2571W Scheduled session from node node name
User Response: None. (platform name) has been denied,
scheduled sessions are not currently
available.
ANR2564I Automatic event record deletion ended -
record count records deleted. Explanation: The client scheduler for node node name
attempts to connect with the server, but is denied a
Explanation: The event deletion process has ended. A session. All sessions that have been allocated for
total of record count event records have been deleted scheduled operations are already in use.
from the database.
User Response: Issue the QUERY OPTION command
User Response: None. to determine if the option DISABLESCHEDS YES has
been specified in the server options file. If so,
ANR2565I schedules schedules for immediate client scheduling can be enabled by updating the server
actions have been deleted. options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied
Explanation: A total of schedules that were generated in the server options file, change the total number of
by the DEFINE CLIENTACTION command have sessions by altering the MAXSESSIONS parameter in
expired and been deleted from the database. the server options file and then restarting the server.
System Action: Server operation continues. The percentage of sessions that are available for
scheduled operations can be increased by using the SET
User Response: None. MAXSCHEDSESSIONS command.
ANR2566E An error occurred while deleting ANR2572W Schedule prompter session to node node
immediate client action schedules. name has been denied, scheduled
Explanation: Processing did not complete for deleting sessions are not currently available.
schedules that were generated by the DEFINE Explanation: The server attempts to prompt the client
CLIENTACTION command. scheduler for node node name, but all sessions that have
System Action: Server operation continues. been allocated for scheduled operations are already in
use.
User Response: Check the activity log for other
messages that might relate to this failure. Correct any System Action: The server continues to attempt
memory or space problems. contact with the client scheduler until the startup
window for the scheduled event has elapsed.
ANR2570W A scheduled session has been denied. User Response: To change the total number of
The schedule manager is not active. sessions, alter the MAXSESSIONS parameter in the
server options file and then restart the server. The
Explanation: The client scheduler attempts to connect percentage of sessions that are available for scheduled
with the server, but it is denied a session because the operations can be increased by using the SET
schedule manager is not active. MAXSCHEDSESSIONS command.
System Action: Server operation continues, but central
scheduling is not operational. ANR2573W Sufficient memory is not available for
the central scheduler - will retry in
User Response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
been specified in the server options file. If so, Explanation: The server suspends central scheduler
scheduling can be enabled by updating the server processing because sufficient server memory is not
options file with DISABLESCHEDS NO and restarting available.
the server. If DISABLESCHEDS YES was not specfied
in the server options file, determine the source of the System Action: Server operation continues; the
error by examining the QUERY ACTLOG command to scheduler operation will be retried after the specified
view the activity log and search for messages. After the delay.
error has been resolved, restart the server to restore User Response: Allocate additional storage to the
central scheduler operations. If the error cannot be server. For details, issue HELP MEMORY to display the
isolated and resolved, contact your service information online or see “Appendix A. Allocating
representative. Additional Server Memory”.

ANR2574W Insufficient recovery log space available
for the central scheduler - will retry in
number of seconds seconds. ANR2578W Schedule schedule name in domain domain
name for node node name has missed its
Explanation: The server suspends central scheduler
scheduled start up window.
processing because sufficient recovery log space is not
available. Explanation: This message is displayed when the
scheduled startup window for this schedule has passed
and the schedule has not begun.
scheduler operation will be retried after the specified
delay. System Action: Server operation continues. The
scheduled operation is not processed by the server.
User Response: To increase the amount of log space
available to the server, an authorized administrator can User Response: Ensure that a scheduled session for
add log volumes by using the DEFINE LOGVOLUME node node name has been initiated from the client to the
command, and can extend the size of the log by using server. Refer to Administrator’s Guide and Administrator’s
the EXTEND LOG command. Reference for more information on setting up scheduling
operations.
ANR2575W Insufficient database space available for
the central scheduler - will retry in ANR2579E Schedule schedule name in domain domain
number of seconds seconds. name for node node name failed (return
code return code).
Explanation: The server suspends central scheduler
processing because sufficient database space is not Explanation: This message is displayed when a client
available. reports failure in executing a scheduled action. The
return code reported by the client is displayed.
scheduler operation will be retried after the specified System Action: Server operation continues.
delay.
User Response: Examine the node’s schedule log to
User Response: To increase the amount of database determine the cause for the failure.
DEFINE DBVOLUME command, and can extend the ANR2580E Schedule schedule name in domain domain
size of the log by using the EXTEND DB command. name for node node name failed.
ANR2576W An attempt was made to update an server finds that a scheduled start window has elapsed
event record for a scheduled operation for a client schedule and the client is not currently
which has already been executed - running the schedule.
multiple client schedulers may be active System Action: Server operation continues.
for node node name.
User Response: Examine the node’s schedule log to
Explanation: The server has attempted to update an determine the cause for the failure. Ensure that the
event record for a scheduled operation for the specified client scheduler is started.
client node. However, the existing event record shows
that this scheduled operation has already been
executed, either successfully or unsuccessfully. Two or ANR2600E Command: Invalid schedule name -
more client schedulers may be running for this node. schedule name.
System Action: Server operation continues. The Explanation: The specified command has been issued
existing event record is not modified. No further with an invalid schedule name.
processing is performed for this scheduled operation. System Action: Server operation continues, but the
User Response: Contact the user for this client node, command is not processed.
and make sure that only one client scheduler is User Response: Issue the command with a valid
running. schedule name.
ANR2577I Schedule schedule name defined. ANR2601E Command: Schedule description exceeds
Explanation: This message is displayed in response to maximum length characters.
the DEFINE SCHEDULE command. The schedule Explanation: The specified command has been issued
named schedule name in the server database. with a description that exceeds the maximum length.

System Action: Server operation continues, but the
ANR2607E Command: Invalid start time - time.
Explanation: The specified command has been issued
User Response: Issue the command and specify a
with an invalid start time.
valid description.
ANR2602E Command: Invalid action - action.
valid start time.
with an invalid action.
ANR2608E Command: Invalid duration - duration.
with an invalid duration.
valid action.
ANR2603E Command: Options string exceeds
maximum length characters. User Response: Issue the command and specify a
valid duration.
with an options string that exceeds the maximum
length. ANR2609E Command: Invalid duration units -
duration units.
command is not processed. Explanation: The specified command has been issued
with an invalid value for duration units.
User Response: Issue the command with a valid
options string. System Action: Server operation continues, but the
ANR2604E Command: Objects string exceeds User Response: Issue the command and specify a
maximum length characters. valid value for duration units.
with an objects string that exceeds the maximum ANR2610E Command: Invalid period - period.
length.
System Action: Server operation continues, but the with an invalid period.
User Response: Issue the command with a valid command is not processed.
objects string.
valid period.
ANR2605E Command: Invalid priority - priority.
Explanation: The specified command has been issued ANR2611E Command: Invalid period units - period
with an invalid priority. units.
System Action: Server operation continues, but the Explanation: The specified command has been issued
command is not processed. with an invalid value for period units.
User Response: Issue the command and specify a System Action: Server operation continues, but the
valid priority. command is not processed.
ANR2606E Command: Invalid start date - date. valid value for period units.
with an invalid start date. ANR2612E Command: Invalid day of week - day of
week.
with an invalid value for day of the week.
valid start date. System Action: Server operation continues, but the

User Response: Issue the command and specify a System Action: Server operation continues, but the
valid value for day of the week. command is not processed.
User Response: Issue the command using a schedule
ANR2613E Command: Invalid expiration - date. that has already been defined for this domain.
with an invalid expiration date. ANR2618E Command: Schedule schedule name is
already defined in policy domain domain
name.
with a schedule name that has already been defined for
valid expiration date.
the indicated policy domain.
ANR2614E Command: Invalid combination of the
following parameters: duration, duration
units, period, period units. User Response: Issue the command using a schedule
that has not already been defined for this domain.
with an invalid combination of the DURATION,
DURUNITS, PERIOD, and PERUNITS parameters. This ANR2619E Command: Currently defined period
message may be displayed if the duration of the period is invalid with updated period
startup window for the schedule is not shorter than the units.
period between windows. This message may also be
displayed if DURUNITS=INDefinite is specified, but
with a value for period units that is not allowed with
PERUNITS=Onetime is not specified.
the existing period.
User Response: Issue the command and specify a new
valid combination of parameters.
period.
ANR2615E Command: Expiration date date has

ANR2620E Command: Currently defined duration
elapsed.
duration is invalid with updated
Explanation: The specified command has been issued duration units.
with an elapsed expiration date date.
System Action: Server operation continues, but the with a value for duration units that is not allowed with
command is not processed. the existing duration.
User Response: Issue the command and specify an System Action: Server operation continues, but the
expiration date that has not already elapsed. command is not processed.
User Response: Issue the command and specify a new
ANR2616E Command: Start date start date must be duration.
earlier than expiration date expiration.
Explanation: The specified command has been issued 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
User Response: Issue the command and specify
start date that is earlier than the expiration date.
different schedules.
ANR2617E Command: Schedule schedule name is not

ANR2622E Command: No new node associations
defined in policy domain domain name.
added.
with a schedule name that has not been defined in the
but no new node associations are defined.
indicated policy domain.

ANR2628E Command: Invalid date - date.
command has no effect.
with an invalid date.
different nodes.
ANR2623E Command: No node associations deleted.
User Response: Issue the command with a valid date.
but no node associations are deleted.
ANR2629E Command: Invalid time - time.
command has no effect. Explanation: The specified command has been issued
with an invalid time.
different nodes. System Action: Server operation continues, but the
ANR2624E Command: No matching nodes registered. User Response: Issue the command with a valid time.
Explanation: No matching nodes are found for the
specified command. ANR2630E Command: Event deletion is already in
process.
while event deletion is already in progress.
different nodes. System Action: Server operation continues, but the
ANR2625E Command: No matching nodes registered User Response: Wait for event deletion to complete
in policy domain domain name. before issuing the command.
Explanation: The specified command has been issued,
but no matching nodes are registered in the indicated ANR2631E Command: Invalid begin date - date.
policy domain.
System Action: Server operation continues, but the with an invalid begin date.
User Response: Issue the command and specify command is not processed.
different nodes.
User Response: Issue the command with a valid begin
date.
ANR2626E Command: Invalid value for replace -
replace.
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
User Response: Issue the command with a valid begin
value for replace.
time.
ANR2627E Command: Invalid value for format -

ANR2633E Command: Invalid end date - date.
format.
with an invalid end date.
with an invalid value for format.
User Response: Issue the command with a valid end
User Response: Issue the command using a valid
date.
value for format.

ANR2634E Command: Invalid end time - time. ANR2642E Command: Invalid percentage for
randomization - value.
with an invalid end time. Explanation: The specified command has been issued
with an invalid value.
command is not processed. System Action: Server operation continues, but the
User Response: Issue the command with a valid end
time. User Response: Issue the command with a valid
value.
ANR2635E Command: Invalid time range - Begin:
begin End: end. ANR2643E Command: Invalid schedule query period
- value.
with an invalid time range. This occurs if the date and Explanation: The specified command has been issued
time for the beginning of the time range (begin) do not with an invalid value.
precede the date and time for the end of the time range
(end).
value.
User Response: Issue the command with a valid time
range.
ANR2644E Command: Invalid maximum number of
command retries - value.
ANR2636E Command: Invalid value for exceptions
only - exceptions only.
with an invalid value for exceptions only.
value.
User Response: Issue the command with a valid value
for exceptions only.
ANR2645E Command: Invalid retry period - value.
ANR2640E Command: Invalid percentage of sessions
for scheduled processing - value.
value.
ANR2646E Command: Invalid scheduling mode -
value.
value.
ANR2641E Command: Invalid event record retention
period - value.
value.
ANR2647E Command: Invalid type - type.
value.
with an invalid type.

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

ANR2700E Schedule manager aborted. ANR2707E Out of server log space in central
scheduler.
Explanation: The schedule manager has ended
because of an error condition and is not able to Explanation: The server ends a database update
maintain entries for scheduled operations. transaction for the central scheduler because sufficient
log space is not available on the server.
central scheduler is not operational. System Action: Server operation continues, but the
database update fails.
examine server messages issued prior to this message. User Response: An authorized administrator can use
Issue the QUERY ACTLOG command to view the the DEFINE LOGVOLUME command to add volumes
activity log and search for messages. After the error has for use by the log and can issue the EXTEND LOG
been resolved, restart the server to restore central command to extend the size of the log so that the new
scheduler operations. If the error cannot be isolated and volumes are used.
resolved, contact your service representative.
ANR2708E Out of server database space in central
ANR2701E The schedule manager could not be scheduler.
started: diagcode.
Explanation: The schedule manager cannot be started transaction for the central scheduler because sufficient
during initialization because sufficient memory is not database space is not available on the server.
available. Diagnostic code diagcode is issued.
System Action: Initialization fails. database update fails.
User Response: Allocate additional storage to the User Response: An authorized administrator can use
server. For details, issue HELP MEMORY to display the the DEFINE DBVOLUME command to add volumes
information online or see “Appendix A. Allocating for use by the database and can use the EXTEND DB
Additional Server Memory”. command to extend the size of the database so that the
ANR2702E The schedule prompter could not be
started: diagcode. ANR2709E Schedule manager : Unable to start
event record deletion.
Explanation: The schedule prompter cannot be started
during initialization because sufficient memory is not Explanation: Event record deletion cannot be started
available. Diagnostic code diagcode is issued. because sufficient memory is not available.
System Action: Initialization fails. System Action: Server operation continues, but event
records are not automatically deleted after their
retention period has elapsed.
information online or see “Appendix A. Allocating User Response: Allocate additional storage to the
Additional Server Memory”. server. For details, issue HELP MEMORY to display the
ANR2703E Schedule prompter aborted.
Explanation: The schedule prompter ends because of a
ANR2712E Node node1 requested scheduling
processing error.
information for node node2 - session
System Action: Server operation continues, but rejected.
prompted scheduling is not operational.
Explanation: A request for pending scheduled
User Response: To determine the source of the error, operations has been sent from the client scheduler for
examine server messages issued prior to this message. node node1. However, the request is for scheduling
Issue the QUERY ACTLOG command to view the information concerning another node node2.
activity log and search for messages. After the error has
been resolved, restart the server to restore central
client scheduler for node node1 will not be able to
scheduler prompting operations. If the error cannot be
process pending operations.
isolated and resolved, contact your service
representative. User Response: Try restarting the client scheduler for
node node1. If the problem persists, contact your service
representative to resolve the client program error.

System Action: Server operation continues, but node
ANR2713E Node node1 trying to start scheduled
node name is not prompted to start the scheduled
operation for node node2 - session
operation. If operations should be started for other
rejected.
nodes, the server will attempt to prompt the client
Explanation: The client scheduler for node node1 has schedulers for these nodes. This error is usually caused
attempted to execute a scheduled operation for another by network outages or the client scheduler program not
node, node2. being run on the client node.
System Action: Server operation continues, but the User Response: Verify that the address type and
scheduled operation is not processed. address are correct for this client. The only valid
address type is 1 (for TCP/IP). Make sure the client
User Response: Try restarting the client scheduler for
scheduler is not using an invalid address, obtained at
node node1. If the problem persists, contact your service
the time the client scheduler was started, from either
representative to resolve client program error.
the client’s options file or from the command line.
Verify that the client scheduler for node node name is
ANR2714E Node node1 trying to report scheduled running and that the necessary communication links to
operation results for node node2 - that scheduler are operational.
session rejected.
Explanation: The client scheduler for node node1 has ANR2717E Schedule prompter cannot contact client
attempted to report the results of a scheduled operation node name using address type (address
using another node name, node2. type).
System Action: Server operation continues, but the Explanation: The server attempts to prompt the client
results that were sent from node node1 are not be stored scheduler for node node name because scheduled work
in the server’s database. should be started. However, either the server does not
support address type address type needed for
User Response: Try restarting the client scheduler for server-prompted scheduling, or the communication
node node1. If the problem persists, contact your service method is not currently available. The only valid
representative to resolve the client program error. address type is 1 (for TCP/IP).
ANR2715E Client node node name unable to register server does not prompt node node name.
valid address for server prompting: type
address type (high address low address). User Response: If the server does not support the
address type specified, clients may only use the polling
Explanation: The client scheduler for node node name mode of scheduling. If the communication method is
has attempted to register an invalid address for temporarily not available, prompted mode scheduling
server-prompted central scheduling. The address was will resume after the communication problem is fixed
type address type with high-level field high address and and service restored. If the problem persists, contact
low-level field low address. The only valid address type your service representative.
is 1.
System Action: Server operation continues, but the ANR2718W Schedule manager disabled.
node node name will not be prompted to perform
scheduled operations. Explanation: The schedule manager has been disabled
because the DISABLESCHEDS YES option was
User Response: Verify that the address type and specified in the server options file.
address are correct for this client. The only valid
address type is 1 (for TCP/IP). Make sure the client System Action: Server operation continues, but the
scheduler is not using an invalid address obtained from central scheduler is not operational.
the client’s options file or from the command line when
User Response: To enable the schedule manager,
the client scheduler was started.
specify DISABLESCHEDS NO in the server options file
and restart the server.
ANR2716E Schedule prompter was not able to
contact client node name using type
ANR2750I Starting scheduled command schedule
address type (high address low address).
name ( scheduled command ).
Explanation: The server has attempted to prompt the
client scheduler for node node name because a
server starts the execution of a scheduled command.
scheduled operation should be started. The server is
The name of the schedule and the actual command
unable to contact the client by using address type
scheduled is displayed.
address type, with high-level field high address and
low-level field low address. System Action: Server operation continues, the
scheduled command is processed.

ANR2756I Scheduled command schedule name
started successfully.
ANR2751I Scheduled command schedule name
completed successfully.
server successfully starts processing of a background
Explanation: This message is displayed when the process for a scheduled command.
server successfully completes processing of a scheduled
command.
ANR2757E Command: The NODES parameter cannot
be used when querying events for
ANR2752E Scheduled command schedule name administrative schedules.
failed.
Explanation: A QUERY EVENT command has been
Explanation: This message is displayed when the issued with TYPE=ADMINISTRATIVE and the NODES
server encounters a failure in processing a scheduled parameter both specified. The NODES parameter
command. cannot be specified when querying events for
administrative schedules.
System Action: Server operation continues. The
scheduled command is ended. System Action: Server operation continues, but the
User Response: Examine messages issued prior to this
message and use the UPDATE SCHEDULE command User Response: Issue the command without the
to correct the scheduled command. The QUERY EVENT NODES parameter.
command may also be used to determine the cause of
the failure for this scheduled command.
ANR2758E Please specifiy a tracefile name with
less than 37 characters if it is fully
ANR2753I (Schedule name):command response qualified or 26 characters if it is not
fully qualified.
Explanation: This message is used to display the
server response to a scheduled command. The name of Explanation: The .template file adds 9 more characters
the command schedule is included at the beginning of to the end of the filename.
the message in parentheses.
User Response: Reduce the filename length to a
scheduled command is ended.
working range for s390 system
ANR2780W Command: Updates for nodes previously
ANR2754E DEFINE SCHEDULE or UPDATE processed during this command will be
SCHEDULE parameter CMD=’command’ rolled back.
- Unknown command.
Explanation: An error has occurred during an
Explanation: The specified command is not a valid UPDATE NODE operation. If the UPDATE NODE
server command. command was processing more than one node, updates
for nodes which were previously processed will be
System Action: The DEFINE SCHEDULE or UPDATE rolled back.
SCHEDULE command is not processed.
User Response: Reissue the correct command.
User Response: Correct the error and reissue the
command.
ANR2755E DEFINE SCHEDULE or UPDATE
SCHEDULE parameter CMD=’command’
- not eligible for scheduling. ANR2800E The license manager cannot be started:
diagcode.
Explanation: The specified command is not eligible for
scheduling. Explanation: The license manager cannot be started
during initialization because sufficient memory is not
System Action: The DEFINE SCHEDULE or UPDATE available. Diagnostic code diagcode is issued.
SCHEDULE command is not processed.

server. For details, issue HELP MEMORY to display the DEFINE DBVOLUME command, and can extend the
information online or see “Appendix A. Allocating size of the log using the EXTEND DB command.
ANR2807E Out of server log space in license
ANR2803I License manager started. manager.
Explanation: The license manager is started when the Explanation: The server ends a database update
server is initialized. The license manager monitors transaction for the license manager because sufficient
license compliance. recovery log space is not available on the server.
System Action: Server operation continues. System Action: Server operation continues, but the
User Response: An authorized administrator can use
ANR2804W Insufficient memory is available for the
for use by the log and can issue the EXTEND LOG
license manager - will retry in number of
seconds seconds.
volumes are used.
Explanation: The server suspends license manager
processing because sufficient server memory is not
ANR2808E Out of server database space in license
available.
manager.
System Action: Server operation continues; the license
manager operation will be retried after the specified
transaction for the license manager because sufficient
delay.
database space is not available on the server.
Additional Server Memory”. User Response: An authorized administrator can use
for use by the database and can use the EXTEND DB
ANR2805W Insufficient recovery log space available
for the license manager - will retry in
ANR2811I Audit License completed - Server is in
processing because sufficient recovery log space is not
available.
Explanation: The results from the AUDIT LICENSES
command indicate the server is in compliance with the
terms of the current license.
delay.
User Response: To increase the amount of log space
available to the server, an authorized administrator can User Response: None.
add log volumes using the DEFINE LOGVOLUME
command, and can extend the size of the log using the
ANR2812W License Audit completed - ATTENTION:
EXTEND LOG command.
Server is NOT in compliance with
license terms.
ANR2806W Insufficient database space available for
Explanation: The results from the AUDIT LICENSES
the license manager - will retry in
command indicate the server is not in compliance with
the terms of the current license.
processing because sufficient database space is not
REGISTER NODE command or backup-archive
available.
requests, or both, will fail.
delay.
compliance.
administrator can add database volumes using the

ANR2813I Server is licensed for a capacity of ANR2818I Command: Licensed capacity is capacity
capacity gigabytes and number of clients GB with number of clients clients.
clients.
Explanation: This message displays the license
Explanation: This message is issued during server information that existed before issuing the REGISTER
startup. LICENSE command.
System Action: Server operation continues. System Action: None.
ANR2814I Audit command: License audit period ANR2819I Command: Licensed capacity changed to
changed to number of days days. capacity GB with number of clients clients.
Explanation: This message is displayed in response to Explanation: The license information has been
the SET LICENSEAUDITPERIOD command used to changed to the indicated values with the REGISTER
change the interval in days between automatic license LICENSE command.
audits.
User Response: To implement the changed license
User Response: None. information, issue an AUDIT LICENSES command or
wait until an automatic license audit occurs.
ANR2815E Command: Invalid value specified for
interval between license audits - value. ANR2820I Automatic license audit started as
process process ID.
with an invalid value. Explanation: A background process has been started
to audit the server for license compliance.
command is not processed. 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
value.
is licensed.
ANR2816E Command: License audit or register
status of the background process using the QUERY
operation already in progress.
PROCESS command.
Explanation: The server is currently performing a
register license or license audit.
ANR2821E Automatic license audit could not be
System Action: The server does not process the started: diagcode.
specified command.
Explanation: The license manager cannot start an
User Response: Reissue the command after the license automatic process to audit server licenses because
audit process or the register license command ends. sufficient memory is not available. Diagnostic code
Only one REGISTER LICENSE command or AUDIT diagcode is issued.
LICENSE process can be running at a time. The
REGISTER LICENSE command and the AUDIT
LICENSE process may not run at the same time. User Response: Allocate additional storage to the
ANR2817I Command: License audit started as
process process ID.
Explanation: A background process has been started
to audit the server for license compliance.
Explanation: The license audit operation has been
System Action: The server checks the existing
cancelled and will end when resources have been freed
configuration for the server and compares it against the
for the background process. This message may be
values for which the server is licensed.
displayed in response to a QUERY PROCESS command
User Response: The administrator may query the for an AUDIT LICENSES operation.
PROCESS command, or cancel the process with the
CANCEL PROCESS command. User Response: None.

ANR2823I Have audited number of nodes nodes
Explanation: An AUDIT LICENSES operation is in
User Response: Reissue the command after waiting 10
progress. The process has audited the specified number
minutes. If this message is displayed after a number of
of nodes. This message may be displayed in response
retry attempts, contact your service representative.
to a QUERY PROCESS command for an AUDIT
LICENSES operation.
ANR2833I Command: Auditing license definitions.
Explanation: The server has started to audit database
definitions that describe licensing information.
ANR2824I License audit process process number
continues.
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 ANR2834W License Audit completed - WARNING:
that have been audited before the operation ended are Server is NOT in compliance with
reported in the message. license terms.
System Action: The server process is ended and Explanation: The results from the AUDIT LICENSES
server operation continues. command indicate that the server is not in compliance
with the terms of the current license.
REGISTER NODE command fails.
ANR2825I License audit process process number
completed successfully - number of nodes User Response: Use the QUERY LICENSE command
nodes audited. to determine the license terms that are no longer in
compliance. Remove nodes or purchase additional
Explanation: A background server process to audit
client node connections. After these actions have been
server licenses has completed successfully after
taken, reissue the AUDIT LICENSES command to
auditing the specified number of nodes.
resynchronize the server configuration with license
System Action: The server process is ended and terms.
User Response: None. ANR2836I Command: License audit started as
process process ID.
ANR2826I License audit process process number Explanation: A background process has been started
terminated in error - number of nodes to audit the server for license compliance.
nodes audited.
System Action: The server checks registered nodes for
Explanation: A background server process to audit the server and compares this against the value for
server licenses encounters an error and is ended. The which the server is licensed.
number of nodes that have been audited before the
operation ended is reported in the message.
status of the background process using the QUERY
System Action: The server process is ended and PROCESS command, or cancel the process with the
server operation continues. CANCEL PROCESS command.
ANR2839I Automatic license audit started as
process process ID.
ANR2832I Command: The License Manager has not
yet completed initialization - please Explanation: A background process has been started
retry this command later. to audit the server for license compliance.
Explanation: While attempting to process the specified System Action: The server checks registered nodes
license command, the server detects that the licensing and compares them against the value for which the
component of the server had not completed server is licensed.
initialization. The licensing facility used on some
platforms may require some time to initialize because
network calls are involved, and waits may occur.
PROCESS command.

ANR2841W Server is NOT IN COMPLIANCE with ANR2860I Server is licensed to support Tivoli
license terms. Disaster Recovery Manager.
Explanation: This message is issued periodically when Explanation: This message is issued during server
the server configuration does not comply with the startup.
terms for which it is licensed.
to display the current server configuration with respect
ANR2900W The character string ’string’ was
to licensed terms to discover which factors of the
truncated during assignment.
configuration do not conform to your license. Contact
your service representative to obtain more licenses, if Explanation: Truncation occurred during assignment
required. 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
ANR2852I Current license information:
target type CHAR(2) without loss of trailing characters.
Explanation: This message is issued during a
System Action: This warning can occur before or after
REGISTER LICENSE command to display the current
SQL query processing, but does not terminate query
licensing information for the server before the new
processing.
license has been interpreted by the command. Messages
appearing after this message display the factors under User Response: None.
which the server is currently licensed.
System Action: Server operation continues. ANR2901W The result of character string
concatenation was truncated.
Explanation: Truncation occurred when the
concatenation of character strings resulted in a length
ANR2853I New license information:
that exceeds the maximum character string length (250
Explanation: This message is issued during a for data type CHAR, and 2000 for data type
REGISTER LICENSE command to display the updated VARCHAR).
licensing information for the server after the new
System Action: This warning can occur before or after
license has been interpreted by the command. Messages
SQL query processing, but does not terminate query
appearing after this message display the updated
processing.
factors under which the server is licensed.
User Response: Check to make sure that the new
ANR2902E Insufficient memory was available to
license information includes the updates that you
process the SQL statement.
intended for the REGISTER LICENSE command. If the
license terms do not change, check the parameters and Explanation: Sufficient memory was not available to
reissue the command, if you find that it was not complete the processing of an SQL query.
entered correctly. If the REGISTER LICENSE command
does not produce the desired updates in terms of System Action: The SQL query is terminated.
licensing, contact your service representative. User Response: None.
ANR2855I Server is licensed to support Tivoli ANR2903E An SQL parser stack overflow occurred
Space Manager clients. while processing token ’token’.
Explanation: This message is issued during server Explanation: The internal stack used by the SQL
startup. query parser has overflowed. This typically occurs
System Action: Server operation continues. when too many column names or expressions have
been specified in the SELECT clause.
System Action: The SQL query is terminated.

ANR2904E Unexpected SQL key word token - ANR2909E The SQL statement is incomplete;
’token’. additional tokens are required.
Explanation: A syntax error occurred because an SQL Explanation: A syntax error occurred because,
key word was found that can not legally be used at the although the syntax of the SQL query expression was
specified position within the SQL statement. Examples correct up to the end of the string, the parser expected
of SQL key words are SELECT, FROM, and WHERE. additional tokens in order to form a
syntactically-correct SQL statement.
ANR2905E Unexpected SQL identifier token -
’token’. ANR2910E Invalid SQL token - ’token’.
Explanation: A syntax error occurred because an SQL Explanation: An invalid SQL token was found. For
identifier was found that can not legally be used at the example, the token formed by the character sequence
specified position within the SQL statement. Examples ″::!″ is not a valid SQL token.
of SQL identifiers are table names and column names.
ANR2911E Invalid SQL numeric literal token -
ANR2906E Unexpected SQL literal token - ’token’. ’token’.
Explanation: A syntax error occurred because an SQL Explanation: An invalid SQL numeric literal token
literal token was found that can not legally be used at was found. For example, the floating point literal
the specified position within the SQL statement. ″1.456E″ is not valid.
Examples of SQL literal tokens are ’abc’, 1.567, and
DATE ’1/1/96’.
ANR2912E Invalid character string literal token -
’token’.
ANR2907E Unexpected SQL operator token - ’token’.
Explanation: An invalid SQL character string literal
Explanation: A syntax error occurred because an SQL token was found. For example, the hexadecimal literal
operator token was found that can not legally be used X’78FG’ is not valid because it contains the character
at the specified position within the SQL statement. ’G’.
Examples of SQL operator tokens are +, *, <, and =.
ANR2913E Invalid SQL identifier token - ’token’.
ANR2908E Unexpected SQL punctuation token -
Explanation: An invalid SQL identifier token was
’token’.
found. For example, the character sequence ″ABC.123″
Explanation: A syntax error occurred because an SQL is not a valid identifier because the second part of the
punctuation token was found that can not legally be identifier, ″123″, does not begin with a letter.
used at the specified position within the SQL statement.
Examples of SQL punctuation tokens are the period,
the comma, and the parenthesis. User Response: None.
ANR2914E SQL identifier token ’token’ is too long;
name or component exceeds 18
characters.
Explanation: An SQL identifier token was found that
exceeds the maximum length of 18 characters per
component.

ANR2920E The SQL data type of expression
’expression’ is data type; expecting a
ANR2915E The SQL token beginning with ’token’ is numeric or interval expression.
missing an ending delimiter.
Explanation: An SQL expression of numeric data type
Explanation: An SQL token was found that is missing (SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
its ending delimiter. For example, each of the tokens FLOAT, DOUBLE) or of interval data type (INTERVAL)
’abc, ″abc, and X’abc is missing its ending delimiter. is expected.
System Action: The SQL query is terminated. System Action: The SQL query is terminated.
ANR2916E The SQL data types data type and data ANR2921E The SQL data type of expression
type are incompatible for operator ’expression’ is data type; expecting a
’operator’. character string expression.
Explanation: The data types of the operands are not Explanation: An SQL expression of character string
compatible when used with the specified operator. For type CHAR or VARCHAR is expected.
example, the expression 3 + ’abc’ is not valid because
the operand data types INTEGER and CHAR(3) are not
compatible for the addition operator ″+″. User Response: None.
’expression’ is data type; expecting a date,
timestamp, character string date,
ANR2917E The SQL data type of expression character string timestamp, or interval
’expression’ is data type; expecting an expression.
integer expression.
Explanation: An SQL expression was expected of one
Explanation: An SQL expression of data type of the types DATE, TIMESTAMP, CHAR, VARCHAR,
SMALLINT, INTEGER, or DECIMAL with scale zero is or INTERVAL as the operand to the EXTRACT
expected. function. In the case of CHAR or VARCHAR, the
expression must be a valid character string
System Action: The SQL query is terminated. representation of a date or a timestamp.
User Response: None. System Action: The SQL query is terminated.
’expression’ is data type; expecting a
Boolean expression. ANR2923E The SQL data type of expression
’expression’ is data type; expecting a time,
Explanation: An SQL expression of data type timestamp, character string time,
BOOLEAN is expected. character string timestamp, or interval
System Action: The SQL query is terminated. expression.
User Response: None. Explanation: An SQL expression was expected of one

of the types TIME, TIMESTAMP, CHAR, VARCHAR, or
INTERVAL as the operand to the EXTRACT function.
ANR2919E The SQL data type of expression In the case of CHAR or VARCHAR, the expression
’expression’ is data type; expecting a must be a valid character string representation of a
numeric expression. time or a timestamp.
Explanation: An SQL expression of numeric data type System Action: The SQL query is terminated.
SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, or DOUBLE_PRECISION is expected. User Response: None.

User Response: None. ’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 User Response: None.
character string representation of a date.
System Action: The SQL query is terminated. ANR2929E The expression ’expression’ is not an
integer constant.
Explanation: An integer constant such as 1 or -9 is
expected. For example, the DECIMAL function requires
that the precision and scale operands be integer
’expression’ is data type; expecting a time
constants. A decimal constant such as 1.67 is not valid.
or character string time expression.
of the types TIME, CHAR, or VARCHAR. In the case of User Response: None.
CHAR or VARCHAR, the expression must be a valid
character string representation of a time.
ANR2930E A subquery used in an SQL expression
System Action: The SQL query is terminated. must specify a single result column.
User Response: None. 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).
’expression’ is data type; expecting a date,
timestamp, character string date, or System Action: The SQL query is terminated.
character string timestamp expression.
of the types DATE, TIMESTAMP, CHAR, or
ANR2931E A subquery expression may not contain
VARCHAR. In the case of CHAR or VARCHAR, the
a reference to a column name that is
expression must be a valid character string
contained in an outer query expression.
representation of a date or a timestamp.
Explanation: A subquery contains a reference to a
column name in an outer query expression.
’expression’ is data type; expecting an
interval containing a single date-time ANR2932E The maximum nesting depth for
field. subquery expressions has been
exceeded.
Explanation: An SQL expression was expected of data
type INTERVAL YEAR, INTERVAL MONTH, Explanation: Too many nested subqueries were
INTERVAL DAY, INTERVAL HOUR, INTERVAL specified.
MINUTE, or INTERVAL SECOND, all of which contain
a single date-time field. Multi-field interval types (for System Action: The SQL query is terminated.
example, INTERVAL DAY TO SECOND) are not User Response: None.
allowed.
System Action: The SQL query is terminated. ANR2933E The WHERE clause must not contain an
User Response: None. aggregate function.
Explanation: The use of the aggregate functions
ANR2928E A number can not be converted to SQL COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
data type INTERVAL if the interval STDDEV in the WHERE clause is not allowed.
contains multiple date-time fields. System Action: The SQL query is terminated.
Explanation: An attempt was made to convert a User Response: None.
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.

ANR2934E The result data type of a CASE
expression can not be determined; at
least one non-null THEN or ELSE ANR2939E The reference ’reference’ is an unknown
expression must be specified. SQL table name.
Explanation: The result data type of a CASE Explanation: The specified table reference is not one
expression can not be determined because all of the of the base tables defined by the server’s database. The
THEN expressions and the ELSE expression (if present) rows of the table SYSCAT.TABLES can be selected to
specifies the NULL key word. obtain a list of all of the valid base tables.
ANR2935E The date-time field field is not present in ANR2940E The reference ’reference’ is an unknown
the expression ’expression’ (data type data SQL column name.
type).
Explanation: The specified column reference is not
Explanation: The specified date-time field (YEAR, one of the base table columns defined by the server’s
MONTH, DAY, HOUR, MINUTE, or SECOND) is not database. The rows of the table SYSCAT.COLUMNS
contained in the data type of the expression. 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
User Response: None. name X must be one of the active correlation names for
the query.
ANR2936E The SQL aggregate function function can System Action: The SQL query is terminated.
not be nested within another aggregate
function.
Explanation: One of the aggregate functions COUNT,
ANR2941E The column reference ’column reference’
MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was
matches more than one SQL column
found nested within another aggregate expression.
name.
Explanation: The specified column reference is
User Response: None. ambiguous because it matches the columns associated
with multiple tables.
ANR2937E An SQL subquery expression can not be System Action: The SQL query is terminated.
nested within an aggregate function.
Explanation: An expression containing a subquery
was found nested within one of the aggregate functions
ANR2942E The column reference ’column reference’ is
COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
not allowed in this context because it is
STDDEV.
part of an outer SQL query expression.
Explanation: The specified column reference is not
User Response: None. 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
ANR2938E The column ’column’ is not allowed in
SELECT clauses.
this context; it must either be named in
the GROUP BY clause or be nested System Action: The SQL query is terminated.
within an aggregate function.
Explanation: A column reference was specified that is
neither a column specified in a GROUP BY clause nor
ANR2943E The column reference ’column reference’ is
is a column nested in one of the aggregate functions
a duplicate of another SQL column
COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
name in the same list.
STDDEV. The use of the column reference is prohibited
because either 1) the GROUP BY clause has been Explanation: A duplicate column reference was
specified, 2) the HAVING clause has been specified, or specified within the same GROUP BY or ORDER BY
3) at least one aggregate function is present. list of columns.

User Response: None. 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,
ANR2944E The reference ’reference’ is an unknown
the string ’abc’ can not be converted to data type
SQL scalar function name.
DATE).
Explanation: The specified function reference is not
the name of a valid scalar function.
ANR2949E Arithmetic overflow occurred for SQL
operator ’operator’.
ANR2945E Too few arguments are specified for
Explanation: An arithmetic overflow occurred for the
SQL scalar function function.
specified operator. Examples of this include: 1) the
Explanation: Too few function arguments were application of the unary negation operator to the
specified. For example, the expression LEFT(x) is smallest INTEGER value (-2147483648) causes overflow
invalid because the LEFT function requires at least two because the result can not be represented in 2’s
arguments. complement; 2) the sum of the set of INTEGER column
values applied to the SUM aggregate function can not
System Action: The SQL query is terminated. be represented within the precision of INTEGER type.
User Response: None. System Action: The SQL query is terminated.
ANR2946E Too many arguments are specified for
SQL scalar function function.
ANR2950E Arithmetic or date-time overflow
Explanation: Too many function arguments were occurred for SQL operator ’operator’ for
specified. For example, the expression UPPER(x,y) is values ’value’ (data type data type) and
invalid because the UPPER function requires exactly ’value’ (data type data type).
one argument.
Explanation: An arithmetic or date-time overflow
System Action: The SQL query is terminated. occurred for the specified operator. The values that
User Response: None. caused the overflow (and their SQL data types) are
displayed.
ANR2947E Division by zero was detected for System Action: The SQL query is terminated.
operator ’operator’. User Response: None.
Explanation: An attempt to divide by the number zero
was detected for the specified SQL operator. The most ANR2951E The value ’value’ (data type data type) is
likely cause of the problem is that one of the values of not a valid argument for operator
a column is zero, and that column is used in the ’operator’.
denominator of a division operation. To protect against
this case the NULLIF function can be used. For Explanation: An invalid value was specified as an
example, instead of the expression 1/X, specify argument to an SQL operator. For example, the
1/NULLIF(X,0), which will set the expression to null expression SQRT(-1) is not valid because the argument
whenever the value if X is zero. to the SQRT function is negative.
ANR2948E The value ’value’ can not be assigned or ANR2952E The value ’value’ (data type data type) is
converted to SQL data type data type. not a valid character string
representation of an SQL date or a
Explanation: A value could not assigned or converted timestamp for operator ’operator’.
to a value in the specified SQL data type because either
1) the data type of the value can not be legally cast to Explanation: An invalid character string
the target data type (for example, data type TIME can representation of a DATE or TIMESTAMP was
not be converted to data type INTEGER); 2) the specified. For example, the string ’abc’ is neither a valid
assignment of the value results in overflow in the date nor a timestamp.
target data type (for example, the decimal value
12345678.34 can not be assigned to data type

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

ANR2961E Invalid SQL enumerated type name - ANR2965E An SQL temporary table cannot be
’name’. built. required columns columns are
needed. maximum columns is the
Explanation: A syntax error occurred because an SQL
maximum.
enumerated type name was expected, but the specified
name is not one of the declared enumerated types. For Explanation: A temporary table required columns wide
example, the literal expression XXX::YYYY is illegal is needed to complete processing for an SQL query. The
because XXX is not a valid enumerated type name. A maximum degree of an SQL table is maximum columns.
list of all of the enumerated types declared by the The table will not be created.
server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
User Response: If the ORDER BY and/or GROUP BY
clauses were specified, reduce the number of columns
User Response: None. needed for the result table.
ANR2962E Unable to resolve SQL enumerated type ANR2966E Command/process: Database temporary
for value ’value’. table storage has been exhausted.
Explanation: A syntax error occurred because an Explanation: The named command or operation could
unqualified SQL enumerated value name was specified, not be completed because insufficient temporary table
but, because that value name is a member of more than storage space was available. Free space in the server
one enumerated type, its type could not be resolved. database is used to store temporary tables created
For example, the enumerated value name YES belongs during the execution of the named command or
to more than one enumerated type, and so the result process.
type of the expression YES = YES can not be resolved.
System Action: The named command or process is
A list of all of the enumerated types declared by the
terminated.
server can be found in the SQL catalog table
SYSCAT.ENUMTYPES. User Response: Extend the server datbase (after
adding database volumes if necessary) and rerun the
commmand or process.
ANR3000E Command: Command can only be issued
ANR2963W This SQL query may produce a very on a configuration manager.
large result table, or may require a
Explanation: The command can only be issued on a
significant amount of time to compute.
server that is a configuration manager.
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 User Response: Issue this command from a
be generated. configuration manager.
continue. ANR3001E Command: Command can only be issued
on a managed server.
User Response: Enter 'Y' to continue with SQL query
processing or 'N' to terminate the query. Explanation: The command can only be issued on a
managed server.
ANR2964E The reference ’reference’ is not a column System Action: Server operation continues. The
of the SQL result table. command is not processed.
Explanation: The ORDER BY clause specified a User Response: Issue this command from a managed
column that is not part of the result table for the SQL server.
query. Only those columns named in the select list are
part of the result table.
ANR3002E Command: Profile name exceeds maximum
System Action: The SQL query is terminated. length characters.
User Response: None. Explanation: The profile name specified in the
command is longer than the maximum length allowed.

User Response: Select a profile name that does not User Response: Reissue the command with the
exceed the maximum length. specified option.
ANR3003E Command: Profile description exceeds ANR3010W This command will delete an object that
maximum length characters. is associated with one or more profiles
on a configuration manager. Subsequent
Explanation: The profile description specified in the
configuration refresh processing will
command is longer than the maximum length allowed.
delete the object on managed servers
System Action: Server operation continues. The that subscribe to a profile with which
command is not processed. the object is associated.
User Response: Select a description that does not Explanation: A command has been entered that will
exceed the maximum length. delete an object from a configuration manager. Since
this object is associated with one or more profiles on a
configuration manager, configuration refresh processing
ANR3004E Command: The configuration manager will delete this object on subscribing managed servers.
name exceeds maximum length characters.
System Action: The system asks whether you wish to
Explanation: The configuration manager name continue with the command.
specified in the command is longer than the maximum
length allowed. User Response: To process the command, enter 'Y' to
continue or 'N' to stop the process.
ANR3011E command: Subscription for profile profile
User Response: Select a configuration manager name name was not deleted because one or
that does not exceed the maximum length. more objects could not be discarded.
Explanation: This message was issued because one or
ANR3005E Command: The server name exceeds more objects could not be discarded by the indicated
maximum length characters. command. A previous message gives an explanation for
Explanation: The configuration manager name each object that could not be discarded.
specified in the command is longer than the maximum System Action: The system may discard some of the
length allowed. managed objects that are associated with profile profile
System Action: Server operation continues. The name The subscription itself is not deleted.
command is not processed. User Response: Examine previous messages to
User Response: Select a configuration manager name determine the action that must be taken before
that does not exceed the maximum length. remaining objects can be discarded. Alternatively, you
can delete the subscription without using the
DISCARDOBJECTS=YES option.
ANR3006E Command: The configuration refresh
interval value must be between minimum
value and maximum value. ANR3012I command: Configuration manager state
set to state.
with an invalid refresh interval. Explanation: The command has successfully set the
configuration manager state.
command is not processed. System Action: The command succeeded.
User Response: Issue the command and specify a User Response: None.
valid refresh interval value.
ANR3013W command: Configuration manager state
ANR3007E Command: The option option must be already set to state.
specified. Explanation: The specified state is already in force on
Explanation: When the command is issued on a a the server.
server that is neither a configuration manager nor a System Action: Server operation continues. The
managed server, the specified option must be supplied. command is not processed.
System Action: Server operation continues. The User Response: This server is already set to the
command is not processed. specified state. If the state should be set differently,
reissue the command specifying the new state value.

ANR3014E command: One or more subscriptions still ANR3018E command: Profile profile name already
exist. exists.
Explanation: A configuration manager state cannot be Explanation: The profile specified already exists on
set to OFF is one or more subscription still exist. The the configuration manager.
server still has a record of one or more subscriptions to
its profiles.
User Response: Decide on another profile name and
reissue the command.
User Response: Use the QUERY SUBSCRIBERS
command to determine which subscriptions still exist.
ANR3019I command: Profile profile name updated.
The DELETE SUBSCRIBER command can be used to
remove the record of these subscriptions. You may Explanation: The command has successfully updated
instead want to delete the actual subscription(s) on the a profile.
managed server(s). When there are no more
subscriptions recorded on the configuration manager, System Action: The command succeeded.
you must then delete all the profiles. Once the profiles User Response: None.
have been deleted, you can reissue the command.
ANR3020E command: Profile profile name not found.

ANR3015E command: One or more profiles still
exist. Explanation: The profile specified could not be found.
Explanation: A configuration manager state cannot be System Action: Server operation continues. The
set to OFF is one or more profiles still exist. command is not processed.
System Action: Server operation continues. The User Response: Check to see if the profile name was
command is not processed. specified correctly on the command. Use the QUERY
PROFILE command to check to see if the profile exists
User Response: Use the QUERY PROFILE command on the configuration manager. Reissue the command
to determine which profiles still exist on the with the correct profile name.
configuration manager then use the DELETE PROFILE
command. After all the profiles have been deleted,
reissue the command. ANR3021I command: Profile profile name copied to
profile profile name.
ANR3016I command: Configuration refresh interval Explanation: The command has successfully copied
set to interval. the first profile to the newly created second profile. All
the profile associations were also copied.
Explanation: The command has successfully set the
configuration refresh interval to the specified value. System Action: The command succeeded.
Automatic configuration refresh processing will User Response: None.
immediatly be attempted and then will again be
performed after the specified number of minutes of
elapsed. ANR3022E command: The profile lock timeout
interval value must be between minimum
System Action: The command succeeded. value and maximum value.
User Response: None. Explanation: The specified command has been issued
with an invalid lock timeout interval.
ANR3017I command: Profile profile name defined. System Action: Server operation continues. The
Explanation: The command has successfully define a command is not processed.
profile. User Response: Issue the command and specify a
System Action: The command succeeded. valid lock timeout interval value.

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.
System Action: The command succeeded.

ANR3028E command: Profile profile name is locked.
Explanation: The specifed command cannot be
ANR3024W command: Profile profile already locked
performed on a locked profile.
with timeout interval greater than
interval. System Action: Server operation continues. The
Explanation: An attempt was made to lock the
specified profile. The profile is already locked with a User Response: Unlock the profile using the
timeout interval greater than the value specifed. UNLOCK PROFILE command and then reissue the
command.
System Action: The profile remains locked with the
original timeout interval.
ANR3029E command: Profile name not specified.
User Response: If you want to lower the timeout
interval, unlock the profile and then lock the profile Explanation: A profile name must be specifed on this
again specifying the lower value. command using the PROFILE= parameter.
ANR3025I command: Profile profile name unlocked. command is not processed.
Explanation: The command has successfully unlocked User Response: Reissue the command and specify a
the profile. Configuration information can now be profile name.
propogated to the subscribers of the profile.
System Action: The command succeeded. ANR3030I command: Subscription defined for
Explanation: The command has successfully defined a
subscription to the specified profile. A refresh of the
ANR3026I command: Profile profile name deleted.
configuration information has been initiated.
Explanation: The command has successfully deleted
the profile from the configuration manager.
ANR3031W command: Subscription for profile profile
name already exists.
ANR3027E command: One or more subscriptions still
Explanation: A subscription already exists for the
exist to profile profile name.
specified profile.
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: Check to make sure you specified the
correction profile name, and reissue the command if
needed.
User Response: Use the QUERY SUBSCRIBERS
ANR3032E command: Server name not specified.
command to determine which subscriptions still exist.
Use the DELETE SUBSCRIPTION command on the Explanation: A server name must be specifed on this
managed server(s) to delete the subscriptions, and then command using the SERVER= parameter. This
reissue the DELETE PROFILE command on the identifies the configuration manager.
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: Reissue the command and specify a
the managed server requests updates for that profile, server name.
informing the managed server that the profile has been
deleted.
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
ANR3038E command: Subscription for profile profile
have one configuration manager.
name not found.
Explanation: A subscription was not found for the
specified profile.
User Response: Reissue the command and leave off
the server parameter. It will default to use the current
configuration manager. A QUERY SUBSCRIPTION will
display the configuration manager currently in use. User Response: Check to see that the profile name
was specified correctly. Issue the QUERY
SUBSCRIPTION command to check to see which
ANR3034E command: Server server cannot be used as
profiles have subscriptions. Reissue the command with
this server’s configuration manager.
the correct profile name.
Explanation: A server name was specified on the
command which cannot be used as a configuration
ANR3039E command: No matching administrators
manager.
found in configuration.
Explanation: No administrator definitions were found
on the configuration manager that match the admin(s)
User Response: Find out the currect name for the specified on the DEFINE PROFASSOCIATION
configuration manager and then reissue the command. command.
ANR3035I command: Subscriber subscriber name command is not processed.
deleted.
User Response: Use the QUERY ADMIN command to
Explanation: The command has successfully deleted a check which administrators that are defined on the
subscriber from the record kept in the configuration server and then reissue to DEFINE
manager. If the subscriber (managed server) still has a PROFASSOCIATION command.
subscription to a valid profile, the record of the
subscription will reappear when it performs its next
ANR3040I command: All administrators associated
configuration refresh.
with profile profilename.
Explanation: The command has successfully
User Response: None. associated all the administrators with the specified
profile. All administrator definitions will be
automatically propogated to managed servers which
ANR3036E command: Subscriber subscriber name not subscribe to the profile. If an administrator is added to
found. the configuration manager in the future, its definition
Explanation: The specified subscriber name was not will also be automatically propogated to the managed
found in the configuration manager’s records as being a servers.
valid subscriber of any profiles. System Action: The command succeeded.
System Action: Server operation continues. The User Response: None.
User Response: Check to see that the subscriber ANR3041I command: Administrator admin associated
(managed server) name is correction. If you think the with profile profilename.
name is correct, perhaps the managed server has not
yet successfully contacted the configuration manager to Explanation: The command has successfully
inform it that the subscription exists. associated the administrator with the specified profile.
The administrator definition will be automatically
propogated to managed servers which subscribe to the
ANR3037I command: Subscription deleted for profile.
Explanation: The command has successfully deleted a
subscription for the specified profile. A refresh of the User Response: None.
configuration information has been initiated.

ANR3042W command: No additional administrators ANR3046W command: No additional domains

associated with profile profilename. associated with profile profilename.
Explanation: No additional administrator were Explanation: No additional domains were associated
associated with the profile. The administrator(s) with the profile. The domain(s) specified are already
specified are already associated with the profile. associated with the profile.
System Action: Server operation continues. The System Action: Server operation continues. The
command is not processed. command is not processed.
User Response: Use the QUERY ADMIN command to User Response: Use the QUERY DOMAIN command
check which administrators are defined on the server to check which domains are defined on the server and
and then reissue to DEFINE PROFASSOCIATION then reissue to DEFINE PROFASSOCIATION
command. The QUERY PROFASSOCIATION command. The QUERY PROFASSOCIATION
FORMAT=DETAILED can be used to see which FORMAT=DETAILED can be used to see which
administrators are already associated with the profile. domains are already associated with the profile.
ANR3043E command: No matching domains found ANR3047E command: No matching admin schedules
in configuration. found in configuration.
Explanation: No domain definitions were found on Explanation: No admin schedule definitions were
the configuration manager that match the domain(s) found on the configuration manager that match the
specified on the DEFINE PROFASSOCIATION admin schedule(s) specified on the DEFINE
command. PROFASSOCIATION command.
User Response: Use the QUERY DOMAIN command User Response: Use the QUERY SCHEDULE
to check which domains that are defined on the server TYPE=ADMIN command to check which admin
and then reissue to DEFINE PROFASSOCIATION schedules are defined on the server and then reissue to
command. DEFINE PROFASSOCIATION command.
ANR3044I command: All domains associated with ANR3048I command: All admin schedules
profile profilename. associated with profile profilename.
Explanation: The command has successfully Explanation: The command has successfully
associated all the domains with the specified profile. associated all the admin schedules with the specified
All domain definitions will be automatically profile. All admin schedule definitions will be
propogated to managed servers which subscribe to the automatically propogated to managed servers which
profile. If a domain is added to the configuration subscribe to the profile. If an admin schedule is added
manager in the future, its definition will also be to the configuration manager in the future, its
automatically propogated to the managed servers. definition will also be automatically propogated to the
managed servers.
ANR3045I command: Domain domain associated with
profile profilename. ANR3049I command: Admin Schedule admin schedule
associated with profile profilename.
associated the domain with the specified profile. The Explanation: The command has successfully
domain definition will be automatically propogated to associated the admin schedule with the specified
managed servers which subscribe to the profile. profile. The admin schedule definition will be
automatically propogated to managed servers which
subscribe to the profile.

ANR3050W command: No additional admin ANR3054W command: No additional scripts

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

ANR3058W command: No additional client option ANR3062W command: No additional servers

sets associated with profile profilename. associated with profile profilename.
Explanation: No additional client option sets were Explanation: No additional servers were associated
associated with the profile. The client option set(s) with the profile. The server(s) specified are already
specified are already associated with the profile. associated with the profile.
User Response: Use the QUERY CLOPTSET command User Response: Use the QUERY SERVER command to
to check which client option sets are defined on the check which servers are defined on the server and then
server and then reissue to DEFINE reissue to DEFINE PROFASSOCIATION command. The
PROFASSOCIATION command. The QUERY QUERY PROFASSOCIATION FORMAT=DETAILED
PROFASSOCIATION FORMAT=DETAILED can be can be used to see which servers are already associated
used to see which client option sets are already with the profile.
associated with the profile.
ANR3063E command: No matching server groups
ANR3059E command: No matching servers found in found in configuration.
configuration.
Explanation: No server group definitions were found
Explanation: No server definitions were found on the on the configuration manager that match the server
configuration manager that match the server(s) group(s) specified on the DEFINE PROFASSOCIATION
specified on the DEFINE PROFASSOCIATION command.
command.
User Response: Use the QUERY SERVERGROUP
User Response: Use the QUERY SERVER command to command to check which server groups that are
check which servers that are defined on the server and defined on the server and then reissue to DEFINE
then reissue to DEFINE PROFASSOCIATION PROFASSOCIATION command.
command.
ANR3064I command: All server groups associated
ANR3060I command: All servers associated with with profile profilename.
profile profilename.
Explanation: The command has successfully associated all the server groups with the specified
associated all the servers with the specified profile. All profile. All server group definitions will be
server definitions will be automatically propogated to automatically propogated to managed servers which
managed servers which subscribe to the profile. If a subscribe to the profile. If a server group is added to
server is added to the configuration manager in the the configuration manager in the future, its definition
future, its definition will also be automatically will also be automatically propogated to the managed
propogated to the managed servers. servers.
ANR3061I command: Server server associated with ANR3065I command: Server group server group
profile profilename. associated with profile profilename.
associated the server with the specified profile. The associated the server group with the specified profile.
server definition will be automatically propogated to The server group definition will be automatically
managed servers which subscribe to the profile. propogated to managed servers which subscribe to the
profile.

User Response: Use the QUERY PROFASSOCIATION
ANR3066W command: No additional server groups
command to check which domains are associated with
associated with profile profilename.
the profile and then reissue to DELETE
Explanation: No additional server groups were PROFASSOCIATION command.
associated with the profile. The server group(s)
specified are already associated with the profile.
ANR3071I command: All domain associations
System Action: Server operation continues. The deleted from profile profilename.
User Response: Use the QUERY SERVERGROUP all domains associations from the specified profile. This
command to check which server groups are defined on will automatically delete these domains from the
the server and then reissue to DEFINE managed servers that are subscribed to this profile.
PROFASSOCIATION command. The QUERY
PROFASSOCIATION FORMAT=DETAILED can be
used to see which server groups are already associated User Response: None.
with the profile.
ANR3072I command: Domain association domain

ANR3067E command: No matching administrators deleted from profile profilename.
associated with profile profile.
Explanation: No matching administrator definitions domain association from the specified profile. This will
are associated with the specified specified profile. automatically delete this domain from the managed
servers that are subscribed to this profile.
command is not processed. System Action: The command succeeded.
User Response: Use the QUERY PROFASSOCIATION User Response: None.
command to check which administrators are associated
with the profile and then reissue to DELETE
PROFASSOCIATION command. ANR3073E command: No matching admin schedules
ANR3068I command: All administrator associations Explanation: No matching admin schedule definitions
deleted from profile profilename. are associated with the specified specified profile.
Explanation: The command has successfully deleted System Action: Server operation continues. The
all administrators associations from the specified command is not processed.
profile. This will automatically delete these User Response: Use the QUERY PROFASSOCIATION
administrators from the managed servers that are command to check which admin schedules are
subscribed to this profile. associated with the profile and then reissue to DELETE
System Action: The command succeeded. PROFASSOCIATION command.

ANR3074I command: All admin schedule
associations deleted from profile
ANR3069I command: Administrator association profilename.
admin deleted from profile profilename.
Explanation: The command has successfully deleted all admin schedules associations from the specified
an administrator association from the specified profile. profile. This will automatically delete these admin
This will automatically delete this administrator from schedules from the managed servers that are subscribed
the managed servers that are subscribed to this profile. to this profile.
ANR3070E command: No matching domains ANR3075I command: Admin schedule association

associated with profile profile. admin schedule deleted from profile
profilename.
Explanation: No matching domain definitions are
associated with the specified specified profile. Explanation: The command has successfully deleted
an admin schedule association from the specified
profile. This will automatically delete this admin

schedule from the managed servers that are subscribed profile. This will automatically delete these client
to this profile. option sets from the managed servers that are
subscribed to this profile.
ANR3076E command: No matching scripts associated
with profile profile. ANR3081I command: Client option set association
client option set deleted from profile
Explanation: No matching script definitions are
profilename.
associated with the specified specified profile.
client option set association from the specified profile.
This will automatically delete this client option set from
User Response: Use the QUERY PROFASSOCIATION the managed servers that are subscribed to this profile.
command to check which scripts are associated with
PROFASSOCIATION command. User Response: None.
ANR3077I command: All script associations deleted ANR3082E command: No matching servers
from profile profilename. associated with profile profile.
Explanation: The command has successfully deleted Explanation: No matching server definitions are
all scripts associations from the specified profile. This associated with the specified specified profile.
will automatically delete these scripts from the
managed servers that are subscribed to this profile.
User Response: None. command to check which servers are associated with
PROFASSOCIATION command.
ANR3078I command: Script association script deleted
from profile profilename.
ANR3083I command: All server associations deleted
from profile profilename.
script association from the specified profile. This will
automatically delete this script from the managed Explanation: The command has successfully deleted
servers that are subscribed to this profile. all servers associations from the specified profile. This
will automatically delete these servers from the
ANR3079E command: No matching client option sets
ANR3084I command: Server association server
Explanation: No matching clent option set definitions
deleted from profile profilename.
are associated with the specified specified profile.
server association from the specified profile. This will
automatically delete this server definition from the
User Response: Use the QUERY PROFASSOCIATION managed servers that are subscribed to this profile.
command to check which client option sets are
associated with the profile and then reissue to DELETE
PROFASSOCIATION command. User Response: None.
ANR3080I command: All client option set ANR3085E command: No matching server groups
associations deleted from profile associated with profile profile.
profilename.
Explanation: No matching server group definitions are
Explanation: The command has successfully deleted associated with the specified specified profile.
all client option sets associations from the specified

System Action: Server operation continues. The up. If the problem persists, consult with your network
command is not processed. administrator.
command to check which server groups are associated ANR3090E command: Server server name is not a
with the profile and then reissue to DELETE configuration manager.
PROFASSOCIATION command.
Explanation: The specified command failed because it
tried to contact the specified server, and discovered that
ANR3086I command: All server group associations the server is not a configuration manager.
deleted from profile profilename.
Explanation: The command has successfully deleted command is not processed.
all server groups associations from the specified profile.
This will automatically delete these server groups from
correct configuration manager name.
the managed servers that are subscribed to this profile.
ANR3091E command: Profile list not specified.
Explanation: The specified command failed because
you did not specify a profile list on the command.
ANR3087I command: Server group association server
group deleted from profile profilename.
server group association from the specified profile. This
profile list.
will automatically delete this server group from the
ANR3092I command: Subscriber notification
processing has begun.
Explanation: A NOTIFY SUBSCRIBER process has
begun. The managed server(s) are being contacted,
ANR3088W This command will cause the deletion asking them to immediately perform a configuration
of objects on any managed server refresh.
subscribed to profile profile name.
Explanation: A DELETE PROFASSOCIATION command succeeded.
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 ANR3093I command: No matching profiles or
of these objects will occurr during the next subscriptions were found.
configuration refresh for that managed server.
Explanation: No subscriptions were found for the
System Action: The system asks whether you wish to profiles specified. Either the profiles do not exist, or
continue with the command. there are no subscriptions to the profiles.
User Response: To process the DELETE System Action: Server operation continues. The
PROFASSOCATION command, enter 'Y' to continue or command is not processed.
'N' to stop the command.
User Response: Use the QUERY PROFILE and
QUERY SUBSCRIBER command to determine which
ANR3089E command: Command failed - profiles exist and which profiles have subscribers.
Server-to-server communication error Reissue the command specifying the correct profile
with server server name. name(s).
Explanation: The specified command failed while
attempting to communicate with the indicated server. ANR3150E Configuration refresh failed with
configuration manager server name. Will
retry in minutes minutes.
Explanation: While receiving configuration
User Response: Verify that the indicated server name
information from the specified configuration manager,
is correctly defined. Try reissuing the command. Use
processing failed because of a communications error.
the server PING command to see if the other server is

configuration refresh process was stopped and will be active. If the problem continues, contact the
automatically retried. administrator for the managed server, or contact a
network administrator. The notify subscriber request
User Response: Perhaps the configuration manager is
will automatically retry several times and then give up.
not active. If the problem continues, contact the
administrator for the configuration manager, or contact
a network administrator. The refresh will automatically ANR3155E Error attempting notify subscribers
retry several times and then give up until the request to managed server server.
configuration refresh interval is reached again.
System Action: Server operation continues. The notify
subscriber request failed.
ANR3151E Configuration refresh failed with
User Response: Examine the activity log for other
configuration manager server name.
messages that may explain why the notify subscriber
Explanation: While receiving configuration request failed.
processing failed.
ANR3156E Configuration refresh failed for
System Action: Server operation continues. The managed server server name.
configuration refresh process was stopped.
Explanation: While sending configuration information
User Response: Examine the activity log for other to the specified managed server, processing failed.
messages that may explain why the configuration
refresh failed. The refresh will attempted again when
configuration refresh process ended.
the configuration refresh interval is reached.
User Response: Examine the activity log of both the
managed server and the configuration manager for
ANR3152I Configuration refresh started with
other messages that may explain why the configuration
configuration manager server name.
refresh failed. The refresh will attempted again by the
Explanation: Configuration refresh processing has managed server when its configuration refresh interval
started. A server-to-server session was opened to is reached.
receive configuration information from the
configuration manager. Updates will be sent for objects
ANR3157I Configuration refresh started for
associated with any subscribed-to profiles.
managed server server name.
System Action: Refresh processing continues.
Explanation: Configuration refresh processing has
User Response: None. started. A server to server session was opened by the
managed server to receive configuration information
from the configuration manager. Updates will be sent
ANR3153I Configuration refresh ended
for objects associated with any subscribed-to profiles.
successfully with configuration manager
server name. System Action: Refresh processing continues.
Explanation: Configuration refresh processing ended User Response: None.
successfully. All updates have been made to managed
objects associated with any subscribed-to profiles.
ANR3158I Configuration refresh ended
System Action: Server processing continues. The next successfully for managed server server
automatic refresh will start when the configuration name.
refresh interval is reached.
Explanation: Configuration refresh processing ended
User Response: None. successfully. All updates have been made to managed
objects associated with any subscribed-to profiles on
the managed server.
ANR3154E Communication error on notify to
managed server server name. Will retry in System Action: Server processing continues.
minutes minutes.
Explanation: While attempting a notify subscriber
request to the specified managed server, a
ANR3159E Managed server server name has newer
communications error was detected.
version for profile profile name.
System Action: Server operation continues. The notify
Explanation: While sending configuration information
subscriber request was stopped and will be
to the specified managed server, it has been detected
automatically retried.
that the managed server has a newer version of
User Response: Perhaps the managed server is not configuration information for the specified profile than

does the configuration manager. This condition can Configuration refresh processing ended.
happen if the configuration manager’s database has
User Response: Make more memory available to the
been restored to an earlier point in time. Another
managed server.
possibility is that the profile was deleted on the
configuration manager and a new profile by the same
name was created. ANR3163E Managed server server name aborted
configuration refresh processing due to
System Action: Server operation continues. No
an internal error.
configuration information for this profile will be sent to
the managed server until this condition is corrected. Explanation: While sending configuration information
to the specified managed server, processing ended
User Response: Before correcting the situation, you
prematurely because of an internal error on the
may want to use QUERY PROFILE to examine the
managed server.
profile associations defined on both the configuration
manager and the managed server. To correct the System Action: Server operation continues.
situation, on the managed server delete the Configuration refresh processing ended.
subscription to the profile and define the subscription
again. This will cause the managed server to be User Response: Examine the activity log of the
refreshed at the configuration manager’s current level. managed server for messages that explain the cause of
the internal error.
ANR3160E Unable to receive confirmation of

refresh from managed server server name. ANR3164E Managed server server name aborted
configuration refresh processing due to
Explanation: While sending configuration information a lock conflict.
to the specified managed server, a communication error
occurred when trying to receive confirmation from the Explanation: While sending configuration information
managed server that information was processed to the specified managed server, processing ended
successfully. prematurely because of a lock conflict on the managed
server.
Configuration refresh processing ended. System Action: Server operation continues.
Configuration refresh processing ended.
User Response: Determine if communication can be
established with the managed server by using the User Response: Use the NOTIFY SUBSCRIBERS
server PING command. Use the NOTIFY command to retry the configuration refresh. If this
SUBSCRIBERS command to force the configuration problem persists, contact your service representative.
refresh to retry.
ANR3165E Managed server server name aborted
ANR3161E Premature end of configuration refresh configuration refresh processing due to
for managed server server server name. a protocol error.
Explanation: While sending configuration information Explanation: While sending configuration information
to the specified managed server, processing ended to the specified managed server, processing ended
prematurely because of on error. prematurely because of a protocol error detected on the
managed server.
Configuration refresh processing ended. System Action: Server operation continues.
User Response: Examine the activity log on the
managed server for any error messages that might User Response: Use the NOTIFY SUBSCRIBERS
explain why the refresh failed. Use the NOTIFY command to retry the configuration refresh. If this
SUBSCRIBERS command on the configuration manager problem persists, contact your service representative.
to force the configuration refresh to retry.
ANR3166E Unable to receive configuration refresh
ANR3162E Managed server server name aborted information from server server name.
configuration refresh processing due to Explanation: While receiving configuration
a low memory condition. information from the specified configuration manager,
Explanation: While sending configuration information processing ended prematurely because of a
to the specified managed server, processing ended communications error.
prematurely because of a low memory condition on the System Action: Server operation continues.
managed server. Configuration refresh processing ended.
System Action: Server operation continues. User Response: Use the server PING command to see

if the configuration manager can be reached. If the issuing the SET CONFIGREFRESH command (using
problem persists, contact your network administrator. the current refresh interval value). If this problem
ANR3167E Configuration manager server name
aborted configuration refresh processing ANR3171E Configuration refresh with
due to a low memory condition. configuration manager server name had
to skip processing for one or more
objects.
processing ended prematurely because of a low Explanation: While receiving configuration
memory condition on the configuration manager. information from the specified configuration manager,
it became necessary to skip the creation or deletion of
one or more objects.
User Response: Notify the administrator of the
configuration manager.
User Response: Examine the managed server’s
activity log for earlier messages that identfy the object,
ANR3168E Configuration manager server name
and take the actions identified in those messages.
aborted configuration refresh processing
Configuration refresh processing will not complete
due to an internal error.
successfully until the problem is clear up.
ANR3172W Subscription exists for deleted profile
processing ended prematurely because of an internal
profile name.
error on the configuration manager.
information from the configuration manager, it has
been detected that the managed server has a
User Response: Examine the activity log of the subscription to an profile that no longer exists on the
configuration manager for messages that explain the configuration manager. This condition can exist because
cause of the internal error. 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
ANR3169E Configuration manager server name regressed because of a restore db.
aborted configuration refresh processing
due to a lock conflict. System Action: Server operation continues.
Explanation: While receiving configuration User Response: The DELETE SUBSCRIPTION

information from the specified managed server, command is used to correct this situation. You need to
processing ended prematurely because of a lock conflict decide if you want the managed objects to remain on
on the configuration manager. the server. If you want them to be deleted, specify
DISCARD=YES. If you want the objects to remain on
System Action: Server operation continues. the managed server as local objects, specify
Configuration refresh processing ended. DISCARD=NO.
User Response: Retry the configuration refresh by
issuing the SET CONFIGREFRESH command (using ANR3173E Server has newer version for profile
the current refresh interval value). If this problem profile name than the configuration
persists, contact your service representative. manager server name.
ANR3170E Configuration manager server name information from the configuration manager, it has
aborted configuration refresh processing been detected that the managed server has a newer
due to a protocol error. version of configuration information for the specified
Explanation: While receiving configuration profile than does the configuration manager. This
information from the specified configuration manager, condition can happen if the configuration manager’s
processing ended prematurely because of a protocol database has been restored to an earlier point in time.
error detected on the configuration manager. Another possibility is that the profile was deleted on
the configuration manager with FORCE=YES and a
System Action: Server operation continues. new profile by the same name was created.
User Response: Retry the configuration refresh by configuration information for this profile will be sent to

the managed server until this condition is corrected. System Action: Server operation continues. Refresh
processings skips over this object. The refresh for the
User Response: Before correcting the situation, you
profile fails.
may want to use QUERY PROFILE to examine the
profile associations defined on both the configuration User Response: The configuration manager is at a
manager and the managed server. To correct the higher release level than the managed server. The
situation, on the managed server delete the managed server subscribed to a profile that contains an
subscription to the profile and define the subscription unsupported object. Delete the subscription to this
again. This will cause the managed server to be profile until service can be applied to the server to
refreshed at the configuration manager’s current level. bring it to a higher release level.
ANR3174E Communication error with managed ANR3200E command: Command cannot be executed
server server name. - domain domain name is a managed
object.
Explanation: While receiving or sending information
to the specified managed server, a communcations error Explanation: The specified command cannot be
was experienced. 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
operation in progress fails.
modified using configuration information propagated
User Response: If this error happens often, consult from the configuration manager.
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. ANR3201E command: Domain domain name is a
managed object and cannot be deleted.
Explanation: While receiving configuration refresh
information from the specified managed server, it was Explanation: The indicated domain is a managed
detected that a subscribed-to profile is locked. object and cannot be deleted on the managed server.
System Action: Server operation continues. Refresh System Action: The command fails and server
processings skips over this profile. operation continues.
User Response: Normally, the profile will later be User Response: To delete this object, you can delete
unlocked automatically, or by an administrator. If you the subscription to the configuration profiles with
think that it should not be locked, have ask the which domain domain name is associated.
configuration manager admin to unlock it using the
UNLOCK PROFILE command.
ANR3202E command: Domain domain name is a
managed object and cannot be updated.
ANR3176W Profile profile name is locked and could
Explanation: The indicated domain is a managed
not be refreshed for managed server
object and cannot be updated on the 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. User Response: To update this object, you can delete
the subscription to the configuration profiles with
System Action: Server operation continues. Refresh
which domain domain name is associated.
processings skips over this profile.
User Response: If the profile should no longer be
ANR3203E command: Policy set set name in domain
locked, use the UNLOCK PROFILE command to
domain name is a managed object and
unlock it.
cannot be deleted.
Explanation: The indicated policy set is a managed
ANR3177W Server level does not support object in
object and cannot be deleted on the managed server.
Explanation: While receiving configuration refresh
information from the configuration manager, an object
was received that is not supported on this managed User Response: To delete this object, you can delete
server. the subscription to the configuration profiles with

ANR3208E command: Archive copy group group name
in domain domain name, policy set set
ANR3204E command: Policy set set name in domain name, management class class name is a
domain name is a managed object and managed object and cannot be deleted.
cannot be updated.
Explanation: The indicated archive copy group is a
Explanation: The indicated policy set is a managed managed object and cannot be deleted on the managed
object and cannot be updated on the managed server. server.
System Action: The command fails and server System Action: The command fails and server
operation continues. operation continues.
User Response: To update this object, you can delete User Response: To delete this object, you can delete
the subscription to the configuration profiles with the subscription to the configuration profiles with
which domain domain name is associated. which domain domain name is associated.
ANR3205E command: Management class class name in ANR3209E command: Backup copy group group name
domain domain name, policy set set name in domain domain name, policy set set
is a managed object and cannot be name, management class class name is a
deleted. managed object and cannot be updated.
Explanation: The indicated management class is a Explanation: The indicated backup copy group is a
managed object and cannot be deleted on the managed managed object and cannot be updated on the
server. managed server.
User Response: To delete this object, you can delete User Response: To update this object, you can delete
ANR3206E command: Management class class name in ANR3210E command: Archive copy group group name
domain domain name, policy set set name in domain domain name, policy set set
is a managed object and cannot be name, management class class name is a
updated. managed object and cannot be updated.
Explanation: The indicated management class is a Explanation: The indicated archive copy group is a
managed object and cannot be updated on the managed object and cannot be updated on the
managed server. managed server.
User Response: To update this object, you can delete User Response: To update this object, you can delete
ANR3207E command: Backup copy group group name ANR3211E command: Client schedule schedule name
in domain domain name, policy set set in domain domain name is a managed
name, management class class name is a object and cannot be deleted.
managed object and cannot be deleted.
Explanation: The indicated client schedule is a
Explanation: The indicated backup copy group is a managed object and cannot be deleted on the managed
managed object and cannot be deleted on the managed server.
server.
System Action: The command fails and server operation continues.
User Response: To delete this object, you can delete
User Response: To delete this object, you can delete the subscription to the configuration profiles with
the subscription to the configuration profiles with which domain domain name is associated.

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

administrator before discarding the administrator
definition.
name is a managed object - authority
cannot be granted.
ANR3224E command: Command script command
script name is a managed object and
managed object. Authority cannot be granted to this
cannot be deleted.
administrator on the managed server.
Explanation: The indicated command script is a
managed object and cannot be deleted 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. User Response: To delete this script, you can delete
name is a managed object - authority
cannot be revoked. ANR3225E command: Command script command
script name is a managed object and
cannot be updated.
managed object. Authority of this administrator cannot
be revoked on the managed server. Explanation: The indicated command script is a
managed server.
User Response: To revoke authority of this
administrator, you can delete the subscription to the
configuration profiles with which the object is User Response: To update this script, you can delete
associated. the subscription to the configuration profiles with
ANR3222W Managed administrator administrator
name is the only system administrator ANR3226E command: Command script command
and cannot be discarded. script name is a managed object and
cannot be renamed.
a DELETE SUBSCRIPTION command with Explanation: The indicated command script is a
DISCARDOBJECTS=YES. The indicated administrator managed object and cannot be renamed on the
cannot be discarded on the managed server because it managed server.
is the only system administrator.
System Action: Administrator administrator name is operation continues.
not deleted.
User Response: To rename this script, you can delete
User Response: Before this administrator can be the subscription to the configuration profiles with
deleted, another administrator must be given system which the object is associated.
authority.
ANR3227E command: Option set optionset name is a

ANR3223W Managed administrator administrator managed object and cannot be deleted.
name is currently accessing the server
and cannot be discarded. Explanation: The indicated option set is a managed
object and cannot be deleted on the managed server.
a DELETE SUBSCRIPTION command with System Action: The command fails and server
DISCARDOBJECTS=YES. The indicated administrator operation continues.
cannot be discarded on the managed server because it User Response: To delete this option set, you can
has an active session with the server. delete the subscription to the configuration profiles
System Action: Administrator administrator name is with which the object is associated.
not deleted.
User Response: Quit or cancel all sessions for this

ANR3228E command: Option set optionset name is a ANR3233E command: Command cannot be executed
managed object and cannot be updated. - server group group name is a managed
object.
Explanation: The indicated option set is a managed
object and cannot be updated on the managed server. Explanation: The specified command cannot be
executed because it would alter the membership of the
indicated managed server group.
User Response: To update this option set, you can
with which the object is associated. User Response: None.
ANR3229E command: Command cannot be executed ANR3234E command: Server server name is a
- option set optionset name is a managed managed object and cannot be deleted.
object.
Explanation: The indicated server is a managed object
Explanation: The specified command cannot be and cannot be deleted on the managed server.
executed because it would alter the contents of the
indicated managed option set.
User Response: To delete this object, you can delete
User Response: None. which the object is associated.
ANR3230E command: Server group group name is a ANR3235E command: Server server name is a
managed object and cannot be deleted. managed object - one or more specified
attributes cannot be updated.
Explanation: The indicated server group is a managed
object and cannot be deleted on the managed server. Explanation: Because the indicated server is a
managed object, certain attributes cannot be updated
on the managed server. These attributes are:
SERVERPASSWORD, HLADDRESS, LLADDRESS,
User Response: To delete this server group, you can COMMMETHOD, DESCRIPTION, URL, and
delete the subscription to the configuration profiles ALLOWREPLACE.
ANR3231E command: Server group group name is a
User Response: You can restrict the update to
managed object and cannot be updated.
attributes that can be updated on the managed server.
Explanation: The indicated server group is a managed For example, the PASSWORD, NODENAME,
object and cannot be updated on the managed server. FORCESYNC, and DELGRACEPERIOD attributes can
be updated, even if the server is a managed object.
System Action: The command fails and server Alternatively, you can delete the subscription to the
operation continues. configuration profiles with which the object is
User Response: To update this server group, you can associated, so that the server is no longer a managed
delete the subscription to the configuration profiles object.
ANR3236W Server server name is currently in use
ANR3232E command: Server group group name is a and cannot be discarded.
managed object and cannot be renamed. Explanation: This message is issued while processing
Explanation: The indicated server group is a managed a DELETE SUBSCRIPTION command with
object and cannot be renamed on the managed server. DISCARDOBJECTS=YES. The indicated server cannot
be discarded on the managed server because server
System Action: The command fails and server name is in use. This could occur if the managed server
operation continues. has an active connection to server name or if the
User Response: To rename this server group, you can managed server has a device class with
delete the subscription to the configuration profiles DEVTYPE=SERVER that refers to server name.
with which the object is associated. System Action: Server server name is not deleted.

User Response: Before server name can be deleted, the reassign the nodes to the new domain. Alternatively, if
managed server must not have a connection to that you want to prevent further attempts to replace the
server and the managed server cannot have any local domain definition during configuration refresh
device-class references to that server. processing, delete the subscription to the profiles with
ANR3237W Server server name is the event server
and cannot be discarded. ANR3351W Managed domain domain name contains
at least one node and cannot be deleted
during configuration refresh processing.
DISCARDOBJECTS=YES. The indicated server cannot Explanation: During configuration refresh processing,
be discarded because it is the event server for the the enterprise configuration facility attempted to
managed server. remove the indicated domain because it has been
deleted from the configuration manager or because the
System Action: Server server name is not deleted.
profile association no longer exists. The domain could
User Response: Before server name can be deleted, the not be deleted on the managed server because it still
DELETE EVENTSERVER command must be used to contains one or more nodes.
remove the event server reference to server name.
System Action: Refresh processing continues, but this
domain is not deleted. The system will attempt to
ANR3238E command: This object cannot be renamed delete the domain during later configuration refresh
because it is associated with one or operations.
more configuration profiles.
User Response: Assign nodes in this domain to
Explanation: This message is issued on a another domain. Alternatively, you can delete the
configuration manager when an attempt is made to subscription to the profiles with which domain domain
rename an object that is associated with one or more name is associated.
configuration profiles. Associated objects cannot be
renamed because the enterprise configuration facility
ANR3352I Locally defined domain domain name
does not support renaming of objects.
replaced during configuration refresh
System Action: The command fails and server processing.
Explanation: During configuration refresh processing,
User Response: If you must change the object name a local domain definition was replaced with a
you can delete the object, define it with a new name, definition from the configuration manager. The system
and then define a profile association to the new object also deleted all policy sets, management classes, copy
(unless a wildcard profile association already exists). groups, and client schedules belonging to the locally
This will cause the object to be deleted and re-defined defined domain and added definitions from the
on managed servers with subscriptions to the profiles configuration manager.
with which this object is associated.
ANR3350W Locally defined domain domain name
contains at least one node and cannot be
replaced with a definition from the ANR3353I Managed domain domain name deleted
configuration manager. during configuration refresh processing.
Explanation: During configuration refresh processing Explanation: During configuration refresh processing,
the indicated locally defined domain could not be the indicated managed domain was removed from the
replaced with a definition from the configuration managed server. This occurred either because the
manager. The domain definition was not replaced domain has been deleted from the configuration
because the domain still contains one or more assigned manager or because the profile association no longer
nodes. exists. The system also deleted all policy sets,
management classes, copy groups, and client schedules
belonging to the managed domain.
domain is not replaced. The system will attempt to
replace the local domain during later configuration System Action: None.
refresh operations.
User Response: If you want existing nodes to be
assigned to the domain from the configuration
manager, you can temporarily assign them to another
domain. After the domain definition has successfully
been propagated from the configuration manager,

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

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

manager or because the profile association no longer
ANR3371W Server group group name cannot be
exists.
defined during configuration refresh
System Action: None. processing because a server already
exists with this name.
the enterprise configuration facility attempted to define
ANR3367I Locally defined option set option set name the indicated server group on a managed server. The
replaced during configuration refresh server group could not be defined because a server
processing. definition with the same name already exists on the
Explanation: During configuration refresh processing, managed server.
a local option set definition was replaced with a System Action: Refresh processing continues, but this
definition from the configuration manager. server group is not defined. The system will attempt to
System Action: None. 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
ANR3368I Managed option set option set name associated or delete the conflicting server definition on
deleted during configuration refresh the managed server. Alternatively, you can rename the
processing. server group on the configuration manager, after first
Explanation: During configuration refresh processing, deleting the profile association for that server group.
the indicated managed option set was removed from
the managed server. This occurred either because the ANR3372I Locally defined server server name
option set has been deleted from the configuration replaced during configuration refresh
manager or because the profile association no longer processing.
exists.
System Action: None. a local server definition was replaced with a definition
User Response: None. from the configuration manager.
ANR3369I Locally defined server group group name User Response: None.
replaced during configuration refresh
processing.
ANR3373I Server server name deleted during
Explanation: During configuration refresh processing, configuration refresh processing.
a local server group definition was replaced with a
definition from the configuration manager. Explanation: During configuration refresh processing,
the definition for managed object server name was
System Action: None. removed from the managed server. This occurred either
User Response: None. because server name has been deleted from the
configuration manager or because the profile
association no longer exists.
ANR3370I Managed server group group name
deleted during configuration refresh System Action: None.
processing. User Response: None.
the indicated managed server group was removed from ANR3374I Server group group name replaced with
the managed server. This occurred either because the server server name during configuration
server group has been deleted from the configuration refresh processing.
manager or because the profile association no longer
exists. Explanation: During configuration refresh processing,
a server group definition was replaced with a server
System Action: None. definition from the configuration manager. The server
User Response: None. has the same name as the deleted server group.

server name can be replaced with a definition from the
ANR3375W Server server name is currently in use
configuration manager, the UPDATE SERVER
cannot be deleted during configuration
command must be used to set the ALLOWREPLACE
refresh processing.
attribute to ON.
the enterprise configuration facility attempted to
ANR3470I Command: Auditing enterprise
remove the indicated server definition because it has
configuration definitions.
been deleted from the configuration manager or
because the profile association no longer exists. The Explanation: The server has started to audit database
indicated server could not be deleted on the managed definitions used by the enterprise configuration facility.
server because server name is in use. This could occur if
the managed server has an active connection to server System Action: Server database audit operation
name or if the managed server has a device class with continues.
DEVTYPE=SERVER that refers to server name. User Response: None.
server definition is not deleted. The system will attempt ANR3471E Audit command: Enterprise configuration
to delete the server during later configuration refresh global attributes are missing.
operations.
Explanation: A database audit process finds that the
User Response: Before server name can be deleted, the global attributes used by the enterprise configuration
managed server must not have a connection to that facility are missing.
server and the managed server cannot have any
device-class references to that server. System Action: Audit processing continues.
User Response: Reissue the audit command with
ANR3376W Server server name is the event server FIX=YES specified so that the enterprise configuration
and cannot be deleted during global attributes can be recreated.
Explanation: During configuration refresh processing, ANR3472I Audit command: Enterprise configuration
the enterprise configuration facility attempted to global attributes are missing - attributes
remove the indicated server definition because it has will be recreated using available
been deleted from the configuration manager or database information or default values.
because the profile association no longer exists. The Explanation: A database audit process finds that the
indicated server could not be deleted on the managed global attributes used by the enterprise configuration
server because it is the event server for the managed facility are missing. Because FIX=YES has been
server. specified on the AUDIT command, these attributes will
System Action: Refresh processing continues, but this be recreated using available information from the
server definition is not deleted. The system will attempt database or default values.
to delete the server during later configuration refresh System Action: Audit processing continues.
operations.
User Response: When the audit completes, you can
User Response: Before server name can be deleted, the use the QUERY STATUS command to examine the
DELETE EVENTSERVER command must be used to values set for the enterprise configuration global
remove the event server reference to server name. attributes. Then use the appropriate SET command to
change the attributes, if desired.
ANR3377W Replacement of local server server name
with a definition from the configuration ANR3473E Audit command: Enterprise configuration
manager is not allowed. global attribute(s) are incorrect.
Explanation: During configuration refresh processing, Explanation: A database audit process finds that
the enterprise configuration facility attempted to global attributes used by the enterprise configuration
replace the indicated server definition with a definition facility are incorrect.
from the configuration manager. This operation could
not be performed because ALLOWREPLACE=NO for System Action: Audit processing continues.
the indicated server. User Response: Reissue the audit command with
System Action: Refresh processing continues, but this FIX=YES specified so that the enterprise configuration
server definition is not replaced. The system will global attributes can be corrected.
attempt to replace the server definition during later
configuration refresh operations.
User Response: Before the local server definition for

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

ANR3483E Audit command: Subscription information
User Response: Reissue the audit command with is inconsistent.
FIX=YES so that the information can be corrected.
Explanation: A database audit process detects
inconsistent profile subscription information. This
ANR3478E Audit command: Profile information is information can be corrected.
inconsistent - it will be corrected.
Explanation: A database audit process detects
inconsistent configuration profile information. Because User Response: Reissue the audit command with
FIX=YES has been specified for the audit command, the FIX=YES so that the information can be corrected.
information will be corrected.

indication of why the files where skipped. Files can be
ANR3484E Audit command: Profile subscription
skipped because of failures locking those files or for
information is inconsistent - it will be
other more serious problems. First, retry the command
corrected.
and see if it completes without any skipped files. If you
Explanation: A database audit process detects are unable to generate the backup set without skipping
inconsistent profile subscription information. Because files, please contact your local service representative for
FIX=YES has been specified for the audit command, the assistance.
information will be corrected.
System Action: Audit processing continues. ANR3503E Generation of backup set for node name
as set name failed.
Explanation: The named object for the specified node
was not created. An error was encountered causing the
ANR3485E Audit command: Profile subscriptions
creation of this object set not to complete successfully.
were found to more than one
configuration manager. System Action: Server operation continues.
Explanation: A database audit process determines that User Response: Evaluate other messages that were
a managed server has subscriptions to more than one issued and try to determine the cause of the failure.
configuration manager. This may cause the enterprise After determining the cause of the failure, retry the
configuration facility to behave in an unpredictable command. If the cause can not be determined, please
manner. contact your local service representative.
System Action: Audit processing continues. If ANR3504W was received, than an error occurred
while logging the volumes used to the server volume
User Response: Delete subscriptions for all but one
history. It is possible to issue a DEFINE BACKUPSET
configuration manager. To do this, it may be necessary
listing these volumes. That would cause the server to
to delete subscriptions to all configuration managers
create the necessary entries for this backup set on this
and then define the desired subscriptions.
server.
ANR3500I Backup set for node node name as set

ANR3504W Backup set for node name as set name was
name being generated.
not able to log the volumes used for this
Explanation: The named object set is being created for operation to the server volume history.
the specified node.
System Action: The server generates a backup set. was created. However, when the process attempted to
add the volumes, used for this operation to the volume
User Response: None. history for the server, an error occurred and this could
not be completed.
ANR3501I Backup set for node name as set name System Action: Server operation continues.
completed successfully - processed files
files. User Response: Review other messages issued to
determine which volumes where used for to generate
Explanation: The named object set was successfully this backup set. The volumes can be inserted into the
created for the specified node. The number of files server volume history for use by issuing a DEFINE
processed is specified. BACKUPSET and listing these volumes. This will also
System Action: None. allow this backup set to be queried from a client as
well since there is not a server entry for this backup
User Response: None. set. Only issue the DEFINE BACKUPSET if this
generate backup set operation completed successfully.
ANR3502W Backup set for node name as set name
completed with file processing errors - ANR3505I Backup set for node name as set name
processed files files with error files files used volume volume name.
skipped.
Explanation: The named object set was successfully used the specified volume.
created for the specified node. However, during
processing errors were encountered accessing some files System Action: Server operation continues.
- these files were skipped. User Response: None.
User Response: Evaluate other server messages for an

volume name.
a QUERY PROCESS command, and indicates that a
generate backupset process has been canceled. The
data storage - insufficient number of
process will end shortly.
System Action: The process terminates and server media.
User Response: None. the server cannot allocate sufficient mount points.
ANR3508W Generation of backup set for node name ended and server operation continues.
as set name failed - no filespaces to
process.
available.
was not created. No filespaces were available to
ANR3513E Command: Output error encountered in
process.
Explanation: The command command operation ends
User Response: Reissue the command against a node because an error has been encountered by the server in
that has filespaces associated with it. If no filespaces writing to a device. Possible reasons include:
exist for a given node, than there is no file data to v I/O error writing to a device
write to the backupset.
v No storage space.
ends and server operation continues.
data storage - device class device class
name is not defined. User Response: Query the activity log to find
messages preceding this one to determine the cause of
the error. After the problem is corrected, the command
an error occurred because the specified device class is
can be retried.
not defined.
System Action: The command command is ended and
ANR3514E Command: Data transfer was interrupted
User Response: Make sure the specified device class is
defined.
command command operation failed because data
ANR3510E Command: Error encountered in accessing external event.
data storage - disk volume specified.
Explanation: During command command processing, ended and server operation continues.
an error occurred because a specified volume is a disk
volume rather than a tape volume.
System Action: The command command is ended and interrupted. Reissue the command command after the
server operation continues. problem is resolved.
User Response: Make sure that all volumes specified
for the command command are tape volumes. ANR3515E Command: Error encountered in accessing
data storage - volume already in use.
ANR3511E Command: Error encountered in accessing Explanation: During command command processing, a
data storage - invalid volume name volume cannot be used because it is already defined in
specified. 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
accessing data storage while processing command
another process.
command. The error occurred because an attempt has
been made to access a volume with an invalid name. System Action: The command command operation is
ended and server operation continues. User Response: Specify a volume that is not in use or

defined in a storage pool, and that has not been System Action: The command command operation
previously used for an export, database dump, or ends and server operation continues.
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. ANR3520E Command: Internal error encountered in
ANR3516E Command: Out of space on sequential Explanation: The server encounters an internal error
media, scratch media could not be in accessing data storage while processing command
mounted. command operation.
Explanation: During command command processing, System Action: The command command operation is
the process encounters an out-of-space condition ended and server operation continues.
writing to the sequential media. Command command
ends when there is no more space on the sequential User Response: Use the QUERY ACTLOG command
media for storing data and SCRATCH=NO has been to examine messages prior to this error to determine
specified on command command. the cause of the data storage failure. If the failure can
be found and resolved, reissue the command command
System Action: Command command processing ends. operation. If the failure cannot be found, contact your
Server processing continues. service representative for assistance in resolving the
problem.
SCRATCH=YES or specify additional volume names on
the command. ANR3521W BackupSet command: Data storage retrieve
or restore failed - data integrity error
detected.
data storage - required volume was not Explanation: The server ends an backup set operation
mounted. because an internal database integrity error has been
encountered on the server.
Explanation: During command command processing, a
required volume cannot be mounted. The mount System Action: The server ends the backup set
request may have been canceled. operation and continues operation.
System Action: The command command operation is User Response: Contact your service representative.
User Response: Issue the command again and make ANR3522W Command: Retrieve or restore failed - file
sure the necessary volumes are accessible. was deleted from data storage during
retrieval.
ANR3518I Command: Processing canceled before Explanation: The server ends a file retrieval operation
completion. for the specified command because the file has been
deleted from data storage by another process before
command command has been canceled with the
CANCEL PROCESS command. System Action: The server ends the command and
System Action: Processing for the command command
ends. Statistics on the number and type of objects User Response: Contact your administrator to find
moved, together with the total number of bytes copied, out if DELETE FILESPACE, DELETE VOLUME, or
are displayed on the server console following this inventory expiration processes are running; these
message. processes can delete data storage files during retrieval.
Reissue the command after these processes have been
completed or canceled.
ANR3519E Command: Insufficient memory available

ANR3523W Backup set command: Retrieve failed -
error on input storage device.
Explanation: The server encounters a memory
Explanation: The server ends a backup set operation
shortage in accessing data storage during command
for the specified session because an I/O error has been
command operation.
encountered by the server in reading from a device.

The object for which the I/O was issued is reported in
ANR3527E Backup set command operation terminated
a later message.
- incomplete input volume list.
System Action: Backup set processing skips this file,
Explanation: The list of volumes needed to process
the command was incomplete. At least one volume
User Response: Query the activity log to find needed for the operation is missing from the end of the
messages preceding this one that specify the device that list.
is failing. Storage pool volumes can be varied offline
System Action: The command operation is ended.
may need to be shut down with the HALT command to User Response: Issue the command again and make
correct the hardware problem. sure the necessary volumes are included in the volume
list.
ANR3524W Backup set command: Transaction failed -
data transfer interrupted. ANR3528E Backup set command: Media not accessible
a backup set operation failed because data transfer to Explanation: The server ends a transaction for a
or from data storage was interrupted by an external backup set operation because storage volumes are not
event. available in the storage pools in which the client files
are to be stored.
System Action: The backup set operation is ended
and server operation continues. System Action: The server ends the backup set
this message to determine why the data transfer was User Response: An authorized administrator can issue
interrupted. Attempt the backup set operation again the DEFINE VOLUME command to add storage to one
after problem is resolved. or more storage pools in the storage hierarchy. The
storage volumes online in the storage hierarchy to
ANR3525W Backup set command: Transaction failed -
make them available for file storage.
Explanation: The server ends a transaction for an
ANR3529W Generate backupset skipping damaged
backup set operation because storage volumes are not
file on volume volume name: Node node
available in the storage pools in which the client files
name, Type file type, File space filespace
are to be stored.
name, fsId filespace id, File name file name.
System Action: The server ends the backup set
Explanation: During generate backupset process, a file
is encountered that was previously found to be
User Response: An authorized administrator can issue damaged. If this file is part of an aggregate, the entire
the DEFINE VOLUME command to add storage to one aggregate was previously marked damaged, possibly
or more storage pools in the storage hierarchy. The because an integrity error was detected for some other
VARY ONLINE command can be used to vary offline file within the aggregate.
storage volumes online in the storage hierarchy to
System Action: The damaged file is not added to the
make them available for file storage.
backupset.
ANR3526E Backup set command: Error encountered in
accessing data storage - volume cannot
will reset the file status if the file is found to be
be used.
undamaged during the audit. If the file is part of an
Explanation: During backup set processing, a volume aggregate, the audit will reset the aggregate status if
has been mounted but cannot be used. the entire aggregate is found to be undamaged. If the
file is reset to the undamaged state and it is important
System Action: The backup set operation is ended that the file be included in the backupset, rerun the
and server operation continues. generate backupset command. If, however, the audit
User Response: Query the activity log for messages does not clear the damaged state of the file and if this
preceding this one that give additional information. volume is in a primary storage pool that has previously
Make sure a usable volume is specified and mounted. been backed up to a copy storage pool, attempt to
restore damaged files by using the RESTORE
STGPOOL command. If it is still important that the file
be included in the backupset, rerun the generate
backupset command.

ANR3540E Object set set node:set name was not ANR3601W Policy Domain release failed for domain
found for session session number, node. domain id due to communications failure.
Explanation: The indicated session id requested to Explanation: The storage agent was attempting to
restore the object set. The object set was not found on inform the database server that it was finished with the
the server. domain indicated by the domain id, but was unable to
communicate with the database server. The cached
System Action: The error is returned to the client.
policy information will be cleaned up when the storage
User Response: None. server terminates or re-starts or when the database
server re-starts.
ANR3541E Error error code occurred opening object System Action: The storage agent continues operation.
set set node:set name for session session The policy information is deleted from the storage
number, node. agent policy cache.
Explanation: An error occurred while opening the User Response: Policy caches are cleaned up on the
indicated object set. storage agent or server re-start. Network
communication between the storage agent and database
System Action: An error is returned to the client. server should be checked.
User Response: Correct the problem reported by
previous messages, if possible. ANR3602E Unable to communicate with database
server.
ANR3542E Error error code occurred reading object Explanation: The storage agent was attempting to
set set node:set name for session session communicate with the database server but was unable
number, node. to do so.
Explanation: An error occurred while reading the System Action: The storage agent operation fails.
indicated object set.
User Response: Check the configuration of the storage
System Action: An error is returned to the client. agent and server to ensure that communication
User Response: Correct the problem reported by parameters are correct. Ensure that the database server
previous messages, if possible. is running and is accepting messages.
ANR3543E Error error code occurred while sending ANR3603E Storage AgentStorage Agent name was
entries from object set set node:set name unable to load policy information due to
for session session number, node. a protocol error.
Explanation: An error occurred while sending entries Explanation: While receiving policy information from
for the indicated object set. a database server, processing ended prematurely
because of a protocol error.
System Action: An error is returned to the client.
System Action: Server operation continues. Policy is
User Response: Correct the problem reported by loaded from the database server database.
previous messages, if possible.
User Response: If this problem persists, contact your
ANR3550E Definition of backup set set name for
node name failed because it has an
unknown format. ANR3604E This command is not supported in the
current operating environment.
was not defined. It was generated on a server that is at Explanation: A command was issued that is valid
a higher level than this server and contains data that under most circumstances, but not in the current server
cannot be properly interpreted by this server. environment.
User Response: Define the object on a server that is User Response: Issue commands which are allowed in
compatible with the server that generated the object, or the current environment.
upgrade this server to be compatible with the server
that generated the object.

communicating, the indicated verb ( an internal request
ANR3605E Unable to communicate with storage
mechanism between the storage agent and database
agent.
server ), was unexpected. The verb number is provided
Explanation: The database server was attempting to for Tivoli support personnel.
communicate with the storage agent but was unable to
System Action: Database server and storage agent
do so.
continue. The restore request may fail, but may be
System Action: The database server operation fails. retried by the client.
User Response: Check the configuration of the storage User Response: If this problem persists, contact your
agent and server to ensure that communication service representative.
parameters are correct.
ANR3609E The storage agent was handling a
ANR3606E The storage agent was communicating restore request. A failure occurred in
with the database server on a restore starting a new thread. The return code
request with verb verb name and return code from the failing routine may
received return code return code. be useful to Tivoli service.
Explanation: The storage agent and database server Explanation: The storage agent was handling a restore
were coordinating a restore request. While request. A new thread could not be started. Without the
communicating using the indicated verb ( an internal new thread the request could not be handled.
request mechanism between the storage agent and
database server ), an unexpected return code was
continue. The restore request has failed.
received. The verb name and return code are provided
for Tivoli support personnel. User Response: Ensure that there is sufficient system
memory for the storage agent to operate properly.
Insufficient memory or paging/swap space can cause
continue. The restore request fails, but may be retried
problems in starting threads. If this problem persists,
by the client.
agent and server to ensure that communication
ANR3610I Domain Identifier domain identifier was
parameters are correct. If this problem persists, contact
not found.
your service representative.
Explanation: The server was cleaning up cached
policy information after a restore request. A domain
ANR3607E The storage agent was communicating
with the indicated identifier was not found in an
with the client on a restore request with
internal list.
verb verb name and received return code
return code. System Action: Database server and storage agent
continue.
Explanation: The storage agent was communicating
with a client for a restore request. While User Response: No response is required if the
communicating using the indicated verb ( an internal message is the result of starting a storage agent. The
request mechanism between the storage agent and storage agent requests that the server purge cached
client ), an unexpected return code was received. The information that it was using previously. It is possible
verb name and return code are provided for Tivoli that information tracking policy caching has become
support personnel. stale. In this case, no response is required. If the
message occurs without a storage agent connecting to
the server, contact your service representative.
continue. The restore request fails, but may be retried
by the client.
ANR3611E Storage Agent unable to contact server.
agent and client to ensure that communication Explanation: The storage agent was attempting to
parameters are correct. If this problem persists, contact contact the server to start a session or run a command.
your service representative. The storage agent was unable to contact the server to
start a transaction.
ANR3608E The storage agent was communicating System Action: The storage agent continues
with the database server on a restore processing. The server may be down or there may be a
request. An unexpected request (id verb ) communications problem.
was received from the database server.
User Response: No response is required if the
Explanation: The storage agent and database server message is the result of stopping a server. Ensure that
were coordinating a restore request. While

the server with which the storage agent communicates
ANR4003I Load command: Database load process
is running and that there is connectivity between the
started.
systems. The server must be restarted before you can
start a new administrator session with the storage Explanation: The database load process has started.
agent.
System Action: The server loads the contents of the
database from a file or removable media.
ANR3999E Failure validating database load:
expected numRecs records and numBV bit
vectors - loaded actNumRecs records and
actNumBV bit vectors. ANR4004I Load command: Database load process
completed.
Explanation: The database load process has ended
and the number of records, the number of bit vectors, Explanation: The database load process has ended.
or both the number of records or number of bit vectors
loaded, failed to validate. System Action: The server completes processing.
System Action: The LOAD DB process completes with User Response: None.
a failure. The server database is not in a usable state.
User Response: A number of possible causes exist. To ANR4005E Load command: Database load process
recover from this situation, first retry the database load terminated due to error (error indicator).
process. If the error reoccurs, check the activity log or Explanation: The database load process has ended
other system logs to determine if there is a hardware or prematurely due to an error.
media error. If a hardware or media error exists, correct
the error and retry the load process. If a hardware or System Action: The server ends load processing.
media error does not exist, it is likely the dump or User Response: Examine previously issued messages
unload of the server database has encounted an error to determine if an error can be corrected, such as a
sesulting in the dump/unload server database image as syntax error. If you cannot resolve the error, contact
being unusable or that there is an error in the logic for your service representative.
load db processing. Contact your service representative
for assistance.
ANR4006I Command: Volume volume number written
by process is volume name.
ANR4000I Dump command: Database dump process
started. Explanation: A sequential data process wrote to the
volume named in the series of one or more volumes
Explanation: The database dump process has started. that were used to store output. The volume’s position
System Action: The server dumps the contents of the in the series in indicated by the volume number
database to a file or removable media. reported.
User Response: None. System Action: The server ends processing.

ANR4001I Dump command: Database dump process
completed. ANR4007E Command: A transaction error was
Explanation: The database dump process has ended. encountered in recording volume usage
history.
System Action: The server completes processing.
Explanation: The command process encounters a
User Response: None. database transaction error in recording the names of the
volumes used for the process in the server database.
ANR4002I Dump command: Database dump process System Action: The server ends processing.
terminated due to error (error indicator).
User Response: Examine previously issued messages
Explanation: The database dump process has ended to determine if there is an error that can be corrected,
prematurely due to an error. such as a syntax error. If you cannot resolve the error,
System Action: The server ends dump processing. contact your service representative. The volumes used
by the process are valid for the corresponding input
User Response: Examine previously issued messages process, but are not recorded in sequential volume
to determine if an error can be corrected, such as an history lists generated by the server.
output error. If you cannot resolve the error, contact

ANR4008W Load command: Database object object ANR4012W Dump command: Database page page
name does not exist. number is damaged.
Explanation: The database load process attempts to Explanation: The specified database page is damaged;
delete a database object, but the object does not exist. it will not be dumped.
System Action: Database processing continues. System Action: Processing continues.
ANR4009E Load command: Database object object ANR4013I Dump command: Dumped number of
name cannot be deleted because it is in entries database entries (cumulative).
use by another process.
Explanation: This message indicates the number of
Explanation: The database load process attempts to database entries that have been dumped so far during
delete a database object, but the object is currently database dump processing.
being used by another process.
System Action: Database processing ends.
User Response: Reissue the command. If it fails,
ANR4014E Load command: The specified input
volume does not contain a server
ANR4010E Dump/load command: Database dump/load database dump.
processing failed - insufficient memory.
Explanation: The specified volume does not contain a
Explanation: The database dump/load process fails dump created from the database dump command.
due to insufficient memory.
System Action: Processing ends.
System Action: Database processing ends.
server. There are two ways to do this:
ANR4015E Load command: Invalid record format
v Increase the size of the server’s virtual machine (for (format code) detected.
VM), or region size (for MVS). For AIX, ensure that
there is sufficient paging space. You may also use Explanation: During processing of command load
SMIT to determine if the number of applications is command, an invalid record type is detected when
causing a memory shortage. For OS/2, ensure that reading the dumped information from the dump
there is sufficient space for the OS/2 SWAPPER.DAT media.
file. Check your CONFIG.SYS for the SWAPPATH System Action: Processing of the command ends.
statement to determine where your SWAPPER.DAT
file is located and then determine how much space is User Response: Examine the server messages issued
left on the drive. prior to this message to determine the source of the
v Decrease the amount of space allocated to the error. On MVS or VM, the LOADDB command syntax
server’s database or log buffer pool. To do this, may be specified by using a ddname or by specifying a
update the value of the BUFPOOLSIZE or device class name. You must use the same method that
LOGPOOLSIZE parameters in the server options file was used when the database was originally dumped. If
and restart the server. Note that each page causes an you did not, this error message will be displayed. Try
additional 4K page to be allocated for the specified loading the database by using the other method of
buffer pool. Reducing the pool sizes requires more syntax (devclass). If the error cannot be isolated and
I/O to service the same amount of data; some resolved, contact your service representative.
performance degradation may result.
ANR4016E Load command: Invalid header sequence
ANR4011W Dump command: Database page page number detected in database dump.
number is invalid - it will be skipped. Expected expected sequence number; Actual
actual sequence number.
Explanation: The specified page is invalid, and it will
not be used during dump processing. Explanation: During processing of command load
command, an invalid sequence number is detected when
System Action: Processing continues. reading the dumped information from the dump
media.

User Response: Examine previously issued server User Response: Refer to the other displayed messages
messages to determine the source of the error. If the to determine why the operation failed; correct the
error cannot be isolated and resolved, contact your problem and restart the process.
ANR4022E Dump command: Error (error code)
ANR4017E Load command: Invalid record type record occurred during a write operation.
type read from database dump data.
Explanation: The server database dump process
Explanation: The server database load process encounters an error while writing to the dump media.
encounters an invalid record in reading data from the
System Action: Server processing continues, the dump
dump media.
processing ends.
System Action: The database load process ends.
User Response: Refer to the other displayed messages
User Response: Examine previously issued server to determine why the operation failed; correct the
messages to determine the source of the error. If the problem and restart the process.
error cannot be isolated and resolved, contact your
ANR4023E Load command: Error (error code) occurred
during a read operation.
ANR4018E Load command: Load processing failed -
Explanation: The server database load process
encounters an error reading from the dump media.
Explanation: The load process fails due to insufficient
System Action: The database load operation ends.
recovery log space.
System Action: Database load processing ends.
to determine why the operation failed; correct the
User Response: Reinstall the server and specify a problem and restart the process.
larger recovery log and reissue the database load
command.
ANR4025I Dumped number of pages database pages,
number of bit vectors bit vectors, and
ANR4019E Load command: Load processing failed - number of database entries database entries;
insufficient database space. number of bad pages bad database pages
have been encountered; number of bytes
Explanation: The load process fails due to insufficient
copied.
database space.
System Action: Load processing ends.
a QUERY PROCESS command executed against an
User Response: Reinstall the server and specify a online database dump process. The message displays
larger database and reissue the database load information about the progress of the dump.
command.
System Action: Database dump processing continues.
User Response: None. You may cancel the dump
ANR4020E Load command: Batch database insert
process with the CANCEL PROCESS command.
failed.
Explanation: The database load process fails when it
ANR4026I Dump command: Process process number,
attempts to insert a batch of rows into the database.
database dump has completed.
System Action: Database load processing ends.
Explanation: The online server database dump process
User Response: Examine the messages issued prior to started as process process number has completed.
this one to determine if an error can be corrected. You
System Action: Database dump processing ends.
may wish to reinstall the server with a new recovery
log and database and reissue the load command. If the User Response: None.
problem persists, contact your service representative.
ANR4021E Dump/load command: Error (error code) database dump was canceled.
occurred during an open operation.
Explanation: The online server database dump process
Explanation: An error occurs while attempting an started as process process number has been canceled
open operation on the dump media for a database with the CANCEL PROCESS command.
dump/load operation.
System Action: Database dump processing ends.

ANR4033I Dump/load command: Copied number of bit
vectors bit vectors.
Explanation: This message is displayed at the end of a
Database dump terminated due to an
server database dump or load command to indicate the
error (error code).
number of database bit vectors copied.
Explanation: The online database dump process has
System Action: Database dump or load processing
ended prematurely due to an error.
ends.
System Action: The server ends dump processing.
this message to see if an error can be corrected, such as
ANR4034I Dump/load command: Encountered number
output error. If you cannot resolve the error, contact
of bit vectors bad database pages.
ANR4029I Dump command: Database checkpoint
number of invalid database pages that have been
started.
encountered.
Explanation: The database dump process is flushing
updated database pages from the database buffer pool
ends.
to stable storage so that they can be dumped.
System Action: Database dump processing continues.
ANR4035I Dump/load command: Encountered number
of bit vectors bad database records.
ANR4030I Dump command: Database checkpoint
completed.
Explanation: The database dump process has flushed number of invalid database records that have been
all updated pages from the database buffer pool to encountered.
stable storage.
System Action: Database load processing continues. ends.
ANR4031I Dump/load command: Copied number of ANR4036I Dump/load command: Copied number of bit
pages database pages. vectors database entries.
Explanation: This message is displayed at the end of a Explanation: This message is displayed at the end of a
server database dump or load command to indicate the server database dump or load command to indicate the
number of database pages copied. number of database entries that have been copied.
System Action: Database dump or load processing System Action: Database dump or load processing
ends. ends.
ANR4032I Dump/load command: Copied number of ANR4037I Dump/load command: number of bit vectors
records database records. copied.
Explanation: This message is displayed at the end of a Explanation: This message is displayed at the end of a
server database dump or load command to indicate the server database dump or load command to indicate the
number of database records copied. number of bytes that have been copied.
System Action: Database dump or load processing System Action: Database dump or load processing
ends. ends.

will attempt to correct the policy domain assignment
ANR4038I Load command: Loading database
for the node.
information dumped on dump date at
dump time. System Action: Audit processing continues.
Explanation: At the beginning of a server database User Response: When the audit command completes,
load process, this message indicates the date and time you may want to check the domain assignment for this
that the dump took place for the database information node, and reassign the node to a different policy
that is loaded into the server. domain, if desired.
System Action: Database load processing continues.
ANR4043I Audit command: Node node name
assignment failed - will attempt to
assign the node to domain domain name.
ANR4039I Load command: Loaded number of entries
Explanation: A database audit process finds a node
database entries (cumulative).
assigned to a policy domain that cannot be located in
Explanation: This message indicates the number of database policy entries. Because FIX=YES has been
database entries that have been loaded so far during specified for the audit command, the audit function is
database load processing. attempting to assign the node to an existing policy
domain. The function attempts to assign the node to
System Action: Database load processing continues.
the domain name specified.
User Response: When the audit command completes,
ANR4040I Audit command: Auditing client node and
you may want to check the domain assignment for this
administrator definitions.
node, and reassign the node to a different policy
Explanation: This message is displayed during a domain, if desired.
database audit and indicates that the client node and
administrator definitions are being examined by the
ANR4044I Audit command: Could not assign Node
database audit process.
node name to a policy domain; use the
System Action: Audit processing continues. UPDATE NODE command to assign a
policy domain for this node.
Explanation: A database audit process cannot find an
appropriate policy domain for assigning the specified
ANR4041I Audit command: Node node name is node.
assigned to Domain domain name, but
not verified by server database policy System Action: Audit processing continues.
entries.
Explanation: A database audit process finds a node use the UPDATE NODE command to assign the
assigned to a policy domain that is not recorded specified node to an appropriate policy domain.
properly in policy database entries.
System Action: Audit processing continues. ANR4045I Audit command: Invalid compression
value encountered for node node name.
User Response: If FIX=YES has not been specified for
the audit command, you may want to run this Explanation: A database audit process encounters an
command again, and specify FIX=YES so that the audit invalid node compression value for the node indicated.
process can correct the policy domain assignment for
the node.
the audit command, you may want to run this
ANR4042I Audit command: Node node name is
command again, and specify FIX=YES so that the audit
assigned to Domain domain name, but
process can correct the problem.
not found in server database policy
entries - attempting to assign the node
to domain domain name. ANR4046I Audit command: Invalid compression
value encountered for node node name
Explanation: A database audit process finds a node
the default value will be set.
assigned to a policy domain that cannot be referenced
in database policy entries. Because FIX=YES has been Explanation: A database audit process encounters an
specified for the audit command, the audit function invalid node compression value for the node indicated.
Because FIX=YES has been specified, the audit function

sets the node’s compression value to the default value. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: If you want the backup delete value
for the specified node to be set to a value other than
User Response: If you want the compression value for
the default, use the UPDATE NODE command to
the specified node to be set to a value other than the
change the value after the audit command has
default, use the UPDATE NODE command to change
completed.
the value after the audit command has completed.
ANR4051I Audit command: Invalid lock state

ANR4047I Audit command: Invalid archive delete
encountered for node node name.
value encountered for node node name.
Explanation: A database audit process encounters an
invalid lock state value for the node indicated.
invalid archive delete permission value for the node
indicated. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: If FIX=YES has not been specified for
ANR4052I Audit command: Invalid lock state
encountered for node node name the
ANR4048I Audit command: Invalid archive delete
node will be unlocked.
the default value will be set. Explanation: A database audit process encounters an
invalid lock state value for the node indicated. Because
FIX=YES has been specified, the audit function sets the
invalid archive delete permission value for the node
node’s lock state to unlocked.
indicated. Because FIX=YES has been specified, the
audit function sets the node’s archive delete permission System Action: Audit processing continues.
value to the default value.
User Response: If you want the lock state for the
System Action: Audit processing continues. specified node to be set to a value other than unlocked,
use the LOCK NODE command to change the value
User Response: If you want the archive delete value
after the audit command has completed.
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 ANR4053I Audit command: Invalid Node conversion
completed. state encountered for node node name.
ANR4049I Audit command: Invalid backup delete invalid Node conversion state value for the node
value encountered for node node name. indicated.
Explanation: A database audit process encounters an System Action: Audit processing continues.
invalid backup delete permission value for the node
indicated.
System Action: Audit processing continues. command again, and specify FIX=YES so that the audit
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
ANR4050I Audit command: Invalid backup delete
node will be reset.
the default value will be set. Explanation: A database audit process encounters an
invalid conversion state value for the node indicated.
invalid backup delete permission value for the node
resets the conversion state.
indicated. Because FIX=YES has been specified, the
audit function sets the node’s backup delete permission System Action: Audit processing continues.
value to the default value.

ANR4055I Audit command: Invalid lock state ANR4059E Audit command: Administrative ID
encountered for administrator assignments are incorrect.
administrator name.
Explanation: A database audit process encounters an global attributes used for server administrative
invalid lock state value for the administrator indicated. activities are incorrect.
System Action: Audit processing continues. System Action: Audit processing continues.
User Response: If FIX=YES has not been specified for User Response: Reissue the audit command with
the audit command, you may want to run this FIX=YES specified so that the administrative global
command again, and specify FIX=YES so that the audit attributes can be corrected.
ANR4060I Audit command: Administrative ID
ANR4056I Audit command: Invalid lock state assignments are incorrect - value(s) will
encountered for administrator be corrected.
administrator name the administrator will
be unlocked.
global attributes used for server administrative
Explanation: A database audit process encounters an activities are incorrect. Because FIX=YES has been
invalid lock state value for the administrator indicated. specified on the AUDIT command, the attribute value
Because FIX=YES has been specified, the audit function will be corrected in the server database.
sets the administrator’s lock state to unlocked.
User Response: If you want the lock state for the
specified administrator to be set to a value other than
ANR4061E Audit command: Administrative global
unlocked, use the LOCK ADMIN command to change
attribute(s) are incorrect.
the value after the audit command has completed.
ANR4057E Audit command: Administrative global
activities are incorrect.
attributes are missing.
global attributes used for server administrative User Response: Reissue the audit command with
activities are missing. FIX=YES specified so that the administrative global
attributes can be corrected.
ANR4062I Audit command: Administrative global
FIX=YES specified so that the administrative global
attribute(s) are incorrect - default values
attributes can be recreated.
will be set.
ANR4058I Audit command: Administrative global
attributes are missing - default values
activities are incorrect. Because FIX=YES has been
will be used to recreate the attributes.
specified on the AUDIT command, default attribute
Explanation: A database audit process finds that the values will be used to correct the administrative global
global attributes used for server administrative 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 User Response: When the audit completes, you can
attributes. use the QUERY STATUS command to examine the
values set for the administrative global attributes, and
use the appropriate SET command to change the
User Response: When the audit completes, you can attributes, if desired.
use the QUERY STATUS command to examine the
values set for the administrative global attributes, and
use the appropriate SET command to change the
attributes, if desired.

review your administrator definitions with the QUERY
ANR4063E Audit command: Client node node number
ADMIN command. You can then use the REGISTER
not found in the server database.
ADMIN and UPDATE ADMIN commands to change
Explanation: A database audit process finds a client any definitions desired.
node reference that is not defined correctly in the
server database.
ANR4067E Audit command: Domain domain name
System Action: Audit processing continues. referenced by an administrator authority
does not exist.
User Response: If the audit command has not been
issued with FIX=YES specified, reissue the audit Explanation: A database audit process finds a policy
function specifying FIX=YES so that the error can be administrator reference to a policy domain that does
corrected. not exist.
ANR4064I Audit command: Client node node number
User Response: Reissue the audit command and
created as node node name assigned to
specify FIX=YES so that the error can be corrected.
policy domain domain name in the server
database.
ANR4068I Audit command: Policy domain domain
Explanation: A database audit process finds a client
name referenced by an administrator
node reference that is not defined correctly in the
authority does not exist - the authority
server database. Because FIX=YES has been specified
will be removed.
for the audit command, the audit function creates a
new node definition for the node with the name Explanation: A database audit process finds a policy
specified. 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, use the QUERY NODE command to
examine the node that was added. Use the RENAME User Response: After the audit command completes,
NODE command to rename the corrected node and the review your administrator definitions with the QUERY
UPDATE NODE command to set attributes for the ADMIN command. You can then use the REGISTER
corrected node, such as its password. You can issue the ADMIN, UPDATE ADMIN, and GRANT AUTHORITY
QUERY FILESPACE command for the node, to commands to change any definitions.
determine which node and platform type was
originally represented by the corrected node.
ANR4069E Audit command: Storage pool storage pool
ANR4065E Audit command: Administrator authority does not exist.
administrator number not found in the
server database. Explanation: A database audit process finds a storage
administrator reference to a storage pool that does not
Explanation: A database audit process finds an exist.
administrator reference that is not defined correctly in
the server database. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: Reissue the audit command and
ANR4070I Audit command: Storage pool storage pool
ANR4066I Audit command: Administrator authority does not exist - the authority
administrator number not found in the will be removed.
server database - reference will be
removed. Explanation: A database audit process finds a policy
administrator reference to a storage pool that does not
Explanation: A database audit process finds an exist. Because FIX=YES has been specified, the
administrator reference that is not defined correctly in authority will be removed.
the server database. The invalid reference will be
removed from the database. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: After the audit command completes,
review your administrator definitions with the QUERY
User Response: After the audit command completes, ADMIN command. You can then use the REGISTER

ADMIN, UPDATE ADMIN, and GRANT AUTHORITY domain do not match the actual number of nodes
commands to change any definitions. assigned to the domain.
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
ANR4077I Audit command: Invalid client node count
node or administrator indicated.
detected for policy domain domain name
System Action: Audit processing continues. count will be corrected.
User Response: If FIX=YES has not been specified for Explanation: A database audit process finds that the
the audit command, you may want to run this count of nodes recorded for the specified policy
command again, and specify FIX=YES so that the audit domain do not match the actual number of nodes
process can correct the problem. assigned to the domain. Because FIX=YES has been
specified for the command, the node count will
automatically be corrected.
ANR4072I Audit command: Invalid file aggregation
information encountered for node node System Action: Audit processing continues.
name.
Explanation: A database audit process encounters
invalid information used for controlling aggregation of
ANR4078E Audit command: Invalid activation
files for the node indicated.
indicators encountered for policy
System Action: Audit processing continues. domain domain name.
User Response: If FIX=YES has not been specified for Explanation: A database audit process finds incorrect
the audit command, you may want to run this policy set activation entries for the specified policy
command again, and specify FIX=YES so that the audit domain.
ANR4073I Audit command: Invalid file aggregation
information encountered for node node
name - information will be corrected.
ANR4079I Audit command: Invalid activation
indicators encountered for policy
invalid information used for controlling aggregation of
domain domain name - entry will be
files for the node specified. Because FIX=YES has been
corrected.
specified, the audit function corrects the information.
Explanation: A database audit process finds incorrect
policy set activation entries for the specified policy
User Response: None. domain. Because FIX=YES has been specified for the
audit command, the entry will be corrected.
ANR4075I Audit command: Auditing policy System Action: Audit processing continues.
definitions.
database audit and indicates that the server policy
ANR4080E Audit command: Invalid grace period
information (domain, policy set, management classes,
backup retention value encountered for
and copy groups) are being examined by the database
audit process.
Explanation: A database audit process finds an
incorrect grace period retention value for the specified
User Response: None. policy domain.
ANR4076E Audit command: Invalid client node count
detected for policy domain domain name.
count of nodes recorded for the specified policy

ANR4081I Audit command: Invalid grace period
backup retention value encountered for
policy domain domain name - default ANR4086E Audit command: Invalid node node number
value will be set. found assigned to domain domain name.
Explanation: A database audit process finds an Explanation: A database audit process finds a node
incorrect grace period retention value for the specified number assigned to a policy domain that does not
policy domain. Because FIX=YES has been specified for reference a valid client node definition.
the audit command, the default value will be set.
User Response: None. specify FIX=YES so that the error can be corrected.
ANR4082E Audit command: Invalid grace period ANR4087I Audit command: Invalid node node number
archive retention value encountered for found assigned to domain domain name
policy domain domain name. reference will be deleted.
Explanation: A database audit process finds an Explanation: A database audit process finds a node
incorrect grace period retention value for the specified number assigned to a policy domain that does not
policy domain. reference a valid client node definition. Because
reference will be deleted.
ANR4083I Audit command: Invalid grace period
archive retention value encountered for ANR4088E Audit command: Default management
policy domain domain name - default class management class name specified for
value will be set. policy set policy set name in domain
domain name does not exist.
Explanation: A database audit process finds an
incorrect grace period retention value for the specified Explanation: A database audit process finds a policy
policy domain. Because FIX=YES has been specified for set with a default management class specified that does
the audit command, the default value will be set. not exist.
User Response: None. User Response: Reissue the audit command and
ANR4084E Audit command: Invalid administrator
update information encountered for ANR4089I Audit command: Default management
policy domain domain name. class management class name specified for
policy set policy set name in domain
domain name does not exist - the
last updated information for the specified policy
reference will be removed.
domain.
Explanation: A database audit process finds a policy
set with a default management class specified that does
User Response: Reissue the audit command and not exist. Because FIX=YES has been specified for the
specify FIX=YES so that the error can be corrected. audit command, the reference will be removed from the
policy set.
ANR4085I Audit command: Invalid administrator System Action: Audit processing continues.
update information encountered for
policy domain domain name - information
examine the policy set specified, and set a new default
will be corrected.
management class for the set. If the policy set is the
Explanation: A database audit process finds incorrect ACTIVE policy set, you must activate a new policy set
last updated information for the specified policy for the domain with a valid default management class.
domain. Because FIX=YES has been specified for the
command, the information is corrected.

ANR4090E Audit command: Active Policy set for ANR4094E Audit command: A management class
domain domain name does not contain a identifier is not defined for
valid default management class - policy management class management class name
will fail for this domain. Please correct in policy set set name, domain domain
the ACTIVE policy set. name - an identifier will be generated
for this management class.
Explanation: A database audit process finds an active
policy set for the specified policy domain that does not Explanation: A database audit process finds incorrect
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.
you must activate a new policy set for the domain with
a valid default management class. User Response: None.
ANR4091E Audit command: Invalid administrator ANR4095E Audit command: An invalid management
update information encountered for class identifier (actual identifier) was
policy set set name in policy domain encountered for management class
domain name. management class name in policy set set
name, domain domain name (expected
expected identifier).
last updated information for the specified policy set.
information for the specified management class.
ANR4092I Audit command: Invalid administrator
policy set set name in policy domain ANR4096E Audit command: An invalid management
domain name - information will be class identifier (actual identifier) was
corrected. encountered for management class
management class name in policy set set
name, domain domain name (expected
last updated information for the specified policy set.
expected identifier) - the correct identifier
Because FIX=YES has been specified for the command,
will be stored.
the information is corrected.
information for the specified management class. The
User Response: None. audit process corrects the identifier, because FIX=YES
has been specified for the audit command.
ANR4093E Audit command: A management class System Action: Audit processing continues.
identifier is not defined for
in policy set set name, domain domain
name. ANR4097E Audit command: Invalid administrator
information for the specified management class.
in policy set set name in policy domain
System Action: Audit processing continues. domain name.
User Response: Reissue the audit command and Explanation: A database audit process finds incorrect
specify FIX=YES so that the error can be corrected. last updated information for the specified management
class.

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

ANR4106E Audit command: An invalid copy group ANR4110E Audit command: Invalid archive copy
identifier (actual identifier) was group attributes encountered for copy
encountered for a copy group in group copy group name in management
management class management class name, class management class name, policy set set
policy set set name, domain domain name name, domain domain name.
(expected expected identifier).
Explanation: A database audit process finds incorrect invalid archive copy group attributes for the specified
information for the specified copy group. copy group.
User Response: For programming support, contact User Response: If FIX=YES has not been specified for
your service representative. 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 ANR4111I Audit command: Invalid archive copy
encountered for copy group name copy group attributes encountered for copy
group name (expected expected identifier). group copy group name in management
class management class name, policy set set
name, domain domain name - the copy
information for the specified copy group name.
group will be corrected using default
System Action: Audit processing continues. attributes.
User Response: For programming support, contact Explanation: A database audit process encounters
your service representative. 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
ANR4108E Audit command: Invalid backup copy default values for the attributes found in error.
group attributes encountered for copy
group copy group name in management System Action: Audit processing continues.
class management class name, policy set set
name, domain domain name.
examine the copy group by using the QUERY
Explanation: A database audit process encounters COPYGROUP command, and correct the attributes
invalid backup copy group attributes for the specified with the UPDATE COPYGROUP command, if desired.
copy group.
System Action: Audit processing continues. ANR4112W Audit command: Storage pool storage pool
name, specified as a destination for copy
User Response: If FIX=YES has not been specified for group copy group name in management
the audit command, reissue the command specifying class management class name, policy set set
FIX=YES so that the inconsistency can be corrected. name, domain domain name, does not
exists.
ANR4109I Audit command: Invalid backup copy Explanation: A database audit process encounters a
group attributes encountered for copy storage pool specified for the destination of the
group copy group name in management specified copy group that is not defined in the server
class management class name, policy set set database. If this copy group is used in an active policy
name, domain domain name - the copy set, then backup or archive operations will fail when
group will be corrected using default attempting to put client data in the destination.
attributes.
invalid backup copy group attributes for the specified User Response: After the audit command completes,
copy group. Because FIX=YES has been specified for use the DEFINE STGPOOL command to define the
the command, the copy group will be corrected using missing storage pool or the UPDATE COPYGROUP
default values for the attributes found in error. command to update the copy group to refer to an
existing storage pool.
examine the copy group by using the QUERY
COPYGROUP command, and correct attributes with
the UPDATE COPYGROUP command, if desired.

ANR4113E Audit command: Invalid administrator ANR4117E Audit command: Policy set set name in
update information encountered for domain domain name is referenced, but
copy group copy group name in not formally defined.
Explanation: A database audit process finds a
policy set set name, policy domain domain
reference to the specified policy set, but the set is not
name.
formally defined in the server database.
last updated information for the specified copy group.
ANR4118I Audit command: Policy set set name in
domain domain name is referenced, but
ANR4114I Audit command: Invalid administrator not formally defined - a policy set with
update information encountered for this name will be created.
copy group copy group name in
reference to the specified policy set, but the set is not
policy set set name, policy domain domain
formally defined in the server database. Because
name - information will be corrected.
FIX=YES has been specified, the audit process will
Explanation: A database audit process finds incorrect create a new policy set with this name.
last updated information for the specified copy group.
the information is corrected. User Response: After the audit command has
completed, you can view the attributes for this policy
set by using the QUERY POLICYSET command, and
User Response: None. update attributes with the UPDATE POLICYSET
command, if desired.
ANR4115E Audit command: Policy domain domain
name is referenced, but not formally ANR4119E Audit command: Management class class
defined. name in policy set set name, domain
domain name is referenced, but not
formally defined.
reference to the specified policy domain, but the
domain is not formally defined in the server database. Explanation: A database audit process finds a
reference to the specified management class, but the
class is not formally defined in the server database.
ANR4116I Audit command: Policy domain domain
name is referenced, but not formally
defined - a policy domain with default ANR4120I Audit command: Management class class
attributes will be defined with this name in policy set set name, domain
name. domain name is referenced, but not
formally defined - the management class
will be created.
reference to the specified policy domain, but the
domain is not formally defined in the server database. Explanation: A database audit process finds a
Because FIX=YES has been specified, a new policy reference to the specified management class, but the
domain with this name will be defined by the audit class is not formally defined in the server database.
processor. Because FIX=YES has been specified for the audit
command, the audit process defines a management
class in the server with this name.
User Response: After the audit command has
completed, you can view the attributes for this policy
domain using the QUERY DOMAIN command, and User Response: After the audit command has
update attributes with the UPDATE DOMAIN completed, you can view the attributes for this
command, if desired. management class by using the QUERY MGMTCLASS

command, and update attributes with the UPDATE
ANR4126E Audit command: Policy global attributes
MGMTCLASS command, if desired.
cannot be found.
Explanation: A database audit process is not able to
ANR4122E Audit command: The instance count for
locate the global attributes for policy information in the
management class class name does not
server database.
agree with the actual management class
data (number of instances instances). System Action: Audit processing continues.
Explanation: A database audit process finds a User Response: Reissue the audit command and
reference count for the specified management class that specify FIX=YES so that the error can be corrected.
did not match the actual number of instances for this
class.
ANR4127I Audit command: Policy global attributes
System Action: Audit processing continues. cannot be found - attributes will
recreated.
specify FIX=YES so that the error can be corrected. Explanation: A database audit process is not able to
locate the global attributes for policy information in the
server database. Because FIX=YES has been specified
ANR4123I Audit command: The instance count for
for the audit command, the attributes will be
management class class name does not
regenerated.
agree with the actual management class
data (number of instances instances) - the System Action: Audit processing continues.
number will be corrected.
reference count for the specified management class that
ANR4128E Audit command: Policy global high-water
does not match the actual number of instances for this
marks do not match the identifiers in
class. The audit process corrects the count because
use.
FIX=YES has been specified for the audit command.
Explanation: A database audit process finds the
attributes used to track policy identifiers are incorrect.
ANR4124E Audit command: The instance count for
copy group copy group name does not
agree with the actual copy group data
(number of instances instances). ANR4129E Audit command: Policy global high-water
use - they will be corrected.
reference count for the specified copy group that does
not match the actual number of instances for this copy Explanation: A database audit process finds the
group. attributes used to track policy identifiers are incorrect.
Because FIX=YES has been specified for the audit
command, the attributes will be corrected.
ANR4125I Audit command: The instance count for
copy group copy group name does not ANR4130W Audit Volume updating object
agree with the actual copy group data information for volume volume name:
(number of instances instances) - the Node node name, Type file type, File space
number will be corrected. filespace name, fsId filespace id , File Name
file name.
reference count for the specified copy group that does Explanation: As the result of an AUDIT VOLUME
not match the actual number of instances for this copy command that specified FIX=YES for the volume
group. The audit process corrects the count because shown, object information for the specified file will be
FIX=YES has been specified for the audit command. updated.
System Action: Audit processing continues. System Action: The object information is updated.

dirty tape heads, correct the hardware problem and
ANR4131W Audit Volume found incorrect object
reissue the AUDIT VOLUME FIX=NO command for
information for volume volume name:
this volume. To remove damaged file references and
Node node name, Type file type, File space
update the object information, issue the AUDIT
filespace name, fsId filespace id, File name
VOLUME command and specify FIX=YES.
file name.
ANR4135I Audit command: Auditing central
command that specified FIX=NO for the volume
scheduler definitions.
shown, object information for the specified file is found
to be in error. Explanation: This message is displayed during a
database audit and indicates that the server scheduling
information is examined by the database audit process.
ANR4132I Audit volume process ended for volume
volume name; file count files inspected, file
count damaged files deleted, file count ANR4136I Audit command: Auditing server
damaged files marked as damaged, file inventory.
count objects updated.
Explanation: The AUDIT VOLUME command database audit and indicates that server information
specifying FIX=YES for the volume shown has ended. about client file spaces is currently being examined by
The number of files audited, the number of inconsistent the database audit process.
files deleted or marked as damaged, and the number of
updated objects are displayed. The number of files System Action: Audit processing continues.
marked as damaged includes all files belonging to User Response: None.
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 ANR4137I Audit command: Auditing inventory file
are known to exist in COPY storage pools. spaces.
System Action: None. Explanation: This message is displayed during a

database audit and indicates that server information
User Response: To recover files that have been about client file spaces is currently being examined by
marked as damaged on the volume, use the RESTORE the database audit process.
STGPOOL or RESTORE volume command.
ANR4133I Audit volume process ended for volume User Response: None.
volume name; file count files inspected, file
count damaged files found and marked ANR4138I Audit command: Auditing inventory
as damaged, file count objects need backup objects.
updating.
Explanation: The AUDIT VOLUME command database audit and indicates that server information
specifying FIX=NO for the volume shown has ended. about client backup objects is currently being examined
The number of files audited, the number of inconsistent by the database audit process.
files found, and the number of files with incorrect
object information are displayed. The number of files System Action: Audit processing continues.
marked damaged includes all files belonging to User Response: None.
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 ANR4139I Audit command: Auditing inventory
STGPOOL or RESTORE VOLUME command if copies archive objects.
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
about client archive objects is currently being examined
the audit volume process cannot access the files due to
by the database audit process.
hardware problems (for example, dirty tape heads).
User Response: If you suspect that files were
inaccessible because of hardware problems such as

ANR4140I Audit command: Database audit process ANR4145E Audit command: One or more central
started. scheduler attributes are incorrect.
Explanation: This message is displayed during a Explanation: A database audit process finds that the
database audit and indicates that the audit process has global attributes used for server scheduling activities
started. are incorrect.
specify FIX=YES so that the administrative global
ANR4141I Audit command: Database audit process
completed.
ANR4146I Audit command: One or more central
scheduler global attribute(s) are
database audit and indicates that the database audit
incorrect - default values will be set.
has successfully completed.
System Action: Audit processing ends.
global attributes used for server scheduling activities
User Response: None. are incorrect. Because FIX=YES has been specified on
the AUDIT command, default attribute values will be
used to correct the scheduling global attributes.
ANR4142I Audit command: Database audit process
terminated in error. System Action: Audit processing continues.
Explanation: This message is displayed during a User Response: When the audit completes, you can
database audit and indicates that the audit process use the QUERY STATUS command to examine the
ended prematurely due to an internal server database values set for the administrative global attributes, and
error. use the appropriate SET command to change the
attributes, if desired.
System Action: Audit processing ends.
User Response: Examine the messages issued prior to ANR4147E Audit command: Policy domain domain
this one to see if the error can be corrected. If the name referenced by schedule schedule
situation cannot be resolved, contact your service name does not exist.
representative.
schedule that references a policy domain that is not
ANR4143E Audit command: Central scheduler global defined in the server database.
attributes cannot be found.
Explanation: A database audit process cannot locate
the global attributes for scheduling information in the User Response: Reissue the audit command and
server database. specify FIX=YES so that the administrative global
User Response: Reissue the audit command and ANR4148I Audit command: Policy domain domain
specify FIX=YES so that the error can be corrected. name referenced by schedule schedule
name does not exist - the schedule will
ANR4144I Audit command: Central scheduler global be deleted.
attributes cannot be found - attributes Explanation: A database audit process finds a
will be recreated. schedule that references a policy domain that is not
Explanation: A database audit process cannot locate defined in the server database. Because FIX=YES has
the global attributes for scheduler information in the been specified for the audit command, the specified
server database. Because FIX=YES has been specified schedule will be deleted from the server database.
for the audit command, the attributes will be System Action: Audit processing continues.
regenerated.

ANR4149E Audit command: One or more attributes ANR4153E Audit command: Schedule schedule name in
for schedule schedule name in policy policy domain domain name references a
domain domain name are incorrect. client node that does not exist.
Explanation: A database audit process finds one or Explanation: A database audit process finds a
more invalid attributes for the specified schedule. schedule that references a client node that is not
defined in the server database.
specify FIX=YES so that the administrative global User Response: Reissue the audit command and
attributes can be corrected. specify FIX=YES so that the administrative global
ANR4150I Audit command: One or more attributes
for schedule schedule name in policy ANR4154I Audit command: Schedule schedule name in
domain domain name are incorrect - policy domain domain name references a
default values will be set. client node that does not exist - the
node reference will be deleted.
Explanation: A database audit process finds one or
more invalid attributes for the specified schedule. Explanation: A database audit process finds a
Because FIX=YES has been specified for the audit schedule that references a client node that is not
command the invalid attributes will be set to default defined in the server database. Because FIX=YES has
values. been specified for the audit command, the reference
will be removed from the server database.
use the QUERY SCHEDULE command to examine the User Response: None.
values set for the schedule, and use the UPDATE
SCHEDULE command to change any attributes desired.
ANR4155E Audit command: Invalid administrator
update information encountered for a
ANR4151E Audit command: Schedule schedule name in schedule assignment.
policy domain domain name not found,
but is referenced by a client node.
last updated information for a schedule-node
Explanation: A database audit process finds a assignment.
schedule reference from a client node for a schedule
that is not defined in the server database.
specify FIX=YES so that the administrative global
ANR4156I Audit command: Invalid administrator
update information encountered for a
schedule assignment - information will
ANR4152I Audit command: Schedule schedule name in be corrected.
policy domain domain name not found,
but is referenced by a client node - the
last updated information for a schedule-node
schedule association will be deleted.
assignment. Because FIX=YES has been specified for
Explanation: A database audit process finds a the command, the information is corrected.
schedule reference from a client node for a schedule
that is not defined in the server database. Because
FIX=YES has been specified for the audit command, the User Response: None.
schedule association will be deleted from the server
database.
ANR4157E Audit command: Scheduling callback
System Action: Audit processing continues. address is registered for a client node
that does not exist.
server-prompted-scheduling callback address for a node
that does not exist.

User Response: Reissue the audit command and User Response: Reissue the audit command and
specify FIX=YES so that the error can be corrected. specify FIX=YES so that the error can be corrected.
ANR4158I Audit command: Scheduling callback ANR4163I Audit command: Invalid object ID
address is registered for a client node high-water mark encountered for
that does not exist - callback inventory global attributes - the value
information will be deleted. will be corrected.
Explanation: A database audit process finds a Explanation: A database audit process finds that the
server-prompted-scheduling callback address for a node object ID high-water mark for the inventory global
that does not exist. Because FIX=YES has been specified attributes is invalid. Because FIX=YES has been
for the command, the callback information will be specified for the command, the object ID high-water
deleted from the server database. mark is determined by the current inventory and set
accordingly.
ANR4159I Audit command: An inventory
authorization rule specifies an invalid ANR4164I Audit command: Invalid object ID
node (node ID) or file space (filespace ID) high-water mark encountered for
- the rule will be deleted. inventory global attributes.
Explanation: A database audit process finds that Explanation: A database audit process finds that the
either a node ID or file space ID is invalid for an object ID high-water mark for the inventory global
authorization rule. Since FIX=YES has been specified, attributes is invalid.
the invalid authorization rule will be deleted.
ANR4160I Audit command: An inventory ANR4165I Audit command: An inventory node

authorization rule specifies an invalid assignment entry was not found for
node (node ID) or file space (filespace ID). node node ID - an entry will be created.
Explanation: A database audit process finds that Explanation: A database audit process cannot find the
either a node ID or file space ID is invalid for an node assignment entry corresponding to the specified
authorization rule. node. Since FIX=YES has been specified for the
command, the required inventory entry will be created
using default values.
ANR4161I Audit command: Inventory global
attributes could not be found - they will ANR4166I Audit command: An inventory node
be created. assignment entry was not found for
node node ID.
Explanation: A database audit process cannot find the
inventory global attributes. Because FIX=YES has been Explanation: A database audit process cannot find the
specified for the command, the information is corrected node assignment entry corresponding to the specified
by the creation of the global attributes. node.
ANR4162I Audit command: Inventory global
attributes could not be found.
inventory global attributes.

ANR4167I Audit command: The file space
high-water mark for node node ID is
incorrect - the value will be corrected. ANR4172I Audit command: Primary backup entry for
an expiring object (object.ID) cannot be
Explanation: A database audit process finds that a file
found.
space high-water mark is incorrect for the specified
node ID. Since FIX=YES has been specified for the Explanation: A database audit process cannot find the
command, the information is corrected. primary backup entry for the specified expiring object.
high-water mark for node node ID is ANR4173I Audit command: Primary archive entry for
incorrect. an expiring object (object.ID) cannot be
found - the expiring object entry will be
Explanation: A database audit process finds that a file
deleted.
space high-water mark is incorrect for the specified
node ID. Explanation: A database audit process cannot find the
primary archive entry for the specified expiring object.
User Response: Reissue the audit command and the information is corrected by deleting the expiring
specify FIX=YES so that the error can be corrected. object entry.
incorrect - the value will be corrected.
ANR4174I Audit command: Primary archive entry for
Explanation: A database audit process finds that an
an expiring object (object.ID) cannot be
authorization rule high-water mark is incorrect for the
found.
specified node ID. Since FIX=YES has been specified for
the command, the information is corrected. Explanation: A database audit process cannot find the
primary archive entry for the specified expiring object.
ANR4170I Audit command: The authorization rule
incorrect. ANR4175I Audit command: Invalid copy type
encountered for an expiring objects
entry (object.ID) - the expiring object
authorization rule high-water mark is incorrect for the
entry will be deleted.
specified node ID.
copy type for the specified expiring object is invalid.
User Response: Reissue the audit command and Because FIX=YES has been specified for the command,
specify FIX=YES so that the error can be corrected. the information is corrected by deleting the expiring
object entry. The entry will be recreated later if it is
necessary.
ANR4171I Audit command: Primary backup entry for
an expiring object (object.ID) cannot be System Action: Audit processing continues.
found - the expiring object entry will be
deleted.
ANR4176I Audit command: Invalid copy type
primary backup entry for the specified expiring object.
encountered for an expiring objects
entry (object.ID).
the information is corrected by deleting the expiring
object entry. Explanation: A database audit process finds that the
copy type for the specified expiring object is invalid.

ANR4182I Audit command: Invalid copy type
encountered for object object.ID - object
found as an archive object - correcting
ANR4177I Audit command: Primary backup entry for the invalid copy type
an object (object.ID) cannot be found -
invalid copy type for the specified object ID but finds a
Explanation: A database audit process cannot find the corresponding archive object for the entry. Because
specified primary backup object. Because FIX=YES has FIX=YES has been specified for the command, the
been specified for the command, the entry is deleted. invalid copy type is corrected.
ANR4178I Audit command: Primary backup entry for ANR4183I Audit command: Invalid copy type
an object (object.ID) cannot be found. encountered for object object.ID -
primary archive entry created for object
Explanation: A database audit process cannot find the using default values.
specified primary backup object.
System Action: Audit processing continues. invalid copy type for the specified object ID and is
User Response: Reissue the audit command and unable to find corresponding primary backup or
specify FIX=YES so that the error can be corrected. primary archive objects. Because FIX=YES has been
specified for the command, a primary archive entry is
created using default values.
an object (object.ID) cannot be found - System Action: Audit processing continues.
entry will be deleted. User Response: None.
specified primary archive object. Because FIX=YES has ANR4184I Audit command: Invalid copy type
been specified for the command, the entry is deleted. encountered for object object.ID.
System Action: Audit processing continues. Explanation: A database audit process encounters an
User Response: None. invalid copy type for the specified object ID and is
unable to find corresponding primary backup or
primary archive objects.
an object (object.ID) cannot be found. System Action: Audit processing continues.
Explanation: A database audit process cannot find the User Response: Reissue the audit command and
specified primary archive object. specify FIX=YES so that the error can be corrected.

ANR4185I Audit command: Object entry for backup
User Response: Reissue the audit command and object object.ID not found - entry will be
specify FIX=YES so that the error can be corrected. created.
ANR4181I Audit command: Invalid copy type object entry for the specified backup object. Because
encountered for object object.ID - object FIX=YES has been specified for the command, an object
found as a backup object - correcting entry is created using default values.
the invalid copy type
invalid copy type for the specified object ID but finds a User Response: None.
corresponding backup object for the entry. Because
FIX=YES has been specified for the command, the ANR4186I Audit command: Object entry for backup
invalid copy type is corrected. object object.ID not found.
System Action: Audit processing continues. Explanation: A database audit process cannot find an
User Response: None. object entry for the specified backup object.

User Response: Reissue the audit command and 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 ANR4192I Audit command: Object entry for archive
be updated. object object.ID not found.
Explanation: A database audit process determines that Explanation: A database audit process cannot find an
the object fields for the specified object ID do not object entry for the specified archive object.
match the fields for the corresponding primary backup
object. Because FIX=YES has specified for the System Action: Audit processing continues.
command, the incorrect object fields will be corrected. User Response: Reissue the audit command and
System Action: Audit processing continues. specify FIX=YES so that the error can be corrected.

for object object.ID do not match the
ANR4188I Audit command: Inventory object fields primary archive entry - the object will
for object object.ID do not match the be updated.
primary backup entry.
Explanation: A database audit process determines that
Explanation: A database audit process determines that the object fields for the specified object ID do not
the object fields for the specified object ID do not match the fields for the corresponding primary archive
match the fields for the corresponding primary backup object. Because FIX=YES has been specified for the
object. command, the incorrect object fields will be corrected.
User Response: Reissue the audit command and User Response: None.

ANR4189I Audit command: Expiring entry for for object object.ID do not match the
inactive backup object object.ID not primary archive entry.
found - the entry will be created.
Explanation: A database audit process cannot find an the object fields for the specified object ID do not
expiring entry for the specified inactive backup entry. match the fields for the corresponding primary archive
Because FIX=YES has been specified for the command, object.
an expiring entry will be created.
ANR4190I Audit command: Expiring entry for ANR4195I Audit command: Expiring entry for
inactive backup object object.ID not archive object object.ID not found - the
found. entry will be created.
Explanation: A database audit process cannot find an Explanation: A database audit process cannot find an
expiring entry for the specified inactive backup entry. expiring entry for the specified archive object. Because
FIX=YES has been specified for the command, an
expiring entry will be created.
ANR4191I Audit command: Object entry for archive
object object.ID not found - entry will be ANR4196I Audit command: Expiring entry for
created. archive object object.ID not found.
Explanation: A database audit process cannot find an Explanation: A database audit process cannot find an
object entry for the specified archive object. Because expiring entry for the specified archive object.
FIX=YES has been specified for the command, the

ANR4197I Audit command: File space entry filespace ANR4202I Audit command: The base date for
ID not found for node node ID. expiration processing of entry object.ID is
not valid - the entry will be deleted.
Explanation: A database audit process cannot find a
file space entry for the specified node. Explanation: A database audit process determines that
the specified expiring object has a date that is not valid.
User Response: Reissue the audit command and the expiring object entry is deleted.
ANR4198I Audit command: File space entry filespace
ID not found for node node name - an
entry will be created. ANR4203I Audit command: The base date for
expiration processing of object object.ID
is not valid.
file space entry for the specified node. Because
FIX=YES has been specified for the command, a file Explanation: A database audit process determines that
space entry has been created. the specified expiring object has a date value that is not
valid.
ANR4199I Audit command: File space entry filespace
ID not found for node node name -
unable to create an entry. ANR4204I Audit command: One or more date values
for a backup entry object.ID is not valid.
file space entry for the specified node. Because Explanation: A database audit process determines that
FIX=YES has been specified for the command, the audit one or more of the date values is improperly formatted
process has attempted to create a file space entry but is or contains incorrect information for the specified
not successful. backup object.
User Response: Contact your system administrator. User Response: Contact your system administrator.
ANR4200I Audit command: Expiring entry node ID ANR4205I Audit command: The insertion date value
and file space filespace ID does not match for archive entry object.ID is not valid.
the object entry for object ID object.ID -
the entry will be deleted.
the insertion date for the specified archive object is
Explanation: A database audit process determines that improperly formatted or contains incorrect information.
the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
Because FIX=YES has been specified for the command, User Response: Contact your system administrator.
the expiring object entry is deleted.
System Action: Audit processing continues. ANR4206I Audit command: Object entry for expiring
object object.ID not found - expiring
object entry will be deleted.
ANR4201I Audit command: Expiring entry node ID
object entry corresponding to the specified expiring
and file space filespace ID does not match
object. Because FIX=YES has been specified for the
the object entry for object ID object.ID.
command, the expiring object entry for the specified
Explanation: A database audit process determines that object ID is deleted.
the specified expiring object entry does not match the
corresponding object entry for the specified object ID.

ANR4207I Audit command: Object entry for expiring ANR4212I Audit command: An object entry for
object object.ID not found. library library name and drive drive name
in the physical volume repository is
invalid - the entry will be deleted.
object entry corresponding to the specified expiring
object. Explanation: A database audit process finds that a
drive entry is missing a corresponding library entry.
User Response: Reissue the audit command and the invalid drive entry is deleted.
ANR4208I Audit command: An inventory node
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
Explanation: A database audit process finds that a
physical volume repository is invalid.
node assignment entry for the specified node ID is not
valid. Since FIX=YES has been specified for the Explanation: A database audit process finds that a
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 Audit command: An inventory node
assignment entry was not found for
node node ID. ANR4214I Audit command: A drive model for
library library name and drive drive name
in the physical volume repository is
node assignment entry for the specified node ID is not
invalid.
valid.
drive model for the specified library and drive is
User Response: Reissue the audit command and invalid.
User Response: Contact the system administrator so
ANR4210I Audit command: Auditing physical
that appropriate action may be taken.
volume repository definitions.
ANR4215I Audit command: An object entry for
database audit and indicates that the physical volume
library library name and volume volume
repository definitions are being examined by the
name in the physical volume repository
is invalid.
User Response: None. library inventory entry is missing a corresponding
library entry.
ANR4211I Audit command: Drive entry library name System Action: Audit processing continues.
for library drive name in the physical
volume repository is invalid.
drive entry is missing a corresponding library entry.
ANR4216I Audit command: An object entry for
System Action: Audit processing continues. library library name and volume volume
name in the physical volume repository
User Response: Reissue the audit command and 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 information is corrected by changing the library type to
deleted. the default type.
ANR4217I Audit command: The volume status for ANR4221I Audit command: An error (error code) was
library library name and volume volume found with archive description for node
name in the physical volume repository (node identifier), description (description),
is invalid. objects (old object count,new object count),
count (old directory count,new directory
count) - entry will be deleted or updated.
volume status for the specified library and volume is
set to scratch. This is incorrect because storage agent Explanation: A database audit process has found an
has a volume name for the library and volume error with the specified archive description. Because
indicating that it should have a volume status of FIX=YES has been specified for the command, the entry
private. is deleted or updated.
User Response: Reissue the audit command and User Response: None.
ANR4222I Audit command: An error (error code) was
ANR4218I Audit command: The volume status for found with archive description for node
library library name and volume volume (node identifier), description (description),
name in the physical volume repository objects (old object count,new object count),
is invalid - the volume status will be count (old directory count,new directory
changed to private. count).
Explanation: A database audit process finds that the Explanation: A database audit process has found an
volume status for the specified library and volume is error with the specified archive description.
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. User Response: Reissue the audit command and
Because FIX=YES has been specified for the command, specify FIX=YES so that the error can be corrected.
the incorrect volume status is set to private.
System Action: Audit processing continues. ANR4223I Audit command: An error (error code) was
found with converted archive object for
node (node identifier), description
(description identifier), object (object.ID),
ANR4219I Audit command: A library type specified filespace (filespace identifier) - entry will
for library library name in the physical be deleted.
volume repository is invalid.
Explanation: A database audit process has found an
Explanation: A database audit process finds that the error with the specified converted archive object.
library type for the specified library is invalid. Because FIX=YES has been specified for the command,
the entry is deleted.
specify FIX=YES so that the error can be corrected. User Response: None.
ANR4220I Audit command: A library type specified ANR4224I Audit command: An error (error code) was
for library library name in the physical found with converted archive object for
volume repository is invalid - the node (node identifier), description
library type has been changed to the (description identifier), object (object.ID),
default of library type default. filespace (filespace identifier).
Explanation: A database audit process finds that the Explanation: A database audit process has found an
library type for the specified library is invalid. Because error with the specified converted archive object.
FIX=YES has been specified for the command, the

User Response: Reissue the audit command and FIX=YES has been specified for the audit command, the
specify FIX=YES so that the error can be corrected. error will be corrected.
ANR4225I Audit command: table entry for archive
object (object.ID), node (node identifier),
description (description), filespace
(filespace identifier) not found - the entry ANR4230I Audit command: Auditing data storage
will be created. definitions.
Explanation: A database audit process cannot find a Explanation: This message is displayed during a
converted table table entry for the specified archive database audit and indicates that the data storage
object. Because FIX=YES has been specified for the definitions are being examined by the database audit
command, an entry will be created. process.
ANR4226I Audit command: table entry for archive ANR4231E Audit command: Invalid device class
object (object.ID), node (node identifier), strategy strategy for device class device
description (description), filespace class name.
(filespace identifier) not found.
Explanation: A database audit process finds a device
Explanation: A database audit process cannot find a class with an invalid access strategy.
converted table table entry for the specified archive
object. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: Reissue the audit command with
FIX=YES so that the access strategy can be corrected.
ANR4232E Audit command: Invalid device class
strategy strategy for device class device
ANR4227E Audit command: Inconsistent information class name - information will be
detected for file aggregate (Aggregate.ID). corrected.
Explanation: A database audit process finds Explanation: A database audit process finds a device
inconsistent information for a file aggregate. This class with an invalid access strategy. Because FIX=YES
problem cannot be corrected by the audit process, but has been specified for the audit command, the access
the file data is not deleted. strategy will be corrected for this device class.
User Response: Contact your service representative. User Response: None.
ANR4228E Audit command: Missing or incorrect ANR4233E Audit command: Pool ID information is
information detected for file aggregate missing or incorrect for storage pool
(Aggregate.ID). storage pool name.
Explanation: A database audit process detects missing Explanation: A database audit process finds a storage
or incorrect information for a file aggregate. This pool whose pool ID information is missing or incorrect.
information can be corrected.
User Response: Reissue the audit command and FIX=YES so that the access strategy can be corrected.
ANR4234E Audit command: Pool ID information is

ANR4229E Audit command: Missing or incorrect missing or incorrect for storage pool
information detected for file aggregate storage pool name - information will be
(Aggregate.ID) - It will be corrected. created or corrected.
Explanation: A database audit process detects missing Explanation: A database audit process finds a storage
or incorrect information for a file aggregate. Because pool whose pool ID information is missing or incorrect.

command, the pool ID information will be created or
ANR4239E Audit command: Storage pool storage pool
corrected for this storage pool.
name specifies an undefined pool ID for
System Action: Audit processing continues. its next storage pool - reference will be
deleted.
Explanation: The specified storage pool references an
invalid pool ID as its next storage pool. Because
ANR4235E Audit command: Device class ID FIX=YES has been specified for the command, the
referenced by storage pool storage pool reference is deleted. The specified storage pool will not
name is not defined - data in this pool have a next pool.
may not be available.
Explanation: A database audit process finds a storage
pool which references a device class ID which is not User Response: After the audit command completes,
defined. use the UPDATE STGPOOL command to assign a next
storage pool, if desired.
User Response: Contact your service representative. ANR4240E Audit command: An invalid attribute was
encountered for storage pool storage pool
ANR4236E Audit command: An invalid access name.
strategy was encountered for storage Explanation: A database audit process encounters an
pool storage pool name. invalid attribute for the specified storage pool.
invalid device access strategy for the specified storage
pool. User Response: Reissue the audit command with
FIX=YES so that the attribute can be corrected.
User Response: Reissue the audit command with ANR4241E Audit command: An invalid attribute was
FIX=YES so that the attribute can be corrected. encountered for storage pool storage pool
name - the attribute will be assigned its
ANR4237E Audit command: An invalid access default value.
strategy was encountered for storage Explanation: A database audit process encounters an
pool storage pool name - the strategy will invalid attribute for the specified storage pool. Because
be corrected. FIX=YES has been specified for the command, the
Explanation: A database audit process encounters an storage pool will be corrected using the default value
invalid device access strategy for the specified storage for the attribute.
pool. Because FIX=YES has been specified for the System Action: Audit processing continues.
command, the storage pool access strategy will be
corrected. User Response: After the audit command completes,
examine the storage pool using the QUERY STGPOOL
System Action: Audit processing continues. command, and correct attributes with the UPDATE
User Response: After the audit command completes, STGPOOL command, if desired.
examine the storage pool using the QUERY STGPOOL
command, and verify that the correct information is ANR4242E Audit command: Invalid administrator
displayed for this storage pool. update information encountered for
ANR4238E Audit command: Storage pool storage pool Explanation: A database audit process finds incorrect
name specifies an undefined pool ID for information pertaining to the last update for the
its next storage pool. specified storage pool.
Explanation: The specified storage pool references an System Action: Audit processing continues.
invalid pool ID as its next storage pool.
System Action: Audit processing continues. specify FIX=YES so that the error can be corrected.
command to update the next pool. Alternatively, if the
audit command is reissued with FIX=YES, the reference
to the next pool will be deleted.

ANR4243E Audit command: Invalid administrator ANR4247E Audit command: Missing information for
update information encountered for volume volume name cannot be created.
storage pool storage pool name - Delete the volume after optionally
information will be corrected. moving any files from the volume.
Explanation: A database audit process finds incorrect Explanation: A database audit process encounters
information pertaining to the last update for the missing database information for the specified volume.
specified storage pool. Because FIX=YES has been Since FIX=YES has been specified for the audit
specified for the command, the information is command, an attempt is made to create the missing
corrected. 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
ANR4244E Audit command: Storage pool ID to this volume. Audit processing continues.
referenced by volume volume name is not
User Response: After audit processing completes, an
defined - data on this volume may not
administrator should take the following actions to
be available.
eliminate the volume
Explanation: A database audit process finds a data v (Optional) Use the UPDATE VOLUME command to
storage volume which references a storage pool ID that set the access mode for the volume to READWRITE.
is not defined. It may then be possible to use the MOVE DATA
command to move files from the volume so that
System Action: Audit processing continues. these files can be accessed by the server.
User Response: You can attempt to move data on the v (Required) Use the DELETE VOLUME command to
specified volume to other volumes using the MOVE delete the volume from the database.
DATA command; then delete the specified volume and
redefine it. If this does not work, contact your service ANR4248E Audit command: Missing or incorrect
representative. information for storage volume volume
name.
ANR4245E Audit command: An invalid access Explanation: A database audit process finds a data
strategy was encountered for volume storage volume for which information is missing or
volume name. incorrect.
invalid device access strategy for the specified volume.
System Action: Audit processing continues. FIX=YES so that the information can be created or
User Response: Reissue the audit command with corrected.
FIX=YES so that the strategy can be corrected.
ANR4249E Audit command: Missing or incorrect
ANR4246E Audit command: An invalid access information for storage volume volume
strategy was encountered for volume name - information will be created or
volume name - the strategy will be corrected.
corrected. Explanation: A database audit process finds a data
Explanation: A database audit process encounters an storage volume for which information is missing or
invalid device access strategy for the specified volume. incorrect. Since FIX=YES has been specified for the
Because FIX=YES has been specified for the command, audit command, the information will be created or
the access strategy will be corrected for this volume. corrected.
ANR4250E Audit command: Extraneous reference

found.
reference to a nonexistent entity such as a storage pool
or volume.

ANR4255E Audit command: Data storage high-water
User Response: Reissue the audit command with marks do not match the identifiers in
FIX=YES so that the non-existant entity is recreated, if use - they will be corrected.
possible. If recreation is not possible, the extraneous
reference is deleted.
information used to track data storage identifiers is
incorrect. Because FIX=YES has been specified for the
ANR4251E Audit command: Extraneous reference audit command, the error will be corrected.
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 ANR4256I Audit command: Auditing data storage
audit command, the nonexistant entity will be definitions for disk volumes.
recreated, if possible. If recreation is not possible, the
extraneous information will be deleted.
database audit and indicates that the database
System Action: Audit processing continues. information relating to data storage disk volumes is
being examined by the database audit process.
ANR4252E Audit command: Data storage global User Response: None.
attributes cannot be found.
Explanation: A database audit process is not able to ANR4257E Audit command: A correctable
locate the global attributes for data storage in the data-integrity error was detected on
server database. volume volume name.
System Action: Audit processing continues. Explanation: A database audit process finds a
data-integrity error for a file stored on the specified
volume. This error is correctable.
ANR4253E Audit command: Data storage global User Response: Reissue the audit command and
attributes cannot be found - attributes specify FIX=YES so that the error can be corrected.
will be recreated.
Explanation: A database audit process is not able to ANR4258E Audit command: A data-integrity error
locate the global attributes for data storage in the was detected on volume volume name -
server database. Because FIX=YES has been specified the error will be corrected.
for the audit command, the attributes will be
regenerated.
correctable data-integrity error for a file stored on the
System Action: Audit processing continues. specified volume. Because FIX=YES has been specified
for the audit command, the error will be corrected.
ANR4254E Audit command: Data storage high-water User Response: None.
use.
ANR4259E Audit command: Invalid data encountered
Explanation: A database audit process finds that the for a file in data storage - data can be
information used to track data storage identifiers is corrected.
incorrect.
Explanation: A database audit process finds invalid
System Action: Audit processing continues. data for a file in data storage. The error should be
correctable.
specify FIX=YES so that the error can be corrected. System Action: Audit processing continues.

ANR4260E Audit command: Invalid data encountered
for a file in data storage - the error will
be corrected. ANR4265I Audit command: Auditing disk file
information.
Explanation: A database audit process finds invalid
data for a file in data storage. Because FIX=YES has Explanation: This message is displayed during a
been specified for the audit command, the error will be database audit and indicates that information on files
corrected. stored on disk media is being examined by the
ANR4261E Audit command: Invalid access
information was encountered for ANR4266I Audit command: Auditing sequential file
volume volume name. information.
Explanation: A database audit process encounters Explanation: This message is displayed during a
invalid access information for the specified volume. database audit and indicates that information on files
stored on sequential media is being examined by the
User Response: After audit processing has completed,
use the UPDATE VOLUME command to set the access
information for this volume. Or reissue the audit User Response: None.
command with FIX=YES, which sets access to the
default value.
ANR4267E Audit command: A storage pool
containing file data cannot be located -
ANR4262E Audit command: Invalid access file data may not be accessible.
information was encountered for
volume volume name - the information Explanation: This message is displayed during a
will be corrected. database audit and indicates that the storage pool
containing a file’s data cannot be located or is not
Explanation: A database audit process encounters defined. This problem cannot be corrected by the audit
invalid access information for the specified volume. process, but the file data is not deleted.
the information will be corrected by setting the default System Action: Audit processing continues.
value. User Response: Contact your service representative.
User Response: After audit processing has completed, ANR4268E Audit command: A storage volume
use the UPDATE VOLUME command to set the access containing file data cannot be located -
information for this volume, if desired. file data may not be accessible.
ANR4263I Audit command: Auditing data storage database audit and indicates that the storage volume
definitions for sequential volumes. containing a file’s data cannot be located or is not
defined. This problem cannot be corrected by the audit
Explanation: This message is displayed during a process, and the file data is deleted.
database audit and indicates that the database
information relating to data storage sequential volumes System Action: Audit processing continues.
is being examined by the database audit process. User Response: Contact your service representative.
User Response: None. ANR4269E Audit command: Extraneous file data
reference found.
ANR4264I Audit command: Auditing file Explanation: A database audit process finds a
information. reference to a file that no longer exists.
Explanation: This message is displayed during a System Action: Audit processing continues.
database audit and indicates that information on stored User Response: Reissue the audit command with
files is being examined by the database audit process. FIX=YES so that the information can be deleted.

ANR4270E Audit command: Extraneous file data
reference found - information will be
deleted. ANR4275E Audit command: A data-integrity error
was detected - it will be corrected.
reference to a file that no longer exists. Because Explanation: A database audit process finds a
FIX=YES has been specified for the audit command, the data-integrity error for a stored file. Because FIX=YES
information will be deleted. has been specified for the audit command, the error
will be corrected.
occupancy information detected. ANR4276E Audit command: Invalid file storage
information detected - file data is not
Explanation: A database audit process detects missing
accessible.
or incorrect occupancy information for a data storage
pool or a data storage volume. Explanation: A database audit process finds invalid
file storage information for a stored file, and it cannot
be corrected.
FIX=YES so that the information can be created or
corrected. User Response: Issue the AUDIT VOLUME command
on all your volumes to correct the data-integrity error.
occupancy information detected - ANR4277E Audit command: Invalid file storage
information will be created or corrected. information detected.
Explanation: A database audit process detects missing Explanation: A database audit process finds invalid
or incorrect occupancy information for a data storage file storage information for a stored file. This
pool or a data storage volume. Because FIX=YES has information can be corrected.
been specified for the audit command, the information
will be created or corrected. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: Reissue the audit command and
ANR4278E Audit command: Invalid file storage

ANR4273E Audit command: A data-integrity error information detected - It will be
was detected on volume volume name - corrected.
Issue the AUDIT VOLUME command to
correct the error. Explanation: A database audit process finds invalid
file storage information for a stored file. Because
Explanation: A database audit process finds a FIX=YES has been specified for the audit command, the
data-integrity error for a file stored on the specified error will be corrected.
volume.
User Response: Issue the AUDIT VOLUME command
on the specified volume to correct the data-integrity
error. ANR4279E Audit command: Administrator
administrator number assigned to more
than just system authority class.
ANR4274E Audit command: A correctable
data-integrity error was detected. Explanation: A database audit process finds that an
administrator is assigned to other authority classes.
Explanation: A database audit process finds a Being assigned with 'SYSTEM' authority supersedes all
data-integrity error for a stored file. This error can be other classes and the other privilege class entries
corrected. should be deleted.

ANR4283E Audit command: Administrator
administrator number assigned as an
ANR4280I Audit command: Administrator unrestricted storage administrator is also
administrator number assigned to more assigned as a restricted administrator for
than just system authority class - the storage pool storage pool name.
other class entries will be deleted.
Explanation: A database audit process finds the
Explanation: A database audit process finds that an specified administrator is assigned as an unrestricted
administrator is assigned to other authority classes. storage administrator. The specified administrator is
Being assigned with 'SYSTEM' authority supersedes all also assigned as the restricted administrator for the
other classes and the other privilege class entries specified storage pool. The unrestricted storage
should be deleted. Because FIX=YES has been specified administration class supersedes any restricted storage
for the command, any authority class other than system class definitions for an administrator. The
will be deleted. administrator’s authority needs to be corrected.
ANR4281E Audit command: Administrator

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

ANR4292I Audit command: Invalid table active
column encountered for license global
attribute - the value will be corrected.
ANR4287E Audit command: Storage allocation error
detected for volume volume name - It will
active column license global attribute is invalid.
be corrected.
Explanation: A database audit process finds incorrect the active column is reset to a proper value.
block allocation information for the specified storage
volume; the error will be corrected.
ANR4293I Audit command: Invalid table active
column encountered for license global
ANR4288E Audit command: Multiple files allocated attributes.
the same disk storage block on volume
volume name.
active column license global attribute is invalid.
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 User Response: Reissue the audit command and
audit process. specify FIX=YES so that the error can be corrected.
ANR4294I Audit command: A license node
node node ID - an entry will be created.
ANR4289E Audit command: Multiple files allocated
the same disk storage block on volume
node assignment entry corresponding to the specified
volume name.
node. Since FIX=YES has been specified for the
Explanation: A database audit process finds multiple command, the required license entry will be created
files allocated the same disk storage block on the using default values.
specified volume; this error cannot be corrected by the
audit process.
ANR4295I Audit command: A license node
ANR4290I Audit command: License global attributes node node ID.
could not be found - they will be
created.
node assignment entry corresponding to the specified
Explanation: A database audit process cannot find the node.
license global attributes. Because FIX=YES has been
specified for the command, the information is corrected
by the creation of the global attributes. User Response: Reissue the audit command and
ANR4296I Audit command: An invalid license node
assignment entry was found for node
ANR4291I Audit command: License global attributes node ID - the entry will be deleted.
could not be found.
Explanation: A database audit process cannot find the license node assignment entry is invalid. Because
license global attributes. FIX=YES has been specified for the command, the node
entry is deleted.
specify FIX=YES so that the error can be corrected. User Response: None.

ANR4297I Audit command: An invalid license node
assignment entry was found for node
node ID. ANR4302I Audit command: Invalid last audit date
encountered for license global attribute.
license node assignment entry is invalid. Explanation: A database audit process finds that the
last audit date license global attribute is invalid.
specify FIX=YES so that the error can be corrected. User Response: Reissue the audit command and
ANR4298I Expiration thread already processing -
unable to begin another expiration ANR4303E Audit command: Inventory references for
process. object(Object.ID) deleted.
Explanation: The expiration thread is already Explanation: A database audit process deleted all
processing. The processing expiration thread is either inventory references for the specified object ID. This
an EXPIRE INVENTORY command or is the automatic process corrects a data-integrity error if FIX=YES was
background expiration process. In either case, another specified.
expiration process cannot be started until the current
expiration process completes or is canceled. System Action: Audit processing continues.
System Action: Current expiration process continues. User Response: None.
User Response: Use the QUERY PROCESS command

to determine the status of the current expiration ANR4304E Audit command: object name missing entry
process. for cluster cluster ID - cluster entries
deleted.
ANR4299I Audit command: Invalid audit interval Explanation: A database audit process is missing a
encountered for license global attribute - corresponding entry for the specified comparison object
the value will be set to the default. and cluster ID. This process indicates a data-integrity
error for the database cluster information. If FIX=YES
Explanation: A database audit process finds that the was specified, the invalid cluster information will be
audit interval license global attribute is invalid. Because deleted.
FIX=YES has been specified for the command, the audit
interval is reset to the default value. System Action: Audit processing continues.
System Action: Audit processing continues. User Response: None.

ANR4305E Audit command: object name missing entry
for cluster cluster ID.
ANR4300I Audit command: Invalid audit interval
encountered for license global Explanation: A database audit process is missing a
attributes. corresponding entry for the specified comparison object
and cluster ID. This indicates a data-integrity error for
Explanation: A database audit process finds that the the database cluster information.
audit interval license global attribute is invalid.
User Response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
ANR4306I AUDITDB: Processed number of entries
ANR4301I Audit command: Invalid last audit date database entries (cumulative).
encountered for license global attribute -
the value will be set to 0. Explanation: This message indicates the number of
database entries that have been processed during
Explanation: A database audit process finds that the database audit processing.
last audit date license global attribute is invalid.
Because FIX=YES has been specified for the command, System Action: Database audit processing continues.
the last audit date is set to 0. The next execution of User Response: None.
AUDIT LICENSES will set a new last audit date.

ANR4307I Audit command: Auditing inventory
external space-managed objects.
ANR4312I Audit command: Object entry for
space-managed object object.ID not
found.
about external space-managed client objects is currently
being examined by the database audit process. Explanation: A database audit process cannot find an
object entry for the specified backup object.
ANR4308I Audit command: External space-managed
entry for node node ID and file space
filespace ID is missing a corresponding ANR4313I Audit command: Space-managed object
space-managed object entry - the (object ID) for node node ID and file
external space-managed entry will be space filespace ID has one or more
deleted. incorrect fields - the values will be
corrected.
external space-managed entry is missing a Explanation: A database audit process determined
corresponding space-managed entry. Because FIX=YES that one or more field values for the specified
has been specified, the orphaned external space-managed object is not valid. Because FIX=YES
space-managed entry is deleted. was specified the values are corrected.
ANR4309I Audit command: External space-managed ANR4314I Audit command: Space-managed object
entry for node node ID and file space (object ID) for node node ID and file
filespace ID is missing a corresponding space filespace ID has one or more
space-managed object entry. incorrect fields.
Explanation: A database audit process finds that an Explanation: A database audit process determined
external space-managed entry is missing a that one or more field values for the specified
corresponding space-managed entry. space-managed object is not valid.
ANR4310I Audit command: Auditing inventory ANR4315I Audit command: Space-managed object
space-managed objects. (object ID) for node node ID and file
space filespace ID is missing the
corresponding external space managed
entry - the entry will be created.
about space-managed client objects is currently being
examined by the database audit process. Explanation: A database audit process determines that
the space-managed object entry is missing a
corresponding external space managed entry. Because
User Response: None. FIX=YES was specified, the missing entry will be
created.
ANR4311I Audit command: Object entry for System Action: Audit processing continues.
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.

ANR4316I Audit command: Space-managed object
(object ID) for node node ID and file
space filespace ID is missing the
corresponding external space managed ANR4321I Audit command: Invalid copy type
entry. encountered for object object.ID - object
found as an space-managed object -
correcting the invalid copy type
the space-managed object entry is missing a
corresponding external space-managed entry. Explanation: A database audit process encounters an
invalid copy type for the specified object ID, but finds
a corresponding space-managed object for the entry.
User Response: Reissue the audit command and Because FIX=YES has been specified for the command,
specify FIX=YES so that the error can be corrected. the invalid copy type is corrected.
object (object ID) for node node ID and
file space filespace ID has one or more
incorrect fields - the values will be ANR4322E Audit command: Management class class
corrected. name in policy set set name, domain
domain name does not have a valid space
Explanation: A database audit process determined
management technique defined.
that one or more field values for the specified external
space-managed object is not valid. Because FIX=YES Explanation: A database audit process finds a
was specified, the values will be corrected. management class that does not have a valid value
specified.
object (object ID) for node node ID and
file space filespace ID has one or more ANR4323E Audit command: Management class class
incorrect fields. name in policy set set name, domain
domain name does not have a valid space
Explanation: A database audit process determined
management technique defined - the
that one or more field values for the specified external
default value will be set.
space-managed object is not valid.
management class that does not have a valid value
User Response: Reissue the audit command and specified. Because FIX=YES was specified for the
specify FIX=YES so that the error can be corrected. AUDITDB operation, the default space management
technique value will be set for the management class
specified.
not found for object object.ID - object System Action: Audit processing continues.
User Response: Refer to the DEFINE MGMTCLASS
Explanation: A database audit process cannot find a command in the Administrator’s Reference for valid
space-managed object entry for the specified object. values.
Because FIX=YES was specified the object entry will be
deleted.
ANR4324E Audit command: Management class class
System Action: Audit processing continues. name in policy set set name, domain
domain name does not have a valid
AUTOMIGNONUSE value specified.
not found for object object.ID.
specified.
space-managed object entry for the specified object.

name in policy set set name, domain User Response: After the audit command completes,
domain name does not have a valid use the DEFINE STGPOOL command to define the
AUTOMIGNONUSE value defined - the missing storage pool or the UPDATE MGMTCLASS
default value will be set. command to update the management class to refer to
an existing storage pool.
specified. Because FIX=YES was specified for the ANR4329I Audit command: Inactive reference found
AUDITDB operation, the default AUTOMIGNONUSE for active backup entry (Object.ID) - the
value will be set for the management class specified. inactive reference will be deleted.
System Action: Audit processing continues. Explanation: A database audit process found that an
active backup entry for the specified object has a
corresponding inactive backup entry. Since FIX=YES
command in the Administrator’s Reference for valid
was specified for the command, the information is
values.
corrected by deleting the inactive backup object entry.
name in policy set set name, domain User Response: None.
domain name does not have a valid
MIGREQUIRESBKUP value specified.
ANR4330I Audit command: Inactive reference found
Explanation: A database audit process finds a for active backup entry (Object.ID).
specified. Explanation: A database audit process found that an
active backup entry for the specified object has a
System Action: Audit processing continues. corresponding inactive backup entry.
User Response: Reissue the audit command and System Action: Audit processing continues.

name in policy set set name, domain ANR4331E command process terminated, no
domain name does not have a valid matching device classes.
MIGREQUIRESBKUP value defined - Explanation: The server did not find any device class
the default value will be set. names matching the specifications entered in the
Explanation: A database audit process finds a RECONCILE VOLUMES command.
management class that does not have a valid value System Action: Server operation continues.
specified. Because FIX=YES was specified for the
AUDITDB operation, the default MIGREQUIRESBKUP User Response: Use the QUERY DEVCLASS
value will be set for the management class specified. command to determine which device classes are
defined on the server and reissue the RECONCILE
System Action: Audit processing continues. VOLUMES command.
command in the Administrator’s Reference for valid ANR4332W This command will compare all volumes
values. used by the specified device class(es)
with the actual data stored on the
ANR4328W Audit command: Storage pool storage pool associated server for those volumes and
name, specified as a space management will report any discrepancies; the data
destination for management class will be inaccessible to users until the
management class name, policy set set operation completes.
name, domain domain name, does not Explanation: During the execution of a RECONCILE
exist. VOLUMES command, any data a volume named
Explanation: A database audit process encounters a would be unavailable to users.
storage pool specified for the space management System Action: The administrator is asked whether to
destination of the specified management class that is continue.
not defined in the server database. If this management
class is used in an active policy set, then migration User Response: Enter 'Y' to reconcile the volumes or
operations will fail when attempting to put client data 'N' to stop the process.
in the destination.

ANR4333W This command will discard any ANR4337W command process terminated - process
references to volumes used by the canceled.
specified device class(es) that are
Explanation: During processing of a RECONCILE
missing from the associated server,
VOLUMES command, the process performing the
thereby rendering the data
reconcile was canceled.
unrecoverable; the valid volumes will
be inaccessible to users until the System Action: The RECONCILE VOLUMES
operation completes. command is ended.
Explanation: During the execution of a RECONCILE User Response: None.
VOLUMES command, any data on a volume being
reconciled would be unavailable to users. After the
command has ended, any inconsistent volumes found ANR4338W command process terminated - sufficient
will be discarded. recovery log space is not available.
System Action: The administrator is asked whether to Explanation: During processing of a RECONCILE
continue. VOLUMES command, the source server does not have
sufficient recovery log space to continue.
User Response: Enter 'Y' to reconcile the volumes or
'N' to stop the process. System Action: The RECONCILE VOLUMES
command is ended.
ANR4334I command (Repair) process started, User Response: If necessary, make more recovery log
process ID process ID. space available to the source server.
Explanation: As the result of a RECONCILE

VOLUMES command that specified FIX=YES, the ANR4339W command process terminated - sufficient
process whose ID is displayed has begun reconciling database space is not available.
the volumes associated with the given device class. Explanation: During processing of a RECONCILE
System Action: The volumes are reconciled and VOLUMES command, the source server does not have
invalid volumes are displayed. sufficient database space to continue.
User Response: None. System Action: The RECONCILE VOLUMES

command is ended.
ANR4335I command (Inspect Only) process started, User Response: If necessary, make more database
process ID process ID. space available to the source server.

VOLUMES command that specified FIX=NO, the ANR4340W command process terminated - thread
process whose ID is displayed has begun reconciling resource not available.
the volumes associated with the given device class. Explanation: During processing of a RECONCILE
System Action: The volumes are reconciled and VOLUMES command, the source server cannot start a
inconsistent volumes are displayed. thread for the reconcile process.
User Response: None. System Action: The RECONCILE VOLUMES

command is ended.
ANR4336W command process ended, process ID User Response: Reissue the RECONCILE VOLUMES
process ID. command. If the error persists, it may indicate a
shortage of source server memory.
Explanation: The RECONCILE VOLUMES command
for the specified device class has ended.
ANR4341W command process terminated - sufficient
System Action: None. memory is not available.
User Response: For complete details on the results of Explanation: During processing of a RECONCILE
the RECONCILE VOLUMES command, examine the VOLUMES command, the source server does not have
previous messages. enough memory available to complete the command.
System Action: The RECONCILE VOLUMES
command is ended.
User Response: If necessary make more memory
available to the source server.

volumes reconciled and the number of invalid volumes
ANR4342W command process terminated - lock
found are displayed.
conflict detected.
VOLUMES command, the source server cannot obtain a User Response: For complete details on the results of
required lock. the RECONCILE VOLUMES command for the shown
device class, examine the previous messages. If you
suspect that volumes were inaccessible because of
command is ended.
communications problems, correct the problems and
User Response: Reissue the RECONCILE VOLUMES retry the RECONCILE VOLUMES command. If the
command. errors are valid, reissue the reconcile volumes
command with FIX=YES so that the source server can
attempt to correct the information.
ANR4343W command process terminated - internal
server error detected.
ANR4352I Contacting Server server name
VOLUMES command, an internal server error occurs Explanation: This message is displayed in response to
on the source server. a QUERY PROCESS command, and indicates that a
reconciliation process is attempting to obtain volume
information from the shown server.
command is ended.
System Action: The reconciliation process continues.
ANR4344I command started for device class device
class (process ID process ID). ANR4353I Cancel in progress
Explanation: The RECONCILE VOLUMES process Explanation: This message is displayed in response to
whose ID is displayed has started reconciling volumes a QUERY PROCESS command, and indicates that a
associated with the given device class. reconciliation process has been canceled. The process
will end shortly.
System Action: The volumes are reconciled and
inconsistent volumes are displayed. System Action: The reconciliation process terminates
ANR4345I command completed for device class
device class; (process ID process ID); ANR4354W command: Source server not authorized
volume count volumes inspected, volume to reconcile target server server name.
count invalid volumes found, volume
count volumes deleted.
VOLUMES command, the source server was not
Explanation: The RECONCILE VOLUMES process permitted to reconcile volume on the shown target
whose ID is displayed has finished reconciling volumes server.
associated with the given device class. The number of
volumes reconciled and the number of invalid volumes
found or deleted are displayed. User Response: If the source server should have
permission to reconcile volumes on the shown target
server, issue the UPDATE SERVER command with
User Response: For complete details on the results of FORCESYNC=YES to cause the target server to accept
the RECONCILE VOLUMES command for the shown reconcile operations for the source server. Reissue the
device class, examine the previous messages. RECONCILE VOLUMES command.
ANR4346I command completed for device class ANR4355W command: Volume volume name not valid,
device class; (process ID process ID); source server missing corresponding
volume count volumes inspected, volume entry for target server.
count invalid volumes found.
Explanation: The RECONCILE VOLUMES process VOLUMES command, the volume shown was reported
whose ID is displayed has finished reconciling volumes by the target server and it has no matching volume on
associated with the given device class. The number of the source server.

User Response: The database on either the source or command to correct the situation. If the condition of
target server has been regressed by either a RESTORE the database on each server is acceptable and the
DATABASE operation or some system facility external RECONCILE VOLUMES command was issued with
to the server. Investigate the action that caused one or FIX=NO, reissue the RECONCILE VOLUMES
both of the databases to be regressed to there current command with FIX=Yes to have the volume deleted
condition. If a newer database images exist for that from the target server.
server, consider restoring the server to that point in
time. If the condition of the database on each server is
ANR4358W command: Volume volume name not valid,
acceptable and the RECONCILE VOLUMES command
the attributes of the volume on target
was issued with FIX=NO, reissue the RECONCILE
server do not match the attributes on the
VOLUMES command with FIX=Yes to have the volume
source server.
deleted from the target server.
VOLUMES command, the volume shown was found on
both the source and target server, but the attributes
target server missing corresponding
describing the volume does not match.
entry for source server.
VOLUMES command, the volume shown was found on User Response: The database on either the source or
the source server and it has no matching volume on the target server has been regressed by either a RESTORE
target server. 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
User Response: The database on either the source or condition. If a newer database image exist for that
target server has been regressed by either an RESTORE server, consider restoring the server to that point in
DATABASE operation or some system facility external time. If the condition of the database on each server is
to the server. Investigate the action that caused one or acceptable, additional actions will have to be taken
both of the databases to be regressed to there current because RECONCILE VOLUMES FIX=YES is unable to
condition. If a newer database images exist for that correct this situation. In the case of a volume in the
server, consider restoring the server to that point in VOLHISTORY, an IMPORT PREVIEW=YES or a
time. If the RECONCILE VOLUMES command was RESTORE DATABASE PREVIEW=YES will determine
issued with FIX=Yes and the volume is defined in a the integrity of the volume. If the volume is in error, a
storage pool, the access mode of the volume will DELETE VOLHISTORY will remove the volume from
changed to unavailable to prevent attempted mounts both the source and target servers. In the case of a
on the source server. If the condition of the database on volume in a storage pool, an AUDIT VOLUME
each server is acceptable, issue the DELETE VOLUME FIX=NO will determine the integrity of the volume. If
or DELETE VOLHISTORY command on the source errors are found, an AUDIT VOLUME FIX=YES may
server to remove the volume from the database. 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.
target server volume refers to device
class device class that does not exist on
the source server. ANR4359W command: Volume volume name not valid,
the size of the volume on target server
does not match the size on the source
server.
the target server and it is associated with the device
class shown. The source server has NO corresponding Explanation: As the result of a RECONCILE
device class. VOLUMES command, the volume shown was found on
both the source and target server, but the size of the
volume does not match.
User Response: The database on either the source or
target server has been regressed by either an RESTORE
DATABASE operation or some system facility external User Response: The database on either the source or
to the server. Investigate the action that caused one or target server has been regressed by either an RESTORE
both of the databases to be regressed to their current DATABASE operation or some system facility external
condition. If a newer database image exist for that to the server. Investigate the action that caused one or
server, consider restoring the server to that point in both of the databases to be regressed to there current
time. In the case of a volume in the VOLHISTORY, the condition. If a newer database image exist for that
device class may have been deleted from the source server, consider restoring the server to that point in
server. If possible, issue the DEFINE DEVCLASS time. If the condition of the database on each server is

acceptable, additional actions will have to be taken User Response: On the target server, an audit with
because RECONCILE VOLUMES FIX=YES is unable to FIX=NO of the volumes in the storage pool used by the
correct this situation. In the case of a volume in the source server will indicate what which volume on the
VOLHISTORY, an IMPORT PREVIEW=YES or a target server is damaged. This AUDIT VOLUME
RESTORE DATABASE PREVIEW=YES will determine command may be able to reset the damaged indicator
the integrity of the volume. If the volume is in error, a in the database if the damage was temporary due to
DELETE VOLHISTORY will remove the volume from hardware problems (for example, dirty tape heads). If
both the source and target servers. In the case of a the volume on the target server is in a primary storage
volume in a storage pool, an AUDIT VOLUME pool that has previously been backed up to a copy
FIX=NO will determine the integrity of the volume. If storage pool, attempt to correct the damage by using
errors are found, an AUDIT VOLUME FIX=YES may the RESTORE STGPOOL command. If attempts to
make some data on the volume accessible. Otherwise, correct the damage on the target server fail, an AUDIT
issue the DELETE VOLUME command on the source VOLUME command FIX=YES from the source server
server to remove the volume from both the source and will mark as damaged in the source server database
target servers. 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
the type of the volume on target server
storage pool, that copy may be accessed for future
does not match the type on the source
operations involving the file.
server.
ANR4362W command: Invalid volume volume name
deleted from server server name for
both the source and target server, but the type of the
device class device class.
volume does not match. For example, the volume on
the target server is defined in a storage pool, but the Explanation: As the result of a RECONCILE
target server indicates that volume was used for a VOLUMES command that specified FIX=YES, the
DATABASE BACKUP. volume shown whose information is displayed is
deleted from the target server.
System Action: The volume is deleted.
User Response: The database on either the source or
target server has been regressed by either an RESTORE User Response: None.
DATABASE operation or some system facility external
to the server. Investigate the action that caused one or
ANR4363W command: Volume volume name access
both of the databases to be regressed to there current
changed to access mode.
condition. If a newer database image exists for that
server, consider restoring the server to that point in Explanation: As the result of a RECONCILE
time. If the condition of the database on each server is VOLUMES command that specified FIX=YES, the
acceptable, additional actions will have to be taken access mode of the source volume has been changed to
because RECONCILE VOLUMES FIX=YES is unable to the value shown.
correct this situation. These actions may have to be
performed on one or both servers. Use the QUERY System Action: The volume’s access mode is changed.
VOLHISTORY and QUERY VOLUME commands on User Response: Review any additional messages
both servers to determine the volume type on each issued by the RECONCILE VOLUMES command and
server. In the case of a volume in the VOLHISTORY, a correct the errors that set the volume to unavailable, or
DELETE VOLHISTORY on the appropriate server that use the DELETE VOLUME command to remove it from
will remove the volume on that server. In the case of a the system.
volume in a storage pool, the DELETE VOLUME
command on the appropriate server will remove the
volume on that server. ANR4364W command: Unable to connect to target
server server name.
ANR4361W command: Volume volume name not valid, Explanation: During processing of indicated
the target server has reported damage to command, the source server was unable to maintain
all or part of the volume. communications with the shown target server.
Explanation: As the result of a RECONCILE System Action: The command process continues.
VOLUMES command, the volume shown was found on User Response: Check both the source server and the
both the source and target server, but the target server target server for any additional messages that might
has reported damage to all or part of the volume. further describe the communications problem.

FORCESYNC=YES to cause the target server to accept
ANR4365W command: Prefix for volume volume name
volume create operations for the source server. Retry
does not match the device class prefix.
the failing operation.
ANR4371E Information on the source server does
both the source and target server, but the beginning
not match information on target server
portion of the high-level archive file name (the prefix)
server name.
on the target server does not match the prefix in the
device class on the source server. Explanation: The source server has determined that
information contained on the shown target server no
longer matches information contained on the source
User Response: Verify that the prefix in the device server.
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 User Response: Issue the RECONCILE VOLUMES
archive objects to match the device class on the source command to determine the problem. If possible, correct
server. the problem and retry the failing operation.
ANR4366I command: Prefix for volume volume name ANR4372E The password on the source server does
was changed to match the device class not match the password on target server
prefix. server name.
Explanation: As the result of a RECONCILE Explanation: The source server has attempted to
VOLUMES FIX=YES command, the beginning portion update both the source password and the target
of the high-level archive file name (the prefix) on the password. An error occurred that prevented the source
target server was changed to match the prefix in the server from updating the target server. The passwords
device class on the source server. no longer match.
System Action: The prefix is corrected. System Action: The operation fails.
User Response: None. User Response: On the target server, issue the
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
ANR4367E Audit command: A storage volume
command to change the password to match the new
containing file data cannot be located -
password on the target server. Retry the failing
file data may not be accessible.
operation.
database audit and indicates that the storage volume
ANR4373E Session rejected by target server server
containing a file’s data cannot be located or is not
name, reason: rejection reason.
defined.
Explanation: The source server has attempted to open
a session with the shown target server. The session was
User Response: Reissue the audit command with rejected for the indicated reason.
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 User Response: Check both the source server and the
the inaccessible file data. target server for any additional messages that might
further describe the reason the session was rejected. For
a reason of AUTHENTICATION FAILURE, ensure that
ANR4370E The source server is not authorized to
both the source and target servers are using the same
create volumes on target server server
password. For a reason of NO RESOURCE, ensure that
name.
the target server is enabled, has sufficient DB, LOG,
Explanation: The source server has attempted to and memory resource to support the source server
create a volume on the shown target server, but the session and that the node name of the source server is
operation failed because the source server does not not locked or in use. If this is a routed command, check
have the authority to create volumes. to make sure that the administator id being used to
route the command is not locked or in use. For a
reason of LICENSE FAILURE, ensure that the target
User Response: If the source server should have server is properly licensed to support the source server
permission to create volumes on the shown target session. For a reason of DOWN LEVEL, ensure that the
server, issue the UPDATE SERVER command with target server program is a level new enough to support
the source server session. For a reason of NODE TYPE,

the source server is not allowed to establish a session System Action: The source server ends the session
with the given target server. The NODETYPE on the and continues operation.
target server is CLIENT. The NODENAME parameter
User Response: Before the source server is permitted
of the server definition on the source server is incorrect.
to access the target server, the target server must be
The NODETYPE parameter of the registered node on
properly defined.
the target server is incorrect and should be
NODETYPE=SERVER. For a reason of INTERNAL
ERROR, use the messages on the target server to ANR4378E For device class device class, the retry of a
determine the problem and contact your service session with target server server name has
representative. Retry the failing operation. timed out.
Explanation: The source server has attempted to
ANR4374E Session failure, source server detected re-establish a session with the shown target server, but
an internal error. the RETRYPERIOD from the given device class has
been exceeded.
Explanation: The source server ends the session
because an internal logic error is detected. System Action: The source server ends the operation.
System Action: The source server ends the session User Response: Determine it the target server is
and continues operation. having a problem or considering increasing the
RETRYPERIOD value.
the administrator can examine server messages issued
prior to this message. The QUERY ACTLOG command ANR4379E The source server was unable to update
can be used to view the activity log and search for the password on target server server
messages. If the error cannot be isolated and resolved, name.
update the target password. An error occurred that
ANR4375E Session failure, source server has prevented the source server from updating the target
insufficient memory. server.
Explanation: The source server ends the session System Action: The operation fails.
because sufficient memory (virtual memory) is not
available. User Response: On the target server, determine the
cause of the problem and correct it. It may be necessary
System Action: The source server ends the session for an administrator to correct the passwords with the
and continues operation. 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.
ANR4376E Session failure, target server server name

ANR4380E The source server was unable to update
is locked on the source server.
the server validation key on target
Explanation: The source server ends the session server server name.
because shown target server is locked from source
server access.
update it’s server validation key on the target server.
System Action: The source server ends the session An error occurred that prevented the source server
and continues operation. from updating the target server.
User Response: Before the source server is permitted System Action: The operation fails.
to access the target server, a properly authorized
User Response: On the target server, determine the
administrator must unlock the target server.
cause of the problem and correct it. It may be necessary
for an administrator to correct the keys with the
ANR4377E Session failure, target server server name following actions. On the source server, issue the
is not defined on the source server. 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.
because shown target server is not defined on the
source server.

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

ANR4397E Audit command: An invalid data format
was encountered for storage pool storage
ANR4390E CANCEL EXPIRATION failed - unable pool name.
to cancel expiration process.
Explanation: The CANCEL EXPIRATION command invalid data format for the specified storage pool.
was issued but encountered an error. Due to this error,
the command was unable to cancel the process.
User Response: Issue the command QUERY PROCESS
to determine the process number for the expiration
ANR4398E Audit command: An invalid data format
process and then issue the command CANCEL
was encountered for storage pool storage
PROCESS for that process number. This will cancel the
pool name - the data format will be
current expiration process.
assigned its default value.
ANR4391I Expiration processing node node name,
invalid data format for the specified storage pool.
filespace filespace name, fsId filespace id,
domain domain name, and management System Action: Because FIX=YES has been specified
class management class name - for type for the command, the audit process assigns the default
type files. value to the data format. Audit processing continues.
Explanation: Expiration processing is currently User Response: If you want the data format for the
evaluating information for the node, filespace, domain specified storage pool to be other than the default, you
name, and management class specified for the file type must delete and re-define the storage pool with the
indicated. desired type after the audit command has completed.
ANR4399I Expiration processing node node name -
for backupset type files.
Explanation: Expiration processing is currently
ANR4395I Audit command: Invalid node type
evaluating information for backup sets for the node
encountered for node node name.
specified.
invalid node type for the node indicated, and FIX=YES
was not specified. User Response: None.
ANR4402I Database Dump command: Database
User Response: You may want to run this command
update activity resumed
again, specifying FIX=YES so that the audit process can
correct the problem. Explanation: Database update activities that were
suspended by the database dump process are restarted.
ANR4396I Audit command: Invalid node type System Action: Server operation continues.
encountered for node node name. The
default type will be set.
ANR4403I Database Load command: Database dump
invalid node type for the node indicated. Because
image is consistent - a database audit
(AUDITDB) will NOT be required if
node’s type to the default value.
this load completes successfully.
Explanation: The database dump that is currently
User Response: If you want the node type for the being loaded by the LOADDB process is a consistent
specified node to be other than the default, you must database image. This process implies that a database
remove and re-register the node with the correct type audit (AUDITDB) will not be required if the load
after the audit command has completed. completes successfully.
System Action: Server database load processing
continues.
User Response: None

ANR4404I Database Load command: Loaded a ANR4408I Audit command: Client option Client
consistent dump image - a database option name sequence number option
audit (AUDITDB) is NOT required. sequence number in optionset optionset
name is not a valid option. The option
Explanation: The database dump image loaded by the
will be deleted.
LOAD command was consistent. A database audit
(AUDITDB) is not required. The server may be started Explanation: A database audit process found that the
normally. specified client option is not a valid option. The option
is deleted.
completes. System Action: Audit processing continues.
ANR4405I Database Load command: Loaded an ANR4409I Audit command: Client option Client
inconsistent dump image - a database option name sequence number option
audit (AUDITDB) IS REQUIRED with sequence number in optionset option set is
FIX=YES. not a valid option.
Explanation: The database dump image loaded by the Explanation: A database audit process found that the
LOAD command was not consistent. A database audit specified client option is not a valid option.
(AUDITDB) with FIX=YES is required to return the
database to a consistent state.
completes.
User Response: To check the database for
ANR4410I Triggered space expansion will be
inconsistencies and correct any inconsistencies, use the
retried in number of seconds seconds.
database audit (AUDITDB) utility as described in the
Administrator’s Reference. Explanation: Because of a problem encountered
during a triggered space expansion for the database
and/or recovery log, the current expansion stops but
ANR4406I Audit command: Client option Client
will be retried after the time period shown.
option name sequence number option
sequence number is not a member of an System Action: The system waits for the specified
optionset. The option will be deleted. period and then retries to expand the database and/or
recovery log.
Explanation: A database audit process found that the
specified client option does not have a corresponding User Response: If possible, correct the condition that
optionset. The option is deleted. stopped the expansion. If the problem persists, contact
ANR4411I Triggered space expansion retry delay
ended; checking space trigger criteria.
ANR4407I Audit command: Client option Client
Explanation: Because a triggered space expansion had
option name sequence number option
been stopped due to a problem, the system waited
sequence number is not a member of an
before retrying. The retry wait period has ended, and
optionset.
the system can now retry to expand space for the
Explanation: A database audit process found that the database and/or recovery log.
specified client option does not have a corresponding
System Action: Space expansion begins.
optionset. The option is deleted.
ANR4412I Data Base and Recovery Log Space
expansion triggered.
Explanation: A triggered space expansion had started.
System Action: Space expansion begins.

ANR4413I Recovery Log Space expansion Is ANR4417W Unable to Create Data Base Copy
Needed, megabytes needed Megabytes Volume Data Base Copy Volume for
needed. volume Data Base Volume.
Explanation: The recovery log is above the utilization Explanation: The Data Base Space Trigger was in the
percentage defined in a DEFINE SPACETRIGGER LOG processing of expanding the data base by creating new
command. An expansion of the indicated number of database volumes. In doing so, database copy volumes
megabytes are needed to be above the space trigger are created for mirroring. The indicated database copy
utilization value. volume could not be created for the primary database
volume named.
System Action: Space expansion begins if supported
on this platform. System Action: Server operation continues. A
database copy volume is not created for the indicated
primary volume.
User Response: Use the Query DBVOL command to
ANR4414I Data Base Space expansion Is Needed,
determine if your database volume configuration is
megabytes needed Megabytes needed.
satisfactory. You may use the DEFINE DBCOPY
Explanation: The database is above the utilization command to define additional database volume copies,
percentage defined in a DEFINE SPACETRIGGER DB if necessary.
command. An expansion of the indicated number of
megabytes are needed to be above the space trigger
ANR4418W Unable to Define Data Base Copy
utilization value.
Volume Data Base Copy Volume for
System Action: Space expansion begins if supported volume Data Base Volume.
on this platform.
Explanation: The Data Base Space Trigger was in the
User Response: None. processing of expanding the data base by creating new
database volumes. In doing so, database copy volumes
are created for mirroring. The indicated database copy
ANR4415I Data Base and Recovery Log Space volume was created for the primary database volume
Expansion Completed. named, but could be registered with the server.
Explanation: A triggered space expansion had System Action: Server operation continues. A
completed. database copy volumes is not registered for the
System Action: Normal operations resume. indicated primary volume. The database copy volume
still exists on the system.
ANR4416W Unable to Determine Maximum Number satisfactory. You may use the DEFINE DBCOPY
of Data Base Volume Copies, rc=return command to retry the definition of the database
code. volume copy, if necessary.
Explanation: The Data Base Space Trigger was in the
processing of expanding the data base by creating new ANR4419W Unable to Determine Maximum Number
database volumes. In doing so, the maximum number of Recovery Log Volume Copies,
of copy volumes for any database volume is rc=return code.
determined. The process of determining this value
failed. Explanation: The Recovery Log Space Trigger was in
the processing of expanding the recovery log by
System Action: Server operation continues. No creating new recovery log volumes. In doing so, the
additional database copy volumes are created during maximum number of copy volumes for any recovery
this database space expansion. log volume is determined. The process of determining
User Response: Use the Query DBVOL command to this value failed.
determine if your database volume configuration is System Action: Server operation continues. No
satisfactory. You may use the DEFINE DBCOPY additional recovery log copy volumes are created
command to define additional database volume copies, during this recovery log space expansion.
if necessary.
User Response: Use the QUERY LOGVOL command
to determine if your recovery log volume configuration
is satisfactory. You may use the DEFINE LOGCOPY
command to define additional recovery log volume
copies, if necessary.

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

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

ANR4433I Data Base now Eligible for Expansion. ANR4437I Audit command: Invalid password
expiration period password expiration
Explanation: The Data Base Space Trigger has
period deleted for client node node name.
previously hit a point where expanding the database
would have caused the size of the database to exceed Explanation: A database audit process finds an invalid
500GB, which is beyond the server maximum limit for password expiration period for a client node. Because
the database. This caused automatic database expansion FIX=YES has been specified for the audit command, the
to be halted. The database size has shrunk or the space audit function deletes the password expiration period,
trigger values have been adjusted to allow expansion. causing the default, global password expiration period
to take effect for the client node.
System Action: Server operation continues, and
automatic database expansion may proceed. System Action: Audit processing continues.
User Response: None. User Response: After the AUDIT command
examine the node that was updated. Use the UPDATE
ANR4434E Audit command: Password expiration
NODE command to set the correct password expiration
found for unknown client node node
period for the node.
name.
ANR4438E Audit command: Password expiration
password expiration period for a client node, but the
found for unknown administrator
client node is not defined correctly in the server
administrator name.
database.
password expiration period for an administrator, but
User Response: If the audit command has not been the administrator is not defined correctly in the server
issued with FIX=YES specified, reissue the audit database.
function specifying FIX=YES so that the error can be
corrected.
issued with FIX=YES specified, reissue the audit
ANR4435I Audit command: Password expiration
period deleted for unknown client node
corrected.
node name.
ANR4439I Audit command: Password expiration
password expiration period for a client node, but the
period deleted for unknown
client node is not defined correctly in the server
administrator administrator name.
database. Because FIX=YES has been specified for the
audit command, the audit function deletes the Explanation: A database audit process finds a
password expiration period. password expiration period for an administrator, but
the administrator is not defined correctly in the server
database. Because FIX=YES has been specified for the
User Response: None. audit command, the audit function deletes the
password expiration period.
ANR4436E Audit command: Invalid password System Action: Audit processing continues.
expiration password expiration period for
client node node name.
Explanation: A database audit process finds an invalid
ANR4440E Audit command: Invalid password
password expiration period for a client node.
expiration password expiration period for
System Action: Audit processing continues. administrator administrator name.
User Response: If the audit command has not been Explanation: A database audit process finds an invalid
issued with FIX=YES specified, reissue the audit password expiration period for an administrator.
corrected.
corrected.

ANR4441I Audit command: Invalid password ANR4445I Context parameter set to value.
expiration period password expiration
Explanation: Determines if context reporting will be
period deleted for administrator
generated when an ANR9999D error occures. This is
administrator name.
turned on or off with the SET CONTEXTmessaging
Explanation: A database audit process finds an invalid command.
password expiration period for an administrator.
command, the audit function deletes the password User Response: None.
expiration period, causing the default, global password
expiration period to take effect for the administrator.
ANR4446I Audit command: Auditing address
System Action: Audit processing continues. definitions.
User Response: After the AUDIT command Explanation: This message is displayed during a
completes, use the QUERY ADMIN command to database audit and indicates that the name address
examine the administrator that was updated. Use the definitions are being examined by the database audit
UPDATE ADMIN command to set the correct password process.
expiration period for the administrator.
ANR4442E Audit command: Extended attribute User Response: None.

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

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

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

ANR4502W No files have been defined for
automatically storing sequential volume
ANR4459E Audit command: Invalid KEEPMP setting history information.
KEEPMP setting for client node node
Explanation: The server is attempting to update all
name.
sequential volume history files defined in the server
Explanation: A database audit process found an options file with information on sequential volume
invalid KEEPMP setting for a client node. usage information. Because no files were configured for
receiving this information, the automatic operation
System Action: Audit processing continues. fails.
User Response: If the audit command has not been System Action: Server operation continues.
function specifying FIX=YES so that the error can be User Response: To have the server automatically
corrected. record sequential volume history information to assist
in server recovery, use the VOLUMEHISTORY option
in the server options file to specify where history
ANR4460I Audit command: Invalid KEEPMP setting information should be written. If you update the
KEEPMP setting deleted for client node options file, restart the server.
node name.
Explanation: A database audit process found an ANR4510E Server could not write sequential
invalid KEEPMP setting for a client node. Because volume history information to volume
FIX=YES has been specified for the audit command, the history file name.
audit function has deleted the KEEPMP setting, causing
the default, KEEPMP setting to take effect for the client Explanation: While attempting to write sequential
node. volume history information to defined history files, the
server could not write to the file name specified.
System Action: The server does not write volume
User Response: After the AUDIT command history information to the file specified
examine the node that was updated. Use the UPDATE User Response: Examine error messages that may
NODE command to set the correct KEEPMP setting for have been displayed prior to this message and correct
the node. 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.
ANR4500I Writing sequential volume history On MVS, make sure that the data set has been allocated
information to defined files. and that the server has authority to write to the data
Explanation: The server is updating all sequential set. After the problem has been corrected, use the
volume history files defined in the server options file BACKUP VOLHISTORY command to write sequential
with information on sequential volume usage volume history information to the file.
information. The files updated are those specified with
the VOLUMEHISTORY option in the server options ANR4511E Volume history file volume history file
file. name could not be opened.
System Action: Server operation continues. Explanation: While attempting to write sequential
User Response: None. volume history information to or read information from
defined history files, the server cannot open the file
name specified.
ANR4501I Sequential volume history information
successfully written to file name. System Action: The server does not write volume
history information to or read volume history
Explanation: The server is updating all sequential information from the file specified
volume history files defined in the server options file
with information on sequential volume usage User Response: Examine error messages that may
information. Volume history information was have been displayed prior to this message and correct
successfully written to the file specified. any problems, if possible. Make sure that the server has
proper authority to write to the file indicated and that
System Action: Server operation continues. there is sufficient space in the file system for the file.
User Response: None. On MVS, make sure that the data set has been allocated
set.

ANR4512E A database transaction failure was
encountered in processing sequential
volume history information.
DEFINE LOGVOLUME command, and extend the size
Explanation: While attempting to process sequential of the database by using the EXTEND LOG command.
volume history information, the server encountered a
database transaction error.
ANR4516E Server could not read sequential volume
System Action: The operation fails. Usage for a history information from any defined
sequential volume was not properly recorded for later files.
reference.
Explanation: While attempting to read sequential
User Response: Examine error messages that may volume history information from defined history files,
have been displayed prior to this message and correct the server finds that it cannot open any of the files
any problems, if possible. If this does not resolve the defined in the server options file.
problem, contact your support representative.
System Action: The server does not read volume
history information. If the current server task requires
ANR4513E A database lock conflict was this information, the task ends.
encountered in processing sequential
volume history information.
Explanation: While attempting to process sequential any problems, if possible. Make sure that the server has
volume history information, the server encountered a proper authority to read from the defined volume
database locking conflict. history files. If you are doing a database restore, issue
RESTORE DB DEVCLASS=VOL.
System Action: The operation fails. This usually
means that usage for a sequential volume was not
properly recorded for later reference ANR4517E No files have been defined for storing
sequential volume history information -
information cannot be read.
any problems, if possible. If this does not resolve the Explanation: The server is attempting to read from at
problem, contact your support representative. least one of the volume history files defined in the
server options file. Since no files were defined for this
information the read operation fails.
ANR4514E Sufficient database space is not
available for the server while processing System Action: Server operation ends.
sequential volume history information.
User Response: You can restore the database
Explanation: While attempting to process sequential specifying the volume names for each restore operation
volume history information, the server found that (in order) up to the desired point-in-time. If a volume
sufficient database space was not available for updates. history file is available, specify its name in the server
options file and retry the operation.
System Action: The operation fails. Usage for a
sequential volume was not properly recorded for later
reference. ANR4518E Volume history file file name line line
number does not have the proper format
- read operation fails.
administrator can add database volumes by using the Explanation: The server is attempting to read from a
DEFINE DBVOLUME command, and extend the size of volume history file and encounters a record that does
the database by using the EXTEND DB command. not have the proper format.
System Action: Server operation terminates.
ANR4515E Sufficient recovery log space is not
User Response: Examine the file specified to
available for the server while processing
determine if the invalid record can be located and
sequential volume history information.
corrected. If the file is corrupted or does not contain
Explanation: While attempting to process sequential valid volume history entries, it cannot be used for the
volume history information, the server finds that desired operation.
sufficient recovery log space is not available for
updates.
System Action: The operation fails. Usage for a
sequential volume was not properly recorded for later
reference.

up the full contents of the database. The full database
ANR4519W Volume History File does not reflect
backup process is assigned the process ID shown.
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. User Response: The administrator may query the
System Action: The storage agent continues
QUERY PROCESS command, or cancel the process by
processing.
using the CANCEL PROCESS command.
User Response: To bypass the problem, a BACKUP
VOLHIST command can be issued from an admin
ANR4553I Incremental database backup triggered;
client connected to the server. The problem may be due
started as process process ID.
to a temporary loss of communication with the server.
Explanation: A background process, triggered by the
LOGFULLPCT parameter on a DEFINE
ANR4549I Database dump command: A database
DBBACKUPTRIGGER command, was started to
dump is already in progress.
incrementally back up the contents of the database. The
Explanation: This message is issued in response to a incremental database backup process was assigned the
database dump command and indicates that a database process ID shown.
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 QUERY PROCESS command, or cancel the process by
started at one time. Use the QUERY PROCESS using the CANCEL PROCESS command.
command to monitor the dump that is in progress.
When completed, issue the database dump command
ANR4554I Backed up number of pages backed up of
to start another database dump if required.
number of pages to back up in current
operation database pages.
ANR4550I Full database backup (process process ID)
Explanation: Periodically, during a database backup,
complete, number of database pages pages
the server displays the number of pages backed up.
copied.
Explanation: A full database backup process has
completed. The output volumes used in this backup User Response: None.
may be used during a database restore operation.
System Action: None. ANR4555I Database backup process process ID
canceled.
Explanation: The database backup process was
canceled by an administrator with the CANCEL
ANR4551I Incremental database backup (process
PROCESS command.
process ID) complete, number of database
pages pages copied. System Action: The database backup process is ended.
Explanation: An incremental database backup process User Response: None.
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 ANR4556W Attention: the database backup
operation. operation did not free sufficient
recovery log space to lower utilization
System Action: None. below the database backup trigger. The
recovery log size may need to be
increased.
Explanation: A database backup process has
ANR4552I Full database backup triggered; started
completed. The server is running in roll-forward mode
as process process ID.
and the recovery log utilization remains above that
Explanation: A background process, triggered by the specified in the database backup trigger.
LOGFULLPCT parameter on a DEFINE
System Action: A database backup operation will be
DBBACKUPTRIGGER command, was started to back
triggered. Unless this situation is corrected, database

backups will be triggered rapidly, one after the other.
ANR4564I Unable to trigger database backup -
User Response: If a database backup operation does sufficient memory is not available.
not free up enough recovery log space to reset
Explanation: A database backup was triggered, but
utilization below the database backup trigger, the
there is not enough server memory available.
recovery log needs to be extended or the database
backup trigger updated to a higher log full percentage. System Action: The backup stops and the server waits
for the retry period to expire and then tries the
database backup again.
ANR4560I Triggered database backup will be
retried in number of seconds seconds. User Response: If necessary, make more memory
Explanation: Because of a problem encountered
during a triggered database backup, the current backup
stops but will be retried after the time period shown. ANR4565E Unable to trigger database backup -
System Action: The system waits for the specified
period and then retries a database backup. Explanation: A database backup was triggered, but
the server cannot start a thread for the backup process.
stopped the database backup. If the problem persists, System Action: The backup stops and the server waits
contact your service representative. for the retry period to expire and then tries the
database backup again.
ANR4561I Triggered database backup retry delay User Response: If the error persists, it may indicate a
ended; checking database backup trigger shortage of server memory. Allocate additional server
criteria. memory.
Explanation: Because a triggered database backup had
been stopped due to a problem, the system waited ANR4570E Database backup/restore terminated -
before retrying. The retry wait period has ended, and device class device class name not defined.
the system can now retry the database backup.
Explanation: During database backup or restore
System Action: Database backup begins. 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
ANR4562I Database backup criteria is no longer
is ended and server operation continues. If the database
met; triggered database backup
backup was triggered automatically, the backup stops
canceled.
and the server waits for the retry period to expire and
Explanation: Because a triggered database backup had then tries the database backup again. A database
been stopped due to a problem, the system waited restore is terminated.
before retrying. The retry wait period has ended, and
User Response: For database backup, make sure the
the system determined that the criteria for triggering a
specified device class is defined. For database restore
database backup was no longer met.
processing, make sure the device class has a definition
System Action: The system waits until the database in a device configuration file that is pointed to in the
backup trigger criteria is met before triggering another server options file.
database backup.
User Response: None. ANR4571E Database backup/restore terminated -
ANR4563I Unable to trigger database backup - a
database define, delete, extend, reduce, Explanation: During database backup or restore, the
or backup operation is already in server cannot allocate sufficient mount points for the
progress. volumes required.
Explanation: A database backup was triggered, but a System Action: If the database backup was started
command that is modifying or backing up the database with the BACKUP DB command, the database backup
is already active. is ended and server operation continues. If the database
System Action: The backup stops and the server waits and the server waits for the retry period to expire and
for the retry period to expire and then tries the then tries the database backup again. A database
database backup again. restore is ended.

User Response: For database backup, make more is ended and server operation continues. If the database
mount points available if necessary. For database backup was triggered automatically, the backup stops
restore processing, make sure the device class has and the server waits for the retry period to expire and
sufficient mount points defined in the device then tries the database backup again. A database
configuration information file that is pointed to in the restore is terminated.
User Response: For database backup, make more
server recovery log space available, if necessary. For
ANR4572E Database restore terminated - excessive database restore, contact your service representative.
read errors encountered.
Explanation: During database restore, read errors ANR4576E Database backup/restore terminated -
occur that prevent the restore from continuing. sufficient database space is not
available.
System Action: Database restore processing stops.
Explanation: During a database backup or restore
User Response: Use a different device for the restore
operation, the server runs out of database space.
operation. If the problem persists, contact your service
representative. System Action: If the database backup was started
is ended and server operation continues. If the database
ANR4573E Database backup terminated - excessive
write errors encountered.
and the server waits for the retry period to expire and
Explanation: During database backup, write errors then tries the database backup again. The database
occur that prevent the backup from continuing. restore process attempts to set the database capacity to
the required capacity to hold the database being
System Action: If the database backup was started restored. If this fails, the restore operation is ended.
is ended and server operation continues. If the database User Response: For database backup, make more
backup was triggered automatically, the backup stops server database space available, if necessary. For
and the server waits for the retry period to expire and database restore, make sure that the size of the online
then tries the database backup again. database is at least the same capacity as the database
being restored.
User Response: If possible, determine and correct the
cause of the write errors. If the problem cannot be
corrected, contact your service representative. ANR4577E Database backup terminated - volume
already in use.
ANR4574E Database backup/restore terminated - Explanation: During a database backup operation, a

data transfer interrupted. volume cannot be used because it is already defined in
a storage pool, or has been previously used by an
Explanation: During a database backup or restore export, a database dump, or a database backup
operation, a data transfer operation has been operation (as recorded in the volume history) or is in
interrupted and cannot be continued. use by another process.
System Action: If the database backup was started System Action: If the database backup was started
with the BACKUP DB command, the database backup with the BACKUP DB command, the database backup
is ended and server operation continues. If the database is ended and server operation continues. If the database
backup was triggered automatically, the backup stops backup was triggered automatically, the backup stops
and the server waits for the retry period to expire and and the server waits for the retry period to expire and
then tries the database backup again. A database then tries the database backup again.
restore is ended.
User Response: Specify a volume that is not in use or
User Response: If possible, determine and correct the defined in a storage pool, and that has not been
cause of the interruption. If the problem cannot be previously used for an export, a database dump, or a
corrected, contact your service representative. database backup operation as recorded in the server
volume history information. The QUERY VOLUME
ANR4575E Database backup/restore terminated - command may be used to display the names of
sufficient recovery log space is not volumes that are defined to server storage pools. The
available. QUERY VOLHISTORY command may be used to
display the names of volumes that have been used for
Explanation: During a database backup or restore export, database dump, or database backup operations.
operation, the server runs out of recovery log space.

ANR4578E Database backup/restore terminated - ANR4581W Database backup/restore terminated -

required volume was not mounted. internal server error detected.
Explanation: During a database backup or restore Explanation: During a database backup or restore
operation, a required volume cannot be mounted, operation, the server encounters an internal error.
because the mount request was canceled.
System Action: If the database backup was started with the BACKUP DB command, the database backup
with the BACKUP DB command, the database backup is ended and server operation continues. If the database
is ended and server operation continues. If the database backup was triggered automatically, the backup stops
backup was triggered automatically, the backup stops and the server waits for the retry period to expire and
and the server waits for the retry period to expire and then tries the database backup again. A database
then tries the database backup again. A database restore is terminated.
restore is terminated.
User Response: Issue the command again or wait for
the server to retry the backup and make sure the
ANR4582E Database restore terminated - volume
necessary volumes are accessible. If you are restoring a
cannot be used.
database to a given date or doing a roll-forward
restore, restart the entire restore operation. If you are Explanation: During a database restore operation, a
restoring a single database backup with COMMIT=NO, volume has been mounted but cannot be used.
reissue the restore command. If you are restoring a
database backup with COMMIT=YES, restore the System Action: The restore operation is terminated.
complete backup series from the beginning. User Response: If a volume list was specified on the
command, make sure the correct volume is being
ANR4579E Database backup/restore terminated - specified and mounted. If no volume list was specified,
thread resource not available. contact your service representative.
Explanation: During a database backup or restore

operation, the server cannot start a thread for the ANR4583E Database backup terminated - output
backup process. media full and scratch media could not
be mounted.
with the BACKUP DB command, the database backup Explanation: During a database backup operation, an
is ended and server operation continues. If the database out-of-space condition occurred writing to the
backup was triggered automatically, the backup stops sequential media, and a scratch volume cannot be
and the server waits for the retry period to expire and mounted.
then tries the database backup again. A database System Action: The database backup is ended and
restore is terminated. server operation continues.
User Response: Retry the command or wait for the User Response: Reissue the command and specify
server to retry the backup if it was started by the additional volume names on the command, or specify
backup trigger. If the error persists, it may indicate a SCRATCH=YES.
ANR4584E Database restore terminated -

ANR4580E Database backup/restore terminated - incomplete input volume list.
insufficient memory available.
Explanation: The list of volumes needed for the
Explanation: During a database backup or restore restore operation was incomplete. At least one volume
operation, there was not enough server memory needed for the restore operation is missing from the
available. end of the list.
System Action: If the database backup was started System Action: The database restore is terminated.
is ended and server operation continues. If the database User Response: If you are using a DSMSERV
backup was triggered automatically, the backup stops RESTORE DB command with the VOLUMENAMES
and the server waits for the retry period to expire and parameter specified, verify that all the volumes within
then tries the database backup again. A database a database backup operation are included in the list.
restore is terminated. Ensure that all the volume names are specified in the
correct sequential order. For a restore with
User Response: If necessary, make more memory COMMIT=NO, reissue the last restore command. For a
available to the server. 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 System Action: The server does not process the
parameter specified, the server created a list of volumes command.
needed for the restore operation. Examine the volume
history files to try to determine the error or use a
date and time.
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 ANR4610E Database volume DB volume name not
time. found in current configuration.
Explanation: The command specified the name of a
ANR4590I Backup type backup series backup series nonexistent database volume.
number operation backup operation in series
stream backup stream within operation System Action: The server does not process the
(always 1) sequence backup volume command.
sequence number in operation taken on date User Response: Reissue the command with a valid
at time. database volume name.
Explanation: During a DSMSERV DISPLAY
DBBACKUPVOL command, the server displays the ANR4611E Unable to restore database and roll
necessary information about a backup volume. forward updates - log mode was not
System Action: Processing continues for all volumes previously set to ROLLFORWARD.
in the given volume list. Explanation: The command specified that the database
User Response: You can use this information to create be restored and all updates rolled forward to the most
a list of volumes for a database restore when a volume current state. This process cannot be accomplished
history backup file is not available. because the server recovery log mode was not set to
ROLLFORWARD; therefore, no update information
exists.
ANR4600I Processing volume history file file name.
Explanation: During a DSMSERV RESTORE DB command.
command with the TODATE parameter specified, the
server is processing the listed file in order to build a User Response: Reissue the command and specify a
list of volumes needed for the restore operation. point in time (TODATE/TOTIME) for restore.

ANR4612E Unable to restore database and roll
User Response: None. forward updates.
Explanation: The command specified that the database
ANR4601E Incomplete volume list found for be restored and all updates rolled forward to the most
TODATE date time - retrying. current state. This process cannot be accomplished
because the internal list of volumes for the most recent
Explanation: During a DSMSERV RESTORE DB
full/incremental backup series is not available. Possible
command with the TODATE parameter specified, the
reasons include:
server created a list of volumes needed for the restore
operation, but the list was incomplete. v No full backup was taken after setting the recovery
log mode to ROLLFORWARD with a SET
System Action: The server tries to build the list again LOGMODE command.
using a different volume history file specified in the
v Only snapshot database backups were created.
server options file. If no other volume history files are
available, the server stops processing. System Action: The server does not process the
command.
User Response: If the problem persists, examine the
volume history files to try and determine the error. You User Response: Reissue the command and specify a
can also restore the database by specifying the volume point in time (TODATE/TOTIME) for restore.
names for each restore operation up to the desired
point in time.
ANR4619I Snapshot database backup series
snapshot database backup series using
ANR4602E No volumes found for TODATE date device class device class.
time.
Explanation: The device class used for the snapshot
Explanation: No volumes were found in the volume database backup is shown.
history files that meet the date and time parameters
specified. System Action: None.

ANR4620I Database backup series Backup series
operation backup operation device class
ANR4632I Starting point-in-time database restore
device class.
(no commit).
Explanation: The device class used for the backup is
Explanation: A point-in-time database restore with a
shown.
specified list of volumes has started. When this restore
System Action: None. is complete, the database will not yet be usable.
User Response: To complete a database restore where
ANR4621I Database backup device class device class. a volume list is specified, specify COMMIT=YES on the
command when restoring the last set of backup
Explanation: The device class for the backup is
volumes. If you forgot to specify COMMIT=YES on the
shown.
command, issue the last restore command again with
System Action: None. COMMIT=YES.

ANR4633I Point-in-time database restore (no
commit) complete.
ANR4622I Volume volume sequence number in backup
operation: volume name. Explanation: A point-in-time database restore with a
specified list of volumes is complete. The database is
Explanation: The volume sequence and name for a not yet usable.
full or an incremental database backup are shown.
User Response: To complete a database restore where
User Response: None. a volume list is specified, specify COMMIT=YES on the
command when restoring the last set of backup
ANR4623I Stream stream number in backup operation volumes. If you forgot to specify COMMIT=YES on the
volume volume sequence number in backup command, issue the last restore command again with
stream: Volume name. COMMIT=YES.
Explanation: The stream number, volume sequence

and name for a full or an incremental database backup ANR4634I Starting point-in-time database restore
are shown. to date date time.
System Action: None. Explanation: A point-in-time database restore with the

TODATE parameter specified has begun. When this
User Response: None. restore is complete, the database will be committed to
the point in time of this backup.
ANR4630I Starting point-in-time database restore System Action: None.
(commit).
specified list of volumes has started. When this restore
is complete, the database will be committed to the ANR4635I Point-in-time database restore complete,
point in time of this backup. restore date date time.
System Action: None. Explanation: A point-in-time database restore with the

TODATE parameter specified has completed. The
User Response: If you inadvertently specified database is committed to the point in time of this
COMMIT=YES, restart the restore process from the backup, which may be different than the TODATE
beginning, starting with restoring the full backup specified. If this is the case, an additional message will
(backup operation 0). be displayed.
ANR4631I Point-in-time database restore (commit)
complete, restore date date time. User Response: None.

specified list of volumes is complete. The date shown is
the date to which the database has been restored.

ANR4636I Starting roll-forward database restore.
Explanation: A roll-forward database restore has
ANR4642I Sequential media log undo pass in
begun. When this restore is complete, the database will
progress.
be returned to its most recent state.
Explanation: During a DSMSERV RESTORE DB, the
process of rolling back incomplete transactions has
User Response: None. begun.
ANR4637I Roll-forward database restore complete.
Explanation: A roll-forward database restore has
ended. All database backups in the most current
ANR4643I Processed number of log records log
backup series have been restored, and all updates to
records.
the database since the most recent backup have been
rolled forward. The database has been returned to its Explanation: Periodically, during the commit of a
most recent state. point-in-time restore or while rolling forward updates
during a roll forward restore, the server displays the
number of log records processed.
ANR4638I Restore of backup series backup series
number operation backup operation in series
in progress. ANR4644I A full backup will be required for the
next database backup operation.
server displays the backup series and operation Explanation: During a point-in-time restore of a
currently being restored. database, this message is displayed to notify the
administrator that the next database backup taken
during normal operation must be a full backup. This
User Response: None. process is normal for point-in-time database restores.
ANR4639I Restored number of pages restored of
User Response: At the next server restart, do a full
number of pages to restore from current
database backup. A full database backup is started
backup operation database pages.
automatically if a DBBACKUPTRIGGER is defined.
Explanation: Periodically, during a DSMSERV
RESTORE DB, the server displays the number of pages
ANR4645I The restore date reflects the most recent
restored from the current backup being restored.
backup available up to the specified
System Action: None. TODATE.
User Response: None. 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
ANR4640I Restored number of database pages pages
command. The backup series that was restored is the
from backup series backup series number
most recent backup series up to and including the
operation backup operation in series.
specified date.
Explanation: At the end of each restored backup, the
server displays the number of database pages restored.
User Response: Make sure the date of the restored
database is satisfactory. If it is not, restore the database
User Response: None. again by specifying a different TODATE or by restoring
individual database backups.
ANR4641I Sequential media log redo pass in

progress. ANR4646I Database capacity required for restore is
number of megabytes megabytes.
process of committing incomplete database updates has Explanation: During a point-in-time restore of a
begun. database, the size of the database being restored is
displayed. The available capacity of the online database

volumes must be at least this size. 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
ANR4647I Database available capacity is number of epoch.
megabytes megabytes.
Explanation: During a DSMSERV RESTORE DB, a
Explanation: During a point-in-time restore of a backup volume was mounted that is not in the correct
database, the available capacity of the online database sequence. The current backup operation cannot be
volumes is displayed. This capacity must be as large as restored in this series because it belongs to the same
the size of the database being restored. backup series from another point in time.
System Action: If the available capacity of the online System Action: The database restore is terminated.
database volumes is not at least this size, the restore
User Response: Restart the database restore from the
cannot continue.
beginning of the full backup. Omit all backups from the
User Response: If the available capacity of the online offending backup and later from the restore.
database is not sufficient, reinstall the server with the
required database size, and try the restore operation
ANR4657E SNMP: Failed to connect to server at
again.
address address, port port.
Explanation: The SNMP client was attempting to run
ANR4648I Extending database assigned capacity to
a session with the server at the indicated address and
port number in response to an SNMP Get Request,
Explanation: During a point-in-time restore of a which causes a Server Script to be run. The subagent
database, the assigned capacity of the online database failed to connect to the server.
is smaller than that of the database being restored.
System Action: The SNMP subagent ends this attempt
However, the available capacity of the online database
to run the script and continues operation.
volumes is sufficient for restore.
User Response: Ensure that the indicated server is up
System Action: The assigned capacity of the online
and able to initiate admin clients using the TCP/IP
database is extended to the size required for restore.
protocol.
ANR4659E SNMP: Communications failure: bad
ANR4649I Reducing database assigned capacity to verb received (verb type).
Explanation: The SNMP client encountered an invalid
Explanation: During a point-in-time restore of a communications verb during a session with the server
database, the assigned capacity of the online database and is not able to continue processing the session.
is larger than that of the database being restored.
System Action: The SNMP session ends and subagent
System Action: The assigned capacity of the online operation continues.
database is reduced to the size required for restore.
ANR4660I Connected to SNMP subagent at SNMP
ANR4650E Restore of backup series current series subagent address on port port number.
operation current operation is not in
Explanation: The server has successfully connected to
sequence; last restored backup was
the SNMP subagent at the indicated address and port.
series previous series operation previous
operation. System Action: The server will now register with the
subagent.
Explanation: During a DSMSERV RESTORE DB, a
backup volume was mounted that is not in the correct User Response: None.
sequence.
System Action: The database restore is terminated. ANR4661E SNMP communication with the
subagent failed because a thread
User Response: Ensure volume names are specified in
resource was not available.
the correct sequential order. For a restore with
COMMIT=NO, reissue the last restore command. For a Explanation: The server could not continue with
restore with COMMIT=YES, restart the restore from the SNMP communication to the SNMP subagent because

sufficient memory is not available for starting
ANR4664W Failure in registering with SNMP
additional processes on the server.
subagent.
System Action: The server discontinues SNMP
Explanation: The server experienced a problem while
attempting to register with the SNMP subagent. This
User Response: Allocate additional storage to the may be due to problems with communication or the
server. For details, issue HELP MEMORY to display 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
ANR4662W Failure sending message to SNMP
and that the TCP/IP protocol stack is functioning by
subagent.
using the tools that come with the particular TCP/IP
Explanation: The server experienced an error return suite on the platform in use.
code from TCP/IP while sending to the SNMP
subagent. This message is also issued when the SNMP
ANR4665W Failure retrying registration with SNMP
subagent has an error sending a verb to the server
subagent.
when acting as an SNMP client. This may be a normal
event if either side of the connection is abruptly ended, Explanation: The server experienced a problem while
as in the case of terminating the subagent program. The attempting to re-register with the SNMP subagent after
error is reflected in another message for TCP/IP which losing contact. This may be due to problems with
further describes the error. communication or the SNMP subagent being
unavailable.
System Action: The session is ended. Server operation
continues. If a message is being forwarded to an SNMP System Action: Registration is re-tried for a number of
managing node, the message is not sent. If a heartbeat attempts before giving up.
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 suite on the platform in use.
intentionally stopping either the subagent, no response
is required. Otherwise, ensure that the TCP/IP protocol
ANR4666W Failure sending heartbeat message to
stack is functioning by using the tools that come with
SNMP subagent.
the particular TCP/IP suite on the platform in use.
attempting to send a heartbeat message to the SNMP
ANR4663W Failure receiving message from SNMP
subagent. This may be due to problems with
subagent.
communication or the SNMP subagent being
Explanation: The server experienced an error return unavailable.
code from TCP/IP while receiving data from the SNMP
System Action: The server will attempt to contact the
subagent. This may be a normal event if either side of
SNMP subagent again and re-synchronize.
the connection is abruptly ended, as in the case of
terminating the subagent program. The error is User Response: Ensure that the subagent is running
reflected in another message for TCP/IP which further and that the TCP/IP protocol stack is functioning by
describes the error. using the tools that come with the particular TCP/IP
suite on the platform in use.
continues. If a heartbeat message was being sent to the
subagent, this heartbeat message is lost and the server ANR4667W Failure retrying heartbeat message to
attempts to re-start its session with the SNMP SNMP subagent.
subagent. If the server was attempting to register to the
SNMP subagent, heartbeat messaging will be disabled Explanation: The server experienced a problem while
until the server is re-started. attempting to send a heartbeat message to the SNMP
subagent. This may be due to problems with
User Response: If the session is ended as a result of communication or the SNMP subagent being
intentionally stopping either the subagent, no response unavailable.
is required. Otherwise, ensure that the TCP/IP protocol
stack is functioning by using the tools that come with System Action: The server attempted to contact the
the particular TCP/IP suite on the platform in use. SNMP subagent again and re-synchronize, but this too
failed. Heartbeat functions are disabled until the server
is re-started.

User Response: Ensure that the subagent is running re-start it if heartbeat and message forwarding
and that the TCP/IP protocol stack is functioning by functions are required.
suite on the platform in use. Re-start the server if the
ANR4672W SNMP message forwarding to the
heartbeat function is required.
SNMP subagent was not started because
a thread resource was not available.
ANR4668I Connection successfully re-established
Explanation: The server could not continue with
with SNMP subagent.
SNMP communication to the SNMP subagent for
Explanation: The server experienced a problem while message forwarding because sufficient memory is not
attempting to send a heartbeat message to the SNMP available for starting additional processes on the server.
subagent.
System Action: The server discontinues SNMP
System Action: The server was able to successfully message processing and server operation continues.
resynchronize with the SNMP subagent.
User Response: None. server. For details, issue HELP MEMORY to display the
ANR4669W Heartbeat message was not accepted by
SNMP subagent.
ANR4673E Insufficient memory for subagent
initialization (the portion of initialization
attempting to send a heartbeat message to the SNMP
where the allocation of memory failed).
subagent. The SNMP subagent was unable to accept the
heartbeat message. If the subagent was stopped and Explanation: The SNMP subagent could not initialize
re-started, this is a normal message. due to the inability to obtain the required memory.
System Action: The server will attempt to contact the System Action: Initialization of the subagent fails.
SNMP subagent again and re-synchronize.
User Response: Allocate additonal storage to the
User Response: Ensure that the subagent is running subagent.
ANR4674E Error starting DPI thread - Return code:
suite on the platform in use.
Return code received from called routine.
Explanation: The SNMP subagent could not start the
ANR4670W Failure in opening session with SNMP
DPI thread.
subagent.
System Action: Initialization of the subagent fails.
attempting to open a session with the SNMP subagent. User Response: Contact your service representative.
System Action: Processing continues. Heartbeat and
message forwarding function will not be available. ANR4675E Server/subagent protocol violation -
invalid (where the protocol breakdown
occurred).
using the tools that come with the particular TCP/IP Explanation: The SNMP subagent received an
suite on the platform in use. If heartbeat and message unexpected request from the server.
forwarding functions are required, re-start the server.
System Action: The subagent will stop processing
requests from the server sending the invalid requests.
ANR4671W SNMP subagent did not accept
registration of this server. User Response: Contact your service representative.

attempting to open a session with the SNMP subagent. ANR4676E Unable to register another server.
The subagent is available but disallowed registration by Explanation: The SNMP subagent received a request
this server. to register a new server and was unable to allocate the
System Action: Processing continues. Heartbeat and memory necessary to register the new server.
message forwarding function will not be available. System Action: The subagent will not register the new
User Response: It may be necessary to stop the server.
subagent and re-start it. Then stop the server and User Response: Contact your service representative.

ANR4677I Session established with server name: ANR4682W A SNMP agent connection error
The name of the registered server.. occurred. Attempting to re-establish
connection.
Explanation: The SNMP subagent completed the
registration of the identified server. Explanation: An error has occurred in the
communication between the subagent and the SNMP
System Action: The subagent will wait for additional
agent.
requests from the server.
System Action: The subagent will attempt to
reconnect.
User Response: Make sure that the SNMP daemon is
ANR4678I Session closed with server name: The
up, running and correctly configured.
name of the deregistered server..
Explanation: The SNMP subagent completed the
ANR4683E Unable to open trace file ’file name’.
deregistration of the identified server.
Explanation: An error occurred while opening the file
for writing trace data.
System Action: The subagent continues operation
without tracing.
ANR4679W Messages are no longer being forwarded
User Response: Ensure there is adequate space on the
to the SNMP subagent.
drive from which you are running the subagent and
Explanation: The server has encountered multiple retry the program.
errors in forwarding messages to the SNMP subagent.
Messages are no longer being forwarded.
ANR4684E Trap request failed - RC: Return code from
System Action: The server continues operating, but the trap request. Server index: Server index
messages are no longer being forwarded. number..
User Response: Message forwarding can be Explanation: An error occurred while attempting to
re-initialized by either stopping the server and process a trap request from a server. data.
re-starting it. Message forwarding will also be
System Action: The subagent processing continues.
re-started if the heartbeat function is in use and the
server re-synchronizes with the subagent. This User Response: Make sure that the SNMP daemon is
re-synchronization occurs if the subagent, dsmsnmp, is up, running and correctly configured.
stopped for longer than a single heartbeat interval (the
heartbeat interval is a server option and appears in the
ANR4685E Insufficient memory for subagent
output of the QUERY OPT command) and then
initialization.
restarted.
Explanation: The SNMP subagent could not initialize
due to the inability to obtain the required memory.
ANR4680I DPI subagent (The subagent name.):
″Connected″ or ″reconnected″, ready to System Action: Initialization of the subagent fails.
receive requests.
User Response: Allocate additional memory to the
Explanation: The subagent has successfully connected subagent.
or reconnected to the SNMP agent.
System Action: The subagent is ready to receive ANR4686E Insufficient memory for subagent trace
requests from servers. initialization.
User Response: None. 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. System Action: Initialization of the subagent fails.
Explanation: The subagent has failed in an attempt to User Response: Allocate additional memory to the
connect to the SNMP agent. subagent.
System Action: The subagent keeps retrying the
connection.
User Response: Make sure that the SNMP daemon is
up, running and correctly configured.

ANR4687E Server/subagent protocol violation - ANR4692I DPI subagent (The subagent name.):
expecting registration request. Received reconnected, ready to receive requests.
request: The value of the request that was
Explanation: The subagent has successfully
received.
reconnected to the SNMP agent.
Explanation: The SNMP subagent was expecting a
System Action: The subagent is ready to receive
registration request. It actually received something
request from servers.
other than a registration request.
ANR4693I Interface Driver information will be
loaded in quiet mode: Only warning
and error messages will be displayed.
ANR4688E Server/subagent protocol violation -
Explanation: The server is loading information needed
incorrect request header version.
for the Administrative WEB Interface. To minimize
Explanation: The SNMP subagent received a request message traffic, only error and warning messages will
from a server that was not at the same maintenance be displayed.
level as the subagent.
System Action: When the command completes, WEB
System Action: The subagent will stop processing administrative information will be loaded into the
requests from the server sending the invalid requests. server.
User Response: Ensure the server and subagent are at User Response: None.
the same maintenance level. If they are, contact your
ANR4694E SNMP Subagent Port Confirmation Has
Failed.
ANR4689E Invalid request type received (The value
Explanation: The server was communicating
of the request that was received.).
configuration data to the SNMP subagent. An error
Explanation: The SNMP subagent received an occurred in the exchange. The server could not
unexpected request from the server. communicate interface information to the subagent.
System Action: The subagent will stop processing System Action: The server continues operation. The
requests from the server sending the invalid requests. SNMP administrative interface is inoperative.
User Response: Contact your service representative. 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
ANR4690E Unexpected request type (The value of the
subagent. If this problem occurs repeatedly, please
request that was received.) in trap data
contact you service representative.
header.
Explanation: The SNMP subagent received an invalid
ANR4695E SNMP: Communications Failure in
trap request from a server.
Receiving ″verb type″ verb.
Explanation: The SNMP client encountered a
communications error in using the verb type verb to
User Response: Contact your service representative. transfer information to or from the server and an
SNMP client.
ANR4691I DPI subagent (The subagent name.): System Action: The SNMP session ends and server
connected, ready to receive requests. operation continues.
Explanation: The subagent has successfully connected User Response: This may not be a problem if the
to the SNMP agent. SNMP subagent was terminated while the session was
in progress. Otherwise, ensure that TCP/IP
System Action: The subagent is ready to receive communications is running normally.
request from servers.

ANR4697E SNMP: Failed to authenticate to server ANR4701I The server move size threshold has been
at address address, port port. set to new threshold. Move operations
that start after this point will use the
Explanation: The SNMP client was attempting to run
new value.
a session with the server at the indicated address and
port number in response to an SNMP Get Request, Explanation: A SETOPT commmand was used to set
which causes a Server Script to be run. The subagent the value for the move size threshold value. This
connected to the indicated server, but failed in setting determines the maximum number of megabytes
authentication. that are moved on the server in one database
transaction, dependent also on the setting for the move
System Action: The SNMP subagent ends this attempt
batch size. The setting influences file movement for
to run the script and continues operation.
server migration, reclmation, storage pool backup, and
User Response: Ensure that the indicated server has move data operations.
an an administrative id of SNMPADMIN and that this
System Action: The server uses this new setting for
adminstrative id has sufficient authority to run the
move operations that are started after this message is
script and commands it contains.
issued.
ANR4698E SNMP: Communications Failure in
Sending ″verb type″ verb (command).
ANR4702I The server transaction group maximum
Explanation: The SNMP client encountered a
has been set to new value. Client sessions
communications error in using the verb type verb to
that are started after this point will use
issue command command.
the new value.
System Action: The SNMP client session ends and
Explanation: A SETOPT commmand was used to set
subagent operation continues.
the value for the maxmimum number of files that can
User Response: Contact your service representative. be sent from the client in a single database transaction.
System Action: The server uses this new setting for
ANR4699E SNMP: Receive Buffer overflow. client sessions that are started after this message is
issued.
Explanation: The SNMP client encountered an
overflow error in transferring information to or from User Response: Contact your service representative.
the server.
System Action: The SNMP client session ends and ANR4703E Invalid key ring filename Key Ring
subagent operation continues. Filename
User Response: Contact your service representative. Explanation: The key ring filename specified did not
contain the .kyr extention.
ANR4700I The server move batch size has been set System Action: None.
to new batch size. Move operations that
User Response: Rename your key ring filename to
start after this point will use the new
contain the .kyr extention. Reexcute the command with
value.
the new filename.
Explanation: A SETOPT commmand was used to set
the value for the move batch size value. This setting
ANR4704I Key ring filename and password have
determines the maximum number of files that are
been set. Restart the server to use the
moved on the server in one database transaction,
new settings
dependent also on the setting for the move size
thrshold. The setting influences file movement for Explanation: The key ring filename have been set to
server migration, reclmation, storage pool backup, and the new value specified in the DEFINE KEYRING
move data operations. command.
System Action: The server uses this new setting for System Action: None.
move operations that are started after this message is
User Response: Restart the server to use the new key
issued.
ring information.

User Response:
ANR4705I The server IDL definitions have not
been installed. These definitions will 1. Remove COMMMETHOD HTTPS from your option
need to be installed for the Web file.
Administrator interface to work. 2. Install and configure the web proxy. See Quick Start
Appendices for more information on how to install
Explanation: The server attempted to query the server
and configure the web proxy.
IDL interface and found no definitions defined. Because
of this error the HTTP engine returns a 404 not found
message. ANR4709W Intervention required to mount volume
Volume Name on Library Manager Server
Server Name.
User Response: If you would like to use the server
Explanation: A volume mount is awaiting operator
web administrator interface you will need to:
intervention on the specified library manager server.
1. Halt the server.
System Action: The volume mount operation waits
2. Issue the command DSMSERV RUNFILE
for operator intervention.
dsmserv.idl. For AS/400 command see next step.
3. For AS/400, issue the command STRSVRADSM User Response: Refer to the server consol and/ir
SVRMODE(*PRPWEB). activity log on the named library manaer server to
determine the action that needs to be performed to
4. Restart the server.
complete the mount operation.
ANR4706W Unable to open file Filename to satisfy

ANR4710W Library manager Server Name could not
web session Session ID.
be contacted to control library Library
Explanation: A web browser requested a file and the Name.
server could not find the file on the local file system.
Explanation: The specified library manager server
Special note, some files requested from the server are
could not be contacted for control of the named library.
not vaild and are caused by a browser error. For
example, a request for CommandLineBeanInfo.class is System Action: The server will continue to contact the
not a valid file request. However, a request of a GIF named library manager server. Volume mounts in the
image or HTML page should not produce this error. library will fail until communication is successful.
System Action: None. User Response: Determine why the named server is
not running or why the network prevents
User Response: Verify that permission for the file are
communication with te named server.
set correctly and file exists.
ANR4712E Command: The DEVCLASS parameter is

ANR4707E Import/Loaddb command operation
only valid for volume history types
terminated - incomplete input volume
DBBACKUP or DBSNAPSHOT.
list.
Explanation: The command failed because an invalid
Explanation: The list of volumes needed to process
volume history type was specified for the TYPE=
the command was incomplete. At least one volume
parameter.
needed for the operation is missing from the end of the
list. System Action: The command fails, and server
System Action: The command operation is ended.
User Response: Re-issue the command and specify a
User Response: Issue the command again and make
valid type value.
sure the necessary volumes are included in the volume
list.
ANR4713E Command: The ″option″ string is not valid
for the Hex Filespace Field.
ANR4708I Native SSL support has been disabled,
please use the web proxy. Explanation: The command indicated specifies a value
that is not valid for the Hex Filespace parameter.
Explanation: Starting in this version of this product
native Secure Socket Layer support has been removed. System Action: The server does not process the
This feature has been replace with the web proxy. command.
Support for non-secure http request (COMMMETHOD
HTTP) has not been disabled. User Response: Reissue the command with a valid
entry for the Hex Filespace parameter.

User Response: To obtain status on the file deletion
ANR4714I Command filename for filespace filespace
process, issue the QUERY PROCESS command. The
name of node node name started as
process may be canceled by an authorized
process process ID.
Explanation: A file deletion process has started to
delete one or more files from the given filespace for the
ANR4718I DELETE FILE file name canceled for
for given node. The process is assigned the ID specified
filespace filespace name of node node name
in the message.
: number of objects objects deleted.
Explanation: A background server process that has
process to perform the operation in response to the
been deleting files for the given fliespace of the given
DELETE FILE command entered by an administrator.
node is canceled by the CANCEL PROCESS command.
User Response: To obtain status on the file deletion The number of objects deleted before the cancel ended
process, issue the QUERY PROCESS command. The the operation are reported in the message.
process may be canceled with the CANCEL PROCESS
command.
User Response: No action is required. An authorized
ANR4715I DELETE FILE file name (backup/archive
administrator can issue the DELETE FILE command to
data) for filespace filespace name of node
delete the remaining files desired.
node name started.
ANR4719I DELETE FILE file name complete for
(on the server) to delete files from the given filespace
filespace filespace name of node node name
for the given node.
: number of objects objects deleted.
Explanation: A server process deleting file space data
backup and archive objects that match the given file
for the node specified has completed. The total number
name while server operation continues.
of objects deleted is reported in the message.
process may be canceled by an authorized
administrator using the CANCEL PROCESS command. User Response: None.
ANR4716I DELETE FILE file name (backup data) for ANR4723E Storage Agent storage agent name is
filespace filespace name of node node name incompatible with this server. Please
started. update the storage agent to the same
level as this server.
(on the server) to delete files from the given filespace Explanation: A downlevel storage agent has connect
for the given node. to this server. The storage agent version, release, and
fix level must exactly match, otherwise data corruption
may occur. For example, a version 4.1.0.0 storage agent
backup objects that match the given file name while
cannot connect to a version 4.2.0.0 server.
System Action: Upgrade the storage agent to the same
level as the server.
process may be canceled by an authorized User Response: None.
ANR4724E During the backup of node node (Node

ANR4717I DELETE FILE file name (archive data) for id) filespace filespace name (filespace id) a
filespace filespace name of node node name deletion activity occurred.
started.
Explanation: During full or incremental backup
Explanation: A background server process has started processing, files were deleted from the file space. The
(on the server) to delete files from the given filespace files were not deleted by expiration, but by some other
for the given node. process, DELETE FILESPACE, DELETE VOLUME,
AUDIT VOLUME, or some other administrator
command that can cause files to be deleted. The file
archive objects that match the given file name while
space image on the server will not be consistent with

the client until an incremental backup is completed for v An unsupported model of the filer server was
the node. detected
System Action: The server will continue processing. System Action: TSM server backup/restore of the file
server fails.
User Response: An incremental backup should be
done for the client node. User Response: Check if file server is accessible
through the network; check each of the attributes
specified during datamover definition; check NDMP
ANR4725E Source file(line number): Server lock
versions supported by the file server; check the number
Locktype, mode Lockmode failed.
of open NDMP sessions with the file server, verify that
Explanation: An internal error occurred in an attempt file server model is supported by TSM server.
to obtain a lock during processing.
System Action: The activity that generated this error ANR4729E Server connection to file server File
fails. server name failed. The level of the file
server operating system is unsupported
User Response: Retry the process. If the process fails by TSM server. Please upgrade the file
contact your service representative. server to the level of the operating
system supported by the server.
ANR4726I The support module has been loaded. Explanation: The TSM server was trying to connect to
Explanation: The module indicated has been a file server with an unsupported level of the operating
successfully loaded. Operations involving this module system. The server can establish NDMP connection
may be performed by the server. only to a file server with supported level of the
operating system. Please check the following site for
System Action: Functions which depend on this supported levels of file server operating systems:
module may now be performed on the server. http://www.tivoli.com/storage
User Response: None. System Action: The TSM server backup/restore of the
file server fails.
ANR4727E Server Server name is incompatible with User Response: Upgrade the file server to a supported
this server. Please update the server to level of the operating system.
the same level as this storage agent.
Explanation: The storage agent attempted to connect ANR4730E Command: Exceeded allowed number of
to a downlevel server. The server version, release, and copy storage pools in list.
fix level must exactly match, otherwise data corruption
may occur. For example, a version 4.2.0.0 storage agent Explanation: The COPYSTGPOOLS parameter
cannot connect to a version 4.1.0.0 server. contains a list that exceeds the maximum limit.
System Action: Upgrade the TSM server to the same System Action: None.
level as the storage agent. User Response: Retry the command with fewer copy
User Response: None. storage pools in the list.
ANR4728E Server connection to file server File ANR4731E Command: Copy storage pool storage pool
server name failed. Please check the name is not defined.
attributes of the file server specified Explanation: A DEFINE STGPOOL or UPDATE
during definition of the datamover. STGPOOL command contained a copy storage pool
Explanation: The server attempted to connect to a file that is not defined.
server. The connection failed because of one of the System Action: None.
following possible reasons:
v One of the parameters specified during datamover User Response: Verify that the copy storage pool
definition was incorrect: TCP/IP address of the file name stated in the error message is correct. Correct the
server, user id, password, TCP/IP port problem by using a copy storage pool that already
exists or define the copy storage pool. Retry the
v File server does not support requested NDMP command.
version
v File server is not accessible
v NDMP server limits the number of opened NDMP
sessions

ANR4732E Command: The storage pool storage pool ANR4736E Set serverfree is not allowed when
name is not a copy storage pool. server free is not available.
Explanation: A DEFINE STGPOOL or UPDATE Explanation: Server free processing did not initialize.
STGPOOL command contained a copy storage pool Changing the status is not allowed.
name that is not a copy storage pool.
User Response: Server free status may be changed
User Response: Remove the storage pool name from when the status is ON or OFF.
the list and retry the command.
ANR4737E Transaction failed for session session
ANR4733E Command: The copy storage pool number for node node name (client
contains a copy storage pool name that platform) - the copy continue attribute for
introduces a cycle into the storage pool storage pool :storage pool name prevented
chain. further reties.
Explanation: A DEFINE STGPOOL or UPDATE Explanation: During the pocess of a backup session
STGPOOL command contained a copy storage pool one or more copy storage pools associated with the
that eventually points to the pool being processed. given storage pool had a failure. The operation was
halted becuase the copy continue option for the given
storage pool indicated to stop the request.
User Response: Remove the storage pool name from
the copy storage pool list and retry the command.
User Response: Verify the following: 1. Does the
device class(es) have enough mount points to satifiy
ANR4734W Copy storage pool Copy Storage Pool
the request? 2. Was the node’s MAXNUMMP value
Name was removed from the copy
high enough to acquire the needed mount points to
storage pool list because of a failure for
satifiy the request? 3. Were there any errors reported
session Session Id.
during the transaction regarding I/O or related issues?
Explanation: The named copy storage pool was This problem could also be solved by updating the
removed from the storage pool list for the current storage pool’s COPYCONTINUE option to YES using
session backup/archive/space management operation the UPDATE STGPOOL command. Setting this attribute
because of an error. This removal is only for the session to YES will allow the transaction to continue if one or
indicated in the message and does not effect other more above error occured.
session operation.
System Action: None. ANR4738E Command: Storage pool storage pool name
is in use in the copy storage pool
User Response: The error that occured could be one parameter for one or more other storage
of many failure. Look for the following items in the pools.
active log or on the server console. 1. Is the named
copy storage pool currently unavailable? 2. Have any Explanation: A DELETE STGPOOL command specifies
I/O error occured on the destination devices (disk or a pool that is listed as one of the copy storage pool for
tape drives)? 3. Is the mount limit on the device class other storage pools’ COPYSTGPOOLS parameter.
correctly set?
command.
ANR4735W Server free processing is not available.
User Response: If necessary, update other storage
Initialization failed.
pools so that they do not reference the pool to be
Explanation: An error occurred while initializing deleted, and reissue the command.
server free processing. Server free data transfer is not
available to backup and restore images.
ANR4980I Auditing Interface Driver definitions.
System Action: Client backup and restore image
Explanation: The server is beginning an audit of the
requests will use lan-based data transfer.
definitions for Web interface.
System Action: The server will audit all definitions
for the Web interface and report any problems.

ANR4981E Interface Driver audit completed - ANR4986I Auditing Interface Driver Classes.
Inconsistencies were found.
Explanation: The server is auditing the driver classes.
Explanation: The server found errors during the audit
System Action: The server will audit the driver
of the definitions for Web interface.
classes and proceed to the next step.
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.
ANR4987E Audit processing failed: sufficient
User Response: Ensure you are using the correct IDL
memory is not available for processing.
file for the server level you are running. Examine error
messages that may have been displayed before and/or Explanation: At RUNFILE time, the server is unable
after this message and correct any problems, if possible. to process the IDL data due to insufficient memory.
If the cause of this can not be determined or resolved,
contact your support representative. System Action: Server runfile stops.
User Response: Restart the server runfile process with
ANR4982I Interface Driver audit completed - more memory available.
definitions are consistent.
Explanation: The server successfully completed the ANR4988I Auditing Interface Driver Complex
installation of the definitions for the Web interface. Class containers.
System Action: The Web Interface is now installed. Explanation: The server is auditing the driver class
The server may be run without any problems. containers.
User Response: None. System Action: The server will audit the driver class
containers and proceed to the next step.
ANR4983I Auditing Interface Driver Groups. User Response: None.
Explanation: The server is auditing the driver groups.

ANR4989I Auditing Interface Driver Operations.
groups and proceed to the next step. Explanation: The server is auditing the driver
operations.
operations and proceed to the next step.
ANR4984E Error description
Explanation: The server found errors during the audit
of the definitions for Web interface.
ANR4990I Auditing Interface Driver Operation
System Action: The audit will fail. Parameters.
User Response: Ensure you are using the correct IDL Explanation: The server is auditing the driver
file for the server level you are running. Examine error operation parameters.
messages that may have been displayed before this
message and correct any problems, if possible. If the System Action: The server will audit the driver
cause of this can not be determined or resolved, contact operation parameters and proceed to the next step.
your support representative. If you contact your User Response: None.
support representative, the entire text of this message
should be reported.
ANR4991I Auditing Interface Driver Tasks.
ANR4985I Auditing Interface Driver Group Explanation: The server is auditing the driver tasks.
Members. System Action: The server will audit the driver tasks
Explanation: The server is auditing the driver group and proceed to the next step.
members. User Response: None.
System Action: The server will audit the driver group
members and proceed to the next step.

ANR4992I • ANR5016E (S/390)
command per open disk so that the CMS DISKID
ANR4992I Auditing Interface Driver Task
function may be used.
Members.
Explanation: The server is auditing the driver task
members. User Response: For a description of the FILEDEF
error code, refer to the CMS Command Reference
System Action: The server will audit the driver task
publication for your operating system.
members and proceed to the next step.
ANR5013E (S/390) Unable to open disk vaddr -
virtual disk not attached.
ANR4993E The client platform platform name is
Explanation: A disk cannot be opened because the
currently not supported by the TSM
virtual disk is not attached to the server’s virtual
Storage Agent.
machine.
Explanation: At this point in time the storage agent
does not accept the incomming client platform.
User Response: Ensure that the VM DASD volume
containing the disk is online, and that the disk is
User Response: None. properly linked to the server’s virtual machine.
ANR5000E (S/390) Unable to load tape deletion exit. ANR5014E (S/390) Unable to open disk vaddr - error
code received from DISKID.
Explanation: The tape deletion exit module specified
in the options file cannot be loaded. Explanation: A disk cannot be opened for processing
because the error code has been received from the
DISKID function.
User Response: Ensure that the tape deletion exit
module is in the system linklist or in the
JOBLIB/STEPLIB for the server. User Response: For a description of the DISKID error
code, refer to the CMS Command Reference publication
for your operating system.
ANR5010E (S/390) Unable to initialize disk driver -
internal error code from IUCV.
Explanation: The server’s disk driver cannot be
internal error code connecting to Block
initialized because the error code has been received
I/O System Service.
from the IUCV DECLARE BUFFER function.
Explanation: A disk cannot be opened for processing
because the IUCV CONNECT error code is received
User Response: For a description of the reported error when attempting to connect to the CP DASD Block I/O
code, refer to the IUCV documentation in the CP System Service.
Programming Services publication for your specific
operating system.
User Response: For a description of the IUCV
CONNECT error code, refer to the IUCV
documentation in the CP Programming Services
invalid virtual device address.
publication for your specific operating system.
because the specified virtual address is beyond the
ANR5016E (S/390) Unable to open disk vaddr - device
supported range. Virtual addresses must be specified in
type not supported.
the range 0001 to FFFF.
because its device type is not supported.
User Response: Specify a valid virtual address.
User Response: Use only the disk devices supported
ANR5012E (S/390) Unable to open disk vaddr - error
by the CP DASD Block I/O System Service.
code received from FILEDEF.
because the error code has been received from the
FILEDEF command. The server enters one FILEDEF

ANR5017E (S/390) • ANR5027E (S/390)
ANR5017E (S/390) Unable to open disk vaddr - block ANR5022E (S/390) Unable to perform I/O to disk
size not supported. vaddr - permanent error writing to block
block.
because its formatted block size is not supported. Explanation: The server encounters a permanent error
while writing to the specified disk and block.
User Response: Use only the disks formatted with
block sizes supported by the CP DASD Block I/O User Response: Reformat or replace the disk.
System Service.
ANR5023E (S/390) Unable to perform I/O to disk
ANR5018E (S/390) Unable to open disk vaddr - IUCV vaddr - permanent error reading from
path already exists to device. block block.
Explanation: A disk cannot be opened because a path Explanation: The server encounters a permanent error
already exists for this device to the CP DASD Block while reading from the specified disk and block.
I/O System Service.
User Response: Reformat or replace the disk.
ANR5019E (S/390) Unable to open disk vaddr - vaddr - format error detected.
internal error code from Block I/O
Explanation: The server encounters a format error on
System Service.
the specified disk.
because the connection to the CP DASD Block I/O
System Service has been severed with error code. User Response: Reformat the disk by using the
DSMDISK exec.
User Response: For a description of the severed error
ANR5025E (S/390) Disk vaddr has been reset and is
code, refer to the documentation for the CP DASD
no longer available.
Block I/O System Service in the CP Programming
Services publication for your specific operating system. Explanation: A disk is reset during operation because
a CP RESET or DETACH command has been entered
from the server’s console.
ANR5020E (S/390) Unable to open disk vaddr - device
is read-only. System Action: The disk is marked off-line.
Explanation: A disk cannot be opened for processing User Response: Ensure that the disk is properly
because it is accessible only as a read-only device. All reattached to the server’s virtual machine.
server disks must be accessible in read/write mode.
System Action: Server operation continues. ANR5026E (S/390) Open of data set dsn failed, return
code rc, reason code reason.
User Response: Ensure that the disk is properly
linked in read/write mode. Explanation: Data set dsn cannot be opened.
vaddr - internal error code on IUCV send. User Response: Verify that dsn is a VSAM linear data
set. If dsn is a valid VSAM linear data set, contact your
Explanation: The IUCV SEND error code is received service representative.
when the server attempts to perform I/O to a disk.
System Action: Server operation continues. ANR5027E (S/390) Open of DDNAME ddname failed,
User Response: For a description of the IUCV SEND
error code, refer to the IUCV documentation in the CP Explanation: The server is unable to open ddname
Programming Services publication for your specific ddname due to a lack of storage.
operating system.
User Response: Increase the region for the server or
lower the MAXSESSIONS parameter in the server

ANR5028E (S/390) • ANR5037E (S/390)
options file. There are three ways to do this: found in the Dynamic Allocation section of MVS/ESA
1. On VM, increase the size of the server’s virtual Programming: Authorized Assembler Services Guide.
machine. This requires that the default storage size System Action: Server operation continues.
be updated in the server’s CP directory entry.
2. On MVS, increase the size of the REGION
parameter on the JOB or EXEC statement of the JCL
used to start the server. ANR5033E (S/390) Close of ddname dsn failed, return
3. Reduce the maximum number of client sessions code rc, reason code reason.
permitted. To do this, edit the server options file Explanation: Data set dsn cannot be closed.
and reduce the value specified for the
MAXSESSIONS statement. Note that each client System Action: Server operation continues.
session causes an additional 64KB of memory to be
User Response: Verify that dsn is a VSAM linear data
allocated.
set. If dsn is a valid VSAM linear data set, contact your
4. Decrease the amount of space allocated to the service representative.
server’s database buffer pool. To do this, edit the
server options file and reduce the value specified
for the BUFPOOLSIZE statement. Note that each ANR5034E (S/390) Unable to allocate processor for
buffer pool page causes an additional 4KB of ddname dsn.
memory to be allocated. Explanation: The number of simultaneous tapes
Note that the server must be shut down (with the supported by the server has been exceeded.
HALT command) before changes can be made to the System Action: Server operation continues.
User Response: Contact your service representative
for a fix that allows additional tapes.
ANR5028E (S/390) Open of data set dsn failed; zero
pages in data set.
ANR5035E (S/390) Dynamic allocation of tape unit
Explanation: The VSAM linear data set dsn has no unit failed, return code rc, error code
space. This message appears when: error-code, info code info-code.
v you issue def vol|dbvol|logvol for a volume that has
not been formatted using the dsmfmt utility Explanation: The dynamic allocation of a tape unit
v you run the dsmfmt utility against a data set that is unit fails. The return code rc, error code error-code, and
too small information code info-code are in decimal and can be
v an existing data set has been corrupted found in the Dynamic Allocation section of MVS/ESA
Programming: Authorized Assembler Services Guide.
User Response: Run the dsmfmt utility, or reallocate
the VSAM linear data set as appropriate. User Response: Examine the MVS messages preceding
this message. They should explain the cause of the
allocation problem; otherwise, contact your service
ANR5030E (S/390) Dynamic allocation of data set dsn representative.
failed, return code rc, error code
error-code, info code info-code.
ANR5036E (S/390) Open of tape unit unit (ddname
Explanation: The dynamic allocation of data set dsn ddname) failed, return code rc.
fails. The return code rc, error code error-code and
information code info-code, are in decimal and can be Explanation: Open of ddname ddname fails.
found in the Dynamic Allocation section of MVS/ESA System Action: Server operation continues.
Programming: Authorized Assembler Services Guide.
User Response: Examine the MVS messages preceding
System Action: Server operation continues. this message. The ANR1401W message and the volume
User Response: Ensure that the data set dsn is name will explain the problem. If necessary, contact
available for allocation by the server. your service representative.
ANR5032E (S/390) Unable to free DDNAME dsn, ANR5037E (S/390) Unable to acquire processor, dsn.
return code rc, error code error-code, info Explanation: The number of simultaneous tapes
code info-code. supported by the server has been exceeded.
Explanation: The dynamic deallocation of data set dsn System Action: Server operation continues.
fails. The return code rc, error code error-code and
information code info-code are in decimal and can be User Response: Contact your service representative

ANR5038E (S/390) • ANR5046I (S/390)
for a fix that allows additional tapes. begin with an alpha character.
ANR5038E (S/390) Volume volume cannot be ANR5043E (S/390) Data set name dsn contains
processed this level of the operating qualifier qual that contains a character
system. that is not alphanumeric.
Explanation: The volume was created on a level of the Explanation: Data set dsn qualifier qual contains a
operating system that had BSAM Large Block support, character that is not alphanumeric. Data set qualifiers
and cannot be processed on this level of the operating must contain only alphanumeric characters.
system.
User Response: Specify data set name qualifiers that
User Response: Mark storage volume pool volumes contain only alphanumeric characters.
unavailable until the operating system is upgraded to
OS/390 R10 or higher. Do not use database backup or
ANR5044E (S/390) Cannot format data set dsn. Data
database dump volumes until the system is upgraded
set is not empty.
to OS/390 R10 or higher.
Explanation: The server will not format dsn because it
is not empty.
ANR5039E (S/390) Unable to open disk vaddr - IUCV
MAXCONN value exceeded. System Action: Server operation continues.
Explanation: The disk at virtual address vaddr cannot User Response: Verify that dsn is the correct data set
be opened due to a lack of IUCV connections. you’d like to format. The server formats empty data
sets only.
User Response: Increase the IUCV MAXCONN value
ANR5045E (S/390) Failed to open dataset dsn. Error
in the server CP directory entry and restart the server.
detected with the VSAM high-used
(VSAM high-used value) or high-allocated
ANR5040E (S/390) Data set name dsn contains (VSAM high-allocated value) values.
qualifier qual that is longer than 8
Explanation: The server did not open dataset dsn. The
characters.
VSAM high-used and high-allocated attributes are
Explanation: Data set dsn qualifier qual is too long. outside of the range expected by the server. The values
Data set qualifiers must be 1 to 8 characters long. may have been corrupted by moving the dataset using
anything other than a logical move.
System Action: Volume is marked read-only, or not
User Response: Specify data set name qualifiers with
brought on-line. Server operation continues.
a maximum of 8 characters.
User Response: Issue listcat entry(dsn) all to check the
high-used and high-allocated values. If you moved the
ANR5041E (S/390) Data set name dsn contains a null
dataset, verify that a logical move was performed.
qualifier.
Correct any user errors. Otherwise, contact your service
Explanation: Data set dsn contains null qualifier representative.
(either 2 consecutive periods or an ending period
without a subsequent qualifier). Data set qualifiers
ANR5046I (S/390) Dynamic allocation of tape unit
must be 1 to 8 characters long.
unit was cancelled by the operator.
Explanation: The dynamic allocation of a tape unit
User Response: Specify valid data set name qualifiers. unit was cancelled by the operator.
System Action: Server operation continues, tape
ANR5042E (S/390) Data set name dsn contains mount fails.
qualifier qual that does not begin, with
an alpha character.
Explanation: Data set dsn qualifier qual does not begin
with an alpha character. Data set qualifiers must start
with an alpha character.
User Response: Specify data set name qualifiers that

ANR5048E (S/390) • ANR5062E (S/390)
User Response: Check for MVS or system application
ANR5048E (S/390) Tape dataset allocation of block
messages preceding this message that indicate what
size changed from server value to current
caused the change to the logical record length. Check
value.
for any system exits that may change the logical record
Explanation: The server allocated the block size of its length (for example, IEFDB401). Ensure that the server
tape data set as server value, but it has been changed to can use its original value for the logical record length.
current value.
System Action: Current tape operation fails. ANR5060E (S/390) Unable to open VTAM ACB
Name name, rc code.
messages preceding this message that indicate what Explanation: The server cannot be identified to VTAM
caused the change to the block size. Check for any with the ACB name specified.
system exits that may change the block size (for
System Action: Server operation continues. Support
example, IEFDB401). Ensure that the server can use its
for the 3270 and SNALU6.2 COMMmethods is
original value for the block size.
disabled. The server periodically tries to open the ACB
and when successful, the 3270 and SNALU6.2
ANR5049E (S/390) Tape data set allocation of data set COMMmethods are enabled.
organization changed from hex server
User Response: For a description of the reported error
value to hex current value.
code, refer to VTAM Programming. If the ACB has been
Explanation: The server allocated the data set temporarily varied off, no action is required. The server
organization of its tape data set as server value, but it periodically tries to open the ACB. If the ACB is not
has been changed to current value in the data control defined and the COMMmethods 3270 or SNALU6.2 are
block (DCB). not supported for any clients, shut down the server
with the HALT command and set the LUNAME
System Action: Current tape operation fails.
statement in the server options file to *NONE*. If
User Response: Check for MVS or system application COMMmethods 3270 or SNALU6.2 are supported,
messages preceding this message that indicate what contact your VTAM (network) administrator to ensure
caused the change to the data set organization. Check that the ACB name has been properly defined in a
for any system exits that may change the data set member of SYS1.VTAMLST.
organization (for example, IEFDB401). Ensure that the
server can use its original value for the data set
ANR5061E (S/390) Unable to issue SETLOGON for
organization. See MVS/DFP V3R3 Macro Instructions for
VTAM ACB Name name, rc code, reas
Data Sets for valid values.
reason, rpl: rtncd return code fdb2 feedback.
ANR5050E (S/390) Tape data set allocation of record
informing VTAM that it is ready to accept a session.
format changed from hex server value to
hex current value. System Action: Server operation continues. Support
for the 3270 and SNALU6.2 COMMmethods is
Explanation: The server allocated the record format of
disabled. The server periodically tries to reissue the
its tape data set as server value, but it has been changed
SETLOGON instruction.
to current value in the data control block (DCB).
System Action: Current tape operation fails.
code, refer to VTAM Programming.
messages preceding this message that indicate what
ANR5062E (S/390) Unable to allocate number of bytes
caused the change to the record format. Check for any
bytes for VTAM control blocks.
system exits that may change the record format (for
example, IEFDB401). Ensure that the server can use its Explanation: The server is unable to access the storage
original value for the record format. See MVS/DFP it needs to support the COMMmethods 3270 and
V3R3 Macro Instructions for Data Sets for valid values. SNALU6.2.
System Action: The COMMmethods 3270 and
ANR5051E (S/390) Tape data set allocation of logical SNALU6.2 are disabled. If the storage for the global
record length changed from server value control block cannot be accessed, these COMMmethods
to current value. remain disabled until the server is shut down with the
HALT command and restarted. Otherwise, the server
Explanation: The server allocated the logical record
periodically tries to access the needed storage and
length of its tape data set as server value, but it has been
when successful, the 3270 and SNALU6.2
changed to current value.
COMMmethods are enabled. Server operation
System Action: Current tape operation fails. continues.

ANR5063E (S/390) • ANR5069E (S/390)
User Response: If the support for the COMMmethods
ANR5065E (S/390) Unable to open session with LU
3270 and SNALU6.2 is needed immediately, shut down
LU ID CID conversation ID, rc code reason
the server (with the HALT command), resolve the
reason, rpl: rtncd return code fdb2 feedback.
storage problem, and restart the server. If the
COMMmethods 3270 and SNALU6.2 are not used, shut Explanation: The server encounters an error while
down the server, set the LUNAME to *NONE*, and accepting an incoming session by way of a VTAM
restart the server. OPNDST instruction. The session is rejected.
ANR5063E (S/390) Unable to allocate session number
User Response: For a description of error code, refer
for LU LU ID.
to VTAM Programming.
Explanation: The server is unable to assign a session
number to the incoming session.
ANR5066E (S/390) Unable to close session with LU
System Action: Server operation continues. The server LU ID CID conversation ID, rc code reason
rejects the incoming session. reason, rpl: rtncd return code fdb2 feedback.
User Response: If the MAXSESSIONS statement in the Explanation: The server encounters an error while
server options file has been set correctly, the end-user ending a session.
(client) must wait until there is a free session before
retrying to connect with the server. If the
MAXSESSIONS statement is in error, shut down the User Response: For a description of the error code,
server, correct the MAXSESSIONS statement, restart the refer to VTAM Programming.
server, and have the client retry connecting with the
server.
ANR5067E (S/390) Unable to close VTAM ACB
Name name, rc code.
ANR5064E (S/390) Unable to allocate number of bytes
bytes for VTAM session with LU LU ID. Explanation: The server detects an error while closing
the ACB for the specified name.
Explanation: The server is unable to access the storage
needed to support the incoming 3270 dial-in session. System Action: The server proceeds with HALT
command processing.
incoming session is rejected. User Response: For a description of the reported error
server virtual machine. There are four ways to do this:
ANR5068E (S/390) Unable to receive on session with
1. On VM, increase the size of the server’s virtual LU LU ID CID conversation ID, rc code
machine. This requires that the default storage size reason reason, rpl: rtncd return code fdb2
be updated in the server’s CP directory entry. feedback sense sense code.
parameter on the JOB or EXEC statement of the JCL Explanation: The server encounters an error while
used to start the server. receiving data on the session.
3. Reduce the maximum number of client sessions System Action: Server operation continues, and the
permitted. To do this, edit the server options file session is ended.
MAXSESSIONS statement. Note that each client
allocated.
4. Decrease the amount of space allocated to the ANR5069E (S/390) Unable to send on session with
server’s database buffer pool. To do this, edit the LU LU ID CID conversation ID, rc code
server options file and reduce the value specified reason reason, rpl: rtncd return code fdb2
for the BUFPOOLSIZE statement. Note that each feedback sense sense code.
buffer pool page causes an additional 4 KB of Explanation: The server encounters an error while
memory to be allocated. sending data on the session.
Note that the server must be shut down (with the System Action: Server operation continues, and the
HALT command) to allow changes made to the server session is ended.
options file to take place.

ANR5070I (S/390) • ANR5085I (S/390)
ANR5070I (S/390) 3270 Dial-in driver terminated as
requested. User Response: Allocate additional storage to the
server virtual machine. There are four ways to do this:
Explanation: The server’s 3270 dial-in
communications driver is ending as requested. 1. On VM, increase the size of the server’s virtual
machine. This requires that the default storage size
System Action: Server operation continues with be updated in the server’s CP directory entry.
support for the 3270 COMMmethod disabled.
User Response: None. parameter on the JOB or EXEC statement of the JCL
used to start the server.
ANR5071W (S/390) Application resource name was 3. Reduce the maximum number of client sessions
defined to VTAM with APPC=NO. permitted. To do this, edit the server options file
Explanation: The specified VTAM application has MAXSESSIONS statement. Note that each client
been defined with APPC=NO. This definition, may be session causes an additional 64KB of memory to be
normal for your installation if SNALU6.2 is not used by allocated.
the clients. If this is true, then this message can be
4. Decrease the amount of space allocated to the
ignored.
System Action: Server operation continues. Support server options file and reduce the value specified
for the SNALU6.2 is disabled. for the BUFPOOLSIZE statement. Note that each
buffer pool page causes an additional 4KB of
User Response: If clients are using SNALU6.2, define memory to be allocated.
the VTAM application with APPC=YES. For the server
to recognize the new definition, you must stop the Note that the server must be shut down (with the
server by using the HALT command and restart the HALT command) before changes can be made to the
server. server options file.
ANR5080I (S/390) IUCV driver ready for connection ANR5083E (S/390) IUCV connection terminated -
with clients. error code accepting connect request.
Explanation: The server’s IUCV communications Explanation: The server’s IUCV communications
driver is ready to receive connection requests from driver is unable to accept a new connection from a
clients. client because error code has been received from the
IUCV ACCEPT function.
System Action: Server operation continues. The IUCV
is enabled. System Action: Server operation continues.
User Response: None. User Response: For a description of the IUCV

ACCEPT error code, refer to the IUCV documentation
in the CP Programming Services publication for your
ANR5081E (S/390) Unable to initialize IUCV driver - specific operating system, and the TCP/IP for MVS
code code. Programmer’s Reference for your version of TCP/IP.
Explanation: The server’s IUCV communications
driver cannot initialize itself because it received the ANR5084W (S/390) IUCV connection terminated -
error code code when entering the IUCV DECLARE server HALT in progress.
BUFFER function.
System Action: Server initialization fails. driver refuses a request for a client connection because
User Response: For a description of the reported error the HALT command has been entered.
code, refer to the IUCV documentation in the CP System Action: The server rejects the session and
Programming Services publication for your specific proceeds with HALT command processing.
operating system, and the TCP/IP for MVS Programmer’s
Reference for your version of TCP/IP. User Response: None.
ANR5082W (S/390) IUCV connection terminated - ANR5085I (S/390) IUCV driver unable to start. Server
insufficient memory. terminating.
Explanation: An IUCV connection request is refused Explanation: The server is unable to start the thread
by the server’s IUCV communications driver because to monitor the status of the IUCV communications
sufficient memory is not available to construct a driver.
session.
System Action: The server shuts down.

ANR5086I (S/390) • ANR5093E (S/390)
User Response: If sufficient storage is available when for the TCP/IP COMMmethod is enabled.
this error occurs, contact your service representative.
On MVS, ensure the region size parameter on the JCL
is at least 128MB. Otherwise if on VM, ensure that the
server virtual machine is at least 128MB in size. ANR5091E (S/390) Unable to initialize TCP/IP driver
- insufficient memory.
ANR5086I (S/390) IUCV driver terminated. Explanation: The server’s TCP/IP communications
driver is unable to initialize itself due to insufficient
Explanation: The IUCV communications driver has
memory (virtual storage).
shut down.
for the IUCV COMMmethod is disabled. The server User Response: Allocate additional storage to the
periodically tries to restart the IUCV communications server virtual machine. There are four ways to do this:
driver. 1. On VM, increase the size of the server’s virtual
User Response: None. machine. This requires that the default storage size
ANR5087I (S/390) IUCV driver starting.
parameter on the EXEC or JOB statement of the JCL
Explanation: The server is reporting that it is in the used to start the server.
process of starting the IUCV communications driver. 3. Reduce the maximum number of client sessions
System Action: The server attempts to initiate a permitted. To do this, edit the server options file
process that will monitor the status of the IUCV and reduce the value specified for the
communications driver. MAXSESSIONS statement. Note that each client
User Response: None. allocated.
ANR5088E (S/390) Unable to establish a wrap server’s database buffer pool. To do this, edit the
connection - return code code. server options file and reduce the value specified
for the BUFPOOLSIZE statement. Note that each
Explanation: The server is unable to establish an buffer pool page causes an additional 4KB of
IUCV connection with itself. memory to be allocated.
for the IUCV COMMmethod is disabled. The server Note that the server must be shut down (with the
will periodically retry the connect. HALT command) before changes can be made to the
User Response: For a description of this IUCV
CONNECT error code, refer to the IUCV
documentation in the CP Programming Services ANR5092E (S/390) Unable to initialize TCP/IP driver
publication for your specific operating system, and the - error creating acceptor socket.
TCP/IP for MVS Programmer’s Reference for your version
Explanation: The server’s TCP/IP communications
of TCP/IP.
driver is unable to create its critical listening socket,
and so TCP/IP communications cannot be initialized.
ANR5089I (S/390) IUCV driver terminated as
System Action: Server initialization continues. TCP/IP
requested.
communications initialization will be retried.
User Response: Check that TCP/IP is running, and
driver is ending as requested.
that TCPName in the options file matches the TCP/IP
System Action: Server operation continues with subsystem name you intend to use.
support for the ADMIUCV COMMmethod disabled.
User Response: None. ANR5093E (S/390) Unable to establish TCP
connection - accept error.
ANR5090I (S/390) TCP/IP driver ready for connection Explanation: The server’s TCP/IP communications
with clients on port port number. driver detects an internal error while attempting to
accept a new client connection.
driver is ready to receive connection requests from System Action: Server operation continues.
clients.
User Response: Report the error to your service
System Action: Server operation continues. Support representative.

ANR5094W (S/390) • ANR5101W (S/390)
ANR5094W (S/390) Unable to establish TCP ANR5097I (S/390) TCP/IP driver terminated as
connection - insufficient memory. requested.
Explanation: A TCP/IP connection request has been Explanation: The server’s TCP/IP communications
refused by the server’s TCP/IP communications driver driver is ending as requested.
because sufficient memory is not available to construct
System Action: Server operation continues with
a session.
support for the TCP/IP COMMmethod disabled.
server virtual machine. There are three ways to do this:
ANR5098I (S/390) TCP/IP driver starting.
1. On VM, increase the size of the server’s virtual
machine. This requires that the default storage size Explanation: The server is in the process of starting
be updated in the server’s CP directory entry. the TCP/IP communications driver.
2. On MVS, increase the size of the REGION System Action: The server tries to initiate a thread
parameter on the EXEC or JOB statement of the JCL that will monitor the status of the TCP/IP
used to start the server. communications driver.
3. Reduce the maximum number of client sessions User Response: None.
permitted. To do this, edit the server options file
MAXSESSIONS statement. Note that each client ANR5099E (S/390) Unable to initialize TCP/IP driver
session causes an additional 64KB of memory to be - error binding acceptor socket socket
allocated. number (rc = code).
4. Decrease the amount of space allocated to the Explanation: The server’s TCP/IP communications
server’s database buffer pool. To do this, edit the driver detects an internal error while attempting to
server options file and reduce the value specified bind the acceptor socket.
buffer pool page causes an additional 4 KB of System Action: The server ends the TCP/IP acceptor
memory to be allocated. process. Server operation continues without support for
the TCP/IP COMMmethod. The server tries to restart
Note that the server must be shut down (with the the acceptor process periodically.
HALT command) before changes can be made to the User Response: Report the error to your service
server options file. representative.
ANR5095W (S/390) Unable to establish TCP ANR5100E (S/390) Unable to initialize TCP/IP driver
connection - server HALT in progress. -error listening on acceptor socket socket
Explanation: The server’s TCP/IP communications number (rc = code).
driver refuses a request for a client connection because Explanation: The server’s TCP/IP communications
the HALT command has been entered. driver detects an internal error while attempting to
System Action: The server rejects the session and listen for a connection on the acceptor socket.
proceeds with HALT command processing. System Action: The server ends the TCP/IP acceptor
User Response: None. process. Server operation continues without support for
the TCP/IP COMMmethod. The server periodically
tries to restart the acceptor process.
ANR5096W (S/390) Unable to initialize OE BPX
TCP/IP driver - TCP/IP is down level. User Response: Report the error to your service
representative.
Explanation: Although the OS/390 is at V2R5 or
above the level of TCP/IP is below V3R4 level, and so
OE BPX TCP/IP communications cannot be initialized. ANR5101W (S/390) TCP/IP communications driver
terminating.
System Action: Server initialization continues. TCP/IP
communications is initialized, instead of OE BPX Explanation: The server’s TCP/IP communications
TCP/IP. driver has shut down.
User Response: Make sure the TCP/IP V3R4 or above System Action: Server operation continues without
is installed and running in the system if OE BPX support for the TCP/IP COMMmethod option. The
TCP/IP communication is to be used. server periodically tries to restart the TCP/IP
communications driver if the server is not in the
process of shutting down.

ANR5102W (S/390) • ANR5108E (S/390)
User Response: If the server is not in the process of
ANR5105I (S/390) Interlink TCPaccess driver is ready
shutting down, this message may indicate that the
for service on port interlink port number.
TCP/IP server is not available or that a server internal
error has occurred. Review the console log to determine Explanation: The server’s Interlink TCPaccess
if an internal error has occurred. If an internal error has communications driver is ready to receive connection
occurred, contact your service representative. If the requests from clients connected through Interlink
TCP/IP server is unavailable, correct the problem and TCPaccess.
the server will automatically reinitiate the TCP/IP
communications driver.
for the ICSSname and ICSPort server options is
enabled.
ANR5102W (S/390) Error received for connection
connection number (socket socket number).
TCP/IP driver will stop, then re-start.
ANR5106E (S/390) Unable to initialize Interlink
TCPaccess driver - error opening listen
driver received an error for the specified connection.
endpoint.
System Action: The server stops the TCP/IP
Explanation: The server’s Interlink TCPaccess driver
communications driver, and restarts the
is unable to create its critical listen endpoint; Interlink
TCPaccess communication cannot be initialized.
User Response: This process may take up to 5
minutes. If the condition persists, report the problem to
Interlink TCPaccess communications will be retried
every minute and this message will suppressed after
being issued three times.
ANR5103I (S/390) CLIO/S (IBM)TCP/IP driver ready
User Response: Check that TCPaccess is running and
for service on port clio port number.
that ICSSname, in the options file, matches the
Explanation: The server’s CLIO/S TCP/IP TCPaccess subsystem name you intend to use. The
communications driver is ready to handle connection ICSSname option should match the SSN parameter of
requests to and from AIX clients using COMMmethod the PROC statement in the TCPaccess startup
CLIO through an IBM TCP/IP host network. procedure. Refer to Interlink TCPaccess publications for
details.
for the TCPName and CLIOPort server options is
enabled. ANR5107E (S/390) Unable to initialize CLIO/S
(IBM)TCP/IP driver - error binding
acceptor socket socket number (rc = code).
ANR5104E (S/390) Unable to initialize CLIO/S
driver detects an error while attempting to bind the
(IBM)TCP/IP driver - error creating
acceptor socket.
listening socket.
System Action: The server ends the TCP/IP acceptor
Explanation: The server’s CLIO/S communication
process. Server operation continues without support for
driver is unable to create its critical listening socket;
the TCP/IP COMMmethod. The server tries to restart
therefore, CLIO/S (IBM)TCP/IP communication cannot
the acceptor process periodically.
be initialized.
User Response: Check that TCP/IP is running and
that TCPName, in the options file, matches the name of
CLIO/S (IBM)TCP/IP communication initialization will
the target TCP/IP address space.
be retried every minute. This message will be
suppressed after being issued for the third time;
however, attempts to initialize CLIO/S communications ANR5108E (S/390) The CLIO/S functions have not
will continue every minute until message ANR5103I is been linked into this module.
issued indicating CLIO/S driver is ready for service.
Explanation: The server cannot find the CLIO/S
User Response: Check that TCP/IP is running, and functions required to support CLIO (IBM)TCP/IP
that TCPName, in the options file, matches the name of communications.
the target TCP/IP address space.
System Action: The connection to the server fails.
User Response: The cause of this error is the omission
of the required post-SMP/E link-edit step to merge
CLIO functions from SYS1.SFCFLIB(FCFIADSM). Before

ANR5109E (S/390) • ANR5115W (S/390)
retrying the operation, ensure that your installation has User Response: Contact your service representative.
performed the required post install link-edit step. Find
the ADSM SAMPLIB and use member ANRCLIOK for
ANR5113W (S/390) 3270 dial-in session terminated -
an example of the required post-SMP/E link edit to
load ANRSERV with CLIO/S communication code.
Explanation: A 3270 dial-in connection request has
been refused by the server’s 3270 communications
ANR5109E (S/390) The CLIO/S communication driver
driver because sufficient memory is not available to
cannot be started.
construct a session.
Explanation: The server is unable to start the CLIO/S
communication driver because either TCPPort and
CLIOPort server options are the same value or User Response: Allocate additional storage to the
TCPName is coded with *NONE*. server virtual machine. There are three ways to do this:
System Action: The CLIO/S communication option 1. On VM, increase the size of the server’s virtual
will not be available and server initialization continues. machine. This requires that the default storage size
User Response: Check the server options file to ensure
CLIOPort and TCPPort values are different. If the
CLIOPort and TCPPort options are specified correctly,
used to start the server.
check the TCPName option to ensure *NONE* is not
coded for this option. Specify a unique CLIOPort value 3. Reduce the maximum number of client sessions
and ensure a valid TCPName parameter is coded to permitted. To do this, edit the server options file
allow the (IBM)TCP/IP CLIO/S communication driver and reduce the value specified for the
to start. CLIOPort has no default value; however, MAXSESSIONS statement. Note that each client
TCPPort and TCPName default to 1500 and TCPIP session causes an additional 64KB of memory to be
respectively. This message can be eliminated if CLIO/S allocated.
communication is not required by removing the 4. Decrease the amount of space allocated to the
CLIOPort option from the server option file and server’s database buffer pool. To do this, edit the
recycling the server. server options file and reduce the value specified
buffer pool page causes an additional 4 KB of
ANR5110I (S/390) 3270 Dial-in driver ready for
memory to be allocated.
connection with clients.
Explanation: The server’s 3270 dial-in Note that the server must be shut down (with the
communications driver is ready to receive connection HALT command) before changes can be made to the
requests from clients. server options file.
for the 3270 COMMmethod is enabled. ANR5114W (S/390) 3270 dial-in session terminated -
device does not support structured
fields.
Explanation: The server’s 3270 communications driver
ANR5111E (S/390) Unable to initialize 3270 dial-in
has refused a client connection request because the 3270
driver - error defining GRAF devices.
device initiating the connection does not support
Explanation: The server’s 3270 dial-in structured fields.
communications driver is unable to define one or more
CP GRAF devices, and is therefore unable to initialize
itself. User Response: Retry the 3270 connection from a
device that properly supports structured fields.
ANR5115W (S/390) 3270 dial-in session terminated -
emulator not supported.
ANR5112W (S/390) Unable to define additional
Explanation: The server’s 3270 dial-in
GRAF devices for dial-in.
communications driver has refused a connection
Explanation: The server’s 3270 dial-in request from a client, because the client’s 3270 emulator
communications driver is unable to define additional does not or is not configured for the level of 3270
CP GRAF devices, and may not be able to accept extended data stream support that the server requires.
subsequent connections from clients.

ANR5116I (S/390) • ANR5125E (S/390)
User Response: Retry the 3270 connection by using a
ANR5121I (S/390) APPC driver ready for connections
supported emulator program, such as the OS/2
with clients on resource resource name.
Communications Manager, or the IBM Personal
Communications/3270 program. Explanation: The server’s APPC communications
driver is reporting that it is ready to receive connection
requests from clients.
ANR5116I (S/390) 3270 Dial-in driver unable to start.
Server terminating. System Action: Server operation continues. Support
for the SNALU6.2 COMMmethod is enabled.
Explanation: The server is unable to start the thread
that monitors the status of the 3270 dial-in User Response: None.
System Action: The server shuts down. ANR5122I (S/390) APPC driver terminated.
User Response: If sufficient storage is available when Explanation: The APPC communications driver has
this error occurs, contact your service representative. shut down.
Otherwise for VM, ensure that the storage for the
server virtual machine is at least 128MB. For MVS,
for the SNALU6.2 COMMmethod is disabled. The
ensure the region size parameter on the JCL is at least
server periodically tries to restart the APPC
128MB.
ANR5117I (S/390) 3270 Dial-in driver terminated.
Explanation: The 3270 dial-in communications driver
ANR5123I (S/390) APPC driver starting.
has shut down.
Explanation: The server is reporting that it is in the
process of starting the APPC communications driver.
for the 3270 COMMmethod is disabled. The server
periodically tries to restart the 3270 dial-in System Action: The server tries to initiate a thread
communications driver. that will monitor the status of the APPC
ANR5118I (S/390) 3270 Dial-in driver starting.
ANR5124E (S/390) APPC driver unable to declare as
Explanation: The server is reporting that it is in the
resource resource name, rc code, reason
process of starting the 3270 dial-in communications
reason.
driver.
Explanation: The server cannot connect to the *IDENT
System Action: The server tries to initiate a process
(the Identify System Service) to identify itself as the
that will monitor the status of the 3270 dial-in
resource manager for the resource specified.
for the SNALU6.2 COMMmethod is disabled. The
server periodically tries to restart the APPC
ANR5120I (S/390) APPC driver unable to start. communications driver.
Server terminating.
User Response: Ensure that the following IUCV
Explanation: The server is unable to start the thread statement is present in the CP directory entry for the
that monitors the status of the APPC communications server: IUCV *IDENT appc-resource GLOBAL
driver. REVOKE.
ANR5125E (S/390) APPC connection terminated -
User Response: If sufficient storage is available when
error code accepting connect request.
this error occurs, contact your service representative.
Otherwise for VM, ensure that storage for the server Explanation: The server’s APPC communications
virtual machine is at least 128MB. For MVS, ensure the driver is unable to accept a new connection from a
region size parameter on the JCL is at least 128MB. client, because error code has been received from the
IUCV ACCEPT function.
User Response: For a description of the IUCV
ACCEPT error code, refer to the IUCV documentation

ANR5126W (S/390) • ANR5131I (S/390)
in the CP Programming Services publication for your retrying to connect with the server. If the
specific operating system. MAXSESSIONS statement is in error, shut down the
server, correct the MAXSESSIONS statement, restart the
server, and have the client retry to connect with the
ANR5126W (S/390) APPC connection terminated -
server.
server HALT in progress.
Explanation: The server’s APPC communications
ANR5129W (S/390) VTAM APPC (LU62) conversation
driver refuses a request for a client connection because
terminated - server HALT in progress.
the HALT command has been entered.
System Action: The server rejects the session and
driver rejects a conversation because the HALT
proceeds with HALT command processing.
command has been entered.
System Action: The server rejects the conversation
and proceeds with HALT command processing.
ANR5127W (S/390) APPC connection terminated -
Explanation: An IUCV connection request is refused
ANR5130W (S/390) VTAM APPC (LU62) conversation
by the server’s APPC communications driver because
(conversation ID) with LU LU ID
sufficient memory is not available to construct a
terminated - insufficient memory.
session.
Explanation: An APPC conversation has been
terminated by the server’s APPC communications
User Response: Allocate additional storage to the driver because sufficient memory is not available to
server virtual machine. There are three ways to do this: support this conversation.
1. On VM, increase the size of the server’s virtual System Action: Server operation continues. The
machine. This requires that the default storage size conversation is deallocated.
used to start the server. 1. Increase the size of the REGION parameter on the
JOB or EXEC statement of the JCL used to start the
3. Reduce the maximum number of client sessions
server.
permitted. To do this, edit the server options file
and reduce the value specified for the 2. Reduce the maximum number of client sessions
MAXSESSIONS statement. Note that each client permitted. To do this, edit the server options file
session causes an additional 64KB of memory to be and reduce the value specified for the
allocated. MAXSESSIONS statement. Note that each client
allocated.
server options file and reduce the value specified 3. Decrease the amount of space allocated to the
for the BUFPOOLSIZE statement. Note that each server’s database buffer pool. To do this, edit the
buffer pool page causes an additional 4 KB of server options file and reduce the value specified
memory to be allocated. for the BUFPOOLSIZE statement. Note that each
Note that the server must be shut down (with the memory to be allocated.
HALT command) before changes can be made to the
server options file. Note that the server must be shut down (with the
ANR5128E (S/390) Unable to allocate session number
for LU LU ID.
ANR5131I (S/390) APPC driver terminated as
Explanation: The server is unable to assign a session requested.
number to the incoming session.
System Action: Server operation continues. The server driver is reporting that it is terminating as requested.
rejects the incoming session.
System Action: Server operation continues with
User Response: If the MAXSESSIONS statement in the support for the SNALU6.2 COMMmethod disabled.
server options file has been set correctly, the end-user
(client) must wait until there is a free session before User Response: None.

ANR5132W (S/390) • ANR5204I (S/390)
ANR5132W (S/390) VTAM APPC (LU62) support is ANR5200S (S/390) Unable to connect to the *MSG
not available with current session. System Service, rc = code.
Explanation: The server’s VTAM APPC (LU6.2) Explanation: The server receives return code code from
communications driver is not available. Clients that use the IUCV CONNECT function when connecting to the
the SNALU6.2 communications method cannot *MSG System Service.
establish a session with the server. Refer to ANR5071W,
which was displayed prior to this message, for
additional information. If the SNALU6.2 User Response: Determine the cause of the error code,
communication method is not used, ignore this correct the problem, and restart the server. For a
message and message ANR5071W. description of the reported error code, refer to the
IUCV documentation in the CP Programming Services
System Action: Server operation continues without
publication, or the publication for your operating
support for the SNALU6.2 COMMmethod.
system that contains documentation for the IUCV
User Response: Verify that the server application is CONNECT function.
defined correctly to VTAM. APPC=YES must be
specified with the VTAM APPL macro when defining
ANR5201S (S/390) Error code from *MSG System
the server application when SNALU6.2 support is used.
Service path path ID.
Explanation: An error occurs on the IUCV path to the
ANR5133W (S/390) VTAM APPC (LU62) connect
*MSG System Service.
request rejected.
Explanation: A client’s VTAM APPC (LU6.2) connect
request was rejected because the LU6.2 communications User Response: Determine the cause of the error code,
driver is not available. This process may be the result correct the problem, and restart the server. For a
of the server application not being defined correctly to description of the reported error code, refer to the
VTAM. The application must be defined with IUCV documentation in the CP Programming Services
APPC=YES with the APPL macro to enable SNALU6.2 publication, or the publication for your operating
support on the server. system that contains IUCV documentation.
System Action: VTAM message IST663I and other
related messages are displayed; server operation ANR5202E (S/390) Unable to communicate with any
continues. Notify user ID.
User Response: Verify that the server application is Explanation: The server is unable to send a message
defined correctly to VTAM. APPC=YES must be to any user ID specified on the NOTIFY option in the
specified with the VTAM APPL macro when defining DSMSERV OPT file.
the server application.
ANR5140I (S/390) HTTP (IBM) communications is User Response: Have someone with an authorized
listening for clients on port port number. NOTIFY user ID log on to the system.
Explanation: The server’s HTTP (IBM) TCP/IP

communications driver is ready to receive connection ANR5203E (S/390) Unable to communicate with any
requests from Web clients. Mount Operator.
System Action: Server operation continues. Support Explanation: The server is unable to send a message
for Web Client HTTP communication is enabled. to any user ID specified on the MOUNTOP option in
the DSMSERV OPT file.
ANR5148I (S/390) HTTP (TCPaccess) driver is User Response: Have someone with an authorized
listening for clients on port port number. MOUNTOP user ID log on to the system.
Explanation: The server’s HTTP (TCPaccess) TCP/IP

communications driver is ready to receive connection ANR5204I (S/390) Autolog-response
requests from Web clients. Explanation: The result of the XAUTOLOG command
System Action: Server operation continues. Support for the mount exit virtual machine is Autolog-response.
for Web Client HTTP over TCPaccess is enabled. System Action: Server operation continues.

ANR5205I (S/390) • ANR5216I (S/390)
System Action: The running task waits until the
ANR5205I (S/390) From userid: msg.
mount is satisfied or canceled.
Explanation: The message msg has been received from
User Response: Use the DSMOP command to satisfy
a nonauthorized user ID userid.
or cancel the mount request.
User Response: If the user ID userid is a server mount ANR5212I (S/390) Request number: Mount devclass
operator, ensure that the user ID is in the MOUNTOP volume ID at vaddr mode via Exit Machine
list in the server options file. machine name.
Explanation: The server has requested a volume be
ANR5208I (S/390) Dismounting volume volser mounted.
(updated).
System Action: The running task waits until the
Explanation: The volume volser is dismounted after mount is satisfied or canceled.
being updated (written to) by the server. Possible
User Response: Use the DSMOP command to satisfy
reasons for the dismount include:
or cancel the mount request.
v The volume was found idle and the drive was
needed for another volume
v The volume is dismounted as a result of the ANR5213I (S/390) Request number: Mount devclass
DISMOUNT VOLUME command volume ID at vaddr mode (format) via Exit
v The volume is dismounted because of a previously Machine machine name.
reported error condition.
Explanation: The server has requested a volume with
System Action: Server operation continues. a specific format be mounted.
User Response: None. System Action: The running task waits until the
mount is satisfied or canceled.
ANR5209I (S/390) Dismounting volume volser User Response: Use the DSMOP command to satisfy
(read-only access). or cancel the mount request.
Explanation: The volume volser is dismounted after
read-only access by the server. Possible reasons for the ANR5214I (S/390) Request number: Mount devclass
dismount include: volume ID at vaddr mode waiting for
v The volume was found idle and the drive was available Exit Machine.
needed for another volume
v The volume is dismounted as a result of the Explanation: The server has requested a volume be
DISMOUNT VOLUME command mounted.
v The volume is dismounted because of a previously System Action: The running task waits until the
reported error condition. mount is satisfied or canceled.
System Action: Server operation continues. User Response: Use the DSMOP command to satisfy
User Response: None. or cancel the mount request.
ANR5210I (S/390) Request number: Mount devclass ANR5215I (S/390) Request number: Mount devclass
volume ID at vaddr mode within number of volume ID at vaddr mode (format) waiting
minutes minutes. for available Exit Machine.
Explanation: The server has requested a volume be Explanation: The server has requested a volume be
mounted. mounted.
System Action: The running task waits until the System Action: The running task waits until the
mount is satisfied or canceled. mount is satisfied or canceled.
User Response: Use the DSMOP command to satisfy User Response: Use the DSMOP command to satisfy
or cancel the mount request. or cancel the mount request.
ANR5211I (S/390) Request number: Mount devclass ANR5216I (S/390) Type volser is expected to be
volume ID at vaddr mode (format) within mounted (mode).
number of minutes minutes. Explanation: The server requires the volume volser be
Explanation: The server has requested a volume with in read/write or read/only mode as indicated by mode
a specific format be mounted. on a device type indicated by type.

ANR5217I (S/390) • ANR5228I (S/390)
ANR5223E (S/390) Deletion Exit for volser (storage
User Response: Locate the specified volume and be pool pool) failed - unknown Rc=rc.
prepared to make it available to the server.
Explanation: The deletion of volume volser in storage
pool pool fails.
ANR5217I (S/390) Dismounting volume volser -
retention minute mount retention
expired. User Response: Contact service representative.
Explanation: The volume volser is dismounted because
the MOUNTRETENTION value retention specified for ANR5224E (S/390) Deletion Exit for volser (storage
this device class has elapsed without activity on this pool pool) failed - ExitRc=rc,
volume. Rc=abend-indicated.
System Action: Server operation continues. Explanation: The deletion of volume volser in storage
pool pool fails.
ANR5218I (S/390) Detaching tape device vaddr - not User Response: If the exit return code rc is nonzero,
requested by server. check the documentation for the tape deletion exit
specified in the server options file. If the tape deletion
Explanation: The virtual address vaddr is detached
exit has abended, the indicator abend-indicated is
because it has not been requested by the server.
nonzero.
User Response: Check the virtual address requested ANR5225E (S/390) Deletion Exit for volser (storage
by the server for tape mounts. Reissue the CP ATTACH pool pool) failed - unable to get device
command and specify the correct virtual address. class information.
ANR5220I (S/390) Deleting type volser from Storage pool pool has failed due to an internal server error.
Pool pool.
Explanation: The volume volser of device type type has
been removed from storage pool pool.
ANR5226E (S/390) Deletion Exit for volser (storage
User Response: The server no longer uses the volume pool pool) failed - unable to start
specified. You can return the volume to the scratch background thread.
pool.
pool pool has failed due to an internal server error.
ANR5221I (S/390) Request: Delete type volser via Exit
Machine userid.
Explanation: The deletion of volume volser of device
type type is scheduled for Mount Exit Virtual Machine
userid as request number request. ANR5227E (S/390) Deletion Exit for volser (storage
pool pool) failed - insufficient memory.
pool pool fails due to lack of available storage.
ANR5222I (S/390) Request: Delete type volser waiting
for available Exit Machine. User Response: Increase the region or virtual machine
size for the server or reduce the MAXSESSIONS value
Explanation: The deletion of volume volser of device
in the server options file.
type type is waiting for an available Mount Exit Virtual
Machine userid as request number request.
ANR5228I (S/390) Deleting type volser from volume
history (previous use volume).
Explanation: The volume volser in device type type has
been deleted from the volume history. It was previously
used for previous use.

ANR5229W (S/390) • ANR5240E (S/390)
System Action: Server operation continues. User Response: None.
User Response: The server no longer tracks the
volume specified. You can return the volume to the ANR5232W (S/390) [XAUTOLOG] mountvm failed
scratch pool. with return code code.
Explanation: An error occurs during XAUTOLOG of a
ANR5229W (S/390) RACROUTE Delete failed for mount exit virtual machine.
volser, SAF return code System Authorized
System Action: The server retries the command. If the
Facility return code, return code RACF
command continues to fail, the mount exit machine is
return code, reason code RACF reason code.
marked off-line, and another mount exit machine is
Explanation: The deletion of the profile for volume used.
volser failed. The return codes and reason code are the
User Response: If the mount exit machine is placed in
result of a RACROUTE call. The codes are in hex. The
the off-line status, determine the cause, correct the
SAF return code is designated as x0yy where yy is the
problem, and use the DSMOP or administrator READY
SAF return code and x indicates the call as follows:
EXIT command to restore the mount exit machine to
x=1 RACROUTE REQUEST=DEFINE, TYPE=DELETE, the ready status.
CLASS='TAPEVOL', ENTITY=volume
x=2 RACROUTE REQUEST=STAT, CLASS='TAPEVOL' ANR5233E (S/390) Exit Machine mountvm taken
offline - nn command attempts failed.
x=3 RACROUTE REQUEST=DEFINE, TYPE=DELETE,
CLASS='DATASET', VOLSER=volume, ENTITY=tape Explanation: The number of XAUTOLOG attempts
dataset name has exceeded an internal threshold. The mount exit
virtual machine is no longer used.
The failure of the profile deletion is not an error if the
volume did not have a profile. No profile will exist for System Action: The server marks the mount exit
a volume if the server was not set up to request a virtual machine off-line.
profile (DEVCLASS parameter PROTECTION=NO)
User Response: To make the mount exit machine
when the volume was first used, or if the server never
available, determine the cause of the autolog failure.
used the volume.
Correct the problem and use the DSMOP or
System Action: Server operation continues. administrator READY EXIT command to restore the
mount exit machine to the ready status.
User Response: If the RACF profile exists for the
volume, check the system log for error messages to find
the cause of the problem. The profile for the volume ANR5234E (S/390) All Exit Machines are ″Offline″.
specified in the message will have to be deleted by
Explanation: All the defined mount exit virtual
issuing the appropriate RACF commands. For
machines have been placed in the off-line status by the
Information on the return codes and reason code, see
server.
External Security Interface (RACROUTE) Macro Reference
for MVS. System Action: Any mount requests by the server are
queued.
ANR5230I (S/390) Request number: Starting Exit User Response: Determine the cause of the autolog
Machine mountvm to mount devclass failures of all the mount exit virtual machines, correct
volume ID. any problems and use the DSMOP or administrator
READY EXIT command to make the mount exit
Explanation: The server has autologged a mount exit
machines available.
virtual machine to handle a mount request.
System Action: The server autologs a mount exit
ANR5240E (S/390) Request number: Mount for volume
virtual machine.
ID has timed out.
Explanation: The mount request has not been satisfied
in the requested time.
ANR5231I (S/390) Request number: Starting Exit
System Action: The server cancels the mount request.
Machine mountvm to delete devclass
volume ID. User Response: None.
Explanation: The server autologs a mount exit virtual
machine to handle a mount delete request.
System Action: The server autologs a mount exit
virtual machine.

ANR5241E (S/390) • ANR5258E (S/390)
ANR5241E (S/390) Exit Machine mountvm not logged ANR5254E (S/390) Command: CP command command
on, mount for volume ID cancelled. name failed.
Explanation: A mount exit virtual machine has logged Explanation: A DSMOP CANCEL REQUEST or a
off without satisfying the server’s mount request. DSMOP REPLY command fails.
System Action: The server cancels the mount request. System Action: The server tries to enter the CP
command command and receives a nonzero return code.
User Response: If you have entered a DSMOP
CANCEL REQUEST, force the mount exit virtual
ANR5250E (S/390) Command: User user ID not
machine to cancel the mount request with the FORCE
authorized.
option. To use the DSMOP CANCEL REQUEST
Explanation: An unauthorized user has attempted to command when running the mount exit, the server
enter a DSMOP command. must have FORCE privilege. If you have entered a
DSMOP REPLY command, attach the device to the
System Action: The server does not process the server with the ATTACH option. To use the DSMOP
command. REPLY command, the server must have ATTACH
User Response: If the user should be authorized, add privilege.
that user ID on the REPLYOP option in the DSMSERV
OPT file. ANR5255E (S/390) Command: No matching Exit
Machines were found ″Offline″.
ANR5251E (S/390) Command: Invalid request number Explanation: A READY EXIT command has been
- request number. issued and all Mount Exit Virtual Machines are ready.
Explanation: A DSMOP command has been entered System Action: Server operation continues.
with an incorrect request number.
command.
ANR5256E (S/390) Command: Invalid match pattern
User Response: Enter the command with the correct specified for Exit Machine name.
request number.
Explanation: A DSMOP READY command has been
entered specifying a user ID that is not a defined
ANR5252E (S/390) Command: No match found for this mount exit virtual machine.
request number.
Explanation: The request number specified by the command.
DSMOP command is not in the list of outstanding
mount requests. User Response: Enter the command and specify the
correct mount exit virtual machine name.
command.
ANR5257I (S/390) Command: No requests
User Response: Enter the command with the correct outstanding.
request number.
Explanation: A DSMOP QUERY MOUNTS command
has been entered when no mount requests are
ANR5253E (S/390) Request: Invalid device address - outstanding.
raddr.
Explanation: The response to server request number
request has specified an invalid real device address User Response: None.
raddr.
System Action: Server operation continues. ANR5258E (S/390) Command: Command not valid
when Exit is active.
User Response: Respond to the request again, by
specifying a valid real device address. Explanation: A DSMOP REPLY command has been
entered by a reply operator when the mount exit is
active.
command.
User Response: The DSMOP REPLY command is

ANR5259E (S/390) • ANR5268I (S/390)
invalid when the mount exit is used. When using
ANR5264I (S/390) Command not executed - password
mount exit machines, all mount requests are issued
has expired.
from the mount exit machines using your installation’s
procedures. Explanation: An administrative command has been
issued, but the administrator’s password has expired.
ANR5259E (S/390) Command: Command not valid System Action: Server operation continues.
when Exit is not active.
User Response: Update your password by starting an
Explanation: A DSMOP READY command or a administrative client session. Alternatively, the server
DSMOP QUERY EXITS command has been entered system administrator may use the UPDATE ADMIN
when the mount exit is not being used. command to update an administrator’s password.
command. ANR5265I (S/390) Command not executed -
administrator name is locked.
Explanation: An administrative command has been
issued, but the administrator’s user ID is locked from
ANR5260E (S/390) Command: Volume volume not
accessing the server.
found.
Explanation: A DISMOUNT VOLUME command was
issued, but the volume to be dismounted cannot be User Response: The server system administrator can
found. issue the UNLOCK ADMIN command to restore access
to a server administrative user ID.
User Response: Ensure that the correct volume name
ANR5266I (S/390) Command not executed -
is entered.
ANR5261E (S/390) Command: Volume volume is not
issued, but there is insufficient memory to execute the
″Idle″.
command.
Explanation: A DISMOUNT VOLUME command has
been issued, but the volume is in use and cannot be
dismounted. User Response: Increase the region or virtual machine
size for the server or lower the MAXSESSIONS
parameter in the server options file and restart the
User Response: If it is necessary to dismount the server.
volume, cancel the session or process that is using the
ANR5267I (S/390) Command not executed - internal
error detected.
ANR5262E (S/390) Command: Device raddr not found.
Explanation: A DISMOUNT DEVICE command has issued, but there is a detected internal processing error
been issued, but the device to be dismounted cannot be that prevents the command from executing.
found.
User Response: Look for preceding message
User Response: Ensure that the correct device has concerning access to administrative user ID information
been specified. within the server and contact your service
representative.
ANR5263E (S/390) Command: Device raddr is not

″Idle″. ANR5268I (S/390) Command not executed -
Explanation: A DISMOUNT DEVICE command has
been issued, but the device is in use and cannot be Explanation: An administrative command has been
dismounted. issued, but there is insufficient recovery log space to
complete the database transaction.
User Response: If it is necessary to dismount the
device, cancel the session or process that is using the User Response: To increase the amount of log space
volume, and reissue the command. available to the server, an authorized admininstrator

ANR5269I (S/390) • ANR5289I (S/390)
can add log volumes using the DEFINE LOGVOLUME mount exit virtual machine to ready.
command, and extend the size of the log using the
EXTEND LOG command.
ANR5284I (S/390) Requests outstanding:

ANR5269I (S/390) Command not executed -
insufficient database space. Explanation: The list of currently outstanding mount
requests follows.
issued, but there is insufficient database space to System Action: The server lists all outstanding mount
complete the database transaction. requests or the one specified on the DSMOP QUERY
command.
admininstrator can add database volumes using the ANR5285I (S/390) Exit Machine Status:
DEFINE DBVOLUME command, and extend the size of
the database using the EXTEND DB command. Explanation: The list of mount exit virtual machine
status follows.
ANR5270I (S/390) SMFWTM macro return code 40 System Action: The server lists the status of all mount
(buffer shortage). exit virtual machines or the status of the one specified
on the DSMOP QUERY command.
Explanation: SMFWTM completed with return code
40. User Response: None.
System Action: The server continues to operate.

ANR5286I (S/390) Exit Machine mountvm: ″Ready″.
User Response: Increase SMF buffer limit or disable
server accounting. Explanation: The status of a mount exit virtual
machine is ready.
ANR5280I (S/390) Command accepted. System Action: Server operation continues.
Explanation: A DSMOP REPLY command is accepted. User Response: None.
System Action: The server processes the DSMOP

REPLY command. ANR5287I (S/390) Exit Machine mountvm: ″Busy″.
User Response: None. Explanation: The status of a mount exit virtual

machine is busy.
ANR5281I (S/390) Request request number for volume System Action: Server operation continues.
ID canceled by user ID. User Response: None.
Explanation: A mount request is successfully canceled.
System Action: The system cancels the mount request. ANR5288I (S/390) Exit Machine mountvm: ″Offline″.
User Response: None. Explanation: The status of a mount exit virtual

machine is off-line.
ANR5282I (S/390) Request request number for volume System Action: Server operation continues.
ID cancelled (PERM) by user ID. User Response: None.
Explanation: A mount request is successfully canceled
with the PERM option. ANR5289I (S/390) Volume volume (class class)
System Action: The system cancels the mount request mounted mode on raddr, status: ″Idle″.
and marks the volume as unavailable. Explanation: Volume volume, which is of device class
User Response: None. class and is mounted at address raddr in mode mode, is
eligible for dismounting or reuse.
ANR5283I (S/390) Exit Machine mountvm status set to System Action: Server operation continues.
″Ready″. User Response: None.
Explanation: A DSMOP READY command has been
entered.
System Action: The server changes the status of the

ANR5290I (S/390) • ANR5302I (S/390)
ANR5290I (S/390) Volume volume (class class) ANR5296I (S/390) Volume volume (class class)
mounted mode on raddr, status: ″In Use″. mounted mode, status: ″Dismounting″.
Explanation: Volume volume, which is of device class Explanation: Volume volume, which is in device class
class and is mounted at address raddr in mode mode, is class in mode mode, is in the process of dismounting.
in use by the server.
ANR5297I (S/390) Volume volume (class class)
ANR5291I (S/390) Volume volume (class class) mounted mode, status: ″In Retry″.
mounted mode on raddr, status:
Explanation: Volume volume, which is in device class
″Dismounting″.
class in mode mode, is currently in RETRY. An attempt
Explanation: Volume volume, which is in device class is being made to re-establish communications with
class and is mounted at address raddr in mode mode, is another server. If the volume remains in retry status for
in the process of dismounting. the amount of time specified by the device class retry
period, the operation will fail and the volume will be
automatically dismounted.
ANR5292I (S/390) number volume(s) found.
Explanation: A QUERY MOUNT command has been
ANR5300I (S/390) Verifying volume label volume ID
issued; number volumes are mounted.
on device real address.
Explanation: The server is verifying the volume label
User Response: None. of a mounted read/write volume again prior to
dismounting the volume.
ANR5293I (S/390) Cancelling mount for volume System Action: The server performs the reverification
volume. of the volume label as an integrity check of the volume.
Explanation: A CANCEL MOUNT command has been User Response: None.

issued for volume volume. The CANCEL command is
being processed.
ANR5301I (S/390) Request number: Verifying volume
System Action: Server operation continues. label volume ID on device device.
User Response: Query the activity log to verify that Explanation: The server is verifying the volume label
the mount request has been cancelled. of a mounted volume during the mount process.
System Action: The server ensures that the volume
ANR5294I (S/390) Volume volume (class class) mounted is acceptable.
mounted mode, status: ″Idle″.
class in mode mode, is eligible for dismounting or reuse.
ANR5302I (S/390) Request number: Assigning volume
System Action: Server operation continues. volume ID to SCRTCH.
User Response: None. Explanation: The server has assigned the mounted
volume to be used as the requested scratch volume.
ANR5295I (S/390) Volume volume (class class) System Action: The server dynamically adds the
mounted mode, status: ″In Use″. volume label of the mounted volume to the storage
pool.
class in mode mode, is in use by the server. User Response: None.


ANR5303I (S/390) • ANR5311E (S/390)
ANR5303I (S/390) Request number: Assigning volume ANR5308E (S/390) Request number: Volume on real
volume ID to EXPORT. address is not write protected.
Explanation: The server has assigned the mounted Explanation: The mounted volume is not write
volume to be used as the requested export volume. protected.
System Action: The server uses the volume for the System Action: The server dismounts the volume,
EXPORT operation. detaches the device, and requests the original volume
again.
User Response: Disable the volume for writing and
reply to the mount again.
volume ID to IMPORT.
ANR5309E (S/390) Request number: Volume on real
Explanation: The server has assigned the mounted
address has no VOL1 label.
volume to be used as the requested import volume.
Explanation: The mounted volume does not have a
System Action: The server uses the volume for the
standard label.
IMPORT operation.
System Action: The server dismounts the volume,
detaches the device, and requests the original volume
again.
ANR5305E (S/390) Request number: Device real address
User Response: Make sure you are mounting the
is not a supported devclass device.
correct volume. All volumes must have a standard
Explanation: A device is attached to the server to VOL1 label.
satisfy a mount request, but it is the wrong device
class. For example, a CARTRIDGE device has been
ANR5310E (S/390) Volume on real address has no
used when the request is for a REEL device.
VOL1 label - volume integrity
System Action: The server dismounts the volume, compromised.
Explanation: During volume unmount label
again.
reverification, the server finds no VOL1 label.
User Response: Make sure the device used to satisfy a
System Action: The server marks the volume as
mount request is the same type as the device requested.
unavailable.
User Response: The volume cannot be used because
ANR5306E (S/390) Request number: Device real address
the VOL1 label has been overwritten. All active data on
not capable.
the volume cannot be recovered. Delete the volume
Explanation: The server requested a volume with a from the storage pool with the DELETE VOLUME
specific density or format. The device used to satisfy command by using the DISCARD=YES option. To use
the mount cannot write using the requested density or this volume again, the volume must be initialized with
format. a VOL1 label. The volume may then be redefined in the
storage pool.
again. ANR5311E (S/390) Request number: Volume label on
raddr (volume ID found) does not match
User Response: Mount the volume on a device volume ID expected.
capable of the requested density or format.
Explanation: During mount processing, the volume ID
read on the mounted volume does not match the
ANR5307E (S/390) Request number: Volume on real specifically requested partially full volume.
address is write protected.
Explanation: The mounted volume is not enabled for detaches the device, and requests the original volume
writing. again.
System Action: The server dismounts the volume, User Response: Make sure you are mounting the
detaches the device, and requests the original volume correct volume.
again.
User Response: Enable the volume for writing and
reply to the mount again.

ANR5312E (S/390) • ANR5322I (S/390)
ANR5312E (S/390) Volume label on raddr (volume ID ANR5317I (S/390) Make device real address ready.
found) does not match volume ID expected
Explanation: The device is in a not ready condition.
- volume integrity compromised.
System Action: The server sends an intervention
Explanation: During volume unmount label
required message to the mount operator user IDs listed
reverification, the server finds a different VOL1 label.
in the DSMSERV OPT file.
System Action: The server marks the volume as
User Response: Make the device ready.
unavailable.
User Response: The volume cannot be used because
ANR5318I (S/390) Intervention cleared on device real
the VOL1 label has been overwritten by a different
address.
VOL1 label. All active data on the volume cannot be
recovered. Delete the volume from the repository with Explanation: The device requiring operator
the DELETE VOLUME command by using the intervention is now ready.
NORECLAIM option. To use this volume again, the
volume must be initialized with a VOL1 label. The System Action: The task waiting for the device
volume may then be redefined in the repository. continues.
ANR5313I (S/390) Request number: Mount for volume
ID complete on device real address. ANR5319I (S/390) Intervention required on device
Explanation: A volume mount has successfully real address.
completed. Explanation: The device requires operator
System Action: The task waiting for a volume mount intervention.
resumes. System Action: The task waits until the device is
User Response: None. made ready.
User Response: Make the device ready.
ANR5314E (S/390) Request number: Permanent I/O
error on device real address. ANR5320I (S/390) Volume volume ID already in use.
Explanation: A permanent I/O error occurred when Explanation: A tape volume has been mounted for use
the device was opened. by the server; after mounting the volume, the server
System Action: The server dismounts the volume, determined that the volume was already in use by the
detaches the device, and requests the original volume server and could not be used to satisfy the current
again. mount request.
User Response: Mount the volume on a different System Action: The server dismounts the volume,
device. detaches the device, and reissues the original request.
User Response: Mount a volume not already in use
ANR5315E (S/390) Read Data Check on device real by the server.
address.
Explanation: A data check occurred during a read ANR5321I (S/390) End of volume reached for volume
operation. ID on device real address.
System Action: The server redrives the I/O by using Explanation: During processing of a read/write tape
Diagnose X'20' or Diagnose X'A8'. volume, the end of the tape volume has been reached.
User Response: None. System Action: The volume is marked read-only and
kept mounted for later use.
ANR5316E (S/390) Write Data Check on device real User Response: None.
address.
Explanation: A data check occurred during a write ANR5322I (S/390) Permanent error on volume volume
operation. ID on device real address.
System Action: The server redrives the I/O by using Explanation: During processing of a tape volume, a
Diagnose X'20' or Diagnose X'A8'. permanent I/O error occurred.
User Response: None. System Action: The server places the volume in an
I/O error state. If the volume was being used for
writing, it is marked read-only.

ANR5323I (S/390) • ANR5331S (S/390)
volume ID to LOADDB.
ANR5323I (S/390) Assigning volume volume ID to
Explanation: The server assigns the mounted volume
SCRTCH.
for use as the requested LOADDB volume.
volume to be used as the requested scratch volume.
LOADDB operation.
System Action: The server dynamically adds the
volume label of the mounted volume to the storage
pool.
DUMPDB.
for use as the requested DUMPDB volume.
EXPORT.
DUMPDB operation.
volume to be used as the requested export volume.
EXPORT operation.
LOADDB.
for use as the requested LOADDB volume.
IMPORT.
LOADDB operation.
volume to be used as the requested import volume.
IMPORT operation.
ANR5331S (S/390) Volume volume ID damaged -
recovery required.
Explanation: The server detects an error on the
ANR5326E (S/390) Volume label on raddr (volume ID
specified volume. The volume has been unexpectedly
found) does not match volume ID expected.
repositioned during write processing. Data may have
Explanation: During mount processing, the volume ID been lost.
read on the mounted volume does not match the
System Action: The server halts the process that is
specifically requested partially full volume.
using the volume and marks the volume as read-only.
User Response: For EXPORT, DBBACKUP, or
DBDUMP tapes, restart the export, backup, or dump
again.
operation. Do not use the tape for an IMPORT,
User Response: Make sure you are mounting the DBRESTORE, or DBLOAD operation. If the tape is a
correct volume. storage pool volume, you can attempt to recover the
data with the following steps:
ANR5327I (S/390) Request number: Assigning volume 1. To identify any missing data, issue the AUDIT
volume ID to DUMPDB. VOLUME command by specifying FIX=NO.
2. If recoverable data exists on the tape, delete
Explanation: The server has assigned the mounted references to the missing data from the database by
volume to be used as the requested DUMPDB volume. issuing the AUDIT VOLUME command and
System Action: The server uses the volume for the specifying FIX=YES.
DUMPDB operation. 3. Issue the MOVE DATA command to remove all
data from the damaged tape after the AUDIT
(FIX=YES) has completed.
NOTE: Issuing an audit command on a damaged
volume can result in a large number of logged
messages.

ANR5332I (S/390) • ANR5351E (S/390)
current Database Backup volume, a full backup must
be done to insure a complete backup exists.
volume ID to DBBKUP.
v If the volume is a storage pool volume, audit the
Explanation: The server assigns the mounted volume volume. If it is a primary volume and a copypool
for use as the requested DBBKUP volume. exists, restore the volume. If it is a copypool volume,
System Action: The server uses the volume for the backup the storage pool again to insure a backup
DBBKUP operation. copy exists for all files.
User Response: None. It is strongly recommended that you use the

DEVCLASS EXPIRATION or RETENTION parameter
ANR5333I (S/390) Assigning volume volume ID to to protect your tapes and prevent damage to tapes you
DBBKUP. create in the future.

for use as the requested DBBKUP volume. ANR5336E (S/390) Volume volume ID must be
read-only on 3590 device.
DBBKUP operation. Explanation: The server requests a volume in a mode
other than read-only. The 3590 device that is used to
User Response: None. satisfy the mount cannot be used to write to the
volume.
ANR5334W (S/390) Volume volume ID reached end of System Action: The server cancels the current
tape. operation.
Explanation: The server has detected end of tape for User Response: Update the volume access to
the specified volume. The volume reached the end of READONLY or insure that a device of the type used to
tape before the maximum capacity value specified in create the volume is used to satisfy the mount.
the device class was reached.
System Action: The server requests another volume if ANR5337I (S/390) Assigning volume volume ID to
one is available. The current process stops writing to backup set.
the specified volume.
User Response: Reduce the maximum capacity in the volume to be used as the requested backup set volume.
device class. The QUERY VOLUME command will
indicate the actual capacity of the volume after it is full. System Action: The server uses the volume for the
Use the UPDATE DEVCLASS command to change the backup set operation.
maximum capacity for the device class. User Response: None.
ANR5335E (S/390) Volume volume ID already used. ANR5350E (S/390) Error locating block block number
Explanation: A tape volume is mounted as scratch for on device real address.
use by the server. After mounting the volume, the Explanation: A Locate Block CCW failed.
server determines that the volume has already been
used by the server and cannot be used to satisfy the System Action: The server marks the volume in an
current mount request. Mounting the volume as scratch I/O error condition and requests another volume be
may have destroyed some of the data previously mounted.
written on that volume. User Response: This failure may be due to a hardware
System Action: The server dismounts the volume, problem. Reset the error condition with the UPDATE
detaches the device, and reissues the original request. VOLUME command. If the problem persists, use the
DELETE VOLUME command with the DISCARD=NO
User Response: Mount a volume not already in use option to remove the volume from the storage pool.
by the server. The damaged volume must be replaced,
restored, or deleted from the volume history file.
ANR5351E (S/390) Error reading BlockID on device
v If the volume is an Export, Database Dump or
real address.
Database Backup volume that contains data that is
no longer needed, use the DELETE VOLHISTORY Explanation: A Read Block ID CCW failed.
command to make the volume available to the server
for reuse. System Action: The server marks the volume in an
I/O error condition and requests another volume be
v If the volume mounted is an Export or Database mounted.
Dump, the tapes are no longer good and another
export or dump must be taken. If the tape is a User Response: This failure may be due to a hardware

ANR5352E (S/390) • ANR5359E (S/390)
problem. Reset the error condition with the UPDATE
ANR5356E (S/390) Unload cartridge on device real
VOLUME command. If the problem persists, use the
address.
option to remove the volume from the storage pool. Explanation: The drive cannot maintain tape tension
and control tape movement during an unload
operation.
ANR5352E (S/390) Synchronize failed on device real
address. System Action: The task waits until the drive is made
ready. An intervention required message is sent to the
Explanation: A Synchronize CCW failed.
mount operator user IDs.
System Action: The server marks the volume in an
User Response: Make the drive ready.
I/O error condition, and requests another volume be
mounted.
ANR5357E (S/390) Manual Rewind/Rewind-Unload
User Response: Reply to the new mount request.
Reset the error condition with the UPDATE VOLUME
command. The integrity of the original volume may Explanation: The Rewind Unload switch or the
have been compromised. To delete the volume, issue Rewind switch on the drive has been pressed.
the DELETE VOLUME command with the
System Action: The server verifies the volume label
DISCARD=NO option.
and attempts to reposition the tape and continue
operation. If the volume label verification fails, the
ANR5353E (S/390) Load Display failed on device real server marks the volume in the unavailable state. If the
address. reposition fails, the server marks the volume in the I/O
error state.
Explanation: A Load Display CCW failed.
User Response: If the server succeeds in its recovery,
System Action: Server operation continues. No text is
no action is required. If recovery is unsuccessful, you
loaded into the display window.
can reset the error status of the volume with the
User Response: None. UPDATE VOLUME command. Volume integrity may
have been compromised. Issue the DELETE VOLUME
command with the DISCARD=NO option to try to
ANR5354E (S/390) Block block number sequence error recover any data.
Explanation: During a read operation, the block ID of ANR5358E (S/390) Request number: I/O Error at
the block being read does not match the block ID beginning of tape on real address.
stored in the data block header.
Explanation: An I/O error has occurred attempting to
System Action: The server places the volume in an mount a tape volume; the beginning of the volume
I/O error state. cannot be detected.
User Response: The integrity of the volume may have System Action: The server places the volume in an
been compromised. Reset the error condition with the I/O error state.
UPDATE VOLUME command and attempt the
operation on a different tape drive. If the problem User Response: The integrity of the volume may have
persists, you can delete the volume with the DELETE been compromised. Reset the error condition with the
VOLUME command, by using the DISCARD=NO UPDATE VOLUME command and attempt the
option. operation on a different tape drive. If the problem
persists, you can delete the volume with the DELETE
VOLUME command, by using the DISCARD=NO
ANR5355E (S/390) Reload cartridge on device real option.
address.
Explanation: The cartridge is not inserted correctly, or ANR5359E (S/390) Request number: Cartridge Length
the tape is not processed correctly. Error on device real address.
System Action: The task waits until the drive is made Explanation: A tape cartridge has been mounted that
ready. An intervention required message is sent to the is too short for processing on the drive.
mount operator user IDs.
User Response: Make the drive ready. I/O error condition and requests another volume be
mounted.
User Response: Reply to the new mount request. If
necessary, reset the error condition with the UPDATE

ANR5360E (S/390) • ANR5366E (S/390)
VOLUME command. The integrity of the original
ANR5363E (S/390) Request number: Cartridge
volume may have been compromised. To delete the
Compaction Incompatible on device real
volume, issue the DELETE VOLUME command with
address.
the DISCARD=NO option.
Explanation: A tape cartridge has been mounted on a
drive but the tape compression algorithm ID is not
ANR5360E (S/390) Request number: Cartridge Length
compatible with the drive.
Incompatible on device real address.
drive and the tape is too long to be processed on the
mounted.
drive or has been initialized to the wrong length.
mounted.
User Response: Reply to the new mount request. If volume, issue the DELETE VOLUME command with
necessary, reset the error condition with the UPDATE the DISCARD=NO option.
ANR5364E (S/390) Record sequence error on device
real address.
the DISCARD=NO option.
Explanation: During processing of a tape volume, the
record tape number read does not match that expected
ANR5361E (S/390) Request number: Cartridge Format
by the drive.
Incompatible on device real address.
I/O error condition.
drive, but the tape format cannot be processed on the
drive. User Response: This failure may be due to a hardware
problem. Reset the error condition with the UPDATE
VOLUME command. If the problem persists, use the
mounted.
option to remove the volume from the storage pool.
ANR5365E (S/390) Volume fenced on device real
address.
volume, issue the DELETE VOLUME command with Explanation: During processing of a tape volume,
the DISCARD=NO option. errors have occurred that caused the tape drive to lose
the ability to process the volume.
ANR5362E (S/390) Request number: Cartridge Length System Action: The server marks the volume in an
Violation on device real address. I/O error condition.
Explanation: A tape cartridge has been mounted on a User Response: Unload and reload the tape to reset
drive but the tape is too long to be processed on the the drive. Reset the error condition with the UPDATE
drive. VOLUME command. This failure may be due to a
hardware problem. If the problem persists, use the
option to remove the volume from the storage pool.
mounted.
ANR5366E (S/390) Request number: Volume volume ID
data set name ″label dsn″ in HDR1 label
cannot be overwritten with Export data
set name ″export dsn″.
the DISCARD=NO option. Explanation: During mount processing of an EXPORT
tape volume, the server encountered a nonblank data
set name in the HDR1 label. Normally, the server
writes the export dsn in this field.

ANR5367I (S/390) • ANR5372I (S/390)
ANR5370E (S/390) Invalid block header on device
again.
real address.
User Response: Most tape volume initialization
Explanation: During a read operation, the block
programs only write VOL1 label. If your tape volume
header of the block read does not contain data
initialization program also writes a HDR1 label, the
recognized by the server.
data set name in the HDR1 label must be blank. Be
sure that the volume in question is the proper tape System Action: The server may place the volume in
volume, and reinitialize it with only a VOL1 label, or an I/O error state.
with a blank data set name in the HDR1 label.
User Response: The integrity of the volume may have
been compromised. Reset the error condition with the
ANR5367I (S/390) Request number: Volume volume ID UPDATE VOLUME command and attempt the
data set name ″label dsn″ in HDR1 label operation on a different tape drive. If the problem
will be overwritten with Export data set persists, try to audit the volume by using the AUDIT
name ″export dsn″. VOLUME command to see if any files on the volume
can be recovered. If not, you can delete the volume
Explanation: During mount processing of an EXPORT
with the DELETE VOLUME command, by using the
tape volume, the server encountered a nonblank data
DISCARD=NO option.
set name in the HDR1 label. This data set name will be
overwritten with export dsn. If a LOADDB operation was being performed, specify
the command syntax by either using a ddname or by
System Action: The server continues with mount
specifying a device class name. You must use the same
processing.
method that was used when the data base was
User Response: None. originally dumped. Otherwise, this error message is
displayed. Try loading the data base by using the other
method of syntax (ddname). Also, verify that you
ANR5368E (S/390) Request number: Volume volume ID specified the correct volume name. The integrity of the
data set name ″label dsn″ in HDR1 label volume may have been compromised. In this case, the
cannot be overwritten with DUMPDB volume cannot be used by the LOADDB operation.
data set name ″dumpdb dsn″.
Explanation: During mount processing of an ANR5371E (S/390) Request number: Volume volume ID
DUMPDB tape volume, the server encountered a data set name ″label dsn″ in HDR1 label
nonblank data set name in the HDR1 label. Normally, cannot be overwritten with DBBKUP
the server would write the dumpdb dsn in this field. data set name ″dbbkup dsn″.
System Action: The server dismounts the volume, Explanation: During mount processing of a DBBKUP
detaches the device, and requests the original volume tape volume, the server encountered a nonblank data
again. set name in the HDR1 label. Normally, the server
User Response: Most tape volume initialization writes the dbbkup dsn in this field.
programs only write a VOL1 label. If your tape volume System Action: The server dismounts the volume,
initialization program also writes a HDR1 label, the detaches the device, and requests the original volume
data set name in the HDR1 label must be blank. Be again.
sure the volume in question is the correct tape volume,
and reinitialize it with only a VOL1 label, or with a User Response: Most tape volume initialization
blank data set name in the HDR1 label. programs only write VOL1 label. If your tape volume
initialization program also writes a HDR1 label, the
data set name in the HDR1 label must be blank. Be
ANR5369I (S/390) Request number: Volume volume ID sure that the volume in question is the proper tape
data set name ″label dsn″ in HDR1 label volume, and reinitialize it with only a VOL1 label, or
will be overwritten with DUMPDB data with a blank data set name in the HDR1 label.
set name ″dumpdb dsn″.
Explanation: During mount processing of an ANR5372I (S/390) Request number: Volume volume ID
DUMPDB tape volume, the server encountered a data set name ″label dsn″ in HDR1 label
nonblank data set name in the HDR1 label. This data will be overwritten with DBBKUP data
set name will be overwritten with dumpdb dsn. set name ″dbbkup dsn″.
System Action: The server continues with mount Explanation: During mount processing of a DBBKUP
processing. tape volume, the server encountered a nonblank data
User Response: None. set name in the HDR1 label. This data set name will be
overwritten with dbbkup dsn.

ANR5373I (S/390) • ANR5412I (S/390)
System Action: The server continues with mount will fail and the tape will be dismounted.
processing.
User Response: Check the tape drive.
ANR5404I (S/390) SERVER volume volume name
ANR5373I (S/390) Cannot allocate tape drive of unit mounted.
type unit type for tape volume ID. Reply
Explanation: The server has mounted the given
C (cancel), R (retry), or W (wait).
volume.
Explanation: The server attempts to allocate a tape
System Action: Read or write operations, or both, will
drive. The allocation attempt fails because no
commence for the volume.
acceptable tape drive is available. An acceptable tape
drive has the unit type indicated in the message. User Response: None.
Before more attempts are made to allocate the tape
drive, the operator is prompted to indicate whether or ANR5405I (S/390) End-of-volume reached for
not the tape drive allocation request can be satisfied. SERVER volume volume name.
The unit type and the VOLSER of the tape volume
volser to be used for the pending request are provided Explanation: The server has detected an
in the message text. end-of-volume condition for the given volume.
System Action: If the operator replies ’R’ (meaning System Action: The volume is marked full. If more
retry), the server will retry the tape drive allocation. If data must be stored, the server accesses another
no acceptable drive is available after retrying the volume.
allocation, the server will reissue this message. User Response: None.
If the operator replies ’W’ (meaning wait), the server
will retry the tape drive allocation. If the allocation ANR5410I (S/390) FILE volume volume name
request cannot be satisfied immediately, the server will mounted.
wait while MVS Allocation Recovery issues message
IEF238D. After IEF238D is issued, none of the following Explanation: The server has opened the given file to
can occur in the server until the allocation completes or simulate a tape volume.
is canceled: System Action: Read or write operations, or both, will
v dynamic allocations or deallocations commence for the volume.
v file opens or closes User Response: None.
v tape volume changes between read mode and write
mode
ANR5411I (S/390) End-of-volume reached for FILE
volume volume name.
If the operator replies ’C’ (meaning cancel), the server
will fail the tape drive allocation and its associated Explanation: The server has detected an
server request. end-of-volume condition for the given volume.
System Action: The volume is marked full. If more
Any other reply will cause the server to reissue this
data must be stored, the server accesses another
message. Determine if there are any tape drives which
volume.
can be used to satisfy this request (either online or
offline) prior to responding to this message. User Response: None.
ANR5412I (S/390) FILE volume volume name
MAXCAPACITY larger than allowed
ANR5374I (S/390) Tape volume volume ID on real
maximum. Overriding maximum
address real address has had an
capacity to FILE maximum capacityMB.
unsolicited interrupt, and may have
been dismounted. Explanation: The maximum capacity specified for the
listed volume is larger than the maximum allowed for
Explanation: An unsolicited interrupt is received for
the FILE device class.
the drive where the volume is mounted. The drive is
not ready or its state cannot be determined, so the tape System Action: The volume capacity is set to the
may have been dismounted. maximum allowed for the FILE device class.
System Action: If the server can recover without User Response: Update the device class of the volume
possibility of data loss, it will reverify the label and MAXCAPACITY value to less than or equal the
continue operations. If the label is not verified or data maximum allowed for the FILE device class.
loss is possible with continued use, the next operation

ANR5413E (S/390) • ANR5419E (S/390)
ANR5413E (S/390) Dynamic allocation of FILE ANR5416E (S/390) Minidisk device class cannot be
volume volume on unit=unit volser=volser used with SFS file file name.
returned rc=rc, info code=info code, error
Explanation: A device class of DEVTYPE=FILE is
code=error code.
defined with FILEMODE= where the file mode letter is
Explanation: The dynamic allocation of FILE volume associated with an SFS directory. Device classes defined
volume on unit unit and volume serial volser fails. The with DEVTYPE=FILE and FILEMODE= parameters can
server uses the unit and volser device class parameters only be associated with an accessed minidisk (CMS file
when allocating new FILE volumes, and always mode letter A-Z).
catalogs the actual MVS data sets. If these parameters
System Action: File is not used.
are not defined, Dynamic Allocation uses system
defaults to select a device on which to create the MVS User Response: When using a minidisk, define the
sequential data set. DEVTYPE=FILE device class with the FILEMODE=
parameter. When using an SFS directory, use the
For previously allocated FILE volumes, the server
DIRECTORY= parameter.
allows Dynamic Allocation to locate the actual MVS
data set using catalog services.
ANR5417E (S/390) File file name already exists, it
The return code rc, information code info code and error
cannot be created.
code error code are in decimal and can be found in the
Dynamic Allocation section of MVS/ESA Programming: Explanation: The server attempted to create a new file
Authorized Assembler Services Guide. using file name but received indication that the file
already exists. The server will create a new file after it
determines that the file named file name is not in its
User Response: For new FILE volumes, verify that all database. The server will append to an existing file
device class parameters are defined correctly and are with the name file name only if it exists in its database.
compatible, and that space is available on the target The server will not overwrite an existing file.
DASD.
System Action: File is not used.
User Response: The file named file name must either
ANR5414E (S/390) Error error code returned while
be renamed or erased.
opening FILE volume volume
Explanation: The BSAM OPEN fails. Error code error
ANR5418E (S/390) File file name cannot be used.
code is returned. Check for accompanying MVS error
messages. Explanation: The server found that the file file name
exists in its database, but either was accessed as
Error codes greater than eight are MVS ABEND codes,
read-only or the file did not exist on the minidisk
documented in MVS/ESA System Codes, GC28-1486.
identified by the file mode letter or the file did not
System Action: Server operation continues. exist in the SFS directory.
User Response: For previously allocated FILE System Action: File is not used.
volumes, verify that the MVS data set used for the
User Response: Make sure the minidisk is accessed
FILE volume exists on the physical device designated
with the file mode letter specified for the device class
by the catalog. Check the accompanying MVS system
defined with DEVTYPE=FILE FILEMODE=?. If the file
messages.
is in an SFS directory, make sure the SFS directory still
exists and the server user ID has been granted
ANR5415W (S/390) SFS CSL call CSL name failed read/write authority to the directory and to the file
with return code rc, reason code rs. named command. If the volume status is read/write and
optional (file or directory being processed) the volume is not full, write access is required. If the
file does not exist, the server cannot use the volume.
Explanation: A call to an SFS CSL routine failed.
Storage volumes should be deleted using the DELETE
System Action: See following server messages. VOLUME command with DISCARDDATA=YES.
Volumes for IMPORT, LOAD or RESTORE DB cannot
User Response: Check the return and reason codes in be used.
the System Messages and Codes manual, ″Callable
Services Library (CSL) Reason Codes″ section, for
information on the problem and on the action needed ANR5419E (S/390) Filemode or directory filemode or
to correct it. directory name cannot be used.
Explanation: The server determined that a minidisk
with the file mode letter filemode or that the SFS
directory directory name were not available for use.

ANR5420W (S/390) • ANR5456E (S/390)
System Action: Server operation continues but file is
ANR5453E (S/390) Device type volume volume name
not used.
cannot be overwritten by EXPORT
User Response: Ensure that a minidisk is accessed operation.
with the file mode letter filemode or that an SFS
Explanation: The specified volume already exists or
directory directory directory exists and that the server
contains data. The server does not allow new export
user ID has been granted read/write authority to the
data to be written to the volume.
directory and all files in that directory.
System Action: The server detects that the given
volume already contains some data that would be
ANR5420W (S/390) FILE FILE name not deleted from
overwritten by the requested export operation.
system, return code return code.
User Response: If the specified volume does not
Explanation: A volume associated with a device class
contain any valuable data, delete it and retry the export
defined with DEVTYPE=FILE was deleted from the
operation.
server, but the associated CMS file or MVS data set
FILE name could not be deleted.
System Action: Server operation continues. No other
cannot be overwritten by DUMPDB
attempts will be made to delete the volume from the
operation.
system.
User Response: If the volume was created and never
contains data. The server does not allow new dump
used, a CMS file or an MVS dataset may not have been
data to be written to the volume.
created and no action is required. If the CMS file or the
MVS dataset FILE name exists it will have to be deleted System Action: The server detects that the given
manually. volume already contains some data that would be
overwritten by the requested dump operation.
ANR5450E (S/390) Error opening filespec. User Response: If the specified volume does not
contain any valuable data, delete it and retry the dump
Explanation: An error occurred while attempting an
operation.
open operation.
User Response: Refer to the other displayed messages cannot be overwritten by BACKUP DB
to determine why the open operation failed. Correct the operation.
problem and restart the process.
contains data. The server does not allow new backup
ANR5451E (S/390) An error (error code) occurred data to be written to the volume.
Explanation: An error occurred while attempting a volume already contains some data that would be
write operation. overwritten by the requested backup operation.
System Action: Server processing continues. User Response: If the specified volume does not
contain any valuable data, delete it and retry the
User Response: Refer to the other displayed messages backup operation.
to determine why the write operation failed. Correct
the problem and restart the process.
cannot be overwritten by backup set
ANR5452E (S/390) An error (error code) occurred operation.
Explanation: An error occurred while attempting a contains data. The server does not allow new backup
read operation. set data to be written to the volume.
System Action: Server processing continues. System Action: The server detects that the given
User Response: Refer to the other displayed messages volume already contains some data that would be
to determine why the read operation failed. Correct the overwritten by the requested backup set operation.
problem and restart the process. User Response: If the specified volume does not
backup set operation.

ANR5499E (S/390) • ANR5506E (S/390)
ANR5499E (S/390) Command: Required parameter was ANR5503E (S/390) Command: Invalid parameter for
not specified parameter. update - parameter.
Explanation: The command command has been issued, Explanation: The command command has been issued.
but without a required parameter. If two parameters However, the parameter is not an attribute that must be
are listed, the command requires at least one of the updated.
parameters.
User Response: Reissue the command, and specify a
User Response: Reissue the command and specify the compatible set of attributes. The HELP UPDATE
missing parameter and any additional parameters that command may be used to obtain syntax assistance.
are required for the command. The HELP DEFINE or
HELP UPDATE commands may be used to obtain
ANR5504E (S/390) Command: ″new attribute″ conflicts
syntax assistance.
with existing ″old attribute″.
Explanation: The command command has been issued.
ANR5500E (S/390) Command: Device type not
However, new attribute conflicts with old attribute in
specified.
updating the device class.
Explanation: The command command has been issued,
but without the DEVTYPE keyword.
compatible set of attributes. You may have to specify
User Response: Reissue the command, and specify the additional keywords to update the device class in a
DEVTYPE keyword and any additional parameters that compatible manner. The HELP UPDATE command may
are required for the command. The HELP DEFINE or be used to obtain syntax assistance.
syntax assistance.
ANR5505E (S/390) Command: ″MOUNTLIMIT″ is less
than current number of mounted
ANR5501E (S/390) Command: ″attribute″ is invalid for volumes.
device type.
Explanation: The command command has been issued
Explanation: The command command has been issued that specifies a MOUNTLIMIT smaller than the existing
with an incompatible combination of device type and number of volumes that are already allocated.
attribute.
User Response: You may wait until volumes are no
User Response: Reissue the command, and specify a longer in use to reissue the command. Alternatively,
compatible set of attributes. The HELP DEFINE or you may cancel sessions or processes that are using
HELP UPDATE commands may be used to obtain volumes; then issue DISMOUNT commands to free
syntax assistance. allocated volumes before reissuing the command. The
QUERY MOUNT command can be issued to determine
which volumes are mounted for use by the server.
ANR5502E (S/390) Command: ″LENGTH″ is invalid
with 3480 and 3480XF formats.
ANR5506E (S/390) Command: Conflicting parameters
Explanation: The command command has been issued
″parm1″ and ″parm2″.
with an incompatible combination of device type,
FORMAT, and LENGTH. A length specification is Explanation: The command command has been issued
invalid with 3480 and 3480XF formats. that specifies conflicting parameters parm1 and parm2.
Conflicting parameters include specifying FORMAT
and LENGTH with DENSITY, and RETENTION with
User Response: Reissue the command, and specify a EXPIRATION.
compatible set of attributes. For 3480 and 3480XF
formats, reenter the command without a LENGTH
keyword. The HELP DEFINE or HELP UPDATE User Response: Reissue the command, and specify a
commands may be used to obtain syntax assistance. compatible set of parameters. The HELP DEFINE or
syntax assistance.

ANR5507E (S/390) • ANR5954W (S/390)
ANR5507E (S/390) Command: Device type ″devtype″ ANR5513E (S/390) Expiration date expdt is not valid.
not supported on this platform.
Explanation: Expiration data expdt is not valid.
Explanation: An unsupported device type has been
specified for command. In MVS, for example, the REEL
device type is not supported. User Response: Reissue the server command, and
specify a valid expiration date.
User Response: Specify a valid device type for the
ANR5514E (S/390) Retention period retpd is not valid.
platform. The HELP DEFINE command may be used to
obtain syntax assistance. Explanation: Retention period retpd is not valid.
ANR5508E (S/390) Device class device class not
defined in device configuration file. User Response: Reissue the server command, and
specify a valid retention period.
Explanation: The issued command requires that the
specified device class be defined in the device
configuration file. The definition was not found. ANR5953W (S/390) Unable to generate accounting
record - ACCT option not specified in
System Action: The command is not processed. CP directory.
User Response: Reissue the command, and specify a Explanation: The SET ACNT ON command has been
valid device class. You may also want to refresh your entered, but the server is unable to generate an
device configuration file by issuing the BACKUP accounting record because the ACCT option has not
DEVCONFIG command. been specified in the server’s CP directory entry.
ANR5509E (S/390) Command: Parameter Parameter is accounting record is generated.
larger than the allowed maximum of
Maximum valueM. User Response: Add the ACCT option to the server’s
CP directory entry. To suppress these messages until
Explanation: The specified parameter is larger than the CP directory can be updated, enter the SET ACNT
the allowed maximum for this device class. OFF command.
System Action: The command is not processed.
ANR5954W (S/390) Unable to generate accounting
record - insufficient memory.
parameter less than or equal to the allowed maximum.
Explanation: The SET ACNT ON command has been
entered, but the server is unable to generate an
ANR5510E (S/390) Data set name dsn is not valid.
accounting record due to a lack of memory (virtual
Explanation: Data set name dsn is not valid. storage). In some cases a 4096-byte buffer is required
for accounting operations, and it is this buffer that
cannot be allocated.
User Response: Reissue the server command, and
specify a valid data set name.
accounting record is generated.
ANR5511E (S/390) Unit name unit is not valid.
Explanation: Unit name unit is not valid. 1. Increase the size of the server’s virtual machine.
System Action: Server operation continues. This requires that the default storage size be
updated in the server’s CP directory entry.
User Response: Reissue the server command, and 2. Reduce the maximum number of client sessions
specify a valid unit name. permitted. To do this, edit the DSMSERV OPT file
ANR5512E (S/390) Volume serial volser is not valid. MAXSESSIONS statement. Note that each client
Explanation: Volume serial volser is not valid. allocated.
System Action: Server operation continues. 3. Decrease the amount of space allocated to the
User Response: Reissue the server command, and
DSMSERV OPT file and reduce the value specified
specify a valid volume serial.

ANR5956E (S/390) • ANR5964E (S/390)
for the BUFPOOLSIZE statement. Note that each to the CP directory entry for the server.
memory to be allocated.
ANR5961E (S/390) Insufficient memory for server
initialization.
Note that the server must be shut down (with the
HALT command) before changes can be made to the Explanation: The server program cannot allocate
DSMSERV OPT file. enough memory (virtual storage) to fully initialize
itself.
ANR5956E (S/390) C library not available, unable to System Action: Server initialization fails. The server is
continue. not started.
Explanation: The C/370 or LE/370 library is not User Response: Allocate additional storage to the
available. server virtual machine or reduce the storage required
by the server. There are three ways to do this:
System Action: Server operation ends.
1. Increase the size of the server’s virtual machine.
User Response: Make the C/370 or LE/370 library This requires that the default storage size be
available to the server. updated in the server’s CP directory entry.
For MVS, increase the region size; 40M is the
ANR5957W (S/390) C library is at level level. recommended minimum size for the server but
larger servers require more.
Explanation: The C run-time library is at a lower level
(level) than expected. 2. Reduce the maximum number of client sessions
permitted. To do this, edit the DSMSERV OPT file
System Action: Server attempts to continue operation. and reduce the value specified for the
MAXSESSIONS statement. Note that each client
User Response: Ensure that the proper level of the
C/370 or LE/370 library is installed and available to
allocated.
the server.
ANR5958E (S/390) SVM is at level level, the server DSMSERV OPT file and reduce the value specified
requires at least required-level, unable to for the BUFPOOLSIZE statement. Note that each
continue. buffer pool page causes an additional 4 KB of
Explanation: The SVM run-time library is at level memory to be allocated.
level, but the server requires at least level required-level.
Note that the server must be shut down (with the
System Action: Server operation ends. HALT command) before changes can be made to the
User Response: Check the required PTFs for the DSMSERV OPT file.
server. Ensure that the proper level of SVM is installed.
ANR5962I (S/390) DSMSERV generated at time on
ANR5959E (S/390) Server not running APF date.
authorized. The server and all Explanation: The server module has been generated at
JOBLIB/STEPLIB libraries (C library the indicated date and time.
and other libraries) must be authorized.
Explanation: The server is not running with MVS
authorization. User Response: None.

ANR5963I (S/390) Server termination complete.
User Response: Ensure that all library data sets
required by the server are authorized. Explanation: The server has completed shut down.
ANR5960E (S/390) Unable to initialize kernel - User Response: None.
virtual machine requires ECMODE
capability.
ANR5964E (S/390) Server unable to mark itself
Explanation: The CP directory entry for the server non-swappable. Return code rc from
does not contain an OPTION ECMODE statement. SYSEVENT TRANSWAP.
System Action: Server operation ends. Explanation: The server cannot issue a SYSEVENT
User Response: Add an OPTION ECMODE statement TRANSWAP macro.

ANR5965I (S/390) • ANR6203I
ANR5982E (S/390) InfoSpeed accept error rc = rc on
User Response: Contact your service representative. port port number.
Explanation: The server’s InfoSpeed communications
ANR5965I (S/390) Console command: command driver has received an error from the ACCEPT
function.
Explanation: A server command command has been
received from an MVS operator console. System Action: Server operation continues and
InfoSpeed communications will be retried.
ANR6200I Command name: Level compression audit

ANR5967W (S/390) Accounting record not produced, level compression audit started as
return code rc. process process ID.
Explanation: There was a problem generating the Explanation: A compression audit at the specified
accounting record. level has been started as a background server process
System Action: Server operation continues. with the process identifier reported.
User Response: Contact your service representative. System Action: Server operation continues. The
background audit attempts to identify client files that
may be affected by the client compression problem.
ANR5980E (S/390) Unable to initialize PDM driver -
insufficient memory. User Response: None.
Explanation: The server’s PDM communications

driver is unable to initialize itself due to insufficient ANR6201I Command name: Level compression audit
memory (virtual storage). level compression audit starting as
background process process ID.
Explanation: A compression audit at the specified
User Response: Allocate additional storage to the level was started as a background server process
server virtual machine. There are three ways to do this: having the process identifier reported.
1. Increase the size of the REGION parameter on the
EXEC or JOB statement of the JCL used to start the
background audit attempts to identify client files that
server.
may be affected by the client compression problem.
2. Reduce the maximum number of client sessions
permitted. To do this, edit the server options file User Response: None.
MAXSESSIONS statement. Note that each client ANR6202I Command name: Verifying candidates
session causes an additional 64KB of memory to be from last audit.
allocated.
3. Decrease the amount of space allocated to the Explanation: A compression audit has started to verify
server’s database buffer pool. To do this, edit the the client file candidates that were identified in a
server options file and reduce the value specified previous compression audit execution. The verification
for the BUFPOOLSIZE statement. Note that each process eliminates compression candidates that are now
buffer pool page causes an additional 4KB of found to be expired by policy on the server.
memory to be allocated. System Action: The audit operation continues.
Note that the server must be shut down (with the User Response: None.
server options file. ANR6203I Command name: Starting level audit level
compression audit from qualifying
ANR5981I (S/390) InfoSpeed/PDM communication entries in the candidates list.
enabled on port port number. Explanation: A compression audit is starting to check
Explanation: The server’s PDM communications qualifying candidates from the candidates list for the
driver is ready to receive connection requests from audit level specified. Client files that were identified as
clients. compression candidates at a lower level will be tested,
subject to the qualifications that were specified for the
System Action: Server operation continues. command.
User Response: None. System Action: The audit operation continues.

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

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

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

ANR6301E Command name: Invalid LEVEL specified. ANR6304E Command name: Command cannot be
This command only supports a value of processed until compression audit is
1 or 2 for the LEVEL parameter. performed.
Explanation: An invalid LEVEL= parameter has been Explanation: The indicated command cannot be
specified for the command. processed until a compression audit is performed using
the AUDIT COMPRESSION command.
value of 1 or 2 for the LEVEL parameter. User Response: Issue the AUDIT COMPRESSION
command and then repeat the attempted operation.
ANR6302E Command name: Process process ID, failed
- number of candidate files candidate files ANR6305E Command name: File identifier is not a
were found in number of files examined suspect for compression errors.
files examined prior to failure.
Explanation: The file with the specified identifier is
Explanation: A compression audit operation failed not listed in the database as a suspect for compression
before completion. The number of candidate files that errors. The file cannot be removed from the suspect list.
were found prior to the failure are displayed.
User Response: Use the QUERY COMPRESSION
User Response: Examine message that appear before command to obtain the correct identifier for the file to
this message on the server console or in the activity log be removed.
to determine the source of the failure. If the error can
be corrected, re-execute the compression audit. If the
ANR6306E Cleanup process name: Process process ID
failure cannot be determined or corrected, contact your
failed due to server error - cleanup
service representative. The compression candidate list
processing is incomplete.
can be displayed with the QUERY COMPRESSION
command. Explanation: A compression cleanup operation has
failed before successful completion.
ANR6303E Command name: Process process ID, failed System Action: The cleanup process ends.
- number of files promoted candidate files
were promoted as candidates at level User Response: Examine messages that appear on the
audit level, number of files eliminated files server console or in the server activity log prior to this
were eliminated as candidates, and message to determine the cause of the error. If the error
number of files expired candidates were can be identified and corrected, restart the cleanup
eliminated because they were found to operation with the CLEANUP COMPRESSION
be expired on the server. command. If the error cannot be corrected, contact your
Explanation: A compression audit operation failed
before completion. The number of candidate files that
were promoted as candidates at this level of audit, ANR6600E Command: Invalid machine name -
eliminated as candidates at this level of audit, and machine name.
found to be expired before the audit failure are Explanation: The machine name specified in the
reported. command is invalid.
System Action: The audit operation ends. System Action: The server does not process the
User Response: Examine message that appear before command.
this message on the server console or in the activity log User Response: Issue the command again and specify
to determine the source of the failure. If the error can a valid machine name.
be corrected, re-execute the compression audit. If the
failure cannot be determined or corrected, contact your
service representative. The compression candidate list ANR6601E Command: Description information
can be displayed with the QUERY COMPRESSION exceeds maximum length characters.
command. Explanation: The description specified in the
command exceeds the maximum length of allowable
characters.
command.

User Response: Issue the command again and specify
ANR6607E Command: Machine machine name is
a valid description.
already defined.
Explanation: The machine specified in the command
ANR6602E Command: Recovery instructions file
is already defined to the server.
name exceeds maximum length characters.
Explanation: The recovery instructions file name
command.
specified in the command exceeds the maximum length
of allowable characters. User Response: Issue the command again and specify
another machine.
command.
ANR6608E Command: A machine containing a server
is already defined.
a valid recovery instructions file name.
Explanation: The ADSMSERVER=YES parameter
specified in the command is invalid because another
ANR6603E Command: Characteristics file name
machine has already been defined with this parameter.
exceeds maximum length characters.
Only one machine can be defined to the server as
Explanation: The characteristics file name specified in containing a server.
the command exceeds the maximum length of
allowable characters.
command.
User Response: Issue the command again and do not
command.
specify ADSMSERVER=YES as a parameter.
a valid characteristics file name.
ANR6609I Machine machine name defined.
Explanation: A DEFINE MACHINE command has
ANR6604E Command: Invalid building identifier -
added the requested machine to the server.
building.
Explanation: The building identifier specified in the
command is invalid. User Response: None.
command. ANR6610E Command: Invalid recovery media name -
recovery media name.
a valid building identifier. Explanation: The recovery media name specified in
the command is invalid.
ANR6605E Command: Invalid floor identifier - floor. System Action: The server does not process the
command.
Explanation: The floor identifier specified in the
command is invalid. User Response: Issue the command again and specify
a valid recovery media name.
command.
ANR6611E Command: Location information exceeds
maximum length characters.
a valid floor identifier.
Explanation: The location specified in the command
exceeds the maximum length of allowable characters.
ANR6606E Command: Invalid room identifier - room.
Explanation: The room identifier specified in the
command.
command is invalid.
a valid location.
command.
a valid room identifier.

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

ANR6623W Command: Machine machine name cannot ANR6628E Command: Volume list exceeds maximum
be processed because it is not defined. length characters.
Explanation: The machine indicated in the message is Explanation: The volume list specified in the
not defined to the server. command exceeds the maximum length of allowable
characters.
System Action: The indicated machine is not
processed, but another machine can be processed if System Action: The server does not process the
specified by this command. command.
User Response: Issue the command again and specify User Response: Issue the command again and specify
a valid machine. a valid volume list.
ANR6624E Command: No matching machine ANR6629E Command: Product name exceeds

defined. maximum length characters.
Explanation: The machine specified in the command Explanation: The product name specified in the
does not match any machine defined to the server. command exceeds the maximum length of allowable
characters.
command.
a valid machine. User Response: Issue the command again and specify
a valid product name.
ANR6625I Machine machine name associated with
recovery media recovery media name. ANR6630E Command: Product information exceeds
maximum length characters.
Explanation: A DEFINE
RECOVERYMEDIAMACHASSOCIATION command Explanation: The product information specified in the
has associated the specified machine with the specified command exceeds the maximum length of allowable
recovery media. The machine machine name is characters.
associated with the recovery media recovery media name.
System Action: None. command.
User Response: None. User Response: Issue the command again and specify
valid product information.
ANR6626E Command: Recovery media/machine
association is already defined. ANR6631E Command: Missing volume list for boot
recovery media.
Explanation: The recovery media/machine association
specified in the command is already defined to the Explanation: Boot recovery media cannot be defined
server. to the server without specifying a volume list.
System Action: The server operation continues, but System Action: The server does not process the
the command has no effect. command.
User Response: Issue the command again and specify User Response: Issue the command again and specify
a valid machine. the volume list for the boot recovery media.
ANR6627I Machine machine name disassociated ANR6632I Recovery media recovery media name
from recovery media recovery media name. defined.
Explanation: A DELETE Explanation: A DEFINE RECOVERYMEDIA command
RECOVERYMEDIAMACHASSOCIATION command has defined the recovery media to the server.
has deleted the requested association from the server.
Machine machine name is not associated with the
recovery media recovery media name. User Response: None.

ANR6633I Recovery media recovery media name ANR6638E Command: The characteristics for
updated. machine machine name are already
defined.
Explanation: An UPDATE RECOVERYMEDIA
command has updated one or more attributes of the Explanation: The characteristics for the machine
recovery media. specified in the command are already defined to the
server.
command.
User Response: If the specified machine is defined to
ANR6634I Recovery media recovery media name
the server, issue an UPDATE MACHINE command to
deleted.
update the existing characteristics. If the machine is not
Explanation: A DELETE RECOVERYMEDIA defined to the server, run AUDIT DRM FIX to delete
command has deleted the requested recovery media the characteristics.
from the server.
System Action: None. ANR6639E Command: The recovery instructions for
machine machine name are already
User Response: None. defined.
Explanation: The recovery instructions for the
ANR6635E Command: Recovery media recovery media machine specified in the command are already defined
name is already defined. to the server.
Explanation: The recovery media specified in the System Action: The server does not process the
command is already defined to the server. command.
System Action: The server does not process the User Response: If the specified machine is defined to
command. the server, issue an UPDATE MACHINE command to
User Response: Issue the command again and specify update the existing recovery instructions. If the
a different recovery media. machine is not defined to the server, run AUDIT DRM
FIX to delete the recovery instructions.
ANR6636E Command: The characteristics specified

for machine machine name exceeds ANR6640E Command: Cannot delete volume list for
maximum length characters. boot recovery media.
Explanation: The characteristics specified in the Explanation: A volume list cannot be deleted for boot
command exceeds the maximum length of allowable recovery media. A volume list must exist for each boot
characters. recovery media defined to the server.
command. command.
User Response: Issue the command again and specify User Response: To delete the volume list, issue an
valid characteristics. UPDATE RECOVERYMEDIA command and specify a
recovery media type of OTHER and VOLUMES=″″. To
change the recovery media type to BOOT, issue an
ANR6637E Command: The recovery instructions UPDATE RECOVERYMEDIA command and specify the
specified for machine machine name volume list containing the boot recovery media and
exceeds maximum length characters. TYPE=BOOT.
Explanation: The recovery instructions specified in the
command exceeds the maximum length of allowable ANR6641E Command: No association found for
characters. machine and node pair specified.
System Action: The server does not process the Explanation: No association found for the machine
command. and node pair specified in the command.
User Response: Issue the command again and specify System Action: Server operation continues, but the
valid recovery instructions. command has no effect.
a valid machine and node pair.

ANR6642E Command: No association found for ANR6647E Audit command: DRM global attributes
recovery media and machine pair are missing.
specified.
Explanation: No association found for the recovery global attributes used for server DRM activities are
media and machine pair specified in the command. missing.
System Action: Server operation continues, but the System Action: Audit processing continues.
command has no effect.
User Response: Issue the command again and specify FIX=YES to recreate the DRM global attributes.
a valid recovery media and machine pair.
ANR6648I Audit command: DRM global attributes
ANR6643E Command: Invalid parameter value - are missing - default values will be used
parameter value. to recreate the attributes.
Explanation: The parameter issued in the command is Explanation: A database audit process finds that the
invalid. 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
command.
to recreate the administrative global attributes.
a valid parameter.
ANR6644E Command: A character string must be
specified. ANR6649E Audit command: DRM machine ID
assignments are incorrect.
Explanation: The INSERT command is invalid. A
character string must be specified. Explanation: A database audit process finds that the
global attributes machine ID used for server DRM
activities are incorrect.
command.
a valid character string. User Response: Reissue the audit command with
FIX=YES specified so that the DRM global attributes
can be corrected.
ANR6645W Node node name has already been
associated with machine machine name.
ANR6650I Audit command: DRM machine ID
Explanation: The node specified in the DEFINE
Assignments are incorrect - values will
MACHNODEASSOCIATION command is invalid. The
be corrected.
node is already associated with another machine shown
in the message. A node can only be associated with one Explanation: A database audit process finds that the
machine. global attributes machine ID used for server DRM
activities are incorrect. Since FIX=YES has been
specified on the AUDIT command, the attribute value
but another node can be processed if specified by the
will be corrected in the server database.
command.
a valid node name. User Response: None
ANR6646I Audit command: Auditing disaster ANR6651I Audit command: Invalid priority value
recovery manager definitions. encountered for machine machine name.
Explanation: This message is displayed during a Explanation: A database audit process encounters an
database audit and indicates that the disaster recovery invalid priority value for the machine indicated.
manager definitions are being examined by the
FIX=YES to correct the priority. Or, issue an UPDATE
User Response: None. MACHINE command and specify a new priority value.

FIX=YES has been specified, the audit function removes
ANR6652I Audit command: Invalid priority value
the machine floor value.
encountered for machine machine name -
the default value will be set. System Action: Audit processing continues.
Explanation: A database audit process encounters an User Response: To set the floor value to another
invalid machine priority value for the machine value, issue an UPDATE MACHINE command after the
indicated. Because FIX=YES has been specified, the audit command has completed.
audit function sets the machine priority value to the
default value.
ANR6657I Audit command: Invalid room value
System Action: Audit processing continues. encountered for machine machine name.
User Response: To override the default value, issue an Explanation: A database audit process encounters an
UPDATE MACHINE command to change the value invalid room value for the machine indicated.
ANR6653I Audit command: Invalid building value User Response: Issue the command again and specify
encountered for machine machine name. FIX=YES to correct the room value. Or, issue an
UPDATE MACHINE command and specify a new
Explanation: A database audit process encounters an room value.
invalid building value for the machine indicated.
System Action: Audit processing continues. ANR6658I Audit command: Invalid room value
the room value will be removed.
FIX=YES to correct the building value. Or, issue an
UPDATE MACHINE command and specify a new Explanation: A database audit process encounters an
building value. invalid room value for the machine indicated. Because
FIX=YES has been specified, the audit function removes
the machine room value.
ANR6654I Audit command: Invalid building value
encountered for machine machine name - System Action: Audit processing continues.
the building value will be removed.
User Response: To set the room value for the specified
Explanation: A database audit process encounters an machine to another value, use the UPDATE MACHINE
invalid building value for the machine indicated. command after the audit command has completed.
removes the machine building value.
ANR6659I Audit command: Invalid server value
System Action: Audit processing continues. encountered for machine machine name.
User Response: To set the building value to another Explanation: A database audit process encounters an
value, issue an UPDATE MACHINE command after the invalid server value for the machine indicated.
audit command has completed.
ANR6655I Audit command: Invalid floor value User Response: Issue the command again and specify
encountered for machine machine name. FIX=YES to correct the server value. Or, issue an
UPDATE MACHINE command and specify a new
Explanation: A database audit process encounters an server value.
invalid floor value for the machine indicated.
System Action: Audit processing continues. ANR6660I Audit command: Invalid server value
the default value will be set.
FIX=YES to correct the floor value. Or, issue an
UPDATE MACHINE command and specify a new floor Explanation: A database audit process encounters an
value. invalid server value for the machine indicated. Because
machine server value to the default value.
ANR6656I Audit command: Invalid floor value
encountered for machine machine name - System Action: Audit processing continues.
the floor value will be removed.
User Response: To override the default value, issue an
Explanation: A database audit process encounters an UPDATE MACHINE command to change the value
invalid floor value for the machine indicated. Because after the audit command has completed.

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

ANR6669I Audit command: Machine is not found for ANR6673I Audit command: Client node not found
internal machine ID machine ID, which for internal node ID node ID, which is
is referenced by recovery media - the referenced by a machine - the client
machine reference will be deleted. node reference will be deleted.
Explanation: A database audit process finds recovery Explanation: A database audit process finds a machine
media that references a machine that is not defined in that references a client node that is not defined in the
the server database. Because FIX=YES has been server database. Because FIX=YES has been specified
specified for the audit command, the reference will be for the audit command, the reference will be removed
removed from the server database. from the server database.
ANR6670E Audit command: Recovery media not ANR6674E Audit command: Machine not found for
found for internal recovery media ID internal machine ID machine ID, which
recovery media ID, which is referenced by is referenced by a client node.
a machine.
Explanation: A database audit process finds a machine node that references a machine that is not defined in
that references recovery media that is not defined in the the server database.
server database.
User Response: Issue the command again and specify FIX=YES to correct the machine attributes.
FIX=YES to correct the recovery media attributes.
ANR6675I Audit command: Machine not found for
ANR6671I Audit command: Recovery media not internal machine ID machine ID, which
found for internal recovery media ID is referenced by a client node - the
recovery media ID, which is referenced by machine reference will be deleted.
a machine - the recovery media
reference will be deleted.
node that references a machine that is not defined in
Explanation: A database audit process finds m the server database. Because FIX=YES has been
machine that references recovery media that is not specified for the audit command, the reference will be
defined in the server database. Because FIX=YES has removed from the server database.
been specified for the audit command, the reference
will be deleted from the server database.
ANR6676E Audit command: Machine not found for
ANR6672E Audit command: Client node not found is referenced by characteristics.
for internal node ID node ID, which is
referenced by a machine.
characteristics that reference a machine that is not
Explanation: A database audit process finds a machine defined in the server database.
that references a client node that is not defined in the
server database.
FIX=YES to correct the machine attributes.
is referenced by characteristics - the
machine reference will be deleted.
characteristics that reference a machine that is not
defined in the server database. Because FIX=YES has

been specified for the audit command, the reference
ANR6682I Command command ended: number of
will be removed from the server database.
volumes volumes processed.
Explanation: The indicated command ended. The total
User Response: None. number of volumes successfully processed is shown in
the message.
ANR6678E Audit command: Machine not found for System Action: The indicated command ends.
is referenced by recovery instructions.
Explanation: A database audit process finds recovery
ANR6683I Command: Volume volume name was
instructions that reference a machine that is not defined
moved from from state state to to state.
in the server database.
Explanation: Volume volume name is successfully
moved from state1 to state2 by the indicated command.
System Action: The indicated volume is moved to the
destination state.
is referenced by recovery instructions - ANR6684I Command: Volume volume name was
the machine reference will be deleted. deleted.
Explanation: A database audit process finds recovery Explanation: The MOVE DRMEDIA *
instructions that reference a machine that is not defined WHERESTATE=COURIERRETRIEVE command
in the server database. Because FIX=YES has been displays the message. Volume volume name is deleted
specified for the audit command, the reference will be from the server database. For database backup volume,
removed from the server database. 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, the
User Response: None. volume record is deleted when it is returned onsite.
System Action: The volume record is deleted from the
ANR6680E Audit command: Missing or invalid server database.
internal database attribute encountered
User Response: Issue the CHECKIN LIBVOLUME
for machine machine name.
command for each volume returned onsite if the
Explanation: A database audit process finds an invalid volume is reused by the server.
attribute for the specified machine.
System Action: Audit processing continues. ANR6685E Command: Volume volume name not
defined.
FIX=YES to correct the machine attributes. Explanation: Volume volume name is not defined to the
server.
ANR6681I Audit command: Missing or invalid System Action: The indicated command is not
internal database attribute encountered processed if the volume name is explicitly specified on
for machine machine name - the attribute the command. If a volume pattern is specified on the
will be corrected. command, the volume shown is not processed, but the
other volumes are processed.
Explanation: A database audit process finds an invalid
attribute for the specified machine. Because FIX=YES User Response: Reissue the command specifying a
has been specified for the audit command the invalid valid volume name.
attribute will be corrected.
System Action: Audit processing continues. ANR6686E Command: Volume volume name in use.
User Response: None. Explanation: The MOVE DRMEDIA *
WHERESTATE=MOUNTABLE command displays the
message. Volume volume name is used for another
operation.
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 User Response: Reissue the command specifying the
indicated volume is not processed, but the other valid volume.
volumes are processed.
User Response: Wait until the conflicting volume ANR6694E Command: The ORM state state is invalid
activity has completed, and then reissue the command. for a volume with access mode access
If the volume is currently mounted, but idle, dismount mode.
the volume by using a DISMOUNT VOLUME
Explanation: The indicated command specifies an
command and then retry this operation.
Offsite Recovery Media state that is invalid for a
volume with the access mode shown. Specify
ANR6687E Command: Executable command string COURIER or COURIERRETRIEVE for a volume that
exceeds maximum length characters. has access mode of OFFSITE.
Explanation: The length of the executable command System Action: The server does not process the
string specified with the CMD parameter exceeds the command.
maximum length of allowable characters (255).
System Action: The server stops processing the COURIER or COURIERRETRIEVE as the state for a
command. volume that has access mode of OFFSITE.
a valid executable command with the CMD parameter. ANR6695E Command: Device class device class name
not defined for volume volume name.
ANR6688E command: The specified command failed Explanation: The MOVE DRMEDIA or QUERY
because the entry/exit port of library DRMEDIA command displays the message. The
library name is full. Please remove the volume being processed has associated with the device
volume(s) from the entry/exit port and class name shown that is not defined to the server.
re-issue the command name command.
System Action: The command is not processed if the
Explanation: The indicated operation has failed volume is explicitly specified on the command. If a
because the entry/exit port of the specified library is volume pattern is specified on the command, the
full. indicated volume is not processed, but the other
volumes not associated with the indicated class are
processed.
User Response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
indicated device class is defined to the server.
any remaining eligible volumes.
ANR6696I command: operation for volume volume

ANR6690E Command: Copy storage pool cstgp name
name in library library name starting.
not defined for Offsite Recovery Media.
Explanation: The indicated operation is being started
Explanation: The MOVE DRMEDIA or QUERY
for the volume shown in the given library.
DRMEDIA command displays the message. The
indicated command was issued with a copy storage System Action: The server starts the operation in
pool name specified, but the specified pool name is not response to the indicated command entered by an
defined to DRM for Offsite Recovery Media. administrator.
System Action: The indicated command is not User Response: For SCSI library users, remove the
processed. volume from the slot and issue a REPLY command,
along with the request ID, to tell the server the volume
User Response: Reissue the command, after defining
was removed from the library.
the specified copy storage pool to DRM for Offsite
Recovery Media.
ANR6697I command: operation for volume volume
name in library library name completed
ANR6691E Command: No match is found for this
successfully.
move.
Explanation: The indicated operation has completed
Explanation: The indicated command was issued, but
successfully for the volume shown in the given library.
no matching volumes are defined to the server or the
volume specified is not managed by the command. 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).

ANR6703E Command: Invalid recovery plan prefix -
prefix.
ANR6698E command: operation for volume volume
Explanation: The indicated command has been
name in library library name failed.
entered with an invalid recovery plan prefix.
Explanation: The indicated operation has failed for the
volume shown in the given library. This message
command.
should be preceded by another error message which
provides more detail about the error. User Response: Reissue the command with a valid
recovery plan prefix.
System Action: The volume is not processed.
User Response: Check for additional message and
ANR6704E Command: Invalid plan instructions
eliminate the condition that caused the failure, then
prefix - prefix.
retry the command.
entered with an invalid plan instructions prefix.
ANR6699I Cancel in progress.
Explanation: The MOVE DRMEDIA command has
command.
been canceled and will end when resources have been
freed for the background process. This message may be User Response: Reissue the command with a valid
displayed in response to a QUERY PROCESS command plan instructions prefix.
for a MOVE DRMEDIA command.
System Action: Server operation continues. ANR6705E Command: Invalid character for volume
postfix - postfix character.
entered with an invalid character that is to be added to
ANR6700I Command command completed
the volumes names in the recovery plan file.
successfully.
Explanation: The indicated command completed
command.
successfully.
character.
ANR6706E Command: Invalid vault name - vault
ANR6701E Command: Invalid courier name - courier name.
name.
Explanation: The indicated command has been entered with an invalid vault name.
entered with an invalid courier name.
command.
User Response: Reissue the command with a valid vault name.
courier name.
ANR6711E Audit command: An invalid database
ANR6702E Command: Invalid expiration days value backup series expiration days
- days value. encountered.
Explanation: The indicated command has been Explanation: A database audit process encounters an
entered that specifies an invalid expiration days value. invalid value for database backup series expiration
days.
command. System Action: Audit processing continues.
User Response: Reissue the command with a valid User Response: Issue the command again and specify
expiration days value. 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 ANR6716I Audit command: An invalid file process
backup series expiration days value encountered - the default value
encountered - the default value will be will be set.
set.
Explanation: A database audit process encounters an invalid file process value. Because FIX=YES has been
invalid value for database backup series expiration specified, the audit function sets the file process value
days. Because FIX=YES has been specified, the audit to the default value.
function sets the expiration days value to the default
value.
User Response: To override the default value, issue a
SET DRMFILEPROCESS command to change the value
User Response: To override the default value, issue a after the audit command has completed.
SET DRMDBBACKUPEXPIREDAYS command to
ANR6717E Audit command: Extraneous DRM global
completed.
attribute encountered.
ANR6713E Audit command: An invalid check label
nonexistent DRM global attribute.
value encountered.
invalid check label value. User Response: Issue the command again and specify
FIX=YES to delete the extraneous attribute.
ANR6718I Audit command: Extraneous DRM global
FIX=YES to correct the check label value. Or, issue a
attribute encountered - the attribute will
SET DRMCHECKLABEL command and specify a new
be deleted.
check label value.
nonexistent DRM global attribute. Since FIX=YES has
ANR6714I Audit command: An invalid check label
been specified, the extraneous attribute will be deleted.
value encountered - the default value
will be set. System Action: Audit processing continues.
Explanation: A database audit process encounters an User Response: None.
invalid check label value. Because FIX=YES has been
specified, the audit function sets the check label value
to the default value. ANR6719E Audit command: DRM machine ID
assignments not found.
Explanation: A database audit process finds no entries
User Response: To override the default value, issue a in server database for DRM internal machine ID
SET DRMCHECKLABEL command to change the value assignments.
ANR6715E Audit command: An invalid file process User Response: Issue the command again and specify
value encountered. FIX=YES to correct the error.

invalid file process value. ANR6720I Audit command: DRM machine ID
assignments not found - entry will be
System Action: Audit processing continues. created.
User Response: Issue the command again and specify Explanation: A database audit process finds no entries
FIX=YES to correct the file process value. Or, issue a in server database for DRM internal machine ID
SET DRMFILEPROCESS command and specify a new assignments. Because FIX=YES has been specified for
file process value. the audit command, the audit function creates an entry
in the server database for the machine ID assignments.

specify FIX=YES to correct the error.
ANR6721E Audit command: DRM recovery media ID
assignments not found.
ANR6726I Audit command: Prefix for DRM recovery
plan instructions not found - entry will
in server database for DRM internal recovery media ID
be created.
assignments.
in server database for DRM recovery plan instructions
User Response: Issue the command again and specify prefix definitions. Because FIX=YES has been specified
FIX=YES to correct the error. for the audit command, the audit function creates an
entry using the default value in the server database for
the recovery plan instructions file prefix.
ANR6722I Audit command: DRM recovery media ID
assignments not found - entry will be System Action: Audit processing continues.
created.
Explanation: A database audit process finds no entries SET DRMPLANINSTRPREFIX command to change the
in server database for DRM internal recovery media ID value after the audit command has completed.
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry
ANR6727E Audit command: Postfix for DRM
in the server database for the recovery media ID
replacement volumes names not found.
assignments.
in server database for DRM postfix definitions for
User Response: None. replacement volumes names.
ANR6723E Audit command: Prefix for DRM recovery
User Response: Issue the audit command again and
plan not found.
in server database for DRM recovery plan prefix
ANR6728I Audit command: Postfix for DRM
definitions.
replacement volumes names not found -
System Action: Audit processing continues. entry will be created.
User Response: Issue the audit command again and Explanation: A database audit process finds no entries
specify FIX=YES to correct the error. in server database for DRM postfix definitions for
replacement volumes names. Because FIX=YES has
been specified for the audit command, the audit
ANR6724I Audit command: Prefix for DRM recovery
function creates an entry using the default value in the
plan not found - entry will be created.
server database for the replacement volumes postfix.
in server database for DRM recovery plan prefix
definitions. Because FIX=YES has been specified for the User Response: To override the default value, issue a
audit command, the audit function creates an entry SET DRMPLANVPOSTFIX command to change the
using the default value in the server database for the value after the audit command has completed.
recovery plan file prefix.
System Action: Audit processing continues. ANR6729E Audit command: Primary storage pools to
be restored by DRM not found.
SET DRMPLANFILEPREFIX command to change the Explanation: A database audit process finds no entries
value after the audit command has completed. in server database for primary storage pools to be
restored by DRM.
ANR6725E Audit command: Prefix for DRM recovery System Action: Audit processing continues.
plan instructions not found.
Explanation: A database audit process finds no entries specify FIX=YES to correct the error.
in server database for DRM recovery plan instructions
prefix definitions.

ANR6730I Audit command: Primary storage pools to ANR6734E Command: Volume volume name not
be restored by DRM not found - entry processed: library library name not
will be created. defined.
Explanation: A database audit process finds no entries Explanation: The indicated volume is not processed
in server database for primary storage pools to be since the designated library has not been defined or has
restored by DRM. Because FIX=YES has been specified been deleted.
for the audit command, the audit function creates an
entry using the default value in the server database for
the primary storage pools to be restored by DRM. User Response: Reissue the command using a
different library name, or define the library before
retrying the command.
SET DRMPRIMSTGPOOL command to change the
ANR6735E Audit command: Courier information for
ORM not found.
ANR6731E Audit command: Copy storage pools to be
in server database for courier name definitions used by
managed by DRM not found.
DRM Offsite Recovery Media (ORM).
in server database for copy storage pools to be
managed by DRM. User Response: Issue the audit command again and
ANR6736I Audit command: Courier information for
ORM not found - entry will be created.
ANR6732I Audit command: Copy storage pools to be
in server database for courier name definitions used by
managed by DRM not found - entry
DRM Offsite Recovery Media (ORM). Because FIX=YES
will be created.
has been specified for the audit command, the audit
Explanation: A database audit process finds no entries function creates an entry using the default value in the
in server database for copy storage pools to be server database for the courier name definitions.
managed by DRM. 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 User Response: To override the default value, issue a
the copy storage pools to be managed by DRM. SET DRMCOURIERNAME command to change the
ANR6737E Audit command: Vault name for ORM not
SET DRMCOPYSTGPOOL command to change the
found.
in server database for vault name definitions used by
ANR6733E Command: Cannot complete initialization
for process name process.
Explanation: The indicated process fails during
process initialization. User Response: Issue the audit command again and
System Action: The indicated command is ended and
server processing continues.
ANR6738I Audit command: Vault name for ORM not
User Response: This usually indicates that sufficient
found - entry will be created.
server memory is not available on the server. Allocate
additional storage to the server. For details, issue HELP Explanation: A database audit process finds no entries
MEMORY to display the information online or see in server database for vault name definitions used by
“Appendix A. Allocating Additional Server Memory”. DRM Offsite Recovery Media (ORM). Because FIX=YES
server database for the vault name definitions.

ANR6743E Audit command: File process indicator for
SET DRMVAULTNAME command to change the value
ORM not found.
in server database for file process definitions used by
ANR6739E Audit command: Database backup series
expiration days for ORM not found.
in server database for database backup series expiration User Response: Issue the audit command again and
days definitions used by DRM Offsite Recovery Media specify FIX=YES to correct the error.
(ORM).
System Action: Audit processing continues. ANR6744I Audit command: File process indicator for
specify FIX=YES to correct the error. Explanation: A database audit process finds no entries
in server database for file process definitions used by
DRM Offsite Recovery Media (ORM). Because FIX=YES
ANR6740I Audit command: Database backup series
expiration days for ORM not found -
entry will be created.
server database for the file process definitions.
in server database for database backup series expiration
days definitions used by DRM Offsite Recovery Media User Response: To override the default value, issue a
(ORM). Because FIX=YES has been specified for the SET DRMFILEPROCESS command to change the value
audit command, the audit function creates an entry after the audit command has completed.
using the default value in the server database for the
database backup series expiration days definitions.
ANR6745E Audit command: DRM recovery media ID
System Action: Audit processing continues. assignments are incorrect.
User Response: To override the default value, issue a Explanation: A database audit process finds that the
SET DRMDBBACKUPEXPIREDAYS command to global attributes recovery media id used for server
change the value after the audit command has DRM activities are incorrect.
completed.
ANR6741E Audit command: Check label indicator for
FIX=YES specified so that the DRM global attributes
ORM not found.
can be corrected.
in server database for check label definitions used by
ANR6746I Audit command: DRM recovery media ID
assignments are incorrect - values will
System Action: Audit processing continues. be corrected.
User Response: Issue the audit command again and Explanation: A database audit process finds that the
specify FIX=YES to correct the error. global attributes recovery media ID used for server
DRM activities are incorrect. Since FIX=YES has been
specified on the AUDIT command, the attribute value
ANR6742I Audit command: Check label indicator for
will be corrected in the server database.
in server database for check label definitions used by User Response: None.
DRM Offsite Recovery Media (ORM ). Because
ANR6747I Number of volumes processed: number
audit function creates an entry using the default value
in the server database for the check label definitions. Explanation: The MOVE DRMEDIA command has
processed the number of volumes displayed. This
message may be displayed in response to a QUERY
User Response: To override the default value, issue a PROCESS command for a MOVE DRMEDIA command.
SET DRMCHECKLABEL command to change the value

ANR6748I Number of volumes processed: number. ANR6752W Disaster recovery manager operation
Checking out volume volume name from Command being processed is in violation of
library library name. server license terms - server is not
licensed for disaster recovery manager
Explanation: The MOVE DRMEDIA command
support.
displays the number of volumes already processed and
the name of the volume currently being checked out Explanation: The server warns about a disaster
from the indicated library. This message may be recovery manager operation because the server is not
displayed in response to a QUERY PROCESS command licensed to support disaster recovery manager.
for a MOVE DRMEDIA command.
User Response: Obtain the license to support disaster
User Response: None. recovery manager from your service provider or
reseller. Issue the REGISTER LICENSE command with
this license to enable disaster recovery manager
ANR6749I Command: process process ID terminated
support.
before completion - process canceled.
Explanation: The indicated background process
ANR6753E command being processed encountered an
performing the command shown has been canceled.
internal server error while checking
System Action: If other processes are executing, these license compliance.
processes continue.
User Response: None. in determining whether the server is in compliance
with license terms.
ANR6750E Disaster recovery manager operation System Action: Server operation continues.
command being processed is denied - server
User Response: Issue the QUERY LICENSE and
is not in compliance with license terms.
QUERY STATUS commands to determine if the server
Explanation: The server refuses a disaster recovery is in compliance with license terms. Start an AUDIT
manager operation because the current server LICENSES process to adjust server license information.
configuration is not in compliance with the license When this process completes, start the session again. If
terms. the problem persists, contact your service
representative.
System Action: Server operation continues. Disaster
recovery operations cannot be performed until the
server is licensed for the Tivoli Disaster Recovery ANR6754I Machine machine name characteristics
Manager product. deleted.
User Response: Issue a QUERY LICENSE command Explanation: A DELETE MACHINE command has
to determine which license terms are not in compliance. deleted the requested characteristics from the server.
ANR6751E Disaster recovery manager operation
command being processed is denied - server
is not licensed for disaster recovery
manager support. ANR6755I Machine machine name recovery
instructions deleted.
Explanation: The server refuses a disaster recovery
manager operation because the server is not licensed to Explanation: A DELETE MACHINE command has
support the disaster recovery manager. deleted the requested recovery instructions from the
server.
User Response: Obtain the license to support the
disaster recovery manager from your service provider User Response: None.
or reseller. Issue the REGISTER LICENSE command
with this license to enable the disaster recovery
ANR6756E Machine machine name characteristics not
manager support.
defined to the server.
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.

System Action: The server operation continues, but v The length of the command created after replacing
the command has no effect. the substitution variables &VOL, &VOLDSN, &NL,
and &LOC exceeds the server allowable command
line length (1500).
a machine that has characteristics defined to the server.
System Action: The server stops processing the
command.
ANR6757E Machine machine name recovery
instructions not defined to the server. User Response: Issue the command again and specify
a valid executable command with the CMD parameter.
Explanation: A DELETE MACHINE command cannot
delete the requested recovery instructions from the In the case where volumes are being ejected from the
server. The recovery instructions for the specified library, it is possible the server database does not reflect
machine are not defined to the server. the true state of the volume. For MOVE DRMEDIA,
rerun the command after determining the cause of the
System Action: The server operation continues, but
error. For MOVE MEDIA, an update volume command
the command has no effect.
should be issued setting the access of the volume to
User Response: Issue the command again and specify read only.
a machine that has recovery instructions defined to the
If this message is issued by a MOVE or QUERY
server.
DRMEDIA command and the volume record has been
deleted from the server database, you can not use the
ANR6758E Command: Only one character string can MOVE or QUERY DRMEDIA commands to create the
be specified. command file entry for this volume. In this case, you
must manually issue the proper command.
Explanation: The INSERT command is invalid. Either
a characteristics string can be specified or a recovery
instructions string can be specified on the command. ANR6761E Command: WHERESTATE parameter is
Both types of strings cannot be specified on the required.
command at the same time.
Explanation: The indicated command specifies a
System Action: The server does not process the volume name containing a pattern matching character
command. and the TOSTATE parameter. The WHERESTATE
parameter is not specified. The specification is invalid.
User Response: Issue the command again and specify Pattern-matching for volume names is only allowed
one valid character string. when the WHERESTATE parameter is specified.
ANR6759E Disaster recovery manager operation command.
command being processed is denied -
disaster recovery manager support is not User Response: Reissue the command specifying a
available for server platform platform. specific volume name or by specifying the
WHERESTATE parameter along with the TOSTATE
Explanation: The server refuses a disaster recovery parameter.
manager operation because disaster recovery manager
support is not available for the indicated server
platform. ANR6762E Command: The specified destination state
tostate is invalid for volume volume name
System Action: Server operation continues. in current state state.
User Response: None. Explanation: The indicated command specifies a
destination state that is invalid for the volume name
ANR6760E Command: Executable command line shown in the indicated current state.
exceeds maximum length characters for System Action: The server does not process the
volume volume name. volume.
Explanation: While writing to a command file, one of User Response: Issue the command again and specify
the following conditions occurred: a valid destination state for the volume name shown.
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 ANR6763I Command: The specified command has
written (255). 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 System Action: The server does not process the
processed. command.
System Action: None. User Response: Reissue the command specifying a
valid prefix.
User Response: Execute the commands written to the
file.
ANR6769E Audit command: Not mountable name
information for ORM not found.
ANR6764E command: Command file name exceeds
maximum characters characters. Explanation: A database audit process finds no entries
in server database for not mountable location name
Explanation: The file name specified for containing
definitions used by DRM Offsite Recovery Media
the executable commands generated by DRM exceeds
(ORM).
the maximum valid length shown.
command. User Response: Issue the audit command again and
valid file name.
ANR6770I Audit command: Not mountable name
information for ORM not found - entry
ANR6765E Command: Invalid not mountable
will be created.
location name - not mountable name.
in server database for not mountable location name
entered with an invalid not mountable location name.
definitions used by DRM Offsite Recovery Media
System Action: The server does not process the (ORM). Because FIX=YES has been specified for the
command. audit command, the audit function creates an entry
using the default value in the server database for the
User Response: Reissue the command with a valid courier name definitions.
not mountable location name.
ANR6766E Command: No command string is User Response: To override the default value, issue a
specified for FORMAT=CMD. SET DRMNOTMOUNTABLENAME command to
Explanation: The indicated command has been completed.
entered with a FORMAT=CMD to write a command
string to a file, but no command string is specified.
ANR6771E Audit command: Command file name
System Action: The server does not process the information for ORM not found.
command.
User Response: Reissue the command specifying a in server database for command file name definitions
command string to be written to a file. used by DRM Offsite Recovery Media (ORM).
ANR6767E Command: Invalid command file name -
command file name. User Response: Issue the audit command again and
entered with an invalid command file name.
ANR6772I Audit command: Command file name
System Action: The server does not process the information for ORM not found - entry
command. will be created.
User Response: Reissue the command with a valid Explanation: A database audit process finds no entries
command file name. in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM). Because
ANR6768E command: Prefix exceeds maximum FIX=YES has been specified for the audit command, the
characters characters. audit function creates an entry using the default value
in the server database for the command file name
Explanation: The prefix specified for recovery plan definitions.
files or for plan instructions files exceeds the maximum
valid length. The maximum valid length is shown in System Action: Audit processing continues.
the message. User Response: To override the default value, issue a

SET DRMCMDFILENAME command to change the deleted from the server database, you can not use the
value after the audit command has completed. MOVE or QUERY DRMEDIA commands to create the
command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6773E Command: Unable to open file ’command
file name’ for output.
ANR6776E Command: Could not delete file: file name
Explanation: An error occurred while opening the
command file name shown. The file name shown in the Explanation: The indicated command failed but the
message is specified with the indicated command, the file created could not be deleted.
SET command, or the default name generated by the
indicated command.
User Response: Delete the file shown.
indicated command.
ANR6777E Command: Command file ’file name’
already in use.
any problems, if possible. Make sure that the server has Explanation: The command indicated references a
proper authority to write to the file indicated. In AIX, command file name that is in use. The command file
make sure that the file name specified in the command name shown is selected for use by the server in the
or in the SET command is a full path file name, not a following order:
directory path name. In MVS, make sure that the file v The file name specified on the indicated command.
name specified in the command or in the SET
command is a valid MVS file name. Reissue the v The file name specified on the SET command.
command after determining the cause of the error. v The file name generated by the server (AIX only).
ANR6774E Command: Invalid volume transition command.
states - from ’specified WHERESTATE’
User Response: Reissue the command at a later time
state to ’specified TOSTATE’ state.
or reissue the command specifying a different
Explanation: The TOSTATE specified is an invalid command file name.
destination state for the WHERESTATE specified.
System Action: The server does not process the ANR6778E Command: Volume volume name not
command. processed: device type device type not
supported.
a valid destination state. Explanation: The indicated volume is not processed
because the device type shown is not supported by the
function.
ANR6775E Command: Error writing to file ’file name’
for volume volume name. System Action: The indicated volume is not
processed.
Explanation: An error occurred while writing to the
file name shown for the indicated volume. User Response: None.
System Action: The server stops processing the

command. ANR6779E Disaster recovery manager operation
command being processed is denied -
User Response: Examine error messages that may disaster recovery manager support is not
have been displayed prior to this message and correct available for server platform.
proper authority to write to the file indicated. Reissue Explanation: The server refuses a disaster recovery
the command after determining the cause of the error. manager operation because disaster recovery manager
support is not available for the server platform.
In the case where volumes are being ejected from the
library, it is possible the server database does not reflect System Action: Server operation continues.
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 ANR6780E Audit command: An invalid recovery plan
read only. file expiration days encountered.
If this message is issued by a MOVE or QUERY Explanation: A database audit process encounters an
DRMEDIA command and the volume record has been invalid value for recovery plan file expiration days.

System Action: Audit processing continues. System Action: Server operation continues.
User Response: Issue the command again and specify User Response: None.
FIX=YES to correct the expiration days. Or, issue an
SET DRMRPFEXPIREDAYS command and specify a
ANR6785W Warning: The ADSM V3 Disaster
new expiration days value.
Recovery Manager Disk Image Dump
function is not supported in the Tivoli
ANR6781I Audit command: An invalid recovery plan Disaster Recovery Manager. The ADSM
file expiration days encountered - the V3 DRM Disk Image Restore function
default value will be set. has been stabilized with no new
maintenance or hardware support
planned.
invalid value for recovery plan file expiration days.
Because FIX=YES has been specified, the audit function Explanation: None.
sets the expiration days value to the default value.
System Action: DRM Disk Image Dump and Restore
System Action: Audit processing continues. function continues.
User Response: To override the default value, issue a User Response: None.
SET DRMRPFEXPIREDAYS command to change the
ANR6900I Command: The recovery plan file file
name was created.
ANR6782E Audit command: Recovery plan file
Explanation: The recovery plan file was created.
expiration days not found.
in server database for recovery plan file expiration days User Response: None.
definitions.
System Action: Audit processing continues. ANR6901I Number of plan stanzas processed:
number.
specify FIX=YES to correct the error. Explanation: The PREPARE command has processed
the number of stanzas displayed. This message may be
ANR6783I Audit command: Recovery plan file
for a PREPARE command.
expiration days not found - entry will
be created. System Action: Server operation continues.
Explanation: A database audit process finds no entries User Response: None.
in server database for recovery plan file expiration days
definitions. Because FIX=YES has been specified for the
audit command, the audit function creates an entry ANR6902I Number of plan stanzas processed:
using the default value in the server database for the number. Currently processing stanza:
recovery plan file expiration days definitions. recovery plan stanza name.
System Action: Audit processing continues. Explanation: The PREPARE command displays the
number of stanzas already processed and the name of
User Response: To override the default value, issue a the stanza currently being processed. This message may
SET DRMRPFEXPIREDAYS command to change the be displayed in response to a QUERY PROCESS
value after the audit command has completed. command for a PREPARE command.
volumes processed. Volumes sent to library User Response: None.
library name for checkout: number volumes
sent. ANR6903I Cancel in progress.
Explanation: The MOVE DRMEDIA command has Explanation: The PREPARE command has been
processed the number of volumes shown. Currently, the canceled and will end when resources have been freed
MOVE DRMEDIA command has sent for processing for the background process. This message may be
the number of volumes shown to the library shown. displayed in response to a QUERY PROCESS command
This message may be displayed in response to a for a PREPARE command.
QUERY PROCESS command for a MOVE DRMEDIA
command. System Action: Server operation continues.

ANR6904I Sending recovery plan file to target ANR6916W Command: No copy storage pools are
server. defined.
Explanation: The PREPARE command is sending the Explanation: The server has no copy storage pools
recovery plan file to the target server. This message defined.
may be displayed in response to a QUERY PROCESS
System Action: Recovery plan file will not contain
command for a PREPARE command.
copy storage pool information.
User Response: Define copy storage pools in the
User Response: None. server.
ANR6905I Command: Recovery plan file RPF volume ANR6918W Command: Recovery instructions file file
name was created. Specified device class name not found.
device class name.
Explanation: A source file for recovery instructions
Explanation: The recovery plan file was created on the was not found.
target server.
System Action: The recovery plan will not contain
System Action: Server operation continues. recovery instructions.
User Response: None. User Response: To get recovery instructions in the
recovery plan, ensure the corresponding instructions
source file exists. If it does, check authorizations to the
ANR6912W Command: The database was not backed
file.
up.
Explanation: No backups have been made of the
ANR6920W Command: Generated replacement
server data base.
volume name volume name is not valid
System Action: Stanzas in the recovery plan do not for server device type device type.
include database recovery information. Original volume name: volume name.
Stanza is stanza name.
User Response: Backup the server data base by
issuing the BACKUP DB command. Explanation: Appending the replacement volume
name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name
ANR6913W Command: No volumes with backup data has created a name that is not valid for the server
exist in copy storage pool storage pool device type shown.
name.
System Action: Replacement volume name is used in
Explanation: A copy storage pool does not contain the recovery plan stanza.
any volumes with usable data.
User Response: Devise a naming convention that
System Action: Stanzas in the recovery plan do not allows the use of the replacement volume name postfix
include recovery information for any volumes in the or at restore time manually update the generated
storage pool. recovery plan with a legal replacement name. For
User Response: Determine why this storage pool has additional information and related commands, refer to
no volumes with usable data. the Administrator’s Reference for your particular
platform.
ANR6915W Command: Storage pool storage pool name

storage pool type is not defined to the ANR6921W Command: Cannot locate server options
server. file ’file name’.
Explanation: A storage pool that is not defined to the Explanation: The Prepare command cannot open the
server was specified by SET DRMPRIMSTGPOOL, SET specified server options file.
DRMCOPYSTGPOOL, or on the PREPARE command System Action: VOLHISTORY and DEVCONFIG
line. options are added to the recovery plan file stanza
System Action: Stanzas in the recovery plan do not DSMSERV.OPT.FILE.
include recovery information for the storage pool. User Response: None.
User Response: Correct the storage pool specification
or define the storage pool to the server.

after the appropriate commands have been issued to
ANR6922W Command: No machine information was
define the recovery media. For additional information
defined for the machine that contains
and related commands, refer to the Administrator’s
server server name.
Explanation: The machine information has not been
saved in the server data base.
ANR6926W Command: There is at least one invalid
System Action: The recovery plan file does not generated volume name associated with
contain the machine and recovery media information storage pool storage pool server device
stanzas. type device type in stanza stanza name.
User Response: If you want to include the machine Explanation: Appending the replacement volume
information in the recovery plan file, issue the DEFINE name postfix (as defined with SET
MACHINE command to save the machine information DRMPLANVPOSTFIX) to the original volume name
in the server data base and reissue the PREPARE has created a name that is not valid for the server
command. device type shown.
ANR6923W Command: No recovery media defined the recovery plan stanza.
for machine machine name.
User Response: Devise a naming convention that
Explanation: No recovery media has been defined to allows the use of the replacement volume name postfix
the server for the specified machine. or at restore time manually update the generated
recovery plan with a legal replacement name. For
System Action: The recovery plan file does not
additional information and related commands, refer to
contain the machine recovery media stanza.
the Administrator’s Reference for your particular
User Response: If you want to include the machine platform.
recovery media information in the recovery plan file,
issue the DEFINE RECOVERYMEDIA command.
ANR6927W Command: Primary storage pool storage
Reissue the PREPARE command after the appropriate
pool name, storage pool data format, is not
commands have been issued to define the recovery
managed by DRM.
media. For additional information and related
commands, refer to the Administrator’s Reference for Explanation: A primary storage pool with
your particular platform. DATAFORMAT=NETAPPDUMP was specified by SET
DRMPRIMSTGPOOL or on the PREPARE command
line.
ANR6924W Command: No recovery instructions
defined for machine machine name. System Action: Stanzas in the recovery plan do not
include recovery information for the storage pool.
Explanation: No recovery instructions have been
defined to the server for the specified machine. User Response: Correct the storage pool specification.
System Action: The recovery plan file does not
contain the machine recovery instructions stanza. ANR6928W Command: No eligible primary storage
pools match the specified storage pool
User Response: If you want to include the machine
name storage pool name .
recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command Explanation: The storage pool specified by SET
after the appropriate commands have been issued to DRMPRIMSTGPOOL or on the PREPARE command
define the recovery media. For additional information line does not match any eligible primary storage pool.
and related commands, refer to the Administrator’s Possible reasons include:
Reference for your particular platform. v Primary storage pools were not defined.
v Primary storage pools were defined, but their data
ANR6925W Command: No machine characteristics format is NETAPPDUMP.
defined for machine machine name. v The name specified does not match eligible primary
Explanation: No characteristics have been defined to storage pool names.
the server for the specified machine. System Action: Stanzas in the recovery plan do not
System Action: The recovery plan file does not include recovery information for the storage pools.
contain the machine characteristics stanza. User Response: Correct the storage pool specification
User Response: If you want to include the machine or define eligible storage pools to the server.
recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command

System Action: The function waits for the mount
ANR6929W Command: No eligible primary storage
point.
pools are defined to the server.
Explanation: The server has no eligible primary
storage pools defined.
ANR6942E Query recovery plan file content is
System Action: Recovery plan file will not contain
waiting for access to input volume
primary storage pool information.
volume name.
User Response: Define eligible primary storage pools
Explanation: Query recovery plan file content has
to the server.
begun to wait for availability of the input volume
shown.
ANR6937E command: parameter name parameter not
System Action: The function waits for the volume to
allowed from the command line.
become available.
Explanation: The parameter shown is not allowed
from the command line interface.
command.
waiting for mount of input volume
User Response: Reissue the command with the volume name.
parameter from the web.
begun to wait for the mount of the input volume
ANR6938I No information found for stanza stanza shown.
name.
System Action: The function waits for mount.
Explanation: No information found for recovery plan
file stanza shown.
System Action: The server does not display the
ANR6944E Command: Invalid recovery plan file
information for the stanza.
name - recovery plan file name.
User Response: None
Explanation: The recovery plan file name specified in
the command is invalid.
ANR6939E Command: Invalid recovery plan file
stanza name - stanza name.
command.
Explanation: The specified recovery plan file stanza
name is invalid.
a valid recovery plan file name.
command.
ANR6945E Command: Cannot find filespace filespace
User Response: Issue the command again and specify name for recovery plan file recovery plan
a valid recovery plan file stanza name. file name.
Explanation: The server cannot find the filespace
ANR6940E command command not allowed from (ADSM.SERVER) for recovery plan file specified in the
server console. server.
Explanation: The indicated command is not allowed System Action: The retrieve operation ends, and the
to be issued from the server console. server operation continues.
System Action: The command is not executed. User Response: Issue QUERY FILESPACE command
on the target server to see if there is any filespaces
User Response: Reissue the command from an
created for the recovery plan file. The filespace name
administrator using an Administrative Client.
for the recovery plan file is ADSM.SERVER.

ANR6946E Command: Retrieve failed for recovery
waiting for mount point in device class
plan file name - error on input storage
device class name.
device.
Explanation: The server ends an retrieve operation
begun to wait for a mount point that can be used for a
because an I/O error has been encountered by the
volume in the device class shown.
server in reading from a device.

System Action: The retrieve operation ends, and the
ANR6951E Command: Recovery plan file file name
was not created.
Explanation: Due to a processing error, a recovery
messages preceding this one that specify the device that
plan file was not created.
is failing. The server may need to be shut down with
the HALT command to correct the hardware problem. System Action: Recovery plan file not created.
ANR6947E Command: Data storage retrieve failed have been displayed prior to this message and correct
for recovery plan file name - data integrity any problems, if possible. Make sure that the server has
error detected. proper authority to write to the file indicated and that
there is sufficient space in the file system for the file.
Explanation: The server ends the retrieve operation
Reissue the command, after determining the cause of
because an internal database integrity error has been
the error.
encountered on the server.
System Action: The retrieve operation ends, and the
ANR6952E Command: File name file name already
exists.
Explanation: File already exits.
ANR6948E Command: Cannot find the recovery plan
file for Recovery plan file name. User Response: Determine why file already exists. If
possible, delete it. Reissue the command, after
Explanation: The server cannot find the specified
determining the cause of the error.
recovery plan file.
ANR6953E Command: File write error.
command.
recovery plan file.
a valid recovery plan file name. Use the QUERY
RPFILE command to view the name of the recovery System Action: The recovery plan file was not
plan file that you are interested in displaying its created.
content.
ANR6949E Command: No matching device class any problems, if possible. Make sure that there is
defined. sufficient space in the file system for the file. Reissue
the command after determining the cause of the error.
Explanation: The device class specified in the
command does not match any device class defined to
the server. ANR6954E Command: Unable to open file ’file name’
for output.
command. Explanation: An error occurred while opening the
recovery plan file for output.
a valid device class. System Action: The recovery plan file was not
created.
ANR6950E Command: The recovery plan file was not User Response: Examine error messages that may
created. have been displayed prior to this message and correct
proper authority to write to the file indicated. Reissue
plan file was not created.
the command after determining the cause of the error.
System Action: Recovery plan file not created.
User Response: Examine error messages that may ANR6959E Command: Plan instructions prefix
have been displayed prior to this message and correct ’instructions prefix’ is not valid.
any problems, if possible. Reissue the command, after
Explanation: The prefix specified for recovery
instructions is not valid.
System Action: The recovery plan file was not
created.

User Response: Reissue the command specifying a User Response: Issue a QUERY ACTLOG command
valid prefix. to view the activity log and search for messages. If the
ANR6960E Command: Recovery plan prefix ’plan
prefix’ is not valid.
ANR6966E Command: Query database volume failed.
Explanation: The prefix specified for the recovery plan
file is too long. Explanation: A server database query error occurred.
This message always accompanies another error
message and provides more detail about that error.
created.
created.
valid prefix.
User Response: Issue a QUERY ACTLOG command
to view the activity log and search for messages. If the
ANR6962E Command: Query database failed.
Explanation: A server database query error occurred. service representative.
ANR6967E Command: Query log volume failed.
Explanation: A server database query error occurred.
created.
User Response: Issue a QUERY ACTLOG command message and provides more detail about that error.
created.
ANR6963E Command: Query log failed.
Explanation: A server database query error occurred. service representative.
ANR6968E Command: Query volume history failed.
Explanation: An server database query error occurred.
created.
created.
ANR6964E Command: Query storage pool failed.
Explanation: An server database query error occurred. service representative.
ANR6969E Command: Query device class failed.
Explanation: An server database query error occurred.
created.
created.
ANR6965E Command: Query volume failed.
Explanation: An server database query error occurred. service representative.
created.

ANR6970E Command: A recovery plan file is already ANR6975E Command: Unable to read file file name.
being created.
Explanation: An error occurred while PREPARE was
Explanation: The server command processor will not attempting to read the local recovery plan file copy in
start a background process to execute another order to send it to the target server.
PREPARE command.
System Action: The recovery plan file is not stored on
System Action: The command process ends and the target server.
User Response: Reissue the command after the first have been displayed prior to this message and correct
PREPARE command has completed. any problems, if possible. Reissue the command after
ANR6971E Command: Could not delete plan file plan
file name. ANR6976E Command: The recovery plan file was not
stored on another server and the local
Explanation: Prepare command failed but the plan file
copy file name cannot be deleted.
created could not be deleted.
plan file was not stored on target server and the local
User Response: Delete the plan file. 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. have been displayed prior to this message and correct
This message always accompanies another error any problems, if possible. After determining the cause
message and provides more detail about that error. of the error, re-issue the PREPARE command and
delete the local recovery plan file.
created.
ANR6977E Command: Device class name device class
User Response: Issue a QUERY ACTLOG command name exceeds maximum characters
to view the activity log and search for messages. If the characters.
service representative. 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
ANR6973E Command: Query recovery media failed. shown in the message.
Explanation: A server recovery media query error System Action: The server does not process the
occurred. This message always accompanies another command.
error message and provides more detail about that
error. User Response: Reissue the command specifying a
valid device class name.
created.
ANR6978E Command: Invalid device class device class
User Response: Issue a QUERY ACTLOG command name.
error cannot be isolated and resolved, contact your Explanation: The specified device class cannot be used
service representative. by the command shown. Possible reasons include:
v The device class is not defined.
ANR6974E Command: Unable to open file file name. v The device class is defined but not of type SERVER.
Explanation: An error occurred while PREPARE was v The name specified is an invalid device class name.
attempting to open the local recovery plan file copy in System Action: The server does not process the
order to send it to the target server. command.
System Action: The recovery plan file is not stored on User Response: Reissue the command with a valid
the target server. device class.
any problems, if possible. Reissue the command after

ANR6979E Command: Recovery plan file was not ANR6986E Command: The DELETELATEST
created. Specified device class device class parameter is only valid for volume
name. history types RPFILE or
RPFSNAPSHOT.
Explanation: A recovery plan file cannot be not
created using the specified device class. Explanation: The command failed because an invalid
volume history type was specified for the TYPE=
parameter.
System Action: The command fails, and server
any problems, if possible. Reissue the command, after
determining the cause of the error. User Response: Re-issue the command and specify a
valid type value.
ANR6980E Command: Prefix prefix exceeds maximum
characters characters. ANR7800I DSMSERV generated at time on date.
Explanation: The command shown has been entered Explanation: The server module was generated at the
and specifies a plan or instructions prefix that is too indicated date and time.
long. The maximum valid length is shown in the
message.
command.
ANR7800I (HP-UX) DSMSERV generated at time on
date.
shorter prefix.
Explanation: The server module was generated at the
indicated date and time.
ANR6984E Command: Out of space on sequential
media, scratch media could not be System Action: Server operation continues.
mounted. Specified device class device
class name; maximum capacity: number of User Response: None.
bytes bytes.
Explanation: During command PREPARE processing, ANR7800I (Solaris) DSMSERV generated at time on
the process encounters an out-of-space condition date.
writing to the sequential media. Command PREPARE Explanation: The server module was generated at the
ends when there is no more space on the sequential indicated date and time.
media for storing data.
System Action: Command PREPARE processing ends.
Server processing continues. User Response: None.
User Response: Increase the device class maximum

capacity and reissue the PREPARE command. If an ANR7800I (Windows NT) DSMSERV generated at
object was created on the target server, issue the time on date.
RECONCILE VOLUMES FIX=YES to delete the object Explanation: The server module was generated at the
from the target server. indicated date and time.
data storage - volume already in use. User Response: None.
Explanation: During command command processing, a

volume cannot be used because it is already defined in ANR7801I Subsystem (master) PID is process
a storage pool, or has been previously used by an identifier.
export, database dump, database backup, or DRM Explanation: The server kernel extension process has
prepare operation or is in use by another process. the indicated process identifier.
System Action: The command command operation is System Action: Server operation continues.
User Response: Re-issue the PREPARE command.

ANR7801I (HP-UX) • ANR7805E
ANR7801I (HP-UX) Subsystem (master) process ID is ANR7804I An server is already running from this
process identifier. directory.
Explanation: The server’s master HP-UX process has Explanation: The server has attempted to open the
the indicated process identifier. adsmserv.lock file in the current directory but failed to
do so because an existing server already has the file
open.
System Action: Server terminates.
User Response: Examine the contents of the
ANR7801I (Solaris) Subsystem process ID is process
adsmserv.lock file. The process ID for the server that is
identifier.
running is recorded in this file. Two servers cannot be
Explanation: The server process has the indicated started from the same directory. You may remove the
process identifier. adsmserv.lock file and attempt to start the server ONLY
if the recorded process ID is NOT currently running
System Action: Server operation continues. dsmserv. The 'ps -e' AIX command can be used to
User Response: None. display processes that are currently running.
ANR7802E Shared memory segments for a server ANR7804I (HP-UX) A server is already running from
running in the current directory already this directory.
exist. The -F parameter can be used to Explanation: The server has attempted to open the
overwrite. adsmserv.lock file in the current directory but failed to
Explanation: Shared memory segments are created for do so because an existing server already has the file
each instance of the server based on the current open.
directory. This message indicates that the shared System Action: Server terminates.
memory segments already exist. A server is presently
running from the current directory or a server running User Response: Examine the contents of the
from the current directory ended abnormally. adsmserv.lock file. The process ID for the server that is
running is recorded in this file. Two servers cannot be
System Action: The server terminates. started from the same directory. You may remove the
User Response: If the server running in the current adsmserv.lock file and attempt to start the server ONLY
directory terminated abnormally, start dsmserv with the if the recorded process ID is NOT currently running
-F parameter to force the existing shared memory dsmserv. The 'ps -e' command can be used to display
segments to be overwritten. If you want to run processes that are currently running.
multiple instances of the server, each instance must be
run from a separate directory with a separate ANR7805E Volume volume name is in use by another
dsmserv.dsk file and have separate log, database, and server.
storage volumes.
Explanation: The server has attempted to open a disk
volume but has discovered that the volume is in use by
ANR7803E Attempt to overwrite a shared memory another server.
segment, as directed with the -F
parameter, FAILED. System Action: The open operation fails for the
volume.
Explanation: The server has been started with the -F
parameter and unsuccessfully attempted to overwrite User Response: To prevent concurrent RAW volume
existing shared memory segments. This error occurs access by more than one server, files are created in the
when the user that starts the server with -F parameter /tmp directory to 'lock' these volumes. The names of
is not the owner of the shared memory segments and these temporary files are
lacks the required authority. /tmp/adsm.disk.dev.<volumename> where
<volumename> is the name of the RAW volume
System Action: Server terminates. defined in the /dev directory. Please note that the name
User Response: Resolve the authorization problem for the logical volume as defined in SMIT is
and restart the server. 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

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

ANR7807W Unable to get information for file file.
Explanation: The server was unable to open the
indicated file. Explanation: The server was unable to get information
about the indicated file.
System Action: The operation that was to use the
indicated file fails. A subsequent unnumbered message System Action: The operation that was to use the
had details from the system. indicated file fails. A subsequent, unnumbered message
has details from the system.
User Response: Determine the reason for being unable
to open the file and re-attempt the operation. Common User Response: Determine the reason for being unable
reasons for being unable to open the file include to access the file and re-attempt the operation.
providing the wrong name, having insufficient Common reasons for being unable to access the file
authorization to open the file and not being the file’s include providing the wrong name, having insufficient
owner. authorization to open the file and not being the file’s
owner.
ANR7806W (HP-UX) Unable to open file file.

ANR7807W (HP-UX) Unable to get information for
Explanation: The server was unable to open the file file.
indicated file.
Explanation: The server was unable to get information
System Action: The operation that was to use the about the indicated file.
indicated file fails. A subsequent unnumbered message
had details from the system. System Action: The operation that was to use the
indicated file fails. A subsequent, unnumbered message
User Response: Determine the reason for being unable has details from the system.
to open the file and re-attempt the operation. Common

ANR7807W (Solaris) • ANR7811E (Solaris)
User Response: Determine the reason for being unable operation. Each thread started by the server is an AIX
to access the file and re-attempt the operation. process. To change the number of processes per user,
Common reasons for being unable to access the file use the SMIT menus for System Environment, and
include providing the wrong name, having insufficient choose Change / Show Characteristics of Operating
authorization to open the file and not being the file’s System. You may also use SMIT to determine if the
owner. number of applications is causing a memory shortage.
It may be necessary to decrease the maximum number
of client sessions by changing the MAXSESSIONS
ANR7807W (Solaris) Unable to get information for
option in the server options file.
file file.
Explanation: The server was unable to get information
ANR7810E (HP-UX) Error creating console input
about the indicated file.
thread.
System Action: The operation that was to use the
Explanation: Unable to start console input thread.
indicated file fails. A subsequent, unnumbered message
has details from the system. System Action: Server operation stops.
User Response: Determine the reason for being unable User Response: See other issued messages.
to access the file and re-attempt the operation.
Common reasons for being unable to access the file
ANR7810E (Solaris) Error creating console input
include providing the wrong name, having insufficient
thread.
authorization to open the file, not being the file’s
owner, or too many soft links to the file. If trying to Explanation: Unable to start console input thread.
access a RAW partition, the server must be started with
superuser privileges. System Action: Server operation stops.
User Response: See other issued messages.
ANR7808W root user authority required for
non-default scheduling policy. ANR7811I Direct I/O will be used for all eligible
Explanation: The server was unable to use the disk files.
scheduling policy specified in the options file. The Explanation: All disk files which meet eligibility
server must be running with root authority to use any requirements will be opened with the O_DIRECT flag.
scheduling policy other than the default.
System Action: Operations continue.
System Action: Operation continues but with the
default scheduling policy. User Response: None
User Response: Run the server with root authority or

don’t specify a scheduling policy in the options file. ANR7811E (HP-UX) Insufficient memory for console
initialization.
ANR7809I Using scheduling policy policy. Explanation: The server is unable to allocate enough
memory for console initialization.
Explanation: All threads in the server will use the
specified scheduling policy. System Action: Server operation stops.
System Action: Operations continue User Response: Ensure that there is sufficient paging
space for HP-UX. It may be necessary to reduce the
User Response: None maximum number of client sessions by changing the
MAXSESSIONS option in the server options file.
ANR7810W Unable to create a new child process.
Explanation: The server cannot create a new child ANR7811E (Solaris) Insufficient memory for console
thread. initialization.
System Action: Server processing continues. Other Explanation: The server is unable to allocate enough
error messages from the server component are memory for console initialization.
displayed. System Action: Server operation stops.
User Response: Ensure that sufficient paging space is User Response: Ensure that there is sufficient paging
available for AIX. If the server has been started from a space for Sun Solaris. It may be necessary to reduce the
non-root user ID, ensure that the AIX process limit per maximum number of client sessions by changing the
user is sufficient for the server. The server requires MAXSESSIONS option in the server options file.
approximately 24 processes, in addition to one process
per client session, and one process for each background

ANR7812I • ANR7820W (Windows NT)
new user settings to take effect. It may be necessary to
ANR7812I Direct I/O will not be used for any disk
decrease the maximum number of client sessions by
files.
changing the MAXSESSIONS option in the server
Explanation: The AIXDIRECTIO option was specified options file.
as NO, so no disk files will be opened with the
O_DIRECT flag.
ANR7820E Insufficient memory to buffer console
System Action: Server processing continues, but no input; the following input line was
disk files will use the Direct I/O feature of AIX. discarded: discarded console input.
User Response: None Explanation: An error occurs during an attempt to
allocate a buffer large enough to read console input.
ANR7812E (HP-UX) Insufficient memory to buffer System Action: The console input is discarded.
console input. The following input line
User Response: Ensure that sufficient paging space is
was discarded: discarded console input.
available for AIX. You may also use SMIT to determine
Explanation: An error occurs during an attempt to if the number of applications is causing a memory
allocate a buffer to hold the specified console input. shortage. It may be necessary to decrease the maximum
number of client sessions by changing the
System Action: The console input is discarded.
User Response: Ensure that there is sufficient paging
space for HP-UX. It may be necessary to reduce the
ANR7820S (HP-UX) Server thread thread ID
maximum number of client sessions by changing the
terminated in response to program
abort.
Explanation: The thread has ended due to a program
ANR7812E (Solaris) Insufficient memory to buffer
abort.
console input. The following input line
was discarded: discarded console input. System Action: The server completes termination
processing.
Explanation: An error occurs during an attempt to
allocate a buffer to hold the specified console input. User Response: Note the associated messages and
System Action: The console input is discarded.
ANR7820S (Solaris) Server thread thread ID
space for Sun Solaris. It may be necessary to reduce the
terminated in response to program
abort.
abort.
ANR7813W (Solaris) Unable to create a new child
thread. System Action: The server completes termination
processing.
Explanation: The server cannot create a new child
thread. User Response: Note the associated messages and call
System Action: Server processing continues. Other
error messages from the server component are
displayed. ANR7820W (Windows NT) Insufficient Space
Available for file file name.
User Response: Ensure that sufficient swap space is
available for Solaris. The amount of swap available can Explanation: The server was attempting to create a file
be obtain by executing ’swap -l’. If the number of free with the indicated name. There was insufficient space
blocks is low, you can add swap files while the system for the file on the disk.
is running by executing ’mkfile’ and then ’swap -a’. See
System Action: Server processing continues. The file
the Solaris man pages on ’mkfile’ and ’swap’ for more
creation request fails.
details. If the server has been started from a non-root
user ID, ensure that the Solaris process limit per user is User Response: Specify a file name on a drive with
sufficient for the server. You can tune the ’maxusers=##’ sufficient space or change the space request to a value
parameter in the /etc/system file to increase the consistent with the drive.
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

System Action: The server completes termination
ANR7821E Error reading from standard input.
processing.
Explanation: An error occurs during an attempt to
read from standard input.
System Action: The console input thread is
ANR7822I (Solaris) Server thread thread ID
terminated.
terminated in response to server
User Response: Correct the standard input problem shutdown.
and restart the server.
Explanation: The thread has ended due to a server
shutdown.
ANR7821I (HP-UX) Server thread thread ID
terminated in response to external
processing.
signal.
Explanation: The thread has ended due to an external
signal.
ANR7822W (Windows NT) File Already exists when
creating volume file name.
processing.
Explanation: The server was attempting to create a file
with the indicated name. The file already exists.
ANR7821I (Solaris) Server thread thread ID
terminated in response to external
signal. User Response: Specify a new file name. The server
will not use an existing file name when creating a file.
signal.
ANR7823E Insufficient memory for console
initialization.
processing.
Explanation: Unable to allocate enough memory for
console initialization.
System Action: Server operation stops.
ANR7821W (Windows NT) Unable to create
directory when creating volume file User Response: Ensure that sufficient paging space is
name. 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
with the indicated name. A new directory was being
created as well, but its creation failed.
ANR7823W (Windows NT) Unable to create file file
User Response: Specify a file name in an existing name.
directory or change the name request to specify a
different directory name.
with the indicated name. The system reported an error
in creating the file.
ANR7822E Error creating console input thread.
System Action: The server continues processing. The
Explanation: Unable to start console input thread. file creation request fails.
System Action: Server operation stops. User Response: Specify a new file name.
User Response: See other issued messages.
ANR7824E Error loading Async I/O support
module.
ANR7822I (HP-UX) Server thread thread ID
terminated in response to server Explanation: The server attempted to load the Async
shutdown. I/O support module, but the load failed. Refer to
accompanying error message for details on the load
Explanation: The thread has ended due to a server
failure.
shutdown.
System Action: Server operation continues, but

ANR7824S (HP-UX) • ANR7832I
without Async I/O support. code may also be provided to your service
representative for interpretation.
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 ANR7826W (Windows NT) Creation of Volume file
AIX was rebooted after the configuration. name failed. Process was cancelled.
ANR7824S (HP-UX) Server operation terminated. with the indicated name. The attempt was cancelled by
a cancel process command.
Explanation: An error occurs that causes server
operation to stop. System Action: The server continues processing. The
file creation request fails.
User Response: The DEFINE command may be
re-entered.
ANR7824S (Solaris) Server operation terminated.

ANR7830E (Solaris) Invalid RAW Partition Name: A
Explanation: An error occurs that causes server valid raw partition name is in the form
operation to stop. of /dev/.../rdsk/.../* , where ... means 0 or
more directories.
Explanation: Use the proper format for specifying a
User Response: Contact your service representative. Raw partition. The ... means zero or more directories.
System Action: Inform the user to use the right RAW
ANR7824W (Windows NT) Unable to write volume partition specification.
file name.
User Response: Have user reenter the RAW partition
Explanation: The server was attempting to create a file with the proper partition name.
with the indicated name. The server was able to
partially write to the file before running out of space.
ANR7831E (Solaris) raw partition name has an existing
System Action: The server continues processing. The filesystem.
file creation request fails. The file is still present on the
system. Explanation: The RAW partition specified has an
existing Solaris file system on it. Writing to this
User Response: Specify a new file name where there partition will most likely destroy this filesystem.
is sufficient space.
System Action: Warn the user that an existing
filesystem for the raw partition specified may be
ANR7825E (Solaris) Server unable to allocate a destroyed if written to.
shared memory segment of size Client
requested shared memory size. User Response: Determine if user still wants the valid
filesystem data. If not, user needs to destroy the
Explanation: A shared memory client has requested a filesystem by either formatting the partition, create a
shared memory segment size that Solaris is unable to program to destroy the filesystem header information
fulfill. so that the server will not be able to detect the
System Action: Client is not allowed to logon filesystem header information, or rearrange the starting
and ending blocks of a partition by using the Solaris
User Response: See the shared memory tuning guide format() command. The user can read the format()
for Solaris (a Sun document). You may need to increase function in the Sun manuals for further details on
the number/size of shared memory segments and/or filesystems.
message queues.
ANR7832I The thread process ID terminated with

ANR7825W (Windows NT) Unable to create volume exit code program exit code.
file name. Return code= return code.
Explanation: The process has ended with the
Explanation: The server was attempting to create a file indicated exit code. This error is due to the problem
with the indicated name. The attempt failed with the caused and indicated by a preceding message.
indicated return code. The return code is an internal
code from the server. System Action: The server completes termination
processing.
file creation request fails. User Response: None.
User Response: Specify a new file name. The return

ANR7832E (Solaris) • ANR7836S
the starting cylinder of this partition to a number
ANR7832E (Solaris) raw partition name corresponds to
greater than 0.
a protected filesystem, such as / or /usr.
Explanation: The RAW partition specified has an
ANR7834I (Windows NT) The server thread thread ID
existing file system on it. This filesystem is the / or
(tid Windows NT thread ID) terminated in
/usr partition. If the SERVER writes to it, it will most
response to external signal.
likely crash the whole operating system.
Explanation: The thread has terminated due to an
System Action: Disallow access to this raw partition.
external signal.
User Response: Have user specify another RAW
partition that is not the / or /usr. It may be possible
processing.
that this is not the actual / or /usr partition of the boot
disk. Check, using the Solaris format() command, if User Response: None.
your partition name tag is labeled incorrectly as / or
/usr.
ANR7835I The server thread thread ID terminated
in response to server shutdown.
ANR7833S The process thread ID terminated in
response to program abort. Explanation: The thread has ended due to a server
shutdown.
abort. System Action: The server completes termination
processing.
processing. User Response: None.

ANR7835E (Solaris) Specified raw partition name raw
partition is too big for this operating
ANR7833E (Solaris) symbolic links has too many system to handle.
symbolic links - the server only
supports a maximum of 10. Explanation: The raw partition specified has greater
than 2GB and the operating system is running below
Explanation: The file specified has too many symbolic Solaris 2.6. Operating system below Solaris 2.6 cannot
links. The server will follow at most 10 links before handle files natively more than 2GB. For operating
ending this symbolic link name resolution. system that is at Solaris 2.6 or above, the limit is 1TB.
System Action: Disallow access to this file System Action: Disallow access to this raw partition
User Response: Have the user specify the actual file, User Response: Have the system administrator change
where the file is not a symbolic link. Using ls -l, one the RAW partition size to be less than 2GB (4194303
can see if the file is a symbolic link. 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.
ANR7834I The thread thread ID terminated in
response to external signal.
ANR7835I (Windows NT) The server thread thread ID
(tid Windows NT thread ID) terminated in
signal.
response to server shutdown.
Explanation: The thread has terminated due to a
processing.
server shutdown.
processing.
ANR7834E (Solaris) Specified raw partition name raw
partition cannot contain the 0th disk
cylinder.
ANR7836S Server initialization terminated.
Explanation: The raw partition specified has the 0th
disk cylinder. The server should not be allowed to Explanation: An error occurs that causes server
write into the 0th cylinder. It allowed, the disk label initialization to end.
would be corrupted.
System Action: Disallow access to this raw partition
User Response: Have the system administrator change

ANR7837S • ANR7849I
ANR7837S Internal error internal error detected. ANR7843W (HP-UX) Unable to determine real
memory size.
Explanation: An internal error is detected during
server initialization or operation. Explanation: The server checks the amount of real
memory in the system to optimize use of storage in the
database buffer pool. The routines used to obtain this
User Response: Contact your service representative. information returned a failing return code or were
unable to return the real memory size.
ANR7837S (Windows NT) Internal error The internal System Action: Server operation continues. The server
error that was detected. detected. allows the data base buffer pool size to grow withoug
taking into account real memory.
Explanation: An internal error was detected during
server initialization or operation. User Response: The server may need to run as a root
user to obtain this information.
System Action: Server operation will halt.
User Response: Contact your service representative. ANR7843W (Solaris) Unable to determine real
memory size.
ANR7838S Server operation terminated. Explanation: The server checks the amount of real
Explanation: An error occurs that causes server memory in the system to optimize use of storage in the
operation to stop. database buffer pool. The routines used to obtain this
information returned a failing return code or were
System Action: Server operation stops. unable to return the real memory size.
User Response: Contact your service representative. System Action: Server operation continues. The server
allows the data base buffer pool size to grow withoug
ANR7841S Insufficient kernel memory available. taking into account real memory.
Explanation: An error occurs due to insufficient kernel User Response: The server may need to run as a root
memory. user to obtain this information.

ANR7843W (Windows NT) Unable to determine real
User Response: Contact your service representative. memory size.
Explanation: The server checks the amount of real
ANR7842S Monitor kernel extension not initialized. memory in the system to optimize use of storage in the
Explanation: The monitor kernel extension is not database buffer pool. The routines used to obtain this
initialized. information returned a failing return code or were
unable to return the real memory size.
System Action: Server operation continues. The server
User Response: Contact your service representative. allows the data base buffer pool size to grow withoug
taking into account real memory.
ANR7843W Unable to determine real memory size. User Response: The server may need to run as a root
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 ANR7849I Server operation terminated - kernel
Manager (ODM) to determine how much real memory extension has been reset.
is installed on the system. The routines used to call
ODM failed or were unable to return the real memory Explanation: The kernel extension has been
size. reinitialized by the server in response to a previous
condition for which a message has been issued.
allows the data base buffer pool size to grow withoug System Action: Server operation stops.
taking into account real memory. User Response: None.
User Response: The server may need to run as a root

ANR7850I The process process ID has terminated on ANR7856W (Windows NT) The affinity mask (0xNT
signal signal number (signal name). 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 Error resetting handler for signal signal
number (signal name).
ANR7860W Insufficient Space Available for file file
Explanation: An error occurs resetting the specified
name.
signal handler.
with the indicated name. There was insufficient space
User Response: Contact your service representative. for the file in the filesystem.
ANR7852I (Windows NT) The current process file creation request fails.
affinity mask is: 0xThe process affinity
User Response: Specify a file name in a filesystem
mask..
with sufficient space or change the space request to a
Explanation: The server is running on the processors value consistent with the filesystem.
indicated by the mask.
System Action: Server operation continues. ANR7860W (HP-UX) Insufficient Space Available for
file file name.
with the indicated name. There was insufficient space
ANR7853W (Windows NT) Could not obtain the for the file in the filesystem.
current process affinity mask. Reason:
NT return code.. System Action: The server continues processing. The
Explanation: A problem was encounterd while
obtaining the current process affinity. User Response: Specify a file name in a filesystem
System Action: Server operation continues. value consistent with the filesystem.
ANR7860W (Solaris) Insufficient Space Available for
ANR7854W (Windows NT) The process affinity file file name.
mask (0xAffinity mask.) specified in Explanation: The server was attempting to create a file
dsmserv.opt is out of range. with the indicated name. There was insufficient space
Explanation: The affinity mask value was out of for the file in the filesystem.
range. System Action: The server continues processing. The
System Action: Server operation continues. file creation request fails.
User Response: None. User Response: Specify a file name in a filesystem

value consistent with the filesystem.
ANR7855W (Windows NT) Could not set new
process affinity mask. Reason: NT return
code. ANR7861W Unable to create directory when creating
volume file name.
Explanation: A problem was encounterd in setting a
new process affinity mask. Explanation: The server was attempting to create a file
System Action: Server operation continues. created as well, but its creation failed.
User Response: None. System Action: The server continues processing. The
User Response: Specify a file name in an existing

ANR7861W (HP-UX) • ANR7864W (HP-UX)
directory or or change the name request to specify a will not use an existing file name when creating a file.
ANR7863W Unable to create file file name.
ANR7861W (HP-UX) Unable to create directory when
creating volume file name.
Explanation: The server was attempting to create a file in creating the file.
User Response: Specify a new file name.
User Response: Specify a file name in an existing
ANR7863W (HP-UX) Unable to create file file name.
directory or or change the name request to specify a
different directory name. Explanation: The server was attempting to create a file
in creating the file.
ANR7861W (Solaris) Unable to create directory when
creating volume file name. System Action: The server continues processing. The
with the indicated name. A new directory was being User Response: Specify a new file name.
System Action: The server continues processing. The ANR7863W (Solaris) Unable to create file file name.
User Response: Specify a file name in an existing with the indicated name. The system reported an error
directory or or change the name request to specify a in creating the file.
ANR7862W File Already exists when creating
volume file name. User Response: Specify a new file name.

with the indicated name. The file already exists. ANR7864W Unable to write volume file name.
System Action: The server continues processing. The Explanation: The server was attempting to create a file
file creation request fails. with the indicated name. The server was able to
partially write to the file before running out of space.
User Response: Specify a new file name. The server
will not use an existing file name when creating a file. System Action: The server continues processing. The
file creation request fails. The file is still present on the
system.
ANR7862W (HP-UX) File Already exists when
creating volume file name. User Response: Specify a new file name where there
with the indicated name. The file already exists.
ANR7864W (HP-UX) Unable to write volume file
System Action: The server continues processing. The name.
User Response: Specify a new file name. The server with the indicated name. The server was able to
will not use an existing file name when creating a file. partially write to the file before running out of space.
ANR7862W (Solaris) File Already exists when file creation request fails. The file is still present on the
creating volume file name. system.
Explanation: The server was attempting to create a file User Response: Specify a new file name where there
with the indicated name. The file already exists. is sufficient space.
User Response: Specify a new file name. The server

ANR7864W (Solaris) • ANR7871W
ANR7864W (Solaris) Unable to write volume file ANR7866W Creation of Volume file name failed.
name. Process was cancelled.
Explanation: The server was attempting to create a file Explanation: The server was attempting to create a file
with the indicated name. The server was able to with the indicated name. The attempt was cancelled by
partially write to the file before running out of space. a cancel process command.
System Action: The server continues processing. The System Action: The server continues processing. The
file creation request fails. The file is still present on the file creation request fails.
system.
User Response: Specify a new file name where there re-entered.
ANR7866W (HP-UX) Creation of Volume file name
ANR7865W Unable to create volume file name. failed. Process was cancelled.
Return code=return code.
Explanation: The server was attempting to create a file with the indicated name. The attempt was cancelled by
with the indicated name. The attempt failed with the a cancel process command.
indicated return code. The return code is an the server
internal code.
re-entered.
code may also be provided to your service
ANR7866W (Solaris) Creation of Volume file name
failed. Process was cancelled.
ANR7865W (HP-UX) Unable to create volume file
with the indicated name. The attempt was cancelled by
name. Return code=return code.
a cancel process command.
with the indicated name. The attempt failed with the
indicated return code. The return code is a server
internal code. User Response: The DEFINE command may be
re-entered.
ANR7870W Unable to initialize odm query. Error
message from odm is odm message.
representative for interpretation. 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
ANR7865W (Solaris) Unable to create volume file
real memory is installed on the system. The routine
name. Return code=return code.
used to initialize an ODM query failed. ODM returned
Explanation: The server was attempting to create a file an error message as indicated.
with the indicated name. The attempt failed with the
indicated return code. The return code is a server
makes assumptions concerning information it could not
internal code.
obtain.
ANR7871W 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

ANR8190I • ANR8192I (HP-UX)
an error message as indicated. 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
makes assumptions concerning information it could not
restart Windows NT.
obtain.
ANR8191W (HP-UX) HTTP driver unable to
initialize due to error in BINDing to
Port port, reason code reason code.
ANR8190I HTTP driver ready for connection with
Explanation: While initializing HTTP communications,
clients on port port number.
the server has failed to connect to a master TCP/IP
Explanation: The server is now able to accept sessions socket on which to listen for clients. The reason code is
with clients that use the HTTP protocol on the the return code from the TCP/IP bind API.
indicated port number.
System Action: Server operation continues. server cannot accept sessions from administrative
clients using HTTP protocol.
User Response: Ensure that no other application is
using the port number specified in the server options
ANR8190I (HP-UX) HTTP driver ready for file with the PORT option. If TCP/IP is also in use for
connection with clients on port port client sessions, ensure that the same port number is not
number. specified for both TCP/IP and HTTP communications.
Explanation: The server is now able to accept sessions This may be done by issuing the TCP/IP netstat -s
with clients that use the HTTP protocol on the command. If the server is brought down and then
indicated port number. started immediately, you may be within the TCP/IP
one minute timeout period for port reusage. Bring
System Action: Server operation continues. down the sever, wait one minute, and then restart the
User Response: None. server. If that does not work, it may be necessary to
restart HP-UX.
ANR8190I (Solaris) HTTP driver ready for

connection with clients on port port ANR8191W (Solaris) HTTP driver unable to
number. initialize due to error in BINDing to
Explanation: The server is now able to accept sessions
with clients that use the HTTP protocol on the Explanation: While initializing HTTP communications,
indicated port number. the server has failed to connect to a master TCP/IP
socket on which to listen for clients. The reason code is
System Action: Server operation continues. the return code from the TCP/IP bind API.
User Response: None. System Action: Server operation continues, but the
server cannot accept sessions from administrative
ANR8191W HTTP driver unable to initialize due to clients using HTTP protocol.
error in BINDing to Port port, reason User Response: Ensure that no other application is
code reason code. using the port number specified in the server options
Explanation: While initializing HTTP communications, file with the PORT option. If TCP/IP is also in use for
the server has failed to connect to a master TCP/IP client sessions, ensure that the same port number is not
socket on which to listen for clients. The reason code is specified for both TCP/IP and HTTP communications.
the return code from the TCP/IP bind API. This may be done by issuing the TCP/IP netstat -s
command. If the server is brought down and then
System Action: Server operation continues, but the started immediately, you may be within the TCP/IP
server cannot accept sessions from administrative one minute timeout period for port reusage. Bring
clients using HTTP protocol. down the sever, wait one minute, and then restart the
server.
file with the PORT option. If TCP/IP is also in use for ANR8192I (HP-UX) HTTPS driver ready for
client sessions, ensure that the same port number is not connection with clients on port port
specified for both TCP/IP and HTTP communications. number.
This may be done by issuing the TCP/IP netstat -s
command. If the server is brought down and then Explanation: The server is now able to accept sessions
started immediately, you may be within the TCP/IP with clients that use the HTTPS protocol on the

ANR8192I (Solaris) • ANR8200I (Solaris)
System Action: Server operation continues. started immediately, you may be within the TCP/IP
down the sever, wait one minute, and then restart the
ANR8192I (Solaris) HTTPS driver ready for restart Solaris
connection with clients on port port
number.
ANR8194W (HP-UX) HTTPS driver unable to
Explanation: The server is now able to accept sessions initialize due to error in secure data
with clients that use the HTTPS protocol on the initialization, reason code reason code.
Explanation: While initializing HTTPS
System Action: Server operation continues. communications, the server has failed initialize of the
secure data certificate information.
ANR8193W (HP-UX) HTTPS driver unable to clients using HTTPS protocol.
Port port, reason code reason code. User Response: Ensure the keyring file name and
keyring file password are correct and that the password
Explanation: While initializing HTTPS has not expired. Check for earlier SKIT messages which
communications, the server has failed to connect to a may indicate the real problem. Replace keyring if
master TCP/IP socket on which to listen for clients. necessary and re-start the server.
The reason code is the return code from the TCP/IP
bind API.
ANR8200I TCP/IP driver ready for connection with
System Action: Server operation continues, but the clients on port port number.
clients using HTTPS protocol. Explanation: The server is now able to accept sessions
with clients that use the TCP/IP protocol on the
User Response: Ensure that no other application is indicated port number.
file with the PORT option. If TCP/IP is also in use for System Action: Server operation continues.
client sessions, ensure that the same port number is not
specified for both TCP/IP and HTTPS communications.
command. If the server is brought down and then ANR8200I (HP-UX) TCP/IP driver ready for
started immediately, you may be within the TCP/IP connection with clients on port port
one minute timeout period for port reusage. Bring number.
with clients using the TCP/IP protocol on the indicated
restart HP-UX.
port number.
ANR8193W (Solaris) HTTPS driver unable to
initialize due to error in BINDing to User Response: None.
Explanation: While initializing HTTPS ANR8200I (Solaris) TCP/IP driver ready for
communications, the server has failed to connect to a connection with clients on port port
master TCP/IP socket on which to listen for clients. number.
The reason code is the return code from the TCP/IP
bind API. Explanation: The server is now able to accept sessions
with clients using the TCP/IP protocol on the indicated
System Action: Server operation continues, but the port number.
clients using HTTPS protocol. System Action: Server operation continues.
User Response: Ensure that no other application is User Response: None.

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 both TCP/IP and HTTPS communications.

ANR8200I (Windows NT) • ANR8202E (Solaris)
ANR8200I (Windows NT) TCP/IP driver ready for ANR8201W (Windows NT) Unable to initialize
connection with clients on port port TCP/IP driver - insufficient memory.
number.
Explanation: The server is unable to communicate by
Explanation: The server can now accept sessions with way of TCP/IP. A memory allocation request has been
clients using the TCP/IP protocol on the indicated port rejected by the operating system.
number.
System Action: Server operation continues. server cannot accept sessions from clients using the
TCP/IP protocol.
User Response: Ensure that there is sufficient space
for the Windows NT paging file. Click on the system
ANR8201W Unable to initialize TCP/IP driver -
icon in the Windows NT control panel and then click
on the virtual memory button. Refer to the online help
Explanation: Because the operating system rejects a for instructions on how to increase the amount of
memory allocation request, the server cannot start virtual memory.
communications through TCP/IP.
System Action: Server operation continues, but the ANR8202W Unable to initialize TCP/IP driver - error
server cannot accept sessions from clients using the creating acceptor socket. Reason code
TCP/IP protocol. reason code.
User Response: Ensure that sufficient paging space is Explanation: Because TCP/IP rejects a request for a
available for AIX. You may also use SMIT to determine socket on which to listen, the server cannot start
if the number of applications is causing a memory communications through TCP/IP.
shortage. It may be necessary to decrease the maximum
server cannot accept sessions from clients using the
TCP/IP protocol.
User Response: Ensure that TCP/IP is operational on
ANR8201E (HP-UX) Unable to initialize TCP/IP
your system by using the ping command with your
driver - socket creation failed; error error
TCP/IP address as a target. If TCP/IP is not started,
code.
use the HALT command from a server prompt to stop
Explanation: The server is unable to initialize the the server and restart it.
TCP/IP driver due to a socket creation error.
System Action: Server operation continues, but ANR8202E (HP-UX) Unable to initialize TCP/IP
TCP/IP support is inoperative. driver - socket bind operation for port
TCP port number failed; error error code.
your system by using the ping command with your Explanation: The server is unable to initialize the
TCP/IP address as a target. If TCP/IP is not active on TCP/IP driver due to a socket binding error.
your system, you must activate it; then halt and restart
the server.
TCP/IP support is inoperative.
ANR8201E (Solaris) Unable to initialize TCP/IP
driver - socket creation failed; error error
TCP/IP address as a target. If TCP/IP is not active on
code.
Explanation: The server is unable to initialize the the server. This message may also result from more
TCP/IP driver due to a socket creation error. than one server running on the same machine with the
same TCP/IP port number. Make sure that the
System Action: Server operation continues, but dsmserv.opt file TCPPort option is different for each
TCP/IP support is inoperative. server.
your system by using the ping command with your ANR8202E (Solaris) Unable to initialize TCP/IP
TCP/IP address as a target. If TCP/IP is not active on driver - socket bind operation for port
your system, you must activate it; then halt and restart TCP port number failed; error error code.
the server.
Explanation: The server is unable to initialize the
TCP/IP driver due to a socket binding error.

ANR8202W (Windows NT) • ANR8204E (HP-UX)
User Response: Ensure that TCP/IP is operational on driver - listen operation failed; error
your system by using the ping command with your error code.
TCP/IP driver due to a socket listen error.
the server. This message may also result from more
than one server running on the same machine with the System Action: Server operation continues, but
same TCP/IP port number. Make sure that the TCP/IP support is inoperative.
dsmserv.opt file TCPPort option is different for each
server.
ANR8202W (Windows NT) Unable to initialize your system, you must activate it; then halt and restart
TCP/IP driver - error creating acceptor the server.
socket.
Explanation: The server is unable to communicate by ANR8203W (Windows NT) Unable to establish TCP
way of TCP/IP. TCP/IP has rejected a request for a connection - accept error.
socket on which the server listens.
Explanation: The server cannot accept a client session
System Action: Server operation continues, but the due to failure in TCP/IP.
TCP/IP protocol.
User Response: Ensure that TCP/IP is operational on TCP/IP protocol.
issue the HALT command to stop the server, and then
restart the server.
issue the HALT command to stop the server, and then
restart the server.
ANR8203W Unable to establish TCP connection -
accept error.
Explanation: The server cannot accept a client session insufficient memory.
due to a failure in TCP/IP.
System Action: Server operation continues, but the due to a memory allocation request failure.
TCP/IP protocol.
session request for this session fails.
User Response: Ensure that sufficient paging space is
available for AIX. You may also use SMIT to determine
use the HALT command from a server prompt to
shortage. You may also decrease the maximum number
terminate the server and restart it.
of sessions that the server can accept with the
driver - listen operation failed; error
error code.
driver - thread creation failed.
TCP/IP driver due to a socket listen error.
TCP/IP driver due to an error creating a server thread.
User Response: This error often results from a lack of
memory. Ensure that your system has sufficient paging
space to support the current activities.
the server.

ANR8204E (Solaris) • ANR8206E (Solaris)
driver - thread creation failed.
TCP/IP driver due to an error creating a server thread.
System Action: Server operation continues, but your system, you must activate it; then halt and restart
TCP/IP support is inoperative. the server.
User Response: This error often results from a lack of
memory. Ensure that your system has sufficient paging ANR8205W (Windows NT) Unable to establish TCP
space to support the current activities. connection - server HALT in progress.
Explanation: The server is unable to accept a client
ANR8204W (Windows NT) Unable to establish TCP session due to server HALT processing that is in
connection - insufficient memory. progress.
Explanation: The server is unable to accept a client System Action: Server operation continues, but the
session due to a memory allocation request failure. session request for this session fails.
System Action: Server operation continues, but the User Response: None.
User Response: Ensure that there is sufficient space ANR8206W Socket socket (session session number)
for the Windows NT paging file. Click on the system closed abruptly.
Explanation: The server detects that the indicated
session on the specified TCP/IP socket is closed outside
for instructions on how to increase the amount of
of the server.
virtual memory. You may also wish to cut down on the
maximum number of sessions that the server can System Action: Server operation continues, but the
accept with the MAXSESSIONS option in the server session is ended.
options file.

server HALT in progress. ANR8206E (HP-UX) Unable to establish TCP/IP
session - invalid host address IP host
Explanation: The server cannot accept a client session address (port port number).
due to server HALT processing that is in progress.
Explanation: The server is unable to establish a
System Action: Server operation continues, but the session because the designated address or port number
session request for this session fails. is not valid.
User Response: None. System Action: Server operation continues.
User Response: Ensure that the specified host name is
ANR8205E (HP-UX) Terminating TCP/IP driver - valid and is accessible over the network. If the
accept operation failed; error error code. TCPCLIENTPort option is specified for the remote
system, ensure it does not conflict with another
application.
TCP/IP driver due to a socket accept error.
ANR8206E (Solaris) Unable to establish TCP/IP
session - invalid host address IP host
User Response: Ensure that TCP/IP is operational on address (port port number).
session because the designated address or port number
is not valid.
the server.
ANR8205E (Solaris) Terminating TCP/IP driver - User Response: Ensure that the specified host name is
socket accept operation failed; error error valid and is accessible over the network. If the
code. TCPCLIENTPort option is specified for the remote
system, ensure it does not conflict with another
application.
TCP/IP driver due to a socket accept error.

ANR8207W • ANR8208W (Windows NT)
ANR8207W TCP/IP driver unable to initialize due to ANR8208W TCP/IP driver unable to initialize due to
socket initialization error. error in BINDing to Port port, reason
code reason code.
Explanation: While initializing TCP/IP
communications, the server fails to set up an interface Explanation: While initializing TCP/IP
with TCP/IP. communications, the server fails to connect to a master
the return code from the TCP/IP bind API.
TCP/IP protocol. System Action: Server operation continues, but the
User Response: Ensure that TCP/IP has been started
TCP/IP protocol.
and is active on your system. You may issue the
TCP/IP ping command to your own address to verify User Response: Ensure that no other application is
that TCP/IP is both started and active. using the port number specified in the server options
file with the PORT option by issuing the TCP/IP
netstat command. If HTTP is also in use for client
ANR8207E (HP-UX) Unable to establish TCP/IP
sessions, ensure that the same port number is not
session with IP host address due to
specified for both TCP/IP and HTTP communications.
memory shortage.
If the server was brought down and client sessions
Explanation: The server is unable to establish a were active, it may be necessary to terminate the client
session because of a memory shortage condition. sessions on the client systems before the port can be
freed.
User Response: Ensure that your system has sufficient ANR8208E (HP-UX) Unable to establish TCP/IP
paging space to support the current level of system session with IP host address - socket
activities. creation failed; error error code.
ANR8207E (Solaris) Unable to establish TCP/IP session because of a socket creation error.
session with IP host address due to
memory shortage. System Action: Server operation continues.
Explanation: The server is unable to establish a User Response: Ensure that TCP/IP is operational on
session because of a memory shortage condition. your system by using the ping command with your
System Action: Server operation continues. your system, you must activate it; then halt and restart
User Response: Ensure that your system has sufficient the server.
paging space to support the current level of system
activities. ANR8208E (Solaris) Unable to establish TCP/IP
session with IP host address - socket
ANR8207W (Windows NT) TCP/IP driver unable to creation failed; error error code.
initialize due to socket initialization Explanation: The server is unable to establish a
error. session because of a socket creation error.
Explanation: While initializing TCP/IP System Action: Server operation continues.
communications, the server has failed to set up an
interface with TCP/IP for Windows NT. User Response: Ensure that TCP/IP is operational on
System Action: Server operation continues, but the TCP/IP address as a target. If TCP/IP is not active on
server cannot accept sessions from clients using the your system, you must activate it; then halt and restart
TCP/IP protocol. the server.
User Response: Ensure that TCP/IP is properly
installed on your system. Ensure that TCP/IP has been ANR8208W (Windows NT) TCP/IP driver unable to
started on your system. Issue the TCP/IP ping initialize due to error in BINDing to
command to your own address to verify that TCP/IP is Port port, reason code reason code.
both installed and active.
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.

ANR8209W • ANR8210E (HP-UX)
server cannot accept sessions from clients using the correct TCPServeraddress and TCPPort of the server
TCP/IP protocol. you are attempting to contact.
using the port number specified in the server options ANR8209W (Windows NT) TCP/IP driver unable to
file with the PORT option. If HTTP is also in use for initialize due to error in LISTENing on
client sessions, ensure that the same port number is not the specified Port, reason code reason
specified for both TCP/IP and HTTP communications. code.
Explanation: While attempting to listen for session
requests from clients using TCP/IP, TCP/IP returns an
started immediately, you may be within the TCP/IP
error. The reason code is the return code from the
TCP/IP listen API.
down the server, wait one minute, and then restart the
server. If that does not work, it may be necessary to System Action: Server operation continues, but the
restart Windows NT. server cannot accept additional sessions from clients
using the TCP/IP protocol.
ANR8209W TCP/IP driver unable to initialize due to User Response: Ensure that TCP/IP is running
error in LISTENing on the specified properly. This may be done by issuing the TCP/IP
Port, reason code reason code. netstat -s and ping commands to other nodes on your
network. It may be possible to correct this condition by
restarting the server.
TCP/IP listen API. ANR8210W TCP/IP driver is terminating due to
error in accepting a new session, reason
code reason code.
server cannot accept additional sessions from clients
using the TCP/IP protocol. Explanation: While attempting to accept a session
request from a client using TCP/IP, TCP/IP returns an
User Response: Ensure that TCP/IP is running
properly by issuing the TCP/IP netstat -s and ping
TCP/IP accept API.
commands to other nodes on your network. It may be
possible to bring the server down and restart it to System Action: Server operation continues, but the
allow additional client sessions to start. server cannot accept additional sessions from clients
using the TCP/IP protocol.
ANR8209E (HP-UX) Unable to establish TCP/IP User Response: Ensure that TCP/IP is running
session with IP host address - connection properly. This may be done by issuing the TCP/IP
refused. netstat -s and ping commands to other nodes on your
network. It may be possible to bring the server down
and restart it to allow additional client sessions to start.
session because the remote system refused the
connection request.
session with IP host address - connection
User Response: Ensure that the specified remote request timed out.
system is operational and is properly configured to run
TCP/IP. Ensure that the client options file specifies the
session because the remote system did not respond to
correct TCPServeraddress and TCPPort of the server
the connection request.
you are attempting to contact.
ANR8209E (Solaris) Unable to establish TCP/IP User Response: Ensure the following:
session with IP host address - connection v The specified remote system is operational and is
refused. properly configured to run TCP/IP.
Explanation: The server is unable to establish a v The client options file specifies the correct
session because the remote system refused the TCPServeraddress and TCPPort of the server you are
connection request. attempting to contact.
System Action: Server operation continues. v Necessary gateways and routers are functioning
properly.
User Response: Ensure that the specified remote

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

User Response: Ensure that the specified remote System Action: The session with the remote system is
system is operational and is properly configured to run ended.
TCP/IP.
ANR8212E (Solaris) Unable to establish TCP/IP TCP/IP.
session with IP host address - connect
failed; error error code.
ANR8213W (Windows NT) Session open with node
Explanation: The server is unable to establish a name timed out.
session because of a connection error.
Explanation: The server attempts to contact the
System Action: Server operation continues. indicated node name. The attempt is unsuccessful.
User Response: Ensure that the specified remote System Action: The attempt to communicate with the
system is operational and is properly configured to run indicated node fails.
TCP/IP.
User Response: Ensure that the node name is properly
specified and that it is accessible over the network. Use
ANR8212W (Windows NT) Unable to resolve the TCP/IP ping command for this purpose.
address for node name.
Explanation: The server attempts to obtain a TCP/IP ANR8214E Session open with IP host address failed
address for the indicated node name. The attempt is due to connection refusal.
unsuccessful.
System Action: The attempt to communicate with the session because the remote system refused the
indicated node fails. Server operation continues. connection request.
User Response: Ensure that the node name is properly System Action: Server operation continues.
the TCP/IP ping command for this purpose.
ANR8213W Session open with node name timed out. correct TCPServeraddress and TCPPort of the server
indicated node name. The attempt is unsuccessful.
ANR8214E (HP-UX) Session Session identifier aborted
System Action: The attempt to communicate with the
due to zero-length message.
indicated node fails.
Explanation: The session between the server and the
specified client system experienced a disruptive error
receiving data.
System Action: The session with the remote system is
ended.
due to send error; error error code. User Response: Ensure that the specified remote
TCP/IP.
specified client system experienced a disruptive error
sending data.
ANR8214E (Solaris) Session Session identifier aborted
due to zero-length message.
ended.
specified client system experienced a fatal error
receiving data.
TCP/IP.
ended.
ANR8213E (Solaris) Session Session identifier aborted
due to send error; error error code. User Response: Ensure that the specified remote
TCP/IP.
specified client system experienced a fatal error sending
data.

ANR8214E (Windows NT) • ANR8216W (Windows NT)
properly specified and that it is accessible over the
ANR8214E (Windows NT) Session open with IP host
network. Use the TCP/IP ping command for this
address failed due to connection refusal.
purpose.
session because the remote system refused the
ANR8216W Error sending data on socket socket
connection request.
number. Reason return code.
Explanation: The server experiences an error return
User Response: Ensure that the specified remote code from TCP/IP while sending data over the
system is operational and is properly configured to run indicated socket. This may be a normal event if either
TCP/IP. Ensure that the client options file specifies the side of the connection is abruptly ended.
correct TCPServeraddress and TCPPort of the server
continues.
User Response: If the session is ended as a result of
ANR8215W Session open with IP host address failed
intentionally stopping either the client or server, no
as unreachable.
response is required. Otherwise, ensure that the client
Explanation: The server is unable to establish a and server can communicate through such means as
session because the remote system is unreachable. Telnet or FTP applications, which are part of the
TCP/IP suite.
User Response: Ensure that the IP host address is
properly specified and that it is accessible over the
session with IP host address due to thread
network. Use the TCP/IP ping command for this
creation error.
purpose.
session because of an error creating a thread.
due to receive error; error error code. System Action: Server operation continues.
Explanation: The session between the server and the User Response: Ensure that your system has sufficient
specified client system experienced a disruptive error paging space to support the current level of system
receiving data. activities.
ended. ANR8216E (Solaris) Unable to establish TCP/IP
session with IP host address due to thread
creation error.
TCP/IP. Explanation: The server is unable to establish a
session because of an error creating a thread.
ANR8215E (Solaris) Session Session identifier aborted System Action: Server operation continues.
due to receive error; error error code.
User Response: Ensure that your system has sufficient
Explanation: The session between the server and the paging space to support the current level of system
specified client system experienced a fatal error activities.
receiving data.
System Action: The session with the remote system is ANR8216W (Windows NT) Error sending data on
ended. socket socket number. Reason return code.
User Response: Ensure that the specified remote Explanation: The server experiences an error return
system is operational and is properly configured to run code from TCP/IP while sending data over the
TCP/IP. indicated socket. This may be a normal event if either
side of the connection is abruptly ended.
ANR8215W (Windows NT) Session open with IP host System Action: The session is ended. Server operation
address failed as unreachable. continues.
Explanation: The server is unable to establish a User Response: If the session is ended as a result of
session because the remote system is unreachable. intentionally stopping either the client or server, no
and server can communicate through such means as
User Response: Ensure that the IP host address is

ANR8217W • ANR8218W (Solaris)
Telnet or FTP applications, which are part of the indicated socket. This may be a normal event if either
TCP/IP suite. side of the connection is abruptly ended.
ANR8217W Error receiving data on socket socket continues.
number. Reason return code.
Explanation: The server experiences an error return intentionally stopping either the client or server, no
code from TCP/IP while receiving data on the response is required. Otherwise, ensure that the client
indicated socket. This may be a normal event if either and server can communicate through such means as
side of the connection is abruptly ended. Telnet or FTP applications, which are part of the
TCP/IP suite.
continues.
ANR8218W Session terminated when no data was
read on socket socket number.
response is required. Otherwise, ensure that the client Explanation: The server is unable to read data on the
and server can communicate through such means as indicated socket. This may be a normal event if either
Telnet or FTP applications, which are part of the side of the connection is abruptly ended.
TCP/IP suite.
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 Telnet or FTP applications, which are part of the
for the indicated client to the requested size shown. TCP/IP suite.
The server uses the default window size for the
indicated session. There may be a lack of memory for
ANR8218W (HP-UX) TCP/IP driver is unable to use
TCP/IP buffers.
the TCP/IP NODELAY option for client
System Action: Server operation continues and the client.
session continues with the default window size.
Explanation: The server cannot set TCP/IP NODELAY
User Response: Retry the session with a smaller for the indicated client. The session proceeds with
window size in the options file. Issue the QUERY TCP/IP Delay processing in effect. This causes TCP/IP
OPTION command to determine the setting of the to buffer data prior to sending it to clients.
server TCPWindowsize.
System Action: Server operation continues and the
session continues with the delay processing on.
ANR8217W (Solaris) Unable to initialize TCP/IP
User Response: Further details for use in contacting
driver - insufficient memory.
your service representative can be obtained by issuing
Explanation: Because the operating system rejects a the following trace commands from an admin session
memory allocation request, the server cannot start or from the server console (proper administrative
communications through TCP/IP. authority is required): TRACE ENABLE TCPINFO
TRACE BEGIN tcptrace.out. After a session starts and
gets message ANR8218W, issue the following
commands: TRACE FLUSH TRACE END. This will
TCP/IP protocol.
create trace data in file tcptrace.out and will terminate
User Response: Ensure that sufficient paging space is the trace. This file should be supplied to your server
available for Solaris. You may also use ps -ef to representative on request.
determine if the number of applications is causing a
memory shortage. It may be necessary to decrease the
ANR8218W (Solaris) Unable to resolve address for
node name.
Explanation: The server attempts to obtain a TCP/IP
address for the indicated node name. The attempt is
ANR8217W (Windows NT) Error receiving data on
unsuccessful.
socket socket number. Reason return code.
indicated node fails. Server operation continues.
code from TCP/IP while receiving data on the

ANR8218W (Windows NT) • ANR8220W (HP-UX)
ANR8219W (Solaris) Unable to establish TCP
connection - insufficient memory.
due to a memory allocation request failure.
ANR8218W (Windows NT) Session terminated when
no data read on socket socket number. System Action: Server operation continues, but the
Explanation: The server cannot read on the indicated
socket. This may be a normal event if either side of the User Response: Ensure that sufficient paging space is
connection is abruptly ended. 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
continues.
server can accept with the MAXSESSIONS option in
User Response: If the session is ended as a result of the server options file.
ANR8219W (Windows NT) TCP/IP driver is unable
to accept a new session due to error in
Telnet or FTP applications, which are part of the
creating a new thread.
TCP/IP suite.
due to the inability to create a new thread.
ANR8219W TCP/IP driver is unable to accept a new
session with client at address TCP/IP System Action: Server operation continues, the session
address due to an error in creating a new request fails.
thread.
User Response: The most likely cause is a lack of
Explanation: The server cannot accept a client session memory. Ensure that there is sufficient space for the
with the client at the indicated address due to an Windows NT paging file. Click on the system icon in
inability to create a new thread. the Windows NT control panel and then click on the
virtual memory button. Refer to the online help for
System Action: Server operation continues, the session
instructions on how to increase the amount of virtual
request fails.
memory. You may also wish to to cut down on the
User Response: The most likely cause is lack of maximum number of sessions that the server can
memory. Ensure that sufficient paging space is available accept with the MAXSESSIONS option in the server
for AIX. You may also use SMIT to determine if the options file.
You may also decrease the maximum number of
ANR8220W TCP/IP driver is unable to set the
sessions that the server can accept with the
window size to TCPWindowsize for client
client. The default value will be used.
Explanation: The server cannot set the window size
ANR8219W (HP-UX) Unable to initialize TCP/IP
for the indicated client to the requested size shown.
The server uses the default window size for the
Explanation: Because the operating system rejects a indicated session. There may be a lack of memory for
memory allocation request, the server cannot start TCP/IP buffers.
communications through TCP/IP.
System Action: Server operation continues, but the session continues with the default window size.
User Response: Retry the session with a smaller
TCP/IP protocol.
window size in the options file. Issue the QUERY
User Response: Ensure that sufficient paging space is OPTION command to determine the setting of the
available for HP-UX. You may also use SMIT to server TCPWindowsize.
memory shortage. It may be necessary to decrease the
ANR8220W (HP-UX) Unable to establish TCP
connection - insufficient memory.

User Response: Ensure that sufficient paging space is should be supplied to your service representative on
available for HP-UX. You may also use SMIT to request.
memory shortage. You may also decrease the maximum
ANR8221W (Solaris) TCP/IP driver is unable to use
number of sessions that the server can accept with the
the TCP/IP NODELAY option for client
client.
ANR8220W (Solaris) TCP/IP driver is unable to set
for the indicated client. The session proceeds with
TCP/IP Delay processing in effect. This causes TCP/IP
client client. The default value will be
to buffer data prior to sending it to clients.
used.
for the indicated client to the requested size shown.
The server uses the default window size for the User Response: Further details for use in contacting
indicated session. There may be a lack of memory for your service representative can be obtained by issuing
TCP/IP buffers. the following trace commands from an admin session
or from the server console (proper administrative
authority is required): TRACE ENABLE TCPINFO
TRACE BEGIN tcptrace.out After a session starts and
User Response: Retry the session with a smaller gets message ANR8221W, issue the following
window size in the options file. Issue the QUERY commands: TRACE FLUSH TRACE END This will
OPTION command to determine the setting of the create trace data in file tcptrace.out and will terminate
server TCPWindowsize. the trace. This file should be supplied to your service
representative on request.
to contact node name due to an output ANR8221W (Windows NT) TCP/IP driver is unable
socket initialization error. to set the window size to TCPWindowsize
for session session, client client. The
default value will be used.
indicated node name. The attempt is unsuccessful due
to the inability to initialize a local socket. Explanation: The server cannot set the window size
for the indicated session/client to the requested size
shown. The server will use the default window size for
the indicated session.
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. User Response: The most likely cause is lack of
memory for TCP/IP buffers. You may retry with a
smaller TCP window size in the options file. You can
ANR8221W TCP/IP driver is unable to use the
issue the QUERY OPTION command to display the
TCP/IP NODELAY option for client
current setting of the TCP window size.
client.
ANR8222W TCP/IP driver is unable to set the
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
User Response: Further details for use in contacting requested size shown. The server uses the default
your service representative can be obtained by issuing window size for listening for sessions. There may be a
the following trace commands from an admin session lack of memory for TCP/IP buffers.
System Action: Server operation continues with the
default window size.
TRACE BEGIN. After a session starts and gets message
ANR8221W, issue the commands TRACE FLUSH User Response: Restart the server with a smaller
TRACE END. This will create trace data in file window size in the options file if necessary. Issue the
tcptrace.out and will terminate the trace. This file QUERY OPTION command to determine the setting of
the server TCPWindowsize.

ANR8222W (Solaris) • ANR8225I (Windows NT)
User Response: The most likely cause is lack of
ANR8222W (Solaris) Unable to establish TCP
memory. Ensure that sufficient paging space is available
connection - server HALT in progress.
for Solaris. You may also use ps -ef to determine if the
Explanation: The server cannot accept a client session number of applications is causing a memory shortage.
due to server HALT processing that is in progress. You may also decrease the maximum number of
sessions that the server can accept with the
ANR8223W (Windows NT) Failed to connect to
system at address address port port.
Explanation: The server attempted to contact the
to use the TCP/IP NODELAY option for
indicated node name at the specified port. The attempt
client client.
is unsuccessful. The target port is not valid at the target
Explanation: The server cannot set TCP/IP NODELAY 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
User Response: Further details for use in contacting with the SNMP subagent, ensure that the hostname and
your service representative can be obtained by issuing port number for the subagent is correct in the server
the following trace commands from an admin session options file.
ANR8224W (Solaris) TCP/IP driver is unable to set
TRACE BEGIN tcptrace.out After a session starts and
gets message ANR8222W, issue the following
the server master socket. The default
commands: TRACE FLUSH TRACE END This will
value will be used.
create trace data in file tcptrace.out and will terminate
the trace. This file should be supplied to your service Explanation: The server cannot set the window size
representative on request. for the socket on which the server listens to the
requested size shown. The server uses the default
window size for listening for sessions. There may be a
ANR8223W Unable to connect to remote system
lack of memory for TCP/IP buffers.
RemoteSystem due to unexpected return
code ReturnCode System Action: Server operation continues with the
default window size.
Explanation: The server was unable to connect to a
remote system due to an unexpected return code from User Response: Restart the server with a smaller
the connect Application Programming Interface. window size in the options file if necessary. Issue the
Common return code are handled with specific QUERY OPTION command to determine the setting of
messages. This return code was unexpected. the server TCPWindowsize.
System Action: Server operation continues but the
connection to the remote system fails. ANR8225I (Windows NT) NETBIOS driver ready for
connection with clients on adapter
User Response: TCP/IP return code are listed in file
network adapter number.
/usr/include/sys/errno.h and may provide a pointer
to the underlying problem. /usr/include/sys/errno.h Explanation: The server is now able to accept sessions
is part of fileset bos.adt.include. with clients using the NETBIOS protocol on the
indicated network adapter.
ANR8223W (Solaris) TCP/IP driver is unable to System Action: Server operation continues.
accept a new session with client at
address TCP/IP address due to an error in
with the client at the indicated address due to an
inability to create a new thread.
request fails.

ANR8226W (Windows NT) • ANR8232W (Windows NT)
not be accepted on this adapter. Other adapters are not
ANR8226W (Windows NT) Unable to initialize
affected.
NETBIOS driver on adapter network
adapter number. User Response: The most likely cause for this message
is the presence of another system on the network that
Explanation: The server cannot obtain sufficient
is using the same name for NETBIOS communications.
NETBIOS resources to initialize communications on the
This may be another server or client or a LAN
indicated network adapter.
Requester node. Changing or adding the
System Action: Server operation continues, but the NETBIOSNAME option for this adapter in your server
server will not accept sessions from clients that use the options file and restarting the server may allow this
NETBIOS protocol. adapter to be used with NETBIOS communications.
User Response: Ensure that NETBIOS is configured
on the system. Ensure that all NETBIOS resources are ANR8230W (Windows NT) Insufficient memory to
not already in use. If the LAN Server or LAN start NETBIOS session on adapter
Requester application is running, you have NETBIOS network adapter number.
configured. In that case, starting the server prior to
starting LAN Server or LAN Requester may allow the
due to a memory allocation request failure on the
server to obtain the necessary NETBIOS resources.
specified adapter.
ANR8227W (Windows NT) NETBIOS connection
session request fails.
terminated - insufficient memory,
network adapter network adapter number. User Response: The most likely cause is a lack of
memory. Ensure that there is sufficient space for the
Explanation: The server cannot listen for client
Windows NT paging file. Click on the system icon in
sessions on the specified network adapter due to a
the Windows NT control panel and then click on the
memory allocation request failure.
System Action: Server operation continues, but the instructions on how to increase the amount of virtual
sessions will not be accepted on the specified adapter. memory. You may also wish to cut down on the
Other network adapters remain unaffected. maximum number of sessions that the server can
accept with the MAXSESSIONS or the
NETBIOSSESSIONS option, or both, in the server
options file.
virtual memory button. Refer to the online help for ANR8231W (Windows NT) Unable to create thread
instructions on how to increase the amount of virtual to accept NETBIOS sessions.
memory.
inability to create a new thread of execution.
ANR8228W (Windows NT) NETBIOS connection
terminated - server HALT in progress.
NETBIOS communications is inoperative.
due to server HALT processing that is in progress.
System Action: Server operation continues, but the Windows NT paging file. Click on the system icon in
session request for this session fails. the Windows NT control panel and then click on the
ANR8229W (Windows NT) Unable to add server maximum number of sessions that the server can
name server name to adapter network accept with the MAXSESSIONS or the
adapter number. NETBIOSSESSIONS option, or both, in the server
options file.
Explanation: The server cannot initialize
communications processing using the NETBIOS
protocol on the indicated network adapter because the ANR8232W (Windows NT) Unable to create thread
server name cannot be added as a NETBIOS name on to listen for NETBIOS sessions on
the adapter. adapter network adapter number.
System Action: Server operation continues, but client Explanation: The server cannot initialize due to the
sessions from clients using the NETBIOS protocol will inability to create a new thread of execution to monitor
the indicated network adapter.

ANR8233W (Windows NT) • ANR8240I (Windows NT)
System Action: Server operation continues, but may allow the server to obtain the requested NETBIOS
NETBIOS communications is inoperative on the resources.
indicated adapter. Other adapters remain unaffected.
User Response: The most likely cause is a lack of ANR8236W (Windows NT) Failure while listening
memory. Ensure that there is sufficient space for the for NETBIOS sessions on adapter
Windows NT paging file. Click on the system icon in network adapter number, NETBIOS listen
the Windows NT control panel and then click on the 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.
NETBIOSSESSIONS option, or both, in the server System Action: Server operation continues. If the
options file. 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
ANR8233W (Windows NT) Unable to create thread
indicated adapter until the problem is corrected and the
to handle NETBIOS session session
server is restarted.
number on adapter network adapter
number. User Response: A NETBIOS listen failure is an
indication of a network problem, an adapter problem,
Explanation: The server cannot start a new client
or a NETBIOS configuration problem. The following
session on the indicated adapter due to an inability to
system configuration and system environment listen
start a separate thread of execution for the indicated
return codes (in hex) and resolution actions for a listen
session.
failure are found in the IBM Local Area Network
System Action: Server operation continues, but this Technical Reference:
Return Code Description
User Response: The most likely cause is a lack of 11 The local session table is full. The
memory. Ensure that there is sufficient space for the maximum number of sessions are in
Windows NT paging file. Click on the system icon in use. Change NETBIOS configuration to
the Windows NT control panel and then click on the increase the maximum number of
virtual memory button. Refer to the online help for 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.
NETBIOSSESSIONS option, or both, in the server
The maximum number of sessions are in
options file.
use. Change NETBIOS configuration to
increase the maximum number of
ANR8235W (Windows NT) Requested number of sessions.
NETBIOS sessions are not available on 35 The operating system resources are
adapter network adapter number, exhausted. A reboot is probably
proceeding with available sessions. required.
Explanation: The server cannot acquire the requested
number of NETBIOS sessions for the indicated adapter.
The server attempts to acquire the number of NETBIOS ANR8240I (Windows NT) IPX/SPX driver ready for
sessions as indicated by the NETBIOSSESSIONS connection with clients on port port
parameter of the server options file or, if this option is number.
not specified, by the MAXSESSIONS option.
Explanation: The server can now accept sessions with
System Action: Server operation continues, but the clients using the IPX/SPX protocol on the indicated
maximum number of NETBIOS sessions is limited to port number.
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 User Response: None.
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

IPX/SPX protocol.
IPX/SPX driver - insufficient memory.
User Response: Ensure that IPX/SPX is properly
installed on your system. Ensure that IPX/SPX has
way of IPX/SPX. A memory allocation request has been
been started on your system. Verify that IPX/SPX is
rejected by the operating system.
both installed and active on your system by using the
System Action: Server operation continues, but the network control panel applet.
IPX/SPX protocol.
ANR8245W (Windows NT) IPX/SPX driver unable to
User Response: Ensure that there is sufficient space initialize due to error in BINDing to
for the Windows NT paging file. Click on the system Port port, reason code reason code.
Explanation: While initializing IPX/SPX
virtual memory.
code is the return code from the IPX/SPX bind API.
IPX/SPX driver - error creating acceptor
IPX/SPX protocol.
socket.
way of IPX/SPX. IPX/SPX has rejected a request for a
file with the PORT option.
socket on which the server listens.
initialize due to error in LISTENing on
IPX/SPX protocol.
the specified Port, reason code reason
User Response: Ensure that IPX/SPX is operational on code.
your system by using the network control panel applet.
If IPX/SPX is not started, issue the HALT command to
requests from clients using IPX/SPX, IPX/SPX returns
stop the server, and then restart the server.
an error. The reason code is the return code from the
IPX/SPX listen API.
ANR8243W (Windows NT) Unable to establish
IPX/SPX connection - insufficient
memory.
using the IPX/SPX protocol.
Explanation: The server is unable to accept a client
User Response: Ensure that IPX/SPX is running
session due to a memory allocation request failure.
properly. This may be done using the network control
System Action: Server operation continues, but the panel applet.
User Response: Ensure that there is sufficient space ANR8247W (Windows NT) IPX/SPX driver is
for the Windows NT paging file. Click on the system terminating due to error in accepting a
icon in the Windows NT control panel and then click new session, reason code reason code.
Explanation: While attempting to accept a session
request from a client using IPX/SPX, IPX/SPX returns
virtual memory. You may also wish to cut down on the
an error. The reason code is the return code from the
IPX/SPX accept API.
accept with the MAXSESSIONS option in the server
options file. System Action: Server operation continues, but the
initialize due to socket initialization User Response: Ensure that IPX/SPX is running
error. properly. This may be done using the network control
panel applet.
Explanation: While initializing IPX/SPX
communications, the server has failed to set up an
interface with IPX/SPX for Windows NT.

ANR8248W (Windows NT) IPX/SPX driver is ANR8252W (Windows NT) Session open with node
terminating due to error in creating a name failed as unreachable.
new thread.
Explanation: The server cannot initialize due its indicated node name. The attempt is unsuccessful.
System Action: Server operation continues, but indicated node fails. Server operation continues.
IPX/SPX communications is inoperative.
User Response: The most likely cause is a lack of specified and that it is accessible over the network.
ANR8253W (Windows NT) Error sending data on
socket socket number. Reason return code.
instructions on how to increase the amount of virtual Explanation: The server experiences an error return
memory. You may also wish to cut down on the code from IPX/SPX while sending data over the
maximum number of sessions that the server can indicated socket. This may be a normal event if either
accept with the MAXSESSIONS option in the server side of the connection is abruptly ended.
options file.
continues.
ANR8249W (Windows NT) Unable to resolve
address for node name. User Response: If the session is ended as a result of
Explanation: The server attempts to obtain a IPX/SPX response is required.
address for the indicated node name. The attempt is
unsuccessful.
ANR8254W (Windows NT) Error receiving data on
System Action: The attempt to communicate with the socket socket number. Reason return code.
User Response: Ensure that the node name is properly code from IPX/SPX while receiving data on the
specified and that it is accessible over the network. indicated socket. This may be a normal event if either
ANR8250W (Windows NT) Session open with node System Action: The session is ended. Server operation
name timed out. continues.
Explanation: The server attempts to contact the User Response: If the session is ended as a result of
indicated node name. The attempt is unsuccessful. intentionally stopping either the client or server, no
response is required.
ANR8255W (Windows NT) Session terminated when
no data read on socket socket number.
specified and that it is accessible over the network.
Explanation: The server cannot read on the indicated
socket. This may be a normal event if either side of the
ANR8251W (Windows NT) Session open with node
connection is abruptly ended.
name failed due to connection refusal.
continues.
indicated node name. The attempt is unsuccessful due
to a refusal by the target node. User Response: If the session is ended as a result of
User Response: Ensure that the node name still has
ANR8256W (Windows NT) IPX/SPX driver is unable
IPX/SPX running and that the client is active in
to accept a new session due to error in
SCHEDULE mode.
due to the inability to create a new thread.
request fails.

User Response: The most likely cause is a lack of Named Pipes communications is inoperative.
options file.
options file.
ANR8257W (Windows NT) IPX/SPX driver is unable
to contact node name due to an output
socket initialization error.
Named Pipes, session session
Explanation: The server attempts to contact the number.WriteFile Return code is return
indicated node name. The attempt is unsuccessful due code.
to the inability to initialize a local socket.
System Action: The attempt to communicate with the code from the WriteFile Windows NT API while
indicated node fails. writing data to Named Pipes over the indicated
session. This may be a normal event if either side of the
User Response: Ensure that IPX/SPX is operating
connection is abruptly ended.
properly on this node and that it can communicate
remotely. System Action: The session is ended. Server operation
continues.
ANR8260I (Windows NT) Named Pipes driver ready User Response: If the session is ended as a result of
for connection with clients. intentionally stopping either the client or server, no
with clients using the Named Pipes protocol.
ANR8264W (Windows NT) Error reading data on
Named Pipes, session session number.
User Response: None. ReadFile return code is return code.
ANR8261W (Windows NT) Named Pipes connection code from the ReadFile Windows NT API while
terminated - insufficient memory. reading data from Named Pipes in the indicated
session. This may be a normal event if either side of the
Explanation: The server cannot accept a client session connection is ended abruptly.
System Action: Server operation continues. Named continues.
Pipes communications is inoperative.
User Response: The most likely cause is a lack of intentionally stopping either the client or server, no
memory. Ensure that there is sufficient space for the response is required.
virtual memory button. Refer to the online help for ANR8265W (Windows NT) Error open Named Pipes
instructions on how to increase the amount of virtual Named Pipes name, CreateNamedPipe
memory. You may also wish to cut down on the return code return code.
code when trying to open the indicated Named Pipes
options file.
name for Named Pipes communication with a client.
The return code shown is returned by the Windows NT
ANR8262W (Windows NT) Named Pipes driver is CreateNamedPipe API.
terminating due to error in creating a
new thread.
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
System Action: Server operation continues, but Pipes communications. It is not normal to run out of

file handles. A system or logic error may be the
ANR8269W (Windows NT) Error opening Named
underlying cause.
Pipe Named Pipes name, reason: System
message.
ANR8266W (Windows NT) Error accepting
connection on Named Pipes Named Pipes
code when trying to open the indicated Named Pipe
name, ConnectNamedPipe return code
name for Named Pipes communication with a client.
return code.
The reason shown is returned by the Windows NT
Explanation: The server experiences an error return FormatMessage API.
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 NT ConnectNamedPipe API. User Response: Consider the reason text and take
appropriate action. Stop and restart the server to
reenable Named Pipes communications.
User Response: A system problem may be preventing
ANR8273I (Windows NT) Shared memory driver
use of Named Pipes. Stop and restart the server to
ready for connection with clients.
reenable Named Pipes communications.
with clients using the shared memory protocol.
ANR8267W (Windows NT) Error initializing a
security descriptor for Named Pipes System Action: Server operation continues.
Named Pipes name, reason: System message.
code when trying to initialize the indicated Named
ANR8274W (Windows NT) Shared memory
Pipe for Named Pipes communication with a client.
communications driver is terminating
The reason shown is returned by the Windows NT
due to error in creating a new thread.
FormatMessage API.
System Action: Server operation continues, but shared
User Response: Administrator Privileges are required.
memory communications is inoperative.
Login using an account wit h Administrator privileges
and restart the server to reenable Named Pipes User Response: The most likely cause is a lack of
communications. memory. Ensure that there is sufficient space for the
ANR8268W (Windows NT) Named Pipe
communications were not enabled due
to an error looking up the following NT
memory.
group name: NT group name. Use the NT
User manager to add the specified
group. Members of the group will then ANR8275W (Windows NT) Shared memory
use NT unified logon to access the connection terminated - insufficient
server over Named pipes. memory.
Explanation: The server experiences an error return Explanation: The server cannot accept a client session
code when trying to initialize the indicated Named due to a memory allocation request failure.
Pipe for Named Pipes communication with a client.
The system could not find the NT Account name System Action: Server operation continues. Shared
specified in the server options file. memory communications is inoperative.
System Action: The session is ended. Server operation User Response: The most likely cause is a lack of
continues. Named Pipes communications is inoperative. memory. Ensure that there is sufficient space for the
User Response: To use NT unified logon specify the the Windows NT control panel and then click on the
name of a valid Windows NT account or group name. virtual memory button. Refer to the online help for
Restart the server to reenable Named Pipes instructions on how to increase the amount of virtual
communications. memory. You may also wish to cut down on the

ANR8276W (Windows NT) • ANR8283W (Solaris)
accept with the MAXSESSIONS option in the server User Response: None.
options file.
ANR8282I (Solaris) SNMP driver ready for
ANR8276W (Windows NT) Shared memory connection with subagent on port port
connection terminated - unable to number.
initialize. Key channel key, Reason: reason
code.
SNMP subagents on the indicated port number.
due being unable to initialize shared memory.
System Action: Server operation continues. Shared
memory communications are inoperative.
ANR8282I (Windows NT) HTTPS driver ready for
User Response: Try a different shared memory
session.
number.
ANR8280I (Windows NT) HTTP driver ready for
clients using the HTTPS protocol on the indicated port
number.
number.
clients using the HTTP protocol on the indicated port User Response: None.
number.
System Action: Server operation continues. ANR8283W (HP-UX) SNMP driver unable to
ANR8281W (Windows NT) HTTP driver unable to
master TCP/IP socket on which to listen to SNMP
subagents. The reason code is the return code from the
Explanation: While initializing HTTP communications, TCP/IP bind API.
the server has failed to connect to a master TCP/IP
server cannot accept sessions from SNMP subagents to
the return code from the TCP/IP bind API.
run macro commands.
file with the PORT option. If TCP/IP or HTTP is also in
User Response: Ensure that no other application is use for client sessions, ensure that the same port
using the port number specified in the server options number is not specified for TCP/IP or HTTP
file with the PORT option. If TCP/IP is also in use for communications and SNMP communications. This may
client sessions, ensure that the same port number is not be done by issuing the TCP/IP netstat command.
specified for both TCP/IP and HTTP communications.
ANR8283W (Solaris) SNMP driver unable to
started immediately, you may be within the TCP/IP
down the sever, wait one minute, and then restart the Explanation: While initializing TCP/IP
server. If that does not work, it may be necessary to communications, the server has failed to connect to a
restart Windows NT. master TCP/IP socket on which to listen to SNMP
TCP/IP bind API.
ANR8282I (HP-UX) SNMP driver ready for
connection with subagent on port port System Action: Server operation continues, but the
number. server cannot accept sessions from SNMP subagents to
run macro commands.
SNMP subagents on the indicated port number. User Response: Ensure that no other application is

ANR8283W (Windows NT) • ANR8286W
use for client sessions, ensure that the same port
ANR8284W (Windows NT) HTTPS driver unable to
number is not specified for TCP/IP or HTTP
initialize due to error in secure data
communications and SNMP communications.
initialization, reason code reason code.
ANR8283W (Windows NT) HTTPS driver unable to
communications, the server has failed to initialize the
secure data certificate information.
clients using HTTPS protocol.
master TCP/IP socket on which to listen for clients.
The reason code is the return code from the TCP/IP User Response: Ensure the keyring file name and
bind API. keyring file password are correct and that the password
has not expired. Check for earlier SKIT messages which
may indicate the real problem. Replace keyring if
necessary and re-start the server.
ANR8285I Shared Memory driver ready for
file with the PORT option. If TCP/IP is also in use for
client sessions, ensure that the same port number is not Explanation: The server is now able to accept sessions
specified for both TCP/IP and HTTPS communications. with clients using the Shared Memory protocol.
started immediately, you may be within the TCP/IP User Response: None.
server. If that does not work, it may be necessary to ANR8285I (HP-UX) Shared Memory driver ready for
restart Windows NT. connection with clients on port port
ANR8284E The Shared Memory Communications with clients using the Shared Memory protocol.
Protocol could not initialize. System Action: Server operation continues.
Explanation: The server was unable to initialize the User Response: None.
Shared Memory Communications Protocol due to an
error.
ANR8285I (Solaris) Shared Memory driver ready for
System Action: Server operation continues without connection with clients on port port
Shared Memory Communications.
User Response: Examine previous error messages for with clients using the Shared Memory protocol.
the cause of the failure.
ANR8284E (Solaris) The Shared Memory User Response: None.

Communications Protocol could not
initialize. ANR8285I (Windows NT) SNMP driver ready for
Explanation: The server was unable to initialize the connection with subagent on port port
Shared Memory Communications Protocol due to an number.
error. Explanation: The server can now accept sessions with
System Action: Server operation continues without SNMP subagents on the indicated port number.
Shared Memory Communications. System Action: Server operation continues.
User Response: Examine previous error messages for User Response: None.
the cause of the failure.
ANR8286W Unable to initialize Shared Memory

Explanation: Because the operating system rejected a
memory allocation request, the server cannot start
communications through the Shared Memory protocol.

ANR8286W (HP-UX) • ANR8288W
System Action: Server operation continues, but the communications and SNMP communications. This may
server cannot accept sessions from clients using the be done by issuing the TCP/IP netstat -s command. If
Shared Memory protocol. 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
space for AIX. You may also use SMIT to determine if
the sever, wait one minute, and then restart the server.
the number of applications is causing a memory
If that does not work, it may be necessary to restart
shortage. It may be necessary to cut down on the
Windows NT.
ANR8287W Unable to initialize Shared Memory
driver - error creating acceptor socket.
ANR8286W (HP-UX) Unable to initialize Shared
Reason code reason code.
Memory driver - insufficient memory.
Explanation: Because TCP/IP rejected a request for a
socket on which to listen, the server cannot start
memory allocation request, the server cannot start
communications through Shared Memory.
communications through the Shared Memory protocol.
Shared Memory protocol.
User Response: If TCP/IP is not started, use the
HALT command from any server prompt to stop the
space for HP-UX. You may also use SAM to determine
server, and restart it.
shortage. It may be necessary to cut down on the
maximum number of client sessions by changing the ANR8287W (HP-UX) Unable to initialize Shared
MAXSESSIONS option in the server options file. Memory driver - error creating acceptor
socket. Reason code reason code.
ANR8286W (Solaris) Unable to initialize Shared Explanation: Because TCP/IP rejected a request for a
Memory driver - insufficient memory. socket on which to listen, the server cannot start
communications through Shared Memory.
memory allocation request, the server cannot start System Action: Server operation continues, but the
communications through the Shared Memory protocol. server cannot accept sessions from clients using the
server cannot accept sessions from clients using the User Response: If TCP/IP is not started, use the
Shared Memory protocol. HALT command from any server prompt to stop the
server, and restart it.
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 ANR8287W (Solaris) Unable to initialize Shared
the MAXSESSIONS option in the server options file. Memory driver - error creating acceptor
socket. Reason code reason code.
ANR8286W (Windows NT) SNMP driver unable to Explanation: Because TCP/IP rejected a request for a
initialize due to error in BINDing to socket on which to listen, the server cannot start
Port port, reason code reason code. communications through Shared Memory.
Explanation: While initializing TCP/IP System Action: Server operation continues, but the
communications, the server has failed to connect to a server cannot accept sessions from clients using the
master TCP/IP socket on which to listen to SNMP Shared Memory protocol.
User Response: If TCP/IP is not started, use the
TCP/IP bind API.
HALT command from any server prompt to stop the
System Action: Server operation continues, but the server, and restart it.
server cannot accept sessions from SNMP subagents to
run macro commands.
ANR8288W Unable to establish Shared Memory
User Response: Ensure that no other application is connection - insufficient memory.
use for client sessions, ensure that the same port
number is not specified for TCP/IP or HTTP System Action: Server operation continues, but the

ANR8288W (HP-UX) • ANR8290W (HP-UX)
ANR8289W (HP-UX) Shared Memory driver is
User Response: Ensure that there is sufficient paging terminating due to error in creating a
space for AIX. You may also use SMIT to determine if new thread.
the number of applications is causing a memory
shortage. You may also wish to cut down on the
accept with the MAXSESSIONS option in the server System Action: Server operation continues, but Shared
options file. Memory communications is inoperative.
ANR8288W (HP-UX) Unable to establish Shared memory. Ensure that there is sufficient paging space for
Memory connection - insufficient HP-UX. You may also use SAM to determine if the
memory. number of applications is causing a memory shortage.
You may also wish to cut down on the maximum
number of sessions that the server can accept with the
ANR8289W (Solaris) Shared Memory driver is
User Response: Ensure that there is sufficient paging terminating due to error in creating a
space for HP-UX. You may also use SAM to determine new thread.
shortage. You may also wish to cut down on the
accept with the MAXSESSIONS option in the server System Action: Server operation continues, but Shared
options file. Memory communications is inoperative.
ANR8288W (Solaris) Unable to establish Shared memory. Ensure that there is sufficient swap space for
Memory connection - insufficient Solaris. You may also wish to cut down on the
memory. maximum number of sessions that the server can
options file.
ANR8290W Error sending data through Shared
Memory. Reason return code.
User Response: Ensure that there is sufficient swap
Explanation: The server experienced an error return
space for Solaris. You may also wish to cut down on
code while sending data through shared memory. This
the maximum number of sessions that the server can
may be a normal event if either side of the connection
is abruptly ended.
options file.
continues.
ANR8289W Shared Memory driver is terminating
due to error in creating a new thread. User Response: If the session is ended as a result of
System Action: Server operation continues, but Shared
ANR8290W (HP-UX) Error sending data through
Memory communications is inoperative.
Shared Memory. Reason return code.
memory. Ensure that there is sufficient paging space for
AIX. You may also use SMIT to determine if the
is abruptly ended.
You may also wish to cut down on the maximum
number of sessions that the server can accept with the System Action: The session is ended. Server operation
MAXSESSIONS option in the server options file. continues.

ANR8290W (Solaris) • ANR8292W (Solaris)
ANR8290W (Solaris) Error sending data through
continues.
is abruptly ended.
ANR8291W (Windows NT) Unable to bind to
IPX/SPX master socket. Return code =
continues.
return code.
Explanation: The server cannot initiate
communications on the socket number designated for
its use.
ANR8290I (Windows NT) IPX/SPX driver ready for
communications using the IPX/SPX protocol is
connection with clients on socket IPX
inoperative.
socket number.
User Response: Ensure that SPX has been configured
to run on this system through the requester
with clients using the IPX/SPX protocol on the
configuration program. Ensure that there is no other
indicated socket number.
instance of the server running on the same system that
System Action: Server operation continues. is using the same socket number. This is likely to be the
case if the return code is zero. Also ensure that the
number of SPX sessions (as specified in your NET.CFG
file) has not been exceeded through other applications
ANR8291W Error receiving data through Shared using the IPX/SPX protocol.
Memory. Reason return code.
Explanation: The server experienced an error return ANR8292W Session terminated when no data was
code while receiving data through the Shared Memory read through Shared Memory.
protocol. This may be a normal event if either side of
Explanation: The server is unable to read data from
the connection is abruptly ended.
Shared Memory. This may be a normal event if either
System Action: The session is ended. Server operation side of the connection is abruptly ended.
continues.
User Response: If the session is ended as a result of continues.
ANR8291W (HP-UX) Error receiving data through
ANR8292W (HP-UX) Session terminated when no
Explanation: The server experienced an error return data was read through Shared Memory.
code while receiving data through the Shared Memory
continues.
continues.
ANR8291W (Solaris) Error receiving data through

ANR8292W (Solaris) Session terminated when no
data was read through Shared Memory.
code while receiving data through the Shared Memory

ANR8292W (Windows NT) • ANR8294W (HP-UX)
ANR8293W (Solaris) Shared Memory driver unable
continues.
to initialize due to socket initialization
User Response: If the session is ended as a result of error.
Explanation: While initializing Shared Memory
communications, the server failed to set up an interface
with TCP/IP.
ANR8292W (Windows NT) IPX/SPX connection
terminated - insufficient memory.
Explanation: The server cannot accept a client session Shared Memory protocol.
System Action: Server operation continues. and is active on your system. You may issue the
TCP/IP ping command to your own address to verify
User Response: The most likely cause is a lack of that TCP/IP is both started and active.
the Windows NT control panel and then click on the ANR8293W (Windows NT) IPX/SPX driver unable to
virtual memory button. Refer to the online help for initialize due to error in LISTENing on
instructions on how to increase the amount of virtual the master socket, return code = return
memory. You may also wish to cut down on the code.
requests from clients using IPX/SPX, the server
options file.
encountered an error.
ANR8293W 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
with TCP/IP.
the getipxad command to determine if an endpoint can
System Action: Server operation continues, but the still be opened and bound; also determine if you can
server cannot accept sessions from clients using the still connect to a NetWare server.
User Response: Ensure that TCP/IP has been started ANR8294W Shared Memory session unable to
and is active on your system. You may issue the initialize.
TCP/IP ping command to your own address to verify
Explanation: While initializing a Shared Memory
that TCP/IP is both started and active.
communications session, an error occurred during
initial setup.
ANR8293W (HP-UX) Shared Memory driver unable
to initialize due to socket initialization
session is terminated.
error.
for assistance in resolving the error.
with TCP/IP.
ANR8294W (HP-UX) Shared Memory session unable
to initialize.
Shared Memory protocol. Explanation: While initializing a Shared Memory
initial setup.
and is active on your system. You may issue the
TCP/IP ping command to your own address to verify System Action: Server operation continues, but the
that TCP/IP is both started and active. session is terminated.

ANR8294W (Solaris) Shared Memory session unable
to initialize.
User Response: Ensure that no application is using
Explanation: While initializing a Shared Memory
the port number specified in the server options file
with the SHMPORT option by issuing the TCP/IP
initial setup.
netstat command. If the server was brought down and
System Action: Server operation continues, but the client sessions were active, it may be necessary to
session is terminated. terminate the client sessions on the client systems
before the port can be freed.
to initialize due to error in BINDing to
ANR8294W (Windows NT) Unable to establish
IPX/SPX connection - accept error.
Return code = tli error. Explanation: While initializing Shared Memory
communications, the server failed to connect to a
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
client sessions were active, it may be necessary to
number of SPX sessions has not been exceeded through
terminate the client sessions on the client systems
other applications using the IPX/SPX protocol, such as
before the port can be freed.
NetWare applications.

ANR8295W Shared Memory driver unable to
session session number. Reason return
code.
code from IPX/SPX while sending data on the
communications, the server failed to connect to a
indicated session. This may be a normal event if either
continues.
Shared Memory protocol. User Response: If the session is ended as a result of
response is required. Otherwise, ensure that IPX/SPX is
still active.
client sessions were active, it may be necessary to ANR8296W Shared Memory driver unable to
terminate the client sessions on the client systems initialize due to error in LISTENing on
before the port can be freed. the specified Port, reason code reason
code.
ANR8295W (HP-UX) Shared Memory driver unable Explanation: While attempting to listen for session
to initialize due to error in BINDing to requests from clients using TCP/IP, TCP/IP returns an
Port port, reason code reason code. error. The reason code is the return code from the
TCP/IP listen API.
communications, the server failed to connect to a System Action: Server operation continues, but the
master socket on which to listen for clients. The reason server cannot accept additional sessions from clients
code is the return code from the TCP/IP bind API. using the Shared Memory protocol.
System Action: Server operation continues, but the User Response: Ensure that TCP/IP is running

ANR8296W (HP-UX) • ANR8300E
ANR8297W (HP-UX) Shared Memory driver is
possible to bring the server down and restart it to
new session, reason code reason code.
allow additional client sessions to start.
request from a client using the Shared Memory
ANR8296W (HP-UX) Shared Memory driver unable
protocol, TCP/IP returns an error. The reason code is
to initialize due to error in LISTENing
the return code from the TCP/IP accept API.
on the specified Port, reason code reason
code. System Action: Server operation continues, but the
using the Shared Memory protocol.
error. The reason code is the return code from the User Response: Ensure that TCP/IP is running
TCP/IP listen API. properly. This may be done by issuing the TCP/IP
netstat -s and ping commands to other nodes on your
ANR8297W (Solaris) Shared Memory driver is
new session, reason code reason code.
allow additional client sessions to start. Explanation: While attempting to accept a session
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.
to initialize due to error in LISTENing
on the specified Port, reason code reason System Action: Server operation continues, but the
code. server cannot accept additional sessions from clients
requests from clients using TCP/IP, TCP/IP returns an User Response: Ensure that TCP/IP is running
error. The reason code is the return code from the properly. This may be done by issuing the TCP/IP
TCP/IP listen API. netstat -s and ping commands to other nodes on your
ANR8300E I/O error on library library name
(OP=internal code, CC=internal code,
KEY=internal code, ASC=internal code,
ASCQ=internal code, SENSE=sense data,
Description=error description). Refer to
allow additional client sessions to start.
Appendix D in the ’Messages’ manual
for recommended action.
ANR8297W Shared Memory driver is terminating
Explanation: An I/O error has occurred while
due to error in accepting a new session,
operating on the designated library device.
reason code reason code.
request from a client using the Shared Memory User Response: Ensure that the DEVICE parameter
protocol, TCP/IP returns an error. The reason code is associated with the library was identified correctly in
the return code from the TCP/IP accept API. the DEFINE LIBRARY 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 drive or
library reference manual provided with the device
usually contain tables that explain the values of the
User Response: Ensure that TCP/IP is running KEY, ASC, and ASCQ fields. If the problem persists,
properly. This may be done by issuing the TCP/IP contact your service representative and provide the
netstat -s and ping commands to other nodes on your internal code values and sense data from this message.

User Response: Ensure that the DEVICE parameter
ANR8301E I/O error on library library name
associated with the drive was identified correctly in the
(OP=internal code, SENSE=internal code).
DEFINE DRIVE command, and that the device is
Explanation: An I/O error has occurred while currently powered on and ready.
operating on the designated library device.
System Action: The operation fails. ANR8305E Library library name is not ready or not
operational.
associated with the library was identified correctly in Explanation: The specified automated library device is
the DEFINE LIBRARY command, and that the library either not ready or not in an operational state.
device is currently powered on and ready. If the library
System Action: Initialization of the library device fails.
has an access door, make sure it is closed. If the
problem persists, contact your service representative User Response: Ensure that the library is powered on
and provide the internal code values from this and ready for automated operations. Further
message. 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
ANR8302E I/O error on drive drive name
startup, however, initialization may be retried after a
(OP=internal code, Error Number=internal
short waiting period.
code, CC=internal code, KEY=internal code,
ASC=internal code, ASCQ=internal code,
SENSE=sense data, Description=error ANR8306I Request number: Insert device type volume
description). Refer to Appendix D in the volume name mount mode into the slot
’Messages’ manual for recommended with element number slot element of
action. library library name within time limit
minutes; issue ’REPLY’ along with the
Explanation: An I/O error has occurred while
request ID when ready.
operating on the designated drive.
Explanation: A CHECKIN LIBVOLUME or a LABEL
LIBVOLUME command is in progress, and the
User Response: Ensure that the DEVICE parameter specified volume is needed. The server expects the
associated with the drive was identified correctly in the volume to be inserted into the slot with the specified
DEFINE DRIVE command, and that the device is element number of the given library within the time
currently powered on and ready. The drive or library limit specified in the message. For the slot and element
reference manual provided with the device usually number diagram of your library, refer to the
contain tables that explain the values of the KEY, ASC, documentation provided with the current ptf level or
and ASCQ fields. If the problem persists, contact your refer to the Administrator’s Guide for your release and
service representative and provide the internal code platform.
values and sense data from this message.
System Action: The server waits until a REPLY
command is issued, or until the time limit expires.
ANR8303E I/O error on drive drive name
User Response: Insert the volume into the slot and
(OP=internal code, SENSE=internal code).
issue a REPLY command, along with the request ID, to
Explanation: An I/O error has occurred while tell the server that the volume has been inserted.
operating on the designated drive.
System Action: The operation fails. ANR8307I Request number: Remove device type
volume volume name from slot with
element number slot name of library
associated with the drive was identified correctly in the
library name; issue ’REPLY’ along with
DEFINE DRIVE command, and that the device is
the request ID when ready.
currently powered on and ready. If the problem
persists, contact your service representative and Explanation: A CHECKOUT LIBVOLUME command
provide the internal code values from this message. 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
ANR8304E Time out error on drive drive name in
diagram of your library, refer to the documentation
library library name.
provided with the current ptf level or refer to the
Explanation: A time out condition occurred while Administrator’s Guide manual for your release and
waiting for the given drive to become ready so that platform.
automated library operations could be performed.
System Action: The operation fails. command is issued.

User Response: Remove the volume from the slot and System Action: The operation fails.
store it in a safe place. Issue a REPLY command, along
with the request ID, to tell the server that the volume
associated with the drive is identified correctly in the
has been removed. The volume can be returned to the
DEFINE DRIVE command, and that the drive is
library with the CHECKIN LIBVOLUME command.
currently powered on and ready. After checking and
correcting these potential problems, retry the operation.
ANR8308I Request number: device type volume volume
name is required for use in library library
ANR8312E Volume volume name could not be
name; CHECKIN LIBVOLUME required
located in library library name.
within time limit minutes.
Explanation: The designated volume cannot be found
Explanation: A mount request has been made for a
at its expected location in the given library.
volume that is defined in a storage pool, but which is
currently checked out of the given library. System Action: The operation fails.
System Action: The server waits until it detects that User Response: Perform an AUDIT LIBRARY
the volume has been checked into the library, or the operation on the designated library, which forces the
time limit expires. server to reevaluate its inventory information for
volumes in the library.
User Response: Obtain the required volume, and
insert it into the library by issuing a CHECKIN
LIBVOLUME command. Use the SWAP=YES option of ANR8313E Volume volume name is not present in
the CHECKIN LIBVOLUME command if the library is library library name.
currently full; this process allows the server to select an
appropriate volume to be swapped out in order to Explanation: A mount request is made for the given
make room for the required volume. volume in the specified library, but the volume is not
currently checked into the library.
ANR8309E Mount attempt failed - library library System Action: The mount operation fails. If the
name is not defined. volume is being mounted for storage pool I/O (as
opposed to import/export I/O), its ACCESS attribute is
Explanation: An attempt has been made to mount a changed to UNAVAILABLE to prevent further mount
volume, but the attempt fails because the specified requests.
library is not defined.
User Response: Issue a CHECKIN LIBVOLUME
System Action: The operation fails. command to return the volume into the library, and
update the volumes ACCESS attribute to READONLY
User Response: Ensure that the LIBRARY attribute of
or READWRITE using the UPDATE VOLUME
the device class associated with the mount operation
command. Retry the mount request.
identifies a defined library. If not, correct the value of
the LIBRARY attribute, or define the specified library
and retry the operation. ANR8314E Library library name is full.
Explanation: A library operation fails because all of
ANR8310E An I/O error occurred while accessing the library’s storage locations are occupied.
Explanation: An I/O error occurs while accessing the
designated library. User Response: Issue a CHECKOUT LIBVOLUME
command to make room in the library. Retry the library
System Action: The operation fails. operation.
associated with the library is identified correctly in the ANR8315E Command: The device type of drive drive
DEFINE LIBRARY command, and that the library is name is not supported in library type
currently powered on and ready. If the library has an libraries.
access door, make sure it is closed. After checking and
correcting these potential problems, retry the operation. Explanation: Drives of the type identified in the
command are not supported in the given type of
library.
ANR8311E An I/O error occurred while accessing
drive drive name for low-level operation System Action: The command is not processed.
operation, errno = drive errno. User Response: Determine whether the drive and
Explanation: An I/O error occurs while performing library combination is supported by the installed level
the operation on the specified drive. of the server. If so, contact your service representative.

ANR8316E Selecting swap volume to be checked ANR8320I Request number: Insert device type volume
out of library library name. volume name mount mode in drive drive
name of library library name within time
Explanation: A CHECKIN LIBVOL command was
limit minute(s); issue ’REPLY ’ along
issued for a library that has no empty slots to hold the
with the request ID when ready.
new cartridge. The SWAP=YES parameter was included
in the command. Explanation: A CHECKIN LIBVOLUME or a LABEL
LIBVOLUME command is in progress, and the
System Action: A CHECKOUT LIBVOL command
specified volume is needed. The server expects the
will be automatically be issued, specifying either a
volume to be inserted in the designated drive of the
scratch volume or, if there are none, a volume with the
given library within the time limit specified in the
lowest number of mounts.
message.
User Response: Use a supported type of drive.
volume from the library and store it in a safe place.
command is issued, or until the time limit expires.
Issue a REPLY command to tell the server that the
volume has been removed. The volume can be User Response: Insert the volume into the drive, and
introduced back into the library with the CHECKIN then issue a REPLY command, along with the request
LIBVOLUME command. ID, to tell the server that the volume has been inserted.
ANR8317I The volume in device type drive drive ANR8321I Request number: Remove device type
name must be manually ejected. volume volume name from drive drive
name of library library name; issue
Explanation: This device type does not automatically
’REPLY’ along with the request ID when
eject the volume when it is dismounted and requires
ready.
that the volume be manually ejected from the drive.
Explanation: A CHECKOUT LIBVOLUME or a
LABEL LIBVOLUME command has completed. You can
User Response: Physically eject the volume from the remove the specified volume from the designated drive
drive. and store it outside the library.
ANR8318I Request number: Mount side side of device command is issued.
type volume volume name mount mode in
User Response: Remove the volume from the drive
drive drive name of library library name
and store it in a safe place. Issue a REPLY command,
within time limit< minutes.
along with the request ID, to tell the server that the
Explanation: The server requires that the specified volume has been removed. The volume can be returned
volume be mounted as requested. Since the volume is to the library with the CHECKIN LIBVOLUME
two-sided, this message specifies which side (A or B) is command.
needed by the server for I/O operations.
System Action: The server waits for the volume to be ANR8322I Request number: Remove device type
mounted. volume volume name from entry/exit port
of library library name; issue ’REPLY’
User Response: Mount the volume in the specified along with the request ID when ready.
drive.
Explanation: A CHECKOUT LIBVOLUME command
has completed. You can remove the specified volume
ANR8319I Request number: Insert device type volume from the entry/exit port of the given library and store
volume name mount mode into library it elsewhere.
library name within time limit minute(s).
Explanation: A CHECKIN LIBVOLUME command is command is issued.
in progress, and the specified volume is needed. The
server expects the volume to be inserted into the User Response: Remove the volume from the library
library with the convenience I/O station mechanism. and store it in a safe place. Issue a REPLY command,
along with the request ID, to tell the server that the
System Action: The server waits until the volume is volume has been removed. The volume can be returned
in the library, or until the time limit expires. to the library with the CHECKIN LIBVOLUME
User Response: Insert the specified volume into the command.
library. If the volume has already been inserted into the
library, no user action is necessary.

ANR8323I Request number: Insert device type volume ANR8327E Command: Cannot cancel request request
volume name mount mode into entry/exit number.
port of library library name within time
Explanation: The request, whose number is specified
limit minute(s); issue ’REPLY’ along with
by the given command, cannot be canceled. The
requested operation must be completed.
Explanation: A CHECKIN LIBVOLUME or a LABEL
System Action: The cancel request command is not
LIBVOLUME cmmand is in progress, and the specified
processed.
volume is needed. Mount the volume in the entry/exit
port of the given library within the time limit specified User Response: Proceed with the requested operation.
in the message.
System Action: The server waits until a REPLY ANR8328I Request number: device type volume volume
command is issued, or until the time limit expires. name mounted in drive drive name.
User Response: Insert the volume into the library’s Explanation: The server verifies that a requested
entry/exit port; and issue a REPLY command, along volume has been mounted properly in the given drive.
with the request ID, to tell the server that the volume
has been inserted. System Action: The volume is accessed for reading or
writing, or both.
ANR8324I Device type volume volume name is User Response: None.

expected to be mounted (mount mode).
Explanation: The specified volume is expected to be ANR8329I Device type volume volume name is
mounted in the near future so the server can access it mounted mount mode in drive drive name,
for reading or writing. status: IDLE.
System Action: None. Explanation: In response to a QUERY MOUNT

command, the server indicates that the given volume is
User Response: If the volume is stored offline, retrieve mounted in the specified drive. The volume is currently
it so that it is readily accessible when the server idle, meaning no active operations are being performed.
requests that it be mounted. 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.
ANR8325I Dismounting volume volume name -
mount retention period minute mount System Action: None.
retention expired.
Explanation: The specified volume is dismounted
because the given mount retention period has expired.
ANR8330I Device type volume volume name is
System Action: The volume is dismounted. mounted mount mode in drive drive name,
status: IN USE.
Explanation: In response to a QUERY MOUNT
ANR8326I Request number: Mount device type volume
mounted in the specified drive. The volume is currently
volume name mount mode in drive drive
in use, meaning that read or write operations, or both,
name of library library name within time
are being performed.
limit minutes.
Explanation: If the volume name includes the names
EXP, IMP, DUMP, or DBBK, the request is for a scratch User Response: None.
volume.
System Action: The server waits for the volume to be ANR8331I Device type volume volume name is
mounted. mounted mount mode in drive drive name,
status: DISMOUNTING.
User Response: Mount the volume in the specified
drive. Explanation: In response to a QUERY MOUNT
mounted in the specified drive. The volume is currently
being dismounted by the server.

ANR8332I Device type volume volume name is ANR8337I Device type volume volume name mounted
mounted mount mode, status: IDLE. in drive drive name.
Explanation: In response to a QUERY MOUNT Explanation: The server verifies that the specified
command, the server indicates that the given volume is mount request has been completed properly. Read or
mounted for I/O operations. The volume is currently write operations, or both, can be performed on the
idle, meaning no active operations are being performed. volume.
If the volume remains in the idle state for the amount
System Action: The label of the volume has been
of time specified by the device class mount retention
verified.
period, it will be automatically dismounted.
ANR8338E Device type volume volume name cannot
be overwritten by EXPORT operation.
mounted mount mode, status: IN USE.
contains data, so that the server cannot allow new
Explanation: In response to a QUERY MOUNT export data to be written to it.
mounted for I/O operations. The volume is currently in
use, meaning that read or write operations, or both are
overwritten by the requested export operation.
being performed.
contain any valuable data, delete it and retry the export
User Response: None. operation.
ANR8334I Number of matches matches found. ANR8339E Device type volume intended volume name
in drive drive name was replaced with
Explanation: This is a summary message for the
volume incorrect volume name.
QUERY MOUNT command. It indicates the total
number of mount points that have been reported in the Explanation: The server detects that a previously
command output. 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,
User Response: None. can occur on the given drive, because data corruption
may occur.
ANR8335I Request number: Verifying label of device System Action: The server dismounts the volume
type volume volume name in drive drive from the drive.
name.
User Response: Mount the correct volume again if it
Explanation: The server verifies the label of the is in a manual library and retry the operation.
volume that has been requested by an earlier mount
message. This is done to ensure that the correct volume
ANR8340I Device type volume volume name
has been mounted by the operator.
mounted.
System Action: The server reads the volume label and
Explanation: The server has mounted the given
checks it for validity.
volume.
System Action: Read or write operations, or both, will
commence for the volume.
ANR8336I Verifying label of device type volume
volume name in drive drive name.
Explanation: The server verifies the label of a volume
ANR8341I End-of-volume reached for device type
that is needed for read or write operations, or both.
volume volume name.
This is done to ensure that the correct volume has been
mounted. Explanation: The server has detected an
end-of-volume condition for the given volume.
System Action: The server reads the volume label and
checks it for validity. System Action: The volume is marked full. If more
data must be stored, the server will access another
volume for it.

ANR8347E Command: Volume volume not found.
Explanation: A DISMOUNT VOLUME command is
ANR8342I Request request number for volume
issued, but the volume to be dismounted cannot be
volume name canceled by administrator
found.
name.
Explanation: A mount request is canceled by the given
administrator. User Response: Ensure that the correct volume name
is entered.
System Action: The system cancels the mount request.
ANR8348E Command: Volume volume is not ″Idle″.
Explanation: A DISMOUNT VOLUME command has
ANR8343I Request request number for volume
been issued, but the volume is still in use and cannot
volume name canceled (PERMANENT) by
be dismounted.
administrator name.
Explanation: A mount request is successfully canceled
with the PERMANENT option. User Response: If it is necessary to dismount the
volume, cancel the session or process that is using the
System Action: The system cancels the mount request
and marks the volume as unavailable.
ANR8349E Command: Device device not found.
ANR8344E Command: Invalid request number -
been issued, but the device to be dismounted cannot be
request number.
found.
Explanation: A command has been entered with an
incorrect request number.
User Response: Ensure that the correct device has
been specified.
command.
User Response: Issue the command with the correct
ANR8350E Command: Device device is not ″Idle″.
request number.
been issued, but the device is still in use and cannot be
ANR8345E Command: No match found for this
dismounted.
request number.
Explanation: The request number specified by the
command is not in the list of outstanding mount User Response: If it is necessary to dismount the
requests. device, cancel the session or process that is using the
device, and reissue the command.
command.
ANR8351E Request number: Mount request for
User Response: Issue the command with the correct
volume volume name has timed out.
request number.
Explanation: The mount request has not been satisfied
in the requested time.
ANR8346I Command: No requests are outstanding.
System Action: The server fails the mount request.
Explanation: A QUERY REQUEST or CANCEL
REQUEST command has been entered although no User Response: Retry the mount request and ensure
mount requests are outstanding. 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
User Response: None. the device class.

library, the library itself may need to be audited by
ANR8352I Requests outstanding:
using the AUDIT LIBRARY command.
Explanation: This message provides a list of currently v The DEVICE parameter associated with the drive is
outstanding mount requests. identified correctly in the DEFINE DRIVE command,
System Action: The server lists all outstanding mount and the drive is currently powered on and ready.
requests or the one specified on the QUERY REQUEST After checking and correcting these potential problems,
command. retry the operation.
ANR8356E Incorrect volume mounted volume name
ANR8353E Request number: I/O error reading label was mounted instead of volume expected
of volume in drive drive name. volume name in library library name.
Explanation: The server detects an error while reading Explanation: The incorrect volume has been mounted
the volume label from the volume in the specified in the designated library. This error can occur if the
drive. library inventory has been altered due to manual
intervention or movement of volumes, or both.
System Action: The volume is ejected, and the server
continues to wait for the requested volume to be System Action: The volume is dismounted; the
mounted. expected volume may be marked unavailable if this
error occurs during normal volume mount activity.
User Response: Ensure the following:
User Response: Use the AUDIT LIBRARY command
v The requested volume is properly inserted in the
to force the library to reevaluate its inventory of
designated drive.
volumes.
v The volume has been labeled by using the
DSMLABEL utility program before you attempt to
use it with the server. ANR8357I Error reading label of volume from
slot-element element address in drive drive
v The DEVICE parameter associated with the drive is
name of library library name.
identified correctly in the DEFINE DRIVE command,
and the drive is currently powered on and ready. Explanation: While processing a search-mode
CHECKIN LIBVOLUME command for the designated
After checking and correcting these potential problems,
library, the server finds a volume whose label cannot be
retry the operation.
read.
System Action: The volume is dismounted and is not
ANR8354E Request number: Incorrect volume (volume
checked into the library.
name) mounted in drive drive name.
User Response: Remove the volume from the library
Explanation: The user has inserted the named volume
and ensure that it is properly labeled. After doing so,
into the indicated drive, but it is not the one requested
the volume can be checked into the library.
by the server.
ANR8358E Audit operation is required for library
continues to wait for the requested volume to be
library name.
mounted.
Explanation: The server encounters a problem
User Response: Ensure that the requested volume is
managing the given library, and determines that an
inserted properly into the designated drive.
AUDIT LIBRARY operation should be performed.
System Action: The server may continue to access the
ANR8355E I/O error reading label for volume
library, but some volumes may not be accessible until
volume name in drive drive name.
an AUDIT LIBRARY command is issued against the
Explanation: The server detects an error while library.
reading/verifying the volume label for the volume in
User Response: Issue an AUDIT LIBRARY command
the specified drive.
against the library.
System Action: The volume is dismounted by the
server.
ANR8359E Media fault detected on device type
User Response: Ensure the following: volume volume name in drive drive name
v Check the integrity of the data on the volume by of library library name.
issuing an AUDIT VOLUME command. If this error Explanation: The server encounters a media fault
occurs on a volume that is stored inside a SCSI while accessing the given volume using the specified
drive.

System Action: The operation that is attempting to System Action: The command is not processed.
access the volume will fail, and the volume will be
User Response: Wait until the server finishes using
immediately dismounted from the drive.
some of the mounted volumes, or force the server to
User Response: In some cases, the server will dismount idle volumes using the DISMOUNT
automatically mark the volume unavailable. If this does VOLUME command, then retry this command.
not happen automatically, issue an UPDATE VOLUME
command to set the volume’s access value to
ANR8365E Command: The parameter parameter
unavailable. This will prevent the server from trying to
cannot be changed.
mount the volume to satisfy user requests. Issue an
AUDIT VOLUME command to determine if any data Explanation: The specified parameter cannot be
has been lost due to the media failure. changed from the value that was provided with the
associated DEFINE command.
ANR8360I Volume volume name has been deleted System Action: The command is not processed.
from MANUAL library library name.
User Response: If it is necessary to use a different
Explanation: The specified volume has been deleted value for the given parameter, the associated object
by the server. It can be returned to a scratch pool by must be deleted and then redefined using the new
the mount operator if desired. parameter value.
System Action: The volume is removed from the
server’s inventory. ANR8366E Command: Invalid value for parameter
parameter.
Explanation: An invalid value has been provided for
the specified parameter.
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 parameter value.
ANR8367E Command: Multiple parameter values are
valid DEVTYPE parameter.
not allowed.
Explanation: The designated parameter is specified
ANR8362E Command: The parameter parameter is
more than once in the command; this is not allowed.
invalid for device type device type.
Explanation: The specified parameter is not valid for a
device class with the given device type. User Response: Reissue the command, but specify the
given parameter only once.
User Response: Reissue the command with a correct
ANR8368E Request number: Incorrect side (side) of
parameter.
volume volume name mounted in drive
drive name.
Explanation: The user inserted the wrong side of the
required for device type device type.
requested volume into the indicated drive.
given parameter be supplied when the indicated device
continues to wait for the requested side of the volume
type is used.
to be mounted.
User Response: Insert the correct side of the requested
User Response: Reissue the command, providing the volume into the designated drive.
required parameter value.
ANR8369E Library library name is not defined.
ANR8364E Command: Cannot reduce MOUNTLIMIT
Explanation: The designated library is not defined,
below number of volumes currently
but has been referenced in a mount request.
mounted.
System Action: The mount request is rejected.
Explanation: The MOUNTLIMIT value cannot be
reduced below the number of currently mounted User Response: Define the given library, or update the
volumes.

LIBRARY parameter of the device class that references with the request ID, to tell the server that the volumes
it. have been inserted.
ANR8370I Device type volume volume name is ANR8374E Unable to unmount mountpoint
mounted mount mode, status: RETRY. mountpoint name.
Explanation: In response to a QUERY MOUNT Explanation: A removable file device class mountpoint
command, the server indicates that the given volume is had to be unmounted using the operating system
mounted for I/O operations. The volume is currently in unmount function. The server did not have permission
RETRY, meaning an attempt is being made to to unmount the directory specified.
re-establish communications with another server. If the
System Action: The server continues, but cannot use
volume remains in the retry state for the amount of
the mountpoint for removablefile support until the
time specified by the device class retry period, the
directory is unmounted.
operation will fail and the volume will be automatically
dismounted. User Response: It may be necessary to run the server
as a root user to mounted directories to be unmounted.
be overwritten by BACKUPSET
ANR8371I I/O is being bypassed for volume volume operation.
name.
Explanation: The indicated volume is mounted but contains data, so that the server cannot allow new
the server is bypassing actual I/O operations for the backup set data to be written to it.
volume. The pool associated with the volume matches
the NULLPOOLNAME option in the options file or
NULLFILEDEVCLASS YES has been specified in the
overwritten by the requested backup set operation.
options file.
User Response: None. backup set operation.
ANR8372I Request number: Remove device type ANR8376I Mount point reserved in device class
volume volume name from drive drive Device class name, status: RESERVED.
name of library library name.
Explanation: A LABEL LIBVOLUME command has command, the server indicates that there is a mount
completed. You can remove the specified volume from point reserved for future I/O operations in the given
the designated drive and store it outside the library. device class.
User Response: Remove the volume from the drive User Response: None.
and store it in a safe place.
ANR8373I Request number: Fill the bulk entry/exit mounted mount mode, status:
port of library library name with all device DISMOUNTING.
type volumes to be processed within time
limit minute(s); issue ’REPLY’ along with
currently being dismounted.
Explanation: A CHECKIN LIBVOLUME or LABEL
LIBVOL command with SEARCH=BULK is in progress.
Load all volumes to be processed into the multi-slot User Response: None.
entry/exit port of the given library within the time
limit specified in the message.
System Action: The server waits until a REPLY mounted mount mode, status: RETRY
command is issued, or until the time limit expires. DISMOUNT FAILURE.
User Response: Insert the volumes into the library’s Explanation: In response to a QUERY MOUNT
entry/exit port; and issue a REPLY command, along command, the server indicates that it is currently

retrying the dismount of the given volume because of a
ANR8400I Library library name defined.
failure during the previous dismount.
Explanation: The designated library has been
successfully defined.
System Action: The library is defined and recorded in
the database.
ANR8379I Mount point in device class Device class
name is waiting for the volume mount to
complete, status: WAITING FOR
VOLUME. ANR8401E Command: Invalid library name library
name.
command, the server indicates that there is a mount Explanation: The designated library name is invalid;
point in the given device class waiting for the volume either it contains too many characters, or some of the
mount to complete. characters are invalid.
System Action: None. System Action: The command is not processed.
User Response: None. User Response: Reissue the command using a valid
library name.
mounted mount mode in drive drive name, ANR8402E Command: Library library name is already
status: RETRY DISMOUNT FAILURE. defined.
Explanation: Because of the failure of a previous Explanation: The designated library cannot be defined
dismount, the server is retrying the dismount of the because it already exists.
specified volume from the specified drive. In response
to a QUERY MOUNT command, the server indicates
that the volume is mounted in the drive. User Response: If you want to define an additional
library, reissue the command with a different library
name.
ANR8403E Command: Operation not allowed for
ANR8381E Device type volume volume name could library type libraries.
not be mounted in drive drive name.
Explanation: The requested operation is not allowed
Explanation: The server could not complete the for libraries of the given type.
specified mount request due to an error. Examine
previous messages for additional information regarding
the specified volume and the operation. User Response: None.
System Action: The requested operation fails.
ANR8404I Drive Drive name defined in library
User Response: Examine previous messages for
library name.
additional information regarding the specified volume
and the operation. Explanation: The designated drive has been
successfully defined as a member of the specified
library.
ANR8382W Library library name is now full.
System Action: The drive is defined and recorded in
Explanation: During a library checkin operation from
the database.
a multi-slot Entry/Exit station, the last storage location
was filled before checking the remainder of the User Response: None.
Entry/Exit slots. because all of the library’s storage
locations are occupied.
ANR8405E Command: Invalid drive name drive name.
System Action: The operation stops but is considered
successful if at least one volume is checked in. Explanation: The designated drive name is invalid;
either it contains too many characters, or some of the
User Response: If more volumes remain to be checked characters are invalid.
in, issue a CHECKOUT LIBVOLUME command to
make room in the library. Retry the library operation. System Action: The command is not processed.
User Response: Reissue the command using a valid
drive name.

ANR8406E Command: Drive drive name is already ANR8412I Drive drive name deleted from library
defined in library library name. library name.
Explanation: The designated drive cannot be defined Explanation: The designated drive has been deleted
because it has already been defined for the specified successfully from the specified library.
library.
System Action: The drive is deleted.
User Response: If you want to define an additional
drive, reissue the command with a different drive
ANR8413E Command: Drive drive name is currently
name.
in use.
Explanation: The designated drive cannot be deleted
ANR8407E Command: The MODEL parameter is
or updated because it is currently in use.
required for this command.
Explanation: The MODEL parameter has not been
provided; it is required. User Response: Wait until the drive is no longer in
use, and reissue the command.
User Response: Reissue the command using the
ANR8414E Command: Drive drive name is not
MODEL parameter.
defined in library library name.
Explanation: The designated drive has not been
ANR8408E Command: The DEVICE parameter is
defined in the given library.
Explanation: The DEVICE parameter has not been
provided; it is required. User Response: Reissue the command using a
different drive name. If appropriate, define the drive
before retrying the command.
User Response: Reissue the command using the
DEVICE parameter.
ANR8409E Command: Library library name is not
Explanation: The specified parameter must be
defined.
provided when processing the given command.
Explanation: The designated library has not been
defined.
User Response: Reissue the command, providing the
required parameter value.
User Response: Reissue the command using a
different library name, or define the library before
invalid for library type library type.
Explanation: The specified parameter is not valid for
ANR8410I Library library name deleted.
libraries of the given type. The scratchcategory must be
Explanation: The designated library has been deleted at lest 2 less than the privatecategory for 349x libraries.
successfully.
System Action: The library is deleted.
User Response: Reissue the command, using only the
User Response: None. proper parameters. If using the scratchcategory make
sure it is at least 2 less than the privatecategory.
ANR8411E Command: One or more drives are still
defined in library library name. ANR8417E Command: The parameter parameter is
invalid for drives in library type libraries.
Explanation: The designated library cannot be deleted
because there are still drives defined within it. Explanation: The specified parameter is not allowed
when defining or updating drives in a library of the
given type.
User Response: Delete all drives from the library, and

User Response: Reissue the command, using only the given library. The process is assigned the ID specified
proper parameters. in the message.
ANR8418E Command: An I/O error occurred while process to perform the operation in response to the
accessing library library name. CHECKIN LIBVOLUME command entered by an
administrator.
designated library. User Response: To obtain status on the process, issue
the QUERY PROCESS command. The process may be
canceled with the CANCEL PROCESS command.
associated with the library is identified correctly in the
ANR8423I CHECKIN LIBVOLUME process for
DEFINE LIBRARY command, and that the library is
library library name has been canceled.
currently powered on and ready. If the library has an
access door, make sure it is closed. After checking and Explanation: A background server process that has
correcting these potential problems, retry the operation. been working to check in one or more volumes for the
given library is canceled by the CANCEL PROCESS
command.
ANR8419E Command: The drive or element conflicts
with an existing drive in library library System Action: The server process is ended and
name. server operation continues.
Explanation: Either there are no more physical drives User Response: None.
in the library, or the specified ELEMENT parameter
conflicts with an existing defined drive in the given
ANR8424I Checking in volume volume name in
library.
Explanation: In response to a QUERY PROCESS
User Response: Specify a valid ELEMENT parameter command, this message displays the status for a
that is not used by any other drive in the library. CHECKIN LIBVOLUME process on the server. The
given volume is being checked in to the designated
library.
ANR8420E Command: An I/O error occurred while
accessing drive drive name. System Action: The background process operation
continues.
specified drive. User Response: None. The process may be canceled
by an authorized administrator using the CANCEL
PROCESS command.
associated with the drive is identified correctly in the
ANR8425I Checking in volumes in search mode in
DEFINE DRIVE command, and that the drive is
currently powered on and ready. After checking and
correcting these potential problems, retry the command. Explanation: In response to a QUERY PROCESS
command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. Volumes
ANR8421E Command: Unable to start a process for
are being checked into the given library automatically
this command.
using a search for previously-unknown volumes.
Explanation: The server cannot start a background
System Action: The background process operation
process to carry out the designated command.
continues.
User Response: None. The process may be canceled
User Response: Check for and correct memory by an authorized administrator using the CANCEL
shortages or other server resource constraints, and PROCESS command.
ANR8426E CHECKIN LIBVOLUME for volume
ANR8422I Command: Operation for library library volume name in library library name failed.
name started as process process ID.
Explanation: The background process for a CHECKIN
Explanation: A volume check-in process has been LIBVOLUME command has failed.
started to handle the insertion of a volume into the
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
present in library library name.
and ready, and then reissue the command.
Explanation: The specified volume cannot be checked
into the given library because it is already present.
ANR8427I CHECKIN LIBVOLUME for volume
volume name in library library name System Action: The command is not processed.
User Response: Provide the name of a volume that is
Explanation: The specified volume was successfully not already present in the given library. Use the
checked in to the library during processing of a QUERY LIBVOLUME command to obtain a full list of
CHECKIN LIBVOLUME or LABEL LIBVOLUME volumes that have already been checked into the
command. library.
System Action: The volume is made available for
mounting in the given library. ANR8433E Command: Volume volume name is not
present in library library name.
Explanation: The specified volume cannot be checked
out of the given library because it is not present.
ANR8428E Command: The STATUS parameter is
required for this command. System Action: The command is not processed.
Explanation: The STATUS parameter must be User Response: Provide the name of a volume that is
provided with the given command. present in the given library. Use the QUERY
LIBVOLUME command to obtain a full list of volumes
that reside in the library.
User Response: Reissue the command, and provide a
valid STATUS parameter value.
ANR8434I Command: Operation for volume volume
name in library library name started as
ANR8429E Command: No drives are currently process process ID.
defined in library library name.
Explanation: A volume check-out process has been
Explanation: The command cannot be issued until at started to handle the removal of a volume from the
least one drive has been defined in the given library. given library. The process is assigned the ID specified
in the message.
User Response: Define a drive in the library, using the process to perform the operation in response to the
DEFINE DRIVE command, and then retry the failed CHECKOUT LIBVOLUME command entered by an
command. administrator.
User Response: To obtain status on the process, issue
ANR8430I Volume volume name has been checked the QUERY PROCESS command. The process may be
into library library name. canceled with the CANCEL PROCESS command.
Explanation: A search-mode CHECKIN LIBVOLUME
process has found the given volume and automatically ANR8435I CHECKOUT LIBVOLUME for volume
checked it into the library. volume name in library library name has
System Action: The volume is added to the given been canceled.
library’s inventory. Explanation: A background server process that has
User Response: None. been working to check out the volume from the given
library is canceled by the CANCEL PROCESS
command.
ANR8431I CHECKIN LIBVOLUME process
completed for library library name; volume System Action: The server process is ended and
count volume(s) found. server operation continues.
Explanation: A search-mode CHECKIN LIBVOLUME User Response: None.

process is completed. The specified number of volumes
have been successfully added to the library’s inventory.
System Action: The volumes are made available for
use by the server.

ANR8436I Checking out volume volume name from ANR8441E Initialization failed for SCSI library
library library name. library name.
Explanation: In response to a QUERY PROCESS Explanation: The initialization process for the given
command, this message displays the status for a library has failed, and will not be retried until the next
CHECKOUT LIBVOLUME process on the server. time the server needs to access the library.
System Action: The background process operation System Action: The library is made temporarily
continues. unavailable.
User Response: None. The process may be canceled User Response: Make sure the library is powered on
by an authorized administrator using the CANCEL and attached.
PROCESS command.
ANR8442E Command: Volume volume name in library
ANR8437E CHECKOUT LIBVOLUME for volume library name is currently in use.
volume name in library library name failed.
Explanation: The command cannot be processed
Explanation: The background process for a because the specified volume is already being used for
CHECKOUT LIBVOLUME command has failed. another operation.
System Action: The background process ends, but the System Action: The command is not processed.
volume has not been checked out of the library.
User Response: Wait until the conflicting volume
User Response: Make sure the library and drive activity has completed, and then reissue the command.
devices associated with this command are powered on If the volume is currently mounted, but idle, you can
and ready, then retry the command. dismount it with the DISMOUNT VOLUME command
and then retry this operation.
ANR8438I CHECKOUT LIBVOLUME for volume
volume name in library library name ANR8443E Command: Volume volume name in library
completed successfully. library name cannot be assigned a status
of SCRATCH.
Explanation: The background process for a
CHECKOUT LIBVOLUME command has completed Explanation: The volume cannot be assigned to the
successfully. given library’s scratch pool because there is a storage
pool volume defined or a volume in the volume history
System Action: The volume is either deleted from the
file with this volume name. Such a volume may still
library’s inventory (if its status is something other than
contain valid data. Assigning the volume to the
DATA) or marked not present (if its status is DATA).
library’s scratch pool might result in a destructive
User Response: None. overwrite of the volume’s data.
ANR8439I SCSI library library name is ready for
User Response: Reissue the command, specifying that
operations.
the volume be assigned a status of PRIVATE.
Explanation: The initialization process for the given
library has completed successfully, and the library is
ANR8444E Command: Library library name is
ready for use.
currently unavailable.
System Action: The library is made ready for use.
Explanation: The requested operation cannot be
User Response: None. completed because the specified library is unavailable
for I/O operations. The library may still be carrying
out its initialization operations.
ANR8440E Initialization failed for SCSI library
library name; will retry in delay time System Action: The command is not processed.
minute(s).
User Response: Wait until the library initialization
Explanation: The initialization process for the given completes or the library becomes ready.
library has failed. It will be retried automatically after
the specified amount of time has elapsed.
ANR8445I Volume volume name in library library
System Action: The initialization will be retried later. name updated.
User Response: Ensure that the library device is Explanation: The specified library volume has been
powered on and ready. If the library has an access updated successfully.
door, make sure it is in the closed position.

System Action: The library volume inventory is a new name in the process, or delete the existing
updated. volume that caused the name conflict.
ANR8449E Scratch volume volume name rejected -
volume name is already in use.
ANR8446I Manual intervention required for library
library name. Explanation: The designated volume has been used to
satisfy a scratch mount, but the volume is already
Explanation: The specified library requires manual
defined in a storage pool, or has been used to store
intervention.
server export, database dump, or database backup
System Action: Current library activity will be information as recorded in the server volume history
delayed until the required intervention occurs. file.
User Response: If the library has an access door, make System Action: The volume is rejected.
sure it is in the closed position. If it has a cartridge
User Response: Use a volume that is not in use, or
carousel, make sure the carousel is installed. The server
rename the rejected volume or delete the existing
automatically detects when the appropriate action has
volume that caused the name conflict.
been taken; it will then continue its operations.
ANR8450E Command: Library library name is

ANR8447E No drives are currently available in
currently in use.
Explanation: The attempted operation cannot be
or updated because it is currently in use for an I/O
completed on the specified library because there are no
operation.
available drives. A drive may be unavailable because
an application other than the server may have the System Action: The command is not processed.
driver opened. This message may also be issued if a
User Response: Wait until the library is no longer in
CHECKIN or LABEL command is issued and no drive
use, and then retry the command.
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. ANR8451I 349X library library name is ready for
operations.
System Action: The attempted operation is
terminated. Explanation: The initialization process for the given
User Response: Use the QUERY DRIVE command to
ready for use.
check the online status of the drives. Drives that are
marked ″Unavailable since hh:mm yy/mm/dd″ are System Action: The library is made ready for use.
drives taken offline by the server at the time specified
because of hardware failures or the inability to open User Response: None.
the drive. If the attempted operation is a CHECKIN or
LABEL command, use the QUERY MOUNT command ANR8452E Initialization failed for 349X library
to determine if all the drives in the library are mounted library name; will retry in delay time
and wait until one of these is available. If there are minute(s).
mounted volumes with an IDLE status, use the
DISMOUNT VOLUME command to free its drive, and Explanation: The initialization process for the given
retry the original operation. library has failed. It is retried automatically after the
specified amount of time has elapsed.
ANR8448E Scratch volume volume name from library System Action: The initialization will be retried later.
library name rejected - volume name is User Response: Ensure that the library device is
already in use. powered on and ready.
Explanation: The designated volume has been used to
satisfy a scratch mount, but the volume is already ANR8453E Initialization failed for 349X library
defined in a storage pool, or has been used to store library name.
server export, database dump, or database backup
information as recorded in the server volume history Explanation: The initialization process for the given
file. library has failed and will not be retried until the next
time the server needs to access the library.
System Action: The volume is rejected.
System Action: The library is made temporarily
User Response: Use a volume that is not in use, or unavailable.
check out and relabel the rejected volume, assigning it

User Response: None. the QUERY PROCESS command. The process may be
canceled with the CANCEL PROCESS command.
ANR8454E Mismatch detected between external
label (volume name from external label) and ANR8458I AUDIT LIBRARY process for library
media label (volume name from media label) library name has been canceled.
in 349X library library name.
Explanation: A background server process that has
Explanation: The external label of a volume was been working to audit the given library is canceled by
found to differ from its media label in the designated the CANCEL PROCESS command.
library.
System Action: The volume will not be accessed. server operation continues.
User Response: Remove the volume from the library User Response: None.
and ensure that it is properly labeled.
ANR8459I Auditing volume inventory for library
ANR8455E Volume volume name could not be library name.
located during audit of library library
name. Volume has been removed from
command, this message displays the status for an
the library inventory.
AUDIT LIBRARY process on the server.
Explanation: While processing an AUDIT LIBRARY
command for the given library, the server cannot find
the given volume in the library. User Response: None. The process may be canceled
System Action: The volume is removed from the
PROCESS command.
library inventory.
User Response: If the volume is needed, it should be
ANR8460E AUDIT LIBRARY process for library
located and checked into the library using the
library name failed.
CHECKIN LIBVOLUME command.
Explanation: The background process for an AUDIT
LIBRARY command has failed.
ANR8456E Multiple volumes named volume name
were found during audit of library System Action: The background process ends.
library name.
Explanation: While processing an AUDIT LIBRARY devices associated with this command are powered on
command for the given library, multiple physical and ready, then reissue the command.
volumes are found to have the same name.
System Action: The first instance of the volume is ANR8461I AUDIT LIBRARY process for library
retained in the server inventory; all other instances are library name completed successfully.
ignored.
Explanation: The background process for an AUDIT
User Response: Remove all of the redundant instances LIBRARY command has completed successfully.
of the volume from the library. If the volume which the
server retained is found to be the incorrect one, it can System Action: The library inventory is updated to
be checked out with the CHECKOUT LIBVOLUME match the contents of the library as found during the
command; then the correct instance can be checked into audit operation.
the library with a CHECKIN LIBVOLUME command. User Response: None.
ANR8457I Command: Operation for library library ANR8462I End-of-side reached for device type
name started as process process ID. volume volume name.
Explanation: A library audit process has been started Explanation: The server has detected an end-of-side
for the given library. The process is assigned the ID condition for the given two sided volume.
specified in the message.
System Action: The server will access the second side
System Action: The server starts a background of the volume.
process to perform the operation in response to the
AUDIT LIBRARY command entered by an User Response: None.
administrator.

ANR8463E Device type volume volume name is write ANR8467I Drive drive name in library library name
protected. updated.
Explanation: The server has detected a write-protect Explanation: An UPDATE DRIVE request has been
condition for the given volume. successfully processed for the given drive.
System Action: The server will dismount the volume System Action: The server updates its information
and continue processing with another volume. about the drive.
User Response: Adjust the write-protect switch on the User Response: None.
volume so that writing is allowed. If the volume is an
optical volume and the write-protect switch is already
ANR8468I device type volume volume name
set to allow writing, use the MOVE DATA command to
dismounted from drive drive name in
move the data off of the volume. Rewritable volumes
may be reformatted and reused after the data is moved
to another volume. Explanation: The specified volume has been
dismounted from the given drive.
ANR8464E command: Invalid update request for System Action: None.
User Response: If the type of the given library is
Explanation: An invalid update request has been MANUAL, the operator may elect to remove the
made for the given library. This can occur if a new volume (which has already been ejected) from the drive
device name is given and the characteristics of the and store it in an appropriate location. For automated
device do not match the characteristics of the original libraries, this message is purely informational.
device.
System Action: The server does not process the ANR8469E Dismount of device type volume volume
command. name from drive drive name in library
library name failed.
User Response: If a different type of library device
has been installed, the old library definition must be Explanation: An attempt to dismount the designated
deleted with a DELETE LIBRARY command, and a volume failed due to an I/O error.
new library must be defined. The UPDATE LIBRARY
command cannot be used in this case. System Action: None.
User Response: If the type of the given library is
ANR8465I Library library name updated. MANUAL, the volume can be manually ejected and
removed from the drive. For automated libraries,
Explanation: An UPDATE LIBRARY request has been manual intervention may be required to correct the
successfully processed for the given library. problem.
System Action: The server updates its information
about the library. ANR8470W Initialization failure on drive drive name
in library library name.
Explanation: The specified drive could not be
initialized at this time.
ANR8466E command: Invalid update request for
drive drive name in library library name. System Action: The initialization of the specified
library continues.
Explanation: An invalid update request has been
made for the given drive. This can occur if a new User Response: Examine previous messages for
device name is given and the characteristics of the additional information regarding the specified drive.
device do not match the characteristics of the original
device.
ANR8471E Server no longer polling drive drive name
System Action: The server does not process the in library library name - path path will be
command. marked off-line.
User Response: If a different type of drive has been Explanation: The server is unable to use the
installed, the old drive definition must be deleted with mentioned drive via the specified path. This may be for
a DELETE DRIVE operation, and a new drive must be the following reasons:
defined. The UPDATE DRIVE command cannot be v The drive cannot be opened
used in this case.
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 User Response: Delete all paths to this library, and
application, or may be loaded with a cartridge not reissue the command.
labeled for server use.
System Action: The path to the drive is offline and is ANR8475I Dismount of volume volume name failed.
not used for tape operations. It may still be in the drive.
User Response: Determine the reason the path to the Explanation: The specified volume could not be
drive is inaccessible, such as hardware errors reported dismounted. TSM encountered an error trying to
in the system logs. Render any needed corrections to dismount the volume. If the volume is a storage pool
the hardware. Then the path may be made online by by volume, TSM already attempted to make it unavailable.
issuing the UPDATE PATH command with the Review the output of the QUERY VOLUME F=D
ONLINE=YES option. command for storage pool volumes. Review the output
of the QUERY VOLHISTORY command for non-storage
pool volumes.
ANR8472I Error reading label of volume in drive
drive name of library library name. System Action: None.
Explanation: While processing a search-mode User Response: Review message ANR8469E in the
CHECKIN LIBVOLUME command for the designated activity log. Check if the volume is still loaded in the
library, the server finds a volume whose label cannot be drive. If the volume is not in the drive, determine
read. where the volume is located in the library.
System Action: The volume is dismounted and is not
checked into the library. ANR8476E Operation is not supported for the
libtype of library library name.
User Response: Remove the volume from the library
and ensure that it is properly labeled. After doing so, Explanation: The operation failed because the libtype
the volume can be checked into the library. of the library is not supported for the operation.
ANR8473I Volume volume name was found in
User Response: Use a different libtype such as
storage element slot element address in
MANUAL to perform the operation.
library library name. It may still be in the
drive.
ANR8477E Device type device type is incorrect for
Explanation: The specified volume was found in the
drive drive name.
storage slot of a cleaner cartridge. After it was loaded
into a drive for cleaning, TSM determined that it is not Explanation: The device type of the specified drive on
a cleaner cartridge. TSM encountered an error trying to the library client is not compatible with the device type
move the cartridge back to the storage slot of the for the same drive on the library manager.
cleaner cartridge. If the volume is a storage pool
volume, TSM already attempted to make it unavailable. System Action: The operation fails.
Review the output of the QUERY VOLUME F=D User Response: Delete the drive definition on the
command for storage pool volumes. Review the output library client, and re-define the drive specifying the
of the QUERY VOLHISTORY command for non-storage correct device. If this does not correct the problem,
pool volumes. contact your service representative for assistance.
User Response: Verify all other cleaner cartridges are ANR8493I device type volume volume name mounted
in the correct storage slots. Issue the QUERY in drive drive name in library library
LIBVOLUME command to obtain the storage slots of name.
all the cartridges currently checked into TSM. Remove Explanation: The specified volume has been mounted
the cartridge in the storage slot identified in the in the specified drive.
ANR8911W message. Remove the specified volume
from the drive. Issue an AUDIT LIBRARY command System Action: None.
against the library. User Response: For automated libraries, this message
is purely informational.
ANR8474E Command: One or more paths are still
defined to library library name.
because there are still paths defined to it.

ANR8494E • ANR8550E (HP-UX)
ANR8494E Command: An option specified is not ANR8498E Drive not defined for library library in
valid for library type libraries. device configuration information file.
Explanation: A requested option is not valid for Explanation: The specified command requires that the
libraries of the given type for the specified command. 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
User Response: None. wrong order.
User Response: Refresh your device configuration
be written by BACKUP DB operation.
information file by issuing the BACKUP DEVCONFIG
Explanation: The specified volume already exists or command. Make sure a drive is defined for the library
contains data, so that the server cannot allow new associated with the device class. Reissue the command.
BACKUP DB data to be written to it. Or there is no
space available on the destination filespace to write this
ANR8499I Command accepted.
backup to.
Explanation: The command is accepted and processed
by the server.
overwritten by the requested BACKUP DB command, System Action: The server processes the command.
or that there is not enough space available.
ANR8500E No paths are defined for library library
BACKUP DB command.
name in device configuration
information file.
ANR8496E Device class device class not defined in
Explanation: The specified command requires that a
device configuration information file.
path be defined in the device configuration information
Explanation: The command that has been issued file for a drive in the specified library. This definition
requires that the specified device class be defined in the was not found, or the statements in the file are in the
device configuration information file. This definition wrong order.
was not found or the statements in the file are in the
wrong order.
User Response: Reissue the command, and specify a command. Make sure a path is defined for the library
valid device class. Refresh your device configuration associated with the device class. Reissue the command.
command.
ANR8550E Error opening filespec.
Explanation: An error occurs while attempting an
ANR8497E Library library not defined in device
open operation.
configuration information file.
specified library be defined in the device configuration User Response: Refer to the other displayed messages
information file. This definition was not found or the to determine why the open operation failed; correct the
statements in the file are in the wrong order. problem and restart the process.
ANR8550E (HP-UX) Error opening file name.
information file by issuing the BACKUP DEVCONFIG Explanation: An error occurs while the server
command. Make sure a library is defined for the device attempts a file open operation.
class. Reissue the command.
to determine why the open operation failed. Correct the
problem and restart the process.

ANR8550E (Solaris) • ANR8553E
ANR8550E (Solaris) Error opening file name.
to determine why the write operation has failed.
Explanation: An error occurs while the server Correct the problem and restart the process.
attempts a file open operation.
System Action: Server processing continues. ANR8552E An error (error code) occurred during a
read operation.
to determine why the open operation failed. Correct the Explanation: An error occurs while attempting a read
problem and restart the process. operation.
ANR8550E (Windows NT) Error opening filespec.
Explanation: The server detects an error while to determine why the read operation failed; correct the
attempting an open operation. problem and restart the process.
ANR8552E (HP-UX) An error (error code) occurred
to determine why the open operation has failed.
Correct the problem and restart the process. Explanation: An error occurs while the server
attempts a read operation.
ANR8551E An error (error code) occurred during a System Action: Server processing continues.
write operation.
Explanation: An error occurs while attempting a write to determine why the read operation failed. Correct the
operation. problem and restart the process.
ANR8552E (Solaris) An error (error code) occurred
to determine why the write operation failed; correct the
problem and restart the process. Explanation: An error occurs while the server
attempts a read operation.
ANR8551E (HP-UX) An error (error code) occurred System Action: Server processing continues.
Explanation: An error occurs while the server to determine why the read operation failed. Correct the
attempts a write operation. problem and restart the process.
ANR8552E (Windows NT) An error (error code)
occurred during a read operation.
the problem and restart the process. Explanation: The server detects an error while
attempting a read operation.
ANR8551E (Solaris) An error (error code) occurred System Action: Server processing continues.
Explanation: An error occurs while the server to determine why the read operation has failed. Correct
attempts a write operation. the problem and restart the process.
be overwritten by DUMPDB operation.
the problem and restart the process. Explanation: The specified volume already exists or
DUMPDB data to be written to it.
ANR8551E (Windows NT) An error (error code)
occurred during a write operation. System Action: The server has detected that the given
overwritten by the requested DUMPDB operation.
attempting a write operation.

ANR8553E (HP-UX) • ANR8570E (Solaris)
contain any valuable data, delete it and retry the writes to or reads from a file.
DUMPDB operation.
to determine why the device class is not defined.
ANR8553E (HP-UX) Device type volume volume name Correct the problem and restart the command if you do
cannot be overwritten by DUMPDB not wish to write to or read from a file.
operation.
Explanation: The specified volume already exists or ANR8554W (HP-UX) Dump/load command: Device
contains data, so that the server cannot allow new class device class name not defined.
DUMPDB data to be written to it. Devtype of FILE is assumed.
System Action: The server has detected that the given Explanation: The specified device class name is not
volume already contains data that would be defined with the DUMPLOADDB DEVCLASS option,
overwritten by the requested DUMPDB operation. to the server in the server options file or the server is
not able to define the specified device class.
contain any valuable data, delete it and retry the System Action: Processing continues. The dump/load
DUMPDB operation, or specify a different volume process assumes the device class is devtype=FILE and
name. writes to or reads from a file.
ANR8553E (Solaris) Device type volume volume name to determine why the device class is not defined.
cannot be overwritten by DUMPDB Correct the problem and restart the command if you do
operation. not wish to write to or read from a file.
contains data, so that the server cannot allow new ANR8554W (Solaris) Dump/load command: Device
DUMPDB data to be written to it. class device class name not defined.
Devtype of FILE is assumed.
System Action: The server has detected that the given
volume already contains data that would be Explanation: The specified device class name is not
overwritten by the requested DUMPDB operation. defined with the DUMPLOADDB DEVCLASS option,
to the server in the server options file or the server is
DUMPDB operation, or specify a different volume System Action: Processing continues. The dump/load
name. process assumes the device class is devtype=FILE and
writes to or reads from a file.
ANR8553E (Windows NT) Device type volume volume User Response: Refer to the other displayed messages
name cannot be overwritten by to determine why the device class is not defined.
DUMPDB operation. Correct the problem and restart the command if you do
not wish to write to or read from a file.
DUMPDB data to be written to it. ANR8570E (HP-UX) HTTPS Initialization failed. No
keyring file or keyring password were
specified.
overwritten by the requested DUMPDB operation. Explanation: HTTPS required keyring file and keyring
password are not found.
contain any valuable data, delete it and retry the System Action: The HTTPS COMMMethod is not
DUMPDB operation. initialized.
User Response: Ensure server has access to keyring
ANR8554W Dump/load command: Device class device file and password. Re-start the server.
class name not defined. Devtype of FILE
is assumed.
ANR8570E (Solaris) HTTPS Initialization failed. No
Explanation: The specified device class name is not keyring file or keyring password were
defined with the DUMPLOADDB DEVCLASS option, specified.
to the server in the server options file or the server is
Explanation: HTTPS required keyring file and keyring
System Action: Processing continues. The dump/load
process assumes the device class is devtype=FILE and

ANR8570E (Windows NT) • ANR8573E (Windows NT)
System Action: The HTTPS COMMMethod is not keyring file. Then re-start the server.
initialized.
User Response: Ensure server has access to keyring ANR8572E (Solaris) HTTPS Initialization failed. The
file and password. Re-start the server. keyring file password is invalid.
Explanation: An invalid password was specified for
ANR8570E (Windows NT) HTTPS Initialization the HTTPS keyring file.
failed. No keyring file or keyring
System Action: The HTTPS COMMMethod is not
password were specified.
initialized.
Explanation: HTTPS required keyring file and keyring
User Response: Obtain the correct password for the
keyring file. Then re-start the server.
initialized.
ANR8572E (Windows NT) HTTPS Initialization
User Response: Ensure server has access to keyring failed. The keyring file password is
file and password. Re-start the server. invalid.
Explanation: An invalid password was specified for
ANR8571E (HP-UX) HTTPS Initialization failed. The the HTTPS keyring file.
keyring file format is invalid.
Explanation: HTTPS required keyring file has an initialized.
invalid format.
System Action: The HTTPS COMMMethod is not keyring file. Then re-start the server.
initialized.
User Response: Keyring file may be corrupted. Obtain ANR8573E (HP-UX) HTTPS Initialization failed. I/O
new copy of the keyring file, then re-start the server. error occurred reading the keyring file.
Explanation: An unknown I/O error occurred reading
ANR8571E (Solaris) HTTPS Initialization failed. The the keyring file.
keyring file format is invalid.
Explanation: HTTPS required keyring file has an initialized.
invalid format.
User Response: Keyring file may be corrupted. Obtain
System Action: The HTTPS COMMMethod is not new copy of the keyring file, then re-start the server.
initialized.
User Response: Keyring file may be corrupted. Obtain ANR8573E (Solaris) HTTPS Initialization failed. I/O
new copy of the keyring file, then re-start the server. error occurred reading the keyring file.
ANR8571E (Windows NT) HTTPS Initialization the keyring file.
failed. The keyring file format is
invalid.
initialized.
Explanation: HTTPS required keyring file has an
invalid format.
new copy of the keyring file, then re-start the server.
initialized.
User Response: Keyring file may be corrupted. Obtain failed. I/O error occurred reading the
new copy of the keyring file, then re-start the server. keyring file.
ANR8572E (HP-UX) HTTPS Initialization failed. The the keyring file.
keyring file password is invalid.
Explanation: An invalid password was specified for initialized.
the HTTPS keyring file.
System Action: The HTTPS COMMMethod is not new copy of the keyring file, then re-start the server.
initialized.

ANR8574E (HP-UX) • ANR8675E
ANR8574E (HP-UX) HTTPS Initialization failed. ANR8575E (Windows NT) HTTPS Initialization
Could not open the the keyring file. failed. The specified certificate within
the keyring file has expired.
Explanation: The keyring file could not be found or
did not allow access. Explanation: The default or specified certificate within
initialized. System Action: The HTTPS COMMMethod is not
initialized.
User Response: Ensure the keyring file is present and
has read access allowed. Then re-start the server. User Response: The certificate must be renewed and
re-instated into the keyring file. Then re-start the server.
ANR8574E (Solaris) HTTPS Initialization failed.
Could not open the the keyring file. ANR8576E (HP-UX) HTTPS Initialization failed. The
specified cert within the keyring file has
as an invalid distinguished name.
did not allow access.
Explanation: The distinguished name for the specified
cert is invalid.
initialized.
initialized.
has read access allowed. Then re-start the server.
User Response: Ensure the correct keyring has been
specified and that the keyring contains the correct
distinguished name. Then re-start the server.
failed. Could not open the the keyring
file.
ANR8576E (Solaris) HTTPS Initialization failed. The
specified cert within the keyring file has
did not allow access.
as an invalid distinguished name.
Explanation: The distinguished name for the specified
initialized.
cert is invalid.
has read access allowed. Then re-start the server.
initialized.
ANR8575E (HP-UX) HTTPS Initialization failed. The
specified certificate within the keyring
distinguished name. Then re-start the server.
file has expired.
Explanation: The default or specified certificate within
failed. The specified cert within the
System Action: The HTTPS COMMMethod is not keyring file has as an invalid
initialized. distinguished name.
User Response: The certificate must be renewed and Explanation: The distinguished name for the specified
re-instated into the keyring file. Then re-start the server. cert is invalid.
ANR8575E (Solaris) HTTPS Initialization failed. The initialized.
specified certificate within the keyring
file has expired.
Explanation: The default or specified certificate within distinguished name. Then re-start the server.
System Action: The HTTPS COMMMethod is not ANR8675E File name with environment variable
initialized. DSMSERV_DIR: File already exists for
File or Filetext Exit.
User Response: The certificate must be renewed and
re-instated into the keyring file. Then re-start the server. Explanation: The specified file already exists and the
file-exit option was set to PRESERVE.
System Action: Server continues running.

ANR8675E (HP-UX) • ANR8677E (Solaris)
User Response: Specify a non-existent file.
ANR8677E User specified module, with environment
variable DSMSERV_DIR: Cannot load into
ANR8675E (HP-UX) File name with environment variable server, system errno = Error number
DSMSERV_DIR: File already exists for generated by AIX.
File or FileText Exit.
Explanation: The server was unable to load the
Explanation: The specified file already exists and the module specified. The module is not a properly
file-exit option was set to PRESERVE. C-compiled and linked dynamic module.
System Action: Server continues running. System Action: Server initialization stops or server
continues running if already up.
User Response: Specify a non-existent file.
User Response: Use the server supplied sample
makefile and export files to compile-link the user-exit
ANR8675E (S/390) File name: File already exists for module. Make sure the export.ref file contains the
File Exit. server-defined function name, and the module actually
Explanation: The specified file already exists and the contains the server-defined function name, with one
file-exit option was set to PRESERVE. void parameter declared.

ANR8677E (HP-UX) User specified module, with
User Response: Specify a non-existent file. environment variable DSMSERV_DIR:
Cannot load into server, system errno =
ANR8675E (Solaris) File name with environment variable Error number generated by HP-UX.
DSMSERV_DIR: File already exists for Explanation: The server was unable to load the
File/FileText Exit, overwrite option not module specified. The module is not a properly
set to YES. C-compiled and linked dynamic module.
Explanation: The specified file already exists and the System Action: Server initialization stops or server
overwrite option was not set to Yes. continues running if already up.
System Action: Server continues running. User Response: Use the server supplied sample
User Response: Specify another file or set the makefile and export files to compile-link the user-exit
overwrite option to YES in the server options file. module. Make sure the export.ref file contains the
server-defined function name, and the module actually
contains the server-defined function name, with one
ANR8675E (Windows NT) File name with path within void parameter declared.
registry.: File already exists for File or
FileText Exit.
ANR8677E (S/390) The user-exit module loaded does
Explanation: The specified file already exists and the not match with type specified in options
File/FileText exit option was set to PRESERVE. file.
System Action: Server continues running. Explanation: The server was able to load a module,
User Response: Specify a non-existent file. but the type of the module did not match the type
specified in the server options file
ANR8676E (S/390) User specified module: Cannot load System Action: Server initialization stops or server
into server, system errno = Error number continues running if already up. The module is
generated by MVS. unloaded.
Explanation: The server was unable to load the User Response: Check the user-exit module
module specified. The module is not a properly compilation type. Make sure it matches with what is
C-compiled/linked dynamic module or an specified in the options file. Only C, Assembler, and
ASSEMBLER/PLI compiled module. PLI compiled modules are supported.

ANR8677E (Solaris) User specified module, with
User Response: Use the server supplied sample environment variable DSMSERV_DIR:
user-exit files as a starting point. Cannot load into server, system errno =
Error number generated by Solaris.
module specified. The module is not a properly
C-compiled and linked dynamic module.

ANR8677E (Windows NT) • ANR8679W (HP-UX)
ANR8678E (Solaris) Cannot bind User specified module,
User Response: Use the server supplied sample with environment variable DSMSERV_DIR
makefile, c, and h files to generate the user-exit into server, system errno = Error number
module. Make sure the module contains server-defined generated by Solaris.
function name adsmV3UserExit, and the module
Explanation: The server was unable to bind with the
actually contains the server-defined function name,
module specified. The server could not find a function
with one void * parameter declared, and returns void.
named adsmV3UserExit in the module.
ANR8677E (Windows NT) User specified module, with
path within registry: Cannot load into User Response: Use the server supplied sample
server, system errno = Error number makefile, c and header files to create the user exit
generated by NT. module. Make sure the shared library module contains
a function named adsmV3UserExit of type void, with
one parameter of a void *.
module specified. The module is not a properly
C-compiled and linked dynamic module.
ANR8678E (Windows NT) Cannot find/set User
specified function name within DLL. in User
User Response: Use the server supplied sample specified DLL library name, with registry
makefile compile-link the user-exit module. path, system errno = Error number
generated by NT.
ANR8678E Cannot bind User specified module, with Explanation: The server was unable to find and/or
environment variable DSMSERV_DIR into bind with the function name in the DLL specified.
server, system errno = Error number
generated by AIX.
Explanation: The server was unable to bind with the
makefile to compile-link the user-exit module. Make
module specified.
sure there is a function name in the DLL as specified in
System Action: Server initialization stops or server the server options file. Make sure the function only
continues running if already up. accepts one argument, a void pointer.

makefile and export files to compile-link the user-exit ANR8679W There is already an user-exit loaded.
module. Make sure the export.ref file contains the
Explanation: There was a previous successful load of
an user-exit module, thus server cannot load another
contains the server-defined function name, with 1 void
one.
parameter declared. The module may contain a global
variable name that conflicts with the server’s. System Action: Server initilization stops or server
ANR8678E (HP-UX) Cannot bind User specified User Response: To load a new user-exit module, halt
module, with environment variable the server and then restart the server with the new
DSMSERV_DIR into server, system errno user-exit module.
= Error number generated by HP-UX.
Explanation: The server was unable to bind with the ANR8679W (HP-UX) There is already an user-exit
module specified. loaded.
System Action: Server initialization stops or server Explanation: There was a previous successful load of
continues running if already up. an user-exit module, thus server cannot load another
one.
makefile and export files to compile-link the user-exit System Action: Server initialization stops or server
module. Make sure the export.ref file contains the continues running if already up.
User Response: To load a new user-exit module, the
contains the server-defined function name, with one
server must be halted and then restart the server with
void parameter declared. The module may contain a
the new user-exit module.
global variable name that conflicts with the server’s.

ANR8679W (Solaris) • ANR8681I (Windows NT)
ANR8679W (Solaris) Unable to unload user exit ANR8680W (Windows NT) There is already a file
module: system errno = Error number used for the file or filetext exit.
generated by Solaris.
Explanation: There was a previous file open for the
Explanation: The server was not able to unload the file or filetext exit. The server cannot open another one.
user-exit module.
User Response: To start a new file for the exit, halt
User Response: The server should be stopped at the the server, then restart the server with a new file name.
earliest possible time before the user exit is to be
reactivated.
ANR8681I Connected to Tivoli event server at node
name on port port.
ANR8679W (Windows NT) There is already an
Explanation: The server successfully established a
user-exit loaded.
connection with the Tivoli event server on the specified
Explanation: There was a previous successful load of node name and port.
an user-exit module, thus server cannot load another
System Action: The server sends events to the Tivoli
one.
event server using this connection.
User Response: To load a new user-exit module, halt
the server and then restart the server with the new
ANR8681I (HP-UX) Connected to Tivoli event server
user-exit module.
at node name on port port.
ANR8680W There is already a file used for the file
or filetext exit.
node name and port.
file or filetext exit. The server cannot open another one.
System Action: Server initialization stops or server
User Response: To start a new file for the file or
ANR8681I (S/390) Connected to Tivoli event server at
filetext exit, halt the server, then restart the server with
node name on port port.
the new file name.
ANR8680W (HP-UX) There is already a file used for
node name and port.
the file or filetext exit.
file or filetext exit. The server cannot open another one.
ANR8681I (Solaris) Connected to Tivoli event server
User Response: To start a new file for the file or
at node name on port port.
filetext exit, halt the server, then restart the server with
a new file name. Explanation: The server successfully established a
node name and port.
ANR8680W (Solaris) There is already a named file
used for the file or filetext exit. System Action: The server sends events to the Tivoli
file or filetext exit. The server cannot open another one. User Response: None.
continues running if already up. ANR8681I (Windows NT) Connected to Tivoli event
server at node name on port port.
User Response: To start a new file for the file or the
filetext exit, halt the server, then restart the server with Explanation: The server successfully established a
a new file name. connection with the Tivoli event server on the specified
node name and port.

ANR8682E • ANR8683E (S/390)
System Action: The server sends events to the Tivoli which the event server is running does not support the
event server using this connection. TCP/IP Portmapper, then ensure that TECPORT is
specified in the server options file.
ANR8682E (Windows NT) Unable to determine port

ANR8682E Unable to determine port of Tivoli event
of Tivoli event server on node name.
server on node name.
Explanation: The server was unable to determine the
TCP/IP port on which the Tivoli event server on node
name is listening.
name is listening.
System Action: Event logging to the Tivoli event
server is disabled.
server is disabled.
User Response: Ensure that the Tivoli event server is
running on the specified system. If the system on
which the event server is running does not support the
TCP/IP Portmapper, then ensure that TECPORT is
ANR8683E Unable to connect to the Tivoli event

ANR8682E (HP-UX) Unable to determine port of
server at node name on port port.
Tivoli event server on node name.
Explanation: The server was unable to establish a
TCP/IP connection with the Tivoli event server on node
name at port port.
name is listening.
server is disabled.
server is disabled.
TCP/IP Portmapper, then ensure that the value
specified for TECPORT in the server options file is
correct.
ANR8682E (S/390) Unable to determine port of Tivoli

ANR8683E (HP-UX) Unable to connect to the Tivoli
event server on node name.
event server at node name on port port.
name is listening.
name at port port.
server is disabled.
server is disabled.
correct.
ANR8682E (Solaris) Unable to determine port of
Tivoli event server on node name.
ANR8683E (S/390) Unable to connect to the Tivoli
Explanation: The server was unable to determine the event server at node name on port port.
name is listening.
System Action: Event logging to the Tivoli event name at port port.
server is disabled.
User Response: Ensure that the Tivoli event server is server is disabled.

ANR8684E (HP-UX) Unable to connect to the Tivoli
event server because TCP/IP is not
available.
specified for TECPORT in the server options file is Explanation: The server was unable to establish a
correct. TCP/IP connection with the Tivoli event server because
TCP/IP services were not available.
ANR8683E (Solaris) Unable to connect to the Tivoli System Action: Event logging to the Tivoli event
event server at node name on port port. server is disabled.
Explanation: The server was unable to establish a User Response:
TCP/IP connection with the Tivoli event server on node v Ensure that COMMMETHOD=TCPIP is specified in
name at port port. the server options file, or that
System Action: Event logging to the Tivoli event COMMMETHOD=NONE is not specified.
server is disabled. v If COMMMETHOD=TCPIP was specified, use the
BEGIN EVENTLOGGING TIVOLI command to
manually start event logging to the Tivoli event
server once server initialization has completed.
specified for TECPORT in the server options file is ANR8684E (S/390) Unable to connect to the Tivoli
correct. event server because TCP/IP is not
available.
ANR8683E (Windows NT) Unable to connect to the Explanation: The server was unable to establish a
Tivoli event server at node name on port TCP/IP connection with the Tivoli event server because
port. TCP/IP services were not available.
Explanation: The server was unable to establish a System Action: Event logging to the Tivoli event
TCP/IP connection with the Tivoli event server on node server is disabled.
name at port port.
User Response:
System Action: Event logging to the Tivoli event v Ensure that a valid value for TCPNAME is specified
server is disabled. in the server options file.
User Response: Ensure that the Tivoli event server is v If TCPNAME has the correct value, use the BEGIN
running on the specified system. If the system on EVENTLOGGING TIVOLI command to manually
which the event server is running does not support the start event logging to the Tivoli event server once the
TCP/IP Portmapper, then ensure that the value server initialization has completed.
correct.
ANR8684E (Solaris) Unable to connect to the Tivoli
event server because TCP/IP is not
ANR8684E Unable to connect to the Tivoli event available.
server because TCP/IP is not available.
Explanation: The server was unable to establish a TCP/IP connection with the Tivoli event server because
TCP/IP connection with the Tivoli event server because TCP/IP services were not available.
TCP/IP services were not available.
System Action: Event logging to the Tivoli event server is disabled.
server is disabled.
User Response:
User Response: v Ensure that COMMMETHOD=TCPIP is specified in
v Ensure that COMMMETHOD TCPIP is specified in the server options file, or that
the server options file. COMMMETHOD=NONE is not specified.
v If COMMMETHOD TCPIP was specified, use the v If COMMMETHOD=TCPIP was specified, use the
BEGIN EVENTLOGGING TIVOLI command to BEGIN EVENTLOGGING TIVOLI command to
manually start event logging to the Tivoli event manually start event logging to the Tivoli event
server once server initialization has completed. server once server initialization has completed.

ANR8684E (Windows NT) • ANR8747I
ANR8684E (Windows NT) Unable to connect to the ANR8743E This server is not licensed to support
Tivoli event server because TCP/IP is library device name. Device Support
not available. Module module number is required.
Explanation: The server was unable to establish a Explanation: Either a DEFINE LIBRARY command, a
TCP/IP connection with the Tivoli event server because volume mount operation, or library initialization cannot
TCP/IP services were not available. be processed because the server is not licensed to
support the given library.
server is disabled. System Action: The operation fails.
User Response: User Response: Contact your service representative to
v Ensure that COMMMETHOD=TCPIP is specified in update the server license terms so that support for the
the server options file, or that given library device is enabled.
COMMMETHOD=NONE is not specified.
v If COMMMETHOD=TCPIP was specified, use the ANR8744E Command: Current license terms do not
BEGIN EVENTLOGGING TIVOLI command to permit this operation.
manually start event logging to the Tivoli event
Explanation: The specified command failed because
server once server initialization has completed.
the current license terms do not permit it.
ANR8740W Number of automated library slots (slots
in use) exceeds license terms (slots User Response: Contact your service representative to
licensed). update the server license terms so that the requested
operation can be processed.
Explanation: The number of slots in use within
automated libraries exceeds the licensed value.
ANR8745E Support for the 3590 device type is
System Action: The operation completes.
disabled for library library name.
User Response: Contact your service representative to
Explanation: The requested operation fails because
update license values for slots in automated libraries,
support for the 3590 device type is not currently
or reduce the number of slots in use by issuing
enabled for the specified library.
CHECKOUT LIBVOLUME commands as necessary.
ANR8741E CHECKIN LIBVOLUME not permitted User Response: Make sure the ENABLE3590LIBRARY
with current license terms. option is specified in the server options file, and that
the scratch category number for 3590 volumes does not
Explanation: The CHECKIN LIBVOLUME operation is
conflict with the private category or the CARTRIDGE
not permitted because the current license terms do not
volume scratch category.
allow it.
ANR8746E Device type device type is not supported
User Response: Contact your service representative to in this release.
update license values for slots in automated libraries,
Explanation: The specified device type cannot be used
or reduce the number of slots in use by issuing
by this release/platform of the server.
CHECKOUT LIBVOLUME commands as necessary.
System Action: The device cannot be used.
ANR8742E This server is not licensed to support User Response: Contact your sales or service
the device type device type. Device representative to upgrade to the latest release of the
Support Module module number is server.
required.
Explanation: A DEFINE DRIVE command or a ANR8747I Checking in volume volume name in
volume mount operation cannot be processed because library library name- CANCEL
the server is not licensed to support the required device PENDING.
type.
System Action: The operation fails. command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. The
given volume was being checked in to the designated
update the server license terms so that support for the
library, but the process was canceled by an
required device type is enabled.
administrator.

System Action: The background process operation is
ANR8751W This server is not licensed to support
in a wait queue. When the process comes off the queue,
the device type device type. Managed
it will be terminated.
Library license is required.
Explanation: This message is issued when a DEFINE
DRIVE command or a volume mount operation uses a
ANR8748I Checking in volumes in search mode in device class that is not licensed on the server.
library library name- CANCEL
System Action: The operation fails if this is a
PENDING.
try-and-buy server. For purchased servers, this message
Explanation: In response to a QUERY PROCESS is to warn you that you are not in compliance with
command, this message displays the status for a registered license terms.
CHECKIN LIBVOLUME process on the server. Volumes
were being checked into the given library in search
update the server license terms so that support for the
mode, but the process was canceled by an
required device type is enabled.
administrator.
being terminated.
library device type. Managed Library
User Response: None. license is required.
Explanation: This message is issued when a DEFINE
ANR8749E Library order sequence check on library LIBRARY command or a volume mount operation uses
library name. a device class that is not licensed on the server.
Explanation: An attempt has been made to mount or System Action: The operation fails if this is a
demount a volume, but the attempt fails for one of the try-and-buy server. For purchased servers, this message
following reasons: is to warn you that you are not in compliance with
v Mount is already in progress or a volume is already registered license terms.
mounted. User Response: Contact your service representative to
v Mount is already pending. update the server license terms so that support for the
v Demount is already pending. required device type is enabled.
v Demount was requested but no volume is mounted.

System Action: The operation fails. library library name. Library Sharing is
User Response: This error usually occurs when a required.
demount fails and a cartridge is left in the drive. All Explanation: This message is issued when a DEFINE
subsequent mounts fail while attempting to insert LIBRARY command or library initialization for a
another cartridge into the same drive. Demount the library that requires library sharing and library sharing
cartridge using the library manager or perform an is not licensed on the server.
AUDIT LIBRARY operation on the designated library.
Retry the operation. 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
ANR8750E Volume is incompatible with specified registered license terms.
device type in library library name.
Explanation: An attempt has been made to mount or update the server license terms so that support for the
check in a volume, but the attempt fails because the required device type is enabled.
cartridge being mounted is not compatible with the
drive (For example, attempting to mount a 3590
cartridge on a 3490 drive). ANR8754E Command: There is already a request to
delete library libary name.
User Response: Ensure the DEVTYPE parameter on or updated because there is a request to delete the
the CHECKIN command matches the device type of library already.
the drive. Retry the operation.

ANR8755E Command: There is already a request to ANR8764E Command: Volume volume name not
update library library name. processed: the operation is not allowed
for library type library type.
because there is a request to update the library already. Explanation: The indicated volume is not processed
since the requested operation is not allowed for
libraries of the given type.
ANR8760I Cancel in progress.
Explanation: The MOVE MEDIA command has been
ANR8765I Request number: device type volume volume
canceled and will end when resources have been freed
name in location location name is required
for the background process. This message may be
for use in library library name; CHECKIN
LIBVOLUME required within time limit
for a MOVE MEDIA command.
minutes.
Explanation: A mount request has been made for a
User Response: None. 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
Explanation: The MOVE MEDIA command has the volume has been checked into the library, or the
processed the number of volumes displayed. This time limit expires.
message may be displayed in response to a QUERY
PROCESS command for a MOVE MEDIA command. User Response: Obtain the required volume from the
indicated location, and insert it into the library by
System Action: Server operation continues. issuing a CHECKIN LIBVOLUME command. Use the
User Response: None. 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
ANR8762I Number of volumes processed: number. swapped out in order to make room for the required
Ejecting volume volume name from volume.
Explanation: The MOVE MEDIA command displays ANR8766I MOVE MEDIA command: CHECKOUT
the number of volumes already processed and the LIBVOLUME command for volume volume
name of the volume currently being ejected from the name in library library name completed
indicated library. This message may be displayed in successfully; Place the ejected volume in
response to a QUERY PROCESS command for a MOVE location location name.
MEDIA command.
Explanation: The CHECKOUT LIBVOLUME operation
System Action: Server operation continues. has completed successfully for the indicated volume in
User Response: None. the given library. Place the ejected volume in the
indicated location.
ANR8763E Command: Volume volume name not System Action: The volume is either deleted from the
processed: library library name not library inventory (if its status is something other than
defined. DATA) or marked not present (if its status is DATA).
Explanation: The indicated volume is not processed User Response: If an *UNKNOWN* location is
since the designated library has not been defined or has displayed, issue UPDATE STGPOOL OVFLOCATION
been deleted. command to define an overflow location name to be
used on the subsequent MOVE MEDIA command. For
System Action: The volume is not processed. the volumes ejected with an *UNKNOWN* location,
User Response: Reissue the command using a use UPDATE VOLUME LOCATION command to
different library name, or define the library before update its location to your overflow location name.

ANR8767I Number of volumes processed: number ANR8772I Moving volume volume name (if known)
volumes processed. Volumes sent to library from drive drive name to slot slot element
library name for checkout: number volumes number in library library name.
sent.
Explanation: A volume found in the drive during
Explanation: The MOVE MEDIA command has library initialization is being moved to the slot.
processed the number of volumes shown. Currently, the
System Action: The volume is moved from the drive
MOVE MEDIA command has sent for processing the
to the slot.
number of volumes shown to the library shown. This
message may be displayed in response to a QUERY User Response: None.
PROCESS command for a MOVE MEDIA command.
System Action: Server operation continues. ANR8773E Incompatible options
CHECKLABEL=NO and SEARCH=YES
for SCSI libraries.
Explanation: If a barcode reader is not installed and
ANR8769E External media management function
detected by the server, the server requires the ability to
request type returned result=result.
check the tape label when searching for new volumes
Explanation: A request of the indicated function type in a SCSI tape library. The CHECKLABEL=NO and
was sent to the external library manager program, SEARCH=YES parameters on the CHECKIN LIBVOL
which returned a result code which was not SUCCESS. command are not compatible.
System Action: The server continues, but the server System Action: The command fails.
operation that was being attempted fails.
User Response: Reissue the CHECKIN LIBVOL
User Response: Consult the documentation for the command and specify CHECKLABEL=YES.
external media management program to determine how
to recover from the error condition. Then attempt the
ANR8774W Volume volume name not checked into
server operation again.
library library name but is using category
category number.
ANR8770W Unable to load external library manager
Explanation: While processing a DEFINE LIBRARY or
filespec.
AUDIT LIBRARY command for the given library, the
Explanation: A library of LIBTYPE=EXTERNAL is server found a volume that was not checked into the
defined but the server cannot load the external library library (with the CHECKIN LIBVOL command), but is
manager. assigned to one of the categories in use by that library.
System Action: The server continues, but the external System Action: If the volume category equals the
library cannot be accessed. value of the library SCRATCHCAT the category is
changed to the value of the library PRIVATECAT. This
User Response: Verify that the
is to prevent the library from loading the volume when
EXTERNALMANAGER parameter for the external
a scratch volume is requested.
library is specified correctly on the DEFINE LIBRARY
or UPDATE LIBRARY command. 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
ANR8771E Volume volume name in library library
command. If the volume is not to be used by the
name is deleted. External Library is not
server, use the mtlib program to reassign the volume to
synchronized with the server. Audit
its correct category. For details about the mtlib
required.
program, refer to the documentation provided with the
Explanation: The server deleted a volume from its library device.
inventory, and its attempt to inform the external library
manager has failed.
ANR8775I Drive drive name unavailable at library
System Action: The server may continue to access the manager.
library, but some volumes may not be accessible until
Explanation: The specified drive availability status at
the external library is synchronized with the server.
the library manager has changed from available to
User Response: Perform the appropriate type of unavailable.
processing on the external library in order to
System Action: The drive status on the server is
synchronize it with the server.
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.

ANR8778W Scratch volume volume name changed to
determine the cause of the drive becoming unavailable.
Private Status to prevent re-access.
Once the service representative has determined the
cause and changed the availability status to available at Explanation: The scratch volume encountered an error
the library manager, the server will resume use of the during mount processing that makes it unusable. The
drive. 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
ANR8776W Volume volume name in drive drive name
pool.)
contains lost VCR data; performance
may be degraded. System Action: Processing continues with another
scratch volume.
Explanation: The Vital Cartridge Records of the
cartridge in the drive are lost or corrupted. This results User Response: See previous error messages to
in the inability of the drive to do fast locates to file determine the cause of the mount failure, and correct
positions on the cartridge, which causes the locate the problem. If the problem is a mislabeled volume or
performance for read or append operations to become unreadable label, relabel the scratch volume using the
degraded. dsmlabel utility with the ″-overwrite″ option. If the
volume is missing from its home slot, issue the AUDIT
System Action: The server continues the operation.
LIBRARY command against the library. If the volume
User Response: There are two methods to restore the has lost or corrupted VCR-data, relabel the volume.
VCR data. The first method uses the MOVE DATA (This reinitializes the VCR-data by writing to the
command to move the data off the tape and to return volume from beginning-of-tape.) Once the problem is
the tape to scratch or empty status. The VCR data is corrected, update the status of the volume to scratch by
rebuilt when the empty tape is rewritten from the using the UPDATE LIBVOL command.
beginning-of-tape. The second method rebuilds the
VCR by loading the tape and locating directly to the
ANR8779E Unable to open drive drive name, error
end-of-data. This is done by the server in normal use
number=errno value from open system call.
when new data is appended to the end of the tape. It
can also be done independent of the server by loading Explanation: The drive cannot be opened by the
the tape in an unused drive and using the tapeutil server. In AIX, error number is the value of errno
program. Select the tapeutil option ″Space to returned by the operating system. In OS/2, it is the
End-of-Data″. value of the return code from the call to DosOpen.
System Action: The transaction needing the drive
ANR8777E Mount for volume volume name failed; fails.
media performance is degraded.
User Response: Use the error number in conjunction
Explanation: The VCR data on the volume is lost or with operating system documentation to narrow the
corrupted, resulting in degraded tape positioning. The scope of the cause. Inspect the drive. Ensure the drive
mount fails because the tape drive was configured to is powered on and ready, the cables are properly
fail mounts that indicate this condition. connected and terminated, and that the device is
properly configured to the operating system.
System Action: The client command fails and the
transaction is rolled back.
ANR8780E Volume in drive drive name has no label.
User Response: Until the VCR data can be restored,
the user can issue the UPDATE VOLUME command to Explanation: The volume in the indicated drive does
make the volume unavailable. There are two methods not have a label. The server requires that all media be
to restore the VCR data. The first method uses the uniquely labelled.
MOVE DATA command to move the data off the tape
System Action: The volume is rejected and the server
and to return the tape to scratch or empty status. The
prompts for a new volume.
VCR data is rebuilt when the empty tape is rewritten
from the beginning-of-tape. The second method User Response: Use the appropriate labelling utility to
rebuilds the VCR by loading the tape and locating label the media. In OS/2 and Windows NT, the LABEL
directly to the end-of-data. This is done by the server in command is used to label removable disk cartridges,
normal use whenever data is appended to the end of diskettes and other media which appear as drive
the tape. It can also be done independent of the server letters.
by loading the tape in an unused drive and using the
tapeutil program. Select the tapeutil option ″Space to
End-of-Data″.

and is properly formatted. Ensure that there are not
ANR8781E Volume in drive drive name has invalid
large numbers of files already in the root of the file
label label.
system. Some file systems have limits on the number of
Explanation: The volume in the indicated drive has files that may be created in the root directory.
the label shown. The name does not conform with
server requirements. The server requires that all media
ANR8785E Out-of-space in file system for device
be uniquely labelled and, for removable media, that the
type volume volume name.
label with file naming conventions. The label found
exceeded the maximum label size for removable media Explanation: The server detected an out-of-space
or did not conform to server labelling requirements. If condition for the file system in which the given volume
????? is shown for the label, it indicates that server was resides.
unable to read the label.
User Response: The file system must be expanded to
User Response: Use the appropriate labelling utility to accommodate volume growth.
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 ANR8786I Request number: Remove device type
letters. This label must still conform to server volume from entry/exit port; insert
requirements. volume volume name mount mode into
entry/exit port of library library name
within time limit minute(s); issue
ANR8782E Volume volume name could not be ’REPLY’ along with the request ID when
accessed by library library name. ready.
Explanation: The designated volume is in the Explanation: A CHECKIN LIBVOLUME command is
inventory of the Library Manager, but the physical in progress, and the specified volume is needed.
location is either inaccessible or unknown. However, there is a volume awaiting to be removed
from the entry/exit port before the specified volume is
System Action: The operation fails. The access mode
inserted into the port of the given library.
of the volume is changed to UNAVAILABLE.
User Response: Ensure that the cartridge is physically
command is issued.
in the library, and reinventory the library. If the volume
location is resolved, restore the access mode of the User Response: Remove the volume from the library
volume to its previous value using the UPDATE and insert the correct volume into the entry/exit port.
VOLUME command. Issue a REPLY command, along with the request ID, to
tell the server that the volume has been removed and a
new volume has been inserted.
ANR8783E Label on volume in drive drive name
could not be read.
ANR8787W Unable to read the barcode label(s) in
Explanation: The server was unable to read the label
on the indicated drive.
Explanation: A command is issued with the
CHECKLABEL=BARCODE option. The library is
User Response: Use the appropriate labelling utility to unable to detect that the cartridges have valid barcode
label the media. In OS/2 and Windows NT, the LABEL labels. The barcode reader is disabled or it is unable to
command is used to label removable disk cartridges, read the labels.
diskettes and other media which appear as drive
System Action: Unless the command is checking in
letters. This label must still conform to server
cleaning cartridges, the process continues by loading
requirements.
the cartridges into the library’s drives and reading the
label from the tape. Cleaning cartridges have no
ANR8784E File file name on volume drive name could internal label that can be checked by loading it in the
not be created. drive.
Explanation: The server was unable to create the User Response: Cancel the process if you do not want
indicated file on the indicated volume. The server to load all of the cartridges into the library’s drives.
creates a file on removable media in which to store Examine the cartridges to ensure they have barcode
data. 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
User Response: Ensure that the media is not defective, functioning properly, if necessary.

User Response: Service the drive for failures. Delete
ANR8788W Unable to read the barcode of cartridge
and redefine the drive to bring it back online.
in slot-id Element number of slot in library
library name; loading in drive to read
label. ANR8793E Dynamic drive recovery failed for device
type volume volume name because not
Explanation: The library barcode reader is unable to
enough drives are available.
read the label of a tape cartridge. The cartridge is
found in the slot with the given element number. Explanation: To recover a volume on another drive,
there must be at least one other drive available that is
System Action: The cartridge is loaded into a drive
not associated with the transaction which is driving the
and its label will be read from the tape.
recovery. In addition, the maximum number of drives
User Response: Cancel the process if you do not want that can have dynamic drive recovery performed at the
to load any cartridges into the library’s drives. Examine same time is one less than the number of drives. This is
the cartridge to ensure it has a barcode label and that it to prevent deadlock from occurring between two
is compatible with the barcode reader. Not all vendors’ recovering transactions. One of these criteria has failed.
labels are readable by all libraries. Check that the
System Action: No DDR is performed and the
barcode reader is configured and is functioning
transaction fails.
properly, if necessary.
User Response: Restart the transaction.
ANR8789W Dynamic drive recovery being attempted
on device type volume volume name due to ANR8794E Retry of operation name operation failed
errors. for device type volume volume name.
Explanation: Due to a drive or media fault, the server Explanation: After successfully mounting the volume
is moving the volume to a new drive. on another drive, due to an I/O error, the original
operation fails when retried.
System Action: Read or write operations resume on
the volume once it is remounted. System Action: No further recovery is performed and
the transaction fails.
User Response: Restart the transaction.
ANR8790I device type volume volume name
re-mounted in drive drive name. ANR8795I Retry of operation name operation for
device type volume volume name is
Explanation: Due to a drive or media fault, the server
successful.
has moved the volume to the specified drive. Read or
write operations resume on the volume. Explanation: After mounting the volume on another
drive, due to an I/O error, the operation is tried
System Action: The label of the volume has been
successfully.
verified.
System Action: The transaction continues from the
point of interruption from the failure.
ANR8791E Unable to move device type volume
volume name to another drive.
ANR8796W Drive drive name of library library name is
Explanation: Dynamic drive recovery was being
not online; UPDATE DRIVE required.
attempted on the volume, but was unable to move the
volume to another drive. Explanation: During the initialization of a library, the
server finds that the drive was updated to be offline.
System Action: The originating process terminates.
System Action: The drive will not be accessible by the
User Response: See previous error messages to
library during tape operations.
determine the cause of the DDR failure, and correct the
problem. If the problem is an unreadable label, any User Response: The drive may be made online by
data on the volume may be lost. issuing the UPDATE DRIVE command with the
ONLINE=YES option.
ANR8792E Unrecoverable drive failures on drive
drive name; drive is now taken offline.
Explanation: The drive has been determined to be
faulty because of recurrent failures.
System Action: The drive is now marked offline.

ANR8797W command: Drive drive name of library ANR8800I LABEL LIBVOLUME for volume volume
library name is inaccessible. name in library library name completed
successfully.
Explanation: The server is unable to use the
mentioned drive. This may be for the following Explanation: The background process to LABEL a
reasons: volume has succeeded.
v The drive cannot be opened. System Action: The volume’s label has been rewritten.
v In the case of a 3494 or a library that can be
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 ANR8801I LABEL LIBVOLUME process process Id
labeled for server use. for library library name completed; count
of labelled volumes volume(s) labelled,
System Action: The drive is temporarily made offline
count of checked in volumes volume(s)
and is not used for tape operations. The server polls
checked-in.
the drive at one-half minute intervals to check if the
condition has cleared. Once the drives is accessible Explanation: A search-mode process to LABEL
again, the drive is brought online. volumes has succeeded.
User Response: Determine the reason the drive is System Action: The volumes have been labelled.
inaccessible, such as hardware errors reported in the
system logs. Render any needed corrections to the User Response: None.
drive. The drive will be brought online automatically
when the polling process detects that is has become ANR8802E LABEL LIBVOLUME process process Id
accessible. for library library name failed.
Explanation: The Label process terminated with a
ANR8798W Drive drive name in library library name is failure.
busy; some transactions may fail.
Explanation: The drive being made offline is currently
mounted with an open tape volume. If the transaction User Response: See previous error messages to
using the volume requires subsequent tape mounts and determine the cause of the failure, and correct the
is unable to acquire a drive, the transaction will fail. problem.
System Action: If this tape volume is one of a

sequence of volumes that are required to process a ANR8803I LABEL VOLUME process process Id for
transaction, a drive must be available for each mount. library library name has been canceled;
This may be any drive in the library, but if all other count of labeled volumes volume(s) labeled,
library drives are currently busy and are still busy at count of checked in volumes volume(s)
the time the new tape must be mounted, the checked-in.
transaction will fail. Explanation: A background server process that has
User Response: If possible, make the drive online been working to label the volumes for the given library
until the transaction using it ends. If there is an idle is canceled by the CANCEL PROCESS command. The
volume on the drive, dismount the volume first. counts provided are for any volumes processed prior to
the cancel.
ANR8799I Command: Operation for library library System Action: The server process is ended and
name started as process process ID. server operation continues.
Explanation: A LABEL process has been started to User Response: None.

write the label on the specified volume in the given
library. The process is assigned the ID specified in the ANR8804I Labelling volume volume name in library
message. library name.
System Action: The server starts a background Explanation: In response to a QUERY PROCESS
process to perform the operation in response to the command, this message displays the status for a
LABEL command entered by an administrator. LABEL process on the server.
User Response: To obtain status on the process, issue System Action: The background process continues.
canceled with the CANCEL PROCESS command. User Response: None. The process may be cancelled
PROCESS command.

User Response: It is usually not necessary to re-label
ANR8805I Labelling volumes in library library
volumes. If the volume must be relabeled, that volume
name; volume count volumes(s) labelled.
must first be removed from the storage pool or volume
Explanation: In response to a QUERY PROCESS history file where it is defined.
command, this message displays the status of a LABEL
process with the SEARCH option.
ANR8809I Request number: Please provide the label
System Action: The background process continues. name for the volume in slot element slot
element number of library library name by
User Response: None. The process may be cancelled
issuing REPLY n LABEL=xxx within time
limit minutes, where n is the re quest ID
PROCESS command.
and xxx is the desired label name.
Explanation: A LABEL LIBVOLUME command is in
ANR8806E Could not write volume label volume
progress, and the name of the next volume is needed.
name on the tape in library library name.
Explanation: The Label process could not write the
command is issued.
label on the tape specified.
User Response: Issue a REPLY command, along with
System Action: For a LABEL operation with
the request ID, and the volume name for the next
SEARCH=YES, the background process continues to the
cartridge.
next volume. For an individual volume, the process
ends. The volume is not labelled and is not checked
into the library. ANR8810I Volume volume name has been labeled in
devices associated with this command are powered on Explanation: The Label process with the search option
and ready, and then reissue the command. has found and labeled a volume.
ANR8807W Could not write label volume name on
the volume in drive drive name of library
library name because volume is already
labelled existing volume name. ANR8811E Command: The LABELSOURCE
parameter is required when using
Explanation: The check in or label process could not
SEARCH with this command.
write the label on the tape specified because the
volume is already labelled. Explanation: The LABELSOURCE parameter must be
provided with the given command.
System Action: The check in process will not
overwrite volumes that are already labelled, and the System Action: The command is not processed.
label process will only overwrite volumes when
OVERWRITE=YES is specified. The volume is not User Response: Reissue the command, and provide a
labelled and cannot be checked in to the library. If valid LABELSOURCE parameter value.
SEARCH=YES, the process continues to the next
volume. For an individual volume, the process ends. ANR8812E Command: The SEARCH parameter is
User Response: Reissue the command with the correct required when using LABELSOURCE
parameters. with this command.
Explanation: When using the LABELSOURCE option
ANR8808E Could not write label label name on the with this command, the SEARCH parameter must be
volume in drive drive name of library also provided.
library name because that volume is System Action: The command is not processed.
already labeled with volume name which
is still defined in a storage pool or User Response: Reissue the command, and provide a
volume history. valid SEARCH parameter value.
Explanation: An attempt was made to overwrite the

label of a volume that is still defined to a storage pool ANR8813W Unable to read the barcode of cartridge
or is still found in the volume history file. Such a in slot element Element number of slot in
volume may still contain valid data. library library name.
System Action: The server process is ended and Explanation: The library barcode reader is unable to
server operation continues. 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 User Response: If the volume is present in an
specified on the LABEL LIBVOLUME command, automated library, it should either be removed or
volumes without a barcode cannot be labelled. When checked into the library’s inventory in the PRIVATE
the VOLRANGE or VOLLIST option is specified on the category.
CHECKIN LIBVOLUME command, volumes without a
barcode cannot be checked in.
ANR8817E Name length for volume ″Volume name″
User Response: Examine the cartridge to ensure it has invalid; max is Maximum name length.
a barcode label and that it is compatible with the
Explanation: During LABEL LIBVOL processing, the
barcode reader. Not all vendors’ labels are readable by
volume name provided to be written on the label
all libraries. Check that the barcode reader is
exceeds the maximum length for the type of cartridge.
configured and is functioning properly, if necessary.
System Action: The label process fails for that
cartridge.
ANR8814I Remove volume Volume name from slot
element Slot element number of library User Response: Reissue the LABEL LIBVOL command
Library name. and provide a volume name that is not longer than the
maximum listed.
Explanation: LABEL LIBVOLUME has ended for the
specified volume and that volume must be removed
from the library because either it was not checked in or ANR8818E I/O Error on library library name; request
there was an error. for op. operation/function to the 3494
Library Manager has timed out.
System Action: The server continues normal
operation. Explanation: A command for the operation was issued
to the Library Manager and a response was not
User Response: Remove the specified volume from
received within the maximum timeout period.
the library.
System Action: The operation and the transaction
fails.
ANR8815I Remove volume Volume name from port
element Port element number of library User Response: Verify that communications with the
Library name. library is operational, that it is online and ready for
commands. Increase the time-out limit of the Library
Explanation: LABEL LIBVOLUME has ended for the
Manager Control Point device driver. If the problem
specified volume and that volume must be removed
persists, provide your service representative with the
from the library because either it was not checked in or
3494 Library Manager transaction logs.
there was an error.
System Action: The server continues normal
ANR8819E Unable to read the barcode label(s) in
operation.
User Response: Remove the specified volume from
Explanation: A LABEL command was issued with the
the library.
LABELSOURCE=BARCODE option. The library was
unable to detect that the cartridges had valid barcode
ANR8816E command: Volume Volume name in library labels or the library did not have a barcode reader. If a
Library name cannot be labelled because barcode reader is present the reader might be disabled
it is currently defined in a storage pool or it is unable to read the labels.
or in the volume history file.
System Action: Examine the cartridges to ensure they
Explanation: During command command processing, a have barcode labels and they are compatible with the
volume cannot be used because there is a storage pool barcode reader. Not all vendors’ labels are readable by
volume defined or a volume in the volume history file all libraries. Check that the barcode reader is
with this volume name. Such a volme may still contain configured and functioning properly.
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 is has previously used by an export, database dump, ANR8820W Repairing VCR data for Volume volume
or database backup operation (as recorded in the name in drive drive name; dismount may
volume history). be delayed.
System Action: If the SEARCH=YES option was Explanation: The Vital Cartridge Records of the
specified, the current volume is skipped and command cartridge in the drive are lost or corrupted, which
processing continues with the next volume found. If results in the inability of the drive to do fast locates to
SEARCH=NO was specified, command processing file positions on the cartridge. The VCR is being rebuilt
terminates.

during the volume dismount process in order to avoid User Response: Verify that communications with the
performance degradation on future mounts of the library is operational, that it is online and ready for
volume. commands. If the problem persists, provide your
service representative with the 3494 Library Manager
System Action: The server continues the dismount
transaction logs and the request id from the failed
operation. There may be a long delay because the VCR
operation.
is rebuilt by spacing the tape forward to the
end-of-data.
ANR8825E ’Volume range’ is not a valid volume
range.
Explanation: The specified string is not a valid
ANR8821E Barcode of element slot element address,
volume range.
’hardware barcode string’, exceeds maximum
length characters in length. System Action: The program prompts for a new
volume range.
Explanation: A barcode is encountered that was
longer than a valid volume name. User Response: Enter the volume names in the range
that is within the length constraints for the media type
System Action: The barcode is not considered valid
being labeled, and which contains only alphanumeric
and will not be used for the server process.
characters. The volume names of the begining and
User Response: Replace the cartridge’s barcode with ending volume must be the same in length and the
one that is supported by the library and whose number incrementals must be in digits.
of characters does not exceed the maximum length.
ANR8826E No Entry/Exit found on library library
ANR8822E ’Volume name’ is not a valid volume name.
name.
Explanation: A CHECKIN LIBVOLUME
Explanation: The specified string is not a valid SEARCH=BULK command was issued on a library that
volume name. has no Entry/Exit ports.
System Action: The program prompts for a new System Action: None.
volume name.
User Response: Enter a volume name that is within
the length constraints for the media type being labeled,
ANR8827E No Entry/Exit port is available on
and which contains only alphanumeric characters.
Explanation: A CHECKOUT LIBVOL command was
ANR8823E Hardware configuration error in library
issued on a library where all its Entry/Exit Ports were
library name: number of drives drives,
found to be full.
number of storage slots storage slots.
Explanation: The library device returned a count of
zero for either the drives orthe slots. The drives may User Response: Empty all the Entry/Exit ports on the
have not yet been configured to the operating system, library and try the command again.
or to the library. The library must have at least one
drive and multiple slots when properly configured in
ANR8828E Slot element number of library library
order to be defined to the server.
name is inaccessible.
Explanation: The slot in the library could not be
User Response: Configure the drives to the operating physically accessed at this time.
system, and reinitialize the library.
User Response: Verify that the Entry/Exit door is
ANR8824E I/O Error on library library name; request
closed and the device has not logged any device errors
request id for operation operation/function
before trying the command again.
to the 3494 Library Manager been lost.
Explanation: A command for the operation was issued
ANR8829I Remove volume volume name from slot
to the Library Manager and a response was not
element number of library library name at
received within the maximum timeout period.
your convenience.
System Action: The operation and the transaction
Explanation: A volume has been checked out from the
fails.
library and placed in a multiple entry/exit port library.

The volume needs to be removed from the library, but
ANR8833E Command: Volume volume name in library
the operation is not critical.
library name is currently being checked
System Action: None. in or checked out.
User Response: Remove the volume from the Explanation: The command cannot be processed
entry/exit slot. because the specified volume is being checked in or
checked out of the library.
ANR8830E Internal Device type drive diagnostics System Action: The command is not processed.
detect excessive media failures for
User Response: Wait until the conflicting checkin or
volume Volume name (MIM MIM Code).
checkout has completed, and then reissue the
Access mode is now set to ″read-only″.
command.
Explanation: The tape drive’s microcode performed an
analysis of the media during the prior mount of the
ANR8834E Library volume volume name is still
volume and determined that the number of temporary
present in library library name drive drive
errors and other indicators exceed the threshold for
name, and must be removed manually.
reliable data recording.
Explanation: Library operations cannot be performed
System Action: The volume is made read-only.
using the drive because a volume is still mounted in it.
User Response: Check system error logs for entries This may be due to a prior dismount failure that
made by the device relative to media errors. It is occurred on the drive.
recommended to move the data off the volume in order
System Action: The command fails. The drive may be
to minimize the impact of future errors and further
taken offline.
damage to the media.
User Response: See previous error messages and the
system error logs to determine the cause of the
ANR8831W Because of media errors for volume
dismount failure or any other reason the volume would
Volume name, data should be removed as
still be loaded in the drive. Hardware diagnostics may
soon as possible.
be required. If neccessary, remove the volume manually
Explanation: Errors previously encountered on the and place it in its storage cell. If the storage cell is
volume leave the access to the data in a questionable unknown, place the volume in any cell and issue the
state. The errors may be permanent temporary media AUDIT LIBRARY command. Use the QUERY DRIVE
failures such as the corruption of the Volume Control command to determine the online status of the drive. If
Region of a Magstar drive. the drive is still functioning, change the status with the
UPDATE DRIVE command.
User Response: Move the data off the volume. This ANR8835W Error returning volume volume name to
can be done with the MOVE DATA command. In some scratch.
cases the tape is reusable by returning it to scratch.
Check system error logs for entries made by the device Explanation: The server external library manager sent
relative to media errors. If the errors cannot be isolated a RELEASE request to the external agent for the named
ore resolved, contact your support representative. volume, but the external agent was unable comply with
Return the tape to scratch or dispose of it. the request. The server, however, marked the volume
scratched in its inventory; consequently, the server
inventory and the external agent inventory are not
ANR8832E CHECKIN LIBVOLUME for volumes in consistent. This message is issued to inform the
search mode in library library name customer that the external agent inventory must be
failed. made consistent with the server inventory using the
Explanation: The background process for a CHECKIN facilities of the external agent.
LIBVOLUME command has failed. System Action: The server has returned the volume to
System Action: The background process ends, but scratch status.
volumes have not been checked into the library. User Response: Consult the documentation for the
User Response: Make sure the library and drive external agent and take the appropriate action to make
devices associated with this command are powered on the agent inventory consistent with the server
and ready, and then reissue the command. inventory.

server starts polling the drive to determine if the
ANR8836E Function RSM_function failed in
library and drive are inaccessable. In most case, the
server_function processing, return return
libary had a temporary failure and recovers. When the
code, call call number.
server determines that the library is available, the drive
Explanation: The library function that uses the API to will be brought back online.
the Windows NT Removable Storage Manager failed
User Response: Verify the library is online. Verify
with a return code from the API. The call number
cable connections between the library and the server. If
represents the exact API call issued in the program.
the problem persists contact your service
System Action: The function fails. representative.
User Response: Use the RSM documentation to
determine the source of the problem. ANR8841I Remove volume from slot element number
of library library name at your
convenience.
ANR8837E RSM Library Library Name not supported
on this Windows platform. Explanation: A volume has been placed in a multiple
entry/exit port library because the volume should be
Explanation: The libtype=RSM was used on a
placed back in the entry/exit port as result of the
Windows platform that does not support RSM.
successful completion of a server command, or there
System Action: The function fails. was a problem during a server command. The volume
needs to be removed from the library, but the operation
User Response: Use another library type to define the is not critical.
library.
ANR8838E I/O error on drive drive name: excessive User Response: Remove the volume from the
unit attentions received from device. entry/exit slot. Examine previous messages for
additional information regarding the specified volume
Explanation: An operation to the drive failed with a and the command.
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 ANR8842E The Device type drive detected a
attention. This indicates a device failure. marginal sector and could not reallocate
the sector for volume Volume name.
System Action: The operation fails. Access mode is now set to ″read-only″.
User Response: See accompanying error messages and Explanation: The optical drive detected a marginal
the system error logs to determine any reason for the sector (media error) while reading the volume. The
drive failure. Hardware diagnostics may be required. It drive read the sector successfully but could not
may be neccessary to manually unload the volume and reallocate the sector because of a previous media error.
mark the drive offline with the UPDATE DRIVE
command. System Action: The volume is made read-only.
User Response: Check system error logs for entries
ANR8839W Drive drive name of library library name is made by the device relative to media errors. It is
accessible. recommended to move the data off the volume in order
to minimize the impact of future errors and further
Explanation: The server is now able to use the damage to the media.
mentioned drive that was inaccessible. However, the
administrator has marked the drive offline while the
drive was being polled. ANR8843E Initialization failed for library type
library library name - the library will be
System Action: The drive is left offline and is not inaccessible.
used for tape operations.
User Response: Issue the UPDATE DRIVE command library has failed. The server is unable to use the
to bring the drive back online. library. This may be for the following reasons:
v The library is defined without a path.
ANR8840E Unable to open device device name with v The device for the library is removed by a DELETE
error error number. PATH command.
Explanation: The library was inaccessible, thus v The data mover controlling the library is offline.
causing a open request to fail. This will inturn cause v The path to the library is offline.
the pending request to fail.
System Action: The library is made offline and will
System Action: A drive is marked inaccessible and the

not be used for any library operations.
ANR8847E No device type-type drives are currently
User Response: Determine the reason the library is available in library library name.
inaccessible. Render any needed corrections to the
Explanation: The attempted operation cannot be
library, shut down the server, and re-bring up the
completed on the specified library because there are no
server so that the library can be completely initialized.
available drives of the specified type. A drive may be
unavailable because a different application has the
ANR8844E Unable to open remote drive drive name, drive opened. This message may also be issued if a
error code=error value from server plugin. CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
Explanation: The indicated remote drive cannot be because all the drives are mounted by other processes
opened by the server. The error code displayed is the or sessions, or the device type was incorrectly specified.
return code from server plugin routine.
System Action: The attempted operation is
System Action: The transaction needing the drive terminated.
fails.
User Response: Use the return code displayed to check the online status of the drives. Drives that are
determine the cause of the open failure or any other marked ″Unavailable since hh:mm yy/mm/dd″ are
reason the drive cannot be opened. Hardware drives taken offline by the server at the time specified
diagnostics may be required. Inspect the drive. Ensure because of hardware failures or the inability to open
that the drive is powered on and ready, the cables are the drive. If the attempted operation is a CHECKIN or
properly connected and terminated, and the device is LABEL command, use the QUERY MOUNT command
properly configured to the operating system. to determine if all the drives in the library are mounted
and wait until one of these is available. If there are
ANR8845E Loadable module module name is mounted volumes with an IDLE status, use the
required for remote operation. DISMOUNT VOLUME command to free its drive, and
retry the original operation. Finally, the DEVTYPE
Explanation: The indicated loadable module is parameter is required for CHECKIN and LABEL
required by the server to perform an operation on a commands specifying 3590 volumes in a 349X library
remote drive or library, but the module has not loaded. that also contains 3490 drives. This is because this
Message ANR4726I is issued during server initializion library also supports 3490 volumes, and the default
when the module is loaded. device type on CHECKIN and LABEL commands is
System Action: The remote operation fails. CART (3490).
User Response: Check the server activity log for

message ANR4726I, indicating if the module was ANR8848W Drive drive name of library library name is
loaded. If you see this message during server inaccessible; server has begun polling
initializion for this module, please contact your service drive.
representative. If you do not see this message, make Explanation: The server is unable to use the
sure the loadable module has not been delete, or mentioned drive. This may be for the following
contact your service representative. reasons:
v The drive cannot be opened
ANR8846E Volume volume name is assigned to a v In the case of a 3494 or a library that can be
category that does not belong to library partitioned, the drive may be unavailable to the
library name. library manager, may be in use by another
Explanation: The attempted operation on the volume application, or may be loaded with a cartridge not
cannot proceed because it is assigned to a category labeled for server use.
other than the insert, private, or scratch category used System Action: The drive is temporarily made offline
by the library. and is not used for tape operations. The server polls
System Action: The attempted operation is the drive at one-half minute intervals to check if the
terminated. condition has cleared. Once the drives is accessible
again, the drive is brought online.
User Response: Use the mtlib utility to query the
volume’s category. If the volume is not in use by User Response: Determine the reason the drive is
another library, use mtlib to reassign the category or inaccessible, such as hardware errors reported in the
choose another volume that is assigned to the proper system logs. Render any needed corrections to the
category. drive. The drive will be brought online automatically
when the polling process detects that is has become
accessible.

ANR8849E Command: There is already a request to ANR8854E ACSAPI(command name) invocation

delete drive drive name. failed, status=acs status.
Explanation: The designated drive cannot be deleted Explanation: The ACSLS library api invocation for the
or updated because there is a request to delete the given command failed.
drive already.
System Action: Depends on the server function and
System Action: The command is not processed. command, library may be unavailable.
User Response: None. User Response: Contact your ACS System
Administrator and perform ACSLS library problem
determination.
ANR8850I ACSLS library library name is ready for
operations.
ANR8855E ACSAPI(command name) response with
unsuccessful status, status=acs status.
ready for use. Explanation: The ACSLS library api responded with
an unsuccessful status as indicated.
System Action: The library is made ready for use.
command, library may be unavailable.
User Response: If the status indicates
ANR8851E Initialization failed for ACSLS library
STATUS_CAP_IN_USE, it might be CAP priorities not
library name; will retry in delay time
set to non-zero. It might also be CAPs are not set to
minute(s).
automatic mode, or CAPs are in manual mode during
Explanation: The initialization process for the given manual checkin. If CAP mode and priorities are set
library has failed. It is retried automatically after the correctly, contact your ACS System Administrator and
specified amount of time has elapsed. perform ACSLS library problem determination.
System Action: The initialization will be retried later.

ANR8856E ACSAPI sequence(sequence number)
User Response: Ensure that the library device is request(request number) timed out, elapse
powered on and ready. time=hours:minutes:seconds.
Explanation: The ACSLS client has received no
ANR8852E Initialization failed for ACSLS library response from the ACSLS server for the period as
library name. indicated in the elapsed time. The ACSLS library api
Explanation: The initialization process for the given function with the associated sequence number is
library has failed and will not be retried until the next canceled if the request number is non-zero.
time the server needs to access the library. System Action: Depends on the server function and
System Action: The library is made temporarily command, library may be unavailable.
unavailable. User Response: Contact your ACS System
User Response: None. Administrator and perform ACSLS library problem
determination.
ANR8853E Incompatible options

CHECKLABEL=NO and SEARCH=YES ANR8857I ACS access control set to user_id - user
for ACSLS libraries. id, status=acs status.
Explanation: The CHECKLABEL=NO and Explanation: The ACSLS ACCESSID structure for
SEARCH=YES parameters on the CHECKIN LIBVOL command and volume access control is set the user_id
command are not compatible. as indicated.
System Action: The command fails. System Action: None.
User Response: Reissue the CHECKIN LIBVOL User Response: Ensure the indicated user_id is the
command and specify CHECKLABEL=YES. same as specified in the environment variable
ACSAPI_USER_ID.

ANR8858W Unable to lock drive drive id,drive id,drive
determination if the problem persist..
id,drive id, status=acs status.
Explanation: The ACSLS library function
ANR8863I Unlocking library library name volumes
acs_lock_drive failed for the specified drive.
from the ACSLS server.
Explanation: The volumes of the specified library are
command, library drive may be unavailable. or may be
being unlocked from the ACSLS server.
temporary unavailable in a shared library environment.
System Action: The operation continues. The process
User Response: Contact your ACS System
may take a while depends on the number of volumes
in the library.
determination if the problem persists.
ANR8859W Unable to lock volume volume id,
status=acs status. ANR8864I ACSLS library library name is being
re-initialized.
Explanation: The ACSLS library function
acs_lock_volume failed for the specified volume. Explanation: The specified ACSLS library is being
re-initialized.
command, library volume is unavailable. 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.
determination if the problem persist.
ANR8860W Volume volume id is already locked by
user id. ANR8865W Volume volume name bypassed for
command, status=acs_status.
Explanation: The specified volume is already locked
by other user or has a different lock id. Explanation: The specified volume is bypassed. The
volume is not in a valid status for the specified
System Action: Depends on the function, the volume
function.
maybe bypassed or the process maybe terminated.
System Action: The operation continues.
User Response: This may not be an error in a shared
configuration. However, if the existing volume lock is User Response: Determine the volume status from the
not needed. contact your ACSLS system administrator ACSSA and re-issue the command if necessary.
to clear the lock the volume.
ANR8866E Incompatible option REMOVE=BULK

ANR8861I Wait and monitor the ACSSA console for ACSLS libraries.
message to remove volume volume id
from CAP. Explanation: The REMOVE=BULK option is not
supported for ACSLS libraries. The final response of
Explanation: The specified volume is about to put into ACSAPI acs_eject does not return to the application
CAP for removal. Monitor the ACSSA console and until the volume is removed from CAP.
removed the volume after it has been placed into the
CAP as indicated in the ACSSA message. System Action: The command fails.
System Action: None. User Response: Reissue the CHECKOUT LIBVOL

command and specify REMOVE=YES or NO.
User Response: Monitor the ACSSA console and wait.
ANR8867I Processing volume volume id for the

ANR8862I Unable to access ACS volume volume id. command command.
Explanation: The specified ACSLS volume can not be Explanation: The specified volume is being processed
accessed in the library. The possible reasons might be for the specified command.
the volume is in use, the user is not authorized, the
volume does not exist in the library. System Action: The command process continues.
System Action: Depends on the server function and User Response: None.
command, library volume is unavailable.

ANR8868E Ejecting Volume volume name Failed, ANR8873E The path from source source name to
status = acs_status. destination drive name is taken offline.
Explanation: The volume is failed to be ejected from Explanation: There is problem using the indicated
the library due to the status as indicated path. The path is now marked offline.
System Action: The operation continues. System Action: The path is inaccessible.
User Response: Determine the volume status from the User Response: Determine the reason the path is
message and do something as needed inaccessible, such as hardware problem. Render any
needed corrections. Then, the path may be made online
by issuing the UPDATE PATH command with the
ANR8869E Command: There is already a request to
ONLINE=YES option.
update drive drive name.
ANR8901E Command: Incompatible options
because there is a request to update the drive already.
STATUS=CLEANER and
System Action: The command is not processed. CHECKLABEL=YES.
User Response: None. Explanation: Cleaner cartridges do not have internal

labels that can be checked by loading them into the
drive.
ANR8870E The path to the library library name is
unavailable. System Action: The command fails.
Explanation: There is no path to the given library, or User Response: Reissue the CHECKIN LIBVOL
the path to the library is offline, or the source entity of command and include the parameter,
the path to the library is offline. CHECKLABEL=BARCODE (with SEARCH=YES
specified), or include the parameter
System Action: The library is inaccessible. CHECKLABEL=NO (with the required volume name
User Response: Ensure that a path is defined to the specified in the CHECKIN command).
library. If there is path defined to the library, make sure
the path is online and the source entity of the path is ANR8902W Unable to read the barcode of cleaner
also online. cartridge in slot-id Element number of slot
in library library name; cleaner not
ANR8871I The device name device name specified checked in.
has been changed to device name. Explanation: The library barcode reader is unable to
Explanation: The specified device name on the read the label of a cartridge that is checked in as a
DEFINE PATH or UPDATE PATH command has been cleaner. The cartridge is found in the slot with the
changed to recommended device name. given element number.
System Action: The command process continues. System Action: The cartridge is not checked in. If the
library is being searched, the checkin process continues
User Response: None. with the next volume.
User Response: Examine the cartridge to ensure it has
ANR8872E No path is available for drive drive name a barcode label and that it is compatible with the
- could not unload volume volume name barcode reader. Not all vendors’ labels are readable by
from drive. all libraries. Check that the barcode reader is
Explanation: There is no path to the given drive or configured and is functioning properly. The cleaner
the path to the drive is offline or the source of the path cartridge can be checked in without use of the barcode
to the drive is offline. The indicated volume may be label by issuing the CHECKIN LIBVOL command.
still on the drive.
System Action: The drive is inaccessible. ANR8903E Command: Missing CLEANINGS
parameter for cleaner cartridge checkin.
User Response: Ensure that a path is defined to the
drive. If there is a path defined to the drive, make sure Explanation: When checking in a cleaner cartridge, the
that the path is online and that the source of the path is CLEANINGS parameter is required.
also online. Run the AUDIT LIBRARY command after System Action: The command fails.
the problem is corrected.
User Response: Reissue the CHECKIN LIBVOL
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.
ANR8908I CLEAN DRIVE for drive drive name in
library library name completed
ANR8904I Command: Cleaning operation for drive successfully.
drive name in library library name started
Explanation: The specified drive is successfully
as process process ID.
cleaned in the library during processing of a CLEAN
Explanation: A command-driven process is started to DRIVE command.
clean the specified drive. The process is assigned the ID
System Action: The drive is available for normal
that is in the message.
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.
ANR8909I Cleaning drive drive name in library
library name- CANCEL PENDING.
canceled with the CANCEL PROCESS command. Explanation: In response to a QUERY PROCESS
CLEAN DRIVE process on the server.
ANR8905I CLEAN DRIVE process for drive drive
name in library library name is been System Action: The background process operation is
canceled. terminated.
Explanation: A background server process is has been User Response: None.
working to clean the specified drive and is canceled by
ANR8910I No cleaner, or no cleaner with cleanings
System Action: The cleaning process is ended. left, found in library library name.
User Response: None. 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.
ANR8906I Cleaning drive drive name in library
library name. System Action: The drive is available for normal
library operations.
command, this message displays the status for a User Response: A cleaner should be checked in to the
CLEAN DRIVE process on the server. The given library by issuing the CHECKIN LIBVOL command.
volume is being checked in to the designated library.
System Action: The background process operation ANR8911W The cartridge in storage element slot
continues. The process may be canceled by an element address in library library name is
authorized administrator using the CANCEL PROCESS not a cleaner cartridge as was expected.
command.
Explanation: The cartridge is listed in the library’s
User Response: None. The process may be canceled inventory with a cleaner volume status. After loading
by an authorized administrator using the CANCEL the cartridge in the specified storage cell into a drive
PROCESS command. for cleaning, it is determined that it is not a cleaner
cartridge.
ANR8907E CLEAN DRIVE for drive drive name in System Action: The drive is available for normal
library library name failed. library operations.
Explanation: The background process for a CLEAN User Response: Verify all other cleaner cartridges are
DRIVE fails. in the correct storage cells. Issue the QUERY
LIBVOLUME command to obtain the storage cells of all
System Action: The background process ends, but the
the cartridges currently checked into TSM. The
drive is not cleaned.
cartridge should be checked out of the library by
User Response: Make sure the library and drive issuing the CHECKOUT LIBVOL command if the
devices associated with this command are powered on cartridge is still listed in the library’s inventory with a
and ready. Reissue the command. cleaner volume status. If necessary a cleaner cartridge
should be checked in to replace it.

cleanings are exhausted. A new cleaner may be checked
ANR8912E Unable to verify the label of volume
in so that the library is not left without a useful cleaner
from slot-element element-address in drive
when the old cleaner is exhausted.
drive name in library library name.
Explanation: The volume from the slot that is
ANR8916I Drivemapping for drive Drive name in
identified by the element address is loaded into a drive.
library library name on storage agent
The drive cannot be opened following the load. The
storage agent name defined.
label cannot be read to process the volume.
Explanation: A drive mapping has been successfully
System Action: The volume is stored, and processing
defined for the specified drive.
continues with the next available slot.
System Action: The drivemapping is defined and
User Response: Check the system error logs for errors
recorded in the database.
reported by the drive that are related to this volume.
Make sure that the cartridge is not a cleaner cartridge User Response: None.
that would have been loaded by mistake. If the
cartridge is a cleaner, issue the QUERY LIBVOL
command to get the correct storage slot for the cleaner ANR8917I Drive mapping for drive Drive name in
and move the cleaner to that slot. If the cleaner is not library library name on storage agent
in the library’s inventory, use the CHECKIN LIBVOL to storage agent name updated.
check the cleaner in. Explanation: An UPDATE DRIVEMAPPING request
has been successfully processed for the given drive.
ANR8913I Drive drive name in library library name is System Action: The server updates its information
currently busy; Cleaning is scheduled. about the drive mapping.
Explanation: A background process to clean the drive User Response: None.
is unable to acquire the drive because the drive is busy.
System Action: The background process operation ANR8918I Drive mapping for drive Drive name in
completes. The drive is scheduled to be cleaned when library library name on storage agent
it is unloaded. storage agent name deleted.
User Response: None. Explanation: The drive mapping for the specified
storage agent, library, and drive has been deleted
ANR8914I Drive drive name in library library name successfully.
needs to be cleaned. System Action: The drive mapping is deleted.
Explanation: The drive has returned indicating to the User Response: None.
server that it needs to be cleaned.
System Action: The server marks the drive to be ANR8919I Initialization and recovery has started
cleaned. If the drive is enabled for server-managed for shared library library name.
cleaning, and a cleaner cartridge is checked into the
library, the server will load the cleaner into the drive Explanation: The shared library has started to
after the current volume is dismounted. See the initialize or recover to resynchronize the library
DEFINE DRIVE and QUERY DRIVE commands for manager and library client.
information on enabling server-managed cleaning. See System Action: None.
the CHECKIN LIBVOL command for checking a
cleaner into the library. User Response: This process should resynchronize all
of the drives that are currently being used by this
User Response: None. library client. This process might also start after a
communication error or if the library client has not
ANR8915I Cleaning cartridge cleaner name in library been able to verify drive status with the library
library name is near end of life; has manager.
cleanings left uses left.
Explanation: A cleaner cartridge is found and used, ANR8920I Initialization and recovery has ended for
but its number of uses it has left is nearly exhausted. shared library library name.
System Action: The cleaning operation continues. Explanation: Initialization or recovery has ended the
library manager and library client should be
User Response: As the cleaner is used, monitor the synchronized.
number of cleanings that remain with the QUERY
LIBVOL command. Remove the cleaner when all System Action: None.

User Response: The drives previously owned by the above server name is still running. Verify that the
library client should now indicate they are free on the sessions have not been disabled and the network is still
library manager. Verify this with the QUERY DRIVE working between the two host machines. Verify that
command on the library manager. If ownership of the the server definition (QUERY SERVER) on both the
drives is still in question restart the library client and library manger and the library client are correct.
library manager.
ANR8926W An Error was encountered while
ANR8921E Unable to start library polling thread . confirming the use of drive drive name in
shared library library name.
Explanation: Library sharing requires that this polling
thread starts. This thread keeps the library manager Explanation: The library client was unable to confirm
and library client synchronized with regards to drive the usage of the drive to the with the library manager.
ownership. These thread are started when the library is
defined or when the server is first initialized.
User Response: Verify that the sessions have not been
disabled and the network is still working between the
User Response: Since the polling thread did not start, two host machines. Verify that the server definition
the user must restart the server in order for library (QUERY SERVER) on both the library manger and the
sharing to correctly work. Failure to restart the server library client are correct.
and get these polling services running can cause
unusual results for library clients.
ANR8927W This library client has been unable to
contact the library manager for elapsed
ANR8922I A device class for library library name time seconds. Releasing ownership of all
was not found. drives in the shared library library name.
Explanation: A library client request a mount Explanation: The library client was unable to confirm
operation to be performed by the library manager. The the usage of the drive with the library manager. The
library manager is missing a device class definition for library client will now dismount all volumes that it
that library. currently owns.
User Response: Define a device class for the library User Response: Verify that the sessions have not been
using the DEFINE DEVCLASS command. disabled and the network is still working between the
two host machines. Verify that the server definition
(QUERY SERVER) on both the library manger and the
ANR8923I Dismount failed because drive drive
library client are correct.
name in library library name is not
currently owned by drive owner name.
ANR8928W Library library name specified for shared
Explanation: A library client attempted to dismount a
file device class device class name was not
drive that was not currently owned by the library
defined as shared. The device class will
client.
not be shareable unless the library is
System Action: None. updated.
User Response: None. Explanation: A pre-existing library was specified for a

new shared file device class. However, files in the
device class cannot be shared unless the library is also
ANR8925W Drive drive name in library library name shared.
has not been confirmed for use by
server server name for over elapsed time System Action: None.
seconds. Drive will be reclaimed for use
User Response: Issue the UPDATE LIBRARY libname
by others.
SHARED=YES command to make the library shared.
Explanation: The library server was unable to contact
the library client for the given interval to verify that the
ANR8929E Library library name specified for shared
library client is still using the drive. At this point the
file device class device class name was not
error recovery logic of the library manager will reclaim
defined as a FILE library.
the drive (including dismounting the client’s volume if
possible) and allow other to use the drive. 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
User Response: Verify that the library client with the parameter.

System Action: None. The device class is not created.
ANR8932W The drive map for server servername,
User Response: Specify a library name that was library library name, drive name drive
created with the LIBTYPE=FILE and SHARED=YES name has directory directory which is
parameters, or specify a library name which does not different than other drive maps for
exist, in which case, the library will be created. You can drives within the same library.
also not specify the LIBRARY parameter, a library name
Explanation: A shared file was about to be created. In
will be created.
doing so, it was determined that there are differing
definitions for the directories associated with the drive
ANR8930W An attempt to define drives to create maps between the indicated drive map and other drive
drives failed for library library name. The maps for drives in the same library. This could cause
device class has a mount limit of mount data to be written in unanticipated locations or may
limit but the number of drives in the prevent data from being written.
associated library is less than the mount
System Action: The server continues operation using
limit.
the indicated directory.
Explanation: When a shared device class is created or
User Response: Use the QUERY DRIVEMAP
updated, an attempt is made to define additional file
command with the F=D parameter to list the directories
drives in the associated library up to the mount limit, if
associated with drive maps for drives in the indicated
the number of drives is less than the mount limit. One
library and ensure that the directories are correct and
or more failures occurred in defining additional drives.
identical. Use the UPDATE DRIVEMAP command to
The number of drives does not correspond to the
update any incorrect directory entries.
mount limit for the associated device class. This can
cause resource balancing problems between the server
and storage agents. ANR8933W File volumename in library library does
not exist in the expected directory.
System Action: The server continues operation.
Explanation: A FILE volume was being dismounted
from a file drive. The file does not exist in the directory
get the names of the drives associated with the library.
in which it was expected to be found.
Use the QUERY DEVCLASS deviceclass F=D command
to find the mount limit of the associated device class. System Action: The server continues operation.
Use the DEFINE DRIVE library drive name
User Response: It is possible that a drive mapping is
DEVICE=FILE command to define additional drives in
incorrect and that a storage agent is using a valid, but
the file library to match the mountlimit of the
different directory than that of the server. In this case,
associated device class.
the storage agent can access the file, but the server
cannot. Use the QUERY DRIVEMAP command with
ANR8931W An attempt to delete drives to delete the F=D parameter to list the directories associated
drives failed for library library name. The with drive maps for drives in the indicated library and
device class has a mount limit of mount ensure that the directories are correct and identical. Use
limit but the number of drives in the the UPDATE DRIVEMAP command to update any
associated library is greater than the incorrect directory entries. To move the file into the
mount limit. correct directory, use the Windows move command or
the Unix mv command, depending on your platform.
Explanation: When a shared device class is updated
and the number of drives in the associated library is
greater than the mount limit of the device class, an ANR8934W File volumename in library library
attempt is made to delete drives so that there are as associated with device class device class
many drives as the mount limit. One or more failures could not be inserted into the library
occurred in deleting drives. The number of drives does inventory.
not correspond to the mount limit for the associated
Explanation: A FILE volume was being inserted into
device class. This can cause resource balancing
the library inventory. The file was not found in the
problems between the server and storage agents.
directory associated with the device class that
System Action: The server continues operation. references the library. However, an entry for the
indicated file name is already in the library inventory.
get the names of the drives associated with the library. System Action: The server continues operation.
Use the QUERY DEVCLASS deviceclass F=D command
User Response: It is possible that a drive mapping is
to find the mount limit of the associated device class.
incorrect and that a storage agent is using a valid, but
Use the DELETE DRIVE command to delete drives
different directory than that of the server. In this case,
until the number of drives in the library corresponds to
the storage agent can access the file, but the server
the device class’s mount limit.
cannot. Use the QUERY DRIVEMAP command with

ANR8935E • ANR9581W (HP-UX)
the F=D parameter to list the directories associated
ANR9579W (HP-UX) Command: Unable to locate file
with drive maps for drives in the indicated library and
file name.
ensure that the directories are correct and identical. Use
the UPDATE DRIVEMAP command to update any Explanation: The specified file cannot be found. Note:
incorrect directory entries. To move the file into the PREPARE assumes that the volume formatting program
correct directory, use the Windows move command or (dsmfmt) is located in the same directory as the server
the Unix mv command, depending on your platform. executable file.
System Action: PREPARE uses the following default
ANR8935E A compatible device class for shared file names in the plan file:
library library name on server server name v For the server executable the default is
was not found. /opt/tivoli/tsm/server/bin/dsmserv.
Explanation: The library client server has a device v For the volume formatting program the default is
class definition that is not compatible with the device /opt/tivoli/tsm/server/bin/dsmfmt.
class definition on this server. The device type and
User Response: Determine why file does not exist;
recording format need to be the same on both servers
create if necessary.
or one of the servers can have a device type of generic
tape.
ANR9579W (Solaris) Command: Unable to locate file
file name.
ANR8936W The path conversion of drive drive name
in library library name with device name Explanation: The specified file cannot be found. Note:
device name failed. UPDATE DRIVE PREPARE assumes that the volume formatting program
required. (dsmfmt) is located in the same directory as the server
executable file.
Explanation: During the initialization of a library, the
server finds that the drive path was removed. System Action: PREPARE uses the following default
file names in the plan file:
System Action: The drive will not be accessible by the
library during tape operations. v For the server executable the default is
/opt/tivoli/tsm/server/bin/dsmserv.
User Response: The drive may be made accessible by
v For the volume formatting program the default is
issuing the UPDATE DRIVE command with the
/opt/tivoli/tsm/server/bin/dsmfmt.
DEVICE= option.
ANR8937W The device name for drive drive name in
library library name is missing. UPDATE
DRIVE required. ANR9580W (Solaris) Command: Generated
replacement volume name volume name
Explanation: The device name for a drive was found
may not be a valid raw partition name.
to be missing.
Original volume name:volume name.
System Action: The drive will not be accessible by the Stanza is stanza name.
server for tape operations.
Explanation: Appending the replacement volume
User Response: The drive may be made accessible by name postfix to the original volume name has created a
issuing the UPDATE DRIVE command with the name that may not be a valid raw partition name.
DEVICE= option.
the recovery plan stanza.
ANR8938E Initialization failed for Shared library
User Response: Manually update the generated
library name; will retry within delay time
recovery plan stanza with a legal replacement name.
minute(s).
The replacement name can be another raw partition
Explanation: The initialization process for the given name or a regular file name.
library has failed. It will be retried automatically in the
specified time.
ANR9581W (HP-UX) Command: Volume file name not
System Action: The initialization will be retried later. found while building stanza recovery
plan stanza name.
User Response: Ensure that the library manager
server is running, and the library is initialized. 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

ANR9581W (Solaris) • ANR9585E (Solaris)
included in the recovery plan stanza. User Response: Reissue the command specifying a
valid prefix. The following commands are used to
specify the prefix:
v SET DRMPLANPREFIX
v SET DRMINSTRPREFIX
ANR9581W (Solaris) Command: Volume file name not
found while building stanza recovery v PREPARE
plan stanza name.
Explanation: This volume is defined to the server but ANR9583E (Solaris) Command: Cannot generate fully
does not exist. The device class associated with the qualified file name for ’name’.
volume is DISK or the device class device type is FILE. Explanation: A failure occurred expanding the
System Action: The entry for the volume is not specified file name.
included in the recovery plan stanza. System Action: Recovery plan file not created.
User Response: Determine why file does not exist; User Response: Reissue the command specifying a
create if necessary. valid prefix. The following commands are used to
specify the prefix:
ANR9582E (HP-UX) Command: Generated file name v SET DRMPLANPREFIX
too long. Length of directory or prefix v SET DRMINSTRPREFIX
’prefix’ plus ’name’ exceeds maximum
v PREPARE
characters characters.
Explanation: The file name generated is too long. The
ANR9584E (HP-UX) command: Cannot generate server
maximum valid length is shown in the message.
options file name.
Explanation: A failure occurred generating the server
created.
options file name.
specify the prefix: User Response: See accompanying messages for more
v SET DRMPLANPREFIX information.
v PREPARE ANR9584E (Solaris) Command: Cannot generate
server options file name.
ANR9582E (Solaris) Command: Generated file name Explanation: A failure occurred generating the server
too long. Length of directory or prefix options file name.
’prefix’ plus ’name’ exceeds maximum System Action: Recovery plan file not created.
Explanation: The file name generated is too long. The information.
System Action: The recovery plan file was not ANR9585E (HP-UX) Command: Cannot generate a
created. volume history file name.
User Response: Reissue the command specifying a Explanation: A failure occurred generating the volume
valid prefix. The following commands are used to history file name.
specify the prefix:
v SET DRMPLANPREFIX System Action: Recovery plan file not created.
v SET DRMINSTRPREFIX User Response: See accompanying messages for more

v PREPARE information.
ANR9583E (HP-UX) Command: Cannot generate fully ANR9585E (Solaris) Command: Cannot generate a
qualified file name for ’name’. volume history file name.
Explanation: A failure occurred expanding the Explanation: A failure occurred generating the volume
specified file name. history file name.
System Action: Recovery plan file not created. System Action: Recovery plan file not created.

ANR9586E (HP-UX) • ANR9604E
User Response: See accompanying messages for more User Response: Contact your service representative
information. for assistance in resolving the error.
ANR9586E (HP-UX) Command: Cannot generate a ANR9601E (Solaris) Failed to allocate message queue
device configuration file name. for the shared memory communications
Error: error text.
Explanation: A failure occurred generating the device
configuration file name. Explanation: An error has occurred when attempting
to get memory for the shared communications option.
System Action: Shared memory communications will
not be activated.
information.
User Response: If the error given is ″ENOSPC″, the
maximum number of system message queues have
ANR9586E (Solaris) Command: Cannot generate a
likely been exceeded. Update ″/etc/system″ with ″set
device configuration file name.
shmsys:msginfo_msgmni=100″. Any other error
Explanation: A failure occurred generating the device suggests an internal problem and shoud be reported.
configuration file name.
System Action: Recovery plan file not created. ANR9602E Invalid JOB information passed to the
NETLS Interface.
information. Explanation: The server licensing functions
encountered an internal error in accessing license
information for the server storage capacity and number
ANR9600E Invalid information passed to NETLS of registered clients.
license interface.
System Action: Server operation continues. New
Explanation: The server licensing functions licensing information is not used by the server.
information for the server storage capacity and number User Response: Contact your service representative
of registered clients. for assistance in resolving the error.
licensing information is not used by the server. ANR9603E The NETLS Nodelock file could not be
created.
for assistance in resolving the error. Explanation: The server was not able to create the file
/usr/lib/netls/conf/nodelock which is used for storing
license password information.
ANR9600E (Solaris) Failed to allocate memory for
shared memory communications. Error: System Action: Server operation continues. New
error text. licensing information is not used by the server.
Explanation: An error has occurred when attempting User Response: If the server is not running with root
to get memory for the shared communications option. authority, make sure that directory authorities in the
/usr/lib/netls/conf path are set so that the user ID
System Action: Shared memory communications will under which the server is running can create, read, and
not be activated. write to the /usr/lib/netls/conf/nodelock file. If the
User Response: The maximum shared memory is, server is running with root authority, contact your
most likely, too small. To increase on SUN, update service representative for assistance in resolving this
″/etc/system″ with ″set problem.
shmsys:shminfo_shmmax=268435456″ (a recommended
size). ANR9604E The NETLS license interface
encountered an internal error.
ANR9601E The NETLS license interface was not Explanation: The server licensing functions
initialized properly. encountered an internal error in accessing license
Explanation: The server licensing functions information for the server storage capacity and number
encountered an internal error in accessing license of registered clients.
information for the server storage capacity and number System Action: Server operation continues. New
of registered clients. licensing information is not used by the server.
System Action: Server operation continues. New User Response: Contact your service representative
licensing information is not used by the server.

for assistance in resolving the error. User Response: Register the license again with the
REGISTER LICENSE command. Be sure to correctly
enter the license information.
ANR9605E An invalid vendor ID was passed to
NETLS.
ANR9610E Unable to create directory: directory.
Explanation: The server licensing functions
encountered an internal error in accessing license Explanation: The REGISTER LICENSE command is
information for the server storage capacity and number unable to either create or verify the specified directory
of registered clients. structure.
System Action: Server operation continues. New System Action: None.
User Response: If the server is not running with root
User Response: Contact your service representative authority, make sure that directory authorities in the
for assistance in resolving the error. /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
ANR9606E NETLS failed to find socket families to
server is running with root authority, contact your
contact a server.
service representative for assistance in resolving this
Explanation: The server licensing functions problem.
information for the server storage capacity and number
ANR9610E (Solaris) Unable to create directory:
of registered clients.
directory.
Explanation: The REGISTER LICENSE command is
unable to either create or verify the specified directory
User Response: Contact your service representative structure.
ANR9607E No NETLS Servers found.
authority, make sure that directory authorities in the
Explanation: The server licensing functions given directory path are set so that the user under
encountered an internal error in accessing license which the server is running can create, read, and write
information for the server storage capacity and number to the server’s license file. If the server is running with
of registered clients. root authority, contact your service representative for
assistance in resolving this problem.
ANR9611E Unable to open NODELOCK file: file.
for assistance in resolving the error. Explanation: The REGISTER LICENSE command is
unable to either create or open the nodelock file.
ANR9608E A NETLS Security Breach was System Action: None.
encountered.
Explanation: The server licensing functions authority, make sure that directory authorities in the
encountered an internal error in accessing license /usr/lib/netls/conf path are set so that the user ID
information for the server storage capacity and number under which the server is running can create, read, and
of registered clients. write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your
System Action: Server operation continues. New service representative for assistance in resolving this
licensing information is not used by the server. problem.
for assistance in resolving the error. ANR9612E Error writing to NODELOCK file.
Explanation: The REGISTER LICENSE command fails
ANR9609E Incorrect license entered: Password writing to the nodelock file.
entered = password Annotation entered =
annotation. System Action: None.
Explanation: The license information entered for a User Response: If the server is not running with root
REGISTER LICENSE command is not correct. authority, make sure that directory authorities in the
/usr/lib/netls/conf path are set so that the user ID

ANR9613W • ANR9615E (Solaris)
under which the server is running can create, read, and
ANR9614E Unable to open license file: file.
write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your Explanation: The REGISTER LICENSE command is
service representative for assistance in resolving this unable to create or open the server license file.
problem.
User Response: Make sure that the user ID under
ANR9613W Error loading modname for Licensing
which the server is running has the authority required
function: error string.
to create or write, or both, to the license file in the
Explanation: The server cannot load file module directory in which the server is running. If this does
modname to initialize licensing functions due to error not resolve the problem, contact your service
error string. representative for assistance.
System Action: Server operation continues. Default
licensing values are in effect for running the server. ANR9614E (Solaris) Unable to open license file: file.
User Response: The dsmreg.lic module is accessed as Explanation: The REGISTER LICENSE command is
part of the load process for licensing. It should be in unable to either create or open the server license file.
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 User Response: Make sure that the user ID under
module is only installed when you purchase the which the server is running has the authority required
product. 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
ANR9613W (HP-UX) Error loading modname for
representative for assistance.
Licensing function: error string.
Explanation: The server cannot load file module
ANR9615E Error writing to adsmserv.licenses file.
modname to initialize licensing functions due to error
error string. Explanation: The REGISTER LICENSE command fails
writing to the server license file.
System Action: Server operation continues. Default
licensing values are in effect for running the server. System Action: None.
User Response: The dsmreg.lic module is accessed as User Response: Make sure that the user ID under
part of the load process for licensing. It should be in which the server is running has the authority required
the same directory as the dsmserv executable or it must to create or write, or both, to the license file in the
be in a directory that is pointed to by the directory in which the server is running. Also, ensure
DSMSERV_DIR environment variable. The dsmreg.lic that free space is available in the file system so that the
module is only installed when you purchase the license information can be written to the file. If this
product. does not resolve the problem, contact your service
representative for assistance.
ANR9613W (Solaris) Error loading modname for
Licensing function: error string. ANR9615E (Solaris) Error writing to
adsmserv.licenses file.
Explanation: The server cannot load file module
modname to initialize licensing functions due to error Explanation: The REGISTER LICENSE command fails
error string. writing to the server license file.
System Action: Server operation continues. Default System Action: None.
licensing values are in effect for running the server.
User Response: Make sure that the userid under
User Response: dsmreg.lic is accessed as part of the which the server is running has the authority required
load process for licensing. It should be in the same to create and/or write to the license file in the directory
directory as the dsmserv executable file or it must be in in which the server is running. Also ensure that there is
a directory that is pointed to by the DSMSERV_DIR free space available in the filesystem so that the license
environment variable. The dsmreg.lic module is only information can be written to the file. If this does not
installed when you purchase the product. resolve the problem contact your service representative
for assistance.

ANR9616I Invalid license record record value found ANR9618E License registration is not supported on
in license file - it will be skipped. this server.
Explanation: The license manager found an invalid Explanation: The REGISTER LICENSE command fails
record in the server license file (adsmserv.licenses). The because the license authorization module cannot be
record is ignored. found.
System Action: The invalid record is ignored. System Action: Server operation continues; licensing
terms are not changed by the REGISTER LICENSE
User Response: Erase the adsmserv.licenses file and
command.
reregister your licenses.
User Response: The license authorization file is
required for formal licensing for the AIX/6000 server.
ANR9616W (Solaris) Invalid license record record
The file is delivered when the product is purchased,
value found in license file - it will be
but it is not available in the product service stream or
ignored.
with demonstration copies of the server. If you have
Explanation: The license manager found an invalid purchased the server, contact your service
record in the server license file (adsmserv.licenses). The representative for assistance in resolving this problem.
record is ignored.
System Action: The invalid record is ignored. ANR9618E (Solaris) License registration is not
supported on this server.
User Response: Erase the adsmserv.licenses file and
reregister your licenses. Refer to the licenses provided Explanation: The REGISTER LICENSE command
to you to ensure that only valid licenses are specified failed because the license authorization module could
with the REGISTER LICENSE command. not be found.
System Action: Server operation continues; licensing
ANR9617I Invalid license authorization: terms are not changed by the REGISTER LICENSE
authorization string. command.
Explanation: The license authorization specified for a User Response: The license authorization file is
REGISTER LICENSE command is not valid. required for formal licensing for the server. The file is
delivered when the server is purchased, but is not
System Action: Server operation continues; licensing available in the product service stream or with
terms are not changed by the REGISTER LICENSE demonstration copies of the server. If you have
command. purchased the server, please contact your service
User Response: Examine the license authorization representation for assistance in resolving this problem.
string that was entered with the REGISTER LICENSE
command. Reenter the command if the license ANR9622I An EVALUATION LICENSE for support
authorization was not specified correctly. If the license of Tivoli Space Management will expire
authorization has been specified correctly, contact your on expiration date.
Explanation: The AIX/6000 server is distributed with
an evaluation license for Tivoli Space Management
ANR9617W (Solaris) Invalid license authorization: support. If no formal license is found for the server and
authorization string. the evaluation period has not lapsed, this message is
Explanation: The license authorization specified for a displayed each time the server checks the server license
REGISTER LICENSE command is not valid. terms.
System Action: Server operation continues; licensing System Action: The Tivoli Space Management license
terms are not changed by the REGISTER LICENSE allows clients to utilize the server for storing files
command. migrated during space management. The server checks
this license when files are migrated to the server from
User Response: Examine the license authorization that client nodes to ensure that the server is licensed to
was entered using the REGISTER LICENSE command. perform this function.
Reenter the command if the license authorization was
not specified correctly. If the license authorization has User Response: If you are interested in using the
been specified correctly, contact your service server, contact your service representative to obtain
representative. 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 • ANR9624I (Windows NT)
allows clients to utilize the server for storing files
ANR9623I An EVALUATION LICENSE for support
migrated during space management. The server checks
of Tivoli Disaster Recovery Manager
will expire on expiration date.
client nodes to ensure that the server is licensed to
Explanation: The AIX/6000 server is distributed with perform this function.
an evaluation license for Tivoli Disaster Recovery
User Response: If you are interested in using the
Manager support. If no formal license is found for the
server, contact your service representative to obtain
server and the evaluation period has not lapsed, this
formal licenses for the server before the evaluation
message is displayed each time the server checks the
server license terms.
System Action: The Tivoli Disaster Recovery Manager expiration date shown.
license allows customers to store information in the
server regarding machines and recovery media, allows
ANR9624I (Solaris) An EVALUATION LICENSE for
management of offsite recovery media, collects and
support of Tivoli Space Management
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 Explanation: The server is distributed with an
machines or recovery media are defined to the server, evaluation license for Tivoli Space Management
when PREPARE or MOVE DRMMEDIA are invoked support. If no formal license is found for the server and
and when a data base backup or storage pool backup the evaluation period has not lapsed, this message is
to a device class of type server are performed to ensure displayed each time the server checks the server license
that the server is licensed to perform this function. terms.
User Response: If you are interested in using the System Action: The Tivoli Space Management license
server, contact your service representative to obtain allows clients to utilize the server for storing files
formal licenses for the server before the evaluation migrated during space management. The server checks
period has elapsed. Without formal licenses, the server this license when files are migrated to the server from
will not support Tivoli Disaster Recovery Manager after client nodes to ensure that the server is licensed to
the expiration date shown. perform this function.
ANR9624E Unexpected error encountered in iFor/LS server, contact your service representative to obtain
(SystemView License Use Management) formal licenses for the server before the evaluation
routine license interface name period has elapsed. Without formal licenses, the server
status=xreported status code. will not support Tivoli Space Management after the
expiration date shown.
Explanation: The server encountered an unexpected
error in accessing the SystemView License Use
Management function specified. ANR9624I (Windows NT) An EVALUATION
LICENSE for support of Tivoli Space
System Action: The server license monitoring
Management will expire on expiration
operation fails
date.
User Response: The SystemView License Use
Explanation: The server is distributed with an
Management product is installed during normal AIX
evaluation license for Tivoli Space Management
server installation. Check to make sure that server was
support. If no formal license is found for the server and
installed correctly. If the installation was successful,
the evaluation period has not lapsed, this message is
re-boot your AIX system and re-start the server. If this
displayed each time the server checks the server license
message continues to be issued, contact your service
terms.
representative.
System Action: The Tivoli Space Management license
allows clients to utilize the server for storing files
ANR9624I (HP-UX) An EVALUATION LICENSE for
migrated during space management. The server checks
support of Tivoli Space Management
client nodes to ensure that the server is licensed to
Explanation: The server is distributed with an perform this function.
evaluation license for Tivoli Space Management
terms.
System Action: The Tivoli Space Management license expiration date shown.

class of type server. The server checks this license when
ANR9625E Could not open file file name.
machines or recovery media are defined to the server,
Explanation: The server could not open the license when PREPARE or MOVE DRMMEDIA are invoked
certificate file specified. and when a data base backup or storage pool backup
to a device class of type server are performed to ensure
System Action: The license registration command
that the server is licensed to perform this function.
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
will not support Tivoli Disaster Recovery Manager after
specification. If an error cannot be found, contact your
the expiration date shown.
ANR9625I (Windows NT) An EVALUATION

ANR9625I (HP-UX) An EVALUATION LICENSE for
LICENSE for support of Tivoli Disaster
support of Tivoli Disaster Recovery
Recovery Manager will expire on
Manager will expire on expiration date.
expiration date.
evaluation license for Tivoli Disaster Recovery Manager
evaluation license for Tivoli Disaster Recovery Manager
terms.
terms.
System Action: The Tivoli Disaster Recovery Manager
System Action: The Tivoli Disaster Recovery Manager
when PREPARE or MOVE DRMMEDIA are invoked
when PREPARE or MOVE DRMMEDIA are invoked
and when a data base backup or storage pool backup
and when a data base backup or storage pool backup
ANR9625I (Solaris) An EVALUATION LICENSE for

ANR9626E Invalid license certificate file: file name.
support of Tivoli Disaster Recovery
Manager will expire on expiration date. Explanation: The specified file does not contain valid
license certificate information.
evaluation license for Tivoli Disaster Recovery Manager System Action: The license registration command
support. If no formal license is found for the server and ignores the contents of the file.
terms.
System Action: The Tivoli Disaster Recovery Manager error is found, re-try the command with the corrected
license allows customers to store information in the specification. If an error cannot be found, contact your
server regarding machines and recovery media, allows service representative.

ignores the contents of the file.
ANR9627E Cannot access node license lock file: file
name. User Response: Examine the file specification entered,
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. service representative.
User Response: Examine the file specification
displayed and ensure that the file attributes will allow ANR9631E (Windows NT) Cannot access node
the server to access the file. The location of the file is license lock file: file name.
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 System Action: The license function fails.
specified for the file. If the problem persists after these
corrections have been made, contact your service User Response: Examine the file specification
representative. displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is
ANR9628E (Windows NT) Unexpected error or in the directory specified by the DSMSERV_DIR
encountered in iFor/LS (SystemView environment variable. Re-specify the DSMSER-DIR
License Use Management) routine license environment variable if this specification is in error.
interface name status=xreported status code. Also ensure that there is sufficient space on the drive
corrections have been made, contact your service
representative.
Management function specified.
ANR9632I (Windows NT) Cannot load licensing DLL
operation fails
library: DLL file name : the server will
User Response: The SystemView License Use assume evaluation licensing mode.
Management product is installed during normal server
Explanation: The server was not able to load the
installation. Check to make sure that the product was
specified dynamic link library.
installed correctly. If the installation was successful,
re-boot your system and re-start the server. If this System Action: Server licensing asumes Try and Buy
message continues to be issued, contact your service mode with licenses for 180 days.
representative.
User Response: The named DLL library(ies) are
required for the server to support feature licensing. If
ANR9629E (Windows NT) Could not open file file you are running an evaluation copy of the server, this
name. message should not cause concern and is normal. If the
libraries are installed and this message continues to be
Explanation: The server could not open the license
issued, contact a support representative for assistance.
certificate file specified.
ANR9634E command name: No license certificate
fails.
files were found with the file name
User Response: Examine the file specification entered, specification specification.
Explanation: The server did not find any license
certificate file(s) with the file name specification
entered.
service representative. System Action: The license registration command
fails.
ANR9630E (Windows NT) Invalid license certificate User Response: Examine the file specification entered,
file: file name. including wildcard characters, to determine if it names
the license certificate file(s) you intended to use. The
Explanation: The specified file does not contain valid
file name specification indicates the fully qualified file
name the server was trying to read. The directory used
System Action: The license registration command to locate the license certificate files when no explicit

ANR9634E (HP-UX) • ANR9636E (HP-UX)
path is provided is determined as follows:
ANR9635E (HP-UX) Invalid license certificate file:
v The directory path pointed by the environmental file name.
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,
contact your service representative. User Response: Examine the file specification entered,
ANR9634E (HP-UX) command name: No license
certificate files were found with the file
name specification specification.
ANR9635E (Solaris) Invalid license certificate file: file
entered.
name.
fails.
error is found, re-try the command with the corrected User Response: Examine the file specification entered,
specification. If an error cannot be found, contact your including wildcard characters, to determine if it names
service representative. the license certificate file(s) you intended to use. If an
ANR9634E (Solaris) command name: No license
certificate files were found with the file
ANR9635E (Windows NT) Invalid license certificate
file: file name.
entered. Explanation: The specified file does not contain valid
fails. System Action: The license registration command
including wildcard characters, to determine if it names User Response: Examine the file specification entered,
the license certificate file(s) you intended to use. If an including wildcard characters, to determine if it names
error is found, re-try the command with the corrected the license certificate file(s) you intended to use. If an
specification. If an error cannot be found, contact your error is found, re-try the command with the corrected
service representative. specification. If an error cannot be found, contact your
ANR9634E (Windows NT) command name: No license
certificate files were found with the file ANR9636E (HP-UX) Could not open file file name.
Explanation: The server did not find any license certificate file specified.
entered.
fails.
fails.
User Response: Examine the file specification entered, the license certificate file(s) you intended to use. If an
including wildcard characters, to determine if it names error is found, re-try the command with the corrected
the license certificate file(s) you intended to use. If an specification. If an error cannot be found, contact your
error is found, re-try the command with the corrected service representative.

ANR9636E (Solaris) • ANR9638W (Solaris)
ANR9636E (Solaris) Could not open file file name.
Explanation: The server could not open the license environment variable. Re-specify the DSMSERV-DIR
certificate file specified. environment variable if this specification is in error.
Also ensure that there is sufficient space on the drive
fails.
User Response: Examine the file specification entered, representative.
ANR9637E (Windows NT) Cannot access node
license lock file: file name.
service representative. Explanation: The server was not able to access the
ANR9636E (Windows NT) Could not open file file
name. System Action: The license function fails.
Explanation: The server could not open the license User Response: Examine the file specification
certificate file specified. displayed and ensure that the file attributes will allow
fails.
User Response: Examine the file specification entered, environment variable. Re-specify the DSMSER-DIR
including wildcard characters, to determine if it names environment variable if this specification is in error.
the license certificate file(s) you intended to use. If an Also ensure that there is sufficient space on the drive
error is found, re-try the command with the corrected specified for the file. If the problem persists after these
specification. If an error cannot be found, contact your corrections have been made, contact your service
service representative. representative.
ANR9637E (HP-UX) Cannot access node license lock ANR9638W (HP-UX) License registration is not
file: file name. supported on this server.
Explanation: The server was not able to access the Explanation: The REGISTER LICENSE command fails
specified file. The node lock file contains licensing because the license authorization module cannot be
information for the server. found.
System Action: The license function fails. System Action: Server operation continues; licensing
User Response: Examine the file specification command.
displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is User Response: The license authorization file is
either in the directory from which the server is started, required for formal licensing for the HP-UX server. The
or in the directory specified by the DSMSERV_DIR file is delivered when the server is purchased, but it is
environment variable. Re-specify the DSMSERV_DIR not available in the product service stream or with
environment variable if this specification is in error. demonstration copies of the server. If you have
Also ensure that there is sufficient space on the drive purchased the server, contact your service
specified for the file. If the problem persists after these representative for assistance in resolving this problem.
representative.
ANR9638W (Solaris) License registration is not
supported on this server.
ANR9637E (Solaris) Cannot access node license lock
Explanation: The REGISTER LICENSE command fails
file: file name.
because the license authorization module cannot be
Explanation: The server was not able to access the found.
System Action: Server operation continues; licensing
System Action: The license function fails. command.
User Response: Examine the file specification User Response: The license authorization file is
displayed and ensure that the file attributes will allow required for formal licensing for the Sun Solaris server.
the server to access the file. The location of the file is The file is delivered when the server is purchased, but
it is not available in the product service stream or with

ANR9638W (Windows NT) • ANR9641W (Solaris)
demonstration copies of the server. If you have function that requires the shared library will be
purchased the server, contact your service inoperative.
representative for assistance in resolving this problem.
User Response: Ensure that the shared library is
accessible. If the problem persists, contact your service
ANR9638W (Windows NT) License registration is representative.
not supported on this server.
Explanation: The REGISTER LICENSE command fails ANR9640E (Solaris) Unable to load procedure
because the license authorization module cannot be address from shared library shared library
found. license module.
System Action: Server operation continues; licensing Explanation: The server module is unable to load the
terms are not changed by the REGISTER LICENSE address of a routine in the indicated shared library for
command. license loading.
User Response: The license authorization file is System Action: Server operation continues, but the
required for formal licensing for the Windows NT function that requires the shared library will be
server. The file is delivered when the product is inoperative.
purchased, but it is not available in the product service
stream or with demonstration copies of the server. If
accessible. If the problem persists, contact your
you have purchased the server, contact your service
customer service representative.
representative for assistance in resolving this problem.
ANR9641W (HP-UX) One or more EVALUATION

ANR9639W (HP-UX) Unable to load shared library
LICENSES will expire on expiration date.
shared library.
Explanation: Although you are running with a
Explanation: The server module is unable to load the
purchased version of the server, there are one or more
indicated shared library.
licenses registered that will expire on the date specified.
System Action: Server operation continues, but the This is usually the case when you have been using
function that requires the shared library will be evaluation licenses prior to purchasing the product.
inoperative.
User Response: Halt the server and erase the
accessible. If this is an evaluation copy of the server,
nodelock file in the server startup directory. After
then this message is normal for the DSMREG library,
restarting the server, use the REGISTER LICENSE
since the library is only provided with purchased
command to define the licensed features that you have
servers. The server licensing will assume ″Try and Buy″
purchased with your server. These licenses should NOT
mode with sample licensed options for a period of
have an expiration date, so this message should not
time.
appear after re-registering the proper licenses. If this
message persists, contact your service representative.
ANR9639W (Solaris) Unable to load Shared License
File shared library.
ANR9641W (Solaris) One or more EVALUATION
Explanation: The server was unable to loaded the LICENSES will expire on expiration date.
shared library.
functions that require the shared library will be
inoperative.
User Response: Make sure the shared library is command to define the licensed features that you have
accessible/readable. This message is normal for those purchased with your server. These licenses should NOT
servers in the Try and Buy mode. have an expiration date, so this message should not
appear after re-registering the proper licenses. If this
message persists, contact your service representative.
ANR9640E (HP-UX) Unable to load procedure
address from shared library shared
library.
address of a routine in the indicated shared library.

ANR9642E (HP-UX) • ANR9656E (HP-UX)
ANR9642E (HP-UX) The specified license
authorization code (license authorization
code) is invalid.
Explanation: The license authorization code which
you entered using the REGISTER LICENSE command is
ANR9654E (Solaris) Could not open file file name.
invalid.
System Action: No additional licenses are registered.
certificate file specified.
Server operation continues.
User Response: Obtain a valid license authorization
fails.
code and try the command again.
ANR9653E (HP-UX) Unexpected error encountered in
iFor/LS (SystemView License Use
Management) routine license interface
name status=xreported status code.
ANR9655E (HP-UX) Invalid license certificate file:
file name.
operation fails
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, User Response: Examine the file specification entered,
re-boot your AIX system and re-start the server. If this including wildcard characters, to determine if it names
message continues to be issued, contact your service the license certificate file(s) you intended to use. If an
representative. error is found, re-try the command with the corrected
ANR9653E (Solaris) Unexpected error encountered in
iFor/LS (SystemView License Use
Management) routine license interface ANR9655E (Solaris) Invalid license certificate file: file
name status=xreported status code. name.
Explanation: The server encountered an unexpected Explanation: The specified file does not contain valid
error in accessing the SystemView License Use license certificate information.
System Action: The server license monitoring ignores the contents of the file.
operation fails
User Response: The SystemView License Use including wildcard characters, to determine if it names
Management product is installed during normal AIX the license certificate file(s) you intended to use. If an
server installation. Check to make sure that server was error is found, re-try the command with the corrected
installed correctly. If the installation was successful, specification. If an error cannot be found, contact your
re-boot your AIX system and re-start the server. If this service representative.
message continues to be issued, contact your service
representative.
ANR9656E (HP-UX) Cannot access node license lock
file: file name.
ANR9654E (HP-UX) Could not open file file name.
Explanation: The server could not open the license specified file. The node lock file contains licensing
certificate file specified. information for the server.
System Action: The license registration command System Action: The license function fails.
fails.
User Response: Examine the file specification
User Response: Examine the file specification entered, displayed and ensure that the file attributes will allow
including wildcard characters, to determine if it names the server to access the file. The location of the file is

ANR9656E (Solaris) • ANR9680W (HP-UX)
ANR9679W Command: Unable to locate file file name.
environment variable. Re-specify the DSMSERV_DIR Explanation: The specified file cannot be found. Note:
environment variable if this specification is in error. PREPARE assumes that the volume formatting program
Also ensure that there is sufficient space on the drive (dsmfmt), is located in the same directory as the server
specified for the file. If the problem persists after these executable file.
representative.
file names in the plan file:
v For the server executable the default is
ANR9656E (Solaris) Cannot access node license lock /usr/tivoli/tsm/server/bin/dsmserv.
file: file name.
v For the volume formatting program the default is
Explanation: The server was not able to access the /usr/tivoli/tsm/server/bin/dsmfmt.
System Action: The license function fails.
User Response: Examine the file specification ANR9679W (Windows NT) Command: Unable to
displayed and ensure that the file attributes will allow locate file file name.
Explanation: The specified file cannot be found.
or in the directory specified by the DSMSERV_DIR System Action: PREPARE uses the following default
environment variable. Re-specify the DSMSERV_DIR file names in the plan file:
environment variable if this specification is in error. v For the server executable the default is
Also ensure that there is sufficient space on the drive c:\prograx1\tivoli\tsm\server\dsmserv.
corrections have been made, contact your service User Response: Determine why file does not exist;
representative. create if necessary.
ANR9677E Failed to allocate memory for shared ANR9680W Command: Could not obtain AIX logical
memory communications. Error: error volume information for volume name
text. while building stanza recovery plan stanza
name.
Explanation: An error has occurred when attempting
to get memory for the shared communications option. Explanation: This volume is defined to the server but
PREPARE can not obtain AIX logical volume
System Action: Shared memory communications will information for it from the AIX Object Data Manager
not be activated. (ODM).
ANR9678E Failed to allocate message queue for the included in the recovery plan stanza.
shared memory communications Error:
error text. User Response: This message should be preceded by
another error message which contains the ODM error
Explanation: An error has occurred when attempting code.
to get memory for the shared communications option.
System Action: Shared memory communications will ANR9680W (HP-UX) Command: Could not obtain
not be activated. logical volume information for volume
name while building stanza recovery plan
ANR9678W (Windows NT) File name used for server stanza name.
executable. A server is currently running Explanation: This volume is defined to the server but
as a service. PREPARE can not obtain logical volume information
Explanation: The name of the executable used when for it.
the server is running as a service cannot be used in the System Action: The entry for the volume is not
plan file. included in the recovery plan stanza.
System Action: PREPARE uses file name identified in User Response: This message should be preceded by
the message within the plan file and generation of the another error message which contains an error code.
plan file continues.

ANR9680W (S/390) • ANR9682E (S/390)
ANR9680W (S/390) Command: Catalog information ANR9681W (S/390) Command: Volume file name not
cannot be obtained for file ’file name’. found while building stanza recovery
plan stanza name.
Explanation: Catalog information cannot be obtained
for the file specified in the message. DRM does not Explanation: This volume is defined to the server but
support creation of JCL for a file that is not catalogued. does not exist. The device class associated with the
System Action: The stanzas, where JCL is created, for
this file will not contain volume or unit information. System Action: The entry for the volume is not
included in the recovery plan stanza.
User Response: Catalog the file.
ANR9680W (Solaris) Command: Could not obtain
logical volume information for volume
name while building stanza recovery plan ANR9681W (Windows NT) Command: Volume file
stanza name. name not found while building stanza
recovery plan stanza name.
Explanation: This volume is defined to the server but
PREPARE can not obtain logical volume information Explanation: This volume is defined to the server but
for it. does not exist. The device class associated with the
included in the recovery plan stanza. System Action: The entry for the volume is not
included in the recovery plan stanza.
User Response: This message should be preceded by
another error message which contains an error code. User Response: Determine why file does not exist;
ANR9680W (Windows NT) Unable to locate path for
component in registry. ANR9682E Command: Generated file name too long.
Length of directory or prefix 'prefix' plus
Explanation: The path to the component could not be
'name' exceeds maximum characters
found in the registry.
characters.
Explanation: The file name generated is too long. The
path names in the plan file:
v For the components installation directory the default
is c:\prograx1\tivoli\tsm\server\ System Action: The recovery plan file was not
created.
v For the administrative command line client the
default is c:\prograx1\tivoli\tsm\baclient\ User Response: Reissue the command specifying a
v For the disk formatting utility the default is valid prefix. The following commands are used to
c:\prograx1\tivoli\tsm\utils\ specify the prefix:
v SET DRMPLANPREFIX
User Response: Determine why path does not exist;
install components if necessary. v SET DRMINSTRPREFIX
v PREPARE
ANR9681W Command: Volume file name not found
while building stanza recovery plan stanza ANR9682E (S/390) Command: Generated file name too
name. long. Length of directory or prefix
’prefix’ plus ’name’ exceeds maximum
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. Explanation: The file name generated is too long. The
included in the recovery plan stanza. System Action: The recovery plan file was not
created.
User Response: Determine why the file does not exist;
create it if necessary. User Response: Reissue the command specifying a
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE

ANR9682E (Windows NT) • ANR9685E (S/390)
ANR9682E (Windows NT) Command: Generated file
name too long. Length of directory or v PREPARE
prefix ’prefix’ plus ’name’ exceeds
maximum characters characters. ANR9684E Command: Cannot generate server
Explanation: The file name generated is too long. The options file name.
maximum valid length is shown in the message. Explanation: A failure occurred generating the server
System Action: The recovery plan file was not options file name.
created. System Action: Recovery plan file not created.
User Response: Reissue the command specifying a User Response: See accompanying messages for more
valid prefix. The following commands are used to information.
specify the prefix:
v SET DRMPLANPREFIX
ANR9684E (S/390) Command: Cannot generate fully
v SET DRMINSTRPREFIX qualified file name for ’name’.
v PREPARE
Explanation: A failure occurred creating the specified
file name.
ANR9683E Command: Cannot generate fully
qualified file name for 'name'. System Action: Recovery plan file not created.
Explanation: A failure occurred expanding the User Response: Reissue the command specifying a
specified file name. valid prefix. The following commands are used to
specify the prefix:
System Action: Recovery plan file not created. v SET DRMPLANPREFIX
User Response: Reissue the command specifying a v SET DRMINSTRPREFIX
valid prefix. The following commands are used to v PREPARE
specify the prefix:
v SET DRMPLANPREFIX
ANR9684E (Windows NT) Command: Cannot generate
v SET DRMINSTRPREFIX server options file name.
v PREPARE
Explanation: A failure occurred generating the server
options file name.
ANR9683W (S/390) Command: Cannot generate fully
qualified file name for ’name’. Prepare System Action: Recovery plan file not created.
will substitute file name ’default name’. User Response: See accompanying messages for more
Explanation: The fully qualified name for the volume information.
history or device configuration file specified in the
message could not be determined. Either the volume ANR9685E Command: Cannot generate a volume
history or device configuration file specified in the plan history file name.
file does not exist or some other error has occurred.
Explanation: A failure occurred generating the volume
System Action: Recovery plan file was created using history file name.
the substitute name.
volume history or device configuration file has been User Response: See accompanying messages for more
backed up. information.
ANR9683E (Windows NT) Command: Cannot generate ANR9685E (S/390) Command: Catalog information
fully qualified file name for ’name’. cannot be found for options file ’file
name’.
Explanation: A failure occurred expanding the
specified file name. Explanation: The options file name specified in the
message is not cataloged. The options file must be
System Action: Recovery plan file not created. cataloged.
User Response: Reissue the command specifying a System Action: The recovery plan file was not
valid prefix. The following commands are used to created.
specify the prefix:
User Response: Catalog the options file.
v SET DRMPLANPREFIX

ANR9685E (Windows NT) • ANR9716E
ANR9685E (Windows NT) Command: Cannot generate ANR9711E Unrecognized argument ’argument’.
a volume history file name.
Explanation: The specified argument is not recognized
Explanation: A failure occurred generating the volume as one that is supported by the label utility program.
history file name.
System Action: The program is halted.
User Response: Retry the label utility program with
User Response: See accompanying messages for more the correct argument syntax.
information.
ANR9712E Argument has invalid value ’argument’.
ANR9686E Command: Cannot generate a device
Explanation: The value specified for the given
argument is not valid.
User Response: Retry the label utility program with
the correct argument syntax.
information.
ANR9713E Only one library can be specified.
Explanation: Only one library can be specified in the
ANR9686E (Windows NT) Command: Cannot generate
argument list for the label utility program.
a device configuration file name.
configuration file name. User Response: Retry the label utility program with
the correct argument syntax.
ANR9714E No drives were specified.
information.
Explanation: At least one drive must be specified for
use by the label utility (DSMLABEL) program.
ANR9690W (S/390) Command: Cannot obtain help file
name. System Action: The program is halted.
Explanation: Help file name cannot be obtained. User Response: Retry the label utility program with
HLPAMENG will not be included in the the correct argument syntax.
START.SERVER stanza of the plan file.
System Action: Processing continues. ANR9715E Error starting label activity for drive
drive name.
Explanation: The label utility is unable to start its
activity for the given drive.
ANR9691W (S/390) Command: Cannot obtain image
file name. System Action: The program is halted.
Explanation: Image file name cannot be obtained. User Response: Increase the number of allowed
IMAGES will not be included in the START.SERVER threads or processes in the system, then retry the
stanza of the plan file. operation.
ANR9716E Device ’library name’ is not accessible, or
is not recognized as a supported library
type.
ANR9710E Insufficient memory to continue
Explanation: The device specified for the library
operations.
cannot be accessed or is not recognized as a supported
Explanation: There is not enough memory to operate device.
the label utility program.
User Response: Retry the operation, specifying a valid
User Response: Provide more memory for the supported library.
program to use.

System Action: The program waits for the volume
ANR9717E Element address element address is not
name to be entered.
valid for drive ’drive name’.
User Response: Mount a new volume, then type a
Explanation: The specified element address does not
volume name for it and press ENTER; or, if you want
represent a valid drive location in the associated library.
to quit the program, press ENTER without entering a
System Action: The program is halted. volume name.
User Response: Retry the operation, specifying a valid
element address for the drive. ANR9723I Insert side A of a new volume in drive
’drive name’, then enter the name
(1-maximum length characters) to be used
ANR9718E Device ’drive name’ is not recognized as a
for its label; or just press ENTER to quit
supported drive type.
this program:
Explanation: The device specified for the drive is not
Explanation: The program prompts for a new volume
recognized as a supported device.
to be mounted in the given drive so that a label can be
System Action: The program is halted. written to it.
User Response: Retry the operation, specifying a valid System Action: The program waits for the volume
supported drive. name to be entered.
User Response: Mount side A of a new volume, then
ANR9719E Too many drives were specified. type a volume name for it and press ENTER; or, if you
want to quit the program, press ENTER without
Explanation: The number of drives specified on the entering a volume name.
command line exceeds the limits of the program.
System Action: The program is halted. ANR9724I Flip the volume in drive ’drive name’ to
User Response: Retry the operation, specifying only side B, then press ENTER.
up to the maximum number of supported drives. The Explanation: The program prompts for a two-sided
program can be invoked with the -help argument to volume to be flipped so that its second side can be
determine this maximum value. labeled.
System Action: The program waits for the ENTER key
ANR9720I Volume ’volume name’ was labeled to be pressed.
successfully using drive ’drive name’.
User Response: Flip the volume in the drive, and
Explanation: The volume is successfully labeled. press ENTER.
System Action: The program continues operation.
User Response: None. ANR9725E The volume in drive ’drive name’ is
already labeled (volume name).
ANR9721E ’Volume name’ is not a valid volume Explanation: The volume in the specified drive cannot
name. be labeled because it already contains a valid label with
the given name.
Explanation: The specified string is not a valid
volume name. System Action: The volume is not labeled.
System Action: The program prompts for a new User Response: If an overwrite of the existing label
volume name. with a new label is desired, restart the DSMLABEL
utility program by using the -overwrite argument.
User Response: Enter a volume name that is within
the length constraints for the media type being labeled,
and which contains only alphanumeric characters. ANR9726E I/O error writing label for volume
’volume name’ in drive ’drive name’.
ANR9722I Insert a new volume in drive ’drive Explanation: An I/O error occurs while attempting to
name’, then enter the name (1-maximum write the label for the specified volume in the given
length characters) to be used for its label; drive.
or just press ENTER to quit this System Action: The volume is not labeled.
program:
User Response: Ensure that the volume is not write
Explanation: The program prompts for a new volume protected, the drive is powered on and ready, and the
to be mounted in the given drive so that a label can be device parameter has the correct value.
written to it.

ANR9727E Media fault detected on volume ’volume
name to be entered.
name’ in drive ’drive name’.
User Response: Insert a new volume into the
Explanation: A media fault condition is detected for
entry/exit port, then type a volume name for it and
the specified volume in the given drive.
press ENTER; or, if you want to quit the program,
System Action: The volume is not labeled. press ENTER without entering a volume name.
User Response: Remove the volume from use, since
the media is questionable. If the media in question ANR9732I Insert a new volume in the entry/exit
requires formatting, such as an unformatted optical port of library ’library device name’ with
disk, retry the operation by starting the program with side A facing up, then enter the name
the '-format' argument. (1-maximum length characters) to be used
this program:
ANR9728E Error ejecting volume from drive ’drive
name’. Explanation: The program prompts for a new volume
to be mounted in the entry/exit port of the given
Explanation: An error occurs while ejecting the
library so that a label can be written to it.
volume from the given drive.
System Action: All further activity on the given drive
name to be entered.
is suspended.
User Response: Insert a new volume into the
User Response: Ensure that the drive is in proper
entry/exit port, then type a volume name for it and
operating condition before resuming its use.
press ENTER; or, if you want to quit the program,
press ENTER without entering a volume name.
ANR9729E I/O error formatting volume ’volume
name’ in drive ’drive name’.
ANR9733I Insert a new volume in drive ’drive name’
Explanation: An I/O error occurs while attempting to of library ’library device name’, then enter
format the media for the specified volume in the given the name (1-maximum length characters)
drive. to be used for its label; or just press
ENTER to quit this program:
System Action: The volume is not labeled.
User Response: Ensure that the volume is not write to be mounted in the given drive so that a label can be
protected, that the drive is powered on and ready, and written to it.
that the media is not damaged.
name to be entered.
ANR9730I Manual intervention required for library
device ’library device name’. User Response: Mount a new volume, close the
library access door, and then type a volume name for it
Explanation: The specified library device requires and press ENTER; or, if you want to quit the program,
manual intervention before it can be accessed for press ENTER without entering a volume name.
normal operations.
System Action: The operation will be retried ANR9734I Insert side A of a new volume in drive
periodically until either the required action is ’drive name’ of library ’library device
performed or a timeout occurs. name’, then enter the name (1-maximum
User Response: If the library has an access door, make length characters) to be used for its label;
sure it is in the closed position. If it has a cartridge or just press ENTER to quit this
carousel, make sure the carousel is installed. program:
ANR9731I Insert a new volume into the entry/exit to be mounted in the given drive so that a label can be
port of library ’library device name’, then written to it.
enter the name (1-maximum length System Action: The program waits for the volume
characters) to be used for its label; or name to be entered.
just press ENTER to quit this program:
User Response: Mount side A of a new volume, close
Explanation: The program prompts for a new volume the library access door, and then type a volume name
to be mounted in the entry/exit port of the given for it and press ENTER; or, if you want to quit the
library so that a label can be written to it. program, press ENTER without entering a volume
name.

ANR9735I Enter the name (1-maximum length ANR9739I Initializing library device ’library device
characters) for the next volume to label name’.
in library ’library device name’; or just
Explanation: The specified library device is being
press ENTER to quit this program:
initialized for use by the labeling utility program.
Explanation: The program prompts for the name of
System Action: The library device is prepared for use.
the next volume to be labeled in the given library.
name to be entered.
ANR9740E Volume ’volume name’ is not in the
User Response: Type the name for the next volume to
INSERT category.
be labeled and then press ENTER; or, if you want to
quit the program, press ENTER without entering a Explanation: The specified volume cannot be labeled
volume name. because it is not in the library’s “insert” category. This
restriction is provided as a safeguard against labeling
volumes that are in use, and possibly destroying valid
ANR9736E An I/O error occurred while accessing
data.
library device ’library device name’.
System Action: The volume is not labeled.
Explanation: An attempted I/O operation for the
given library failed. User Response: If you are sure the volume contains
no valid data, it can be removed from the library and
System Action: If the error is noncritical, operation
then reinserted with the library’s convenience I/O
continues; otherwise, the program is halted.
station. This will cause the volume’s category code to
User Response: Ensure that the library device is be changed to the INSERT category, and thus allow the
powered on and ready, any access doors are closed, the labeling operation to work.
device parameter has the correct value, and then retry
the operation that was in progress when the error
ANR9741E Drives ’drive name’ and ’drive name’
occurred.
cannot use the same element address.
Explanation: The element addresses specified for the
ANR9737I Remove the volume from drive ’drive
given drives are the same. This is not allowed, since the
name’ in library ’library device name’, then
element address is the only way in which the robot can
press ENTER.
distinguish between different drives in a SCSI library.
Explanation: All activity associated with the volume
System Action: The program is stopped.
in the given drive is complete, so it should be removed.
User Response: Restart the program, providing valid
System Action: The program waits until the ENTER
and unique element addresses. Appropriate values can
key is pressed.
be determined with the worksheets in Administrator’s
User Response: Remove the volume from the Guide.
specified drive, then close the library access door and
press ENTER.
ANR9742E The element address for drive ’drive
name’ is missing or invalid.
ANR9738I Remove the volume from the entry/exit
Explanation: The element address value for the
port of library ’library device name’, then
specified drive is omitted, or an illegal value has been
press ENTER.
provided.
Explanation: All activity associated with the volume
System Action: The program is stopped.
in the entry/exit port is complete, so it should be
removed. User Response: Restart the program, providing a
valid element address. Appropriate values can be
System Action: The program waits until the ENTER
determined with the worksheets in Administrator’s
key is pressed.
Guide.
User Response: Remove the volume from the
entry/exit port, and press ENTER.
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.

User Response: None. 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.
ANR9744E Volume ’volume name’ is not present in
library ’library name’.
ANR9749I Insert a new volume into slot with
Explanation: The specified volume is not present in
element number ’slot element address’ of
the given library, so it cannot be labeled.
library ’library device name’ with side A
System Action: Labeling activity continues for other facing up, then enter the name
volumes. (1-maximum length characters) to be used
User Response: Insert the volume into the library, this program:
then retry the operation.
to be inserted into the slot with the specified element
ANR9745E Only one trace argument is allowed. number so that a label can be written to it. For the slot
Explanation: More than one trace argument has been and element number diagram of your library, refer to
encountered, but only one is allowed. the documentation provided with the current PTF level
or refer to the Installing the Server and Administrative
System Action: The program is halted. Client manual for your release and platform.
User Response: Retry the program, specifying at most System Action: The program waits for the volume
one trace argument. name to be entered.
User Response: Insert side A of a new volume, close
ANR9746E Unable to open trace file ’file name’. the library access door, type a volume name for it, and
Explanation: An error occurs while opening the press ENTER; or, if you want to quit the program,
specified file for writing trace data. press ENTER without entering a volume name.

ANR9750I Remove the volume from slot with
User Response: Retry the program, specifying a valid element number ’slot element address’ in
file name for the trace file. library ’library device name’, then press
ENTER.
ANR9747I Unable to write to trace file. Explanation: All activity associated with the volume
Explanation: An error occurs while writing data to the in the given slot with the specified element number is
trace file. complete, so it should be removed. For the slot and
element number diagram of your library, refer to the
System Action: The program continues, but trace data documentation provided with the current PTF level or
may be lost. refer to the Administrator’s Guide for your release and
platform.
User Response: Make sure the disk that contains the
trace file is not full or defective and then retry the System Action: The program waits until the ENTER
operation. key is pressed.
User Response: Remove the volume from the
ANR9748I Insert a new volume into slot with specified slot, close the library access door, and press
element number ’slot element address’ of ENTER.
library ’library device name’, then enter
the name (1-maximum length characters)
to be used for its label; or just press ANR9751E The volume in drive ’drive name’ is not
ENTER to quit this program: compatible with the drive.
Explanation: The program prompts for a new volume Explanation: The volume cannot be used in the drive.
to be inserted into the given slot with the specified It is most likely an outdated media type that the drive
element number so that a label can be written to it. For cannot write.
the slot and element number diagram of your library, System Action: The volume is not labeled.
refer to the documentation provided with the current
PTF level or refer to the Administrator’s Guide for your User Response: Remove the volume; replace it with a
release and platform. different type known to work in the drive, or press
ENTER to end the program.
name to be entered.
User Response: Insert a new volume, close the library

ANR9752E Could not access drive ’drive name’. It ANR9757E ACS drive id ACS drive id is not valid
may be in use by another application. for drive ’drive name’.
Explanation: The specified drive cannot be accessed. 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, User Response: Retry the operation, specifying a valid
then retry the operation. drive id for the drive.
ANR9753E Skipping slot element address ’slot ANR9758W Error mounting volume ’volume name’.
element address’, which has no barcode.
Explanation: An error occurs while mounting the
Explanation: The cartridge in the indicated slot will volume to the drive. This may not be an error since the
not be labeled, since it does not have a valid barcode. volume or drive maybe in use or locked in a shared
environment.
System Action: The program attempts to label the
next cartridge. System Action: The specified volume is bypassed for
labeling.
User Response: Examine the cartridge to see if it has a
barcode. Add a barcode if required. User Response: Ensure that the volume is not locked
or in use if label is required.
ANR9754I Barcode of element slot element address,
’hardware barcode string’, exceeds maximum ANR9759E unsuccessful ACSAPI response,
length characters in length. status=acs status.
Explanation: A barcode is encountered that was Explanation: The ACSLS library api responded with
longer than a valid volume name. an unsuccessful status as indicated.
System Action: The barcode is not considered valid System Action: Depends on the ACS api for labeling,
and will not be used for the server process. the process may continue as the error may not be a
problem.
User Response: Replace the cartridge’s barcode with
one that is supported by the library and whose number User Response: If the label process terminates, contact
of characters does not exceed the maximum length. your ACS System Administrator and perform ACSLS
library problem determination.
ANR9755E There are no barcodes available.
ANR9760I Wait and monitor the ACSSA console
Explanation: The hardware did not return any valid
message to remove volume volume id
barcode data for any cartridge.
from CAP.
System Action: The program terminates without
Explanation: The specified volume is about to put into
attempting to label any cartridges.
CAP for removal. Monitor the ACSSA console and
User Response: Make sure the hardware supports removed the volume after it has been placed into the
barcodes, or that barcode labels have been affixed to CAP as indicated in the ACSSA message.
the cartridges.
User Response: Monitor the ACSSA console and wait.
ANR9756I No volumes were found.
Explanation: No volumes are found in the library.
ANR9773E Hardware configuration error in library
This means that in a 349x ATL, no volumes were found
library name: number of drives drives,
in the insert category (xFF00), and that in a SCSI
number of storage slots storage slots.
autochanger, no cartridges were loaded into the library.
Explanation: The library device retuned a count of
System Action: The program terminates normally.
zero for either the drives or the slots. The drives may
User Response: Insert cartridges into the library. For a have not yet been configured to the operating system,
349x ATL, this may involve changing the category of or to the library. The library must have at least one
previously inserted cartridges to be relabeled. 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. library manager is up and operational. Once the server
is verified to be operational, retry the operation.
ANR9774W Volume volume name should be freed of
data as soon as possible. ANR9779E Unable to acquire a drive for volume
volume name from the library manager.
Explanation: The server has received an indication
from the 3995 that the indicated volume is out of spare Explanation: The library manager was unable to
sectors for re-allocation. Spare sectors are reserved to assign a drive to the library client. There are a couple
take the place of sectors that experience I/O problems. of situations that can cause this error.
The re-allocation can take place on either a read or v All drives are currently allocated to other library
write. clients or the library manager.
System Action: The indicated volume is marked v The request for a specific drive cannot be satisfied.
read-only by the server. This can occur if a drive on the library client side is
marked offline or is currently busy with another
User Response: A MOVE DATA command should be
process.
used as soon as possible to move the data from this
cartridge to other cartridges in the library. This v A communication error occurred during the request
cartridge should NOT be marked read-write again to mount a volume.
through the UPDATE VOLUME command. v The requested volume was not present in the library
manager’s inventory
ANR9775E Error while writing on volume volume System Action: None.
name (RC=internal code).
User Response: Verify that a drive is available on the
Explanation: An I/O error has occurred while writing library manager side and the drive is currently not
on the specified volume. 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
User Response: Ensure that the 3995 volume is a lower mount retention value can free up drives.
accessible and that the media is usable. Diagnostics
may have to be run on the 3995 with the specified
ANR9780E Volume volume name is not mounted in
volume. If the problem persists, contact your service
drive from the library drive name.
representative and provide the internal code values
from this message. The internal code is returned to the Explanation: A communication error occurred while
server from the OS/2 operating system. dismount the volume.
ANR9776I File file name is being erased and
User Response: Verify the library manager is up and
deleted. Data erasure may take several
operational. Verify that the library manager and library
minutes.
client can communicate using command routing.
Explanation: A file is being deleted from an optical
library cartridge. The file is deleted when a LAN3995
ANR9781E Volser volume name was not found to be
device class volume is deleted. File deletion includes
mounted on the library manager.
erasure of data. The erasure process can take several
minutes to complete. Explanation: According to the library manager the
requested volume is no longer mounted. The can
System Action: The operation continues.
occurred if the library manager forced the volume to be
User Response: None. dismounted because of a communication error.
ANR9778E Unable to establish a communication
User Response: Verify that the volume has been
session with either the primary library
dismounted.
manager or the secondary library
manager.
ANR9782E Primary Library Manager primary library
Explanation: The requested operation required that a
manager name is NOT defined as a
communication session be established with a library
server.
manager. Both library managers were found to be
unavailable at this time. Explanation: The primary library manager server has
not be defined to this server.
User Response: Verify the primary or secondary

User Response: Define the server to this server using
the DEFINE SERVER command.
defined - the primary library manager
not defined.
ANR9783E Primary Library Manager does not
Explanation: The designated library is not defined
contain a valid value.
because the primary library manager is not defined as a
Explanation: The primary library manager server has server to this server.
not be defined to this server.
User Response: Define the server to this server using
User Response: Define the server to this server using the DEFINE SERVER command.
the DEFINE SERVER command.
ANR9784E Secondary Library Manager secondary defined - the secondary library manager
library manager name is NOT defined as a not defined.
server.
Explanation: The designated library is not defined
Explanation: The secondary library manager server because the secondary library manager is not defined
name has not be defined to this server. as a server to this server.
System Action: None. System Action: The command is not processed.
User Response: Define the server to this server using User Response: Define the server to this server using
the DEFINE SERVER command. the DEFINE SERVER command.
ANR9785E Drive drive name, is not defined on the ANR9790W Request to mount volume Volume Name
library manager. for library client Library Client Name
failed.
Explanation: A drive is being defined that does not
exist or is being managed by the library manager. Explanation: A library client requested a volume to be
mount by the library manager, which in turn failed.
User Response: Verify drive name with the library
manager. User Response: Verify the status of all drives are
currently online and not in use by other library clients
or the library manager itself. Free up drive resources as
ANR9786E A communication error has occurred. needed.
Operation ending.
Explanation: A communication error occurred. ANR9791I Volume Volume Name in library Library
System Action: None. Name ownership is changing from
Current volume owner to New Volume
User Response: Verify the library manager is up and owner.
operational. Verify that the library manager and library
client can communicate using command routing. Explanation: A library client requested a volume to be
mount by the library manager, which in turn failed.
ANR9787E The owner name specified is not System Action: None.

defined to this server. User Response: Verify the status of all drives are
Explanation: A command was issued specifying currently online and not in use by other library clients
ownership of a volume. The name of the owner given or the library manager itself. Free up drive resources as
was not defined to this server. needed.

ANR9792E Library Library Name on library manager
User Response: Define the server to this server using Library Manager Name is currently not
the DEFINE SERVER command. being shared.
Explanation: A define library command attempted to
define a shared library that was not being shared by
the library manager.

ANR9793I • ANR9803W (Windows NT)
User Response: Verify the library on the library
ANR9797E Command: Drive mapping for drive drive
manager is being shared. If the library is not being
name is not defined in library library
shared, update the library shared status to yes.
name on storage agent storage agent name.
Explanation: The designated drive map has not been
ANR9793I process name in library library name-
defined for the given drive in the given library on the
CANCEL PENDING.
given storage agent.
process on the server. The command was started, but User Response: Reissue the command using a
the process was canceled by an administrator. different drive name. If appropriate, define the drive
before retrying the command.
being terminated.
ANR9798E Command: One or more paths are still
defined for drive drive name in library
library name.
ANR9794E Unable to load the RSM dynamic link
library dynamic link library.
because there are still paths defined for it.
indicated dynamic link library.
User Response: Delete all paths for the drive, and
function that requires the dynamic link library will be
inoperative.
ANR9799E Command: Library Library Name is
User Response: Ensure that the installed Windows
currently not being shared.
version supports RSM. Ensure that the Removable
Storage Manager is installed and the system DLL is Explanation: The command attempted to perform an
accessible. operation that is not allowed unless the library is
allowed to be shared .
ANR9795E Command: Invalid storage agent name System Action: None.
storage agent name.
User Response: Verify the library on the library
Explanation: The designated storage agent name is manager is being shared. If the library is not being
invalid; either it contains too many characters, or some shared, update the library shared parameter to yes.
of the characters are invalid.
System Action: The command is not processed. ANR9801I (Windows NT) ANR9801: Ready for
operations.
User Response: Reissue the command using a valid
storage agent name. Explanation: The device driver has successfully
initialized and is ready to accept requests from the
server.
ANR9796E Command: Drive mapping is already
defined for drive drive name in library System Action: Processing continues.
library name on storage agent storage agent
name.
Explanation: The designated drive mapping cannot be
ANR9803W (Windows NT) ANR9803: ERROR!
defined because it has already been defined for the
Insufficient free memory to initialize
specified drive, library, and storage agent.
driver.
Explanation: The server device driver is unable to
User Response: If you want to define an additional initialize due to an inability to acquire dynamic storage.
drive mapping, reissue the command with a different
System Action: Processing continues. The device
drive name.
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
NT and the device drivers you want to use.

ANR9810I (Windows NT) • ANR9902W
ANR9810I (Windows NT) ANR9810: SCSI Tape
Device Driver Initializing... User Response: Ensure that there is sufficient disk
space and that the accounting file is not marked as
Explanation: The server SCSI tape device driver has
read-only.
been invoked by the system and is initializing.
ANR9901W Attention -- Accounting records could
User Response: None. not be written to the file: filespec.
Explanation: The server detects an error while trying
ANR9820I (Windows NT) ANR9820: SCSI to write an accounting record.
Autochanger Device Driver Initializing...
Explanation: The server SCSI automatic changer
User Response: Ensure that there is sufficient disk
device driver has been invoked by the system and is
initializing.
read-only.
User Response: None. ANR9901W (HP-UX) Attention -- Accounting records
could not be written to the file: file name.
ANR9900W Attention -- Accounting records could Explanation: The server detects an error while trying
not be written to the file: filespec. to write an accounting record.
Explanation: The server detects an error while trying System Action: Server processing continues.
to open the accounting file.
System Action: Server processing continues. space and that the accounting file is not marked as
read-only.
read-only. ANR9901W (Solaris) Attention -- Accounting records
could not be written to the file: file name.
ANR9900W (HP-UX) Attention -- Accounting records Explanation: The server detects an error while trying
could not be written to the file: file name. to write an accounting record.
System Action: Server processing continues, but no space and that the accounting file is not marked as
accounting records are written. read-only.
space and that the accounting file is not marked as ANR9901W (Windows NT) Attention -- Accounting
read-only. records could not be written to the file:
filespec.
ANR9900W (Solaris) Attention -- Accounting records Explanation: The server detects an error while trying
could not be written to the file: file name. to write an accounting record.
System Action: Server processing continues, but no space and that the accounting file is not marked as
accounting records are written. read-only.
space and that the accounting file is not marked as ANR9902W Attention -- Accounting records could
read-only. not be written to the file: filespec.
ANR9900W (Windows NT) Attention -- Accounting to close the accounting file.
records could not be written to the file:
filespec.
User Response: Ensure that sufficient disk space is
available and that the accounting file is not marked as
read-only.

ANR9902W (HP-UX) • ANR9953E (S/390)
ANR9902W (HP-UX) Attention -- Accounting records ANR9951W (S/390) Attention -- License option could
could not be written to the file: file name. not be written to the file: filespec.
Explanation: The server detects an error while trying Explanation: The server detects an error while trying
to close the accounting file. to write to the options file.
System Action: Server processing continues. System Action: Server processing continues.
User Response: Ensure that there is sufficient disk User Response: Ensure that sufficient disk space is
space and that the accounting file is not marked as available and that the options file is not marked as
read-only. read-only.
ANR9902W (Solaris) Attention -- Accounting records ANR9951W (Windows NT) Attention -- License
could not be written to the file: file name. option could not be written to the file:
filespec.
to close the accounting file. Explanation: The server detects an error while trying
to close the options file.
space and that the accounting file is not marked as User Response: Ensure that there is sufficient disk
read-only. space and that the options file is not marked as
read-only.
ANR9902W (Windows NT) Attention -- Accounting
records could not be written to the file: ANR9952E (S/390) Command: Invalid value specified
filespec. for licensed storage capacity - value.
Explanation: The server detects an error while trying Explanation: The specified command has been issued
to close the accounting file. with an invalid value.
System Action: Server processing continues. System Action: Server operation continues, but the
space and that the accounting file is not marked as User Response: Reissue the command using a valid
read-only. value.
ANR9950W (S/390) Attention -- License option could ANR9952E (Windows NT) Command: Invalid value
not be written to the file: filespec. specified for licensed storage capacity -
value.
to write to the options file. Explanation: The specified command has been issued
User Response: Ensure that sufficient disk space is
available and that the options file is not marked as
read-only. User Response: Issue the command using a valid
value.
ANR9950W (Windows NT) Attention -- License
option could not be written to the file: ANR9953E (S/390) Command: Invalid value specified
filespec. for number of licensed clients - value.
Explanation: The server detects an error while trying Explanation: The specified command has been issued
to write to the options file. with an invalid value.
System Action: Server processing continues. System Action: Server operation continues, but the
space and that the options file is not marked as User Response: Reissue the command using a valid
read-only. value.

ANR9953E (Windows NT) • ANR9960W (Windows NT)
ANR9953E (Windows NT) Command: Invalid value ANR9957W (Windows NT) One or more
specified for number of licensed clients EVALUATION LICENSES will expire on
- value. expiration date.
Explanation: The specified command has been issued Explanation: Although you are running with a
with an invalid value. 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
User Response: Issue the command using a valid NT.
value.
ANR9954S (S/390) The server is not licensed for use
on this system.
Explanation: DFSMS/MVS Feature server is not command to define the licensed features that you have
defined as licensed for this system to use in purchased with your NT server. These licenses should
SYS1.PARMLIB member IGDDFPKG. NOT have an expiration date, so this message should
not appear after re-registering the proper licenses. If
System Action: The server operation ends. this message persists, contact your service
User Response: If you are licensed to use the server, representative.
update the IGDDFPKG member in SYS1.PARMLIB to
set the correct value that enables the server. Either start ANR9958W (Windows NT) Node entry node name
task DFSMSPKG or reIPL. was removed from this server’s
definition in Active Directory.
ANR9955W (Windows NT) Unable to load dynamic Explanation: In response to a REMOVE NODE
link library dynamic link library. command, the requested backup-archive node has been
Explanation: The server module is unable to load the removed from this server’s definition in Active
indicated dynamic link library. Directory.
System Action: Server operation continues, but the System Action: None.
function that requires the dynamic link library will be User Response: None.
inoperative.
User Response: Ensure that the dynamic link library ANR9959W (Windows NT) Node entry node name
directories are accessible. If this is an evaluation copy was not removed from this server’s
of the server, then this message is normal for the definition in Active Directory.
DSMREG library, since the library is only provided
with purchased NT servers. The server licensing will Explanation: In response to a REMOVE NODE
assume ″Try and Buy″ mode with sample licensed command, the requested backup-archive node has not
options for a period of time. been removed from this server’s definition in Active
Directory.
ANR9956E (Windows NT) Unable to load procedure System Action: None.

address from dynamic link library
User Response: To remove a node entry in the Active
dynamic link library.
Directory, the option ″adunregister″ has to be set to
Explanation: The server module is unable to load the ″yes″ in the server options file. A domain controller
address of a routine in the indicated dynamic link must also be available. The Active Directory
library. Configuration wizard can be used to manually update
the server definition.
function that requires the dynamic link library will be
inoperative. ANR9960W (Windows NT) Node entry node name has
been added to this server’s definition in
User Response: Ensure that the dynamic link library Active Directory.
directories are accessible. If the problem persists,
contact you service representative. 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.

ANR9965W (Windows NT) Could not create the
inital node list in Active Directory for
ANR9961W (Windows NT) Node entry node name has this server.
not been added to this server’s
Explanation: At startup the server’s registered nodes
could not be added to the server definition in Active
Explanation: The requested backup-archive node entry Directory
has not been added to this server’s definition in Active
Directory in response to a REGISTER NODE command.
User Response: Try using the option ″adsetdc″ in the
server options file to explicitly provide the TCP/IP
User Response: To register a node entry in the Active address of the domain controller where Active
Directory, the option ″adregister″ has to be set to ″yes″ Directory is located.
in the server options file. A domain controller must also
be available. The Active Directory Configuration wizard
ANR9966I (Windows NT) NodeName node name.
can be used to manually update the server definition.
Explanation: The NodeName is registered in Active
Directory.
ANR9962W (Windows NT) Node entry node name
was renamed in this server’s definition System Action: Server operation continues.
in Active Directory.
command, the requested backup-archive node has been
ANR9967I (Windows NT) Server server name was
renamed to the new name shown.
defined in Active Directory.
Explanation: The server is registered in Active
User Response: None. Directory.
ANR9963W (Windows NT) Node entry node name
was not renamed in this server’s
ANR9968I (Windows NT) Success accessing Active
Directory.
command, the requested backup-archive node has not
been renamed. Explanation: Active Directory Server could be
contacted.
System Action:
User Response: To Rename Node in the Active
Directory, the options ″adregister″ and ″adunregister″ User Response: None.
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 ANR9969E (Windows NT) Unable to open volume
manually update the server definition. volume name. The most likely reason is
that another TSM server is running and
has the volume allocated.
ANR9964W (Windows NT) Failed to access Active
Directory. RC: return code Explanation: Only one TSM server can have a given
volume open at a time.
Explanation: Could not communicate with an Active
Directory server. System Action: The TSM server does not start.
System Action: Server operation continues. User Response: See if another TSM server is already
running and if so use it.
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 ANR9970W (Windows NT) Unable to get socket
Directory is located. name for the IPX/SPX driver.Reason
Code Reason code.
way of IPX/SPX. IPX/SPX has rejected a request for a
IPX socket name.

ANR9999D
IPX/SPX protocol.
User Response: Ensure that IPX/SPX is operational on
your system by using the network control panel applet.
If IPX/SPX is not started, issue the HALT command to
stop the server, and then restart the server.
ANR9999D (component)(code):(text)
Explanation: This message carries diagnostic text
relating to a server process or algorithm. This
information is intended for reporting processing
exceptions and other non-standard situations that occur
on the ADSM server. The (component), (code), and
(text) will vary depending upon the cause of the
message and the server process or algorithm that issues
the message.
System Action: Server processing may or may not
continue depending upon the cause of this message.
Use the SET CONTEXTMESSAGING command and set
the message context reporting to ON to receive
additional information when the server issues this
message. See the Administrator’s Reference.
have been displayed before and/or after this message
and correct any problems, if possible. If the cause of
this message can not be determined or resolved, contact
your support representative. If you contact your
should be reported.

Chapter 4. Client Events Logged to Server (ANE4000—4999)
ANE4000E Error processing ’filespace-name’: file ANE4005E Error processing ’filespace
space does not exist namepath-namefile-name’: file not found
Explanation: The specified file space (domain) is Explanation: The file being processed for backup,
incorrect or does not exist on the workstation. archive or migrate no longer exists on the client.
System Action: Processing stopped. Another process deletes the file before it can be backed
User Response: Retry the operation specifying an up, archived or migrated by TSM.
existing domain (drive letter or file system name). System Action: File skipped.
ANE4001E Error processing ’filespace-name’: file
space not known to server ANE4006E Error processing ’filespace
Explanation: The number defining the correspondence namepath-namefile-name’: directory path
between drive letter or file (domain name) and volume not found
label is not known to the server. Explanation: You specified an incorrect directory path.
System Action: Processing stopped. System Action: Processing stopped.
User Response: Report the program error to your User Response: Correct the syntax specified on the
service representative. call and retry the operation.
ANE4002E Error processing ’filespace-name’: volume ANE4007E Error processing ’filespace

label does not exist namepath-namefile-name’: access to the
Explanation: The selected drive does not have a label. object is denied
System Action: TSM is unable to do the requested Explanation: Access to the specified file or directory is
operation without a drive or label entered. denied. You tried to read from or write to a file and
User Response: If the drive is a floppy drive, place a you do not have access permission for either the file or
disk with a volume label in it and retry the operation. the directory.
If the disk is a hard drive, ensure the drive has a System Action: Processing stopped.
volume label, and retry the operation. User Response: Ensure that you specified the correct
file or directory name, correct the permissions, or
specify a new location.
ANE4003E Error processing ’filespace-name’:
duplicate volume label encountered
Explanation: The selected drive has a duplicate ANE4008E Error processing ’filespace
volume label. Because TSM uses the volume label to namepath-namefile-name’: file is
keep track of backup/archive information, it cannot temporarily unavailable
back up or archive files from a drive with a duplicate Explanation: File is temporarily unavailable.
volume label. System Action: File skipped.
System Action: TSM cannot select the drive. User Response: Check and see if file is locked by
User Response: If the volume needs to be available to other process. If not, retry the command.
the system, exit TSM, and assign a volume label to the
drive. Restart TSM and retry the operation.
ANE4009E Error processing ’filespace
namepath-namefile-name’: disk full
ANE4004E Error processing ’filespace condition
namepath-namefile-name’: destination file Explanation: No more files can be restored or
or directory is write locked retrieved because the destination disk is full.
Explanation: The file or directory being restored or System Action: Processing stopped.
retrieved from the server cannot be written to because User Response: Free up disk space, or restore or
the destination is write locked. Another operation retrieve the file to another disk.
might have the file open and will not allow it to be
updated.
System Action: File skipped.
namepath-namefile-name’: stale NFS handle
User Response: Either determine which operation has
Explanation: An NFS file system becomes stale.
the file write locked, or restore the file to another name
System Action: File system skipped.
or location.
User Response: Check the NFS mounted filesystem.

User Response: Stop the operation that is running the
file and retry the operation, or restore or retrieve the
namepath-namefile-name’: no file handles
file to a different name or directory.
available
Explanation: All file handles for your system are
currently in use. No more are available. ANE4017E Error processing ’filespace
System Action: Processing stopped. namepath-namefile-name’: too many
User Response: Either free some file handles by symbolic links were detected while
ending other processes, or modify your system setup to resolving name
allow for more files to be open at the same time. Explanation: While trying to resolve the file name, too
many symbolic links were found.
User Response: Ensure that you do not have a
namepath-namefile-name’: file already
looping symbolic link for the file.
exists
Explanation: The file being restored or retrieved
exists. ANE4018E Error processing ’filespace
System Action: File is replaced or skipped depending namepath-namefile-name’: file name too
on client options. long
User Response: None. Explanation: The file name specified is too long to be
handled by TSM.
System Action: File is skipped.
User Response: See the appropriate Using the
namepath-namefile-name’: invalid file
Backup-Archive Client book for the particular operating
handle
system, for the file names that are handled by TSM.
Explanation: An internal system error occurred. A file
operation failed because an invalid file handle was
passed. ANE4019E Error processing ’filespace
System Action: Processing stopped. namepath-namefile-name’: file system is
User Response: Report the problem to your system locked by system
administrator, and then retry the operation. Explanation: File system cannot be accessed because it
is locked by the system.
System Action: TSM cannot complete the operation.
User Response: See your system administrator.
namepath-namefile-name’: unknown system
error (error-code) encountered. Program
ending. ANE4020E Error processing ’filespace
Explanation: An unknown and unexpected error-code namepath-namefile-name’: format unknown
occurred within the client program. This is a Explanation: TSM tried to restore or retrieve a file, but
programming failure and the client program ends. it had an unknown format.
System Action: Processing stopped. System Action: File skipped.
User Response: Retry the operation. If the problem User Response: See your system administrator.
continues, see your administrator.

ANE4015E Error processing ’filespace namepath-namefile-name’: file system not
namepath-namefile-name’: unexpected error ready
(error-code) encountered Explanation: The file system/drive was not ready for
Explanation: An unexpected error occurred. This access.
might be a low-level system or communication error System Action: Processing stopped.
that TSM cannot handle or recover from. User Response: Ensure that the drive is available to
System Action: Processing stopped. TSM, and then retry the operation.
User Response: Retry the operation. If the problem
continues, determine where the problem exists. See
your system administrator for further help. ANE4022E Error processing ’filespace
namepath-namefile-name’: file system is
invalid
ANE4016E Error processing ’filespace Explanation: The drive was not available for access. A
namepath-namefile-name’: file is being directory exists that does not have either a '.' or '..'
executed; write permission denied entry.
Explanation: The current file cannot be opened to System Action: Processing stopped.
write to because it is currently being run by another User Response: Ensure that the drive is operational,
operation. and then retry the operation. If unsuccessful, have your
System Action: File skipped. service representative check the error log.

ANE4023E Error processing ’filespace ANE4029E Error processing ’filespace
namepath-namefile-name’: file input/output namepath-namefile-name’: unable to build
error a directory path; a file exists with the
Explanation: An error was found while reading from same name asa directory
or writing to the file. Explanation: TSM tried to create a directory path, but
System Action: File skipped. is unable to because a file exists that has the same
User Response: Check your system to ensure that it is name as a directory.
operating properly. For OS/2, run CHKDSK /F for the System Action: Processing stopped.
failing drive which can be found in dsmerror.log. 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.
namepath-namefile-name’: file write error
Explanation: An error was found while writing to the ANE4030E Error processing ’filespace
file. namepath-namefile-name’: disk space limit
System Action: File skipped. for this process reached
User Response: Check your system to ensure that it is Explanation: The disk space allocated for the client
operating properly. owner is full.
System Action: Processing stopped.
User Response: Free up disk space and retry the
restore or retrieve operation.
namepath-namefile-name’: file exceeds user
or system file limit
Explanation: A file being restored or retrieved exceeds ANE4031E Error processing ’filespace
system set limits for this user. namepath-namefile-name’: destination
System Action: File skipped. directory path length exceeds system
User Response: Ensure that the system limits are set maximum
properly. Explanation: The path name specified plus the path
name in the restored file name combine to create a
name whose length exceeds the system maximum.
ANE4026W Error processing ’filespace
namepath-namefile-name’: size of ’file-size’
User Response: Specify a destination path that, when
exceeded the maximum file size limit on
combined, is less than the system maximum.
your system
Explanation: You tried to restore or retrieve a file that
has exceeded the maximum file size limitation on your ANE4032E Error processing ’filespace
system. namepath-namefile-name’: file is not
System Action: TSM cannot restore or retrieve the file. compressed.
User Response: Restore or retrieve this file on a Explanation: A file that was flagged as compressed
system that supports the file size. See your system was not compressed, and the system failed.
administrator. System Action: Processing stopped.
User Response: See your system administrator to
report this problem. This error is a system failure.
ANE4027S Error processing ’filespace
namepath-namefile-name’: internal program
message ’value’ encountered ANE4033E Error processing ’filespace
Explanation: An unexpected catastrophic program namepath-namefile-name’: file compressed
failure occurred, indicated by value. on a different client machine that has
System Action: Processing stopped. more memory
User Response: Retry the operation. If the problem Explanation: You are trying to restore a file that was
continues, see your system administrator or service backed up and compressed on another client
representative. 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.
namepath-namefile-name’: cannot create
System Action: TSM canceled the operation.
file/directory entry
User Response: Obtain a machine with more memory
Explanation: The directory path for files being
and retry the operation.
restored or retrieved cannot be created.
User Response: Ensure that you have the proper
authorization to create the directory for file being
restored or retrieved.
Chapter 4. Client Events Logged to Server (ANE4000—4999) 521

System Action: TSM will not migrate files from this
file system.
User Response: Recall some files, or ask the system
error
administrator to increase the quota for this file system.
Explanation: An unknown error occurred. This might
be a low-level system or communication error that TSM
cannot handle or recover from. ANE4041W Error processing ’filespace
System Action: Processing stopped. namepath-namefile-name’: Out of free
User Response: Retry the operation. If the problem space or inodes in file system filespace
continues, determine where the problem exists. See name to migrate or recall.
your system administrator for further help. 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
ANE4035W Error processing ’filespace
migrated or recalled.
namepath-namefile-name’: file currently
System Action: TSM terminates the current operation
unavailable on server.
for this file system.
User Response: Remove some files in the file system,
is currently not available from the server.
and then run reconciliation. Retry the operation.
System Action: TSM cannot restore or retrieve the file.
determine why the file is unavailable and then try your ANE4042E Object name ’filespace
operation again. namepath-namefile-name’ contains one or
more unrecognized characters and is not
valid.
ANE4036E An error occurred saving the registry
Explanation: The filename, directory name, or volume
key.
label syntax is incorrect.
Explanation: The active registry key cannot be saved.
System Action: Registry backup operation terminates.
User Response: You need to check the disk for errors.
ANE4900W Schedule ’schedule name’ has opened a

ANE4037E File ’file-namefile-namefile-name’ changed
new session with the server.
during processing. File skipped.
Explanation: A scheduled event ended due to a
Explanation: The specified file-name was skipped
connection failure. The scheduled event had to be
during backup, archive, or migrate because it was
restarted outside of its normal start-up window to
changing during the attempt to process it.
continue the operation.
System Action: TSM skipped the file.
System Action: Be advised that there are multiple
User Response: If you want the file backed up,
sessions associated with the scheduled event.
archived, or migrated retry the operation. If it fails,
determine why the file is being changed. For more
information on backing up, archiving, or migrating
changing files, see your system administrator. ANE4987E Error processing ’filespace namepath-name
file-name’: the object is in use by another
process
ANE4038E An error occurred processing file system
Explanation: Access to the specified file or directory is
’filespace name’.
denied. You tried to read from or write to a file and
Explanation: File system ’filespace name’ is corrupted
you do not have access permission for either the file or
or contains one or more corrupted directories and
the directory.
System Action: File system is skipped.
User Response: Ensure that you specified the correct
User Response: Check your system to ensure that it is
operating properly. For the Windows environment, run
CHKDSK utility for the failing drive. More information
about corrupted directories can be found in
dsmerror.log. ANE4988W File ’filespace namepath-namefile-name’ is
currently unavailable on server and has
been skipped.
namepath-namefile-name’: file system
is currently not available from the TSM server.
filespace name has exceeded its space
management quota.
User Response: Try to restore or retrieve after the file
Explanation: TSM detects that the file system has
was made available on the server. See your system
exceeded its quota. No more data can be migrated out
administrator.
of this file system.

ANE4999E Unable to log message ’message number’
to server: message too long.
Explanation: The message text and inserts were too
large to send to the server in the available internal
buffer.
System Action: Refer to the local client error log for
more information
Chapter 4. Client Events Logged to Server (ANE4000—4999) 523

Part 3. Client Messages
This section contains a listing of messages for the following:
v TSM administrative clients
v Application program interface clients
v Backup–archive and Tivoli Space Manager (HSM client) workstations
The messages are documented in ascending numeric order.
This section also contains Diagnosis, Modification, or Tuning Information. Some of

these messages include information about the TSM error log that you can use
when working with your service representative.
ANS0201E Invalid parameter was found. ANS0205E Unable to open error log file.
Explanation: The system encountered an internal Explanation: The system is unable to open the error
program error due to an invalid parameter. log file.
System Action: The system returns to the calling System Action: The system returns to the calling
procedure. procedure.
User Response: Ask your service representative to User Response: Verify the DSMI_LOG value and
check the error log. access permission. On the AS/400 platform, verify the
value specified for ERRORLOGNAME in the API
options file.
ANS0202E Not authorized to restore the other
node’s data.
ANS0206E The log file cannot be written to.
Explanation: The client is not authorized to restore the
other node's data. Explanation: There was an error writing to the log
file.
System Action: The system returns to the calling
procedure. System Action: The system returns to the calling
procedure.
User Response: Get authorization from the other
node. User Response: Verify the DSMI_LOG value and
access permission. on the AS/400 platform, verify the
ANS0203E The objName field has no leading
options file.
directory separator.
Explanation: The objName field does not have a
ANS0207E The log file name was not specified.
leading directory separator.
Explanation: The system is unable to open the error
log file.
procedure.
User Response: Correct the value for the objName.
procedure.
User Response: Verify the DSMI_LOG value and
ANS0204E Wildcards are not allowed in the
access permission. On the AS/400 platform, verify the
objName directory path.
Explanation: Wildcards are not allowed in the options file.
objName directory path.
System Action: The system returns to the calling ANS0208E The TCP/IP WINSOCK.DLL file cannot
procedure. be found.
User Response: Correct the value for the objName. Explanation: The TCP/IP WINSOCK.DLL file cannot
be found.

ANS0215E There is no server policy information.
User Response: Verify your TCP/IP installation.
Explanation: The server did not respond with the
policy information.
ANS0209E An error occurred while loading a
library.
procedure.
Explanation: An error occurred while loading a
User Response: Verify the server policy definitions.
library. The TCP/IP DLL load failed.
ANS0216E The dataBlk bufferLen value is zero.
Explanation: The value for the dataBlk bufferLen is
zero.
ANS0210E The TCP/IP load function failed.
Explanation: An error occurred while locating a procedure.
function. The TCP/IP load function failed.
User Response: Provide a non-zero value for the
System Action: Processing stopped. bufferLen.

ANS0217E The dataBlk bufferPtr is NULL.
ANS0211E The object name pointer is NULL. Explanation: There is no value provided for the
dataBlk bufferPtr.
Explanation: There is no value provided for the object
name pointer. System Action: The system returns to the calling
procedure.
procedure. User Response: Provide an address for the bufferPtr.
User Response: Provide an address for the
dsmObjName structure. ANS0218E The objType is invalid.
Explanation: The value for the objType is invalid.
ANS0212E The data block pointer is NULL.
Explanation: There is no value provided for the data procedure.
block pointer.
User Response: The value for dsmObjName.objType
System Action: The system returns to the calling must be:
procedure. DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for
User Response: Provide an address for the DataBlk Backup, or
structure. DSM_OBJ_FILE for Archive.
ANS0213E The object attribute pointer is NULL. ANS0219E The dsmEndTxn vote is invalid.
Explanation: There is no value provided for the object Explanation: The dsmEndTxn vote is invalid.
attribute pointer.
System Action: The system returns to the calling procedure.
procedure.
User Response: The vote must be
User Response: Provide an address for the ObjAttr DSM_VOTE_COMMIT or DSM_VOTE_ABORT.
structure.
ANS0220E An invalid option was found during
ANS0214E There is no server session information. option parsing.
Explanation: The server did not respond with the Explanation: An invalid option was found.
session information.
procedure.
User Response: Verify the options in dsm.opt,
User Response: Verify the server status. dsm.sys, and the options string. Check the error log for
more details about the error. on the AS/400 platform,
verify the options in *LIB/QOPTTSM(APIOPT).

ANS0221E There was an error in the TSM API ANS0226E The object owner is invalid.
internals.
Explanation: The object owner must be either the root
Explanation: The system encountered an error in the user, or the object owner must be the same as the
API internals. session owner.
User Response: Shut down the process and retry the User Response: Verify the session owner and object
operation. Verify that any previous dsmInit calls were owner.
cleaned up and terminated by a dsmTerminate call. If
the problem continues, contact your system
ANS0227E The dsmBindMC sendType is invalid.
administrator or service representative.
Explanation: The dsmBindMC sendType is invalid.
ANS0222E The repository type is invalid. System Action: The system returns to the calling
procedure.
Explanation: The repository type is invalid.
User Response: The sendType must be one of the
following:
procedure.
stBackup
User Response: For dsmDeleteFS the repository must
stArchive
be one of the following:
stBackupMountWait
v DSM_ARCHIVE_REP
stArchiveMountWait
v DSM_BACKUP_REP
v DSM_REPOS_ALL.
ANS0228E The dsmSendObj sendType is invalid.
ANS0223E Filespace name should start with the Explanation: The dsmSendObj sendType is invalid.
directory delimiter. System Action: The system returns to the calling
Explanation: The filespace name is invalid. procedure.
System Action: The system returns to the calling User Response: The sendType must be one of the
procedure. following:
stBackup
User Response: Filespace name should start with the
directory delimiter. stArchive
stBackupMountWait
ANS0224E The object name is either an empty stArchiveMountWait
string or has no leading delimiter.
Explanation: The object name is invalid because of an ANS0229E The dsmDeleteObj delType is invalid.
empty string or there is no leading delimiter. Explanation: The dsmDeleteObj delType is invalid.
User Response: Verify the format of the dsmObjName User Response: The delType must be dtBackup or
full path. dtArchive.
ANS0225E Low level qualifier of the object name ANS0230E The query Backup objState is invalid.
should start with the directory delimiter.
Explanation: The query Backup objState is invalid.
Explanation: The low level qualifier for the object
name is invalid. System Action: The system returns to the calling
procedure.
procedure. User Response: The qryBackupData.objState must be
one of the following:
User Response: Start the low level qualifier of the
object name with the directory delimiter. DSM_ACTIVE
DSM_INACTIVE
DSM_ANY_MATCH
Part 3. Client Messages 527

ANS0231E The management class name was not ANS0236E On dsmInit, the owner is not allowed
found. when PASSWORDACCESS=generate.
Explanation: A query or send operation is unable to Explanation: PASSWORDACCESS=generate
find the management class name. establishes a session with the current login user as the
owner.
procedure.
User Response: Verify the management class name.
User Response: When using
PASSWORDACCESS=generate, set clientOwnerNameP
ANS0232E The drive letter is not an alphabetic
to NULL.
character.
Explanation: The drive letter is not an alphabetic
ANS0237E On dsmInit, the node is not allowed
character. This return code is valid on Microsoft
when PASSWORDACCESS=generate.
Windows only.
Explanation: PASSWORDACCESS=generate
establishes a session with the current hostname as the
procedure.
node.
User Response: Verify that the drive designation is an
alphabetic character. The referenced field is
procedure.
dsmDosFSAttrib.driveLetter.
PASSWORDACCESS=generate, set clientNodeNameP to
ANS0233E The Register Filespace name is NULL.
NULL.
Explanation: There is no value provided for the
Register Filespace name.
ANS0238E The sequence of calls is invalid.
Explanation: The sequence of calls is invalid.
procedure.
User Response: Provide a filespace name on
procedure.
dsmRegisterFS.
User Response: Verify the transaction call sequence.
ANS0234E The new password value is NULL or
blank. ANS0239E On dsmSendObj, wildcards are not
allowed for the objName.
Explanation: There is no value provided for new
password. Explanation: On dsmSendObj, wildcards are not
allowed for the objName.
procedure.
User Response: Provide a new password on
dsmChangePW. User Response: Provide a fs, hl, and ll on the
dsmObjName.
ANS0235E The old password value is NULL or
blank. ANS0240E The filespace to delete/set access cannot
be found.
Explanation: There is no value provided for old
password. Explanation: The filespace to delete cannot be found.
User Response: Provide an old password on User Response: Verify the filespace name.
dsmChangePW.
ANS0241E On dsmSendObj, dsmDeleteObj, or
dsmUpdateFS the filespace is not
registered.
Explanation: On dsmSendObj, dsmDeleteObj, or
dsmUpdateFS, the filespace is not registered.

System Action: The system returns to the calling The maximum number of objects is exceeded.
procedure.
User Response: Verify the filespace name. procedure.
User Response: Issue dsmEndTxn and start a new
ANS0242W On dsmRegisterFS the filespace is transaction session.
already registered.
Explanation: On dsmRegisterFS the filespace is ANS0247E The backup or archive object is
already registered. excluded from processing.
System Action: The system returns to the calling Explanation: The backup or archive object is excluded
procedure. from processing.
User Response: Verify the filespace name. System Action: The system returns to the calling
procedure.
ANS0243E On dsmBeginGetData the objID is User Response: Verify the objName and Exclude lists.
NULL.
Explanation: On dsmBeginGetData, the objID is ANS0248E The backup object does not have a copy
NULL. group.
System Action: The system returns to the calling Explanation: The backup object does not have a copy
procedure. group.
User Response: Verify the following: System Action: The system returns to the calling
The dsmGetList is not NULL. procedure.
Each objID is not NULL. User Response: Verify server policy definitions.
The dsmGetList numObjId is not zero.
ANS0249E The archive object does not have a copy
ANS0244E On dsmInit the caller’s API version is group.
different than the TSM library version. Explanation: The archive object does not have a copy
Explanation: On dsmInit the caller's API version has a group.
higher value than the TSM library version. System Action: The system returns to the calling
procedure. User Response: Verify server policy definitions.
User Response: Install the latest TSM API library and
trusted agent module. ANS0250E Memory used by the TSM API has been
corrupted.
ANS0245E The caller’s structure version is different Explanation: Memory used by the TSM API has been
than the TSM library version. corrupted.
Explanation: The caller's structure version is different System Action: The system returns to the calling
than the TSM library version. procedure.
System Action: The system returns to the calling User Response: Retry the operation. If the problem
procedure. continues, contact your system administrator or service
User Response: Ensure that the stVersion field is set representative.
with the value in the header file. Recompile the
application with the latest header files. ANS0251E The sendObj Archive description is too
long.
ANS0246E Issue dsmEndTxn and then begin a new Explanation: The sendObj Archive description is too
transaction session. long.
Explanation: This transaction must be ended and a System Action: The system returns to the calling
new one must be started due to one of the following procedure.
reasons:
User Response: The sndArchiveData.descr string must
The destination changed.
be less than or equal to DSM_MAX_DESCR_LENGTH.
The byte limit is exceeded

equal to DSM_MAX_FSINFO_LENGTH.
ANS0252E The sendObj ObjAttr.objInfo is too
long.
ANS0258I On dsmGetNextQObj or dsmGetData
Explanation: The sendObj ObjAttr.objInfo is too long.
there is more available data.
Explanation: On dsmGetNextQObj or dsmGetData
procedure.
User Response: The objInfo field must be less than or
equal to DSM_MAX_OBJINFO_LENGTH.
procedure.
User Response: Call the function again.
ANS0253E The sendObj dsmObjName.hl is too
long.
ANS0259E The dataBlk buffer is too small for the
Explanation: The sendObj dsmObjName.hl is too long.
query response.
Explanation: The dataBlk buffer is too small for the
procedure.
query response.
User Response: The hl field must be less than or
equal to DSM_MAX_HL_LENGTH.
procedure.
User Response: On dsmGetNextQObj ensure that the
ANS0254E The dsmChangePW password is too
dataBlk buffer is at least as big as the query response
long.
structure.
Explanation: The dsmChangePW password is too
long.
ANS0260E An invalid option keyword was found
System Action: The system returns to the calling during option parsing.
procedure.
Explanation: An invalid option keyword was found in
User Response: The password field must be less than the dsmInit configuration file, the option string,
or equal to DSM_MAX_VERIFIER_LENGTH. dsm.sys, or dsm.opt.
ANS0255E The sendObj dsmObjName.fs is too procedure.
long.
User Response: Correct the spelling of the option
Explanation: The sendObj dsmObjName.fs is too long. keywords. Verify that the dsmInit configuration file
only has a subset of the dsm.sys options. Check the
error log for more details about the error.
procedure.
User Response: The fs field must be less than or equal
ANS0261E The configuration file specified on
to DSM_MAX_FS_LENGTH.
dsmInit cannot be opened.
Explanation: The configuration file specified on
ANS0256E The sendObj dsmObjName.ll is too
long.
Explanation: The sendObj dsmObjName.ll is too long.
procedure.
User Response: Verify the file name.
procedure.
User Response: The ll field must be less than or equal
ANS0262E The Include/Exclude definition file was
to DSM_MAX_LL_LENGTH.
not found.
Explanation: The Include/Exclude definition file was
ANS0257E On RegisterFS or UpdateFS the fsAttr’s
not found.
fsInfo is too long.
Explanation: On RegisterFS or UpdateFS the fsAttr's
procedure.
fsInfo is too long.
User Response: Verify the file name on the Inclexcl
option.
procedure.
User Response: The fsInfo field must be less than or

ANS0263E Either the dsm.sys file was not found, or ANS0268E Server problem: Destination not
the Inclexcl file specified in dsm.sys defined.
was not found.
Explanation: Server problem: Destination not defined.
Explanation: Either the dsm.sys file was not found, or
the Inclexcl file specified in dsm.sys was not found.
User Response: Have your service representative
check the error log.
procedure.
User Response: The dsm.sys file must be in the
ANS0269S The structured file data type is
directory referenced by the environment variable
unknown.
DSMI_DIR. Verify the file name on the Inclexcl option
in the dsm.sys file. Explanation: An unknown and unexpected error code
occurred within the client program. The structured file
data type is unknown. This is a programming failure
ANS0264E Only a UNIX root user can execute
and the client program ends.
dsmChangePW or dsmDeleteFS.
Explanation: Only a UNIX root user can execute
dsmChangePW or dsmDeleteFS. User Response: Retry the operation. If the problem
continues, contact your system administrator.
procedure.
ANS0270S The data buffer overflowed.
User Response: Run this program as a root user.
Explanation: The data buffer overflowed. This is a
programming failure and the client program ends.
ANS0265E You must issue dsmBindMC before
dsmSendObj. System Action: Processing stopped.
Explanation: You must issue dsmBindMC before User Response: Retry the operation. If the problem
dsmSendObj. continues, contact your system administrator.
procedure. ANS0271E No more files can be restored or
retrieved since the destination directory
User Response: Modify your program.
is full.
Explanation: No more files can be restored or
ANS0266I The dsmEndTxn vote is ABORT, so
retrieved since the destination directory is full.
check the reason field.
Explanation: After a dsmEndTxn call, the transaction
is aborted by either the server or client with a User Response: Free up disk space, or restore or
DSM_VOTE_ABORT and the reason is returned. retrieve the file to another disk.
procedure. ANS0272I The operation is finished.
User Response: Check the reason field for the code Explanation: The operation is finished.
which explains why the transaction has been aborted.
procedure.
ANS0267E Invalid command line option/value:
’option’ User Response: Proceed with next function call.
Explanation: The option is not valid on this command

line. ANS0273E The trusted agent execution/owner
permissions are invalid.
System Action: Processing stops
Explanation: The trusted agent execution/owner
User Response: Verify that the option and value are permissions are invalid.
not misspelled and are valid with the current
command. System Action: Processing stopped.
User Response: Have your system administrator
check the installation instructions for the client to
ensure that the trusted agent permissions are set
correctly.

ANS0274S Process killed.
User Response: Verify the application sets the
Explanation: Processing stopped. This is a
mountWait value correctly on dsmBeginGetData.
ANS0280E Unable to find Trusted Agent module.
Explanation: TSM was unable to find the TSM Trusted
Agent module in the specified directory. The name of
the TSM Trusted Agent module is dsmtca.
ANS0275S Trusted agent would block the
System Action: TSM ends.
operation.
User Response: Make sure the Trusted Agent module
Explanation: The trusted agent blocks the operation.
is in the directory specified by DSMI_DIR.
This is a programming failure and the client program
ends.
ANS0281E Access denied for dsmapitca.
Explanation: An attempt to access a system function
has been denied.
ANS0276S The area for the include/exclude pattern User Response: Contact your system administrator.
is too small.
Explanation: The area for the include/exclude pattern ANS0282E Password file is not available.
is too small. This is a programming failure and the
client program ends. Explanation: The file containing the stored password
for the specified server-name is unavailable.
continues, contact your system administrator. User Response: The root user must set and store a
new password.
ANS0277S There is no closing bracket in the

pattern. ANS0283E High level qualifier of the object name
Explanation: There is no closing bracket in the
pattern. This is a programming failure and the client Explanation: The high level qualifier for the object
program ends. name is invalid.
System Action: Processing stopped. System Action: The system returns to the calling
procedure.
continues, contact your system administrator. User Response: High level qualifier of the object name
ANS0278S The transaction will be aborted.

ANS0284E The number of objects on
Explanation: The server encountered an error and will dsmBeginGetData exceeds
abort the transaction. DSM_MAX_GET_OBJ |
DSM_MAX_PARTIAL_GET_OBJ.
System Action: The transaction will be aborted. The
reason code is passed on the dsmEndTxn call. Explanation: The number of objects (numObjId)
specified on the dsmBeginGetData call exceeds
User Response: Issue the dsmEndTxn with a vote of
DSM_MAX_GET_OBJ |
DSM_VOTE_COMMIT and examine the reason code.
DSM_MAX_PARTIAL_GET_OBJ.
ANS0279I A file was skipped during a restore
procedure.
operation because the file is off line and
the application has chosen not to wait User Response: Check the number of objects before
for a tape mount. calling dsmBeginGetData. If it is greater than
DSM_MAX_GET_OBJ |
Explanation: A file was skipped during a restore
DSM_MAX_PARTIAL_GET_OBJ, then issue multiple
operation because the file is off line and the application
Get call sequences.
has chosen not to wait for a tape mount.

to find out why your user id is locked.
ANS0285E The update action is invalid.
Explanation: The dsmUpdateFS or dsmUpdateObj
ANS0299E Scheduler cannot be started manually
action is invalid.
because the value of
System Action: The system returns to the calling MANAGEDSERVICES option is
procedure. SCHEDULE.
User Response: Correct the action value. Valid values Explanation: if MANAGEDSERVICES SCHEDULE is
are defined in dsmapitd.h and documented in our indicated in the option file, the TSM scheduler cannot
Using the API book. be started in the traditional manner.
System Action: Scheduler stopped.
ANS0286E The key file is missing.
User Response: If you are not going to use dsmcad to
Explanation: The key file for Tivoli Data Protection manage the schedule anymore, stop dsmcad and
application client for Oracle cannot be found. remove MANAGEDSERVICES option from the option
file.
procedure.
ANS0301E The TSM DLL dsm3270.dll cannot be
User Response: Ensure that you have ordered the
found in the user’s path.
Tivoli Data Protection application client which contains
TDP for Oracle, and install the key file. Explanation: The TSM DLL dsm3270.dll cannot be
found in the user's path.
ANS0287E The key file content is invalid. System Action: Communications link is not
established.
Explanation: The key file content for Tivoli Data
Protection application client for Oracle is invalid. User Response: Make sure that the TSM DLL
dsm3270.dll is in a directory that is included in the
user's path.
procedure.
ANS0302I Successfully done.
Tivoli Data Protection application client which contains
the TDP for Oracle, and install the key file. Explanation: The operation successfully completed.
ANS0296I Encryption key passwords are not the
same. Please try again...
Explanation: TSM found that the encryption key
ANS0304E Unable to generate password because
passwords do not match.
password access is not set to
System Action: You are prompted for the encryption GENERATE.
key password.
Explanation: User issued the Generate Password
User Response: Enter the correct encryption key command, but password access is not set to
password. GENERATE in the options file.
System Action: TSM none.
ANS0297E Error opening specified file.
User Response: Add PASSWORDACCESS
Explanation: The specified file could not be located or GENERATE to your dsm.opt file .
opened.
System Action: Attempts to open file failed. ANS0305E Unable to generate password because no
NAS Node was specified.
User Response: Make sure the file exists.
Explanation: User issued the Generate Password
command with class=NAS, but no NAS node was
ANS0298E Session Rejected: The specified user id
specified.
is currently locked
Explanation: The user id you specified is currently
locked on the server. User Response: Retry the command and use the
-nasnodename option.
System Action: Session was not started.
User Response: Check with your system administrator

ANS0306E Unable to generate password because ANS0316E Unable to use message text file.
Class type is invalid or unknown.
Explanation: The system is unable to use the message
Explanation: User issued the Generate Password text file (dscameng.txt or dsmclientV3.cat for AIX)
command with an invalid or unknown class. because of an invalid header. On the AS/400 platform
this file is QANSAPI/QAANSAMENG(TXT).
User Response: Retry the command and use a
procedure.
supported class type option (class=CLIENT or
class=NAS). User Response: Install the message text file again.
ANS0307I Password generated. ANS0317E Unable to use message text file.

Explanation: User issued the Generate Password Explanation: The system is unable to use the message
command and it was successful. txt file (dscameng.txt or dsmclientV3.cat for AIX)
because of an invalid control record. On the AS/400
platform this file is QANSAPI/QAANSAMENG(TXT).
procedure.
ANS0308E Remote operation failed to start on
User Response: Install the message text file again.
obj-name. Status: status reason: reason
Explanation: The request to start a remote operation
ANS0318E Invalid value for DATEFORMAT
has failed for the indicated node and filespace. The
specified.
status and the reason for the failure are shown.
Explanation: An invalid value is specified for
System Action: TSM ended the current operation.
DATEFORMAT.
User Response: Contact your system administrator for
more information.
procedure.
User Response: Specify a valid value.
ANS309E Remote operation failed to start on
obj-name. Status: status
ANS0319E Invalid value for TIMEFORMAT
Explanation: The request to start a remote operation
specified.
has failed for the indicated node and filespace. The
status of the failure is shown. Explanation: An invalid value is specified for
TIMEFORMAT.
procedure.
more information.
ANS0315E Unable to open message text file.
ANS0320E Invalid value for NUMBERFORMAT
Explanation: The system is unable to open the
specified.
message txt file (dscameng.txt or dsmclientV3.cat for
AIX). On the AS/400 platform this file is Explanation: An invalid value is specified for
QANSAPI/QAANSAMENG(TXT). NUMBERFORMAT.
User Response: Verify that the dscameng.txt file is in User Response: Specify a valid value.
the directory pointed to by DSMI_DIR. For AIX, verify
that the dsmclientV3.cat file has a symbolic link to
ANS0321E msg parameter for dsmRCMsg is a
/usr/lib/nls/msg/<locale>/dsmclientV3.cat .
NULL pointer.
Explanation: The message parameter for dsmRCMsg
is a NULL pointer.
procedure.

User Response: Allocate enough space for the User Response: Try the operation with a different file
message parameter. specification.
ANS0322E no text available for this return code. ANS0328E The specified objects failed the merge
test.
Explanation: The dsmRC parameter for dsmRCMsg is
an unsupported return code. Explanation: The specified objects failed the merge
test, operation cannot complete.
procedure. System Action: The requested operation failed.
User Response: Specify a valid value. User Response: See documentation for the merge test
parameters.
ANS0323E partialObjOffset value for partial object
retrieve is invalid. ANS0330E The dsmSetAccess access Type is
invalid.
Explanation: The partialObjOffset value for partial
object retrieve is invalid. Explanation: The dsmSetAccess accessType is invalid.
User Response: Specify a valid value. User Response: The accessType must be one of the
following:
ANS0324E partialObjLength value for partial object atBackup
retrieve is invalid. atArchive
Explanation: partialObjLength value for partial object
retrieve is invalid. ANS0331E No files have been previously backed
up for this filename/filespace.
procedure. Explanation: You tried to set access to files when no
files for the specified filename, drive or file system
were previously backed up.
ANS0325E Partial Object Retrieve is not supported
on this server. User Response: Ensure that the correct drive or file
system was specified and that files are backed up for
Explanation: The TSM server specified by the user
you to set access.
does not support partial object retrieve.
ANS0332E No files have been previously archived
procedure.
for this filename/filespace.
User Response: Specify a TSM server which supports
Explanation: You tried to set access to files when no
the partial object retrieve function.
were previously archived.
ANS0326E Node has exceeded max tape mounts
allowed.
User Response: Ensure that the correct drive or file
Explanation: All the tape mount points for this node
system was specified and that files are archived for you
are in use.
to set access.
procedure.
ANS0333E Unknown Remote Mover type
User Response: Increase the number of allowed tape
Explanation: The specified Remote Mover type is
mounts for this node on the server.
unknown.
ANS0327E A duplicate object was found, operation
cannot complete. User Response: Contact your system administrator for
more information.
Explanation: A duplicate object was found, operation
cannot complete.
System Action: The requested operation failed.

ANS0334E An Operation for the requested node ANS0340E A target storage pool does not have the
and filespace is already in progress. correct data format for the given node
type.
Explanation: A request has been made to use a data
mover to perform an operation for the indicated node Explanation: none
and filespace. Since an operation for this node and
filespace is already in progress, the new operation
cannot be performed. User Response: Contact your system administrator for
more information.
User Response: Retry the operation at a later time.
ANS0341E No associated data mover is defined for
the given node.
ANS0335E System resource in use
Explanation: none
Explanation: A required resource is in use by another
command or process.
more information.
ANS0342E The CRC received from the Server does
ANS0336E Server plugin communication error not match the CRC calculated by the
client.
Explanation: Communication between a server plugin
module and a NAS filer failed. Explanation: The server sent a CRC for a buffer. The
client calculated a CRC for the same buffer. These did
not match. The mismatch indicates a communication
User Response: Contact your system administrator for failure.
more information.
System Action: In some cases, the client can indicate
the failure to the server and retry the operation.
ANS0337E Server plugin detected unsupported
User Response: Check the trace log for additional
NAS filer operating system.
information and retry the operation. If the problem
Explanation: A plugin module detected that a NAS persists, contact your system administrator.
filer is running an unsupported operating system or
operating system level.
ANS0343E An invalid operation was attempted on
System Action: TSM ended the current operation. a group leader or group member.
User Response: Contact your system administrator for Explanation: An invalid operation was attempted on a
more information. logical group.
System Action: The current operation stops.
ANS0338E An invalid operation was attempted on
User Response: Retry a valid operation.
a node
Explanation: The operation is not valid.
ANS0344E Cannot Send data with a zero byte
System Action: TSM ended the current operation. sizeEstimate.
User Response: Contact your system administrator for Explanation: You cannot send data for an object with
more information. size estimate = 0.
ANS0339E The specified target storage pool is not procedure.
defined.
User Response: Set size estimate greater than 0 in
Explanation: The storage pool is not defined. dsmSendObj.

ANS0400E License file could not be opened.
more information. Explanation: The license file was not found, or could
not be opened because of permissions or the file is
corrupted.

System Action: The system returns to the calling User Response: Contact your system administrator.
procedure.
User Response: Check permissions on file. See if the ANS0411E Oracle passed null file name
license file is in the correct place.
Explanation: Null filename passed by Oracle.
ANS0401E Read failure on the license file.
procedure.
Explanation: The license file was not found, or could
User Response: Contact your system administrator.
not be opened because of permissions, or the file is
corrupted.
ANS0412E Wrong data block size
procedure. Explanation: Wrong Block Size
User Response: Check permissions on file. See if the System Action: The system returns to the calling
license file is in the correct place. procedure.
ANS0402E Write failure on the license file.
Explanation: The license file was not found, or could ANS0413E Object exists
corrupted. Explanation: Backup or Restore Object already exists.
User Response: Check permissions on file. See if User Response: If backing up an object, be sure to
license file is in the correct place. generate a unique object name.
ANS0403E Data in the license file is not in a valid ANS0414E Not same Oracle handle
format. Explanation: The handle passed from Oracle is not the
Explanation: The license file is not valid. same handle that TSM passed back.
User Response: User needs to obtain a new license. User Response: Contact your system administrator.
ANS0404E The checksum in the license file does ANS0415E End of file reached
not match the licenseregistration string. Explanation: End of file reached.
Explanation: The registration string is not valid. System Action: The system returns to the calling
procedure. User Response: None
User Response: User needs to obtain a new license.
ANS0416E Wrong Read State
ANS0405E This is an expired try and buy license. Explanation: The operation must be in READ state.
Explanation: The registration string is not valid. System Action: The system returns to the calling
procedure. User Response: Contact your service representative.
ANS0417E Runtime API version is outdated
ANS0410E Oracle passed invalid mode Explanation: Runtime API is lower than compile time
Explanation: Invalid mode passed by Oracle. API.
User Response: Use the WHAT command to find out

the compile time API level. Obtain the same or higher environment variables in the NOTES.INI file to avoid
level of API library. using the problem file. Also check your available disk
space.
ANS0418E Wrong write state
ANS0905S Error getting current working directory.
Explanation: The operation must be in WRITE state.
Explanation: An error occurred while trying to
retrieve the current working directory.
procedure.
System Action: Processing stops.
User Response: Check the LOG.DSM file for any
further details on the specific error. There may be an
ANS0419E Invalid flag passed
error in your operating system since it cannot
Explanation: Invalid flag passed from Oracle. determine your current working directory.

procedure. ANS0907E Error in getting file system information.
User Response: Contact your system administrator. Explanation: An error was encountered when an
attempt was made to obtain the file system information
for the drive on which the Notes database resides.
ANS0900I dsmnotes completed.
Explanation: The dsmnotes command completed
successfully. User Response: Check the drive on which the Notes
database you are processing resides. Be sure that the
System Action: The program completes. volume has a label and your disk is attached. Check
User Response: Not Applicable. the LOG.DSM file for details about the error.
ANS0901S Cannot allocate memory. ANS0908E Error getting database volume label.
Explanation: An attempt was made to allocate Explanation: An error was encountered when an
memory but failed. attempt was made to obtain the volume label of the
drive on which the Notes database resides.
User Response: Check the LOG.DSM file for further
details about the failure. User Response: Check the drive on which the Notes
database you are processing resides. Be sure that the
volume has a label and your disk is attached.
ANS0903E I/O error opening file.
Explanation: An I/O error occurred when an attempt ANS0909E Error in parsing options.
was made to open one of the supporting files (for
example: a trace file or log file). This message does not Explanation: A general parsing error occurred on a
suggest an I/O error in a Notes database. dsmnotes command. Either you entered too many path
names, or a hyphen (-) or an equal (=) sign is missing
System Action: Processing stops. in the option.
User Response: Check all supporting files, including System Action: Processing stops.
the log file, and trace file. Consider updating the
environment variables in the NOTES.INI file to avoid User Response: Check the syntax of the command.
using the problem file, or check access permission on Correct the syntax and reissue the command.
the file.
ANS0910E Invalid option keyword.
ANS0904E I/O error writing to a file. Explanation: An invalid option keyword was specified
Explanation: An I/O error occurred when an attempt on a dsmnotes command.
was made to write to a supporting file like a trace file System Action: Processing stops.
or log file. This message does not suggest an I/O error
in a Notes database. User Response: Identify and correct the invalid
keyword. Then reissue the command.
User Response: Check all supporting files, including
the log file, and trace file. Consider updating the

ANS0912E The specified password is too long. ANS0917E Usage: dsmnotes <actions> <options>
<db pathname>
Explanation: The TSM password you entered is too
long. Explanation: No parameters were specified on the
dsmnotes command. Some parameters are required
such as action parameter and database name parameter.
User Response: If you are resetting a new TSM
password, you need to choose a shorter password. If
you are entering a current TSM password, check that User Response: Refer to the user’s guide of the
the password is correct. If the password is correct but corresponding platform for the correct syntax of your
the problem still occurs, ask your TSM administrator to command, including required parameters. Correct the
reset your password to a new value. If you do this, syntax and reissue the command.
choose a shorter password.
ANS0918E dsmnotes action (1st parm) is
ANS0913E An invalid option value was specified. unrecognized.
Explanation: An invalid value was specified for an Explanation: A syntax error was made on a dsmnotes
option on a dsmnotes command. command. The first parameter on the command is
generally used to identify what kind of action is to be
performed (for example, “INCR” for incremental
User Response: Identify and correct the invalid value. backup), but this first parameter on the command was
Then reissue the dsmnotes command. not recognized as a valid action.
ANS0914E Required keywords are missing.
User Response: Refer to the user’s guide of the
Explanation: One or more required keywords are corresponding platform for the correct command
missing from the dsmnotes command. syntax. Correct the syntax and reissue the command.

ANS0919E Usage: dsmnotes incr <options> <db
User Response: Identify and check the proper syntax pathname>
and provide the missing keywords and values. Then
reissue the dsmnotes command. Explanation: A syntax error occurred on the
incremental backup command.
ANS0915E An invalid date was entered. System Action: Processing stops.
Explanation: An invalid date value was entered. User Response: Refer to the user’s guide of the
Either the syntax of the value was not correct, or an corresponding platform for the correct syntax. Correct
actual value (for example, “45” for month) was invalid. the syntax and reissue the command.
ANS0920E Usage: dsmnotes restore <options> <db
User Response: Identify and correct the invalid date pathname>
value. Refer to the user’s guide of the corresponding
platform for the correct date syntax. Explanation: A syntax error occurred on the
incremental backup command.
ANS0916E An invalid time was entered. System Action: Processing stops.
Explanation: An invalid time value was entered. User Response: Refer to the user’s guide of the
Either the syntax of the value was not correct, or an corresponding platform for the correct syntax. Correct
actual value (for example, “75” for hour) was invalid. the syntax and reissue the command.
ANS0921E Usage: dsmnotes restdel <options> <db
User Response: Identify and correct the invalid date pathname>
value. Refer to the user’s guide of the corresponding
platform for the correct time syntax. Explanation: A syntax error occurred on the restore
deletion stubs command.
corresponding platform for the correct syntax. Correct
the syntax and reissue the command.

ANS0923E Database path name is invalid. ANS0929E User interrupted operation.
Explanation: The given path name does not resolve to Explanation: The user has interrupted the operation
a valid Notes database file name. (for example, by pressing an interrupt key such as
<Ctrl C>).
User Response: Validate that the given path name is
correct. If wildcard symbols are used, refer to the user’s User Response: None
guide of the corresponding platform for the correct
usage of these symbols. Also check for defaulting to the
ANS0930I Database rebuild done.
Notes data directory to ensure that the path name is
not defaulting incorrectly. Explanation: Database rebuild from backup copies of
notes was successfully completed.
ANS0924E Cannot restore to original database. System Action: The program completes successfully.
Explanation: An attempt was made to rebuild a Notes User Response: None.
database from backup copies of notes, but the original
database file was specified as the target database.
ANS0931E Cannot log errors.
Explanation: An attempt was made to initiate error
User Response: Choose an original name for the logging, which includes either opening or creating a
target database. The name cannot belong to an existing LOG.DSM file. The attempt failed.
file.
ANS0925E -days value cannot be negative (OS/2). User Response: Check the LOG.DSM file to see why it
The days value cannot be negative (AIX cannot be opened or created.
and Windows NT)
Explanation: Only a positive number of days can be ANS0932I No matching data on server.
specified. Explanation: An attempt was made to query one or
System Action: Processing stops. more backup copies of notes on the TSM server, but no
copies existed or an attempt was made to merge the
User Response: Either specify a positive number of data notes (documents) from the TSM server into the
days or let the system default to restore all the deleted original database, but no data notes existed.
documents that it can identify.
System Action: The program ends.
ANS0926E Cannot open database. User Response: If you believe that some matching
data should exist on the server, check your database
Explanation: An attempt to open a Notes database path name to ensure that you are using the correct
was unsuccessful. database file name. If the -merge keyword is used, your
database might only have nondata notes (documents).
User Response: Check the LOG.DSM file for more
ANS0933E The days value is invalid.
information about the error. Verify the path name of
your database. If the path name is correct, then verify Explanation: The days value is either negative or
the database itself to ensure that it can be opened greater than 65535.
through the Notes workspace.
ANS0928I Restore of Note(s) done. User Response: Use correct days value.
Explanation: Restoration of one or more notes was

successful. ANS0934E TSM new passwords do not match.
System Action: The program completes successfully. Explanation: An attempt was made to change the
TSM password through the Lotus Notes workspace but
User Response: None. the two new TSM passwords entered did not match.
User Response: Retry the command with matching
new TSM passwords.

the database file through the TSM client.
ANS0935E This Notes database file not on server.
Explanation: Either the given database file was not
ANS0940E Some options are mutually exclusive.
backed up on the server, or the database file space was
removed from the server. Explanation: Some of the options specified are
mutually exclusive. For example:
v For OS/2, the options “-MERGE=NO”, “-TO” and
User Response: Check the name of the database to “-FROMDate” cannot all be specified simultaneously
ensure that it is the correct database, and check the because a new target database may not be operable if
DSM.OPT file to ensure that you are accessing the some documents (such as view and form design
correct TSM server. You can ask the TSM administrator documents) are excluded.
to check the filespaces for your node. A database name Design documents are normally backed up with the
is equivalent to a filespace. initial incremental, and not subsequently modified.
In this situation, allowing the FROMDate option
ANS0936E This action is not allowed on a remote would cause some design documents to be excluded
database. when creating the new database.
v For AIX and Windows NT, the options “-MERGE”
Explanation: The action you tried to perform is not and “-TO” are mutually exclusive because a new
allowed on a database that is not local. target database cannot be specified for a merge.
System Action: Processing stops. System Action: Processing stops.
User Response: If the action is not allowed through User Response: Correct the syntax of the command
the Notes workspace interface, but allowed through the and then reissue the command.
TSM Notes application client command-line interface,
then use the appropriate dsmnotes command. An
alternative is to complete the action on the appropriate ANS0941E Invalid date/time range.
machine. Explanation: An invalid date or time range was given.
For example, the “TO” time is earlier than the “FROM”
ANS0937E Cannot enter new database name (OS/2). time.
Must restore to original database (AIX System Action: Processing stops.
and Windows NT).
User Response: Correct the date or time range and
Explanation: You are not allowed to enter a new rerun the program. Be sure that all year, month, day,
target database name for this restore operation. hour, and minute values are in the correct order and
For OS/2, refer to the dsmnotes restore -FROMDATE are valid values.
option in the user’s guide documentation.
System Action: Processing stops. ANS0942E No notes chosen.
User Response: If your interface is the Notes Explanation: An attempt was made to restore a note
workspace, then replace the database name in the entry or notes, but no notes documents were chosen.
field with blanks. If your interface is a command, then System Action: Processing stops.
do not specify a target (“-TO”) database.
User Response: On the lotus Notes Workspace, select
the notes to be restored by placing a checkmark next to
ANS0938E Database name required. the notes.
Explanation: You are required to enter a database
name. ANS0944E dsmnotes errors occurred.
System Action: Processing stops. Explanation: Errors occurred on one or more
User Response: Enter the database name. databases.
System Action: The program partially completes.
ANS0939I No deletion stubs in database. User Response: Check the LOG.DSM file for further
Explanation: There are no deletion stubs in the given details about the failure.
database.
System Action: The program ends.
User Response: If there are no deletion stubs in the
database to initiate the restore, then you may need to
rebuild the database by restoring the older version of

ANS0947E Error initializing Notes. ANS0953E No license or license expired.
Explanation: Error occurred while initializing the Explanation: You do not have a valid Tivoli Data
Lotus Notes runtime system. Protection application client license or your license has
already expired.
User Response: Check the Lotus Notes environment.
Try to bring up your Notes workspace if you have not User Response: Refer to the user’s guide of the
already done so. Also, check the NOTES.INI file to see corresponding platform or call the IBM sales
if it has the correct setup for the Tivoli Data Protection representatives for license information.
application client. Refer to the user’s guide of the
corresponding platform.
ANS0955E Database IDs do not match.
Explanation: An attempt was made to back up a
ANS0948E Pathname is a directory.
database that has the same path and name as a
Explanation: An attempt was made to restore a single database that is previously backed up to the TSM
Database but the pathname specified was a directory. server. These two databases have the same name, but
they have different database IDs. As a result, they were
treated as two different databases.
User Response: If you want to restore a single
database, make sure your database name ends with a
“.nsf” extension. User Response: Rename the database to be backed up.
If the database that is previously backed up in the TSM
server is no longer needed, ask your TSM administrator
ANS0950E Data on server has an invalid version.
to delete the database’s filespace on the server.
Explanation: Data structure for the application is not
compatible with the data stored on the server.
ANS0956E The TSM password is needed.
Explanation: A TSM password is required.
User Response: Check the user’s software version.
User Response: If the TSM PASSWORDACCESS
ANS0951E Lotus Notes error: error_code occurred.
PROMPT option in the option file is used, you are
Explanation: A Lotus Notes error has occurred but the required to enter the password by using the -adsmpw
Tivoli Data Protection application client was not able to keyword.
translate the error code into a valid Lotus Notes error
If the TSM PASSWORDACCESS GENERATE option is
message.
used, issue the dsmnotes change command with
System Action: Processing stops. appropriate parameters to create a password file. Refer
to the user’s guide of the corresponding platform for
User Response: The supported Lotus Notes version is the correct syntax to use.
4.50 for AIX and NT, or 4.52 or above for OS/2. You
probably have a downlevel Lotus Notes software
installed on your system. Check with your Lotus Notes ANS0957E An operation is already active.
Administrator for assistance.
Explanation: An active restore operation is being
processed.
ANS0952E TSM error: error_code occurred.
Explanation: A TSM error has occurred but the Tivoli
User Response: Wait for the active restore operation
Data Protection application client was not able to
to complete before starting a second one.
translate the error code into a valid TSM error message.
ANS0958E Usage: dsmnotes change -adsmpw=old
User Response: Check with your TSM Administrator -newadsmpw=new
for assistance.
Explanation: The syntax of the dsmnotes change
command is incorrect.
User Response: Use correct syntax. Refer to the user’s
guide of the corresponding platform for the correct
syntax.

ANS0959I TSM password changed. ANS0971E Too few parameters.
Explanation: The TSM password has been changed Explanation: One or more parameters are required.
successfully.
System Action: The program completes successfully.
User Response: None. corresponding platform for the correct number of
parameters. Enter the correct number of parameters
and reissue the command.
ANS0960E Cannot write over data in buffer.
Explanation: An attempt was made to overwrite valid
ANS0972E Too many parameters.
data in the buffer.
Explanation: Too many parameters were passed to the
command.
User Response: Check the integrity of the database by
opening it in the Lotus Notes workspace. If the
database opens successfully, reissue the command. If User Response: Refer to the user’s guide of the
the error is persistent, contact the IBM technical corresponding platform for the correct number of
support. parameters. Enter the correct number of parameters
and reissue the command.
ANS0961E Database not allowed.
ANS0973E Invalid parameter: parameter.
Explanation: A database name is not allowed with
this command. Explanation: An invalid parameter is entered.
User Response: Remove the database name and User Response: Correct the invalid parameter. Reissue
reissue the command. the command.
ANS0962E Filespace not allowed. ANS0974E No log file is specified.

Explanation: A filespace name is not allowed with this Explanation: The Tivoli Data Protection application
command. client’s log file is not entered.
User Response: Remove the filespace name and User Response: Enter a fully qualified Tivoli Data
reissue the command. Protection application client log file, then reissue the
command.
ANS0964E Invalid Notes Build Version.
ANS0975E No log database is specified.
Explanation: A wrong version of Tivoli Data
Protection application client is being used. Explanation: The Lotus Notes log database is not
entered.
User Response: Check the Tivoli Data Protection
application client Readme file to verify if the installed User Response: Enter the Lotus Notes log database
Tivoli Data Protection application client supports the (usually log.nsf). Refer to the user’s guide of the
current version of Lotus Notes on your workstation. corresponding platform for further information.
Uninstall the current version of Tivoli Data Protection
application client. Then reinstall and be sure to select
ANS0976E Error opening the log database DBname.
the correct version of Tivoli Data Protection application
client during the installation. Explanation: The specified log database cannot be
opened.
ANS0970I Processing log file Logname. System Action: Processing stops.
Explanation: The Tivoli Data Protection application User Response: Verify the path name of your log
client’s log file is being processed. database. If the path name is correct, verify the log
database itself to ensure that it can be opened through
System Action: Program continues.
the Notes workspace.

ANS0977E Error getting the mode of log database ANS0982E Error getting log file end time.
DBname.
Explanation: The program is not able to interpret the
Explanation: The program cannot verify that the input last date/time stamp in the TSMConnect Agent’s log
log database is a valid database. file. The last date/time stamp format either does not
match the date/time stamp format of your operating
system, or it is corrupted.
User Response: Verify the path name of your log
database. If the path name is correct, then verify the log
database itself to ensure that it can be opened in the User Response: For consistency reason, the date/time
Notes workspace. stamp format of the log file must match the date/time
stamp format of your operating system. Check the
locale of your operating system to ensure that you have
ANS0978E DBname. is not a Lotus Notes database.
matching date/time stamp formats.
Explanation: An invalid database has been specified.
System Action: Processing stops. ANS0983W Too large a record in log file.
User Response: Verify the path name of your log Explanation: One of the records in the Tivoli Data
database. If the path name is correct, verify the log Protection application client is too large, or there is no
database itself to ensure that it can be opened in the carriage return character in the log file.
Notes workspace.
System Action: Program continues.
User Response: If the command is successful, check
ANS0979E Error closing log file Logname: system
the log database to ensure that the correct record was
error code.
added to the database. If the command fails, verify that
Explanation: An I/O error occurred when an attempt the data in the Tivoli Data Protection application
was made to close the Tivoli Data Protection client’s log file is valid.
application client’s log file.
System Action: Processing stops. ANS0984E Error opening the log file Logname:
system error code.
User Response: Check the access permission on the
Tivoli Data Protection application client’s log file. Explanation: An I/O error occurred when an attempt
was made to open the Tivoli Data Protection
ANS0980E Error deleting log file Logname: system
error code. System Action: Processing stops.
Explanation: An I/O error occurred when an attempt User Response: Verify the path name of the log file.
was made to delete the Tivoli Data Protection Also Check the access permission on the log file.
System Action: Processing stops. ANS0985E Error closing the database DBname:
system error code.
User Response: Check the access permission on the
Tivoli Data Protection application client’s log file. Explanation: An I/O error occurred when an attempt
was made to close the log database.
ANS0981E Error getting log file start time. System Action: Processing stops.
Explanation: The program is not able to interpret the User Response: Check the access permission on the
first date/time stamp in the Tivoli Data Protection log database.
application client’s log file. The first date/time stamp
format either does not match the date/time stamp
ANS0986I Log file Logname successfully written to
format of your operating system, or it is corrupted.
DBname.
Explanation: The Tivoli Data Protection application
User Response: For consistency reason, the date/time client’s log file has been successfully written to the log
stamp format of the log file must match the date/time database.
stamp format of your operating system. Check the
locale of your operating system to ensure that you have
matching date/time stamp formats. User Response: None.

ANS0987E Log file Logname NOT written to
DBname.
ANS1003E Backup failed to start for node =
node-name, file system = fs-name, errno =
client’s log file was not written to the log database due
error-code, reason : error-reason
to error.
Explanation: An attempt to start backup for remote
node failed.
User Response: Check the error messages that
System Action: Backup fails.
preceded this message.
persists, contact the server administrator.
ANS0988I Log file Logname deleted.
ANS1004W Node has exceeded max tape mounts
client’s log file was deleted because the “-d” option
allowed. Operation for ’filespace-name’
was used.
will be tried again later.
Explanation: Node has exceeded max tape mounts
User Response: None. allowed. The operation will be tried again later.
System Action: The operation will be retried.
ANS0989E Log file Logname was NOT deleted, due
User Response: Increase the number of allowed tape
to error.
mounts for this node on the server to avoid this
Explanation: The user has used the option “-d” but situation again.
the Tivoli Data Protection application client’s log file
was NOT deleted due to error.
ANS1005E TCP/IP read error on socket = socket-id,
System Action: Processing stops. errno = error-code, reason : ’error-reason’.
User Response: Check the error messages that Explanation: An attempt to receive data using TCP/IP
preceded this message. connection failed. If reason : ’Connection reset by peer’,
it is possible that the server control connection timed
out. This can occur if the file transfer time is greater
ANS1000E Attempting to use a communications
than the IDLETIMEOUT value set on the server.
method that is not supported
System Action: TCP/IP connection to server fails.
Explanation: You specified a communication method
that is not supported. User Response: If the timeout was due to a large file
transfer time, you can ignore this message. The client
will reconnect with the server automatically, finish
User Response: Specify a valid communication transferring the data, and send statistics. You can also
interface for the TSM client and your operating system. consider increasing the IDLETIMEOUT value in the
ANS1001E Volume being backed up was not a

system volume. Skipped. ANS1006E TCP/IP write error on socket = socket-id,
errno = error-code, reason : error-reason
Explanation: User specified to back up system volume
only. This volume was not backed up since this volume Explanation: An attempt to send data using TCP/IP
is not a system volume. connection failed.
System Action: Volume was not backed up. System Action: Connection to server fails.
User Response: Use All option or use image backup User Response: Retry the operation. If the problem
command to backup this volume. persists, contact your system administrator.
ANS1002I MOS image is being created. It may ANS1007E Sending of object ’object-nameobject-
take a while. nameobject-name’ failed: No Backup Copy
Group
Explanation: Mini Operating System image is beging
created. It may take a while to create it. Explanation: The management class for this file
(object-name) did not have a backup copy group
System Action: TSM is gathering necessary specified.
information.
System Action: TSM did not back up the file.

User Response: See your system administrator. User Response: See your system administrator.
ANS1008E Sending of object ’object-nameobject- ANS1025E Session rejected: Authentication failure

nameobject-name’ failed: No Archive Copy
Explanation: Authentication failure. You entered an
Group
incorrect password.
Explanation: The management class for this file
System Action: TSM canceled the current operation.
(object-name) did not have an archive copy group
specified. User Response: Enter your correct password. If you
cannot remember the correct password, see your
system administrator to have a new one assigned for
User Response: See your system administrator. your node name.
ANS1017E Session rejected: TCP/IP connection ANS1026E Session rejected: Communications

failure protocol error
Explanation: An attempt to connect to the server Explanation: Communications protocol error. An
using TCP/IP communications failed. This error can unexpected communications message was received by
occur if the LAN connection went down or if your the client.
system administrator canceled a backup operation.
System Action: Session rejected. Processing stopped.
User Response: Verify that your communication path
User Response: Retry the operation, or wait until the is functioning properly. If the problem continues, have
server comes back up and retry the operation. If the your service representative check for a possible
problem continues, see your system administrator for program error.
further help.
ANS1028S Internal program error. Please see your
ANS1022E Cancel failed for node: node-name service representative.
filesystem: fs-name operation: op-type
Explanation: An unexpected program failure occurred.
error: error
Explanation: The request to cancel a remote operation
has failed. The node, filespace, operation and reason for User Response: Retry the operation. If the problem
the failure are shown. continues, see your system administrator or your
System Action: TSM operation not cancelled.
ANS1029E Communications have been dropped.
more information.
Explanation: Communications with the server
dropped.
ANS1023E Session rejected: Node type mismatch
Explanation: Your node name is associated with a
different type of operating system (such as OS/2 or User Response: Restart the TSM client and retry the
AIX) and cannot be used on this system. operation.
ANS1030E System ran out of memory. Process
User Response: If you need a new node name, see
ended.
your system administrator to assign a new one to you.
Generally, you have a unique node name for each Explanation: TSM cannot allocate storage for the
machine and operating system pair that requires access specified operation.
to the server.
System Action: TSM cannot complete the requested
operation.
ANS1024E Session rejected: Unable to locate
required file WSOCK32.DLL User Response: Stop TSM, restart TSM, and retry the
operation. If unsuccessful, close all unneeded
Explanation: The 32-Bit Windows Sockets DLL applications and retry the operation. For UNIX systems
WSOCK32.DLL could not be located that support resource limits, you can check if the
memory resource limit is too low by entering the
System Action: Communications link is not
following command: ulimit -a Based on the
established. Session rejected.
resulting data, you can ask the UNIX system root user

to increase resource limits so that it will override the You can do this by entering the SET command at your
current default. The UNIX system root user has the system.) If this environment variable is set, ensure the
authority to increase resource limits. file indicated by the variable exists. If it is not set, then
TSM looks for the file dsm.opt in the current directory.
If neither of these cases is met, you receive this error
ANS1031E Establishment of a TCP/IP connection
message.
timed out before connection was made
Explanation: The attempt to establish a TCP/IP
ANS1036S Invalid option ’option’ found in options
connection timed out before the connection was made.
file ’file-name’ at line number : number
System Action: Processing stopped. Invalid entry : ’entry’
User Response: Check for a networking problem. If Explanation: The specified option in the TSM options
the problem continues, see your system administrator. file (file-name) is in error.
API applications should close the session with
dsmTerminate.
User Response: Correct the options file entry.
ANS1032E An attempt to establish a TCP/IP
connection was rejected by the host ANS1037S Invalid keyword specified
Explanation: An attempt to establish a TCP/IP Explanation: TSM found an incorrect keyword in the
connection was rejected by the server. options file.
User Response: The server was not fully initialized, is User Response: Correct the options file with valid
not currently running, was not enabled for TCP/IP entries.
communications, or an incorrect TCP/IP port number
was specified. If the problem continues, see your
ANS1038S Invalid option specified
system administrator.
Explanation: An incorrect option was specified to
TSM.
ANS1033E An invalid TCP/IP host name was
specified System Action: Processing stopped.
Explanation: An invalid TCP/IP host name or address User Response: Correct the options used for running
was specified. TSM.
ANS1039S Include/Exclude pattern too complex
User Response: Check your options file for the correct
TCPSERVERADDRESS statement. See your Explanation: The include or exclude pattern issued is
administrator for the correct name of the server. too complex to be accurately interpreted by TSM.
ANS1034E The specified TCP/IP host name is
unreachable User Response: Recode the include or exclude pattern
as shown in one of the examples in the appropriate
Explanation: The TCP/IP host name specified in the Using the Backup-Archive Client book for the particular
TCPSERVERADDRESS statement cannot be reached. operating system.
ANS1040S Include/Exclude pattern is missing a
User Response: Check your options file for the correct
closing bracket
TCPSERVERADDRESS statement. See your
administrator for the correct name of the server. Explanation: The include or exclude pattern is
incorrectly constructed. The closing bracket is missing.
ANS1035S Options file ’file-name’ not found System Action: Processing stopped.
Explanation: The options file specified by file-name User Response: Correct the syntax for the pattern.
cannot be found.
System Action: The TSM client ends.
User Response: See if you have the environment
variable DSM_CONFIG (or DSMI_CONFIG for the API)
set, which explicitly identifies the TSM options file. (

System Action: TSM attempts to continue the current
ANS1041S Include/Exclude pattern must start with
operation.
a directory delimiter
User Response: Check the length of environment
Explanation: The include or exclude pattern must start
string and break it up into smaller strings using
with a directory delimiter.
multiple environment variables.
User Response: Correct the syntax for the pattern. ANS1051E Invalid password
Explanation: You entered an invalid password.
ANS1042S Include/Exclude pattern has a ’...’
System Action: TSM cannot connect to the server
without beginning/ending directory
without the correct password.
delimiter
User Response: Enter the password, or ask your
Explanation: The include/exclude pattern has a ’...’
system administrator for the correct password.
without a beginning or ending directory delimiter.
ANS1052E Direct connection to the Storage Agent
User Response: Correct the syntax for the pattern. is not allowed.
Explanation: You cannot connect directly to the
ANS1043S Quotes are not matched Storage Agent.
Explanation: The quotes specified in the pattern are System Action: Processing stopped.
not the same and do not make a set.
User Response: To perform Lanfree operations using
System Action: Processing stopped. the Storage Agent, specify the ENABLELANFREE
option in your options file, and restart the process.
User Response: Correct the pattern by using matching
quotes in the syntax.
ANS1053I Existing filespace name filespace-name
has been renamed to filespace-name
ANS1044S Unresolved environment name
’environment-name’.This filespace is being Explanation: The existing filespace name using the
ignored. Processing Continues. volume label has been renamed to the UNC format
naming convention.
Explanation: The specified environment-name in the
options file is invalid. System Action: Processing continues.
System Action: TSM attempts to continue the current User Response: None.
operation.
User Response: Check the environment variable in the ANS1054E Unable to rename existing filespace
options file and use a valid environment variable. Retry filespace-name to new filespace
the operation. filespace-name.RC=retcode from
cuFSUpd().
ANS1045S Environment variable syntax error. Explanation: Unable to rename the existing filespace
name using the volume label to the UNC format
Explanation: Incorrect syntax is specified in the
naming convention.
options file. Make sure that the variable is enclosed in
curly braces. System Action: Processing stopped.
System Action: TSM attempts to continue the current User Response: None.
operation.
User Response: Check the syntax of environment ANS1055I Trying to rename existing filespace
variable in the options file. Correct it and retry the filespace-name to new filespace
operation. filespace-name, but drive letters do not
match, old=drive-letter, new=drive-letter.
Ignore the old filespace and backup to
ANS1046S Environment string for variable
the new filespace.
’environment-name’ too long. Anything
beyond 1024 characters is being ignored Explanation: Trying to rename the existing filespace
Explanation: Environment variable expanded to a
naming convention but the drive letters do not match.
string which is too long. Make sure that the string is no
Leave the existing filespace alone and create a new
more than 1023 characters long.
filespace.

ANS1060E The specified path is not a mounted
User Response: None. filesystem
Explanation: You entered a file system name that does
ANS1056E Share/network path cannot be resolved. not correspond to a mounted file system for this
Path does not exist. system. It is possible the file system name is
misspelled, or simply that the file system is not
Explanation: For backup: Trying to backup currently mounted.
share/network, which either does not exist or does not
have the correct privilege to access the share. For System Action: The requested logical volume
restore : Trying to restore to a share/network path that operation is not performed.
cannot be resolved. The directory path does not exist.
User Response: Retry the operation, using name of a
System Action: Processing stopped. mounted file system.

destination, or restore the directory tree first before ANS1061E The specified device corresponds to a
trying to restore the share point. mounted file system, use the file system
name.
ANS1057I Trying to rename existing filespace Explanation: You entered a logical device name that is
filespace-name to new filespace mapped to a mounted file system. This volume must
filespace-name, but both filespaces exist. only be referenced by its file system name.
Ignore the old filespace and backup to
System Action: The requested logical volume
the new filespace.
operation is not performed.
Explanation: Trying to rename the existing filespace
User Response: Retry the operation, using the file
system name.
naming convention but both filespaces exists. Leave the
existing filespace alone and backup to the new
filespace. ANS1062E Only a single image may be selected
when a destination is entered.
Explanation: You selected more than one image object
(logical volume) to be restored. You also specified a
destination. The system cannot place more than one
ANS1058E Destination file space or drive letter image into a single destination volume. When more
’filespace name’ is unavailable. than one object is selected, each must be restored to its
original location.
Explanation: Trying to restore or retrieve to a
destination that cannot be reached. The specified file System Action: The requested logical volume restore
space name or drive letter is not valid, does not exist, is not performed.
or you are specifying a local share name that cannot be
User Response: Retry the operation, selecting one
resolved.
object to be restored to the given destination, or retry
System Action: Processing stopped. the operation without entering the destination.

different destination. ANS1063E Invalid path specification
Explanation: The path specified is not a valid
ANS1059E Two inactive objects with the same file-system or logical volume name.
image name were selected. Process
terminates
Explanation: You selected more than one inactive
User Response: Retry the operation, using a valid
version of the same image object (logical volume). The
path.
system has no way to decide which you want to
restore.
ANS1064E Internal error
System Action: The requested logical volume restore
is not performed. Explanation: An error occurred in the image utility
internals.
User Response: Retry the operation, selecting an
active version or only one inactive version of the System Action: The requested logical volume
volume you wish to restore. operation is not performed.

User Response: Contact your TSM administrator. User Response: Re-try the operation, check error log
for more information.
ANS1065E Library version of the image utility does
not match that of the TSM API ANS1071E Invalid domain name entered:
’domain-name’
Explanation: The current system has a mix of installed
components. Explanation: You entered an invalid domain-name.
System Action: The requested logical volume System Action: Processing stopped.
User Response: Enter a valid drive or file system
User Response: Re-install all TSM components name (domain).
ANS1066E Restore successful. File system mount ANS1072E Unable to continue operation; Drive
failed. ’drive-name’ has no volume label.
Explanation: The file system was successfully Explanation: The specified drive-name in the domain
restored, but the attempt to re-mount it failed. list does not have a volume label.
System Action: The file system is left unmounted. System Action: Processing stopped.
User Response: Use the mount command to mount User Response: Use the system format utility to place
the file system. On AIX, run fsck if requested by the a unique volume label on all drives on which you
operating system. intend to run TSM.
ANS1067E Error in system call, check log file for ANS1073E File space correspondence for domain
more information ’domain-name’ is not known
Explanation: An error occurred during a system call, Explanation: The number defining the correspondence
check the error log for more information. between drive letter or file (domain name) and volume
label is not known to the server.
operation is not performed. System Action: Processing stopped.
User Response: Check error log. User Response: Report the program error to your
ANS1068E Device is not local
ANS1074W *** User Abort ***
Explanation: The selected path is not a local device
and therefore is not a valid object for image operations Explanation: An abort signal to stop an operation was
received.
operation is not performed. System Action: Processing stopped.
User Response: Choose another object. User Response: Continue with normal operations.
ANS1069E An error occurred while reading data ANS1075E *** Program memory exhausted ***
from the device
Explanation: The program has exhausted all available
Explanation: An error occurred while reading data storage.
from the device.
User Response: Free any unnecessary programs, for
example, terminate and stay resident programs (TSRs),
User Response: Re-try the operation, check error log that are running and retry the operation. Reducing the
for more information. scope of queries and the amount of data returned can
also solve the problem.
ANS1070E Write error
ANS1076E *** Directory path not found ***
Explanation: An error occurred while writing data to
the device. Explanation: You specified an incorrect directory path.
System Action: The requested logical volume System Action: Processing stopped.

User Response: Correct the syntax specified and retry
ANS1084E No files have previously been backed
the operation.
up for ’filespace-name’
Explanation: You tried to restore files when no files
ANS1078S *** Unknown system error error-code;
for the specified drive or file system (filespace-name)
program ending ***
were previously backed up.
Explanation: An unknown and unexpected error-code
occurred within the client program. This is a
programming failure and the client program ends. User Response: Ensure that the correct drive or file
you to restore.
ANS1085E No memory available to store Archive
Management Class override name
ANS1079E No file specification entered
Explanation: Not enough memory was available for
Explanation: You did not enter a file specification as the operation.
prompted.
System Action: TSM did not continue with the
User Response: Retry the operation or restart the
requested operation.
system with fewer programs in memory.
User Response: Enter a file specification to continue.
ANS1086E File not found during Backup, Archive
ANS1081E Invalid search file specification ’string’ or Migrate processing
entered
Explanation: The file being processed for backup,
Explanation: You entered a file specification or search archive or migrate no longer exists on the client.
string that contains incorrect characters or contains Another process deleted the file before it could be
wildcard characters in the drive specification or file backed up, archived or migrated by TSM.
system name.
User Response: Enter a correct file specification as
described in the appropriate Using the Backup-Archive
ANS1087E Access to the specified file or directory
Client book for the particular operating system.
is denied
Explanation: Access to the specified file or directory is
ANS1082E Invalid destination file specification
’file-name’ entered
you do not have access permission for either the file or
Explanation: You entered a destination file-name the directory.
specification that contains incorrect characters or has
wildcard characters in the specification.
User Response: Enter a correct file specification as specify a new location.
described in the appropriate Using the Backup-Archive
Client book for the particular operating system.
ANS1088E File space ’filespace-name’ does not exist
Explanation: The specified file space (domain) is
ANS1083E No files have previously been archived
incorrect or does not exist on the machine.
for ’filespace-name’
Explanation: You tried to retrieve files when no files
for the specified drive or file system (filespace-name) User Response: Retry the operation specifying an
were previously archived. existing domain (drive letter or file system name).
system was specified and that files are archived for you
to retrieve.

ANS1089E Destination directory path length ANS1094E Server does not support Query Node
exceeds system maximum command.
Explanation: The path name specified plus the path Explanation: The server to which you are connected
name in the restored file name combine to create a does not support Query Node command.
name whose length exceeds the system maximum.
User Response: Use a TSM Server that supports
User Response: Specify a destination path that, when Query Node command.
ANS1096S Either an Active Policy Set or a node
ANS1090E Unable to build directory branch; A file was not found on the server; Unable to
exists with the same name as a directory. proceed
Failing path was: ’path-name’.
Explanation: Either no Active Policy Set data was
Explanation: TSM tried to create a directory path-name, found on the server or a fromnode option contained a
but is unable to because a file exists that has the same nodename not found on the server.
name as a directory.
User Response: Remove the file that has the same
name as the directory. Refer to the given failing path,
ANS1097E Unable to read help text
and either remove or move the file that caused this
problem and restart the restore/retrieve operation. Explanation: The Help facility cannot read the help
text file.
ANS1091E Communications error with server System Action: Processing stopped.
during object query
User Response: Make sure the DSM_DIR environment
Explanation: An unexpected communications error variable points to the correct directory containing the
occurred during an object query to the server. current level of TSM program files.
ANS1098E Process terminated; Program memory
User Response: Verify that communications are active
exhausted.
between the client and server machines. Server outages,
processor outages, and communication controller Explanation: The program used all available storage.
outages can cause this error.
ANS1092E No files matching search criteria were User Response: Free any unnecessary programs
found (TSRs) that are running, and retry the operation.
Reducing the scope of queries and the amount of data
Explanation: You entered a search pattern or file name returned can also solve the problem.
that cannot be found in the server database.
System Action: Processing stopped. ANS1099E File ’filename’ not previously archived
User Response: Ensure that your search pattern is Explanation: You tried to give access to a file, which
correct, or specify a new search string. is not stored on the server.
ANS1093E Server does not support point-in-time
option. User Response: Ensure that the correct filename is
specified.
Explanation: The server to which you are connected,
does not support point in time values.
ANS1100E File ’filename’ not previously backed up
Explanation: You tried to give access to a file, which
User Response: Enter the command without is not stored on the server.
specifying the point in time option.
User Response: Ensure that the correct filename is
specified.

the management class, and then retry the operation.
ANS1101E User is not authorized to decrypt
filename .
ANS1106E ENCRYPTKEY SAVE not configured
Explanation: The user is not authorized to decrypt the
correctly. Encryption not used.
file; the user cannot restore the file. Only a TSM
Authorized user or a root user can decrypt and restore Explanation: This message is issued for TSM
the file. Authorized Users and root users when ENCRYPTKEY
SAVE and PASSWORDACCESS PROMPT options are
System Action: The file is not restored.
set. Please note that these are the default values. These
User Response: Contact your system administrator to values do not allow encryption.
restore the file.
System Action: The file is not encrypted.
User Response: To save encryption keys, you must
ANS1102E Excessive number of command line
change configuration values. Add PASSWORDACCESS
arguments passed to the program!
GENERATE to your system option file.
Explanation: This command processing routine
received more operands than it can use. Query can
ANS1107E Invalid option/value: ’option’
contain only one file specification. Restore and Retrieve
can contain two file specifications. Archive, Delete, and Explanation: You specified an incorrect TSM option
Selective can contain a maximum of 20 file option.
specifications.
User Response: Specify a correct TSM option as
User Response: Reduce the number of arguments and defined in the appropriate Using the Backup-Archive
retry the operation. For UNIX-based systems, ensure Client book for the particular operating system.
that you do not omit the quotes around pattern
matching characters.
ANS1108E Invalid option (option) for the function
command
ANS1103E Invalid management class entered
Explanation: The option option was specified for a
Explanation: You entered an invalid management command or subcommand (function) that cannot make
class. use of that option.
System Action: TSM is unable to do the requested System Action: Processing stopped.
operation.
User Response: Retry the operation using a valid Backup-Archive Client book for your operating system
management class. for correct use of the named option.
ANS1104E The management class for this file does ANS1109E User is not authorized to decrypt the
not have a valid archive copy group. file.
This file will not be archived.
Explanation: The user is not authorized to decrypt the
Explanation: The management class for this file does file; the user cannot restore the file. Only a TSM
not have an archive copy group specified. This file will Authorized user or a root user can decrypt and restore
not be archived. the file.
System Action: Processing stopped. System Action: The file is not restored.
User Response: Add a valid archive copy group to the User Response: Contact your system administrator to
management class, and then retry the operation. restore the file.
ANS1105E The management class for this file does ANS1110E Unable to open Help file file-name
not have a valid backup copy group.
This file will not be backed up. Explanation: The Help facility cannot find the help
file file-name.
Explanation: The management class for this file does
not have a backup copy group specified. This file will System Action: Processing stopped.
not be backed up. User Response: Ensure that the DSM_DIR
System Action: Processing stopped. environment variable points to the correct directory
containing the current level of TSM program files.
User Response: Add a valid backup copy group to

User Response: Enter a correct file space number.
ANS1111E Unable to get Help file table of contents
Explanation: The Help facility cannot read the help
ANS1119I Initiating the removal of ’filespace-name’
text file, or the file is corrupted.
file space.
Explanation: Indicates that file space deletion has
User Response: Make sure the DSM_DIR environment started on the specified filespace-name.
variable points to the correct directory containing the
current level of TSM program files, and that the files
are intact. User Response: None.
ANS1114I Waiting for mount of offline media. ANS1120E Removal of file space ’filespace-name’
failed
Explanation: The server is waiting for the requested
media to become available before the operation can Explanation: Deletion of the specified filespace-name
continue. failed.
System Action: TSM waits for requested data. System Action: Processing stopped.
User Response: None. User Response: Try again. If the problem continues,
see your system administrator to delete the file space
for you.
ANS1115W File ’file-namefile-namefile-name’ excluded
by Include/Exclude list
ANS1121I Removal of file space ’filespace-name’
Explanation: You tried to back up or migrate a file
successfully completed.
(file-name) that was specified to be excluded from
backup. Explanation: TSM successfully deleted the specified
filespace-name.
System Action: TSM did not back up or migrate the
file. System Action: None.
User Response: Specify the file using the Include User Response: None.
option and retry the operation.
ANS1122W File space ’filespace-name’ does not exist

ANS1116E Unable to read commands entered from on the server. The file space might have
keyboard. Exiting... been deleted by another client using
your client’s node name or an
Explanation: Unable to read commands entered from
administrator.
keyboard. TSM cannot process your intended
command. Explanation: The specified filespace-name does not exist
on the server. Your system administrator deleted the
file space or another client using your client’s node
User Response: Ensure that you are entering a correct name might have deleted it.
command.
ANS1117E The PICK and LATEST options are not
valid together
ANS1123E The vertical screen dimension is too
Explanation: During a restore, PICK and LATEST
small to display the Help directory.
options cannot be used together.
Increase your window height.
Explanation: Execution of the HELP command
User Response: Try again using either the PICK or the requires space for both the user prompts and at least
LATEST option. one line of the HELP directory.
System Action: The help directory is not displayed,
ANS1118I Invalid file space number entered. Try and the help command cannot complete.
again.
User Response: Increase the size of your display
Explanation: The number that represents a file space window to allow more rows of text to be displayed.
was incorrect while you were using the PICK option.
System Action: TSM waits for your specification.

disk with a volume label in it and retry the operation.
ANS1125E Unmatched Quotes: ’string’
If the disk is a hard drive, ensure the drive has a
Explanation: The quotes specified in the pattern are volume label, and retry the operation.
System Action: Processing stopped. ANS1131E Unable to continue operation. Duplicate
labels exist.
User Response: Correct the pattern using matching
quotes in the syntax. Explanation: The selected drive has a duplicate
volume label. Because TSM uses the volume label to
keep track of backup/archive information, it cannot
ANS1126E Unable to delete the file space because
back up or archive files from a drive with a duplicate
this node does not have permission to
volume label.
delete archived data and/or backed up
file space. System Action: TSM cannot select the drive.
Explanation: During a delete filespace operation, you User Response: If the volume needs to be available to
specified a file space to which your node does not have the system, exit TSM, and assign a volume label to the
permission to delete archived data and/or backed up drive. Restart TSM and retry the operation.
data.
System Action: Delete processing fails. ANS1132E ’Access rule’ Access Rule already defined
for node ’node’. Old rule must be
deleted before new one can be defined.
Explanation: You are trying to define authorization for
ANS1127E Your node does not have permission to
the specified node, which already has authorization
delete archived files
defined.
Explanation: Your node is not allowed by the server
System Action: TSM did not redefine authorization
to delete archived files.
for the specified node.
System Action: TSM did not delete the archived files.
User Response: Update the authorization, or delete
User Response: See your system administrator. the old rule and define a new one, or use the current
authorization.
ANS1128S Invalid Management Class assigned to

directories. Please see the error log. ANS1133W An expression might contain a wildcard
not enclosed in quotes
Explanation: An invalid management class was
assigned to directories. Explanation: TSM cannot process the command
because a UNIX shell expands a wildcard expression,
System Action: Processing stopped. for example, asterisk (*) or question mark (?), that has
User Response: Have your service representative no quotes.
check the error log. System Action: Command dependent.
User Response: Enclose the wildcard expression in
ANS1129S No backup copy group in the quotes and enter the command.
management class used for directories.
Please see the error log.
ANS1134E Drive drive-name is an invalid drive
Explanation: The management class used for specification
directories does not have a backup copy group.
Explanation: The specified drive-name was found to be
System Action: Processing stopped. invalid; the drive probably has not been defined.
User Response: Have your service representative System Action: TSM skips the invalid drive and
check the error log. continues to the next drive.
User Response: Check the invalid drive.
ANS1130E Unable to continue operation. Drive has
no label.
ANS1135E Drive drive-name1 is a virtual drive of
Explanation: The selected drive does not have a label. drive-name2 Not a valid drive to be
System Action: TSM is unable to do the requested backed up
operation without a drive or label entered. Explanation: The drive-name1 was found to be a
User Response: If the drive is a floppy drive, place a substitute (SUBST) of another drive-name2. It is not

available for backup/archive.
ANS1143E The DIRSONLY and FILESONLY
System Action: TSM skips the SUBST drive and options are not valid together
continues to the next drive.
Explanation: The DIRSONLY and FILESONLY options
User Response: None. cannot be used together.
ANS1136E Not file owner
User Response: Try again using either the DIRSONLY
Explanation: The file cannot be backed up because the or the FILESONLY option.
client is not the file owner.
System Action: TSM skips the file. ANS1144W Password authentication not active on
server
Explanation: None.
ANS1137W Invalid Index ’number’ skipped. System Action: Processing stopped.
Explanation: An incorrect number was entered for the User Response: Because password authentication is
Index. turned off on the server, you do not need to update the
password.
User Response: Correct the Index entry and retry the ANS1145E Maximum macro nesting level exceeded.
operation.
Explanation: Too many levels of macro nesting are
encountered.
ANS1138E The ’command-name’ command must be
followed by a subcommand System Action: The macro is ignored and an error is
returned.
Explanation: You entered an incomplete
command-name. User Response: Reduce the level of macro nesting.
ANS1146E Macro file ’file spec’ cannot be opened.
User Response: Enter the correct syntax of the
command and continue. Explanation: A macro command has been entered that
specifies the macro file name shown. However, that file
cannot be opened for reading.
ANS1139E Post restore processing failed.
System Action: The macro is ignored and an error is
Explanation: Post restore processing failed due to an returned.
internal system error.
User Response: Enter the command with the proper
System Action: Please see error log for more details. macro name.
User Response: Please see your system administrator
for assistance. ANS1147E File is temporarily unavailable.
Explanation: File is temporarily unavailable.
ANS1140E Invalid format for Set Access command.
Explanation: None.
User Response: Check and see if file is locked by
System Action: Processing stopped. other process. If not, retry the command.
User Response: Enter the SET ACCESS command
using the correct syntax. ANS1148I ’Command-name’ command successfully
completed
ANS1141W Unknown command - command-name Explanation: The specified command-name was
Explanation: You entered an incorrect command-name. successfully completed.
System Action: None. System Action: TSM completed the command.
User Response: Enter the correct command. User Response: Continue with normal operations.

ANS1149E No domain available for incremental ANS1154E Drive filespace is a cluster disk. Not valid
backup for backup/archive when
CLUSTERNODE option is NO.
Explanation: An incremental backup was started, but
no domain was selected. Explanation: The filespace is a cluster disk.
Backup/archive is not allowed when the
CLUSTERNODE option is set to NO.
User Response: Choose a domain and restart the
incremental backup.
User Response: Set CLUSTERNODE option to YES,
then backup/archive the drive. Otherwise, you cannot
ANS1150E Unable to restore current user profile
backup/archive the drive.
because you are running as a local
system account.
ANS1155E CLUSTERNODE option is set to YES
Explanation: The local system account does not have a
but cluster is not enabled. Either the
profile. Therefore you cannot restore its profile.
machine does not have cluster server
System Action: Processing stops. installed, or the cluster server is not
running.
User Response: Log on to the user whose profile you
want to restore. Explanation: If CLUSTERNODE option is set to YES,
TSM must be running on a Windows NT Server
Enterprise Edition machine with the cluster server
ANS1151E Drive drive-name1: is not a cluster disk. installed and running.
Not valid for backup/archive when
CLUSTERNODE option is YES. System Action: Processing stops.
Explanation: The drive-name1 is not a cluster disk. User Response: Ensure TSM is running in a cluster
Backup/archive is not allowed when the environment and that the cluster server has been
CLUSTERNODE option is set to YES. started.

ANS1156E NODENAME cannot be the local
User Response: Set CLUSTERNODE option to NO, machine name when CLUSTERNODE is
then backup/archive the drive. Otherwise, you cannot set to YES
Explanation: When TSM is running as a cluster node,
the nodename cannot be the local machine name.
ANS1152E Drive filespace is not a cluster disk. Not
valid for backup/archive when System Action: Processing stops.
CLUSTERNODE option is YES.
User Response: Change the nodename either to the
Explanation: The filespace is not a cluster disk. cluster name or to any other name, and restart TSM.
Backup/archive is not allowed when the
CLUSTERNODE option is set to YES.
ANS1157I Backup/Restore of the registry is not
System Action: Processing stops. allowed when running as a cluster node.
User Response: Set CLUSTERNODE option to NO, Explanation: When running as a cluster node, registry
then backup/archive the drive. Otherwise, you cannot cannot be backed up or restored.
ANS1153E Drive drive-name1: is a cluster disk. Not
valid for backup/archive when
CLUSTERNODE option is NO. ANS1158I Backup/Restore of the event logs is not
allowed when running as a cluster node.
Explanation: The drive-name1 is a cluster disk.
Backup/archive is not allowed when the Explanation: When running as a cluster node, event
CLUSTERNODE option is set to NO. logs cannot be backed up or restored.
System Action: Processing stops. System Action: Processing continues.
User Response: Set CLUSTERNODE option to YES, User Response: None.
then backup/archive the drive. Otherwise, you cannot

User Response: Choose a destination that has the
ANS1159E The specified file is being used by
same file system type as the source.
another process
Explanation: The specified file is being used by
ANS1168E ERROR: could not create image object.
another process. You tried to read from or write to a
file that is currently being used by another process. Explanation: Creation of the image object failed for
one of the following reasons:
v The image command was executed by a non-root
User Response: Ensure that you specified the correct user
v The image plugin library was not found.
User Response: Retry the operation after correcting
the cause for failure.
ANS1162E Filesystem could not be mounted
System Action: The requested logical volume function
Explanation: The system call to mount the file system
is not performed.
failed.
System Action: The file system remains unmounted.
ANS1169W There is no table of contents for
User Response: Use the mount command to mount image-name.
the file system. On AIX, run fsck if requested by the
Explanation: The image item for which a table of
operating system.
contents was requested is either a RAW logical volume
or it was backed up without the -TOC option.
ANS1163E Filesystem could not be unmounted.
System Action: No table of contents is displayed.
Explanation: The system call to unmount the file
User Response: Select another image object for TOC
system failed.
display.
System Action: The logical volume operation is not
performed.
ANS1170I Invalid selection number entered. Try
User Response: Make sure the device or file system is again.
not being accessed, then retry the operation.
Explanation: You entered a number not shown in the
list of images. It is either less than one or greater than
ANS1164E Filesystem is not mounted the highest item number displayed.
Explanation: The named file system is not currently System Action: TSM waits for you to enter a valid
mounted. It must be mounted for TSM to perform an selection.
image backup.
User Response: Enter a number from the list or ’Q’ to
System Action: The logical volume operation is not quit.
performed.
User Response: Mount the file system. ANS1177E Must specify a path for this operation.
Explanation: A path must be specified for this
ANS1165E Destination is smaller than source operation to execute successfully.
Explanation: The space allocation for the selected System Action: Processing stops.
destination is smaller than the source.
User Response: Specify a valid path and execute the
System Action: The restore operation is not command again.
performed.
User Response: Choose a different, bigger destination ANS1181E Communication failure with the journal
or increase the size of the destination file space. service.
Explanation: An error occurred using named pipe
ANS1166E Source and destination are not the same communication with the journal service.
file system type.
Explanation: The source and destination file system
User Response: Attempt to restart the service and
types do not match.
retry the backup. If the journal service is not running, a
System Action: The requested logical volume non-journaled backup will proceed.

ANS1183E An unknown error occurred while ANS1190E Symbolic link ’linkname’ to ’target’ was
processsing system object ’sys-obj-name’: successfully deleted.
MS API function ’func-name’ failed with
Explanation: Log ’linkname’ cannot be a symbolic link.
error error (error)
System Action: The symbolic link ’linkname’ is
Explanation: An unknown error occurred while
deleted, the log is recreated, and processing stops.
processing a system object. The error information
captured indicates the reason for the failure. This User Response: Check the location of the new file. To
information can be used to diagnose the problem. specify the location of log files, refer to the user’s
manual for the ’errorlogname’ option, the
’schedlogname’ option, and the ’DSM_LOG’
User Response: Contact your system administrator for environmental variable.
more information.
ANS1191E Unable to delete symbolic link ’link’.
ANS1184W The command subcommand command is
Explanation: Log ’linkname’ cannot be a symbolic link.
not supported on this client.
Explanation: The command subcommand command is
not supported for the client running on this operating User Response: Delete the symbolic link ’linkname’.
system on this computer.
User Response: None. ANS1192E Specifying the error log ’link’ as a
symbolic link is not allowed.
Explanation: Error log ’linkname’ cannot be a symbolic
link.
ANS1185W Server not capable of server-free data
movement. System Action: The symbolic link ’linkname’ is
deleted, the error log is recreated, and processing stops.
Explanation: The TSM server that the TSM client has
opened a session with is not capable of server-free data User Response: Check the location of the new error
movement, either because it is not supported by the log. To specify the location of the error logs, refer to the
server’s level or platform, or because the appropriate user’s manual for the ’errorlogname’ option and
license is not installed on the server. ’DSM_LOG’ environmental variable.
System Action: The operation is retried using
LAN-free (if available) or LAN-based data movement. ANS1193E Specifying the trace file ’link’ as a
symbolic link is not allowed.
User Response: Remove the ENABLESERVERFREE
option from the system option file. Explanation: Trace file ’linkname’ cannot be a symbolic
link.
ANS1188E The selected filesystem is managed by System Action: The symbolic link ’linkname’ is
HSM, and therefore is not a valid object deleted, the trace file is recreated, and processing stops.
for image operations
User Response: Specify the trace file location with the
Explanation: Due to the nature of HSM, image backup ’tracefile’ option.
is not allowed on managed filesystems.
System Action: The requested logical volume ANS1194E Specifying the schedule log ’link’ as a
operation is not performed. symbolic link is not allowed.
User Response: None. Explanation: Schedule log ’linkname’ cannot be a
symbolic link.
ANS1189E The DIRSONLY and V2ARCHIVE System Action: The symbolic link ’linkname’ is
options are not valid together deleted, the schedule log is recreated, and processing
stops.
Explanation: The DIRSONLY and V2ARCHIVE
options cannot be used together. User Response: Check the location of the new
schedule log. To specify the location of the schedule
log, refer to the user’s manual for the ’schedlogname’
User Response: Try again using either the DIRSONLY option.
or the V2ARCHIVE option.

User Response: Identify and repair the problem that
ANS1195E An error occurred while accessing the
caused the command to fail. If a non-zero return code
image snapshot old-blocks index file: .
is normal for this command, then consider wrapping
Explanation: During the image snapshot backup TSM the command in a script that always exits with a return
encountered an error while opening or reading the code of zero.
old-blocks index file.
System Action: Processing stopped. ANS1200W The POSTSNAPSHOTCMD command
completed with a non-zero return code.
User Response: Contact your TSM administrator.
Explanation: If the command specified by the
POSTSNAPSHOTCMD option completed with a
ANS1196E An error occurred while accessing the
non-zero return code, then the image snapshot backup
image snapshot old-blocks data file: .
operation will continue, but with a warning-level
Explanation: During the image snapshot backup TSM result. Note that the result of the
encountered an error while opening or reading the POSTSNAPSHOTCMD command will not supercede a
old-blocks data file. higher result from the image snapshot backup
command. For example, if the image snapshot backup
System Action: Processing stopped. command completed with a return code of 12, the
User Response: Contact your TSM administrator. image snapshot backup will be considered to have
completed with a return code of 12, regardless of the
outcome of the POSTSNAPSHOTCMD command.
ANS1197E The snapshot cache size was exceeded
during the snapshot backup. System Action: The image snapshot backup continues,
but with a warning return code of at least 8.
Explanation: The image snapshot backup was not able
to complete because while creating the snapshot TSM User Response: Identify and repair the problem that
exceeded the snapshot cache size allowed via the caused the command to fail. If a non-zero return code
SNAPSHOTCACHESize option. is normal for this command, then consider wrapping
the command in a script that always exits with a return
System Action: Processing stopped. code of zero.
User Response: Increase the SNAPSHOTCACHESize
value for this volume and retry the operation. ANS1201E Unable to build a directory path; a file
exists with the same name as a directory.
ANS1198E An invalid snapshot cache location was Explanation: TSM tried to create a directory path, but
entered: . is unable to because a file exists that has the same
Explanation: The SNAPSHOTCACHELocation option name as a directory.
value entered for this volume is not valid. The value System Action: Processing stopped.
for this option must be an existing, full directory path.
System Action: Processing stopped. name as the directory. Refer to the last restore/retrieve
User Response: Please enter a valid operation and check all directories along the path.
SNAPSHOTCACHELocation value and retry the
operation. ANS1202E TOC backup for the image failed. Check
log files.
ANS1199E The PRESNAPSHOTCMD command Explanation: An error occurred during backup of the
failed. The image snapshot backup will table of contents. Check the error log for more
not be executed. information.
Explanation: The command specified by the System Action: The requested logical volume
PRESNAPSHOTCMD option must complete operation is not performed.
successfully in order to execute the image snapshot
backup. If the command completed with a return code User Response: Check error log.
of 0 (zero), it is considered to have completed
successfully. If the command completed with any other ANS1203E Deactivating the TOC object failed.
return code, it is considered to have failed. If the
command failed then the image snapshot backup is not Explanation: An error occurred while deactivating the
executed. table of contents object.
System Action: The client does not execute the image System Action: Image backup was successful. But
snapshot backup operation. deactivating the TOC object from the previous backup
failed.

User Response: Check error log.
ANS1212I Invalid Process number entered. Try
again.
ANS1204E Image restore failed. Check the error
log.
list of processes. It is either less than one or greater
Explanation: An error occurred while restoring the than the highest item number displayed.
image. Check log file for more information.
System Action: TSM waits for you to enter a valid
System Action: Restore stops. The file system is not selection.
mounted back.
User Response: Enter a number from the list or ’Q’ to
User Response: Check error log. quit.
ANS1205E Image backup failed. Check the error ANS1213W Snapshot image backup is not possible
log. for device devicename.Starting off-line
image backup.
Explanation: An error occurred while backing up the
image. Check log file for more information. Explanation: On Linux platform, snapshot image
backup is only possible for logical volumes created by
System Action: Backup stopped. The file system is not the Linux logical volume manager (LVM). The default
mounted back. image backup type is snapshot. Backing up a partition
User Response: Check error log. with snapshot image backup automatically leads to a
static image backup. In this case this warning appears.
To aviod this message please specify static image
ANS1206E TOC backup of a raw device is not backup or dynamic image backup.
supported. But the raw device is backed
up. System Action: Snapshot image backup will failover
to static image backup
Explanation: TOC backup of a raw device is not
supported. But the raw device is backed up. User Response: None.
System Action: Raw device is backed up with no TOC

object. ANS1214E Not enough space left in the volume
group which contains the logical volume
User Response: NONE. to be backed up.
Explanation: On Linux platform, the snapshot is
ANS1207E No TOC has been previously backed up created in the same volume group like the logical
for this file system. volume on which it is made. In this volume group
Explanation: The user is trying to query the TOC of a there must be enough free space for the snapshot. It is
file system. TOC backup for that file system has not possible to change the size of the snapshot by using a
been previously done. different value for snapshotcachesize.
System Action: Query stopped. System Action: None.
User Response: Backup the file system again with User Response: Decrease the value for
-TOC option. snapshotcachesize
ANS1209E The input argument list exceeds the ANS1215E The snapshot cache location cannot be
maximum length of maximum length located on the same volume that is
characters. being backed up.
Explanation: Arguments list for TSM program should Explanation: The snapshot cache location is on the
not exceed maximum length characters. same volume that is being backed up, but this is not
allowed; The default cache location is on the system
System Action: The command is not processed. drive.
User Response: Correct the command and retry the System Action: The client does not execute the image
operation. snapshot backup operation.
User Response: Specify a different snapshot cache
location using the SNAPSHOTCACHELOCATION
option.

the problem continues, see your system administrator
ANS1216E Not authorized to run TSM. See the
to isolate what resource is unavailable.
administrator for your system.
Explanation: The system options file for the server
ANS1221E Transaction aborted
that you are attempting to connect to contains a user
entry, a group entry, or both a user and group entry. Explanation: The current transaction between the
Your user ID, or group ID, was not found in any of the server and the client stopped. A server, client, or
entries. You are currently not authorized to run TSM to communication failure cannot be recovered.
this server.
System Action: TSM initialization fails and the
program ends. User Response: Retry the operation. If the problem
continues, see your system administrator to isolate the
User Response: See the TSM administrator for your problem.
system, and ask to be added to the user or group list
for this server.
ANS1222E Disk space limit for this process reached
ANS1217E Server name not found in System Explanation: The disk space allocated for the client
Options File owner is full.
Explanation: The system options file does not contain System Action: Processing stopped.
the SERVERNAME option. User Response: Free up disk space and retry the
System Action: TSM initialization fails and the restore or retrieve operation.
program ends.
User Response: See the TSM administrator for your ANS1223E File is not compressed; System failure.
system, and make sure that the system options file Explanation: A file that was flagged as compressed
contains the server name. was not compressed, and the system failed.
ANS1218E TCPSERVERADDRESS not defined for
this server in the System Options File User Response: See your system administrator to
report this problem. This error is a system failure.
Explanation: The TCPSERVERADDRESS for this
server is not defined in the server name stanza in the
system options file. ANS1224E File compressed on a different client
machine that has more memory
program ends. Explanation: You are trying to restore a file that was
backed up and compressed on another client
User Response: See the TSM administrator for your workstation that had more memory than your client
system, and make sure that the server to which you are workstation. You cannot restore this file. When the file
trying to connect, has a valid TCPSERVERADDRESS is restored, it is expanded and your workstation does
defined in the system options file. not have enough memory.
ANS1219E NODENAME cannot be the same as
HostName User Response: Obtain a machine with more memory
Explanation: The NODENAME defined in the options
file cannot be the same as the system HostName.
ANS1225E Insufficient memory for file
System Action: Initialization fails and the program compression/expansion
ends.
Explanation: Not enough memory is available to do
User Response: See your system administrator or the data compression or expansion. For a restore or
root user. retrieve, the file cannot be recalled from the server until
more storage is made available. For a backup or
ANS1220E Server out of resources archive, try running without compression if storage
cannot be made available.
Explanation: The server ran out of resources. A lack of
storage or a condition does not allow any new activity. System Action: Processing stopped.
System Action: TSM canceled the current operation. User Response: Free up extra storage for the
operation to continue, or run the backup or archive
User Response: Retry the operation at a later time. If process without compression enabled.

User Response: Either free some file handles by
ANS1226E Destination file or directory is write
ending other processes, or modify your system setup to
locked
allow for more files to be open at the same time.
Explanation: The file or directory being restored or
retrieved from the server cannot be written to because
ANS1232E File exists
the destination is write locked. Another operation
might have the file open and will not allow it to be Explanation: The file being restored or retrieved
updated. exists.
System Action: File skipped. System Action: File is replaced or skipped depending
on client options.
the file write locked, or restore the file to another name User Response: None.
or location.
ANS1233E Invalid file handle passed; System Error.

ANS1227E Processing stopped; Disk full condition
Explanation: No more files can be restored or operation failed because an invalid file handle was
retrieved because the destination disk is full. passed.
User Response: Free up disk space, or restore or User Response: Report the problem to your system
retrieve the file to another disk. administrator, and then retry the operation.
ANS1228E Sending of object ’object-nameobject- ANS1234E Protocol violation

nameobject-name’ failed
Explanation: A communications protocol error
Explanation: The specified file (object-name) cannot be occurred. The communication subsystem is not
sent to the server. properly defined or is itself in error.
System Action: File skipped. System Action: TSM ended the current operation.
User Response: Retry the operation. If the problem User Response: Verify that the communication
continues, see your system administrator to isolate the processes are operating properly, and then retry the
problem through use of the server console. operation.
ANS1229E INCREMENTAL BY DATE is invalid on ANS1235E Unknown system error

file-space. Image backup not processed.
Explanation: The Incremental by Date option is not be a low-level system or communication error that TSM
valid on file-space because the filespace has been the cannot handle or recover from.
subject of a progressive incremental backup since the
last full image backup was performed. System Action: Processing stopped.
System Action: File system skipped. User Response: Retry the operation. If the problem
User Response: If an image backup of the named your system administrator for further help.
file-system is desired, retry without the Incremental
Image By Date option.
ANS1236E Unexpected error
ANS1230E Stale NFS File Handle Explanation: An unexpected error occurred. This
might be a low-level system or communication error
Explanation: An NFS file system becomes stale. that TSM cannot handle or recover from.
System Action: File system skipped. System Action: Processing stopped.
User Response: Check the NFS mounted filesystem. User Response: Retry the operation. If the problem
your system administrator for further help.
ANS1231E No file handles available
Explanation: All file handles for your system are
currently in use. No more are available.

ANS1237E Server problem. Please see error log. ANS1245E Format unknown
Explanation: This is a server problem. Explanation: TSM tried to restore or retrieve a file, but
it had an unknown format.
check the error log. User Response: See your system administrator.
ANS1238S Internal Error. Please see error log. ANS1246E A command-line argument exceeded the
maximum length (maximum length) for a
Explanation: Server problem. Invalid policy binding.
single token.
Explanation: Command-line arguments may not
User Response: Have your service representative exceed maximum length characters.
User Response: Correct the command and retry the
ANS1241E File is in use; Write permission denied.
operation.
Explanation: The current file cannot be opened to
write to because it is currently being run by another
ANS1247I Waiting for files from the server...
operation.
Explanation: Restore request has been sent to the
server. The wait time depends on how many files you
User Response: Stop the operation that is running the are restoring.
System Action: TSM waits for files to restore from the
file to a different name or directory.
server.
ANS1242E Too many symbolic links were detected
while resolving name
ANS1248E An active restore for the same source
Explanation: While trying to resolve the file name, too
file specification exists. Unable to
continue with this request.
Explanation: Currently, there is an active restore for
User Response: Ensure that you do not have a the same source file specification. Another restore of the
looping symbolic link for the file. same source file specification cannot be started.
System Action: The requested restore fails.
ANS1243E File name too long
User Response: Start another restore with a different
Explanation: The file name specified is too long to be source file specification.
handled by TSM.
System Action: File is skipped. ANS1249W Server cannot restart the last restore
request. Do you want to restore without
User Response: See the appropriate Using the restart or abort the request?
system, for the file names that are handled by TSM. Explanation: The restart restore token has expired.
The server cannot restart the restore from where it last
ended.
ANS1244E File system is locked by system
System Action: Processing stopped; waiting for user
Explanation: File system cannot be accessed because it intervention.
User Response: Retry the request without restart or
System Action: TSM cannot complete the operation. abort the request.
ANS1251E File system/drive not ready
Explanation: The file system/drive was not ready for
access.

User Response: Ensure that the drive is available to
ANS1257E Error preparing object for restore.
TSM, and then retry the operation.
Explanation: Clean-up failed due to an internal
system error.
ANS1252E File system/drive is bad. A directory
exists that is missing either a ’.’ or ’..’ System Action: Please see error log for more details.
entry. Have your service representative
User Response: Please see your system administrator
for assistance.
Explanation: The drive was not available for access. A
directory exists that does not have either a '.' or '..'
ANS1258E The image snapshot operation failed.
entry.
Explanation: TSM was not able to take a snapshot of
the specified volume. Please refer to the error log for
User Response: Ensure that the drive is operational, more information on the cause of failure.
and then retry the operation. If unsuccessful, have your
service representative check the error log.
ANS1253E File input/output error
ANS1259E The image snapshot operation failed
Explanation: An error was found while reading from
during: .
or writing to the file.
Explanation: During the image snapshot backup TSM
System Action: File or file system is skipped.
encountered an error while performing the specified
User Response: Check your system to ensure that it is task.
operating properly. For OS/2, run CHKDSK /F for the
failing drive which can be found in dsmerror.log.
ANS1254E File write error
ANS1260E File is being recalled or has been
Explanation: An error was found while writing to the
recalled.
file.
Explanation: The file is being recalled by another
process or has been recalled.
operating properly.
User Response: None
ANS1255E File exceeds system/user file limits
ANS1261W The archive description you specified is
Explanation: A file being restored or retrieved exceeds
the empty string. TSM will use the
system set limits for this user.
default description (Archive Date:
System Action: File skipped. current date).
User Response: Ensure that the system limits are set Explanation: The description option on the archive
properly. command may not specify a null string.
System Action: Processing continues, and the
ANS1256E Cannot make file/directory description option is ignored.
Explanation: The directory path for files being User Response: None. Specify at least one character in
restored or retrieved cannot be created. the description
ANS1262E Password is not updated. Either an
invalid current password was supplied
authorization to create the directory for file being
or the new password does not fulfill the
restored or retrieved. Make sure that you have write
server password requirements.
access.
Explanation: The password is not updated because of
one of the following reasons:
v You entered an incorrect current password or
v You entered a new password that does not fulfill the
password length requirements set on the server.

System Action: The password is not updated on make sure that there is no FSM mount for that
server. filesystem; if it is still there then unmount it. If
unsuccessful, see your system administrator for more
User Response: Enter another password.
information.
ANS1263E The active policy set does not contain

ANS1267E The management class for file file-name
any backup copy groups. Unable to
does not allow migration. This file will
continue with selective backup.
not be migrated.
Explanation: You tried to do a selective backup and
have specified a policy set that does not contain a
not allow migration
backup management information (the copy group).
System Action: TSM did not backup the file.
User Response: Either have the TSM administrator
User Response: Create a management class that has a
change the Space Management Technique within the
backup copy group, bind the file to that management
management class to a value other than NONE or
class in your include-exclude list, and retry the
change the include/exclude list to specify a
operation. If unsuccessful, see your system
management class with the appropriate Space
administrator for more information.
Management Technique value.
ANS1264E The active policy set does not contain

ANS1268E This file has been migrated.
any archive copy groups. Unable to
continue with archive. Explanation: File has been migrated. If files that are
hard linked together are migrated then files subsequent
Explanation: You tried to archive a file or group of
to the first one encountered get this.
files and have specified a policy set that does not
contain an archive management information (the copy System Action: File is skipped.
group).
System Action: TSM did not archive the file.
User Response: Create a management class that has ANS1269I File is implicitly excluded.
an archive copy group, assign the file to the
management class, either through your include-exclude
that is implicitly excluded.
list or with the ARCHMC option, and retry the
operation. If unsuccessful, see your system System Action: TSM will not back up or migrate an
administrator for more information. implicitly excluded file.
ANS1265E Encountered bad mount or filesystem,
processing stopped.
ANS1271E Error Loading WINSOCK.DLL - not in
Explanation: The getmnt system call returned an error Search Path
indication. Error was encountered trying to determine
what the mounted file systems are. Explanation: TSM cannot find the Windows Socket
support file (WINSOCK.DLL) in the current search
System Action: Processing stopped. Cannot recover. path. This message only applies when using TCP/IP
communications.
User Response: There is a bad file system or mount
point on your system. Look at file systems and mounts, System Action: Connection to server fails.
and correct any errors. If unsuccessful, see your system
administrator for more information. User Response: Shut down Windows and place the
directory where this file resides in the DOS path
statement.
ANS1266E Encountered bad mount or filesystem,
processing stopped.
ANS1272E The logical volume snapshot agent is
Explanation: An error was encountered trying to not available for this volume.
determine what the mounted file systems are.
Explanation: During the image snapshot backup TSM
System Action: Processing stopped. Cannot recover. was not able to communicate with the logical volume
snapshot agent (LVSA).
User Response: There is a bad filesystem or mount
point on your system. Look at file systems and mounts, System Action: Processing stopped.
and correct any errors. If you used to have an FSM
(HSM) file system but then removed HSM from it, User Response: Please verify that the LVSA is

correctly installed on your system. If the problem virtual mount points will be expired when the file
persists please contact your TSM administrator. system is unmounted.
System Action: The virtual mount point is ignored.
ANS1273E The image plugin was not able to
User Response: Delete the virtual mount point.
acquire an exclusive lock on volume:
Explanation: To perform an off-line image backup or
ANS1286E -nasnodename option required for this
an image restore TSM requires exclusive use of the
operation.
volume.
Explanation: User issued a NAS related command and
NASNodename option is missing.
User Response: Please verify that no other application
System Action: Operation aborted.
is accessing the volume. If this volume is being
accessed by applications that can not be shutdown User Response: Use -nasnodename option with the
during backup then perform an online image backup command or place nasnodename option in the option
(snapshot with LVSA) instead. During restore of an file.
image TSM must have exclusive use of the volume.
ANS1287E Volume could not be locked.

ANS1274E Error Loading WINSOCK.DLL
Explanation: The system call to lock the volume
Explanation: Error loading the Windows socket failed.
support file into memory. This error only applies when
using TCP/IP communications. System Action: Processing stopped.
System Action: Connection to server fails. User Response: Please verify that no other application
is accessing the volume. If this volume is being
User Response: Because this error is caused by accessed by applications that can not be shutdown
insufficient memory, shut down running applications during backup then perform an online image backup
and retry. If the problem persists, see your system (snapshot with LVSA) instead. During restore of an
administrator. image TSM must have exclusive use of the volume.
ANS1275E Error Loading Function(s) from ANS1288E The image plugin is not supported on
WINSOCK.DLL this platform.
Explanation: Error loading one or more functions Explanation: TSM does not support image operations
from the Windows socket support file. on this platform.
System Action: Connection to server fails. System Action: Processing stopped.
User Response: Since this might possibly be caused User Response: Contact your TSM administrator.
by insufficient memory, shut down running
applications and retry. If the problem persists, see your
system administrator. ANS1301E Server detected system error
Explanation: The server detected a system error and
ANS1278W Virtual mount point ’filespace-name’ is a notified the clients.
file system. It will be backed up as a System Action: Processing stopped.
file system.
User Response: See your system administrator for
Explanation: A virtual mount point that is a file further information on server activity.
system is invalid and should be deleted.
System Action: The virtual mount point is ignored. ANS1302E No objects on server match query
User Response: Delete the virtual mount point. Explanation: No objects on the server match the query
operation being performed. If this object is part of a
ANS1279W Virtual mount point ’filespace-name’ backupset generated on a node, and the node name is
cannot be used in a file system handled changed on the server, any backup set objects that were
by automounter and is ignored. generated prior to the name change will not match the
new node name.
Explanation: Virtual mount points cannot be used in a
file system handled by automounter. If virtual mount System Action: Processing stopped.
points reside in a file system that is processed from an User Response: Ensure the names are properly
automounter, the backed up files underneath the entered. If the object is part of a backupset generated

prior to a node name change, ensure that the node
ANS1309W Requested data is offline
name is the same as the node for which the backup set
was generated. Explanation: For the restore or retrieve operation, one
or more of the requested files must be recalled from
offline storage media (generally tape). The wait time
ANS1303E Client ended transaction
depends on your site’s offline storage management
Explanation: The client system ended the operation policies.
with the server and ended the current transaction.
System Action: TSM waits for offline storage media to
System Action: Processing stopped. become available and then continues.
User Response: Restart the session. User Response: None.
ANS1304W Active object not found ANS1310E Object too large for server limits
Explanation: TSM did not find an active object Explanation: The object is too large. The configuration
flagged for expiration on the server. The object is of the server does not have any data storage space that
marked as expired by another TSM operation. accepts the object.
System Action: None. System Action: File skipped.
User Response: None. User Response: See your system administrator to

determine the maximum file (object) size for which
your site’s server is configured.
ANS1305E No data on server
Explanation: TSM tried to do a restore or retrieve on ANS1311E Server out of data storage space
an object that has no data associated with it.
Explanation: The server does not have any space
System Action: TSM ended the current operation. available to store the object.
User Response: See your system administrator to System Action: TSM ended the current operation.
verify the problem. If the problem continues, see your
system administrator. User Response: You can take any of the following
actions:
ANS1306E Bad verifier v Request the system administrator to add space to the
storage pool.
Explanation: You entered an incorrect password v For TSM client, set COMPRESSALWAYS=NO and
(verifier). COMPRESSIon=YES in the options file (DSM.OPT),
System Action: Processing stopped. then the file will be resent uncompressed if it grows
during compression.
User Response: Retry the session with the correct
v For API Applications, consult the application’s
password.
documentation for recommendations regarding
compression.
ANS1307E Node in use v Turn off disk caching in the disk storage pool, and
Explanation: The node you are running on is in use issue MOVE DATA commands to each disk pool
by another operation on the server. This might be from volume to clear out the cached bitfiles.
another client or from some activity on the server.
System Action: Processing stopped. ANS1312E Server media mount not possible
User Response: Retry the operation, or see your Explanation: Server media mount not possible. The
system administrator to see what other operations are server timed out waiting for a mount of an offline
running for your node. volume.
ANS1308E Expiration date must be greater than User Response: Retry later when server volumes can
today’s date be mounted. Ensure that the MAXNUMMP (maximum
Explanation: Archive expiration date is too low, the number of mount points) defined on the server for this
date must be greater than today’s date. node is greater than 0.

User Response: Retry archiving the file with an
expiration date that is higher than today’s date.

ANS1313E Size estimate exceeded ANS1317E The server does not have enough
database space to continue the current
Explanation: The total amount of data for a backup or
operation
archive operation exceeds the estimated size originally
sent to the server for allocating data storage space. This Explanation: The server ran out of database space.
happens when many files are growing by large
amounts while the backup or archive operation is in
session. User Response: See your system administrator.
ANS1318E The server does not have enough
memory to continue the current
continues, check what other processes are running on
operation.
the client machine that are generating large amounts of
data. Disable those operations while the backup or Explanation: The server ran out of memory.
archive operation is taking place.
ANS1314E File data currently unavailable on server User Response: This is a temporary problem. Retry
later or see your system administrator.
Explanation: The file data is currently unavailable on
the server. A retrieve or restore operation was
attempted. Possible causes are: ANS1319E An error occurred while trying to
v Data was corrupted at the server rename this file space:
v Server found a read error Explanation: This operation cannot be completed
v File is temporarily involved in a reclaim operation at because the file space could not be renamed.
the server
v Server requested a tape volume that was marked System Action: TSM ended the current operation.
unavailable. User Response: Contact system administrator for
System Action: Processing stopped. more information.

continues, see your system administrator to determine ANS1320E The specified file space does not exist
the problem from the server console or the activity log. on the server. The file space might have
Check whether any requests were made for a tape been deleted by another client or an
volume that was unavailable. A tape volume may be administrator.
marked unavailable if prior read errors were Explanation: The specified file space does not exist on
encountered or the volume is checked out of the tape the server. Your system administrator deleted the file
library. space or another client using your client’s node name
deleted it.
ANS1315E Unexpected Retry request System Action: TSM canceled the current operation.
Explanation: Unexpected Retry request. The server User Response: Check the file space name to see if it
found an error while writing data to the server’s data is correct, and retry the operation.
storage.
System Action: Client retries the operation. ANS1321S Open Registration failed because the
User Response: None. specified node name is defined in the
server
ANS1316E The server does not have enough Explanation: Open registration failed because a node
recovery log space to continue the is defined in the server with the same name.
current operation System Action: TSM canceled the current operation.
Explanation: The server ran out of recovery log space. User Response: Retry with another node name.
User Response: This error is a temporary problem. ANS1322S Open Registration failed because no
Retry later or see your system administrator. default domain exists
Explanation: Open registration failed because a
default policy domain does not exist for you to place
your node.

ANS1334E Restoring a volume mount point to a
non-empty directory.
ANS1323S Open Registration failed because an
Explanation: You are trying to restore a volume
invalid node name was specified
mount point to a non-empty directory which is not
Explanation: Open registration failed because the allowed. Volume mount point is not restored.
specified node name contains invalid characters.
User Response: Retry with another node name that
does not have any invalid characters.
ANS1335E Attempt to import RSM database files
failed. No changes effected.
ANS1326S Unexpected Wait For Space from the
Explanation: An error occurred while importing the
server
RSM database files. The database will not be updated.
Explanation: The client received an unexpected Wait Reboot the machine and then restore RSM again.
For Space message from the server.
User Response: Ask your system administrator to
User Response: See your system administrator. check the error log.
ANS1329S Server out of data storage space ANS1336I RSM service must be restarted for
changes to become effective.
Explanation: The server does not have space available
to store the object. Explanation: RSM database files have been restored
from the server and imported. The RSM service must
System Action: TSM ended the current operation. be restarted for the updates to become effective.
User Response: Report to your system administrator System Action: Processing continues.
that a storage pool on the server is full.
ANS1330S This node currently has a pending
restartable restore session. The ANS1337I Restarting the RSM service...
requested operation cannot complete
Explanation: RSM database files have been restored
until this session either completes or is
from the server and imported. TSM is about to stop
canceled.
then restart the RSM service.
Explanation: This operation can not be completed
because a restartable restore session is pending. The
operation is not allowed because the restartable session User Response: None.
and the current operation affect the same file space.
System Action: TSM ended the current operation. ANS1338I Restart of the RSM service is completed.
User Response: Issue a query restore to see the Explanation: RSM database files have been restored
conflict. Issue the cancel restore command to delete any from the server and imported. TSM has restarted the
unneeded restartable restore sessions. RSM service on the user’s behalf.
ANS1331E Only a TSM authorized user can
perform this Action.
Explanation: User must be a TSM authorized user to
ANS1339E Restart of the RSM service failed.
perform this action. User is not password authorized
Restart the RSM service manually.
and this action requires authorization.
from the TSM server and imported. TSM has tried to
User Response: User must be root user, or user must restart the RSM service on the user’s behalf but has run
be the owner of the executable and the set effective into a problem.
user id bit is set to ’on’ (’s’ bit).
User Response: Restart the RSM service manually.

administrator to isolate the problem through use of the
ANS1340E Exporting RSM database files failed. No
server console.
files will be backed up.
Explanation: An error occurred while exporting the
ANS1351E Session rejected: All server sessions are
RSM database files. The database will not be backed
currently in use
up.
Explanation: TSM has all available sessions in use and
cannot accept a new one at this time.
continues, see your system administrator to increase the
ANS1341E Delta file ’delta-file-name’ already exists
number of concurrently active sessions to the server.
on client cache.
Explanation: The number defining the correspondence
ANS1352E Session rejected: Password has expired
between drive letter or file (domain name) and volume
label is not known to the server. Explanation: Your TSM password has expired.
System Action: Processing stopped. System Action: TSM canceled the current operation.
You are not allowed to connect to the server until the
User Response: Report the program error to your
password is updated.
User Response: Update your password.
ANS1342E Client cache is locked; unable to
continue with operation. ANS1353E Session rejected: Unknown or incorrect
ID entered
Explanation: The client cache is currently locked by
another process. Explanation: The node name you entered is not
known by the server, or you are attempting to access a
file migrated to a different node.
You are not allowed to connect to the server until your
node name is registered with the server. If attempting
ANS1343E Wrong Key entered; unable to restore to access a migrated file, your nodename must be the
the file. same node which migrated the file.
Explanation: Key entered does not match the key User Response: Ensure that you entered your TSM
used for the backed up file. node name correctly. If yes, see your system
administrator. Verify that the server is using closed
registration and that your node name is registered with
User Response: Recollect the key used for backup. the server.
ANS1344E Job is running in the background. ANS1354E Session rejected: Duplicate ID entered
Cannot prompt for the Key.
Explanation: Another process using this node name is
Explanation: When jobs are run in the background, active with the server.
the client cannot prompt for the key.
System Action: TSM cannot connect to the server.
System Action: Processing stopped. TSM canceled the current operation.
User Response: Run the Job in the foreground. User Response: If you are running a UNIX-based
system, ensure that another process is not active with
TSM under the same name. Also, ensure that your
ANS1345E No objects on server match node name is unique to the server so that it cannot be
’object-nameobject-nameobject-name’ used by another person. See your system administrator
Explanation: The specified file (object-name) does not to identify the owner of that node name.
have a match on the server.
User Response: Backup the file and retry the
operation. If the problem continues, see your system

ANS1355E Session rejected: Server disabled
Explanation: The server is in a disabled state and
ANS1361E Session Rejected: The specified node
cannot be accessed for normal activity.
name is currently locked
Explanation: The node name you specified is currently
User Response: Retry the operation after the server locked on the server.
returns to an enabled state. If the problem continues,
see your system administrator.
to find out why your node name is locked.
ANS1356E The server is not configured to allow
open registration
ANS1362S SLM LICENSE EXCEEDED: The client
Explanation: No authorization. Registration is
licenses for TSM are exceeded. See your
required by your system administrator. The server is
not configured to allow open registration.
Explanation: Adding a new enrollment will exceed the
System Action: Session not started.
product license count for TSM.
User Response: You must obtain a TSM node and
System Action: Execution of the client enrollment or
password from your system administrator.
connection request ends.
ANS1357S Session rejected: Downlevel client code
version
ANS1363E Session Rejected: The server does not
Explanation: The server version and your client
have enough memory to allow a
version do not match. The client code is downlevel.
connection to be established.
Explanation: The server does not have enough
User Response: See your system administrator to see memory to allow your client to establish a connection
what version of TSM to run for your location. with the server.
ANS1358S Session rejected: Downlevel server code
User Response: Retry later or see your system
version
administrator.
Explanation: The server version and your client
version do not match. The server code is downlevel.
System Action: TSM canceled the current operation. have enough recovery log space to allow
a connection to be established.
User Response: See your system administrator to see
what version of TSM to run for your location. Explanation: The server ran out of recovery log space.
ANS1359E Session Rejected: The specified node
User Response: This error is a temporary problem.
name is currently in use
Retry later or see your system administrator.
Explanation: The node name you specified is in use
on the server.
System Action: Session was not started. have enough database space to allow a
connection to be established.
User Response: The server is probably performing a
task that prevents your node from establishing a Explanation: The server ran out of database space.
session. Retry later or check with your system
administrator.
ANS1360I Compressed Data Grew
ANS1366E Session Rejected: The server has an
Explanation: The size of the file after compressesion is
internal error
greater than the size of the file before compressed.
Explanation: The client cannot establish a connection
System Action: Even though the size of the file
to the server because of an internal server error.
increased, the file is compressed.

User Response: See your system administrator
ANS1372E An inconsistency was detected between
immediately.
the client node and the node that is
registered to the TSM server.
Explanation: The user has probably coded the node
allow a signon as a Unicode enabled
option incorrectly. For instance, the node that is
client
registered to the TSM server might be a type of NAS,
Explanation: The client can not establish a connection but the node is actually a non-NAS client.
to the server because of a unicode enabling mismatch
System Action: The TSM operation ends.
between server and client.
User Response: Ensure that the node name is correct
in the client options file. Make sure to use a node of
User Response: See your system administrator type NAS only with the nasnodename option.
immediately.
ANS1403E Error loading a required DLL
ANS1368S Session Rejected: The server is not
licensed for this platform type. See your
dynamic link library. The DLL load failed.
Explanation: The server is not licensed for the
requesting client type. User Response: Verify that your system software is up
to date and that all DLLs required by the TSM client
are present.
ANS1404E Error loading one or more functions
from a required DLL
ANS1369W Session Rejected: The session was
canceled by the server administrator.
function from a dynamic link library. The DLL load
Explanation: The server administrator canceled the failed.
current client session.
System Action: Execution of the client connection
User Response: Verify that your system software is up
request ends.
to date.
ANS1405I ’service-name’ service needs to be
ANS1370E The user ID entered does not have the restarted.
correct level of authority to access the
Explanation: The service must be restarted for the
client machine.
restored changes to take effect.
Explanation: The user ID entered cannot access this
System Action: Changes are not effected.
TSM client.
User Response: Restart the service.
User Response: Grant authority to this user ID on the
ANS1409E The remote copy process process ID on
TSM server so that it can access this TSM client.
server could not be canceled.
Explanation: A remote copy operation with process id
ANS1371E Unable to reconstruct ’’ from subfile
process ID, which is in progress on server, could not be
components.
canceled. Check your error log to see cause of failure.
Explanation: An error occurred while reconstructing
this file from its subfile components.
User Response: Please check error log for more
ANS1410E Unable to access the network path.
information.
Explanation: The network path cannot be accessed
due to a possible network problem.
System Action: The client terminates.

User Response: Ensure that the network is up and the
ANS1415W Resetting enableserverfree option. This
path can be accessed using a system command, and
operation will continue without
server-free data movement.
Explanation: Server-free data movement is not
ANS1411E A communication session was dropped.
possible due to the reason described by the preceding
Explanation: A communication session was dropped message.
due to a possible network problem.
System Action: The requested operation will continue
System Action: The client terminates. without server-free data movement.
User Response: Ensure that the network is up and User Response: Contact your TSM administrator to
retry the operation. correct problems with server-free data movement.
ANS1412E Directory or file has bad EA data or ANS1416W Management class name to which
inconsistent data. volume filespace-name is bound does not
allow server-free data movement.
Explanation: Directory or file has bad EA data or
inconsistent data. Explanation: The management class to which this
filespace-name is bound does not have a server-free path
System Action: The client terminates. to the destination storage pool. This message is also
User Response: Check failing directory or file for bad reported when server-free data movement is not
EA data. Copy the directory to a new location and retry enabled on server using ″set serverfree status=on″.
the operation. System Action: The requested operation will continue
with out server-free data movement.
ANS1413W File ’filespace namepath-namefile-name’ is User Response: Contact your TSM administrator to
not recognized by the system as a disk allow server-free data movement from this system.
file and cannot be processed. The file is
skipped.
ANS1417W An error occured while obtaining
Explanation: The client is unable to process file types physical extent map for volume
that are not ’disk’, such as ’character’ and ’pipe’. This filespace-name.
message is typically, but not always, issued for file
names that are normally reserved for the operating Explanation: An error occured while obtaining
system. In the Windows environment, reserved names volume’s filespace-name logical and physical layout.
include AUX, CON, NUL, PRN, COMx or LPTx, where
System Action: The requested operation will be
’x’ is any digit from 1 to 9 (for example, COM1, LPT3,
retried with out server-free data movement.
etc.).
User Response: Contact your TSM administrator to
System Action: The file is skipped.
correct problems with server-free data movement.
User Response: Either delete the file if you do not
need it, or else use an EXCLUDE statement in the client
ANS1418W A call to TSM API API-name failed.
options to prevent the client from trying to process the
file. In the Windows environment, normal delete Explanation: An unexpected error occured while
commands will most likely not work. You will need to performing server-free data movement.
prefix the file name with the characters ’\\.\’. For
example, ″del c:\mydir\lpt4″ will not work, but ″del
\\.\c:\mydir\lpt4″ will work.
ANS1414W Don’t have sufficient authority to delete
open group on server.
ANS1419W Remote copy operation for volume
Explanation: An open image group exists on the TSM
filespace-name failed or could not be
server and cannot be deleted due to missing backup
restarted, return code retcode.
delete rights for this node.
Explanation: An error occurred on server when
starting or during the remote copy operation for
User Response: Ask your TSM administrator to grant volume filespace-name.
backup delete rights for your node.

ANS1425W Retry of failed image operation for
volume filespace-name is not possible due
to severe error.
ANS1420W Server-free path is not available for one
Explanation: A retry of image operation is not
or more disks for volume filespace-name.
possible, because an unrecoverable TSM client or server
Explanation: One or more disks used for volume error has occured. Check your error log to see cause of
filespace-name does not have server-free path available. failure.
System Action: The requested operation will be System Action: None.

ANS1426E An error occurred creating the Backup
Registry Directory structure
ANS1421E The image object object-type was not
Explanation: An error occurred while creating the
found on server.
directory structure to the save/replace registry key.
Explanation: The image object type filespace-namecould
System Action: Registry function fails.
not be located on the server.
ANS1427I Registry Backup function completed
successfully.
ANS1422W The image data for volume filespace-name
Explanation: Registry backup was successful.
is either compressed or its compression
information can not be determined. System Action: None.
Explanation: The image data was backed up either User Response: Continue with normal operations.
with compression or by an older client version. This
data format cannnot be restored on server-free path.
ANS1428E Registry Backup function failed.
retried without server-free data movement.
registry.
System Action: Registry backup function fails.
ANS1423W The image for volume filespace-name was
backed-up in old format.
ANS1429I Registry Restore function completed
Explanation: The image data was backed up in old
successfully.
image (single object) format. This data format cannnot
be restored on server-free path. Explanation: Registry Restore was successful.
System Action: The requested operation will be System Action: None.
User Response: Continue with normal operations.
ANS1430I The machine must be rebooted for the
ANS1424W Retrying failed image operation for changes to take effect
volume filespace-name.
Explanation: The machine must be started for the
Explanation: The transaction for image operation for restored registry changes to take effect.
volume filespace-name failed due to reason described by
earlier message(s). System Action: None
System Action: The requested image operation will be User Response: Reboot the machine
retried again.
User Response: None. ANS1431E Registry Restore Function Failed.
Explanation: An error occurred while restoring the
registry key(s) from the server.
System Action: Registry restore function fails.

ANS1438E Event Log Backup function failed.
ANS1432E Keyword Expected after keyword
event logs.
’keyword’.
System Action: Event log backup function fails.
Explanation: A registry command was incorrectly
entered. User Response: See your system administrator.
System Action: Registry function is not invoked.
ANS1439I Event Log Restore function completed
User Response: Refer to the command reference for
successfully.
this command.
Explanation: Event Log Restore was successful.
ANS1433E Extraneous argument ’input’ after System Action: None.
keyword ’keyword’
entered.
ANS1440E Event Log Restore Function Failed.
System Action: Registry function not invoked.
User Response: Refer to the command reference for event log(s) from the server.
this command.
System Action: Event Log Restore function fails.
ANS1434E Invalid argument ’input’ after keyword
’keyword’
ANS1441E Keyword Expected after keyword
’keyword’.
entered.
Explanation: A event log command was incorrectly
System Action: Registry function not invoked.
entered.
System Action: Event Log function is not invoked.
this command.
this command.
ANS1435E An Error Occurred saving the Key.
ANS1442E Extraneous argument ’input’ after
System Action: Registry backup operation terminates. keyword ’keyword’
User Response: See your system administrator. Explanation: A event log command was incorrectly
entered.
ANS1436E An Error Occurred replacing the Key. System Action: Event Log function not invoked.
Explanation: The backed up registry key is restored User Response: Refer to the command reference for
from the server but cannot be made active into the this command.
registry.
System Action: Current Registry key remains active. ANS1443E Invalid argument ’input’ after keyword
’keyword’
Explanation: A event log command was incorrectly
entered.
ANS1437I Event Log Backup function completed
successfully. System Action: Event Log function not invoked.
Explanation: Event Log backup was successful. User Response: Refer to the command reference for
this command.
ANS1444E An error occurred creating the Backup
Registry Directory structure
Explanation: An error occurred while creating the
directory structure to the save/replace registry key.

System Action: Registry function fails.
ANS1469I Error processing ’filespace
User Response: See your system administrator. namepath-namefile-name’: invalid
encryption key
ANS1445E ERROR: could not create NAS image Explanation: Key entered does not match the key
object. used for the backed up file.
Explanation: Creation of the NAS image object failed System Action: Processing stopped.
for one of following reasons:
User Response: Recollect the key used for backup.
v An unauthorized user invoked the NAS command
v NAS operations are not supported on the current
ANS1473E Session rejected: TCP/IP connection
platform
failure for Shared Memory
v Cannot find the NAS plugin library.
Explanation: An attempt to connect to the local server
System Action: The requested NAS operation is not using the Shared Memory protocol has failed during
performed. initial TCP/IP communications. This error can occur if
User Response: Retry the operation after correcting the server is not listening on the correct port, or if the
the cause for failure. server is down.
System Action: Session rejected. Processing stopped.
ANS1446W The volume layout of name is not User Response: Retry the operation, or wait until the
supported by server-free. server comes back up and retry the operation. If the
Explanation: The logical volume layout is not problem continues, see your system administrator for
currently supported by server-free. further help.
System Action: Processing continues using

non-server-free data movement. ANS1474E An error occurred using the Shared
Memory protocol
User Response: Refer to the documentation for
information on what volume layouts are supported by Explanation: An error has occurred while reading or
server-free. writing data through the Shared Memory
communications protocol.
ANS1447I Current user does not need to back up System Action: TSM cannot complete the requested
the default profile. operation.
Explanation: You are currently using the default User Response: Check the trace log for additional
profile, and there is no need to back it up. information and retry the operation. If the problem
continues, see your system administrator for further
System Action: None. help.
ANS1475E Insufficient authority to connect to the
shared memory region
ANS1448E An error occurred accessing NTFS
security information Explanation: The user issuing the command does not
have authority to connect to the shared memory
Explanation: An error occurred while attempting to
segment. When the shared memory segment is created
access NTFS security information.
by the server, it will be owned by the effective uid of
System Action: Object will not be processed. the server process (dsmserv). Only processes running
under this uid or root will be allowed to connect to the
User Response: See your system administrator or
segment (and thus to the server).
bypass by using SkipNTSecurity option.
System Action: The session is rejected and processing
stops.
ANS1449E A required NT privilege is not held
User Response: Run the command under the uid of
Explanation: The user account running TSM does not
the processing running dsmserv, if possible. Otherwise
possess a required NT user right/privilege for
contact your system administrator for further help.
performing the current operation.
System Action: Object will not be processed.

ANS1476E CLUSTERNODE is set to YES but the ANS1481E The CLUSTERNODE option is not
Cluster Information Daemon is not supported on this system.
started.
Explanation: This option is not supported on this
Explanation: The HACMP Cluster Information system.
Daemon must be started in order to specify the
CLUSTERNODE option.
User Response: Disable the CLUSTERNODE option in
the local options file.
User Response: Start the HACMP Cluster Information
Dameon.
ANS1482E An unexpected error (retcode) occurred
trying to obtain the cluster name from
ANS1477E CLUSTERNODE is set to YES but the the system.
cluster load library is not valid.
Explanation: An unknown error occurred while trying
Explanation: The load library that the operating to obtain the cluster name from the cluster services.
system provides to obtain the cluster name is not valid.
Possible causes are an out-of-date load library which
doesn’t contain the proper routines which this product User Response: Contact your system administrator for
is expecting. more information.
ANS1483I Schedule log pruning started.
User Response: Ensure that the latest cluster software
is installed on the system. Explanation: The schedule log pruning function has
begun.
ANS1478E CLUSTERNODE is set to YES but the System Action: The schedule log is pruned.
cluster software is not available on this
system. User Response: None.
Explanation: The load library that the operating

systems provides to obtain the cluster name is not ANS1484I Schedule log pruning finished
available on this system. successfully.
System Action: Processing ends. Explanation: The schedule log pruning function
completed with no errors.
User Response: Ensure that the cluster software is
installed on the system. System Action: None.
ANS1479E CLUSTERNODE is set to YES but this
machine is not a member of a cluster. ANS1485E Schedule log pruning failed.
Explanation: This machine is not a member of a Explanation: The schedule log pruning function failed.
cluster node. Possible causes are that the cluster service
has not been configured correctly or that the cluster is System Action: The schedule log pruning function
in the process of initialization. stops.
System Action: Processing ends. User Response: Retry the command with the tracing
turned on to help determine why the pruning function
User Response: Ensure that the cluster software is failed.
configured properly. If the cluster is in the process of
initialization, retry the operation at a later time.
ANS1486E Restoring WMI repository failed. No
changes will be in effect.
ANS1480E CLUSTERNODE is set to YES but the
cluster service is not enabled on this Explanation: An error occurred while restoring the
system. WMI repository. The database will not be updated.
Explanation: The cluster service has not been enabled System Action: Processing stopped.
on this system. User Response: Ask your system administrator to
System Action: Processing ends. check the error log.
User Response: Enable the cluster service on the

system.

ANS1487E Backing up WMI repository failed. No
operation.
files will be backed up.
User Response: Check the VIRTUALMOUNTPOINT
in the system options file and make sure it is accessible.
WMI repository. The database will not be backed up.
Retry the operation.
User Response: Ask your system administrator to ANS1494S Invalid virtual mountpoint filespace-name:
check the error log. Symbolic link.
Explanation: The specified VIRTUALMOUNTPOINT
ANS1489E The WMI service failed to stop. No files in the system options file is invalid because it is a
will be restored. symbolic link and FOLLOWSYMBOLIC is not set.
Explanation: An error occurred while stopping the System Action: TSM attempts to continue the current
WMI service. The database will not be restored up. operation.
System Action: Processing stopped. User Response: Set the option FOLLOWSYMBOLIC to
YES in the user options file. Retry the operation.
ANS1495S Invalid virtual mountpoint filespace-name:
Other error, rc = return-code.
ANS1490W File specification ’file-spec’ ignored. A
file list has already been specified. Explanation: The specified VIRTUALMOUNTPOINT
in the system options file is invalid.
Explanation: A non-option argument (file
specification) was encountered after the -FILELIST has System Action: TSM attempts to continue the current
been processed. operation.
System Action: The argument is ignored. User Response: Make sure the virtual mountpoint is a
directory and accessible from the shell, and retry the
User Response: You may have either a -FILELIST or
operation.
explicit file specifications on this command, but not
both.
ANS1496W Duplicate include/exclude option ’option
file-name’ found while processing the
ANS1491E Only one -FILELIST option allowed.
client options file. This might produce
Explanation: The -FILELIST option may only be unexpected results.
specified once per command
Explanation: TSM found a duplicate statement while
System Action: The command is not executed. processing the client options file, which might produce
unexpected results.
User Response: Enter only one -FILELIST option on
the command. System Action: Processing continues.
User Response: Verify if you obtained the desired
ANS1492S Invalid virtual mountpoint filespace-name: results. If not, you need to correct the client options file
File not found. by removing the duplicate option statement.

in the system options file is invalid because it could not ANS1497W Duplicate include/exclude option ’option
be found in the file system. file-name’ found while processing the
client options passed by the server. This
System Action: TSM attempts to continue the current might produce unexpected results.
operation.
Explanation: TSM found a duplicate statement while
User Response: Check the virtual mountpoint in the processing the client options by the server, which might
system options file and make sure it exists in the file produce unexpected results.
system. Retry the operation.
ANS1493S Invalid virtual mountpoint filespace-name: User Response: Verify if you obtained the desired
Access denied. results. If not, you need to correct either the client
options file or the client options passed by the server.
in the system options file is invalid because access to it
is denied.

ANS1498E The IIS services failed to stop. No files ANS1504E Error starting the Trusted
will be restored. Communication Agent process.
Explanation: An error occurred while stopping the IIS Explanation: An error has occurred starting the
services. The metabase will not be restored up. Trusted Communication Agent process; specifically, the
fork() function has failed.
check the error log. User Response: Probable system error. If the problem
persists, restart the workstation.
ANS1500E Module dsmtca not found in secure
directory. ANS1505E Trusted Communication Agent has
terminated unexpectedly.
Explanation: TSM cannot find the Trusted
Communication Agent module (dsmtca) in the Explanation: The Trusted Communication Agent has
appropriate directory. terminated unexpectedly.
System Action: TSM ends. System Action: TSM ends.
User Response: Log on as root user, then create a link User Response: Check the error log for more
to dsmtca module in /usr/bin with the command: ln -s information. Retry the activity. If the problem persists,
/usr/tivoli/tsm/client/ba/bin/dsmtca contact your service representative.
/usr/bin/dsmtca
ANS1506E Trusted Communication Agent received
ANS1501E Trusted agent execution/owner invalid request.
permissions are invalid
Explanation: The Trusted Communication Agent has
Explanation: The Trusted Communication Agent received an unknown request from the TSM client.
execution/owner permissions are invalid.
User Response: Internal error. If the problem recurs,
User Response: Have your system administrator contact your service representative.
check the installation instructions for the client to
ensure that the Trusted Communication Agent
ANS1507E This action requires TSM administrative
permissions are set correctly. This error can be caused
authority on this system.
by installing TSM as a non-root user. For the UNIX
platforms that have the installation program Explanation: An activity has been attempted that must
(dsm.install), you must run dsm.install while logged in be performed by the TSM administrator (for example,
as the root user. open registration, filespace delete or password update).
ANS1502E Access to system function required to
run has been denied User Response: If the activity is required, the
administrator for this system must perform it.
Explanation: The permissions of the Trusted
Communication Agent do not allow it to be accessed
by the user of the TSM client. ANS1508E Error allocating semaphores.
System Action: TSM ends. Explanation: An error has occurred because the
semaphores you are attempting to allocate have become
User Response: See your system administrator. insufficient.
ANS1503E Valid password not available for server
’server-name’. The administrator for your User Response: Ask your system administrator for
system must run TSM and enter the assistance, and possibly increase the number of
password to store it locally. semaphores in your system.
Explanation: The file containing the stored password

for the specified server server-name is unavailable. ANS1509E Error setting semaphore value or
waiting on semaphore.
Explanation: An error has occurred while attempting
User Response: The administrator for your system to set or wait on a semaphore.
must set and store a new password.

User Response: Probable system error. If the problem If you are unable to determine what is wrong, report
persists, restart the workstation. the problem to your service representative.
ANS1510E Trusted Communications Agent error ANS1514W Encryption key passwords are not the
attaching shared memory. same.
Explanation: An error has occurred while attaching Explanation: The key passwords are different.
the trusted agent’s shared memory.
System Action: TSM allows you to try again.
System Action: Return to caller.
User Response: Enter the correct password.
User Response: Stop application, check shared
memory usage and retry the command. Read the
ANS1802E Incremental backup of ’file-name’
tca.log file for the system error number.
finished with number failure
Explanation: The incremental backup of the specified
ANS1511I Invalid Restore session number entered.
file-name completed with the specified number of
Try again.
failures.
list of restartable restores. The number you entered is
either less than one or greater than the highest item User Response: Check the reasons for the failures.
number displayed.
System Action: TSM waits for you to enter a valid ANS1803E Archive processing of ’file-space name’
selection. finished with failures.
User Response: Enter a number from the list or ’Q’ to Explanation: The archive of the specified file-space
quit. name completed with failures.
ANS1512E Scheduled event ’event’ failed. Return
code = value. User Response: Check the reasons for the failures.
Explanation: The scheduled event did not complete

successfully. ANS1804E Selective Backup processing of ’file-space
name’ finished with failures.
System Action: Scheduled event failed.
Explanation: The selective backup of the specified
User Response: Ensure that your environment is set file-space name completed with failures.
up correctly. If the problem continues, see your system
administrator to correct the problem. System Action: Processing continues.
User Response: Check the reasons for the failures.
ANS1513E The object ’’ is skipped from rename.
Error_condition. ANS1805E Unable to restore symbolic link
Explanation: TSM skips the specified object from ’file-name’.
renaming because the object with the same long name Explanation: The client operating system is not able to
but with different attributes exists on the server. create a symbolic link because the link points to a
System Action: The backup operation will continue. filename that is not given.
The specified object will be expired during the next System Action: Processing continues.
incremental backup.
User Response: Try the restore on a different
User Response: The object is skipped if one of the operating system.
following condition takes place:
The long name object(LN) has more recent insert
ANS1806W Size exceeded the maximum file size
date than the short name object(SN).
limit on your system for ’filespace
The management classes for LN and SN don’t namepath-namefile-name’ of ’file-size’.
match.
The copygroups for LN and SN don’t match.
has exceeded the maximum file size limitation on your
LN and SN have different owners. system.
The creation date for LN and SN don’t match.
The short name attribute for LN doesn’t match SN.
User Response: Restore or retrieve this file on a

system that supports the file size. See your system
ANS1814E Unable to start scheduled event ’event’
administrator.
Explanation: Scheduled event was no longer valid on
the server. Either the window has elapsed or the
ANS1807E Unable to recall file from server due to
schedule has been deleted.
error from recall daemon.
System Action: The client scheduler queries the server
Explanation: Unable to recall file. The recall daemon
to obtain the next scheduled event.
reported an error while trying to recall a file. Look in
the recall daemon’s error log for more information. This User Response: If the problem continues, see your
can happen if the server is down, the connection is system administrator to correct the problem on the
broken, or the file is missing on the server. It is also server.
possible that the migration server in the system option
file has been changed to a different server. The recall
ANS1815E Either the window has elapsed or the
daemon does not check the system option file for
schedule has been deleted
changes once it has started.
Explanation: Scheduled event was no longer valid on
the server.
User Response: See if the server is up, and retry. If the
System Action: The client scheduler queries the server
problem still exists, look in the error log. Also have the
to obtain the next scheduled event.
workstation administrator run dsmreconcile against the
file system and see if the file shows up in the User Response: If the problem continues, see your
.SpaceMan/orphan.stubs file. If system option file has system administrator to correct the problem on the
been changed, stop all recall daemons and restart the server.
master recall daemon to pick up the changes.
ANS1816E Invalid scheduling mode

ANS1809W Session is lost; initializing session
reopen procedure. Explanation: The mode entered for the scheduled
event was not correct.
Explanation: The session with the server has been
lost. System Action: Event does not occur.
System Action: The system will attempt to reestablish User Response: Enter the correct scheduling mode
session with TSM. and retry the operation.

ANS1817E Schedule function can only be run by a
TSM authorized user.
ANS1810E TSM session has been reestablished.
Explanation: An attempt to use the schedule function
Explanation: The session with the server has been failed because of improper authority.
reestablished.
System Action: Processing will now continue.
User Response: See the TSM authorized user for
User Response: None. schedule function information.
ANS1811S TSM session could not be reestablished. ANS1818E Schedule function not allowed in loop
mode.
Explanation: The session with the server has been
lost. Attempts to reestablish the session were Explanation: The operation cannot be scheduled
unsuccessful. Possible causes include, but are not during a loop mode.
limited to the following:
System Action: Event does not occur.
v The server has been halted.
v The network connection to the server is down. User Response: Enter the command again without the
loop.
v The communication program that TSM is interacting
with has encountered some problem.
ANS1819E Server cannot register address
System Action: Processing is stopped.
Explanation: An address for a server was entered that
User Response: Check network connection to the cannot be recorded.
server. Insure that the TSM server is running. Insure
that the communication program underlying TSM is System Action: Processing stopped.
working properly.
User Response: Ensure that you have the server

specified correctly, and retry the operation.
ANS1826E Unable to open trace output file
file-name.
ANS1820E Command line options must be
Explanation: A TRACEFILE option in the user
preceded by a ’-’
configuration file or on the command line used a
Explanation: An option was specified without a '–' directory path and file-name combination to which you
delimiter. do not have write access.
System Action: Processing stopped. System Action: Client program did not initialize.
User Response: Enter the command again with a dash User Response: Change the TRACEFILE value so that
preceding each option. it is a location to which you have write access.
ANS1821E Unable to start POSTSCHEDULECMD/ ANS1828E Screen size is too small for using the
PRESCHEDULECMD ’command’ PICK option.
Explanation: The requested action required a new Explanation: You cannot use the PICK option on a
process to be created. Either an option or a schedule workstation that has a screen smaller than 20 characters
“action” that requested an operating system command across and 10 lines down.
to be executed was entered.
System Action: TSM did not complete the operation.
System Action: Request is ignored.
User Response: Retry the operation using a
User Response: Remove the request from the options workstation that has a screen with the minimum size,
file or the schedule defined on the server. or do not use the PICK option.
ANS1823E Invalid trace keyword - ’keyword’ ANS1830E Unable to write to trace file tracefile.
Tracing disabled.
Explanation: A TRACEFLAG option in the user
configuration file or on the command line is incorrect. Explanation: An error occurred when writing to the
specified tracefile.
System Action: Client program did not initialize or
tracing was not enabled in the applet. System Action: Tracing is disabled. Processing
continues.
User Response: Correct the value. See the entry for
TRACEFLAGS in the Trace Facility Guide document for User Response: Ensure the device that the tracefile
a list of valid trace flags. access is available and has sufficient space for the
tracefile. Retry the command.
ANS1824E Invalid trace file name (name too long).

ANS1831E Password expired. The administrator for
Explanation: A TRACEFILE option in the preferences this system must run TSM to update the
files used a file name that is too long. password.
System Action: Client program did not initialize. Explanation: The password expired.
User Response: Change the file name used as the System Action: TSM ends.
TRACEFILE so that it is equal to or less than 255
characters in length. User Response: The administrator for this system
must update the password.
ANS1825E Unable to close trace output file
file-name. ANS1832S Unable to send generated password
using MailProg ’option’
Explanation: An error occurred during the closing of a
trace output file-name (for example, not enough disk Explanation: TSM cannot send the file containing the
space). generated password to the user ID specified in the
MailProg option.
User Response: Check the options.doc file for a
description of possible causes of the error, or see your User Response: Have your service representative
system administrator. check the error log for reasons why the file was not
sent to the user ID.

ANS1834S Unable to write to ’file-name’ for storing ANS1839E Cannot read password.
password
Explanation: An error occurred in setting up the input
Explanation: TSM cannot write to the specified file (for example, the terminal) to be read.
file-name.
User Response: Check the attributes of the terminal.
User Response: Check access permissions and disk
space. If unsuccessful, see your system administrator.
ANS1867E The server generated a CRC for verb
type CRC verb which does not match the
ANS1835E PASSWORDACCESS is GENERATE, verb received received verb.
but password needed for server
Explanation: The server calculates a CRC and notes
’server-name’. Either the password is not
the verb type. This did not match the verb received.
stored locally, or it was changed at the
server. System Action: The client indicates protocol error.
Explanation: Either the password is not stored locally, User Response: Check the trace log for additional
or it was changed at the server. information and retry the operation. If the problem
continues, see your system administrator for further
System Action: TSM prompts you for the password if
help.
TSM is running in the foreground.
User Response: If TSM was running as a background
ANS1869E The NDS object requires its parent, or
process, issue any TSM command from the foreground.
container, to be present before this
Enter the password in answer to the prompt. Then try
object can be restored. Try first restoring
your background TSM command again.
the parent of this object.
Explanation: SMS requires the parent of the object
ANS1836S MailProg file-name failed with return
(container) to be present before the child or object can
code = value.
be created.
Explanation: An error occurred with the specified
MailProg file-name.
User Response: Retry restoring, but at least one level
up. For instance, restore 'dir\.o=ibm\*' instead of
User Response: Check the return code for the 'dir\ou=gpl.o=ibm\*'.
MailProg file-name. See your system administrator if
you are unable to resolve the problem.
ANS1870E NDS transport failure FFFDFEAF has
occurred. Please contact Novell to
ANS1837S File space filespace-name is ignored. resolve it.
Processing continues.
Explanation: This error message is being returned
Explanation: The specified filespace-name in the system from the NDS call ResolveName. It indicates that the
options file is invalid. read/write partition that the object resides on has been
found but is unavailable at this time. Basically, there is
no communication between the backup server and the
operation.
server that has the read/write partition that contains
User Response: Check the file space in the system this object.
options file and use a valid file space. Retry the
System Action: Object skipped.
operation.
ANS1838E Error opening user specified options file
’filespace-name’ .
ANS1871W The server CRC version is server CRC
Explanation: The specified options file-name could not
version which does not match the client
be located or opened.
version client CRC version.
System Action: TSM attempts to open default option
Explanation: The server is using a CRC version that
file.
does not match the client.
User Response: Make sure specified option file exists
System Action: The client does no CRC checking.
and is valid.

User Response: Make sure the client and server are at
ANS1877E The name is too long for TSM to
compatible levels.
process.
Explanation: The name was being parsed. The parsing
ANS1872E Unable to connect to NetWare target
routine detected that TSM cannot process it.
service ’server-name’. Make sure the TSA
NLM is loaded on the specified System Action: TSM canceled the current operation.
machine.
User Response: See your service representative if this
Explanation: TSM interacts with the Target Service error persists.
Agent (TSA) and the connection cannot be made to the
Netware server-name.
ANS1878E An unknown error occurred while
System Action: Processing stopped. processsing system object ’sys-obj-name’:
Service ’service-name’ and its dependent
User Response: Ensure that the TSA is loaded and
services could not be stopped.
retry the TSM command.
processing a system object. The service listed in the
ANS1873E An unknown error occurred while
message and all of its dependent services could not be
processsing system object ’sys-obj-name’:
stopped. Processing cannot complete until the service is
utility function ’func-name’ failed with
stopped.
error error
processing a system object. The error information User Response: Manually stop the service and retry
captured indicates the reason for the failure. This the operation.
information can be used to diagnose the problem.
System Action: TSM ended the current operation. ANS1879E NetWare NDS error on restore
processing: **object ’nds_objectnds_object’
**TSA error ’tsa_error’, tsa_error_text
more information.
Explanation: TSM received an unexpected error from
the Novell TSA interface.
ANS1874E Login denied to NetWare Target Service
Agent ’server-name’. System Action: Object skipped.
Explanation: The connection to the Target Service User Response: Report the program error to your
Agent (TSA) requires a NetWare user name and a service representative.
password. The password you entered at the prompt
may be incorrect.
ANS1880E TSA Connect error,
System Action: Processing stopped. NWSMConnectToTargetService
’TSA_Target_Service’ password file
User Response: Retry the TSM command, supplying
’password_file’. Userid = ’NetWare_userid’
the correct LAN password.
failed with cc = TSA_ccode
ANS1875E Unable to connect to target service. Out
the Novell TSA interface while processing the userid
of memory.
and password from NWPWFILE.
Explanation: Not enough memory to connect to the
System Action: If the failure is a 'Login Denied' the
Target Service Agent (TSA).
user will be prompted for a Novell NetWare Userid
System Action: Processing stopped. and Password, and a password file will be created.
User Response: Either add memory to the server or User Response: The cc is returned from the TSA
free memory by unloading some programs, or by which belongs to Novell NetWare. If you get cc =
restarting the server. FFFDFFD7 'Login Denied', please check the following:
The user-id has been disabled.
ANS1876E Unable to connect to target service. The user-id/password is invalid or expired.
NetWare SMS return code = value. The user-id has inadequate security access.
Explanation: Unexpected return code value. The user-id has insufficent rights to files and
directorys.
The user-id specified has a login restriction based
User Response: See your service representative. on time-0f-day.

The user-id specified has a Network address remove it from the local filesystem.
restriction.
The user-id specified has a login restriction based ANS1895I Highest macro return code was return
on number of concurrent connections. code value.
NetWare is not allowing logins (DISABLE LOGIN
Explanation: This message is issued after all
was issued at the console).
commands in a client macro have completed. The
If you are unable to determine what is wrong, report return code represents the highest return code that was
the problem to your service representative. issued during processing of the macro. In order of
increasing severity, the return code meanings are:
0 - The command completed successfully
ANS1881E TSM is unable to use NWPWFILE
4 - One or more files were skipped
’password_file’ to connect TSA target
8 - One or more warning messages were issued
service ’TSA_Target_Service’, the file is
12 - One or more error messages (except for skipped
corrupted.
files) were issued
Explanation: TSM could not use the NWPWFILE to
connect to Novell TSA interface. The file was
corrupted. User Response: For return codes other than 0, the
user may wish to verify the results of the client
System Action: User will be prompted for Novell
operation(s) and take diagnostic and repair actions, as
NetWare Userid and Password, and password file will
necessary.
be created.
User Response: The file can be corrupted via another
ANS1896I ***** Restored number objects *****
application or hardware failures. If problem is
persistent contact your service representative. A copy of Explanation: Indicates the number of objects TSM has
the corrupted password file will be needed. This restored. During a restore session, the running total is
corrupted file must be preserved before you enter a periodically printed to the screen of a command line
new userid and password, because TSM will overwrite client.
the corrupted file with correct information.
System Action: Continue with restore.
ANS1882E Unable to stop service ’service-name’;
error error
ANS1897I ***** Retrieved number objects *****
Explanation: The service could not be stopped by the
program. Explanation: Indicates the number of objects TSM has
retrieved. During a retrieve session, the running total is
periodically printed to the screen of a command line
User Response: Manually stop the service and retry client.
the operation.
System Action: Continue with retrieve.
ANS1891W SUBDIR is not a valid option when
using FILELIST, SUBDIR will be
ignored. ANS1898I ***** Processed count files *****
Explanation: When Specifing FILELIST each entry is a Explanation: TSM has processed the specified number
single object and so SUBDIR will not apply. of files.
System Action: The option SUBDIR is ignored. System Action: Processing continues.
User Response: You may have either a -FILELIST or User Response: None.
SUBDIR on this command, but not both.
ANS1899I ***** Examined count files *****
ANS1892W Expire command is not allowed on the
TSM journaled filespace ’filespace’. Explanation: TSM has examined the specified number
of files.
Explanation: You cannot expire files from the server
on a TSM journaled filespace. System Action: Processing continues.
System Action: The expire command will not work on User Response: None.
this filespec
User Response: If you want to expire this filepec

the command to complete before starting the scheduled
ANS1900I Return code is return code value.
event, then consider using the PRENSCHEDULECMD
Explanation: The return code has been issued for the option, which does not require that the command
preceding client command. In order of increasing complete successfully. If a non-zero return code is
severity, the return code meanings are: normal for this command, then consider wrapping the
0 - The command completed successfully command in a script that always exits with a return
4 - One or more files were skipped code of zero.
ANS1903W The POSTCHEDULECMD command
files) were issued
failed.
The return code indicates the highest severity message
Explanation: If the command specified by the
that was issued during execution of the client
POSTSCHEDULECMD option completed with a
command. For a scheduled event, the event will be
non-zero return code, then the scheduled event is
considered successful if the return code is 0, 4, or 8.
considered to have completed successfully, but with a
The event will be considered to have failed if the return
warning-level result. Note that the result of the
code is 12.
POSTSCHEDULECMD command will not supercede a
System Action: None. higher result from the scheduled client command. For
example, if the scheduled client command completed
User Response: For return codes other than 0, the
with a return code of 12, the scheduled event will be
considered to have completed with a return code of 12,
operation and take diagnostic and repair actions, as
regardless of the outcome of the POSTSCHEDULECMD
necessary.
command.
System Action: At a minimum, the result code of the
ANS1901I Highest return code was return code
scheduled event is 8.
value.
Explanation: This message indicates the highest return
caused the command to fail. If it is not necessary for
code of all the client commands that were executed. In
the command to complete before posting the result of
order of increasing severity, the return code meanings
the scheduled event, then consider using the
are:
PRENSCHEDULECMD option. If a non-zero return
0 - The command completed successfully
code is normal for this command, then consider
4 - One or more files were skipped
wrapping the command in a script that always exits
with a return code of zero.
files) were issued
ANS1904E The archive description may not contain
any wildcard characters like ’?’ or ’*’.
User Response: For return codes other than 0, the
Explanation: Descriptions for archive files must not
contain wildcard characters.
operation(s) and take diagnostic and repair actions, as
necessary. System Action: Processing stopped.
User Response: Enter an archive description that does
ANS1902E The PRESCHEDULECMD command not contain wildcard characters.
failed. The scheduled event will not be
executed.
ANS1905E NetWare SMS error processing
Explanation: The command specified by the ’filespace-namepath-namefile-name’: error-text
PRESCHEDULECMD option must complete
successfully in order to execute the scheduled event. If
the Novell SMS interface.
the command completed with a return code of 0 (zero),
it is considered to have completed successfully. If the System Action: Object skipped.
command completed with any other return code, it is
considered to have failed. If the command failed then User Response: Report the program error to your
the scheduled event is not executed. service representative.
System Action: The client does not execute the

scheduled event, and the result code of the scheduled
event will be 12.
caused the command to fail. If it is not necessary for

ANS1906I Destination must be specified for this ANS1913E An invalid registry subkey was
operation when using FROMNODE. specified.
Explanation: The user must specify a destination with Explanation: The specified registry subkey is invalid.
a Restore/Retrieve command when using FROMNODE
processing.
operation.
User Response: Retry the Restore/Retrieve command
with a destination specified.
ANS1914E The specified subkey isn’t valid for the
specified hive.
ANS1907E An error occurred while trying to
Explanation: The specified registry subkey is invalid
perform an object merge operation on
for the specified registry hive.
the server.
Explanation: Netware: The server is unable to perform
a NetWare long name conversion. UNIX or Windows User Response: Correct the command and retry the
image backup: The open group used to group operation.
associated image components could not be closed.
System Action: TSM ended the current operation. ANS1915E Too many arguments specified for the
BACKUP REGISTRY command.
more information. Netware: It is possible that a more Explanation: Too many arguments were specified for
recent level of the server can perform the conversion. the BACKUP REGISTRY command.
ANS1908I The scheduled command completed
successfully. User Response: Correct the command and retry the
operation.
Explanation: The scheduled command completed with
return code of zero, which is interpreted as success.
ANS1916E Too many arguments specified for the
System Action: The scheduled event is successful. The RESTORE REGISTRY command.
result code for the event is 0.
Explanation: Too many arguments were specified for
User Response: None. the RESTORE REGISTRY command.
ANS1909E The scheduled command failed.
Explanation: The scheduled command completed with operation.
a non-zero return code, which is interpreted as failure.
System Action: The scheduled event is failed. The ANS1917E Too few arguments specified for the
result code for the event is 12. BACKUP REGISTRY command.
User Response: Identify and repair the problem that Explanation: Too few arguments were specified for
caused the command to fail. If a non-zero return code the BACKUP REGISTRY command.
is normal for this command, then consider wrapping
the command in a script that always exits with a return System Action: Processing stopped.
code of zero. User Response: Correct the command and retry the
operation.
ANS1912E An invalid registry hive was specified.
Explanation: The specified registry hive is invalid. ANS1918E Too few arguments specified for the
RESTORE REGISTRY command.
Explanation: Too few arguments were specified for
User Response: Correct the command and retry the the RESTORE REGISTRY command.
operation.
operation.

ANS1919E The specified eventlog is not valid. ANS1925E The specified system object type is not
valid.
Explanation: The specified eventlog is not valid.
Explanation: The specified system object type is not
valid.
operation.
operation.
BACKUP EVENTLOG command.
ANS1926E The specified system object type is only
valid on Windows NT.
the BACKUP EVENTLOG command.
Explanation: The specified system object type is only
valid on Windows NT.
operation.
operation.
RESTORE EVENTLOG command.
ANS1928E An error occurred creating the registry
staging directory.
the RESTORE EVENTLOG command.
Explanation: An error occurred creating the registry
staging directory.
operation.
operation.
ANS1922E Too few arguments specified for the
BACKUP EVENTLOG command.
ANS1929E An error saving one or more registry
keys.
the BACKUP EVENTLOG command.
Explanation: An error occurred saving one or more
registry keys.
operation.
operation.
ANS1923E Too few arguments specified for the
RESTORE EVENTLOG command.
ANS1930E An error occurred creating the eventlog
staging directory.
the RESTORE EVENTLOG command.
Explanation: An error occurred creating the eventlog
staging directory.
operation.
operation.
ANS1924E The specified system object is not valid.
Explanation: The specified system object is not valid.
ANS1931E An error saving one or more eventlogs.
User Response: Correct the command and retry the eventlogs.
operation.
operation.

ANS1932E An error replacing one or more registry ANS1938E NT Active Directory is not supported in
keys. this OS level.
Explanation: An error occurred replacing one or more Explanation: NT Active Directory is not supported in
registry keys. this OS level.
User Response: Correct the command and retry the User Response: Install Active Directory before
operation. performing backup operation.
ANS1933E Error accessing file or device ’name’. ANS1939E File Replication Service backup failed.
Explanation: An error has occurred while accessing Explanation: Tivoli Storage Manager encountered an
the file or device. error while backing up files under control of the
Windows 2000 File Replication Service
System Action: Backup set operation is not
completed. System Action: Processing stopped.
User Response: Verify that the file or device exists User Response: Examine the Windows 2000 File
and is accessible. Replication Service Event log to insure the File
Replication Service is operating properly. Restart the
service and retry the backup operation.
ANS1934E Backup set ’name’ not found.
Explanation: The backup set name was not found on
ANS1940E File Replication Service restore failed.
the server.
Explanation: Tivoli Storage Manager encountered an
System Action: The backup set operation is not
error while restoring files under control of the
processed.
User Response: Verify that the backup set name is
correct.
User Response: Examine the Windows 2000 File
Replication Service Event log to insure the File
BACKUP NTDS command.
service and retry the restore operation.
the BACKUP NTDS command.
ANS1941E System Volume backup failed.
User Response: Correct the command and retry the error while backing up files of the Windows 2000
operation. System Volume
ANS1936E Not enough arguments specified for the
BACKUP NTDS command.
Replication Service Event log to insure the system
Explanation: Not enough arguments were specified volume was successfully initialized. Restart the service
for the BACKUP NTDS command. and retry the backup operation

ANS1942E System Volume restore failed.
operation. Explanation: Tivoli Storage Manager encountered an
ANS1937E No NTDS server name specified for the
BACKUP NTDS command. System Action: Processing stopped.
Explanation: No NTDS server name was specified for User Response: Examine the Windows 2000 File
the BACKUP NTDS command. Replication Service Event log to insure the system
volume was successfully initialized. Restart the service
System Action: Processing stopped. and retry the restore operation.
User Response: Specify NTDS server name at the
command and retry the operation.

User Response: The backup copy of the named stream
ANS1943E The operation is not supported:
is damaged. The file is restored to as great an extent as
Downlevel server version.
possible, but the file should be examined to verify that
Explanation: The operation cannot be performed it is usable.
because server version is downlevel.
System Action: Processing stopped. ANS2049W Named stream of object ’object-name’
may be corrupt.
User Response: Use correct server version.
Explanation: One or more of the file’s named streams
may be corrupt.
ANS1944E Error accessing file or device.
System Action: The named stream is
Explanation: An error has occurred while accessing
restored/retrieved to as great an extent as possible.
the file or device.
User Response: The backup copy of the named stream
System Action: Backup set operation is not
may be damaged. The file is restored to as great an
completed.
extent as possible, but the file should be examined to
User Response: Verify that the file or device exists verify that it is usable.
and is accessible.
ANS2600S Browser trying to establish connection
ANS1945E The long namespace has been removed to client; received socket exception:
from the local filespace. If you wish to exception-name
proceed wth the backup/archive
Explanation: The browser received the exception
operation, rename your filespace on the
exception-name trying to connect to the TSM client
server.
machine.
Explanation: TSM has detected that the server
namespace is NTW:LONG, but the local volume does
not have long name support. If you would like to back User Response: Determine what might be causing this
up the volume using the short names, rename the kind of an exception. Validate that the LAN is up and
filespace on the server. If you would like to back up that you are trying to connect to the correct port
using long names, add the long namespace support number.
back to the volume in question.
System Action: Processing stopped. ANS2601S Browser trying to establish connection
to client; received unknown host
User Response: Add the long namespace support to
exception: exception-name
the volume or rename(remove) the corresponding
server filespace. Explanation: The browser received the exception
machine.
ANS2000I Unable to convert file names because
MEMORYEFficientbackup option is ON. System Action: The TSM operation ends.
Explanation: TSM has detected that a local name User Response: Retry the operation. If it persists,
space change has occurred on the volume that is determine what might be causing this kind of a
currently being backed up. TSM would convert the file problem. Determine if your LAN went down.
names to the new name space, but cannot because the Determine if you are trying to connect to the correct
option MEMORYEFficientbackup, is on. TSM client machine.
System Action: TSM continues to backup using the
old name space. ANS2602S Browser trying to establish connection
to client; received IO exception:
User Response: Edit the dsm.opt file, and set
exception-name
MEMORYEFficientbackup to OFF.
ANS2048E Named stream of object
machine.
’object-namepath-namefile-name’ is corrupt.
Explanation: One or more of the file’s named streams
are corrupt. User Response: Determine what might be causing this
kind of an exception. Retry the problem, and check if
System Action: The named stream is not
the LAN is down.
restored/retrieved.

ANS2603S Browser trying to establish connection ANS2608S Nothing was selected so no operation
to client; received exception: was performed.
exception-name
Explanation: No object was selected in the GUI for the
Explanation: The browser received the exception operation to be performed upon.
machine.
User Response: Make sure you select one or more
objects (volume, directory or file) in the GUI before
User Response: Determine what might be causing this clicking on the operation to be performed.
kind of an exception. Determine if the LAN may be
down, or if the TSM Client Acceptor Daemon on the
ANS2609S TCP/IP communications failure between
TSM machine is up and running.
the browser and the client machine.
Explanation: This error can occur due to any of the
ANS2604S The Web client agent was unable to
following:
authenticate with the server.
v The LAN connection to the TSM client machine went
Explanation: The TSM Web client agent was unable to down.
authenticate with the TSM server.
v You are trying to connect to the TSM client machine
System Action: The TSM operation ends. using the wrong port number.
User Response: One possible solution is to run the v The Client Acceptor Daemon on the TSM client
command line client so that the client password can be machine is not up and running and accepting
re-entered. Another approach is to check the error log connections.
on the TSM Web client agent for any relevant messages. System Action: The TSM operation ends.
User Response: Retry the operation and make sure
ANS2605S Browser could not re-establish the LAN is up. Also check that the port number is
connection to client; received protocol correct, and that the Client Acceptor Daemon is started
error. and running on the TSM client machine, and that it is
Explanation: The browser received a protocol error listening on the correct port number.
trying to re-connect to the TSM client machine.
System Action: The TSM operation ends. ANS2610S TCP/IP communications failure between
the client and the server machine.
User Response: Determine what might be causing this
kind of an error. Determine if the TSM browser and the Explanation: This error can occur if the LAN
TSM client code might be out of sync. connection between the TSM client machine and the
server machine went down.
ANS2606S An invalid password was sent to the System Action: The TSM client ends.
server. User Response: Retry the operation and make sure
Explanation: The TSM password that was sent to the the LAN is up. Make sure that both the TSM server
TSM server was invalid. and the TSM client are up and running.

ANS2611S An unknown error occurred in the
User Response: Make sure that you have the correct browser.
password. Also make sure that it is valid, for example
it is not too short. Explanation: An unknown error occurred in the
applet running in the browser.
ANS2607S Browser could not establish connection System Action: The TSM operation ends.
to client. User Response: Retry the operation. If the problem
Explanation: The TSM browser could not connect to persists, turn on tracing and see if the trace to the
the TSM client machine. browser console gives the reason for the error.

ANS2612S An unknown error occurred in the client
User Response: Determine what might be causing this Please check the TSM Error Log for any
kind of a problem. Determine if the LAN is down, or if additional information
the TSM Client Acceptor Daemon on the TSM machine
is up and running. Explanation: An unknown error occurred in the TSM
client.

ANS2618S Browser trying to retrieve resources;
User Response: Retry the operation. If the problem received resource exception:
persists, check the TSM Error Log for any additional exception-name
information.
exception-name trying to retrieve resources from the
ANS2613S A protocol error occurred in TSM client machine.
communications between the browser
and the client.
User Response: Verify that the resources are installed
Explanation: A protocol error happened between the
correctly on the TSM client machine.
applet running in the browser and the TSM client.
ANS2619S The Client Acceptor Daemon was
User Response: Retry the operation. If the problem unable to start the Remote Client Agent.
persists, turn on tracing and see if the trace to the
Explanation: The TSM Client Acceptor Daemon could
browser console gives the reason for the error.
not start the TSM Remote Client Agent.
ANS2614S A protocol error occurred in
communications between the client and User Response: Check the error log on the TSM Web
the server. client agent for any relevant messages. Then correct the
problem and retry.
Explanation: A protocol error happened between the
TSM client and the TSM server.
ANS2620W The expand entire branch operation may
take a long time, and cannot be canceled
User Response: Retry the operation. If the problem once it has started. Are you willing to
persists, check the TSM Error Log for any additional wait for the operation to complete?
information. Verify that you are running the correct
Explanation: The expand entire branch operation
applet with the appropriate level of the client.
could take a long time and cannot be canceled once it
is started.
ANS2615S The user ID entered does not match the
nodename configured on the client
intervention.
machine.
User Response: Answer 'Yes' to start the expand
Explanation: The user ID that was entered is not the
entire branch operation. If you answer 'No', the current
same as the nodename on this TSM client.
operation will be canceled.
User Response: Verify that the nodename entered is ANS2621W This function is not available on the
configured correctly on the TSM client. client platform
Explanation: The browser received a request that is
ANS2616I The machine must be rebooted for the not available on the TSM client machine. For example,
changes to take effect registry backup and restore are available only on the
Windows platform.
Explanation: The machine must be started for the
restored registry changes to take effect. System Action: The TSM operation ends.
System Action: None User Response: Request only those functions that are
valid for the platform of the TSM client machine.
User Response: Reboot the machine
ANS2622S Invalid ID or password submitted.

ANS2617S The destination directory specified is
invalid. Explanation: An invalid ID or an invalid password
was submitted.
Explanation: The user specified a destination target
directory for restore or retrieve which is invalid. System Action: The TSM operation ends.
System Action: The TSM operation ends. User Response: Verify that the ID and the password
that you entered are correct. If going to a different
User Response: Retry the operation specifying a valid server (for example by hyperlinking) then make sure
directory name.

that the different server has the same ID defined with unable to start, correct the problem, and restart the
the same password. client.
ANS2623S Web Client applet level is out of sync ANS3002I Session started for user userid
with Web Client agent. (communication-method address).
Explanation: The Web Client applet and Web Client Explanation: A session was started for the specified
agents are at incompatible levels. user.
System Action: The TSM operation ends. System Action: None.
User Response: Verify that you have the correct level User Response: None.
of the applet installed with the client, and that an
incorrect level of the applet was not placed in the
ANS3003I Session ended for user userid.
install directory.
Explanation: A session ended for the specified user.
ANS2624E This operation requires client owner System Action: None.
authority.
Explanation: Your user ID has insufficient authority to
perform this operation.
ANS3004E Session for user userid terminated -
System Action: Processing continues, but the user is invalid password entered.
not allowed to do this operation.
Explanation: A session was terminated for the
User Response: Do not perform this operation, or get specified user because an invalid password was
a higher authority level for your user ID in order to entered.
perform this operation.
System Action: The session with the specified user is
terminated.
ANS2625E Node does not support this image
operation. User Response: Re-start the remote client and enter
the correct password for the specified user.
Explanation: Node does not support or is not
configured to perform this image operation.
ANS3005I Session for user userid terminated - idle
System Action: Processing continues, but the user is for idle-minutes minutes.
not allowed to do this operation.
Explanation: A session was terminated for the
User Response: Verify whether this image related specified user because there was no activity on the
operation is supported or configured on the target session for the specified number of minutes.
platform.
System Action: The session with the specified user is
terminated.
ANS3000I communication-type communications
available on port port-number. User Response: Re-start the remote client to begin a
new session.
Explanation: The specified communications are
available on the specified port number.
ANS3006I Processing request for the TSM Web
System Action: None. Client (ip-address).
User Response: None. Explanation: A request for the Web Client is being
processed.
ANS3001E Error initializing HTTPS System Action: None.
communications - Secure HTTP not
available. User Response: None.
Explanation: An error occurred initializing HTTPS

communications. Processing will continue, but secure ANS3007I TSM client-name terminating - idle for
HTTP communications will not be available. idle-minutes minutes.
System Action: Processing continues, but secure HTTP Explanation: The specified client is terminating
communications will not be available. because it has been idle for the specified time. It will be
automatically started when it is needed.
User Response: Check the console and error logs to
determine why secure HTTP communications was System Action: The client program stops.

User Response: None. System Action: The selected operation is not
performed.
ANS3008E Too many symbolic links were detected User Response: Retry the operation after installing the
while resolving name ’file_name’ Logical Volume Snapshot Agent.
many symbolic links were found. ANS4000E 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 may mean
ANS3009E The Logical Volume Snapshot Agent that you have entered the name of a raw logical
plugin library was not found. volume. The MODE=INCREMENTAL option is not
valid for raw logical volumes.
Explanation: The selected operation cannot be
performed because the Logical Volume Snapshot Agent System Action: Processing stopped.
plugin library was not found.
User Response: Retry the operation specifying an
System Action: The selected operation is not existing domain (drive letter or file system name). If
performed. the message resulted from improper use of the
MODE=INCREMENTAL option, retry the command,
User Response: Retry the operation after correcting omitting that option.
ANS4001E Error processing ’filespace-name’: file

ANS3010E The Logical Volume Snapshot Agent space not known to server
wizard operation failed.
Explanation: The number defining the correspondence
Explanation: The Logical Volume Snapshot Agent between drive letter or file (domain name) and volume
wizard operation failed with a non-zero return code. label is not known to the server.
Check the error log for additional information.
System Action: The selected operation is not
performed. User Response: Report the program error to your
User Response: Retry the operation after correcting
ANS4002E Error processing ’filespace-name’: volume
label does not exist
ANS3011E Previous changes have not been
commited. The machine must be Explanation: The selected drive does not have a label.
rebooted before this operation can be
System Action: TSM is unable to do the requested
performed
operation without a drive or label entered.
Explanation: A previous operation required the
User Response: If the drive is a floppy drive, place a
machine to be rebooted for the changes to take effect,
disk with a volume label in it and retry the operation.
but the machine has not been rebooted. The machine
must be rebooted before this selected operation can be
volume label, and retry the operation.
performed.
System Action: The selected operation is not
ANS4003E Error processing ’filespace-name’:
performed.
duplicate volume label encountered
User Response: Reboot the machine and then retry
Explanation: The selected drive has a duplicate
the operation.
volume label. Because TSM uses the volume label to
ANS3012E The Logical Volume Snapshot Agent is back up or archive files from a drive with a duplicate
not installed. Use the Setup Wizard to volume label.
configure the Logical Volume Snapshot
System Action: TSM cannot select the drive.
Agent.
User Response: If the volume needs to be available to
Explanation: The selected operation requires the
Logical Volume Snapshot Agent, but it is not installed.
Use the Setup Wizard to install the LVSA.

ANS4004E Error processing ’filespace ANS4008E Error processing ’filespace
namepath-namefile-name’: destination file namepath-namefile-name’: file is
or directory is write locked temporarily unavailable
Explanation: The file or directory being restored or Explanation: File is temporarily unavailable.
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 User Response: Check and see if file is locked by
updated. other process. If not, retry the command.
ANS4009E Error processing ’filespace
namepath-namefile-name’: disk full
condition
or location.
retrieved because the destination disk is full.
namepath-namefile-name’: file not found System Action: Processing stopped.
Explanation: The file being processed for backup, User Response: Free up disk space, or restore or
archive or migrate no longer exists on the client. retrieve the file to another disk.
Another process deletes the file before it can be backed
up, archived or migrated by TSM.
System Action: File skipped. namepath-namefile-name’: stale NFS handle
User Response: None. Explanation: An NFS file system becomes stale.
System Action: File system skipped.
namepath-namefile-name’: directory path User Response: Check the NFS mounted filesystem.
not found
Explanation: You either have specified a directory that ANS4011E Error processing ’filespace
does not exist as shown in the message (path-name), or namepath-namefile-name’: no file handles
the directory being processed no longer exists on the available
client because another process deleted it before it could Explanation: All file handles for your system are
be backed up or archived by TSM. currently in use. No more are available.
User Response: Recheck all spelling and punctuation, User Response: Either free some file handles by
particularly the placement of directory delimiters (for ending other processes, or modify your system setup to
example, ″\″). Correct the syntax if it is incorrect, then allow for more files to be open at the same time.

ANS4007E Error processing ’filespace namepath-namefile-name’: file already
namepath-namefile-name’: access to the exists
object is denied
Explanation: Access to the specified file or directory is exists.
you do not have access permission for either the file or System Action: File is replaced or skipped depending
the directory. on client options.
System Action: Processing stopped. User Response: None.

file or directory name, correct the permissions, or ANS4013E Error processing ’filespace
specify a new location. namepath-namefile-name’: invalid file
handle
passed.

User Response: Report the problem to your system System Action: File is skipped.
administrator, and then retry the operation.
ANS4014E Error processing ’filespace system, for the file names that are handled by TSM.
error (error-code) encountered. Program
ending.
Explanation: An unknown and unexpected error-code locked by system
occurred within the client program. This is a
Explanation: File system cannot be accessed because it

namepath-namefile-name’: format unknown
namepath-namefile-name’: unexpected error
(error-code) encountered Explanation: TSM tried to restore or retrieve a file, but
it had an unknown format.
Explanation: An unexpected error occurred. This
might be a low-level system or communication error System Action: File skipped.
that TSM cannot handle or recover from.
User Response: Retry the operation. If the problem ANS4021E Error processing ’filespace
continues, determine where the problem exists. See namepath-namefile-name’: file system not
your system administrator for further help. ready
Explanation: The file system/drive was not ready for
ANS4016E Error processing ’filespace access.
namepath-namefile-name’: file is being
executed; write permission denied System Action: Processing stopped.
Explanation: The current file cannot be opened to User Response: Ensure that the drive is available to
write to because it is currently being run by another TSM, and then retry the operation.
operation.
System Action: File skipped. ANS4022E Error processing ’filespace
User Response: Stop the operation that is running the invalid
file to a different name or directory. Explanation: The drive was not available for access. A
entry.
namepath-namefile-name’: too many System Action: Processing stopped.
symbolic links were detected while User Response: Ensure that the drive is operational,
resolving name and then retry the operation. If unsuccessful, have your
Explanation: While trying to resolve the file name, too service representative check the error log.
System Action: File skipped. ANS4023E Error processing ’filespace
namepath-namefile-name’: file input/output
User Response: Ensure that you do not have a error
Explanation: An error was found while reading from
or writing to the file.
namepath-namefile-name’: file name too System Action: File skipped.
long User Response: Check your system to ensure that it is
Explanation: The file name specified is too long to be operating properly. For OS/2, run CHKDSK /F for the
handled by TSM. failing drive which can be found in dsmerror.log.

ANS4024E Error processing ’filespace ANS4026W Error processing ’filespace
namepath-namefile-name’: file write error namepath-namefile-name’: size of ’file-size’
exceeded the maximum file size limit on
your system
file.
has exceeded the maximum file size limitation on your
User Response: Check your system to ensure that it is system.
operating properly.
User Response: Restore or retrieve this file on a
system that supports the file size. See your system
administrator.
Explanation: A file being backed up/restored or
ANS4027S Error processing ’filespace
archived/retrieved exceeds system set limits for this
namepath-namefile-name’: internal program
user. Shown below are the filesize limits corresponding
message ’value’ encountered
to various platforms.
Explanation: An unexpected catastrophic program
AIX 68,589,453,312 (64GB)
failure occurred, indicated by value.
HP-UX 1,099,511,627,775 (1TB-1)
Linux 2,147,483,647 (2GB)
Mac pre-OS9 continues, see your system administrator or service
2,147,482,624 (2GB-1K) representative.
Mac OS9
18,446,744,073,709,551,616 (16EB) ANS4028E Error processing ’filespace
namepath-namefile-name’: cannot create
NetWare file/directory entry
4,294,963,200 (4GB -4KB)
Explanation: The directory path for files being
NUMA-Q DYNIX/ptx restored or retrieved cannot be created.
4.5 1,095,216,660,480 (1TB-4GB)
OS/390 4,294,967,295 (4GB)
SGI 18,446,744,073,709,551,615 (16EB-1) authorization to create the directory for file being
Solaris 2.6 or higher restored or retrieved.
1,099,511,627,775 (1TB-1)
Tru64 UNIX ANS4029E Error processing ’filespace
1,099,511,627,776 (1TB) namepath-namefile-name’: unable to build
a directory path; a file exists with the
UnixWare same name as a directory
2,147,483,647 (2GB)
Explanation: TSM tried to create a directory path, but
Windows 95 (FAT16) is unable to because a file exists that has the same
2,147,483,647 (2GB) name as a directory.
Windows 98 (FAT32) System Action: Processing stopped.
4,294,967,295 (4GB)
Windows NT/2000 (NTFS) name as the directory. Refer to the last restore/retrieve
17,592,185,978,880 (16TB-64K) operation and check all directories along the path.
User Response: Ensure that the system limits are set ANS4030E Error processing ’filespace
properly. namepath-namefile-name’: disk space limit
for this process reached
Explanation: The disk space allocated for the client
owner is full.

ANS4035W File ’filespace namepath-namefile-name’
restore or retrieve operation.
currently unavailable on server.
namepath-namefile-name’: destination
directory path length exceeds system System Action: TSM Cannot restore or retrieve the
maximum file.
Explanation: The path name specified plus the path User Response: Try to restore or retrieve after the file
name in the restored file name combine to create a was made available on the server. See your system
name whose length exceeds the system maximum. administrator.
ANS4036E An error occurred saving the registry
key.
ANS4032E Error processing ’filespace System Action: Registry backup operation terminates.
namepath-namefile-name’: file is not
compressed.
Explanation: A file that was flagged as compressed
ANS4037E File ’file-namefile-namefile-name’ changed
was not compressed, and the system failed.
during processing. File skipped.
Explanation: The specified file-name was skipped
User Response: See your system administrator to during backup, archive, or migrate because it was
report this problem. This error is a system failure. changing during the attempt to process it.
System Action: TSM skipped the file.
User Response: If you want the file backed up,
namepath-namefile-name’: file compressed
archived, or migrated, retry the operation. If it fails,
on a different client machine that has
determine why the file is being changed. For more
more memory
information on backing up, archiving, or migrating
Explanation: You are trying to restore a file that was changing files, see your system administrator.
backed up and compressed on another client
workstation that had more memory than your client
ANS4038E An error occurred processing file system
’filespace name’.
not have enough memory. Explanation: File system ’filespace name’ is corrupted
or contains one or more corrupted directories and
User Response: Obtain a machine with more memory
System Action: File system is skipped.
operating properly. For the Windows environment, run
CHKDSK utility for the failing drive. More information
about corrupted directories can be found in
error
dsmerror.log.
be a low-level system or communication error that TSM
cannot handle or recover from.
namepath-namefile-name’: file system
System Action: Processing stopped. filespace name has exceeded its space
management quota.
continues, determine where the problem exists. See Explanation: TSM detects that the file system has
your system administrator for further help. exceeded its quota. No more data can be migrated out
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. System Action: TSM cannot restore or retrieve the file.
User Response: Try to restore or retrieve after the file
ANS4041W Error processing ’filespace was made available on the server. See your system
namepath-namefile-name’: Out of free administrator.
space or inodes in file system to migrate
or recall.
ANS4991I Application Type Application Message Id
Explanation: The file system is full. No more free Application Message
space or free inodes are available to be allocated for the
Explanation: This is a message sent by the application
transaction file that is needed when a file is being
you are currently running with TSM.
migrated or recalled.
System Action: TSM logs the application message.
for this file system. User Response: Refer to the documentation for the
application that you are using.
User Response: Remove some files in the file system,
and then run reconciliation. Retry the operation.
ANS4992W Application Type Application Message Id
Application Message
ANS4042E Object name ’filespace
namepath-namefile-name’ contains one or Explanation: This is a message sent by the application
more unrecognised characters and is not you are currently running with TSM.
valid.
System Action: TSM logs the application message.
Explanation: The filename, directory name, or volume
label syntax is incorrect. User Response: Refer to the documentation for the
application that you are using.
User Response: You need to check the disk for errors. ANS4993E Application Type Application Message Id
Application Message
ANS4900W Schedule ’schedule name’ has opened a Explanation: This is a message sent by the application
new session with the server. you are currently running with TSM.
Explanation: A scheduled event ended due to a System Action: TSM logs the application message.
connection failure. The scheduled event had to be
restarted outside it's normal start-up window to User Response: Refer to the documentation for the
continue the operation. application that you are using.
System Action: Be advised that there are multiple

sessions associated with the scheduled event. ANS4994S Application Type Application Message Id
Application Message
User Response: none.
Explanation: This is a message sent by the application
you are currently running with TSM.
ANS4987E Error processing ’filespace namepath-name
file-name’: the object is in use by another System Action: TSM logs the application message.
process User Response: Refer to the documentation for the
Explanation: Access to the specified file or directory is application that you are using.
you do not have access permission for either the file or ANS4999E Unable to log message ’message number’
the directory. to server: message too long.
System Action: Processing stopped. Explanation: The message text and inserts were too
User Response: Ensure that you specified the correct large to send to the server in the available internal
file or directory name, correct the permissions, or buffer.
specify a new location. System Action: Refer to the local client error log for
more information
ANS4988W File ’filespace namepath-namefile-name’ is User Response: None.
currently unavailable on server and has
been skipped.

information (the copy group).
ANS5000W Unable to update password
System Action: TSM did not back up the file(s).
Explanation: Intended new password cannot be
registered. User Response: Change the management class that
binds the files, and retry the operation.
System Action: The server did not replace the old
password with the new password.
ANS5007W The policy set does not contain any
User Response: Update the password again. If
archive copy groups. Unable to continue
unsuccessful, see your system administrator.
with archive.
Explanation: You tried to archive the files using a
ANS5001E Open registration required. Root user
policy set that contains no archive management
must run TSM to register with server
information (the copy group).
Explanation: This client must be registered with this
System Action: TSM did not archive the files.
server.
User Response: Change the management class that
binds the files, and retry the operation.
User Response: The root user must register the client
with the server.
ANS5008W Incorrect password entered
Explanation: You entered a password that was
ANS5002E Open registration failed
incorrect.
Explanation: During the change password, update
password, or open register dialog, the open registration
without the correct password.
failed.
User Response: Reenter the password, or ask your
System Action: TSM did not register this system.
system administrator for the current password.
User Response: Reenter the password, or see your
system administrator to register this system.
ANS5009W New password entries are not the same
Explanation: During the change password, update
ANS5003S Invalid Management Class assigned to
password, or open registration dialog, the two entries
directories. Please see the error log.
for the new password were not the same.
System Action: The password was not changed on the
assigned.
server.
System Action: TSM cannot perform the requested
User Response: Backspace over both of the new
operation.
passwords and reenter them, ensuring that they match.
User Response: Retry the operation using a valid
management class. If unsuccessful, have your service
ANS5011I Backup stopped by user
representative check the error log.
Explanation: You requested to stop the backup
operation.
ANS5004S No backup copy group in the
management class used for directories. System Action: Backup stopped.
Please see the error log.
Explanation: The management class contained no
backup copy group for directories.
ANS5012E Server out of backup data storage space
System Action: TSM did not complete the backup
operation. Explanation: The server ran out of space in its backup
data storage.
check the error log. System Action: TSM cannot complete the requested
backup operation. Any files displayed on the lower half
of the backup activity panel were successfully backed
ANS5006W The policy set does not contain any up.
backup copy groups. Unable to continue
with backup. User Response: See your system administrator.
Explanation: You tried to back up the files using a

policy set that contained no backup management

User Response: Close all unneeded applications and
ANS5013E Not enough memory for backup
retry the operation. Reducing the scope of queries and
operation
the amount of data returned might also help, or see
Explanation: TSM cannot allocate memory for the your system administrator.
specified backup operation.
System Action: TSM cannot complete the requested ANS5019I Archive stopped by user
operation.
Explanation: You requested to stop the archive
User Response: Close all unneeded applications and operation.
System Action: Archive stopped.
your system administrator. User Response: Continue with normal operations.
ANS5014I Backup completed ANS5020E Server out of archive data storage space
Explanation: The backup was completed. Explanation: The server ran out of space in its archive
data storage.
System Action: TSM backed up the files.
archive operation. Any files displayed on the lower half
of the archive activity panel were successfully archived.
ANS5015I Restore stopped by user
Explanation: You requested to stop the restore
operation.
ANS5021I Archive completed
Attention: If you were restoring files with “overwrite” Explanation: An archive was completed.
option specified, the file you restored last can be
System Action: TSM archived the files.
damaged (partially overwritten).
System Action: Restore stopped.
ANS5022I Retrieve stopped by user
Explanation: You requested to stop the retrieve
ANS5016E Not enough memory for restore
operation.
operation
Explanation: TSM cannot allocate memory for the Attention: If you were retrieving files with
requested restore operation. “overwrite” option specified, the file you retrieved last
can be damaged (partially overwritten).
restore operation. System Action: Retrieve stopped.
User Response: Close all unneeded applications and User Response: Continue with normal operations.
the amount of data returned can also help, or see your
system administrator. ANS5023E Not enough memory for retrieve
operation
ANS5017I Restore completed Explanation: TSM cannot allocate memory for the
specified retrieve operation.
Explanation: A restore was completed.
System Action: TSM restored the files. retrieve operation.
User Response: Continue with normal operations. User Response: Close all unneeded applications and
ANS5018E Not enough memory for archive
your system administrator.
operation
Explanation: TSM cannot allocate memory for the
requested archive operation.
System Action: TSM cannot complete the archive
operation.

ANS5024I Retrieve completed ANS5094E Session Rejected. Sufficient server
Explanation: A retrieve was completed.
Explanation: The server does not have enough
System Action: TSM retrieved the files.
memory to allow your client to establish a connection
User Response: Continue with normal operations. with the server.
ANS5025E The nodename contains invalid
User Response: Retry later or see your system
characters.
administrator.
Explanation: The specified node name has invalid
characters.
ANS5122E The specified filespace does not exist on
System Action: TSM canceled the current operation. the server. The filespace might have
been deleted by another client or an
User Response: Retry with another node name that administrator.
has valid characters.
Explanation: The specified filespace does not exist on
the server. Your administrator might have already
ANS5026W MatchAllChar and MatchOneChar deleted the filespace or another client using your
options MUST precede Include/Exclude client's node name might have deleted it.
options
System Action: TSM ends the current operation.
Explanation: The MatchAllChar and MatchOneChar
options must precede any include-exclude options. User Response: Retry your operation. The filespace
you were working on should not exist any more. See
System Action: The TSM client ends the current your system administrator for more information.
application.
User Response: Move the MatchAllChar and ANS5123S Open registration failed because the
MarchOneChar options before any include-exclude specified node name is already defined
options. in the server.
Explanation: Open registration failed because a node
ANS5091S Unexpected Wait_For_Space from the is defined on the server with the same name.
server.
Explanation: The client received an unexpected Wait
For Space message from the server. User Response: Retry with another node name.
ANS5124S Open registration failed because there is
User Response: See your system administrator. no default domain.
Explanation: Open registration failed because a
ANS5092S Server out of data storage space. default policy domain does not exist for you to place
Explanation: The server does not have any more space your node.
available to store the object. System Action: TSM canceled the current operation.
System Action: TSM ended the current operation. User Response: See your system administrator.
User Response: Report to your system administrator
that a storage pool on the server is full. ANS5125S Open registration failed because an
invalid node name was specified.
ANS5093S SLM_LICENSE_EXCEEDED: The client Explanation: Open registration failed because the
licenses for TSM are exceeded. See your specified node name has invalid characters.
product license count for TSM User Response: Retry with another node name that
does not have any invalid characters.

ANS5126S Filespaces with duplicate names are not
supported. Please unmount the
duplicate filespace. ANS5133I Filespace ’filespace’ was deleted
Explanation: The selected filespace has a duplicate Explanation: The specified filespace was successfully
volume label. Because TSM uses the volume label to deleted.
back up or archive files from a filespace with a System Action: TSM deleted the filespace.
duplicate volume label. User Response: Continue with normal operations.
System Action: TSM cannot select the volume.
User Response: If the filespace needs to be available ANS5134E Unable to delete the filespace because
to the system, exit TSM, and assign a volume label to this node does not have permission to
the filespace. Restart TSM and retry the operation. delete archived data and/or backed up
Otherwise, unmount the duplicate filespace. data.
Explanation: You tried to delete a filespace that you
ANS5127W File excluded do not have permission to access.
Explanation: A file cannot be processed because it is System Action: TSM canceled the operation.
explicitly excluded by the include-exclude list defined User Response: Ensure that you specify the correct
in the options file. filespace, or specify a filespace you have access to.
User Response: Look in the options file for the ANS5135I Archive delete stopped by user
include-exclude list of that file. Consider changing the Explanation: You requested to stop the archive delete
options file or see your system administrator. operation.
System Action: Archive delete stopped.
ANS5128E No Backup Copy Group
Explanation: The management class for this file did
not have a backup copy group specified.
ANS5136E Not enough memory for archive delete
System Action: TSM did not back up the file. operation
User Response: See your system administrator. Explanation: TSM cannot allocate memory for the
specified archive delete operation.
ANS5129E No Archive Copy Group System Action: TSM cannot continue with the
Explanation: The management class for this file did requested archive delete operation.
not have an archive copy group specified. User Response: Close all unneeded applications and
System Action: TSM did not archive the file. retry the operation. Reducing the scope of queries and
User Response: See your system administrator. your system administrator.
ANS5130W No filespaces selected for deletion ANS5138I Archive delete completed

Explanation: You requested a deletion operation Explanation: An archive delete was completed.
without selecting a client domain.
System Action: TSM deleted the archived files.
System Action: TSM cannot perform a deletion
without a domain selected. User Response: Continue with normal operations.
User Response: Select the volumes you want to delete

and retry the operation. ANS5139E Your node does not have permission to
delete archived files.
ANS5132I Filespace deletion canceled by user Explanation: Your node is not allowed by the server
to delete archived files.
Explanation: You requested to cancel the filespace
deletion operation. System Action: TSM did not delete the archived files.
System Action: The filespace deletion operation User Response: See your system administrator.
stopped.

ANS5145W Server cannot restart the last restore ANS5151S This node currently has a pending
request. Do you want to restore without restartable restore session. The
restart? requested operation cannot complete
until this session either completes or is
Explanation: The restart restore token has expired.
canceled.
The server cannot restart the restore from where it last
ended. Explanation: This operation can not be completed
because a restartable restore session is pending. The
operation is not allowed because the restartable session
intervention.
and the current operation affect the same file space.
User Response: Retry the request without restart or
abort the request.
User Response: Issue a query restart to see the
conflict. Issue the cancel restore command to delete any
ANS5146W You cannot perform this operation while
unneeded restartable restore sessions.
accessing data for another node. Do you
wish to switch back to accessing your
own node? ANS5152S Session Rejected: The server is not
licensed for this platform type. See your
Explanation: The user cannot perform the selected
operation while accessing another users data.
requesting client type.
intervention.
User Response: Answer ″Yes″ to switch back to
accessing the server as the original node.
ANS5148W The server needs to do a one-time
conversion of your archive data before ANS5153E Session Rejected: The server does not
you can continue. This operation may allow a signon as a Unicode enabled
take a long time, and cannot be canceled client.
once it has started. Are you willing to
wait for the conversion to complete?
to the server because of a unicode enabling mismatch
Explanation: The server must do a conversion of the between server and client.
archive data before continuing. The conversion could
take a long time, and cannot be canceled once it is
started. User Response: See your system administrator
immediately.
intervention.
ANS5154I File is implicitly excluded
User Response: Answer “Yes” to start the archive data
conversion. If you answer “No”, the current operation Explanation: You tried to back up or migrate a file
will be canceled. that is implicitly excluded.
System Action: TSM will not back up or migrate an
ANS5150E An active restore for the same source implicitly excluded file.
file specification exists. Unable to
continue with this request. User Response: None.
Explanation: Currently, there is an active restore for

the same source file specification. Another restore of the ANS5155E Valid password not available. The TSM
same source file specification cannot be started. administrator for your system must run
TSM and enter the password to store it
System Action: The requested restore fails. locally.
User Response: Start another restore with a different Explanation: The file containing the stored password
source file specification. for the specified server server-name is unavailable.
User Response: The TSM administrator for your
system must set and store a new password.

ANS5157E This action requires TSM administrative ANS5169E The destination path must contain a
authority on this system. drive letter
Explanation: An activity has been attempted that must Explanation: The entered path must begin with a
be performed by the TSM administrator (for example, drive letter, colon, and root slash.
open registration, filespace delete or password update).
System Action: TSM canceled the operation. requested operation.
User Response: If the activity is required, the TSM User Response: Enter the destination path in the
administrator for this system must perform it. correct format.
ANS5158S Filespace deletion is in progress. Try ANS5173E An error occurred accessing NTFS
again later. security information.
Explanation: The filespace is in the process of being Explanation: An error occurred while attempting to
deleted. access NTFS security information.
System Action: TSM cannot complete the requested System Action: Object will not be processed.
operation.
User Response: See your system administrator or
User Response: Try the operation again later. If the bypass by using SkipNTSecurity option.
filespace was being deleted, it could take awhile for it
to complete. If the problem continues, report the
ANS5174E A required NT privilege is not held.
problem to your system administrator.
Explanation: The user account running TSM does not
possess a required NT user right/privilege for
ANS5164E Backing up/Archiving drives with
performing the current operation.
duplicate volume labels is not allowed.
System Action: Object will not be processed.
Explanation: You tried to back up or archive a drive
that has a duplicate volume label. Because TSM uses User Response: See your system administrator.
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. ANS5178E Restart of the RSM service failed.
Restart the RSM service manually.
User Response: If the volume needs to be available to from the TSM server and imported. TSM has tried to
the system, exit TSM, and assign a volume label to the restart the RSM service on the user’s behalf but has run
drive. Restart TSM and retry the operation. into a problem.
ANS5165E Drive has no volume
label.Backup/Archive not allowed. User Response: Restart the RSM service manually.
Explanation: You tried to backup or archive a drive

that has no volume label. ANS5179E Restoring a volume mount point to a
non-empty directory.
System Action: TSM rejected the selected drive.
Explanation: You are trying to restore a volume
User Response: If the drive is a floppy drive, place a mount point to a non-empty directory which is not
disk with a volume label in it and retry the operation. allowed. Volume mount point is not restored.
volume label, and retry the operation. System Action: Processing continues.
ANS5166E An error occurred saving the registry
key ANS5181E Invalid selection; A specific backup set
Explanation: The active registry key cannot be saved. must be selected.
System Action: Registry backup operation terminates. Explanation: A selection was made that might result
in multiple backup sets being restored at the same
User Response: See your system administrator. time, but restoring multiple backup sets at the same
time is not supported.
System Action: The backup set restore was not
performed.

User Response: Select a specific backup set to be
ANS5193E Certificate Services is not online.
restored.
Offline backup is not supported.
Explanation: Certificate Services is not online when
ANS5182E Multiple backup sets can not be
performing a backup operation. Offline backup is not
restored at the same time.
supported.
Explanation: Multiple backup sets were selected to be
restored, but restoring multiple backup sets at the same
time is not supported. User Response: Start Certificate Services and try the
operation again.
System Action: The backup set restore was not
performed.
ANS5194E Certificate Services is online. Online
User Response: Select a specific backup set to be
restore is not supported.
restored.
Explanation: Certificate Services is online when
performing a restore operation. Online restore is not
ANS5183W Objects of different types cannot be
supported.
restored at the same time.
Explanation: Restoring objects of different types is not
allowed. For example, restoring Backup Sets and User Response: Stop Certificate Services and try the
regular file objects at the same time is not possible. operation again.
System Action: No processing takes place.
ANS5196W Invalid key password entered.
User Response: Select objects of the same type to
perform restore operation. Explanation: The key password is invalid.
System Action: TSM allows you to try again.
ANS5188E Unable to clear SHAREAS extended
User Response: Enter the correct password.
attribute for file: ’pathname’ Return code:
’returncode’ ’strerror’ Reason code:
’reasoncode’ ANS5197E File Replication Service backup failed.
Explanation: You must be the file owner or have Explanation: Tivoli Storage Manager encountered an
superuser authority. error while backing up files under control of the
System Action: File processed without setting
attribute. System Action: Processing stopped.
User Response: The attribute must be set manually. User Response: Examine the Windows 2000 File
ANS5191E NT Active Directory is not online.
service and retry the backup operation.
Offline backup is not supported.
Explanation: NT Active Directory is not online when
ANS5198E File Replication Service restore failed.
performing a backup operation. Offline backup is not
supported. Explanation: Tivoli Storage Manager encountered an
User Response: Reboot computer and turn on Active
Directory, and try the operation again.
ANS5192E NT Active Directory is online. Online
restore is not supported.
service and retry the restore operation.
Explanation: NT Active Directory is online when
performing a restore operation. Online restore is not
supported.
changes to take effect. Would you like
System Action: Processing stopped. to reboot the machine now?
User Response: Reboot computer and enter Active Explanation: The machine must be rebooted for the
Directory repair mode, then try the operation again. changes to take effect. The user can select to have the
program reboot the machine now or can perform this

action manually at a later time.
ANS5205E An error saving one or more eventlogs
System Action: TSM None.
User Response: Select ’YES’ to reboot the machine eventlogs.
immediately.
ANS5200I ’service-name’ service needs to be
operation.
restarted.
Explanation: The service must be restarted for the
ANS5206E An error replacing one or more registry
restored changes to take effect.
keys
System Action: Changes are not effected.
Explanation: An error occurred replacing one or more
User Response: Restart the service. registry keys.
ANS5201E The specified function is not
implemented
operation.
Explanation: The specified function is not
implemented.
System Action: Processing stopped. changes to take effect
User Response: Correct the command and retry the Explanation: The machine must be started for the
operation. changes to take effect.
System Action: TSM backed up the files.
ANS5202E An error occurred creating the registry
User Response: Reboot the machine
staging directory
Explanation: An error occurred creating the registry
ANS5208E An invalid date or time was entered.
staging directory.
Explanation: An invalid date or time value was
entered. Either the syntax of the value was not correct,
User Response: Correct the command and retry the or an actual value (for example, “45” for month) was
operation. invalid.
ANS5203E An error saving one or more registry
User Response: Identify and correct the invalid date
keys
or time value. Refer to the user’s guide of the
Explanation: An error occurred saving one or more corresponding platform for the correct date syntax.
registry keys.
System Action: Processing stopped. ANS5209E System Volume backup failed.
User Response: Correct the command and retry the Explanation: Tivoli Storage Manager encountered an
operation. error while backing up files of the Windows 2000
System Volume
ANS5204E An error occurred creating the eventlog System Action: Processing stopped.
staging directory
Explanation: An error occurred creating the eventlog Replication Service Event log to insure the system
staging directory. volume was successfully initialized. Restart the service
and retry the backup operation
User Response: Correct the command and retry the ANS5210E System Volume restore failed.
operation.
error while restoring files of the Windows 2000 System
Volume

Replication Service Event log to insure the system
ANS7503W Invalid drive entry
volume was successfully initialized. Restart the service
and retry the restore operation. Explanation: An invalid entry is entered on the Drive
field.
ANS5211E The Cluster Service is offline. The System Action: TSM prompts you to enter a valid
Cluster Service must be online to drive letter.
perform a restore operation.
User Response: Enter a valid drive letter or see your
Explanation: The Cluster Service is offline. The system administrator for the correct syntax.
Cluster Service must be online to restore the cluster
database.
ANS7504W Invalid directory entry
System Action: TSM None.
Explanation: An invalid entry is entered on the
User Response: Start the Cluster Service and retry the Directory field.
operation.
System Action: TSM prompts you to enter a valid
directory.
ANS5212E An error occurred while trying to
User Response: Enter a valid directory or see your
rename file space.
system administrator for the correct syntax.
Explanation: This operation can not be completed
because the file space could not be renamed.
ANS7505W Invalid filename entry
Explanation: An invalid entry is entered on the
User Response: Contact system administrator for Filename field.
more information.
System Action: TSM prompts you to enter a valid file
name.
ANS5213W NAS objects cannot be selected with
User Response: Enter a valid file name or see your
other objects for backup.
Explanation: Backing up NAS objects with other types
of objects is not allowed.
ANS7506W Invalid label entry
Explanation: An invalid entry is entered on the Label
User Response: Select NAS objects without other field.
objects to perform backup NAS operation.
volume label.
ANS5214W NAS objects cannot be selected with
User Response: Enter a valid volume label or see your
other objects for restore.
system administrator for correct syntax.
Explanation: Restoring NAS objects with other types
of objects is not allowed.
ANS7507W Invalid node entry
Explanation: An invalid entry is entered on the Node
User Response: Select NAS objects without other Name field.
objects to perform restore NAS operation.
node name.
ANS6001S NULL character found in the name of
User Response: Enter a valid node name or see your
folder/file filename.
Explanation: A NULL character was found in the
name of a file or folder. Some products place a NULL
ANS7508W Duplicate authorization
character in a file name so that the file is sorted
alphabetically to the top of a list. TSM cannot Explanation: The authorization rule entered by the
backup/restore such files. user is already defined. Duplicate rules are not allowed.
System Action: TSM cannot complete the requested System Action: TSM allows you to enter a different
operation. rule.
User Response: Remove the NULL character by User Response: Enter an authorization rule that has
renaming the file or folder. not been defined yet or cancel defining authorization
rules.

ANS7509W Drive and/or volume label do not exist ANS7555E The destination path must contain a
drive letter
Explanation: Either the drive or the volume label or
both do not match the existing ones. Rules must be Explanation: The entered path must begin with a
defined on existing drives and volumes. drive letter, colon, and root slash.
System Action: TSM prompts you to reenter drives System Action: TSM did not continue with the
and/or volumes or cancel defining authorization rules. requested operation.
User Response: Enter an existing drive and volume to User Response: Enter the destination path in the
define the desire rule. correct format.
ANS7521E Error Loading WINSOCK.DLL - not in ANS7556E An invalid drive letter was entered
Search Path
Explanation: You entered an invalid drive letter.
Explanation: TSM cannot find the Windows Socket
System Action: TSM prompts you for the correct
support file (WINSOCK.DLL) in the current search
drive ID.
path. This message only applies when using TCP/IP
communications. User Response: Reenter the drive ID in the correct
format.
System Action: Connection to server fails.
User Response: Shut down Windows and place the
ANS7560E Drive drive-name has no volume label.
directory where this file resides in the DOS path
Backup/Archive not allowed.
statement.
Explanation: The specified drive-name selected cannot
be backed up.
ANS7524E Error Loading WINSOCK.DLL
System Action: TSM rejected the selected drive.
Explanation: Error loading the Windows socket
support file into memory. This error only applies when User Response: If the drive is a floppy drive, place a
using TCP/IP communications. disk with a volume label in it and retry the operation.
System Action: Connection to server fails.
User Response: Because this error is caused by
insufficient memory, shut down running applications
ANS7561E Drive drive-name is unavailable
and retry. If the problem persists, see your system
administrator. Explanation: In an attempt to process a file, the
specified drive-name was found unavailable.
ANS7525E Error Loading Function(s) from System Action: TSM did not process the file.
WINSOCK.DLL
User Response: Determine why the drive was not
Explanation: Error loading one or more functions available, make it ready, and retry the operation.
from the Windows socket support file.
System Action: Connection to server fails. ANS7564E Backing up/Archiving drives with
duplicate volume labels is not allowed.
User Response: Since this might possibly be caused
by insufficient memory, shut down running Explanation: You tried to back up or archive a drive
applications and retry. If the problem persists, see your that has a duplicate volume label. Because TSM uses
system administrator. 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.
ANS7551E The source path cannot contain a drive
letter System Action: TSM cannot select the drive.
Explanation: The entered path cannot contain a drive User Response: If the volume needs to be available to
letter. the system, exit TSM, and assign a volume label to the
User Response: Enter the source path in the correct
format.

ANS7641E Registry Backup failed ANS7731E Event Log Restore failed
Explanation: TSM An error occurred while backing up Explanation: An error occurred while restoring the
the registry. event logs from the server.
System Action: Registry backup function fails. System Action: Event Log restore function fails.
User Response: See you system administrator. User Response: See your system administrator.
ANS7642E An Error occurred creating the registry ANS7732E An Error occurred creating the event log
directory structure directory structure
Explanation: An error occurred while creating the Explanation: An error occurred while creating the
directory structure to save/replace registry key. directory structure to save the event logs.
System Action: Registry function fails. System Action: Event Log function fails.
User Response: See you system administrator. User Response: See your system administrator.
ANS7643E An error occurred saving the registry ANS8000I Server command: ’command’
key
Explanation: The specified command is being sent to
Explanation: The active registry key cannot be saved. the server. This message is displayed when the
command is generated from a macro or when the client
System Action: Registry backup operation terminates.
is running in batch mode.
System Action: The command is sent to the server for
processing.
ANS7650E An error occurred replacing the registry
key
Explanation: The backed up registry key(s) were
ANS8001I Return code return code value.
restored from the server but cannot be made active into
the registry. Explanation: The error code shown has been returned
from the preceding server command. This message is
System Action: Current Registry key remains active.
preceded by a server message explaining the reason for
User Response: See your system administrator. the error code.
ANS7660E Registry activation failed
registry key from the server.
ANS8002I Highest return code was return code
System Action: Registry restore function fails. value.
User Response: See your system administrator. Explanation: At exit from the client, the highest return
code encountered during the session is displayed.
ANS7701E Create directory failed System Action: This value is used as the program exit
code.
Explanation: The specified new directory cannot be
created. User Response: None.
System Action: Specify another directory name.
ANS8003I Process number process ID started.
Explanation: As a result of the preceding server
command, the process whose ID is shown starts to
ANS7730E Event Log Backup failed execute the command. The process can be monitored
Explanation: An error occurred while backing up the using the QUERY PROCESS command.
event logs. System Action: None.
System Action: Event log backup function fails. User Response: None.

correct it. If the problem persists, contact your service
ANS8008W Redirection inside macro whose output
representative.
is redirected is ignored.
Explanation: An output redirection symbol has been
ANS8016E Command line parameter parameter
encountered inside a macro. However, the output of the
number: ’parameter’ is too long.
macro itself (or a higher level macro) is already being
redirected. Explanation: The specified command line parameter
exceeds the maximum length for a command line
System Action: The redirection request is ignored.
parameter.
System Action: The administrative client session is
ended.
ANS8009E Exiting due to command or option
User Response: Reissue the command with a shorter
errors.
parameter.
Explanation: Because of errors in command line or
option file parameters displayed earlier, the
ANS8017E Command line parameter parameter
administrative client session is ending.
number: ’parameter’ is not valid.
System Action: The client exits.
Explanation: The command line parameter shown is
User Response: Fix the option file parameter in error not a valid administrative client parameter.
and restart the client, or restart the client with proper
command line parameters.
ended.
User Response: Reissue the command with valid
ANS8012E Option processing storage exhausted.
parameters.
Explanation: During processing of the client options
file, the client runs out of memory.
ANS8018E Administrative command not valid in
System Action: The client session is ended. Console mode.
User Response: Make more memory available and Explanation: The Console Mode option has been
restart the administrative client. specified but the client encounters what appears to be a
server command on the command line.
ANS8014E Insufficient information to connect to System Action: The administrative client session is
host. ended.
Explanation: The client options file or command line, User Response: Reissue the command with no server
or both, do not contain enough communications command.
information to successfully connect to the server
system. For example, with TCP/IP both the TCPPort
ANS8019E Id and password must be supplied in
number and TCPServer address are required to make a
Batch mode.
connection.
Explanation: A server command has been encountered
on the command line, but no administrator ID or
ended.
password, or both, are specified.
User Response: Determine what information is
needed to establish a connection for your
ended.
communications method and then specify all that
information in your client options file or on the User Response: Reissue the command and include the
administrative client command line. -ID and -PASSWORD parameters on the command line.
ANS8015E File ’file spec’, error code error code from ANS8020E Unable to open file ’file spec’ for output.
options processing.
Explanation: The file name specified in the -OUTFILE
Explanation: An unknown error code is returned from option cannot be opened.
the routine that processes the client options file.
System Action: The -OUTFILE parameter is ignored.
ended. User Response: Allow processing to continue or exit
the session and correct the file name.
User Response: Attempt to determine the error and

ANS8021E Exiting Batch mode session due to ANS8026E Input line longer than maximum of max
output file error. length characters. Use continuation.
Explanation: The file specified in the -OUTFILE Explanation: An input command line is longer than
parameter cannot be opened for a session running in the maximum input line length allowed.
Batch mode.
System Action: The input command is ignored.
User Response: Reissue the command with several
ended.
lines using continuation characters.
output file name or make space available for the output
ANS8027E Unterminated comment in command.
file.
Explanation: An input command contains an opening
comment mark but no closing comment mark.
ANS8022E Output will be written only to stdout.
Explanation: The file specified in the -OUTFILE
parameter cannot be opened, so output is written only User Response: Reissue the command with matching
to the standard output stream. comment marks.
System Action: Output that would have been written
to the output file is written to the standard output ANS8028E Command longer than maximum of max
stream. length characters.
User Response: Allow processing to continue or exit Explanation: An input command longer than the
the session and correct the file name. maximum command length allowed has been entered.
ANS8023E Unable to establish session with server.
User Response: Reissue the command with fewer
Explanation: The administrative client cannot start a characters. This could mean replacing series of
session with the requested server. This message is repeating blanks with a single blank.
preceded by another message that explains the reason
for the error.
ANS8029E Macro processing terminated.
ended. Explanation: An error occurs during processing of a
macro because the -ITEMCOMMIT option is not
User Response: Attempt to correct the error. If the specified on the command line. Processing of this
problem persists, contact your service representative. macro and any higher level macro is terminated.
System Action: All current macro processing ends.
ANS8024E End of macro after continued command
line. User Response: Specify the -ITEMCOMMIT option on
the command line to ensure that the server commits
Explanation: A macro containing a continuation line each command in the macro individually.
has been executed, but no more lines are found in the
macro file.
ANS8030E Substituted command longer than
System Action: The continued command is ignored, maximum of max length characters.
and an error return code is set for the macro.
Explanation: After variable substitution, an input
User Response: Correct the macro in error. command is longer than the maximum command
length allowed.
ANS8025E I/O Error reading command input. System Action: The input command is ignored.
Explanation: The client is unable to read an input User Response: Reissue the command with fewer
command from the terminal. characters. This may require replacing a series of
repeating blanks with a single blank.
ended.
ANS8031E Missing name of macro to execute.
User Response: Correct the problem on the terminal
and retry the administrative session. Explanation: A macro command is encountered that
does not contain a macro name.

User Response: Reissue the macro command with a
ANS8038E Unable to open file ’file spec’ for
macro file name.
redirection.
Explanation: A command has been entered that
ANS8032E Could not allocate storage to process
specifies an output redirection file, but the file cannot
macro ’file spec’.
be opened.
Explanation: The client cannot allocate enough
System Action: The command is ignored and an error
memory to process the macro shown.
is returned.
System Action: The macro is ignored and an error is
returned.
output file name or make space available for the output
User Response: Make more memory available to the file.
client and retry the macro command.
ANS8041E The server connection has been lost and
ANS8034E Your administrator ID is not recognized cannot be re-established.
by this server.
Explanation: During an administrative session, the
Explanation: The administrator ID entered is not client discovers that the connection with the server has
known to the requested server. been severed; an attempt to reestablish the connection
fails.
System Action: The administrative session terminates.
User Response: Ensure that you are using a registered
administrative ID for the server to which you are User Response: Determine the cause of the failure;
connecting. then try to restart the session at a later time. If the
ANS8035E Interrupted by user.

ANS8045E Communications error.
Explanation: During an administrative session, a
keyboard interrupt or break sequence is entered. Explanation: An unexpected communications error
occurs during an administrative session.
System Action: The administrative session is
terminated. System Action: The client session is ended.
User Response: Restart the administrative client User Response: Verify that communications are active
session. between the client and server machines. Server outages,
processor outages, and communication controller
ANS8036E Administrative command not valid in
Mount mode.
ANS8046E System failure.
Explanation: The Mount Mode option has been
specified but the client encounters what appears to be a Explanation: The client connection with the server has
server command on the command line. terminated due to a system error.
System Action: The administrative client session is System Action: The client session is ended.
ended.
User Response: Reissue the command with no server
command.
ANS8047E Buffer overflow.
Explanation: A communications buffer overflow
ANS8037E Missing name for redirection file.
occurs.
Explanation: A command is entered that contains an
output redirection symbol but no output file name.
System Action: The command is ignored and an error
is returned.
User Response: Reissue the command with an output
ANS8049E Connection timed out.
file name.
Explanation: The connection to the server cannot be
established.

User Response: Check for a networking problem. If
the problem persists, contact your service
allow a signon as a Unicode enabled
representative.
administrative client
Explanation: The administrative client is unable to
ANS8052E Unable to decrypt file ’filespace
establish a connection to the server because of a
namepath-namefile-name’ ....Please try to
unicode enabling mismatch between server and client.
restore this file individually
Explanation: File could not be decrypted and restored.
User Response: Register a new administrator from a
System Action: File is not restored.
different administrative client or the server console, and
User Response: Restore the file separately. signon with the new administrator ID.
ANS8053E Network cannot be accessed. ANS8064E Communication timeout. Reissue the

command.
Explanation: An error occurs accessing the network.
Explanation: The connection to the server is ended
System Action: The client session is ended. because of a communication timeout from the server.
User Response: Retry the administrative session. If the System Action: The server does not process the
problem persists, contact your service representative. command.
User Response: Reissue the command. If necessary,
ANS8054E No memory available to service request. increase the values of IDLETIMEOUT and
Explanation: Sufficient server memory is not available. COMMTIMEOUT options in the server options file.

ANS8494E Error during buffer operation (file
User Response: Retry the administrative session. If the name:line number) error code: error code
Explanation: Error occurs when doing the following
operations: 1. Creating input buffer. 2. Retrieving data
ANS8055E No server resources available. from buffer. 3. Retrieving the pointer to field data. 4.
Explanation: Sufficient server resources are not Clearing input buffer. 5. Deleting input buffer.
available. System Action: The administrative client session ends.
System Action: The client session is ended. User Response: Contact your service representative.
User Response: Retry the administrative session. If the
problem persists, contact your service representative. ANS8495E Error while writing data (file name:line
number) error Code: error code
ANS8056E Your administrator ID is locked. Explanation: An error occurs while writing data to the
Explanation: The administrative ID entered has been session.
locked by a system administrator and cannot be used. System Action: The administrative client session ends.
System Action: The client session is ended. User Response: Contact your service representative.
User Response: Contact your system administrator to
unlock your ID. ANS8496E Error during session operation (file
name:line number) error code: error code
ANS8057E The requested language files are not Explanation: An error occurs during one of the
available. following operations: 1. Retrieving session description.
Explanation: The NLS repository for the language 2. Initializing session description. 3. Initializing window
specified is not available. description. 4. Creating the session. 5. Writing title to
the display. 6. Writing prompt to the display.
System Action: The administrative client session ends.
User Response: Use a different language or obtain a
copy of the NLS repository for the language desired. User Response: Contact your service representative.

v Restart the TSM Administrator’s graphical user
ANS8500I User action cannot be completed due to
interface.
the following error:
v If this problem persists, save the dsmerror.log file
Explanation: An error has occurred while processing residing in the directory specified by the
your requested action, user action. The message environment variable DSMG_LOG or in the current
displaying with this message identifies the error. directory if DSMG_LOG is not specified, and contact
System Action: The system does not process your your service representative for assistance.
requested action.
User Response: See Explanation for the message ANS8504E A message related to this window or
displaying with ANS8000I. your requested action cannot be
displayed due to an internal error in
this graphical user interface. Refresh
ANS8501E Internal error in this graphical user this window or request the action again.
interface. Try one of the following in
the order listed: 1) close this window Explanation: An internal processing error has
and reopen it 2) close this object and occurred in the TSM Administrator’s graphical user
reopen it 3) shut down this graphical interface while attempting to display an informational,
user interface and restart it 4) save warning, or error message related to the current
dsmerror.log residing in the directory window or your requested action.
specified by DSMG_LOG and contact System Action: The system may or may not process
your service representative for your requested action.
assistance.|Graphical User Interface -
Internal error User Response: View the Activity Log window in the
Server object to find out if your requested action has
Explanation: An internal processing error has completed. If it has completed successfully, refresh the
occurred in the TSM Administrator’s graphical user current window to show its results. If it has not
interface while processing your requested action. completed successfully, make your request again.
Message ANS8000I, which displays with this message,
identifies your requested action.
ANS8516E The values entered for the New
System Action: The system does not process your Password and Reenter New Password
requested action. fields do not match. Type the same
User Response: value into both fields.
v Close the window in which your failed request was Explanation: You have entered different values into
made and reopen it. the New Password and Reenter New Password fields.
v If this problem persists, close all windows associated System Action: The system does not process your
with the object toward which your failed request was requested action.
directed and reopen them.
User Response: Enter the same value into the New
v If this problem persists, shut down the TSM
Password and Reenter New Password fields.
Administrator’s graphical user interface and restart
it.
v If this problem persists, save the dsmerror.log file ANS8566E You have not entered or selected a value
residing in the directory specified by the for this required field. Enter or select a
environment variable DSMG_LOG or in the current value for this field.
directory if DSMG_LOG is not specified, and contact Explanation: You have not entered or selected a value
your service representative for assistance. for a required field.
System Action: The system does not process your
ANS8502S Due to this error, processing cannot requested action.
continue. This graphical user interface
will shut down. User Response: Enter or select a valid value for this
required field.
Explanation: A severe error has occurred. The
message displaying with this message identifies the
actual error. ANS9003E program-name: file system for path-name is
not in the dsmmigfstab file.
System Action: The TSM Administrator’s graphical
user interface closes. Explanation: TSM cannot find the file system in the
dsmmigfstab file.
User Response:
operation.

User Response: Ensure that the file system is both
ANS9018W program-name: option option value value
valid and local, and that it is an FSM file system.
invalid, range min-value to max-value.
Explanation: An invalid value has been entered. Value
ANS9004E program-name: cannot update file-system
should be in the range specified by the message.
because it is not an FSM file system.
System Action: TSM uses defaults instead of the value
Explanation: The program cannot find the file system
specified by the user.
in the dsmmigfstab file. The update failed.
User Response: Correct the invalid input value.
operation.
ANS9019W program-name: unable to parse option
User Response: The file system cannot be updated
value ’argument’
because it is not an FSM file system. You must first add
space management to the file system before you can Explanation: Input is incorrect or is not in correct
update space management settings for the file system. format.
System Action: TSM continues.
ANS9012E error-program: Command must be run by
User Response: Retry operation with correct usage
root user.
syntax.
Explanation: TSM requires that a root user perform
this operation.
ANS9021E error-program Unknown recall daemon
System Action: TSM terminates the operation. (pid process-ID) terminated abnormally,
status: status.
User Response: Change to root user, and then retry
the operation. Explanation: A recall daemon is terminated
abnormally.
ANS9016E Cannot get space management migration System Action: TSM terminates the operation.
status for path.
User Response: Retry operation. If problem persists,
Explanation: An error occurred while trying to get the contact your service representative.
space management migration status. Either the
permissions for the status file are not set correctly, or
ANS9022E error-program Recall daemon (pid
the status file is damaged.
process-ID) terminated abnormally,
System Action: TSM terminates the operation. status: status.
User Response: The root user should check the Explanation: A recall daemon is terminated
permissions of the status file, or contact the service abnormally.
representative.
System Action: TSM terminates the operation.
User Response: Retry operation. If problem persists,
ANS9017W error-program: Minimum number of
recall daemons min-dsmrecalld cannot be
greater than maximum number of recall
daemons max-dsmrecalld; defaulting to ANS9023I error-program: Subsidiary recall daemon
minimum min-dsmrecalld and maximum process exiting.
max-dsmrecalld.
Explanation: The process is interrupted and exiting.
Explanation: A minimum number of recall daemons The user has terminated the process.
has been entered that is greater than the maximum
number of recall daemons. System Action: TSM detected an interrupt. The recall
daemon is terminated and exiting.
System Action: TSM uses defaults instead of the
values specified in the client system options file User Response: None.
(dsm.sys).
User Response: Correct the MINRECALLDAEMONS ANS9024E Starting with this release all candidate
and MAXRECALLDAEMONS options in the client processing is done internally by the
system options file and retry the operation. TSM monitor daemon. Thus -c is no
longer a valid option for dsmreconcile.
Explanation: The command line options -c and
-Candidates are no longer valid for dsmreconcile as all

candidates processing is now performed by
ANS9032W File file-name is not in an FSM file
dsmmonitord.
system.
System Action: TSM detected an invalid option.
Explanation: TSM detects that the file is not in an
dsmreconcile is exiting.
FSM file system, and therefore, it cannot perform the
User Response: Don’t use options -c and -Candidates operation requested.
with dsmreconcile anymore.
System Action: TSM does not set the file attributes.
User Response: Add space management to the file
ANS9025W program-name: cannot truncate inode
system, migrate the file, and then retry the operation.
inode-number on file system
(file-system-ID, file-system-ID): error.
ANS9036W program-name: migrated file(s) are
Explanation: TSM cannot truncate the file to its correct
missing on server for number stub file(s).
stub file size. The file remains one full block in size.
Look in ’file-spec’ for file names.
Explanation: TSM cannot find the migrated file(s) on
User Response: Retry the operation. If error persists, the server.
reboot the system. If error still persists, contact your
User Response: Look in the path mentioned in the
message for the file name. Also ensure that you are
ANS9028E program-name: cannot determine the file
working with the correct server for this file.
system name for fsid (file-system-ID,
file-system-ID).
ANS9054E error-program: cannot set specified
Explanation: TSM is unable to determine the name of
execution mode: error.
the file system with the specified file-system-id.
Explanation: TSM cannot set the execution mode
System Action: TSM is unable to recall the requested
successfully.
file.
User Response: Determine if the file system which
operation.
contains the file has an entry in
/etc/adsm/SpaceMan/config/dsmmigfstab. Typically User Response: Retry the operation. If the problem
this problem should not occur unless the dsmmigfstab persists, contact your service representative.
file was manually updated after the file system was
mounted, and the entry was either removed or
ANS9057W error-program: cannot get space
commented out. Once the entry is added back to
information for file-system: error.
dsmmigfstab, try the file recall again.
Explanation: TSM cannot get the space information
for the file system.
ANS9030W Cannot set conflicting attributes to file
file-name. System Action: TSM continues.
Explanation: TSM cannot set the file attributes User Response: Verify that space management has
because the requested attributes are in conflict with one been added to the file system.
another.
System Action: TSM does not set the file attributes. ANS9058E error-program: cannot close file-spec: error.
User Response: Retry this operation with attributes Explanation: TSM cannot close the file.
that do not conflict with each other.
System Action: TSM terminates the current operation.
ANS9031W File file-name is not a migrated file. User Response: Retry the operation. If problem
persists, contact your system administrator.
Explanation: TSM can only set file attributes to a
migrated file. This file has not been migrated.
ANS9059E error-program: process cannot detach to
System Action: TSM does not set the file attributes. become a daemon.
User Response: Migrate this file, and then retry the Explanation: TSM process cannot detach itself to
operation. become a daemon.
System Action: TSM cannot start the daemon as
requested. TSM stops.

User Response: Retry the operation.
ANS9069I program-name: all file systems are
reactivated to previous states.
ANS9060W error-program: cannot get and increase
Explanation: TSM has reactivated all file systems
limit of open files.
managed by HSM to their previous states before the
Explanation: TSM either cannot get the limit of the global deactivation.
number of open files, or cannot increase the limit of the
number of open files.
User Response: Continue with normal operation.
System Action: TSM cannot increase the number of
open files, and was not able to complete the operation.
ANS9070I program-name: space management is now
User Response: Free some file space by ending some
deactivated for all FSM file systems.
processes or removing some files, and retry the
operation. Explanation: TSM has deactivated space management
for all file systems listed in the dsmmigfstab file.
ANS9063E error-program: file system file-system is out System Action: TSM continues.
of inodes.
Explanation: TSM cannot get space for the file system
because the file system is out of inodes.
ANS9071W program-name: error reactivating space
System Action: TSM cannot get space via migration. management for all FSM file systems.
User Response: Remove some files to make more Explanation: TSM found an error in trying to
inodes available and retry. reactivate space management.
System Action: TSM does not reactivate space
ANS9064E error-program: Cannot fork a new management for FSM file systems.
process: error.
User Response: Make sure space management is
Explanation: TSM cannot fork a new process that is installed correctly and retry the operation.
needed.
System Action: TSM cannot complete the requested ANS9072W error-program: error deactivating space
operation. management for all FSM file systems.
User Response: Free some file space by ending some Explanation: TSM found an error in trying to
processes or removing some files, and retry the deactivate space management.
operation.
System Action: TSM does not deactivate space
management for FSM file systems.
ANS9067W error-program: error updating
dsmmigfstab file for file-system.
installed correctly and retry the operation.
Explanation: TSM found an error in updating the
dsmmigfstab file for this file system.
ANS9073W program-name: error deactivating space
System Action: TSM does not update the management for file system file-system.
dsmmigfstab file.
Explanation: TSM found an error in trying to
User Response: See the preceding error message and deactivate the file system.
correct the error if possible. Then, retry the operation. If
System Action: TSM does not deactivate space
problem persists, contact your system administrator.
management for the file system.
ANS9068I program-name: dsmmigfstab file updated
installed correctly and retry the operation.
for file system file-system.
Explanation: TSM successfully updated the
ANS9074I program-name: FSM file system file-system
dsmmigfstab file for the file system.
is now deactivated.
Explanation: TSM has deactivated space management
User Response: Continue with normal operation. for the file system.

ANS9075W program-name: error reactivating space ANS9080E program-name: not enough space to recall
management for file system file-system. all migrated files.
Explanation: TSM found an error in trying to Explanation: TSM detects there is not enough space in
reactivate space management for the file system. the file system to hold all the migrated files if all are
recalled.
System Action: TSM does not reactivate space
management for the file system. System Action: TSM does not attempt to recall all the
migrated files.
User Response: Correct the error if possible and retry
the operation. If the problem persists, contact your User Response: Make room in the file system by
service representative. increasing the file system size or removing some files.
Retry the operation.
ANS9076I program-name: space management is now
active for file system file-system. ANS9081W program-name: orphaned stub file(s)
detected in file system file-system.
Explanation: TSM has reactivated space management
for the file system. Explanation: TSM detected one or more orphaned
stub files. Either the migration server was changed in
the client system options file after the file was
User Response: Continue with normal operation. migrated, or the migration server database is damaged.
System Action: TSM does not attempt to remove
ANS9077I program-name: removed space space management from the file system.
management from file system file-system.
User Response: Determine the cause of orphaned stub
Explanation: TSM removed space management. The files. Switch to the correct migration server and recall
file system is now a native file system. the migrated files. Retry the operation.

ANS9082W program-name: error encountered while
User Response: Continue with normal operation. reconciling file system file-system.
Explanation: TSM encountered an error performing
ANS9078W Space management is not removed from reconciliation on the file system.
file system file-system.
Explanation: TSM was not able to remove space
management from this file system. Possible causes: User Response: Refer to other messages displayed or
Kernel extension is downlevel. messages in the log to correct the problem. Then retry
Program is downlevel. the operation.
Insufficient disk space.
System Action: TSM is unable to complete the ANS9083W program-name: cannot deactivate space
requested operation. management on file system file-system.
User Response: Refer to the immediately preceding Explanation: TSM cannot deactivate space
error message and retry the operation. management on the file system.
ANS9079W program-name: no migrated files
User Response: Correct the error if possible and retry
matching search criteria found.
the operation.
Explanation: TSM did not find any migrated files
matching the search criteria.
ANS9085E program-name: space management has not
System Action: TSM cannot complete the requested been added to file system file-system.
operation.
Explanation: There is no entry for the file system in
User Response: Retry the operation with a different the dsmmigfstab file.
search criteria.
System Action: TSM will not perform space
management functions on this file system.
User Response: Add space management to the file
system, if appropriate, and then retry the operation.

ANS9086E program-name: error adding FSM to file
system file-system.
ANS9096E User is not the owner of file
Explanation: TSM encountered an error and cannot
filesystem-namedirectory-namefile-name so
add FSM to the file system.
file is skipped.
Explanation: The user does not own this file and
User Response: Refer to the preceding error message cannot perform this operation.
System Action: TSM skips the file.
User Response: None, or if you have root-user
ANS9087I Space management is successfully
authority, switch to root user and retry the operation.
added to file system file-system.
Explanation: TSM has added space management to
ANS9098E program-name: space management does
the file system, and will now monitor its space usage.
not support file system file-system.
You can also perform other space management
operations on this file system. Explanation: TSM space management does not
support this type of file system. Space management
supports only true local file systems (e.g. JFS on AIX).
User Response: Continue with normal operation. Space management does not support other types of file
systems (AFS, NFS, etc).
ANS9088W program-name: an entry for file system System Action: Processing of the file system stopped.
file-system is already in the dsmmigfstab
file.
Explanation: TSM found that the file system is already
ANS9099E program-name: space management is not
listed in the dsmmigfstab file.
active for file system file-system.
Explanation: TSM found the file system did not have
User Response: None. space management activated.
System Action: Processing of that file system stopped.
ANS9090E program-name: file-system is not a valid
User Response: Reactivate space management for the
file system name.
file system.
Explanation: TSM received an invalid file system
name. The file system is not mounted, or is not
ANS9100E Space management has not been added
mounted correctly.
to file system file-system, or FSM is not
System Action: TSM continues. mounted.
User Response: Correct the file system name, and Explanation: TSM found the file system was not in a
retry the operation. migratable state. Either space management was not
added to the file system, or the FSM is not mounted.
ANS9093W program-name: cannot update migration System Action: Processing of the file system stopped.
candidates list file-name.
User Response: Either add space management to the
Explanation: TSM cannot update the migration file system, or mount the FSM if it is not mounted.
candidates list because not enough memory is available Refer to the User’s Guide for the correct syntax for
to create a temporary file. mounting the FSM.
ANS9101I No migrated files matching ’file-name’
User Response: Make some memory available by
were found.
ending some processes, and then retry the operation.
Explanation: You entered a search pattern or file name
that cannot be found in the server database as a
ANS9094W program-name: no candidates found in
migrated file.
Explanation: TSM found no files eligible for migration
in the file system after running dsmreconcile. User Response: Ensure that your search pattern is
correct, or specify a new search string.

ANS9126E program-name: cannot get the state of ANS9134W program-name: invalid age factor (value).
space management for file-system: error.
Explanation: An invalid value has been entered for
Explanation: TSM cannot determine whether space the age factor setting.
management is activated, deactivated, or globally
System Action: TSM logs the condition and continues.
deactivated on the file system.
System Action: TSM stops the operation.
User Response: Retry the operation.
ANS9135W program-name: invalid premigration
percentage (value).
ANS9128I program-name: exported space
management file system file-system.
premigration percentage.
Explanation: TSM has exported the indicated space
managed file system. You must import this file system
to gain access to the migrated files. User Response: Correct the invalid input value.
ANS9136W program-name: invalid high threshold
(value).
ANS9130W program-name: High threshold (value) less
high threshold.
than low threshold (value).
Explanation: TSM detects that the high threshold is
lower than the low threshold. The high threshold must User Response: Correct the invalid input value.
be higher than or equal to the low threshold.
System Action: TSM logs the condition and continues ANS9137W program-name: invalid low threshold
processing other parameters. (value).
User Response: Correct the invalid input value. Explanation: An invalid value has been entered for
low threshold.
ANS9131W program-name: invalid size factor (value). System Action: TSM logs the condition and continues.
Explanation: An invalid value has been entered for User Response: Correct the invalid input value.
the size factor.
System Action: TSM logs the condition and continues ANS9140W program-name: invalid size factor (value)
processing other parameters. for file-system, range value..value.
the size factor setting. Value should be in the range
specified by the message.
ANS9132W program-name: invalid stub file size
(value). System Action: TSM does not change value.
the stub file size setting.
System Action: TSM logs the condition and continues ANS9141W program-name: invalid age factor (value)
processing other parameters. for file-system, range value..value.
the age factor setting. Value should be in the range
specified by the message.
ANS9133W program-name: invalid quota factor
(value). System Action: TSM does not change the value.
the quota setting for the file system.

ANS9142W program-name: file-spec: high threshold ANS9148E program-name: cannot find mount point
(value) less than low threshold (value) for for file system file-system.
file-system.
Explanation: TSM cannot find file system mount
Explanation: TSM detects that high and low point.
thresholds specified for the file system are invalid
values. The high threshold must be greater than or
operation.
equal to the low threshold.
System Action: TSM logs the condition and stops.
continues, check with your system administrator.
User Response: Enter valid values for the high and
low thresholds.
ANS9149E program-name: cannot create transition
stub file: error.
ANS9144W program-name: file-spec: invalid high
Explanation: TSM cannot create transition stub file.
threshold (value) for file-system, range
0..100. System Action: TSM cannot complete the requested
operation. Processing continues.
Explanation: TSM detects an invalid high threshold
value for the file system. User Response: Retry the operation. If the problem
User Response: Enter a valid value for the high
ANS9150W Space management is not exported from
threshold.
Explanation: TSM was not able to export the space
ANS9145W program-name: file-spec: invalid low
managed file system. Possible causes:
threshold (value) for file-system, range
Kernel extension is downlevel.
0..100.
Program is downlevel.
Explanation: TSM detects an invalid low threshold
System Action: TSM is unable to complete the
value for the file system.
User Response: Refer to the immediately preceding
User Response: Enter a valid value for the low error message and retry the operation.
threshold.
ANS9152E program-name: cannot deactivate space
ANS9146E program-name: file-spec: expecting value management for whole system: error.
field(s) in line line-number, found value
Explanation: Cannot deactivate space management for
field(s).
this whole system (whole machine).
Explanation: TSM detects too many or too few fields
System Action: TSM cannot deactivate space
in an entry in the dsmmigfstab file.
management support.
operation.
User Response: Edit the dsmmigfstab file manually,
and then retry the operation. Note:Do not manually
ANS9153E program-name: cannot reactivate space
edit the dsmmigfstab file unless specifically instructed
management for whole system: error.
by a message.
Explanation: Cannot reactivate space management for
this whole system (whole machine).
ANS9147E program-name: cannot read file-spec: error.
System Action: TSM cannot reactivate space
Explanation: TSM cannot read this file.
management support.
System Action: TSM cannot fully complete the
User Response: Retry the operation. Try to determine
why the read failed. If the problem continues, check
with your system administrator.

User Response: Retry the operation. Determine why
ANS9154E program-name: cannot deactivate space
the write failed. If the problem continues, check with
management for file system file-system:
your system administrator.
error.
Explanation: Cannot deactivate space management for
ANS9162E program-name: file-spec invalid: not found
this file system.
in path/path.
System Action: TSM unable to deactivate space
Explanation: TSM cannot find an entry for the file
management support for the file system.
system in the dsmmigfstab file.
operation.
ANS9155E program-name: cannot reactivate space
management for file system file-system:
error.
ANS9165E program-name: cannot open directory
Explanation: Cannot reactivate space management for
directory-spec: error.
this file system.
Explanation: TSM cannot open the directory.
System Action: TSM cannot reactivate space
management support to the file system. System Action: TSM cannot complete the requested
operation.
continues, check with your system administrator. User Response: Retry the operation. If the problem
ANS9157W program-name: cannot turn off ENOSPC
checking in kernel: error. ANS9168E program-name: cannot open database
file-spec: error.
Explanation: TSM cannot turn off ENOSPC checking.
Explanation: TSM cannot successfully open
System Action: TSM cannot turn off ENOSPC
(lock/unlock) the database.
checking. Processing continues.
operation.
ANS9158W program-name: cannot turn on ENOSPC
checking in kernel: error.
ANS9169E program-name: cannot create directory
Explanation: TSM cannot turn on ENOSPC checking.
directory-spec, reason.
System Action: TSM cannot turn on ENOSPC
Explanation: TSM cannot create this directory.
checking. Processing continues.
System Action: TSM does not create this directory.
continues, check with your system administrator. User Response: Verify that this directory does not
already exist, and that its parent directory has proper
permissions.
ANS9159E program-name: unable to create temporary
file.
ANS9170E program-name: file-system is not a
Explanation: TSM cannot create a temporary file.
mounted local file system.
System Action: TSM cannot complete its operation.
Explanation: TSM did not find that this file system is
User Response: Retry the operation. If the problem properly mounted.
System Action: TSM ignores the file system.
User Response: Verify that this file system is local and
ANS9160E program-name: cannot write to temporary
mounted and activated properly.
file file-spec: error.
Explanation: TSM cannot complete writing to the
temporary file.
operation.

problem continues, check with your system
ANS9171E Internal string is too long: error.
administrator.
Explanation: TSM internally has a long string that is
beyond its capability.
ANS9189I Recall stopped by user
Explanation: You requested that TSM stop the recall
operation and stops processing.
operation.
System Action: Recall stopped.
ANS9178E program-name: cannot open file file-spec:
error. ANS9191E Error checking file system state
Explanation: TSM cannot open the file. Explanation: The system cannot open /dev/dsm or
cannot open the file system.
operation. System Action: Transaction stopped.
User Response: Retry the operation. If the problem User Response: Retry the operation. If the problem
continues, check with your system administrator. continues, check with your system administrator.
ANS9183E program-name: file system file-system is ANS9192I Cannot disable file-system.

not in the dsmmigfstab file.
Explanation: TSM cannot disable the file system.
Explanation: TSM cannot find the file system in the
dsmmigfstab file. System Action: TSM ignores the request.
System Action: TSM cannot complete the requested User Response: TSM space management is not
operation. installed correctly. Read the space management
documentation for installation instructions, or check
User Response: Ensure that the file system is both with your system administrator.
valid and local. Retry the operation. If the problem
ANS9193I Cannot open file-system.
ANS9184E program-name: cannot allocate memory, Explanation: TSM cannot open the file system.
error: error. System Action: TSM ignores the request.
Explanation: TSM cannot allocate adequate storage for User Response: Verify whether this file system exists
the user. and whether space management has been added to it.
operation. ANS9194W A selective migration is in progress.
User Response: Retry the operation. If the problem Wait until it completes and retry the
continues, check with your system administrator. recall.
Explanation: You tried a recall operation while a
ANS9186E program-name: cannot open mounted file selective migration is in progress.
system file-system: error. System Action: TSM ignores the request.
Explanation: TSM cannot open mounted file system. User Response: Wait until the selective migration is
System Action: TSM ignores the file system. complete and retry the recall operation.
User Response: Verify that this file system is mounted

and activated properly. ANS9195W A selective recall is in progress. Wait
until it completes and retry the
migration.
ANS9188E Not enough memory for recall operation
Explanation: You initiated a migration operation while
Explanation: TSM cannot allocate storage for the a selective recall is in progress.
requested recall operation.
System Action: TSM ignores the request.
operation. User Response: Wait until the selective recall is
complete and retry the migration operation.
User Response: Retry the recall operation. If the

User Response: Remove the ENABLELANFREE
ANS9196W The PASSWORDACCESS option in
option from the system option file. ENABLELANFREE
your dsm.sys file is not set to
can only be used when HSM is not installed.
GENERATE. Reset it to GENERATE and
restart the HSM client.
ANS9230E Cannot unmount FSM from file system
Explanation: The PASSWORDACCESS option in your
file-system. Message from umount
dsm.sys file is set to PROMPT. It must be set to
command:
GENERATE in order for automatic space management
services to work. Explanation: Space management control files have
been updated or deleted, or both, for the file system.
System Action: TSM terminates the client.
However, FSM cannot be unmounted because the file
User Response: The root user must set the system is being referenced by another process.
PASSWORDACCESS option to GENERATE in the
System Action: TSM left FSM mounted on the file
dsm.sys file.
system.
User Response: Determine why unmounting the FSM
ANS9197E File: file-name has already been recalled.
failed.
Explanation: You tried to recall the a file that has If the reason is Device Busy, try unmounting the
already been recalled. FSM by issuing the umount command for the file
System Action: TSM does not highlight the file. system.
If umount again fails, check to see if the current
directory is in the file system, or if another process
is referencing the file system, such as an NFS mount
ANS9198E File: file-name is a resident file. or an open file.
Explanation: You tried to recall a file that is resident. After the file system is clear of references, issue the
umount command for the file system. No problems will
System Action: TSM will not highlight the file. result in continuing to run with the FSM mounted and
User Response: None. a machine reboot will eliminate the FSM.
ANS9199S Cannot open /dev/fsm ANS9240W Couldn’t acquire serial number of disk
disk-name at LUN LUN-id.
Explanation: TSM cannot open the space management
device file, /dev/fsm. Explanation: TSM was not able to determine the serial
number of the specified disk. The disk may not support
System Action: TSM cannot complete the operation. SCSI inquiries of the Vital Product Data on page 0x80.
User Response: Check to see whether TSM is installed System Action: Server-free data movement will not be
correctly and that the /dev/fsm file exists. Correct the possible for data residing on the specified disk.
problem and retry the operation.
ANS9201W Lanfree path failed: using lan path.

ANS9249E File ’file-namefile-namefile-name’ accessed
Explanation: A lanfree connection could not be made. during migration. File skipped.
System Action: The system will connect to the server Explanation: The specified file-name was not migrated
without using the Lanfree path. because the file was accessed by another process during
User Response: Verify your lanfree setup. the attempt to migrate it.
System Action: TSM left the file resident.
ANS9203E ENABLELANFREE can not be used User Response: If you want the file migrated, stop the
when HSM is installed. process which is accessing the file and retry the
Explanation: The TSM client has detected that HSM is migration.
installed on the system. LanFree is not a valid option
when HSM is installed. This error occurs on AIX when ANS9250I File system ’file-system’ reconciliation
this file is found: completed.
/usr/tivoli/tsm/client/hsm/bin/dsmrecalld or on
Solaris when this file is found: Explanation: TSM has finished reconciling the file
/opt/tivoli/tsm/client/hsm/bin/dsmrecalld system.
System Action: An invalid option is detected and System Action: TSM continues.
processing stops.

User Response: Continue with normal operations. User Response: If you want to use the space
management function, make sure you connect to a
server that supports space management.
ANS9251E ProgramName: Cannot parse
command-line options correctly.
ANS9263W program-name: cannot reserve transition
Explanation: An internal program error occurred
stub file for file system file-system:
trying to parse the command-line arguments.
reason.
System Action: The program is not able to process the
Explanation: TSM cannot reserve transition stub file.
request.
TSM tries to reserve some space for the transition stub
User Response: Use the -h or -help option to see what file for emergency cases. At this point, there is either
options are allowed on the command-line, and then not enough space or inodes to allow the reservation.
retry the request. If this problem continues, contact The attempt to reserve the transition stub file will be
your service representative. made again during reconciliation.
System Action: TSM cannot reserve space for the
ANS9254E Error encountered while adding implicit transition stub files. Processing continues.
excludes to the include-exclude list.
User Response: If possible, make more space or
Explanation: Error encountered when implicitly inodes available and run reconciliation.
excluded files are being added to the include-exclude
list.
ANS9267E program-name: File system file-system has
System Action: TSM cannot proceed. exceeded its quota.
User Response: Retry the operation. If the problem Explanation: TSM detects that the file system has
persists, contact your service representative. exceeded its quota. No more data can be migrated out
ANS9255E program-name: invalid value found in the System Action: TSM will not migrate files from this
dsmmigfstab file for file system file-spec. file system.
Explanation: TSM detects invalid values in the User Response: Recall some files, or ask the system
dsmmigfstab file. The entry that contains the invalid administrator to increase the quota for this file system.
values is for file system file-spec
System Action: TSM cannot perform migration until ANS9280E program-name: cannot get space
the error is corrected in the table. management kernel extension ID. Error :
error.
User Response: Find the invalid values in the table
entry and correct them using the dsmmigfs command Explanation: The program cannot determine the level
or the HSM graphical user interface. of space management client kernel extension.
System Action: TSM stops the operation.
ANS9256E File ’file-namefile-namefile-name’ is
User Response: Ensure that space management is
currently opened by another process.
installed correctly, and then retry the operation. If the
File skipped.
problem continues, check with your system
Explanation: The specified file-name was not migrated administrator.
because the file was open by one or more other
processes.
ANS9281E Space management kernel extension is
System Action: TSM left the file resident. downlevel from the user program.
User Response: If you want the file migrated, stop the Explanation: The space management kernel extension
processes which currently have the file open and retry on the system is downlevel from the user program that
the migration. is currently running. Unexpected results may occur.
System Action: TSM stops processing the kernel
ANS9257E Server ’server-name’ does not support extension.
space management.
User Response: Upgrade the space management
Explanation: The specified server-name does not kernel extension to the correct level, and then retry the
support space management. It is a downlevel server, or operation.
a platform that does not support space management.
System Action: TSM failed the operation.

ANS9282E User program is downlevel from the ANS9288I File file-name of size file-size is too small
space management kernel extension. to qualify for migration.
Explanation: The user program that is currently Explanation: The file is smaller than the minimum
running is downlevel from the space management size required for migration. A file is considered for
kernel extension on the system. Unexpected results migration only if its size is greater than both the stub
may occur. file size specified for the file system plus 1 byte and the
block size defined for the file system.
System Action: TSM stops processing the extension.
System Action: TSM does not migrate this file because
User Response: Upgrade the user program to the
it will not free additional space.
correct level, and then retry the operation.
ANS9283K Tivoli Space Manager is recalling a
migrated file. ANS9289I Object ’dir-name’ is a directory. It is
skipped for migration.
Explanation: The space management kernel extension
is attempting to access a file that is not stored locally. If Explanation: The object is a directory. It is not
the file is migrated, TSM is attempting to access it from migrated. Space management does not migrate
an TSM space management server. directories.
System Action: TSM waits for the kernel to access the System Action: TSM does not migrate this object
file. because it is a directory.
ANS9284K File access waiting for migration to ANS9290I File file-name of type file-type is skipped
complete. for migration.
Explanation: The file being accessed is currently being Explanation: The file either cannot be read, is not a
migrated. Access to this file must wait until the regular file, or its type is unknown to space
migration process is finished. management. Space management only migrates regular
files and does not migrate directories.
System Action: TSM waits until the file migration is
completed. System Action: TSM does not migrate this file.
ANS9285K Cannot complete remote file access. ANS9291E program-name: A conflicting space
management program is already running
Explanation: The space management kernel extension
in the file-system file system. Re-run this
cannot complete the remote file access. The file may be
program later in this file system.
migrated to an TSM migration server. The file cannot
be recalled to the local machine. The server could be Explanation: TSM detected another program running
temporarily disabled. in the file system that cannot run at the same time as
the program your tried to initiate. The following
programs cannot run at the same time for a file system:
User Response: Check to see whether the server has dsmreconcile
been disabled by the system administrator, then retry dsmautomig
the operation. dsmmigfs remove.
Also, dsmmigfs remove cannot run while a migration
ANS9286K File migration has been discontinued. process is running in the file system.
Explanation: Migration stops because the file is being System Action: TSM will not run the program at this
migrated by another process. time.
System Action: TSM terminates the current operation. User Response: Try running the program later.

ANS9292E program-name: Cannot access lock file
lock-file/lock-filelock-file: error
Explanation: TSM cannot access a lock file due to an
error. The lock file provides serialization of certain

programs to prevent conflicting processes from running migration server is an old version. This file will not be
at the same time. migrated. Note: TSM checks only the migration server
for a backup copy. If the migration server and backup
System Action: TSM will not run the program at this
server are different servers, there must be a valid
time.
backup copy of the file on the migration server.
User Response: Check the permissions on the
System Action: TSM does not migrate this file.
directories leading up to the lock file and also the
permissions on the program executable. User Response: Back up the current file on the
migration server, or assign a management class to this
file that does not require a current backup copy. Retry
ANS9293E TSM space management cannot access
the operation.
ERRORPROG error-program:error
Explanation: TSM encountered an error trying to
ANS9299I Cannot get the number of migrated files
access the program specified with the ERRORPROG
for file system file-system.
option in your client system options file (dsm.sys). This
message will appear only the first time this error Explanation: Failed to get the number of migrated
occurs. files on the file system. The number is stored in the
status file for the file system.
System Action: TSM cannot send a severe error
message to the specified error message program. System Action: If you are removing space
management from the file system, processing stops.
User Response: Check to make sure the program
Space management is not removed.
exists and that it accepts standard input when run. It is
usually best if ERRORPROG specifies the fully User Response: Run reconciliation to reconcile the file
qualified file name of the program. system. Retry operation.
ANS9294I No files matching ’file-name’ were found. ANS9300I Migrated files found in file system
file-system. Check for any error
Explanation: You entered a search pattern or file name
encountered during recall.
that cannot be found in the local file system.
Explanation: Remove space management failed
because there are migrated files in the file system. TSM
User Response: Ensure that your search pattern is was unable to recall any files, or some of the migrated
correct, or specify a new search string. files may have failed during a recall operation.
System Action: TSM remove processing stops.
ANS9297I File file-name is skipped for migration:
User Response: Check for error messages that
No backup copy found.
occurred during the recall process, correct any
Explanation: A management class is assigned to the problems, and retry the remove process.
file with the attribute MIGREQUIRESBKUP set to YES.
This requires a current backup copy of the file before
ANS9301I Cannot remove the entry for file-system
migration. However, there is no backup copy found on
from the dsmmigfstab file.
the migration server. This file will not be migrated.
Note: TSM checks only the migration server for a Explanation: The entry for the file system in the
backup copy. If the migration server and backup server dsmmigfstab file cannot be removed. Possible reasons:
are different servers, TSM does not find a backup copy v Not enough memory to create temporary file name
of the file. for temporary file system table.
v Not enough free space or inodes to create temporary
file system table
User Response: Back up this file on the migration v Cannot open the real and/or temporary file system
server, or assign a management class to this file that table files.
does not require a current backup copy. Retry the
System Action: TSM does not remove the entry from
operation.
the dsmmigfstab file.
User Response: Manually edit the dsmmigfstab file
ANS9298I File file-name is skipped for migration:
and delete the entry.
Backup copy found is not current.
Explanation: A management class is assigned to the
migration. However, the backup copy found on the

ANS9302E Mount FSM: ERROR - file-system is not ANS9306E Mount FSM: ERROR - mount-path must
in the dsmmigfstab file. Check the be a directory
/etc/adsm/SpaceMan/config/dsmmigfstab
Explanation: TSM cannot mount the file system
file, or add space management to the
because the mount path is not a directory.
file system.
System Action: TSM does not mount the FSM to the
file system.
because it is not listed in the dsmmigfstab file.
User Response: Correct the problem and retry the
mount. Make sure the mount path is a directory.
file system.
User Response: If you previously added space
ANS9307W Mount FSM: TSM space management is
management to the file system, check the
already mounted on mount-path
/etc/adsm/SpaceMan/config/dsmmigfstab file to see
whether the entry has been removed or commented Explanation: TSM cannot mount the file system
out. If you want to add space management to the file because the file system is already mounted.
system, use 'dsmmigfs add'.
file system.
ANS9303E Mount FSM: ERROR - file system type
’FSM’ was not found. TSM space User Response: None.
management is not installed correctly.
Please read the space management ANS9308E Mount FSM: ERROR - mount-path is not
documentation for installation a supported native file system
instructions.
Explanation: TSM cannot mount the file system because it is not a supported native file system.
because the file 'FSM' entry is missing from /etc/vfs.
System Action: TSM does not mount the FSM to the file system.
file system.
User Response: The file system must be one of the
User Response: AIX only. TSM space management is supported native file systems in order for the TSM
not installed correctly. Read the space management space management to mount it.
documentation for installation instructions.
ANS9309I Mount FSM: TSM space management

ANS9304E Mount FSM: ERROR - invalid source mounted on mount-path
(object) path ’source-path’: error
Explanation: TSM successfully mounted the FSM to
Explanation: TSM cannot mount the file system due the file system.
to an invalid path.
System Action: TSM space management now manages
System Action: TSM does not mount the FSM to the the file system.
file system.
mount.
ANS9310E Mount FSM: ERROR - cannot FSM
mount source-path on mount-path: error
ANS9305E Mount FSM: ERROR - invalid mount
(stub) path ’mount-path’: error Explanation: TSM cannot mount the file system due
to the specified error.
Explanation: TSM cannot mount the file system due
to an invalid path. System Action: TSM does not mount the FSM to the
file system.
file system. User Response: Correct the problem and retry the
mount.
mount. Make sure the directory exists.
ANS9311E Mount FSM: ERROR - cannot unlock
file system, internal error: error
Explanation: TSM cannot unlock the internal file
system lock.

System Action: TSM does not allow non-root user
ANS9357E The dsmscout executable cannot be used
access to the file system.
on the user level.
User Response: Attempt to unmount the file system,
Explanation: The dsmscout process is exclusively
and try the mount again. If the problem continues,
started by the dsmmonitord.
System Action: TSM aborts the operation.
ANS9312S program-name: Cannot change User Response: None.
owner/group on file: file-name: error
Explanation: TSM cannot change the ownership or ANS9400W program-name: Recovered program-name.
group, or both for the specified file. This change is The daemon was either not started or in
necessary for space management to run properly. corrupted state.
System Action: TSM cannot continue processing. Explanation: TSM HSM daemon breakdown with
automatic recovery by the dsmwatchd.
User Response: Ensure that directory permissions
allow the file owner or group to be changed. Reissue System Action: Restarting the daemon.
the command.
ANS9318W program-name: error encountered while

ANS9401E program-name: Cannot kill recall daemon.
undeleting file system file-system.
Explanation: TSM A request for killing the recall
Explanation: TSM encountered an error performing
daemon failed. This may happen during node failover.
undelete on the file system.
System Action: none.
User Response: Continue with normal operation
unless further errors occur.
ANS9349I Selective Recall completed

ANS9402E program-name: Cannot notify to recover
Explanation: The selective recall was completed. HSM operations on a failure node.
System Action: TSM recalled the files. Explanation: TSM In order to takeover the
functionality of a malfunctional partner node the
dsmwatchd must notify the local daemons.
System Action: none.
ANS9353I Selective Recall stopped by user.
User Response: Contact service representative.
Explanation: You requested to stop the selective recall
operation.
ANS9403E program-name: The local HSM
System Action: Selective recall stopped.
functionality cannot be recovered.
User Response: Continue with normal operations. Trying to initiate failover to another
node.
ANS9354E Not enough memory for selective recall Explanation: TSM If the GPFS daemon crashes or the
operation. local HSM daemons cannot perform their function for
whatever reason the dsmwatchd will try to migrate the
Explanation: TSM cannot allocate memory for the functionality to another node.
requested recall operation.
System Action: Migrate HSM functionality to another
System Action: TSM cannot complete the requested node.
recall operation.
User Response: Check failure node. It may be
User Response: Close all unneeded applications and necessary to recover the local GPFS daemon.
the amount of data returned can also help, or see your
system administrator. ANS9404W program-name: Received failover request
from node ID with frame ID . Trying to
takeover remote filesystems.
Explanation: TSM The local dsmwatchd received a
notification about a failing HSM node. It will try to
takeover its managed filesystems.

System Action: HSM will try to takeover the managed System Action: None.
filesystems from a failure node.
User Response: Check failure node.
ANS9418W program-name: File file-name is locked at
ANS9405W program-name: The takeover of filesystem the moment. Will try to acquire the SDR
path succeeded. lock in a few seconds again.
Explanation: TSM During a failover scenario the local Explanation: SP-wide files are stored in the SDR.
node will try to takeover the managed filesystems of a These files can be accessed as soon as it is possible to
failure node. set a certain SDR lock. If a 2nd process holds this lock,
access to the file is denied till the lock is released.
System Action: HSM will try to takeover the managed
filesystems from a failure node. System Action: TSM None.
User Response: Check failure node. User Response: Wait. If the situation does not get
resolved within a reasonable amount of time (about 1
min.), execute dsmmigfs SDRreset. This will reset all
ANS9412E program-name: Failover is disabled on the
activated locks in the SDR for the local GFPS node set.
local machine. Aborting failover ...
Explanation: TSM Failover operations were disabled
ANS9419E program-name:The filesystem
either by the system or the user.
filesystem-name is either already managed
System Action: None. locally or under the contol of a remote
HSM instance.
User Response: Check failover policy if necessary.
Explanation: A GPFS filesystem can be managed just
once.
ANS9413W program-name: The remote node was able
to recover from failure situation. System Action: Aborting operation.
Aborting takeover ...
User Response: Execute dsmmigfs query -detail to
Explanation: The remote dsmwatchd was able to have a look at the current HSM configuration within
recover from the failure situation during the local the local GFPS node set.
takeover operation.
System Action: None. ANS9420E program-name: An update of the
configuration files in the SDR is not
User Response: Check failure node for consistency. allowed as long as failover is disabled
on the local machine.
ANS9414E program-name: Unable to create file-name Explanation: You cannot update configuration files in
in the SDR. Aborting ... the SDR when failover is disabled on the local machine.
Explanation: An update of an SDR object failed. System Action: TSM Aborting operation.
System Action: Aborting operation. User Response: Do nothing, or activate failover by
User Response: Check SDR consistency. using dsmmigfs enableFailover before running
dsmmigfs SDRupdate.
ANS9415W program-name: The HSM service provider

on Node ID: node with Frame ID: frame ANS9421W program-name: Recovered from Lock on
left the failover group voluntarily. SDR File file-name
Explanation: Failover was disabled on a remote HSM Explanation: This output relates to ANS9418W. A
node. previously blocked SDR file got unlocked.
System Action: None. System Action: TSM continues.
ANS9416W program-name: The HSM service provider ANS9423E program-name: Setting the default
on Node ID: node with Frame ID: frame partiton name failed! Aborting operation
joined the failover group. ...
Explanation: TSM Failover was activated on a remote Explanation: The application needs to have access to
HSM node. the SP Group Services. In this context it tries to extract
the default partition name for the local system as

provided by spget_syspar. The data extraction failed. User Response: Check consistency of the GPFS
daemon.
System Action: Aborting operation.
User Response: Check node consistency.
ANS9442E program-name: It appears that another
dsmmigfs add/rem/update command is
ANS9424E program-name: Severe problem! It was in process within the local GPFS
not possible to send a message to the SP nodeset. Please wait a few moments,
Group Services. then repeat the operation. If a previous
dsmmigfs command was aborted, there
Explanation: The Failover environment requires could be a stale lock in the SDR. If so,
proper access to the SP Group Services. The run dsmmigfs SDRreset to fix the
distribution of a message failed. problem.
System Action: Aborting operation. Explanation: There can only be one instance of
User Response: Check node consistency. dsmmigfs add/rem/update running within a GPFS
nodeset at the same time.
ANS9425E program-name: It was not possible to System Action: Aborting operation.

notify the dsmwatchd in order to User Response: Wait for a bit and try again. If no
distribute a message within the failover other instance of dsmmigfs is running within the local
group. The data of the current operation GPFS nodeset run dsmmigfs SDRreset.
may get lost.
Explanation: Some HSM commands need to inform ANS9443E program-name: The operation cannot be
the dsmwatchd about the current operation. This executed in a deactivated failover
notification failed. environment.
System Action: Aborting operation. Explanation: The operation relies on an active failover
User Response: Restart the GPFS daemon and check environment.
that the DMApi support is active by executing System Action: Aborting operation.
/usr/lpp/mmfs/bin/mmlsfs deviceName.
User Response: Run dsmmigfs enableFailover on the
local node and repeat the operation.
ANS9428E program-name: The takeover of filesystem
filesystem failed.
ANS9449W program-name: Forced deactivation of the
Explanation: A remote node requested the takeover of local failover environment!
a filesystem but the local activation failed.
Explanation: TSM Failover was initiated or a problem
System Action: Aborting operation. with the group services occured.
User Response: Check whether the filesystem gets System Action: Continuing failover or aborting
managed by another node. If not, recover the initial operation.
node and restart the HSM service.
User Response: Check HSM and SP Group Services
environments. Execute dsmmigfs enableFailover after
ANS9432E Severe problem! It was not possible to resolving the problem.
start the dispatcher thread for the
communication with the SP Group
Services. The failover environment is in ANS9450W program-name: No eligible filesystem for
corrupted state now. takeover.
Explanation: Unable to start required thread. Explanation: None of the locally mounted GPFS
filesystems matches with the remotely managed
System Action: Aborting operation. filesystems of the failure node.
User Response: Check node consistency. System Action: Aborting takeover operation.
User Response: Check that the filesystems of the
ANS9433E program-name: dm_send_msg failed with remote failure node get managed elsewhere within the
errno Errno. node set.
Explanation: Unable to execute DMApi call.
System Action: Aborting operation.

ANS9451E program-name: GPFS or the SP switch is ANS9459E Using the specified MAXCANDIDATES
down locally. Aborting takeover activies parameter would produce an
... out-of-space condition in the parent
filesystem of
Explanation: TSM GPFS is not functional locally.
/etc/adsm/SpaceMan/candidatesPool.
System Action: Aborting takeover operation. Based on the current free space situation
the maximum value for the
User Response: Check switch and VSD status. The MAXCANDIDATES parameter is value.
local system must be unfenced.
Explanation: TSM The automigration candidate pools
for the selected filesystem require
ANS9452E program-name: The DMApi is not MAXCANDIDATES/10 KB plus a safety buffer of 5 MB
functional locally. Aborting takeover of memory under
activies ... /etc/adsm/SpaceMan/candidatesPool, which exceeds
Explanation: The operation stopped because the the available space.
DMApi interface is not accessible. System Action: TSM Abort operation.
System Action: Aborting takeover operation. User Response: Increase the filesystem size or choose
User Response: Check GPFS status. a smaller value for the MAXCANDIDATES parameter.
You may also create a dedicated filesystem with
sufficient space for the migration pools under
ANS9454W program-name: Performing /etc/adsm/SpaceMan/candidatesPool. Kill the
synchronization between the local and dsmscout processes after performing this option.
global file event handling.
Explanation: The local node received a request from a ANS9462E Failover functionality is not supported
remote node to synchronize with the global file event with this HSM release.
handling (DMApi event disposition).
Explanation: TSM user executed dsmmigfs with
System Action: Synchronizisation proceeds. failover flag on an unsupported platform.
User Response: None. System Action: TSM Abort operation.
ANS9455E program-name: Unable to join the local
failover group with rc=return-code!
ANS9469E Warning! Unable to write a complete
Explanation: SP Group services reported a problem migration candidate list due to low
accessing/creating an HSM group. space in the parent filesystem of name.
System Action: Aborting operation. Explanation: TSM Low space in filesystem which
User Response: Check PSSP environment on the local stores the migration candidates files.
node. System Action: TSM The executable writes a partial
migration candidates list.
ANS9458W program-name: Joined successfully to the User Response: Increase the filesystem size or create a
local failover group! dedicated filesystem with sufficient size under the
Explanation: Joining the Group Services HSM failover given path.
group succeeded.
System Action: Processing continues. ANS9500W program-name: cannot disposition the
mount event. Reason: error
Explanation: The system wide mount event could not
be dispositioned. Mount events will not be received by
this daemon.
User Response: Try to resolve the problem and restart
the recall daemon. If the problem cannot be resolved
immediately, kill and restart the recall daemon after an
TSM space management supported file system has been
added using dsmmigfs or after a file system has been
mounted using the mount command.

system (Hierarchical Storage Management Support).
ANS9501W program-name: cannot set event
disposition on session session for file
system mountdir token = token. Reason : ANS9507E program-name: cannot request the right
error on session session for file handle
filehandle token = token. Reason : error
Explanation: Events could not be dispositioned on the
file system. No events will be received for this Explanation: TSM space management cannot request
filesystem. HSM is not enabled for this file system. the required right on a file.
System Action: TSM continues. System Action: Processing of the file is interrupted.
User Response: The file system must be one of the User Response: Continue with normal operation.
supported native file systems in order for the TSM
space management to support it. Verify that the mount
options the file system are correct. Correct the problem ANS9508W program-name: cannot release the right on
and remount the file system. session session for file handle = filehandle
token = token. Reason : error
ANS9502W program-name: cannot remove event Explanation: TSM space management cannot release
disposition on session session for file the right on a file.
system mountdir token = token. Reason : System Action: Processing of the file is interrupted.
error
Explanation: Event dispositions could not be removed
from the file system.
ANS9509W program-name: received an unexpected
System Action: TSM continues. event of type event-type on session
User Response: Correct the problem and retry the session.
operation. Explanation: TSM space management daemon
received an unexpected event. This event has not been
ANS9503I program-name: events have been set and dispositioned.
dispositioned on session session for file System Action: TSM ignores event and continues.
system filesystem-name
Explanation: Setting events and dispositioning these
on a DM session enables the file system for TSM space
management support. ANS9510E program-name: cannot get event messages
from session session, expected max
System Action: TSM continues. message-length = msglen, returned
User Response: Continue with normal operation. message-length = return-length. Reason :
error
ANS9504W program-name: The file system Explanation: TSM space management encountered an
filesystem-name is not mounted or is error while trying to receive a message on a DM
mounted with wrong options. session.
Explanation: Either the file system is not mounted or System Action: TSM continues.
it has been mounted with incorrect options. User Response: Continue with normal operation.
User Response: Mount the file system or remount it ANS9511E program-name: cannot read DM attributes
with corrected mount options. on session session for file handle = handle
token = token. Reason : error
ANS9505E program-name: cannot initialize DM Explanation: TSM space management cannot read the
services. Reason: error DM attributes of a DM object, usually a file.
Explanation: TSM space management cannot initialize System Action: Processing of the file is interrupted.
the DM services. User Response: Continue with normal operation.
System Action: TSM cannot start space management
support.
User Response: Correct error and retry operation.
Make sure that DM services have been installed on the

System Action: TSM DM session is not destroyed.
ANS9512E program-name: cannot set DM attributes
on session session for file handle = User Response: See your system administrator.
filehandle token = token. Reason : error
Explanation: TSM space management cannot set DM ANS9518E program-name: cannot respond to an
attributes for a DM object, usually a file. event message on session session using
token token Reason : error
System Action: Processing of the file is interrupted.
Explanation: An event message could not be
responded to (returned to the system).
System Action: TSM space management continues.
ANS9513E program-name: cannot remove DM
attributes on session session for file User Response: If a user process is unexpectely
handle = filehandle token = token. Reason blocked and cannot be killed, see your system
: error administrator.
Explanation: TSM space management cannot remove
DM attributes for a DM object, usually a file. ANS9519W program-name: cannot set eventlist for a
file system on session session token =
token fs-handle = fs-handle. Reason : error
Explanation: An eventlist could not be set on a file
system. None of the events will be generated by the
ANS9514E program-name: cannot create a file handle system on this file system.
from path. Reason: error
Explanation: TSM space management cannot create a
User Response: Resolve the problem and retry the
file handle from the given file.
operation.
User Response: Continue with normal operation. ANS9520E program-name: cannot set a managed
region on session session for file handle
= filehandle token = token. Reason : error
ANS9515E program-name: cannot set the migration
information. Reason: error Explanation: A managed region could not be set on a
file. No events will be generated for this file.
Explanation: TSM space management cannot set the
migration information of a file, because space System Action: Processing of the file is interrupted.
management cannot create a file handle from the file
User Response: If this error recurs, see your system
and/or from the file system.
administrator.
User Response: Continue with normal operation. ANS9521E program-name: cannot get the file
attributes on session session for file
handle = handle token = token. Reason :
ANS9516E program-name: cannot create an user
error
event message on session session.
Reason: error Explanation: TSM space management cannot read the
attributes of a file.
Explanation: TSM space management cannot create an
user event message, needed to reference rights on a file System Action: Processing of the file is interrupted.
to be processed.
System Action: Processing of the file is interrupted. administrator.
ANS9523E program-name: is unable to verify the
stubsize for the file on session session
ANS9517E program-name: cannot clear all event
file handle = filehandle token = token.
messages from session session. Reason:
Reason : error
error
Explanation: A correct stubsize could not be
Explanation: TSM space management is in the process
determined by the system.
of destroying a DM session. There are still - unexpected
- event messages on this session that could not be System Action: TSM stopped migration of the file.
responded to.

ANS9529W program-name: cannot obtain handle of
operation.
file system state file
Explanation: TSM space management could not find
ANS9524W program-name: adjusted stubsize to an
the handle of a file system state file, that is stored in
allowed value on session session file
the global state file. This can be true if either space
handle = filehandle token = token old
management is querying a file system that has no HSM
stubsize = old-size new stubsize =
support added, or the file system state file is corrupted,
new-size
or the global state file is corrupted.
Explanation: The predefined stubsize for the file was
System Action: TSM continues or stops processing,
not valid. The system corrected the stubsize.
depending on the situation.
User Response: If processing has stopped, resolve the
User Response: Continue with normal operation. problem and retry the operation.
ANS9525E program-name: is unable to create a ANS9530W program-name: cannot remove an entry

stubfile on session session for file handle for file-system from the global state file.
= handle token = token. Reason : error
Explanation: The entry for the file system in the
Explanation: An error occurred while creating a stub dmiFSGlobalState file cannot be removed. Possible
file. reasons:
v Not enough memory to create temporary file name
System Action: Processing of the file is interrupted. for temporary file system table.
User Response: Continue with normal operation. v Not enough free space or inodes to create temporary
file system table
v Cannot open the real and/or temporary file system
ANS9526E program-name: cannot open the state file table files.
filename for writing. Reason: error
System Action: TSM does not remove the entry from
Explanation: The state file (global or file system state the global state file.
file) could not be opened.
System Action: TSM stops processing. operation.
operation. ANS9531E program-name: cannot create a DM
session: old session = oldsession session
ANS9527E program-name: cannot write to the state info = session-info. Reason : error
file filename. Reason: error Explanation: TSM space management could not create
Explanation: TSM space management could not write a DM session.
to the state file. System Action: TSM stops processing.
System Action: TSM stops processing. User Response: See your system administrator.
operation. ANS9532W program-name: cannot destroy the session
session. Reason: error
ANS9528W program-name: cannot read from the state Explanation: TSM space management could not
file filename. Reason: error destroy a DM session.
Explanation: TSM space management could not read System Action: TSM continues.
from the state file.
System Action: TSM stops processing.
User Response: Resolve the problem and retry the ANS9533W program-name: failed getting all sessions.
operation. Reason: error
Explanation: TSM space management could not get all
DM sessions on the system.
System Action: TSM stops processing.

User Response: Resolve the problem, then restart the
ANS9534W program-name: cannot query a session.
monitor daemon.
Reason: error
Explanation: TSM space management could not query
ANS9544W program-name: cannot obtain allocation
a DM session on the system.
info on session sessionL file handle =
System Action: TSM continues. filehandle token = tokenL offset=offsetL
number of extents = nextents (returned =
nreturned) Reason: error
Explanation: TSM space management could not get
ANS9535E program-name: a file handle could not be
allocation information of a file.
created from the file descriptor
file-descriptor. Reason: error System Action: Processing of the file is interrupted.
Explanation: TSM space management could not create User Response: If this error recurs, see your system
a file handle. administrator.
ANS9545E program-name: cannot get lock for
lockdirlockfile to continue processing.
administrator.
Explanation: TSM space management could not obtain
a lock for a file.
ANS9538W program-name: request request for DM file
attributes not recognized System Action: Processing stopped.
Explanation: An unknown request type has been User Response: Resolve the problem and retry the
encountered that cannot be handled. operation.
ANS9548W Cannot complete remote file access.
Explanation: TSM space management cannot complete
the remote file access. The file may be migrated to an
ANS9539E program-name: cannot create a file system
TSM migration server. The file cannot be recalled to the
handle from the file handle = filehandle.
local machine. The server could be temporarily
Reason : error
disabled.
Explanation: A file system handle could not be
created from a file handle.
User Response: Check to see whether the server has
been disabled by the system administrator, then retry
User Response: Continue with normal operation. the operation.
ANS9542E program-name: the file attributes could ANS9550W File recall has been discontinued.
not be set on session session for file
Explanation: Recall stops because the file being
handle = filehandle token = token flag =
recalled would cause the file system to run out of
flag Reason : error
space.
Explanation: TSM space management could not
update file attributes.
User Response: Increase the file system space, or
remove unneeded files, or wait until space
User Response: If this error recurs, see your system management has migrated files off the file system by
administrator. demand or threshold migration, or manually migrate
files. Then retry the operation.
ANS9543W program-name: cannot reserve blocks for

nospace condition on file system ANS9552E program-name: cannot add fsm to
filesystem-name. Reason: error file-system; path includes non-local file
system.
Explanation: TSM space management could not
reserve blocks on the file system to be used in a Explanation: An attempt was made to add space
nospace condition. management to a file system whose path contains
non-local elements.

User Response: File system must be entirely local. reason these files are not selected, for example, inclexcl
list.
ANS9553I Wrote temporary candidates list to
file-name. ANS9735E Error doing realtime initialization
Explanation: Due to out of space condition, the Explanation: TSM ran out of resource (either processes
candidates list was written to the named temporary or shared storage) that prevents it from starting a
file. migrate or recall operation. Your file selections remain
intact.
System Action: Temporary file created.
System Action: TSM cannot start the migrate or recall
User Response: Temporary file can be copied to the
operation.
appropriate .SpaceMan directory when space is made
available. User Response: Retry the operation. If unsuccessful,
ANS9613E program-name: Stubsize of stubsize bytes
is not supported on filesystem. ANS9736E Not enough memory for authorization
list table
Explanation: The given stubsize value not a multiple
of the file system blocksize and cannot be supported. Explanation: TSM cannot allocate enough storage for
the authorization list.
System Action: The program aborts the operation.
User Response: Use a correct stub size.
operation.
User Response: Retry the operation. If unsuccessful,
ANS9641S Invalid option ’option’ found in options
file ’file-name’ at line number : number
Invalid entry : ’entry’
ANS9737E Authentication failed -- Exit TSM to
Explanation: The specified option in the TSM options
retry
file (file-name) is in error.
Explanation: You typed an incorrect password four
times in a row.
User Response: Correct the options file entry.
without a correct password.
ANS9732E No Backup Copy Group for
User Response: Exit and restart TSM if authorized;
Management Class: management-class
otherwise, see your system administrator.
not have a backup copy group specified.
ANS9738S Out of memory
Explanation: TSM found an error allocating storage at
User Response: See your system administrator. initialization.
System Action: TSM cannot continue.
ANS9733E File: File-name excluded by the
Include/Exclude list
Explanation: You tried to back up the named file-name
ANS9739E Cannot get shared memory
that was specified to be excluded from backup.
Explanation: The system ran out of shared storage
resources.
User Response: Specify the file using the Include
System Action: TSM cannot continue without a
option and retry the operation.
shared storage segment.
User Response: Check the output of the “ipcs”
ANS9734E There are number file(s) not selected.
program to see if there are many new shared storage
Click on file to find out reason.
segments. Use “ipcrm” to remove them. If this problem
Explanation: There are files that cannot be selected. continues, configure UNIX to allow more shared
storage segments.
System Action: These files will not be selected for
migrate or recall.
User Response: Click on the files to find out the

ANS9740S This program is not installed correctly. ANS9790I File is skipped for migration: No
Please place the application defaults file backup copy found.
(file-name) into the application default
directory (usually directory-name), or set
the XAPPLRESDIR environment
variable to the directory containing the
migration. However, there is no backup copy found on
file-name defaults file.
the migration server. This file will not be migrated.
Explanation: TSM cannot find its resource file (Sm) in Note: TSM checks only the migration server for a
the default directory (directory-name). A problem may backup copy. If the migration server and backup server
have occurred during installation. are different servers, TSM does not find a backup copy
of the file.
System Action: TSM cannot start.
User Response: Back up this file on the migration
server, or assign a management class to this file that
ANS9741E Not enough memory to hold directory
does not require a current backup copy. Retry the
structure
operation.
Explanation: TSM cannot allocate storage for the
requested directory structure. This error can happen
ANS9791I File is skipped for migration: Backup
under migrate or recall operations.
copy found is not current.
operation.
User Response: Retry the operation. If unsuccessful, This requires a current backup copy of the file before
see your system administrator. migration. However, the backup copy found on the
migration server is an old version. This file will not be
migrated. Note: TSM checks only the migration server
ANS9742E Error reading directory structure for a backup copy. If the migration server and backup
Explanation: TSM cannot load the requested directory server are different servers, there must be a valid
structure. This error is due to a corrupted file system or backup copy of the file on the migration server.
a storage shortage. This can happen under selective System Action: TSM does not migrate this file.
migrate or selective recall.
User Response: Back up the current file on the
System Action: TSM cannot complete the requested migration server, or assign a management class to this
operation. file that does not require a current backup copy. Retry
User Response: Retry the operation. If unsuccessful, the operation.
ANS9792W A tree view of a file system is being
ANS9743W No files selected in directory tree built. Please wait until it completes, and
then retry the operation.
Explanation: You did not select any files to list for
migrate or recall. Explanation: You tried to choose Selective Migration
or Selective Recall when a tree view of a file system is
System Action: TSM cannot complete the requested being built.
operation.
User Response: Select files and retry the operation.
User Response: Wait until the tree view build
completes, and then retry the operation.
ANS9744W Size exceeds limit
Explanation: You tried to recall a file that has ANS9796E Cannot access lock file for file-system file
exceeded the maximum file size limitation on your system.
system.
Explanation: TSM cannot access a lock file due to an
System Action: TSM cannot recall the file. error. The lock file provides serialization of certain
User Response: Recall this file on a system that programs to prevent conflicting processes from running
supports the file size. See your system administrator. at the same time.
System Action: TSM will not run the program at this
time.

User Response: Check the permissions on the
ANS9803W Cannot create premigration database.
directories leading up to the lock file and also the
permissions on the program executable. Explanation: Cannot create a premigration database
for this file system.
ANS9797E A conflicting space management process System Action: TSM cannot add space management
is already running in the file-system file to the file system.
system. Rerun this process at a later
User Response: Check with the system administrator.
time.
Explanation: TSM detects that another process that
ANS9804W Cannot create migration candidates list.
conflicts with the process you are trying to run is
running in the file system. The following processes Explanation: Cannot create a migration candidates list
cannot be run at the same time for a file system: for this file system.
dsmreconcile
dsmautomig System Action: TSM cannot add space management
dsmmigfs remove. to the file system.
Also dsmmigfs remove cannot run while a migration User Response: Check with the system administrator.
process is running in the file system.
System Action: TSM will not run the process at this ANS9805W Cannot create .SpaceMan directory.
time. Explanation: Cannot create .SpaceMan directory for
User Response: Try running the process again later. this file system.
System Action: TSM cannot add space management
ANS9799W Cannot open temp file for mount to the file system.
command. User Response: Check with the system administrator.
Explanation: TSM cannot open a temporary file to
process the mount command for this file system. ANS9806W File system type is not supported.
System Action: TSM cannot add space management Explanation: The file system is not a type supported
to the file system. by space management.
User Response: Check with the system administrator. System Action: TSM cannot add space management
to the file system.
ANS9800W Cannot create temp file for mount User Response: Check with the system administrator.
command.
Explanation: TSM cannot create a temporary file to ANS9808W Invalid field in the dsmmigfstab file.
process the mount command for this file system.
Explanation: There is an invalid field in the
System Action: TSM cannot add space management dsmmigfstab file entry for the file system.
to the file system.
User Response: Check with the system administrator. to the file system.
ANS9801W Cannot create transaction file.
Explanation: Cannot create transaction file for this file ANS9809W Cannot open the dsmmigfstab file.
system.
Explanation: TSM cannot open the dsmmigfstab file.
to the file system. System Action: TSM cannot add space management
to the file system.
ANS9802W Cannot create status file.

ANS9811W Server did not respond. Check the
Explanation: Cannot create status file for this file server connection. Select OK to exit.
system.
Explanation: Server did not respond.
to the file system. System Action: TSM stops processing.
User Response: Check with the system administrator. User Response: Exit dsmhsm. Check the server

connection and try again later.
ANS9817W file-system is globally deactivated. Please
wait until the file system is globally
ANS9812I Files not found in current directory. reactivated.
Refresh file systems.
Explanation: The file system is in a global inactive
Explanation: Some files are not found in the local file state.
system.
System Action: TSM cannot continue the process.
System Action: The transaction will show incorrect
User Response: Wait until the system administrator
results.
globally reactivates the file system.
User Response: Refresh the file systems to reflect local
file systems.
ANS9818W A selective recall is in progress. Stop the
recall, and then close the window.
ANS9813W Incorrect data shown. Run reconcile.
Explanation: You tried to close the Selective Recall
Explanation: Information in the space management Status window while a selective recall was in progress.
status file is not synchronized with the file system.
System Action: TSM continues processing.
User Response: Stop the selective recall process, and
User Response: To correct the information, run then close the window.
reconcile, and then refresh the current window.
ANS9819W A selective migration is in progress.
ANS9814W Cannot create migration object ID. Stop the process, and then close the
window.
Explanation: The file system is full. No more free
space can be allocated for the migration object ID when Explanation: You tried to close the Selective Migration
a file is being migrated or recalled. Status window while a selective migration was in
progress.
for this file system. System Action: TSM ignores the request.
User Response: Remove some files in the file system, User Response: Stop the selective migration process,
and then run reconciliation. Retry the operation. and then close the window.
ANS9815W Out of free space or inodes in file ANS9820W A selective recall or a selective
system to migrate or recall. migration is in progress. Wait until it
completes, and then retry the operation.
Explanation: The file system is full. No more free
space or free inodes are available to be allocated for the Explanation: You tried to perform one of the
transaction file that is needed when a file is being following while a selective recall or selective migration
migrated or recalled. process was in progress:
Add space management
System Action: TSM terminates the current operation Deactivate or reactivate space management
for this file system. Global deactivate or reactivate space management
User Response: Remove some files in the file system, Display policy information
and then run reconciliation. Retry the operation. Change password
ANS9816W File system has exceeded its quota. User Response: Wait until the selective recall or
Explanation: TSM detects that the file system has selective migration process is complete, and then retry
exceeded its quota. No more files can be migrated to the operation.
TSM storage for this file system.
System Action: TSM will not migrate files from this ANS9821W New password is not re-entered.
file system. Explanation: You did not re-enter the new password.
User Response: Either recall some files to the local file System Action: The Change password dialog will
system, or ask the system administrator to increase the display again.
quota for this file system.
User Response: Re-enter the new password.

ANS9822W New password is not entered. ANS9829W Recall daemon is not running.
Explanation: You did not enter the new password. Explanation: An TSM recall daemon is not running.
System Action: The Change password dialog will System Action: TSM recall fails.
display again.
User Response: Ask the system administrator to start
User Response: Enter the new password. a recall daemon by issuing the dsmrecalld command.
ANS9823W Current password is not entered. ANS9830W Space monitor daemon is not running.
Explanation: You did not enter the current password. Explanation: The space monitor daemon is not
running.
System Action: The Change password dialog will
display again. System Action: TSM is unable to perform space
management functions.
User Response: Enter the current password.
User Response: Ask the system administrator to start
the space monitor daemon by issuing the dsmmonitord
ANS9824W Cannot update space management
command.
settings for file-system
Explanation: You tried to update space management
ANS9840W Cannot open /dev/fsm.
settings for a file system, and the update failed.
Explanation: While attempting to add space
System Action: TSM continues with normal operation.
management to a file system, TSM was unable to open
User Response: Check with the system administrator. the /dev/fsm device, which is the space management
(hsm) device driver.
ANS9825W Total migrated space is greater than System Action: TSM terminates the requested process
quota for file system. and returns to normal operation.
Explanation: TSM total migrated space is greater than User Response: Retry the operation. If the problem
quota. continues, check with your system administrator.

ANS9841E Cannot get user name for the user ID.
User Response: You can remove this warning message
by increasing the quota for the file system. Explanation: TSM cannot get the user name for the
user ID.
ANS9827W Error accessing the Recall daemon lock System Action: TSM terminates the requested process
file: file name. and returns to normal operation.
Explanation: There is a problem accessing the recall User Response: Retry the operation. If the problem
daemon lock file. continues, check with your system administrator.
System Action: TSM cannot determine whether the
recall daemon is running. Because the recall daemon is ANS9843E Cannot connect to migration server.
needed to perform file recalls, the recall fails.
Explanation: TSM cannot connect to the migration
User Response: Check with the system administrator. server specified in your client system options file.
The recall process needs read access to the
System Action: TSM terminates the requested process
/etc/adsm/SpaceMan/dsmrecalld.pid file.
and returns to normal operation.
ANS9828W Error processing the space monitor
daemon: reason.
Explanation: There is a problem accessing the space
ANS9844E Cannot close the premigrated files
monitor daemon.
database.
System Action: TSM cannot perform automatic space
Explanation: TSM cannot close the premigrated files
management functions.
database for the file system. The premigrated files
User Response: Check with the system administrator. database resides in the .SpaceMan subdirectory of the
The space monitor daemon is normally installed as file system’s root directory.
/usr/lpp/adsm/bin/dsmmonitord.
System Action: TSM terminates the requested process,
and returns to normal operation.

User Response: Retry the operation. If the problem process which is accessing the file and retry the
continues, check with your system administrator. migration operation.
ANS9846W Cannot add space management to file ANS9856E File is currently opened by another
system. process. File skipped. File has already
been migrated or is currently being
Explanation: TSM cannot add space management to
migrated by another process.
the file system.
Explanation: The specified file was not migrated
because the file was opened by one or more other
User Response: Check with the system administrator. processes.
ANS9848W Cannot activate file system file system.
User Response: If you want the file migrated, stop the
Explanation: TSM cannot activate space management processes which currently have the file open, and retry
for the specified file system. the migration operation.
System Action: TSM file system state is not changed.

ANS9858E Bit file for image on push button cannot
User Response: Check with your system be found. Please check to make sure the
administrator. pixmap file exists in your TSM installed
directory.
ANS9852E Cannot query the level of client and Explanation: TSM failed to find the pixmap file
kernel. defined for the push button.
Explanation: The space management GUI client fails System Action: TSM continues with normal operation.
to query the level of kernel and client code.
User Response: Check to see whether the pixmap file
System Action: TSM continues with normal operation. exists in the TSM installation directory.
User Response: Check with your system
administrator. ANS9860W Some selected files are hidden. Change
View option to see all.
ANS9853W The space management client program Explanation: You have selected all files in a directory
is downlevel. or in all subdirectories. Due to the current View option,
Explanation: The space management client is only certain types of files are shown (either migrated,
downlevel compared to the kernel level. resident, or premigrated files).
System Action: TSM continues with normal operation. System Action: TSM proceeds normally.
User Response: Check with your system User Response: If you want to see all selected files,
administrator. change the View option from the View menu bar
option.
ANS9854W The space management kernel is

downlevel. ANS9862W Do you want to exit TSM space
management?
Explanation: The space management kernel is
downlevel compared to the client level. Explanation: You have selected Exit from the File
menu bar option.
System Action: TSM waits for your response.
administrator. User Response: If you want to exit the program, select
OK. Otherwise, select Cancel.
ANS9855W File is accessed during migration. File

skipped. ANS9871W Specified column width is smaller than
the largest attribute value. Data will be
Explanation: The specified file-name was not migrated truncated.
because the file was accessed by another process during
the attempt to migrate it. Explanation: You have entered a column width that is
too small to display all digits of the largest attribute.
System Action: TSM accepts your request.

User Response: To see all attributes in full length,
ANS9879W Age Factor must be a numeric value
increase the column width.
between 0 - 999999999.
Explanation: You have entered an invalid value for
ANS9873W This function should not be used on
Age Factor. It must be a positive number between 0
large file systems. Continue anyway ?
and 999999999.
Explanation: You have decided to open selective recall
or selective migration window, but these functions may
take too long for large file systems. User Response: Enter a positive number between 0
and 999999999.
System Action: TSM waits for your response.
User Response: If you want to continue, select OK.
ANS9880W Age Factor must be a positive number.
Otherwise, select Cancel.
Age Factor. It must be a positive number between 0
ANS9875W Refresh time must be numeric value and
and 999999999.
within 0 - 14400 minutes or 0 - 240 hours
(10 days). System Action: TSM continues with normal operation.
Explanation: You have entered an invalid value for User Response: Enter a positive number between 0
Refresh time. It must be a positive number between 0 and 999999999.
and 14400.
System Action: TSM continues with normal operation. ANS9881W Premigration Percent must be a numeric
value between 0 - 100.
User Response: Enter a positive number between 0
and 14400. Explanation: You have entered an invalid value for
Premigration Percentage. It must be a positive number
between 0 and 100.
ANS9876W Refresh time must be a positive number.
Refresh time. It must be a positive number between 0 User Response: Enter a positive number between 0
and 14400. and 100.
ANS9882W Premigration Percent must be a positive
number.
and 14400.
Premigration Percentage. It must be a positive number
ANS9877W Size Factor must be a numeric value
between 0 and 100.
between 0 - 999999999.
Size Factor. It must be a positive number between 0 User Response: Enter a positive number between 0
and 999999999. and 100.
ANS9883W Quota must be a numeric value between
0 - 999999999.
and 999999999.
Quota. It must be a positive number between 0 and
ANS9878W Size Factor must be a positive number.
999999999.
Size Factor. It must be a positive number between 0
and 999999999. User Response: Enter a positive number between 0
and 999999999.
ANS9884W Quota must be a positive number.
and 999999999.
Quota. It must be a positive number between 0 and
999999999.

ANS9891W Please mark either or both check boxes
and 999999999.
before proceeding.
Explanation: You have not marked either of the check
ANS9885I The premigration percentage will not be
boxes.
updated until you select the Update
push button on the Update window or System Action: TSM does not proceed with reconcile
the Add push button on the Add processing.
window.
User Response: Mark either or both check boxes.
Explanation: While you have just selected 'OK' in the
Advanced Feature dialog, the premigration percentage
ANS9895W Space management in file system file
is not activated until you select 'Add' or 'Update' in the
system is not active.
'Add space management', or the 'Update space
management' dialog. Explanation: You tried to select a file in a file system
for which space management is inactive.
System Action: TSM waits until you select 'Add' or
'Update' to apply your premigration percentage to the System Action: TSM continues with normal operation.
system.
User Response: When you have changed the space file system, and then proceed with selecting files.
management attribute, select 'Add' or 'Update', and
then the system will apply your new premigration
percentage. ANS9900E FSM kernel extension not installed.
Explanation: The file system selected is not fully
ANS9886W Enter a positive number for Column activated. The system received an error trying to open
Width. /dev/fsm.
Explanation: You have entered an invalid value for System Action: TSM operation stops.
Column Width. It must be a positive number between 0 User Response: Check to see whether /dev/fsm entry
and 18. exists, and check space management installation.
User Response: Enter a positive number between 0 ANS9901E Cannot migrate TSM system internal
and 18. file.
Explanation: You tried to select files that are used
ANS9887W Enter a positive number for Space internally by the HSM client. You cannot migrate TSM
Between Column. internal files.
Explanation: You have entered an invalid value for System Action: TSM ignores your request.
Space Between Column. It must be a positive number User Response: None.
between 0 and 18.
System Action: TSM continues with normal operation. ANS9903E Space management is deactivated for
User Response: Enter a positive number between 0 this file system.
and 18. Explanation: You tried to migrate a file in a file
system for which space management is inactive.
ANS9889W Space management has not been added System Action: TSM continues to migrate files only in
to file-system file system. Do you want to active file systems.
build the directory tree anyway?
Explanation: You selected a file system that is not file system, and retry the migration operation.
managed by HSM.
System Action: TSM builds the directory tree if you ANS9904E Transaction failed, migration aborted.
select the OK button. Otherwise, it will not.
Explanation: The specified file-name was not migrated
User Response: You can add space management to because the file was accessed by another process during
the file system by selecting the Space Manager push the attempt to migrate it.
button in the TSM main window, and then selecting
Add under the Selected menu option. System Action: TSM migration is aborted.

process that is accessing the file, and then retry the User Response: Select OK to return.
migration.
ANS9929I Space management has been reactivated
ANS9908E System Error. successfully on file-system file system.
Explanation: TSM detects an error in reading the state Explanation: Space management is reactivated
of the file system. successfully.
System Action: TSM proceeds with normal operation. System Action: TSM reactivated space management
User Response: Report the error to your system
administrator. User Response: Select OK to return.
ANS9909I Error in accessing migration candidates ANS9933I Migration candidates list only exists in
list file. an ’Active’ file system. If you want to
make file-system file system ’Active’,
Explanation: TSM detects an error in reading the
select ’Add Space Management’.
migration candidates list file. This file resides in the
.SpaceMan directory of the file system. Explanation: You tried to display the migration
candidates list for a “Native” file system (a file system
System Action: TSM proceeds with normal operation.
to which space management has not been added).
User Response: Report the error to your system
administrator.
User Response: Select OK to return. Select “Add
Space Management” if you want to add space
ANS9914I Space management settings have been
management to the file system.
modified successfully on file-system file
system.
ANS9934I Reconcile only works on an ’Active’ file
Explanation: Space management settings have been
system. If you want to make file-system
updated successfully.
file system ’Active’, select ’Add Space
System Action: TSM updated space management Management’.
settings for the file system.
Explanation: You tried to start reconciliation on a
User Response: Continue with normal operation. “Native” file system (a file system to which space
management has not been added). You must add space
management to a file system before starting reconcile.
ANS9915I Space management has been added
successfully to file-system file system. System Action: Processing stopped.
Explanation: Space management has been added User Response: Select OK to return. Select “Add” if
successfully. you want to add space management to the file system.
System Action: TSM added and activated space

management for the file system. ANS9935I Start Threshold Migration only works
on an ’Active’ file system. If you want
User Response: Continue with normal operation. to make file-system file system ’Active’,
select ’Add Space Management’.
ANS9918E Cannot open migration candidates list Explanation: You tried to start Threshold Migration on
for file-system. a “Native” file system (a file system to which space
Explanation: TSM cannot access the migration management has not been added). You must add space
candidates list for the specified file system. management to the file system first.
System Action: TSM continues normal operation. System Action: Processing stopped.
User Response: Select OK to return. User Response: Select OK to return. Select “Add” if
you want to add space management to the file system.
ANS9928I Space management has been deactivated

successfully on file-system file system.
Explanation: Space management is deactivated
successfully.
System Action: TSM deactivated space management

ANS9936I Start Threshold Migration only works
on an ’Active’ file system. If you want User Response: Select OK to return.
to make file-system file system ’Active’,
select ’Reactivate’.
ANS9944I Space management has been deactivated
Explanation: You tried to start Threshold Migration on on file-system file system. You must
an “Inactive” file system (a file system for which space reactivate space management before you
management has been deactivated). You must reactivate can remove it.
space management for your file system first.
Explanation: You tried to remove space management
System Action: Processing stopped. from a file system for which space management has
been deactivated. You must reactivate space
User Response: Select OK to return. Select 'Reactivate'
management for the file system before you can remove
to reactivate space management for the file system.
it.
ANS9938I Space management has not been added
to file-system file system. You do not User Response: Select OK to return. Select
need to deactivate space management. “Reactivate”, and then select “Remove” to remove
space management.
Explanation: You tried to deactivate space
management on a file system to which space
management has not been added. ANS9945I Space management has not been added
to file-system file system. You do not
need to remove space management.
User Response: Select OK to return.
Explanation: You tried to remove space management
from a file system to which space management has not
ANS9941I Space management has not been added been added.
to file-system. If you want to add space
management, select ’Add space
management’ option. The file system User Response: Select OK to return.
will automatically be activated when
you add space management.
ANS9947E File: file-spec is in a file system to which
Explanation: You tried to activate space management space management has not been added.
on a file system to which space management has not
been added. You must first add space management. Explanation: You tried to migrate a file that resides in
The file system will automatically be activated when a file system to which space management has not been
the add process is complete. added.
System Action: Processing stopped. System Action: TSM will not highlight/process the
file.
User Response: Select OK to return. Select “Add” if
you want to add space management to the file system. User Response: Switch over to the Space Manager
window, and add space management to the file system.
ANS9942S Space management has not been added

to file-system file system. Do you want to ANS9948E File: file-spec size is less than the
add space management now? minimum size required for migration.
Explanation: You tried to update space management Explanation: You tried to migrate a file that is smaller
settings for a file system to which space management than the minimum size required for migration. To be
has not been added. eligible for migration, a file must be larger than both
the stub file size specified for the file system plus one
System Action: Processing stopped. byte and the block size defined for the file system.
User Response: Select OK to add space management System Action: TSM will not highlight the file.
to the file system. Select Cancel to return.
ANS9943I Space management has already been

added to file-system file system. ANS9949E File: file-spec is not a regular file and
therefore not qualified for migration.
Explanation: You tried to add space management to a
file system to which space management has already Explanation: You tried to migrate a file that is not a
been added. regular file. It might be a FIFO file, a special file, a
directory or a symbolic link.

System Action: TSM will not highlight the file. User Response: Select the files that you want to
migrate or recall, and retry the operation.
ANS9961E Server out of migrate data storage space.

ANS9950E File: file-spec is not qualified for
migration because the Space Explanation: The server ran out of space in its migrate
Management Technique attribute is set data storage.
to None.
System Action: TSM cannot complete the migrate
Explanation: The Space Management Technique operation. Any files displayed in the Successful list of
attribute in the management class is set to None, which the Migrate Status window were successfully migrated.
does not allow a file to be migrated.
System Action: TSM will not highlight the file. administrator.
User Response: Assign a management class to the file
that specifies “Automatic” or “Selective” for the Space ANS9962I Migration stopped by user.
Management Technique attribute.
Explanation: You requested that TSM stop the migrate
operation.
ANS9951E File: file-name file has already been
System Action: Migration stopped.
migrated.
Explanation: You tried to migrate a file that is already
migrated.
ANS9963I Selective Recall completed. Check
System Action: TSM will not highlight the file.
failure list for possible errors.
Explanation: The recall was completed.
System Action: TSM recalled the files.
ANS9953E The management class assigned to this
file does not allow migration. User Response: Continue with normal operations.
Explanation: The management class assigned to this
file does not allow migration. ANS9964I Selective Migration completed. Check
failure list for possible errors.
System Action: TSM does not migrate the file.
Explanation: The migration was completed.
System Action: TSM migrated the files.
ANS9954E This file has already been migrated. User Response: Continue with normal operations.
Explanation: The file has been previously migrated.
ANS9965S Please select a file system first.
Explanation: You did not select any file system for the
Migrate window.
System Action: TSM ignores this request and
ANS9958E File ’file-namefile-namefile-name has not yet
continues.
reached the age for migration. File
skipped. User Response: Select a file system, a directory, and
all files you want to migrate, and then select the
Explanation: This file cannot be migrated because it
Migrate button to start the process.
has not yet reached the age for migration.
System Action: TSM will not highlight the file.
ANS9966S No file system has been selected.
Explanation: You did not select a file system.
System Action: TSM ignores the request and
ANS9960W No files selected for migrate or recall.
continues.
Explanation: You requested a migrate or recall
User Response: Select at least one file system and
operation without selecting files from the presented
retry the operation
directory tree.
System Action: TSM cannot do the migration or recall
without selected files.

this message can not be determined or resolved, contact
ANS9988S As part of the remove process, all
your support representative. If you contact your
migrated files in file-system will be
recalled from TSM server. Do you want
should be reported.
to continue with the remove process
now?
ANS13401W The volume name is invalid.
Explanation: When you remove space management
from a file system, TSM recalls all migrated files. Explanation: A volume with this name could not be
found or is not suitable for server-free operations.
System Action: TSM waits for your response before
proceeding with the remove process. System Action: Processing stopped.
User Response: Select Yes to remove space User Response: Specify the correct name.
management from the selected file system, or select
Cancel to skip the remove.
ANS13402W name: MS API function func failed with
code rc.
ANS9997W The selective migration, selective recall,
or policy information window is Explanation: Failed to get volume information.
displayed. Stop any operations, close the System Action:
window, and then retry the operation.
User Response: Contact your system administrator or
Explanation: When a node is contacting more than TSM administrator.
one server for space management services, the selective
migration, selective recall, and policy information
windows may not be displayed at the same time. ANS13403W Cannot open the volume name for
reading. System error code err.
Explanation: The volume could not be opened for
User Response: Close the selective migration, selective reading.
recall, or policy information window, and then retry the
operation. System Action:
ANS9998E The migration server changed after the
selective migration or selective recall ANS13404W Error reading the volume name.
window was displayed. Close the
window, and then retry the operation. Explanation: The volume could not be read.
Explanation: A migrate or recall operation will not be System Action:

allowed to proceed if the user changed the migration User Response: Contact your system administrator.
server after the selective migration or selective recall
window was displayed.
ANS13405W Unknown filesystem fs on volume name.
System Action: No files will be migrated or recalled.
Explanation: The filesystem found on the volume is
User Response: Close the selective migration or not recognized.
selective recall window, and then retry the operation.
ANS9999E (): User Response: Contact your systems administrator.
Explanation: This message carries diagnostic text
relating to a client process or algorithm. This ANS13406W Physical mapping of the volume name is
information is intended for reporting processing not supported.
exceptions and other non-standard situations that occur
Explanation: The logical volume layout is not
on the TSM client. The (component), (code), and (text)
currently supported for physical mapping.
will vary depending upon the cause of the message
and the client process or algorithm that issues the System Action:
message.
User Response: Refer to the documentation for
System Action: Client processing may or may not information on what volume layouts are supported for
continue depending upon the cause of this message. physical mapping.
have been displayed before and/or after this message
and correct any problems, if possible. If the cause of

ANS13407W name is not local.
Explanation: The drive or filesystem is not local and is
not suitable for image backup.
User Response: Specify a volume that is local.
ANS13408W The volume name contains bad blocks.

Explanation: The volume contains bad blocks and is
not suitable for server-free operations.
System Action: Processing continues using
non-server-free data movement.

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

Part 4. Tivoli Data Protection Products Messages
This section contains messages for the following Tivoli Data Protection products:
v Tivoli Data Protection for Lotus Domino
v Tivoli Data Protection for Microsoft Exchange Server
v Tivoli Data Protection for Microsoft SQL Server
v Tivoli Data Protection for Oracle
v Tivoli Data Protection for R/3
v Tivoli Data Protection for R/3 for DB/2
v Tivoli Data Protection for R/3 for Oracle
v Tivoli Data Protection for EMC Symmetrix for R/3
v Tivoli Data Protection for IBM ESS for R/3
v Tivoli Data Protection for WebSphere Application Server
Note: The TDP for Lotus Notes messages have a prefix that is common with
administrative clients, API clients, backup–archive clients, and HSM clients.
See Part III for a listing of those messages.
Each of the Tivoli Data Protection products in this section has a unique prefix or
numeric range for its messages. The prefix (and numeric range) that corresponds to
each Tivoli Data Protection product is as follows:
ACD (0000–9999)
TDP for Lotus Domino
ACN (0000–9999)
TDP for Microsoft Exchange Server
ACO (0000–9999)
TDP for Microsoft SQL Server
ANU (0000–9999)
TDP for Oracle
BKI (0000–9999)
TDP for R/3, TDP for R/3 for DB/2, TDP for R/3 for Oracle
IDS (0000–0999)
TDP for EMC Symmetrix for R/3
IDS (1000–1999)
TDP for ESS for R/3
DKP (0000–0999)
TDP for WebSphere Application Server
For each Tivoli Data Protection product, the messages are listed in numeric order.
This section also contains Diagnosis, Modification, or Tuning Information. Some of

these messages include information about the TSM error log that you can use
when working with your service representative.

Chapter 5. Tivoli Data Protection for Lotus Domino
(ACD0000–ACD9999)
This chapter describes the messages issued by Tivoli Data Protection for Lotus
Domino, Version 1.1.2. The messages begin with the prefix ACD and are listed in
numerical order.
ACD0003S An internal processing error has ACD0055E Write failure on license file (licensefile).
occurred.
Explanation: An attempt was made to write to the
Explanation: An internal processing error has license file. This attempt failed.
occurred.
User Response: Be sure that there is enough space on
User Response: Retry the operation. If this error the workstation to write the file. If there is, try running
persists, contact your service representative. the command again.
ACD0004E An unknown error has been detected. ACD0056E Data in the license file (licensefile) is not
in a valid format.
Explanation: An internal processing error has
occurred that prevents the generation of a message for Explanation: An attempt was made to read
a return code. information from the license file. This attempt failed.
System Action: Processing continues. System Action: Processing ends.
User Response: Retry the operation. If this error User Response: Reinstall the product.
ACD0057E The checksum in the license file
ACD0005E Out of memory. Stop other processes (licensefile) does not match the license
and retry the operation. string text.
Explanation: The machine has run out of memory. Explanation: An attempt was made to read
information from the license file. The checksum was
not valid so it appears that the license file is not at the
User Response: Free up some system memory and correct level.
User Response: Reinstall the product.
ACD0053E License file (licensefile) could not be
opened.
ACD0058E The ’Try and Buy’ license has expired.
Explanation: An attempt was made to read from the
license file. This attempt failed. Explanation: This is an error message that indicates
that the ’Try and Buy’ license that was detected has
expired.
User Response: Reinstall the product. This will ensure
that the correct license file is installed.
User Response: This product is no longer valid for
use. A valid license must be obtained before running
ACD0054E Read failure on license file (licensefile).
the product.
license file. This attempt failed.
ACD0100E Incomplete command:
Explanation: This message displays the incomplete
User Response: Reinstall the product. This will ensure command that was entered.
User Response: Re-enter the complete command.

ACD0101E • ACD0132W
ACD0101E Invalid argument: ACD0107E This command requires one of the

following options:
Explanation: This message displays the command that
was entered, up to and including the invalid command Explanation: This message displays the options that
or option argument that was detected. were missing from the command entered.
System Action: Processing ends. System Action: Processing ends.
User Response: Re-enter the command specifying a User Response: Re-enter the command specifying one
valid argument for the command or option. of the command options required by the command.
ACD0102E Invalid command: ACD0108E Multiple dbnames are not allowed.

Explanation: This message displays the invalid Explanation: A Restore command was issued and
command that was entered. either multiple dbnames were specified for the dbname
positional parameter into, relocate or to options or a
wildcard character was part of the specified dbname,
User Response: Re-enter a valid command. into, relocate or to option.
ACD0103E Invalid option for the specified
User Response: Re-enter the command either
command:
specifying a single value for the positional parameter or
Explanation: This message displays the command that option in error.
was entered, up to and including the option that was
detected as invalid for the command.
ACD0109E Equal numbers of the relocate and to
System Action: Processing ends. options must be specified.
User Response: Re-enter the command specifying Explanation: Unequal numbers of the relocate and to
valid command options. options were specified on a restore command.
ACD0104E Invalid option:
User Response: Re-enter the command specifying the
Explanation: This message displays the command that same number of relocate and to options.
was entered, up to and including the invalid option
that was detected.
ACD0110E Wildcards are not allowed as part of the
System Action: Processing ends. following parameters/options:
User Response: Re-enter the command specifying Explanation: This message displays the positional
valid command options. parameters and/or options that were specified
incorrectly.
ACD0105E Missing argument: System Action: Processing ends.
Explanation: This message displays the command that User Response: Re-enter the command specifying the
was entered, up to and including the command or correct parameters and/or options.
option whose required argument is missing.
System Action: Processing ends. ACD0132W Tracing could not be started. Processing
will continue.
User Response: Re-enter the command specifying a
valid argument for the command or option. Explanation: There was a problem trying to begin
tracing.
ACD0106E The following options cannot be System Action: Processing will continue with the
specified together: command entered.
Explanation: This message displays the conflicting User Response: There should be other messages along
command options that were entered. with this one. Refer to the other messages to determine
the problem.
User Response: Re-enter the command specifying
valid command options.

ACD0133W • ACD0156E
ACD0133W Could not locate installation directory. ACD0153I Performance stats: seconds seconds spent
Attempting to continue... in function
Explanation: An attempt was made to read the Explanation: The indicated number of seconds were
registry to determine where the Tivoli Data Protection spent the named function.
application client was installed. This attempt failed.
System Action: Processing will continue with the
User Response: None
command entered.
User Response: There should be other messages along
ACD0154E The Tivoli Data Protection application
with this one. Refer to the other messages to determine
client cannot work with the version of
the problem. If the problem can not be determined, it
the Tivoli Storage Manager API you
may be necessary to reinstall the application client
have installed. Please install version
code. This will ensure that the registry entries are set
version.release.level or greater.
up correctly.
Explanation: The version of the Tivoli Storage
Manager API currently installed on the system is older
ACD0134W Could not locate log directory.
than the version used to build the Tivoli Data
Processing will continue...
Protection application client.
Explanation: An attempt was made to read the
registry to determine where the Tivoli Data Protection
application client log is located. This attempt failed. User Response: Install a version of the Tivoli Storage
Manager API at or later than the indicated level. A
copy is distributed with the Tivoli Data Protection
command entered.
application client.
ACD0155E The Tivoli Data Protection application
client cannot work with the release of
Tivoli Storage Manager API you have
installed. Please install release
up correctly.
Explanation: The release of the Tivoli Storage
ACD0150I Operation canceled by user.
Explanation: The user has requested that the Tivoli than the release used to build the Tivoli Data Protection
Data Protection application client end by entering application client.
ctrl-C.
User Response: Install a release of the Tivoli Storage
User Response: None Manager API at or later than the indicated level. A
application client.
ACD0151E Errors occurred while processing the
request.
ACD0156E Could not load the Tivoli Storage
Explanation: Attempting to process the request
Manager API.
entered, an error occurred.
Explanation: The Tivoli Storage Manager API could
not be loaded.
User Response: Attempt to determine the source of
the errors from viewing the log file. Correct the
problems and try running the command again. User Response: Ensure the Tivoli Storage Manager
API is correctly installed. Run the Tivoli Data
Protection application client with the
ACD0152I Performance stats: seconds seconds spent
/TRACEFLAGS=API /TRACEFILE=filename options
in apicall API calls
and view the tracefile to determine why it could not be
Explanation: The indicated number of seconds were loaded. Another possible cause is that the TSMAPI.DLL
spent making API calls for the indicated system. does not exist in the system directory. Re-install the
Tivoli Storage Manager API, if this is the case.
User Response: None
Chapter 5. Tivoli Data Protection for Lotus Domino 657

ACD0160E • ACD0207E
ACD0160E An authentication error occurred with ACD0201E File (filename) could not be opened for
your stored Tivoli Storage Manager writing.
password.
Explanation: An attempt was made to open a file for
Explanation: You were unable to log on to the Tivoli writing. This attempt failed.
Storage Manager server due an authentication error.
User Response: None
User Response: The stored Tivoli Storage Manager
password may have become corrupted. Contact your
ACD0202E Read failure on file (filename).
Tivoli Storage Manager server administrator.
Explanation: An attempt was made to read from a
file. This attempt failed.
ACD0161E Authentication error. The password
entered is not valid. You are not logged System Action: Processing ends.
on to the Tivoli Storage Manager server.
User Response: None
Explanation: An incorrect password was entered.
System Action: Processing stops. ACD0203E Write failure on file (filename).
User Response: Enter the correct Tivoli Storage Explanation: An attempt was made to write to a file.
Manager password and try again. This attempt failed.
ACD0162E The passwords entered do not match.
Please enter them again. User Response: None

ACD0204E File (filename) could not be closed.
Explanation: An attempt was made to close a file.
User Response: Enter the passwords again. This attempt failed.
ACD0163E The directory path needs to be
fully-qualified. User Response: None
Explanation: The /intopath option was specified.

However, this path needs to be fully-qualified. ACD0205E File (filename) statistics could not be
obtained.
Explanation: An attempt was made to obtain file
User Response: Re-enter the command again giving a statistics. This attempt failed.
fully-qualified /intopath.
ACD0167E The fully-qualified file name is too User Response: None

long.
Explanation: An attempt was made to use a ACD0206E Directory (directory) could not be created.
fully-qualified file name that was too long. This Explanation: An attempt was made to create a
attempt failed. directory. This attempt failed.
ACD0200E File (filename) could not be opened for ACD0207E Directory path (directorypath) is too long.
reading.
Explanation: An attempt was made to use a directory
Explanation: An attempt was made to open a file for path that was too long. This attempt failed.
reading. This attempt failed.
User Response: None
User Response: None

User Response: Increase the maximum number of
ACD0208E There is not enough disk space for the
objects allowed per transaction on the Tivoli Storage
operation attempted.
Manager server and retry the operation.
Explanation: An attempted operation required more
disk space than was available. The attempt failed.
ACD0214E The backup object’s management class
System Action: Processing ends. backup copy group does not exist.
User Response: None Explanation: The Tivoli Storage Manager server has
indicated that the backup object’s management class
backup copy group does not exist.
ACD0209E The rename of file (filename1) to
(filename2) failed. System Action: Processing ends.
Explanation: An attempt was made to rename a file. User Response: Contact your Tivoli Storage Manager
This attempt failed. server administrator.
ACD0215E All backup objects do not have the same
User Response: None
management class backup copy
destination.
ACD0210E The Tivoli Storage Manager high level
Explanation: In order to maintain backup data
qualifier is too long.
integrity, multiple backup objects are sent to the Tivoli
Explanation: An attempt was made to use a Tivoli Storage Manager server within a single transaction. All
Storage Manager high level qualifier that was too long. backup objects within a single transaction are required
This attempt failed. to have the same management class backup copy
destinations.
User Response: None
User Response: Contact your Tivoli Storage Manager
server administrator.
ACD0211E The Tivoli Storage Manager low level
ACD0216E Unable to obtain space information for
Explanation: An attempt was made to use a Tivoli volume (volumename).
Storage Manager low level qualifier that was too long.
This attempt failed. Explanation: An attempt was made to obtain space
information for a volume. This attempt failed.
User Response: None
User Response: None
ACD0212E The Tivoli Storage Manager filespace
name is too long. ACD0217E The Tivoli Storage Manager filespace
name is invalid.
Explanation: An attempt was made to use a Tivoli
Storage Manager filespace name that was too long. This System Action: Processing ends.
attempt failed.
User Response: None ACD0218E The Tivoli Storage Manager high level
qualifier is invalid.
ACD0213E The maximum number of objects System Action: Processing ends.
allowed per Tivoli Storage Manager
transaction is too small.
ACD0219E The Tivoli Storage Manager low level
Storage Manager server in a single transaction. The
Tivoli Storage Manager server has indicated that the System Action: Processing ends.
maximum number of objects allowed per transaction is
less than the minimum required by the Tivoli Data

ACD0256E The password in your Tivoli Storage ACD0261I There are no backups for the server
Manager options file has expired. Please named servername.
change your password on the Tivoli
Explanation: There are no backups on the Tivoli
Storage Manager server using the
Storage Manager server for the specified server name.
’change password’ command and then
either change or remove the password System Action: Processing ends.
value in your options file.
User Response: None
Explanation: Your Tivoli Storage Manager password
has expired. You need to change your password.
ACD0263E Failed to start Web browser with a
System Action: Processing ends. return code of returncode.
User Response: Obtain a new password for your Explanation: An attempt was made to start the web
Tivoli Storage Manager node using the change browser to view the TSM HTML book. This attempt
password command or by asking your Tivoli Storage failed.
Manager Administrator to change your password.
ACD0257E Your password has expired. User Response: Start your web browser manually and
point it to bookfrm.htm in the agent htm directory.
has expired. A new password needs to be obtained.
ACD0264I Could not find the default browser
System Action: Processing ends. defined. An attempt will be made to use
Microsoft’s Internet Explorer.
User Response: Obtain a new password for your
Tivoli Storage Manager node using the change Explanation: An attempt was made to read the
password command or by asking your Tivoli Storage registry to determine the default browser. However,
Manager Administrator to change your password. there was not one defined. It will be determined where
Microsoft Internet Explorer is installed.
ACD0258E You did not enter a valid password. System Action: Processing continues.
Processing ends.
User Response: It is possible that a default browser is
Explanation: The password that was entered was not not defined for the system. This is okay. An attempt
a valid password. will be made to use Microsoft’s Internet Explorer.
ACD0265E Could not find Internet Explorer.
valid password. Explanation: An attempt was made to read the
registry to determine where Microsoft’s Internet
Explorer was installed. This attempt failed.
ACD0259E The password you entered for
verification does not match the System Action: Processing ends.
password you entered for your new
password. Your password will not be User Response: Make sure that the registry is set up
changed. correctly for Internet Explorer.
Explanation: The password you entered for

verification of your new password does not match the ACD0266E Could not find the Tivoli Storage
new password that was entered. Manager HTML books.
System Action: Processing ends. Explanation: An attempt was made to read the
registry to determine where the Tivoli Storage Manager
User Response: Try again to change your password books were installed. This attempt failed.
being sure to enter the same password for the new
password and for the verification password. System Action: Processing ends.
User Response: It may be necessary to reinstall the
ACD0260I Password successfully changed. application client code. This will ensure that the
registry entries are set up correctly.
Explanation: The change password command
completed successfully
User Response: None

ACD0267E The verify password entered does not ACD0262I There are no backups matching the
match the new password entered. filespec directorypathfilename and the
server name servername.
Explanation: The verify password does not match the
new password. Explanation: There are no database backups on the
Tivoli Storage Manager server for the specified server
name.
User Response: Retry the command with a matching
verify password.
User Response: None
ACD0300E Invalid restore type.
ACD5022I A new configuration file has been
Explanation: The type of restore requested is invalid.
created.
Explanation: The /configfile value specified a file
User Response: Re-enter the command specifying a name that didn’t already exist. A new file has been
valid restore type. created.
ACD0301E Invalid backup type.
Explanation: The type of backup requested is invalid.
System Action: Processing ends. ACD5023W The configuration file cannot be found,
using default settings.
valid backup type. Explanation: The /configfile value specified a file that
can’t be found so default settings are being used.
ACD0302E A failure occurred on stripe number System Action: Processing continues.
(stripe number), rc = return code
User Response: Ensure the file name intended is
Explanation: A failure occurred on the numbered specified then re-enter the command.
stripe.
System Action: Processing ends. ACD5110E Could not locate the Domino server
configuration file (notes.ini).
with this one. Refer to the other messages to determine Explanation: The Tivoli Data Protection application
the problem. client could not find the Domino server configuration
file (notes.ini) file.
ACD0255E PASSWORDACCESS is Generate. Either System Action: Processing ends.

the stored password is incorrect or there
User Response: Ensure that the ’notes.ini’ file is in the
is no stored password. If you do not
PATH or that the ’NOTESInipath’ configuration
have a stored password, use of the
parameter is correct.
-ADSMPWD=xxx option will set and
store your password.
ACD5111E Error getting the name of the Domino
Explanation: The client options file has the
data directory.
PASSWORDACCESS option set to generate. Currently,
there is no password that has been stored. An initial Explanation: The Lotus Domino API could not return
password needs to be stored. the name of the Domino data directory.
User Response: Invoke the command again using the User Response: Ensure the Lotus Domino server is
-ADSMPWD option. Any subsequent commands installed correctly.
should now complete without specifying a password.
ACD5115E No databases were found that match the
file specification entered.
Explanation: The Lotus Domino Server was searched
for databases that matched the file specification
enetered. No databases were found.

ACD5128E • ACD5206I
User Response: Correct the file specification and retry System Action: None
the operation.
User Response: None Centrally logged
ACD5128E The user specified NotesIniPath does

ACD5202E TDP for Lotus Domino: Backup of
not exist. Verify that the path setup for
database database from server servername
the NotesIniPath preference really
failed.
exists.
Explanation: This is an informational message that is
Explanation: The Tivoli Data Protection for Lotus
written to the Tivoli Storage Manager Server activity
Domino application client could not find the specified
log when a database backup fails.
NotesIniPath.
System Action: None
User Response: Ensure that the NotesIniPath is
correctly entered in the preferences file. This can be
done by issuing the ’DOMDSMC QUERY ACD5203I TDP for Lotus Domino: Starting archive
PREFERENCES’ command. of transaction log file transactionlog from
server servername.
ACD5129E The Lotus Domino Server program Explanation: This is an informational message that is
executable directory was not found. written to the Tivoli Storage Manager Server activity
log when a transaction log file archive is started.
client could not find the Lotus Domino Server program System Action: None
executable directory.
User Response: Ensure that the Lotus Domino Server ACD5204I TDP for Lotus Domino: Archive of
program executable directory is in the PATH and retry transaction log file transactionlog from
the operation. server servername completed successfully.
ACD5130E Could not initialize the connection to written to the Tivoli Storage Manager Server activity
Lotus Domino properly. error=errorcode log when a transaction log file archive completes
successfully.
client could not initialize Lotus Domino properly. The System Action: None
error code is given.
User Response: Ensure that Tivoli Data Protection ACD5205E TDP for Lotus Domino: Archive of
application client and Lotus Domino Server were transaction log file transactionlog from
installed properly and retry the operation. server servername failed.
ACD5200I TDP for Lotus Domino: Starting backup written to the Tivoli Storage Manager Server activity
of database database from server log when a transaction log file archive fails.
servername.
System Action: None
written to the Tivoli Storage Manager Server activity User Response: None Centrally logged
log when a database backup is started.
System Action: None ACD5206I TDP for Lotus Domino: Starting
incremental database backup from
User Response: None Centrally logged server servername.
ACD5201I TDP for Lotus Domino: Backup of written to the Tivoli Storage Manager Server activity
database database from server servername log when an incremental backup is started.
System Action: None
written to the Tivoli Storage Manager Server activity User Response: None Centrally logged
log when a database backup completes successfully.

ACD5207I • ACD5217I
ACD5207I TDP for Lotus Domino: Incremental
database backup from server servername
complete. Total Domino databases ACD5212I TDP for Lotus Domino: Starting restore
backed up: numberdbs Total bytes for server servername.
transferred: bytes Elapsed processing
time: time Secs Throughput rate: rate Explanation: This is an informational message that is
Kb/Sec written to the Tivoli Storage Manager Server activity
log when a restore is started.
written to the Tivoli Storage Manager Server activity System Action: None
log when an incremental backup ends. User Response: None Centrally logged
System Action: None
User Response: None Centrally logged ACD5213I TDP for Lotus Domino: Restore
database from server servername to server
servername complete. Total Domino
ACD5208I TDP for Lotus Domino: Starting databases restored: numberdbs Total bytes
selective database backup from server transferred: bytes Elapsed processing
servername. time: time Secs Throughput rate: rate
Kb/Sec
written to the Tivoli Storage Manager Server activity Explanation: This is an informational message that is
log when a selective backup is started. written to the Tivoli Storage Manager Server activity
log when a restore ends.
System Action: None
System Action: None
ACD5209I TDP for Lotus Domino: Selective
database backup from server servername ACD5215E An error occurred trying to set the
complete. Total Domino databases requested preference.
backed up: numberdbs Total bytes
transferred: bytes Elapsed processing Explanation: An error occurred while writing to the
time: time Secs Throughput rate: rate preferences file.
Kb/Sec System Action: Processing ends.
Explanation: This is an informational message that is User Response: View any other messages that were
written to the Tivoli Storage Manager Server activity displayed. After reviewing the messages and fixing any
log when a selective backup ends. of the problems indicated, try running the command
System Action: None again.

ACD5216E The value for the preference preference is
not valid. See the DOMDSMC HELP
ACD5210I TDP for Lotus Domino: Starting SET output or the User’s Guide for
transaction log archive from server valid SET command parameters.
servername.
Explanation: The preference being set is not valid.
written to the Tivoli Storage Manager Server activity System Action: Processing ends.
log when a transaction log archive is started. User Response: Run ″domdsmc help set″ or look at
System Action: None the User’s Guide for valid SET command parameters.

ACD5217I The preference has been set
successfully.
ACD5211I Transaction log archive from server
servername complete Explanation: The preference was set successfully.
Explanation: This is an informational message that is System Action: Processing ends.

written to the Tivoli Storage Manager Server activity User Response: None
log when a transaction log archive ends.
System Action: None

ACD5218E The Lotus Domino API could not be ACD5224E Could not obtain the current pending
loaded. Could not load the nnotes.dll database list. The pending database list
was not available.
Explanation: The Lotus Domino Api, nnotes.dll, could
not be loaded. Explanation: The pending database list could not be
read because the pending database list was in use at
the time or the permissions did not allow access.
User Response: Ensure that the Lotus Domino Server
has been correctly installed.
User Response: Retry the operation. If the error
continues, contact your service representative.
ACD5220I The logfile log file could not be pruned.
Processing will continue.
ACD5225E Unknown Domino API error code
Explanation: An attempt was made to prune the log.
received: returncode
This attempt was unsuccessful.
Explanation: An unknown Domino API error code
was received. The error code is specified in the text of
User Response: It could be that the log file does not the message.
exist. If this is not the case, view the log for indications
of what the problems may be.
continues, contact your service representative.
ACD5221I The logfile log file has been pruned
successfully.
ACD5226W The logfile log file cannot be opened for
Explanation: The log mentioned pruned successfully.
writing. There will be no logging of
System Action: Processing continues. events.
User Response: None. Explanation: The log mentioned could not be opened
for append. Therefore, there will be no logging done.
ACD5222W The logfile name is greater than the System Action: Processing continues without logging.
maximum allowed. Processing will
User Response: Determine why the log could not be
continue using a logfile name of logfile
opened. It could be that the log file is going to a
in the current directory.
non-existent drive or partition. Or, that the file is
Explanation: The logfile name entered was not fully read-only and cannot be written to.
qualified. When the fully qualified logfile name was
created, it was longer than the possible length of a
ACD5227W The logfile log file cannot be opened for
logfile.
writing. The log was not pruned and
System Action: Processing continues creating and there will be no logging of events.
using a logfile in the current directory.
Explanation: The log mentioned could not be opened
User Response: You may want to consider updating for append. Therefore, there will be no logging done
the logfile name using a fully qualified path. and the request to prune now was not done.
System Action: Processing continues without logging
ACD5223E The database could not be placed into and without pruning.
pending state. The pending database list
was in use.
Explanation: The database could not be placed into non-existent drive or partition. Or, that the file is
pending state because the pending database list was in read-only and cannot be written to.
use at the time or the permissions did not allow access.
System Action: The database was not restored ACD5228I TDP for Lotus Domino: Starting restore
correctly and is not usable. of database database to database on server
servername.
User Response: Retry the restore of the database that
failed. If the error continues, contact your service Explanation: This is an informational message that is
representative. written to the Tivoli Storage Manager Server activity
log when a database restore is started.
System Action: None

ACD5229I • ACD5238I
User Response: None Centrally logged User Response: None Centrally logged
ACD5229I TDP for Lotus Domino: Restore of ACD5234I TDP for Lotus Domino: Inactivation of
database database to server servername transactionlog transaction log archive
completed successfully. succeeded.
Explanation: This is an informational message that is Explanation: This is an informational message that is
written to the Tivoli Storage Manager Server activity written to the Tivoli Storage Manager Server activity
log when a database restore completes successfully. log when an inactivation of a transaction log file
archive succeeds.
System Action: None
System Action: None
ACD5230E TDP for Lotus Domino: Restore of
database database to server servername ACD5235I TDP for Lotus Domino: Starting
failed. inactivation of transaction log archive
transactionlog.
log when a database restore fails. written to the Tivoli Storage Manager Server activity
log when an inactivation of a transaction log file
System Action: None
archive is started.
System Action: None
ACD5231I TDP for Lotus Domino: Starting
inactivation of transaction log archives
for server servername. ACD5236I TDP for Lotus Domino: Starting restore
of transaction log files for server
servername.
log when an inactivation of transaction log file archives Explanation: This is an informational message that is
starts. written to the Tivoli Storage Manager Server activity
log when a restore of transaction log files is started.
System Action: None
System Action: None
ACD5232I TDP for Lotus Domino: Ending
inactivation of transaction log archives ACD5237I TDP for Lotus Domino: Restore of log
for server servername. There were files for server servername complete.
numberlogs transaction log archives Total Domino log files restored:
inactivated. numberlogs Total bytes transferred: bytes
Elapsed processing time: time Secs
log when an inactivation of transaction log file archives written to the Tivoli Storage Manager Server activity
ends. log when a restore of transaction log files ends.
ACD5233E TDP for Lotus Domino: Inactivation of ACD5238I TDP for Lotus Domino: Starting restore
transactionlog transaction log archive of transaction log file transactionlog for
failed. server servername.
log when an inactivation of a transaction log file log when a restore of a transaction log file is started.
archive fails.
System Action: None
System Action: None

ACD5239E TDP for Lotus Domino: Restore of ACD5332E No transaction log file archives were
transaction log file transactionlog failed. found that match the file specification
entered.
written to the Tivoli Storage Manager Server activity Explanation: The Tivoli Storage Manager Server was
log when a restore of a transaction log file fails. searched for transaction log file archives that matched
the file specification enetered. No transaction log file
System Action: None
archives were found.
User Response: Correct the file specification and retry
ACD5240I TDP for Lotus Domino: Restore of log
the operation.
file transactionlog succeeded.
ACD5335I No Transaction Log Files match the
following file spec(s): filespec
log when a restore of a transaction log file succeeds.
Explanation: The TSM API could not find any
System Action: None
transaction log extents that match this file specification
User Response: None Centrally logged entered by the user.
System Action: The file spec is ignored.
ACD5242I TDP for Lotus Domino: Restore of
User Response: Check for a misspelled file spec and
transaction log files for server servername
re-enter command.
complete. Total Domino transaction log
files restored: numberlogs Total bytes
transferred: bytes Elapsed processing ACD5404E There is no keyfilename or
time: time Secs Throughput rate: rate serverKeyfilename entry in the notes.ini
Kb/Sec file
Explanation: This is an informational message that is Explanation: We could not find the name of the Lotus
written to the Tivoli Storage Manager Server activity Domino Server id file in notes.ini.
log when a restore of transaction log files ends.
System Action: None
User Response: Ensure the Lotus Domino Server is
User Response: None Centrally logged correctly installed.
ACD5243E Transaction log files to be restored span ACD5405E There is no server name in the Lotus
multiple log identifiers. Domino Server id file
Explanation: All transaction log files to be restored Explanation: We could not find the name of the Lotus
must have the same log identifier. Domino Server in the id file.
User Response: Re-enter a seperate command for each User Response: Ensure the Lotus Domino Server is
set of transaction log files that corresponds to a unique correctly installed.
log identifier.
ACD5406E The directory directory does not exist
ACD5327I No databases match the following file
Explanation: We could not find the directory
spec(s): filespec
specified.
Explanation: The Domino API could not find any
databases that match this file specification entered by
the user. User Response: Ensure the directory exists and retry
the command.
System Action: The file spec is ignored.
User Response: Check for a misspelled file spec and
ACD5407E The database database does not exist
re-enter command.
Explanation: We could not find the database specified.

User Response: Ensure the database exists and retry
ACD5612E Unable to create or write to the file.
the command.
Domino return code: returncode.
Explanation: An attempt was made to create a file on
ACD5408E The NotesInitExtended api failed with a
the Domino server. This attempt failed.
return code of returncode. The error
message text for this is not available. System Action: Processing ends.
Explanation: Notes initialization failed with the User Response: Determine and fix the problem.
indicated return code.
System Action: Processing ends. ACD5613E You can only archive logs on a Domino
Server with archival logging on.
User Response: Ensure the Lotus Domino Server is
Domino return code: returncode.
installed properly.
Explanation: An attempt was made to archive logs on
a Domino Server that is not running archival logging.
ACD5412W An error was encountered with Tivoli
Storage Manager API initialization, rc = System Action: Processing ends.
returncode. Examine the dsierror.log for
User Response: This operation cannot be performed
more information or determine if the
until archival logging is turned on for the Domino
TSM API is installed properly.
server.
Explanation: An attempt was made to run setup for
the Tivoli Storage Manager API. However, errors were
ACD5614E The Domino Server is not running with
encountered.
logging on. You cannot applylogs.
System Action: Processing continues. Domino return code: returncode.
User Response: Examine the dsierror.log file to Explanation: An attempt was made to restore a
determine the problem. If this file does not exist, it is database and applylogs to this database. However,
possible that the TSM API is not installed properly. If logging has not been turned on for your Domino
this is the case, reinstall the TSM API and try running server.
the command again.
ACD5418I There are no databases pending
until logging is turned on for your Domino server.
activation.
Explanation: A query was issued to look at the
ACD5615E You cannot archive a Domino Log file
databases that are pending activation. There are none.
when logging is turned off. Domino
System Action: Processing ends. return code: returncode.
User Response: None Explanation: An attempt was made to archive a
Domino Log file. However, logging is not turned on for
your Domino server.
ACD5420E File filename is not a database.
Explanation: The specified file is not a database.
until logging is turned on for your Domino server.
User Response: Retry the operation, specifing a valid
database name.
ACD5700E The database file name is to be
generated from path (path) and filename
ACD5551E Screen size is too small for using the (filename) is too long.
PICK option.
Explanation: The database file name to be generated
Explanation: You cannot use the PICK option on a is too long.
workstation that has a screen smaller than 20 characters
across and 10 lines down.
User Response: Re-enter the command, using the
System Action: The operation was not completed.
INTO option to specify an alternate destination file
User Response: Retry the operation using a name.
workstation that has a screen with the minimum size,
or do not use the PICK option.

the database is activated without applying any
ACD5701E A Tivoli Storage Manager API error has
transaction log file(s).
occurred.
Explanation: A Tivoli Storage Manager API api error
has occurred.
ACD5709E The domino environment variable
(environmentvariable) is missing or
User Response: Retry the operation. If the error invalid. Threshold criteria will be based
persists, contact your service representative. upon all available disk space on the log
volume.
ACD5702E A Domino api error has occured. System Action: Processing continues with thresholds
based upon all available transaction log disk space.
Explanation: A Domino api error has occured.
User Response: (Re)define the domino environment
variable, specifing a valid value and retry the
User Response: Retry the operation. If the error operation.
ACD5710E The domino environment variable
ACD5703E The specified point-in-time is invalid. (environmentvariable) is missing or
invalid. The destination path can not be
Explanation: The specified point-in-time is invalid. determined.
User Response: Retry the operation, specifing a User Response: (Re)define the domino environment
properly formatted point-in-time. variable, specifing a valid value, or use the /INTOPath
option to specify the destination path and retry the
ACD5704E The requested transaction log file operation.
archive was not found: Destination:
destination Logger Id : ACD5740E Unable to load the Tivoli Data
OFlogid1:logid2-ONlogid3:logid4 Log Protection for Lotus Domino DLL,
Number : lognumber dll_name.
Explanation: The Lotus Domino api that recovers Explanation: Unable to load the dll containing the
databases from the transaction log has requested a resources for the Tivoli Data Protection for Lotus
transaction log file archive that was not found on the Domino GUI.
Tivoli Storage Manager Server.
User Response: Ensure that Tivoli Data Protection for
User Response: Verify that the transaction log file Lotus Domino has been correctly installed.
archive is on the Tivoli Storage Manager Server. If it is
not, it is possible that you will need to activate your
databases without applying logs. ACD5741E Error writing option_name preference to
the configuration file.
ACD5707E The high level qualifier of the Explanation: Could not write the specified preference
transaction log file archive is invalid. to the configuration file.
Explanation: The high level qualifier of a transaction System Action: Preferences processing ends.
log file archive was determined to be invalid.
User Response: Make sure you have a valid
System Action: Processing ends. configuration file, then try to update the preference
again.
ACD5742I The logfile_name log file did not need

ACD5708I The applylogs option is ignored when pruning.
activating databases restored from an
alternate Domino server. Explanation: The log file specified did not need to be
pruned.
Explanation: An attempt was made to apply
transaction log files to a database that was restored System Action: Processing continues.
from an alternate Domino server. This attempt failed.
User Response: The log file will automatically be
System Action: The applylogs option is ignored and pruned at a later date. If the log file is too large now,

ACD5743W • ACD5772E
lower the number of days the log entries are retained.
ACD5767I You have not selected any pending
databases to activate.
ACD5743W Changing from Selective Backup to
Explanation: The user has not selected any pending
Incremental Backup will erase all
databases to activate but has pressed the Activate
current selections for the Selective
button.
Backup! You can only select ONE
directory at a time for the Incremental System Action: Processing ends.
Backup. Do you wish to continue?
User Response: Do not press the Activate button until
Explanation: Incremental backup only allows one pending databases have been selected for activation.
directory to be backup each time.
System Action: Processing continues once either ″Yes″ ACD5768I There are no databases pending
or ″No″ is pressed. activation.
User Response: User needs to understand how the Explanation: The list of pending databases is empty
incremental and selective backup works. and the user has selected the Activate button.
ACD5764I Changing this setting (to active only)
User Response: None
will refresh the view. All selections will
be lost. Do you want to continue?
ACD5769I Logs cannot be applied to databases
Explanation: The user has selected the active only
backed up from another Domino server.
toolbar button or pulldown menu item. To activate this
Do you wish to continue?
setting the view must be refreshed.
Explanation: Pending databases from a Domino server
System Action: Continues or ends processing as
other than the local Domino server have been selected
requested.
and the Apply Logs box has been checked.
User Response: Select Yes or No. Selecting Yes will
refresh the view. Selecting No will leave the current
requested.
view unchanged.
User Response: Press Yes to continue. Press No to
terminate the request.
ACD5765I Changing this setting (to active/inactive)
will refresh the view. All selections will
be lost. Do you want to continue? ACD5770I You have not selected any databases to
restore.
Explanation: The user has selected the active/inactive
toolbar button or pulldown menu item. To activate this Explanation: The user has not selected any databases
setting the view must be refreshed. to restore but has pressed the Restore button.
System Action: Continues or ends processing as System Action: Processing ends.
requested.
User Response: Do not press the Restore button until
User Response: Select Yes or No. Selecting Yes will databases have been selected for restore.
refresh the view. Selecting No will leave the current
view unchanged.
ACD5771I There are no databases to restore.
ACD5766I When the view is refreshed all Explanation: There are no database backups and the
selections will be lost and an attempt user has selected the Restore button.
will be made to expand the new tree to System Action: Processing ends.
the currently highlighted item. Do you
want to continue? User Response: None
Explanation: The user has selected the refresh toolbar

button or pulldown menu item. ACD5772E More than one database has been
selected but only one restore location
System Action: Continues or ends processing as has been specified. When more than one
requested. database is selected the ’Restore Into’
User Response: Select Yes or No. Selecting Yes will specification must contain an ’=’.
refresh the view. Selecting No will leave the current Explanation: More than one database has been
view unchanged. selected and the Restore Into specification does not
contain an ’=’.

ACD5773I • ACD5823E
ACD5818I There are no database backups for the
User Response: Provide a valid Restore Into value server named servername.
and retry.
ACD5773I You have selected multiple backups of
some databases to be restored. For these
databases, only the ones with the latest User Response: None
backup dates will be restored. Do you
want to continue?
ACD5819I There are no transaction log file
Explanation: More than one backup of at least one archives for the server named servername.
database has been selected for restore. We will restore
Explanation: There are no transaction log file archives
the backup with the latest date.
on the Tivoli Storage Manager server for the specified
System Action: Continues or ends processing as server name.
requested.
User Response: None
ACD5820I There are no database backups matching

ACD5774I Changing the Point in Time setting will
the filespec filespec and the server name
cause the tree to be refreshed. All
servername.
selections will be lost. Do you want to
continue? Explanation: There are no database backups on the
Tivoli Storage Manager server for the specified server
Explanation: The has exited the Point in Time dialog
name.
by pressing OK.
requested. User Response: None
terminate the request. ACD5821I There are no transaction log file
archives matching the filespec filespec
and the server name servername.
ACD5806W The path specified does not contain a
notes.ini file. Do you still want to save Explanation: There are no database backups on the
this? Tivoli Storage Manager server for the specified server
name.
Explanation: No notes.ini file could be found in the
directory path entered. System Action: Processing ends.
System Action: Processing continues once either ″Yes″ User Response: None
or ″No″ is pressed.
User Response: Ensure the correct directory path is ACD5822I You have not selected any databases for
entered. Selective backup.
Explanation: The user has not selected any databases
ACD5807W The preference has been set to do Selective backup but has pressed the Backup
successfully, however, the path specified button.
does not currently contain a notes.ini
file. System Action: Processing ends.
Explanation: No notes.ini file could be found in the User Response: Do not press the Backup button until
directory path entered. one or more databases have been selected for Selective
backup.
System Action: The preference has still been set with
the directory path entered.
ACD5823E Invalid incremental backup list was
User Response: Ensure the correct directory path is created.
entered.
Explanation: An invalid incremental backup list was
created or found.

ACD5824I • ACD5900E
User Response: Retry the operation. If the error User Response: Ensure archival transaction logging is
persists, contact your service representative. in effect and archive some transaction log files before
re-attempting this operation.
ACD5824I You have not selected any databases for
Incremental backup. ACD5830E Invalid date. Please re-enter.
Explanation: The user has not selected a directory for Explanation: An invalid date was entered.
Incremental backup but has pressed the Backup button.
System Action: The current dialog remains active and
System Action: Processing ends. the focus is set to the invalid date.
User Response: Do not press the Backup button until User Response: Enter a valid date.
one directory has been selected for Incremental backup.
ACD5831I You have selected multiple archives of
ACD5825I You can only select ONE directory at a some transaction log files to be restored.
time for Incremental backup. For these log files, only the ones with
the latest archive dates will be restored.
Explanation: The user cannot select more than one
Do you want to continue?
directory at a time for Incremental backup.
Explanation: More than one archives of at least one
log file has been selected for restore. We will restore the
User Response: Do not press the Backup button until log file archive with the latest date.
only one directory has been selected for Incremental
backup.
requested.
ACD5826E Invalid selective backup list was
created.
Explanation: An invalid selective backup list was
ACD5832I A query for the transaction log file
created or found.
archives failed.
Explanation: A query of the transaction log file
User Response: Retry the operation. If the error archives failed with an error.
ACD5827E Insert to the Backup List failed.
Explanation: Cannot insert database to the Backup
List.
ACD5838E The Restore Into name you entered is
System Action: Processing ends. too long. Please enter a name no longer
than numberofchars.
persists, contact your service representative. Explanation: The Restore Into name entered is too
long.
ACD5828E Invalid Domino server name is selected. System Action: Processing ends.
Explanation: An invalid Domino server name is User Response: Provide a valid Restore Into value
selected. and retry.

ACD5900E The ’Restore Into:’ field requires a
User Response: Retry the operation. If the error complete filename. Please enter the field
persists, contact your service representative. again with a complete filename or an ’=’
(equals sign) representing the complete
ACD5829I No transaction log file archives can be filename.
found. Explanation: The Restore Into field requires a
Explanation: There are no transaction log file archives. complete filename. Directory names are not allowed.
The transaction log may not have been previously System Action: Processing ends.
archived.
User Response: Provide a valid ’Restore Into’ value
System Action: Processing ends. and retry the operation.

ACD5901E
ACD5901E The ’-INTO=filename’ parameter

requires a complete filename. Please
enter the parameter again with a
complete filename or an ’=’ (equals
sign) representing the complete
filename.
Explanation: The -INTO=filename parameter requires
a complete filename. Directory names are not allowed.
User Response: Provide a valid -INTO=filename
parameter and retry the operation.

Chapter 6. Tivoli Data Protection for Microsoft Exchange
Server (ACN0000–ACN9999)
This chapter describes the messages issued by Tivoli Data Protection for Microsoft
Exchange Server, Version 2.2.0. The messages begin with the prefix ACN and are
listed in numerical order.
ACN0003S An internal processing error has ACN0055E Write failure on license file (licensefile).
occurred.
occurred.
ACN0004E An unknown error has been detected. ACN0056E Data in the license file (licensefile) is not
in a valid format.
ACN0057E The checksum in the license file
ACN0005E Out of memory. Stop other processes (licensefile) does not match the license
ACN0053E License file (licensefile) could not be
opened.
ACN0058E The ’Try and Buy’ license has expired.
expired.
ACN0054E Read failure on license file (licensefile).
the product.
ACN0100E Incomplete command:

ACN0101E • ACN0132W
ACN0101E Invalid argument: ACN0107E This command requires one of the

following options:
ACN0102E Invalid command: ACN0108E Multiple dbnames are not allowed.

ACN0103E Invalid option for the specified
command:
ACN0109E Equal numbers of the relocate and to
ACN0104E Invalid option:
that was detected.
ACN0110E Wildcards are not allowed as part of the
incorrectly.
ACN0105E Missing argument: System Action: Processing ends.
System Action: Processing ends. ACN0132W Tracing could not be started. Processing
will continue.
tracing.
ACN0106E The following options cannot be System Action: Processing will continue with the
the problem.

ACN0133W • ACN0156E
ACN0133W Could not locate installation directory. ACN0153I Performance stats: seconds seconds spent
User Response: None
command entered.
ACN0154E The Tivoli Data Protection application
up correctly.
ACN0134W Could not locate log directory.
command entered.
application client.
ACN0155E The Tivoli Data Protection application
up correctly.
ACN0150I Operation canceled by user.
ctrl-C.
application client.
ACN0151E Errors occurred while processing the
request.
ACN0156E Could not load the Tivoli Storage
Manager API.
not be loaded.
ACN0152I Performance stats: seconds seconds spent
User Response: None
Chapter 6. Tivoli Data Protection for Microsoft Exchange 675

ACN0160E • ACN0207E
ACN0160E An authentication error occurred with ACN0201E File (filename) could not be opened for
password.
User Response: None
ACN0202E Read failure on file (filename).
ACN0161E Authentication error. The password
User Response: None
System Action: Processing stops. ACN0203E Write failure on file (filename).
ACN0162E The passwords entered do not match.

ACN0204E File (filename) could not be closed.
ACN0163E The directory path needs to be

However, this path needs to be fully-qualified. ACN0205E File (filename) statistics could not be
obtained.
ACN0167E The fully-qualified file name is too User Response: None

long.
Explanation: An attempt was made to use a ACN0206E Directory (directory) could not be created.
ACN0200E File (filename) could not be opened for ACN0207E Directory path (directorypath) is too long.
reading.
User Response: None
User Response: None

ACN0208E There is not enough disk space for the
ACN0214E The backup object’s management class
ACN0209E The rename of file (filename1) to
ACN0215E All backup objects do not have the same
User Response: None
destination.
ACN0210E The Tivoli Storage Manager high level
destinations.
User Response: None
ACN0211E The Tivoli Storage Manager low level
ACN0216E Unable to obtain space information for
User Response: None
User Response: None
ACN0212E The Tivoli Storage Manager filespace
name is too long. ACN0217E The Tivoli Storage Manager filespace
name is invalid.
attempt failed.
User Response: None ACN0218E The Tivoli Storage Manager high level
ACN0213E The maximum number of objects System Action: Processing ends.
ACN0219E The Tivoli Storage Manager low level

ACN0255E • ACN0264I
ACN0255E PASSWORDACCESS is Generate. Either ACN0259E The password you entered for
the stored password is incorrect or there verification does not match the
is no stored password. If you do not password you entered for your new
have a stored password, use of the password. Your password will not be
-TSMPassword=xxx option will set and changed.
store your password.
Explanation: The client options file has the verification of your new password does not match the
PASSWORDACCESS option set to generate. Currently, new password that was entered.
there is no password that has been stored. An initial
password needs to be stored.
User Response: Try again to change your password
User Response: Invoke the command again using the password and for the verification password.
-TSMPassword option. Any subsequent commands
should now complete without specifying a password.
ACN0260I Password successfully changed.
ACN0256E The password in your Tivoli Storage
Manager options file has expired. Please
change your password on the Tivoli System Action: Processing ends.
’change password’ command and then User Response: None
either change or remove the password
value in your options file. ACN0261I There are no backups for the server
Explanation: Your Tivoli Storage Manager password named servername.
has expired. You need to change your password. Explanation: There are no backups on the Tivoli
System Action: Processing ends. Storage Manager server for the specified server name.
User Response: Obtain a new password for your System Action: Processing ends.
Tivoli Storage Manager node using the change User Response: None
password command or by asking your Tivoli Storage
ACN0262I There are no backups matching the
filespec directorypath and the server
ACN0257E Your password has expired. name servername.
Explanation: Your Tivoli Storage Manager password Explanation: There are no database backups on the
has expired. A new password needs to be obtained. Tivoli Storage Manager server for the specified server
System Action: Processing ends. name.
User Response: Obtain a new password for your System Action: Processing ends.
Tivoli Storage Manager node using the change User Response: None
password command or by asking your Tivoli Storage
ACN0263E Failed to start Web browser with a
return code of returncode.
ACN0258E You did not enter a valid password.
Processing ends. Explanation: An attempt was made to start the web
browser to view the TSM HTML book. This attempt
Explanation: The password that was entered was not failed.
a valid password.
User Response: Start your web browser manually and
User Response: Re-enter the command specifying a point it to bookfrm.htm in the agent htm directory.
valid password.
ACN0264I Could not find the default browser

defined. An attempt will be made to use
registry to determine the default browser. However,

ACN0265E • ACN3503I
there was not one defined. It will be determined where
ACN0302E A failure occurred on stripe number
Explanation: A failure occurred on the numbered
User Response: It is possible that a default browser is stripe.
not defined for the system. This is okay. An attempt
will be made to use Microsoft’s Internet Explorer.
ACN0265E Could not find Internet Explorer.
the problem.
ACN3500I TDP for Microsoft Exchange: Starting
backup type backup of object name from
System Action: Processing ends. server server name.
User Response: Make sure that the registry is set up Explanation: This is an informational message that is
correctly for Internet Explorer. written to the Tivoli Storage Manager Server activity
log when a backup is started.
ACN0266E Could not find the Tivoli Storage System Action: None
Manager HTML books.
ACN3501I TDP for Microsoft Exchange: backup type
books were installed. This attempt failed.
backup of object name from server server
System Action: Processing ends. name completed successfully. bytes bytes
sent in seconds seconds.
application client code. This will ensure that the Explanation: This is an informational message that is
registry entries are set up correctly. written to the Tivoli Storage Manager Server activity
log when a backup completes successfully.
ACN0267E The verify password entered does not System Action: None
match the new password entered.
new password.
ACN3502E TDP for Microsoft Exchange: backup type
System Action: Processing ends. backup of object name from server server
name failed, rc = return code.
verify password. Explanation: This is an informational message that is
log when a restore fails.
ACN0300E Invalid restore type.
System Action: None
User Response: Re-enter the command specifying a ACN3503I TDP for Microsoft Exchange: backup type
valid restore type. backup of storage group name from server
server name was canceled by the user.
ACN0301E Invalid backup type. Explanation: This is an informational message that is
Explanation: The type of backup requested is invalid. written to the Tivoli Storage Manager Server activity
log when a storage group backup was canceled by the
System Action: Processing ends. user.
User Response: Re-enter the command specifying a System Action: None
valid backup type.

ACN3504I • ACN3513E
ACN3504I TDP for Microsoft Exchange: Starting ACN3509I TDP for Microsoft Exchange: backup type
restore for server servername. restore of storage group storage group
name to server server name was canceled
by the user.
log indicating the start of a restore. Explanation: This is an informational message that is
System Action: None
log when a storage group restore was canceled by the
User Response: None Centrally logged user.
System Action: None
ACN3505I TDP for Microsoft Exchange: Restore
from server servername to servername is
complete. Total backups restored: Total
bytes transferred: Elapsed processing ACN3510I TDP for Microsoft Exchange:
time: Secs Throughput rate: Kb/Sec Attempting to inactivate the object:
filespace - [filespace name], hl - [high level],
ll - [low level]
log indicating the end of a restore. Explanation: This is an informational message that is
System Action: None
log indicating the attempt to inactivate an object.
System Action: None
ACN3506I TDP for Microsoft Exchange: Starting
backup type restore of storage group
storage group name to server server name. ACN3511I TDP for Microsoft Exchange:
Inactivation of the previous objects
succeeded.
log indicating the start of a storage group restore. Explanation: This is an informational message that is
System Action: None
log indicating the success of the inactivation of objects.
System Action: None
ACN3507E TDP for Microsoft Exchange: backup type
restore of storage group storage group
name to server server name completed ACN3512E TDP for Microsoft Exchange:
successfully. Inactivation of the previous objects
failed.
log when a storage group restore completes written to the Tivoli Storage Manager Server activity
successfully. log indicating the failure of the inactivation of objects.
ACN3508E TDP for Microsoft Exchange: backup type ACN3513E TDP for Microsoft Exchange:
restore of storage group storage group Inactivation of the previous objects was
name to server server name failed, rc = canceled.
return code.
Explanation: This is an informational message that is written to the Tivoli Storage Manager Server activity
written to the Tivoli Storage Manager Server activity log indicating the failure of the inactivation of objects
log when a storage group restore fails. because the task was canceled by the user.

ACN3514I • ACN5056I
ACN3514I TDP for Microsoft Exchange: Starting ACN5051W The configuration file cannot be found,
backup for server servername. using default settings.
Explanation: This is an informational message that is Explanation: The /configfile value specified a file that
written to the Tivoli Storage Manager Server activity can’t be found, so default settings are being used.
log indicating the start of a backup.
System Action: None
User Response: Ensure the file name intended is
User Response: None Centrally logged specified, then re-enter the command.
ACN3516I TDP for Microsoft Exchange: Backup of ACN5052E An error occurred trying to set the
server servername is complete. Total preference preference.
storage groups backed up: Total bytes
transferred: Elapsed processing time:
preferences file.
Secs Throughput rate: Kb/Sec
written to the Tivoli Storage Manager Server activity User Response: View any other messages that were
log indicating the end of a backup request. displayed. After reviewing the messages and fixing any
of the problems indicated, try running the command
System Action: None
again.
ACN5053E The value for the preference preference is
ACN3517E TDP for Microsoft Exchange: Backup of not valid. See the TDPEXCC HELP SET
server servername failed, rc = returncode. output or the User’s Guide for valid
SET command parameters.
written to the Tivoli Storage Manager Server activity Explanation: The preference being set is not valid.
log indicating the failure of a backup request.
System Action: None
User Response: Run ″tdpexcc help set″ or look at the
User Response: None Centrally logged User’s Guide for valid SET command parameters.
ACN3518I TDP for Microsoft Exchange: Backup of ACN5054I The preference has been set
server servername failed. The request was successfully.
canceled by the user.
Explanation: The preference was set successfully.
log indicating the failure of a backup request. The user User Response: None
canceled the backup.
System Action: None ACN5055E The Microsoft Exchange API could not
be loaded.
Explanation: If running on Microsoft Exchange 5.5,
the dll that is attempting to load is edbbcli.dll. If
ACN5050I A new configuration file has been
running on a later version of Microsoft Exchange, the
created.
dll that is attempting to load is esebcli2.dll.
name that didn’t already exist. A new file has been
created. User Response: Ensure that the Microsoft Exchange
Server has been correctly installed.
ACN5056I The logfile log file could not be pruned.
Explanation: An attempt was made to prune the log.
This attempt was unsuccessful.

ACN5057I • ACN5066W
User Response: It could be that the log file does not
ACN5062E The version of Microsoft Exchange that
is running is not a supported version for
Tivoli Data Protection for Microsoft
Exchange.
ACN5057I The logfile log file has been pruned
Explanation: Tivoli Data Protection for Microsoft
successfully.
Exchange supports Microsoft Exchange 5.5 or Microsoft
Explanation: The log mentioned pruned successfully. Exchange 2000.
User Response: None. User Response: Update your Microsoft Exchange

server to a supported platform.
ACN5058W The logfile name is greater than the

maximum allowed. Processing will ACN5063E An error occurred trying to get the
continue using a logfile name of logfile Microsoft Exchange version information.
in the current directory. It could be a problem with the registry.
Or, a Microsoft Exchange Server is not
Explanation: The logfile name entered was not fully installed on this machine.
qualified. When the fully qualified logfile name was
created, it was longer than the possible length of a Explanation: An attempt was made to read the
logfile. registry to determine the level of Microsoft Exchange
that is currently running. This attempt failed.
System Action: Processing continues creating and
using a logfile in the current directory. System Action: Processing ends.
User Response: You may want to consider updating User Response: Determine if the registry has been
the logfile name using a fully qualified path. corrupted. Or, it is possible that the Microsoft Exchange
Server is not installed on this machine.
ACN5059W The logfile log file cannot be opened for

writing. There will be no logging of ACN5064W The service cannot be started when
events. doing a restore.
Explanation: The log mentioned could not be opened Explanation: A request was made to restore the listed
for append. Therefore, there will be no logging done. database. However, the service associated with this
database is started. It needs to be stopped in order to
System Action: Processing continues without logging. do this restore.
User Response: Determine why the log could not be System Action: Processing ends.
non-existent drive or partition. Or, that the file is User Response: Stop the associated service and
read-only and cannot be written to. reenter the restore command.
ACN5060E A Tivoli Storage Manager API error has ACN5065E All of the services associated with this
occurred. restore are running.
Explanation: A Tivoli Storage Manager API api error Explanation: A request was made to restore some
has occurred. databases. However, all of the services associated with
these databases are running. The services need to be
System Action: Processing ends. stopped in order to do this restore.
User Response: Retry the operation. If the error System Action: Processing ends.
User Response: Stop the associated services and
reenter the restore command.
ACN5061E A Microsoft Exchange api error has
occurred.
ACN5066W The storage group <storagegroup> does
Explanation: A Microsoft Exchange api error has not exist.
occurred.
Explanation: A storage group was entered that does
System Action: Processing ends. not exist on the server specified. In particular, the one
User Response: Retry the operation. If the error that is listed in the message.
persists, contact your service representative. System Action: Processing ends.

ACN5067E • ACN5076W
User Response: Reenter the command giving a
ACN5071W The Information Store is not running.
storage group that exists.
The Information Store will not be
backed up.
ACN5067E None of the storage groups and/or
Explanation: A request was made to backup the
databases entered exist. Or, if they do
Information Store. However, the Information Store
exist, and you are using Exchange 2000,
needs to be running in order to do the backup.
it could be that the databases have not
been dismounted. System Action: Processing ends.
Explanation: None of the storage groups that were User Response: Start the Information Store and
entered, exist on the Microsoft Exchange Server. Or, this reenter the backup command.
could mean that of the storage groups entered, it is
possible that there are some databases that are being
ACN5072W Databases in storage group <storage
restored that are not dismounted.
group> are dismounted -- skipping.
Explanation: A request was made to backup a set of
User Response: Verify that all of the databases have storage groups. However, there are databases in this
been dismounted in order to do the restore. Or, verify storage group that are not mounted. All of the
that all of the storage groups exist that were entered on databases need to be mounted in order to backup this
the command line. storage group.
System Action: Processing continues, but skips this
ACN5068W The database <databasename> does not particular database.
exist in the storage group <storagegroup>.
User Response: Mount all of the databases for this
Explanation: The database that was entered does not particular storage group and reissue the backup for this
exist in the storage group that was entered. storage group.
ACN5073E None of the storage groups entered are
User Response: Reenter the command giving a valid
in a state to be backed up.
database name that would exist in a valid storage
group. Explanation: A request was made to backup a set of
storage groups. However, each of the storage groups
entered has at least one database that is dismounted.
ACN5069W The database <database> in the storage
group <storage group> is not dismounted. System Action: Processing ends.
Explanation: While looking at the list to restore, it was User Response: Mount all of the databases for the
determined that not all of the databases within the particular storage groups and reissue the backup
storage groups were dismounted. command.
System Action: Processing continues skipping over
the listed databases and storage groups. ACN5074E None of the databases/storage groups
entered exist.
User Response: If a restore needs to be done for one
of the databases skipped, reenter the command being Explanation: A request was made to backup a set of
sure that these databases are now dismounted. storage groups or databases. However, none exist. It
could be that the name was typed in without the
correct casing.
ACN5070W The Directory Service is not running.
The Directory will not be backed up. System Action: Processing ends.
Explanation: A request was made to backup the User Response: Be sure that the correct casing was
Directory service. However, the Directory service needs used when entering the list to be backed up. Then,
to be running in order to do the backup. reissue the backup command.
ACN5076W Unable to inactivate all previous backup
User Response: Start the Directory service and reenter
objects.
the backup command.
Explanation: A request was made to inactivate some
previous backup objects. This attempt failed.
User Response: When the next full of the database is

ACN5083I • ACN5240E
done, another attempt will be made to inactivate the System Action: This combination is ignored.
failed objects.
User Response: Check for misspelled input and
re-enter command.
ACN5083I All of the storage groups entered have
been excluded.
ACN5142E No storage group was found that
Explanation: An attempt was made to do a backup. matches the request.
However, the storage groups or databases entered have
Explanation: The storage groups or databases could
been excluded by an exclude statement in the options
not be found on this Microsoft Exchange server.
file.
System Action: Execution ends.
User Response: Check for misspelled input and
User Response: If you want this storage group or
re-enter command.
database backed up, you need to modify the exclude
statements in your options file.
ACN5237E Unable to communicate with the
Microsoft Exchange Server.
ACN5084W IS was not input as one of the parts to
restore. The partial option will be Explanation: An attempt was made to communicate
ignored. the with the Microsoft Exchange Server that was
entered. This attempt failed.
Explanation: A request was made to restore either/or
the private or public part of the Information Store. System Action: Processing ends.
However, the IS was not input as one of the parts to
restore. User Response: Be sure that the Microsoft Exchange
server that was entered is valid. Also, be sure that the
System Action: Processing continues ignoring the Microsoft Exchange server is running.
partial option.
User Response: If you really want to restore either/or ACN5238E Unable to retrieve the domain
the public or private part of the Information Store, you information for the Microsoft Exchange
need to enter IS as an input. Server.
Explanation: An attempt was made to retrieve the
ACN5086W None of the storage groups entered domain information for the Microsoft Exchange Server.
exist. Or, if doing a DBCOPY backup, This attempt failed.
the database entered does not exist.
Explanation: A storage group was entered that does
not exist on the server specified. Or, if a DBCOPY User Response: Be sure that the Microsoft Exchange
backup was entered, the dbname specified does not server is running.
exist on the Microsoft Exchange Server.
System Action: Processing ends. ACN5239E Unable to retrieve the storage group
information.
User Response: Reenter the command giving a
storage group or dbname that exists. Explanation: An attempt was made to retrieve the
storage group information for the Microsoft Exchange
Server. This attempt failed.
ACN5140I Storage Group <storagegroup> does not
exist - skipping. System Action: Processing ends.
Explanation: The storage group that was specified by User Response: Be certain that the Microsoft Exchange
the user is not found on this Exchange server. Server is running properly.
System Action: This storage group is ignored.

ACN5240E Unable to retrieve the database
User Response: Check for misspelled input and information.
re-enter command.
Explanation: An attempt was made to retrieve the
database information for the storage group of the
ACN5141I Database <database>, Storage Group Microsoft Exchange Server. This attempt failed.
<storagegroup> does not exist - skipping.
Explanation: This combination of storage group and
database name that was specified by the user is not User Response: Be certain that the Microsoft Exchange
found on this Microsoft Exchange server. Server is running properly.

ACN5241E The Microsoft Exchange Information ACN5305E Unable to query service information.
Store is currently not running.
Explanation: An attempt was made to query specific
Explanation: An attempt was made to retrieve the service information. This attempt failed.
Microsoft Exchange Server information. This attempt
System Action: Command ends.
failed.
User Response: Determine if there is a problem with
the Microsoft Exchange server.
User Response: In order to retrieve the Microsoft
Exchange Server information, the Microsoft Exchange
ACN5350E An unknown Exchange API error has
Information Store needs to be running. Start this service
occurred.
to get the requested information.
Explanation: An Exchange api error has occurred but
the associated error message could not be found. The
ACN5301E Unable to get the value for the
Windows NT event log may contain more information.
Organization from the registry.
registry to determine the organization for the Microsoft User Response: If the Windows NT event log does not
Exchange Server. This attempt failed. help resolve the problem, verify the Exchange Server
installation and retry the operation. If the error persists,
the registry. Or, Microsoft Exchange may not be
ACN5351E The Exchange server application is not
installed properly.
registered for backup.
Explanation: The Exchange server application must be
ACN5302E Unable to get the value for the Site from
registered for backup with the Windows Server. The
the registry.
Windows NT event log may contain more information.
registry to determine the site for the Microsoft
Exchange Server. This attempt failed. User Response: If the Windows NT event log does not
help resolve the problem, verify the Exchange Server
installation and retry the operation. If the error persists,
User Response: Determine if there is a problem with contact your service representative.
the registry. Or, Microsoft Exchange may not be
installed properly.
registered for offline restore.
ACN5303E Unable to get the value for Circular
Logging from the registry.
registered for offline restore with the Windows Server.
Explanation: An attempt was made to read the The Windows NT event log may contain more
registry to determine the Circular Logging setting for information.
either the IS or the DIR of the Microsoft Exchange
Server. This attempt failed.
User Response: If the Windows NT event log does not
User Response: Determine if there is a problem with installation and retry the operation. If the error persists,
the registry. Or, Microsoft Exchange may not be contact your service representative.
installed properly.
ACN5304E Unable to open service to determine if registered for online restore.
running or not.
Explanation: An attempt was made to open a service. registered for online restore with the Windows Server.
This attempt failed. The Windows NT event log may contain more
information.
the Microsoft Exchange server. User Response: If the Windows NT event log does not

installation and retry the operation. If the error persists, get the TEMP environment variable for the machine.
contact your service representative. This attempt failed.
ACN5354E The storage group was not found.
User Response: Be sure that the TEMP environment
Explanation: The specified storage group name was variable is set for this machine. Or, you can use the
not found. TEMPLOGRESTOREPATH option with the restore.
ACN5360E The /ERASEexistingdata option is not
User Response: Verify the command input and retry
allowed during a partial restore.
the operation. If the error persists, contact your service
representative. Explanation: A partial storage group restore was
requested with the /ERASEexistingdata option. The
/ERASEexistingdata option is not allowed during a
ACN5355E The database was not found.
partial restore.
Explanation: The specified database name was not
found.
User Response: Reissue the command to restore the
entire storage group or reissue the command without
User Response: Verify the command input and retry the /ERASEexistingdata option.
the operation. If the error persists, contact your service
representative.
ACN5361E It is invalid to have an ’*’ within a
storage group name.
ACN5356E The database file name is undefined.
Explanation: An attempt was made to backup a
Explanation: Every Microsoft Exchange database must storage group that contains an ’*’. It is invalid to have
specify a database file name. an ’*’ in a storage group name.
System Action: Processing ends. System Action: Processing continues, but this storage
group will not be backed up.
User Response: Verify the database properties and
retry the operation. If the error persists, contact your User Response: Either rename the storage group or
service representative. this storage group cannot be backed up.
ACN5357W The truncation of the transaction log ACN5362W The filespace <filespace> in an invalid
failed. filespace name.
Explanation: The truncation of the transaction log Explanation: When getting the filespaces, it was noted
failed. that the filespace displayed in the message existed, but
is an invalid filespace.
System Action: Processing continues, but this filespace
User Response: There should be other messages along will not be used.
the problem. User Response: It is possible that there is a storage
group that exists that contains invalid characters within
its name. Refer to the Microsoft Exchange
ACN5358E A Microsoft Exchange API protocol error documentation as to the list of invalid characters.
has occurred.
Explanation: An unrecoverable Microsoft Exchange ACN5500E The MultiByteToWideChar() function
API protocol error has occurred. failed.
System Action: Processing ends. Explanation: This is an internal error.
User Response: Contact your service representative. System Action: Processing ends.
User Response: Retry the operation. If this error
ACN5359E An attempt was made to get the TEMP persists, contact your service representative.
environment variable. This attempt
failed.
Explanation: The TEMPLOGRESTOREPATH option
was not set for the restore. So, an attempt was made to

User Response: Select a database then press the
ACN5501E The WideCharToMultiByte() function
backup button.
failed.
Explanation: This is an internal error.
ACN5725I No Storage Groups have been selected
System Action: Processing ends. for backup.
User Response: Retry the operation. If this error Explanation: The backup button was pressed but no
persists, contact your service representative. Storage Groups have been selected in the tree or list in
the graphical user interface.
ACN5705W An error was encountered with Tivoli System Action: Processing stops.
Storage Manager API initialization, rc =
User Response: Select a Storage Group then press the
backup button.
more information or determine if the
TSM API is installed properly.
ACN5741I No Backups have been selected to be
Explanation: An attempt was made to run setup for
Restored.
the Tivoli Storage Manager API. However, errors were
encountered. Explanation: The restore button was pressed but
nothing was selected in the tree or list view.
User Response: Examine the dsierror.log file to
determine the problem. If this file does not exist, it is User Response: Select something then press the
possible that the TSM API is not installed properly. If restore button again.
this is the case, reinstall the TSM API and try running
the command again.
ACN5771W At least one of the database’s services
that is selected for restore is running.
ACN5706I The logfile_name log file did not need Do you want to stop the service(s)?
pruning.
Explanation: It has been detected that a service you
Explanation: The log file specified did not need to be are trying to restore is running.
pruned.
System Action: None
User Response: The log file will automatically be ACN5772W At least one of the databases that is
pruned at a later date. If the log file is too large now, selected for restore is mounted. Do you
lower the number of days the log entries are retained. want to dismount the database(s)?
Explanation: It has been detected that a database you
ACN5707W The logfile_name log file could not be are trying to restore is mounted.
opened for writing. The log was not
pruned and there will be no logging of System Action: None
events.
Explanation: The log mentioned could not be opened ACN5779E Unable to dismount database database in
for append. Therefore, there will be no logging done storage group storage group. Do you want
and the request to prune was not done. to continue the restore process?
System Action: Processing continues without logging Explanation: An error was received while trying to
and without pruning. dismount a database.
User Response: Determine why the log could not be System Action: None.
opened. It could be that the log file is going to a User Response: Press OK to try to continue with the
non-existent drive or partition, or that the file is restore process or cancel to stop.
marked read-only.
ACN5724I No databases have been selected for

backup.
Explanation: The backup button was pressed but no
databases have been selected in the list in the graphical
user interface.

Chapter 7. Tivoli Data Protection for Microsoft SQL Server
(ACO0000–ACO9999)
This chapter describes the messages issued by Tivoli Data Protection for Microsoft
SQL Server, Version 2.2.0. The messages begin with the prefix ACO and are listed
in numerical order.
ACO0003S An internal processing error has ACO0055E Write failure on license file (licensefile).
occurred.
occurred.
ACO0004E An unknown error has been detected. ACO0056E Data in the license file (licensefile) is not
in a valid format.
ACO0057E The checksum in the license file
ACO0005E Out of memory. Stop other processes (licensefile) does not match the license
ACO0053E License file (licensefile) could not be
opened.
ACO0058E The ’Try and Buy’ license has expired.
expired.
ACO0054E Read failure on license file (licensefile).
the product.
ACO0100E Incomplete command:

ACO0101E • ACO0132W
ACO0101E Invalid argument: ACO0107E This command requires one of the

following options:
ACO0102E Invalid command: ACO0108E Multiple dbnames are not allowed.

ACO0103E Invalid option for the specified
command:
ACO0109E Equal numbers of the relocate and to
ACO0104E Invalid option:
that was detected.
ACO0110E Wildcards are not allowed as part of the
incorrectly.
ACO0105E Missing argument: System Action: Processing ends.
System Action: Processing ends. ACO0132W Tracing could not be started. Processing
will continue.
tracing.
ACO0106E The following options cannot be System Action: Processing will continue with the
the problem.

ACO0133W • ACO0156E
ACO0133W Could not locate installation directory. ACO0153I Performance stats: seconds seconds spent
User Response: None
command entered.
ACO0154E The Tivoli Data Protection application
up correctly.
ACO0134W Could not locate log directory.
command entered.
application client.
ACO0155E The Tivoli Data Protection application
up correctly.
ACO0150I Operation canceled by user.
ctrl-C.
application client.
ACO0151E Errors occurred while processing the
request.
ACO0156E Could not load the Tivoli Storage
Manager API.
not be loaded.
ACO0152I Performance stats: seconds seconds spent
User Response: None
Chapter 7. Tivoli Data Protection for Microsoft SQL 691

ACO0160E • ACO0208E
ACO0160E An authentication error occurred with ACO0202E Read failure on file (filename).
your stored Tivoli Storage Manager
password.
Explanation: You were unable to log on to the Tivoli
User Response: None
ACO0203E Write failure on file (filename).
Tivoli Storage Manager server administrator. Explanation: An attempt was made to write to a file.
This attempt failed.
ACO0161E Authentication error. The password System Action: Processing ends.
entered is not valid. You are not logged
on to the Tivoli Storage Manager server. User Response: None

ACO0204E File (filename) could not be closed.
User Response: Enter the correct Tivoli Storage This attempt failed.
Manager password and try again.
ACO0162E The passwords entered do not match. User Response: None

Please enter them again.
Explanation: An incorrect password was entered. ACO0205E File (filename) statistics could not be
obtained.
User Response: Enter the passwords again. statistics. This attempt failed.
ACO0163E The directory path needs to be

However, this path needs to be fully-qualified. ACO0206E Directory (directory) could not be created.
System Action: Processing stops. Explanation: An attempt was made to create a

directory. This attempt failed.
User Response: Re-enter the command again giving a
fully-qualified /intopath. System Action: Processing ends.
User Response: None
ACO0200E File (filename) could not be opened for
reading. ACO0207E Directory path (directorypath) is too long.
Explanation: An attempt was made to open a file for Explanation: An attempt was made to use a directory
reading. This attempt failed. path that was too long. This attempt failed.
ACO0201E File (filename) could not be opened for ACO0208E There is not enough disk space for the
writing. operation attempted.
Explanation: An attempt was made to open a file for Explanation: An attempted operation required more
writing. This attempt failed. disk space than was available. The attempt failed.

ACO0209E The rename of file (filename1) to ACO0214E The backup object’s management class
(filename2) failed. backup copy group does not exist.
Explanation: An attempt was made to rename a file. Explanation: The Tivoli Storage Manager server has
This attempt failed. indicated that the backup object’s management class
User Response: None
ACO0210E The Tivoli Storage Manager high level
ACO0215E All backup objects do not have the same
Storage Manager high level qualifier that was too long.
destination.
This attempt failed.
User Response: None Storage Manager server within a single transaction. All
backup objects within a single transaction are required
to have the same management class backup copy
ACO0211E The Tivoli Storage Manager low level destinations.
Storage Manager low level qualifier that was too long. User Response: Contact your Tivoli Storage Manager

ACO0216E Unable to obtain space information for
User Response: None volume (volumename).
Explanation: An attempt was made to obtain space
ACO0212E The Tivoli Storage Manager filespace information for a volume. This attempt failed.
name is too long.
Storage Manager filespace name that was too long. This User Response: None
attempt failed.
System Action: Processing ends. ACO0217E The Tivoli Storage Manager filespace
name is invalid.
User Response: None
ACO0213E The maximum number of objects User Response: Contact your service representative.
ACO0218E The Tivoli Storage Manager high level
Explanation: In order to maintain backup data qualifier is invalid.
Tivoli Storage Manager server has indicated that the User Response: Contact your service representative.
ACO0219E The Tivoli Storage Manager low level

ACO0256E The password in your Tivoli Storage ACO0261I There are no backups for the server
User Response: None
ACO0263E Failed to start Web browser with a
ACO0257E Your password has expired. User Response: Start your web browser manually and
ACO0264I Could not find the default browser
ACO0258E You did not enter a valid password. System Action: Processing continues.
Processing ends.
ACO0265E Could not find Internet Explorer.
ACO0259E The password you entered for

verification of your new password does not match the ACO0266E Could not find the Tivoli Storage
ACO0260I Password successfully changed. application client code. This will ensure that the
User Response: None

ACO0267E • ACO3006I
ACO0267E The verify password entered does not ACO3002E TDP for Microsoft SQL Server: backup
match the new password entered. type backup of database database name
from server server name failed, rc = return
code.
new password.
User Response: Retry the command with a matching log when a database restore fails.
verify password.
System Action: None
ACO0300E Invalid restore type.
ACO3003I TDP for Microsoft SQL Server: Starting
System Action: Processing ends. restore type restore of backup object object
name to database database name on server
User Response: Re-enter the command specifying a server name.
valid restore type.
ACO0301E Invalid backup type. log when a restore is started.
Explanation: The type of backup requested is invalid. System Action: None
System Action: Processing ends. User Response: None Centrally logged
valid backup type. ACO3004I TDP for Microsoft SQL Server: restore
type restore of backup object object name
ACO0302E A failure occured on stripe number to database database name on server server
(stripe number), rc = return code name completed successfully.
Explanation: A failure occured on the numbered Explanation: This is an informational message that is
stripe. written to the Tivoli Storage Manager Server activity
log when a database restore completes successfully.
System Action: None
with this one. Refer to the other messages to determine User Response: None Centrally logged
the problem.
ACO3005E TDP for Microsoft SQL Server: restore
ACO3000I TDP for Microsoft SQL Server: Starting type restore of backup object object name
backup type backup of database database to database database name on server server
name from server server name. name failed.
log when a backup is started. log when a database restore fails.
ACO3001I TDP for Microsoft SQL Server: backup ACO3006I TDP for Microsoft SQL Server: Starting
type backup of database database name backup for server server name.
from server server name completed Explanation: This is an informational message that is
successfully. written to the Tivoli Storage Manager Server activity
Explanation: This is an informational message that is log indicating the start of a backup.
written to the Tivoli Storage Manager Server activity System Action: None
log when a database backup completes successfully.
System Action: None

ACO3007I • ACO3014I
ACO3007I TDP for Microsoft SQL Server: Backup ACO3011I TDP for Microsoft SQL Server: Restore
of server servername is complete. Total from server server name to server server
SQL backups selected: number selected name is complete. Total database
Total SQL backups attempted: number backups inspected: number inspected Total
attempted Total SQL backups completed: database backups requested for restore:
number completed Total SQL backups number requested Total database backups
excluded: number excluded Throughput restored: number restored Total database
rate: rate Kb/Sec Total bytes transferred: skipped: number skipped Throughput rate:
bytes Elapsed processing time: time Secs rate Kb/Sec Total bytes transferred: bytes
log indicating the end of a backup request. written to the Tivoli Storage Manager Server activity
log indicating the end of a restore.
System Action: None
System Action: None
ACO3008I TDP for Microsoft SQL Server: Backup
of server servername is complete. Total ACO3012I TDP for Microsoft SQL Server: restore
SQL backups selected: number selected type restore of backup object object name
Total SQL backups attempted: number to database database name from server
attempted Total SQL backups completed: server name canceled by user.
number completed Total SQL backups
excluded: number excluded Total SQL
backups inactivated: number inactivated
log indicating that a backup request was canceled by
Throughput rate: rate Kb/Sec Total bytes
the user.
transferred: bytes Elapsed processing
time: time Secs System Action: None
Explanation: This is an informational message that is User Response: None Centrally logged
log indicating the end of a backup request.
ACO3013I TDP for Microsoft SQL Server: Starting
System Action: None Inactivate processing for backup objects
from server servername
ACO3009I TDP for Microsoft SQL Server: backup
log when an inactivate begins.
type backup of database database name
from server server name canceled by user. System Action: None
Explanation: This is an informational message that is User Response: None Centrally logged
log indicating that a backup request was canceled by
the user. ACO3014I TDP for Microsoft SQL Server:
Inactivate processing complete Total
System Action: None database backups inspected: number
inspected Total database backups
requested for inactivation: number
requested Total database backups
ACO3010I TDP for Microsoft SQL Server: Starting inactivated: number inactivated Total
restore for server servername. database skipped: number skipped
log indicating the start of a restore. written to the Tivoli Storage Manager Server activity
log to indicate the end of an inactivate command.
System Action: None
System Action: None
User Response: None

ACO3015I • ACO5060E
User Response: None
ACO3015I TDP for Microsoft SQL Server:
Inactivating backup type backup backup
object. ACO5056I The logfile log file could not be pruned.
written to the Tivoli Storage Manager Server activity Explanation: An attempt was made to prune the log.
log when an inactivation of a backup object is started. This attempt was unsuccessful.
System Action: None System Action: Processing continues.
User Response: None Centrally logged User Response: It could be that the log file does not
ACO5050I A new configuration file was created.
ACO5057I The logfile log file was pruned
name that didn’t already exist. A new file was created.
successfully.
Explanation: The log mentioned pruned successfully.
ACO5051I The configuration file cannot be found,
using default settings.
ACO5058W The logfile name is greater than the
Explanation: The /configfile value specified a file that
maximum allowed. Processing will
can’t be found.
continue using a logfile name of logfile
System Action: Processing continues. in the current directory.
User Response: Ensure the correct file name is Explanation: The logfile name entered was not fully
specified. qualified. When the fully qualified logfile name was
created, it was longer than the possible length of a
logfile.
ACO5052E An error occurred trying to set the
requested configuration option. System Action: Processing continues creating and
using a logfile in the current directory.
configuration file. User Response: You may want to consider updating
the logfile name using a fully qualified path.
User Response: View any other messages that were
ACO5059W The logfile log file cannot be opened for
displayed. After reviewing the messages and fixing any
writing. There will be no logging of
of the problems indicated, try running the command
events.
again.
Explanation: The log mentioned could not be opened
for append. Therefore, there will be no logging done.
ACO5053E The value for the option option is not
valid. See the TDPSQLC HELP SET System Action: Processing continues without logging.
output or the User’s Guide for valid
SET command parameters.
Explanation: The configuration option being set is not non-existent drive or partition. Or, that the file is
valid. read-only and cannot be written to.
ACO5060E A Tivoli Storage Manager API error has
User Response: Run ″tdpsqlc help set″ or look at the
occurred.
User’s Guide for valid SET command parameters.
Explanation: A Tivoli Storage Manager API api error
has occurred.
ACO5054I The configuration option was set
successfully. System Action: Processing ends.
Explanation: The configuration option specified on the User Response: Retry the operation. If the error
SET command was set successfully. persists, contact your service representative.

ACO5061E A Mircosoft Sql api error has occured. ACO5091E PASSWORDACCESS is Generate. Either
the stored password is incorrect or there
Explanation: A Microsoft Sql api error has occured.
is no stored password. If you do not
System Action: Processing ends. have a stored password, use of the
-TSMPassword=xxx option will set and
User Response: Retry the operation. If the error store your password.
Explanation: The client options file has the
PASSWORDACCESS option set to generate. Currently,
ACO5063I The logfile_name log file did not need there is no password that has been stored. An initial
pruning. password needs to be stored.
Explanation: The log file specified did not need to be System Action: Processing ends.
pruned.
User Response: Invoke the command again using the
System Action: Processing continues. -TSMPassword option. Any subsequent commands
User Response: The log file will automatically be should now complete without specifying a password.
pruned at a later date. If the log file is too large now,
lower the number of days the log entries are retained. ACO5400E The Virtual Device Interface is not
registered with the Common Object
ACO5064W The logfile_name log file could not be Model.
opened for writing. The log was not Explanation: The virtual device interface could not be
pruned and there will be no logging of created because it is not registered with the common
events. object model. The SQL server may not be properly
Explanation: The log mentioned could not be opened installed.
for append. Therefore, there will be no logging done System Action: Processing ends.
and the request to prune was not done.
User Response: Verify your SQL server installation
System Action: Processing continues without logging and retry the operation. If the error persists, contact
and without pruning. your service representative.
opened. It could be that the log file is going to a ACO5401E The Virtual Device Interface could not
non-existent drive or partition, or that the file is be created.
marked read-only.
Explanation: The virtual device interface could not be
created. The SQL server virtual device interface log or
ACO5065E The value specified for the /SQLUSer Windows NT event log may contain more information.
option does not match the registry entry.
Explanation: A Backup, Restore or Query Sql
command was issued with User Response: If the SQL server messages do not
/SQLAUTHentication=SQLUserid and the /SQLUSer help resolve the problem retry the operation. If the
option also specified. An attempt was made to obtain error persists, contact your service representative.
the sqlpassword value from the registry but the userid
in the registry does not match the userid specified with
ACO5402E The Virtual Device Set could not be
the /sqluser option.
created.
Explanation: The virtual device set could not be
User Response: Reissue the command specifying created. The SQL server virtual device interface log or
either the /sqluser value which matches the registry Windows NT event log may contain more information.
entry or specify the desired values for both /sqluser
and /sqlpassword on the command.
User Response: If the SQL server messages do not
help resolve the problem retry the operation. If the
error persists, contact your service representative.

log, or Windows NT event log may contain more
ACO5403E The configuration of the Virtual Device
information.
Set could not be obtained.
Explanation: The configuration of the virtual device
set could not be obtained. The SQL server virtual User Response: If the SQL server messages do not
device interface log, SQL server activity log, SQL server help resolve the problem retry the operation. If the
error log, or Windows NT event log may contain more error persists, contact your service representative.
information.
System Action: Processing ends. ACO5420E
User Response: If the SQL server messages do not Explanation: A SQL API error has occurred.
error persists, contact your service representative. System Action: Processing for this operation ends.
ACO5404E The Virtual Device Set could not open a help resolve the problem retry the operation. If this
virtual device. error persists, contact IBM support.
Explanation: The virtual device set could not open a

virtual device. The SQL server virtual device interface ACO5421E Received the following from the MS
log, SQL server activity log, SQL server error log, or COM component: SQL message
Windows NT event log may contain more information. Explanation: A SQL error has occurred.
System Action: Processing ends. System Action: Processing for this operation ends.
User Response: If the SQL server messages do not User Response: If the SQL server messages do not
help resolve the problem retry the operation. If the help resolve the problem retry the operation. If this
error persists, contact your service representative. error persists, contact IBM support.
ACO5405E An unknown virtual device error has ACO5422E Received the following from the MS
been detected. SQL server: SQL message
Explanation: A virtual device returned and unknown Explanation: A SQL error has occurred.
return code.\n″ The SQL server virtual device interface
log, SQL server activity log, SQL server error log, or System Action: Processing for this operation ends.
Windows NT event log may contain more information. User Response: If the SQL server messages do not
System Action: Processing ends. help resolve the problem retry the operation. If this
error persists, contact IBM support.
error persists, contact your service representative. ACO5423E The following string is too long: string
Explanation: A SQL error has occurred.
ACO5406E The SQL server closed a virtual device System Action: Processing for this operation ends.
prematurely.
Explanation: The SQL server aborted the operation on help resolve the problem retry the operation. If this
the selected database. The SQL server virtual device error persists, contact IBM support.
interface log, SQL server activity log, SQL server error
log, or Windows NT event log may contain more
information. ACO5424E Could not connect to SQL server; SQL
server returned: SQL message
help resolve the problem retry the operation. If the System Action: Processing for this operation ends.
error persists, contact your service representative. User Response: If the SQL server messages do not
help resolve the problem retry the operation. If this
ACO5407E The SQL server aborted the operation. error persists, contact IBM support.
Explanation: The SQL server aborted the operation on

the selected database. The SQL server virtual device
interface log, SQL server activity log, SQL server error

ACO5425E The SQL server is not running: SQL ACO5450E The specified number of stripes (number
message of stripes) is invalid. Processing will
continue with the maximum number of
stripes (maximum number of stripes).
System Action: Processing for this operation ends.
Explanation: An invalid number of stripes was
User Response: Start the SQL server and retry the specified.
operation.
System Action: Processing continues utilizing the
maximum number of stripes allowed.
ACO5426E The SQL logon is does not have the
User Response: None
Sysadmin role: SQL message
Explanation: An attempt was made to logon to the
ACO5451E A failure occured on vdev (vdev name), rc
SQL server but the specified logon name does not have
= return code
the Sysadmin role.
Explanation: A failure occured on the named virtual
device.
User Response: Retry the operation specifying a logon
name that does have the Sysadmin role or change the
specified logon name to have the Sysadmin role. User Response: There should be other messages along
the problem.
ACO5427E The SQL server version is less than 7.0:
SQL message
ACO5452E Unable to delete temporary object:
Explanation: An attempt was made to use TDP for
(filespace name) (high level qualifier) (low
MS SQL Server V2 with a SQL server version prior to
level qualifier)
7. This is not allowed.
Explanation: When a backup fails, the TDP agent
attempts to delete all temporary backup data objects
User Response: Use the TDP for MS SQL V1 client from the TSM server. This message indicates that the
with SQL server versions prior to SQL 7.0. Or retry the specified temporary backup data object could not be
operation for a SQL server verison 7.0 or later. deleted from the TSM server. This error is usually
caused by the lose of all TSM server sessions.
ACO5428E The SQL server is not on the local System Action: Processing continues.
machine: SQL message
User Response: None. A backup of the database
Explanation: An attempt was made to use the should detect the temporary backup data object and
application client specifying a SQL server that was not delete it from the TSM server.
on the local machine.
System Action: Processing for this operation ends. ACO5453E The number of tsm sessions (number of
tsm sessions) is invalid for the specified
User Response: Retry the operation on the machine number of stripes (number of stripes).
where the SQL server resides. Processing will continue with the
number of tsm sessions (number of tsm
ACO5429E Could not obtain an event from SQL sessions) as the number of stripes.
server: SQL message Explanation: An invalid number of tsm sessions was
Explanation: A SQL error has occurred. detected for the specified number of stripes. This
message is caused by the circumvention of an internal
System Action: Processing for this operation ends. error.
User Response: If the SQL server messages do not System Action: Processing continues utilizing the
help resolve the problem retry the operation. If this number of tsm sessions as the number of stripes.
error persists, contact IBM support.

ACO5454E • ACO5550I
ACO5454E The maximum number of objects ACO5458W The TSM Server ’backup delete’ setting
allowed per tsm transaction (number of for node (TSM server NODENAME) is set
objects allowed per tsm transaction) is to NO. It should be set to YES for
invalid for the specified number of proper operation. Processing will
stripes (number of stripes). Processing will continue.
continue with (new number of stripes)
Explanation: The TSM Server setting that allows TSM
stripes.
clients to delete their own backups is set to NO for the
Explanation: The maximum number of objects specified NODENAME. It must be set to YES in order
allowed per tsm transaction is invalid for the specified for cleanup operations to perform correctly. With this
number of stripes for at least one tsm session. All tsm value set to NO it is possible to have residual data
sessions must allow at least one more object per tsm stored on the TSM Server that is not usable.
transaction than the number of stripes
System Action: Processing continues utilizing the new
User Response: Make sure the ’backup delete’ setting
number of stripes.
for the specified NODENAME is set to YES on the TSM
User Response: Reduce the number of stripes and/or Server. Your TSM Server administrator can change this
update the tsm server to increase the maximum setting for your NODENAME. The setting can only be
number of logical files that a client can send to the changed on the TSM Server.
server in a single transaction (TxnGrpMax).
ACO5500E The MultiByteToWideChar() function
ACO5455E The backup is corrupt and can not be failed.
restored.
Explanation: This is an internal error that indicates
Explanation: The backup being restored is corrupt corrupted storage.
because the data object(s) found do not correspond to
System Action: Processing for this database ends.
the meta data.
ACO5501E The Common Object Model (COM)
library failed to initialize.
ACO5456W The backup is corrupt and is not fully
Explanation: The unsuccessful call was
restorable. Processing will continue.
CoInitializeEx(NULL,COINIT_MULTITHREADED).
Explanation: The backup being restored is corrupt OLE32.dll or another COM dll may be missing,
because the data object(s) found do not correspond to down-level, or corrupted.
the meta data. Depending on the restore command and
System Action: Processing for this database ends.
backup type, a partial restore may be possible.
User Response: Verify your Windows NT (version 4
or later) installation is complete then retry the
User Response: Retry the operation. If the error operation. If this error persists, contact your service
persists, contact your service representative. representative.
ACO5457E An unknown SQL api error has occured. ACO5550I There are no backups matching the
filespec directorypathfilename and the
Explanation: A SQL api error has occurred but the
server name servername.
associated error message could not be found. The SQL
server activity log, SQL server error log, or Windows Explanation: There are no database backups on the
NT event log may contain more information. Tivoli Storage Manager server for the specified server
name.
help resolve the problem retry the operation. If the User Response: None
error persists, contact your service representative.

ACO5551I • ACO5722I
User Response: Make sure the SQL server is running.
ACO5551I There are no backups matching the
criteria specified for server name
servername. ACO5718I When the view is refreshed all
selections will be lost and an attempt
Explanation: There are no database backups on the
will be made to expand the new tree to
Tivoli Storage Manager server matching the query
the currently highlighted item. Do you
criteria for the specified server name.
want to continue?
Explanation: The user has selected the refresh toolbar
User Response: Try issuing the query specifying a button or pulldown menu item.
broader range of search criteria.
User Response: Select Yes or No. Selecting Yes will
ACO5552I No matches were found for the criteria
refresh the view, selecting No will leave the current
specified.
view unchanged.
Explanation: The SQL Server was searched for
databases that matched the criteria specified.
ACO5719I There are currently no backups on TSM.
Explanation: On the Inactivate page, the SQL server
User Response: Check the search criteria specified name expansion button was pressed.
(database name, group name, logical filename).
Re-enter the command.
User Response: Either nothing has been backed up to
a TSM server or all active backups have already been
ACO5715E Error writing option_name preference to
inactivated.
the configuration file.
Explanation: Could not write the specified preference
ACO5720I No databases have been selected for
to the configuration file.
backup.
System Action: Preferences processing ends.
Explanation: The backup button was pressed but no
User Response: Make sure you have a valid databases have been selected from the tree or list in the
configuration file, then try to update the preference graphical user interface.
again.
User Response: Select a database then press the
ACO5716W An error was encountered with Tivoli
backup button.
Storage Manager API initialization, rc =
more information or determine if the ACO5721I No backups have been selected for
TSM API is installed properly. restore.
Explanation: An attempt was made to run setup for Explanation: The restore button was pressed but no
the Tivoli Storage Manager API. However, errors were backups have been selected from the tree or list in the
encountered. graphical user interface.
System Action: Processing continues. System Action: Processing stops.
User Response: Examine the dsierror.log file to User Response: Select an object then press the restore
determine the problem. If this file does not exist, it is button.
possible that the TSM API is not installed properly. If
this is the case, reinstall the TSM API and try running
the command again. ACO5722I No backups have been selected for
inactivate.
ACO5717E Unable to log on to the SQL server. Explanation: The inactivate button was pressed but no
backups have been selected from the tree or list in the
Explanation: An error occured while trying to log on graphical user interface.
to the SQL server.
System Action: If running the client from the comand
line, the client ends. If running the client from the GUI, User Response: Select an object then press the
a prompt is displayed to enter the SQL user id and inactivate button.
password, or to choose NT authentication.

ACO5723E • ACO5824W
ACO5723E A named mark must be specified.

Explanation: The ″Stop At Mark″ or ″Stop Before
Mark″ option was chosen but the named mark was not
specified.
User Response: Enter a named mark or choose the
″Stop At″ option.
ACO5801E A log must be selected to use point in

time.
Explanation: A log must be selected before setting
point in time parameters.
User Response: Select at least one log for restore
before specifying a point in time.
ACO5823I Unable to get information. If data is

backed up to tape check the ″Wait for
Tape Mounts for File Information″
checkbox.
Explanation: Processing stops.
System Action: None
User Response: Try checking the box specified in the
message.
ACO5824W The SQL Server you are restoring from

is different than the SQL server you are
currently logged on to. Do you want to
continue?
Explanation: Processing continues.
System Action: None
User Response: If you want to restore something from
a different SQL server, press OK; otherwise press
Cancel and log on to the other SQL server.

Chapter 8. Tivoli Data Protection for Oracle
(ANU0000–ANU9999)
The messages in this section are for the Tivoli Data Protection for Oracle, Version
2.2.1. The messages begin with the prefix ANU and are listed in numerical order.
ANU0003S An internal processing error has ANU0055E Write failure on license file (licensefile).
occurred.
occurred.
ANU0004E An unknown error has been detected. ANU0056E Data in the license file (licensefile) is not
in a valid format.
ANU0057E The checksum in the license file
ANU0005E Out of memory. Stop other processes (licensefile) does not match the license
ANU0053E License file (licensefile) could not be
opened.
ANU0058E The ’Try and Buy’ license has expired.
expired.
ANU0054E Read failure on license file (licensefile).
the product.
ANU0100E Incomplete command:

ANU0101E • ANU0132W
ANU0101E Invalid argument: ANU0107E This command requires one of the

following options:
ANU0102E Invalid command: ANU0108E Multiple dbnames are not allowed.

ANU0103E Invalid option for the specified
command:
ANU0109E Equal numbers of the relocate and to
ANU0104E Invalid option:
that was detected.
ANU0110E Wildcards are not allowed as part of the
incorrectly.
ANU0105E Missing argument: System Action: Processing ends.
System Action: Processing ends. ANU0132W Tracing could not be started. Processing
will continue.
tracing.
ANU0106E The following options cannot be System Action: Processing will continue with the
the problem.

ANU0133W • ANU0156E
ANU0133W Could not locate installation directory. ANU0153I Performance stats: seconds seconds spent
User Response: None
command entered.
ANU0154E The Tivoli Data Protection application
up correctly.
ANU0134W Could not locate log directory.
command entered.
application client.
ANU0155E The Tivoli Data Protection application
up correctly.
ANU0150I Operation canceled by user.
ctrl-C.
application client.
ANU0151E Errors occurred while processing the
request.
ANU0156E Could not load the Tivoli Storage
Manager API.
not be loaded.
ANU0152I Performance stats: seconds seconds spent
User Response: None
Chapter 8. Tivoli Data Protection for Oracle 707

ANU0160E • ANU0207E
ANU0160E An authentication error occurred with ANU0201E File (filename) could not be opened for
password.
User Response: None
ANU0202E Read failure on file (filename).
ANU0161E Authentication error. The password
User Response: None
System Action: Processing stops. ANU0203E Write failure on file (filename).
ANU0162E The passwords entered do not match.

ANU0204E File (filename) could not be closed.
ANU0163E The directory path needs to be

However, this path needs to be fully-qualified. ANU0205E File (filename) statistics could not be
obtained.
ANU0167E The fully-qualified file name is too User Response: None

long.
Explanation: An attempt was made to use a ANU0206E Directory (directory) could not be created.
ANU0200E File (filename) could not be opened for ANU0207E Directory path (directorypath) is too long.
reading.
User Response: None
User Response: None

ANU0208E There is not enough disk space for the
ANU0214E The backup object’s management class
ANU0209E The rename of file (filename1) to
ANU0215E All backup objects do not have the same
User Response: None
destination.
ANU0210E The Tivoli Storage Manager high level
destinations.
User Response: None
ANU0211E The Tivoli Storage Manager low level
ANU0216E Unable to obtain space information for
User Response: None
User Response: None
ANU0212E The Tivoli Storage Manager filespace
name is too long. ANU0217E The Tivoli Storage Manager filespace
name is invalid.
attempt failed.
User Response: None ANU0218E The Tivoli Storage Manager high level
ANU0213E The maximum number of objects System Action: Processing ends.
ANU0219E The Tivoli Storage Manager low level

ANU0256E The password in your Tivoli Storage ANU0261I There are no backups for the server
User Response: None
ANU0263E Failed to start Web browser with a
ANU0257E Your password has expired. User Response: Start your web browser manually and
ANU0264I Could not find the default browser
ANU0258E You did not enter a valid password. System Action: Processing continues.
Processing ends.
ANU0265E Could not find Internet Explorer.
ANU0259E The password you entered for

verification of your new password does not match the ANU0266E Could not find the Tivoli Storage
ANU0260I Password successfully changed. application client code. This will ensure that the
User Response: None

ANU0267E The verify password entered does not ANU366E Unable to close trace output file
match the new password entered. file-name.
Explanation: The verify password does not match the Explanation: An error occurred during the closing of a
new password. trace output file-name (for example, not enough disk
space).
verify password. User Response: Check the options.doc file for a
description of possible causes of the error, or see your
ANU0300E Invalid restore type.
ANU367E Unable to write to trace file tracefile.
System Action: Processing ends. Tracing disabled.
User Response: Re-enter the command specifying a Explanation: An error occurred when writing to the
valid restore type. specified tracefile.
System Action: Tracing is disabled. Processing
ANU0301E Invalid backup type. continues.
Explanation: The type of backup requested is invalid. User Response: Ensure the device that the tracefile
access is available and has sufficient space for the
System Action: Processing ends. tracefile. Retry the command.
valid backup type. ANU368E Invalid trace file name (name too long).
Explanation: A TRACEFILE option in the preferences
ANU0302E A failure occurred on stripe number files used a file name that is too long.
System Action: Client program did not initialize.
Explanation: A failure occurred on the numbered
stripe. User Response: Change the file name used as the
TRACEFILE so that it is equal to or less than 255
System Action: Processing ends. characters in length.
with this one. Refer to the other messages to determine ANU2500E Oracle passed an invalid mode
the problem.
Explanation: Invalid mode passed by Oracle.
ANU351E Invalid trace keyword - ’keyword’ System Action: The system returns to the calling
procedure.
Explanation: A TRACEFLAG option in the user
configuration file or on the command line is incorrect. User Response: Contact your system administrator.
System Action: Client program did not initialize or
tracing was not enabled in the applet. ANU2501E Oracle passed a null file name
User Response: Correct the value. See the entry for Explanation: Null file name passed by Oracle.
TRACEFLAGS in the Trace Facility Guide document for
a list of valid trace flags.
procedure.
ANU357E Unable to open trace output file
file-name.
ANU2502E Wrong data block size
Explanation: A TRACEFILE option in the user
configuration file or on the command line used a Explanation: Wrong data block size.
directory path and file-name combination to which you
do not have write access.
procedure.
System Action: Client program did not initialize.
User Response: Change the TRACEFILE value so that
it is a location to which you have write access.

ANU2503E Object already exists ANU2510E The Caller must be a root user
Explanation: Backup or restore object already exists. Explanation: Only a UNIX root user can execute
password
procedure.
User Response: If backing up an object, make sure
you generate a unique object name. User Response: Contact your system administrator.
ANU2504E Dissimilar Oracle handle ANU2511E Reduce the number of copies to that
specified in RMAN
Explanation: The handle passed from Oracle is not the
same handle that TSM passed back. Explanation: The duplex copy feature has reached
maximum allowed copies.
procedure.
User Response: Reduce the number of backup copies
to that allowed by RMAN.
ANU2505I End of file reached
Explanation: End of file reached.
ANU2512E Could not open license file: license file
Explanation: The license file could not be opened.
procedure.
procedure.
User Response: Check that the license file exists and
ANU2506E Wrong Read State
the permissions are correct.
Explanation: The operation must be in READ state.
System Action: The system returns to the calling ANU2513E Could not read license file: license file
procedure.
Explanation: The license file could not be read.
User Response: Contact TSM support.
procedure.
ANU2507E Runtime API version is outdated
User Response: Check that the license file permissions
Explanation: Runtime API is lower than compile time are correct.
API.
System Action: The system returns to the calling ANU2514E Could not write license file: license file
procedure.
Explanation: The license file could not be written.
User Response: Check compile time API level, obtain
same or higher level of API library.
procedure.
User Response: Check that the license file permissions
ANU2508E Wrong write state
are correct.
System Action: The system returns to the calling ANU2515E Invalid data format in license file: license
procedure. file
User Response: Contact TSM support. Explanation: The license file data format is invalid.
ANU2509E Invalid flag passed procedure.
Explanation: Invalid flag passed from Oracle. User Response: Reinstall the license that came with
TDP for Oracle.
procedure.

ANU2516E Bad checksum of license file: license file ANU2523E The Management Class does not match
Explanation: The license file has a bad checksum. Explanation: The management class for the query
object could not be found.
procedure.
User Response: Reinstall the license that came with
TDP for Oracle. User Response: Contact your system Administrator.
ANU2517E Try and Buy Evaluation period is over ANU2525E Input date does not match expected date
for license file: license file format or range.
Explanation: The Try and Buy Evaluation period is Explanation: The input date does not match the
over. expected date format or range.
User Response: Purchase the product or discontinue User Response: Check that the format and length of
use. the date entry matches TDP_DATE_FORMAT type and
the range of the date values are valid.Valid days are:
1-31Valid months are: 1-12Valid years are:1990-2089
ANU2518E License file: license file not valid for this
application
ANU2529E To Date cannot occur before From Date
Explanation: The license file is not intended for this
application. Explanation: The specified To Date occurs before From
Date.
procedure. System Action: The system returns this error.
User Response: Reinstall the license that came with User Response: Enter a valid To Date that occurs after
TDP for Oracle. the From Date.
ANU2519E Could not read password ANU2530E Screen size is too small for PICK
window.
Explanation: Invalid password or password file not
found. Explanation: You cannot use the PICK on a
workstation that has a screen smaller than 20 characters
across and 10 lines down.
procedure.
System Action: The operation was not completed.
User Response: Check that password file exists and is
valid. User Response: Retry the operation using a
workstation that has a screen with the minimum size.
ANU2521E Error opening file name. Check
permissions. ANU2531E Could not create file for TDPO utility
Explanation: A directory could not be created. Explanation: The temporary file could not be created.
User Response: Check that permissions allow the User Response: Check the status of the filespace.
creation of directories.
ANU2532E Unknown Error - Check TDP for Oracle
ANU2522E No memory error log
Explanation: There is not enough system memory to Explanation: There was an unknown error - check the
complete command. tdpoerror.log.
System Action: The system returns to the calling System Action: None
procedure.
User Response: None
User Response: Free up system resources before
continuing.

ANU2533E SQLPLUS error ANU2539E Function Name: Error - string pointer is

NULL.
Explanation: The utility could not find SQLPLUS or
there was a scripting error. Explanation: A NULL pointer was passed to TDP for
Oracle.
procedure.
User Response: Check that SQLPLUS is installed and
in your search path and verify password. User Response: Contact your system administrator.
ANU2534E Option file error. ANU2571E Could not load the library: tdporacle
library
Explanation: The option or option file name is invalid.
Explanation: Library cannot be loaded.
procedure.
User Response: Check the tdpoerror.log file for an
explanation of the error. User Response: Check that the library exists.
ANU2535I File /fs/hl/ll = number bytes sent ANU2600E There is no Registry entry for the TSM
API.
Explanation: This is the total bytes sent to server for
that file name Explanation: The Windows Registry entry was not
found.
procedure.
User Response: Check the TSM Server activity Log.
User Response: Check that the TSM API is installed
correctly.
ANU2536I File /fs/hl/ll = number bytes recieved
Explanation: This is the total bytes recieved from
ANU2601E There is no Registry entry for TDP for
server for that backup file name.
Oracle install path.
Explanation: The Registry Entry for the TDP for
procedure.
Oracle install path was not found.
User Response: Check the TSM Server activity Log.
procedure.
ANU2537E Error found while parsing options in
User Response: Check that TDP for Oracle was
TDP for Oracle options file.
installed correctly.
Explanation: There was an error found while parsing
the TDP for Oracle options file.
ANU2602E The object Filespace NameHigh Level
System Action: The system returns to the calling NameLow Level Name was not found on
procedure. the TSM Server
User Response: Check that the option file and options Explanation: The object name was not found on the
are valid. TSM Server.
ANU2538E Error found while initializing tracing for procedure.
TDP for Oracle.
User Response: Check that the object name is correct
Explanation: Error found while initializing the TDP and exist on the TSM Server.
for Oracle trace facility.
System Action: The system returns to the calling ANU2603E The option Option Name in file Filename
procedure.
Explanation: A wrong option was passed into the
User Response: Contact your system administrator. TDP for Oracle options file.
procedure.

User Response: Verify that your options are correct in
the TDP for Oracle options file.

Chapter 9. Tivoli Data Protection for R/3 (BKI0000–BKI9999)
This chapter describes the messages issued by Tivoli Data Protection for R/3. The
messages begin with the prefix BKI and are listed in numerical order.
User Response: None

BKI0000E Profile not specified.
Explanation: Tivoli Data Protection for R/3 cannot
BKI0023I Time: current_time
locate the profile.
Done: saved_bytes(percent)of bytes
User Response: Ensure that a profile is available. Estimated end time: end_time
Notice that the BACKINT call must have the following
Explanation: Tivoli Data Protection for R/3 finished
form: backint -p init<SID>.util....
saving a specific object at current_time. The saved_bytes
amount of the total number of bytes have been saved.
BKI0004E Function not defined. percent shows the percentage. This Tivoli Data
Protection for R/3 call will be completed at the
Explanation: SAPDBA, BRBACKUP, or BRARCHIVE
estimated end_time.
passed an invalid argument to Tivoli Data Protection
for R/3. User Response: None
User Response: Ensure that you have the correct
version of SAPDBA, BRBACKUP, or BRARCHIVE BKI0027I Time: current_time
installed. Valid functions are: -f backup or -f restore or -f Objects: current_num of total_num
password or -f delete or -f inquire. in process: file_name
MGMNT-CLASS: management_class
TSM Server: servername.
BKI0005I Start of backint program at:time
Explanation: Tivoli Data Protection for R/3 started
Explanation: Tivoli Data Protection for R/3 received
saving current_num files at current_time. The total
control from SAPDBA, BRBACKUP, BRARCHIVE or
number of files to save is total_num. The file file_name is
BRRESTORE at time.
currently being processed. The files are transferred to
User Response: None the Tivoli Storage Manager server servername, which
stores them in the Management Class management_class.
BKI0006E Type for backup not defined [type]. User Response: None
Please use ’file’ or ’file_online’.
Explanation: Tivoli Data Protection for R/3 expects as BKI0030I Time: current_time
backup type parameter only file or file_online. Objects: current_num of total_num
in process: file_name
User Response: If you start Tivoli Data Protection for Size: bytes MB
R/3 manually to do a backup, ensure that the type TSM Server: servername.
option (-t) receives the correct arguments (file or
file_online). If your Tivoli Data Protection for R/3 has Explanation: Tivoli Data Protection for R/3 completed
been invoked by one of the SAP database utilities (e.g., saving current_num files at current_time. The total
BRBACKUP), ensure that the SAP backup profile number of files to save is total_num. The file file_name is
init<SID>.sap is customized correctly. currently being processed. The Tivoli Storage Manager
server servername is selected.
BKI0020I End of backint program at: time User Response: None
Explanation: Tivoli Data Protection for R/3 returned

control to SAPDBA, BRBACKUP, BRARCHIVE, or BKI0031W Object not found or not accessible:
BRRESTORE at time. objectname.
User Response: none Explanation: The object was not found or is not
accessible to Tivoli Data Protection for R/3.
BKI0021I Elapsed time: elapsedtime User Response: Check path and name and the
permissions of that object and try again.
Explanation: The time needed for the complete
backup was elapsedtime.

BKI0049I • BKI0063E
User Response: None
BKI0049I Please enter password for node nodename
on server servername
BKI0055I Object objectname with size saved with
Explanation: The password for the node nodename on
description description.
the Tivoli Storage Manager server servername has to be
entered for storing it in the Tivoli Data Protection for Explanation: The object objectname was saved
R/3 configuration file. successfully.
User Response: Enter the password for the User Response: None
corresponding Tivoli Storage Manager server.
BKI0056I Object objectname with size restored with

BKI0050I Please enter password for node nodename description description.
on server servername again
Explanation: The object objectname was restored
Explanation: In order to avoid typing errors, you have successfully.
to enter the password twice.
User Response: None
User Response: Enter the password again.
BKI0059E You have to set the environment
BKI0051I Password successfully verified for node variable DSMI_CONFIG to the full
nodename on server servername. filename of the Tivoli Storage Manager
client option file ’dsm.opt’.
the Tivoli Storage Manager server servername was Explanation: Tivoli Storage Manager client option file
changed successfully. not found.
User Response: None User Response: Verify that the Tivoli Storage Manager
option file dsm.opt is pointed to by DSMI_CONFIG.
BKI0052E Password verification for node nodename
on server servername failed. BKI0060E The parameter parameter is not known.
Explanation: The password you entered for the node Explanation: The command parameter parameter for
nodename on the Tivoli Storage Manager server Tivoli Data Protection for R/3 is unknown.
servername was wrong.
User Response: Check the specified command
User Response: Enter the password again. If this error parameter and try again.
still exists, contact your Tivoli Storage Manager
administrator.
BKI0061E The output file filename is not valid.
BKI0053I Time: current_time Explanation: Tivoli Data Protection for R/3 is not able
Objects: current_num of total_num to write the output file filename correctly.
done: file_name with: bytes saved with User Response: Check the path and name of the
description object_desc. output file and the appropriate file access permission.
Explanation: Tivoli Data Protection for R/3 completed
saving current_num file at current_time. The total BKI0062E The input file filename is not valid.
number of files to be saved is total_num. The file
file_name with the size bytes is saved with the Explanation: Tivoli Data Protection for R/3 is not able
description object_desc. to read the input file filename correctly.
User Response: None User Response: Check the path and name of the
output file and the appropriate file access permission.

Objects: current_num of total_num BKI0063E The UTL file filename is not valid.
done: file_name with: bytes Explanation: Tivoli Data Protection for R/3 is not able
restored with description object_desc. to read the input file filename correctly.
Explanation: Tivoli Data Protection for R/3 completed User Response: Check the path and name of the
restoring of current_num file at current_time. The total output file and the appropriate file access permission.
number of files to be restored is total_num. The file
file_name with the size bytes is restored with the
description object_class.

BKI0064E • BKI1003W
BKI0064E The option ’option’ is unknown. BKI0411E Maximum time waiting for BRBACKUP
expired.
Explanation: A Tivoli Data Protection for R/3 option
is invalid or unknown. Explanation: The SAP database utilities did not
respond within the expected time.
User Response: Check the specified option(s) and try
again. User Response: Contact your R/3 administrator.
BKI0065E The argument is missing for option BKI0412E BRBACKUP was not able to switch
’option’. requested tablespace in BEGIN
BACKUP mode.
Explanation: Every Tivoli Data Protection for R/3
option requires an argument. Explanation: Tivoli Data Protection for R/3 could not
continue the backup, because BRBACKUP was not able
User Response: Insert the missing argument and try
to switch the requested tablespace in BEGIN backup
again.
mode. This is necessary for locking the tablespace.
User Response: Contact your R/3 administrator.
BKI0101I Session session: Please enter ’cont’ to
continue or ’stop’ to cancel.
BKI0450I Version 2 restore: file
Explanation: If Tivoli Data Protection for R/3 is
running in unattended mode (profile keyword BATCH), Explanation: A restore of data backed up with Tivoli
it terminates the current run if operator intervention is Data Protection for R/3 version 2 was executed.
required.
User Response: None
User Response: Enter ’cont’ or ’stop’.
BKI1000E Syntax error in line line: ’statement’
BKI0102I Your reply: ’reply’.
Explanation: The statement statement in the Tivoli
Explanation: Tivoli Data Protection for R/3 indicates Data Protection for R/3 profile is unknown or incorrect.
the reply you made.
User Response: Correct the error and try again.
User Response: None
BKI1001E Syntax error in file ’filename’. Exiting
BKI0400I TDP is waiting for BRBACKUP Program.
Explanation: Tivoli Data Protection for R/3 is waiting Explanation: Tivoli Data Protection for R/3 has
for BRBACKUP to set a tablespace in the begin/end detected an syntax error in the file filename and stops
backup mode. any action.
User Response: None User Response: Correct the error(s) in the file filename
and try again.
BKI0405I TDP waited num_sec sec. for
BRBACKUP in util_file_online BKI1002E BACKUPIDPREFIX must be
communication. number_of_characters characters.
Explanation: Tivoli Data Protection for R/3 waited Explanation: The length of BACKUPIDPREFIX must
num_sec seconds for BRBACKUP to set a tablespace in be number_of_characters characters.
begin/end backup mode.
User Response: Enter a BACKUPIDPREFIX with the
User Response: None required length (e.g., SAP___, BKI___).
BKI0410E Cannot open or delete switch file BKI1003W Please set REDOLOG_COPIES to a
’filename’. Check permissions. number between 1 and max_copies. Now
it is set to act_copies.
Explanation: If Tivoli Data Protection for R/3 is not
correctly installed (as the root user on UNIX or Explanation: Tivoli Data Protection for R/3 currently
administrator group on Windows NT) then Tivoli Data supports 1 to 9 copies of offline redo log files.
Protection for R/3 is not able to open the necessary
User Response: Adapt the REDOLOG_COPIES
communication file to the SAP R/3 system.
settings in the Tivoli Data Protection for R/3 profile.
User Response: Check the file permission.
Chapter 9. Tivoli Data Protection for R/3 719

BKI1004W • BKI1015I
BKI1004W You should specify the BKI1010W The configfile name

BACKUPIDPREFIX before the ’configuration_filename’ should be
TRACEFILE statement, so that the absolute.
BACKUPIDPREFIX can be used in the
Explanation: None
tracefile name.
User Response: Specify an absolute filename, for
Explanation: The BACKUPIDPREFIX is used to build
example /oracle/C21/dbs/initC21.bki.
the Name of the tracefile. Therefore,
BACKUPIDPREFIX must be specified before the
TRACEFILE statement. BKI1011W The sortfile name ’sortfile_filename’
should be absolute.
User Response: Define a 6 characters long
BACKUPIDPREFIX in the Tivoli Data Protection for Explanation: None
R/3 profile (e.g., SAP___, BKI___).
User Response: Specify an absolute filename, for
example /oracle/C21/dbs/sortfile.
BKI1005W The tracefile name ’trace_filename’ should
be absolute.
BKI1012E The configfilename
Explanation: None ’configuration_filename’ could not be
opened.
User Response: Specify an absolute tracefile name, for
example /oracle/C21/saptrace/tracefile. Explanation: Tivoli Data Protection for R/3 is unable
to read the file configuration_filename.
BKI1006E The SERVERNAME must be less than User Response: This error could have various reasons,
max_char characters. try the following:
1. Check the path of the configuration file. The path
Explanation: You have used a SERVERNAME with
must be specified in the profile (parameter
more than max_char characters.
CONFIG_FILE).
User Response: Use a shorter SERVERNAME. 2. Make sure, that the file access permission are set
correctly.
BKI1007E The NODENAME must be less than
max_char characters. BKI1013E Profile not found or permissions denied
: ’profile_filename’.
Explanation: You have used a NODENAME with
more than max_char characters. Explanation: Tivoli Data Protection for R/3 is unable
to open the profile profile_filename.
User Response: Use a shorter NODENAME.
User Response: Ensure that the SAP backup profile
init<SID>.sap contains a valid entry util_par_file for
BKI1008E The MANAGEMENTCLASSNAME
the Tivoli Data Protection for R/3 profile. Furthermore,
must be less than max_char characters.
this file must be readable by Tivoli Data Protection for
Explanation: You have used a R/3.
MANAGEMENTCLASSNAME with more than
max_char characters.
BKI1014I The parameter PERF_MONITOR is no
User Response: Use a shorter longer supported. Now it is enabled by
MANAGEMENTCLASSNAME. default.
Explanation: For version 2.7 or later of Tivoli Data
BKI1009W Please set MULTIPLEX to a number Protection for R/3, the Performance Monitor of the
between 1 and max_multiplex. Now it is Administration Assistant can be used by default.
set to act_multiplex. Therefore, the profile parameter PERF_MONITOR is no
longer needed.
Explanation: You have set multiplexing to an
unsupported number. Tivoli Data Protection for R/3 User Response: None
now uses act_multiplex.
User Response: Set multiplexing to a number between BKI1015I The parameter BACKAGENT is no
1 and max_multiplex. longer needed.
Protection for R/3,, only one executable, called
BACKINT, will be provided and needed. The former

BKI1200E • BKI1209E
executable, called BACKAGENT, will no longer
BKI1205E If you want num_redo
supported or needed.
REDOLOGCOPIES on Tivoli Storage
User Response: None Manager-Server servername, you should
give me at least num_mc different
Archive Management Classes.
BKI1200E Can’t read/write file: filename.
Explanation: Tivoli Data Protection for R/3 requires
Explanation: Tivoli Data Protection for R/3 is unable that the number of different Archive Management
to read or write a datafile (filename) of a tablespace Classes (parameter BRARCHIVEMGTCLASS) on the
being backed up or restored. Tivoli Storage Manager servers is equal to or greater
User Response: Check the file access permission of than the number of redo log copies (parameter
the affected file(s). Try again. If the problem still exists, REDOLOG_COPIES).
contact the SAP R/3 administrator. User Response: Define at least as many different
Archive Management Classes as redo log copies
BKI1201E There are no Tivoli Storage requested.
Manager-Servers available.
Explanation: Tivoli Data Protection for R/3 cannot BKI1206W If you want num_redo
locate a Tivoli Storage Manager server. REDOLOGCOPIES on Tivoli Storage
Manager-Server servername, you should
User Response: Install and specify at least one Tivoli give me at least num_mc different
Storage Manager server in the Tivoli Data Protection Archive Management Classes.
for R/3 profile (keyword SERVER).
Explanation: The message appears during a
BRBACKUP run. A BRARCHIVE run afterwards would
BKI1202E You must specify either be failed.
MAX_SESSIONS or all off
MAX_ARCH_SESSIONS, User Response: Define at least as many different
MAX_BACK_SESSIONS and Archive Management Classes as redo log copies
MAX_RESTORE_SESSIONS requested.
Explanation: There is a setup error with the

SESSIONS parameters within the Tivoli Data Protection BKI1207E Directory backup not supported
for R/3 profile. Explanation: This option is not yet available.
User Response: Specify either MAX_SESSIONS and User Response: Wait for a future release of Tivoli Data
one of the more specific parameters Protection for R/3, which supports this option.
MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS or
MAX_RESTORE_SESSIONS or all of the three specific
session parameters without the MAX_SESSIONS BKI1208E The object ’filename’ will be retried
parameter. [retry_num]
Explanation: There was an error with the object
BKI1203E Not enough sessions available (number file_name. Tivoli Data Protection for R/3 will try to
of sessions required and number of save/restore the object one retry_num times.
sessions available).
User Response: Look at the error messages in the
Explanation: The sum of available sessions specified Tivoli Data Protection for R/3 protocol and solve the
in the various server statements (parameter SESSIONS) error for the next run.
does not cover the required number of sessions
(parameter MAX_SESSIONS).
BKI1209E Object not found or not accessible
User Response: Change the values of the ’objectname’.
corresponding parameters in the Tivoli Data Protection
for R/3 profile, so that the condition mentioned in the
locate the Oracle object objectname.
explanation is fulfilled.
User Response: The backup integrity is affected.
Contact the SAP or Tivoli Data Protection for R/3
support.

if Prole is still running and try again.
BKI1210E Input file not found or not accessible
’filename’.
BKI2005E Illegal parameter in message from Prole.
Exiting...
locate the temporary file filename. This file contains the
list of Oracle objects to be backed up/restored. It is Explanation: This error occurs if the version of Prole
passed to Tivoli Data Protection for R/3 by and of the executable BACKINT or the backup library
BRBACKUP, BRARCHIVE or BRRESTORE. libtdp_r3 does not match.
User Response: Ensure, that you have the correct User Response: Check the version of Prole and
version of SAPDBA, BRBACKUP, BRARCHIVE or BACKINT/backup library libtdp_r3 you are currently
BRRESTORE installed. using.
BKI1211E There is something wrong with your BKI2006E General exception in dispatcher.
CONFIG_FILE ’filename’. Exiting...
Explanation: There is a problem with your Tivoli Data Explanation: Internal Tivoli Data Protection for R/3
Protection for R/3 configuration file setup. error.
User Response: Check the file permission and the User Response: Contact the Tivoli Data Protection for
filename specified in the Tivoli Data Protection for R/3 R/3 support.
profile keyword CONFIG_FILE.
BKI2007E Unknown Port: port

BKI2000I Successfully connected to PROLE on
port portnumber. Explanation: The port specified for the communication
between Prole and Backint is unknown.
Explanation: One of the Tivoli Data Protection for R/3
modules BACKINT or the backup library libtdp_r3 User Response: Check the port value specified when
initiated a successful connection to the background Prole was started. Additionally, check the environment
process Prole on port portnumber. variable PROLE_PORT for the Backint environment.
These two values must match.
User Response: None
BKI2008E Unable to connect to PROLE.

BKI2001E Socket error while connecting to
PROLE: reason. Explanation: Internal Tivoli Data Protection for R/3
error.
Explanation: The Tivoli Data Protection for R/3
background process Prole is not running. User Response: Contact the Tivoli Data Protection for
R/3 support.
User Response: Start Prole manually and try again.
BKI2009I Deleting all versions with version
BKI2002E No valid callback function of type Number <= version_number.
fkt_type supplied.
Explanation: All full database backups and their
Explanation: Internal Tivoli Data Protection for R/3 corresponding redo log backups will be deleted from
error Tivoli Storage Manager storage, if their version number
is less than or equal to version_number.
User Response: Contact the Tivoli Data Protection for
R/3 support. User Response: None
BKI2003I File file_name, BID deleted. BKI2010E Error occurred processing FRONTEND
Explanation: The file file_name with the backup ID Explanation: An error occurred during the frontend
BID was deleted from the Tivoli Storage Manager. processing.
User Response: None User Response: Check the frontend script/program
and the settings in the Tivoli Data Protection for R/3
profile (keyword FRONTEND) and try again.
BKI2004E Connection to PROLE lost.
Explanation: During Tivoli Data Protection for R/3
operation the connection to Prole was lost. Network
problems could be the reason.
User Response: Check your network environment and

BKI2011E Error occurred processing BACKEND. BKI4001E File ’filename’ cannot be created. Reason:
errno (error_num) error_desc.
Explanation: An error occurred during the backend
processing. Explanation: The file filename to be restored could not
be created/written. It is possible, that you do not have
User Response: Check the backend script/program
the appropriate rights for writing the file filename to the
destination path.
profile (keyword BACKEND) and try again.
User Response: Check the error number error_num
and the error description error_desc to avoid this
BKI2012E Passwords do not match. Try again.
problem in the future. Furthermore, check the write
Explanation: The first and second password you permission of the user who started the restore.
entered do not match.
User Response: Enter the password correctly. BKI4002E Error during restore of file ’filename’.
Reason: errno (error_num) error_desc.
BKI2013I Starting FRONTEND Program. Explanation: An error occurs during the restore
process of the file filename.
Explanation: The frontend program is executing.
User Response: None and the error description error_desc to avoid this
problem in the future.
BKI2014I FRONTEND program finished.
Explanation: The frontend program is finished. BKI4003E Error reading file filename. Only read
num_bytes out of all_bytes.
User Response: None
Explanation: An error occurs reading the file filename.
Only num_bytes of all_bytes could be read.
BKI2015I Starting BACKEND program.
User Response: Try your last action again. If the error
Explanation: The backend program is executing. still exists please contact the Tivoli Data Protection for
User Response: None R/3 support.
BKI2016I BACKEND program finished. BKI4004E Error writing file filename. Only wrote
Explanation: The backend program is finished.
Explanation: An error occurs writing the file filename.
User Response: None Only num_bytes of all_bytes could be written.
BKI2017I Blocksize is set to num_bytes bytes. still exists please contact the Tivoli Data Protection for
Explanation: The operational blocksize of Tivoli Data R/3 support.
Protection for R/3 is num_bytes bytes.
User Response: None BKI5000E Tivoli Storage Manager Error:
error_message
BKI4000W The attributes of file ’filename’ cannot be Explanation: During a connection of Tivoli Data
restored. Reason: errno (error_num) Protection for R/3 to Tivoli Storage Manager server, a
error_desc. Tivoli Storage Manager error error_message occurred.
Explanation: The file filename was restored User Response: Use the Tivoli Storage Manager
successfully but one or more file attributes (permission, Messages guide and correct the Tivoli Storage Manager
ownership, date/time) of the file filename cannot be server error. Try your last action again.
restored correctly.
User Response: Check the error number error_num BKI7001E Backup file ’filename’ already exists.
and the error description error_desc to avoid this Explanation: This is an RMAN internal error.
problem in the future. An initial solution could be to
set the appropriate correct permission for the file User Response: See your Oracle documentation or
filename manually. contact your Oracle database administrator.

BKI7002E Bad mode specified.

Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or
contact your Oracle database administrator.
BKI7009E Cannot connect to media manager.

Explanation: Tivoli Data Protection for R/3 is not able
to connect to the Tivoli Storage Manager server.
User Response: Check the Tivoli Storage Manager API
environment variables DSMI_DIR and DSMI_CONFIG.
BKI7010E Permission denied.

Explanation: The permission for a connection to the
Tivoli Storage Manager server are not valid.
User Response: Check your Tivoli Storage Manager
client (API client) permission. For further information
contact your Tivoli Storage Manager administrator.
BKI7012E Invalid arguments during call of

’function’.
BKI7020E Bad handle ’rman_handle’ during call of

’function’.
BKI7021E Bad flags during call of ’function’.

BKI9000E System error: error

Explanation: Tivoli Data Protection for R/3 has found
the following error: error. This is a ’catch_all’ error code
for unpredictable system errors.
User Response: Contact your system representative.
BKI9001E Internal error: error

the following internal error: error.
R/3 support.

Chapter 10. Tivoli Data Protection for R/3 File Manager
This chapter contains messages issued by TDP for R/3 File Manager. These
messages have no message identifier.
User Response: Please inform your system

Backint not found!
administrator or the Tivoli Data Protection for R/3
Explanation: The executable BACKINT was not found. support about this problem.
This executable is necessary to run Tivoli Data
Protection for R/3 File Manager.
User Response: Make sure backfm is installed in the
same directory as backint and has the same permission.
Profile not specified. Please use 'backfm -p

<ParFileName>' !
Explanation: Since Tivoli Data Protection for R/3 File
Manager calls Tivoli Data Protection for R/3, the profile
for Tivoli Data Protection for R/3 is required.
User Response: Specify the full file name of the Tivoli
Data Protection for R/3 profile when starting Tivoli
Data Protection for R/3 File Manager, for example:
backfm -p /oracle/C21/dbs/initC21.utl.
Backint call was not successful!

Explanation: The communication with the Tivoli
Storage Manager server failed.
User Response: Check that Tivoli Data Protection for
R/3 and the Tivoli Storage Manager server(s) work
correctly. It must be possible to run Tivoli Data
Protection for R/3 directly from the command line,
otherwise Tivoli Data Protection for R/3 File Manager
will also not work.
Cannot open temporary file!

Explanation: A temporary file could not be opened.
This could have several reasons.
User Response:
UNIX Make sure the directory /tmp is not full and
you have write permission for this directory.
NT Make sure that the current drive is not full.
Unable to allocate memory!

Unable to install SIGWINCH-handler!
Unable to remove Backup IDs!
Unable to install SIGINT-handler!
Can’t get window size!
Explanation: These error messages indicate problems
which usually cannot be resolved by the users
themselves.

Chapter 11. Tivoli Data Protection for R/3 for DB2 UDB
(BKI0000–BKI9999)
This chapter describes the messages issued by Tivoli Data Protection for R/3 for
DB2 UDB. The messages begin with the prefix BKI and are listed in numerical
order.
BKI0000E Profile not specified. BKI0021I Elapsed time: elapsedtime

Explanation: Tivoli Data Protection for R/3 cannot Explanation: The time needed for the complete
locate the profile. backup was elapsedtime.
User Response: Ensure that a profile is available. User Response: None
BKI0004E Function not defined. Estimated end time: end_time
Explanation: SAPDBA, BRBACKUP, or BRARCHIVE Explanation: Tivoli Data Protection for R/3 finished
passed an invalid argument to Tivoli Data Protection saving a specific object at current_time. The saved_bytes
for R/3. amount of the total number of bytes have been saved.
percent shows the percentage. This Tivoli Data
version of SAPDBA, BRBACKUP, or BRARCHIVE
estimated end_time.
installed. Valid functions are: -f backup or -f restore or -f
password or -f delete or -f inquire. User Response: None
BKI0005I Start of backint program at:time BKI0024I Return code is: return code
Explanation: Tivoli Data Protection for R/3 received Explanation: Shows the return code of Tivoli Data
control from SAPDBA, BRBACKUP, BRARCHIVE or Protection for R/3. A return code of 0 means no errors
BRRESTORE at time. or warnings occurred. If the return code is 1, at least
one warning was issued by the program. If the return
User Response: None
code is 2, at least one error message was issued.
User Response: For return codes other than 0, check
BKI0006E Type for backup not defined [type].
the run log for warnings or error messages.
Explanation: Tivoli Data Protection for R/3 expects as
backup type parameter only file or file_online.
Objects: current_num of total_num
User Response: If you start Tivoli Data Protection for in process: file_name
R/3 manually to do a backup, ensure that the type MGMNT-CLASS: management_class
option (-t) receives the correct arguments (file or TSM Server: server name.
file_online). If your Tivoli Data Protection for R/3 has
been invoked by one of the SAP database utilities (e.g.,
BRBACKUP), ensure that the SAP backup profile
init<SID>.sap is customized correctly.
the Tivoli Storage Manager server server name, which
BKI0020I End of backint program at: time stores them in the Management Class management_class.
Explanation: Tivoli Data Protection for R/3 returned User Response: None
control to SAPDBA, BRBACKUP, BRARCHIVE, or
BRRESTORE at time.
User Response: none

BKI0030I • BKI0056I
BKI0030I Time: current_time BKI0051I Password successfully verified for node

Objects: current_num of total_num nodename on server server name.
Size: bytes MB
the Tivoli Storage Manager server server name was
TSM Server: server name.
changed successfully.
User Response: None
currently being processed. The Tivoli Storage Manager BKI0052E Password verification for node nodename
server server name is selected. on server server name failed.
User Response: None Explanation: The password you entered for the node
nodename on the Tivoli Storage Manager server server
name was wrong.
BKI0031W Object not found or not accessible:
objectname. User Response: Enter the password again. If this error
Explanation: The object was not found or is not
administrator.
User Response: Check path and name and the
done: file_name with: bytes saved with
BKI0032E Error opening file file name: system error description object_desc.
description
Explanation: A system error occurred during opening saving current_num file at current_time. The total
of the file file name. system error description will describe number of files to be saved is total_num. The file
the error in more detail. file_name with the size bytes is saved with the
description object_desc.
User Response: Read the system error description.
User Response: None
BKI0033E Error opening file file name: system error
description BKI0054I Time: current_time
Explanation: See BKI0032E.
done: file_name with: bytes
User Response: See BKI0032E. restored with description object_desc.
BKI0049I Please enter password for node nodename restoring of current_num file at current_time. The total
on server server name number of files to be restored is total_num. The file
Explanation: The password for the node nodename on description object_class.
the Tivoli Storage Manager server server name has to be
entered for storing it in the Tivoli Data Protection for User Response: None
R/3 configuration file.
User Response: Enter the password for the BKI0055I Object objectname with size saved with
corresponding Tivoli Storage Manager server. description description.
Explanation: The object objectname was saved
BKI0050I Please enter password for node nodename successfully.
on server server name again
User Response: None
Explanation: In order to avoid typing errors, you have
User Response: Enter the password again. description description.
successfully.
User Response: None

BKI0059E You have to set the environment BKI0101I Session session: Please enter ’cont’ to
variable DSMI_CONFIG to the full continue or ’stop’ to cancel.
filename of the Tivoli Storage Manager
running in unattended mode (profile keyword BATCH),
Explanation: Tivoli Storage Manager client option file it terminates the current run if operator intervention is
not found. required.
User Response: Verify that the Tivoli Storage Manager User Response: Enter ’cont’ or ’stop’.
BKI0060E The parameter parameter is not known.
Explanation: Tivoli Data Protection for R/3 indicates
Explanation: The command parameter parameter for the reply you made.
Tivoli Data Protection for R/3 is unknown.
User Response: None
parameter and try again.
BKI0400I TDP is waiting for BRBACKUP
Explanation: Tivoli Data Protection for R/3 is waiting
BKI0061W The output file file name is not valid.
for BRBACKUP to set a tablespace in the begin/end
Explanation: The specified output file file name could backup mode.
not be created.
User Response: None
User Response: Check that file name is a valid file
name on your operating system. Also check that the
application has the appropriate permissions to create
BRBACKUP in util_file_online
the file within the specified directory. The directory
communication.
must already exist. If the file already exists, rename the
old one. Explanation: Tivoli Data Protection for R/3 waited
num_sec seconds for BRBACKUP to set a tablespace in
BKI0062E The input file file name is not valid.
User Response: None
to read the input file file name correctly.
BKI0410E Cannot open or delete switch file ’file
User Response: Check the path and name of the
name’. Check permissions.
correctly installed (as the root user on UNIX or
BKI0063E The UTL file file name is not valid.
administrator group on Windows NT) then Tivoli Data
Explanation: Tivoli Data Protection for R/3 is not able Protection for R/3 is not able to open the necessary
to read the input file file name correctly. communication file to the SAP R/3 system.
User Response: Check the path and name of the User Response: Check the file permission.
BKI0411E Maximum time waiting for BRBACKUP
BKI0064E The option ’option’ is unknown. expired.
Explanation: A Tivoli Data Protection for R/3 option Explanation: The SAP database utilities did not
is invalid or unknown. respond within the expected time.
User Response: Check the specified option(s) and try User Response: Contact your R/3 administrator.
again.
BKI0412E BRBACKUP was not able to switch
BKI0065E The argument is missing for option requested tablespace in BEGIN
’option’. BACKUP mode.
Explanation: Every Tivoli Data Protection for R/3 Explanation: Tivoli Data Protection for R/3 could not
option requires an argument. continue the backup, because BRBACKUP was not able
again.
Chapter 11. Tivoli Data Protection for R/3 for DB2 UDB 729
BKI0450I • BKI1007E
BKI0450I Version 2 restore: file BKI1000E Syntax error in line line: ’statement’
Explanation: A restore of data backed up with Tivoli Explanation: The statement statement in the Tivoli
Data Protection for R/3 version 2 was executed. Data Protection for R/3 profile is unknown or incorrect.
User Response: None User Response: Correct the error and try again.
BKI0451I This version of Tivoli Data Protection BKI1001E Syntax error in file ’file name’. Exiting
for R/3 will expire on ’date’. Program.
Explanation: This is a test version that will expire on Explanation: Tivoli Data Protection for R/3 has
’date’. detected an syntax error in the file file name and stops
any action.
User Response: Correct the error(s) in the file file name
and try again.
BKI0452E This version of Tivoli Data Protection
for R/3 has expired.
BKI1002E BACKUPIDPREFIX must be
Explanation: This is a test version that has expired.
number_of_characters characters.
User Response: Order a release version of Tivoli Data
Explanation: The length of BACKUPIDPREFIX must
Protection for R/3 or contact your IBM/Tivoli Sales
be number_of_characters characters.
Representative.
required length (e.g., SAP___, BKI___).
BKI0453W This version of Tivoli Data Protection
for R/3 will expire in ’number’ days.
BKI1004W You should specify the
Explanation: This is a test version with a time limit. It
BACKUPIDPREFIX before the
will expire in ’number’ days.
TRACEFILE statement, so that the
User Response: Order a release version of Tivoli Data BACKUPIDPREFIX can be used in the
Protection for R/3 or contact your IBM/Tivoli Sales tracefile name.
Representative before the version expires.
BKI0454I *** This copy is NOT FOR RESALE. *** BACKUPIDPREFIX must be specified before the
TRACEFILE statement.
Explanation: This version is not for resale.
User Response: None. BACKUPIDPREFIX in the Tivoli Data Protection for
BKI0455E License file ’file name’ does not exist.
Explanation: The license file ’agent.lic’ was not found BKI1005W The tracefile name ’trace_filename’ should
where expected. be absolute.
User Response: Make sure that the ’agent.lic’ file Explanation: None
resides in the same directory as the init<SID>.utl file. User Response: Specify an absolute tracefile name, for
example /db2/C21/saptrace/tracefile.
BKI0456E Unable to access license file ’file name’.
Explanation: Unable to access license file. BKI1006E The SERVERNAME must be less than
User Response: Make sure the access permissions
allow read/write access. Explanation: You have used a SERVERNAME with
BKI0457E License file file name contains invalid User Response: Use a shorter SERVERNAME.
data/checksum.
Explanation: The license file is invalid. BKI1007E The NODENAME must be less than
User Response: Make sure you have the right
agent.lic file for the right platform installed. ’agent.lic’ Explanation: You have used a NODENAME with
files are platform dependent. more than max_char characters.

Administration Assistant can be used by default.
BKI1008E The MANAGEMENTCLASSNAME
Therefore, the profile parameter PERF_MONITOR is no
longer needed.
Explanation: You have used a
User Response: None
MANAGEMENTCLASSNAME with more than
BKI1015I The parameter BACKAGENT is no
User Response: Use a shorter
longer needed.
MANAGEMENTCLASSNAME.
Protection for R/3,, only one executable, called
BKI1009W Please set MULTIPLEX to a number
between 1 and max_multiplex. Now it is
set to act_multiplex.
supported or needed.
User Response: None
unsupported number. Tivoli Data Protection for R/3
now uses act_multiplex.
BKI1016W The trace file name ’file name’ could not
User Response: Set multiplexing to a number between
be opened for writing!
1 and max_multiplex.
Explanation: The trace file could not be opened for
writing.
BKI1010W The configfile name
’configuration_filename’ should be User Response: Ensure that you have specified a
absolute. correct path for the trace file.
Explanation: None
BKI1017E The server ’server name’ is already
User Response: Specify an absolute file name, for
defined. Please use another name!
example /db2/C21/dbs/initC21.bki.
Explanation: The server you want to configure is
already defined.
BKI1012E The configfilename
’configuration_filename’ could not be User Response: Specify another server name. Server
opened. names have to be unique.
Explanation: Tivoli Data Protection for R/3 is unable
to read the file configuration_filename. BKI1200E Can’t read/write file: file name.
User Response: This error could have various reasons, Explanation: Tivoli Data Protection for R/3 is unable
try the following: to read or write a datafile (file name) of a tablespace
1. Check the path of the configuration file. The path being backed up or restored.
CONFIG_FILE). User Response: Check the file access permission of
2. Make sure, that the file access permission are set the affected file(s). Try again. If the problem still exists,
correctly. contact the SAP R/3 administrator.
BKI1013E Profile not found or permissions denied BKI1201E There are no Tivoli Storage
: ’profile_filename’. Manager-Servers available.
Explanation: Tivoli Data Protection for R/3 is unable Explanation: Tivoli Data Protection for R/3 cannot
to open the profile profile_filename. locate a Tivoli Storage Manager server.
User Response: Ensure that the SAP backup profile User Response: Install and specify at least one Tivoli
init<SID>.sap contains a valid entry util_par_file for Storage Manager server in the Tivoli Data Protection
the Tivoli Data Protection for R/3 profile. Furthermore, for R/3 profile (keyword SERVER).
R/3. BKI1203E Not enough sessions available (number
of sessions required and number of
BKI1014I The parameter PERF_MONITOR is no sessions available).
longer supported. Now it is enabled by Explanation: The sum of available sessions specified
default. in the various server statements (parameter SESSIONS)
Explanation: For version 2.7 or later of Tivoli Data does not cover the required number of sessions
Protection for R/3, the Performance Monitor of the (parameter MAX_SESSIONS).
User Response: Change the values of the
BKI1216E There are no BRBACKUPMGTCLASSES
corresponding parameters in the Tivoli Data Protection
available.
for R/3 profile, so that the condition mentioned in the
explanation is fulfilled. Explanation: The BRBACKUPMGTCLASSES you have
specified in your init<SID>.utl file are not correct.
BKI1207E Directory backup not supported User Response: Check the management classes on the
TSM server and specify correct ones.
Explanation: This option is not yet available.
User Response: Wait for a future release of Tivoli Data
BKI1217E There are no
Protection for R/3, which supports this option.
BRARCHIVEMGTCLASSES available.
Explanation: The BRARCHIVEMGTCLASSES you
BKI1208E The object ’file name’ will be retried
have specified in your init<SID>.utl file are not correct.
[retry_num]
User Response: Check the management classes on the
Explanation: There was an error with the object
file_name. Tivoli Data Protection for R/3 will try to
save/restore the object one retry_num times.
BKI2000I Successfully connected to PROLE on
User Response: Look at the error messages in the
port portnumber.
Tivoli Data Protection for R/3 protocol and solve the
error for the next run. Explanation: One of the Tivoli Data Protection for R/3
modules BACKINT or the backup library libtdp_r3
initiated a successful connection to the background
process Prole on port portnumber.
’objectname’.
User Response: None
locate the DB2 object objectname.
BKI2001E Socket error while connecting to
User Response: The backup integrity is affected.
PROLE: reason.
Contact the SAP or Tivoli Data Protection for R/3
support. Explanation: The Tivoli Data Protection for R/3
background process Prole is not running.
BKI1211E There is something wrong with your User Response: Start Prole manually and try again.
CONFIG_FILE ’file name’.
Explanation: There is a problem with your Tivoli Data BKI2002E No valid callback function of type
Protection for R/3 configuration file setup. fkt_type supplied.
User Response: Check the file permission and the file Explanation: Internal Tivoli Data Protection for R/3
name specified in the Tivoli Data Protection for R/3 error
profile keyword CONFIG_FILE.
R/3 support.
BKI1213I Program ended with code = ’return code’
Explanation: The return code of the program is BKI2003I File file_name, BID deleted.
displayed.
Explanation: The file file_name with the backup ID
User Response: None. BID was deleted from the Tivoli Storage Manager.
User Response: None
BKI1214E TSM Error: ’error text’
Explanation: The specified TSM error occurred. BKI2004E Connection to PROLE lost.
User Response: Check error text and correct the Explanation: During Tivoli Data Protection for R/3
problem. operation the connection to Prole was lost. Network
BKI1215I Average transmission rate was ’number’ User Response: Check your network environment and
GB/h (’number’ MB/sec). if Prole is still running and try again.
Explanation: The average transmission rate is
displayed.

profile (keyword BACKEND) and try again.
Exiting...
BKI2012E Passwords do not match. Try again.
Explanation: This error occurs if the version of Prole
and of the executable BACKINT or the backup library Explanation: The first and second password you
libtdp_r3 does not match. entered do not match.
User Response: Check the version of Prole and User Response: Enter the password correctly.
BACKINT/backup library libtdp_r3 you are currently
using.
BKI2013I Starting FRONTEND Program.
BKI2006E General exception in dispatcher. Explanation: The frontend program is executing.

Exiting... User Response: None
Explanation: Internal Tivoli Data Protection for R/3
error. BKI2014I FRONTEND program finished.
User Response: Contact the Tivoli Data Protection for Explanation: The frontend program is finished.
R/3 support.
User Response: None
BKI2007E Unknown Port: port

Explanation: The port specified for the communication
between Prole and Backint is unknown. Explanation: The backend program is executing.
User Response: Check the port value specified when User Response: None
Prole was started. Additionally, check the environment
variable PROLE_PORT for the Backint environment. BKI2016I BACKEND program finished.
These two values must match.
BKI2008E Unable to connect to PROLE. User Response: None

error. BKI2017I Blocksize is set to num_bytes bytes.
User Response: Contact the Tivoli Data Protection for Explanation: The operational blocksize of Tivoli Data
R/3 support. Protection for R/3 is num_bytes bytes.
User Response: None
BKI2009I Deleting all versions with version
Number <= version_number. BKI2018E Exception in main message loop:
Explanation: All full database backups and their ’description’
corresponding redo log backups will be deleted from Explanation: An error occurred during processing.
Tivoli Storage Manager storage, if their version number The error may contain a descriptive text.
User Response: None
BKI2019E Socket error while connecting to Prole

BKI2010E Error occurred processing FRONTEND on port ’number’ for tracing: ’description’
Explanation: An error occurred during the frontend Explanation: During processing, a socket error
processing. occurred on port ’number’. ’description’ may contain the
User Response: Check the frontend script/program system error text.
and the settings in the Tivoli Data Protection for R/3 User Response: Check the ’description’. If the error
profile (keyword FRONTEND) and try again. persists, contact your service representative.
BKI2011E Error occurred processing BACKEND. BKI2020E Error occurred for trace connection to
Explanation: An error occurred during the backend Prole on port ’number’.
processing. Explanation: The network connection that is used for
User Response: Check the backend script/program tracing generated an error on port ’number’.
User Response: Contact your service representative. User Response: Check the error number error_num
BKI2021E Unable to delete file ’file name’:
’description’
BKI4003E Error reading file file name. Only read
Explanation: Unable to delete the file ’file name’.
’description’ may contain the system error text.
Explanation: An error occurs reading the file file name.
User Response: Check the ’description’. If the error
still exists please contact the Tivoli Data Protection for
BKI2022E Unable to change mode of file ’file
R/3 support.
name’: ’description’
Explanation: Unable to change mode of file ’file name’.
BKI4004E Error writing file filename. Only wrote
Explanation: An error occurs writing the file file name.
Only num_bytes of all_bytes could be written.
BKI2023E Error occurred during trace connection
to Prole. Tracing will stop now.
R/3 support.
Explanation: Error occurred during trace connection
to Prole.
BKI4005E Error allocating memory block for file
User Response: Tracing will stop. If the problem file name. BLOCKSIZE may be too large.
Explanation: Tivoli Data Protection for R/3 was not
able to request new memory blocks during the backup
BKI4000W The attributes of file ’file name’ cannot of file file name.
be restored. Reason: errno (error_num)
User Response: Verify that you have set a valid value
error_desc.
for BLOCKSIZE. If you are not sure what value is
Explanation: The file file name was restored valid, comment it out so the default value is used.
successfully but one or more file attributes (permission, Furthermore, you can check if you have enough RAM
ownership, date/time) of the file file name cannot be available with your machine. Also, check the memory
restored correctly. usage during backup. It may be necessary to stop
another application, increase memory, or change the
User Response: Check the error number error_num configuration of Tivoli Data Protection for R/3.
set the appropriate correct permission for the file file BKI4006E Error allocating memory block for file
name manually. file name. BLOCKSIZE may be too large.
BKI4001E File ’file name’ cannot be created. Reason:
User Response: See BKI4005E.
Explanation: The file file name to be restored could not
BKI5000E Tivoli Storage Manager Error:
error_message
the appropriate rights for writing the file file name to
the destination path. Explanation: During a connection of Tivoli Data
Protection for R/3 to Tivoli Storage Manager server, a
Tivoli Storage Manager error error_message occurred.
problem in the future. Furthermore, check the write User Response: Use the Tivoli Storage Manager
permission of the user who started the restore. Messages guide and correct the Tivoli Storage Manager
server error. Try your last action again.
BKI4002E Error during restore of file ’file name’.
Reason: errno (error_num) error_desc.
Explanation: An error occurs during the restore
process of the file file name.

BKI5001E Tivoli Storage Manager Error: BKI5010E Tivoli Storage Manager Error:
error_message error_message
Explanation: See BKI5000E. Explanation: See BKI5000E.
User Response: See BKI5000E. User Response: See BKI5000E.
BKI5002E Tivoli Storage Manager Error: BKI5011E Tivoli Storage Manager Error:
error_message error_message
Explanation: See BKI5000E. Explanation: See BKI5000E.
User Response: See BKI5000E. User Response: See BKI5000E.
BKI5003E Tivoli Storage Manager Error: BKI7009E Cannot connect to media manager.
error_message
Explanation: See BKI5000E. to connect to the Tivoli Storage Manager server.
User Response: See BKI5000E. User Response: Check the Tivoli Storage Manager API
error_message BKI7010E Permission denied.
Explanation: See BKI5000E. Explanation: The permission for a connection to the
error_message
the following error: error. This is a ’catch_all’ error code
BKI5006E Tivoli Storage Manager Error: for unpredictable system errors.
error_message
User Response: See BKI5000E. BKI9001E Internal error: error
BKI5007E Tivoli Storage Manager Error: the following internal error: error.
error_message
Explanation: See BKI5000E. R/3 support.

error_message

error_message
Chapter 12. Tivoli Data Protection for R/3 for Oracle
(BKI0000–BKI9999)
This chapter describes the messages issued by Tivoli Data Protection for R/3 for
Oracle. The messages begin with the prefix BKI and are listed in numerical order.
BKI0000E Profile not specified. BKI0021I Elapsed time: elapsedtime

Explanation: Tivoli Data Protection for R/3 cannot Explanation: The time needed for the complete
locate the profile. backup was elapsedtime.
User Response: Ensure that a profile is available. User Response: None
BKI0004E Function not defined. Estimated end time: end_time
Explanation: SAPDBA, BRBACKUP, or BRARCHIVE Explanation: Tivoli Data Protection for R/3 finished
passed an invalid argument to Tivoli Data Protection saving a specific object at current_time. The saved_bytes
for R/3. amount of the total number of bytes have been saved.
percent shows the percentage. This Tivoli Data
version of SAPDBA, BRBACKUP, or BRARCHIVE
estimated end_time.
installed. Valid functions are: -f backup or -f restore or -f
password or -f delete or -f inquire. User Response: None
BKI0005I Start of backint program at:time BKI0024I Return code is: return code
Explanation: Tivoli Data Protection for R/3 received Explanation: Shows the return code of Tivoli Data
control from SAPDBA, BRBACKUP, BRARCHIVE or Protection for R/3. A return code of 0 means no errors
BRRESTORE at time. or warnings occurred. If the return code is 1, at least
one warning was issued by the program. If the return
User Response: None
code is 2, at least one error message was issued.
BKI0006E Type for backup not defined [type].
Explanation: Tivoli Data Protection for R/3 expects as
backup type parameter only file or file_online.
User Response: If you start Tivoli Data Protection for in process: file_name
R/3 manually to do a backup, ensure that the type MGMNT-CLASS: management_class
option (-t) receives the correct arguments (file or TSM Server: server name.
file_online). If your Tivoli Data Protection for R/3 has
been invoked by one of the SAP database utilities (e.g.,
BRBACKUP), ensure that the SAP backup profile
init<SID>.sap is customized correctly.
the Tivoli Storage Manager server server name, which
BKI0020I End of backint program at: time stores them in the Management Class management_class.
Explanation: Tivoli Data Protection for R/3 returned User Response: None
control to SAPDBA, BRBACKUP, BRARCHIVE, or
BRRESTORE at time.
User Response: none

BKI0030I • BKI0056I
BKI0030I Time: current_time BKI0051I Password successfully verified for node

Objects: current_num of total_num nodename on server server name.
Size: bytes MB
changed successfully.
User Response: None
currently being processed. The Tivoli Storage Manager BKI0052E Password verification for node nodename
server server name is selected. on server server name failed.
User Response: None Explanation: The password you entered for the node
nodename on the Tivoli Storage Manager server server
name was wrong.
BKI0031W Object not found or not accessible:
objectname. User Response: Enter the password again. If this error
administrator.
done: file_name with: bytes saved with
BKI0032E Error opening file file name: system error description object_desc.
description
Explanation: A system error occurred during opening saving current_num file at current_time. The total
of the file file name. system error description will describe number of files to be saved is total_num. The file
the error in more detail. file_name with the size bytes is saved with the
description object_desc.
User Response: Read the system error description.
User Response: None
BKI0033E Error opening file file name: system error
description BKI0054I Time: current_time
done: file_name with: bytes
User Response: See BKI0032E. restored with description object_desc.
BKI0049I Please enter password for node nodename restoring of current_num file at current_time. The total
on server server name number of files to be restored is total_num. The file
Explanation: The password for the node nodename on description object_class.
the Tivoli Storage Manager server server name has to be
entered for storing it in the Tivoli Data Protection for User Response: None
R/3 configuration file.
User Response: Enter the password for the BKI0055I Object objectname with size saved with
corresponding Tivoli Storage Manager server. description description.
Explanation: The object objectname was saved
BKI0050I Please enter password for node nodename successfully.
on server server name again
User Response: None
Explanation: In order to avoid typing errors, you have
User Response: Enter the password again. description description.
successfully.
User Response: None

BKI0059E You have to set the environment BKI0101I Session session: Please enter ’cont’ to
variable DSMI_CONFIG to the full continue or ’stop’ to cancel.
running in unattended mode (profile keyword BATCH),
Explanation: Tivoli Storage Manager client option file it terminates the current run if operator intervention is
not found. required.
User Response: Verify that the Tivoli Storage Manager User Response: Enter ’cont’ or ’stop’.
BKI0060E The parameter parameter is not known.
Explanation: Tivoli Data Protection for R/3 indicates
Explanation: The command parameter parameter for the reply you made.
Tivoli Data Protection for R/3 is unknown.
User Response: None
BKI0400I TDP is waiting for BRBACKUP
Explanation: Tivoli Data Protection for R/3 is waiting
BKI0061W The output file file name is not valid.
for BRBACKUP to set a tablespace in the begin/end
Explanation: The specified output file file name could backup mode.
not be created.
User Response: None
User Response: Check that file name is a valid file
BRBACKUP in util_file_online
communication.
old one. Explanation: Tivoli Data Protection for R/3 waited
num_sec seconds for BRBACKUP to set a tablespace in
BKI0062E The input file file name is not valid.
User Response: None
to read the input file file name correctly.
BKI0410E Cannot open or delete switch file ’file
name’. Check permissions.
correctly installed (as the root user on UNIX or
BKI0063E The UTL file file name is not valid.
administrator group on Windows NT) then Tivoli Data
Explanation: Tivoli Data Protection for R/3 is not able Protection for R/3 is not able to open the necessary
to read the input file file name correctly. communication file to the SAP R/3 system.
User Response: Check the path and name of the User Response: Check the file permission.
BKI0411E Maximum time waiting for BRBACKUP
BKI0064E The option ’option’ is unknown. expired.
Explanation: A Tivoli Data Protection for R/3 option Explanation: The SAP database utilities did not
is invalid or unknown. respond within the expected time.
User Response: Check the specified option(s) and try User Response: Contact your R/3 administrator.
again.
BKI0412E BRBACKUP was not able to switch
BKI0065E The argument is missing for option requested tablespace in BEGIN
’option’. BACKUP mode.
Explanation: Every Tivoli Data Protection for R/3 Explanation: Tivoli Data Protection for R/3 could not
option requires an argument. continue the backup, because BRBACKUP was not able
again.
Chapter 12. Tivoli Data Protection for R/3 for Oracle 739
BKI0450I • BKI1005W
BKI0450I Version 2 restore: file BKI1000E Syntax error in line line: ’statement’
Explanation: A restore of data backed up with Tivoli Explanation: The statement statement in the Tivoli
Data Protection for R/3 version 2 was executed. Data Protection for R/3 profile is unknown or incorrect.
User Response: None User Response: Correct the error and try again.
BKI0451I This version of Tivoli Data Protection BKI1001E Syntax error in file ’file name’. Exiting
for R/3 will expire on ’date’. Program.
Explanation: This is a test version that will expire on Explanation: Tivoli Data Protection for R/3 has
’date’. detected an syntax error in the file file name and stops
any action.
User Response: Correct the error(s) in the file file name
and try again.
BKI0452E This version of Tivoli Data Protection
for R/3 has expired.
BKI1002E BACKUPIDPREFIX must be
number_of_characters characters.
Explanation: The length of BACKUPIDPREFIX must
be number_of_characters characters.
Representative.
required length (e.g., SAP___, BKI___).
BKI0453W This version of Tivoli Data Protection
for R/3 will expire in ’number’ days.
BKI1003W Please set REDOLOG_COPIES to a
number between 1 and max_copies. Now
it is set to act_copies.
Explanation: Tivoli Data Protection for R/3 currently
supports 1 to 9 copies of offline redo log files.
Representative before the version expires.
User Response: Adapt the REDOLOG_COPIES
settings in the Tivoli Data Protection for R/3 profile.
BKI0454I *** This copy is NOT FOR RESALE. ***
BKI1004W You should specify the
User Response: None. BACKUPIDPREFIX before the
TRACEFILE statement, so that the
BACKUPIDPREFIX can be used in the
BKI0455E License file ’file name’ does not exist. tracefile name.
Explanation: The license file ’agent.lic’ was not found Explanation: The BACKUPIDPREFIX is used to build
where expected. the Name of the tracefile. Therefore,
User Response: Make sure that the ’agent.lic’ file BACKUPIDPREFIX must be specified before the
resides in the same directory as the init<SID>.utl file. TRACEFILE statement.
BKI0456E Unable to access license file ’file name’. BACKUPIDPREFIX in the Tivoli Data Protection for
Explanation: Unable to access license file.
User Response: Make sure the access permissions BKI1005W The tracefile name ’trace_filename’ should
allow read/write access. be absolute.
Explanation: None
BKI0457E License file file name contains invalid
data/checksum. User Response: Specify an absolute tracefile name, for
example /oracle/C21/saptrace/tracefile.
Explanation: The license file is invalid.
agent.lic file for the right platform installed. ’agent.lic’
files are platform dependent.

BKI1006E The SERVERNAME must be less than
CONFIG_FILE).
Explanation: You have used a SERVERNAME with 2. Make sure, that the file access permission are set
more than max_char characters. correctly.
User Response: Use a shorter SERVERNAME.
BKI1013E Profile not found or permissions denied
: ’profile_filename’.
BKI1007E The NODENAME must be less than
max_char characters. Explanation: Tivoli Data Protection for R/3 is unable
to open the profile profile_filename.
Explanation: You have used a NODENAME with
more than max_char characters. User Response: Ensure that the SAP backup profile
init<SID>.sap contains a valid entry util_par_file for
the Tivoli Data Protection for R/3 profile. Furthermore,
BKI1008E The MANAGEMENTCLASSNAME R/3.
Explanation: You have used a BKI1014I The parameter PERF_MONITOR is no
MANAGEMENTCLASSNAME with more than longer supported. Now it is enabled by
max_char characters. default.
User Response: Use a shorter Explanation: For version 2.7 or later of Tivoli Data
MANAGEMENTCLASSNAME. Protection for R/3, the Performance Monitor of the
Administration Assistant can be used by default.
Therefore, the profile parameter PERF_MONITOR is no
BKI1009W Please set MULTIPLEX to a number longer needed.
between 1 and max_multiplex. Now it is
set to act_multiplex. User Response: None

unsupported number. Tivoli Data Protection for R/3 BKI1015I The parameter BACKAGENT is no
now uses act_multiplex. longer needed.
User Response: Set multiplexing to a number between Explanation: For version 2.7 or later of Tivoli Data
1 and max_multiplex. Protection for R/3,, only one executable, called
BKI1010W The configfile name supported or needed.
’configuration_filename’ should be
absolute. User Response: None
Explanation: None
BKI1016W The trace file name ’file name’ could not
User Response: Specify an absolute file name, for be opened for writing!
example /oracle/C21/dbs/initC21.bki.
writing.
BKI1011W The sortfile name ’sortfile_filename’
should be absolute. User Response: Ensure that you have specified a
correct path for the trace file.
Explanation: None
User Response: Specify an absolute file name, for BKI1017E The server ’server name’ is already
example /oracle/C21/dbs/sortfile. defined. Please use another name!
BKI1012E The configfilename already defined.
’configuration_filename’ could not be
opened. User Response: Specify another server name. Server
names have to be unique.
Explanation: Tivoli Data Protection for R/3 is unable
to read the file configuration_filename.
User Response: This error could have various reasons,
try the following:
User Response: Define at least as many different
BKI1200E Can’t read/write file: file name.
Explanation: Tivoli Data Protection for R/3 is unable requested.
to read or write a datafile (file name) of a tablespace
being backed up or restored.
BKI1206W If you want num_redo
User Response: Check the file access permission of REDOLOGCOPIES on Tivoli Storage
the affected file(s). Try again. If the problem still exists, Manager-Server server name, you should
contact the SAP R/3 administrator. give me at least num_mc different
Archive Management Classes.
BKI1201E There are no Tivoli Storage Explanation: The message appears during a
Manager-Servers available. BRBACKUP run. A BRARCHIVE run afterwards would
be failed.
locate a Tivoli Storage Manager server. User Response: Define at least as many different
User Response: Install and specify at least one Tivoli
requested.
Storage Manager server in the Tivoli Data Protection
for R/3 profile (keyword SERVER).
BKI1207E Directory backup not supported
BKI1202E You must specify either Explanation: This option is not yet available.
MAX_SESSIONS or all off
User Response: Wait for a future release of Tivoli Data
MAX_ARCH_SESSIONS,
Protection for R/3, which supports this option.
MAX_BACK_SESSIONS and
MAX_RESTORE_SESSIONS
BKI1208E The object ’file name’ will be retried
Explanation: There is a setup error with the
[retry_num]
SESSIONS parameters within the Tivoli Data Protection
for R/3 profile. Explanation: There was an error with the object
file_name. Tivoli Data Protection for R/3 will try to
User Response: Specify either MAX_SESSIONS and
save/restore the object one retry_num times.
one of the more specific parameters
MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS or User Response: Look at the error messages in the
MAX_RESTORE_SESSIONS or all of the three specific Tivoli Data Protection for R/3 protocol and solve the
session parameters without the MAX_SESSIONS error for the next run.
parameter.

BKI1203E Not enough sessions available (number ’objectname’.
sessions available). Explanation: Tivoli Data Protection for R/3 cannot
locate the Oracle object objectname.
Explanation: The sum of available sessions specified
in the various server statements (parameter SESSIONS) User Response: The backup integrity is affected.
does not cover the required number of sessions Contact the SAP or Tivoli Data Protection for R/3
(parameter MAX_SESSIONS). support.

corresponding parameters in the Tivoli Data Protection BKI1210E Input file not found or not accessible
for R/3 profile, so that the condition mentioned in the ’file name’.
explanation is fulfilled. Explanation: Tivoli Data Protection for R/3 cannot
locate the temporary file file name. This file contains the
BKI1205E If you want num_redo list of Oracle objects to be backed up/restored. It is
REDOLOGCOPIES on Tivoli Storage passed to Tivoli Data Protection for R/3 by
Manager-Server servername, you should BRBACKUP, BRARCHIVE or BRRESTORE.
give me at least num_mc different User Response: Ensure, that you have the correct
Archive Management Classes. version of SAPDBA, BRBACKUP, BRARCHIVE or
Explanation: Tivoli Data Protection for R/3 requires BRRESTORE installed.
that the number of different Archive Management
Classes (parameter BRARCHIVEMGTCLASS) on the
Tivoli Storage Manager servers is equal to or greater
than the number of redo log copies (parameter
REDOLOG_COPIES).

BKI1211E There is something wrong with your BKI2000I Successfully connected to PROLE on
CONFIG_FILE ’file name’. port portnumber.
Explanation: There is a problem with your Tivoli Data Explanation: One of the Tivoli Data Protection for R/3
Protection for R/3 configuration file setup. modules BACKINT or the backup library libtdp_r3
initiated a successful connection to the background
User Response: Check the file permission and the file
process Prole on port portnumber.
name specified in the Tivoli Data Protection for R/3
profile keyword CONFIG_FILE. User Response: None
BKI1212W The file ’file name’ was not found in the BKI2001E Socket error while connecting to
manual sorting file. PROLE: reason.
Explanation: The file you want to back up was not Explanation: The Tivoli Data Protection for R/3
found in the manual sorting file. background process Prole is not running.
User Response: Check and correct the manual sorting User Response: Start Prole manually and try again.
file so that it contains all the files you are backing up.
BKI2002E No valid callback function of type
BKI1213I Program ended with code = ’return code’ fkt_type supplied.
Explanation: The return code of the program is Explanation: Internal Tivoli Data Protection for R/3
displayed. error
User Response: None. User Response: Contact the Tivoli Data Protection for
R/3 support.
BKI1214E TSM Error: ’error text’
BKI2003I File file_name, BID deleted.
Explanation: The specified TSM error occurred.
User Response: Check error text and correct the
BID was deleted from the Tivoli Storage Manager.
problem.
User Response: None
BKI1215I Average transmission rate was ’number’
GB/h (’number’ MB/sec). BKI2004E Connection to PROLE lost.
Explanation: The average transmission rate is Explanation: During Tivoli Data Protection for R/3
displayed. operation the connection to Prole was lost. Network
User Response: Check your network environment and
BKI1216E There are no BRBACKUPMGTCLASSES
available.
Explanation: The BRBACKUPMGTCLASSES you have
Exiting...
specified in your init<SID>.utl file are not correct.
Explanation: This error occurs if the version of Prole
and of the executable BACKINT or the backup library
libtdp_r3 does not match.
User Response: Check the version of Prole and
BKI1217E There are no
BACKINT/backup library libtdp_r3 you are currently
BRARCHIVEMGTCLASSES available.
using.
Explanation: The BRARCHIVEMGTCLASSES you
have specified in your init<SID>.utl file are not correct.
BKI2006E General exception in dispatcher.
User Response: Check the management classes on the Exiting...
error.
R/3 support.
BKI2007E Unknown Port: port BKI2014I FRONTEND program finished.

Explanation: The port specified for the communication Explanation: The frontend program is finished.
between Prole and Backint is unknown.
User Response: None
User Response: Check the port value specified when
Prole was started. Additionally, check the environment
variable PROLE_PORT for the Backint environment.
These two values must match. Explanation: The backend program is executing.
User Response: None
BKI2008E Unable to connect to PROLE.
Explanation: Internal Tivoli Data Protection for R/3 BKI2016I BACKEND program finished.
error.
R/3 support. User Response: None
BKI2009I Deleting all versions with version BKI2017I Blocksize is set to num_bytes bytes.
Number <= version_number. Explanation: The operational blocksize of Tivoli Data
Explanation: All full database backups and their Protection for R/3 is num_bytes bytes.
corresponding redo log backups will be deleted from User Response: None
Tivoli Storage Manager storage, if their version number
BKI2018E Exception in main message loop:
User Response: None ’description’
Explanation: An error occurred during processing.
BKI2010E Error occurred processing FRONTEND The error may contain a descriptive text.
Explanation: An error occurred during the frontend User Response: Contact your service representative.
processing.
User Response: Check the frontend script/program BKI2019E Socket error while connecting to Prole
and the settings in the Tivoli Data Protection for R/3 on port ’number’ for tracing: ’description’
profile (keyword FRONTEND) and try again.
Explanation: During processing, a socket error
occurred on port ’number’. ’description’ may contain the
BKI2011E Error occurred processing BACKEND. system error text.
Explanation: An error occurred during the backend User Response: Check the ’description’. If the error
processing. persists, contact your service representative.
and the settings in the Tivoli Data Protection for R/3 BKI2020E Error occurred for trace connection to
profile (keyword BACKEND) and try again. Prole on port ’number’.
Explanation: The network connection that is used for
BKI2012E Passwords do not match. Try again. tracing generated an error on port ’number’.
Explanation: The first and second password you User Response: Contact your service representative.
entered do not match.
User Response: Enter the password correctly. BKI2021E Unable to delete file ’file name’:
’description’
BKI2013I Starting FRONTEND Program. Explanation: Unable to delete the file ’file name’.
Explanation: The frontend program is executing. ’description’ may contain the system error text.
User Response: None User Response: Check the ’description’. If the error

BKI2022E Unable to change mode of file ’file
R/3 support.
name’: ’description’
BKI4004E Error writing file filename. Only wrote
BKI2023E Error occurred during trace connection
to Prole. Tracing will stop now.
R/3 support.
Explanation: Error occurred during trace connection
to Prole.
BKI4005E Error allocating memory block for file
User Response: Tracing will stop. If the problem file name. BLOCKSIZE may be too large.
Explanation: Tivoli Data Protection for R/3 was not
able to request new memory blocks during the backup
BKI4000W The attributes of file ’file name’ cannot of file file name.
be restored. Reason: errno (error_num)
error_desc.
for BLOCKSIZE. If you are not sure what value is
Explanation: The file file name was restored valid, comment it out so the default value is used.
successfully but one or more file attributes (permission, Furthermore, you can check if you have enough RAM
ownership, date/time) of the file file name cannot be available with your machine. Also, check the memory
restored correctly. usage during backup. It may be necessary to stop
another application, increase memory, or change the
configuration of Tivoli Data Protection for R/3.
set the appropriate correct permission for the file file BKI4006E Error allocating memory block for file
name manually. file name. BLOCKSIZE may be too large.
BKI4001E File ’file name’ cannot be created. Reason:
error_message
the appropriate rights for writing the file file name to
the destination path. Explanation: During a connection of Tivoli Data
Protection for R/3 to Tivoli Storage Manager server, a
Tivoli Storage Manager error error_message occurred.
problem in the future. Furthermore, check the write User Response: Use the Tivoli Storage Manager
permission of the user who started the restore. Messages guide and correct the Tivoli Storage Manager
BKI4002E Error during restore of file ’file name’.
Reason: errno (error_num) error_desc. BKI5001E Tivoli Storage Manager Error:
error_message
process of the file file name. Explanation: See BKI5000E.
User Response: Check the error number error_num User Response: See BKI5000E.
error_message
BKI4003E Error reading file file name. Only read
num_bytes out of all_bytes. Explanation: See BKI5000E.
Explanation: An error occurs reading the file file name. User Response: See BKI5000E.
BKI5003E Tivoli Storage Manager Error: BKI7001E Backup file ’file name’ already exists.
error_message
User Response: See BKI5000E. contact your Oracle database administrator.
BKI5004E Tivoli Storage Manager Error: BKI7002E Bad mode specified.

error_message
User Response: See BKI5000E. contact your Oracle database administrator.
BKI5005E Tivoli Storage Manager Error: BKI7009E Cannot connect to media manager.
error_message
Explanation: See BKI5000E. to connect to the Tivoli Storage Manager server.
User Response: See BKI5000E. User Response: Check the Tivoli Storage Manager API
error_message BKI7010E Permission denied.
Explanation: See BKI5000E. Explanation: The permission for a connection to the
error_message
BKI7012E Invalid arguments during call of
User Response: See BKI5000E. ’function’.
error_message
User Response: See BKI5000E. BKI7020E Bad handle ’rman_handle’ during call of
’function’.
BKI5009E Tivoli Storage Manager Error: Explanation: This is an RMAN internal error.
error_message
Explanation: See BKI5000E. contact your Oracle database administrator.

BKI7021E Bad flags during call of ’function’.
BKI5010E Tivoli Storage Manager Error: Explanation: This is an RMAN internal error.
error_message
Explanation: See BKI5000E. contact your Oracle database administrator.

BKI5011E Tivoli Storage Manager Error: Explanation: Tivoli Data Protection for R/3 has found
error_message the following error: error. This is a ’catch_all’ error code
for unpredictable system errors.

BKI9001E
BKI9001E Internal error: error

the following internal error: error.
R/3 support.
Chapter 13. Tivoli Data Protection for EMC Symmetrix for R/3
(IDS0000–IDS0999)
This chapter describes the messages issued by Tivoli Data Protection for EMC
Symmetrix for R/3. The messages begin with the prefix IDS and are listed in
numerical order.
value in the profile for TDP for Symmetrix.

IDS0000E Profile not specified
Explanation: TDP for Symmetrix cannot locate the
IDS0009E Directory path <path> for the IDS
profile.
control file does not exist.
User Response: Ensure that a profile is available. Note
Explanation: Either the entry for the parameter
that the idscntl call must have the following form:
IDS_CONTROL_FILE is incorrect or the path does not
<path>/idscntl -p <path>/init<SID>.fcs -f <function>....
exist.
User Response: Ensure that the parameter
IDS0001E Function not defined
IDS_CONTROL_FILE in the profile has a valid path. If
Explanation: An invalid argument has been specified the path does not exist, you must create it.
for the -f option of TDP for Symmetrix.
User Response: Ensure that you pass a valid function IDS0010E Option -i <backup_list> not specified.
name with the option -f. Valid functions are: split,
Explanation: The function -f split requires the
synchronize, unmount, password and inquire.
specification of the option -i <backup_list> too.
User Response: Ensure that you transfer the list of the
IDS0004E Subfunction not defined.
files to backup when you call the function -f split. Note
Explanation: An invalid argument has been specified that the idscntl call must in this case have the following
for the -s option of TDP for Symmetrix. This option has form: <path>/idscntl -p <path>/init<SID>.fcs -f split -i
been designed for internal idscntl use only and should <backup_list> ... When the split function runs under
not be used externally. the control of the R/3 DBA tool brbackup by means of
the split_cmd statement of the R/3 DBA profile, you
User Response: Do not use the -s option with the
must ensure that the correct syntax is used there (e.g.
idscntl call.
″... -i $″). brbackup replaces the ″$″ character with the
name of the list file.
IDS0005I Start of idscntl program at: time.
Explanation: TDP for Symmetrix started at time. IDS0011E Option -f <function> not specified.
User Response: None. Explanation: idscntl always requires the option -f

<function> with a valid function.
IDS0007I End of idscntl program at: time. User Response: Ensure that the idscntl call has the
following form: <path>/idscntl -p
Explanation: TDP for Symmetrix ended at time. <path>/init<SID>.fcs -f <function>....
Control will be returned to either the shell or to
brbackup when idscntl was called by brbackup based
on the entries split_cmd and resync_cmd in the IDS0014I <subsystem message>
brbackup profile (e.g., init<SID>.sap)
Explanation: TDP for Symmetrix received an
User Response: None. information message from the IDS subsystem.
IDS0008E Parameter <keyword> in the profile file
required.
IDS0015W <subsystem message>
Explanation: The parameter <keyword> in the profile
Explanation: TDP for Symmetrix received a warning
for TDP for Symmetrix could not be found. It must be
message from the IDS subsystem.
defined.
User Response: Set the parameter <keyword> and its

IDS0016E • IDS0035I
IDS0016E <subsystem message> IDS0032W Information from TDP for R/3 was not
found.
Explanation: TDP for Symmetrix received an error
message from its IDS control part. Explanation: The exchange data between TDP for
Symmetrix and TDP for R/3 was not found during the
User Response: See the subsystem error messages for
execution of one of the functions synchronize or
more information and perform required action.
unmount. Either the TDP for R/3 you have installed
does not support TDP for Symmetrix, or TDP for R/3
IDS0024I Exiting with return code <rc>. has failed after splitting the BCV/STD pairs.
Explanation: The idscntl program issues this message User Response: Check the run logs of brbackup. This
on terminating. The program returns the value 0, or error could have various reasons and should be
nonzero if the execution of the called function failed. resolved depending on the specific situation:
User Response: If the called function has failed, check Case 1: brbackup has finished successfully.
for previous error messages.
Result: The backup on disks (BCVs) as well as the one
done to the TSM server is valid. However, TDP for
IDS0025I Time stamp: <current_time> Symmetrix cannot show the BACKUPID in its report
when using the function inquire.
Explanation: TDP for Symmetrix performs several
tasks in sequence (e.g. split BCVs on the production Reason for warning: It is very likely that TDP for R/3
system and mount file systems on the backup system). does not have TDP for Symmetrix support (prior to
Tracking the various time stamps allows analysis of version 3.1.0.3).
how long each task took.
Action: Install the appropriate TDP for R/3.
Case 2: brbackup has terminated abnormally.
Result: Check carefully the run log of brbackup for any
IDS0026I Start of idscntl on the production
BKI, ANS or ANR error messages. Most likely, the
system ...
backup on disks (BCVs) is valid (check with ’idscntl -f
Explanation: TDP for Symmetrix has issued a call to inquire’ whether PSI is PSI_MOUNT_DONE or
the production system and is waiting for the end of the PSI_UNMOUNT_DONE), but the backup to the TSM
execution. server is invalid.
User Response: None. Cause: Any problems with the network or on the TSM
server caused TDP for R/3 running a backup to fail.
IDS0027I idscntl ended on the production system Action: Depending on the error message, eliminate the
successfully. reason for not getting a successful backup to the TSM
server.
Explanation: TDP for Symmetrix has ended the call to
the production system successfully.
IDS0033I Information from TDP for R/3 has been
User Response: None. found with BACKUPID <backupid>.
Explanation: The exchange data between TDP for R/3
IDS0030I Split started ... and TDP for Symmetrix has been found during the
Explanation: The command for the split of the BCVs execution of one of the functions synchronize or
has been issued on the production system, and the unmount. The backup on disks (BCVs) as well as to the
program idscntl waits until this action has finished. TSM server is valid. The list of files has been saved in
the Tivoli Storage Manager with the BackupID
User Response: None. <backupid>.
IDS0031I Split successful.
Explanation: The command for the split of the BCVs IDS0035I The IDS control file exists and a new
has terminated successfully on the production system. backup cycle entry has been created.
User Response: None. Explanation: At the start of the function -f split, TDP
for Symmetrix inserts a record in the IDS control file
for the new backup cycle. This record will be updated
as the status of the new backup cycle changes (e.g.
BCVs getting mounted, unmounted, synchronized).

IDS0038I • IDS0052I
backup host. A list of mount points or disk groups
IDS0038I The IDS control file <ids_control_file>
(VxVM) will be shown.
does not exist. It will be created.
Explanation: TDP for Symmetrix will write the first
record to the IDS control file specified in the entry
IDS_CONTROL_FILE of the profile. IDS0047I End of listing.
User Response: None. Explanation: Corresponds to start message IDS0046I.
IDS0039E The IDS control file has no entry.
Explanation: TDP for Symmetrix has found the IDS IDS0048E The progress status indicator cannot be
control file, but it has no records. This error occurs PSI_MOUNT_DONE when you call the
when you start one of the functions inquire, function split.
synchronize or unmount before you have run the split
function for the first time. Explanation: TDP for Symmetrix has found that the
progress status indicator of the latest backup cycle
User Response: After you run at least one brbackup already has a value of PSI_MOUNT_DONE. This
with a successful split, the problem will be resolved. indicates that the file systems are still mounted when a
new STD/BCV split is requested.
IDS0043I The maximum number of backup cycles User Response: Run the synchronize or unmount
in the IDS control file has been reached. function and try again.
Explanation: The maximum number of backups
controlled via the parameter BACKUP_MAX will be IDS0050E The version of the idscntl program must
exceeded with the new inserted record. If the be the same on the backup and
parameter is not set, the program will use the default production systems.
value of 30.
Explanation: The version of TDP for Symmetrix on
User Response: None. the production system is different from the version on
the backup system.
IDS0044I Delete backup cycle with BSEQ_N = User Response: Ensure that you install the same
<bseq_n> and all associated files ... version of TDP for Symmetrix on the production and
backup systems. You get the version number when you
Explanation: Since the maximum number of records
start idscntl without parameters.
has been reached, the program will delete the oldest
record with the backup sequence number <bseq_n>. In
addition, the oldest reports and traces associated with IDS0051I Enter the password for the user <user
that backup cycle will be deleted. ID>
User Response: None. Explanation: The password for the user ID <user ID>
has to be entered. It will be encoded and stored in a
file specified in the parameter CONFIG_FILE. Note that
IDS0045W Directory path <directory> for the report
this user ID and password have to be the same on the
files does not exist. Using the current
production and backup systems. The TDP for
directory.
Symmetrix program idscntl uses the user ID to execute
Explanation: The directory entry of the parameter a remote shell on the production system.
LOG_TRACE_DIR in the profile could not be found.
User Response: Enter the password for the
The current directory will be used for the log and trace
corresponding user ID.
files.
User Response: In order to avoid directories cluttered
IDS0052I Enter the password for the user <user
with reports and traces, the parameter
ID> again
LOG_TRACE_DIR should be used, or the directory it
specifies must be created if necessary. Explanation: In order to avoid typing errors, you have
IDS0046I Start of listing of importing disk User Response: Enter the password again.
groups/mounting file systems ...
Explanation: After splitting the STD/BCV pairs on the
production system, TDP for Symmetrix will make the
corresponding target resources (BCVs) available to the
Chapter 13. Tivoli Data Protection for EMC Symmetrix for R/3 751
IDS0053I • IDS0067E
LOGON_HOST_PROD/LOGON_HOST_BACK from
IDS0053I The password entry does not match,
the profile, or the parameter values are incorrect. Note
please try again
that these parameters must have the following format:
Explanation: The two entered passwords are not
LOGON_HOST_PROD <hostname> <user ID>
identical. You must enter the password again.
LOGON_HOST_BACK <hostname>
User Response: Enter the password again. You are
permitted three attempts before the program The hostnames must match the respective hostnames of
terminates. the production and backup systems. The user ID
specified must match the oracle DBA user ID
(ora<sid>).
IDS0054E No password stored.
User Response: Ensure that the profile contains valid
entries for LOGON_HOST_PROD and
identical. You have tried three times, and the
LOGON_HOST_BACK.
passwords were different in each case.
User Response: You must start the idscntl program
IDS0064E The parameter <keyword> in the profile
with the function -f password again. If no password is
is not known.
stored, or it is invalid, idscntl fails when the split
function is used. Explanation: An unknown parameter <keyword> has
been found in the profile.
IDS0055E The config file named <config_file> User Response: Check the specified parameter in the
could not be opened for reading/writing. profile and try again.
Explanation: TDP for Symmetrix is unable to read the
configuration file <config_file>. IDS0065W The progress status indicator (PSI) is
already PSI_SYNCHRONIZED.
User Response: This error could have various reasons.
Try the following: Explanation: You cannot run the
synchronize/unmount function multiple times without
having done a brbackup with a split request. Doing this
will cause warnings. It might be that a previous split
CONFIG_FILE).
request failed due to network problems and the
2. Make sure that the file access permissions are set synchronization could therefore not be done.
correctly.
User Response: Make sure you run a brbackup with
the function -f split prior to using the TDP for
IDS0060I Start of listing of deporting disk Symmetrix functions unmount or synchronize.
groups/unmounting file systems ...
Explanation: Before synchronizing the STD/BCVs IDS0066E The option -f split can only be used on
pairs, TDP for Symmetrix will disable the the backup system.
corresponding resources from the backup host. A list of
Explanation: You cannot start the split function on the
unmount points or deporting disk groups (VxVM) will
production system.
be shown.
User Response: Make sure you start idscntl with the
function -f split on the backup system only. Ensure that
the profile contains a valid entry for
IDS0062I The progress status indicator (PSI) is LOGON_HOST_BACK.
already PSI_UNMOUNT_DONE.
Explanation: TDP for Symmetrix has been called with IDS0067E The options -f split -s performsplit can
the function synchronize or unmount, but the PSI value only be used on the production system.
of the latest backup cycle was already updated to
Explanation: The option -s was designed for internal
PSI_UNMOUNT_DONE in a previous idscntl call.
idscntl use only and should not be used externally.
User Response: Make sure you start idscntl -f split on
the backup system only. Ensure that the profile contains
IDS0063E Parameters valid entries for LOGON_HOST_PROD and
LOGON_HOST_PROD/LOGON_HOST_BACKLOGON_HOST_BACK. Do not use the -s option with
in profile wrong or missing. the idscntl call.
Explanation: Either TDP for Symmetrix is unable to
read one of the parameters

IDS0068E • IDS0304E
<ids_control_file> or
IDS0068E The option -f synchronize can only be
the field value EXCHANGE_FILE in a backup cycle record.
used on the backup system.
User Response: Check the access permissions of the
Explanation: You cannot start the function
affected file and try again.
synchronize on the production system.
IDS0302E The environment variable <env_var>
function -f synchronize on the backup system only.
must be set.
Ensure that the profile contains a valid entry for
LOGON_HOST_BACK. Explanation: The environment variable <env_var> is
required. The following environment variables must be
set when running TDP for Symmetrix:
IDS0069E The option -f unmount can only be used
on the backup system.
ORACLE_HOME: to the home directory of the user ID
Explanation: You cannot start the function unmount ORACLE_SID: to the R/3 Oracle DB system ID
on the production system.
User Response: Set the missing environment variable
User Response: Make sure you start idscntl with the and try again.
function -f unmount on the backup system only. Ensure
that the profile contains a valid entry for
LOGON_HOST_BACK. IDS0303E The environment variable <env_var> is
not correct.
IDS0070I Checking and if necessary Explanation: This error can occur when the
synchronizing STD/BCV pairs. environment variable is set but contains a non-existent
directory path.
Explanation: At this point, idscntl checks on the
production system for the availability of synchronized User Response: Check the value of the environment
STD/BCV pairs. If the pairs are not yet synchronized, variable and try again.
idscntl will synchronize them at this point. However,
this will take much more time than if the IDS0304E File not found or not accessible:
synchronization had been initiated on the backup <filename>.
system before running the brbackup that started a split
request via the split_cmd statement. Explanation: The file <filename> was not found or is
not accessible to TDP for Symmetrix. The affected files
User Response: Avoid this type of late could be: <ORACLE_HOME>/dbs/init<SID>.fcs or the
synchronization in a brbackup run and synchronize the argument value of the option -i (that file contains the
BCVs with the STDs before starting brbackup or within list of files to backup).
brbackup via the resync_cmd statement.
User Response: Check path, name and the
permissions of the file and try again.
IDS0300E Cannot read file: <filename>.
Explanation: TDP for Symmetrix is unable to read the
data file <filename>. The affected files could be e.g.:
<ORACLE_HOME>/dbs/init<SID>.fcs, the argument
value of the option -i (file containing the list of files to
back up), <config_file>, <ids_control_file> or the field
value of EXCHANGE_FILE in a backup cycle record.
affected file and try again.
IDS0301E Cannot write file: <filename>.

Explanation: TDP for Symmetrix is unable to write to
the data file filename. The affected files could be e.g.:
<LOG_TRACE_DIR>/idscntl_b_<time>.log,
<LOG_TRACE_DIR>/idscntl_p_<time>.log,
<LOG_TRACE_DIR>/idscntl_b_<time>.trace,
<LOG_TRACE_DIR>/idscntl_p_<time>.trace,
<config_file>,
Chapter 13. Tivoli Data Protection for EMC Symmetrix for R/3 753
Chapter 14. Tivoli Data Protection for IBM ESS for R/3
(IDS1000–IDS1999)
This chapter describes the messages issued by Tivoli Data Protection for IBM ESS
for R/3. The messages begin with the prefix IDS and are listed in numerical order.
IDS1000E Profile not specified IDS1009E Directory path <path> for the IDS
control file does not exist.
Explanation: TDP for ESS cannot locate the profile.
Explanation: Either the entry for the parameter
IDS_CONTROL_FILE is incorrect or the path does not
that the idscntl call must have the following form:
exist.
<path>/idscntl -p <path>/init<SID>.fcs -f <function>....
User Response: Ensure that the parameter
IDS_CONTROL_FILE in the profile has a valid path. If
IDS1001E Function not defined
the path does not exist, you must create it.
Explanation: An invalid argument has been specified
for the -f option of TDP for ESS.
IDS1010E Option -i <backup_list> not specified.
User Response: Ensure that you pass a valid function
Explanation: The function -f flashcopy requires the
name with the option -f. Valid functions are: withdraw,
specification of the option -i <backup_list> too.
flashcopy, password, unmount, and inquire.
User Response: Ensure that you transfer the list of the
files to back up when you call the function -f flashcopy.
IDS1004E Subfunction not defined.
Note that the idscntl call must in this case have the
Explanation: An invalid argument has been specified following form: <path>/idscntl -p
for the -s option of TDP for ESS. This option has been <path>/init<SID>.fcs -f flashcopy -i <backup_list> ...
designed for internal idscntl use only and should not When the FlashCopy function runs under the control of
be used externally. the R/3 DBA tool brbackup by means of the split_cmd
statement of the R/3 DBA profile, you must ensure that
User Response: Do not use the -s option with the the correct syntax is used there (e.g. ″... -i $″). brbackup
idscntl call. replaces the ″$″ character with the name of the list file.
IDS1005I Start of idscntl program at: time. IDS1011E Option -f <function> not specified.
Explanation: TDP for ESS started at time. Explanation: idscntl always requires the option -f
User Response: None. <function> with a valid function.
User Response: Ensure that the idscntl call has the
IDS1007I End of idscntl program at: time. following form: <path>/idscntl -p
<path>/init<SID>.fcs -f <function>....
Explanation: TDP for ESS ended at time. Control will
be returned to either the shell or to brbackup when
idscntl was called by brbackup based on the entries IDS1014I <subsystem message>
split_cmd and resync_cmd in the brbackup profile (e.g., Explanation: TDP for ESS received an information
init<SID>.sap) message from the IDS subsystem.
IDS1008E Parameter <keyword> in the profile file IDS1015W <subsystem message>

required.
Explanation: TDP for ESS received a warning message
Explanation: The parameter <keyword> in the profile from the IDS subsystem.
for TDP for ESS could not be found. It must be defined.
User Response: Set the parameter <keyword> and its
value in the profile for TDP for ESS.

IDS1016E • IDS1032W
IDS1016E <subsystem message> IDS1025I Time stamp: <current_time>

Explanation: TDP for ESS received an error message Explanation: TDP for ESS performs several tasks in
from its IDS control part. sequence (e.g. initiate the FlashCopy of source volumes
on the production system and mount file systems on
User Response: See the subsystem error messages for
the backup system). Tracking the various time stamps
more information and perform required action.
allows analyzing how long each task took.
IDS1016E Neither the primary nor the backup ESS
server has been specified.
IDS1026I Start of idscntl on the production
Explanation: Neither the
system ...
SHARK_SERVERNAME_PRIMARY nor
SHARK_SERVERNAME_BACKUP parameter has been Explanation: TDP for ESS has issued a call to the
specified in the TDP for ESS profile (init<SID>.fcs). production system and is waiting for the end of the
execution.
User Response: Ensure that the profile contains
entries for SHARK_SERVERNAME_PRIMARY and User Response: None.
SHARK_SERVERNAME_BACKUP and their values
form a valid TCP/IP address.
IDS1027I idscntl ended on the production system
successfully.
IDS1016I(E) The ESS primary server is down or has
Explanation: TDP for ESS has ended the call to the
an invalid address.
production system successfully.
Explanation: The ESS primary server with the TCP/IP
address specified in the parameter
SHARK_SERVERNAME_PRIMARY is down or cannot
be reached. IDS1030I Flashcopy started ...
User Response: If this message appears as a Explanation: The command with the flashcopy
information message, function has been issued on the production system, and
SHARK_SERVERNAME_BACKUP was specified and the program idscntl waits until this action has finished.
the connection will be made via its TCP/IP address.
Otherwise, this message will appear as an error. Ensure User Response: None.
that the profile contains entries for
SHARK_SERVERNAME_PRIMARY and IDS1031I Flashcopy successful.
SHARK_SERVERNAME_BACKUP and their values
form a valid TCP/IP address. Explanation: The command for the FlashCopy of the
volume pairs has terminated successfully on the
production system.
IDS1016E There is a problem with both ESS copy
services. User Response: None.
Explanation: Neither the connection to the ESS

primary server nor the one to the ESS backup server is IDS1032W Information from TDP for R/3 was not
working properly. found.
User Response: Ensure that the profile contains Explanation: The exchange data between TDP for ESS
entries for SHARK_SERVERNAME_PRIMARY and and TDP for R/3 was not found during the execution
SHARK_SERVERNAME_BACKUP and their values of the unmount function. Either the TDP for R/3 you
form a valid TCP/IP address. Contact your ESS have installed does not support TDP for ESS, or TDP
administrator. for R/3 has failed after a successful FlashCopy and
mount.
IDS1024I Exiting with return code <rc>. User Response: Check the run logs of brbackup. This
error could have various reasons and should be
Explanation: The idscntl program issues this message resolved depending on the specific situation:
on terminating. The program returns the value 0, or
nonzero if the execution of the called function failed. Case 1: brbackup has finished successfully.
User Response: If the called function has failed, check Result: The backup on disk (FlashCopy target volumes)
for previous error messages. as well as the one done to the TSM server are valid.
However, TDP for ESS cannot show the BACKUPID in
its report when using the function inquire.
Reason for warning: It is very likely that TDP for R/3

IDS1033I • IDS1044I
(AIX version) does not have TDP for ESS support (prior
IDS1039E The IDS control file has no entry.
to version 3.1.0.3).
Explanation: TDP for ESS has found the IDS control
Action: Install the appropriate TDP for R/3 version.
file, but it has no records. This error occurs when you
Case 2: brbackup has terminated abnormally. start one of the functions inquire, withdraw or
unmount before you have run the flashcopy function
Result: Check carefully the run log of brbackup for any for the first time.
BKI, ANS or ANR error messages. Most likely, the
backup on disk (FlashCopy target volumes) is valid User Response: After you run at least one brbackup
(check with ’idscntl -f inquire’ whether PSI is with a successful flashcopy, the problem will be
PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but resolved.
the backup to the TSM server is invalid.
Cause: Any problems with the network or on the TSM IDS1040E The IDS control file must be read or
server caused TDP for R/3 running a backup to fail. inserted before update.
Action: Depending on the error message, eliminate the Explanation: TDP for ESS has detected a logical error
reason for not getting a successful backup to the TSM when processing the IDS control file.
server.
User Response: Contact Tivoli Data Protection for R/3
support.
IDS1033I Information from TDP for R/3 has been
found with BACKUPID <backupid>.
IDS1042W Info data from TDP for R/3
Explanation: The exchange data between TDP for R/3 /tmp/bki<SID>.ids cannot be read.
and TDP for ESS has been found during the execution
Explanation: Before the unmount process, TDP for
of the function unmount. The backup on disk
ESS will read /tmp/bki<SID>.ids, which contains
(FlashCopy target volumes) as well as to the TSM
information about the backup that was done by TDP
server are valid. The list of files has been saved in the
for R/3. Among the information read is:
Tivoli Storage Manager with the BackupID <backupid>.
v Backup id
v Util file used for the backup
v List of files used for the backup
IDS1034E Entry <field_name> in the current
v Backup type
backup cycle of the IDS control file is
missing. This message will be issued if TDP for R/3 terminated
unsuccessfully for some reason.
Explanation: The field with the name <field_name> in
the current backup cycle was unexpectedly empty. User Response: Ensure that TDP for R/3 runs
successfully.
User Response: Please check for other errors prior to
this one.
IDS1043I The maximum number of backup cycles
in the IDS control file has been reached.
IDS1035I The IDS control file exists and a new
backup cycle entry has been created. Explanation: The maximum number of backups
controlled via the parameter BACKUP_MAX will be
Explanation: At the start of the function -f flashcopy,
exceeded with the new inserted record. If the
TDP for ESS inserts a record in the IDS control file for
parameter is not set, the program will use the default
the new backup cycle. This record will be updated as
value of 30.
the status of the new backup cycle changes (e.g.
FlashCopy target volumes/filesystems being mounted User Response: None.
or unmounted).
User Response: None. IDS1044I Delete backup cycle with BSEQ_N =
<bseq_n> and all associated files ...
IDS1038I The IDS control file <ids_control_file> Explanation: Since the maximum number of records
does not exist. It will be created. has been reached, the program will delete the oldest
record with the backup sequence number <bseq_n>. In
Explanation: TDP for ESS will write the first record to
addition, the oldest reports and traces associated with
the IDS control file specified in the entry
that backup cycle will be deleted.
IDS_CONTROL_FILE of the profile.
Chapter 14. Tivoli Data Protection for IBM ESS for R/3 757
IDS1045W • IDS1055E
IDS1045W Directory path <directory> for the report IDS1051I Enter the password for the user <user
files does not exist. Using the current ID>
directory.
Explanation: The password for the user ID <user ID>
Explanation: The directory entry of the parameter has to be entered. It will be encoded and stored in a
LOG_TRACE_DIR in the profile could not be found. file specified in the parameter CONFIG_FILE. Note that
The current directory will be used for the log and trace this user ID and password have to be the same on the
files. production and backup systems. The TDP for ESS
program idscntl uses the user ID to execute a remote
User Response: In order to avoid directories cluttered
shell on the production system.
with reports and traces, the parameter
LOG_TRACE_DIR should be used, or the directory it User Response: Enter the password for the
specifies must be created if necessary. corresponding user ID.
IDS1046I Start of listing of importing volume IDS1052I Enter the password for the user <user
groups/mounting file systems ... ID> again
Explanation: After initiating the FlashCopy Explanation: In order to avoid typing errors, you have
source/target volumes on the production system, TDP to enter the password twice.
for ESS will make the corresponding target volumes
User Response: Enter the password again.
available to the backup host. A list of mount points or
volume groups will be shown.
IDS1053I The password entry does not match,
please try again
IDS1047I End of listing.
identical. You must enter the password again.
Explanation: Corresponds to start message IDS1046I.
User Response: Enter the password again. You are
User Response: None. permitted three attempts before the program
terminates.
IDS1048I The unmount process will be skipped
because the progress status indicator IDS1054E No password stored.
(PSI) has a value of ’psi’.
Explanation: When the ’withdraw’ function is started, identical. You have tried three times, and the
the unmount process will be performed only if the PSI passwords were different in each case.
has a value of PSI_MOUNT_STARTED or
User Response: You must start the idscntl program
PSI_MOUNT_DONE.
with the function -f password again. If no password is
User Response: Tivoli Data Protection for IBM ESS for stored, or it is invalid, idscntl fails when the flashcopy
R/3: Installation and User’s Guide shows the function is used.
permissible functions depending on the backup
progress status indicator.
IDS1055E The config file named <config_file>
could not be opened. Please call idscntl
IDS1050E The version of the idscntl program must with the password function to create
be the same on the backup and that file.
production systems.
Explanation: TDP for ESS is unable to read the
Explanation: The version of TDP for ESS on the configuration file <config_file>.
production system is different from the version on the
User Response: This error could have various reasons.
backup system.
Try the following:
User Response: Ensure that you install the same
1. Call idscntl with the ’password’ function to create
version of TDP for ESS on the production and backup
the file.
systems. You get the version number when you start
idscntl without parameters. 2. Check the path of the configuration file. The path
CONFIG_FILE).
3. Make sure that the file access permissions are set
correctly.

IDS1060I • IDS1069E
User Response: Check the specified parameter in the
IDS1060I Start of listing of exporting volume
profile and try again.
groups/unmounting file systems ...
Explanation: A list of unmount points or exporting
IDS1065E You cannot run the function ’function’ if
disk groups will be shown. Due to the usage of the
the progress status indicator (PSI) has a
unmount function on the backup host,TDP for ESS will
value of ’psi’.
unmount the file systems and export volume groups on
the backup host that had been imported or mounted Explanation: The backup cycle was left in a state that
when the TDP for ESS flashcopy function was does not allow TDP for ESS to start the specified
executed. function.
User Response: None. User Response: Tivoli Data Protection for IBM ESS for
R/3: Installation and User’s Guide shows the
permissible functions depending on the backup
IDS1061I Start the withdraw of the target-source
progress status indicator.
pairs ...
Explanation: The command with a withdraw has been
IDS1066E The option -f flashcopy can only be
issued from the backup system to the primary Copy
used on the backup system.
Services server on the ESS.
Explanation: You cannot start the flashcopy function
IDS1062I The progress status indicator (PSI) is
function -f flashcopy on the backup system only.
already PSI_UNMOUNT_DONE.
Ensure that the profile contains a valid entry for
Explanation: TDP for ESS has been called with the LOGON_HOST_BACK.
function withdraw or unmount, but the PSI value of
the latest backup cycle was already updated to
IDS1067E The options -f flashcopy -s performsplit
PSI_UNMOUNT_DONE in a previous idscntl call.
can only be used on the production
User Response: None. system.
Explanation: The option -s was designed for internal
IDS1063E Parameters LOGON_HOST_PROD/ idscntl use only and should not be used externally.
LOGON_HOST_BACK in profile wrong
User Response: Make sure you issue idscntl -f
or missing.
flashcopy on the backup system only. Ensure that the
Explanation: Either TDP for ESS is unable to read one profile contains valid entries for LOGON_HOST_PROD
of the parameters LOGON_HOST_PROD/ and LOGON_HOST_BACK. Do not use the -s option
LOGON_HOST_BACK from the profile, or the with the idscntl call.
parameter values are incorrect. Note that these
parameters must have the following format:
IDS1068E The option -f withdraw can only be
LOGON_HOST_PROD <hostname> <TCP/IP address> used on the backup system.
<user ID>
Explanation: You cannot start the function withdraw
LOGON_HOST_BACK <hostname> on the production system.
The hostnames must match the respective hostnames of User Response: Make sure you start idscntl with the
the production and backup systems. TCP/IP address function -f withdraw on the backup system only.
will be used for the communication between the two Ensure that the profile contains a valid entry for
systems. The user ID specified must match the oracle LOGON_HOST_BACK.
DBA user ID (’ora<sid>’).
User Response: Ensure that the profile contains valid IDS1069E The option -f unmount can only be used
entries for LOGON_HOST_PROD and on the backup system.
LOGON_HOST_BACK.
Explanation: You cannot start the function unmount
IDS1064E The parameter <keyword> in the profile
is not known.
function -f unmount on the backup system only. Ensure
Explanation: An unknown parameter <keyword> has that the profile contains a valid entry for
been found in the profile. LOGON_HOST_BACK.
IDS1071E • IDS1081W
IDS1071E Topic named <topicname> could not be IDS1077I Semaphore released.

found in the file <filename>.
Explanation: After the program has passed the critical
Explanation: TDP for ESS could read the file part of the run, the semaphore is released.
<filename> but the expected entry for the topic
User Response: None
<topicname> was not found.
User Response: When the affected file is the field
IDS1078W The semaphore could not be created.
value of the parameter SHARK_VOLUMES_FILE, you
System error <sys_errno>:
need to check whether the topic name has the format:
<sys_message>.
>>> shark_volumes_set_# where # is a placeholder for
the volume set number (1, 2, ..) Explanation: If TDP for ESS could not create the
semaphore, the system error number and message will
When the affected file is another file, you likely have
be issued as a warning. The concurrent run of multiple
another error prior this one. Otherwise, contact Tivoli
production systems with a single backup system will
Data Protection for R/3 support.
not work properly.
User Response: Check the system error number and
IDS1073E No target volumes were specified for
message with your system administrator.
the set <shark_volumes_set_#> in file
<filename>.
IDS1079W The semaphore could not be initialized.
Explanation: TDP for ESS has read file <filename>
contained in the parameter SHARK_VOLUMES_FILE.
<sys_message>.
The format of the file is correct, but the list of target
volumes is missing. Explanation: If TDP for ESS could not initialize the
User Response: See the description of the FlashCopy
be issued as a warning. The concurrent run of multiple
target volumes file in Tivoli Data Protection for IBM
ESS for R/3: Installation and User’s Guide.
not work properly.
IDS1075I Creating a semaphore for the critical
part of importing/exporting ...
Explanation: When multiple production systems run a
IDS1080W The semaphore could not be allocated.
backup via a single backup system at the same time,
TDP for ESS will ensure that the critical parts of the
<sys_message>.
code run for a single instance of the program at a time.
These phases are: Explanation: If TDP for ESS could not allocate the
1. when the FlashCopy has been done and resources semaphore, the system error number and message will
(volume groups and file systems) are being enabled be issued as a warning. The concurrent run of multiple
2. before the FlashCopy relationship is withdrawn and
not work properly.
resources (volume groups and file systems) are
being disabled. User Response: Check the system error number and
For this synchronization process, a semaphore with the
fixed key 0x88886666 will be created.
IDS1081W The semaphore could not be released.
User Response: None
System error <sys_error>:
<sys_message>.
IDS1076I Trying to set the semaphore for the
Explanation: If TDP for ESS could not allocate the
critical part of importing/exporting ...
Explanation: If the TDP for ESS semaphore is already be issued as a warning. The concurrent run of multiple
allocated, the program will wait until it is released. production systems with a single backup system will
Otherwise, the program will set it and pass into the not work properly.
critical part of the run. Another instance arriving at this
point will now have to wait for the release of the
semaphore.
User Response: None

IDS1082E Duplicate target volume ’serial number’ IDS1303E The environment variable <env_var> is
was found in the target list. not correct.
Explanation: TDP for ESS found a duplicate serial Explanation: This error can occur when the
number for an ESS target volume in the file specified in environment variable is set but contains a non-existent
the SHARK_VOLUMES_FILE parameter. directory path.
User Response: Ensure that the serial numbers of the User Response: Check the value of the environment
target volumes in the file SHARK_VOLUMES_FILE are variable and try again.
unique .
IDS1304E File not found or not accessible:
IDS1300E Cannot read file: <filename>. <filename>.
Explanation: TDP for ESS is unable to read the data Explanation: The file <filename> was not found or is
file <filename>. The affected files could be e.g.: not accessible to TDP for ESS. The affected files could
v <ORACLE_HOME>/dbs/init<SID>.fcs be: <ORACLE_HOME>/dbs/init<SID>.fcs or the
argument value of the option -i (that file contains the
v the argument value of the option -i (file containing
list of files to back up).
the list of files to back up)
v <config_file> User Response: Check path, name and the
permissions of the file and try again.
v <ids_control_file>
v the field value of EXCHANGE_FILE in a backup
cycle record. IDS1305E The effective user ID of the process
could not be set to the user <userid>.
affected file and try again. Explanation: One of the following cases can cause this
error:
v the access rights for idscntl are not set to 4750. Since
IDS1301E Cannot write file: <filename>.
the s-bit is not set, TDP for ESS cannot switch
Explanation: TDP for ESS is unable to write to the between the users ’ora<sid>’ and ’root’ during the
data file filename. The affected files could be e.g.: execution of the program.
v <LOG_TRACE_DIR>/idscntl_b_<time>.log v the file system in which idscntl is installed was
v <LOG_TRACE_DIR>/idscntl_p_<time>.log mounted with the NOSUID option.
v <LOG_TRACE_DIR>/idscntl_b_<time>.trace User Response:

v <LOG_TRACE_DIR>/idscntl_p_<time>.trace v Check the idscntl file in the directory
v <config_file> /usr/tivoli/tsm/tdpessr3/oracle/1.x.y.z, and set the
access rights for idscntl with chmod 4750 idscntl.
v <ids_control_file> After the installation, the command
v the field value EXCHANGE_FILE in a backup cycle ls -l idscntl.... outputs a line such as:
record. -rwsr-x---1 root dba 1918611 Apr 11 17:09 idscntl
affected file and try again. (This is what setup.sh would do if the user had used
it.)
IDS1302E The environment variable <env_var> v If the file system in which idscntl is installed was
must be set. mounted with the NOSUID option, mount the file
system with SUID allowed.
Explanation: The environment variable <env_var> is
required. The following environment variables must be
set when running TDP for ESS: IDS1306E Operating system error <error_no>:
<message text>.
ORACLE_HOME: to the home directory of the user ID Explanation: TDP for ESS encountered an unexpected
ORACLE_SID: to the R/3 Oracle DB system ID message error during the execution of a system
function. The respective operating system error and
User Response: Set the missing environment variable
message text will be displayed. The message will
and try again.
appear, for example, as a result of
v a wrong user ID on the parameter
LOGON_HOST_PROD in the fcs file
v a wrong password given for the user ID on the
parameter LOGON_HOST_PROD in the fcs file
v a wrong TCP/IP name on the parameter
LOGON_HOST_PROD in the fcs file (e.g: connection
timeout)
v a failure allocating memory through the function
malloc, and the operating system cannot satisfy the
request
User Response: Check the specific error message.
IDS1452E This version of Tivoli Data Protection

for IBM ESS for R/3 has expired.
Protection for IBM ESS for R/3 or contact your
IBM/Tivoli sales representative.
IDS1453W This version of Tivoli Data Protection

for IBM ESS for R/3 will expire in
’number’ days.
Protection for IBM ESS for R/3 or contact your
IBM/Tivoli sales representative before the version
expires.
IDS1454I *** This copy is NOT FOR RESALE. ***

IDS1455E License file ’filename’ does not exist.

Explanation: The license file ’agentess.lic’ was not
found where expected.
User Response: Make sure that the ’agentess.lic’ file
resides in the same directory as the init<SID>.fcs
profile.
IDS1456E Unable to access license file ’file name’.

Explanation: Unable to access license file.
User Response: Make sure the access permissions
allow read/write access.
IDS1457E License file ’file name’ contains invalid

data/checksum.
Explanation: The license file is invalid.
agentess.lic file installed.

Chapter 15. Tivoli Data Protection for WebSphere Application
Server (DKP0000–DKP0999)
This chapter describes the messages issued by Tivoli Data Protection for
WebSphere Application Server. The messages begin with the prefix DKP and are
listed in numerical order.
DKP0000E Profile not specified. DKP0024I Return code is: return code
Explanation: Tivoli Data Protection for WebSphere Explanation: Shows the return code of Tivoli Data
Application Server cannot locate the profile. Protection for WebSphere Application Server. A return
code of 0 means no errors or warnings occurred. If the
return code is 1, at least one warning was issued by the
that the call must have the following form: tdpws -p
program. If the return code is 2, at least one error
initWAS.utl ...
message was issued.
DKP0004E Function not defined.
Explanation: You passed an invalid argument to Tivoli
Data Protection for WebSphere Application Server.
DKP0027I Time: current_time
User Response: Valid functions are: -f backup, -f restore, Objects: current_num of total_num
-f delete, and -f inquire. in process: file_name
MGMNT-CLASS: management_class
DKP0005I Start of program at: time
Explanation: Tivoli Data Protection for WebSphere
Explanation: The program has been started. Application Server started saving current_num files at
User Response: None. current_time. The total number of files to save is
total_num. The file file_name is currently being
processed. The files are transferred to the Tivoli Storage
DKP0020I End of program at: time Manager server server name, which stores them in the
Explanation: The program has finished. Management Class management_class.
DKP0021I Elapsed time: elapsedtime DKP0030I Time: current_time

Explanation: The time needed for the complete in process: file_name
backup was elapsedtime. Size: bytes MB
User Response: None. TSM Server: server name.
DKP0023I Time: current_time Application Server completed saving current_num files
Done: saved_bytes (percent) of bytes at current_time. The total number of files to save is
Estimated end time: end_time total_num. The file file_name is currently being
processed. The Tivoli Storage Manager server server
Explanation: Tivoli Data Protection for WebSphere name is selected.
Application Server finished saving a specific object at
current_time. The saved_bytes amount of the total User Response: None.
number of bytes have been saved. percent shows the
percentage. This Tivoli Data Protection for WebSphere DKP0031W Object not found or not accessible:
Application Server call will be completed at the objectname.
estimated end_time.
User Response: None. accessible to Tivoli Data Protection for WebSphere
Application Server.

DKP0032E • DKP0060E
DKP0032E Error opening file file name: system error done: file_name with: bytes saved with
description description object_desc.
Explanation: A system error occurred during opening Explanation: Tivoli Data Protection for WebSphere
of the file file name. system error description will describe Application Server completed saving current_num file at
the error in more detail. current_time. The total number of files to be saved is
total_num. The file file_name with the size bytes is saved
User Response: Read the system error description. with the description object_desc.
DKP0033E Error opening file file name: system error
description
Explanation: See DKP0032E. Objects: current_num of total_num
User Response: See DKP0032E. done: file_name with: bytes
restored with description object_desc.
DKP0049I Please enter password for node nodename Explanation: Tivoli Data Protection for WebSphere
on server server name Application Server completed restoring of current_num
file at current_time. The total number of files to be
Explanation: The password for the node nodename on restored is total_num. The file file_name with the size
the Tivoli Storage Manager server server name has to be bytes is restored with the description object_class.
entered for storing it in the Tivoli Data Protection for
WebSphere Application Server configuration file. User Response: None.
User Response: Enter the password for the

corresponding Tivoli Storage Manager server. DKP0055I Object objectname with size saved with
DKP0050I Please enter password for node nodename Explanation: The object objectname was saved
on server server name again successfully.
Explanation: In order to avoid typing errors, you have User Response: None.
User Response: Enter the password again. DKP0056I Object objectname with size restored with
DKP0051I Password successfully verified for node Explanation: The object objectname was restored
nodename on server server name. successfully.
Explanation: The password for the node nodename on User Response: None.
changed successfully. DKP0059E You have to set the environment
User Response: None. variable DSMI_CONFIG to the full
DKP0052E Password verification for node nodename
on server server name failed. Explanation: Tivoli Storage Manager client option file
not found.
Explanation: The password you entered for the node
nodename on the Tivoli Storage Manager server server User Response: Verify that the Tivoli Storage Manager
name was wrong. option file dsm.opt is pointed to by DSMI_CONFIG.
User Response: Enter the password again. If this error

still exists, contact your Tivoli Storage Manager DKP0060E The parameter parameter is not known.
administrator. Explanation: The command parameter parameter for
Tivoli Data Protection for WebSphere Application
Server is unknown.

DKP0061W • DKP0456E
DKP0061W The output file file name is not valid. DKP0102I Your reply: ’reply’.
Explanation: The specified output file file name could Explanation: Tivoli Data Protection for WebSphere
not be created. Application Server indicates the reply you made.
User Response: Check that file name is a valid file User Response: None.
DKP0451I This version of Tivoli Data Protection
for WebSphere Application Server will
expire on ’date’.
old one.
Explanation: This is a test version that will expire on
’date’.
DKP0062E The input file file name is not valid.
Application Server is not able to read the input file file
name correctly. DKP0452E This version of Tivoli Data Protection
for WebSphere Application Server has
expired.
DKP0063E The UTL file file name is not valid. User Response: Order a release version of Tivoli Data
Protection for WebSphere Application Server or contact
your IBM/Tivoli Sales Representative.
Application Server is not able to read the input file file
name correctly.
DKP0453W This version of Tivoli Data Protection
for WebSphere Application Server will
expire in ’number’ days.
DKP0064E The option ’option’ is unknown.
Explanation: A Tivoli Data Protection for WebSphere
Application Server option is invalid or unknown.
Protection for WebSphere Application Server or contact
User Response: Check the specified option(s) and try your IBM/Tivoli Sales Representative before the
again. version expires.
DKP0065E The argument is missing for option DKP0454I *** This copy is NOT FOR RESALE. ***
’option’.
Explanation: Every Tivoli Data Protection for
WebSphere Application Server option requires an
argument.
DKP0455E License file ’file name’ does not exist.
again. Explanation: The license file ’agent.lic’ was not found
where expected.
DKP0101I Session session: Please enter ’cont’ to User Response: Make sure that the ’agent.lic’ file
continue or ’stop’ to cancel. resides in the same directory as the initWAS.utl file.
Explanation: If Tivoli Data Protection for WebSphere
Application Server is running in unattended mode DKP0456E Unable to access license file ’file name’.
(profile keyword BATCH), it terminates the current run
if operator intervention is required. Explanation: Unable to access license file.
User Response: Enter ’cont’ or ’stop’. User Response: Make sure the access permissions
allow read/write access.
Chapter 15. Tivoli Data Protection for WebSphere Application Server 765
DKP0457E License file file name contains invalid DKP1006E The SERVERNAME must be less than
data/checksum. max_char characters.
Explanation: The license file is invalid. Explanation: You have used a SERVERNAME with
agent.lic file for the right platform installed. ’agent.lic’ User Response: Use a shorter SERVERNAME.
files are platform dependent.
DKP1007E The NODENAME must be less than
DKP1000E Syntax error in line line: ’statement’ max_char characters.
Explanation: The statement statement in the Tivoli Explanation: You have used a NODENAME with
Data Protection for WebSphere Application Server more than max_char characters.
profile is unknown or incorrect.
User Response: Correct the error and try again.
DKP1008E The MANAGEMENTCLASSNAME
DKP1001E Syntax error in file ’file name’. Exiting must be less than max_char characters.
Program.
Explanation: You have used a
Explanation: Tivoli Data Protection for WebSphere MANAGEMENTCLASSNAME with more than
Application Server has detected an syntax error in the max_char characters.
file file name and stops any action.
User Response: Use a shorter
User Response: Correct the error(s) in the file file name MANAGEMENTCLASSNAME.
and try again.
DKP1009W Please set MULTIPLEX to a number
DKP1002E BACKUPIDPREFIX must be between 1 and max_multiplex. Now it is
number_of_characters characters. set to act_multiplex.
Explanation: The length of BACKUPIDPREFIX must Explanation: You have set multiplexing to an
be number_of_characters characters. unsupported number. Tivoli Data Protection for
WebSphere Application Server now uses act_multiplex.
required length (e.g., TDP_WS). User Response: Set multiplexing to a number between
1 and max_multiplex.
DKP1004W You should specify the
BACKUPIDPREFIX before the DKP1010W The configfile name
TRACEFILE statement, so that the ’configuration_filename’ should be
BACKUPIDPREFIX can be used in the absolute.
tracefile name.
Explanation: None.
User Response: Specify an absolute file name, for
example /usr/tivoli/tsm/tdpwas/initWAS.bki
BACKUPIDPREFIX must be specified before the
TRACEFILE statement.
DKP1012E The configfilename
User Response: Define a 6-character
’configuration_filename’ could not be
BACKUPIDPREFIX in the Tivoli Data Protection for
opened.
WebSphere Application Server profile (e.g., TDP_WS).
Application Server is unable to read the file
DKP1005W The tracefile name ’trace_filename’ should
configuration_filename.
be absolute.
User Response: This error could have various reasons,
Explanation: None.
try the following:
User Response: Specify an absolute tracefile name, for 1. Check the path of the configuration file. The path
example /tmp/tdpws_tracefile. must be specified in the profile (parameter
CONFIG_FILE).
2. Make sure that the file access permissions are set
correctly.

DKP1013E Profile not found or permissions denied DKP1208E The object ’file name’ will be retried
: ’profile_filename’. [retry_num]
Explanation: Tivoli Data Protection for WebSphere Explanation: There was an error with the object
Application Server is unable to open the profile file_name. Tivoli Data Protection for WebSphere
profile_filename. Application Server will try to save/restore the object
one retry_num times.
User Response: Ensure that the profile initWAS.utl is
readable by Tivoli Data Protection for WebSphere User Response: Look at the error messages in the
Application Server. Tivoli Data Protection for WebSphere Application
Server protocol and solve the error for the next run.
DKP1016W The trace file name ’file name’ could not
be opened for writing! DKP1209E Object not found or not accessible
’objectname’.
writing. Explanation: Tivoli Data Protection for WebSphere
Application Server cannot locate the object objectname.
User Response: Ensure that you have specified a
correct path for the trace file. User Response: Check the file permissions for
objectname and try again. If the problem persists,
contact Tivoli Data Protection for WebSphere
DKP1017E The server ’server name’ is already
Application Server support.
defined. Please use another name!
DKP1211E There is something wrong with your
already defined.
CONFIG_FILE ’file name’.
User Response: Specify another server name. Server
Explanation: There is a problem with your Tivoli Data
names have to be unique.
Protection for WebSphere Application Server
configuration file setup.
DKP1200E Can’t read/write file: file name.
User Response: Check the file permission and the file
Explanation: Tivoli Data Protection for WebSphere name specified in the Tivoli Data Protection for
Application Server is unable to read or write a data file WebSphere Application Server profile keyword
(file name) of a tablespace being backed up or restored. CONFIG_FILE.
User Response: Check the file access permission of

the affected file(s). Try again. DKP1213I Program ended with code = ’return code’
Explanation: The return code of the program is
DKP1201E There are no Tivoli Storage Manager displayed.
Servers available.
Application Server cannot locate a Tivoli Storage
DKP1214E TSM Error: ’error text’
Manager server.
Explanation: The specified TSM error occurred.
User Response: Install and specify at least one Tivoli
Storage Manager server in the Tivoli Data Protection User Response: Check error text and correct the
for WebSphere Application Server profile (keyword problem.
SERVER).
DKP1215I Average transmission rate was ’number’
DKP1203E Not enough sessions available (number GB/h (’number’ MB/sec).
Explanation: The average transmission rate is
sessions available).
displayed.
Explanation: The sum of available sessions specified
in the server statement (parameter SESSIONS) does not
cover the required number of sessions (parameter
MAX_SESSIONS). DKP1216E There are no backup management
classes available.
corresponding parameters in the Tivoli Data Protection Explanation: The backup management classes you
for WebSphere Application Server profile, so that the have specified in your initWAS.utl file are not correct.
condition mentioned in the explanation is fulfilled.
DKP2005E Illegal parameter in message from Prole.
Exiting...
DKP1217E There are no archive management
Explanation: This error occurs if the versions of Prole
classes available.
and the other Tivoli Data Protection for WebSphere
Explanation: The archive management classes you Application Server modules do not match.
have specified in your initWAS.utl file are not correct.
User Response: Check the version of Prole and all
User Response: Check the management classes on the modules you are currently using.
DKP2006E General exception in dispatcher.
DKP2000I Successfully connected to PROLE on Exiting...
port portnumber.
Explanation: Internal Tivoli Data Protection for
Explanation: One of the Tivoli Data Protection for WebSphere Application Server error.
WebSphere Application Server modules initiated a
User Response: Contact Tivoli Data Protection for
successful connection to the background process Prole
WebSphere Application Server support.
on port portnumber.
DKP2007E Unknown Port: port
Explanation: The port specified for communication
DKP2001E Socket error while connecting to
with the background process Prole is unknown.
PROLE: reason.
User Response: Check the port value specified when
Explanation: The Tivoli Data Protection for WebSphere
Prole was started.
Application Server background process Prole is not
running or is listening on the wrong port.
DKP2008E Unable to connect to PROLE.
User Response: Check if the background process Prole
on the local or remote system is running and listening Explanation: Internal Tivoli Data Protection for
on port port number. The name of the system can be WebSphere Application Server error.
taken from the message preceding this one. It will be
one of the following: DKP8000I, DKP8003I, DKP8006I
or DKP8008I.
DKP2009I Deleting all versions with version

DKP2002E No valid callback function of type
Number <= version_number.
func_type supplied.
Explanation: All full database backups and their
Explanation: Internal Tivoli Data Protection for
corresponding redo log backups will be deleted from
WebSphere Application Server error
Tivoli Storage Manager storage, if their version number
User Response: Contact Tivoli Data Protection for is less than or equal to version_number.
DKP2003I File file_name, BID deleted.

DKP2010E Error occurred processing FRONTEND
Explanation: An error occurred during the frontend
BID was deleted from the Tivoli Storage Manager.
processing.
User Response: Check the frontend script/program
and the settings in the Tivoli Data Protection for
DKP2004E Connection to PROLE lost. WebSphere Application Server profile (keyword
FRONTEND) and try again.
Explanation: During Tivoli Data Protection for
WebSphere Application Server operation the connection
to Prole was lost. Network problems could be the DKP2011E Error occurred processing BACKEND.
reason.
Explanation: An error occurred during the backend
User Response: Check your network environment and processing.
and the settings in the Tivoli Data Protection for
WebSphere Application Server profile (keyword
BACKEND) and try again.

DKP2012E Passwords do not match. Try again. DKP2021E Unable to delete file ’file name’:
’description’
Explanation: The first and second password you
entered do not match. Explanation: Unable to delete the file ’file name’.
User Response: Enter the password correctly.
DKP2013I Starting FRONTEND Program.
Explanation: The frontend program is executing.
DKP2022E Unable to change mode of file ’file
User Response: None. name’: ’description’
DKP2014I FRONTEND program finished. ’description’ may contain the system error text.
Explanation: The frontend program is finished. User Response: Check the ’description’. If the error
DKP2023E Error occurred during trace connection

DKP2015I Starting BACKEND program. to Prole. Tracing will stop now.
Explanation: The backend program is executing. Explanation: Error occurred during trace connection
User Response: None. to Prole.
User Response: Tracing will stop. If the problem
DKP2016I BACKEND program finished. persists, contact your service representative.

DKP4000W The attributes of file ’file name’ cannot
User Response: None. be restored. Reason: errno (error_num)
error_desc.
DKP2017I Blocksize is set to num_bytes bytes. Explanation: The file file name was restored
Explanation: The operational blocksize of Tivoli Data successfully but one or more file attributes (permission,
Protection for WebSphere Application Server is ownership, date/time) of the file file name cannot be
num_bytes bytes. restored correctly.
User Response: None. User Response: Check the error number error_num
DKP2018E Exception in main message loop: set the appropriate correct permission for the file file
’description’ name manually.
Explanation: An error occurred during processing.
The error may contain a descriptive text. DKP4001E File ’file name’ cannot be created. Reason:
User Response: Contact your service representative. errno (error_num) error_desc.
DKP2019E Socket error while connecting to Prole be created/written. It is possible, that you do not have
on port ’number’ for tracing: ’description’ the appropriate rights for writing the file file name to
the destination path.
Explanation: During processing, a socket error
occurred on port ’number’. ’description’ may contain the User Response: Check the error number error_num
system error text. and the error description error_desc to avoid this
problem in the future. Furthermore, check the write
User Response: Check the ’description’. If the error permission of the user who started the restore.
DKP4002E Error during restore of file ’file name’.

DKP2020E Error occurred for trace connection to Reason: errno (error_num) error_desc.
Prole on port ’number’.
Explanation: The network connection that is used for process of the file file name.
tracing generated an error on port ’number’.
DKP5001E Tivoli Storage Manager Error:
error_message
Explanation: See DKP5000E.
DKP4003E Error reading file file name. Only read
num_bytes out of all_bytes. User Response: See DKP5000E.
Explanation: An error occurs reading the file file name.
Only num_bytes of all_bytes could be read. DKP5002E Tivoli Storage Manager Error:
error_message
still exists, contact Tivoli Data Protection for WebSphere Explanation: See DKP5000E.
Application Server support.
User Response: See DKP5000E.
DKP4004E Error writing file filename. Only wrote

error_message
still exists, contact Tivoli Data Protection for WebSphere
Application Server support. DKP5004E Tivoli Storage Manager Error:
error_message
DKP4005E Error allocating memory block for file Explanation: See DKP5000E.
file name. BLOCKSIZE may be too large.
Application Server was not able to request new
memory blocks during the backup of file file name. DKP5005E Tivoli Storage Manager Error:
error_message
for BLOCKSIZE. If you are not sure what value is Explanation: See DKP5000E.
valid, comment it out so the default value is used. User Response: See DKP5000E.
Furthermore, you can check if you have enough RAM
available with your machine. Also, check the memory
usage during backup. It may be necessary to stop DKP5006E Tivoli Storage Manager Error:
another application, increase memory, or change the error_message
configuration of Tivoli Data Protection for WebSphere Explanation: See DKP5000E.
Application Server.
DKP4006E Error allocating memory block for file

file name. BLOCKSIZE may be too large. DKP5007E Tivoli Storage Manager Error:
error_message

error_message DKP5008E Tivoli Storage Manager Error:
error_message
Explanation: During a connection of Tivoli Data
Protection for WebSphere Application Server to Tivoli Explanation: See DKP5000E.
Storage Manager server, a Tivoli Storage Manager error User Response: See DKP5000E.
error_message occurred.
User Response: Use the Tivoli Storage Manager DKP5009E Tivoli Storage Manager Error:
Messages guide and correct the Tivoli Storage Manager error_message

DKP5010E • DKP8009I
DKP5010E Tivoli Storage Manager Error: DKP8003I Host ″hostname″: start backup.
error_message
Explanation: The backup of files specific to
Explanation: See DKP5000E. WebSphere Application Server has been started on host
hostname.
User Response: Watch for the corresponding message
DKP8004I.
error_message
DKP8004I Host ″hostname″: backup with ID backup
ID successfully finished.
Explanation: The backup of the files specific to
WebSphere Application Server on host hostname has
DKP7009E Cannot connect to media manager. completed successfully.
Explanation: Tivoli Data Protection for WebSphere User Response: None.

Application Server is not able to connect to the Tivoli
Storage Manager server.
DKP8005I Now restoring number files for backup
User Response: Check the Tivoli Storage Manager API with ID backup ID.
Application Server will restore number files on the local
DKP7010E Permission denied. host.
Explanation: The permission for a connection to the User Response: None.

User Response: Check your Tivoli Storage Manager DKP8006I Host ″hostname″: start restore of database
client (API client) permission. For further information ″database name″.
Application Server is performing a restore of the
DKP8000I Host ″hostname″: start backup of database database name on host hostname.
database ″database name″.
Explanation: Tivoli Data Protection for WebSphere DKP8007I.
Application Server is now performing a backup of the
database database name on the host hostname.
DKP8007I Host ″hostname″: database ″database name″
User Response: Watch for the corresponding message successfully restored.
DKP8002I.
Explanation: The restore of the database database name
on host hostname has completed successfully.
DKP8001E Error: error message
Explanation: An error in one of the subcomponents
has been encountered. error message has been issued by
DKP8008I Host ″hostname″: start restore.
the corresponding subsystem, which should describe
the problem or reason of the error in more detail. Explanation: The restore of files specific to WebSphere
Application Server has been started on host hostname.
User Response: Correct the problem and try again.
DKP8009I.
DKP8002I Host ″hostname″: backup of database
database name with ID backup ID
successfully finished. DKP8009I Host ″hostname″: successfully restored.
Explanation: The backup of the database database name Explanation: The restore of files specific to WebSphere
on host hostname has completed successfully. Application Server has completed successfully.
DKP8010I • DKP8907W
DKP8010I Preparing to delete all files for backup DKP8017I Please enter the backup IDs to delete
ID backup ID. and press ENTER twice:
Explanation: All files loaded under backup ID backup Explanation: When you invoke Tivoli Data Protection
ID will now be deleted. for WebSphere Application Server with the option
’-delete’, you are prompted to enter the backup IDs to
delete.
User Response: Enter the backup IDs to delete. Press
DKP8011I Querying for files for backup with ID
ENTER after each backup ID. Press ENTER twice to
backup ID.
terminate the list.
Application Server is querying the Tivoli Storage
DKP8018I Found number backup IDs:
Manager server for all files that belong to the backup
ID backup ID. This may take some time. Explanation: Tivoli Data Protection for WebSphere
Application Server prints how many and which backup
IDs are currently stored on the TSM server.
DKP8012I Host ″hostname″: BID backup ID
successfully deleted.
DKP8904I User exit started on start_date_and_time.
Explanation: The backup ID backup ID has been
successfully deleted on the Tivoli Storage Manager Explanation: Log File Manager processing started on
server. start_date_and_time.
DKP8013I Administrative database was backed up DKP8905I User exit completed on

offline. Other hosts will be skipped. end_date_and_time.
Explanation: If all WebSphere Application Servers of Explanation: Log File Manager processing ended on
the current administrative domain are stopped, the end_date_and_time.
administrative database will be backed up in offline
mode. In this case, the other nodes of this domain
cannot be determined and are not backed up.
DKP8906I User exit completed with return code
User Response: Such a backup can only be used to
return_code.
restore the administrative database and nothing else.
Explanation: Log File Manager processing completed
with return code return_code.
DKP8015I Examining configuration.
User Response: If the return code is not 0, this
indicates that the Log File Manager could not complete
Application Server is determining the hosts of the
the request successfully. In this case, check the log for
WebSphere administrative domain and the objects on
error messages and respond to them. If the reason for a
each host to back up. This may take some time.
bad return code cannot be determined, save the log and
User Response: None. contact your service representative.
DKP8016I Please enter the backup ID to restore DKP8907W WARNING: The installed message
and press ENTER: catalog has an incompatible version
[version.release.modification_level.level]. The
Explanation: When you invoke Tivoli Data Protection
default English messages will be used
for WebSphere Application Server with the option ’-f
instead.
restore’, you will be prompted for the backup ID to
restore. See message DKP8018I. Explanation: A message catalog is installed, but its
version is not compatible with the version of the Log
User Response: Enter the ID of the backup you want
File Manager. Possible reason: The message catalog was
to restore and press the ENTER key.
installed with an earlier version of Tivoli Data
Protection for WebSphere Application Server. The Log
File Manager will use the default English messages
instead of the installed message catalog.

DKP8908W • DKP8930E
User Response: Install the current version of the
DKP8921E Error writing to file file: error_information.
message catalog.
Explanation: The Log File Manager could not write to
a file.
DKP8908W WARNING: The message catalog could
not be opened. The default English User Response: Check the error information given in
messages will be used instead. the message and respond accordingly.
Explanation: The Log File Manager was not able to
open the message catalog. Most probably, a message DKP8922E Error renaming file source_filename to
catalog was not installed in the path. Refer to the Tivoli new name target_filename:
Data Protection for WebSphere Application Server error_information.
documentation for assistance on how to install the
Explanation: The Log File Manager could not rename
message catalog.
a file.
User Response: Install the current version of the
User Response: Check the error information given in
message catalog.
the message and respond accordingly.
DKP8910E Invalid option option detected in call of

DKP8923E Error closing file file: error_information.
executable.
Explanation: The Log File Manager could not close a
Explanation: The Log File Manager was called with
file.
an invalid option.
User Response: If the Log File Manager was called by
DB2, save the log and call your service representative.
DKP8924E No access_mode access for path path_name:

DKP8911E Value for option option missing in call of
error_information.
executable.
Explanation: The required access is not granted for
path path. Processing has been stopped.
an option whose value was not specified.
DB2, save the log and call your service representative.
DKP8925W File file was not found. Nothing to be

DKP8912E Invalid option value value detected in
done.
call of executable.
Explanation: The Log File Manager was called with a
request for file file, but the file cannot be located. If this
an invalid option value.
was an archive request, an earlier request might not
User Response: If the Log File Manager was called by have returned to DB2 in time, so that DB2 retried the
DB2, save the log and call your service representative. action. If the earlier request succeeded in the meantime,
DB2 might have renamed the redo log file. If this was a
retrieve request the end of logs was probably reached.
DKP8913E Option(s) option_list missing in call of
executable. User Response: None.
Explanation: Required options are missing in a call of
the Log File Manager. DKP8929E Error setting up environment variable
variable: error_information.
DB2, save the log and call your service representative. Explanation: An environment variable could not be
set.
DKP8920E Error opening file file for mode mode: User Response: Check the error information given in
error_information. the message and respond accordingly.
Explanation: A file could not be opened by the Log
File Manager in the mode requested. DKP8930E Syntax error in file file, line line_number:
too many tokens.
the message and respond accordingly. Explanation: Too many tokens were encountered
while parsing file file at line line_number.
User Response: Correct the file syntax.
DKP8931E Syntax error in file file, line line_number: DKP8937E Required parameter keyword missing in
unknown parameter keyword. section for database database_name, node
node_number in profile file.
Explanation: An unknown keyword was encountered
in file file. Explanation: A required parameter was not specified
in the profile. Processing is stopped.
User Response: Correct the file contents by specifying
all required parameters.
DKP8932E Syntax error in file file, line line_number:
no value found for parameter keyword.
DKP8940E Error calling executable: error_information.
Explanation: A parameter value is missing in file file.
Explanation: An error occurred when calling an
executable.
User Response: Check the error information and
DKP8933E No section found for database
respond accordingly.
database_name, node node_number in
profile file.
DKP8941I Return code from call to executable:
Explanation: The profile for the Log File Manager
return_code
does not contain a section for the DB2 node issuing an
archive or retrieve request. There is no configuration Explanation: An executable was called and completed
information available for this request. Processing has with the return code indicated.
been stopped, and the request cannot be satisfied.
User Response: If the return code is not 0, this
User Response: Include a section of configuration indicates that the Log File Manager could not complete
information for the database node indicated in the the request successfully. In this case, check the log for
message in the Log File Manager profile. The section error messages and respond to them. If the reason for a
must start with the keywords bad return code cannot be determined, save the log and
LOG_DB_NAME database_name contact your service representative.
LOG_DB_NODE node_number
DKP8942E No output from call to executable.
DKP8934W Warning: Syntax error in file file, line Explanation: A called executable did not generate the
line_number: parameter keyword value output expected. Possible reasons:
ignored.
v The executable was not found or cannot be executed.
Explanation: The keyword in the indicated line of v The shell or command processor could not be
profile file was ignored. Possible reasons: started.
v More than one section for a specific DB2 node was
found in the profile for the Log File Manager. User Response: Check that the executable is accessible
in the path.
v A keyword was specified more than the allowed
number of times within a section.
DKP8998I Trace file: file
User Response: Correct file contents if necessary.
Explanation: Tracing is switched on. The trace can be
found in the path indicated.
DKP8935E Syntax error in file file, line line_number:
invalid parameter value value for User Response: None.
parameter keyword.
Explanation: The profile file contains an invalid DKP8999E Internal system error. Please contact
parameter value for keyword. your service representative. Error
information: error_information
User Response: Correct file contents.
Explanation: An internal system error occurred.
DKP8936E Inconsistent information found in User Response: Save the log and contact your service
output of executable: data. representative.
Explanation: An executable was called. When
analyzing its output, inconsistent information was
encountered.
User Response: Save the log and contact your service
representative.

DKP9000E System error: error

Application Server has found the following error: error.
This is a ’catch-all’ error code for unpredictable system
errors.
DKP9001E Internal error: error

Application Server has found the following internal
error: error.
Part 5. Appendixes

Appendix A. API Return Codes with Explanations
This appendix describes the return codes. The return codes are listed in numeric
order. For each return code, the following information is provided:
v The return code number. This number corresponds to the number in the dsmrc.h
header file.
v The severity code. This letter is an indication of the severity that generated the
return code. The possible severity codes and their meanings include:
S Severe error Processing cannot continue.

E Error Processing cannot continue.
W Warning Processing can continue, but problems might develop
later. You should be cautious.
I Information Processing continues. User response is not necessary.
v The symbolic name. This name corresponds to the definition in the header file,
dsmrc.h. Always use the symbolic name for a return code in your application rather
than the return code number.
v The explanation. This field explains the circumstances under which this return
code might be generated.
v The system action. This field describes what action TSM is going to take in
response to the return code.
v The user response. This field explains how you should respond to the system
action.
Many of the return codes describe errors that cause processing to stop. You can
send a message to the end user that describes the problem and suggest a course of
action. To identify different messages, use these return code values or develop your
own numbering system.

-452 E DSM_RC_SHM_NOTAUTH
Explanation: The user issuing the command does not
-056 E DSM_RC_TCPIP_DLL_LOADFAILURE
have authority to connect to the shared memory
segment. When the shared memory segment is created Explanation: An error occurred while loading a
by the server, it will be owned by the effective uid of library. The TCP/IP DLL load failed.
the server process (dsmserv). Only processes running
under this uid or root will be allowed to connect to the System Action: Processing stopped.
segment (and thus to the server). User Response: Verify your TCP/IP installation.
System Action: The session is rejected and processing
stops. -055 E DSM_RC_WINSOCK_MISSING
User Response: Run the command under the uid of Explanation: The TCP/IP WINSOCK.DLL file cannot
the processing running dsmserv, if possible. Otherwise be found.
contact your system administrator for further help.
-451 E DSM_RC_SHM_FAILURE User Response: Verify your TCP/IP installation.
Explanation: An error has occurred while reading or

writing data through the Shared Memory -054 E DSM_RC_NETWORK_UNREACHABLE
communications protocol. Explanation: The TCP/IP host name specified in the
System Action: TSM cannot complete the requested TCPSERVERADDRESS statement cannot be reached.
operation. System Action: Processing stopped.
User Response: Check the trace log for additional User Response: Check your options file for the correct
information and retry the operation. If the problem TCPSERVERADDRESS statement. See your
continues, see your system administrator for further administrator for the correct name of the server.
help.
-053 E DSM_RC_BAD_HOST_NAME
-450 E DSM_RC_SHM_TCPIP_FAILURE
Explanation: An invalid TCP/IP host name or address
Explanation: An attempt to connect to the local server was specified.
using the Shared Memory protocol has failed during
initial TCP/IP communications. This error can occur if System Action: Processing stopped.
the server is not listening on the correct port, or if the User Response: Check your options file for the correct
server is down. TCPSERVERADDRESS statement. See your
System Action: Session rejected. Processing stopped. administrator for the correct name of the server.
User Response: Retry the operation, or wait until the

server comes back up and retry the operation. If the -052 E DSM_RC_CONN_REFUSED
problem continues, see your system administrator for Explanation: An attempt to establish a TCP/IP
further help. connection was rejected by the server.
-124 E DSM_RC_3270COMM_MISSING_DLL
User Response: The server was not fully initialized, is
Explanation: The TSM DLL dsm3270.dll cannot be not currently running, was not enabled for TCP/IP
found in the user's path. communications, or an incorrect TCP/IP port number
System Action: Communications link is not was specified. If the problem continues, see your
established. system administrator.
User Response: Make sure that the TSM DLL

dsm3270.dll is in a directory that is included in the -051 E DSM_RC_CONN_TIMEDOUT
user's path. Explanation: The attempt to establish a TCP/IP
connection timed out before the connection was made.
-057 E DSM_RC_TCPIP_LOADFAILURE System Action: Processing stopped.
Explanation: An error occurred while locating a User Response: Check for a networking problem. If
function. The TCP/IP load function failed. the problem continues, see your system administrator.
System Action: Processing stopped. API applications should close the session with
dsmTerminate.

-050 E DSM_RC_TCPIP_FAILURE
Explanation: An attempt to connect to the server
0005 E DSM_RC_ABORT_NO_DATA
using TCP/IP communications failed. This error can
occur if the LAN connection went down or if your Explanation: TSM tried to do a restore or retrieve on
system administrator canceled a backup operation. an object that has no data associated with it.
System Action: Session rejected. Processing stopped. System Action: TSM ended the current operation.
User Response: Retry the operation, or wait until the User Response: See your system administrator to
server comes back up and retry the operation. If the verify the problem. If the problem continues, see your
problem continues, see your system administrator for system administrator.
further help.
0006 E DSM_RC_ABORT_BAD_VERIFIER
0000 I DSM_RC_OK
Explanation: You entered an incorrect password
Explanation: The operation successfully completed. (verifier).
System Action: None. System Action: Processing stopped.
User Response: None. User Response: Retry the session with the correct
password.
0001 E DSM_RC_ABORT_SYSTEM_ERROR
0007 E DSM_RC_ABORT_NODE_IN_USE
Explanation: The server detected a system error and
notified the clients. Explanation: The node you are running on is in use
by another operation on the server. This might be from
another client or from some activity on the server.
User Response: See your system administrator for
further information on server activity.
User Response: Retry the operation, or see your
system administrator to see what other operations are
0002 E DSM_RC_ABORT_NO_MATCH
running for your node.
Explanation: No objects on the server match the query
operation being performed. If this object is part of a
0008 E DSM_RC_ABORT_EXPDATE_TOO_LOW
backupset generated on a node, and the node name is
changed on the server, any backup set objects that were Explanation: Archive expiration date is too low, the
generated prior to the name change will not match the date must be greater than today’s date.
new node name.
User Response: Retry archiving the file with an
User Response: Ensure the names are properly expiration date that is higher than today’s date.
entered. If the object is part of a backupset generated
prior to a node name change, ensure that the node
name is the same as the node for which the backup set 0009 W DSM_RC_ABORT_DATA_OFFLINE
was generated. Explanation: For the restore or retrieve operation, one
or more of the requested files must be recalled from
0003 E DSM_RC_ABORT_BY_CLIENT offline storage media (generally tape). The wait time
depends on your site’s offline storage management
Explanation: The client system ended the operation policies.
with the server and ended the current transaction.
System Action: TSM waits for offline storage media to
System Action: Processing stopped. become available and then continues.
User Response: Restart the session. User Response: None.
0004 W DSM_RC_ABORT_ACTIVE_NOT_FOUND 0010 E DSM_RC_ABORT_EXCLUDED_BY_SIZE

Explanation: TSM did not find an active object Explanation: The object is too large. The configuration
flagged for expiration on the server. The object is of the server does not have any data storage space that
marked as expired by another TSM operation. accepts the object.
System Action: None. System Action: File skipped.
Appendix A. API Return Codes with Explanations 781

User Response: See your system administrator to v Server found a read error
determine the maximum file (object) size for which v File is temporarily involved in a reclaim operation at
your site’s server is configured. the server
v Server requested a tape volume that was marked
unavailable.
0011 E DSM_RC_ABORT_NO_REPOSIT_SPACE
Explanation: The server does not have any space
available to store the object. User Response: Retry the operation. If the problem
continues, see your system administrator to determine
the problem from the server console or the activity log.
User Response: You can take any of the following Check whether any requests were made for a tape
actions: volume that was unavailable. A tape volume may be
v Request the system administrator to add space to the marked unavailable if prior read errors were
storage pool. encountered or the volume is checked out of the tape
library.
v For TSM client, set COMPRESSALWAYS=NO and
COMPRESSIon=YES in the options file (DSM.OPT),
then the file will be resent uncompressed if it grows 0015 E DSM_RC_ABORT_RETRY
during compression.
Explanation: Unexpected Retry request. The server
v For API Applications, consult the application’s found an error while writing data to the server’s data
documentation for recommendations regarding storage.
compression.
System Action: Client retries the operation.
v Turn off disk caching in the disk storage pool, and
issue MOVE DATA commands to each disk pool User Response: None.
volume to clear out the cached bitfiles.
0016 E DSM_RC_ABORT_NO_LOG_SPACE
0012 E DSM_RC_ABORT_MOUNT_NOT_POSSIBLE
Explanation: The server ran out of recovery log space.
Explanation: Server media mount not possible. The
server timed out waiting for a mount of an offline
volume. User Response: This error is a temporary problem.
Retry later or see your system administrator.
User Response: Retry later when server volumes can
0017 E DSM_RC_ABORT_NO_DB_SPACE
be mounted. Ensure that the MAXNUMMP (maximum
number of mount points) defined on the server for this Explanation: The server ran out of database space.
node is greater than 0.
0013 E DSM_RC_ABORT_SIZESTIMATE_EXCEED User Response: See your system administrator.
Explanation: The total amount of data for a backup or

archive operation exceeds the estimated size originally 0018 E DSM_RC_ABORT_NO_MEMORY
sent to the server for allocating data storage space. This Explanation: The server ran out of memory.
happens when many files are growing by large
amounts while the backup or archive operation is in System Action: TSM ended the current operation.
session. User Response: This is a temporary problem. Retry
System Action: Processing stopped. later or see your system administrator.

continues, check what other processes are running on 0020 E DSM_RC_ABORT_FS_NOT_DEFINED
the client machine that are generating large amounts of Explanation: The specified file space does not exist on
data. Disable those operations while the backup or the server. Your system administrator deleted the file
archive operation is taking place. space or another client using your client’s node name
deleted it.
0014 E DSM_RC_ABORT_DATA_UNAVAILABLE System Action: TSM canceled the current operation.
Explanation: The file data is currently unavailable on User Response: Check the file space name to see if it
the server. A retrieve or restore operation was is correct, and retry the operation.
attempted. Possible causes are:
v Data was corrupted at the server

0021 S DSM_RC_ABORT_NODE_ALREADY_DEFED 0028 E DSM_RS_ABORT_RULE_ALREADY_DEFED
Explanation: Open registration failed because a node Explanation: You are trying to define authorization for
is defined in the server with the same name. the specified node, which already has authorization
defined.
System Action: TSM did not redefine authorization
User Response: Retry with another node name.
for the specified node.
User Response: Update the authorization, or delete
0022 S DSM_RC_ABORT_NO_DEFAULT_DOMAIN
the old rule and define a new one, or use the current
Explanation: Open registration failed because a authorization.
default policy domain does not exist for you to place
your node.
0029 S DSM_RC_ABORT_NO_STOR_SPACE_STOP
Explanation: The server does not have space available
User Response: See your system administrator. to store the object.
0023 S DSM_RC_ABORT_INVALID_NODENAME
User Response: Report to your system administrator
Explanation: Open registration failed because the that a storage pool on the server is full.
specified node name contains invalid characters.
System Action: TSM canceled the current operation. 0032 E DSM_RC_ABORT_DUPLICATE_OBJECT
User Response: Retry with another node name that Explanation: A duplicate object was found, operation
does not have any invalid characters. cannot complete.
0024 S DSM_RC_ABORT_INVALID_POL_BIND
User Response: Try the operation with a different file
Explanation: Server problem. Invalid policy binding. specification.
0033 E DSM_RC_ABORT_INVALID_OFFSET
check the error log. Explanation: The partialObjOffset value for partial
object retrieve is invalid.
0025 E DSM_RC_ABORT_DEST_NOT_DEFINED System Action: The system returns to the calling
procedure.
Explanation: Server problem: Destination not defined.
User Response: Have your service representative 0034 E DSM_RC_ABORT_INVALID_LENGTH
Explanation: partialObjLength value for partial object
retrieve is invalid.
0026 S DSM_RC_ABORT_WAIT_FOR_SPACE
Explanation: The client received an unexpected Wait procedure.
For Space message from the server.
User Response: See your system administrator. 0041 E DSM_RC_ABORT_EXCEED_MAX_MP
Explanation: All the tape mount points for this node
0027 E DSM_RC_ABORT_NOT_AUTHORIZED are in use.
Explanation: During a delete filespace operation, you System Action: The system returns to the calling
specified a file space to which your node does not have procedure.
permission to delete archived data and/or backed up
data. User Response: Increase the number of allowed tape
mounts for this node on the server.
System Action: Delete processing fails.

0045 E DSM_RC_ABORT_MERGE_ERROR 0053 E DSM_RC_REJECT_ID_UNKNOWN
Explanation: The specified objects failed the merge Explanation: The node name you entered is not
test, operation cannot complete. known by the server, or you are attempting to access a
file migrated to a different node.
User Response: See documentation for the merge test
You are not allowed to connect to the server until your
parameters.
node name is registered with the server. If attempting
to access a migrated file, your nodename must be the
0047 E DSM_RC_ABORT_INVALID_OPERATION same node which migrated the file.
Explanation: The operation is not valid. User Response: Ensure that you entered your TSM
node name correctly. If yes, see your system
System Action: TSM ended the current operation. administrator. Verify that the server is using closed
User Response: Contact your system administrator for registration and that your node name is registered with
more information. the server.
0048 E DSM_RC_ABORT_STGPOOL_UNDEFINED 0054 E DSM_RC_REJECT_DUPLICATE_ID
Explanation: The storage pool is not defined. Explanation: Another process using this node name is
active with the server.
System Action: TSM cannot connect to the server.
User Response: Contact your system administrator for TSM canceled the current operation.
more information.
User Response: If you are running a UNIX-based
system, ensure that another process is not active with
0049 E DSM_RC_ABORT_INVALID_DATA_FORMATTSM under the same name. Also, ensure that your
Explanation: none node name is unique to the server so that it cannot be
used by another person. See your system administrator
System Action: TSM ended the current operation. to identify the owner of that node name.
more information. 0055 E DSM_RC_REJECT_SERVER_DISABLED
Explanation: The server is in a disabled state and
0050 E DSM_RC_ABORT_DATAMOVER_UNDEFINED
cannot be accessed for normal activity.
Explanation: none System Action: TSM canceled the current operation.
System Action: TSM ended the current operation. User Response: Retry the operation after the server
User Response: Contact your system administrator for returns to an enabled state. If the problem continues,
more information. see your system administrator.
0051 E DSM_RC_REJECT_NO_RESOURCES 0056 E DSM_RC_REJECT_CLOSED_REGISTER
Explanation: TSM has all available sessions in use and Explanation: No authorization. Registration is
cannot accept a new one at this time. required by your system administrator. The server is
not configured to allow open registration.
System Action: Session not started.
continues, see your system administrator to increase the User Response: You must obtain a TSM node and
number of concurrently active sessions to the server. password from your system administrator.
0052 E DSM_RC_REJECT_VERIFIER_EXPIRED 0057 S DSM_RC_REJECT_CLIENT_DOWNLEVEL
Explanation: Your TSM password has expired. Explanation: The server version and your client
version do not match. The client code is downlevel.
You are not allowed to connect to the server until the System Action: TSM canceled the current operation.
password is updated. User Response: See your system administrator to see
User Response: Update your password. what version of TSM to run for your location.

0058 S DSM_RC_REJECT_SERVER_DOWNLEVEL 0065 E DSM_RC_REJECT_NO_LOG_SPACE
Explanation: The server version and your client Explanation: The server ran out of recovery log space.
version do not match. The server code is downlevel.
User Response: This error is a temporary problem.
User Response: See your system administrator to see Retry later or see your system administrator.
what version of TSM to run for your location.
0066 E DSM_RC_REJECT_INTERNAL_ERROR
0059 E DSM_RC_REJECT_ID_IN_USE
Explanation: The node name you specified is in use to the server because of an internal server error.
on the server.
User Response: See your system administrator
User Response: The server is probably performing a immediately.
task that prevents your node from establishing a
session. Retry later or check with your system
0067 S DSM_RC_SIGNONREJECT_INVALID_CLI
administrator.
requesting client type.
0061 E DSM_RC_REJECT_ID_LOCKED
Explanation: The node name you specified is currently
locked on the server.
0068 W DSM_RC_SESSION_CANCELED
to find out why your node name is locked.
Explanation: The server administrator canceled the
current client session.
0062 S DSM_RC_SIGNONREJECT_LICENSE_MAX
System Action: Execution of the client connection
request ends.
product license count for TSM.
0073 E DSM_RC_REJECT_INVALID_NODE_TYPE
Explanation: The user has probably coded the node
option incorrectly. For instance, the node that is
0063 E DSM_RC_REJECT_NO_MEMORY
registered to the TSM server might be a type of NAS,
Explanation: The server does not have enough but the node is actually a non-NAS client.
memory to allow your client to establish a connection
with the server.
User Response: Ensure that the node name is correct
in the client options file. Make sure to use a node of
User Response: Retry later or see your system type NAS only with the nasnodename option.
administrator.
0101 W DSM_RC_USER_ABORT
0064 E DSM_RC_REJECT_NO_DB_SPACE
Explanation: An abort signal to stop an operation was
Explanation: The server ran out of database space. received.
System Action: Session was not started. System Action: Processing stopped.
User Response: See your system administrator. User Response: Continue with normal operations.

ending other processes, or modify your system setup to
0102 E DSM_RC_NO_MEMORY
allow for more files to be open at the same time.
Explanation: The program has exhausted all available
storage.
0108 E DSM_RC_FILE_EXISTS
User Response: Free any unnecessary programs, for exists.
example, terminate and stay resident programs (TSRs),
System Action: File is replaced or skipped depending
that are running and retry the operation. Reducing the
on client options.
scope of queries and the amount of data returned can
also solve the problem. User Response: None.
0104 E DSM_RC_FILE_NOT_FOUND 0109 E DSM_RC_INVALID_PARM

Explanation: The file being processed for backup, Explanation: The system encountered an internal
archive or migrate no longer exists on the client. program error due to an invalid parameter.
Another process deleted the file before it could be
backed up, archived or migrated by TSM. System Action: The system returns to the calling
procedure.
User Response: Ask your service representative to
User Response: None. check the error log.
0105 E DSM_RC_PATH_NOT_FOUND 0110 E DSM_RC_INVALID_HANDLE

Explanation: You specified an incorrect directory path. Explanation: An internal system error occurred. A file
passed.
User Response: Correct the syntax specified and retry
the operation.
User Response: Report the problem to your system
administrator, and then retry the operation.
0106 E DSM_RC_ACCESS_DENIED
Explanation: The specified file is being used by
0111 E DSM_RC_DISK_FULL
another process. You tried to read from or write to a
file that is currently being used by another process. Explanation: No more files can be restored or
retrieved because the destination disk is full.
file or directory name, correct the permissions, or User Response: Free up disk space, or restore or
specify a new location. retrieve the file to another disk.
0106 E DSM_RC_ACCESS_DENIED 0113 E DSM_RC_PROTOCOL_VIOLATION

Explanation: Access to the specified file or directory is Explanation: A communications protocol error
denied. You tried to read from or write to a file and occurred. The communication subsystem is not
you do not have access permission for either the file or properly defined or is itself in error.
the directory.
User Response: Verify that the communication
User Response: Ensure that you specified the correct processes are operating properly, and then retry the
file or directory name, correct the permissions, or operation.
0114 E DSM_RC_UNKNOWN_ERROR
0107 E DSM_RC_NO_HANDLES
Explanation: All file handles for your system are be a low-level system or communication error that TSM
currently in use. No more are available. cannot handle or recover from.
User Response: Either free some file handles by User Response: Retry the operation. If the problem

0121 I DSM_RC_FINISHED
Explanation: The operation is finished.
0115 E DSM_RC_UNEXPECTED_ERROR System Action: The system returns to the calling
procedure.
Explanation: An unexpected error occurred. This
might be a low-level system or communication error User Response: Proceed with next function call.
that TSM cannot handle or recover from.
System Action: Processing stopped. 0122 E DSM_RC_UNKNOWN_FORMAT
User Response: Retry the operation. If the problem Explanation: TSM tried to restore or retrieve a file, but
continues, determine where the problem exists. See it had an unknown format.
0116 E DSM_RC_FILE_BEING_EXECUTED
Explanation: The current file cannot be opened to
0123 E DSM_RC_NO_AUTHORIZATION
write to because it is currently being run by another
operation. Explanation: The client is not authorized to restore the
other node's data.
User Response: Stop the operation that is running the
procedure.
file to a different name or directory. User Response: Get authorization from the other
node.
0117 E DSM_RC_DIR_NO_SPACE
0124 E DSM_RC_FILE_SPACE_NOT_FOUND
retrieved since the destination directory is full. Explanation: The specified file space (domain) is
incorrect or does not exist on the machine.
User Response: Free up disk space, or restore or
retrieve the file to another disk. User Response: Retry the operation specifying an
existing domain (drive letter or file system name).
0118 E DSM_RC_LOOPED_SYM_LINK
0125 E DSM_RC_TXN_ABORTED
many symbolic links were found. Explanation: The current transaction between the
server and the client stopped. A server, client, or
communication failure cannot be recovered.
continues, see your system administrator to isolate the
0119 E DSM_RC_FILE_NAME_TOO_LONG
problem.
Explanation: The file name specified is too long to be
handled by TSM.
0126 E DSM_RC_SUBDIR_AS_FILE
Explanation: TSM tried to create a directory path, but
User Response: See the appropriate Using the is unable to because a file exists that has the same
Backup-Archive Client book for the particular operating name as a directory.
system, for the file names that are handled by TSM.
0120 E DSM_RC_FILE_SPACE_LOCKED
name as the directory. Refer to the last restore/retrieve
Explanation: File system cannot be accessed because it operation and check all directories along the path.

0127 E DSM_RC_PROCESS_NO_SPACE 0133 E DSM_RC_FS_NOT_KNOWN
Explanation: The disk space allocated for the client Explanation: The number defining the correspondence
owner is full. between drive letter or file (domain name) and volume
label is not known to the server.
restore or retrieve operation. User Response: Report the program error to your
0128 E DSM_RC_PATH_TOO_LONG
0134 E DSM_RC_NO_LEADING_DIRSEP
Explanation: The path name specified plus the path
name in the restored file name combine to create a Explanation: The objName field does not have a
name whose length exceeds the system maximum. leading directory separator.
procedure.
combined, is less than the system maximum. User Response: Correct the value for the objName.
0129 E DSM_RC_NOT_COMPRESSED 0135 E DSM_RC_WILDCARD_DIR

Explanation: A file that was flagged as compressed Explanation: Wildcards are not allowed in the
was not compressed, and the system failed. objName directory path.
procedure.
report this problem. This error is a system failure. User Response: Correct the value for the objName.
0130 E DSM_RC_TOO_MANY_BITS 0136 E DSM_RC_COMM_PROTOCOL_ERROR

Explanation: You are trying to restore a file that was Explanation: Communications protocol error. An
backed up and compressed on another client unexpected communications message was received by
workstation that had more memory than your client the client.
not have enough memory. User Response: Verify that your communication path
is functioning properly. If the problem continues, have
your service representative check for a possible
User Response: Obtain a machine with more memory program error.
0137 E DSM_RC_AUTH_FAILURE
0131 S DSM_RC_SYSTEM_ERROR
Explanation: Authentication failure. You entered an
Explanation: An unexpected program failure occurred. incorrect password.
System Action: Processing stopped. System Action: TSM canceled the current operation.
User Response: Retry the operation. If the problem User Response: Enter your correct password. If you
continues, see your system administrator or your cannot remember the correct password, see your
service representative. system administrator to have a new one assigned for
your node name.
0132 E DSM_RC_NO_SERVER_RESOURCES
0138 E DSM_RC_TA_NOT_VALID
Explanation: The server ran out of resources. A lack of
storage or a condition does not allow any new activity. Explanation: The trusted agent execution/owner
permissions are invalid.
User Response: Retry the operation at a later time. If
the problem continues, see your system administrator User Response: Have your system administrator
to isolate what resource is unavailable. check the installation instructions for the client to

ensure that the trusted agent permissions are set
0150 S DSM_RC_UNKNOWN_FILE_DATA_TYPE
correctly.
Explanation: An unknown and unexpected error code
occurred within the client program. The structured file
0139 S DSM_RC_KILLED
data type is unknown. This is a programming failure
Explanation: Processing stopped. This is a and the client program ends.
User Response: Retry the operation. If the problem continues, contact your system administrator.
0151 S DSM_RC_BUFFER_OVERFLOW
0145 S DSM_RC_WOULD_BLOCK
Explanation: The data buffer overflowed. This is a
Explanation: The trusted agent blocks the operation. programming failure and the client program ends.
This is a programming failure and the client program
ends.
0154 E DSM_RC_NO_COMPRESS_MEMORY
Explanation: Not enough memory is available to do
0146 S DSM_RC_TOO_SMALL
data compression or expansion. For a restore or
Explanation: The area for the include/exclude pattern retrieve, the file cannot be recalled from the server until
is too small. This is a programming failure and the more storage is made available. For a backup or
client program ends. archive, try running without compression if storage
cannot be made available.
continues, contact your system administrator. User Response: Free up extra storage for the
operation to continue, or run the backup or archive
process without compression enabled.
0147 S DSM_RC_UNCLOSED
Explanation: There is no closing bracket in the 0155 T DSM_RC_COMPRESS_GREW
pattern. This is a programming failure and the client
program ends. Explanation: The size of the file after compressesion is
greater than the size of the file before compressed.
System Action: Even though the size of the file
User Response: Retry the operation. If the problem increased, the file is compressed.
0148 S DSM_RC_NO_STARTING_DELIMITER
0156 E DSM_RC_INV_COMM_METHOD
Explanation: The include or exclude pattern must start
with a directory delimiter. Explanation: You specified a communication method
that is not supported.
User Response: Correct the syntax for the pattern.
User Response: Specify a valid communication
interface for the TSM client and your operating system.
0149 S DSM_RC_NEEDED_DIR_DELIMITER
Explanation: The include/exclude pattern has a ’...’ 0157 S DSM_RC_WILL_ABORT
without a beginning or ending directory delimiter.
Explanation: The server encountered an error and will
System Action: Processing stopped. abort the transaction.
User Response: Correct the syntax for the pattern. System Action: The transaction will be aborted. The
reason code is passed on the dsmEndTxn call.
User Response: Issue the dsmEndTxn with a vote of

DSM_VOTE_COMMIT and examine the reason code. and then retry the operation. If unsuccessful, have your
service representative check the error log.
0158 E DSM_RC_FS_WRITE_LOCKED
0164 E DSM_RC_FIO_ERROR
Explanation: The file or directory being restored or
retrieved from the server cannot be written to because Explanation: An error was found while reading from
the destination is write locked. Another operation or writing to the file.
might have the file open and will not allow it to be
System Action: File or file system is skipped.
updated.
operating properly. For OS/2, run CHKDSK /F for the
User Response: Either determine which operation has failing drive which can be found in dsmerror.log.
or location.
0165 E DSM_RC_WRITE_FAILURE
0159 I DSM_RC_SKIPPED_BY_USER
file.
Explanation: A file was skipped during a restore
operation because the file is off line and the application
has chosen not to wait for a tape mount. User Response: Check your system to ensure that it is
operating properly.
User Response: Verify the application sets the
0166 E DSM_RC_OVER_FILE_SIZE_LIMIT
mountWait value correctly on dsmBeginGetData.
Explanation: A file being restored or retrieved exceeds
system set limits for this user.
0160 E DSM_RC_TA_NOT_FOUND
Explanation: TSM was unable to find the TSM Trusted
Agent module in the specified directory. The name of User Response: Ensure that the system limits are set
the TSM Trusted Agent module is dsmtca. properly.
0167 E DSM_RC_CANNOT_MAKE
User Response: Make sure the Trusted Agent module
is in the directory specified by DSMI_DIR. Explanation: The directory path for files being
restored or retrieved cannot be created.
0161 E DSM_RC_TA_ACCESS_DENIED System Action: File skipped.
Explanation: An attempt to access a system function User Response: Ensure that you have the proper
has been denied. authorization to create the directory for file being
restored or retrieved. Make sure that you have write
access.
0168 E DSM_RC_NO_PASS_FILE
0162 E DSM_RC_FS_NOT_READY
Explanation: The file containing the stored password
Explanation: The file system/drive was not ready for for the specified server-name is unavailable.
access.
User Response: The root user must set and store a
User Response: Ensure that the drive is available to new password.
TSM, and then retry the operation.
0169 E DSM_RC_VERFILE_OLD
0163 E DSM_RC_FS_IS_BAD
Explanation: Either the password is not stored locally,
Explanation: The drive was not available for access. A or it was changed at the server.
System Action: TSM prompts you for the password if
entry.
TSM is running in the foreground.
User Response: If TSM was running as a background
User Response: Ensure that the drive is operational, process, issue any TSM command from the foreground.

Enter the password in answer to the prompt. Then try User Response: Specify the file using the Include
your background TSM command again. option and retry the operation.
0173 E DSM_RC_INPUT_ERROR 0186 E DSM_RC_TL_NOACG

Explanation: Unable to read commands entered from Explanation: The management class for this file does
keyboard. TSM cannot process your intended not have an archive copy group specified. This file will
command. not be archived.
User Response: Ensure that you are entering a correct User Response: Add a valid archive copy group to the
command. management class, and then retry the operation.
0174 E DSM_RC_REJECT_PLATFORM_MISMATCH 0187 E DSM_RC_PS_INVALID_ARCHMC

Explanation: Your node name is associated with a Explanation: You entered an invalid management
different type of operating system (such as OS/2 or class.
AIX) and cannot be used on this system.
System Action: TSM canceled the current operation. operation.
User Response: If you need a new node name, see User Response: Retry the operation using a valid
your system administrator to assign a new one to you. management class.
Generally, you have a unique node name for each
machine and operating system pair that requires access
0188 S DSM_RC_NO_PS_DATA
to the server.
Explanation: Either no Active Policy Set data was
found on the server or a fromnode option contained a
0175 E DSM_RC_TL_NOT_FILE_OWNER
nodename not found on the server.
Explanation: The file cannot be backed up because the
client is not the file owner.
System Action: TSM skips the file.
0189 S DSM_RC_PS_INVALID_DIRMC
0177 S DSM_RC_UNMATCHED_QUOTE
assigned to directories.
Explanation: The quotes specified in the pattern are
User Response: Correct the pattern by using matching
quotes in the syntax.
0190 S DSM_RC_PS_NO_CG_IN_DIR_MC
Explanation: The management class used for
0184 E DSM_RC_TL_NOBCG
directories does not have a backup copy group.
not have a backup copy group specified. This file will
not be backed up. User Response: Have your service representative
User Response: Add a valid backup copy group to
0200 E DSM_RC_TCA_ATTACH_SHR_MEM_ERR
the management class, and then retry the operation.
Explanation: An error has occurred while attaching
the trusted agent’s shared memory.
0185 W DSM_RC_TL_EXCLUDED
System Action: Return to caller.
(file-name) that was specified to be excluded from User Response: Stop application, check shared
backup. memory usage and retry the command. Read the
tca.log file for the system error number.
System Action: TSM did not back up or migrate the
file.

0231 E DSM_RC_ABORT_MOVER_TYPE 0237E DSM_RC_ABORT_INVALID_GROUP_ACTION
Explanation: The specified Remote Mover type is Explanation: An invalid operation was attempted on a
unknown. logical group.
System Action: TSM ended the current operation. System Action: The current operation stops.
User Response: Contact your system administrator for User Response: Retry a valid operation.
more information.
0292 E DSM_RC_TCA_FORK_FAILED
0232 E DSM_RC_ABORT_ITEM_IN_USE
Explanation: An error has occurred starting the
Explanation: A request has been made to use a data Trusted Communication Agent process; specifically, the
mover to perform an operation for the indicated node fork() function has failed.
and filespace. Since an operation for this node and
filespace is already in progress, the new operation
cannot be performed. User Response: Probable system error. If the problem
persists, restart the workstation.
0294 E DSM_RC_TCA_DIED
Explanation: The Trusted Communication Agent has
0233 E DSM_RC_ABORT_LOCK_CONFLICT
terminated unexpectedly.
Explanation: A required resource is in use by another
command or process.
User Response: Check the error log for more
information. Retry the activity. If the problem persists,
User Response: Retry the operation at a later time. contact your service representative.
0234 E DSM_RC_ABORT_SRV_PLUGIN_COMM_ERROR
0295 E DSM_RC_TCA_INVALID_REQUEST
Explanation: Communication between a server plugin Explanation: The Trusted Communication Agent has
module and a NAS filer failed. received an unknown request from the TSM client.
System Action: TSM ended the current operation. System Action: TSM ends.
User Response: Contact your system administrator for User Response: Internal error. If the problem recurs,
more information. contact your service representative.
0235 E DSM_RC_ABORT_SRV_PLUGIN_OS_ERROR0296 E DSM_RC_TCA_NOT_ROOT

Explanation: A plugin module detected that a NAS Explanation: An activity has been attempted that must
filer is running an unsupported operating system or be performed by the TSM administrator (for example,
operating system level. open registration, filespace delete or password update).
System Action: TSM ended the current operation. System Action: TSM ends.
User Response: Contact your system administrator for User Response: If the activity is required, the
more information. administrator for this system must perform it.
0236E DSM_RC_ABORT_CRC_FAILED 0297 E DSM_RC_TCA_SEMGET_ERROR

Explanation: The server sent a CRC for a buffer. The Explanation: An error has occurred because the
client calculated a CRC for the same buffer. These did semaphores you are attempting to allocate have become
not match. The mismatch indicates a communication insufficient.
failure.
System Action: In some cases, the client can indicate
User Response: Ask your system administrator for
the failure to the server and retry the operation.
assistance, and possibly increase the number of
User Response: Check the trace log for additional semaphores in your system.
information and retry the operation. If the problem
persists, contact your system administrator.

0298 E DSM_RC_TCA_SEM_OP_ERROR 0409 E DSM_RC_INVALID_SERVER
Explanation: An error has occurred while attempting Explanation: The system options file does not contain
to set or wait on a semaphore. the SERVERNAME option.
System Action: Processing ends. System Action: TSM initialization fails and the
program ends.
User Response: Probable system error. If the problem
persists, restart the workstation. User Response: See the TSM administrator for your
system, and make sure that the system options file
contains the server name.
0400 E DSM_RC_INVALID_OPT
Explanation: An invalid option was found.
0410 E DSM_RC_INVALID_KEYWORD
Explanation: An invalid option keyword was found in
procedure.
the dsmInit configuration file, the option string,
User Response: Verify the options in dsm.opt, dsm.sys, or dsm.opt.
dsm.sys, and the options string. Check the error log for
more details about the error. on the AS/400 platform,
procedure.
verify the options in *LIB/QOPTTSM(APIOPT).
User Response: Correct the spelling of the option
keywords. Verify that the dsmInit configuration file
0405 E DSM_RC_NO_HOST_ADDR
only has a subset of the dsm.sys options. Check the
Explanation: The TCPSERVERADDRESS for this error log for more details about the error.
server is not defined in the server name stanza in the
system options file.
0411 S DSM_RC_PATTERN_TOO_COMPLEX
Explanation: The include or exclude pattern issued is
program ends.
too complex to be accurately interpreted by TSM.
User Response: See the TSM administrator for your
system, and make sure that the server to which you are
trying to connect, has a valid TCPSERVERADDRESS User Response: Recode the include or exclude pattern
defined in the system options file. as shown in one of the examples in the appropriate
Using the Backup-Archive Client book for the particular
operating system.
0406 S DSM_RC_NO_OPT_FILE
Explanation: The options file specified by file-name
0412 S DSM_RC_NO_CLOSING_BRACKET
cannot be found.
Explanation: The include or exclude pattern is
incorrectly constructed. The closing bracket is missing.
User Response: See if you have the environment
variable DSM_CONFIG (or DSMI_CONFIG for the API)
set, which explicitly identifies the TSM options file. ( User Response: Correct the syntax for the pattern.
You can do this by entering the SET command at your
system.) If this environment variable is set, ensure the
0600 E DSM_RC_DUP_LABEL
file indicated by the variable exists. If it is not set, then
TSM looks for the file dsm.opt in the current directory. Explanation: The selected drive has a duplicate
If neither of these cases is met, you receive this error volume label. Because TSM uses the volume label to
message. keep track of backup/archive information, it cannot
back up or archive files from a drive with a duplicate
volume label.
0408 E DSM_RC_MACHINE_SAME
Explanation: The NODENAME defined in the options
file cannot be the same as the system HostName. User Response: If the volume needs to be available to
System Action: Initialization fails and the program
ends.
User Response: See your system administrator or the
root user.

0601 E DSM_RC_NO_LABEL 0614 E DSM_RC_NLS_INVALID_TIME_FMT
Explanation: The selected drive does not have a label. Explanation: An invalid value is specified for
TIMEFORMAT.
operation without a drive or label entered. System Action: The system returns to the calling
procedure.
User Response: If the drive is a floppy drive, place a
disk with a volume label in it and retry the operation. User Response: Specify a valid value.
0615 E DSM_RC_NLS_INVALID_NUM_FMT
Explanation: An invalid value is specified for
0610 E DSM_RC_NLS_CANT_OPEN_TXT
NUMBERFORMAT.
Explanation: The system is unable to open the
message txt file (dscameng.txt or dsmclientV3.cat for
procedure.
AIX). On the AS/400 platform this file is
QANSAPI/QAANSAMENG(TXT). User Response: Specify a valid value.
procedure. 0620 E DSM_RC_LOG_CANT_BE_OPENED
User Response: Verify that the dscameng.txt file is in Explanation: The system is unable to open the error
the directory pointed to by DSMI_DIR. For AIX, verify log file.
that the dsmclientV3.cat file has a symbolic link to
/usr/lib/nls/msg/<locale>/dsmclientV3.cat . System Action: The system returns to the calling
procedure.
0611 E DSM_RC_NLS_CANT_READ_HDR User Response: Verify the DSMI_LOG value and

access permission. On the AS/400 platform, verify the
Explanation: The system is unable to use the message value specified for ERRORLOGNAME in the API
text file (dscameng.txt or dsmclientV3.cat for AIX) options file.
because of an invalid header. On the AS/400 platform
this file is QANSAPI/QAANSAMENG(TXT).
0621 E DSM_RC_LOG_ERROR_WRITING_TO_LOG
procedure. Explanation: There was an error writing to the log
file.
User Response: Install the message text file again.
procedure.
0612 E DSM_RC_NLS_INVALID_CNTL_REC
User Response: Verify the DSMI_LOG value and
Explanation: The system is unable to use the message access permission. on the AS/400 platform, verify the
txt file (dscameng.txt or dsmclientV3.cat for AIX) value specified for ERRORLOGNAME in the API
because of an invalid control record. On the AS/400 options file.
platform this file is QANSAPI/QAANSAMENG(TXT).
System Action: The system returns to the calling 0622 E DSM_RC_LOG_NOT_SPECIFIED
procedure.
Explanation: The system is unable to open the error
User Response: Install the message text file again. log file.
0613 E DSM_RC_NLS_INVALID_DATE_FMT procedure.
Explanation: An invalid value is specified for User Response: Verify the DSMI_LOG value and
DATEFORMAT. access permission. On the AS/400 platform, verify the
options file.
procedure.
0927 E DSM_RC_NOT_ADSM_AUTHORIZED
Explanation: User must be a TSM authorized user to
perform this action. User is not password authorized
and this action requires authorization.

User Response: User must be root user, or user must
2004 E DSM_RC_NULL_OBJATTRPTR
be the owner of the executable and the set effective
user id bit is set to ’on’ (’s’ bit). Explanation: There is no value provided for the object
attribute pointer.
961 E System Action: The system returns to the calling
DSM_RC_DIRECT_STORAGE_AGENT_UNSUPPORTED
procedure.
Explanation: You cannot connect directly to the
Storage Agent. User Response: Provide an address for the ObjAttr
structure.
User Response: To perform Lanfree operations using
2006 E DSM_RC_NO_SESS_BLK
the Storage Agent, specify the ENABLELANFREE
option in your options file, and restart the process. Explanation: The server did not respond with the
session information.
963 E DSM_RC_FS_NAMESPACE_DOWNLEVEL System Action: The system returns to the calling
procedure.
Explanation: TSM has detected that the server
namespace is NTW:LONG, but the local volume does User Response: Verify the server status.
not have long name support. If you would like to back
up the volume using the short names, rename the
2007 E DSM_RC_NO_POLICY_BLK
filespace on the server. If you would like to back up
using long names, add the long namespace support Explanation: The server did not respond with the
back to the volume in question. policy information.
procedure.
User Response: Add the long namespace support to
the volume or rename(remove) the corresponding User Response: Verify the server policy definitions.
server filespace.
2008 E DSM_RC_ZERO_BUFLEN
2000 E DSM_RC_NULL_OBJNAME
Explanation: The value for the dataBlk bufferLen is
Explanation: There is no value provided for the object zero.
name pointer.
procedure.
User Response: Provide a non-zero value for the
User Response: Provide an address for the bufferLen.
dsmObjName structure.
2009 E DSM_RC_NULL_BUFPTR
2001 E DSM_RC_NULL_DATABLKPTR
Explanation: There is no value provided for the
Explanation: There is no value provided for the data dataBlk bufferPtr.
block pointer.
procedure.
User Response: Provide an address for the bufferPtr.
User Response: Provide an address for the DataBlk
structure.
2010 E DSM_RC_INVALID_OBJTYPE
2002 E DSM_RC_NULL_MSG Explanation: The value for the objType is invalid.
Explanation: The message parameter for dsmRCMsg System Action: The system returns to the calling
is a NULL pointer. procedure.
System Action: The system returns to the calling User Response: The value for dsmObjName.objType
procedure. must be:
DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for
User Response: Allocate enough space for the Backup, or
message parameter.
DSM_OBJ_FILE for Archive.

2011 E DSM_RC_INVALID_VOTE 2017 E DSM_RC_INVALID_OBJNAME
Explanation: The dsmEndTxn vote is invalid. Explanation: The object name is invalid because of an
empty string or there is no leading delimiter.
procedure.
User Response: The vote must be
DSM_VOTE_COMMIT or DSM_VOTE_ABORT. User Response: Verify the format of the dsmObjName
full path.
2012 E DSM_RC_INVALID_ACTION
2018 E DSM_RC_INVALID_LLNAME
Explanation: The dsmUpdateFS or dsmUpdateObj
action is invalid. Explanation: The low level qualifier for the object
name is invalid.
procedure.
User Response: Correct the action value. Valid values
are defined in dsmapitd.h and documented in our User Response: Start the low level qualifier of the
Using the API book. object name with the directory delimiter.
2014 E DSM_RC_INVALID_DS_HANDLE 2019 E DSM_RC_INVALID_OBJOWNER

Explanation: The system encountered an error in the Explanation: The object owner must be either the root
API internals. user, or the object owner must be the same as the
session owner.
procedure.
User Response: Shut down the process and retry the
operation. Verify that any previous dsmInit calls were User Response: Verify the session owner and object
cleaned up and terminated by a dsmTerminate call. If owner.
the problem continues, contact your system
administrator or service representative.
2020 E DSM_RC_INVALID_ACTYPE
Explanation: The dsmBindMC sendType is invalid.
2015 E DSM_RC_INVALID_REPOS
Explanation: The repository type is invalid.
procedure.
procedure.
following:
User Response: For dsmDeleteFS the repository must stBackup
be one of the following:
stArchive
v DSM_ARCHIVE_REP
stBackupMountWait
v DSM_BACKUP_REP
stArchiveMountWait
v DSM_REPOS_ALL.
2021 E DSM_RC_INVALID_RETCODE
2016 E DSM_RC_INVALID_FSNAME
Explanation: The dsmRC parameter for dsmRCMsg is
Explanation: The filespace name is invalid. an unsupported return code.
User Response: Filespace name should start with the User Response: Specify a valid value.
directory delimiter.
2022 E DSM_RC_INVALID_SENDTYPE
Explanation: The dsmSendObj sendType is invalid.
procedure.

2028 E DSM_RC_INVALID_HLNAME
following:
stBackup Explanation: The high level qualifier for the object
name is invalid.
stArchive
stBackupMountWait System Action: The system returns to the calling
procedure.
stArchiveMountWait
User Response: High level qualifier of the object name
2023 E DSM_RC_INVALID_PARAMETER
Explanation: The dsmDeleteObj delType is invalid.
2029 E DSM_RC_NUMOBJ_EXCEED
Explanation: The number of objects (numObjId)
procedure.
specified on the dsmBeginGetData call exceeds
User Response: The delType must be dtBackup or DSM_MAX_GET_OBJ |
dtArchive. DSM_MAX_PARTIAL_GET_OBJ.
2024 E DSM_RC_INVALID_OBJSTATE procedure.
Explanation: The query Backup objState is invalid. User Response: Check the number of objects before
calling dsmBeginGetData. If it is greater than
System Action: The system returns to the calling DSM_MAX_GET_OBJ |
procedure. DSM_MAX_PARTIAL_GET_OBJ, then issue multiple
User Response: The qryBackupData.objState must be Get call sequences.
one of the following:
DSM_ACTIVE 2030 E DSM_RC_NEWPW_REQD
DSM_INACTIVE Explanation: There is no value provided for new
DSM_ANY_MATCH password.
2025 E DSM_RC_INVALID_MCNAME procedure.
Explanation: A query or send operation is unable to User Response: Provide a new password on
find the management class name. dsmChangePW.
procedure. 2031 E DSM_RC_OLDPW_REQD
User Response: Verify the management class name. Explanation: There is no value provided for old
password.
2026 E DSM_RC_INVALID_DRIVE_CHAR System Action: The system returns to the calling
procedure.
Explanation: The drive letter is not an alphabetic
character. This return code is valid on Microsoft User Response: Provide an old password on
Windows only. dsmChangePW.
procedure. 2032 E DSM_RC_NO_OWNER_REQD
User Response: Verify that the drive designation is an Explanation: PASSWORDACCESS=generate
alphabetic character. The referenced field is establishes a session with the current login user as the
dsmDosFSAttrib.driveLetter. owner.
2027 E DSM_RC_NULL_FSNAME procedure.
Explanation: There is no value provided for the User Response: When using
Register Filespace name. PASSWORDACCESS=generate, set clientOwnerNameP
to NULL.
procedure.
User Response: Provide a filespace name on
dsmRegisterFS.

2033 E DSM_RC_NO_NODE_REQD 2061 E DSM_RC_FS_NOT_REGISTERED
Explanation: PASSWORDACCESS=generate Explanation: On dsmSendObj, dsmDeleteObj, or
establishes a session with the current hostname as the dsmUpdateFS, the filespace is not registered.
node.
procedure.
User Response: Verify the filespace name.
PASSWORDACCESS=generate, set clientNodeNameP to
2062 W DSM_RC_FS_ALREADY_REGED
NULL.
Explanation: On dsmRegisterFS the filespace is
already registered.
2034 E DSM_RC_KEY_MISSING
Explanation: The key file for Tivoli Data Protection
procedure.
application client for Oracle cannot be found.
User Response: Verify the filespace name.
procedure.
2063 E DSM_RC_OBJID_NOTFOUND
Tivoli Data Protection application client which contains Explanation: On dsmBeginGetData, the objID is
TDP for Oracle, and install the key file. NULL.
2035 E DSM_RC_KEY_BAD procedure.
Explanation: The key file content for Tivoli Data User Response: Verify the following:
Protection application client for Oracle is invalid. The dsmGetList is not NULL.
System Action: The system returns to the calling Each objID is not NULL.
procedure. The dsmGetList numObjId is not zero.
Tivoli Data Protection application client which contains 2064 E DSM_RC_WRONG_VERSION
the TDP for Oracle, and install the key file.
Explanation: On dsmInit the caller's API version has a
higher value than the TSM library version.
2041 E DSM_RC_BAD_CALL_SEQUENCE
Explanation: The sequence of calls is invalid. procedure.
System Action: The system returns to the calling User Response: Install the latest TSM API library and
procedure. trusted agent module.
User Response: Verify the transaction call sequence.
2065 E DSM_RC_WRONG_VERSION_PARM
2050 E DSM_RC_WILDCHAR_NOTALLOWED Explanation: The caller's structure version is different
Explanation: On dsmSendObj, wildcards are not than the TSM library version.
allowed for the objName. System Action: The system returns to the calling
procedure. User Response: Ensure that the stVersion field is set
User Response: Provide a fs, hl, and ll on the with the value in the header file. Recompile the
dsmObjName. application with the latest header files.
2060 E DSM_RC_FSNAME_NOTFOUND 2070 E DSM_RC_NEEDTO_ENDTXN
Explanation: The filespace to delete cannot be found. Explanation: This transaction must be ended and a
new one must be started due to one of the following
System Action: The system returns to the calling reasons:
procedure.
The destination changed.
User Response: Verify the filespace name. The byte limit is exceeded
The maximum number of objects is exceeded.

System Action: The system returns to the calling User Response: The objInfo field must be less than or
procedure. equal to DSM_MAX_OBJINFO_LENGTH.
User Response: Issue dsmEndTxn and start a new
transaction session. 2102 E DSM_RC_HL_TOOLONG
Explanation: The sendObj dsmObjName.hl is too long.
2080 E DSM_RC_OBJ_EXCLUDED
Explanation: The backup or archive object is excluded procedure.
from processing.
User Response: The hl field must be less than or
System Action: The system returns to the calling equal to DSM_MAX_HL_LENGTH.
procedure.
User Response: Verify the objName and Exclude lists. 2103 E DSM_RC_PASSWD_TOOLONG
Explanation: The dsmChangePW password is too
2081 E DSM_RC_OBJ_NOBCG long.
Explanation: The backup object does not have a copy System Action: The system returns to the calling
group. procedure.
System Action: The system returns to the calling User Response: The password field must be less than
procedure. or equal to DSM_MAX_VERIFIER_LENGTH.
User Response: Verify server policy definitions.
2104 E DSM_RC_FILESPACE_TOOLONG
2082 E DSM_RC_OBJ_NOACG Explanation: The sendObj dsmObjName.fs is too long.
Explanation: The archive object does not have a copy System Action: The system returns to the calling
group. procedure.
System Action: The system returns to the calling User Response: The fs field must be less than or equal
procedure. to DSM_MAX_FS_LENGTH.
User Response: Verify server policy definitions.
2105 E DSM_RC_LL_TOOLONG
2090 E DSM_RC_APISYSTEM_ERROR Explanation: The sendObj dsmObjName.ll is too long.
Explanation: Memory used by the TSM API has been System Action: The system returns to the calling
corrupted. procedure.
System Action: The system returns to the calling User Response: The ll field must be less than or equal
procedure. to DSM_MAX_LL_LENGTH.
continues, contact your system administrator or service 2106 E DSM_RC_FSINFO_TOOLONG
representative.
Explanation: On RegisterFS or UpdateFS the fsAttr's
fsInfo is too long.
2100 E DSM_RC_DESC_TOOLONG
Explanation: The sendObj Archive description is too procedure.
long.
User Response: The fsInfo field must be less than or
System Action: The system returns to the calling equal to DSM_MAX_FSINFO_LENGTH.
procedure.
User Response: The sndArchiveData.descr string must 2107 E DSM_RC_SENDDATA_WITH_ZERO_SIZE
be less than or equal to DSM_MAX_DESCR_LENGTH.
Explanation: You cannot send data for an object with
size estimate = 0.
2101 E DSM_RC_OBJINFO_TOOLONG
Explanation: The sendObj ObjAttr.objInfo is too long. procedure.
System Action: The system returns to the calling User Response: Set size estimate greater than 0 in
procedure. dsmSendObj.

2110 E DSM_RC_INVALID_ACCESS_TYPE
Explanation: The dsmSetAccess accessType is invalid.
2200 I DSM_RC_MORE_DATA
Explanation: On dsmGetNextQObj or dsmGetData
procedure.
User Response: The accessType must be one of the
following:
procedure.
atBackup
User Response: Call the function again.
atArchive
2210 E DSM_RC_BUFF_TOO_SMALL
2111 E DSM_RC_QUERY_COMM_FAILURE
Explanation: The dataBlk buffer is too small for the
Explanation: An unexpected communications error
query response.
occurred during an object query to the server.
procedure.
User Response: Verify that communications are active
User Response: On dsmGetNextQObj ensure that the
between the client and server machines. Server outages,
dataBlk buffer is at least as big as the query response
processor outages, and communication controller
structure.
2228 E DSM_RC_NO_API_CONFIGFILE
2112 E DSM_RC_NO_FILES_BACKUP
Explanation: The configuration file specified on
Explanation: You tried to set access to files when no
were previously backed up. System Action: The system returns to the calling
procedure.
User Response: Verify the file name.
you to set access. 2229 E DSM_RC_NO_INCLEXCL_FILE
Explanation: The Include/Exclude definition file was
2113 E DSM_RC_NO_FILES_ARCHIVE not found.
Explanation: You tried to set access to files when no System Action: The system returns to the calling
files for the specified filename, drive or file system procedure.
were previously archived.
User Response: Verify the file name on the Inclexcl
System Action: Processing stopped. option.
system was specified and that files are archived for you 2230 E DSM_RC_NO_SYS_OR_INCLEXCL
to set access.
Explanation: Either the dsm.sys file was not found, or
the Inclexcl file specified in dsm.sys was not found.
2114 E DSM_RC_INVALID_SETACCESS
Explanation: None. procedure.
System Action: Processing stopped. User Response: The dsm.sys file must be in the
directory referenced by the environment variable
User Response: Enter the SET ACCESS command
DSMI_DIR. Verify the file name on the Inclexcl option
using the correct syntax.
in the dsm.sys file.
2120 E DSM_RC_STRING_TOO_LONG
2231 E DSM_RC_REJECT_NO_POR_SUPPORT
Explanation: The message text and inserts were too
Explanation: The TSM server specified by the user
large to send to the server in the available internal
does not support partial object retrieve.
buffer.
System Action: Refer to the local client error log for
procedure.
more information

User Response: Specify a TSM server which supports System Action: The system returns to the calling
the partial object retrieve function. procedure.
User Response: Check permissions on file. See if
2300 E DSM_RC_NEED_ROOT license file is in the correct place.
Explanation: Only a UNIX root user can execute
dsmChangePW or dsmDeleteFS. 2403 E DSM_RC__ALMGR_DATA_FMT
System Action: The system returns to the calling Explanation: The license file is not valid.
procedure.
User Response: Run this program as a root user. procedure.
2301 E DSM_RC_NEEDTO_CALL_BINDMC
Explanation: You must issue dsmBindMC before 2404 E DSM_RC_ALMGR_CKSUM_BAD
dsmSendObj.
Explanation: The registration string is not valid.
procedure.
procedure.
User Response: Modify your program.
2302 I DSM_RC_CHECK_REASON_CODE
2405 E DSM_RC_ALMGR_TRIAL_EXPRD
Explanation: After a dsmEndTxn call, the transaction
Explanation: The registration string is not valid.
is aborted by either the server or client with a
DSM_VOTE_ABORT and the reason is returned. System Action: The system returns to the calling
procedure.
procedure. User Response: User needs to obtain a new license.
User Response: Check the reason field for the code
which explains why the transaction has been aborted. 2410 E DSM_RC_ORC_INVALID_MODE
Explanation: Invalid mode passed by Oracle.
2400 E DSM_RC_ALMGR_OPEN_FAIL
Explanation: The license file was not found, or could procedure.
corrupted. User Response: Contact your system administrator.

procedure. 2411 E DSM_RC_ORC_NULL_FILENAME
User Response: Check permissions on file. See if the Explanation: Null filename passed by Oracle.
license file is in the correct place. System Action: The system returns to the calling
procedure.
2401 E DSM_RC_ALMGR_READ_FAIL User Response: Contact your system administrator.
Explanation: The license file was not found, or could
not be opened because of permissions, or the file is 2412 E DSM_RC_ORC_WRONG_BLKSIZE
corrupted.
Explanation: Wrong Block Size
procedure.
User Response: Check permissions on file. See if the
license file is in the correct place. User Response: Contact your system administrator.
2402 E DSM_RC_ALMGR_WRITE_FAIL 2413 E DSM_RC_ORC_OBJ_EXISTS
Explanation: The license file was not found, or could Explanation: Backup or Restore Object already exists.
not be opened because of permissions or the file is System Action: The system returns to the calling
corrupted. procedure.

User Response: If backing up an object, be sure to
generate a unique object name.
2414 E DSM_RC_ORC_NOTSAME_HANDLE
Explanation: The handle passed from Oracle is not the
same handle that TSM passed back.
procedure.
2415 E DSM_RC_ORC_END_OF_FILE
Explanation: End of file reached.
procedure.
User Response: None
2416 E DSM_RC_ORC_WRONG_RDSTATE
Explanation: The operation must be in READ state.
procedure.
2417 E DSM_RC_ORC_LOWER_APIVER
Explanation: Runtime API is lower than compile time
API.
procedure.
User Response: Use the WHAT command to find out
the compile time API level. Obtain the same or higher
level of API library.
2418 E DSM_RC_ORC_WRONG_WRTSTATE
procedure.
2419 E DSM_RC_ORC_INVALID_FLAG
Explanation: Invalid flag passed from Oracle.
procedure.

Appendix B. Allocating Additional Server Memory
If the server is low on memory, the following actions can be taken to allocate
additional storage resource for the server:
v 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.
v For VM, increase the size of the server’s virtual machine. This requires that the
default storage size be updated in the server’s CP directory entry.
v For OS/390 and z/OS, increase the size of the REGION parameter on the JOB or
EXEC statement of the JCL used to start the server.
A minimum size of 128MB is recommended for TSM, but larger servers will
require a larger region size.
v For Windows, the preferred method of solving a low memory condition is to
add physical memory to the system. Otherwise, increase the amount of the
system’s virtual memory. This can be done from the control panel by running
the system applet and increasing the total paging file size.
v For HP-UX, ensure that there is sufficient paging space and that a sufficient
amount of shared memory is available. For information on shared memory, refer
to the Tivoli Storage Manager Quick Start.
v For Sun Solaris, ensure that there is sufficient paging space. Consult your Sun
Solaris system documentation for details.
Reduce the maximum number of client sessions permitted. To do this, update the
value of the MAXSESSIONS parameter in the server options file and restart the
server.
Decrease the amount of space allocated to the server’s database or log buffer pool.
To do this, update the value of the BUFPOOLSIZE or LOGPOOLSIZE parameters
in the server options file and restart the server. Note that each page causes an
additional 4KB 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.

Appendix C. I/O Error Code Descriptions for Server Messages
This section contains code descriptions for possible I/O error messages from the
TSM server for the AIX and Windows NT® operating systems.
Code Description
OP I/O operation that failed. Some possible values displayed are:
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 “Operation Code Values for Tape Library Devices” on page 809 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” on page 806 for a list of completion codes. Refer to the IBM SCSI
Tape Drive, Medium Changer, and Library Device Drivers: Installation and User’s
Guide for information on tape library system calls and error description 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 = illegal request
6 = unit attention (for example, a SCSI bus reset)
7 = data protect
8 = blank check
9 = vendor specific
A = copy aborted
B = aborted 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. You should refer to the sense byte
number along with the value for a complete description of the common
values of the ASC and ASCQ codes. The drive or library reference manual
provided with the device usually contain tables explaining the values of
the KEY, ASC, and ASCQ fields. “Common Values for ASC and ASCQ
Codes” on page 809 also provides additional information on the common
values of ASC and ASCQ.

Completion Code and Operation Code Values
This section lists the completion code values for the following:
v All device classes
v Media changers
v Tape and optical drives
This section lists the operation code values for tape library devices. See “Operation
Code Values for Tape Library Devices” on page 809 for a description of the
operation codes.
Completion Code Values Common to All Device Classes

The following table shows the completion code values, in decimal and hexadecimal
numbers, common to all device classes. It provides a description for the I/O error
message and the recommended action. After performing the recommended action,
retry the failing operation. If the failing operation is not successful, contact TSM
support.
Table 1. Completion Code Values Common to All Device Classes
Decimal Hexadecimal Description Recommended Action
200 X'C8' The device indicated a failure condition, Retry the failing operation.
but sense data was unavailable.
201 X'C9' Device driver failure Contact TSM support.
202 X'CA' The device EEPROM failed. The device should be tested or serviced.
203 X'CB' Manual intervention required Correct the problem on the device. This
may be a stuck tape, dirty heads or a
jammed library arm.
204 X'CC' Recovered from an I/O error; for your No action necessary
information only
205 X'CD' SCSI adapter failure Check for loose cables, bent pins, bad
cables, bad SCSI adaptors, improper
termination or bad terminators.
206 X'CE' General SCSI failure Check for loose cables, bent pins, bad
cables, bad SCSI adaptors, improper
termination or bad terminators.
207 X'CF' Device is not in a state capable of Ensure the device is on and ready.
performing request Ensure the DEFINE DRIVE and DEFINE
DEVCLASS have been issued properly.
208 X'D0' Command aborted Contact TSM support.
209 X'D1' Device microcode failure detected Check the microcode level of the drive.
Call the drives manufacturer and
request latest level.
210 X'D2' The device was reset due to device Retry the failing operation.
power-up, SCSI bus reset, or manual
tape load/eject.
211 X'D3' The SCSI bus was busy. Ensure the SCSI ids are correctly
assigned to the correct device, and the
device is not being accessed by another
process.

Completion Code Values for Media Changers
numbers, for the media changers. It provides a description for the I/O error
support.
Table 2. Completion Code Values for Media Changers
300 X'12C' Cartridge entry/exit error Check the entry/exit ports for a jammed
volume.
301 X'12D' Cartridge load failure Check the drive for jammed volumes.
On AIX, display the errpt to check for
hardware errors.
302 X'12E' Cartridge in failed drive Check the drive for jammed volumes.
hardware errors.
303 X'12F' Carousel not loaded Ensure the carousel is correctly in place
and the door is shut.
304 X'130' Changer failure On AIX, display the errpt to check for
hardware errors.
305 X'131' Drive failure Ensure the heads have been cleaned. On
AIX, display the errpt to check for
hardware errors.
306 X'132' Drive or media failure Ensure the heads have been cleaned. On
AIX, display the errpt to check for
hardware errors.
307 X'133' Entry/exit failure Contact TSM support.
308 X'134' Entry/exit port not present Contact TSM support.
309 X'135' Library audit error Ensure that there are no jammed
volumes. It is possible that the library
audit is failing due to hardware errors.
hardware errors.
310 X'136' Library full Check for jammed volumes. Ensure the
volumes have not been rearranged. If
the library is not actually full, perform
an AUDIT LIBRARY.
311 X'137' Media export Contact TSM support.
312 X'138' Slot failure Ensure that nothing is jammed in the
slot.
313 X'139' Slot or media failure Ensure the volume is not jammed in the
slot and that the volumes have not been
rearranged. If problem persists, perform
an AUDIT LIBRARY.
314 X'13A' The source slot or drive was empty in Ensure the volumes have not been
an attempt to move a volume. rearranged. If problem persists, perform
an AUDIT LIBRARY.
315 X'13B' The destination slot or drive was full in Ensure the volumes have not been
an attempt to move a volume. rearranged, or that a volume is not
stuck in the drive. If problem persists,
perform AUDIT LIBRARY.
Appendix C. I/O Error Code Descriptions 807

Table 2. Completion Code Values for Media Changers (continued)
316 X'13C' Cleaner cartridge installed Contact TSM support.
317 X'13D' Media not ejected Ensure the volumes have not been
rearranged, or that a volume is not
stuck in the drive. If problem persists,
perform AUDIT LIBRARY.
318 X'13E' I/O port not configured Contact TSM support.
319 X'13F' First destination empty Ensure the volumes have not been
rearranged. If problem persists, perform
AUDIT LIBRARY.
320 X'140' No inventory information Perform AUDIT LIBRARY.
321 X'141' Read element status mismatch Contact TSM support.
322 X'142' Initialize range failed Contact TSM support.
Completion Code Values for Tape and Optical Drives

numbers, for tape and optical drives. It provides a description for the I/O error
support.
Table 3. Completion Code Values for Tape and Optical Drives
400 X'190' Physical end of media encountered Ensure the heads are clean on the drive.
402 X'192' Media corrupted Ensure the heads are clean and the
media is not physically damaged or too
old.
403 X'193' Media failure Ensure the heads are clean and the
media is not physically damaged or too
old.
404 X'194' Media incompatibility Ensure the correct length and type of
media is being used.
406 X'196' Sector requested is invalid. Internal server error. Contact TSM
support.
407 X'197' Write protect Ensure 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 the media is
not physically damaged or too old.
410 X'19A' Cleaning complete Retry the failing operation.
412 X'19C' Media not present in drive Ensure the media is correctly positioned
in the drive. If problem persists,
perform an AUDIT LIBRARY.
414 X'19E' Erase failure Clean the drive heads.
415 X'19F' Attempted to overwrite written WORM Internal server error. Contact TSM
media support.

Table 3. Completion Code Values for Tape and Optical Drives (continued)
416 X'1A0' An incorrect length block was read. Ensure the heads are clean. On AIX,
display the errpt to check for hardware
errors.
417 X'1A1' Open read only Contact TSM support.
418 X'1A2' Open write only Contact TSM support.
419 X'1A2' Media scan failed Clean the drive and media.
420 X'1A4' Logical write protect Ensure the heads have been cleaned.
Check operating system error logs for
hardware errors.
422 X'1A6' Cleaning required Clean the tape drive.
423 X'1A7' Optical media error Check operating system error logs for
hardware errors. Possible bad media.
Operation Code Values 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. Refer to the
Tape Library System Calls chapter in the IBM SCSI Tape Drive, Medium Changer, and
Library Device Drivers: Installation and User’s Guide for detailed information on
operation codes.
Table 4. 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 given message
ID.
X'6D38' MTIOCLQMID Query the status of the operation for a given message
ID.
X'6D39' MTIOCLSDC Assign a category to the automatic cartridge loader for a
specified device.
Common Values for ASC and ASCQ Codes

This section provides descriptions for common values of the ASC and ASCQ codes,
which are bytes 12 and 13 for SCSI-2 devices. For Windows NT , these codes also
appear in the Event Log. See “Windows NT Event Log Entries” on page 812.
See server message ANR8300E or ANR8302E for the recommended action.
The following table provides descriptions for common values of the ASC and
ASCQ codes. Each value has a prefix of 0x, which indicates that it is a hexadecimal
constant.

Table 5. Common Values for ASC and ASCQ Codes
ASC ASCQ Description
0x00 0x00 No additional sense
0x00 0x01 Filemark detected
0x00 0x02 End-of-medium detected
0x00 0x03 Setmark detected
0x00 0x04 Beginning of medium
0x00 0x05 End of data
0x00 0x06 I/O process terminated
0x02 0x00 No seek complete
0x03 0x00 Device write fault
0x03 0x01 No write current
0x03 0x02 Excessive write errors
0x04 0x00 Logical unit not ready
0x04 0x01 Becoming ready
0x04 0x02 Not ready, initializing command required
0x04 0x03 Not ready, manual intervention required
0x04 0x04 Not ready, formatting
0x05 0x00 No response to select
0x06 0x00 No reference position found
0x07 0x00 Multiple devices selected
0x08 0x00 Communication failure
0x08 0x01 Communication timeout
0x08 0x02 Communication parity error
0x09 0x00 Track following error
0x0A 0x00 Error log overflow
0x0C 0x00 Write error
0x11 0x00 Unrecovered read error
0x11 0x01 Read retries exhausted
0x11 0x02 Error too long to correct
0x11 0x03 Multiple read errors
0x11 0x08 Incomplete block read
0x11 0x09 No gap found
0x11 0x0A Miscorrected error
0x14 0x00 Recorded entity not found
0x14 0x01 Record not found
0x14 0x02 Filemark/setmark not found
0x14 0x03 End-of-data not found
0x14 0x04 Block sequence error
0x15 0x00 Random positioning error
0x15 0x01 Mechanical positioning error
0x15 0x02 Read positioning error

Table 5. Common Values for ASC and ASCQ Codes (continued)
0x17 0x00 No error correction applied
0x17 0x01 Recovered with retries
0x17 0x02 Recovered with positive head offset
0x17 0x03 Recovered with negative head offset
0x18 0x00 ECC applied
0x1A 0x00 Parameter list length error
0x1B 0x00 Synchronous data transfer error
0x20 0x00 Invalid operation code
0x21 0x00 Block out of range
0x21 0x01 Invalid element address
0x24 0x00 Invalid field in CDB
0x25 0x00 LUN not supported
0x26 00 Invalid field in parameter list
0x26 0x01 Parameter not supported
0x26 0x02 Parameter value invalid
0x26 0x03 Threshold parameters not supported
0x27 0x00 Write protected
0x28 0x00 Not-ready to ready
0x28 0x01 Import/export element accessed
0x29 0x00 Power-on, reset, bus reset
0x2A 0x00 Parameters changed
0x2A 0x01 Mode parameters changed
0x2A 0x02 Log parameters changed
0x2B 0x00 Copy cannot execute
0x2C 0x00 Command sequence error
0x2D 0x00 Overwrite error on update
0x2F 0x00 Command cleared by initiator
0x30 0x00 Incompatible media
0x30 0x01 Media unknown format
0x30 0x02 Media incompatible format
0x30 0x03 Cleaning cartridge installed
0x31 0x00 Media format corrupted
0x33 0x00 Tape length error
0x37 0x00 Rounded parameter
0x39 0x00 Saving parameters not supported
0x3A 0x00 Medium not present
0x3B 0x00 Sequential positioning error
0x3B 0x01 Positioning error at BOT
0x3B 0x02 Positioning error at EOT
0x3B 0x08 Reposition error

Table 5. Common Values for ASC and ASCQ Codes (continued)
0x3B 0x0D Medium destination element full
0x3B 0x0E Medium source element empty
0x3D 0x00 Invalid bits in message
0x3E 0x00 LUN not self-configured
0x3F 0x00 Operating conditions changed
0x3F 0x01 Microcode has been changed
0x3F 0x02 Changed operating definition
0x3F 0x03 Inquiry data has changed
0x43 0x00 Message error
0x44 0x00 Internal target failure
0x45 0x00 Select/reselect failure
0x46 0x00 Unsuccessful soft reset
0x47 0x00 SCSI parity error
0x48 0x00 Initiator detected message received
0x49 0x00 Invalid message error
0x4A 0x00 Command phase error
0x4B 0x00 Data phase error
0x4C 0x00 LUN failed self-configuration
0x4E 0x00 Overlapped commands attempt
0x50 0x00 Write append error
0x50 0x01 Write append position error
0x50 0x02 Position error (timing)
0x51 0x00 Erase failure
0x52 0x00 Cartridge fault
0x53 0x00 Load/media eject failed
0x53 0x01 Unload tape failure
0x53 0x02 Media removal prevented
0x5A 0x00 Operator state changed
0x5A 0x01 Operator media removal
0x5A 0x02 Operator write protect
0x5A 0x03 Operator write permit
0x5B 0x00 Log exception
0x5B 0x01 Threshold condition met
0x5B 0x02 Log counter at maximum
0x5B 0x03 Log list codes exhausted
Windows NT Event Log Entries

The code values will appear as hexadecimal values in the Data area of the
Windows NT Event Log. The Event Log omits the 0x prefix for the displayed
information.

In the NT Event Log, the entries with source AdsmScsi are produced by the
AdsmScsi device driver. In these entries, byte 44 is the sense key, byte 43 is the
ASC, and byte 42 is the ASCQ. (This is also true of entries logged by any of the
NT tape device drivers.) 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.

Appendix D. Device Errors in AIX System Error Log
TSM logs certain device errors in the AIX system error log. This section provides a
brief description of the device error. It also provides the detail data and a
description of the data. For a detailed description of the AIX error logging facility
and of the information contained within an error report, refer to AIX Version 4
Problem Solving Guide and Reference.
DEVICE ERROR and ERROR DESCRIPTION
ADSM_DD_LOG1 (0xAC3AB953)
DEVICE DRIVER SOFTWARE ERROR
This error is logged by the ADSM device driver when a problem is
suspected in the ADSM device driver software. For example, if the ADSM
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 ADSM support personnel.
Detail Data: Sense Data
The sense data consists of information that can determine the cause of the
error. All data in the error entry should be reported to ADSM support
personnel.
ADSM_DD_LOG2 (0x5680E405)
HARDWARE/COMMAND-ABORTED ERROR
This error is logged by the ADSM device driver when the device reports a
particular hardware error or command-aborted error in response to a SCSI
I/O command.
The sense data consists of information that can determine the exact cause
of the error; in this case, which hardware component failed and why. To
interpret the sense data for a particular device, refer to the device’s SCSI
specification manual.
ADSM_DD_LOG3 (0x461B41DE)
MEDIA ERROR
This error is logged by the ADSM device driver when a SCSI I/O
command fails because of corrupted or incompatible media, or because a
drive requires cleaning.
The sense data consists of information that can determine the exact cause
of the error. To interpret the sense data for a particular device, refer to the
device’s SCSI specification manual.
ADSM_DD_LOG4 (0x4225DB66)
TARGET DEVICE GOT UNIT ATTENTION
This error is logged by the ADSM device driver after receiving certain
UNIT ATTENTION notifications from a device. UNIT ATTENTIONs are
informational and usually indicate that some state of the device has
changed. For example, this error would be logged if the door of a library

device was opened and then closed again. Logging this event indicates that
the activity occurred and that the library inventory may have been
changed.
The sense data consists of information that describes the reason for the
UNIT ATTENTION. To interpret the sense data for a particular device,
refer to the device’s SCSI specification manual.
ADSM_DD_LOG5 (0xDAC55CE5)
PERMANENT UNKNOWN ERROR
This error is logged by the ADSM device driver after receiving an
unknown error from a device in response to a SCSI I/O command. If the
error persists, report it to ADSM support personnel.
The sense data consists of information that can determine the cause of the
error. All data in the error entry should be reported to ADSM support
personnel.
ADSM_DD_LOG6 (0xBC539B26)
WARNING OR INFORMATIONAL MESSAGE FOR TARGET DEVICE
This error is logged by the ADSM device driver after receiving a warning
or informational message from a device in response to a SCSI I/O
command. These are informational messages and may not be an indication
of a problem. If the message persists, report it to ADSM support personnel.
The sense data consists of information that can determine the reason for
the message. All data in the message entry should be reported to ADSM
support personnel.

Appendix E. 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 give 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 (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, 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.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Information Enabling Requests
Dept. M13
5600 Cottle Road
San Jose CA 95193-0001
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.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Programming Interface
This publication is intended to help the customer with the Tivoli Storage Manager
messages.
This publication documents information that is not intended to be used as

programming interfaces of the Tivoli Storage Manager.

Trademarks
The following terms are trademarks of the International Business Machines
Corporation in the United States or other countries or both:
Advanced Peer-to-Peer Networking OpenEdition
AIX Operating System/2
Application System/400 Operating System/400
APPN OS/2
AS/400 OS/390
DB2 OS/400
DFDSM POWERparallel
DFS RACF
DFSMS/MVS Redbooks
DFSMShsm RISC System/6000
DFSMSrmm RS/6000
DPI SAA
Enterprise Storage Server SANergy
ESCON SP
Extended Services System/370
FlashCopy System/390
IBM SystemView
IBMLink Tivoli
Magstar Tivoli Enterprise Console
MVS Tivoli Management Environment
MVS/ESA TME
MVS/SP VTAM
NetView z/OS
Lotus, Lotus 1–2–3, Lotus Approach®, Lotus Domino and Lotus Notes are
trademarks of Lotus Development Corporation in the United States and/or other
countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States and/or other countries.
UNIX® is a registered trademark of the Open Group in the United States and/or
other countries.
Java™ and all Java-based trademarks and logos are trademarks of Sun
Microsystems, Inc. in the United States and/or other countries.
Intel is a registered trademark of the Intel Corporation in the United States and/or
other countries.
Other company, product, and service names may be trademarks or service marks
of others.
Appendix E. Notices 819

Glossary
The terms in this glossary are defined as they pertain to the Tivoli Storage Manager library. If you do not find the
term you need, refer to the IBM Software Glossary on the Web at this URL: www.ibm.com/ibm/terminology/. You
can also refer to IBM Dictionary of Computing, New York: McGraw-Hill, 1994.
This glossary may include terms and definitions from:

v The American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright (ANSI). Copies may
be purchased from the American National Standards Institute, 11 West 42nd Street, New York 10036.
v The Information Technology Vocabulary, developed by Subcommittee 1, Joint Technical Committee 1, of the
International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC
JTC2/SC1).
A administrative command schedule. A database record

that describes the planned processing of an
administrative command during a specific time period.
absolute mode. A backup copy group mode indicating
See also client schedule.
that specifies that a file is considered for incremental
backup even if the file has not changed since the last administrative privilege class. See privilege class.
backup. See also mode. Contrast with modified mode.
administrative session. A period of time in which an
access mode. An attribute of a storage pool or a administrator user ID communicates with a server to
storage volume that specifies whether the server can perform administrative tasks. Contrast with client node
write to or read from the storage pool or storage session.
volume. The access mode can be read/write, read-only,
or unavailable. Volumes in primary storage pools can administrator. A user who has been registered to the
also have an access mode of destroyed. Volumes in server. Administrators can be authorized to one or
copy storage pools can also have an access mode of more of the following administrative privilege classes:
offsite. system, policy, storage, operator, or analyst.
Administrators can use the administrative commands
activate. To validate the contents of a policy set and and queries allowed by their privileges.
make it the active policy set.
aggregate file. A file, stored in one or more storage
active policy set. The activated policy set that contains pools, consisting of a group of logical files packaged
the policy rules currently in use by all client nodes together. See logical file and physical file.
assigned to the policy domain. See also policy domain
and policy set. analyst privilege class. A privilege class that allows
an administrator to reset statistics. See also privilege
active version. The most recent backup copy of a file class.
stored by Tivoli Storage Manager. The active version of
a file cannot be deleted until a backup process detects application client. One of the Tivoli Data Protection
that the user has either replaced the file with a newer programs installed on a system to protect an
version or has deleted the file from the workstation. application. The Tivoli Storage Manager server
Contrast with inactive version. provides backup services to an application client.
activity log. A log that records normal activity archive. To copy one or more files to a storage pool
messages generated by the server. These messages for long-term storage. Archived files can include
include information about server and client operations, descriptive information and can be retrieved by archive
such as the start time of sessions or device I/O errors. date, by file name, or by description. Contrast with
Each message includes a message ID, date and time retrieve.
stamp, and a text description. The number of days to
retain messages in the activity log can be specified. archive copy. A file that has been archived to server
storage.
administrative client. A program that runs on a file
server, workstation, or mainframe that administrators archive copy group. A policy object containing
use to control and monitor the Tivoli Storage Manager attributes that control the generation, destination, and
server. Contrast with backup-archive client.

expiration of archive copies. An archive copy group backup-archive client. A program that runs on a
belongs to a management class. workstation or file server and provides a means for
users to back up, archive, restore, and retrieve files.
archive retention grace period. The number of days Contrast with administrative client.
that Tivoli Storage Manager retains an archive copy
when the server is unable to rebind the file to an backup copy group. A policy object containing
appropriate management class. attributes that control the generation, destination, and
expiration of backup versions of files. A backup copy
assigned capacity. The portion of available space that group belongs to a management class.
can be used to store database or recovery log
information. See also available space. backup retention grace period. The number of days
that Tivoli Storage Manager retains a backup version
association. (1) The defined relationship between a after the server is unable to rebind the file to an
client node and a client schedule. An association appropriate management class.
identifies the name of a schedule, the name of the
policy domain to which the schedule belongs, and the backup set. A portable, consolidated group of active
name of a client node that performs scheduled backup versions of files, generated for a backup-archive
operations. (2) On a configuration manager, the defined client.
relationship between a profile and an object such as a
policy domain. Profile associations define the backup version. A file that a user backed up to server
configuration information that will be distributed to a storage. More than one backup version can exist in
managed server when it subscribes to the profile. server storage, but only one backup version is the
active version. See also active version and inactive
audit. To check for logical inconsistencies between version.
information that the server has and the actual condition
of the system. Tivoli Storage Manager can audit binding. The process of associating a file with a
volumes, the database, libraries, and licenses. For management class name. See rebinding.
example, when Tivoli Storage Manager audits a
volume, the server checks for inconsistencies between buffer pool. Temporary space used by the server to
information about backed-up or archived files stored in hold database or recovery log pages. See database buffer
the database and the actual data associated with each pool and recovery log buffer pool.
backup version or archive copy in server storage.
authentication. The process of checking a user’s

C
password before allowing that user access to the server. cache. The process of leaving a duplicate copy on
Authentication can be turned on or off by an random access media when the server migrates a file to
administrator with system privilege. another storage pool in the hierarchy.
authority. The right granted to a user to perform tasks central scheduler. A function that allows an
with Tivoli Storage Manager servers and clients. See administrator to schedule client operations and
also privilege class. administrative commands. The operations can be
scheduled to occur periodically or on a specific date.
autochanger. A small, multislot tape device that
See client schedule and administrative command schedule.
automatically puts tape cartridges into tape drives. See
also library. client. A program running on a PC, workstation, file
server, LAN server, or mainframe that requests services
available space. The amount of space, in megabytes,
of another program, called the server. The following
that is available to the database and recovery log. This
types of clients can obtain services from a Tivoli
space can be used to extend the capacity of the
Storage Manager server: administrative client,
database or recovery log, or to provide sufficient free
application client, API client, backup-archive client, and
space before a volume is deleted from the database or
HSM client (also known as Tivoli Space Manager).
recovery log.
client domain. The set of drives, file systems, or
B volumes that the user selects to back up or archive
using the backup-archive client.
back up. To copy information to another location to
ensure against loss of data. In Tivoli Storage Manager, client migration. The process of copying a file from a
you can back up user files, the Tivoli Storage Manager client node to server storage and replacing the file with
database, and storage pools. Contrast with restore. See a stub file on the client node. The space management
also database backup series and incremental backup. attributes in the management class control this
migration. See also space management.

client node. A file server or workstation on which the configuration manager. One Tivoli Storage Manager
backup-archive client program has been installed, and server that distributes configuration information to
which has been registered to the server. other Tivoli Storage Manager servers (called managed
servers) via profiles. Configuration information can
client node session. A period of time in which a client include policy and schedules. See managed server and
node communicates with a server to perform backup, profile.
restore, archive, retrieve, migrate, or recall requests.
Contrast with administrative session. copy group. A policy object whose attributes control
how backup versions or archive copies are generated,
client options file. A file that a client can change, where backup versions or archive copies are initially
containing a set of processing options that identify the located, and when backup versions or archive copies
server, communication method, and options for backup, expire. A copy group belongs to a management class.
archive, hierarchical storage management, and See also archive copy group, backup copy group, backup
scheduling. Also called the dsm.opt file. version, and management class.
client-polling scheduling mode. A client/server copy storage pool. A named set of volumes that
communication technique where the client queries the contains copies of files that reside in primary storage
server for work. Contrast with server-prompted pools. Copy storage pools are used only to back up the
scheduling mode. data stored in primary storage pools. A copy storage
pool cannot be a destination for a backup copy group,
client schedule. A database record that describes the an archive copy group, or a management class (for
planned processing of a client operation during a space-managed files). See primary storage pool and
specific time period. The client operation can be a destination.
backup, archive, restore, or retrieve operation, a client
operating system command, or a macro. See also
administrative command schedule. D
client system options file. A file, used on UNIX damaged file. A physical file for which Tivoli Storage
clients, containing a set of processing options that Manager has detected read errors.
identify the Tivoli Storage Manager servers to be
contacted for services. This file also specifies database. A collection of information about all objects
communication methods and options for backup, managed by the server, including policy management
archive, hierarchical storage management, and objects, users and administrators, and client nodes.
scheduling. Also called the dsm.sys file. See also client
user options file. database backup series. One full backup of the
database, plus up to 32 incremental backups made
client user options file. A user-created file, used on since that full backup. Each full backup that is run
UNIX clients, containing a set of processing options starts a new database backup series. A backup series is
that identify the server, communication method, identified with a number.
backup and archive options, space management
options, and scheduling options. Also called the dsm.opt database backup trigger. A set of criteria that defines
file. See also client system options file. when and how database backups are run automatically.
The criteria determine how often the backup is run,
closed registration. A registration process in which whether the backup is a full or incremental backup,
only an administrator can register workstations as and where the backup is stored.
client nodes with the server. Contrast with open
registration. database buffer pool. Storage that is used as a cache
to allow database pages to remain in memory for long
collocation. The process of keeping all data belonging periods of time, so that the server can make continuous
to a single client node or a single client file space on a updates to pages without requiring input or output
minimal number of sequential-access volumes within a (I/O) operations from external storage.
storage pool. Collocation can reduce the number of
volumes that must be accessed when a large amount of database snapshot. A complete backup of the entire
data must be restored. Tivoli Storage Manager to media that can be taken
off-site. When a database snapshot is created, the
compression. The process of saving storage space by current database backup series is not interrupted. A
eliminating empty fields or unnecessary data in a file. database snapshot cannot have incremental database
In Tivoli Storage Manager, compression can occur at a backups associated with it. See also database backup
workstation before files are backed up or archived to series. Contrast with full backup.
server storage. On some types of tape drives, hardware
compression can be used. default management class. A management class
assigned to a policy set that the server uses to manage
Glossary 823
backed-up or archived files when a user does not enterprise logging. The sending of events from Tivoli
specify a management class for a file. Storage Manager servers to a designated event server.
The event server routes the events to designated
desktop client. The group of backup-archive clients receivers, such as to a user exit. See also event.
supported by Tivoli Storage Manager that includes
clients on Windows, Apple, and Novell NetWare estimated capacity. The available space, in megabytes,
operating systems. of a storage pool.
destination. A copy group or management class event. (1) An administrative command or a client
attribute that specifies the primary storage pool to operation that is scheduled to be run using Tivoli
which a client file will be backed up, archived, or Storage Manager scheduling. (2) A message that a
migrated. Tivoli Storage Manager server or client issues.
Messages can be logged using Tivoli Storage Manager
device class. A named set of characteristics applied to event logging.
a group of storage devices. Each device class has a
unique name and represents a device type of disk, file, event record. A database record that describes actual
optical disk, or tape. status and results for events.
device configuration file. A file that contains event server. A server to which other servers can send
information about defined device classes, and, on some events for logging. The event server routes the events
Tivoli Storage Manager servers, defined libraries and to any receivers that are enabled for the sending
drives. The file can be created by using a Tivoli Storage server’s events.
Manager administrative command or by using an
option in the server options file. The information is a exclude. To identify files that you do not want to
copy of the device configuration information in the include in a specific client operation, such as backup or
Tivoli Storage Manager database. archive. You identify the files in an include-exclude list.
disaster recovery plan. A file created by Tivoli exclude-include list. See include-exclude list.
Disaster Recovery Manager (DRM) that contains
information about how to recover computer systems if expiration. The process by which files are identified
a disaster occurs and scripts that can be run to perform for deletion because their expiration date or retention
some recovery tasks. The file includes information period has passed. Backed-up or archived files are
about the software and hardware used by the Tivoli marked expired by Tivoli Storage Manager based on
Storage Manager server and the location of recovery the criteria defined in the backup or archive copy
media. group.
domain. See policy domain or client domain. expiration date. On some Tivoli Storage Manager
servers, a device class attribute used to notify tape
DRM. A short name for Tivoli Disaster Recovery management systems of the date when Tivoli Storage
Manager. Manager no longer needs a tape volume. The date is
placed in the tape label so that the tape management
dsm.opt file. See client options file and client user system does not overwrite the information on the tape
options file. volume before the expiration date.
dsmserv.opt. See server options file. export. To copy administrator definitions, client node
definitions, policy definitions, server control
dsm.sys file. See client system options file. information, or file data to external media. Used to
move or copy information between servers.
dynamic. A value for serialization that specifies that
Tivoli Storage Manager accepts the first attempt to back extend. To increase the portion of available space that
up or archive a file regardless of whether the file is can be used to store database or recovery log
modified during the backup or archive process. See information. Contrast with reduce.
also serialization. Contrast with shared dynamic, shared
static, and static.
F
E file space. A logical space in Tivoli Storage Manager
server storage that contains a group of files. For clients
enterprise configuration. A method of setting up on Windows systems, a file space is a logical partition
Tivoli Storage Manager servers so that the that is identified by a volume label. For clients on
administrator can distribute the configuration of one of UNIX systems, a file space is a logical space that
the servers to the other servers, using server-to-server contains a group of files backed up or archived from
communication. See configuration manager, managed the same file system, or part of a file system that stems
server, profile, and subscription.

from a virtual mount point. Clients can restore, retrieve, client system. Inactive backup versions are eligible for
or delete their file spaces from Tivoli Storage Manager expiration processing according to the management
server storage. Tivoli Storage Manager does not class assigned to the file. Contrast with active version.
necessarily store all the files from a single file space
together, but can identify all the files in server storage include-exclude file. On UNIX and Windows clients,
that came from a single file space. a file containing statements that Tivoli Storage Manager
uses to determine whether to include certain files in
file space ID (FSID). A unique numeric identifier that specific client operations, and to determine the
the server assigns to a file space when it is stored in associated management classes to use for backup,
server storage. archive, and space management. See include-exclude list.
frequency. A copy group attribute that specifies the include-exclude list. A group of include and exclude
minimum interval, in days, between incremental option statements that Tivoli Storage Manager uses.
backups. The exclude options identify files that are not to be
included in specific client operations such as backup or
FSID. See file space ID. space management. The include options identify files
that are exempt from the exclusion rules. The include
full backup. The process of backing up the entire options can also assign a management class to a file or
server database. A full backup begins a new database group of files for backup, archive, or space
backup series. See also database backup series and management services. The include-exclude list for a
incremental backup. Contrast with database snapshot. client may include option statements from the
include-exclude file (for UNIX clients) or the client
fuzzy copy. A backup version or archive copy of a file
options file (for other clients), and from a client option
that might not accurately reflect what the original
set on the server.
content of the file because Tivoli Storage Manager
backed up or archived the file while the file was being incremental backup. (1) The process of backing up
modified. files or directories that are new or have changed since
the last incremental backup. See also selective backup. (2)
H The process of copying only the pages in the database
that are new or changed since the last full or
hierarchical storage management (HSM) client. The incremental backup of the database. Contrast with full
Tivoli Space Manager program that runs on backup. See also database backup series.
workstations to allow users to maintain free space on
their workstations by migrating and recalling files to
and from Tivoli Storage Manager storage. Synonymous
L
with space manager client. LAN-free data transfer. The movement of client data
directly between a client and a storage device over a
high migration threshold. A percentage of the storage
SAN, rather than over the LAN.
pool capacity that identifies when the server can start
migrating files to the next available storage pool in the library. (1) A repository for demountable recorded
hierarchy. Contrast with low migration threshold. See media, such as magnetic tapes. (2) For Tivoli Storage
server migration. Manager, a collection of one or more drives, and
possibly robotic devices (depending on the library
HSM client. Hierarchical storage management client.
type), which can be used to access storage volumes. (3)
Also known as the space manager client.
In the AS/400 system, a system object that serves as a
directory to other objects. A library groups related
I objects, and allows the user to find objects by name.
image backup. A backup of a full file system or raw library client. A Tivoli Storage Manager server that
logical volume as a single object. uses server-to-server communication to access a library
that is managed by another Tivoli Storage Manager
import. The process of copying exported administrator server. See also library manager.
definitions, client node definitions, policy definitions,
server control information or file data from external library manager. A Tivoli Storage Manager server that
media to a target server. A subset of information can be controls device operations when multiple Tivoli Storage
imported to a target server from the external media. Manager servers share a storage device. The device
Used to move or copy information between servers. See operations include mount, dismount, volume
export. ownership, and library inventory. See also library client.
inactive version. A backup version of a file that is logical file. A file stored in one or more server storage
either not the most recent backup version or that is a pools, either by itself or as part of an aggregate file. See
backup version of a file that no longer exists on the also aggregate file and physical file.
Glossary 825
logical occupancy. The amount of space used by maximum extension. Specifies the maximum amount
logical files in a storage pool. This space does not of storage space, in megabytes, that you can extend the
include the unused space created when logical files are database or recovery log.
deleted from aggregate files, so it might be less than
the physical occupancy. See also physical occupancy, maximum reduction. Specifies the maximum amount
physical file, and logical file. of storage space, in megabytes, that you can reduce the
database or recovery log.
logical volume. (1) A portion of a physical volume
that contains a filesystem. (2) For the Tivoli Storage maximum utilization. The highest percentage of
Manager server, the combined space on all volumes for assigned capacity used by the database or recovery log.
either the database or the recovery log. The database is
one logical volume and the recovery log is one logical migrate. To move data from one storage location to
volume. another. See also client migration and server migration.
low migration threshold. A percentage of the storage mirroring. The process of writing the same data to
pool capacity that specifies when the server can stop multiple disks at the same time. Mirroring data protects
the migration of files to the next storage pool. Contrast against data loss within the database or recovery log.
with high migration threshold. See server migration.
mode. A copy group attribute that specifies whether
to back up a file that has not been modified since the
M last time the file was backed up. See modified and
absolute.
macro file. A file that contains one or more Tivoli
Storage Manager administrative commands, which can modified mode. A backup copy group mode that
be run only from an administrative client by using the specifies that a file is considered for incremental
MACRO command. Contrast with Tivoli Storage backup only if it has changed since the last backup. A
Manager command script. file is considered changed if the date, size, owner, or
permissions have changed. See also mode. Contrast with
managed object. A definition in the database of a absolute mode.
managed server that was distributed to the managed
server by a configuration manager. When a managed mount. To place a data medium (such as a tape
server subscribes to a profile, all objects associated with cartridge) on a drive in a position to operate.
that profile become managed objects in the database of
mount limit. A device class attribute that specifies the
the managed server. In general, a managed object
maximum number of volumes that can be
cannot be modified locally on the managed server.
simultaneously accessed from the same device class.
Objects can include policy, schedules, client options
The mount limit determines the maximum number of
sets, server scripts, administrator registrations, and
mount points. See mount point.
server and server group definitions.
mount point. A logical drive through which the server
managed server. A Tivoli Storage Manager server that
accesses volumes in a sequential access device class.
receives configuration information from a configuration
For a removable media device such as tape, a mount
manager via subscription to one or more profiles.
point is a logical drive associated with a physical drive.
Configuration information can include definitions of
For a device class with the device type of FILE, a
objects such as policy and schedules. See configuration
mount point is a logical drive associated with an I/O
manager, subscription, and profile.
stream. The number of mount points for a device class
managed system. A client or server that requests is determined by the mount limit for that class. See
services from the Tivoli Storage Manager server. mount limit.
management class. a policy object that users can bind mount retention period. A device class attribute that
to each file to specify how the server manages the file. specifies the maximum number of minutes that the
The management class can contain a backup copy server retains a mounted sequential access media
group, an archive copy group, and space management volume that is not being used before it dismounts the
attributes. The copy groups determine how the server sequential access media volume.
manages backup copies or archive copies of the file.
mount wait period. A device class attribute that
The space management attributes determine whether
specifies the maximum number of minutes that the
the file is eligible to be migrated from the space
server waits for a sequential access volume mount
manager client nodes to server storage and under what
request to be satisfied before canceling the request.
conditions the file is migrated. See also copy group, space
manager client, binding, and rebinding.

N 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 HSM client
node. (1) A workstation or file server that is registered
nodes. You can back up a primary storage pool to a
with a Tivoli Storage Manager server to receive its
copy storage pool. See destination and copy storage pool.
services. See also client node and NAS node. (2) In a
Microsoft cluster configuration, one of the computer privilege class. A level of authority granted to an
systems that make up the cluster. administrator. The privilege class determines which
administrative tasks the administrator can perform. For
node privilege class. A privilege class that allows an
example, an administrator with system privilege class
administrator to remotely access backup-archive clients
can perform any administrative task. Also called
for a specific client node or for all clients in a policy
administrative privilege class. See also system privilege
domain. See also privilege class.
class, policy privilege class, storage privilege class,
operator privilege class, and analyst privilege class. See
O also system privilege class, policy privilege class, storage
privilege class, operator privilege class, analyst privilege
open registration. A registration process in which any class, and node privilege class.
users can register their own workstations as client
nodes with the server. Contrast with closed registration. profile. A named group of configuration information
that can be distributed from a configuration manager
operator privilege class. A privilege class that allows when a managed server subscribes. Configuration
an administrator to issue commands that disable or halt information can include registered administrators,
the server, enable the server, cancel server processes, policy, client schedules, client option sets,
and manage removable media. See also privilege class. administrative schedules, Tivoli Storage Manager
command scripts, server definitions, and server group
definitions. See configuration manager and managed
P server.
page. A unit of space allocation within Tivoli Storage
Manager database volumes. R
physical file. A file stored in one or more storage randomization. The process of distributing schedule
pools, consisting of either a single logical file, or a start times for different clients within a specified
group of logical files packaged together (an aggregate percentage of the schedule’s startup window.
file). See also aggregate file and logical file.
rebinding. The process of associating a backed-up file
physical occupancy. The amount of space used by with a new management class name. For example,
physical files in a storage pool. This space includes the rebinding occurs when the management class
unused space created when logical files are deleted associated with a file is deleted. See binding.
from aggregates. See also physical file, logical file, and
logical occupancy. recall. To access files that have been migrated from
workstations to server storage by using the space
policy domain. A policy object that contains policy manager client. Contrast with migrate.
sets, management classes, and copy groups that are
used by a group of client nodes. See policy set, receiver. A server repository that contains a log of
management class, and copy group. server messages and client messages as events. For
example, a receiver can be a file exit, a user exit, or the
policy privilege class. A privilege class that allows an Tivoli Storage Manager server console and activity log.
administrator to manage policy objects, register client See also event.
nodes, and schedule client operations for client nodes.
Authority can be restricted to certain policy domains. reclamation. A process of consolidating the remaining
See also privilege class. data from many sequential access volumes onto fewer
new sequential access volumes.
policy set. A policy object that contains a group of
management classes that exist for a policy domain. reclamation threshold. The percentage of reclaimable
Several policy sets can exist within a policy domain but space that a sequential access media volume must have
only one policy set is active at one time. See before the server can reclaim the volume. Space
management class and active policy set. becomes reclaimable when files are expired or are
deleted. The percentage is set for a storage pool.
premigration. For a space manager client, the process
of copying files that are eligible for migration to server recovery log. A log of updates that are about to be
storage, while leaving the original file intact on the written to the database. The log can be used to recover
local system. from system and media failures.
Glossary 827
recovery log buffer pool. Storage that the server uses selective backup. The process of backing up selected
to hold new transaction records until they can be files or directories from a client domain. incremental
written to the recovery log. backup. See also incremental backup.
reduce. To free up space from the database or serialization. The process of handling files that are
recovery log, to allow you to delete a volume. Contrast modified during backup or archive processing. See
with extend. static, dynamic, shared static, and shared dynamic.
register. (1) To define a client node or administrator server migration. The process of moving data from
who can access the server. See registration. (2) To specify one storage pool to the next storage pool defined in the
licenses that have been purchased for the server. hierarchy, based on the migration thresholds defined
for the storage pools. See also high migration threshold
registration. The process of identifying a client node and low migration threshold.
or administrator to the server.
server options file. A file that contains settings that
restore. To copy information from its backup location control various server operations. These settings, or
to the active storage location for use. In Tivoli Storage options, affect such things as communications, devices,
Manager, you can restore the server database, storage and performance.
pools, storage pool volumes, and users’ backed-up files.
The backup version in the storage pool is not affected server-prompted scheduling mode. A client/server
by the restore operation. Contrast with backup. communication technique where the server contacts the
client when a scheduled operation needs to be done.
retention. The amount of time, in days, that inactive Contrast with client-polling scheduling mode.
backed-up or archived files are kept in the storage pool
before they are deleted. Copy group attributes and server storage. The primary and copy storage pools
default retention grace periods for the domain define used by the server to store users’ files: backup versions,
retention. archive copies, and files migrated from Tivoli Space
Manager client nodes (space-managed files). See
retention period. On an MVS server, a device class primary storage pool, copy storage pool, storage pool volume,
attribute that specifies how long files are retained on and volume.
sequential access media. When used, Tivoli Storage
Manager passes this information to the MVS operating session resource usage. The amount of wait time,
system to ensure that other tape management systems CPU time, and space used or retrieved during a client
do not overwrite tape volumes that contain retained session.
data.
shared dynamic. A value for serialization that
retrieve. To copy archived information from the specifies that a file must not be backed up or archived
storage pool to the workstation for use. The archive if it is being modified during the operation. Tivoli
version in the storage pool is not affected by the Storage Manager retries the backup or archive
retrieve operation. Contrast with archive. See also operation a number of times; if the file is being
storage pool. modified during each attempt, Tivoli Storage Manager
will back up or archive the file on its last try. See also
rollback. To remove changes that were made to serialization. Contrast with dynamic, shared static, and
database files since the last commit point. static.
shared library. A library device that is shared among

S multiple Tivoli Storage Manager servers.
schedule. A database record that describes scheduled shared static. A value for serialization that specifies
client operations or administrative commands. See that a file must not be backed up or archived if it is
administrative command schedule and client schedule. being modified during the operation. Tivoli Storage
Manager retries the backup or archive operation a
scheduling mode. The method of interaction between
number of times; if the file is being modified during
a server and a client for running scheduled operations
each attempt, Tivoli Storage Manager will not back up
on the client. Tivoli Storage Manager supports two
or archive the file. See also serialization. Contrast with
scheduling modes for client operations: client-polling
dynamic, shared dynamic, and static.
and server-prompted.
snapshot. See database snapshot.
scratch volume. A labeled volume that is either blank
or contains no valid data, that is not currently defined source server. A server that can send data, in the form
to Tivoli Storage Manager, and that is available for use. of virtual volumes, to another server. Contrast with target
server.
script. See Tivoli Storage Manager command script.

space-managed file. A file that is migrated from a subscription. The method by which a managed server
client node by the space manager client (HSM client). requests that it receive configuration information
The space manager client recalls the file to the client associated with a particular profile on a configuration
node on demand. manager. See managed server, configuration manager, and
profile.
space management. The process of keeping sufficient
free storage space available on a client node by system privilege class. A privilege class that allows an
migrating files to server storage. The files are migrated administrator to issue all server commands. See also
based on criteria defined in management classes to privilege class.
which the files are bound, and the include-exclude list.
Synonymous with hierarchical storage management. See
also migration.
T
space manager client. The Tivoli Space Manager tape library. A term used to refer to a collection of
program that enables users to maintain free space on drives and tape cartridges. The tape library may be an
their workstations by migrating and recalling files to automated device that performs tape cartridge mounts
and from server storage. Also called hierarchical storage and demounts without operator intervention.
management (HSM) client.
tape volume prefix. A device class attribute that is the
startup window. A time period during which a high-level-qualifier of the file name or the data set
schedule must be initiated. name in the standard tape label.
static. A value for serialization that specifies that a file target server. A server that can receive data sent from
must not be backed up or archived if it is being another server. Contrast with source server. See also
modified during the operation. Tivoli Storage Manager virtual volumes.
does not retry the operation. See also serialization.
Tivoli Disaster Recovery Manager (DRM). A product
Contrast with dynamic, shared dynamic, and shared static.
that works with Tivoli Storage Manager to assist in
storage agent. A program that enables Tivoli Storage preparing and later using a disaster recovery plan file
Manager to back up and restore client data directly to for the Tivoli Storage Manager server.
and from SAN-attached storage.
Tivoli Storage Manager command script. A sequence
storage hierarchy. A logical ordering of primary of Tivoli Storage Manager administrative commands
storage pools, as defined by an administrator. The that are stored in the Tivoli Storage Manager server
ordering is usually based on the speed and capacity of database. You can run the script from any interface to
the devices that the storage pools use. In Tivoli Storage the server. The script can include substitution for
Manager, the storage hierarchy is defined by command parameters and conditional logic.
identifying the next storage pool in a storage pool
definition. See storage pool. U
storage pool. A named set of storage volumes that is
UCS-2. An ISO/IEC 10646 encoding form, Universal
the destination that the Tivoli Storage Manager server
Character Set coded in 2 octets. The Tivoli Storage
uses to store client data. The client data consists of
Manager client on Windows NT and Windows 2000
backup versions, archive copies, and migrated files. You
uses the UCS-2 code page when the client is enabled
can back up a primary storage pool to a copy storage
for Unicode.
pool. See primary storage pool and copy storage pool.
Unicode Standard. A universal character encoding
storage pool volume. A volume that has been
standard that supports the interchange, processing, and
assigned to a storage pool. See volume, copy storage pool,
display of text that is written in any of the languages of
and primary storage pool.
the modern world. It can also support many classical
storage privilege class. A privilege class that allows and historical texts and is continually being expanded.
an administrator to control how storage resources for The Unicode Standard is compatible with ISO/IEC
the server are allocated and used, such as monitoring 10646. For more information, see
the database, recovery log, and server storage. http://www.unicode.org.
Authority can be restricted to certain storage pools. See
UTF-8. Unicode transformation format - 8. A
also privilege class.
byte-oriented encoding form specified by the Unicode
stub file. A file that replaces the original file on a Standard.
client node when the file is migrated from the client
node to server storage by Tivoli Space Manager.
Glossary 829
V volume. The basic unit of storage for the Tivoli
Storage Manager database, recovery log, and storage
pools. A volume can be an LVM logical volume, a
validate. To check a policy set for conditions that can
standard file system file, a tape cartridge, or an optical
cause problems if that policy set becomes the active
cartridge. Each volume is identified by a unique
policy set. For example, the validation process checks
volume identifier. See database volume, scratch volume,
whether the policy set contains a default management
and storage pool volume.
class.
volume history file. A file that contains information
version. A backup copy of a file stored in server
about: volumes used for database backups and
storage. The most recent backup copy of a file is the
database dumps; volumes used for export of
active version. Earlier copies of the same file are
administrator, node, policy, or server data; and
inactive versions. The number of versions retained by
sequential access storage pool volumes that have been
the server is determined by the copy group attributes
added, reused, or deleted. The information is a copy of
in the management class.
the same types of volume information in the Tivoli
virtual volume. An archive file on a target server that Storage Manager database.
represents a sequential media volume to a source server.

Program Number: 5698-ISE
5698-ISM
5697-ISM
Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.
GC32-0767-00
Spine information:
Version 5
Tivoli Storage Manager Messages Release 1

Tivoli Messages

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tivoli Messages

Uploaded by

Copyright:

Available Formats

Tivoli Storage Manager

First Edition (March 2002)

Part 1. Introduction . . . . . . . . . 1 Chapter 9. Tivoli Data Protection for

© Copyright IBM Corp. 1993, 2002 iii

iv Tivoli Storage Manager: Messages

Messages Not Appearing in This Publication

ANR0628I ANR7837S ANR5400E ANR7830E ANR7823S ANR7823S

© Copyright IBM Corp. 1993, 2002 v

vi Tivoli Storage Manager: Messages

ANR7831I ANR7918I ANR7937I ANR7980E ANR7998E ANR8066E ANR8124E

ANE4950 ANE4951 ANE4952 ANE4953 ANE4954 ANE4955 ANE4956

See “Internet and IBMLink Assistance” on page 7 for additional information.

Title Order Number

Tivoli Storage Manager Publications

Publication Title Order Number

viii Tivoli Storage Manager: Messages

Publication Title Order Number

Publication Title Order Number

The following table lists Tivoli Data Protection publications.

Referenced OS/390 and z/OS™ System Publications

Publication Title Order Number

Related IBM Hardware Products Publications

Title Order Number

x Tivoli Storage Manager: Messages

Title Order Number

Tivoli Storage Manager Web Site

Contacting Customer Support

You can order documentation by e-mail at swdist@tivoli.com. Please provide the

xii Tivoli Storage Manager: Messages

Technical Changes for Version 5 Release 1—March 2002

See Administrator’s Guide for more information.

© Copyright IBM Corp. 1993, 2002 xiii

xiv Tivoli Storage Manager: Messages

See Administrator’s Guide for more information.

Summary of Changes for Tivoli Storage Manager Version 5 xv

© Copyright IBM Corp. 1993, 2002 1

© Copyright IBM Corp. 1993, 2002 3

See the Tivoli Storage Manager Administrator’s Guide.

4 Tivoli Storage Manager: Messages

Explanation: The server installation procedure

System Action: Server completes installation System Action

User Response: None. User Response

How to Read a Return Code Message

Example One for QUERY EVENT Command:

6 Tivoli Storage Manager: Messages

Internet and IBMLink Assistance

Online help is available through Internet and IBMLink/ServiceLink.

A newsgroup, listserv@marist.edu, is implemented by a third party. IBM supports

Describing the Error with Keywords

The following example displays the necessary set of keywords:

© Copyright IBM Corp. 1993, 2002 7

Component Identification Keyword

8 Tivoli Storage Manager: Messages

Obtaining Online HELP (Get Help on Error Messages)

Contacting Your Service Representative

Running Trace Commands

Messages That Do Not Appear in This Publication

Chapter 2. Obtaining Help for Tivoli Storage Manager 9

© Copyright IBM Corp. 1993, 2002 11

© Copyright IBM Corp. 1993, 2002 13

ANR0132E DiagnosticID: Memory allocation failed:

ANR0130E DiagnosticID: Server LOG space

14 Tivoli Storage Manager: Messages