TSM 5 5 Messages PDF

Tivoli Storage Manager
Version 5.5
Messages
SC32-0140-01
Tivoli Storage Manager
Version 5.5
Messages
SC32-0140-01
Note!
Before using this information and the product it supports, be sure to read the general information under Notices on page
1157.
Edition Notice
This edition applies to Version 5 Release 5 of the IBM Tivoli Storage Manager and IBM Tivoli Storage Manager
Extended Edition for AIX, HP-UX, Linux, Sun Solaris, Windows, and z/OS (5608ISM, 5608ISX, 5698A11,
5698A13); IBM Tivoli Storage Manager for Space Management (5608HSM); IBM Tivoli Storage Manager for
Storage Area Networks (5608SAN); IBM Tivoli Storage Manager for Databases (5608APD); IBM Tivoli Storage
Manager for Mail (5608APE); IBM Tivoli Storage Manager for Advanced Copy Services (5608ACS); IBM Tivoli
Storage Manager for Copy Services (5608CCS); IBM Tivoli Storage Manager for Enterprise Resource Planning
(5608APR); IBM Tivoli Storage Manager for Application Servers (5608APW); IBM System Storage Archive
Manager (5608ARM); IBM Tivoli Storage Manager for Mail System for z/OS (5698A12); IBM Tivoli Storage
Manager for Data Retention for z/OS (5698A25); and to any subsequent releases until otherwise indicated in new
editions or technical newsletters.
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 click the Feedback link on
the left panel of the Tivoli Storage Manager Support site at www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html.
Copyright International Business Machines Corporation 1993, 2007. All rights reserved.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this Guide . . . . . . . . . . . v
IBM Tivoli Storage Manager Publications . . . . . v
IBM Tivoli Storage Manager Library . . . . . v
Accessing IBM Tivoli Storage Manager
Publications . . . . . . . . . . . . . vii
New, Changed, and Deleted Messages
ix
Server Messages . . . . . . . . . . . . . ix
New Server Messages . . . . . . . . . . ix
Changed Server Messages . . . . . . . . xviii
Deleted Server Messages . . . . . . . . xxxi
Client Messages with ANS Prefix . . . . . . xxxix
New Client Messages . . . . . . . . . xxxix
Changed Client Messages . . . . . . . . xli
Deleted Client Messages . . . . . . . . xlvi
Data Protection for Lotus Domino Server
Messages . . . . . . . . . . . . . . xlvii
Data Protection for Lotus Domino Server: New
Messages . . . . . . . . . . . . . xlvii
Data Protection for Lotus Domino Server:
Changed Messages . . . . . . . . . . xlix
Data Protection for Lotus Domino Server: Deleted
Messages . . . . . . . . . . . . . . . l
Data Protection for Microsoft Exchange Server
Messages . . . . . . . . . . . . . . . . l
Data Protection for Microsoft Exchange Server:
New Messages . . . . . . . . . . . . . l
Changed Messages . . . . . . . . . . . li
Deleted Messages. . . . . . . . . . . . li
Data Protection for Microsoft SQL Server Messages . li
Data Protection for Microsoft SQL Server: New
Messages . . . . . . . . . . . . . . li
Data Protection for Microsoft SQL Server:
Changed Messages . . . . . . . . . . . lii
Data Protection for Microsoft SQL Server: Deleted
Messages . . . . . . . . . . . . . . lii
Data Protection for Oracle Version 5.4.1 Messages . . lii
Data Protection for Oracle: New Messages . . . lii
Data Protection for Oracle: Changed Messages . . lii
Data Protection for Oracle: Deleted Messages . . lii
Data Protection for SAP Messages . . . . . . . lii
Data Protection for SAP (DB2 and Oracle): New
Messages . . . . . . . . . . . . . . liii
Data Protection for SAP (DB2 and Oracle):
Changed Messages . . . . . . . . . . . lvi
Data Protection for SAP (DB2 and Oracle):
Deleted Messages . . . . . . . . . . . lix
Data Protection for Snapshot Devices for mySAP for
DB2 UDB Messages Version 5.4.1 . . . . . . . lx
Data Protection for Snapshot Devices for mySAP
for DB2 UDB: New Messages . . . . . . . lx
for DB2 UDB: Changed Messages . . . . . . lx
Copyright IBM Corp. 1993, 2007

for DB2 UDB: Deleted Messages . . . . . . lx
Data Protection for Snapshot Devices for mySAP for
Oracle Messages Version 5.4.1 . . . . . . . . lx
for Oracle: New Messages . . . . . . . . lx
for Oracle: Changed Messages . . . . . . . lx
for Oracle: Deleted Messages . . . . . . . lxi
Data Protection for Disk Storage and SAN VC for
Oracle Messages. . . . . . . . . . . . . lxi
Summary of Changes for Version 5.5
lxiii
Part 1. Introduction . . . . . . . . . 1
Chapter 1. Introduction . . . . . . . . 3
Messages Not Appearing in This Publication
Understanding Messages . . . . . . .
Message Format . . . . . . . . .
.
.
.
.
.
.
. 3
. 3
. 4
Chapter 2. Obtaining Help for IBM Tivoli

Storage Manager . . . . . . . . . . . 7
Learning About Your Product . . . . . . . . .
Searching Knowledge Bases . . . . . . . . .
Searching the Information Center on your Local
System or Network . . . . . . . . . . .
Obtaining Message Explanations from the Product
Command Line Interface . . . . . . . . .
Searching the Internet . . . . . . . . . .
Obtaining Product Support . . . . . . . . .
7
8
8
8
9
9
Part 2. Server Messages . . . . . . 11

Chapter 3. Common and Platform
Specific Messages
(ANR0100ANR9999) . . . . . . . . . 13
Chapter 4. Client Events Logged to
Server (ANE40004999). . . . . . . 637
Part 3. Client Messages . . . . . . 643

Chapter 5. Client Messages
(ANS0100ANS9999) . . . . . . . . 645
Part 4. Data Protection Products

Messages . . . . . . . . . . . . 855
iii
Chapter 6. Data Protection for Lotus

Domino Server (ACD0000ACD9999) . 857
Prefix EEO .
Prefix IDS .
Chapter 7. Data Protection for

Microsoft Exchange Server
(ACN0000ACN9999) . . . . . . . . 889
Chapter 13. Data Protection for Disk

Storage and SAN VC for Oracle
Version 5.3 (EEO0000EEO9999) . . 1073

Microsoft SQL Server
(ACO0000ACO9999) . . . . . . . . 911
Appendix A. API Return Codes with

Explanations . . . . . . . . . . . 1101
Chapter 9. Data Protection for Oracle

Version 5.4.1 (ANU0000ANU9999) . . 931
Chapter 10. Shared Library Messages:
Data Protection for SAP (DB2 and
Oracle) . . . . . . . . . . . . . . 945
Prefix BKI
. 945

Snapshot Devices for mySAP for DB2
UDB Version 5.4.1
(EEP0000EEP7999) and
(IDS0000IDS2999) . . . . . . . . . 985
Messages from splitint . .
Prefix EEP . . . . .
Prefix IDS . . . . .
Messages from tdphdwdb2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 985
. 985
. 1002
. 1022

Snapshot Devices for mySAP for
Oracle Version 5.4.1
(EEO0000EEO7999) and
(IDS0000IDS1999) . . . . . . . . 1033
iv
IBM Tivoli Storage Manager: Messages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1033
. 1050
Appendix B. Allocating Additional

Server Memory . . . . . . . . . . 1143
Appendix C. I/O Error Code
Descriptions for Server Messages . . 1145
Completion Code and Operation Code Values
Completion Code Values Common to All
Device Classes. . . . . . . . . . .
Completion Code Values for Media Changers
Completion Code Values for Tape and Optical
Drives . . . . . . . . . . . . .
Operation Code Values for Tape Library
Devices . . . . . . . . . . . . .
Common Values for ASC and ASCQ Codes . .
Windows Event Log Entries . . . . . .
1146
. 1146
1147
. 1148
. 1149
. 1150
. 1153
Appendix D. Device Errors in AIX

System Error Log . . . . . . . . . 1155
Notices
Trademarks .
. . . . . . . . . . . . . 1157
.
. 1158
Glossary . . . . . . . . . . . . . 1161
About this Guide

IBM Tivoli Storage Manager is a client/server program that provides storage
management solutions to customers in a multi-vendor computer environment. IBM
Tivoli Storage Manager provides an automated, centrally scheduled,
policy-managed backup, archive, and space-management facility for file servers
and workstations.
IBM Tivoli Storage Manager Publications

This section lists publications in the IBM Tivoli Storage Manager library and
related documents. It also describes how to access Tivoli publications online and
how to order Tivoli publications.
IBM Tivoli Storage Manager Library

The following documents are available in theTivoli Storage Manager library:
Publication Title
Order Number
IBM Tivoli Storage Manager Messages
SC32-0140
IBM Tivoli Storage Manager Performance Tuning Guide
SC32-0141
IBM Tivoli Storage Manager Problem Determination Guide
SC32-0142
IBM Tivoli Storage Manager for AIX Administrators Guide
SC32-0117
IBM Tivoli Storage Manager for AIX Administrators Reference
SC32-0123
IBM Tivoli Storage Manager for AIX Installation Guide
GC23-5969
IBM Tivoli Storage Manager for HP-UX Administrators Guide
SC32-0118
IBM Tivoli Storage Manager for HP-UX Administrators Reference
SC32-0124
IBM Tivoli Storage Manager for HP-UX Installation Guide
GC23-5970
IBM Tivoli Storage Manager for Linux Administrators Guide
SC32-0119
IBM Tivoli Storage Manager for Linux Administrators Reference
SC32-0125
IBM Tivoli Storage Manager for Linux Installation Guide
GC23-5971
IBM Tivoli Storage Manager for z/OS Administrators Guide
SC32-0122
IBM Tivoli Storage Manager for z/OS Administrators Reference
SC32-0128
IBM Tivoli Storage Manager for z/OS Installation Guide
GC23-5974
IBM Tivoli Storage Manager for Sun Solaris Administrators Guide
SC32-0120
IBM Tivoli Storage Manager for Sun Solaris Administrators Reference
SC32-0126
IBM Tivoli Storage Manager for Sun Solaris Installation Guide
GC23-5972
IBM Tivoli Storage Manager for Windows Administrators Guide
SC32-0121
IBM Tivoli Storage Manager for Windows Administrators Reference
SC32-0127
IBM Tivoli Storage Manager for Windows Installation Guide
GC23-5973
IBM Tivoli Storage Manager for System Backup and Recovery Installation SC32-6543
and Users Guide
The following table lists Tivoli Storage Manager storage agent publications.
Publication Title
Order Number
IBM Tivoli Storage Manager for SAN for AIX Storage Agent Users
Guide
SC32-0129
IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent Users
Guide
SC32-0130
IBM Tivoli Storage Manager for SAN for Linux Storage Agent Users
Guide
SC32-0131
IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent
Users Guide
SC32-0132
IBM Tivoli Storage Manager for SAN for Windows Storage Agent Users
Guide
SC32-0133
The following table lists Tivoli Storage Manager client publications.

Publication Title
Order Number
IBM Tivoli Storage Manager for Space Management for UNIX and Linux: SC32-0148
Users Guide
IBM Tivoli Storage Manager for HSM for Windows Administration Guide SC32-1773
IBM Tivoli Storage Manager for Macintosh: Backup-Archive Clients
Installation and Users Guide
SC32-0143
IBM Tivoli Storage Manager for NetWare: Backup-Archive Clients

SC32-0144
IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive

Clients Installation and Users Guide
SC32-0145
IBM Tivoli Storage Manager for Windows: Backup-Archive Clients

SC32-0146
IBM Tivoli Storage Manager Using the Application Program Interface
SC32-0147
The following table lists publications for application protection products.

Publication Title
Order
Number
IBM Tivoli Storage Manager for Application Servers: Data Protection for
WebSphere Application Server Installation and Users Guide Version 5.2
SC32-9075
IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL
Server Installation and Users Guide
SC32-9059
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIX
and Linux Installation and Users Guide Version 5.4
SC32-9064
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for
Windows Installation and Users Guide Version 5.4
SC32-9065
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for SC33-6341
SAP Installation and Users Guide for DB2
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for SC33-6340
SAP Installation and Users Guide for Oracle
IBM Tivoli Storage Manager for Hardware: Data Protection for FlashCopy Devices GC32-1772
for Oracle Installation and Users Guide Version 5.3
vi
Order
Number
Publication Title
IBM Tivoli Storage Manager for Advanced Copy Services: Installation and Users
Guide for DB2 UDB Version 5.3
GC32-1780
IBM Tivoli Storage Manager for Advanced Copy Services: Data Protection for
SC33-8208
Snapshot Devices for mySAP Installation and Users Guide for DB2 UDB Version
5.4
IBM Tivoli Storage Manager for Advanced Copy Services: Data Protection for
Snapshot Devices for mySAP Installation and Users Guide for Oracle Version 5.4
SC33-8207
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for
UNIX, Linux, and OS/400 Installation and Users Guide
SC32-9056
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino for
Windows Installation and Users Guide
SC32-9057
IBM Tivoli Storage Manager for Mail: z/OS Edition Licensed Program
Specifications
GC32-0838
IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange
Server Installation and Users Guide
SC32-9058
Accessing IBM Tivoli Storage Manager Publications

To access the most recent English and translated IBM Tivoli Storage Manager
publications, visit the Tivoli Storage Manager product Web site at
http://www.ibm.com/software/tivoli/products/storage-mgr. From the left pane
select Technical Documentation. The publications are available in PDF or HTML
formats, or both.
Note: If you print PDF documents on paper that is not letter-sized, check the Fit
to page check box in the Adobe Acrobat Print dialog (select File --> Print).
This ensures that the full dimensions of a letter-sized page are printed on
the paper that you are using.
About this Guide
vii
viii

This section contains lists of the new, changed, and deleted messages for the
server, client, and Data Protection products. The changes occurred since the last
edition of this publication, January 2007.
Server Messages
This section contains lists of the new, changed, and deleted messages for the
servers. The changes occurred since the last edition of this publication, January
2007.
New Server Messages

ANR0160I
ANR0161I
ANR0470W
ANR0654I
ANR1053E
ANR1054E
ANR1055E
ANR1056E
ANR1057E
ANR1058E
ANR1348I
ANR1349E
ANR1350E
ANR1351I
ANR1352I
ANR1353I
ANR1354I
ANR1355I
ANR1356I
ANR1357I
ANR1358I
ANR1359I
ANR1371I
ANR1372I
ANR1373I
ANR1374I
ANR1375I
ANR1865I
ANR1866I
ANR1867I
ANR1868I
ix
ANR1869W
ANR1870I
ANR1871I
ANR1872I
ANR1873I
ANR1874I
ANR1875I
ANR1903E
ANR3547I
ANR4749I
ANR4817E
ANR4890I
ANR4891I
ANR4892I
ANR4893I
ANR4894I
ANR4977W
ANR4978W
ANR5000E
ANR5021E
ANR5022E
ANR5023E
ANR5024E
ANR5025E
ANR5026E
ANR5028E
ANR5030E
ANR5032E
ANR5033E
ANR5035E
ANR5036E
ANR5038E
ANR5045E
ANR5046I
ANR5048E
ANR5049E
ANR5050E
ANR5051E
ANR5208I
ANR5209I
ANR5216I
ANR5217I
ANR5220I
ANR5224E
ANR5226E
ANR5227E
ANR5228I
ANR5229W
ANR5260E
ANR5261E
ANR5262E
ANR5263E
ANR5270I
ANR5280I
ANR5289I
ANR5290I
ANR5291I
ANR5292I
ANR5293I
ANR5294I
ANR5295I
ANR5296I
ANR5297I
ANR5305E
ANR5307E
ANR5308E
ANR5317I
ANR5318I
ANR5319I
ANR5320I
ANR5321I
ANR5323I
ANR5324I
ANR5325I
ANR5326E
ANR5329I
ANR5330I
ANR5331S
ANR5333I
ANR5334W
ANR5335E
ANR5336E
ANR5337I
ANR5338E
ANR5351E
ANR5352E
ANR5354E
ANR5370E
ANR5373I
ANR5404I
xi
ANR5405I
ANR5410I
ANR5411I
ANR5412I
ANR5413E
ANR5414E
ANR5415E
ANR5416I
ANR5417I
ANR5418I
ANR5419E
ANR5420W
ANR5421E
ANR5422E
ANR5423W
ANR5424E
ANR5453E
ANR5454E
ANR5455E
ANR5456E
ANR5500E
ANR5501E
ANR5502E
ANR5503E
ANR5504E
ANR5505E
ANR5506E
ANR5507E
ANR5508E
ANR5509E
ANR5510E
ANR5511E
ANR5512E
ANR5513E
ANR5514E
ANR5515I
ANR5516E
ANR5517E
ANR5518E
ANR5519I
ANR5520I
ANR5953W
ANR5954W
ANR5959E
ANR5960E
xii
ANR5967W
ANR5984E
ANR5985E
ANR7800I
ANR7801I
ANR7804I
ANR7805E
ANR7806W
ANR7807W
ANR7808W
ANR7809I
ANR7810W
ANR7811E
ANR7811I
ANR7812E
ANR7813W
ANR7814I
ANR7814I
ANR7814I
ANR7820E
ANR7822E
ANR7823E
ANR7825E
ANR7826E
ANR7827E
ANR7832I
ANR7833S
ANR7834I
ANR7835I
ANR7836S
ANR7837S
ANR7838S
ANR7839E
ANR7841S
ANR7842S
ANR7843W
ANR7849I
ANR7850I
ANR7851S
ANR7859W
ANR7860W
ANR7861W
ANR7862W
ANR7863W
ANR7864W
xiii
ANR7865W
ANR7866W
ANR7867I
ANR8190I
ANR8191W
ANR8195I
ANR8195I
ANR8196I
ANR8196I
ANR8198E
ANR8198E
ANR8199I
ANR8199I
ANR8200I
ANR8201W
ANR8202W
ANR8203W
ANR8204W
ANR8205W
ANR8206W
ANR8207W
ANR8208W
ANR8209W
ANR8210W
ANR8211W
ANR8212W
ANR8213W
ANR8214E
ANR8215W
ANR8216W
ANR8217W
ANR8218W
ANR8219W
ANR8220W
ANR8221W
ANR8222W
ANR8223W
ANR8224W
ANR8225I
ANR8225I
ANR8226E
ANR8227E
ANR8227W
ANR8227W
ANR8230I
xiv
ANR8230I
ANR8230I
ANR8230I
ANR8230I
ANR8233E
ANR8233E
ANR8233E
ANR8233E
ANR8233E
ANR8234I
ANR8234I
ANR8234I
ANR8234I
ANR8234I
ANR8234I
ANR8237E
ANR8284E
ANR8285I
ANR8286W
ANR8287W
ANR8288W
ANR8289W
ANR8290W
ANR8291W
ANR8292W
ANR8293W
ANR8294W
ANR8295W
ANR8296W
ANR8297W
ANR8391E
ANR8392E
ANR8393E
ANR8505I
ANR8506E
ANR8507W
ANR8550E
ANR8551E
ANR8552E
ANR8554W
ANR8555E
ANR8556E
ANR8557W
ANR8558E
ANR8577E
xv
ANR8577E
ANR8578E
ANR8578E
ANR8579E
ANR8579E
ANR8580E
ANR8580E
ANR8581E
ANR8581E
ANR8582E
ANR8582E
ANR8583E
ANR8583E
ANR8584I
ANR8584I
ANR8585I
ANR8585I
ANR8586E
ANR8586E
ANR8587E
ANR8587E
ANR8588E
ANR8588E
ANR8589E
ANR8589E
ANR8590I
ANR8590I
ANR8591E
ANR8675E
ANR8677E
ANR8678E
ANR8679W
ANR8680W
ANR8681I
ANR8682E
ANR8683E
ANR8684E
ANR8685I
ANR8686I
ANR8687E
ANR8688W
ANR8689I
ANR9600E
ANR9601E
ANR9602E
xvi
ANR9603E
ANR9604E
ANR9605E
ANR9606E
ANR9607E
ANR9608E
ANR9609E
ANR9610E
ANR9611E
ANR9612E
ANR9613W
ANR9614E
ANR9615E
ANR9616I
ANR9617I
ANR9618E
ANR9622I
ANR9623I
ANR9624E
ANR9625E
ANR9626E
ANR9627E
ANR9634E
ANR9638W
ANR9676E
ANR9677E
ANR9678E
ANR9679W
ANR9680W
ANR9681W
ANR9682E
ANR9683E
ANR9684E
ANR9685E
ANR9690W
ANR9691W
ANR9900W
ANR9901W
ANR9902W
ANR9904W
ANR9905W
ANR9950W
ANR9951W
xvii
Changed Server Messages

In addition to the message number, the part of the message that has changed is
listed.
Message Number
ANE4018
ANE4042
ANE4046
ANE4973
ANE4974
ANE4989
ANR0110
ANR0114
ANR0124
ANR0125
ANR0133
ANR0134
ANR0141
ANR0193
ANR0195
ANR0197
ANR0199
ANR0262
ANR0321
ANR0364
ANR0366
ANR0379
ANR0381
ANR0390
ANR0394
ANR0395
ANR0396
ANR0399
ANR0410
ANR0421
ANR0425
ANR0450
ANR0454
ANR0463
ANR0475
ANR0476
ANR0477
ANR0478
ANR0488
ANR0493
ANR0495
ANR0496
ANR0497
ANR0499
ANR0502
ANR0512
ANR0513
ANR0514
ANR0515
ANR0533
xviii
Change
Explanation, System Action, or
Message Text and Explanation,
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
System Action, or User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
Message Number
ANR0534
ANR0535
ANR0537
ANR0538
ANR0542
ANR0548
ANR0549
ANR0552
ANR0558
ANR0564
ANR0565
ANR0591
ANR0592
ANR0593
ANR0636
ANR0655
ANR0657
ANR0658
ANR0659
ANR0660
ANR0661
ANR0663
ANR0664
ANR0666
ANR0667
ANR0668
ANR0669
ANR0670
ANR0673
ANR0674
ANR0675
ANR0686
ANR0687
ANR0688
ANR0689
ANR0690
ANR0691
ANR0692
ANR0693
ANR0694
ANR0695
ANR0696
ANR0697
ANR0698
ANR0700
ANR0701
ANR0705
ANR0706
ANR0708
ANR0709
ANR0710
ANR0711
ANR0712
ANR0713
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
xix
Message Number
ANR0714
ANR0715
ANR0716
ANR0717
ANR0718
ANR0719
ANR0720
ANR0721
ANR0722
ANR0723
ANR0724
ANR0725
ANR0726
ANR0727
ANR0728
ANR0729
ANR0730
ANR0731
ANR0732
ANR0733
ANR0740
ANR0741
ANR0742
ANR0743
ANR0744
ANR0745
ANR0746
ANR0749
ANR0750
ANR0753
ANR0754
ANR0755
ANR0756
ANR0757
ANR0759
ANR0760
ANR0762
ANR0763
ANR0766
ANR0767
ANR0768
ANR0769
ANR0770
ANR0771
ANR0772
ANR0773
ANR0774
ANR0775
ANR0776
ANR0777
ANR0780
ANR0782
ANR0783
ANR0784
xx
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Message Number
ANR0785
ANR0786
ANR0787
ANR0788
ANR0789
ANR0790
ANR0791
ANR0792
ANR0793
ANR0794
ANR0795
ANR0797
ANR0799
ANR0800
ANR0801
ANR0802
ANR0803
ANR0804
ANR0805
ANR0806
ANR0811
ANR0812
ANR0814
ANR0815
ANR0818
ANR0820
ANR0822
ANR0823
ANR0824
ANR0826
ANR0828
ANR0829
ANR0830
ANR0831
ANR0832
ANR0833
ANR0834
ANR0835
ANR0836
ANR0837
ANR0838
ANR0839
ANR0840
ANR0841
ANR0842
ANR0843
ANR0845
ANR0847
ANR0848
ANR0849
ANR0850
ANR0851
ANR0852
ANR0853
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
xxi
Message Number
ANR0854
ANR0857
ANR0858
ANR0859
ANR0860
ANR0861
ANR0862
ANR0865
ANR0866
ANR0867
ANR0868
ANR0869
ANR0870
ANR0871
ANR0872
ANR0873
ANR0874
ANR0875
ANR0876
ANR0877
ANR0878
ANR0879
ANR0880
ANR0884
ANR0885
ANR0888
ANR0894
ANR0895
ANR0897
ANR0898
ANR0899
ANR0901
ANR0902
ANR0903
ANR0904
ANR0909
ANR0910
ANR0911
ANR0912
ANR0913
ANR0914
ANR0919
ANR0924
ANR0925
ANR0936
ANR0937
ANR0939
ANR0940
ANR0942
ANR0945
ANR0946
ANR0947
ANR0948
ANR0949
xxii
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Message Number
ANR0950
ANR0951
ANR0952
ANR0953
ANR0954
ANR0955
ANR0956
ANR0957
ANR0959
ANR0969
ANR0980
ANR0981
ANR0982
ANR0983
ANR0985
ANR0986
ANR0987
ANR0988
ANR0989
ANR1000
ANR1004
ANR1013
ANR1014
ANR1034
ANR1045
ANR1066
ANR1070
ANR1071
ANR1072
ANR1073
ANR1074
ANR1076
ANR1078
ANR1079
ANR1080
ANR1081
ANR1082
ANR1083
ANR1084
ANR1085
ANR1086
ANR1087
ANR1088
ANR1089
ANR1090
ANR1091
ANR1092
ANR1093
ANR1095
ANR1096
ANR1106
ANR1107
ANR1108
ANR1109
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
xxiii
Message Number
ANR1110
ANR1112
ANR1113
ANR1114
ANR1121
ANR1122
ANR1123
ANR1124
ANR1125
ANR1126
ANR1127
ANR1128
ANR1129
ANR1130
ANR1131
ANR1132
ANR1133
ANR1135
ANR1153
ANR1157
ANR1161
ANR1163
ANR1165
ANR1167
ANR1182
ANR1183
ANR1184
ANR1229
ANR1242
ANR1256
ANR1258
ANR1284
ANR1295
ANR1309
ANR1322
ANR1324
ANR1325
ANR1328
ANR1331
ANR1343
ANR1344
ANR1366
ANR1369
ANR1402
ANR1407
ANR1418
ANR1419
ANR1425
ANR1426
ANR1427
ANR1428
ANR1437
ANR1497
ANR1498
xxiv
Change
Explanation, System Action,
Message Text
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Message Number
ANR1499
ANR1505
ANR1506
ANR1507
ANR1509
ANR1551
ANR1552
ANR1563
ANR1564
ANR1570
ANR1573
ANR1574
ANR1575
ANR1576
ANR1577
ANR1578
ANR1579
ANR1583
ANR1587
ANR1594
ANR1615
ANR1617
ANR1619
ANR1622
ANR1624
ANR1698
ANR1704
ANR1709
ANR1723
ANR1724
ANR1725
ANR1726
ANR1727
ANR1728
ANR1729
ANR1734
ANR1735
ANR1736
ANR1737
ANR1738
ANR1739
ANR1744
ANR1745
ANR1747
ANR1748
ANR1749
ANR1750
ANR1753
ANR1762
ANR1765
ANR1766
ANR1767
ANR1768
ANR1771
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
xxv
Message Number
ANR1772
ANR1774
ANR1776
ANR1784
ANR1785
ANR1786
ANR1787
ANR1788
ANR1789
ANR1790
ANR1791
ANR1792
ANR1793
ANR1794
ANR1795
ANR1797
ANR1798
ANR1799
ANR1803
ANR1851
ANR1856
ANR1859
ANR1860
ANR1861
ANR1863
ANR1864
ANR1900
ANR1994
ANR1995
ANR1996
ANR1997
ANR1998
ANR2018
ANR2090
ANR2098
ANR2111
ANR2216
ANR2218
ANR2259
ANR2289
ANR2337
ANR2338
ANR2354
ANR2365
ANR2366
ANR2367
ANR2405
ANR2412
ANR2414
ANR2416
ANR2418
ANR2420
ANR2426
ANR2427
xxvi
Change
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
Message Number
ANR2428
ANR2505
ANR2506
ANR2507
ANR2535
ANR2541
ANR2542
ANR2544
ANR2545
ANR2546
ANR2548
ANR2554
ANR2558
ANR2559
ANR2568
ANR2569
ANR2570
ANR2571
ANR2579
ANR2581
ANR2582
ANR2586
ANR2588
ANR2597
ANR2598
ANR2661
ANR2662
ANR2663
ANR2664
ANR2665
ANR2666
ANR2670
ANR2717
ANR2758
ANR2765
ANR2770
ANR2772
ANR2773
ANR2774
ANR2775
ANR2777
ANR2779
ANR2797
ANR2816
ANR2958
ANR2996
ANR2998
ANR4132
ANR4133
ANR4498
ANR4732
ANR4924
ANR4972
ANR6947
Change
Explanation, System Action, or User Response
Message Type and Explanation, System Action, or User Response
Message Text and Explanation, System Action, or User Response
xxvii
Message Number
ANR7804
ANR7805
ANR7807
(HP-UX)
ANR7807
(Linux)
ANR7807 (Solaris)
ANR7810
Change

Message Type and Message Text and Explanation, System Action, or
User Response
ANR7813
ANR7820
ANR7823
ANR7831 (Solaris) Explanation, System Action, or User Response
ANR7859
ANR7859
(HP-UX)
ANR7859 (Linux) Explanation, System Action, or User Response
ANR7864
(HP-UX)
ANR7867
ANR7867
(HP-UX)
ANR8200
(HP-UX)
ANR8200 (Linux) Message Text and Explanation, System Action, or User Response
ANR8200 (Solaris) Message Text and Explanation, System Action, or User Response
ANR8200
(Windows)
ANR8201
ANR8202
Message Text
(Windows)
ANR8204
ANR8206
(Windows)
ANR8207
ANR8207
Message Text
(Windows)
ANR8210
(HP-UX)
ANR8211
ANR8212
(HP-UX)
ANR8213 (Linux) Message Text
ANR8213 (Solaris) Message Text
ANR8218
(HP-UX)
ANR8219
xxviii
Message Number
ANR8219 (Linux)
ANR8220
(Windows)
ANR8221
(HP-UX)
ANR8221 (Linux)
ANR8221 (Solaris)
ANR8224 (Linux)
ANR8224 (Solaris)
ANR8225 (Solaris)
ANR8226 (Linux)
ANR8284 (Solaris)
ANR8286
ANR8286
(HP-UX)
ANR8286 (Linux)
ANR8286 (Solaris)
ANR8288
ANR8289
ANR8323
ANR8366
ANR8374
ANR8383
ANR8387
ANR8388
ANR8389
ANR8416
ANR8447
ANR8471
ANR8478
ANR8480
ANR8481
ANR8500
ANR8501
ANR8502
ANR8503
ANR8504
ANR8557
ANR8572
(Windows)
ANR8575 (Linux)
ANR8677
ANR8678
ANR8679
ANR8682
(HP-UX)
ANR8682 (Linux)
ANR8682 (Solaris)
ANR8685
ANR8687
ANR8768
ANR8780
ANR8781
ANR8783
Change
Message Text
User Response
User Response
User Response
User Response
User Response
User Response

User Response
User Response
System Action,
System Action,
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
System Action,
User Response
User Response
User Response
User Response
User Response
System Action,
or User Response
or User Response
or User Response
or User Response

User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
xxix
Message Number
ANR8801
ANR8804
ANR8805
ANR8806
ANR8807
ANR8813
ANR8816
ANR8823
ANR8825
ANR8827
ANR8834
ANR8838
ANR8840
ANR8845
ANR8847
ANR8854
ANR8855
ANR8856
ANR8874
ANR8876
ANR8882
ANR8883
ANR8940
ANR8941
ANR8948
ANR8951
ANR8954
ANR8957
ANR8958
ANR8963
ANR8966
ANR8968
ANR8973
ANR8974
ANR8975
ANR8977
ANR8978
ANR8984
ANR8985
ANR8987
ANR9579
(HP-UX)
ANR9579 (Solaris)
ANR9581
(HP-UX)
ANR9581 (Linux)
ANR9581 (Solaris)
ANR9602 (Solaris)
ANR9613 (Linux)
ANR9618
ANR9622
ANR9623
ANR9624
ANR9625
(HP-UX)
xxx
Change
Message Text
Message Text
Message Text
System Action,
System Action,
System Action,
User Response
System Action,
User Response
or User Response
or User Response
or User Response
or User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response

User Response
User Response
User Response
User Response
User Response
User Response
User Response
Message Number
ANR9625 (Solaris)
ANR9636
(HP-UX)
ANR9636 (Linux)
ANR9636 (Solaris)
ANR9639
(HP-UX)
ANR9676
ANR9677
(HP-UX)
ANR9677 (Linux)
ANR9678
(HP-UX)
ANR9678 (Linux)
ANR9680
ANR9681
ANR9682
ANR9683
ANR9684
ANR9685
ANR9759
ANR9761
ANR9771
ANR9773
ANR9901
(HP-UX)
ANR9901
ANR9901
ANR9902
(HP-UX)
ANR9902
ANR9902
ANR9904
ANR9904
(HP-UX)
ANR9905
ANR9999
Change
Message Text
User Response
(Linux) Explanation, System Action, or User Response

(Solaris) Explanation, System Action, or User Response
(Linux) Explanation, System Action,
(Solaris) Explanation, System Action,
or
or
or
or
User
User
User
User
Response
Response
Response
Response

Deleted Server Messages

ANR5000E
ANR5010E
ANR5011E
ANR5012E
ANR5013E
ANR5014E
ANR5015E
ANR5016E
ANR5017E
ANR5018E
ANR5019E
xxxi
ANR5020E
ANR5021E
ANR5022E
ANR5023E
ANR5024E
ANR5025E
ANR5026E
ANR5027E
ANR5028E
ANR5030E
ANR5032E
ANR5033E
ANR5034E
ANR5035E
ANR5036E
ANR5037E
ANR5038E
ANR5039E
ANR5040E
ANR5041E
ANR5042E
ANR5043E
ANR5044E
ANR5045E
ANR5046I
ANR5048E
ANR5049E
ANR5050E
ANR5051E
ANR5060E
ANR5061E
ANR5062E
ANR5063E
ANR5064E
ANR5065E
ANR5066E
ANR5067E
ANR5068E
ANR5069E
ANR5070I
ANR5071W
ANR5080I
ANR5081E
ANR5082W
ANR5083E
xxxii
ANR5084W
ANR5085I
ANR5086I
ANR5087I
ANR5088E
ANR5089I
ANR5090I
ANR5091E
ANR5092E
ANR5093E
ANR5094W
ANR5095W
ANR5096W
ANR5097I
ANR5098I
ANR5099E
ANR5100E
ANR5101W
ANR5102W
ANR5103I
ANR5104E
ANR5105I
ANR5106E
ANR5107E
ANR5108E
ANR5109E
ANR5110I
ANR5111E
ANR5112W
ANR5113W
ANR5114W
ANR5115W
ANR5116I
ANR5117I
ANR5118I
ANR5120I
ANR5121I
ANR5122I
ANR5123I
ANR5124E
ANR5125E
ANR5126W
ANR5127W
ANR5128E
ANR5129W
xxxiii
ANR5130W
ANR5131I
ANR5132W
ANR5133W
ANR5140I
ANR5142I
ANR5143I
ANR5148I
ANR5200S
ANR5201S
ANR5202E
ANR5203E
ANR5204I
ANR5205I
ANR5208I
ANR5209I
ANR5210I
ANR5211I
ANR5212I
ANR5213I
ANR5214I
ANR5215I
ANR5216I
ANR5217I
ANR5218I
ANR5220I
ANR5221I
ANR5222I
ANR5223E
ANR5224E
ANR5225E
ANR5226E
ANR5227E
ANR5228I
ANR5229W
ANR5230I
ANR5231I
ANR5232W
ANR5233E
ANR5234E
ANR5240E
ANR5241E
ANR5250E
ANR5251E
ANR5252E
xxxiv
ANR5253E
ANR5254E
ANR5255E
ANR5256E
ANR5257I
ANR5258E
ANR5259E
ANR5260E
ANR5261E
ANR5262E
ANR5263E
ANR5264I
ANR5265I
ANR5266I
ANR5267I
ANR5268I
ANR5269I
ANR5270I
ANR5280I
ANR5281I
ANR5282I
ANR5283I
ANR5284I
ANR5285I
ANR5286I
ANR5287I
ANR5288I
ANR5289I
ANR5290I
ANR5291I
ANR5292I
ANR5293I
ANR5294I
ANR5295I
ANR5296I
ANR5297I
ANR5300I
ANR5301I
ANR5302I
ANR5303I
ANR5304I
ANR5305E
ANR5306E
ANR5307E
ANR5308E
xxxv
ANR5309E
ANR5310E
ANR5311E
ANR5312E
ANR5313I
ANR5314E
ANR5315E
ANR5316E
ANR5317I
ANR5318I
ANR5319I
ANR5320I
ANR5321I
ANR5322I
ANR5323I
ANR5324I
ANR5325I
ANR5326E
ANR5327I
ANR5328I
ANR5329I
ANR5330I
ANR5331S
ANR5332I
ANR5333I
ANR5334W
ANR5335E
ANR5336E
ANR5337I
ANR5338E
ANR5350E
ANR5351E
ANR5352E
ANR5353E
ANR5354E
ANR5355E
ANR5356E
ANR5357E
ANR5358E
ANR5359E
ANR5360E
ANR5361E
ANR5362E
ANR5363E
ANR5364E
xxxvi
ANR5365E
ANR5366E
ANR5367I
ANR5368E
ANR5369I
ANR5370E
ANR5371E
ANR5372I
ANR5373I
ANR5374I
ANR5404I
ANR5405I
ANR5410I
ANR5411I
ANR5412I
ANR5413E
ANR5414E
ANR5415W
ANR5416E
ANR5417E
ANR5418E
ANR5419E
ANR5420W
ANR5450E
ANR5451E
ANR5452E
ANR5453E
ANR5454E
ANR5455E
ANR5456E
ANR5499E
ANR5500E
ANR5501E
ANR5502E
ANR5503E
ANR5504E
ANR5505E
ANR5506E
ANR5507E
ANR5508E
ANR5509E
ANR5510E
ANR5511E
ANR5512E
ANR5513E
xxxvii
ANR5514E
ANR5515I
ANR5516E
ANR5517E
ANR5518E
ANR5519I
ANR5520I
ANR5953W
ANR5954W
ANR5956E
ANR5957W
ANR5958E
ANR5959E
ANR5960E
ANR5961E
ANR5962I
ANR5963I
ANR5964E
ANR5965I
ANR5967W
ANR5980E
ANR5981I
ANR5982E
ANR5983I
ANR5984E
ANR5985E
ANR8675E
ANR8676E
ANR8677E
ANR8678E
ANR8679E
ANR8681I
ANR8682E
ANR8683E
ANR8684E
ANR9680W
ANR9681W
ANR9682E
ANR9683W
ANR9684E
ANR9685E
ANR9690W
ANR9691W
ANR9950W
ANR9951W
xxxviii
ANR9952E
ANR9953E
ANR9954S
Client Messages with ANS Prefix

This section contains lists of the new, changed, and deleted ANS messages for the
clients. The changes occurred since the last edition of this publication, January
2007.
New Client Messages

ANS1559I
ANS1561I
ANS1564I
ANS1579E
ANS1592E
ANS1593E
ANS1594E
ANS1595E
ANS1596E
ANS1599E
ANS1650I
ANS1651I
ANS1652I
ANS1653I
ANS1654E
ANS1655I
ANS1656I
ANS1657I
ANS1658I
ANS1659I
ANS1660I
ANS1661I
ANS1662I
ANS1753E
ANS1754E
ANS1763W
ANS1764W
ANS1765W
ANS1766W
ANS1767E
ANS1768E
ANS1770E
ANS2046S
ANS2213E
ANS2219E
xxxix
ANS2220E
ANS2221W
ANS2223W
ANS2225W
ANS2627W
ANS2628W
ANS2742I
ANS3013E
ANS4051E
ANS4052E
ANS4053E
ANS4997E
ANS5219W
ANS7500W
ANS7501E
ANS7502E
ANS7534W
ANS7535W
ANS7543E
ANS8104W
ANS8946E
ANS9020E
ANS9025E
ANS9029E
ANS9034E
ANS9054E
ANS9062E
ANS9065E
ANS9089E
ANS9091E
ANS9092W
ANS9100E
ANS9121I
ANS9156I
ANS9157W
ANS9161E
ANS9166I
ANS9167W
ANS9172I
ANS9173I
ANS9174I
ANS9175E
ANS9176I
ANS9177T
ANS9179W
xl
ANS9180W
ANS9181I
ANS9182W
ANS9183W
ANS9185W
ANS9187W
ANS9206W
ANS9220W
ANS9227E
ANS9231E
ANS9233E
ANS9236E
ANS9252I
ANS9263W
ANS9264E
ANS9265E
ANS9266E
ANS9278E
ANS9279E
ANS9280E
ANS9287E
ANS9296W
ANS9316T
ANS9472I
ANS9476I
ANS9857W
Changed Client Messages

In addition to the message number, the part of the message that has changed is
listed.
Message
Number
ANS0254
ANS1004
ANS1030
ANS1036
ANS1065
ANS1067
ANS1070
ANS1090
ANS1097
ANS1101
ANS1110
ANS1111
ANS1116
ANS1156
ANS1183
ANS1219
Change
Message Text
Message Text
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
xli
Message
Number
ANS1238
ANS1266
ANS1271
ANS1273
ANS1305
ANS1328
ANS1347
ANS1349
ANS1353
ANS1357
ANS1358
ANS1373
ANS1374
ANS1377
ANS1408
ANS1417
ANS1422
ANS1449
ANS1452
ANS1455
ANS1458
ANS1460
ANS1461
ANS1463
ANS1469
ANS1476
ANS1499
ANS1505
ANS1510
ANS1515
ANS1522
ANS1532
ANS1566
ANS1567
ANS1568
ANS1570
ANS1574
ANS1575
ANS1577
ANS1580
ANS1610
ANS1612
ANS1618
ANS1622
ANS1798
ANS1823
ANS1871
ANS1872
ANS1873
ANS1878
ANS1880
ANS1891
xlii
Change
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Type and Message Text and Explanation, System Action, or User
Response
Response
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message
Number
ANS1892
ANS1902
ANS1903
ANS1909
ANS1943
ANS1945
ANS1964
ANS1971
ANS1981
ANS1987
ANS1989
ANS2025
ANS2036
ANS2048
ANS2056
ANS2057
ANS2070
ANS2071
ANS2073
ANS2095
ANS2204
ANS2604
ANS2605
ANS2615
ANS2622
ANS2702
ANS2707
ANS2718
ANS2719
ANS2720
ANS2730
ANS2734
ANS2748
ANS2796
ANS2804
ANS3005
ANS3009
ANS3010
ANS3012
ANS3408
ANS3411
ANS3415
ANS4020
ANS4025
ANS4039
ANS4047
ANS4054
ANS4900
ANS4973
ANS4974
ANS4987
ANS4989
ANS4999
Change
Message Text
Message Text
Message Text
Message Text
Message Text
Response
xliii
Message
Number
ANS5003
ANS5153
ANS5186
ANS5190
ANS5253
ANS5256
ANS5257
ANS5258
ANS5261
ANS5262
ANS5265
ANS5267
ANS7650
ANS8055
ANS8061
ANS8820
ANS8822
ANS8823
ANS8824
ANS8825
ANS8826
ANS8827
ANS8828
ANS8829
ANS8831
ANS8832
ANS8833
ANS8834
ANS8835
ANS8836
ANS8837
ANS8838
ANS8839
ANS8844
ANS8846
ANS8848
ANS8849
ANS8850
ANS8851
ANS8852
ANS8854
ANS8856
ANS8858
ANS8859
ANS9032
ANS9064
ANS9078
ANS9126
ANS9128
ANS9146
ANS9150
ANS9164
ANS9230
xliv
Change
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Response
Message
Number
ANS9257
ANS9401
ANS9402
ANS9404
ANS9405
ANS9423
ANS9425
ANS9433
ANS9449
ANS9450
ANS9451
ANS9452
ANS9454
ANS9459
ANS9469
ANS9474
ANS9501
ANS9502
ANS9519
ANS9520
ANS9521
ANS9522
ANS9523
ANS9524
ANS9526
ANS9527
ANS9528
ANS9529
ANS9530
ANS9532
ANS9533
ANS9535
ANS9542
ANS9554
ANS9576
ANS9577
ANS9578
ANS9613
ANS9732
ANS9736
ANS9738
ANS9740
ANS9782
ANS9807
ANS9821
ANS9840
ANS9842
ANS9849
ANS9850
Change
Message Text
Message Text
User Response
User Response
User Response
User Response
User
User
User
User
Response
Response
Response
Response

User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
xlv
Deleted Client Messages

ANS0888W
ANS1150E
ANS1209E
ANS1252E
ANS1343E
ANS1448I
ANS1465I
ANS1467I
ANS1488I
ANS1490W
ANS1588E
ANS1620I
ANS3029W
ANS3041I
ANS3042I
ANS3052I
ANS3053E
ANS3054I
ANS4039E
ANS4500E
ANS4501E
ANS4502E
ANS4503E
ANS4504E
ANS4505E
ANS4506E
ANS4507E
ANS5127W
ANS5558E
ANS5879W
ANS6211W
ANS6317I
ANS8772W
ANS8774W
ANS8980W
ANS8991W
ANS9011W
ANS9036W
ANS9046E
ANS9108E
ANS9109E
ANS9110E
ANS9111E
ANS9115E
xlvi
ANS9302E
ANS9303E
ANS9304E
ANS9305E
ANS9306E
ANS9307W
ANS9308E
ANS9309I
ANS9310E
ANS9311E
Data Protection for Lotus Domino Server Messages

This section contains lists of the new, changed, and deleted messages for Data
Protection for Lotus Domino Server. The changes occurred since the last edition
of this publication, January 2007.
Data Protection for Lotus Domino Server: New Messages

ACD487E
ACD488E
ACD495E
ACD496I
ACD497I
ACD498I
ACD501E
ACD515E
ACD516I
ACD517I
ACD518E
ACD519E
ACD520E
ACD521E
ACD522E
ACD524S
ACD5125E
ACD5132E
ACD5134E
ACD5135E
ACD5136E
ACD5137E
ACD5138E
ACD5139E
ACD5140E
ACD5141E
ACD5142E
ACD5143E
xlvii
ACD5144E
ACD5145E
ACD5146E
ACD5147E
ACD5148E
ACD5149E
ACD5150E
ACD5214I
ACD5241E
ACD5246I
ACD5432I
ACD5437I
ACD5450E
ACD5713E
ACD5714E
ACD5715E
ACD5716E
ACD5717E
ACD5718E
ACD5719E
ACD5720E
ACD5721E
ACD5836I
ACD5837I
ACD5838I
ACD5839T
ACD5840T
ACD5841E
ACD5842E
ACD5843I
ACD5844T
ACD5845T
ACD5846T
ACD5847T
ACD5848T
ACD5849T
ACD5850E
ACD5851T
ACD6023I
ACD6024E
ACD6025T
ACD6026T
ACD6027T
ACD6028T
ACD6029T
xlviii
ACD6030T
ACD6031T
ACD6032T
ACD6039T
ACD6041T
ACD6042E
ACD6043E
ACD6044E
ACD7000I
ACD7001I
ACD7002I
ACD7003I
ACD7004I
ACD7005I
ACD7006I
ACD7007I
ACD7020I
ACD7021I
ACD7022I
ACD7023I
ACD7024I
ACD7025I
ACD7026I
ACD7027I
ACD7028I
ACD7029I
ACD7030I
ACD7031I
ACD7032I
ACD7033I
ACD7034I
Data Protection for Lotus Domino Server: Changed Messages

Message
Number
ACD0150
ACD0154
ACD0155
ACD0156
ACD0213
ACD476
ACD5110
ACD5129
ACD5130
ACD5200
ACD5201
ACD5202
Change
Message Text
Message Text
Message Text
User Response
User Response
User Response
User Response
User Response
User Response
User Response
xlix
Message
Number
ACD5203
ACD5204
ACD5205
ACD5206
ACD5207
ACD5208
ACD5209
ACD5210
ACD5212
ACD5213
ACD5218
ACD5226
ACD5228
ACD5229
ACD5230
ACD5231
ACD5232
ACD5233
ACD5234
ACD5235
ACD5236
ACD5237
ACD5238
ACD5239
ACD5240
ACD5242
ACD5774
ACD5996
ACD6014
Change
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Response
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Data Protection for Lotus Domino Server: Deleted Messages

There are no deleted messages.
Data Protection for Microsoft Exchange Server Messages

Protection for Microsoft Exchange Server. The changes occurred since the last
edition of this publication, January 2007.
Data Protection for Microsoft Exchange Server: New

Messages
ACN524S
ACN5802I
ACN5803I
ACN5821I
ACN5824I
ACN5825E
ACN5829E
ACN5836T
ACN5837E
ACN5839E
ACN5840W
ACN5841W
ACN5843I
Data Protection for Microsoft Exchange Server: Changed

Messages
Message
Number
ACN476
ACN496
ACN497
ACN501
ACN517
ACN5051
ACN5067
Change
Message Text
Message Text
Message Type
Message Type
Message Text
Data Protection for Microsoft Exchange Server: Deleted

Messages
Data Protection for Microsoft SQL Server Messages

Protection for Microsoft SQL Server. The changes occurred since the last edition of
this publication, January 2007.
Data Protection for Microsoft SQL Server: New Messages

ACO521E
ACO522E
ACO524S
ACO5097I
ACO5098E
ACO5124E
ACO5125E
ACO5126E
ACO5127E
ACO5128E
ACO5129E
ACO5170E
ACO5171E
ACO5177E
ACO5186E
ACO5187E
ACO5188E
ACO5204E
li
ACO5459W
ACO5460E
ACO5616T
ACO5617I
ACO5629E
ACO5630E
ACO5631E
ACO5633E
ACO5634E
Data Protection for Microsoft SQL Server: Changed Messages

Message
Number
ACO476
ACO496
ACO497
ACO501
ACO517
ACO5452
Change
Message Text
Message Text
Message Type
Data Protection for Microsoft SQL Server: Deleted Messages

Data Protection for Oracle Version 5.4.1 Messages

This component was last documented January 2007 at Version 5.4.0. Since that
time, the component was updated to Version 5.4.1. Changes occurred as identified
in the sections below.
Data Protection for Oracle: New Messages

ANU524S
ANU2622E
ANU2623I
Data Protection for Oracle: Changed Messages

Message
Number
ANU501
ANU2621
Change
Message Type
Data Protection for Oracle: Deleted Messages

Data Protection for SAP Messages

Protection for SAP. The changes occurred since the last edition of this publication,
January 2007.
lii
Data Protection for SAP (DB2 and Oracle): New Messages

For Version 5.5, the messages for Data Protection for SAP for DB2 and Data
Protection for SAP for Oracle are documented as a single, common library of
messages. In previous versions, the messages for each component (DB2 and Oracle)
were documented separately. The messages below did not exist in previous
versions, neither as Data Protection for SAP for DB2 messages nor as Data
Protection for SAP for Oracle messages.
BKI1230E
BKI1505E
BKI1506E
BKI1507E
BKI1508E
BKI1509E
BKI1510I
BKI1511I
BKI1512E
BKI1513I
BKI1514I
BKI1515I
BKI1517I
BKI1518E
BKI1519E
BKI1520E
BKI1521I
BKI1522E
BKI1523W
BKI1525E
BKI1526E
BKI1529E
BKI1530E
BKI1534E
BKI1535E
BKI1536E
BKI1537E
BKI1538E
BKI1539E
BKI1540E
BKI1541E
BKI1542E
BKI1543E
BKI1544E
BKI1545E
BKI1546E
BKI1547E
BKI1548E
BKI1549E
liii
BKI1550E
BKI1553I
BKI1554W
BKI1555I
BKI1556E
BKI1557I
BKI6901I
BKI6902I
BKI6903I
BKI6904I
BKI6905I
BKI6906I
BKI6907I
BKI6908I
BKI6909I
BKI6910E
BKI6911E
BKI6912E
BKI6913E
BKI6914E
BKI6915E
BKI6917E
BKI6918E
BKI6919E
BKI6920E
BKI6921E
BKI6922E
BKI6923I
BKI6924E
BKI6925E
BKI6926I
BKI6927E
BKI6928E
BKI6929E
BKI6930E
BKI6931E
BKI6932E
BKI6933I
BKI6934I
BKI6935I
BKI6936E
BKI6937I
BKI6938E
BKI6939I
BKI6940I
liv
BKI6941I
BKI6942E
BKI6943I
BKI6944I
BKI6945I
BKI6946E
BKI6947E
BKI6950W
BKI6951E
BKI6952E
BKI6953E
BKI6954E
BKI6955E
BKI6956E
BKI6957E
BKI6958I
BKI6959I
BKI6960E
BKI6961E
BKI7048I
BKI8300I
BKI8301E
BKI8302E
BKI8305E
BKI8306E
BKI8307E
BKI8308E
BKI8309E
BKI8310E
BKI8311E
BKI8312E
BKI8313E
BKI8314E
BKI8315E
BKI8316E
BKI8317W
BKI8318E
BKI8319W
BKI8320I
BKI8321I
BKI8322E
BKI8323E
BKI8324E
BKI8325E
BKI8326E
lv
BKI8327E
BKI8328E
BKI8330E
BKI8331E
BKI8332E
BKI8333E
BKI8334E
BKI8335E
BKI8336E
BKI8337E
BKI8338E
BKI8339E
BKI8340E
BKI8341E
BKI8343W
BKI8344E
BKI8345E
BKI8349I
BKI9309E
BKI9310E
BKI9311E
BKI9312E
BKI9313E
BKI9314E
BKI9315E
BKI9316E
Data Protection for SAP (DB2 and Oracle): Changed Messages

For Version 5.5, the messages for Data Protection for SAP for DB2 and Data
Protection for SAP for Oracle are documented as a single, common library of
messages. In previous versions, the messages for each component (DB2 and Oracle)
were documented separately. The messages below existed in previous product
versions, and were documented either as Data Protection for SAP for DB2
messages or as Data Protection for SAP for Oracle messages. The messages have
changed as indicated below.
Message
Number
BKI0000
BKI0004
BKI0005
BKI0006
BKI0020
BKI0023
BKI0024
BKI0027
BKI0049
BKI0053
BKI0054
lvi
Change
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
Explanation,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
System Action,
or
or
or
or
or
or
or
or
or
or
or
User
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
Message
Number
BKI0060
BKI0062
BKI0063
BKI0064
BKI0065
BKI0101
BKI0102
BKI0311
BKI0400
BKI0405
BKI0410
BKI0411
BKI0412
BKI0413
BKI0414
BKI0450
BKI0452
BKI0453
BKI0459
BKI1000
BKI1001
BKI1003
BKI1004
BKI1005
BKI1009
BKI1010
BKI1012
BKI1013
BKI1019
BKI1021
BKI1022
BKI1023
BKI1200
BKI1201
BKI1202
BKI1203
BKI1205
BKI1207
BKI1208
BKI1209
BKI1210
BKI1211
BKI1222
BKI1223
BKI1228
BKI1229
BKI2000
BKI2001
BKI2007
BKI2008
BKI2010
BKI2011
BKI2017
Change
Message Text
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
lvii
Message
Number
BKI2024
BKI2025
BKI2026
BKI2027
BKI2029
BKI2031
BKI2033
BKI4005
BKI4008
BKI5000
BKI5001
BKI5015
BKI5017
BKI5018
BKI7049
BKI7051
BKI7053
BKI7055
BKI7056
BKI7057
BKI7058
BKI7059
BKI7060
BKI7303
BKI7305
BKI7307
BKI7308
BKI7309
BKI7310
BKI7311
BKI7312
BKI7313
BKI7314
BKI7315
BKI7318
BKI7321
BKI7322
BKI7323
BKI8525
BKI8526
BKI8540
BKI8555
BKI8557
BKI8558
BKI8559
BKI8561
BKI8587
BKI8588
BKI8589
BKI8618
BKI8643
BKI8651
BKI8652
lviii
Change
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text
Message Text

User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
System Action,
User Response
User Response
User Response
User Response
System Action,
System Action,
System Action,
System Action,
System Action,
or User Response
or
or
or
or
or
User
User
User
User
User
Response
Response
Response
Response
Response
User Response
System Action,
System Action,
System Action,
User Response
User Response
System Action,
System Action,
User Response
or User Response
or User Response
or User Response
or User Response
or User Response

User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
Message
Number
BKI8667
BKI8700
BKI8701
BKI8703
BKI8738
BKI8743
BKI8744
BKI8773
BKI8800
BKI8801
BKI8802
BKI8803
BKI8804
BKI8806
BKI8807
BKI8808
BKI8810
BKI9001
BKI9003
BKI9005
BKI9006
BKI9008
BKI9009
BKI9200
BKI9201
BKI9202
BKI9203
BKI9204
BKI9205
BKI9206
BKI9207
BKI9208
BKI9209
BKI9210
BKI9211
BKI9212
BKI9213
BKI9214
BKI9216
BKI9217
BKI9218
BKI9219
BKI9220
BKI9301
BKI9302
BKI9306
BKI9307
BKI9308
Change
Message Text
Message Text
User
User
User
User
User
User
User
User
User
User
Response
Response
Response
Response
Response
Response
Response
Response
Response
Response
User Response
System Action,
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
System Action,
User Response
User Response
System Action,
User Response
User Response
User Response
System Action,
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
User Response
or User Response
or User Response
or User Response
or User Response
Data Protection for SAP (DB2 and Oracle): Deleted Messages

lix
Data Protection for Snapshot Devices for mySAP for DB2 UDB
Messages Version 5.4.1
Data Protection for Snapshot Devices for mySAP for DB2

UDB: New Messages
IDS1436E
IDS1437E
IDS1438W
IDS1439W
IDS1440E
IDS1441I
IDS1443E

UDB: Changed Messages
There are no changed messages.

UDB: Deleted Messages
Data Protection for Snapshot Devices for mySAP for Oracle Messages
Version 5.4.1
Data Protection for Snapshot Devices for mySAP for Oracle:

New Messages
IDS1436E
IDS1437E
IDS1438W
IDS1439W
IDS1440E
IDS1441I
IDS1443E

Changed Messages
There are no changed messages.
lx

Deleted Messages
Data Protection for Disk Storage and SAN VC for Oracle Messages
This component has not changed since previously documented.
lxi
lxii
Summary of Changes for Version 5.5

For a high-level summary of changes for Tivoli Storage Manager Version 5.5, see
the product announcement letters. The announcement letter Web site is
http://msdomino2.whiteplains.ibm.com/t_dir/Tivoli%20Web.nsf/tivoli?OpenPage.
For a summary of changes that apply to a specific product or server platform or
client platform, see the user's guide for that product, server platform, or client
platform. In addition to a summary of changes, the user's guide contains more
detailed information about the changes. The users guides can be accessed from the
product information center, as described in Searching the Information Center on
your Local System or Network on page 8
lxiii
lxiv
Part 1. Introduction
Chapter 1. Introduction
IBM Tivoli Storage Manager is an enterprise-wide storage management application
for the network. It provides automated storage management services to
multi-vendor workstations, personal computers, and local area network (LAN) file
servers. Tivoli Storage Manager includes the following components:
v Server
v Administrative client
v Backup-archive client
v Space Manager (Hierarchical storage management (HSM) client)
v Application programming interface (API)
v Data Protection products (application products)
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, backup-archive client, API, HSM, and Data Protection products.
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.
Tivoli Storage Manager provides an activity log to help the administrator track
server activity and monitor the system. The activity log contains messages
generated by the server, and is stored in the database. The server automatically
deletes messages from the activity log after they have passed the specified
retention period. Any messages sent to the server console are stored in the activity
log. Examples of the types of messages stored in the activity log include:
v When client sessions start or end
v When migration starts or ends
v When backed up files are expired from server storage
v Any output generated from background processes
See the IBM Tivoli Storage Manager Administrators Guide.
Messages Not Appearing in This Publication

Message numbers in the range ANR01000120, 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.
Understanding Messages
The following examples illustrate the format used in this publication to describe
Tivoli Storage Manager messages:
v Messages that begin with prefix ANE and are in range 40004999 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 can 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 components:
Administrative clients
Application program interface clients

Backuparchive clients
Space Manager (HSM) clients
Microsoft Exchange VSS and Hardware Devices Snapshot Integration
Modules
DB2 UDB and Hardware Devices Snapshot Integration Modules
v Messages that begin with prefix ACD are from Data Protection for Lotus
Domino Server.
v Messages that begin with prefix ACN are from Data Protection for Microsoft
Exchange Server.
v Messages that begin with prefix ACO are from Data Protection for Microsoft
SQL Server.
v Messages that begin with prefix ANU are from Data Protection for Oracle.
v Messages that begin with prefix BKI are from Data Protection for mySAP for
DB2 UDB and Data Protection for mySAP for Oracle.
v Messages that begin with prefix EEO are from one of the following components:
Data Protection for Snapshot Devices for mySAP for Oracle
Data Protection for Disk Storage and SAN VC for Oracle
v Messages that begin with prefix EEP are from Data Protection for Snapshot
Devices for mySAP for DB2 UDB.
v Messages that begin with prefix IDS are from one of the following components:
Data Protection for Snapshot Devices for mySAP for Oracle
Data Protection for Snapshot Devices for mySAP for DB2 UDB
Message Format
Messages consist of the following elements:
v A three-letter prefix. The relation of the prefixes to products is explained above.
v A numeric message identifier.
v A one-letter severity code. Severity codes are explained below.
v Message text that is displayed on screen and written to message logs.
v Explanation, System Action, and User Response texts. These texts elaborate on
the message text, and are accessible only via documentation.
The image below presents a typical message.
The callouts on the right of the image identify each element of the message.
Message Prefix
Message Number
Message Type*
ANR 0992 I
Server installation complete.
Message Text
Explanation: The server installation procedure

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

processing.
System Action
User Response: None.
User Response
* I = Information
E = Error
S = Severe Error
W = Warning
K = Kernel message that originates from the
hierarchical storage management (HSM) client
The following letters give an indication of the severity of the action that generated
the message. The severity codes and their meanings are as follows:
E
W
I
Error
Warning
Information
Processing cannot continue.

Processing can continue, but problems may occur later.
Processing continues. User response is not necessary.
Message variables in the message text appear in italics.
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.
In these examples, two different commands yield the same return code, but they
also return descriptive messages that are unique to each command. The two
commands are q event standard dddd and def vol cstg05 primary. Both yield a
generic message with return code:
ANS5102I: Return Code 11.
But the first command also yields a descriptive message:

ANR2034I: QUERY EVENT: No match found for this query.
And the second command also yields a unique, descriptive message:

ANRxxxx: DEFINE VOLUME: Storage pool CSTG05 is not defined.
Example One for QUERY EVENT Command:
Chapter 1. Introduction
Example Two for DEFINE VOLUME Command:
Chapter 2. Obtaining Help for IBM Tivoli Storage Manager

There are many opportunities to learn about your product. Proactive education can
help you when you encounter problems, and help you get the most out of your
product. If you have questions or problems with your software product, you can
search for an answer in several knowledge bases. You also have the option to
obtain product support.
Learning About Your Product

Start at the Tivoli Software Training and Certification site at www.ibm.com/
software/tivoli/education.
The Training tab contains information about and links to the following educational
resources:
v Role-based training road maps
v Course catalogs by product
v Class schedules by locale
v Upcoming web seminars
The Resources tab contains information about and links to the following
educational resources:
v Free online product tutorials
v Support Technical Exchanges
This program provides support discussions containing product information,
deployment and trouble-shooting tips, common issues, problem solving
resources and other Support and Services recommendations. Tivoli engineers
and consultants presenting the topic provide subject matter expert direction and
value as Exchange leaders.
v Tivoli Field Guides
These white papers and scripts written by Tivoli employees and by Tivoli
customers are for two types of issues:
Technical Issues. These papers are designed to address specific technical
scenarios or concepts, which are often complex to implement or difficult to
understand.
Business Issues. These papers are designed to address specific business
practices that have a high impact on the success or failure of an ESM project.
v The Global Tivoli User Group Community
This is the information and community hub for user groups, business partners,
IT professionals and business users. It is a forum to communicate and share
experiences, ideas, solutions, and technical expertise related to the use of Tivoli
family of products and related products and services.
For more resources, see the IBM Tivoli Storage Manager Support site at
www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html. From this site you can search knowledge
bases for information about Tivoli Storage Manager:
v Technotes. Technotes are published by the technical support organizations to

assist IBM customers and personnel in the installation, use and management of
IBM products. Each addresses a specific topic.
v White Papers. White Papers are published by the technical support organizations
to provide guidance and detailed technical information on the installation, use
and management of IBM products.
v Redbooks. Redbooks are the output of residencies which are intensive,
multi-week work efforts where small teams explore and document product
implementation, integration and operations, often in the context of marketplace
solutions.
v FAQs
v Product Manuals
You can personalize your support experience at the Software Support site at
www.ibm.com/software/support/einfo.html. A tutorial that demonstrates how to
personalize your support experience is available at www.ibm.com/software/
support/sitetours.html#My_Support.
To participate in user discussions of Tivoli Storage Manager you can also subscribe
to the ADSM-L list server. This is a user forum maintained by Marist College. The
forum is not officially supported by IBM, but Tivoli Storage Manager developers
and other IBM support staff participate on an informal, best-effort basis.
You can subscribe by sending a note to the following e-mail address:
listserv@vm.marist.edu The body of the message must contain the following:
SUBSCRIBE ADSM-L yourfirstname yourlastname The list server will send you a
response asking you to confirm the subscription request. Once you confirm your
subscription request, the list server will send you further instructions. You will
then be able to post messages to the list server by sending e-mail to:
ADSM-L@vm.marist.edu.
Searching Knowledge Bases

If you have a problem with your IBM software, begin by searching the available
knowledge bases to determine whether the resolution to your problem is already
documented.
Searching the Information Center on your Local System or

Network
The most recent English and national language version IBM Tivoli Storage
Manager publications are available at the online information center linked from the
Tivoli Storage Manager product Web site at www.ibm.com/software/tivoli/
products/storage-mgr/. From the left pane select Technical Documentation. The
publications are available in PDF or HTML formats, or both.
Obtaining Message Explanations from the Product Command

Line Interface
Use the HELP command on the server console or administrative command line
client to display explanations about server and administrative command line client
messages (ANRxxxx). Use the HELP command on the backup-archive client to
display explanations about client messages (ANSxxxx).
For server 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, except those specific to the
administrative graphical user interface client.
Searching the Internet

If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem. You can search multiple Internet resources for your product at the Tivoli
Storage Manager Support at www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html. Find the section to search the support
knowledge bases near the top. From this section, you can search a variety of
resources including: IBM technotes, IBM downloads, IBM Redbooks, and Flashes
(alerts from technical support). A guided tour of how to search effectively is
available at www.ibm.com/software/support/viewlet/
sw_search_viewlet_swf.html.
The Marist College ADSM-L list server also contains information and respondents
who might solve your problem. For more information about the Marist College
ADSM-L list server, please see Learning About Your Product on page 7
Obtaining Product Support

The Tivoli Storage Manager Support site offers self-help resources at
support/IBMTivoliStorageManager.html. At this site you can get the IBM Support
Assistant product plug-in for Tivoli Storage Manager Server. IBM Support
Assistant makes it easier to access support resources for multiple products. You can
add plug-ins to IBM Support Assistant for the IBM products you use. The Tivoli
Storage Manager Server product plug-in enhances the Search, Education, Support
Links and Service component of IBM Support.
If you dont find a solution to your problem in the self-help resources, and you
have a maintenance contract, you may submit a service request. Tutorials on using
ESR (Electronic Service Request) for submitting problem records online is available
at www.ibm.com/software/support/sitetours.html#My_Support.
An overview of the software support process is provided in the Software Support
Handbook, which can be found by clicking on the Support Handbook under
Support Essentials at the right side of the Tivoli Storage Manager Support site at
support/IBMTivoliStorageManager.html. The goals of the Handbook are to provide
information on the support services currently available from IBM, including
definitions of programs, policies, and procedures, and to help you effectively
utilize IBM Software Support services. The Handbook also includes a glossary of
acronyms often used in the Support process.
Chapter 2. Obtaining Help for IBM Tivoli Storage Manager
10
Part 2. Server Messages
11
12
Chapter 3. Common and Platform Specific Messages

(ANR0100ANR9999)
This chapter contains the common and platform-specific server messages. 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

creating table table name.
ANR0104E

deleting row from table table name.
Explanation: An internal error has occurred in an

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

attempt to remove data from a server database table.
This message always accompanies another error
message and provides more detail about that error.
System action: The activity that generated this error

fails.

fails.
User response: Contact your service representative.
ANR0101E

opening table table name.
ANR0105E
Source file(line number): Error setting

search bounds for table table name.

attempt to access a server database table. This message

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

fails.

fails.
ANR0102E

inserting row in table table name.

attempt to add data to a server database table. This
fails.
ANR0106E
Source file(line number): Unexpected error

error code fetching row in table table
name.

attempt to access data in a server database table. This
fails.
ANR0103E

updating row in table table name.

attempt to update data in a server database table. This
fails.
ANR0107W
Source file(line number): Transaction

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

transaction commit. This message should be preceded
by another error message which provides more detail
about that error.

13
ANR0108E ANR0115W
fails.
ANR0111E

ANR0108E
Source file(line number): could not start a

new transaction.
Explanation: An error occurred while attempting to

start a new transaction. Possibly there is not enough
memory.
fails.
User response: Allocate additional storage to the
server. For details, issue HELP MEMORY to display the
information online or see Appendix A. Allocating
Additional Server Memory.
ANR0109E
Attempt number att_num Unable to load

cryptography module from icc location.

load the cryptography module.
Command: The BEGINNODEID and

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

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

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

ENDNODEID is invalid because the value of the
BEGINNODEID is greater than the ENDNODEID.
User response: Reissue the command, specifying the
ENDNODEID to be greater than the BEGINNODEID,
or both to be equal.
System action: The application will not start.

User response: Verify that the ICC cryptography
directory is located in either the application root
directory or the directory specified in the platform
specific environment variable (the DSMSERV_DIR for
Unix platforms or the Windows registry).
ANR0110E
An unexpected system date has been

detected; the server is disabled. Verify
the system date and use the ACCEPT
DATE command to establish the current
date as valid.
Explanation: The server has noted that the current

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

been specified more than once. The name occurs more
than once in the COPYSTGPOOLS list, more than once
in the ACTIVEDATAPOOLS list, or it has been
specified in both lists.
System action: The command fails.
User response: Reissue the command specifying
unique storage pool names.
ANR0114E
Command: The NUMBER parameter is

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

the FORMAT LFVOLUME COMMAND when the
LFVOLUMEFORMATCOUNT option is set to 0.
System action: The command is not executed.
User response: Either reissue the command with the
NUMBER parameter or else use the the SETOPT
command to change the LFVOLUMEFORMATCOUNT
value.
ANR0115W
14
Command: The storage pool list specified

with the parameter parameter name
includes storage pool storage pool name
more than once for simultaneous write.
The server script script name attempted

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

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

commands started by the script to complete. When all
previous parallel commands are complete, the server
allows the script to continue. The script can attempt to
start more parallel commands. If the limit is exceeded,
the command will run serially.
System action: The option is ignored and is not sent

to the client. The server continues processing.
User response: Client options INCLUDE and
EXCLUDE are not valid; use the INCLEXCL option
along with the specific include or exclude option that
you want the clients to use.
ANR0119W
The client option client option is not

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

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

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

state has been set.
System action: The server waits for all previous

parallel commands before allowing the script to
continue.
System action: Processing continues.
User response: Reduce the number of parallel

commands or scripts that are running on the server at
any one time.
ANR0121E
ANR0117E
The server contains stored data. Archive

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

state cannot be changed while the server contains any
backup, archive, or space-managed data.
User response: None.
Explanation: The specified command is not allowed

when archive data retention protection is enabled on
the server.
ANR0122E

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

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

EXCLUDE are not valid and have been replaced by the
combined INCLEXCL. If INCLUDE and EXCLUDE are
used in client option sets, use the INCLEXCL option
along with the specific include or exclude option that
you want the clients to use.
command is not allowed when archive

data retention is enabled.
command: A node cannot be assigned to

a new domain when archive data
retention is enabled.
Explanation: A previously defined node cannot be

assigned to a new domain when archive data retention
protection is enabled on the server.
ANR0123E
command: A device type of SERVER is

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

when archive data retention protection is enabled on
the server.
15
ANR0124W ANR0132E
ANR0124W
Object object name (object id hi.object id lo)

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

because:
v Archive retention protection is enabled and the
objects retention period has not elapsed, or
v The object is part of a deletion hold.
System action: Server operation continues.
ANR0125W
DELETE FILESPACE filespace name for

node node name contains retention
protected data and cannot be deleted.
Explanation: The specified file space cannot be deleted

because it contains one or more objects that must be
retained for one of the following reasons:
objects retention period has not elapsed.
ANR0128W
Explanation: At server startup, the server discovered

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

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

because it contains one or more objects that must be
retained because of one of the following:
objects retention period has not elapsed.

ANR0130E
ANR0127E
command to another server is not

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

when data retention protection is enabled on the target
server.
Diagnostic(ID): Server LOG space

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

server recovery log.
fails.
User response: To increase the amount of log space
available to the server, an authorized administrator can
add log volumes by using the DEFINE LOGVOLUME
command, and extend the size of the log by using the
EXTEND LOG command.
ANR0131E

Database upgrade completed

successfully.
Explanation: The requested database upgrade

operation completed successfully.
System action: The file space is not deleted.

The previous database upgrade did not

complete successfully.
Diagnostic(ID): Server DB space

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

server database.
fails.
User response: To increase the amount of database
space available to the server, an authorized
administrator can add database volumes by using the
DEFINE DBVOLUME command, and extend the size of
the database by using the EXTEND DB command.

ANR0132E
Diagnostic(ID): Memory allocation failed:

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

memory to create the object named.
16
ANR0133E ANR0147E
fails.

ANR0143E
ANR0133E
Error loading module modname: error

string
Explanation: The error specified by error string

occurred when the server attempted to load module
modname
System action: Server operation continues, but the
function provided by the module is not available.
Explanation: The command fails if the administrator

issuing the command does not have sufficient authority.
User response: Check the help for the command and
verify that the administrator has either system or
unrestricted policy authority; then issue the command
again.
ANR0144E
User response: Refer to the error string and correct

the condition causing the load to fail.
ANR0134W
There is an error reading from standard

input; the console input daemon
stopped.
Explanation: Warning: warning string

System action: Server operation continues, but
standard input is not available.
User response: If the server was started in the
background, there is no error, or else standard input is
in an error state.
ANR0140I
Command: success. Node node_id_1 is

granted proxy authority to node
node_id_2.
Command: failed. Proxynode authority

for node node_id_1 has not been revoked
to node node_id_2.
Command: failed. Node node_id_1 was not

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

nodes has not been defined to the server.
User response: Verify that both nodes have been
defined to the server and then issue the command
again.
ANR0145E
Command: failed. Node node_id_1 already

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

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

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

ANR0146E
ANR0141E

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

do not exist, or if the administrator issuing the
command does not have sufficient authority.
User response: Verify that both nodes exist and that
the administrator has sufficient authority, then issue the
command again.
ANR0142I
Command: success. Proxynode authority

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

granted proxynode authority to itself.
Explanation: The command failed because a node

cannot have a proxy relationship defined to itself.
ANR0147E
Command: failed. Proxy node authority

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

nodes has not been defined to the server.
User response: Verify that both nodes have been
System action: The server performs the command.

17
ANR0148I ANR0193E
defined to the server, and then issue the command
again.
ANR0148I
Command: No proxy relationships were

found.
User response: Reissue the command specifying ten or

fewer active-data pool names.
ANR0153E
Explanation: No proxy relationships were found.

System action: None.
Command: The pool active data pool name

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

active-data pool. Only active-data pools are allowed to
be specified in the ACTIVEDESTINATION parameter.
ANR0149E
Filespace filespace for node node_name

was deleted concurrently with the
command.
Explanation: The command failed. The requested

filespace was deleted concurrently with the command.
User response: Reissue the command specifying ten or

fewer active-data pool names.
ANR0160I
System action: The server will fail the command.

User response: Retry the command.
ANR0150E
Failed to open object object_name. There

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

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

specified with the
ACTIVEDESTINATION parameter
includes active data pool active data pool
name more than once.
Explanation: The number of active data pool names

that can be specified with the ACTIVEDESTINATION
parameter is limited to 10, and the names entered with
this parameter must be unique.
unique active-data pool names.
ANR0152E
Command: The number of active data

pool names specified with the
ACTIVEDESTINATION parameter
exceeds the maximum number allowed.
Explanation: The number of active data pool names

that can be specified with the ACTIVEDESTINATION
parameter is limited to 10.
18
Displaying segment segment number of

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

can have a very long name. When the name is very
long, it is broken into segments and displayed one
segment at a time.
System action: The fully-qualified name for this object
is displayed, one segment at a time, until the complete
name is displayed.
ANR0161I
Displaying segment segment number for

message insert insert identifier with text:
segment text.
Explanation: A message insert is too long to be

displayed in a single message. The message insert is
broken into segments and displayed one segment at a
time.
System action: The message insert is displayed one
segment at a time.
ANR0193E
The REPAIR EXPIRATION TYPE=type

command cannot be issued from the
server console.
Explanation: The specified REPAIR EXPIRATION

command was issued from the server console. This
command cannot be issued from the server console
because the administrator must be prompted to
continue processing the command.
System action: The server ignores the command and
continues processing.
User response: Issue the command from an
administrative client.
ANR0195W ANR0203W
ANR0195W
Attempting to remove extraneous

database entries for volume volume name.
Explanation: The server is attempting to remove

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

for volume volume name was successful.
Explanation: The server successfully removed

System action: System operation continues and future
operations on the specified volume should work
normally.
User response: The server successfully repaired the
specified volume.
ANR0197E

for volume volume name failed due to
contention with other server processes
or activities.
contention of the problem persists, please contact your

service representative for additional assistance.
ANR0199W
Not possible to repair volume volume

name due to other database references to
this volume.
Explanation: The server was not able to remove

extraneous database entries for the specified volume
because other database references to this volume exist.
System action: System operation continues.
User response: The volume repair operation for this
volume is not able to take any action because other
unexpected database references to this volume exists.
For additional assistance contact your IBM service
representative.
ANR0200I
Recovery log assigned capacity is size

megabytes.
Explanation: The amount of space allocated to the

recovery log is shown.
ANR0201I
Database assigned capacity is size

megabytes.

This was due to contention with another server process
or activity.
Explanation: The amount of space allocated to the

database is shown.
System action: System operation continues and this

volume still has extraneous database entries.
User response: It is possible that future server

activities or processes will select this volume and
attempt to repair it. If this occurs and the future
attempt is successful, no further action is needed. The
server administrator should review the activity log for
the time that the repair was attempted and try to
determine what caused the contention. If you are
unable to determine the cause of the contention of the
problem persists, please contact your service
representative for additional assistance.
ANR0202W
ANR0198E

for volume volume name failed.
Database volume volume name varied

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

varied offline because too many read errors have been
encountered.
System action: If available, a mirrored copy of the
volume is used.
User response: Correct the cause of the read errors.
ANR0203W

offline due to excessive write errors.

Explanation: The database volume shown has been

varied offline because too many write errors have been
encountered.
System action: System operation continues and this

volume still has extraneous database entries.

volume is used.
User response: The server administrator should

review the activity log for the time that the repair was
attempted and try to determine the cause of the failure.
If you are unable to determine the cause of the
User response: Correct the cause of the write errors.
19
ANR0204W ANR0213W
ANR0204W
Recovery log volume volume name varied

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

been varied offline because too many read errors have
been encountered.
User response: See accompanying messages for

information about the volume in error.
ANR0209E

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

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

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

page does not contain the expected page address.
System action: The failed I/O operation is retried on a
mirrored volume.
Explanation: The recovery log volume shown has

been varied offline because too many write errors have
been encountered.


volume is used.
ANR0210S
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
page number (physical page physical page
number).
Explanation: During a write of a database page, an

error occurred so that the page was not completely
written to disk.
Inconsistency found in LVM data page

page number - partial write detected.

mirrored volume.
ANR0211S

mirrored volume.
Inconsistency found in LVM data page

page number - page address mismatch
(actual page number).

Explanation: During a read of an LVM internal page,

the page does not contain the expected page address.
ANR0207E

mirrored volume.
Page address mismatch detected on

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

page does not contain the expected page address.

ANR0212E
Unable to read disk definition file file

specification.

mirrored volume.
Explanation: At startup, the server cannot read the

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

System action: Server initialization fails.
ANR0208W
Partial write detected on recovery log

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

an error occurs so that the page is not completely
written to disk.
mirrored volume.
20
User response: Use a text editor to recreate the file; it

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

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

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

the specified database volume is in the offline state.
System action: The volume is not accessed.
User response: Determine the reason for the volume
being offline; if possible, vary it online.
ANR0219I
Explanation: An attempt has been made to add a

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

the offline state - VARY ON required.

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

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

volume name - capacity must be at least 5
megabytes.
Synchronization of database volume

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

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

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

volume.

synchronize the contents of the recovery log volume
shown with its copy volume(s). The background
process was assigned the process ID shown.

ANR0217I
Recovery log volume volume name is in

the stale state - synchronization
process started.

the recovery log volume shown is not synchronized.
System action: A process is started to synchronize the
volume.
ANR0218I
Unable to install database volume

volume name - capacity must be at least 5
megabytes.
Synchronization of recovery log volume

volume name started as process process ID.
System action: The background process starts to

synchronize the volume and server operation continues.
PROCESS command, or cancel the process by using the
ANR0222E
Error action disk definition file file

specification.
Explanation: An error occurred creating or changing

the disk definition file.
Explanation: An attempt has been made to add a

database volume that is smaller than the server
minimum.

write error and correct it.
System action: The volume is not added.
ANR0223E
User response: Increase the size of the volume or

supply another larger volume.
Error writing list of disks to disk

definition file.
Explanation: The disk definition file cannot be

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

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

specified more than once in the server installation
execution.
ANR0234I
Synchronization complete for database

volume volume name.
Explanation: The synchronization process for the

database volume named has finished successfully.
System action: The volume is varied online.
System action: Installation ends.
ANR0235I
User response: Reinitialize the server install specifying

a unique name for each database and recovery log
volume.
Explanation: The synchronization process for the

recovery log volume named has finished successfully.
Synchronization complete for recovery

log volume volume name.

ANR0230E
Synchronization process failed for

database volume volume name.
Explanation: The process that was attempting to

synchronize the database volume shown has failed.
System action: The volume is in the stale state.
User response: See accompanying messages for more
information.
ANR0231E
Synchronization process failed for

recovery log volume volume name.

synchronize the recovery log volume shown has failed.
information.
ANR0232I
Synchronization process canceled for


synchronize the database volume shown has been
canceled.

ANR0240E
Deletion process failed for database

volume volume name.

delete the database volume shown has failed.
System action: The volume is not deleted.
information.
ANR0241E
Deletion process failed for recovery log

volume volume name.

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

volume volume name.

delete the database volume shown has been canceled.
User response: If desired, issue a VARY ONLINE

command to start another synchronize process.

ANR0233I
Synchronization process canceled for


synchronize the database volume shown has been
canceled.
User response: If desired, issue a VARY ONLINE
command to start another synchronize process.
22
ANR0243I
Deletion process canceled for recovery

log volume volume name.

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

volume name.
ANR0249E
Explanation: The delete process for the database

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

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

attempting to read a page from the specified recovery
log volume.
ANR0245I

mirrored volume, if available.
System action: The volume is deleted.
Deletion complete for recovery log

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

volume named has finished successfully.

information about the volume in error. If the error
persists and another mirrored copy of the volume is
available, the failing volume should be taken offline, by
using the VARY OFF command, and repaired.

ANR0250I
ANR0246E
Error reading logical page logical page

number) from database volume volume
name.

attempting to read a page from the specified database
volume.
mirrored volume, if available.
information about the volume in error. If the error
persists and another mirrored copy of the volume is
available, the failing volume should be taken offline by
using the VARY OFF command, and repaired.
Otherwise, halt the server and repair the volume. Then
restart the server.
Recovery log page logical page number

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

read the desired page from another synchronized
mirrored volume.
ANR0251E
Unable to read recovery log page logical

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

read the desired page from another mirrored volume
because no other mirrored volume was in the
synchronized state. This message is normally preceded
by a message indicating which volume failed.
System action: Processing is ended.
ANR0247I
Database page logical page number

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

read the desired page from another synchronized
mirrored volume.
User response: You can repair the failed volume by

halting the server and correcting the volume errors.
ANR0252E
Error writing logical page logical page

number) to database volume volume name.

attempting to write a page to the specified database
volume.
Unable to read database page logical page

number from any alternate copy.
System action: If a mirrored volume is available then

the failing volume is forced into the offline state.
Explanation: After a read error, the server is unable to

read the desired page from another mirrored volume
because no other mirrored volume is in the
User response: Repair the failing volume, and then

use the VARY ON command to bring the volume back
online.
ANR0248E

23
ANR0253E ANR0261I
ANR0253E
Unable to write database page logical

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

to write the desired page to another mirrored volume

volume.
System action: If a mirrored volume is available, the
failing volume is forced into the offline state.
online.

User response: Repair the failed volume.
ANR0254E
Error writing logical page logical page

number) to recovery log volume volume
name.

attempting to write a page to the specified recovery log
volume.
online.
ANR0255E
Unable to write recovery log page logical

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

to write the desired page to another mirrored volume
ANR0258E
Unable to write complete

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

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

restart/checkpoint information from any
database or recovery log volume.
Explanation: During server restart, the server is

unable to read a complete set of restart/checkpoint
information from any of the defined database or
recovery log volumes.
System action: Server restart is ended.
User response: Ensure that all defined database and
recovery log volumes are available for use by the
server.

ANR0256E
Error writing physical page physical page

number to restart/checkpoint area on

volume.
online.
ANR0257E
Error writing physical page physical page

number to restart/checkpoint area on
24
ANR0260I
Database page logical page number

successfully resynchronized.
Explanation: After detecting a partially-written

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

successfully resynchronized.
Explanation: After detecting a partially-written

recovery log page, the server is able to rewrite the page
by using a synchronized mirror copy.
ANR0262W ANR0272E
ANR0262W
Incompatible database restart/recovery

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

database and recovery log volumes were written in a
format that is not compatible with the restart/recovery
area written by other versions of the server.
System action: The server starts normally. If the
database and recovery log are writable (not Read
Only), then the restart/recovery area will be converted
to a compatible format. Message ANR0263I will be
issued when the conversion has been completed.
ANR0263I
Database restart/recover area

successfully converted to compatable
format.
Explanation: The server converted the

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

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

unable to process the server log disks due to
insufficient memory.
System action: Server installation stops.
User response: Restart the server installation process
with more memory available.
ANR0266E
Database disk processing failed:

sufficient memory is not available.
unavailable, and correct the problem. Restart the server

installation process.
ANR0268E
Database volume volume name is not

available.
Explanation: The specified volume cannot be found

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

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

volume, the server cannot start a thread to service I/O
requests.
Additional Server Memory. Restart the server
ANR0270E
Process for Database volume volume

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

volume, the server cannot start a thread to service I/O
requests.
Additional Server Memory. Restart the server
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

specified than the server can manage.
User response: Restart the server installation process

with more memory available.
User response: Reduce the number of recovery log

volumes specified. Restart the server installation
process.
ANR0267E
Log volume volume name is not available.
Explanation: The specified volume cannot be found

during installation.
User response: Determine the reason the disk is
ANR0272E
Maximum number of database volumes

exceeded.
Explanation: More database volumes have been

specified than the server can manage.
25
ANR0273W ANR0291E
User response: Reduce the number of database
volumes specified. Restart the server installation
process.
ANR0273W
Not initializing library library name

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

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

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

not be used for new transactions until it is set online
again.
System action: This mount fails.
User response: Refer to the UPDATE PATH command
for details on changing the online option.
ANR0285I
Database page shadowing started using

file file name.
Explanation: The database page shadowing function

was started. The file specified is used to store the
shadowed database pages.
contents are not valid. This can be caused by: a partial

write to the page shadow file itself, the file being
manipulated by a process outside of the server, the file
being overlayed by a different file, or the file could
have been erased.
ANR0288W
Explanation: One or more pages from the last batch of

pages written to the server database has been detected
to be corrupt. The server will attempt to use the
contents of database page shadow file and replace the
corrupted database page.
System action: Server startup continues.
User response: A corruption of a database page within
the server database, is typically caused by a partial
write. A partial write may occur when the server is
brought down external to normal server processing. If
the server terminated without a halt command being
issued or if the machine the server is running on
crashed unexpectedly, this may account for the partial
write. Other possible causes of a partial write are a disk
drive failure, improperly terminated scsi bus, or a
failure in a device controller. Please try to identify the
cause of the partial write and take the appropriate
action to prevent this from occurring in the future.
ANR0289W

ANR0286W
Database page shadowing using file file

name failed to start.

could not start. An error has been encountered
accessing the page shadow file specified.
ANR0287W
Contents of the page shadow file file

name are not valid.

could not use the contents of the existing file. Restart
recovery using this file is not possible.
System action: The server attempts to start without
having the database page shadow file available.
User response: The database page shadow file
26
Damaged database pages were

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

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

User response: Verify that there is enough space for
the page shadow file. That page shadow file requires
approximately 65 kilobytes of space, if this space is not
available a new location for the file should be specified.
One or more database pages in the last

batch written is corrupt - contents of
database page shadow file will be used
to fix the page or pages.
Failure occurred attempting to replace

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

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

file.
Explanation: The server encountered an error writing

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

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

shadow file referenced but was unable to open the file.
The file does not exist.
ANR0304I
Page service time: rate ms.
Explanation: During formatting, the formatter

required the number of milliseconds indicated to
process each page.
ANR0305I
Recovery log format complete.
Explanation: Formatting of the server recovery log

completed successfully.
System action: The server will continue to operate

and will attempt to create this as a new database page
shadow file.
ANR0306I
ANR0300I
Recovery log format started; assigned

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

log has started.
Recovery log volume mount in progress.
Explanation: During restart, the server is mounting

required recovery log volumes.

ANR0307I
Recovery log extend in progress; count

megabytes of count formatted.
System action: The log is formatted for use by the

server.
Explanation: As a result of an EXTEND LOG

command, the additional recovery log pages are being
formatted.
System action: Formatting continues.
ANR0301I
Recovery log format in progress; count

megabytes of count.
Explanation: The amount of the server recovery log

shown has been successfully formatted.

ANR0309I
Recovery log extend terminated process canceled.
Explanation: The process started as a result of an

EXTEND LOG command and has been canceled.
System action: The EXTEND command is ended.
ANR0302I
Recovery log formatting took mseconds

milliseconds.
Explanation: Formatting of the recovery log has

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

processed the number of pages indicated each second.

ANR0311I
Recovery log reduce in progress; count

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

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

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

REDUCE LOG command and has been canceled.
System action: The REDUCE command is ended.
ANR0314W
Recovery log usage exceeds utilization

percentage % of its assigned capacity.
Explanation: This message is issued to notify the

administrator that the server recovery log utilization
exceeds 90% or more of its assigned capacity.
back-level and is not able to support LAN-Free

operations using this device class.
System action: LAN-Free data movement operations
are not performed. The operations are either sent via
the LAN or else proxied by the storage agent directly
to the server.
User response: In TSM version 5.3, a change was
made to the way the FILE and device classes are
supported. This change prevents back-level storage
agents from being able to use these device classes. The
storage agent should be upgraded to the same version
and release as the server. Until the storage agent is
upgraded, any LAN-Free data movement operations
that are attempted will be done using the LAN.

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

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

information in the recovery log. Typically, the
corruption is caused by a hardware or environmental
failure external to TSM.
System action: Server operation terminates.
User response: If the server database and recovery log
are mirrored, set the MIRRORREAD LOG VERIFY and
MIRRORREAD DB VERIFY options in the server
options file and restart the server. If database and
recovery log mirrors are not available, or all mirrors are
corrupted, restore the server database to the latest
backup and restart the server.
ANR0320W
Storage agent storage agent is not able to

use device class device class for storage
pool storagepool for LAN-Free data
movement operations.
Explanation: The storage agent referenced is not able

to perform LAN-Free data movement operations using
this storage pool and device class. The storage agent is
28
ANR0321W
Storage agent storage agent name at

version storage agent VRMF does not
support operation operationName,
although the server server name at
version server VRMF can support it.
Explanation: The storage agent is at an earlier version

than the server and is not able to use advanced
functions that were requested by a client.
System action: The operation is not allowed.
User response: The storage agent must be upgraded
to a version, release, and level that supports this
operation. Typically, the problem is that the storage
agent and server are not at the same version and
release. For example, if the server is version 5.3.0.0 and
the storage agent is version 5.2.3.0, the storage agent
needs to be upgraded to version 5.3.0.0 to perform the
requested function.
If this was a restore or retrieve operation and the client
node DATAREADPATH setting was ANY or LANFREE,
the server will override this to be LAN only. This will
cause the operation to fail on the storage agent and
message ANR0416W to be issued. Retry the operation
after performing one of the following actions:
v Halt the storage agent, upgrade the storage agent
program, and then restart the storage agent.
v Set the ENABLELANFREE client option to NO, and
then restart the client
If this was a no-query restore operation, the data was
not restored by the storage agent using LAN-Free data
transfer. If the client node is allowed to read data over
the LAN, the data was restored over the LAN. If the
operation failed because the client node is not allowed
to read data over the LAN, consider updating the
DATAREADPATH setting for this node by using the
UPDATE NODE command.
If this was an operation performed by an agent node
with proxy node authority to a target node, the session
failed with a protocol error. The operation was
attempted by a version 5.3 or higher client and server,
but the storage agent is not able to support this
ANR0348S ANR0359E
operation. To allow an agent node to perform
operations for a target node, the storage agent must be
upgraded to version 5.3.0 or later.
ANR0348S
Database restart record version version is

not recognized.
Explanation: During server initialization, the server

database initialization failed because the version of the
restart record is not recognized.
System action: The Server is terminated.
User response: Install the latest version of the Server
or restore the database to a point in time prior to the
previous upgrade.
ANR0349S
The database has been upgraded from

Express.
Explanation: The Express server has been started with

a database that has been upgraded from Express to
base TSM. Once the database is upgraded from
Express, it cannot be used by an Express server.
ANR0353I
Recovery log analysis pass in progress.
Explanation: During server initialization, the process

of analyzing the server recovery log has begun.
ANR0354I
Recovery log redo pass in progress.

of committing incomplete transactions has begun.
ANR0355I
Recovery log undo pass in progress.

of rolling back incomplete transactions has begun.
System action: The Server is terminated.

User response: Either restore the database from a
version taken prior to the upgrade, or use a base TSM
Server with the current database.
ANR0350I
Recovery checkpoint started.

of bringing the server database back to a state of
consistency has begun.
ANR0351I
Recovery checkpoint complete.

of bringing the server database back to a state of
consistency has completed successfully.
ANR0352I
Transaction recovery complete.

of recovering any incomplete transactions has
ANR0356I
Recovery log compression started.
Explanation: The process of removing unneeded data

from the server recovery log has begun.
ANR0357I
Recovery log compression ended.
Explanation: The process of removing unneeded data

from the server recovery log has completed.
ANR0358E
Database initialization failed: sufficient


database fails initialization because sufficient server
System action: Initialization fails.
User response: Make more memory available to the
server.
ANR0359E
Database initialization failed: unable to

read database restart record.

database initialization fails because the required restart
record cannot be read.
29
ANR0360E ANR0379W
ANR0360E
Database initialization failed: database

size mismatch; LVM size = size, expected
size = size.

database initialization fails because the size of the
database does not match its prior size.
ANR0361E
Database initialization failed: error

initializing database page allocator.

database initialization fails because the page allocator
cannot be started.
recovery process is the database must be restored with

a process that includes a DSMSERV FORMAT. Either
the data base volumes must be formatted then a
DSMSERV RESTORE DB performed from a data base
backup that does not have this problem, or a
DSMSERV UNLOADDB followed by the formatting,
then a DSMSERV LOADDB. Do not use DSMSERV
DUMPDB on the data base for this recovery.
System action: Server RESTORE DB continues.
User response: Perform one of the data base recovery
actions after the RESTORE DB completes.
ANR0365I
Database format started.
Explanation: Formatting of the server database has

started.
System action: The database is formatted for use by
the server.
ANR0362W
Database usage exceeds utilization

percentage % of its assigned capacity.
ANR0366I
Database format in progress; count

megabytes of count processed.

administrator that the server database utilization
exceeds 80% or more of its assigned capacity.
Explanation: The number of megabytes shown have

been successfully formatted for the server database.
User response: Depending upon the size of your

database, add database volumes, or extend the
database, or both, before it fills completely. The server
expiration process may also free up database space
making it available to other server processes. Refer to
the EXPIRE INVENTORY, DEFINE DBVOL, and
EXTEND DB commands for more information on these
operations.

ANR0367I
Database format completed.
Explanation: Formatting of the server database

ANR0363I
Database was automatically upgraded to

the server program level.

administrator that the server database was
automatically upgraded to the current server program
level. The upgrade is performed when the
UPGRADEDB parameter is specified at server start-up
and the server is started over a database that was
written by a down-level version of the server program.
User response: None. The UPGRADEDB parameter
does not need to be specified during future server
start-ups.
ANR0364W
Server has detected a zero bit mismatch

error.

administrator that the server has detected a zero bit
mismatch error during a RESTORE DB process. The
30
ANR0379W
A server database deadlock situation has

been encountered; the lock request for
the lock name lock, key name will be
denied to resolve the deadlock.
Explanation: The server detected a deadlock situation

between a number of processes attempting to access
database information. A lock request for one of the
processes will be denied to resolve the database
deadlock. When the server processes encounter a
database deadlock, they usually try to run the function
that was in progress when the deadlock was
encountered again. Not all process can explicitly try an
operation again. For example, migration and
reclamation will eventually try again. However,
something like a delete volume run in a macro will
only be tried again if the delete command is reissued
either in the macro or the command line.
System action: A lock request fails for one of the
deadlocked processes. Server operation continues.
ANR0380W ANR0387I
User response: If a process can try again (like
migration), then monitor the try-again attempt to see if
it succeeds or not. If it fails, contact a service
representative. If the process or command is not able to
try again, then reissue the command or macro that
caused the action to occur. If it fails again, contact a
service representative for further assistance to better
isolate the deadlock condition.
ANR0380W
The database buffer pool recovered

from an overcommit of number of pages
pages. Consider increasing your buffer
pool size by kilobytes needed kilobytes
under current server load.
Explanation: During normal processing, additional

buffer pool space is required beyond that specified in
the BUFPOOLSIZE in the server options file. The
additional kilobytes of buffer pool space that are
required are indicated in the message.
System action: Server operation continues; the
additional buffer pool space is obtained from available
server memory.
User response: If the current server load is typical,
consider increasing the size specified for your
BUFPOOLSIZE option by the number of kilobytes
specified in the message. To do this, you must halt the
server, change the options file, and then restart the
server.
ANR0381I
Buffer pool statistics were successfully

reset.
Explanation: Buffer pool statistics, such as the Cache

Hit Ratio, have been reset. The RESET BUFPOOL
command and the ESTIMATE DBREORGSTATS
command will reset the buffer pool statistics.
ANR0383I
The recovery log maximum utilization

statistic was successfully reset.
Explanation: The recovery log maximum utilization

statistic has been reset by the RESET
LOGMAXUTILIZATION command to the current
utilization.
User response: The QUERY LOG command
(FORMAT=DETAILED) can be used to display the
current value for the maximum utilization.
ANR0384I
The recovery log consumption statistic

was successfully reset.
Explanation: The recovery log consumption statistic

has been reset by the RESET LOGCONSUMPTION
command.
User response: The QUERY LOG command
current value for recovery log consumption.
ANR0385I
Could not free sufficient buffers to

reach reduced BUFPoolsize.
Explanation: A reduction in the database buffer pool

size was requested. However, too many buffers were in
use to reach the lower buffer pool size.
System action: Server operation continues. Whatever
buffer pool size reduction that could be achieved is in
effect. The new bufpoolsize is written to the options file
for use on the next server startup.
ANR0386I
User response: The QUERY DB command

(FORMAT=DETAILED) can be used to to display the
current values for the buffer pool statistics.
Explanation: The BUFPoolsize option has been

changed to the indicated value.
ANR0382I
The database maximum utilization

statistic was successfully reset.
Explanation: The database maximum utilization

statistic has been reset by the RESET
DBMAXUTILIZATION command to the current
utilization.
User response: The QUERY DB command
current value for the maximum utilization.
The BUFPoolsize has been changed to

buffer pool size.

ANR0387I
Evaluating node node name using storage

agent storage agent for LAN-free data
movement.
Explanation: The server is evaluating whether the

node and storage agent can use storage pools capable
of LAN-free data movement.
System action: The server evaluates the storage pool
destinations available to this node and reports which
storage pools can and cannot be used for LAN-free
data movement.
User response: Review the results of this processing to
31
ANR0388I ANR0393I
determine if the appropriate LAN-free environment is
configured.
ANR0388I
Node node name using storage agent

storage agent has capable count storage
pools capable of LAN-free data
movement and not capable count storage
pools not capable of LAN-free data
movement.
Explanation: The server has completed evaluation of

the LAN-free and non-LAN-free storage pool
destinations for this node using this storage agent. The
server determined that there are capable count storage
pools that are capable of LAN-free data movement. It
also determined that there are not capable count storage
pools that cannot be used for LAN-free data
movement.
User response: Review the other messages issued to
determine which storage pools are capable of LAN-free
data movement and those which are not capable of
LAN-free data movement for this node using this
storage agent.
ANR0389W
Node node name has data path

restrictions.
Explanation: The node name has data path restrictions.

The registered node has data write path, data read
path, or both, configured to not allow LAN-free
operations.
User response: Issue the command QUERY NODE
node name F=D and evaluate the data read path and
data write path settings. To store data or read data
using LAN-free data movement, set the data write path
to ANY or LANFREE.
ANR0390W
A server database deadlock situation has

been encountered; the lock request for
transaction transaction ID will be denied.
Explanation: The server detected a deadlock situation

between a number of processes that were attempting to
access database information. A lock request for one of
the processes is denied, to resolve the database
deadlock. When server processes encounter a database
deadlock, they usually reattempt the function that was
in progress when the deadlock was encountered. Not
all process can explicitly try an operation again. For
example, migration and reclamation will eventually be
tried again. However, something such as a delete
volume run in a macro will only be tried again if the
delete command is reissued either in the macro or the
command line.
System action: A lock request fails for one of the
deadlocked processes. Server operation continues.
32
User response: If a process can retry (like migration),

then monitor the re-try attempt to see if it succeeds or
not. If it fails, contact a service representative. If the
process or command is not able to retry on its own,
then reissue the command or macro that caused the
action to occur. If it fails again, contact a service
representative for further assistance to better isolate the
deadlock condition.
ANR0391I
Evaluating lanfree destination for node

node name using storage agent storage
agent.
Explanation: The server is evaluating to determine

lanfree destination storage pools for the node and
storage agent referenced.
System action: The server will evaluate the storage
pool destinations available to this node and report
which pools may be used lanfree and for those that can
not be used lanfree it will report why that pool can not
be used.
User response: Review the results of this processing to
determine if the appropriate lanfree environment is
configured.
ANR0392I
Node node name using storage agent

storage agent has lanfree count lanfree and
non-lanfree count non-lanfree storage pool
destinations.
Explanation: The server is completed evaluation of the

lanfree and non-lanfree storage pool destinations for
this node using this storage agent. The server
determined that there are lanfree count storage pools
that are lanfree capable. It also determined that there
are non-lanfree count storage pools configured as
destinations for this node.
User response: Review the other messages issued to
determine which storage pools are capable of lanfree
data transfer and those which are not capable of lanfree
data transfer for this node using this storage agent.
ANR0393I
Management class management class with

destination storage pool for operation type
operations is lanfree capable for node
node name using storage agent storage
agent.
Explanation: The storage pool is capable of lanfree data

transfer operations for this node name using this storage
agent.
ANR0394W ANR0400I
ANR0394W

operations is not lanfree capable for
node node name using storage agent
storage agent because this destination is a
CENTERA device.
Explanation: The storage pool is not capable of lanfree

data transfer operations for this node name using this
storage agent. This storage pool uses a CENTERA device
and as such can not be used for lanfree operations.
not lanfree capable is if there are no paths defined for a

device to this storage agent. Use the QUERY PATH,
QUERY SERVER, QUERY STGPOOL, QUERY
LIBRARY, and QUERY DRIVE commands to determine
the drive or drives that need paths defined to this
server (storage agent). The final reason a storage pool is
reported as not lanfree capable is if there are define
paths to this storage agent but no paths are online. Use
the QUERY PATH and QUERY DRIVE commands to
evaluate this and if necessary use update those paths to
be online.

User response: To configure this node for lanfree data
transfer operations, update the destination storage pool
for the copygroup or assign this node to a domain that
has lanfree storage pool destinations.
ANR0395W

storage agent because this destination is
configured for simultaneous write.

storage agent. This storage pool is configured for
simultaneous write operations. Simultaneous write
operations are only allowed for data sent directly to the
server. Configuring a storage pool for simultaneous
write operations disqualifies it from being eligible for
use for lanfree operations.
User response: To configure this node for lanfree data
transfer operations, update the destination storage pool
for the copygroup or assign this node to a domain that
has lanfree storage pool destinations. Or update this
storage pool to disable simultaneous write by setting
the copy storage pools field to blank.
ANR0396W

storage agent because no online paths are
available.

storage agent.
User response: A storage pool can be reported as not
having lanfree capable paths for a number of reasons.
First, if this is a DISK storage pool, these are not
capable of lanfree operations. In this case, the
destination for this node or the domain this node is
assigned to should be changed to one that is lanfree
capable. The next reason a storage pool is reported as
ANR0397I
Session session number for node

agent_node has begun a proxy session for
node target_node.
Explanation: A client session has begun proxy

operations.
System action: The server granted a proxy session to
a client node.
ANR0398W

agent_node has failed to begin a proxy
session for node target_node.
Explanation: A client session attempted to begin a

proxy operation. The server failed the client request.
This can occur if the agent node does not have a proxy
association with the target node.
System action: The server blocks the proxy
authorization attempt.
ANR0399I

agent_node has ended a proxy session for
node target_node.
Explanation: A proxy session has been ended. The

server terminates a session if there is an error in the
protocol. On the other hand, the client can also
terminate the session.
System action: The server, or the client, has ended a
proxy session for a client node.
ANR0400I
Session session number started for node

node name (client platform) (communication
method).
Explanation: A new client session has been initiated

by the specified node. The session number, client
platform type and communication method used by this
session are included in the message.
System action: The server begins a communications
session to service the client node.
33
ANR0401I ANR0410E
ANR0401I

method) (WDSF client).
Explanation: A new WDSF client session has been

initiated by the specified node. The session number,
client platform type and communication method used
by this session are included in the message.
ANR0402I
Session session number started for

administrator administrator ID
(administrators platform) (communication
method).
Explanation: A new administrator client session has

been initiated by the specified administrator. The
session number, administrators platform type and
communication method used by this session are
included in the message.
session to service the administrator client.
ANR0403I
Session session number ended for node

node name (client platform).
Explanation: A client session has completed normally.

ANR0404I
Session session number ended for node

node name (client platform) (WDSF client).
Explanation: A WDSF client session has completed

normally.
ANR0406I
Explanation: A new client session has been initiated

by the specified node. The session number, client
platform type, communication method and address
used by this session are included in the message.
ANR0407I
Session session number started for

administrator administrator ID
(administrators platform) (communication
method communication address).
Explanation: A new administrator client session has

been initiated by the specified administrator. The
session number, administrators platform type,
communication method and address used by this
session are included in the message.
ANR0408I
Session session number started for server

server name (servers platform)
(communication method) for purpose.
Explanation: A new server session has been initiated

by the specified server for the specified purpose. The
session number, servers platform type and
communication method used by this session are
included in the message.
ANR0409I


method communication address).
Session session number ended for server

server name (client platform).
Explanation: A server has completed normally.

ANR0405I
Session session number ended for

administrator administrator ID (client
platform).
Explanation: An administrative client session has

completed normally.
34

ANR0410E
EXPORT operation to server server name

rejected - administrator administrator is
not authorized to perform the import
operation on the target server.
Explanation: An export operation to the named server

was rejected, because the administrator issuing the
export command is not defined on the target server or
does not have sufficient authority to perform the
import operation on the target server.
ANR0411I ANR0419W
ANR0416W

ANR0411I
Session session number for administrator

administrator name logged in as node node
name restored or retrieved object type
object: node node name, filespace filespace
name, object object name.
Explanation: This message logs information about an

object that was restored or retrieved by an
administrator logged in for a node.
ANR0412I
Session session number for node node

name restored or retrieved object type
object: node node name, filespace filespace
name, object object name.

name not allowed to operation using path
data transfer path.
Explanation: This session attempted this operation

using the specified data transfer path. This operation is
not permitted for this client.
User response: Issue QUERY NODE
FORMAT=DETAILED for this node to see the current
DATA WRITE PATH or DATA READ PATH settings.
These settings determine if a given operation is
permitted using a specific data transfer path. If this
client node should be permitted to perform this
operation using this data transfer path, the UPDATE
NODE command should be used to correct this.
ANR0417W

name terminated - data transfer path not
allowed.
Explanation: This message logs information about an

object that was restored or retrieved by an
administrator logged in for a node.
Explanation: This session attempted an operation that

needed a data transfer path that this node is not
allowed to use.
System action: This client session terminates.
User response: Refer to the ANR0416W message that

was issued for this client session to determine which
operation and data transfer path was attempted.
ANR0413I

administrator name logged in as node node
name is restoring backup set: node node
name, set filespace name.
Explanation: This message logs information about a

backup set restored by an administrator logged in for a
node.
ANR0414I

name is restoring backup set: node node
name, set filespace name.
Explanation: This message logs information about a

backup set restored by a node.
ANR0418W

administrator name (client platform) is
refused because an incorrect password
was submitted.
Explanation: The server refuses a request to start a

client session because an invalid password has been
submitted by the client during sign-on processing.
System action: The server will continue to deny access
attempts by this client until a valid password is
submitted.
User response: Enter the proper password. If you
have forgotten the password, contact an authorized
administrator, who can assign a new password using
the UPDATE ADMIN command.

ANR0415I
Session session number proxied by storage

agent name started for node node name.
Explanation: This session is started for the indicated

node and the storage agent acts as the proxy for the
node. Client node sessions are used to perform
LAN-free operations between the client and server.
ANR0419W
Administrative client userid

administrative ID cannot be used when
authentication is on.
Explanation: The server refuses a request for a client

(administrative) session because the user ID specified
cannot be used when authentication of IDs is in effect.
SERVER_CONSOLE is an administrative ID that has
this restriction.
User response: Use an administrative ID that was
35
ANR0420W ANR0427W
registered for this server and that has a password.
ANR0420W

name (client platform) refused - server
disabled for user access.

(backup-archive) session because the server is currently
disabled for client access.
Administrative clients are permitted access to the
server.
User response: An authorized administrator must
issue the ENABLE SESSION command before client
nodes are permitted access to the server.
ANR0421W

name (client platform) refused - sign-on
protocol violation.

session because sign-on protocol has been violated.
User response: This error is usually the result of a
client programming error in which the sign-on verb has
been incorrectly formatted and delivered to the server.
This error can also result when the server is contacted
by an application that is not a part of this product.
ANR0422W

name (client platform) refused - node
name not registered.

client session because the client node name is not
registered in the server database.
the server before establishing a session. An authorized

administrator must use the REGISTER ADMIN
command to register the administrator with the server.
ANR0424W

client session because an invalid password has been
submitted by the client during sign-on processing. The
server will continue to deny access attempts by this
client until a valid password is submitted.
User response: Enter the proper password. If the
password has been forgotten by the user, an authorized
administrator can assign a new password by using the
ANR0425W
ANR0423W

administrator ID (client platform) refused administrator name not registered.

name (client platform) refused - Node
password has expired.
Explanation: The server refuses the specified session

because the client nodes password has expired.
User response: Upon receipt of this error condition,
the client program immediately reconnects to the server
specifying a password update session and prompts the
user for a new password. After the user enters a new
password, the client reconnects to the server for normal
operations. Alternatively, an authorized administrator
can update the client password using the UPDATE
NODE command.
ANR0426W

User response: Register the node name with the
server before establishing a session. If the server is
running with OPEN registration, no action is required;
the client prompts the user for a password and
registers the client with the server. If CLOSED
registration is in effect on the server, an authorized
administrator must use the REGISTER NODE
command to register the client node name with the
server.

name (client platform) refused - invalid
password submitted.

name (client platform) refused - open
registration not permitted.
Explanation: The server refuses a client session

because an open registration action has been attempted
and the server is running with CLOSED registration.
User response: Ask an authorized administrator to
submit the request using the REGISTER NODE or
REGISTER ADMIN command.
ANR0427W

version is down-level with this client.
Explanation: The server refuses a request to start an

administrative session because the administrator name
is not registered in the server database.

because the client program version level is newer than
that supported by the server program.
User response: Register the administrator name with
User response: Apply service to the server program to
36
ANR0428W ANR0435W
make it compatible with the newer client program, or
use an older client program to contact the server.
ANR0428W

name (client platform) refused - client is
down-level with this server version.

because the client program version level is older than
that supported by the server program. For certain
problems (such as the compression fix), once a node
connects to the server using the newer client, the server
records this fact and will not let this node back off this
client version to a version that does not include the fix.
User response: Apply service to the client program to
make it compatible with the newer server program.
ANR0429W

name (client platform) refused - maximum
server sessions (max sessions allowed)
exceeded.
Explanation: The server refuses the specified client or

administrative session because the maximum number
of concurrent client sessions has been exceeded.
User response: If necessary, increase the maximum
number of permitted sessions. To do this, update the
value for the MAXSESSIONS parameter in the server
options file and restart the server with the updated
options file. Note that increasing the MAXSESSIONS
value requires additional memory resource by the
server. You may want to retry the connection at a later
time.
ANR0430W

name is locked.
Explanation: The server refuses the specified client

session because the node is locked from server access
(with the LOCK NODE command).
User response: Before the client node is permitted to
access the server, a properly authorized administrator
must unlock the node with the UNLOCK NODE
command.
ANR0431W
Session session number refused administrator administrator ID (client

platform) is locked.
Explanation: The server refuses the specified

administrative session because the administrator is
locked from server access (with the LOCK ADMIN
command).

User response: Before the administrator is permitted
to access the server, a properly authorized
administrator must unlock the administrator with the
UNLOCK ADMIN command.
ANR0432W

name (client platform) refused insufficient memory.
Explanation: The server ends the specified session

because sufficient memory (virtual memory) is not
available.
System action: The server ends the session and
continues operation.
ANR0433W
Session session number for node or

administrator ID (client platform) refused insufficient recovery log space.
Explanation: The server ends the specified client or

administrative session because sufficient log space is
not available to complete a database transaction.
add log volumes using the DEFINE LOGVOLUME
command, and extend the size of the log using the
EXTEND LOG command.
ANR0434W
Session session number for node or

administrator ID (client platform) refused insufficient database space.
Explanation: The server ends the specified client or

administrative session because sufficient database space
is not available to complete a database transaction.
administrator can add database volumes using the
the database using the EXTEND DB command.
ANR0435W

name (client platform) refused - internal
error detected.

because an internal logic error is detected.
37
ANR0436W ANR0442W
User response: To determine the source of the error,
the administrator can examine server messages issued
prior to this message. The QUERY ACTLOG command
can be used to view the activity log and search for
messages. If the error cannot be isolated and resolved,
contact your service representative.
ANR0436W
Session session number refused - a WDSF

client is attempting to access the server
using client name client node name (client
platform), associated with a non-WDSF
client.

because a Workstation DataSave Facility (WDSF) client
is attempting to access the server using a node name
associated with a non-WDSF client. When converting
from WDSF, WDSF client programs cannot be used to
access the server with a specific node name once the
non-WDSF client program has been used to access the
server with that node name.
User response: Access the server using a non-WDSF
client program for the node name.
ANR0437W
Session session number for node client

node name (client platform) encountered an
internal server error while checking
license compliance.
Explanation: The server encountered an internal error

in determining if the server is in compliance with
license terms.
System action: The client session is ended.
User response: Use the QUERY LICENSE and QUERY
STATUS commands to determine if the server is in
compliance with license terms. Start an AUDIT
LICENSES process to re-adjust server license
information. When this process completes you may
restart the session. If the problem persists, contact your
service representative.
ANR0439W
Explanation: The server refuses a client backup

operation because the current server configuration is
not in compliance with license terms.
System action: Server operation continues. Clients
may perform any action except backup or archive.
User response: Use the QUERY LICENSE command to
determine the license terms that are no longer in
compliance.
ANR0440W
Session session number archive operation

for client client node name (client platform)
has been denied - Server is not in
compliance with license terms.
Explanation: The server refuses a client archive

operation because the current server configuration is
not in compliance with license terms.
may perform any action except backup or archive.
compliance.
38
Protocol error on session session number

for node client node name (client platform) invalid verb header received.
Explanation: The server detects a protocol error on the

specified session because an invalid verb header has
been received from the client. Verb headers always
precede communication sent to the server from the
client or from the server to the client.
System action: The server ends the client session.
User response: Correct the programming error in the
client program if it has been written by your
installation using WDSF verbs. Otherwise, contact your
ANR0441W

for node client node name (client platform) invalid data length received.

specified session because an invalid verb length has
been received from the client.
ANR0442W
ANR0438W
Session session number backup operation

for client client node name (client platform)
has been denied - Server is not in

for node client node name (client platform) excessively large verb received.

specified session because an invalid verb length has
been received from the client.
ANR0443W ANR0449W
ANR0443W

for node client node name (client platform) invalid field name field found in verb
name verb (offset offset position).

specified session because an invalid field has been
found in a verb sent from the client node.
User response: The compression method used by the

client is no longer supported. In order to use
compression, the client needs to be upgraded to a client
service level that supports the newer compression
method.
ANR0447W

ANR0444W

for node client node name (client platform) out-of-sequence verb (type verb name)
received.

specified session because a verb has been received that
does not adhere to the client-server exchange sequence.
Session session number space

management migration operation for
client client node name (client platform) has
been denied - Server is not in
Explanation: The server refuses a client space

management migration operation because the current
server configuration is not in compliance with license
terms.
may perform any action except backup, archive, or
space-managed file migration.
compliance.

User response: If the client generating the error is not
an API client, contact your service representative. If the
client generating the error is an API client, contact the
owner of the API client. If the client generating the
error is a client that you have created using WDSF
verbs, correct the programming error in your client
program.
ANR0445W

for node client node name (client platform) maximum group transaction size
exceeded.

specified session because the client has attempted to
group more than the maximum database update
operations in a single database transaction.
ANR0446W
Session session number client client node

name compression method unsupported Compression forced OFF. Please obtain
the latest level of the client code.
Explanation: The client is using a compression

method that is no longer supported by the Server.
System action: Server operation continues. The clients
backup operation continues, without compressing the
data.
ANR0448W

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.
User response: Licenses to support space-managed
clients can be obtained from your service provider or
reseller. The REGISTER LICENSE command can be
used with these licenses to enable space management
support.
ANR0449W

client client node name (client platform) is
in violation of server license terms server is not licensed for space
management support.
Explanation: The server warns about a client space

management migration operation because the server is
not licensed to support space-managed clients.
User response: Licenses to support space-managed
clients can be obtained from your service provider or
reseller. The REGISTER LICENSE command can be
used with these licenses to enable space management
support.
39
ANR0450W ANR0455W
ANR0450W
Session session number for server server

name not defined for server to server
communications.

server session because the requesting server name is
not defined in the server database, or the requesting
server definition does not have a SERVERPASSWORD.
User response: Register the requesting server name
with the server before establishing a session, or update
the existing requesting server definition and set a
SERVERPASSWORD. An authorized administrator
must use the DEFINE SERVER or UPDATE SERVER
command to register the requesting server and set the
password.
ANR0453W
Server to server session refused - no

password defined.
Explanation: The server to server session cannot be

initiated because no server password has been defined
for this server.
User response: Define a server password with the SET
SERVERPASSWORD command and retry the
command.
ANR0454E
Session rejected by server server name,

reason: rejection reason.
Explanation: The server has attempted to open a

session with the shown server. The session was rejected
for the indicated reason.
System action: The operation fails.
ANR0451W

name (server platform) refused - invalid
password submitted.

server session because an invalid password has been
submitted during sign-on processing. The server will
continue to deny access attempts by that server until
valid passwords are submitted.
User response: Set the proper passwords. If the
password has been changed on either server, an
authorized administrator can set new passwords by
using the UPDATE SERVER command with the
SERVERPASSWORD parameter.
ANR0452W
Session for server server name refused server name not defined for server to
server communications.

server to server session because a server name is not
defined in the server database, or the server definition
does not have a SERVERPASSWORD. Server to server
communications using the serverpassword requires that
the each server has had a server definition for the other
server.
User response: Register the server names on both
servers before establishing a session, or update the
servers existing server definition and set a
SERVERPASSWORD. An authorized administrator
must use the DEFINE SERVER or UPDATE SERVER
command register the servers and set the passwords.
User response: Check both the servers for any

additional messages that might further describe the
reason the session was rejected. For a reason of
AUTHENTICATION FAILURE, ensure that all
passwords have been set correctly on both servers. The
password for the server (set by SET
SERVERPASSWORD on server X) and the password in
the server definition (set by DEFINE or UPDATE
SERVER X SERVERPASSWORD=) are the same
password. For a reason of VERIFICATION FAILURE,
use the QUERY SERVER command to determine that
the HLADDRESS and LLADDRESS of the target server
are correct. If they are not, correct them with the
UPDATE SERVER command. If they are correct,
resynchronize with the target server by issuing the
UPDATE SERVER FORCESYNC=YES. For a reason of
COMMUNICATION FAILURE ensure that the target
server is available and that TCPIP is available on both
servers. For a reason of NO RESOURCE, ensure that
the receiving server is enabled, has sufficient DB, LOG,
and memory resource to support the source server
session. For a reason of INTERNAL ERROR, use the
messages on the target server to determine the problem
and contact your service representative. Retry the
failing operation.
ANR0455W
Invalid Command command name for

SNMP session.
Explanation: An SNMP administrative session

attempted to run a command which is not an macro
invocation. SNMP administrative sessions are only
allowed to issue macro commands.
User response: Enter commands through the SNMP
administrative interface which are macros defined on
the server.
40
ANR0456W ANR0463W
ANR0456W
Session rejected for server name server

name at High level address Low level
address does not match.
ANR0460W
Open registration failed for session

session number - node name node name
(client platform) already exists.
Explanation: The server name at the address specified

does not match the name in the server definition. The
connection is not established.
Explanation: The server refuses a client session during

open registration because the client has specified a
node name that is already registered on the server.
System action: The server continues.
User response: Ensure the HLADDRESS and

LLADDRESS in the define server command are correct,
and that the servername on the server being contacted
matches the name used in the DEFINE SERVER
command.
User response: The client program user must specify a

different node name for the client in the client options
file.
ANR0457W
Session for server server name refused crossdefine is not allowed on this
server.

server to server session for crossdefine because it is not
allowed on this server. The server will deny any
sessions for crossdefine until crossdefine is allowed on
this server.
User response: An authorized administrator must use
the SET CROSSDEFINE ON command to allow cross
registration of servers.
ANR0458S
Server server name does not support

access by the Storage Agent.
Explanation: The storage agent attempted to contact a

Database Server, but the server contacted was not at
the correct level.
ANR0461W

open registration because the STANDARD policy
domain does not exist. All nodes added to the server
database under open registration are automatically
assigned to the STANDARD policy domain. This policy
domain must be defined and have an active policy set
to support open registration.
User response: If you want to support open
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and
activate a valid policy set in the domain. You can issue
the UPDATE NODE command to move nodes to
different policy domains after the nodes have registered
themselves through open registration.
ANR0462W
System action: The Storage Agent terminates.

User response: Specify a correct Database Server in
the devconfig file for the Storage Agent.
ANR0459W
Signon for administrator administrator

name refused - invalid administrator
name and/or password submitted.
Explanation: The server refuses a request to start an

administrative session because an invalid administrator
name and/or password has been submitted by the user
during sign-on processing. The server will continue to
deny access attempts by this administrator until a valid
password is submitted, or until the administrator is
locked due to maximum number of invalid password
attempts being exceeded.
User response: Enter the proper password. If the
password has been forgotten by the user, an authorized
administrator can assign a new password by using the
UPDATE ADMIN command.

session number for node node name (client
platform) - policy domain STANDARD
does not exist.

platform) - invalid node name.

open registration because the node name specified by
the client is not valid.
User response: Specify a node name in the options file
of the client program that contains valid characters and
does not exceed the maximum length in size. Refer to
Backup-Archive Clients Installation and Users Guide for a
description of the node name restrictions.
ANR0463W

platform) - invalid password.

open registration because the password name specified
by the user is not valid.
User response: Specify a password that uses valid
41
ANR0464W ANR0474W
characters and is less than the maximum length in size.
Refer to Backup-Archive Clients Installation and Users
Guide for a description of the password restrictions.
ANR0464W

platform) - exceeded number of nodes
available under license terms.
Explanation: The server detected an attempt to

register more nodes than allowed by the terms of the
current license.
REGISTER NODE command fails, and the node is not
registered.
compliance.
ANR0465W

platform) - policy domain STANDARD
does not have an ACTIVE policy set.

open registration because the STANDARD policy
domain does not have an active policy set. All nodes
added to the server database under open registration
are automatically assigned to the STANDARD policy
domain. This policy domain must be defined and have
an active policy set to support open registration.
User response: None

ANR0468E
Explanation: An attempt was made to export to an

outdated server. The server on which the import is
performed must be at the same or later level than the
server from which the data was exported.
System action: The export operation ends and server
operation continues.
User response: Export to a server that is at the same
or later level.
ANR0469W
ANR0466E
The SETSTORAGESERVER command

did not complete successfully.
Explanation: The SETSTORAGESERVER command

encountered an error and did not complete successfully.

name (client platform) refused - client is
not configured for archive retention
protection.

because the client is not configured for archive
retention protection.
User response: Either disable archive retention
protection on the server or configure the client for
archive retention protection.
ANR0470W

User response: If you want to support open
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and
activate a valid policy set in the domain. You can issue
the UPDATE NODE command to move nodes to
different policy domains after the nodes have registered
themselves through open registration.
Server-to-server export and import not

allowed with server server name. Export
server is at version export version; import
server is at version import version.

dministrator name refused - administrator
password has expired.
Explanation: The server refuses the specified session

because the administrators password has expired.
User response: Upon receipt of this error condition,
the client program immediately reconnects to the server
specifying a password update session and prompts the
user for a new password. After the user enters a new
password, the client reconnects to the server for normal
operations. Alternatively, an authorized administrator
can update the client password using the UPDATE
ADMIN command.
System action: Storage agent operation terminates.

User response: Please review prior error messages and
take the necessary corrective actions.
ANR0467I
The SETSTORAGESERVER command

Explanation: The SETSTORAGESERVER command

has completed successfully, and the appropriate device
configuration files have been updated.
System action: Storage agent operation terminates.
42
ANR0474W

administrator ID (administrator platform)
was refused because administrators are
not allowed to initiate sessions on the
client port.
Explanation: The server did not start the specified

administrative session because the administrator
connected to the server on the server port that is used
for client sessions, and the option
ADMINONCLIENTPORT is set to NO. When different
port numbers are used for administrative and client
ANR0475W ANR0480W
sessions (controlled by the TCPPORT and
TCPADMINPORT options), and option
ADMINONCLIENTPORT is set to NO, administrative
sessions can be started only on the port used for
administrative sessions (as specified by the
TCPADMINPORT option).
User response: Update the client options file to
specify the port to be used for administrative sessions.
This is typically specified by the TCPADMINPORT
option in both client and server option files.
ANR0475W

name (client platform) refused - node is
not allowed to initiate sessions on
administrative port.
Explanation: The server had refused to start a session

with the specified client node because the node
connected to the server on the servers administrative
port. When different port numbers are used for
administrative and client sessions, client sessions may
be started only on the port used for client sessions.
can only sign on with a platform type of TSMNAS,

all other node types cannot use this platform type.
System action: The session request is refused. The
server operation continues.
User response: Verify that the Id used by a client to
sign on has the proper platform type.
ANR0478W
Explanation: A client has requested a session with the

server. The server is running in a mode in which it
cannot start client sessions.
User response: No response is required. To reduce or
disable the display of this message, you can update the
server options before running in standalone mode with
the COMMMETHOD NONE option. This will allow the
server to run without enabling client connections.
ANR0479W

User response: The client option file should be
updated to specify the port to be used for client
sessions. This is typically specified by TCPPORT option
in both client and server option files. The MVS server
also uses the ICSPORT option.
Session request refused. Server is

running in standalone mode.

name (server platform) terminated connection with server severed.
Explanation: If server A has opened a connection with

server B, server Bs session is ended because the
communications link has been closed by a network
error or by server As program.
System action: Server A continues operation.
ANR0476W

name (client platform) refused - node is
not allowed to initiate sessions.
Explanation: The server had refused to start a session

with the specified client node because the node is not
allowed to initiate session. Only server initiated
sessions are allowed with this client. The SESSIONINIT
parameter of the REGISTER NODE and UPDATE
NODE commands control the ability of a client to
initiate sessions.
User response: An administrator can use the UPDATE
NODE command with the SESSIONINIT parameter to
sepcify that the client may initiate sessions.
Alternatively, sessions can be scheduled with the client
that are stared by the server through server-prompted
scheduling commands ( DEFINE SCHEDULE, DEFINE
ASSOCIATION ).
ANR0477W
Session session number refused - The

client client node name cannot access the
server with a platform type of client
platform.
User response: If server B halts operation or in some

way stops communicating with server A, this message
will be displayed on server A indicating that the
connection was closed suddenly by server B. A network
failure can also cause this message to be displayed. If a
large number of these messages occur simultaneously,
check the network for failure and correct any problems.
ANR0480W

name (client platform) terminated connection with client severed.
Explanation: The specified client session is ended

because the communications link has been closed by a
network error or by the client program.
User response: If a user breaks out of a client
program, this message will be displayed on the server
as the connection is suddenly closed by the client. A
network failure can also cause this message to be
displayed. If a large number of these messages occur
simultaneously, check the network for failure and
correct any problems.
Explanation: A client with a invalid combination of

node type and platform type has requested a session
with the server. For example, a node id of type NAS
43
ANR0481W ANR0486W
ANR0481W

name (client platform) terminated - client
did not respond within commtimeout
seconds seconds.
Explanation: The server ends a client session because

the client has been holding database locks (a
transaction was in progress) and the client has not
responded in the number of seconds specified by the
COMMTIMEOUT parameter in the server options file.
System action: The server rolls back the transaction
that has been in progress and the session is ended.
Server operation continues.
User response: If a large number of these messages
appear, you may want to increment the value specified
for the COMMTIMEOUT value in the server options
file and restart the server. The amount of time that it
takes for a client to respond is dependent upon the
speed and processor load for the client and the network
load.
ANR0482W

name (client platform) terminated - idle for
more than idletimeout minutes minutes.
Explanation: The server ends a client session because

it has been idle for more minutes than specified in the
IDLETIMEOUT parameter in the server options file.
The client program will automatically attempt to
reconnect to the server when necessary.
User response: If the problems persists, increase the
value specified for the IDLETIMEOUT parameter in the
server options file and restart the server. Many times,
the client program is idle while waiting for the user to
choose an action to perform (for example, backup,
archive, restore, or retrieve files). If a user starts the
client program and does not choose an action to
perform, the session will eventually time out. The client
program automatically reconnects to the server when
the user chooses an action that requires server
participation. Note that a large number of idle sessions
can inadvertently prevent other users from connecting
to the server, so care should be used when increasing
the IDLETIMEOUT parameter.
ANR0483W

name (client platform) terminated - forced
by administrator.
Explanation: The server ends a client session in

response to a CANCEL SESSION command issued by
an authorized administrator.
System action: The server rolls back any transactions
in progress for the terminated client session.
44
ANR0484W

name (client platform) terminated protocol violation detected.

because a communications protocol error by the client
has been detected.
User response: Examine the client message to
determine the problem. Correct the programming error
in the client program. If the error cannot be isolated
and resolved, contact your service representative.
If this session is a proxied LAN-Free session for a
storage agent, this error may be the result of a mount
point or volume preemption on the storage agent.
Review the messages logged by the storage agent to
determine if a storage agent action caused this to occur.
ANR0485W

name (client platform) terminated sufficient memory is not available.

available.
ANR0486W

name (client platform) terminated internal error detected.
Explanation: The specified client session is ended by

the server because an internal processing error has been
detected on the server. A programming error may have
occurred in the server program.
System action: The session is ended and server
User response: If this session is a proxied LAN-Free
session for a storage agent, this error may be the result
of a mount point or volume preemption on the storage
agent. Review the messages logged by the storage
agent to determine if a storage agent action caused this
to occur.
If the cause of the error can not be determined after
reviewing the activity log, contact your service
representative.
ANR0487W ANR0492I
ANR0487W

name (client platform) terminated preempted by another operation.
Explanation: The server ends a client session in

response to a cancel request issued by a higher priority
operation that needed the mount point that the client
was using.
System action: The server rolls back any transactions
in progress for the terminated client session.
User response: Reissue the operation. If this message
appears frequently, consider increasing the mountlimit
value for the affected device class.
ANR0488W

name (client platform) terminated transfer rate is less than (transfer rate)
and more than (elapsed time since first data
transfer) minutes have elapsed since first
data transfer.
Explanation: The server is canceling client session

number session number. Depending on the state of the
session, it may take a while for the session to be
canceled. The server ends a client session because it has
been active for more minutes than specified in the
THROUGHPUTTIMETHRESHOLD parameter in the
server options file and the data transfer rate is less than
the amount specified with the
THROUGHPUTDATATHRESHOLD parameter in the
server options file. The client is transferring data to the
server at an abnormally slow rate and may have
become a bottleneck for handling data from other
clients. If the client has caused log records to be
written, it is possible that this client will prevent log
space reclamation.
System action: The session is canceled and server
User response: If a low data transfer rate is not a
problem, the THROUGHPUTTIMETHRESHOLD or
THROUGHPUTDATATHRESHOLD parameters in the
server options file can be set to zero - this will disable
the throughput check. The change can be made without
taking down the server and restarting it by using the
SETOPT THROUGHPUTTIMETHRESHOLD or the
SETOPT THROUGHPUTDATATHRESHOLD
commands. If a low data transfer rate is not expected,
external causes should be investigated. This would
include network problems and problems in accessing
data on the client node. The client program may
automatically reconnect to the server, so this message
may appear on subsequent sessions until the data
transfer problem is resolved. The default server
operation is not to perform a throughput check.
ANR0489W
Session session number refused for client

node name - NAS type nodes are not
supported by a storage agent.
Explanation: The specified client tried to connect to a

storage agent. The storage agent does not support a
node that is defined as TYPE=NAS.
User response: The client should be reconfigured to
not try LAN-free operations. This may be done by
setting UPDATE NODE ENABLELANFREE=NO for the
client.
ANR0490I
Canceling session session number for

node node name (client platform) .
Explanation: The server is canceling client session

number session number. This message is displayed in
response to the CANCEL SESSION command.
Depending on the state of the session, it may take a
while for the session to be canceled.
ANR0491I
No matching session(s) found to cancel.
Explanation: The server cannot find any sessions to

cancel matching the specifications entered in the
CANCEL SESSION command.
User response: Use the QUERY SESSION command to
ensure that the session you wish to cancel is connected.
Reissue the command using the appropriate session
number to cancel the client session.
ANR0492I
All drives in use. Session session number

for node node name (client platform) being
preempted by higher priority operation.
Explanation: When a high priority operation

attempted to find an available drive, all the drives were
being used. To free up a drive for this operation, the
client session identified is being cancelled by the
system.
System action: The lower priority client session is
cancelled to free up a mount point (drive).
User response: When a drive again becomes available,
restart the session that was cancelled. This session was
most likely a backup/archive session and you may just
want to let it restart automatically during its next
scheduled backup window. If this message appears
frequently, you may want to increase the number of
drives available. See the MOUNTLIMIT parameter on
the UPDATE DEVCLASS command.
45
ANR0493I ANR0501W
ANR0493I
Restore session session number canceled.

Explanation: The specified session was canceled with

the CANCEL RESTORE command.
System action: The restore session is canceled and

ANR0499E

ANR0494I
Volume volume name in use. Session

platform) being preempted by higher
priority operation.

attempted to acquire a specific volume, it was being
used. To free the volume for this operation, the client
session identified is being cancelled by the system.
System action: The lower priority client session is
cancelled to free up the volume.
User response: Restart the session that was cancelled,
it will wait until the higher priority operation if
finished with the volume. This cancelled session was
most likely a backup/archive session and you may just
want to let it restart automatically during its next
scheduled backup window.
ANR0495I
Cannot cancel the specified

EXPORT/IMPORT session.
Explanation: The server cannot cancel the session

specified in the CANCEL SESSION command.
User response: Export/Import sessions cannot be
canceled using CANCEL SESSION. The user should
use the CANCEL PROCESS command to terminate the
EXPORT/IMPORT operation.
ANR0496E
Session session number operation for

been denied because verb (type verb
name) is not allowed when archive
retention is active.
The backup server database has reached

the maximum allowed occupancy.
name (client platform) is terminated.
Explanation: The session attempted to store new data

on the backup server, but the database has reached the
maximum allowed occupancy. No new data can be
stored on the backup server until database space is
made available.
System action: The backup server terminates the
session and operation continues.
User response: You can make database space available
for new data to be stored by deleting data you no
longer need. You should also consider reducing the
amount of new data being stored on the backup server.
You may need to acquire additional Express backup
servers to share the load or upgrade to an Enterprise
server.
ANR0500W
Transaction failed for session session

number for node node name (client
platform) - invalid password submitted.
Explanation: The server ends a password update

transaction because the user has not correctly specified
the current password.
User response: Update your password by correctly
specifying the current password. If the current
password has been misplaced, the administrator can
reassign a password for the client by using the
UPDATE NODE or UPDATE ADMIN command.
ANR0501W

platform) - invalid policy binding
specified.
Explanation: The server ends a database update

transaction for the specified session because an invalid
management class has been specified for a file or
directory object.
User response: Do not send the specified operation to

the server when archive retention protection is active.
System action: The specified session is ended and

Explanation: The server refuses the specified client

operation because archive retention protection is active.
ANR0497W
Session request refused from

non-Express client.
Explanation: A non-Express client has requested a

session with the Express server. Only connections from
an Express client will be accepted by an Express server.
46

ANR0502E ANR0521W
ANR0502E

platform) - A storage pool for the target
destination is associated with a device
class that has a Centera device type.

transaction for the specified session because an invalid
management class has been specified. Centera device
types may be used only for archive objects.
User response: Ensure that Centera device types are
associated with device classes that are used only for
archive operations. The Update Copygrp command can
be used to update copy groups associated with space
mamagement and/or backup storage pools so that they
point to valid destinations.

ANR0514I
Session process number closed volume

volume name.
Explanation: The indicated session has finished using

the specified volume.
ANR0515I
Process process number closed volume

volume name.
Explanation: The indicated process has finished using

the specified volume. It is possible that the process
indicated was not the process that opened the volume.
ANR0510I
Session session number opened input

volume volume name.
ANR0520W
Explanation: The indicated session has opened the

specified volume for input processing.
ANR0511I
Session session number opened output

volume volume name.
Explanation: The indicated session has opened the

specified volume for output processing.
ANR0512I
Process process number opened input

volume volume name.
Explanation: The indicated process has opened the

specified volume for input processing. You may or may
not see an associated ANR0515I message for this
process/volume combination, since some volumes are
shared between multiple processes.
ANR0513I
Process process number opened output

volume volume name.
Explanation: The indicated process has opened the

specified volume for output processing. You may not
see an associated ANR0515I message for this
process/volume combination, since some volumes are
shared between multiple processes.

platform) - storage pool pool name is not
defined.
Explanation: The server rolls back a database update

transaction for the specified session because the
destination specified for a management class copy
group specifies the named storage pool, but that
storage pool does not exist.
User response: An administrator with policy authority
over the client policy domain must correct management
class definitions so that copy group destinations refer
to defined storage pools, or the specified storage pool
must be created by an authorized administrator.
ANR0521W

platform) - object excluded by size in
storage pool pool name and all successor
pools.

transaction for the specified session because the size of
a file sent from the client node is larger than that
allowed in the storage pool specified in the clients
management class copy group. No successor storage
pools to the one specified on the copy group can accept
the large file.
User response: If the client is not using compression
to send files to the host, turn compression on for the
client (using the UPDATE NODE command) to try and
resolve the problem. Otherwise, the maximum file size
for one or more of the storage pools in the storage
47
ANR0522W ANR0528W
hierarchy can be increased to accommodate the file. An
authorized administrator can increase the MAXSIZE
parameter by issuing the UPDATE STGPOOL
command.
ANR0522W

platform) - no space available in storage
pool pool name and all successor pools.

transaction for the specified session because the storage
pool specified in the clients management class copy
group does not contain enough free space to hold the
files sent from the client. Successor storage pools to the
one specified on the copy group do not contain enough
free space.
User response: An authorized administrator can issue
the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy. This
action may also involve creating storage space by using
an operating system specific utility.
ANR0523W

platform) - error on output storage
device.

transaction for the specified client because an I/O error
has been encountered by the server in writing to a
device.
User response: Query the activity log to find messages
preceding this one that specify the failing device.
Storage pool volumes can be varied offline (by using
the VARY command), or the server may need to be
halted to correct the hardware problem. After the
problem is corrected, the client should retry the
operation.
ANR0524W

platform) - data transfer interrupted.
Explanation: The database transaction associated with

session session number was aborted because data
transfer to or from data storage was interrupted by an
external event.
User response: Examine the messages issued prior to
this message to determine why the data transfer was
interrupted. Attempt the client operation again if the
problem can be resolved.
48
ANR0525W

platform) - storage media inaccessible.
Explanation: The server ends a transaction for the

specified session because storage volumes are not
available in the storage pools in which the clients files
are to be stored.
System action: The server ends the specified session
and server operation continues.
or more storage pools in the storage hierarchy. The
VARY ONLINE command can be used to vary offline
storage volumes online in the storage hierarchy to
make them available to client nodes for file storage.
ANR0526W

platform) - sufficient recovery log space
is not available.

transaction for the specified session because sufficient
log space is not available on the server.
the DEFINE LOGVOLUME command to add volumes
for use by the log, and can issue the EXTEND LOG
command to extend the size of the log so that the new
volumes are used.
ANR0527W

platform) - sufficient database space is
not available.

database space is not available on the server.
the DEFINE DBVOLUME command to add volumes
for use by the database, and can issue the EXTEND DB
command to extend the size of the database so that the
new volumes are used.
ANR0528W

platform) - thread resource not available.

memory is not available for starting additional
processes on the server.
ANR0529W ANR0534W
ANR0529W

platform) - insufficient memory.

memory is not available on the server.
ANR0530W

platform) - internal server error detected.

transaction for the specified session because an internal
logic error is detected.
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
representative.
ANR0531W

platform) - invalid file space identifier
specified by client.

transaction for the specified session because the file
space identified by the client for the transaction does
not exist.
System action: This action usually occurs when a
client is operating on a file space that is currently being
deleted as a result of an administrative command or
client action. The server ends the specified session and
User response: Use the QUERY PROCESS command
to monitor and wait for any file space deletion
processes to complete, or cancel the process if you do
not want to delete the file space. Try the client action
again after this action has been taken.
ANR0532W
Diagnostic(ID): Transaction transaction ID

was aborted for session session number
for node node name (client platform).
Explanation: An error has been detected during a

transaction commit for the specified session. This
message should be preceded by other messages that
give additional information about the failed transaction.
fails.
User response: Check for additional messages and
eliminate the condition that caused the failed
transaction. If the error cannot be isolated and resolved,
ANR0533W

number - compression method used by
client not supported. Please obtain the
latest level of the client code.
Explanation: The server ends the transaction for the

specified session because the compression method that
is used by the client is no longer supported by the
server.
User response: The client must either backup the data
with compression turned off, or upgrade to a client that
supports the newer compression method. If the client is
a WDSF client, upgrade to a non-WDSF client in order
to use the compression performed by the client.
ANR0534W

platform) - size estimate exceeded and
server is unable to obtain additional
space in storage pool pool name.

transaction for the specified session because the size
estimate provided by the client is too small. The server
has attempted to obtain additional space in the
indicated storage pool, but was unable to do so.
System action: Depending on the cause of the failure,
the client might attempt to retry the transaction. If
possible, data is stored in the next pool in the storage
hierarchy. If this is not possible, the session is ended. If
pool name is a random access storage pool with caching
enabled, it is also possible that additional space can be
made available in this storage pool by eliminating
cached files. When the server allocates space based on
the size estimate provided by the client, it frees space
occupied by cached files if this space is needed to
obtain the estimated space. However, if the server later
determines that the file size estimate was too low, it
attempts to obtain additional space that is not utilized,
but does not delete cached files to do so. If the client
sending the data has the option COMPRESSALWAYS
49
ANR0535W ANR0539W
YES set, it is possible that a file grew during the
compression operation and when the client sent it to
the server it exceeded the space available in storage
pool pool name.
User response: This message may indicate that there
is no additional space in pool name. The following are
possible circumventions:
An authorized administrator can issue the DEFINE
VOLUME command to add storage to this pool.
If the suspected cause of the failure is that pool name is
a DISK storage pool and that space in use by cached
files was not freed, turn off caching for the storage pool
and issue the MOVE DATA command for the volumes
in pool pool name.
If the suspected cause of the failure is that a file grew
in size during compression on the client, another
possible circumvention is to set the
COMPRESSALWAYS option in the client options file to
NO and retry the operation. This may allow the client
to accurately report the file size and possibly avoid the
out of space condition in the storage pool.
ANR0535W

platform) - insufficient mount points
available to satisfy the request.
Explanation: The server was unable to allocate

sufficient mount points to process the transaction.
System action: The operation is ended and server
User response: If necessary, make more mount points
available or validate your device class and library
configuration.
ANR0536W

platform) - downlevel client does not
support format of stored files.
Explanation: A client attempts to perform an

operation involving files that are stored in a format that
is not supported by that client level.
User response: Upgrade the client to a later level.
ANR0537E

platform) - filespace name cannot be
renamed from or to a unicode name.

transaction for the specified session because a file space
was attempted to be renamed to or from unicode.
System action: The server ends the specified
50
transaction and server operation continues.

User response: Do not attempt to rename a unicode
file space to a non-unicode name or a non-unicode file
space to a unicode name.
ANR0538I
A resource waiter has been aborted.
Explanation: The server aborts a resource wait

because of waiting too long for a resource to become
available. This could cause a process or session to fail.
If this causes a process or a session to fail then there
will be other messages at this time indicating which
process or session has failed. Resources are internal
server resources such as locks and synchronization
objects.
System action: The server terminates the resource
with request and server operation continues.
User response: Either a server deadlock situation has
occurred or the resource timeout value is set too low.
Check the setting for the RESOURCETimeout server
option and increase the value. If the problem persists
with a higher timeout then contact your service
representative.
ANR0539W

number for node node name. This node
has exceeded its maximum number of
mount points.
Explanation: The server ends the transaction because

the node requires mount points to store data, and
either the node is not allowed to acquire any mount
points, or the node is already using the maximum
number of mount points allowed for the node. The
maximum number of mount points a node is allowed
to use on the server is controlled by the setting of the
MAXNUMMP parameter on the REGISTER NODE or
User response: If the number of mount points that the
node is allowed to use on the server are already
acquired, reduce the number of client sessions for the
specified node that are running concurrently. For
example, decrease the value of the client option
RESOURCEUTILIZATION. If sufficient mount points
(for example, drives) are available to satisfy the data
store operations, issue the UPDATE NODE command
to increase the value of the MAXNUMMP parameter.
If the node is not allowed to acquire any mount points
(the nodes MAXNUMMP option is set to zero), issue
the UPDATE NODE command to change the value of
the MAXNUMMP parameter.
ANR0540W ANR0547E
ANR0540W
Retrieve or restore failed for session

platform) - data integrity error detected.
Explanation: The server ends a file retrieval operation

for the specified session because an internal database
integrity error has been encountered on the server.
and continues operation.
ANR0541W

platform) - error on input storage device.

interrupted. Attempt the client operation again, if the
problem can be resolved.
ANR0544W

platform) - thread resource not available.
Explanation: The server ends a file retrieval or restore

operation for the specified session because sufficient
Explanation: The server ends a client retrieval or

restore operation for the specified session because an
I/O error has been encountered by the server in
reading from a device.


ANR0545W

preceding this one that specify the device that is failing.
the VARY OFFLINE command), or the server may need
to be shut down by using the HALT command to
correct the hardware problem. After the problem is
corrected, the client may try the operation again.
ANR0542W

platform) - storage media inaccessible.

restore operation for the specified session because a
needed storage pool volume has been varied offline or
the storage pool is unavailable.
User response: Use the VARY ONLINE command to
vary offline storage volumes online in the storage
hierarchy and make them available to client nodes for
file storage. If all volumes are online, check the
ACCESS parameter of the storage pool. If the access
mode is UNAVAILABLE, use the UPDATE STGPOOL
command to update it to READONLY or READWRITE.
ANR0543W

platform) - data transfer interrupted.

session session number was aborted because data
external event.

platform) - insufficient memory.

operation for the specified session because sufficient
ANR0546W

platform) - internal server error detected.

operation for the specified session because an internal
logic error is detected in the server program.
error. Use the QUERY ACTLOG command to view the
representative.
ANR0547E
Invalid data was encountered in the

command processor output stream:
output formatting terminated for the last
command entered.
Explanation: The server console session encounters an

error in formatting output from a command.
51
ANR0548W ANR0553E
System action: The command output is discarded and
User response: Use the server QUERY command to
determine if the command you entered had the desired
affect in the server. Use the QUERY ACTLOG
command to see if a server error condition (like out of
memory) occurred prior to the command. Resolve the
error if it is found. Contact your service representative
if you cannot resolve the error, or if an error is not
found.
ANR0548W

platform) processing file space filespace
filespace id for file file name stored as
storage repository - error detected.

for the specified session because an error has been
encountered on the server. Some common reasons for
the error are:
v The input volume is unavailable
v The storage pool is unavailable
v Data is corrupted on the input volume
v Hardware or media failure has occurred
v Database corruption
ANR0550E
The client operation failed for session

platform) - see previous error messages.
Explanation: The indicated operation has failed. This

message is always preceded by one or more other error
messages which provide more detail about why the
command failed.
User response: Examine the previous error messages
to determine the source of the error. Use the QUERY
ACTLOG command to view the activity log and search
for messages if needed. Correct the problem and try the
command again.
ANR0551E
The client operation failed for session

platform) - lock conflict.
Explanation: An operation that requires the server to

lock a system resource has been initiated. The operation
cannot be executed because the resource is already in
use by another command or process.
System action: The server does not process the
command.

User response: Try the command again at a later time.
User response: Re-try the restore or retrieve operation,

and if the file is also backed up in a copy storage pool,
the operation will attempt to read the file from the
alternate location. If retry of the restore or retrieve
operation continues to fail examine any prior error
messages to determine the source of the error. Use the
QUERY ACTLOG command to view the activity log
and search for messages if needed. Correct the problem
and try the restore or retrieve again. You can also refer
to the Problem Determination Guide for problem
determination hints and information. If retry of the
restore or retrieve operation continues to fail contact
ANR0552E
Client operation failed for session

platform) - destination storage pool
storage pool was skipped.
Explanation: The indicated client operation failed

because the destination storage pool was skipped. A
storage pool may be skipped because it does not have
enough available space, or because it has a MAXSIZE
value that is less than the size of the object to be
inserted.
Explanation: A client attempted to start an additional

no query restore session to increase restore throughput,
but the original restore session was not found.
User response: Ensure that the destination storage

pool is available, has an adequate MAXSIZE setting,
and has adequate space. The MAXSIZE setting may be
changed using the UPDATE STGPOOL command.
Space may be added to the storage pool by checking in
scratch volumes or defining new volumes in the
storage pool. If volumes in the destination storage pool
are offline, use the VARY ONLINE command to vary
them online and make them available for use. Correct
the problem and try the command again.

ANR0553E
User response: Check the status of the original restore.

It may have already completed or been cancelled. The
QUERY SESSION command and the QUERY RESTORE
commands can provide information about existing
sessions and restore sessions which are restartable.
Explanation: The specified administrator does not

have the proper authority necessary to perform this
ANR0549W
52

platform) - no existing restore session
found.
Client operation failed for session

session number - Administrator
administrator name does not have
adequate authority over node node name.
ANR0554E ANR0560E
operation on the specified node.
ANR0557I
System action: The server does not perform the query.

User response: Issue the command from a properly
authorized administrator ID, or contact the system
administrator to have additional authority granted to
the current administrator ID.
ANR0554E
command name: The parameter name

parameter is only valid if the
TOSERVER parameter is specified.
Explanation: The command failed because the

TOSERVER parameter was not specified.
Explanation: An invalid import record was found for

the specified version, copy type and object type. The
object will be skipped, and import processing will
continue.
User response: Issue QUERY ACTLOG to determine
the source of the error.
ANR0558W
System action: The command fails and server

User response: Reissue the command and specify the
TOSERVER parameter. For information on valid values
for the command parameter,refer to the :cit.ADSM
Administrators Reference:ecit. for your particular
platform.
ANR0555E
command name: The parameter name

parameter cannot be specified when the
TOSERVER parameter is specified.
Import command: An invalid export

record (version version, copy type copy
type, object type object type) was found.
Import processing did not create a

proxynode association for nodes
node_id_target and node_id_agent.
Explanation: Import processing did not create a

proxynode association between the two nodes. The
association fails if either of the nodes does not exist on
the server, or if import processing was not allowed to
complete.
System action: The server does not create the
specified proxynode association.

TOSERVER parameter was not specified.
User response: Verify that both nodes were imported

properly and issue the import command again. Or, use
the GRANT PROXYNODE command to manually
create the proxynode association.

ANR0559E
User response: Reissue the command and omit the

TOSERVER parameter. For information on valid values
for the parameter for the command parameter, refer to
the :cit.ADSM Administrators Reference:ecit. for your
particular platform.
ANR0556E
command name: DATES=RELATIVE

parameter value cannot be specified
when merging imported files using the
MERGE=YES parameter value.
Explanation: When importing files and merging them

into existing file spaces, the DATES=RELATIVE
parameter value cannnot be specified.
User response: Reissue the command and omit the
DATES=RELATIVE parameter. For information on valid
values for the parameter for the command, refer to the
:cit.ADSM Administrators Reference:ecit. for your
Too many domains are specified on the

EXPORT NODE command.
Explanation: The maximum length of the domain list

cannot exceed approximately 1400 characters.
System action: The EXPORT command is ended.
User response: If you specified DOMAIN=* on the
command, issue the command again without specifying
the domain to let it default to all domains. If you
specified a domain list, then split up the EXPORT into
multiple export commands to reduce the number of
domains specified on the command.
ANR0560E
Import command: Unable to decrypt

encrypted password or key.
Explanation: The server is not able to decrypt the

password associated with a node or administrator, or
the client encryption key associated with an object
being imported. The password or key was encrypted
with the AES encryption standard, but the server does
not support AES.
System action: The object is not imported.
User response: Rerun the export command, specifying
the ENCryptionstrength=DES option. Or, rerun the
import on a server that supports AES.
53
ANR0561E ANR0569I
ANR0561E
Export command: Process aborted - sign

on to server, target server name, failed.
Explanation: The server export process encountered

an error in establishing a communication session with
the target server.
System action: The export process ends and server
User response: Check the activity log and server
console for messages that indicate a failure or problem
on the server issuing this command and on the target
server. Next, check the server definition, administrator
name, and password on both the server issuing the
command and the server specified. Also, check the
communication connection between the two servers.
And finally, verify that the target server specified is
running. If the problem is not resolved, contact your
ANR0566W

for the specified session because the file has been
deleted from data storage by another process before
retrieval is complete.
User response: Contact your administrator to find out
if DELETE FILESPACE, DELETE VOLUME, or
inventory expiration processes are running; these
processes can delete data storage files during retrieval.
Reissue the restore or retrieve operation and specify a
different file version.
ANR0567W
ANR0564E
Restartable restore request failed for

session session number, restartable restore
session restore session number - sessions
are active from the original restore.
Explanation: A client attempted to restart a restartable

no query restore session; However, sessions from the
original no query restore invocation are still active.
Both the current and restartable restore session
numbers are shown.
System action: The restartable restore request is ended
and server operation continues. The restores
restartability status does not change.
User response: Check the status of the original restore.
The QUERY RESTORE command can be used to show
the status of restartable restores. The restartable restore
session number is the one for which sessions were
found to be running. Sessions may be active on either
the server or a storage agent. Restartable restores may
be cancelled by issuing the CANCEL RESTORE
command, after which the restore may be retried. Once
CANCEL RESTORE is issued for a restore session, it is
not eligible to be restarted.
ANR0565W

platform). The storage volume volume
name is inaccessible.

restore operation for the specified session because a
needed storage pool volume has been varied offline.
User response: Use the VARY ONLINE command to
vary offline storage volumes online, and make them
available to client nodes for file storage.
54

platform) - file was deleted from data
storage during retrieval.
Retrieve or restored failed for session

platform) - insufficient mount points
available to satisfy the request.

sufficient mount points to process the retrieve or
restore operation.
available.
ANR0568W
Session session number for admin admin

name (client platform) terminated connection with client severed.
Explanation: The specified admin session is ended

because the communications link has been closed by a
network error or by the client program.
User response: If a user breaks out of a client
program, this message will be displayed on the server
as the connection is suddenly closed by the client. A
network failure can also cause this message to be
displayed. If a large number of these messages occur
simultaneously, check the network for failure and
correct any problems.
ANR0569I
Object not processed for node name:

type=type, file space=filespace name,
object=object name.
Explanation: An error occurred. The object for node

name, identified by type, file space and object name was
not processed.
System action: Server action is defined by the error
that occurred.
ANR0570E ANR0576E
User response: Issue QUERY ACTLOG to determine
the source of the error.
ANR0570E
Export command: Invalid value for

DURUNITS parameter detected while
exporting administrative schedule
schedule name - default or existing value
is used during import.
Explanation: During processing of command export

command, an invalid value is encountered for the
DURUNITS parameter for administrative schedule
schedule name.
System action: Export processing continues, but the
exported data contains an unknown DURUNITS value
for this schedule. If this data is imported, the server
uses the default or existing DURUNITS value.
User response: Update the DURUNITS value for this
schedule and restart the export command. Alternatively,
the export data with the unknown value can be used,
and the DURUNITS value can be checked and updated
after import processing has been performed.
ANR0571E

PERUNITS parameter detected while

PERUNITS parameter for administrative schedule
schedule name.
exported data will contain an unknown PERUNITS
value for this schedule. If this data is imported, the
server uses the default or existing PERUNITS value.
User response: Update the PERUNITS value for this
use the export data with the unknown value, and check
and update the PERUNITS value after import
processing has been performed.
ANR0572E

DAYOFWEEK parameter detected while

DAYOFWEEK parameter for administrative schedule
schedule name.
exported data contains an unknown DAYOFWEEK
server uses the default or existing DAYOFWEEK value.
User response: Update the DAYOFWEEK value for
this schedule and restart the export command.

Alternatively, use the export data with the unknown
value, and check and update the DAYOFWEEK value
ANR0573I
Export/import command: Processing

administrative schedule schedule name.
Explanation: The background export or import

process to service the command export/import command
is currently processing the schedule definition
information for administrative schedule schedule name.
System action: Export or import processing for the
command continues.
ANR0574E
Import command: Invalid value for

DURUNITS or PERUNITS parameter in
exported data for administrative
schedule schedule name.
Explanation: During preview processing of command

import command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for administrative
System action: Processing of the command continues.
If a later command is issued that causes the data to be
imported, the default or existing values are used for
DURATION, DURUNITS, PERIOD, and PERUNITS.
User response: If the data is imported with a later
command, verify that the correct values for
DURATION, DURUNITS, PERIOD, and PERUNITS are
used for this schedule.
ANR0575E

DAYOFWEEK parameter in exported
data for administrative schedule schedule
name.

schedule name.
imported, the default or existing DAYOFWEEK value is
used.
command, verify that the correct DAYOFWEEK value is
ANR0576E

exported data - administrative schedule
schedule name defined with default
values for DURATION, DURUNITS,
PERIOD, and PERUNITS.
55
ANR0577E ANR0582E
Explanation: During processing of command import
System action: Processing of the command continues,
by using the default values for DURATION,
DURUNITS, PERIOD, and PERUNITS.
by using the existing DAYOFWEEK value for this

schedule.
User response: Verify that the correct DAYOFWEEK
value has been used for this schedule. Update this
value, if necessary.
ANR0580E
User response: Verify that the correct values have

been used for DURATION, DURUNITS, PERIOD, and
PERUNITS. Update these values, if necessary.
ANR0577E

data - administrative schedule schedule
name defined with default DAYOFWEEK
value.

schedule name.
by using the default DAYOFWEEK value for this
schedule.
ANR0578E

exported data - existing values for
DURATION, DURUNITS PERIOD, and
PERUNITS for administrative schedule
schedule name were not updated.

by using the existing values for DURATION,
ANR0579E

data - existing DAYOFWEEK value for
administrative schedule schedule name
was not updated.

schedule name.
56

SPACEMGTECHNIQUE parameter
detected while exporting management
class management class name in domain
domain name, set policy set name - default
or existing value is used during import.

SPACEMGTECHNIQUE parameter for management
class management class name in domain domain name,
policy set policy set name.
exported data contains an unknown
SPACEMGTECHNIQUE value for this management
class. If this data is imported, the default or existing
SPACEMGTECHNIQUE value is used.
User response: Update the SPACEMGTECHNIQUE
value for this copy group and restart the export.
value, and check and update the
SPACEMGTECHNIQUE value after import processing
has been performed.
ANR0581E

MIGREQUIRESBKUP parameter
detected while exporting management
class management class name in domain
domain name, set policy set name - default

MIGREQUIRESBKUP parameter for management class
management class name in domain domain name, policy
set policy set name.
exported data contains an unknown value for this
management class. If this data is imported, the default
or existing MIGREQUIRESBKUP value is used.
User response: Update the MIGREQUIRESBKUP
value for this copy group and restart the export.
value, and check and update the MIGREQUIRESBKUP
value after import processing has been performed.
ANR0582E

SPACEMGTECHNIQUE parameter in
exported data for management class
management class name in domain domain
name, set policy set name.
ANR0583E ANR0588E
class management class name, in policy domain domain
name, policy set policy set name.

management class name, in policy domain domain name,

imported, the default or existing
SPACEMGTECHNIQUE value is used.

If a later command causes the data to be imported, the
default or existing MIGREQUIRESBKUP value is used.
User response: None. If the data is imported with a

later command, verify that the correct
SPACEMGTECHNIQUE value is used for this
management class.

later command, verify that the correct
MIGREQUIRESBKUP value is used for this
management class.
ANR0586E
ANR0583E

exported data - management class
name, set policy set name defined with
default SPACEMGTECHNIQUE value.

by using the default SPACEMGTECHNIQUE value for
this management class.
User response: Verify that the correct
SPACEMGTECHNIQUE value has been used for this
management class. Update this value, if necessary.

management class name, in policy domain domain name,
by using the default MIGREQUIRESBKUP value for
MIGREQUIRESBKUP value has been used for this
ANR0587E
ANR0584E

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

by using the existing SPACEMGTECHNIQUE value for
SPACEMGTECHNIQUE value has been used for this
ANR0585E

MIGREQUIRESBKUP parameter in
exported data for management class
name, set policy set name.

exported data - management class
name, set policy set name defined with
default MIGREQUIRESBKUP value.

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

MIGREQUIRESBKUP parameter.
by using the existing MIGREQUIRESBKUP value for
MIGREQUIRESBKUP parameter has been used for this
ANR0588E
Import command: Server is down-level

compared to export data version version
number.
Explanation: An attempt is made to import data to a

down-level server. The server on which the import is
performed must be at the same or later level than the
server from which the data was exported.
57
ANR0589E ANR0596W
System action: The import process ends and server
User response: Import to a server that is at the same
or later level than the server from which the export
was performed.
User response: Reissue the command and specify a

valid TOC parameter. For information on valid values
for the TOC parameter for the command, refer to the
Administrators Reference for your particular platform.
ANR0593E
ANR0589E
Import command: Preview processing

terminated abnormally - server is
down-level.
Explanation: Processing for the command import

command in preview mode ends when it is determined
that the server is down-level compared to the export
data.
System action: Import processing ends and server
was performed.
Explanation: The value (parameter value) specified for

the NOSPAN parameter in command export/import
command is not a valid value for this parameter.
valid NOSPAN parameter. For information on valid
values for the NOSPAN parameter for the command,
refer to the Administrators Reference for your particular
platform.
ANR0594E
ANR0590E
Import command: Processing terminated

abnormally - server is down-level.

command ends when it is determined that the server is
down-level compared to the export data.
was performed.
ANR0591E
Export/import command: Invalid value for

FILELIST parameter - parameter value.

the FILELIST parameter in command export/import
valid FILELIST parameter. For information on valid
values for the FILELIST parameter for the command,
platform.
ANR0592E

table of contents parameter - parameter
value.

the table of contents (TOC) parameter in command
export/import command is not a valid value for this
parameter.
58

NOSPAN parameter - parameter value.
device class: NOSPAN parameter can only

be used with a 3590 device class.
Explanation: The device class specified must be a 3590

device class when NOSPAN is set to True.
valid NOSPAN/Device Class parameter. For
information on valid values for the NOSPAN parameter
for the command, refer to the Administrators Reference
for your particular platform.
ANR0595W
The server deleted object count objects

that were part of incomplete groups.
Explanation: After importing data that was exported

from another server, the server deletes any objects that
are part of incomplete groups. Incomplete groups may
be a result of importing from media written by an
export operation that failed. Incomplete groups may
also be a result of a failed import operation.
User response: Ensure that the export and import
operations run to completion. If any errors are
observed, correct them and re-run the export or import
or both, as needed.
ANR0596W
Space-managed object object name for

client node node name, filespace filespace
name already exists on the server - it will
be skipped.
Explanation: While attempting to import a

spaced-managed object, the server discovers that the
object already exists. The space-managed object is
skipped.
ANR0597W ANR0604I
ANR0597W
IMPORT: Space management attributes

in management class management class
name for domain domain name is not
defined - default management class will
be used.
Explanation: During import processing, the server

finds that the space management attributes for a
space-managed file being imported does not exist in
the active policy set for the domain to which the node
is assigned.
System action: The default management class for the
nodes policy domain is bound to the space-managed
file and import processing continues.
User response: If you want to define the missing
management class, an authorized administrator may
cancel the import operation, define the missing space
management attributes or management class for the
domain, and process the import operation again.
ANR0598W
IMPORT: Space management attributes

not found for default management class
in domain domain name - space managed
files bound to management class
management class name in this domain
cannot be imported.

finds that a management class bound to a
space-managed file being imported does not exist in
the active policy set for the domain to which the node
is assigned. When trying to rebind the space-managed
file to the default management class for the domain,
the server finds that the space-managed attributes are
not defined for the default management class.
System action: The file is not imported; import
processing continues.
User response: If you want to define the missing copy
group, an authorized administrator may cancel the
import operation, define the missing space
management attributes or management class for the
domain, and process the import operation again.
ANR0599E
Export/import command: Invalid volume

name volume name specified for device
class device class name.
Explanation: One of the volume names specified in

the VOLUMENAMES parameter for an import or
export command is not a valid volume name for the
device class specified in the DEVCLASS parameter.
System action: The export or import command fails.
User response: Specify volume names in the
VOLUMENAMES parameter that are valid for the
device class specified in the DEVCLASS parameter.
ANR0600I
Export command: No matching policy

domains found for exporting.
Explanation: The background export process does not

find any policy domains that match the specification
entered in the export command.
System action: The export process continues and no
policy domains are exported from the server.
ANR0601I
Export command: No policy sets found in

policy domain domain name for
exporting.

find any policy sets defined in domains matching
domain name.
policy sets are exported from the domain.
ANR0602I
Export command: No management classes

were found in policy domain domain
name for exporting.

find any management classes defined in policy
domains matching domain name.
management classes are exported from the domain.
ANR0603I
Export command: No copy groups were

found in policy domain domain name for
exporting.

find any copy groups defined in policy domains
matching domain name.
copy groups are exported from the domain.
ANR0604I
Export command: No schedules were

found in policy domain domain name for
exporting.

find any schedules defined for policy domains
matching domain name.
schedules are exported for the domain.
59
ANR0605I ANR0614I
ANR0605I
Export command: No schedule

associations were found in policy
domain domain name for exporting.

find any schedule node associations defined for policy
domains matching domain name.
schedule associations are exported for the domain.
ANR0606I
Export command: No node definitions

were found for exporting.

find any node definitions to export as specified in the
command export command.
System action: The export process continues.
ANR0607I
Export command: No administrator

definitions were found for exporting.

find any administrator definitions to export as specified
in the command export command.
ANR0610I
Explanation: A background process has started to

service the command command entered by administrator
administrator name. The background process is defined
as process process ID.
User response: To query the progress of the
background process, use the QUERY PROCESS
command. To cancel the background process, use the
CANCEL PROCESS command. Use the process ID
number to specify this specific process.
ANR0611I
ANR0608I
Export command: No file spaces were

found for exporting.

find any file space definitions to export as specified in
the command export command.
Command started by administrator name as

process process ID has ended.
Explanation: The background process to service the

command command by administrator administrator name
has completed processing.
System action: The specified process ends, and server
ANR0612I


process process ID.
Import command: Reading EXPORT

SERVER data from server server name
exported export date export time.
Explanation: The background import process to

service the command import command is importing
information exported from server server name with the
EXPORT SERVER command on export date at export
time.
System action: Import processing continues.

ANR0609I
Command started as process process ID.
Explanation: A background process has been started

to service the command command. The background
process is defined as process process ID.
ANR0613I

POLICY data from server server name

EXPORT POLICY command on export date at export
time.
ANR0614I

ADMIN data from server server name

60
ANR0615I ANR0622I
EXPORT ADMIN command on export date at export
time.
number of bytes copied, are displayed on the server

console following this message.

ANR0619I
ANR0615I

NODE data from server server name

EXPORT NODE command on export date at export time.
ANR0616I
Export/import command: Preview

processing completed successfully.

in preview (Preview=Yes) mode has completed
successfully.
command completes. Statistics on the projected number
and type of objects moved, together with the projected
total number of bytes copied, are displayed on the
server console following this message.
ANR0617I

completed with status status.

has completed with status status. If the status is
INCOMPLETE, some files have been skipped due to
errors reading or writing the file.
command completes. Statistics on the number and type
of objects moved, together with the total number of
bytes copied, are displayed on the server console
following this message. A summary of the number of
files that were skipped is also displayed.
Command: Processing canceled before

completion.

command command has been canceled with the
System action: Processing for the command command
ends. Statistics on the number and type of objects
moved, together with the total number of bytes copied,
are displayed on the server console following this
message.
ANR0620I
Export/import command: Copied number

domain(s).

copies number policy domain definitions from the
server database to export media or from export media
into the server database. Data is not actually moved if
Preview=Yes is specified in the command export/import
command.
command completes. Server operation continues.
ANR0621I

policy sets.

copies number policy set definitions from the server
database to export media or from export media into the
server database. Data is not actually moved if
command.

ANR0622I
ANR0618I

processing canceled before completion.

in preview (Preview=Yes) mode has been canceled with
the CANCEL PROCESS command.
command ends. Statistics on the projected number and
type of objects moved, together with the projected total

management classes.

copies number management class definitions from the
into the server database. Data is not moved if
command.
61
ANR0623I ANR0630I

ANR0627I
ANR0623I

copy groups.

copies number copy group definitions from either the
command.
ANR0624I

schedules.

copies number schedule definitions from either the
command.
ANR0625I

administrators.

copies number administrator definitions from either the
command.
ANR0626I

node definitions.

copies number client node definitions from the server
database to export media or from export media into the
server database. Data is not moved if Preview=Yes is
specified in the command export/import command.
62
Export/import command: Copied filespace

number file spaces archive number archive
files, backup number backup files, and
spacemg number space managed files.

copies filespace number client file space definitions,
archive number archive file copies, backup number backup
file copies, and spacemg number space-managed files
from either the server database to export media or from
import media into the server database. Data is not
actually moved if Preview=Yes is specified in the
command export/import command.
ANR0629I

bytes of data.

copies number bytes of data from the server database
and data storage to the export media or from the
export media to the server database and data storage.
Data is not moved if Preview=Yes is specified in the
command export/import command. This figure can be
used during export preview processing to estimate the
number of removable media volumes needed to hold
the exported information from the server.
ANR0630I

kilobytes of data.

copies number kilobytes of data from the server
database and data storage to the export media or from
the export media to the server database and data
storage. This figure can be used during export preview
processing to estimate the number of removable media
volumes needed to hold the exported information from
the server.
ANR0631I ANR0637I
ANR0631I

megabytes of data.

copies number megabytes of data from the server
the server.
ANR0632I

gigabytes of data.

copies number gigabytes of data from the server
the server.
ANR0633I

terabytes of data.

copies number terabytes of data from the server
the server.
ANR0634I
Export/import command: Detected number

errors.

detects number errors while copying information from
the server database and data storage to the export
media or from the export media to the server database
and data storage.

prior to this message to view the error. Use the QUERY
for messages.
ANR0635I
Export/import command: Processing node

node name in domain domain name.

is currently processing the client node definition
information for node node name. The node will be
imported to domain domain name.
command continues.
ANR0636I
Import command: Processing file space

filespace name for node node name as file
space new filespace name.

service the command import command is currently
processing the client file space definition information
for file space filespace name belonging to client node
node name. The file space is imported under the name
new filespace name. During import processing, file spaces
defined for clients are not replaced, and file copy
information in the file spaces are imported to new file
space names so that client file copies are not mixed
with existing definitions. Import processing can then
create file spaces with names generated by the import
processor for client nodes that existed prior to the
import operation.
System action: Import processing for the command
continues.
User response: None; however, clients may want to
examine the contents of the file space with the name
new filespace name so that they know where certain file
copies are kept.
ANR0637I
Export/import command: Processing file

space filespace name for node node name
fsId filespace id .

is currently processing client node file space
information for file space filespace name belonging to
client node node name.
command continues.
63
ANR0638I ANR0645I
ANR0638I

administrator administrator name.

is currently processing the administrator definition
information for administrator administrator name.
command continues.
definition information for management class class name

belonging to policy set set name in policy domain
domain name.
command continues.
ANR0643I

ANR0639I

domain domain name.

is currently processing the policy domain definition
information for domain domain name.
command continues.

archive copy group in domain domain
name, set set name, management class
class name.
Explanation: The background export process to

service the command export/import command is currently
processing the archive copy group definition
information for management class class name belonging
to policy set set name in policy domain domain name.
System action: Export processing for the command
continues.

ANR0644I
ANR0640I
Export/import command: Processing policy

set set name in policy domain domain
name.

is currently processing the policy set definition
information for policy set set name belonging to policy
domain domain name.
command continues.
ANR0641I

management class class name in domain
domain name, set set name.

is currently processing the management class definition
information for management class class name belonging
to policy set set name in policy domain domain name.
command continues.
ANR0642I

backup copy group in domain domain
class name.

is currently processing the backup copy group
64
Export command: Processing copy group

of unknown type in domain domain
class name.

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

schedule schedule name in domain domain
name.

is currently processing the schedule definition
information for schedule schedule name belonging to
policy domain domain name.
command continues.
ANR0646I ANR0652W
ANR0646I
Export/import command: message
ANR0650W

has received the message message from the server.
command continues, but errors may have been
encountered.
User response: Examine the documentation for the
message message and resolve the problem reported.
ANR0647I
Cancel in progress
Explanation: The export or import operation has been

canceled and will end when resources have been freed
for the background process. This message may be
displayed in response to a QUERY PROCESS command
for an export or import operation.
ANR0648I

ANR0649I

finds that a management class or copy group bound to
an archive file being imported does not exist in the
active policy set for the domain to which the node is
assigned.
nodes policy domain is bound to the archive file and
import processing continues.
cancel the import operation, define the missing
management class or copy group for the domain, and
process the import operation again.
ANR0651W
Have copied the following:
Explanation: The export or import operation has

copied the number and types of objects displayed. This
message may be displayed in response to a QUERY
PROCESS command for an export or import operation.
Import command: Domain domain name

does not exist - the system will attempt
to import node node name to domain
STANDARD.

processing client node node name. This node was
assigned to domain domain name at the time of export.
However, domain domain name does not exist on the
server to which the import is being performed.
System action: Import processing continues, but node
node name will be assigned to domain STANDARD
during import unless one of the following conditions
exist:
v Preview=Yes
v Node node name is already registered and
Replacedefs=No
v Domain STANDARD does not exist
User response: If Preview=Yes, consider defining
domain domain name before nodes are actually
imported. Otherwise, domain domain name can be
created after the node is imported and the UPDATE
NODE command can be used to assign the node to
domain domain name.
IMPORT: Archive copygroup copy group

name in management class management
class name for domain domain name is not
defined, default management class will
be used.
IMPORT: Backup copygroup copy group

class name for domain domain name is not
defined, default management class will
be used.

a backup file being imported does not exist in the
assigned.
nodes policy domain is bound to the backup file copy
and import processing continues.
cancel the import operation, define the missing
management class or copy group for the domain, and
process the import operation again.
ANR0652W
IMPORT: Archive copygroup not found

for default management class in domain
domain name - archive files bound to
management class management class name
in this domain cannot be imported.

an archive file being imported does not exist in the
assigned. When trying to rebind the archive file to the
default management class for the domain, the server
finds that an archive copy group is not defined for the
default management class.
65
ANR0653W ANR0658W
import operation, define the missing management class
or copy group for the domain, and process the import
operation again.
ANR0653W
IMPORT: Backup copygroup not found

for default management class in domain
domain name - backup files bound to
in this domain cannot be imported.

a backup file being imported does not exist in the
assigned. When trying to rebind the backup file to the
default management class for the domain, the server
finds that a backup copy group is not defined for the
default management class.
import operation, define the missing management class
or copy group for the domain, and process the import
operation again.
ANR0654I
Restartable export command with export

identifier exportID started as process
process ID.

service the command command. The background
background server-to-server export process, issue the
QUERY PROCESS or QUERY EXPORT command. To
suspend the process, issue the SUSPEND EXPORT
command. To cancel the background process, issue the
ANR0655W
Command: Retrieve or restore failed - file

was deleted from data storage during
retrieval.

for the specified command because the file has been
System action: The server ends the command and
Reissue the command after these processes have been
completed or canceled.
66
ANR0656W
Export/import command: Skipped archive

number archive files, backup number
backup files, and spacemg number space
managed files.

skipped archive number archive file copies, backup
number backup file copies, and spacemg number
space-managed files from either the server database to
export media or from import media into the server
database. Data is not actually moved if Preview=Yes is
User response: Check previous messages for the
names of the files that were not exported or imported,
and problem determination information.
ANR0657W
Export command: Invalid authorization

rule type rule type encountered for file
space filespace name fsId filespace id in
node node name - both backup and
archive will be assumed during import.

encounters an invalid file space authorization rule type
for the indicated file space and node.
User response: After import processing is completed,
ask the user of node node name to query the access rules
and ensure that they are specified as desired. The user
should correct any rules that grant access to objects that
the user does not want others to access.
ANR0658W
Export command: The password for

administrator administrator name could
not be obtained. The value password
value will be assumed: The system
administrator may wish to change this
password after importing administrator
administrator name.

command, the export processor cannot obtain the
password for administrator administrator name. The
value password value is assigned as the password for the
administrator on the export media.
User response: After the administrative definition has
been imported to another server, an authorized
administrator should use the UPDATE ADMIN
command to set a password for the administrator
administrator name.
ANR0659W ANR0665W
ANR0659W
Export command: The password for node

node name could not be obtained. The
value password value will be assumed:
The system administrator may wish to
change this password after importing
node node name.

command, the export processor cannot obtain the
password for client node node name. The value password
value is assigned as the password for the client node on
the export media.
User response: After the client node definition has
been imported to another server, an authorized
administrator should use the UPDATE NODE
command to set a password for the node node name.
ANR0660E
Command: Insufficient memory available

in accessing data storage.
Explanation: The server encounters a memory

shortage in accessing data storage during command
command operation.
System action: The command command operation ends
ANR0661E
Command: Internal error encountered in

accessing data storage.
Explanation: The server encounters an internal error

in accessing data storage while processing command
command operation.
System action: The command command operation is
ended and server operation continues.
User response: Use the QUERY ACTLOG command to
examine messages prior to this error to determine the
cause of the data storage failure. If the failure can be
found and resolved, reissue the command command
operation. If the failure cannot be found, contact your
service representative for assistance in resolving the
problem.
ANR0662E
Command: Output error encountered in

Explanation: The command command operation ends

because an error has been encountered by the server in
writing to a device. Possible reasons include:

preceding this one to determine the cause of the error.
After the problem is corrected, the command can be
retried.
ANR0663E
Command: Data transfer was interrupted


command command operation failed because data
external event.
interrupted. Reissue the command command after the
problem is resolved.
ANR0664E
Export/import command: Media not

accessible in accessing data storage.
Explanation: The server ends a transaction for an

export or import operation because storage volumes are
not available in the storage pools in which the client
files are to be stored.
System action: The server ends the export or import
operation and server operation continues.
make them available for file storage.
ANR0665W
Import command: Transaction failed storage pool pool name is not defined.
Explanation: The server rolls back a database update

transaction for an import operation because the
destination specified for a management class copy
group specifies the named storage pool, but that
storage pool does not exist.
System action: The import operation is ended and
User response: An administrator with policy authority
over the client policy domain must correct management
class definitions so that copy group destinations refer
to defined storage pools, or the specified storage pool
must be created by an authorized administrator.
v I/O error writing to a device

v No storage space.
v Incompatible storage pool data format.
67
ANR0666W ANR0672W
ANR0666W
Import command: Transaction failed object excluded by size in storage pool

pool name and all successor pools.

transaction for an import operation because the size of
an imported file is larger than that allowed in the
storage pool specified in the bound management class
copy group for the file. No successor storage pools to
the one specified on the copy group can accept the
large file.
User response: The maximum file size for one or more
of the storage pools in the storage hierarchy can be
increased to accommodate the file. An authorized
administrator can increase the MAXSIZE parameter by
issuing the UPDATE STGPOOL command.
Alternatively, the appropriate copygroup definition can
be updated so that a different destination storage pool
is specified.
ANR0667W
Import command: Transaction failed - no

space available in storage pool pool name
and all successor pools.
Explanation: The server ends an import operation

because the storage pool specified in a management
class copy group does not contain enough free space to
hold the files being imported. Successor storage pools
to the one specified on the copy group do not contain
enough free space.
ANR0669W

an export or import operation failed because data
external event.
System action: The export or import operation is
interrupted. Attempt the export/import operation again
after problem is resolved.
ANR0670W
ANR0668W
Export/import command: Transaction failed

- error on output storage device.

- storage media inaccessible.

export or import operation because storage volumes are
not available in the storage pools in which the client
files are to be stored.
ANR0671W

or more storage pools in the storage hierarchy.

- data transfer interrupted.

- sufficient recovery log space is not
available.

transaction for an export or import operation because
sufficient log space is not available on the server.
Explanation: The server ends an export or import

operation for the specified session because an I/O error
has been encountered by the server in writing to a
device.

for use by the log, and the EXTEND LOG command to
extend the size of the log so that the new volumes are
used.

ANR0672W

to be shut down by using the HALT command to
correct the hardware problem. After the problem is
corrected, the client may be able to try the operation
again.

- sufficient database space is not
available.

transaction for an export or import operation because
sufficient database space is not available on the server.
68
ANR0673W ANR0681E
for use by the database, and the EXTEND DB
volumes are used.
ANR0673W
Export/import command: Data storage

retrieve or restore failed - error detected.
Explanation: The server ends an export or import

operation because an error has been encountered on the
server. Some common reasons for the error are:
ANR0676E
EXPORT/IMPORT: Invalid
Communications Buffer State in SEND.
Explanation: The server export/import process

encounters a communications error in transferring
information to or from the server.
System action: The export or import process ends and

ANR0677E

operation and continues operation.
User response: Examine any prior error messages to
determine the source of the error. Use the QUERY
restore or retrieve again. You can also refer to the
Problem Determination Guide for problem determination
hints and information. If retry of the operation
continues to fail contact your service representative.
ANR0674W
Export command: Retrieve failed - error

on input storage device.
Explanation: The server ends an export operation for

the specified session because an I/O error has been
encountered by the server in reading from a device.
The object for which the I/O was issued is reported in
a later message.
System action: Export processing skips this file, and
to be shut down with the HALT command to correct
the hardware problem.

encounters a communications error in transferring
ANR0678E
EXPORT/IMPORT: Error starting the

Export/Import Session.
Explanation: The server export/import process is not

able to start the session to export information from the
server or import information into the server.
EXPORT/IMPORT: Communications
Failure in Sending verb type verb.

encounters a communications error in using the verb
type verb to transfer information to or from the server.
ANR0679E
Failure in Receiving verb type verb.

type verb to transfer information to or from the server.
ANR0681E
ANR0675E
EXPORT/IMPORT: Invalid
Communications Buffer State in
RECEIVE.
EXPORT/IMPORT: Authentication
Failure.

encounters an authentication error in transferring

69
ANR0682E ANR0690E
ANR0682E
Failure in Sending verb type verb
(command).
ANR0687E
Export/import command: Transaction

failure - could not commit database
transaction.

type verb to issue command command.
Explanation: During processing of command

export/import command, a database transaction cannot be
committed to the server database.

System action: Processing of the command ends.

ANR0683E
EXPORT/IMPORT: Receive Buffer

overflow.

encounters an overflow error in transferring

representative.
ANR0688E

failure - commit called when no
transaction started.

started in the server database.
ANR0684E
failure: bad verb received (verb type).
Explanation: The server encounters an invalid

communications verb during export or import
processing and is not able to continue processing.
ANR0685E

failure - could not start database
transaction.

started in the server database.
System action: Processing of the command terminates.
representative.
70
ANR0689W
EXPORT/IMPORT: Internal error:

Invalid table output handle detected.

encounters an internal error in transferring information
to or from the server.
ANR0686E

representative.
Import command: Client platform type

(platform type) for imported node node
name conflicts with an existing node
with the same name - the node will not
be imported.

encounters an imported node definition that has the
same name as an existing node, but has a different
client platform type (for example, OS/2 or AIX).
Because file data may not be compatible across
different client platforms, the node is not imported.
System action: Import processing continues, and the
named node is skipped by import processing.
User response: If you want to import the named
node, cancel the import process, rename the existing
node to a new name by using the RENAME NODE
command, and run the import again. After you have
imported the node, use the RENAME NODE command
to set the node names as you desire.
ANR0690E

failure - server aborted the transaction
(abort code).

ANR0691E ANR0697E
committed in the server database. The reason code abort
code is returned.
representative.
ANR0691E
Export command: Error abort code writing

export data.

command, an input/output error occurs when writing
the exported information to the export media.
ANR0694E

command, an invalid record type is detected when
reading the exported information from the export
media.
representative.
ANR0695E

representative.
ANR0692E
Command: Out of space on sequential

media, scratch media could not be
mounted.
Explanation: During command command processing,

the process encounters an out-of-space condition
writing to the sequential media. Command command
ends when there is no more space on the sequential
media for storing data and SCRATCH=NO has been
specified on command command.
System action: Command command processing ends.
Server processing continues.
User response: Reissue the command and specify
SCRATCH=YES or specify additional volume names on
the command.
ANR0693E
Import command: Error abort code reading

export data.

command, an input/output error occurs when reading
the exported information from the export media.
representative.
Import command: Invalid record format

(format code) detected on import.
Export command: Unexpected error error

code encountered in receiving table
output data.

command, an unexpected error is detected.
representative.
ANR0696E
Export command: Output table error

encountered - 0 columns reported in the
table.

representative.
ANR0697E
Export command: Output table error

encountered - not positioned to the first
column in the table.

representative.
71
ANR0698E ANR0708E
ANR0698E

FILEDATA parameter - parameter value.

the FILEDATA parameter in command export/import
valid FILEDATA parameter. For information on valid
values for the FILEDATA parameter for the command,
platform.
ANR0699E
Export/import command: Device class

DISK cannot be specified for this
command.
Explanation: The DEVCLASS value DISK cannot be

specified for the command export/import command.
valid device class. Issue the QUERY DEVCLASS
command for a list of valid device classes for the
server.
ANR0700E

PREVIEW parameter - parameter value.

the PREVIEW parameter in command export/import
valid PREVIEW parameter. For information on valid
values for the PREVIEW parameter for the command,
platform.
ANR0701E

SCRATCH parameter - parameter value.
ANR0705E
Export command: The VOLUMENAMES

parameter must be specified when
SCRATCH=NO is specified.
Explanation: The SCRATCH parameter is specified as

NO for the command export command but the
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES
parameter must be specified to indicate the volumes
that can be used for the command.
valid VOLUMENAMES parameter. For information on
valid parameter values for the command, refer to the
ANR0706E
Export command: A device class must be

specified unless PREVIEW=YES is
specified.
Explanation: The DEVCLASS parameter is not

specified in the command export command. Unless
PREVIEW=YES is specified, a DEVCLASS value must
be specified.
server.
ANR0707E
Export command: The FILESPACE

parameter cannot be specified.
Explanation: The FILESPACE parameter is specified

for the command export command, but the FILEDATA
parameter is specified as NONE, or is not specified and
defaults to NONE. File spaces are only copied if the
FILEDATA parameter is specified with a value other
than NONE.

the SCRATCH parameter in command export/import

parameter values for the command, refer to the

ANR0708E

valid SCRATCH parameter. For information on valid
values for the SCRATCH parameter for the command,
platform.
72
Import command: The FILESPACE

parameter cannot be specified unless the
FILEDATA parameter specifies that files
should be imported.
Explanation: The FILESPACE parameter is specified

for the command import command, but the FILEDATA
parameter is specified as NONE, or is not specified and
defaults to NONE. File spaces are only copied if the
ANR0709E ANR0716E
FILEDATA parameter is specified with a value other
than NONE.



valid DATES parameter. For information on valid
values for the DATES parameter for the command,
platform.

parameter values for the command, refer to the
ANR0713E
ANR0709E
Command: No matching nodes registered

in the specified domains.
Explanation: The DOMAIN parameter has been

specified for this command, but no nodes matching the
node name specification are found in the domains
specified.
valid combination of node and domain names. Use the
QUERY NODE command to view the names of nodes
in the domains that you are interested in exporting.
ANR0710E
Command: Unable to start background

process.
Explanation: The server command processor is not

able to start a background process to perform the
command command.
System action: The command process ends and server
ANR0711E
Import command: Unable to start import

process.
Explanation: The server import command processor is

not able to start a background process to perform the
import operation.
ANR0712E

DATES parameter - parameter value.

the DATES parameter in command import command is
not a valid value for this parameter.

REPLACEDEFS parameter - parameter
value.

the REPLACEDEFS parameter in command import
valid REPLACEDEFS parameter. For information on
valid values for the REPLACEDEFS parameter for the
command, refer to the Administrators Reference for your
ANR0714E
Import command: The EXTFILE device

class cannot be specified when the
VOLUMENAMES parameter is
specified.
Explanation: An invalid combination of parameters

has been entered for command import command. The
EXTFILE device class cannot be used in combination
with the VOLUMENAMES parameter.
User response: Reissue the command with the correct
syntax.
ANR0715E
Import command: A device class must be

specified.
Explanation: The command import command has been

specified, but does not include specification of the
DEVCLASS parameter. The DEVCLASS parameter
must be specified for this command.
valid device class. For a list of valid device classes for
the server, issue the QUERY DEVCLASS command.
ANR0716E
Import command: Invalid export data

detected.
Explanation: The command import command

encounters invalid data on the export media while
trying to import server information.
73
ANR0717E ANR0723E
User response: Ensure that the mounted export tapes
are in the correct order (mounted in the same order as
they were mounted during export). Reissue the
command, and mount the tapes in the correct order. If
the VOLUMENAMES parameter has been specified,
make sure that the volume names in the command are
specified in the correct order.
ANR0717E

processing terminated abnormally communications send or receive failed.
Explanation: Processing for the command export/import

command in preview mode has been terminated when
an internal communications error is encountered in the
server.
System action: Export/import processing is ended
representative.
ANR0718E

terminated abnormally communications send or receive failed.

command ends when an internal communications error
is encountered in the server.
representative.
ANR0719E

processing terminated abnormally insufficient memory.

command in preview mode is ended because sufficient
74
ANR0720E
command: Processing terminated

abnormally - insufficient memory.
Explanation: Processing for the command ends

because sufficient memory is not available on the
server.
System action: Command processing is ended and
ANR0721E

processing terminated abnormally unexpected verb received from server.

command in preview mode ends when an internal
communications error is encountered in the server.
System action: Export/import processing ends and
representative.
ANR0722E

terminated abnormally - unexpected
verb received from server.

command ends when an internal communications error
representative.
ANR0723E

processing terminated abnormally transaction failure.

command in preview mode ends when a database
transaction error is encountered in the server.
ANR0724E ANR0730E
representative.
ANR0724E

terminated abnormally - transaction
failure.

command ends when a database transaction error is
encountered in the server.
representative.
ANR0725E

processing terminated abnormally authentication failure.

command in preview mode ends when an authentication
error is encountered in the server.
representative.
ANR0726E

terminated abnormally - authentication
failure.

command ends when an authentication error is
representative.
ANR0727E

processing terminated abnormally internal error.

command in preview mode ends when an internal error
representative.
ANR0728E

terminated abnormally - internal error.

command ends when an internal error is encountered in
the server.
representative.
ANR0729E
Import command: Syntax error from

command server command.
Explanation: During processing of the command

import command, an internal syntax error is encountered
in the server.
System action: Import processing continues, but the
indicated command will have no effect.
activity log and search for messages. After import
processing is complete, it may be necessary to issue
additional commands manually to obtain the necessary
definitions.
ANR0730E
Import command: Internal error from

command server command.

command ends when an internal command error is
75
ANR0731E ANR0738E
representative.
ANR0731E

COMPRESSION parameter in exported
data for node node name.

COMPRESSION parameter for node node name.
default or existing COMPRESSION value is used.
later command, verify that the correct COMPRESSION
value is used for this node.
ANR0732E

ARCHDELETE parameter in exported

ARCHDELETE parameter for node node name.
default or existing ARCHDELETE value is used.
later command, verify that the correct ARCHDELETE
ANR0733E

BACKDELETE parameter in exported

BACKDELETE parameter for node node name.
default or existing BACKDELETE value is used.
later command, verify that the correct BACKDELETE
ANR0734E

data - node node name registered with
default COMPRESSION value.

76
by using the default COMPRESSION value for this

node.
User response: Verify that the correct COMPRESSION
value has been used for this node. Update this value, if
necessary.
ANR0735E

default ARCHDELETE value.

by using the default ARCHDELETE value for this node.
User response: Verify that the correct ARCHDELETE
necessary.
ANR0736E

default BACKDELETE value.

by using the default BACKDELETE value for this node.
User response: Verify that the correct BACKDELETE
necessary.
ANR0737E

data - existing COMPRESSION value
for node node name was not updated.

by using the existing COMPRESSION value for this
node.
User response: Verify that the correct COMPRESSION
necessary.
ANR0738E

data - existing ARCHDELETE value for
node node name was not updated.

ANR0739E ANR0744E
by using the existing ARCHDELETE value for this
node.
ANR0742E
User response: Verify that the correct ARCHDELETE

necessary.
ANR0739E

data - existing BACKDELETE value for
node node name was not updated.
Import command: Invalid value for TYPE

parameter in exported data for copy
group copy group name in domain domain
name, set policy set name, management
class management class name - this copy
group will not be imported.

command, an invalid value is encountered for the TYPE
parameter for copy group copy group, in policy domain
domain name, policy set policy set name, management
class management class name.


However, this copy group is not imported because a
TYPE value cannot be assigned.

by using the existing BACKDELETE value for this
node.
User response: Manually define this copy group, if

necessary.
User response: Verify that the correct BACKDELETE

necessary.
ANR0743E
ANR0740E

class management class name - backup is
assumed.

Based upon other copy group parameters, a copy group
type of backup is assigned.
User response: Verify that the assigned TYPE value of
backup for this copy group is correct.
ANR0741E

class management class name - archive is
assumed.

Based upon other copy group parameters, a copy group
type of archive is assigned.

MODE parameter in exported data for
archive copy group copy group name in
domain domain name, set policy set name,
management class management class name.

MODE parameter for archive copy group copy group
name, in policy domain domain name, policy set policy set
name, management class management class name.
default or existing MODE value is used.
later command, verify that the correct MODE value is
used for this archive copy group.
ANR0744E

MODE parameter in exported data for
backup copy group copy group name in

MODE parameter for backup copy group copy group
default or existing MODE value is used.
later command, verify that the correct MODE value is
used for this backup copy group.
User response: Verify that the assigned TYPE value of

archive for this copy group is correct.
77
ANR0745E ANR0750E
ANR0745E

SERIALIZATION parameter in exported
data for archive copy group copy group
name in domain domain name, set policy
set name, management class management
class name.

SERIALIZATION parameter for archive copy group
copy group name, in policy domain domain name, policy
set policy set name, management class management class
name.
default or existing SERIALIZATION value is used.
later command, verify that the correct SERIALIZATION
value is used for this archive copy group.
ANR0748E

by using the default MODE value for this backup copy
group.
User response: Verify that the correct MODE value
has been used for this copy group. Update this value, if
necessary.
ANR0749E
ANR0746E

MODE parameter in exported data backup copy group copy group name in
defined with default MODE value.

data for backup copy group copy group
class name.

data - archive copy group copy group
class name defined with default
SERIALIZATION value.

SERIALIZATION parameter for backup copy group
name.

name.


by using the default SERIALIZATION value for this
archive copy group.

later command, verify that the correct SERIALIZATION
value is used for this backup copy group.

SERIALIZATION value has been used for this copy
group. Update this value, if necessary.
ANR0747E

MODE parameter in exported data archive copy group copy group name in
defined with default MODE value.

by using the default MODE value for this archive copy
group.
necessary.
78
ANR0750E

data - backup copy group copy group
class name defined with default
SERIALIZATION value.

name.
by using the default SERIALIZATION value for this
backup copy group.
ANR0751E ANR0756E
ANR0751E

MODE parameter in exported data existing MODE value for archive copy
class management class name was not
updated.

by using the existing MODE value for this archive copy
group.
necessary.
ANR0752E

MODE parameter in exported data existing MODE value for backup copy
class management class name was not
updated.

by using the existing MODE value for this backup copy
group.
necessary.
ANR0753E

data - existing SERIALIZATION value
for archive copy group copy group name
in domain domain name, set policy set
name, management class management class
name was not updated.

name.
by using the existing SERIALIZATION value for this

archive copy group.
ANR0754E

data - existing SERIALIZATION value
for backup copy group copy group name
in domain domain name, set policy set
name, management class management class

name.
by using the existing SERIALIZATION value for this
backup copy group.
ANR0755E

ACTION parameter in exported data for
name.

ACTION parameter for schedule schedule name in policy
domain domain name.
default or existing ACTION value is used.
command, verify that the correct ACTION value is
ANR0756E

exported data for schedule schedule name
in domain domain name.

DURUNITS or PERUNITS parameter for schedule
schedule name in policy domain domain name.
default or existing values are used for DURATION,
79
ANR0757E ANR0763E
command, verify that the correct values for
DURATION, DURUNITS, PERIOD, and PERUNITS are
ANR0757E

data for schedule schedule name in
domain domain name.

DAYOFWEEK parameter for schedule schedule name in
default or existing DAYOFWEEK value is used.
command, verify that the correct DAYOFWEEK value is
ANR0758E

ACTION parameter in exported data schedule schedule name in domain domain
name defined with default ACTION
value.

domain domain name.
by using the default ACTION value for this schedule.
User response: Verify that the correct ACTION value
has been used for this schedule. Update this value, if
necessary.
ANR0759E

exported data - schedule schedule name in
domain domain name defined with
default values for DURATION,

by using the default values for DURATION,
ANR0760E

data - schedule schedule name in domain
domain name defined with default
DAYOFWEEK value.

by using the default DAYOFWEEK value for this
schedule.
ANR0761E

ACTION parameter in exported data existing ACTION value for schedule
schedule name in domain domain name was
not updated.

domain domain name.
by using the existing ACTION value for this schedule.
User response: Verify that the correct ACTION value
has been used for this schedule. Update this value, if
necessary.
ANR0762E

exported data - existing values for
DURATION, DURUNITS PERIOD, and
PERUNITS for schedule schedule name in
domain domain name were not updated.

by using the existing values for DURATION,
ANR0763E

data - existing DAYOFWEEK value for
80
ANR0764E ANR0769E
command. Alternatively, use the export data with the

unknown value, and the system will attempt to assign
a TYPE during import processing.

by using the existing DAYOFWEEK value for this
schedule.
ANR0767E

ANR0764E
Import command: Invalid lock status

detected while importing node node
name - this node will not be locked.

command, an invalid value is encountered for the lock
status for node node name.
but the node is not locked.
User response: An administrator with the proper
authorization must issue the LOCK NODE command, if
necessary.
ANR0765E
Import command: Invalid lock status

detected while importing administrator
administrator name - this administrator
will not be locked.

MODE parameter for copy group copy group name in
domain domain name, policy set policy set name,
exported data contains an unknown MODE value for
this copy group. If this data is imported, the default or
existing MODE value is used.
User response: Update the MODE value for this copy
group and restart the export command. Alternatively,
and update the MODE value after import processing
has been performed.
ANR0768E

status for administrator administrator name.
but the administrator is not locked.
authorization must issue the LOCK ADMIN command,
if necessary.
ANR0766E
Export command: Invalid value for TYPE

parameter detected while exporting copy
class management class name - system will
attempt to assign value during import.

parameter for copy group copy group name, in domain

MODE parameter detected while
exporting copy group copy group name in
- default or existing value is used
during import.

SERIALIZATION parameter detected
while exporting copy group copy group
class name - default or existing value is
used during import.

SERIALIZATION parameter for copy group copy group
name, in domain domain name, policy set policy set name,
exported data contains an unknown SERIALIZATION
value for this copy group. If this data is imported, the
User response: Update the SERIALIZATION value for
this copy group and restart the export command.
value, and check and update the SERIALIZATION
value after import processing has been performed.
ACTION parameter detected while
exporting schedule schedule name in
domain domain name - default or existing
value is used during import.

exported data contains an unknown TYPE value for
this copy group. If this data is imported, the system
attempts to assign a TYPE value based upon values for
other copy group parameters.
ANR0769E
User response: Delete and define this copy group to

eliminate the invalid data, and then restart the export

81
ANR0770E ANR0774E
ACTION parameter for schedule schedule name in
domain domain name.
exported data will contain an unknown ACTION value
for this schedule. If this data is imported, the default or
existing ACTION value is used.
User response: Update the ACTION value for this
and update the ACTION value after import processing
has been performed.
ANR0770E

DURUNITS parameter detected while

domain domain name.
exported data contains an unknown DAYOFWEEK
default or existing DAYOFWEEK value is used.
User response: Update the DAYOFWEEK value for
value, and check and update the DAYOFWEEK value
ANR0773E
Export command: Invalid lock status

detected while exporting administrator
administrator name - this administrator
will not be locked during import.

DURUNITS parameter for schedule schedule name in
domain domain name.

status for administrator administrator name.

exported data contains an unknown DURUNITS value
for this schedule. If this data is imported, the default or
existing DURUNITS value is used.

exported data contains an unknown lock status for this
administrator. If this data is imported, the
administrator will not be locked.
User response: Update the DURUNITS value for this

and update the DURUNITS value after import

authorization must issue the LOCK NODE or
UNLOCK NODE command to achieve the desired lock
status, and then restart the export command.
status, and issue a LOCK ADMIN or UNLOCK
ADMIN command after import processing has been
performed.
ANR0771E

PERUNITS parameter detected while

PERUNITS parameter for schedule schedule name in
domain domain name.
exported data will contain an unknown PERUNITS
default or existing PERUNITS value is used.
User response: Update the PERUNITS value for this
and update the PERUNITS value after import
ANR0772E
82

DAYOFWEEK parameter detected while
ANR0774E

COMPRESSION parameter detected
while exporting node node name - default

exported data contains an unknown COMPRESSION
value for this node. If this data is imported, the default
or existing COMPRESSION value is used.
User response: Update the COMPRESSION parameter
for this node and restart the export command.
value, and check and update the COMPRESSION value
ANR0775E ANR0782E
ANR0775E
Export command: Invalid lock status

detected while exporting node node name
- this node will not be locked during
import.

status for node node name.
exported data contains an unknown lock status for this
node. If this data is imported, the node will not be
locked.
User response: Lock or unlock the node to achieve the
desired lock status, and then restart the export
command. Alternatively, use the export data with the
unknown status, and lock or unlock the node after
import processing has been performed.
ANR0776E

ARCHDELETE parameter detected
while exporting node node name - default

exported data contains an unknown ARCHDELETE
or existing ARCHDELETE value is used.
User response: Update the ARCHDELETE parameter
value, and check and update the ARCHDELETE value
ANR0777E

BACKDELETE parameter detected while
exporting node node - default or existing

exported data contains an unknown BACKDELETE
or existing BACKDELETE value is used.
User response: Update the BACKDELETE parameter
value, and check and update the BACKDELETE value
ANR0778E
Command: Error encountered in accessing

data storage - device class device class
name is not defined.

an error occurred because the specified device class is
not defined.
System action: The command command is ended and
User response: Make sure the specified device class is
defined.
ANR0779E

data storage - disk volume specified.

an error occurred because a specified volume is a disk
volume rather than a tape volume.
User response: Make sure that all volumes specified
for the command command are tape volumes.
ANR0780E
Export/import command: Process aborted a server communications session could

not be established.

encounters an internal error in establishing an
intermemory communications session with other server
components.
Additional Server Memory. If the error is not resolved,
ANR0781E
Export/import command: Process aborted server sign on failed.

encounters an internal error in establishing an
intermemory communications session with other server
components.
ANR0782E
Export/import command: Process aborted a server data storage session could not
be established (rc return code).

encounters an internal error in establishing a session
83
ANR0783E ANR0789E
with the data storage services.
representative.
ANR0783E
Export/import command: Process aborted a server data storage Export/Import

stream could not be established (rc
return code).

encounters an internal error in establishing a session
with the data storage services.
representative.
ANR0784E
Export/import command: Process aborted internal error detected with the

Export/Import level: level number.

encounters an internal error in evaluating the
export/import level (SERVER, NODE, ADMIN,
POLICY).
representative.
ANR0785E
Import command: Invalid record type

xrecord type read from export data.

representative.
ANR0786E
Import command: Invalid export version

version number in exported data.
Explanation: The server import process encounters an

internal error in reading data from the export media.
An invalid export version number (version number) is
encountered during the read operation.
representative.
ANR0787E
Import command: Import of file space

filespace name in node node name aborted
by server (abort reason).

internal error in importing file space filespace name for
client node node name. The reason code abort reason is
encountered.
representative.
ANR0788E
Import command: Error error code during

import of data storage data.

internal data storage error. The error code error code is
encountered.

encounters an internal error in reading data from the
export media. An invalid record type of record type is
encountered during the read operation.

representative.

ANR0789E

84
Import command: Failure in normalizing

transaction identifier for sending to the
server.
ANR0790E ANR0795E
internal database transaction error in importing
information into the server database.
representative.
ANR0790E
Import command: Error in absorbing data

records.

internal error in importing information into the server
database.
representative.
Because the imported information for the rule is

ambiguous, the server assumes that the rule is for
backup data.
System action: The import process continues.
User response: The user for node node name should
query the access rules for the specified node name after
the import process has completed, and correct or delete
any access rules that are in error or not needed.
ANR0793E

in accessing data storage while executing an import or
export preview operation.
cause of the data storage failure. If you find and
resolve the error, retry the export or import operation.
If you cannot find the error, contact your service
representative for assistance in resolving the problem.
ANR0794E
ANR0791E
Export/import command: Protocol error verb verb type with length verb length
received, expected expected type.
Explanation: The server export or import process

encounters an internal protocol error in exporting
information from or importing information into the
server database. The verb verb type is encountered with
a length of verb length when a verb type of expected type
was expected.
representative.
ANR0792E
Import command: Invalid copy type

encountered in an imported file space
authorization rule for node node name,
file space filespace name - a type of
BACKUP will be assumed.
Explanation: During import processing for command

import command, an invalid copy type is encountered
for an authorization rule that grants access for file
space filespace name on node node name. Authorization
rules typically specify copy types of backup or archive,
depending on whether backup file access or archive file
access is granted by the file space owner to other users.

processing terminated abnormally error accessing data storage.

terminated abnormally - error accessing
data storage.

export operation.
cause of the data storage failure. If the import or export
operation involves a session with another server, run
the QUERY ACTLOG command to examine messages
on the other server as well. Messages on the other
server can help you troubleshoot the error on the local
server. If you find and resolve the error, retry the
export or import operation. If you cannot find the error,
contact your service representative for assistance in
resolving the problem.
ANR0795E

data storage - invalid volume name
specified.
Explanation: The server encounters an error in

accessing data storage while processing command
command. The error occurred because an attempt has
been made to access a volume with an invalid name.
85
ANR0796E ANR0803I
User response: Issue the command with a valid
volume name.
ANR0796E

data storage - insufficient number of
mount points available for removable
media.

the server cannot allocate sufficient mount points.
available.
ANR0797E

data storage - required volume was not
mounted.
Explanation: During command command processing, a

required volume cannot be mounted. The mount
request may have been canceled.
User response: Issue the command again and make
sure the necessary volumes are accessible.
ANR0798E
Import command: Error encountered in

accessing data storage - volume cannot
be used.
Explanation: During import processing, a volume has

been mounted but cannot be used.
User response: Query the activity log for messages
preceding this one that give additional information.
Make sure a usable volume is specified and mounted.
ANR0799E

data storage - volume already in use.

volume cannot be used because it is already defined in
a storage pool, or has been previously used by an
export, database dump, or database backup operation
(as recorded in the volume history) or is in use by
another process.
User response: Specify a volume that is not in use or
defined in a storage pool, and that has not been
previously used for an export, database dump, or
database backup operation as recorded in the server
volume history information. Use the QUERY VOLUME
command to display the names of volumes that are
86
defined to server storage pools. Use the QUERY

VOLHISTORY command to display the names of
volumes that have been used for export, database
dump, or database backup operations.
ANR0800I
Command command for node node name

started as process process ID.
Explanation: A file space deletion process has started

to delete one or more file spaces for the specified node.
The process is assigned the ID specified in the message.
System action: The server starts a background process
to perform the operation in response to the DELETE
FILESPACE command entered by an administrator.
User response: To obtain status on the file space
deletion process, issue the QUERY PROCESS command.
The process may be canceled with the CANCEL
PROCESS command.
ANR0801I

node node name started as process process
ID.
Explanation: The specified client node has started a

file space deletion process (on the server) to delete one
or more file spaces. The process has been assigned the
ID specified in the message.
to perform the operation in response to a request from
the client node.
The process may be canceled by an authorized
administrator using the CANCEL PROCESS command.
ANR0802I
DELETE FILESPACE filespace name

(backup/archive data) for node node name
started.
Explanation: A background server process has started

(on the server) to delete the specified file space
belonging to the node indicated. If a file space name is
not included in the message, all file spaces belonging to
the node are deleted.
System action: The background process deletes
backup and archive objects for the specified file space
while server operation continues.
ANR0803I

(backup data) for node node name
started.
ANR0804I ANR0813I
(on the server) to delete backup objects in the specified
file space belonging to the node indicated. If a file
space name is not included in the message, then the
backup objects for all file spaces that belong to the
node are deleted.
backup objects for the specified file space while server
ANR0804I

(archive data) for node node name started.

(on the server) to delete archive objects in the specified
file space belonging to the node indicated. If a file
space name is not included in the message, then the
archive objects for all file spaces that belong to the
node are deleted.
ANR0811I
Explanation: The server has started roll-off processing

to remove expired client backup and archive file copies,
based on the management class policy that is bound to
the files. The copy group retention and version
parameters for each files copy group are used by the
server to determine if copies are to be deleted from the
server. The expiration process was started as process
number process ID, and may be queried or canceled
with the QUERY PROCESS or CANCEL PROCESS
commands, respectively.
System action: The expiration process is now
cancellable. Server operation continues.
ANR0812I

archive objects for the specified file space while server
ANR0805I

canceled for node node name: number of
objects objects deleted.
Explanation: A background server process that has

been deleting file space data for the indicated node is
canceled by the CANCEL PROCESS command. The
number of objects deleted before the cancel ended the
operation are reported in the message.
System action: The server process is ended and server
User response: No action is required. An authorized
administrator can issue the DELETE FILESPACE
command to delete remaining objects in the file space.
complete for node node name: number of
objects objects deleted.
Explanation: A server process deleting file space data

for the node specified has completed. The total number
of objects deleted is reported in the message.
Inventory file expiration process process

ID completed: examined number of objects
objects, deleting number of backup objects
backup objects, number of archive objects
archive objects, number of DB backup
volumes DB backup volumes, and number
of recovery plan files recovery plan files.
error count errors were encountered.
Explanation: Server roll-off processing has completed.

The number of client objects examined and deleted,
based on management class policy, are displayed in the
message. A total error count is also displayed. The
number of DB backup volumes deleted is based on the
value specified on the SET
DRMDBBACKUPEXPIREDAYS. The number of
recovery plan files deleted is based on the value
specified on the SET DRMRPFEXPIREDAYS. Server
roll-off processing deletes the DB backup volumes and
recovery plan files only if DRM is licensed on the
server and the volumes or plan files are created on the
server to server virtual volumes.
System action: The roll-off process is ended and
User response: If the error count is not equal to 0,
examine messages that may have been issued in the
activity log to determine the cause for the errors.
ANR0813I
ANR0806I
Inventory client file expiration started as

process process ID.
Inventory file expiration process process

ID canceled prior to completion:
examined number of objects objects,
deleting number of backup objects backup
objects, number of archive objects archive
objects, number of DB backup volumes DB
backup volumes, and number of recovery
plan files recovery plan files. error count
errors were encountered.
Explanation: The inventory file expiration process was

canceled by an administrator. The number of objects
examined and deleted prior to the cancelation are
reported. A total error count is also displayed.
87
ANR0814I ANR0821E
System action: The server ends the file expiration
process.
ANR0814I
Expiration retry retry number of maximum

retries in number of seconds seconds.
Explanation: Server roll-off processing has

encountered an error in attempting to remove expired
client file copies from the server database. The
operation will be tried again in the number of seconds
indicated.
System action: The server waits for the number of
seconds indicated and retries the file expiration
operation.
User response: Expiration retry processing occurs
when the server database is full, the log is full, or
sufficient server memory is not available to continue
processing. Use the QUERY ACTLOG command to look
for messages issued prior to this one that indicate the
type of error encountered. If the server is out of
database space, issue the DEFINE DBVOLUME and
EXTEND DB commands to add volumes to the server
database and extend the database size. If the server is
out of log space, issue the DEFINE LOGVOLUME and
EXTEND LOG commands to add volumes to the server
log and extend the log size. If the server is low on
memory, allocate additional storage to the server. For
details, issue HELP MEMORY to display the
ANR0815I
Expiration retry in progress.
Explanation: The server is retrying an operation

during client file roll-off processing. Expiration retry
processing occurs when the server database is full, the
log is full, or sufficient server memory is not available
to continue processing.
System action: The roll-off operation is retried.
look for messages issued prior to this one that indicate
the type of error encountered. If the server is out of
database space, issue the DEFINE DBVOLUME and
ANR0816I
Expiration retry was successful.
Explanation: In accordance with management class

policy, server roll-off processing has been successful in
retrying a client file expiration.
System action: Server roll-off processing continues.
ANR0818I
Waiting to retry expiration because of

insufficient resources.
Explanation: The server inventory expiration process

is waiting to retry expiration processing that failed
because of insufficient memory, database, or log
resources on the server.
System action: Server operation continues. The
expiration processing is reattempted automatically.
examine messages issued prior to this one, which
indicated the resource that is not available to the
expiration process. Correct the shortage.
ANR0819I
Cancel in progress
Explanation: This message is displayed in response to

a QUERY PROCESS command, and indicates that an
inventory expiration process has been canceled. The
process will end shortly.
System action: The expiration process terminates and
ANR0820I
Sorting information for number objects

has been deleted.
Explanation: A background server process has deleted

sorting information for number files from the server
database. This process is started during initialization to
remove any sorting information which is left over from
previous export operations.
System action: The actual backup or archive objects
were not deleted, but only information used to sort
these objects during the previous export operation.
ANR0821E
Filespace identifier fsId is not valid.
Explanation: The identifier assigned for a filespace is

out of range.
System action: The file space is not added.
88
ANR0822I ANR0830W
ANR0822I
command: Filespace filespace name

(fsId=filespace id) successfully renamed
to new filespace name for node node name.
Explanation: The file space specified was renamed to

the new name specified for the node. This message is
displayed in response to successful completion of the
RENAME FILESPACE command.
System action: The system renames the file space for
the node as indicated
encountered when multiple file space deletion

processes are running at the same time. No action is
required unless the DELETE FILESPACE terminates
without completing the deletion process (see message
ANR0828).
ANR0827I
DELETE FILESPACE filespace name will

be retried for node node name.
Explanation: A file space deletion process for the node

indicated is being retried because an error was
encountered.
System action: The server process is retried.
ANR0823E
command: Filespace filespace name cannot

be renamed to new filespace name, a
filespace with this name already exists
for node node name.

ANR0828W
Explanation: The file space name specified as a target

name for the command was found to already exist for
the node specified. The command fails.
System action: Server operation continues, the
command fails.
User response: Reissue the command with a different
target filespace name
ANR0824I
Delete Filespace filespace name

(space-managed data) for node node name
started.

(on the server) to delete space-managed objects in the
specified file space belonging to the node indicated. If a
file space name is not included in the message, then the
space-managed objects for all file spaces that belong to
the node are deleted.
space-managed objects for the specified file space while
ANR0826I

node node name encountered a
transaction failure.

node node name terminated before
completion due to transaction failure:
number of objects objects deleted.

been deleting file space data for the indicated node is
terminated prematurely because of transaction failure.
The number of objects deleted before the operation
ended are reported in the message.
User response: Termination of this process because of
transaction failure usually indicates that a database
deadlock was detected during file space deletion. These
deadlock conditions are sometimes encountered when
multiple file space deletion processes are running at the
same time. The command should be started again
when fewer file space deletion processes are active. An
authorized administrator can issue the DELETE
FILESPACE command to delete remaining files in the
file space(s).
ANR0829E
Command: Invalid combination of TYPE

and DATA parameters.
Explanation: The specified command has been issued

with an invalid combination of the TYPE and DATA
parameters. DATA=IMAGES can only be specified if
TYPE=ANY or TYPE=BACKUP.
command is not processed.

been deleting file space data for the indicated node
encountered a transaction failure.
User response: Issue the command and specify a valid

combination of parameters.
System action: The server process is retried if the

maximum number of retry attempts have not been
exceeded.
ANR0830W
User response: Transaction failure usually indicates

that a database deadlock was detected during file space
deletion. These deadlock conditions are sometimes
Management class class name in domain

domain name used by node node name in
file space filespace name is no longer
active, or no longer has a BACKUP copy
group: DEFAULT management class
attributes will be used for expiration.
89
ANR0831W ANR0835W
Explanation: During policy roll-off processing, the
server has found a client file copy whose management
class or backup copy group no longer exists.
System action: The server obtains the DEFAULT
management class for the specified domain and uses its
backup copy group version and retention parameters to
determine if file copies need to be expired.
User response: No action is required. A policy
administrator with authority over the specified domain
may use the DEFINE COPYGROUP, DEFINE
MGMTCLASS, and ACTIVATE POLICY commands to
define and activate a policy set that contains definitions
for the missing management class or copy group.
ANR0831W
The DEFAULT management class class

name in domain domain name does not
have a BACKUP copy group: GRACE
PERIOD will be used for expiration.

server found a client file copy whose management class
or backup copy group no longer exists. The DEFAULT
management class for the indicated policy domain does
not contain a backup copy group; therefore, the server
uses the GRACE PERIOD retention value defined for
the specified policy domain to determine if client file
copies need to be expired and removed from the server
database.
System action: The server obtains the GRACE
PERIOD retention values for the specified domain and
then determines if backup file copies need to be
expired.
for the missing management class or backup copy
group.
ANR0832W

filespace filespace name is no longer
active, or no longer has an ARCHIVE
copy group: DEFAULT management
class attributes will be used for
expiration.

or archive copy group no longer exists.
archive copy group retention parameter to determine if
file copies need to be expired.
90

for the missing management class or copy group.
ANR0833W
The DEFAULT management class class

name in domain domain name does not
have an ARCHIVE copy group: GRACE
PERIOD will be used for expiration.

or archive copy group no longer exists. The DEFAULT
management class for the indicated policy domain does
not contain an archive copy group; therefore, the server
uses the GRACE PERIOD retention value defined for
the specified policy domain to determine if client file
copies need to be expired and removed from the server
database.
System action: The server obtains the GRACE
PERIOD retention values for the specified domain and
then determines if archive file copies need to be
expired.
MGMTCLASS, and ACTIVATE POLICYSET commands
to define and activate a policy set that contains
definitions for the missing management class or backup
copy group.
ANR0834W
Inventory client file expiration cannot

start because of insufficient memory will retry in number of seconds seconds.
Explanation: The server inventory expiration process

is pausing to retry an operation that failed because
sufficient memory is not available on the server.
expiration process will be retried after the stated delay.
ANR0835W

domain name is no longer active, or no
longer has a BACKUP copy group, or no
longer has an ARCHIVE copy group.
DEFAULT management class used to
delete number of backup files backup files
and number of archive files archive files.
Retention grace period used to delete
number of backup files backup files and
number of archive files archive files.

server found a management class or backup copy
group or archive copy group that no longer exists.
When a management class or backup copy group no
ANR0836W ANR0842E
longer exists, the number of backup client file copies
that have been deleted using the default management
class or the retention grace period is displayed in the
message. When a management class or archive copy
group no longer exists, the number of archive client
files that have been deleted using the default
management class or the retention grace period is
displayed in the message.
backup copy group or archive copy group version and
retention parameters to determine if file copies need to
be expired. If, however, the needed backup copy group
or archive copy group does not exist in the DEFAULT
management class, the server will use the retention
grace period for the domain.
User response: No action is required. This message is
only issued when expiration processing has been
started with the QUIET option to suppress detailed
messages. Expiration processing can be started without
the QUIET option to see the detailed messages which
will indicate specific node and filespaces and will
further distinguish between backup and archive copy
groups. A policy administrator with authority over the
specified domain may use the DEFINE COPYGROUP,
DEFINE MGMTCLASS, and ACTIVATE POLICY
commands to define and activate a policy set that
contains definitions for the missing management class
or copy group.
ANR0836W
No query restore processing session

session id for node node name and filespace
name failed to retrieve file high-level file
namelow-level file name - file being
skipped.
Explanation: The no query restore processing for the

session listed relating to the specified node name and
filespace failed to retrieve the specified file. An error
occurred while retrieving this file so it will be skipped.
System action: The no query restore operation
continues.
User response: Determine the cause of the file retieve
failure and correct it. After this situation is correct, the
client can do a restore of the specific file that was
skipped.
ANR0837I
The expire inventory running duration

of number of minutes minutes has
expired. The expire inventory process
ends.
Explanation: An ADSM Administrator or schedule

issued the command EXPIRE INVENTORY ...
DURATION=xxx, where xxx is the number of minutes
for the expire inventory process to run. That xxx
number of minutes has been reached, so the expire
inventory process ends.
System action: The expire inventory process ends.

ANR0838I
Pass pass of group table conversion

processing beginning.
Explanation: The contents of the group information

tables needs to be updated before the server can fully
initialize. This is an informational message indicating
that processing has begun for a particular pass of the
conversion.
System action: Server processing continues.
ANR0839I
Pass pass of group table conversion

processing complete.
Explanation: The contents of the group information

tables have been successfully converted for the
specified pass.
System action: If all passes of the conversion are
complete, server processing continues. If not, additional
passes will be performed.
ANR0840I
Converting group table information for

node node.
Explanation: The group table information for the

displayed node is being converted.
System action: Server processing continues
ANR0841I
Conversion for node Node name will be

undone.
Explanation: The indicated node is converted. This

status will be undone before the update archive
operation can be performed.
ANR0842E
Command: the update archive operation

for node node name did not complete
(result).
Explanation: The update archive operation for the

specified node did not complete.
System action: The update archive operation ends.
User response: Check previous error messages.
91
ANR0843I ANR0852E
ANR0843I

for node node name completed
successfully.
Explanation: The update archive operation for the

specified node completed successfully.
ANR0844E
Command: node name is not a

backup-archive node.
Explanation: The specified node name is not a

backup-archive node.
System action: Processing fails for the command.
User response: Reissue the command with a valid
node name.
ANR0845E
Undo conversion processing for node

node name did not complete (result).
Explanation: UNDO ARCHCONVERSION was issued

for the specified node. The specified error occurred.
User response: Check previous error messages.
ANR0847I
CLEANUP BACKUPGROUPS evaluated

number of groups groups, and deleted
groups deleted orphan groups with
members deleted members deleted.
Explanation: The CLEANUP BACKUPGROUPS has

finished processing, and has deleted the specified
number of orphan groups and members.
ANR0848W
Expiration failed to delete file type file

file name for node node name and
filespace filespace name - file will be
skipped.
Explanation: The expiration process was unable to

delete the indicated file. The file will be skipped by
expiration.
System action: The expiration process continues.
User response: Re-try expiration to determine if the
cause of the deletion failure was an intermittent
problem or if it is a permanent problem. If after a
subsequent expiration attempt the file still is not
deleted, please contact your service representative.
92
ANR0849E
Command: Not permitted for node Node

Name - node of type SERVER.
Explanation: The indicated DELETE FILESPACE

process is not started because the node specified is of
NODETYPE=SERVER. A DELETE FILESPACE may
only be processed for nodes of this type with the
TYPE=SERVER parameter specified.
System action: The DELETE FILESPACE command is
ended and server processing continues.
User response: If this filespace must be deleted,
Reissue the command with the TYPE parameter set to
TYPE=SERVER. Please use caution when using the
TYPE=SERVER parameter as this can impact the
availability of data for the server that owns these files.
ANR0850E
Command: Cannot Start process name

Process.

process cannot be started on the server.
User response: This usually indicates that sufficient
server memory is not available on the server. Allocate
additional storage to the server. For details, issue HELP
MEMORY to display the information online or see
Appendix A. Allocating Additional Server Memory.
ANR0851E
Cannot start delete file space thread for

node node name.

process cannot be started on the server. Sufficient
memory on the server may not be available.
ANR0852E
Command: No matching file spaces

found for node node name.
Explanation: The server did not find any file spaces

for the node indicated matching the names specified in
the command.
System action: The server ends the command.
User response: Enter the command with file space
names that refer to defined file spaces for the specified
node. Note that file space names are case sensitive.
Enter them by using exactly the same uppercase and
lowercase characters that match the file space name
defined on the server. Use the QUERY FILESPACE
ANR0853E ANR0860E
command to determine which file spaces are defined
for a node on the server.
database using the EXTEND DB command.

ANR0857E
ANR0853E
Transaction failed in file space deletion,

DELETE FILESPACE process aborted.
Explanation: A database transaction fails while the

server is deleting file space data.
System action: The server ends the file space deletion
process.
representative.
Explanation: The server encounters an error accessing

data storage during file space deletion processing.
process.
representative.
ANR0858E
ANR0854E
Inventory file space query failure,


querying the inventory database during a file space
deletion process.
process.
representative.
Server LOG space exhausted, DELETE
FILESPACE process aborted.
Inventory object search failure, DELETE

Explanation: The server encounters an error accessing

the inventory database during file space deletion
processing.
process.
representative.
ANR0859E
ANR0855E
Data storage session failure, DELETE

Data storage object erasure failure,

Explanation: Insufficient server log space has been

encountered during file space deletion processing.

removing file copies from data storage during file space
deletion processing.

process.

process.

command, and can extend the size of the log by using
the EXTEND LOG command.

representative.
ANR0856E
Server database space exhausted,

Explanation: Insufficient server database space has

been encountered during file space deletion processing.
process.
administrator can add log volumes using the DEFINE
DBVOLUME command and can extend the size of the
ANR0860E
Expiration process process ID terminated

due to internal error: examined number of
objects objects, deleting number of backup
objects backup objects, number of archive
objects archive objects, number of DB
backup volumes DB backup volumes, and
number of recovery plan files recovery plan
files. error count errors were encountered.

during file expiration processing. The number of files
93
ANR0861E ANR0866E
examined and deleted prior to the error are reported. A
total error count is also displayed.
System action: The server ends the expiration process.
representative.
ANR0861E
Transaction failed in expiration,

inventory expiration aborted.
Explanation: The server encounters a database

transaction failure during policy roll-off processing.

command and can extend the size of the log by using
ANR0865E
Expiration processing failed - internal

server error.
Explanation: Server retry processing during policy

roll-off fails.
System action: The server ends policy roll-off
processing.
Explanation: The server ends policy roll-off processing

because sufficient server memory is not available.

activity log and search for messages. If the server is out
of database space, issue the DEFINE DBVOLUME and
Additional Server Memory. If the error cannot be
isolated and resolved, contact your service
representative.

processing and server operation continues.
ANR0866E

Explanation: Server policy roll-off processing ends

because retry processing has not been successful in
expiring client file copies from the server database.
ANR0863E

System action: The server ends roll-off processing.

representative.
ANR0862E
Expiration processing suspended insufficient memory.
Expiration processing suspended insufficient DB space.

because sufficient server database space is not
available.
DEFINE DBVOLUME command and can extend the
size of the database using the EXTEND DB command.
ANR0864E
Expiration processing suspended insufficient LOG space.

because sufficient server log space is not available.
94
Expiration processing retries failed - no

success after maximum retries retries.

activity log and search for messages. If the server is out
of database space, issue the DEFINE DBVOLUME and
Additional Server Memory. If the error cannot be
representative.
ANR0867E ANR0874E
ANR0867E
Unable to open policy domain for node

node name during server operation.
Explanation: Policy roll-off processing on the server

encounters an error while obtaining policy information
related to the specified node.
System action: The server ends roll-off processing and
representative.
ANR0868E
Cannot find management class name for

ID management class ID.

encounters an error while obtaining policy information.
representative.
ANR0869E
Cannot find policy domain for node

node ID.

encounters an error while obtaining policy information
related to the specified node.
representative.
ANR0870E
Cannot find node name for node node

ID.

encounters a database error in obtaining information
for a client node.

representative.
ANR0871E
Cannot find file space name for node

node ID, file space file space ID.

encounters a database error in obtaining information
for a client node.
representative.
ANR0872E
Grace Period retention for domain

domain name could not be obtained.

encounters a database error in obtaining GRACE
PERIOD values for the specified policy domain.
representative.
ANR0873E
Invalid copy type encountered in

expiring files: copytype ID

encounters a database error in obtaining copy group
information.
representative.
ANR0874E
Backup object object.ID not found during

inventory processing.
Explanation: Inventory processing on the server

encounters a database error in obtaining backup
information in data storage.
System action: The server ends roll-off processing, or
client session(s) and server operation continues.
95
ANR0875E ANR0882E
representative.
ANR0875E
Archive object object.ID not found

during expiration processing.

encounters a database error in obtaining archive
information in data storage.
representative.
ANR0876E
Data storage erasure failed during

expiration processing.

encounters a database error while deleting information
from data storage.
representative.
ANR0877E
Copy type not backup for object

object.ID.

encounters a database error in accessing inventory
information.
representative.

information.
representative.
ANR0879E

information.
representative.
ANR0880E
Entry for backup object object.ID not

found.
96
Filespace command: No matching file

spaces.
Explanation: The server did not find any file space

names matching the specifications entered in the
filespace command.
User response: Use the QUERY FILESPACE command
to determine which file spaces are defined on the
server. Note, that file space names are case sensitive.
Reissue the file space command and specify the proper
file space name (in proper case).
ANR0881E
Policy Error : the GRACE PERIOD

archive retention value could not be
obtained for domain domain ID during
client inventory processing.

in accessing policy information.
ANR0882E
ANR0878E
Error opening inventory file space

query.
Policy Error: Unable to open policy

domain for node node name during client
inventory query processing.

in accessing policy information.
ANR0883E ANR0889E
System action: The client operation is ended and
ANR0883E
Cannot obtain node name for node node

ID.
want to examine the policy definitions for new

management class name so they are aware of the
management classes that may be used if the policy set
containing this management class is activated.
ANR0886E

in accessing client node information.
ANR0884E
Error code during deletion of sorting

information for number objects.
Explanation: A background server process

encountered an internal error after deleting sorting
information for number files from the server database.
This process is started during initialization to remove
any sorting information which is left over from

server finds a client file copy with a management class
or a backup copy group that no longer exists.
System action: The server skips the files in error.
User response: For programming support, contact
ANR0887E
System action: The backup or archive objects were not

deleted. Only the information used to sort these objects
during the previous export operation was deleted. The
background process was terminated before all sorting
information had been deleted. The system will not
perform further export processing of file data until this
problem has been resolved.
activity log and search for messages. Then restart the
server. If the error cannot be isolated and resolved,
ANR0885I
Import command: Processing management

class management class name for domain
domain name and policy set policy set
name as management class new
management class name.

processing the policy information for management class
management class name in domain domain name and
policy set policy set name. The management class is
imported under the name new management class name.
During import processing, management classes defined
as either DEFAULT or GRACE_PERIOD must be
renamed so that the management class does not conflict
with existing server policy conventions. Import
processing is then able to import file data by using the
renamed management class.
System action: Import processing for the command
continues.
User response: None. However, an administrator may

file space filespace name has no BACKUP
copy group with id copy group id;
Expiration will not be performed for
files from this node and filespace that
are bound to this management class and
copy group id.

file space filespace name has no archive
copy group with id copy group id. Server
operation will not be performed for files
from this node and filespace that are
bound to this management class and
copy group id.

server finds a client file copy with a management class
or an archive copy group that no longer exists.
System action: The server skips the specified files.
ANR0888E
SQL commands cannot be issued from

the server console.
Explanation: An SQL command was issued from the

server console. SQL commands cannot be issued from
the server console because they may require a long
time complete and the server console should be
available to control other server functions.
User response: Issue the SQL command from an
ANR0889E
The server is not licensed for Central

Administration functions. This includes
the ability to issue SQL commands.
Explanation: An SQL command was issued but the

server is not licensed to support Central Administrative
functions, including SQL query support.
97
ANR0890I ANR0898I
User response: If you have purchased the Central
Administration license, use the REGISTER LICENSE
command to enable the license on the server. If you
have not purchased the license and wish to do so,
ANR0890I

optionset optionset name.

is currently processing optionset definition information.
command continues.
ANR0891I

optionset definitions.

copies number client optionset definitions from the
command.
ANR0894I
Current system has been accepted as

valid.
Explanation: This message is displayed when the

ACCEPT DATE command has been issued and the date
has been accepted as valid by the server.
System action: The current system date is accepted as
valid by the server. The server will begin processing
using the current system date.
User response: Issue the ENABLE SESSIONS ALL
command to allow client, server and administrative
sessions to start.
ANR0895E
Command: Cannot Start process name

Process.
Explanation: The indicated process cannot be started

on the server.
System action: The specified command is ended and
server processing continues.
ANR0897I

Node Node name has (Filespace count)

filespaces. Command has reset
descriptions for (Directory count)
directories and (File count) files. (Delete
count) directories were deleted.

optionsets from the server.
Explanation: The indicated update archive operation

has completed processing a node to reset the
descriptions for directories and files. The information
displayed includes the number of filespaces processed,
the number of directories and files for which
descriptions were reset, and the number of directories
that were deleted because they had the same path
specification.
ANR0892I
Export command: No matching optionsets

found for exporting.

find any client optionsets for export command.

ANR0893I
Are you sure that you want to accept the

current system date as valid ?

ACCEPT DATE command has been issued to confirm
that you want to accept the date on the system as
valid. Accepting an invalid date can cause any of the
following problems: Premature deletion of data
Excessive retention of data Scheduling problems Event
record problems Password expiration problems.
System action: The command waits for you to
confirm the action.
User response: Specify Yes if you want to accept the
system date as valid, or No if you do not want to
execute the command.
98
ANR0898I

filespaces with (Directory count)
directories and (File count) files. There
are (Unique count) directories with
different path specifications and (Not
referenced) not referenced by files. The
node is converted (Conversion status).

has completed processing a node for the UPDATE
ARCHIVE SHOWSTATS command. The information
displayed includes counts for the filespaces, directories
and files.
ANR0899I ANR0910W
ANR0899I

filespaces. Command has deleted
(Directory count) directories and found
(File count) new files with no directories.

has completed processing a node to delete directories.
The information displayed includes the number of
filespaces processed, the number of directories that
were deleted and the number of files that, now, do not
have directories.
ANR0903W
Explanation: While processing the specified server

options file, the server has encountered more of the
named statement type than can be processed.
System action: The server ignores the extra statement.
Server initialization continues.
User response: Ignore the error, or use a text editor to
correct the error and restart the server.
ANR0904W

ANR0900I
Processing options file filespec.
Explanation: At server initialization, the server is

reading the server options file whose name is shown in
the message.
System action: The server reads and processes the
options in this file.
ANR0901W
Invalid option statement found in file

filespec.
Explanation: While processing the server options file

named, the server has encountered an invalid
statement. The invalid statement type is shown in the
message. The lines following this message provide
more information.
System action: The server ignores the statement in
error. Server initialization continues. The default value
is used for any missing or ignored options.
ANR0902W
Unsupported keyword found in file

filespec.

named, the server has encountered an invalid keyword
on an option statement. The lines following this
message provide more information.
System action: The server ignores the option
statement in error. Server initialization continues. The
default value is used for any missing or ignored
options.
Excessive option statement found in file

filespec.
Duplicate option statement found in file

filespec.

named, the server has encountered a duplicate
statement of the type shown.
System action: The server ignores the duplicate
statement. Server initialization continues.
ANR0905W
Options file filespec not found.

unable to locate the server options file named.
System action: The server uses the default values for
all options. Server initialization continues.
User response: If the default values are acceptable,
ignore the error. Otherwise, move a valid server
options file to the proper location, rename a valid
options file to the proper name, or use a text editor to
build the proper server options file, and then restart the
server.
ANR0909E
Insufficient memory to process options

file.

unable to process the server options file due to
System action: Server initialization ends.
User response: Restart the server with more memory
available. Refer to the Administrators Guide for your
ANR0910W
Archive entries for nodeName are already

converted.
Explanation: Archive entries for nodeName have

already been converted to the description tables. They
will not be converted again.
User response: To force the reconversion of the
archive entries for nodeName, use the FORCE=Yes
99
ANR0911I ANR0920I
option to the CONVERT ARCHIVE command.
ANR0911I
Archive conversion processing for node

name completed successfully. The
description tables have description count
descriptions, directory count directories,
file count and files and object set count
object sets.
Explanation: CONVERT ARCHIVE for the specified

node completed successfully. The node can now query
for archive objects specifying a non-wildcarded
description.
User response: Ensure that a valid language is

specified in the LANGUAGE option of the server
options file. If a change is made to the options file,
restart the server to activate changes.
ANR0916I
Product Name distributed by Company is

now ready for use.
Explanation: The server has completed startup

processing and is now ready for use.

ANR0912I
Undo conversion processing for node

node name completed successfully. The
node is no longer converted.
Explanation: UNDO ARCHCONVERSION was issued

for the specified node. The node will no longer use the
archive description tables.
ANR0913E
Archive conversion processing for node

node name did not complete (result).
Explanation: Archive conversion for the indicated

node did not complete because of the specified result.
System action: Archive conversion ends. Server
User response: Check previous messages for error
conditions.
ANR0914E
Diagnostic(ID): a request failed because

object (object name), size (size), exceeds
the maximum size of maximum size.
Explanation: The size of the specified object exceeds

the maximum size defined for that object. The server
cannot handle the new object.
fails.
User response: Determine why the new objects length
exceeds the maximum specified for the object. Reduce
the length of the object.
ANR0917W
Explanation: The client cannot handle very long

policies.
System action: The client operation is ended and
User response: Upgrade the client to the latest level,
or activate a policy set with fewer management classes.
ANR0918E
Unable to open language language name

for message formatting.
Explanation: The server is unable to open the

specified message repository.
System action: Server initialization continues with the
default message repository.
100
Inventory operation for node node name

terminated - lock conflict.
Explanation: During the indicated operation, the

server needs to obtain a lock that is not available.
System action: The indicated operation ends.
User response: Restart the operation.
ANR0919E
Filespace name fsName with length

length was encountered for nodes node
list.
Explanation: The specified filespace name was found

for the nodes in the list. The name is not allowed. The
error may occur while processing an administrative
command or client request.
User response: If the error occurs during processing
for an administrative command such as EXPORT
NODE or RENAME FILESPACE, rename the filespace
for the nodes in the list using a valid name. If found
while processing a client request, contact your service
representative.
ANR0920I
ANR0915E

name (client platform) - in domain domain
name failed because of policy length.
Tracing is now active to standard

output.
Explanation: In response to a TRACE START

command, server trace records are being written to the
standard output destination (usually the server
console).
ANR0921I ANR0936E
ANR0921I
User response: Reissue the command with the proper

parameters.
Tracing is now active to file file spec.
Explanation: In response to a TRACE START

command, server trace records are being written to the
file named.
ANR0927E
Unknown trace class keyword - class.
Explanation: A TRACE ENABLE command has been

entered which specifies an unknown trace class.
System action: The command is ignored.
User response: Reissue the TRACE command with the

correct class.
ANR0922I
Trace ended.
Explanation: In response to a TRACE END command,

server trace records are no longer being written.
ANR0923E
Tracing is inactive.
Explanation: A TRACE END command has been

entered, but tracing is not active.
ANR0928E
Unable to open trace file file spec for

appending.
Explanation: A TRACE BEGIN command specifies an

output file, but the server cannot write to that file.
User response: Check the file for proper access
permissions, or reissue the TRACE command
specifying a different output file.
ANR0929E
Insufficient memory to activate tracing.
User response: If tracing is desired, use the TRACE

ENABLE and TRACE START commands to activate
server tracing.
Explanation: A TRACE BEGIN command has been

entered, but the server has insufficient memory
available to activate tracing.
ANR0924E
Tracing is already active to file file spec.

entered, but tracing is already active to the file named.
User response: If the current trace output file is
acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
ANR0925E
Tracing is already active to standard

output.

entered, but tracing is already active to the standard
output destination (usually the server console).
User response: If the current trace output destination
is acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
the TRACE BEGIN command as desired.
ANR0926E
Missing or invalid TRACE command

parameter.
User response: If tracing is required, make more

memory available to the server then restart the server.
ANR0936E
Session session ID for session name failed

sending verb verb name because client
not able to handle extended qualifier
attribute.
Explanation: A server was going to send the reported

verb for the indicated session but was not able to send
it. The verb could not be sent to the client because it
contains extended information about the low-level
qualifier. The extended low-level qualifier is used to
store names up to 512 bytes in length. The client that
this verb was supposed to be sent to does not support
the extented low-level qualifier information.
System action: The send of the verb to the reported
session fails and this server operation will fail and
report a communication error.
User response: The client session reported needs to
have the installed client upgraded to TSM version 5.1.5
or higher in order to support the extended low-level
qualifier.
Explanation: The TRACE command issued contains

an invalid parameter, or is missing a required
parameter.
101
ANR0937I ANR0947E
ANR0937I
Expiration process process ID is ending.
Explanation: The expiration process referenced is

ending either because it has been cancelled or because
it has completed the necessary actions. This message is
only issued in the case where expiration was processing
a long-running operation, such as deleting a group of
related files (for example, a backup group). This
message indicates the time when the long-running
operation ended.
User response: If the wrong process number has been

entered, reissue the command with the correct process
number.
ANR0943E
Command: Process process ID could not be

canceled.
Explanation: A CANCEL PROCESS command has

been entered for the specified process, but the process
specified is an automatic process, such as migration or
reclamation, that cannot be canceled.
System action: The server ignores the command.
ANR0939E
Error error code occurred while locating

base object (baseIdHi.baseIdLo) for subfile
(subfileIdHi.subfileIdLo): Node node name,
File space filespace name, Type file type,
File name file name.
ANR0944E
Command: No active processes found.
Explanation: A QUERY PROCESS command has been

entered, and no processes are active.
Explanation: Export processing did not find the base

object for the specified subfile. Export processing does
not continue.
System action: Export processing stops. Server

ANR0945W
User response: Audit the database to correct the

entries.
Explanation: An error is detected during transaction

commit for the specified process. This message should
be preceded by other messages that give additional
information about the failed transaction.
ANR0940I
Cancel request accepted for process

process ID.

been entered for the specified process. Some processes
will experience a delay before they terminate. This
delay may be lengthy for processes that involve remote
data movement.

was aborted for process process ID.

fails.

ANR0946E
Archive processing fails: Object

objIdHi.objIdLo not found.

been entered for the specified process, but a cancel is
already pending for that process.
Explanation: Archive processing fails because the

specified object was not found. An archive request is
completed in stages. The object may have been deleted
by an archive delete request, delete filespace or
expiration that began and completed between these
stages.
System action: System processing continues.
User response: Check the client log for error and retry
messages. Reissue the archive request if the retry failed.
ANR0941I
ANR0942E
Command: Cancel for process process ID

is already pending.
Command: Process process ID cannot be

found.
ANR0947E
Error writing to trace file file spec.

been entered for the specified process, but the process
is not active. Either the process has already ended or
the wrong process number has been entered.
Explanation: An error occurred while writing to the

specified trace file.

permissions, or for the out of space issue for the trace
102
System action: Trace is disabled.
ANR0948I ANR0956I
file. Once this is corrected, reissue the TRACE BEGIN
command, specifying either the same or a different
output file.
ANR0948I

for node Node name has started as
background process process ID.
Explanation: An update archive operation has started

under the indicated background server process with the
indicated process identifier.
ANR0953W
Audit command: Redundant encryption

keys for the archive object (object.ID) do
not match.
Explanation: The encryption key stored for the archive

object in the Object.Ids table does not match the
encryption key stored in the Archive.Objects table. The
audit command is not able to determine which key is
the correct key.
System action: The objects encryption keys are not
modified.

ANR0954W
ANR0949I

for node Node name has started as
foreground process process ID.
Explanation: An update archive operation has started

under the indicated foreground server process with the
indicated process identifier.
ANR0950I

for node Node name has been cancelled.

was cancelled.
administrator can re-issue the command at a later time,
if appropriate.
ANR0951I

for node Node name completed
successfully.
Explanation: An update archive operation completed

successfully.
ANR0952W
The filespace Filespace name cannot be

included in the backup set because it
contains encrypted data.
Explanation: Data from the filespace cannot be

included in the backup set because the filespace
contains encrypted data.
System action: The filespace is skipped.
Audit command: Redundant encryption

keys for the backup object (object.ID) do
not match.
Explanation: The encryption key stored for the bckup

object in the Object.Ids table does not match the
encryption key stored in the Backup.Objects table. The
audit command is not able to determine which key is
the correct key.
System action: The objects encryption keys are not
modified.
ANR0955I

node node name failed deletion because
of a restartable restore session.
Explanation: The reported node and filespace have a

restartable restore session active or restartable. A
filespace cannot be deleted while the restartable restore
session exists.
System action: The server process is retried if the
maximum number of retry attempts have not been
exceeded.
User response: Use the QUERY RESTORE command
to view active and restartable restores sessions for this
filespace. Either wait for the sessions to complete or
cancel the sessions with the CANCEL RESTORE
command, and reissue the DELETE FILESPACE
command. To view restartable restore sessions issue the
command QUERY RESTORE. Either:
v wait to reissue the DELETE FILESPACE command
after this restartable restore has completed
v cancel the restartable restore session with the
CANCEL RESTORE command
ANR0956I
Audit command: Active version for

inactive inventory object (object.ID) does
not exist. The expiring object entry must
be corrected.
Explanation: A database audit process found an

expiring object entry for an inactive inventory object
that indicates an active version of the object exists, but
103
ANR0957I ANR0966I
the active version does not exist. Because FIX=NO has
been specified for the command, the expiring object
entry is not corrected.
System action: Audit processing continues.
used for a volume in the device class shown.

System action: The process waits for the mount
points.
User response: Respond to any mount requests.

ANR0962I
ANR0957I
Audit command: Active version for

inactive inventory object (object.ID) does
not exist. The expiring object entry will
be corrected.

expiring object entry for an inactive inventory object
that indicates an active version of the object exists, but
the active version does not exist. Because FIX=YES has
been specified for the command, the expiring object
entry will be corrected.
Explanation: The process whose ID is shown has

begun to wait for mount points that can be used for a
volume in the two device classes shown.
System action: The process waits for the mount
points.
ANR0963I

ANR0958I
CLEANUP BACKUPGROUPS evaluated

objectcount group objects, found
errorcount errors, and deleted deleted
group objects with completion state
state.
Explanation: The CLEANUP BACKUPGROUPS utility

ended with the presented state.
ANR0959I
Conversion of grouping table is percent

done percent complete.
Explanation: An internal data base table is being

converted, and the conversion process is the indicated
amount complete.
Process process ID waiting for mount

points in device classes device class name
and device class name.
Process process ID waiting for mount of

input volume volume name.

begun to wait for the mount of the input volume
shown.
System action: The process waits for the mount.
ANR0964I

output volume volume name.

begun to wait for the mount of the output volume
shown.
ANR0965I

scratch volume.

begun to wait for the mount of a scratch volume.
ANR0960I
Process process ID waiting for mount

point in device class device class name.

begun to wait for a mount point that can be used for a
volume in the device class shown.
System action: The process waits for the mount point.
ANR0961I
Process process ID waiting for multiple

mount points in device class device class
name.

begun to wait for multiple mount points that can be
104

ANR0966I
Process process ID waiting for access to

input volume volume name.

begun to wait for availability of the input volume
shown.
System action: The process waits for the volume to
become available.
ANR0967I ANR0984I
ANR0967I
Process process ID waiting for access to

output volume volume name.

begun to wait for availability of the output volume
shown.
System action: The process waits for the volume to
become available.
ANR0969E
The server database must be formatted

and loaded or restored before the server
can be started.
Explanation: The server has been restarted after

toleration of a zero bit mismatch error. In order to start
the server, you must recover the database with a
process that includes a DSMSERV FORMAT. Perform
one of the following procedures. Either do these steps:
command. For complete details on this command, refer

to the Administrators Reference.
ANR0982E
Explanation: The server database must be initialized

before it can be loaded with the LOADDB parameter,
by issuing the DSMSERV LOADFORMAT command.
The server database is not currently in the initialized
state.
System action: Server LOADDB processing stops.
User response: Issue the DSMSERV LOADFORMAT
command. For complete details on this command, refer
ANR0983W
1. Format the volumes using DSMSERV FORMAT

2. Restore the database using DSMSERV RESTORE DB
Or do these steps:
1. Unload the database using DSMSERV UNLOADDB
2. Format the volumes using DSMSERV FORMAT
3. Load the database using DSMSERV LOADDDB
Note: Do not use DSMSERV DUMPDB on the database
for this recovery.
System action: Server initialization stops.
User response: Perform one of the database recovery
actions.
The server database must be initialized

before the database can be loaded.
The server database was recorded by a

down-level version of the server
program. The UPGRADEDB parameter
is required to start the server and
automatically upgrade the database
contents to the current server version.
Please refer to installation instructions
for precautionary backup procedures
prior to doing this.
Explanation: At server startup, the server has

discovered that the database information was written
by an earlier version of the server program and is not
compatible with this version. To automatically upgrade
the server database to this version of the server
program, the UPGRADEDB parameter must be
specified when starting the server.
System action: The server ends.
ANR0980E
The server database must be audited

with FIX=YES before the server can be
started.
Explanation: The server has been restarted after a

DSMSERV LOADDB command processed a database
image that was known to have inconsistencies. In order
to bring the database back to a consistent state, you
must run the AUDITDB command.
User response: Refer to installation instructions for

specific information on precautionary measures that
you may want to take to back up the database prior to
upgrading it to the current server level. After you have
taken these measures, start the server and specify the
UPGRADEDB parameter. This parameter only needs to
be specified once to start the server, and should NOT
be included in any automated programs that start the
server.

User response: Issue the DSMSERV AUDITDB
FIX=YES command. For complete details on this
command, refer to the Administrators Reference.
ANR0981E
The server database must be restored

before the server can be started.
Explanation: The server has been restarted after an

incomplete RESTORE DB. In order to start the server,
you must restore to the database to a consistent state
using the DSMSERV RESTORE DB command.
ANR0984I
Process process ID for process name started

in the process state at process start time.
Explanation: The process whose ID is shown has been

started for the process indicated by the process name
running in the indicated state.

User response: Issue the DSMSERV RESTORE DB
105
ANR0985I ANR0991I
ANR0985I
Process process ID for process name

running in the process state completed
with completion state completion state at
process start time.
Explanation: A completion state of FAILURE indicates

that the operation encountered an error condition or
terminated before completion. A completion state of
SUCCESS indicates that the operation ran to
completion, but in some situations may have
encountered and reported conditions that would affect
the outcome of the operation.
User response: If the completion state is FAILURE,
then review the activity log and the event log to try to
determine the cause of the failure. If the completion
state is SUCCESS, the activity log and the event log can
still be checked for warning messages regarding
conditions that could have affected the operation.
ANR0986I

running in the process state processed
items processed items for a total of bytes
processed bytes with a completion state
of completion state at process start time.

ANR0987I

items processed items with a completion
state of completion state at process start
time.

106
ANR0988I

bytes processed bytes with a completion
state of completion state at process start
time.

ANR0989E
The server database must be loaded or

restored before the server can be started.
Explanation: The server is restarted after the

LOADFORMAT command is run. To start the server,
you must load the database by issuing the DSMSERV
LOADDB or the DSMSERV RESTORE DB command.
User response: Issue the DSMSERV LOADDB or
DSMSERV RESTORE DB command. For complete
details on these commands, refer to the Administrators
Reference.
ANR0990I
Server restart-recovery in progress.
Explanation: The server has been restarted after a halt

or system failure. If necessary, the server performs
recovery processing in order to bring the system back
to a consistent state.
System action: Server initialization continues.
ANR0991I
server shutdown complete.
Explanation: In response to a HALT command, the

server or storage agent has completed its termination
processing.
System action: The server or storage agent ends.
ANR0992I ANR1003I
ANR0992I
Server installation complete.
ANR1000I
Explanation: The server installation procedure has

completed successfully. The server is now available for
normal operation.
System action: Server completes installation
processing.
ANR0993I
Server initialization complete.
Explanation: The server has been restarted after a halt

or system failure. It is now ready to resume normal
operation.
System action: Server completes initialization.
Migration process process ID started for

storage pool storage pool name
automatically or manually,
highMig=highMig value, lowMig=lowMig
value, duration=duration.
Explanation: Because the high migration threshold for

the storage pool shown has been exceeded, a process
has been started to migrate files from the storage pool.
Note: a duration value of No means that the duration
is not specified and hence the migration runs without
duration.
System action: Data is moved from this storage pool
to the next (target) pool.
ANR1001I
ANR0994W
Explanation: A migration process for the named

storage pool ends. This action can occur because the
low migration threshold for the storage pool has been
reached, there are no more nodes with files to be
migrated, there are no more volumes to be migrated, or
the duration specified has been reached.
This server has not been properly

installed.
Explanation: The server was started for normal

operation, but had not yet been installed.
User response: Install the server properly before
starting it.
ANR0995W
This version of the server program is

down-level with respect to the
information recorded on disk; a newer
version of the program should be used.
Migration process process ID ended for

storage pool storage pool name.

ANR1002I
Migration for storage pool storage pool

name will be retried in number of seconds
seconds.

discovered that the disk information was written by a
later version of the server program. This version of the
server program should not be used.
Explanation: Because of a problem encountered

attempting migration for the named storage pool,
migration is delayed but will be retried after the time
period shown.
System action: The server waits for the specified

period and then retries migration for the storage pool.
This delay applies to a single migration process. After a
number of unsuccessful retries, the server will
automatically cancel the process. If other migration
processes are executing for the named storage pool,
these processes will continue migration.
User response: Start a version of the server program

that is at the same level as the prior server program
used.
ANR0996W
The information on disk was recorded

by a down-level version of the server
program; re-installation is required to
use this version.

discovered that the disk information was written by an
earlier version of the server program and is not
compatible with this version.
User response: Install this version of the server to
bring the information up to the level of the program
being used.
User response: If possible, correct the condition that

has caused delayed migration.
ANR1003I
Migration retry delay ended; checking

migration status for storage pool storage
pool name.
Explanation: Because migration for the indicated

storage pool had been delayed due to a problem, the
system waited before retrying. The retry wait period
has ended, and the system will now retry migration.
System action: Migration processing for the storage
pool resumes.
107
ANR1004I ANR1020W
ANR1004I
ANR1014W
Server formatting complete, database

ready for loading.
The pool type storage pool pool name is

either not available, or does not have
enough space for a simultaneous write
operation.
Explanation: The server formatting procedure has

completed successfully. The server is ready to be
loaded by issuing the DSMSERV LOADDB or the
DSMSERV RESTORE DB command.
Explanation: During a backup, archive, client

migration, or import operation that is using
simultaneous write, the server cannot write data to the
specified storage pool. Possible reasons include:
System action: Server completes formatting

processing.
v The storage pool is unavailable.
User response: The DSMSERV LOADDB or the

DSMSERV RESTORE DB command is required to load
the database before the server will be ready for use. For
complete details on these commands, refer to the
Administrators Reference.
ANR1013I
During a store operation, the server is

switching to a next pool in the storage
hierarchy. The next storage pool will
inherit the simultaneous write
configuration from the destination
primary storage pool.
v There is not enough space available in the specified

storage pool.
System action: The result of the simultaneous write
operation depends on the setting of the
COPYCONTINUE attribute of the original destination
primary pool destination:
v If the value of the COPYCONTINUE attribute of the
destination primary pool is YES, the server will stop
writing to the failing copy pool for the remainder of
the session, but continue storing files into a primary
pool in the storage hierarchy and any other
remaining copy pools.
destination primary pool is NO, the server will fail
the transaction and discontinue the operation.
Explanation: If during a backup, archive, client

migration, or server import operation, the server must
write data to a next pool in a storage pool hierarchy,
the following rules will apply:
Refer to the Administrators Guide for details about the

simultaneous write COPYCONTINUE attribute.
1. If the destination storage pool specified in the

management class copy group has one or more
copy storage pools associated with it for
simultaneous write operations:
User response: Ensure the copy storage pool is set for

READWRITE access. If needed, make more space
available in the copy storage pool. After the problem is
corrected, take one of the following actions:
a. The server will write the data to the next storage

pool and to the copy pools that are associated
with the original destination primary storage
pool.
b. The setting of the COPYCONTINUE attribute of
the original destination primary pool will be
inherited by the next pool.
c. If the next pool is configured for simultaneous
write operations, the copy storage pools
associated with the next pool will be ignored as
well as the value of its COPYCONTINUE
attribute.
2. If the primary storage pool specified in the
management class copy group does not have copy
pools associated with it for simultaneous write
operations:
a. The server will write the data to the next storage
pool.
b. If the next pool is configured for simultaneous
write operations, the copy pools associated with
the next pool will be ignored.
System action: The server operation continues.
User response: None. Refer to the Administrators
Guide for details about simultaneous write
configurations.
108

destination primary pool is YES, issue the BACKUP
STGPOOL commands to back up any files in
primary storage pools in the storage pool hierarchy
that have not been copied to the copy pool that
failed.
destination primary pool is NO, run the
simultaneous write operation again.
ANR1020W
Migration process process ID terminated

for storage pool storage pool name process canceled.
Explanation: During migration for the indicated

storage pool, a process performing the migration has
been canceled.
System action: The migration process is terminated. If
other migration processes are executing for the named
storage pool, these processes will continue migration.
ANR1021W ANR1028W
ANR1021W

for storage pool storage pool name storage media inaccessible.

storage pool, a required volume could not be mounted.
System action: The indicated migration process ends.
The server waits for the retry period to expire and then
tries the migration again. If other migration processes
are executing for the named storage pool, these
processes will continue migration.
ANR1022W

for storage pool storage pool name excessive read errors encountered.

storage pool, read errors occur that prevented the
migration from continuing.
User response: If possible, correct the cause of the
read errors.
ANR1023W

for storage pool storage pool name excessive write errors encountered.

storage pool, write errors occur that prevent the
write errors.
ANR1024W

for storage pool storage pool name - data
transfer interrupted.

interruption.
ANR1025W

for storage pool storage pool name insufficient space in subordinate storage
pool.

storage pool, the server cannot move the data from the
storage pool, because there is not enough space on the
next storage pool to hold it.
tries the migration again.
User response: Make more space available in the next
storage pool, or use the UPDATE STGPOOL command
to change the next storage pool to one with more space.
ANR1026W

for storage pool storage pool name unable to move file to subordinate
storage pool due to exclusion by size.

storage pool, the server cannot move the data from the
storage pool, because a file is larger than what is
allowed on the next storage pool.
User response: Use the UPDATE STGPOOL command
to change the next storage pool maximum file size or to
change the next storage pool target.
ANR1027W

for storage pool storage pool name sufficient recovery log space is not
available.

storage pool, the server runs out of recovery log space.

storage pool, a data transfer operation was interrupted
and could not be continued.
User response: If necessary, make more server

recovery log space available.

ANR1028W

for storage pool storage pool name sufficient database space is not
available.

storage pool, the server runs out of database space.
109
ANR1029W ANR1040I
database space available.

ANR1029W

for storage pool storage pool name - lock
conflict.

storage pool, the server needs to obtain a lock that is
not available.
User response: Wait for the server to retry the
migration.
ANR1030W

for storage pool storage pool name - thread
resource not available.

storage pool, the server cannot start a thread for the
migration process.
migration. If the error persists, it may indicate a
shortage of server memory.
ANR1031W

for storage pool storage pool name sufficient memory is not available.

storage pool, there is not enough server memory
available.
User response: If necessary, make more memory
available to the server.
ANR1032W

for storage pool storage pool name internal server error detected.

storage pool, the server encounters an internal error.
110
ANR1033W

for storage pool storage pool name transaction aborted.

storage pool, the server detected an error while
attempting to commit a transaction. This message
should be preceded by other messages that give
additional information about the failed transaction.
transaction.
ANR1034W
Files stored on volume volume name

cannot be migrated - volume is offline
or access mode is unavailable or
destroyed.
Explanation: During migration, files on the indicated

volume cannot be migrated either because the volume
has been varied offline or because of the volumes
access mode.
System action: The server continues migration
processing, but skips files stored on the indicated
volume.
User response: If necessary, use the VARY ON or
UPDATE VOLUME command for this volume.
ANR1040I
Space reclamation started for volume

volume name, storage pool storage pool
name (process number process ID).
Explanation: The percentage of reclaimable space on

the volume shown has reached the reclaim percentage
specified for the storage group; as a result, data from
the volume is moved to another volume so that the
volume can be reclaimed.
System action: The server starts volume space
reclamation.
ANR1041I ANR1056E
ANR1041I
Space reclamation ended for volume

volume name.
Explanation: Space reclamation for the volume named

is complete.
other reclamation processes are running, these

processes will continue the reclamation.
to change the value of the MAXSIZE parameter for the
storage pool. Specify the value as NOLIMIT, or specify
a value larger than the largest file to be reclaimed.

ANR1053E
ANR1042I
Space reclamation for storage pool

storage pool name will be retried in
number of seconds seconds.

attempting space reclamation for the named storage
pool, reclamation stops but will be retried after the
time period shown. After a number of unsuccessful
retries, the process will be automatically cancelled.
System action: The system waits for the specified
period and then retries space reclamation for the
storage pool.
has stopped reclamation.
ANR1043I
Space reclamation retry delay ended;

checking volume reclamation status for
Explanation: Because space reclamation for the

indicated storage pool had been stopped due to a
problem, the system waited before retrying. The retry
wait period has ended, and the system can now retry
space reclamation.
System action: Reclamation for the pool begins.
ANR1044I
Removable volume volume name is

required for space reclamation.
Command: Invalid process number processIdvalue
Explanation: A QUERY EXPORT command was

issued that specifies an invalid process number.
command.
process number.
ANR1054E
Command: Invalid export operation state

- export state
Explanation: A QUERY EXPORT command was

issued that specifies an invalid export state.
command.
export operation state.
ANR1055E
Command: Invalid export session

identifier name - export sess name.
Explanation: The issued command specifies an invalid

export session identifier.
command.
export session identifier.
Explanation: During space reclamation processing, the

server determines that a removable volume is required
in order to complete processing.
ANR1056E
System action: The server attempts to mount the

removable volume.
Explanation: The command failed because of an

invalid combination of arguments.
User response: Respond to any mount request for the

indicated volume.

operations continue.
ANR1045E
Reclamation has ended for volume

volume name. The files on the volume are
too large for the target storage pool,
storage pool name.
command name: The PROCESS parameter

is not valid if an export identifier is
specified.
User response: Reissue the command with a valid set

of parameters. For information on valid values for the
command parameter, refer to the :cit.ADSM
platform.
Explanation: During reclamation for the indicated

volume, the server cannot move the data from the
volume because a file is larger than allowed for the
indicated storage pool.
System action: Reclamation of the volume stops. If
111
ANR1057E ANR1065I
ANR1057E
command name: The PROCESS parameter

is not valid when the STATE parameter
is specified with a value of
INITIALIZING or SUSPENDED
Explanation: The command failed because of an

invalid combination of arguments.
User response: Reissue the command with a valid set
of parameters. For information on valid values for the
command parameter, refer to the :cit.ADSM
platform.
ANR1058E
command name: TODATE must be

specified when TOTIME is specified.
Explanation: A command supporting the TODATE

and TOTIME parameters was issued with the TOTIME
parameter specified but without the TODATE
parameter. When the TOTIME parameter is used, the
TODATE parameter must be specified.
ANR1061W
Error initiating space reclamation for

storage pool storage pool name - sufficient
Explanation: During an attempt to initiate space

reclamation for the indicated storage pool, there is not
enough server memory available.
System action: Space reclamation stops. The server
waits for the retry period to expire and then tries the
reclamation again.
ANR1062W

storage pool storage pool name - internal
server error detected.
Explanation: During an attempt to initiate space

reclamation for the indicated storage pool, an internal
server error is encountered.
will wait for the retry period to expire and then tries
the reclamation again.

User response: Reissue the command and specify both

the TODATE and TOTIME parameters.
ANR1063I
ANR1059I
Selective restore of NAS node nodename,

file system file system, started as process
process ID by administrator administrator.
Specified files and/or directory trees
will be restored to destination
destination.
Explanation: A restore is started for the indicated file

system of a NAS node. The operation is initiated by the
administrator shown. Selected files and/or directory
trees specified by the administrator will be restored to
the indicated destination.
System action: The indicated process is started.
ANR1060W

storage pool storage pool name - lock
conflict.
Explanation: While attempting to initiate space

reclamation for the indicated storage pool, the server
needs to obtain a lock that is not available.
waits for the retry period to expire and then tries the
reclamation again.
reclamation.
112
Full backup of NAS node nodename, file

system file system, started as process
Explanation: A full backup is started for the indicated

file system of a NAS node. The operation is initiated by
the administrator shown.
ANR1064I
Differential backup of NAS node

nodename, file system file system, started
as process process ID by administrator
administrator.
Explanation: A differential backup is started for the

indicated file system of a NAS node. Only files that
have changed since the last full backup will be
processed. The operation is initiated by the
administrator shown.
ANR1065I
Restore of NAS node nodename, file

A full image for this file system will be
restored to destination destination.

ANR1066I ANR1075E
administrator shown. The restore will be performed
using a full image of this file system. The file system
will be restored to the indicated destination.
errors and restart the operation.

ANR1071E

ANR1066I
Restore of NAS node nodename, file

A full image plus a differential image
for this file system will be restored to
destination destination.

administrator shown. The restore will be performed
using a full image plus a differential image of this file
system. The file system will be restored to the indicated
destination.
ANR1067I
Operation process process ID completed.
Explanation: During the indicated operation, read

errors prevent the operation from continuing.
System action: The indicated process ends.
errors and restart the operation.
ANR1072E
Operation process process ID terminated insufficient space in destination storage

pool.
Explanation: During the indicated operation, there is

not enough space available in the destination storage
pool.
User response: Make more space available in the
storage pool and restart the operation.
ANR1073E
Explanation: The indicated operation completed.

Operation process process ID terminated read errors encountered.
Operation process process ID terminated sufficient recovery log space is not

available.

server runs out of recovery log space.
ANR1068W
Operation process process ID terminated process cancelled.
Explanation: During the indicated operation, a

background process was cancelled.

ANR1074E

ANR1069E
Operation process process ID terminated insufficient number of mount points

available for removable media.

server could not allocate sufficient mount points for the
volumes required.
available.
Operation process process ID terminated sufficient database space is not

available.

server runs out of database space.
ANR1075E
Operation process process ID terminated lock conflict.

server needs to obtain a lock that is not available.
ANR1070E
Operation process process ID terminated write errors encountered.
User response: Restart the operation.
Explanation: During the indicated operation, write

errors prevent the operation from continuing.
113
ANR1076E ANR1084E
ANR1076E
Operation process process ID terminated sufficient memory is not available.
Explanation: During the indicated operation, not

enough server memory is available.
available to the server, and then restart the operation.
ANR1077E
Operation process process ID terminated transaction aborted.

server detected an error while attempting to commit a
transaction. This message should be preceded by other
messages that give additional information about the
failed transaction.
transaction.
ANR1078E
Operation process process ID terminated internal server error detected.

server encounters an internal error.
ANR1081E
Explanation: During space reclamation for the

indicated volume, a required volume cannot be
mounted.
System action: Space reclamation of the volume stops.
If other reclamation processes are executing, these
ANR1082E

If other reclamation processes are running, these
available.
ANR1083E

Server-free backup of node nodename,
file system file system, started as process
Explanation: The administrator initiates a server-free

backup of the nodes file system.
Space reclamation is ended for volume

volume name. There is an insufficient
number of mount points available for
removable media.

indicated volume, the server could not allocate
sufficient mount points for the volumes required.
ANR1079I

volume name. Storage media is
inaccessible.

volume name. Excessive read errors were
encountered.

indicated volume, read errors occur that prevent
reclamation from continuing.
User response: If possible, determine and correct the
cause of the read errors.

ANR1084E
ANR1080W

volume name. The process is canceled.

volume name. Excessive write errors were
encountered.

indicated volume, the process performing the
reclamation has been canceled.

indicated volume, write errors occur that prevent
reclamation from continuing.



cause of the write errors.
114
ANR1085E ANR1093E
ANR1085E

volume name. Data transfer was
interrupted.

indicated volume, a data transfer operation has been
interrupted and cannot be continued.
cause of the interruption.
ANR1086E

volume name. There is insufficient space
in storage pool.

indicated volume, the server determines that data
cannot be moved from the volume due to insufficient
space on other volumes in the storage pool.
User response: Make more space available on other
volumes in the storage pool.
ANR1087E

volume name. Sufficient recovery log
space is not available.

indicated volume, the server runs out of recovery log
space.

User response: Wait for the server to try the
reclamation again.
ANR1090E

indicated volume, the server cannot start a thread for
the reclamation process.
User response: Wait for the server to try the
reclamation again. If the error persists, it might indicate
a shortage of server memory.
ANR1091E
ANR1088E

volume name. Sufficient database space is
not available.

indicated volume, the server runs out of database
space.
System action: Space reclamation stops.
ANR1089E

volume name. There is a lock conflict.

indicated volume, the server needed to obtain a lock
that is not available.

volume name. Sufficient memory is not
available.

indicated volume, there was not enough server
memory available.
ANR1092E
System action: Space reclamation stops.


volume name. Thread resource is not
available.

volume name. An internal server error
was detected.

indicated volume, the server encounters an internal
error.
ANR1093E

volume name. The transaction is ended.

indicated volume, the server detected an error while
attempting to commit a transaction.
transaction.
115
ANR1094E ANR1101I
ANR1094E
Invalid destination storage pool storage

pool name specified for storage of an
object using data mover data mover.
Explanation: While attempting to store an object using

the indicated data mover, the server determined that
the indicated storage pool was invalid for this
operation. The indicated storage pool is used because it
is specified as the copy group destination of the
assigned management class.
ANR1096E
Operation process process ID terminated storage media inaccessible.
Explanation: During the indicated operation, a

required volume cannot be mounted.
User response: If possible, correct the problem and
restart the operation.
This storage pool could be invalid for any of the

following reasons:
ANR1097E
v The storage pool is not defined
Explanation: During the indicated operation, a data

transfer operation is interrupted and cannot be
continued.
v The storage pool is a random-access storage pool and

this operation requires a sequential-access storage
pool
v The storage pool is not a primary storage pool
Operation process process ID terminated data transfer interrupted.
v The storage pool has a NATIVE or NONBLOCK data

format, which is not supported for this operation
User response: If possible, correct the problem and

restart the operation.
v The storage pool is not a NONBLOCK data format,

which is required for server-free operations
ANR1098E
v The data format of the storage pool does not match

the data format of the data mover
User response: This message usually indicates a
configuration problem with either the storage pool or
the policy. Ensure that the destination storage pool has
appropriate attributes, including data format, for this
operation. Check the copy group of the assigned
management class. If the destination is incorrect, either
assign a new management class, or change the
destination in the copy group and activate the changed
policy. Also, consider whether you must define a new
storage pool or data mover.
ANR1095E
Data mover operation for node node

name and file space filespace name cannot
be started - an operation involving this
node and file space is already in
progress.
Explanation: A request has been made to use a data

mover to perform an operation involving the indicated
node and file space. The indicated file space was either
specified as the source for a backup operation or the
destination location for a restore operation. However, a
data mover operation involving that node and file
space is already in progress; the indicated file space is
either the source for a currently running backup
operation or is the destination for a currently running
restore operation. To avoid possible conflicts, the new
operation is not performed.
User response: Allow the current operation to
complete before starting a new operation for this node
and file space.
116
Operation process process ID terminated file deleted from data storage during
retrieval.
Explanation: During the indicated operation, a file

was deleted from data storage during retrieval.
ANR1099E
Operation process process ID terminated thread resource not available.

server cannot start a thread.
User response: The problem may indicate a shortage
of memory. If necessary, make more memory available
to the server, and then restart the operation.
ANR1100I
Migration started for volume volume

name, storage pool storage pool name
(process number process ID).
Explanation: Because the high migration threshold for

the indicated storage pool has been exceeded,
migration of files from the volume shown begins.
System action: The system moves the data from this
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.
ANR1102I ANR1108W
ANR1102I

required for migration.
Explanation: During migration processing, the server

determines that a removable volume is required in
order to complete processing.
removable volume.
indicated volume.
ANR1103E
Operation process process ID terminated server-free input/output errors

encountered.
Explanation: During the indicated operation,

input/output errors were encountered which prevent
the operation from continuing.
User response: Check previous messages for problem
determination information.
ANR1104E
Operation process process ID terminated NDMP session errors encountered.

NDMP session with the NAS file server reported errors
which prevent the operation from continuing.
User response: Check the NDMP logs for the NAS file
server and, if possible, correct the cause of the errors
and restart the operation.
ANR1106W
An incorrect destination storage pool

storage pool name was specified for
storing a table of contents for an image.
A table of contents will not be created
for the image.
Explanation: While attempting to store an image

object, the server determined that the indicated table of
contents (TOC) destination storage pool was invalid.
The indicated storage pool is used because it is
specified as the copy group TOC destination of the
following reasons:
creation is preferred, but not required. A TOC will not

be created for the stored image object.
the policy. Ensure that the TOC destination storage
pool has appropriate attributes, including data format.
Check the copy group of the assigned management
class. If the TOC destination is incorrect, either assign a
new management class, or change the TOC destination
in the copy group and activate the changed policy.
ANR1107E
An incorrect destination storage pool

storage pool name was specified for
storage of a table of contents for an
image object. The backup operation
fails.
Explanation: While attempting to store an image

object, the server determined that the indicated table of
contents (TOC) destination storage pool was invalid.
The indicated storage pool is used because it is
specified as the copy group TOC destination of the
following reasons:
v The storage pool has a data format other than
NATIVE or NONBLOCK
the policy. Ensure that the TOC destination storage
pool has appropriate attributes, including data format.
Check the copy group of the assigned management
class. If the TOC destination is incorrect, either assign a
new management class, or change the TOC destination
in the copy group and activate the changed policy.
ANR1108W
The server is unable to create a table of

contents for node node name, file space
file space in storage pool storage pool name.
Explanation: While attempting to create a table of

contents (TOC) for the specified node and file space in
the indicated TOC destination pool, a failure occurred.
System action: The operation continues because TOC
be created for the stored image object.
User response: Look for previous messages giving a
specific reason for the failure. Take corrective action as
appropriate.

v The storage pool has a data format other than
NATIVE or NONBLOCK
117
ANR1109W ANR1115W
ANR1109W
Command: A table of contents was

requested, but there is no table of
contents destination storage pool
specified. The table of contents will not
be created, but the operation continues.
ANR1112W
Command: No table of contents

destination storage pool available for
backup set for node Node name (data
type data type). The table of contents
will not be created.
Explanation: While preparing to create a table of

contents (TOC), the server determined that the TOC
destination storage pool is not specified in the backup
copy group for the assigned management class.


be created.

be created.
User response: This message indicates a configuration

problem with the policy. Either assign a new
management class with appropriate attributes, or
correct the assigned management class by setting the
TOC destination in the backup copy group and
activating the changed policy.

activating the changed policy.
ANR1110E
Command: A table of contents was

requested, but there is no table of
contents destination storage pool
specified. The table of contents can not
be created and the operation fails.
ANR1113E
Command: No table of contents

destination storage pool available for
backup set for node Node name (data
type data type). The backup set will not
be generated.



activating the changed policy. If a TOC is not required,
change the value of the TOC parameter on the
command.

activating the changed policy. If a TOC is not required,
change the value of the TOC parameter on the
command.
ANR1111E
Command: An incorrect message number,

message number, was specified.
Explanation: A MSGSTACKTRACE ENABLE or

MSGSTACKTRACE DISABLE command has been
entered that specifies an invalid message number.
Messages must be between 3 and 8 digits. No letters
are allowed on message numbers.
command.
message number.
ANR1114E
Command: No nodes or data types are

eligible for backup set generation.
Explanation: None of the specified nodes or data

types are eligible to be included in the backup set.
User response: Check previous messages for problem
determination information.
ANR1115W
Error initiating migration for storage

pool storage pool name - lock conflict.
Explanation: While trying to start migration for the

indicated storage pool, the server needs to obtain a lock
that is not available.
System action: Migration stops. The server waits for
118
ANR1116W ANR1124E
the retry period to expire and then tries the migration
again.
migration.
ANR1116W

pool storage pool name - sufficient

indicated storage pool, there is not enough server
memory available.
again.
ANR1117W

pool storage pool name - internal server
error detected.

indicated storage pool, the server encounters an
internal error.
again.
ANR1118I
Command: Table of contents successfully

generated for node Node name, backup
set backup set name.
Explanation: You requested a table of contents to be

generated for the specified backup set and data type.
The table of contents was successfully generated.
ANR1120W

volume, the process performing the migration has been
canceled.
System action: The migration process stops. If other
migration processes are running, these processes will
continue migration.
ANR1121E
ANR1119W
Command: Table of contents already

exists for node Node name, backup set
backup set name (data type data type). The
table of contents will not be created.
Migration is ended for volume volume

name - storage. Media is inaccessible.

volume a required volume cannot be mounted.
System action: Migration of the volume stops. If other
continue migration.
ANR1122E

name. An insufficient number of mount
points are available for removable
media.

volume the server could not allocate sufficient mount
points for the volumes required.
continue migration.
available.
ANR1123E


name. The process is canceled.

name. Excessive read errors were
encountered.

volume, read errors occurred that prevent the migration
from continuing.
continue migration.
Explanation: You requested a table of contents to be

generated for the specified backup set and data type,
but the table of contents already exists.

read errors.
System action: The server will not generate a table of

contents for this backup set and data type.
ANR1124E
User response: If the specified backup set name and

data type are not correct, re-issue the command with
the correct parameters.

name. Excessive write errors were
encountered.

volume, write errors occurred that prevent the
119
ANR1125E ANR1133E
continue migration.

write errors.
ANR1129E
ANR1125E

name. Data transfer is interrupted.

volume a data transfer operation was interrupted and
could not be continued.
continue migration.
ANR1126E

name. There is insufficient space in
subordinate storage pools.

volume because there is not enough space on the next
storage pool to hold it.
continue migration.
storage pool, or use the UPDATE STGPOOL command
to change the next storage pool to one with more space.
ANR1127E

name. - The server is unable to move
files to subordinate storage pools
because the files are too large.

volume because a file size is larger than allowed on the
next storage pool.

name. Sufficient database space is not
available.

volume pool, the server runs out of database space.
System action: Migration stops.
ANR1130E

name. There is a lock conflict.

volume, the server needs to obtain a lock that is not
available.
continue migration.
User response: Wait for the server to try the migration
again.
ANR1131E

name. A thread resource is not available.

volume, the server cannot start a thread for the
migration process.
continue migration.
User response: Wait for the server to try the migration
again. If the error persists, it might indicate a shortage
of server memory.
ANR1132E

name. Sufficient memory is not
available.

continue migration.

volume, there is not enough server memory available.

change the next storage pool target.

ANR1128E

name. Sufficient recovery log space is
not available.
ANR1133E

name. An internal server error is
detected.

volume, the server runs out of recovery log space.

volume, the server encounters an internal error.

continue migration.
120
ANR1134E ANR1146W
ANR1134E
ANR1142I
Migration is ended for storage pool

storage pool name. There is an insufficient
removable media.

storage pool the server could not allocate sufficient
mount points in the next storage pool.
again.
available.
ANR1135E

name. The transaction is ended.

volume, the server detected an error while attempting
to commit a transaction.
continue migration.
transaction.
ANR1136W
Operation process process ID completed There is no data to process for the

differential backup of NAS node node
name, file space file space.
Explanation: The NAS file server reported zero bytes

stored at the conclusion of an NDMP backup of the
specified file space. The command ends without
updating the servers database.
Explanation: As a result of a MOVE DATA command,

data moves from the volume indicated to new volumes;
the message shows the total number of clusters (data
objects) on the volume and the current cluster being
processed.
ANR1143W
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.
Move data process terminated for

volume volume name - process canceled.
Explanation: During move data processing for the

indicated volume, the process performing the move
data was canceled. It is possible that the server may
issue this message more than once while the server is
ending this process.
System action: The server ends the MOVE DATA
command.
ANR1144W

volume volume name - storage media
inaccessible.

indicated volume, a required volume cannot be
mounted.
command.
ANR1145W

ANR1140I
Moving data for collocation cluster

cluster number of total clusters on volume
volume name.

volume volume name - insufficient
removable media.

indicated volume, the server could not allocate
sufficient mount points for the volumes required.
command.

available.
ANR1141I
ANR1146W
Move data process ended for volume

volume name.
Explanation: The MOVE DATA command for the

volume shown completes.

volume volume name - excessive read
errors encountered.

121
ANR1147W ANR1153W
indicated volume, read errors occurred that prevented
the move from continuing.
command.
allowed on the next storage pool.

System action: The server ends the MOVE DATA or
MOVE NODEDATA command.

read errors and then reissue the MOVE DATA
command.

change the next storage pool target, and then reissue
the MOVE DATA or MOVE NODEDATA command.
ANR1147W
ANR1151W

volume volume name - excessive write
errors encountered.

volume volume name - sufficient recovery
log space is not available.

indicated volume, write errors occurred that prevented
the move from continuing.

indicated volume, the server runs out of recovery log
space.

command.

command.

write errors and then reissue the MOVE DATA
command.

ANR1152W
ANR1148W

volume volume name - data transfer
interrupted.

indicated volume a data transfer operation was
interrupted and could not be continued.
command.

indicated volume, the server runs out of database
space.
command.
ANR1153W
ANR1149W

volume volume name - insufficient space
in target storage pool.

indicated volume, the server cannot move the data
from the volume, because there is not enough space on
the destination storage pool to hold it or the access for
the storage pool is either unavailable or readonly.
command.
storage pool, or specify a storage pool with more space,
and reissue the MOVE DATA command.
ANR1150W

volume volume name - unable to move
file to target storage pool due to
exclusion by size.

indicated volume, the server cannot move the data
from the volume because a file size is larger than
122

volume volume name - sufficient database

volume volume name - lock conflict.
Explanation: During move data processing, the server

was unable to obtain the volume specified because a
lock was not available or a restartable restore is active
for data on the volume and has it locked. .
command.
User response: Check for restartable restores by
issuing the QUERY RESTORE command. If the volume
specified contains any data from the node and filespace
identifed by the QUERY RESTORE command, the
MOVE DATA command will fail. The restartable
restores must complete or be cancelled before the
MOVE DATA command can succeed.
If the volume does not contain data from the node and
filespace identified by the QUERY RESTORE command,
the reissue the MOVE DATA command.
ANR1154W ANR1162W
ANR1154W

volume volume name - thread resource
not available.

indicated volume, the server cannot start a thread for
the migration process.
command.
User response: Reissue the MOVE DATA command. If
the error persists, it may indicate a shortage of server
memory.
ANR1155W

volume volume name - sufficient memory
is not available.

indicated volume, there is not enough server memory
available.
command.
available to the server, and then reissue the MOVE
DATA command.
ANR1156W

volume volume name - internal server
error detected.

indicated volume, the server encounters an internal
error.
command.
ANR1157I

required for move process.
Explanation: During move data or move node data

processing, the server determines that the indicated
removable volume is required in order to complete
processing.
removable volume.
indicated volume.
ANR1160W
Transaction was aborted for volume

volume name.

fails.
ANR1161W
The move process is skipping a

damaged file on volume volume name:
Node node name, Type file type, File space
filespace name, File name file name.
Explanation: During the move process, a file is

encountered that was previously found to be damaged.
If this file is part of an aggregate, the entire aggregate
was previously marked damaged, possibly because an
error was detected for some other file within the
aggregate.
System action: The damaged file is not moved.
User response: Perform the following actions:
v Audit the indicated volume with FIX=NO to verify
that the file is damaged. The audit will reset the file
status if the file is found to be undamaged during
the audit. If the file is part of an aggregate, the audit
will reset the aggregate status if the entire aggregate
is found to be undamaged.
v If this volume is in a primary storage pool that has
previously been backed up to a copy storage pool,
attempt to restore damaged files by using the
RESTORE STGPOOL command.
ANR1162W
Space reclamation skipping damaged

file on volume volume name: Node node
name, Type file type, File space filespace
name, File name file name.
Explanation: During reclamation, a file is encountered

that was previously found to be damaged. If this file is
part of an aggregate, the entire aggregate was
previously marked damaged, possibly because an
integrity error was detected for some other file within
the aggregate.
System action: The damaged file is not moved.
User response: Audit the indicated volume with
FIX=NO to verify that the file is damaged. The audit
will reset the file status if the file is found to be
undamaged during the audit. If the file is part of an
aggregate, the audit will reset the aggregate status if
the entire aggregate is found to be undamaged. If this
volume is in a primary storage pool that has previously
been backed up to a copy storage pool, attempt to
restore damaged files by using the RESTORE
STGPOOL command.
Explanation: An error was detected during transaction

commit. This message should be preceded by other
failed transaction.
123
ANR1163W ANR1168W
ANR1163W
Offsite volume volume name still

contains files which could not be
moved.
Explanation: During processing of a MOVE DATA

command or reclamation, the server determined that
the indicated offsite volume contained one or more files
that could not be moved. One or more files could not
be copied from the other available volumes.
The server might not move some files if the storage
pool is collocated and the volume being moved or
reclaimed contains files that require different output
volumes. The server will skip these files and no
messages are issued identifying the skipped files. The
files are skipped to honor the collocation attribute of
the storage pool.
accessible by changing the access mode of the primary

pool or volume.
ANR1166E
Move Data for offsite volume cannot

copy damaged file in storage pool
storage pool name: Node node name, Type
file type, File space filespace name, fsId
filespace id, File name file name.
Explanation: A move data process for an offsite

volume cannot locate an undamaged copy of the
specified file in any storage pool accessible by the
server. If this file is part of an aggregate, the process
could not locate an undamaged copy of the aggregate
to which the file belongs.
System action: The file will skipped and will not be
moved from the offsite volume.
v Make the primary volumes available and reissue a

MOVE DATA command to reclaim the volume.
User response: The indicated storage pool is a

primary pool that contains a damaged copy of the file.
The only usable copy of the file may now only reside
on the offsite volume that was involved in the move
data process. If you bring this volume back onsite, you
can recreate the file in the primary pool by using the
RESTORE STGPOOL command. After the restore, you
can reissue the MOVE DATA command.
v Delete the files by using the DELETE VOLUME

command.
ANR1167E
User response: Check for messages indicating reasons

why files could not be moved. To complete the move
operation, you have several options:
v Bring the volume back on site and reissue a MOVE
DATA command to reclaim the volume.
If, however, the server is skipping files to honor the

collocation attribute of the storage pool, run the MOVE
DATA command, or wait until reclamation runs again.
In either case, the server will move files to the
appropriate output volumes until the volume being
moved or reclaimed is empty. It might take more than
one attempt to totally empty the volume.
ANR1165E
Error detected for file in storage pool

storage pool name: Node node name, Type
file type, File space filespace name, fsId
filespace id, File name file name.
Explanation: The server has detected an error for the

indicated file.
System action: The file will be marked damaged in
the server database, and will not be accessed for future
operations. If this file is part of an aggregate, the entire
aggregate will be marked damaged. If a usable copy of
the file exists in another storage pool, that copy may be
accessed for future operations involving the file.
User response: If the indicated storage pool is a
primary pool, and a usable copy of the file exists in a
copy storage pool, you can recreate the file in the
primary pool using the RESTORE STGPOOL command.
If the indicated storage pool is a copy storage pool, it is
possible that the primary copy of the file is usable, but
was not accessed because the access mode for the
primary storage pool or volume is unavailable. If this is
the case, the primary copy of the file may be made
124
Space reclamation for offsite volume

volume name cannot copy damaged file in
storage pool storage pool name: Node node
name,fsId filespace id , File name file name.
Explanation: A reclamation process of offsite volumes

cannot locate an undamaged copy of the specified file
in any storage pool accessible by the server. If this file
is part of an aggregate, the process could not locate an
undamaged copy of the aggregate to which the file
belongs.
System action: The file is skipped and will not be
primary pool that contains a damaged copy of the file.
The only usable copy of the file may now only reside
on an offsite volume that was involved in the
reclamation process, but was not totally reclaimed. If
you bring this volume back onsite, you can recreate the
file in the primary pool by using the RESTORE
STGPOOL command.
ANR1168W
Migration skipping damaged file on

volume volume name: Node node name,
Type file type, File space filespace name,
fsId filespace id, File name file name.
Explanation: During migration, a file is encountered

that was previously found to be damaged. If this file is
part of an aggregate, the entire aggregate was
previously marked damaged, possibly because an
ANR1169W ANR1173E
the aggregate.
System action: The damaged file will not be moved.
FIX=NO to verify that the file is damaged. The audit
will reset the file status if the file is found to be
undamaged during the audit. If the file is part of an
the entire aggregate is found to be undamaged. If this
volume is in a primary storage pool that has previously
been backed up to a copy storage pool, you can also
attempt to restore damaged files by using the
ANR1169W
Lock conflict on movement of offsite

file - file is skipped.
Explanation: During migration, reclamation, or move

data processing of a volume that is offsite, a copy of
the file that resides in a primary disk storage pool is
locked by another process.
System action: The file is skipped and the process will
try to find another copy of the file in a copy storage
pool. If another copy cannot be used, the move
operation on the volume may be incomplete.
User response: If a move operation was incomplete,
try repeating the operation.
ANR1170E
Out of Space in target copy storage

pool: copy storage pool name.
Explanation: During reclamation, or move data

processing of a volume that is offsite, there was no
volume available in the specified target copy storage
pool.
System action: The operation is terminated.
User response: Define volumes to the copy storage
pool or raise the MAXSCRATCH value.
ANR1171W
Unable to move files associated with

node node name, filespace filespace name
fsId filespace id on volume volume name
due to restore in progress.
Explanation: During movement of data (migration,

reclamation, move data) from a sequential volume, one
or more files were encountered that were locked by a
restore operation.
System action: The files are not moved, but are
skipped.
User response: Use the QUERY RESTORE
FORMAT=DETAILED command to determine if the
restore operation is active or is in restartable state. A
restartable restore operation will keep the files locked
from movement until the RESTOREINTERVAL is
reached. QUERY OPTION will display this interval.
You may wish to lower the RESTOREINTERVAL to

cause a restartable restore operation to be removed and
free up the locked files. The RESTOREINTERVAL is a
server option. If you received this message due to a
MOVE DATA operation, reissue the MOVE DATA
command after the restore operation has completed in
order to move any remaining files.
ANR1172E
Move Data for offsite volume cannot

copy file in storage pool storage pool
name: Node node name, Type file type, File
space filespace name, fsId filespace id, File
name file name.
Explanation: A move data process for an offsite

volume cannot locate a copy of the specified file in any
storage pool accessible by the server. If this file is part
of an aggregate, the process could not locate copy of
the aggregate to which the file belongs on an accessible
volume.
System action: The file will skipped and will not be
primary pool that should contain a primary copy of the
file. Perhaps the volume on which that file resides is on
a destroyed volume. The only usable copy of the file
may now only reside on the offsite volume that was
involved in the move data process. If you bring this
volume back onsite, you can recreate the file in the
primary pool by using the RESTORE STGPOOL
command. After the restore, you can reissue the MOVE
DATA command.
ANR1173E
Space reclamation for offsite volume(s)

cannot copy file in storage pool storage
pool name: Node node name, Type file type,
File space filespace name, fsId filespace id,
File name file name.
Explanation: A reclamation process of offsite volumes

cannot locate a copy of the specified file in any storage
pool accessible by the server. If this file is part of an
aggregate, the process could not locate a copy of the
aggregate to which the file belongs on an accessible
volume.
System action: The file is skipped and will not be
primary pool that should contain a copy of the file.
Perhaps the volume on which that file resides is on a
destroyed volume. The only usable copy of the file may
now only reside on an offsite volume that was involved
in the reclamation process, but was not totally
reclaimed. If you bring this volume back onsite, you
can recreate the file in the primary pool by using the
125
ANR1174W ANR1182I
ANR1174W
One or more cached files were not

deleted on volume volume name.
Explanation: The MOVE DATA command could not

delete one or more cached files on the disk volume
shown. Migration was probably running at the same
time, creating cached files while the MOVE DATA
command was trying to delete them.
System action: The MOVE DATA command ran to
completion.
User response: If you want the remaining cached files
removed from the disk volume, reissue the MOVE
DATA command.
ANR1175W
Volume volume name contains files which

could not be reclaimed.
Explanation: After reclamation of the indicated

volume, it still contains one or more files that could not
be reclaimed. These files were skipped because of read
errors, or because the files are marked damaged.
System action: The volume is marked unavailable so
it will not be chosen again for reclamation.
data from a primary storage pool to the indicated

active data.
System action: For every noncached, active file in the
primary pool, a copy is made in the active data pool, if
a copy of that file does not already exist.
ANR1179I
Explanation: A preview process has been started to

copy active data from a primary storage pool to the
indicated active data pool.
System action: Preview information about the COPY
ACTIVEDATA operation is collected and displayed, but
files are not copied.
ANR1180W
User response:
v Use the UPDATE VOLUME command to set the
volume access to readonly.
v Try using the MOVE DATA command to manually
reclaim the volume.
Preview of copying active files from

primary storage pool primary pool name to
active data pool active data pool name
Access mode for volume volume name

has been set to unavailable due to file
read or integrity errors.
Explanation: During processing of a storage pool

volume, input/output or other errors occur that force
the server to mark the volume unavailable for further
processing.
v If files still exist on the volume, audit the volume

using AUDIT VOLUME FIX=YES.
System action: The server sets the volume status to

unavailable.
v Try using the MOVE DATA command again.
User response: Correct the errors that set the volume

to unavailable, or use the DELETE VOLUME command
to remove it from the system.
v Use the RESTORE VOLUME command to restore

files marked damaged.
ANR1176I
Moving data for collocation set set

number of total sets on volume volume
name.
Explanation: As a result of a move operations, such as

MOVE DATA, MOVE NODEDATA, migration, or
reclamation, the server is moving data from the volume
indicated to new volumes. This message shows the
total sets of data on the volume to be processed.
Depending upon the collocation setting of the
destination storage pool, a set can be file spaces that
belong to the same collocation group, file spaces for a
node, or a single filespace.
ANR1178I
Copying active files from primary

storage pool primary pool name to active
data pool active data pool name started as
process process ID.
Explanation: A process has been started to copy active
126
ANR1181E
Diagnostic(ID): Data storage transaction

transaction ID was aborted.
Explanation: A database transaction failed because of

an error that was detected during data storage
processing. This message should be preceded by other
failed transaction.
System action: The server operation that encountered
this error during data storage processing fails.
transaction.
ANR1182I

required for a restore request from
session session id.
Explanation: A restore request will need a removable

volume. This message is issued as soon as the server
determines that the volume will be needed. A mount
request will be made when the volume is actually
ANR1183I ANR1211I
needed for processing. When the first pass
determination of needed volumes is complete, message
ANR1183I will be issued. However, it is possible that
additional volumes will be needed later, as indicated in
the explanation for message ANR1183I. This message is
not issued for DISK device class volumes nor is it
issued for FILE device class volumes.
System action: The server continues processing.
indicated volume.
ANR1183I
Initial determination of removable

volumes required for a restore request
from session session id is complete.
Additional volumes may still be
required.
Explanation: The first pass determination of needed

volumes is complete for the indicated restore session. It
is possible that additional volumes will be needed as
individual objects are restored. This can happen for a
variety of reasons. Examples of such reasons include: 1.
An object spanning from one volume to another, where
the second volume is not needed for any other objects
during this restore session. 2. An object is found to be
damaged and a copy storage pool volume is needed to
complete the restore. 3. A volume is unavailable and a
copy storage pool volume is needed to complete the
restore.
System action: The server continues processing.
User response: Respond to any mount request for any
additional volumes.
ANR1184I
Copy active data process process ID

ended for storage pool storage pool name.
Explanation: A COPY ACTIVEDATA process for the

named primary storage pool has ended.
ANR1186I
Explanation: The administrator initiates a restore of

the nodes file system. The restore will be performed
using a full image of this file system. The file system
will be restored to the indicated destination.
ANR1189I
System action: Unless this is a preview process, the

server attempts to mount the removable volume.
indicated volume.
ANR1199I
Explanation: While copying active data from the

indicated primary storage pool, a process performing
the operation has been canceled.
System action: If other copy active data processes are
executing for the named storage pool, these processes
continue.

required for audit process.
Explanation: During audit volume processing for the

indicated volume, the server determines that a
removable volume is required in order to complete
processing.
removable volume.
indicated volume.
ANR1210I

Copy active data process process ID
terminated for storage pool storage pool
name - process canceled.

required for copying active data.
Explanation: During processing of a COPY

ACTIVEDATA command, the server determines that a
removable volume is required.
ANR1185I
Restore of node nodename, file system file

system, started as process process ID by
administrator administrator. A full image
for this file system will be restored to
destination destination.
Backup of primary storage pool primary

pool name to copy storage pool copy pool
name started as process process ID.
Explanation: A process has been started to back up a

primary storage pool to the indicated copy storage
pool.
System action: For every noncached file in the
primary pool, a backup copy is made in the copy pool,
if a copy of that file does not already exist.
ANR1211I
Backup preview of primary storage pool

primary pool name to copy storage pool
copy pool name started as process process
ID.

back up a primary storage pool to the indicated copy
storage pool.
127
ANR1212I ANR1221E
System action: Preview information about the backup
operation is collected and displayed, but files are not
backed up.
ANR1212I
Backup process process ID ended for

Explanation: A backup process for the named primary

storage pool has ended.
ANR1216E
Explanation: During backup processing, a required

volume could not be mounted.
System action: The indicated backup process ends.
ANR1217E

ANR1213I
Backup process process ID terminated for

storage pool storage pool name - process
canceled.
Explanation: During backup of the indicated primary

storage pool, a process performing the backup has been
canceled.
System action: If other backup processes are executing
for the named storage pool, these processes continue.
ANR1214I
Backup of primary storage pool primary

pool name to copy storage pool copy pool
name has ended. Files Backed Up:
number of files, Bytes Backed Up: number
of bytes, Unreadable Files: number of
unreadable files, Unreadable Bytes: number
of bytes in unreadable files.
Explanation: Backup processing for the specified

storage pool has ended with the results shown.
User response: Examine previous messages to
determine whether all backup processes ended
successfully.
Backup preview of primary storage pool
primary pool name to copy storage pool
copy pool name has ended. Files Backed
Up: number of files, Bytes Backed Up:
number of bytes.
Explanation: Backup preview processing for the

specified storage pool has ended with the results
shown.
Command: Process process ID terminated insufficient number of mount points

Explanation: During backup processing, the server

could not allocate sufficient mount points for the
volumes required.
available.
ANR1218E
Command: Process process ID terminated excessive read errors encountered.
Explanation: During backup processing, read errors

occur that prevent the backup from continuing.
read errors and reissue the backup command.
ANR1219E
Command: Process process ID terminated excessive write errors encountered.
Explanation: During backup processing, write errors

write errors and reissue the backup command.
ANR1220E
ANR1215I
Command: Process process ID terminated storage media inaccessible.
Command: Process process ID terminated data transfer interrupted.
Explanation: During backup processing, a data

transfer operation was interrupted and could not be
continued.
interruption and reissue the backup command.
ANR1221E
Command: Process process ID terminated insufficient space in target storage pool

pool name.

cannot copy data to the specified copy or active-data
storage pool because not enough space is available in
the specified copy or active-data storage pool, or, the
128
ANR1222E ANR1230I
access for the copy or active-data storage pool is either
unavailable or readonly.
available to the server, and then reissue the backup

command.

User response: Make more space available in the copy
or active-data storage pool and reissue the backup
command, or reissue the backup command and specify
another copy or active-data storage pool with more
space.
ANR1222E
Command: Process process ID terminated sufficient recovery log space is not

available.

runs out of recovery log space.
ANR1223E
Command: Process process ID terminated sufficient database space is not

available.

runs out of database space.
ANR1227E

encounters an internal error.
ANR1228I
ANR1224E
Command: Process process ID terminated lock conflict.

User response: Reissue the backup command.
ANR1225E
Command: Process process ID terminated thread resource not available.

cannot start a thread.
User response: Reissue the backup command. If the
error persists, it may indicate a shortage of server
memory.
ANR1226E
Command: Process process ID terminated sufficient memory is not available.
Explanation: During backup processing, not enough

server memory is available.

required for storage pool backup.
Explanation: During processing of a BACKUP

STGPOOL command, the server determines that a
removable volume is required.
indicated volume.
ANR1229W

Command: Process process ID terminated internal server error detected.
Volume volume name cannot be backed

up - the volume is offline, in use by
another process, not currently
mountable, or access mode is
unavailable or destroyed.
Explanation: During storage pool backup, a volume

cannot be backed up because of one of the following:
v The volume is offline
v The volume is in use by another process
v The volume cannot be mounted
v The access mode of the volume does not allow the
operation
System action: The server continues backup
processing, but skips the indicated volume.
User response: If necessary, use the VARY ON or
UPDATE VOLUME command for this volume and
restart the backup command. If the volume is in use by
another process, wait for that process to complete and
then restart the backup. If the volume is not currently
mountable, verify that the drive can mount the volume
and retry the command.
ANR1230I
Restore of primary storage pool primary

pool name started as process process ID.
Explanation: A process has been started to restore the

indicated primary storage pool.
System action: Non-cached files that reside in the
named primary storage pool are restored if either of the
following criteria are met:
v The file is stored on a volume whose access mode is
destroyed
129
ANR1231I ANR1239I
v The primary file has been identified as having
data-integrity errors during a previous operation
ANR1235I

ANR1231I
Restore preview of primary storage pool

primary pool name started as process
process ID.

restore a primary storage pool.
System action: Preview information about the restore
restored. The restore preview includes noncached files
that reside in the specified primary storage pool and
that meet either of the following conditions:
v The file is stored on a volume whose access mode is
destroyed
v The primary file has been identified as having
data-integrity errors during a previous operation
Restore process process ID ended for

volumes in storage pool storage pool
name.
Explanation: A restore process for volumes in the

named primary storage pool has ended.
ANR1236I
Restore process process ID terminated for

storage pool storage pool name - process
canceled.
Explanation: During restore of the indicated primary

storage pool, a process performing the restore has been
canceled.
System action: If other restore processes are executing
for the named storage pool, these processes continue.

ANR1237I
ANR1232I
Restore of volumes in primary storage

pool primary pool name started as process
process ID.
Restore process process ID terminated for

volumes in storage pool storage pool name
- process canceled.
Explanation: A process has been started to restore one

or more volumes in the indicated primary storage pool.
Explanation: During restore of volumes in the

indicated primary storage pool, a process performing
the restore has been canceled.
System action: Noncached files that reside on selected

volumes in the primary storage pool are restored.
System action: If other restore processes are executing

for the volumes, these processes continue.
ANR1233I
ANR1238I
Restore preview of volumes in primary

storage pool primary pool name started as
process process ID.

restore one or more volumes in the indicated primary
storage pool.
System action: Preview information about the restore
restored. The restore preview includes noncached files
that reside on selected volumes in the primary storage
pool.
ANR1234I
Restore process process ID ended for

Explanation: A restore process for the named primary

Restore of primary storage pool primary

pool name has ended. Files Restored:
number of files, Bytes Restored: number of
bytes, Unreadable Files: number of
Explanation: Restore processing for the specified

determine whether all restore processes ended
successfully.
ANR1239I
Restore preview of primary storage pool

primary pool name has ended. Files
Restored: number of files, Bytes Restored:
number of bytes.
Explanation: Restore preview processing for the

shown.
130
ANR1240I ANR1249E
ANR1240I
Restore of volumes in primary storage

pool primary pool name has ended. Files
Restored: number of files, Bytes Restored:
number of bytes, Unreadable Files: number
of unreadable files, Unreadable Bytes:
number of bytes in unreadable files.
Explanation: Restore processing for volumes in the

shown.
determine whether all restore processes ended
successfully.
ANR1241I
Restore preview of volumes in primary

storage pool primary pool name has
ended. Files Restored: number of files,
Bytes Restored: number of bytes.
Explanation: Restore preview processing for volumes

in the specified storage pool has ended with the results
shown.

read errors and reissue the restore command.
ANR1245E
Explanation: During restore processing, write errors

occur that prevent the restore from continuing.
System action: The indicated restore process ends.
write errors and reissue the restore command.
ANR1246E
Command: Process process ID terminated storage media inaccessible.
Explanation: During restore processing, a required

volume could not be mounted.
User response: Verify that the copy and primary
storage pools and volumes being accessed are available.
Check the ACCESS parameter for both of the storage
pools and all related volumes to ensure the ACCESS
state is not preventing access.
ANR1243E
Command: Process process ID terminated insufficient number of mount points

Command: Process process ID terminated data transfer interrupted.
Explanation: During restore processing, a data transfer

operation was interrupted and could not be continued.
interruption and reissue the restore command.
ANR1247E

ANR1242E
Command: Process process ID terminated excessive write errors encountered.
Command: Process process ID terminated 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.
User response: Make more space available in the
target primary storage pool, and then reissue the
restore command.
ANR1248E
Command: Process process ID terminated sufficient recovery log space is not

available.

runs out of recovery log space.

could not allocate sufficient mount points for the
volumes required.

ANR1249E

available.
ANR1244E
Command: Process process ID terminated excessive read errors encountered.
Explanation: During restore processing, read errors

Command: Process process ID terminated sufficient database space is not

available.

runs out of database space.
131
ANR1250E ANR1257W
ANR1250E
Command: Process process ID terminated lock conflict.

System action: The server continues restore

processing, but skips the indicated volume.
User response: If the volume is stored at an offsite
location, bring the volume onsite. Use the UPDATE
VOLUME command to change the access mode for the
volume and restart the restore command.
User response: Reissue the restore command.

ANR1256W
ANR1251E
Command: Process process ID terminated thread resource not available.

cannot start a thread.
User response: Reissue the restore command. If the
error persists, it may indicate a shortage of server
memory.
ANR1252E
Command: Process process ID terminated sufficient memory is not available.
Explanation: During restore processing, there is not

enough server memory available.
available to the server; and then reissue the restore
command.
ANR1253E
Command: Process process ID terminated internal server error detected.
Volume volume name contains files that

could not be restored.
Explanation: During processing of a RESTORE

STGPOOL or RESTORE VOLUME command, the server
determines that the indicated volume contains one or
more files that could not be restored. If this is a
preview operation, this message indicates that a
restorable backup copy cannot be found for one or
more files on the indicated volume. If this is an actual
restore operation, this message could result if any of
the following conditions exist for a file on the indicated
volume:
v A restorable backup copy cannot be found for the
file.
v A restorable backup copy of the file exists, but is
located on a copy storage pool volume whose access
mode is unavailable or offsite.
v During restore processing, a backup copy was
selected for restore processing, but was deleted or
moved before the file was actually restored. This
action could occur as a result of MOVE DATA,
DELETE VOLUME, AUDIT VOLUME FIX=YES, or
reclamation processing of a copy storage pool
volume while the restore was in progress.

encounters an internal error.
v A restorable backup copy of the file exists, but is on

a copy storage pool volume that cannot be accessed
since no drive path exists.

STGPOOL or RESTORE VOLUME command, the server
determines that a removable volume is required.
User response: If this was an actual restore operation,

check for messages indicating that files could not be
restored because a copy storage pool volume was
unavailable or offsite. Check to see if a move data,
delete volume, audit volume, or reclamation process
occurred for a copy storage pool while the restore was
in progress. If either of these conditions existed, correct
the situation and reissue the restore command.

ANR1257W
ANR1254I

required for restore processing.

indicated volume.
ANR1255W
Files on volume volume name cannot be

restored - access mode is unavailable
or offsite.

STGPOOL or RESTORE VOLUME command, files on a
copy storage pool volume cannot be restored because
of the volumes access mode.
132
Storage pool backup skipping damaged

name, fsId filespace id, File name file name.
Explanation: During storage pool backup, a file is

encountered that was previously found to be damaged.
If this file is part of an aggregate, the entire aggregate
was previously marked damaged, possibly because an
the aggregate.
System action: The damaged file will not be backed
up.
ANR1258W ANR1265E
FIX=YES. The audit will verify whether or not the file
is damaged and perform one of the following actions:
v If the the file is found to be undamaged, the audit
will reset the file status. If the file is part of an
the entire aggregate is found to be undamaged.
v If the file is found to be damaged and the file had
not previously been backed up to a copy storage
pool, the audit will delete the file.
v If the file is found to be damaged and the file has
previously been backed up to a copy storage pool,
the audit will report the file as damaged and you
must use the RESTORE STGPOOL command to
recover the file.
ANR1258W
Files on volume volume name needed for

move data cannot be accessed - access
mode is unavailable, offsite, or
destroyed.
Explanation: During a move data operation, files on a

storage pool volume cannot be copied because of the
volumes access mode. The server cannot move data on
a volume that has an access mode of unavailable,
offsite, or destroyed.
System action: The server continues move data
processing, but one or more files were not moved from
the volume.
User response: If the specified volume can be made
available, use the UPDATE VOLUME command to
change the access mode for the volume and reissue the
MOVE DATA or MOVE NODEDATA command.
ANR1259W
Files on volume volume name needed for

offsite reclamation cannot be accessed access mode is unavailable or offsite.
Explanation: During reclamation processing of an

offsite volume, files on a storage pool volume cannot
be copied because of the volumes access mode.
System action: The server continues reclamation, but
one or more files were not moved from an offsite
volume, which prevents it from being reclaimed.
User response: If the specified volume can be made
available, use the UPDATE VOLUME command to
change the access mode for the volume and initiate
reclamation again by updating the reclamation
threshold for the copy storage pool.
ANR1260W
Volume volume name contains one or

more damaged, primary files.
Explanation: This message is issued during RESTORE

STGPOOL processing. The indicated volume contains
one or more primary, noncached files that have
previously been found to be damaged.
System action: If this is not a preview operation, the

restore processing attempts to restore the damaged files
from copies located in a copy storage pool. If this is a
preview operation, no system action is taken.
User response: You can take the following actions:
v Issue the QUERY CONTENT command with
DAMAGED=YES to obtain a list of damaged files on
the indicated volume.
v Audit the indicated volume with FIX=NO to verify
that the files are damaged; the audit will reset the
status of any files that are found to be undamaged
during the audit.
v If this message was issued during a restore preview
operation, attempt to restore the damaged files using
the RESTORE STGPOOL command.
v Audit the indicated volume with FIX=YES to delete
the damaged files from the database.
ANR1263I
command: Processing completed

successfully.

command command has completed successfully.
System action: Processing for the command
completes. Statistics on the number and type of objects
message.
ANR1264I

completion.

message.
ANR1265E
Salvage volume command: Processing

data storage.

in accessing data storage while executing a salvage
volume operation.
resolve the error, retry the operation. If you cannot find
133
ANR1266E ANR1274I
the error, contact your service representative for
assistance in resolving the problem.
ANR1266E
Salvage volume command: Processing

terminated abnormally - volume not a
storage pool volume.

in accessing data storage while executing a salvage
volume operation.The error occurred because an
attempt has been made to access a volume that was not
a storage pool volume.
volume name.
ANR1267I
Salvage volume command: Processed

number volume(s).

command Salvage volume command inspected number
input volumes.
System action: Salvage processing for the command
completes. Server operation continues.
ANR1268I
Salvage volume command: Recovered

number byte(s).

command Salvage volume command recovered number
bytes worth of data.
ANR1269I
Salvage volume command: Recovered

number file(s).

command Salvage volume command recovered number
files.
ANR1270I
Salvage volume command: File (internal file

identifierinternal file identifier) recovered.

command Salvage volume command recovered a file. The
new file was given a new, system generated name
based on the internal file identifier and the name of the
volume from which the file was recovered. The internal
file identifier is the identifier by which the file was
134
known to the server before the file was deleted.

ANR1271I
Salvage volume command: * number bytes

recovered from volume volume.

command Salvage volume command recovered a file from
the volume volume. The number of bytes recovered from
the volume is listed.
ANR1272I
Salvage volume command: * File is

complete - it began and ended on
volume volume.

the volume volume. The file was completely contained
on volume.
ANR1273I

incomplete - it began on volume volume
but did not end.

the volume volume. The file was not completely
contained on volume. Although the file began on this
volume, it spanned out to a different volume.
ANR1274I

incomplete - it ended on volume volume
but did not begin there.

contained on volume. Although the file ended on this
volume, it spanned in from a different volume.
ANR1275I ANR1284I
ANR1275I

incomplete - it did not began or end on
volume volume.

contained on volume. It spanned in from one volume
and spanned out to a another.
value based on current sequential volume information.

ANR1280E
Command: Process process ID terminated transaction aborted.


detected an error while attempting to commit a
failed transaction.
ANR1276E
Command: Process terminated - sufficient

Explanation: During salvage processing, not enough

server memory is available.

transaction.
ANR1281E
System action: The salvage process ends.

available to the server, and then reissue the salvage
command.
ANR1277E
Command: Process terminated - the

default management class in the active
policy set in policy domain domain name
does not contain an archive copy group.
Unable to continue with salvage.

command Salvage volume command was unable to
recover any files because the default management class
in the active policy set in policy domain does not contain
an archive copy group.
Command: Process process ID terminated transaction aborted.

detected an error while attempting to commit a
failed transaction.
transaction.
ANR1282I
Logical occupancy is incorrect for

storage pool storage pool name. Logical
occupancy is being reset.
System action: The salvage process ends.
Explanation: The server has detected incorrect logical

occupancy information.
User response: Add an archive copy group to the

default management class in the active policy set of the
specified domain, and then reissue the salvage
command.
System action: The server recalculates the logical

occupancy value based on current storage pool
information.
ANR1278I
Occupancy is incorrect for storage pool

storage pool name. Occupancy is being
reset.
Explanation: The server has detected incorrect

System action: The server recalculates the occupancy
value based on current storage pool information.
ANR1279I
Occupancy is incorrect for volume name

volume name. Occupancy is being reset.
Explanation: The server has detected incorrect


ANR1283I
File count is incorrect for storage pool

storage pool name - file count is being
reset.
Explanation: The server has detected an incorrect

count of the number of files within this storage pool.
System action: The server will correct this
information.
ANR1284I
Move node data started as process

process ID.
Explanation: A process has been started to move data

by node.
System action: The server recalculates the occupancy

135
ANR1288I ANR1297E
System action: The indicated process has started.
User response: To query the progress of the process,
use the QUERY PROCESS command. To cancel the
background process, use the CANCEL PROCESS
command. Use the process ID number to specify this
process.
ANR1288I
Move node data process process ID

ended for storage pool storage pool name.
This warning message is only issued once per volume,

when this condition is detected when data is first
placed on the volume.
System action: The operation continues.
User response: Verify that the Tivoli Storage Manager
COPYGROUP attributes and the retention settings of
the Network Appliance file system are consistent with
your requirements for WORM volume storage.
Explanation: A move node data process for the named

ANR1296W
Explanation: This message might be issued during the

definition or updating of a storage pool, or during
BACKUP or RESTORE STGPOOL commands, or in
other such situations when it is determined that data
on WORM volumes might be moved to other media. It
names a storage pool that does not contain WORM
FILE volumes.

ANR1289I
Move node data process process ID

terminated for the storage pool storage
pool name - process canceled.
Explanation: During move node data processing in

the indicated storage pool, the process performing the
move node data has been canceled.
System action: If other move node data processes are
executing for the storage pool, these processes continue.
ANR1290I
Move node data from storage pool

storage pool name to storage pool storage
pool name has ended. Files Moved:
number of files, Bytes Moved: number of
bytes, Unreadable Files: number of
Explanation: Move node processing for the specified

storage pool has ended with the displayed results.
determine whether all move node data processes ended
successfully.
ANR1295W
An attempt to set end reclamation date

for WORM volume volume name to end
reclamation date failed. end reclamation
date set to SnapLock retention date.
Explanation: Tivoli Storage Manager computes and

attempts to set the end reclamation date for a volume
based on the RETMIN and RETVER COPYGROUP
attributes. When setting the end reclamation date for
the named volume, the Network Appliance SnapLock
file system was unable to fulfil the request. It was,
however, able to set the date to the Snaplock retention
date, which is farther in the future than the requested
date. This is probably due to how the SnapLock NAS
file servers retention date is configured.
136
Storage pool storage pool name does not

contain WORM FILE volumes.
When it is issued during the DEFINE and UPDATE

STGPOOL commands, it indicates that the storage pool
being defined or updated is being configured with
WORM FILE volumes (Reclamationtype is SnapLock),
but other storage pools being specified on the storage
pool definition (for example, the Next or Reclaim or
Copy storage pool parameters) do not contain WORM
FILE volumes (Reclamationtype is Threshold). Such
configurations might cause data on those WORM FILE
volumes to be moved to a storage pool that does not
support WORM FILE volumes.
For other situations, this message might be issued
when there will be a movement of data from a storage
pool with WORM FILE volumes (Reclamationtype is
SnapLock) to a storage pool that does not have WORM
FILE volumes (Reclamationtype is Threshold).
The server allows this type of movement, but the
customer needs to be aware that if data is moved from
a WORM FILE volume to another type of media, the
data may no longer be protected from inadvertent or
malicious deletion. In addition, if this data is on
WORM volumes to meet data retention and protection
requirements for certain legal purposes and is moved
to other media, the data might no longer meet those
requirements.
System action: The command continues.
User response: Verify that the storage pools being
used meet your requirements for data protection and
retention.
ANR1297E
Storage pools with

RECLAMATIONTYPE=SNAPLOCK can
only be defined on servers with archive
data retention protection enabled.
Explanation: Defining storage pools with

RECLAMATION=SNAPLOCK is only supported on a
server with archive data protection enabled.
ANR1298W ANR1306I
System action: The define storage pool command
fails.
ANR1301I
User response: Define the storage pool with

RECLAMATIONTYPE=THRESHOLD on this server. Or
else enable archive data retention protection on this
server, and try the command again.
Explanation: A VARY OFFLINE command has caused

a vary-off process to be started for the volume
specified.
VARY OFFLINE command initiated for

disk volume volume name.
System action: The volume is varied offline.

ANR1298W
The server encountered an error in

attempting to delete an object in a
Centera storage device. The Centera
representation of the name is Centera
object string. The server was keeping
track of the object in volume id volume
id. The return code received was return
code.
Explanation: The server failed to delete an object in a

Centera storage device after server records concerning
the object were deleted. The object is no longer
accessible through the server. The object continues to
occupy space in the Centera storage device. The return
code that is returned is either from the server interface
to Centera services, or it can be directly from the
Centera device.

ANR1302E
Disk volume volume name is already

online.
Explanation: A VARY ONLINE command specified a

volume that was already online.
ANR1303E
Disk volume volume name is already

offline.
Explanation: A VARY OFFLINE command specified a

volume that was already offline.
System action: The server continues operation, and

the object is logically deleted within the server, but
continues to occupy space in the Centera device.
User response: The server can continue to operate in

spite of this error. Centera service can be required if the
volume of unpurged objects becomes a problem.
ANR1304E
ANR1299E
The server encountered an invalid

storage format while attempting a
partial object retrieve for object
seg_id_hi,seg_id_lo.
Explanation: A partial object retrieve was attempted

on a file that was stored in a format that does not
support partial object retrieves.
System action: The transaction ends and the retrieve
request fails.
User response: Try the retrieve again, using a regular
or full retrieve instead of a partial object retrieve.
ANR1300I
VARY ONLINE command initiated for

disk volume volume name.
Explanation: A VARY ONLINE command has caused

a vary-on process to be started for the volume
specified.

Disk volume volume name is currently in
use.
Explanation: A VARY OFFLINE command specified a

volume that is currently in use and cannot be varied
offline at this time.
User response: Try the command again at a later time,
or attempt to determine how it is currently being used
and free it.
ANR1305I
Disk volume volume name varied online.
Explanation: The specified volume has been varied

online as the result of a VARY ONLINE command.
ANR1306I
Disk volume volume name varied online

(read-only).

online in read-only mode as the result of a VARY
ONLINE command.

137
ANR1307I ANR1314E
ANR1307I
Disk volume volume name varied offline.

offline as the result of a VARY OFFLINE command.
ANR1308W
Storage agent not sychronized with

server - restart needed.
Explanation: The storage agent has detected that a

policy, storage pool, device class, or other attributes
that is read from the server at initialization is no longer
valid.
System action: The operation of the storage agent
continues. Depending upon what has changed on the
server the storage agent behavior may be
unpredicatable and other failures may result.
User response: The storage agent should be halted
and restarted to synchronize the storage agent with the
server.
ANR1309W
Shred value zero for storage pool storage

pool name may render deleted data non
shreddable.
Explanation: This message is issued during the define

or update of a storage pool when a SHRED value of
zero has been found with a storage pool in the storage
pool hierachy.
The server allows this type of operation, but the
administrator needs to be aware that if data is stored or
moved to the affected storage pool, the data cannot be
shredded after deletion.
When it is issued during the DEFINE command, it
indicates that the storage pool definition is being
configured with a non zero SHRED value, however
other storage pools being specified on the definition
(for example, the Next or Reclaim or Copy storage pool
parameters) have a SHRED value of zero.
When issued during the UPDATE command, it
indicates the specified storage pool may be altering the
SHRED value from non zero to zero or that the
specified Copy, Next or Reclaim storage pool has a
SHRED value zero. Such configurations may result in
data to become non shreddable if data from the
primary random access storage pool is moved to one of
the storage pools with a zero SHRED value.
System action: The command continues.
User response: Verify that the storage pools being
used meet your requirements for data protection.
138
ANR1310E
Vary-on failed for disk volume volume

name - insufficient memory.
Explanation: A VARY ONLINE command has been

issued for the disk volume specified, but sufficient
memory is not available to process the command.
System action: The volume is not varied online.
User response: Reissue the command at a later time,
or make more memory available to the server.
ANR1311E

name - unable to access disk device.

issued for the disk volume specified, but the server is
unable to access the disk.
inability to access the volume and correct the problem.
ANR1312E

name - error reading disk.

issued for the disk volume specified but the server
encounters an error reading the disk.
read error and correct the problem.
ANR1313E

name - unsupported block size (block
size).

issued for the disk volume specified, but the volume is
formatted with a block size that cannot be used.
User response: Reformat the disk with a block size
that is an evenly divisible by 4096.
ANR1314E

name - reduced capacity (was count
blocks, now count blocks.

issued for the disk volume specified, but the size of the
volume does not match the size expected.
User response: Restore the volume or otherwise
correct the disk volume size, and reissue the command.
ANR1315E ANR1324E
ANR1315E

name - invalid label block.

issued for the disk volume specified, but the label block
of the volume is invalid or cannot be read.
for the specified storage pool has ended with the

results shown.
ANR1320W
User response: Restore or reformat the disk volume.

ANR1316E

name - internal error detected.

issued for the disk volume specified, but fails due to an
internal server error.
Vary-on not possible for disk volume

volume name - access state is
unavailable.

issued for the disk volume specified, but the status of
the volume is unavailable.
User response: If necessary, use the UPDATE
VOLUME command to change the status of the
volume, and reissue the command.

ANR1321W
ANR1317E
Command: Storage pool storage pool name

is not a shreddable pool.
Explanation: The command indicated specifies the

name of a storage pool which is not a shreddable pool.
The command syntax requires that
SHREDTONOSHRED=YES be specified when data is
moved from a shreddable storage pool to a non
shreddable storage pool.
command.
User response: Reissue the command with
SHREDTONOSHRED=YES.
ANR1318I
Copying active data from primary

storage pool primary pool name to active
data pool active data pool name has ended.
Files Copied Up: number of files, Bytes
Copied Up: number of bytes, Unreadable
Files: number of unreadable files,
Unreadable Bytes: number of bytes in
unreadable files.
Explanation: Copy active data processing for the

shown.
determine whether all copy active datat processes
ended successfully.
ANR1319I
Preview of copying active data from

primary storage pool primary pool name to
active data pool active data pool name has
ended. Files Copied: number of files,
Bytes Copied: number of bytes.
Explanation: Preview of copy active data processing
Vary-on not possible for disk volume

volume name - access state is destroyed.

issued for the disk volume specified, but the status of
the volume is destroyed.
User response: If necessary, use the UPDATE
VOLUME command to change the status of the
ANR1322W
The shredding mode is already shredding

mode.
Explanation: A SETOPT SHREDDING command was

issued to change the shredding mode, but the new
mode is the same as the existing mode.
System action: The shredding mode is unchanged.
ANR1323E
Command SHRED DATA is invalid for

automatic shredding mode.
Explanation: A SHRED DATA command was issued

while shredding mode is set to Automatic.
User response: Set the shredding mode to Manual or
wait for automatic shredding to shred the data.
ANR1324E
Process process number is already running

a SHRED DATA.
Explanation: A SHRED DATA command was issued

while another SHRED DATA process is still executing.
Only a single SHRED DATA process is allowed at any
time.
139
ANR1325W ANR1338I
User response: Wait for the current SHRED DATA
process to finish, and issue the command again.
ANR1325W
Shreddable object for node name:

type=type, file space=filespace name,
object=object name skipped.
Explanation: The object for node name, identified by

type, file space and object name was found in a
shreddable storage pool and is skipped, however the
EXPORT continues.
ANR1329I
Explanation: The automatic shredding of deleted

objects is starting.
ANR1330E
System action: The server process continues exporting

and will skip all shreddable objects.
User response: Specify the
ALLOWSHREDDABLE=YES parameter when exporting
objects from a shreddable storage pool. Using this
option forces EXPORT to process all objects, including
objects found in shreddable storage pools.
Automatic shredding started.
The server has detected possible

corruption in an object being restored or
moved. The actual values for the
incorrect frame are: magic magic hdr
version ver hdr length hdrLen sequence
number seqNum data length length server
id srvId segment id segId crc crc.
Explanation: An invalid frame has been detected. This

may indicate corruption within the object being
restored or moved.
System action: The object is not restored or moved.
ANR1326I
Shredding process complete after

shredding shredded bytes bytes and
skipping skipped bytes bytes.
Explanation: The shredding process has completed.

The amount of data successfully shredded and the
amount of data that was skipped are reported.
System action: Server operation continues. If any data
was skipped, the server will attempt to shred it the
next time shredding runs.
User response: Please retry the failing operation. If the

operation fails again, please contact your service
representative and provide the information from this
message.
ANR1331E
Invalid frame detected. Expected magic

magic sequence number seqNum server id
servId segment id segId.
Explanation: This message indicates the expected

values when an invalid frame is detected.
ANR1327I
Automatic shredding stopped. Total

bytes shredded was shredded bytes and
total bytes skipped was skipped bytes
bytes.
Explanation: The automatic shredding process has

ended. The amount of data successfully shredded and
skipped during automatic shredding is reported.
was skipped, the server will attempt to shred it the
next time shredding runs.
ANR1328E
The server has detected an attempt to

restore or retrieve a shredded object.
Explanation: An attempt was made to retrieve or

restore an object which has already been shredded. This
can happen if your datasbase was recently restored,
and data which existed at the time of the database
backup has since been erased and shredded.
User response: Perform an AUDIT VOLUME
operation on the volume containing the shredded data.
User response: If contacting support, please provide

the information from this message.
ANR1332W
Shredding cancelled prior to

completion. Total bytes shredded was
shredded bytes and total bytes skipped
was skipped bytes bytes.
Explanation: The shredding process was cancelled

either because the specified duration has elapsed, or
because the CANCEL PROCESS command was used to
cancel it. The amount of data successfully shredded
and skipped is reported.
was skipped or not processed, the server will attempt
to shred it the next time shredding runs.
ANR1338I
Private volume volume name is now

pending - please delete the volume from
storage pool storage pool name after the
reuse delay period for this storage pool
has elapsed.
Explanation: All files have been deleted from the
140
ANR1339W ANR1344I
indicated private volume. The volume will not be
removed from the storage pool until user delete it
manually. If the storage pool does not have a reuse
delay specified, the indicated volume was emptied after
it had been requested by another process. It will be in
the full or filling state if the process places more data
on the tape.
User response: Use DELete Volume command delete
the volume after the reuse delay period for this storage
pool has elapsed.
ANR1339W
Session session id underestimated a size

allocation request - additional spaceMB
more space was allocated to allow the
operation to continue.
ANR1342I
Scratch volume volume name is now

pending - volume will be deleted from
storage pool storage pool name after the
reuse delay period for this storage pool
has elapsed.
Explanation: All files have been deleted from the

indicated scratch volume. The volume will not be
removed from the storage pool until the reuse delay
time period for the indicated storage pool has elapsed.
If the storage pool does not have a reuse tdelay
specified, the indicated volume was emptied after it
had been requested by another process. It will be in the
full or filling state if the process places more data on
the tape, or it will be removed from the storage pool
after it is no longer required.
Explanation: This session required additional space

megabytes of space in order for the operation to
continue. The client is responsible for accurately
reporting the size of a file to be stored to the server.
The size reported by the client is used to reserve space
in the DISK storage pool to store this file. If this size is
underestimated, the server may not be able to allocate
the additional space needed for this file to continue
with this operation.
System action: None, the operation was able to

continue.
System action: None
User response: The installed version of the client for

this node should be evaluated. In most cases, if a client
has underestimated the sizes of files reported to the
server, this may have been corrected in a newer version
of the client. If this is an application using the TSM API
that is not an IBM product, contact the vendor for the
application to have this corrected.
ANR1340I
Scratch volume volume name is now

defined in storage pool storage pool name.
Explanation: The scratch volume specified has been

added to the storage pool shown.
ANR1341I
Scratch volume volume name has been

deleted from storage pool storage pool
name.
Explanation: The scratch volume specified is no

longer in use and has been removed from the indicated
storage pool.
ANR1343I
Unable to delete scratch volume volume

name.
Explanation: A scratch volume cannot be deleted from

the server and returned to scratch at this time because
all the locks have not be released. A number of retries
have been attempted.
User response: The scratch volume will be

automatically deleted when the server is restarted. Or,
you may manually delete this volume later, using the
DELETE VOLUME command.
ANR1344I
Volume volume name cannot be reused.

Remove the volume from server storage.
Explanation: A volume that was full and is now

empty cannot be reused by the server because the
volume is on WORM media.
System action: The volume is in a state where the
access mode is READONLY, the status is FULL, and the
percent utilized is 0. The server considers the volume
to be empty when calculating the occupancy and
utilization fields for the volume.
User response: The volume remains in the library and
in the storage pool, with the attributes described in the
System Action section. If this is not a volume in a
RECLAMATIONTYPE=SNAPLOCK storage pool, you
may remove the volume by performing these steps:
1. Remove the volume from the storage pool by
issuing the DELETE VOLUME command.
2. Remove the volume from the library by issuing the
CHECKOUT LIBVOLUME command.
If this is a volume in a
RECLAMATIONTYPE=SNAPLOCK storage pool, you
cannot remove the volume. Rather, allow Tivoli Storage
Manager reclamation processing to delete the volume.
141
ANR1345I ANR1351I
ANR1345I
Volume volume name cannot be reused

by other applications and will remain in
the storage pool.
Explanation: A WORM (write-once-read-many)

volume that has been written by the server cannot be
used by other applications. This volume was not full
and has been emptied due to expiration, delete
commands, or transaction failure.
System action: The volume remains in the storage
pool to be reused by IBM Tivoli Storage Manager,
unless it is manually deleted. The remaining space on
the volume will be used in the normal course of server
operation.
User response: If the volume is no longer to be used,
manually delete it from the storage pool.
ANR1346E

processing terminated abnormally error accessing data storage.

export preview operation.
ANR1347E

data storage.

export operation.
ANR1348I
Export Operation information for number

objects has been deleted.
Explanation: A background server process deleted

export operation information for number files from the
server database. This process started during
initialization to remove any unneeded export
information.
142
System action: The actual backup or archive objects

were not deleted. Only information used to sort these
objects during the previous export operation was
deleted.
ANR1349E
Error code during deletion of export

operation information for number
objects.
Explanation: A background server process

encountered an internal error after deleting export
operation information for number files from the server
database. This process started during initialization to
remove any sorting information which is left over from
System action: The backup or archive objects were not
deleted. Only the information used to sort these objects
during the previous export operation was deleted. The
background process was terminated before all sorting
information was deleted. The system will not perform
further export processing of file data until this problem
is resolved.
activity log and search for messages, then restart the
server. If the error cannot be isolated and resolved,
ANR1350E
Command: Invalid time range specified.

FROM: fromdate fromtime TO: todate
totime.
Explanation: A command was issued that specifies an

invalid FROM and TO date or time range. This error
can occur when the FROM date or time is not before
the TO date or time.
command.
date or time range.
ANR1351I

suspended with status status.

command command was suspended with a SUSPEND
command.
stops. Statistics on the number and type of objects
message.
ANR1352I ANR1361I
ANR1352I

process process ID has been suspended.

command command by administrator administrator name
suspended processing.
Issue the QUERY EXPORT command to identify the

current state the EXPORT operation.
ANR1357I
System action: The specified process suspends, and

server operations continues.
ANR1353I
Command: Cannot cancel the EXPORT

operation with export identifier exportId.
The operation is currently active.
Explanation: The server cannot cancel the export

operation specified in the CANCEL EXPORT command
because it is currently running as an active process.
System action: Server operations continue.
User response: Only suspended EXPORT operations
may be cancelled by issuing the CANCEL EXPORT
command. Issue the QUERY EXPORT command to
identify the current state of the EXPORT operation.
ANR1354I
command name: The EXPORTIDentifier

parameter is not supported when the
FILEDATA parameter is set to NONE.
Running as non-restartable export.
Explanation: The EXPORTIDentifier parameter is

ignored while the command continues.
System action: The command runs and server
command name: The EXPORTIDentifier

parameter is not supported when the
PREVIEWIMPORT parameter is
specified. Running as non-restartable
export.
Explanation: The EXPORTIDentifier parameter is

ignored while the command continues.
System action: The command runs and server
ANR1358I
Export Identifier: Export Id
Explanation: This is a restartable export operation that

can be referenced by the displayed EXPORTIDentifier
parameter.
ANR1359I
Suspend in progress
Explanation: The server-to-server export operation has

been suspended and will stop when resources have
been freed for the background process. This message
may be displayed in response to a QUERY PROCESS
command for an export operation.

ANR1360I
ANR1355I
command name: An export operation

already exists with the
EXPORTIDentifier export ID.
Explanation: The export command fails.

User response: Reissue the export command with an
unused export identifier.
ANR1356I
Command: Cannot restart the EXPORT

operation with export identifier exportId.
The operation is currently active.
Explanation: The server cannot restart the export

operation specified in the RESTART EXPORT command
because the export operation is currently running as an
active process.
Output volume volume name opened

(sequence number sequence number).
Explanation: During a sequential data operation, the

volume specified has been opened for output as the
volume number shown.
ANR1361I
Output volume volume name closed.

volume specified has been closed because the export or
dump is complete.

User response: Only suspended Export operations
may be restarted using RESTART EXPORT command.
143
ANR1362I ANR1370E
ANR1362I
Output volume volume name closed

(full).

volume specified has been closed because the volume is
full.
ANR1363I
Input volume volume name opened

(sequence number sequence number).
Explanation: Because of a sequential data operation,

the volume specified has been opened for input as the
volume number shown.
ANR1364I
Input volume volume name closed.

volume specified has been closed because the operation
is complete.
ANR1367W
Import volume volume name was written

by a different export process.
Explanation: During an IMPORT operation, the

volume specified has been mounted but contains an
export identifier that does not match the import
process.
System action: The volume is not used.
User response: Supply a volume created by the proper
export process.
ANR1368W
Input volume volume name contains

sequence number sequence number;
volume sequence number sequence
number is required.

volume specified has been mounted but contains the
wrong volume sequence number.
User response: Supply the volume with the proper
sequence number. The volume history file can help you
choose the correct volume.

ANR1365I
Volume volume name closed (end

reached).

volume specified has been closed because processing of
the volume is complete.
ANR1366W
Input volume volume name contains an

invalid identifier.

volume specified has been mounted but contains an
invalid identifier.
User response: Make sure you specified the correct
volume for the operation. If a LOADDB operation was
being performed on MVS, the command syntax may be
specified by using a ddname or by specifying a device
class name. You must use the same method that was
used when the database was originally dumped. If you
did not, this error message will be displayed. Try
loading the data base by using the other method of
syntax (ddname).
144
ANR1369E
Input volume volume name contains

Version 1 dump.

volume specified has been mounted but appears to
contain a version 1 database dump.
System action: The volume is not used. The operation
is terminated.
User response: Make sure you specified the correct
volume for the operation. A Version 1 database dump
may not be loaded into a Version 2 server. The Version
1 database dump must only be loaded into a Version 1
server.
ANR1370E
Insufficient number of mount points

available in device class device class name.
Explanation: During IMPORT or EXPORT processing,

the server cannot allocate sufficient mount points for
the device class specified. The device class associated
with the EXPORT or IMPORT drive only has a mount
limit of one. The operation needs to read or write file
data from or to the same device class because file data
is being imported or exported.
System action: The IMPORT or EXPORT command is
User response: Make more mount points available.
ANR1371I ANR1404W
ANR1371I
Command: The export operation with

export identifier Export Id has been
deleted.
Explanation: The suspended server-to-server export

operation has been deleted. This operation may no
longer be restarted. This message is be displayed in
response to a CANCEL EXPORT command.
ANR1400W
Mount request denied for volume

volume name - mount canceled.
Explanation: The volume shown cannot be mounted

because the mount request has been canceled.
System action: The volume is not mounted.

ANR1372I
Suspend export request accepted for

export process with export Identifier
Export Id ( process process ID).
Explanation: A SUSPEND EXPORT command has

been entered for the specified server-to-server export
process. Some processes will experience a delay before
they suspend. This delay may be lengthy for processes
that involve remote data movement.
ANR1401W

volume name - mount failed.

because the mount request cannot be completed
successfully. Possible reasons include, an error in device
specifications to the server or the mount request timed
out.
User response: If the device specifications (DEFINE
DEVCLASS and so forth) are in error, correct them and
reissue the command that requested the volume to be
mounted.

ANR1402W
ANR1373I
Process process Id for Command has been

suspended on source server.
Explanation: The background import process has been

suspended on the source server.
ANR1374I
Process process Id for Command has been

canceled on source server.
Explanation: The background import process has been

canceled on the source server.
ANR1375I
Command: Cannot suspend the export

operation export Id because the current
state is not valid.
Explanation: This message is returned in response to a

SUSPEND EXPORT command which specified an
export operation that is not currently suspendible. The
export operation may not be running, or it may be in
the process of being suspended.
System action: The specified command fails, and

volume name - volume unavailable.

because it is not available.
User response: If the attempted mount occurs in a
library sharing environment and the library manager
was recently recycled, try again in five minutes. In this
case the library manager and library client need a few
minutes to reestablish communication and synchronize
the mounting information between the two servers.
ANR1403W
Scratch volume mount request denied mount canceled.
Explanation: A scratch volume cannot be mounted

because the mount request has been canceled.
System action: The scratch volume is not mounted.
ANR1404W
Scratch volume mount request denied mount failed.

because the mount request cannot be completed
successfully. Possible reasons include, an error in device
specifications to the server or the mount request timed
out.
User response: If the device specifications (for
example, DEFINE DEVCLASS) are in error, correct
145
ANR1405W ANR1414W
them and reissue the command that requested the
volume to be mounted.
ANR1405W
Scratch volume mount request denied no scratch volume available.

because no scratch volume is available.
server storage pools. Use the QUERY VOLHISTORY

command to display the names of volumes that have
been used for export or database backup operations. If
no volume names are displayed using the query
commands described above, ensure that the volume
identified in this message has not been specified or
used more than once in the operation being performed.
ANR1410W

ANR1406E
Simultaneous write operation could not

release all the acquired mount points.
Explanation: A simultaneous write to a primary and

copy storage pools failed to release all the acquired
mount points. When a simultaneous write operation
begins it will attempt to acquire all of the necessary
mount points. If a mount point cannot be acquired or
the simultaneous write operation has to wait for a
mount point, then the operation will release any mount
points it has already acquired. This prevents the
simultaneous write operation from holding mount
points and other mount requests from completing. This
message is issued if one of the previously acquired
mount points cannot be released.
System action: At least one mount point acquired by
simultaneous write operation is not released.
Explanation: The status of the volume shown has

been set to unavailable.
ANR1411W
Scratch volume mount request denied storage pool pool name has reached
maxscratch limit.

now set to read-only due to write
error.
Explanation: Because of an unrecoverable write error

on the volume shown, the status of the volume has
been set to read-only.
ANR1412W

ANR1407W

now set to unavailable.
Volume volume name access mode is

unavailable.
Explanation: At server startup, the status of the

indicated volume is unavailable.

because the storage pool has reached the maximum
scratch volume limit allowed by the MAXSCRATCH
parameter.
ANR1413W
System action: A scratch volume is not mounted.

indicated volume is read-only.
User response: Use the UPDATE STGPOOL poolname

MAXSCRATCH=xx command command to increase the
number of scratch volumes allowed in the storage pool.
ANR1409W
Volume volume name already in use skipped.

read-only.

ANR1414W

read-only due to previous write error.
Explanation: During an export or database backup, a

a storage pool, or has already been used by the current
operation, or has been previously used by an export or
database backup operation (as recorded in the volume
history) or is in use by another process.

indicated volume is read-only due to an unrecoverable
write error, or because an administrator used the
UPDATE VOLUME command to set the volume access
mode to read-only.
System action: The operation continues and the

volume is skipped.
User response: Use the QUERY VOLUME command

to display the names of volumes that are defined to
146
ANR1415W ANR1424W
ANR1415W

destroyed.

indicated volume is destroyed.
parameter is used, the FROMDATE parameter must be

specified.
User response: Reissue the command with both the
FROMDATE and FROMTIME parameters specified.

ANR1420W
ANR1416W

offsite.

indicated volume is offsite.
ANR1417W

now set to read-only due to excessive
read error.
Read access denied for volume volume

name - volume access mode =
unavailable.
Explanation: An attempt to access the named volume

for reading fails because the volume status is
unavailable.
System action: The volume is not used for read
access.
ANR1421W

name - volume is offline.
Explanation: Because of an numerous read errors on

the volume shown, the status of the volume has been
set to read-only.

for reading failed because the volume is offline.
User response: Use QUERY VOLUME

FORMAT=DETAILED for the volume to view the
access mode and number of read errors. You may want
to use the MOVE DATA command to move the
retrievable data from this volume to another volume.
For the damaged files, use the RESTORE VOLUME
command to restore a readable copy of the file to the
storage pool.
ANR1418E
command name: Export commands that

target another server cannot be issued
from the server console.
Explanation: An EXPORT command that targets

another server was issued from the server console. This
command cannot be issued from the server console
because it requires authentication of the issuing
administrator on the target server.
User response: Issue the command from an
ANR1419E
command name : FROMDATE must be

specified when FROMTIME is
specified.
Explanation: A command that supports the

FROMDATE and FROMTIME parameters was issued
with the FROMTIME parameter specified, but without
the FROMDATE parameter. When the FROMTIME
ANR1422W

name - volume access mode=offsite.

for reading failed because the volume status is offsite.
access.
ANR1423W
Scratch volume volume name is empty

but will not be deleted - volume access
mode is offsite.
Explanation: The named scratch volume is empty but

will not be deleted at this time because the access mode
is offsite.
User response: After bringing the volume onsite,
change the access mode to read-only so the volume will
be deleted.
ANR1424W

name - volume access mode=destroyed.

for reading failed because the volume status is
destroyed.
access.
147
ANR1425W ANR1432I
ANR1425W
Scratch volume volume name is empty

but will not be deleted - volume state is
mountablenotinlib.
Explanation: The named scratch volume is empty but

will not be deleted at this time because the state of the
volume is MOUNTABLENOTINLIB. Possible reasons
include, a MOVE MEDIA command was used to check
the volume out of the library and the volume was
subsequently checked into the library using CHECKIN
LIBVOL without first running a MOVE MEDIA
command to update the volume state back to
MOUNTABLEINLIB state. If this should happen, the
QUERY MEDIA will display the volume to be in
MOUNTABLEINLIB state since QUERY MEDIA does
verify if the volume is actually in the library before
displaying the state of the volume.

activity log and search for messages. Contact your
service representative for further assistance.
ANR1428W
Explanation: An object on the indicated volume

cannot be shredded because the volume is offline.
System action: The object is not shredded at this time.
When the volume is put back online, another attempt
will be made to shred the object.
User response: Determine why the volume is offline,
and, if possible, place the volume back online.
ANR1430W

User response: The following steps may be used if the
volume is to be deleted:
1. Run CHECKOUT LIBVOL to check the affected
volume out of the library, the REMOVE=NO option
may be used to prevent actual volume movement
2. Run MOVE MEDIA * STG=*
WHERESTATE=MOUNTTABLENOTINLIB
WHERESTATUS=EMPTY. When the volume is
moved by MOVE MEDIA
WHERESTATE=MOUNTABLENOTINLIB, the
scratch empty volume is deleted
All legacy FILE volumes have been

marked FULL.
Retrieval request denied for storage

pool storage pool name - access
mode=unavailable.
Explanation: An attempt was made to retrieve a file

from the storage pool shown, but the access mode of
the storage pool is unavailable.
System action: The file is not retrieved from this
storage pool. If possible, the file is retrieved from
another storage pool.
User response: Consider changing the access mode for
the storage pool.
ANR1431E
3. Check the volume back into the library using

CHECKIN LIBVOL command
ANR1426I
Shredding access denied for volume

volume name - volume is offline.
An error occurred while writing to side

A of volume volume name. An attempt
will be made to write to side B of this
volume.
Explanation: An error occurred while writing to side

A of a two-sided volume.
Explanation: As part of the conversion of the database

to Tivoli Storage Manager version 5.3, all existing
non-full volumes of devtype FILE have been marked
FULL to keep them from being extended.
System action: No additional data will be written to

side A of this volume. Any remaining space on side A
will not be used. An attempt will be made to use the
reverse side (side B) of the volume.
System action: All FILE volumes that were not

already FULL have been marked FULL and cannot be
appended to.
User response: None required if the side B can be

used successfully. However, the administrator should
investigate the cause of the error and may want to
move data from this volume.

ANR1427E
No legacy FILE volumes were marked

FULL.
Explanation: As part of the conversion of the database

to Tivoli Storage Manager Version 5.3, all existing
non-full volumes of devtype FILE were attempted to be
made FULL. However, a database error prevented the
conversion, and the status of these volumes remains
unchanged.
System action: The volumes are not marked FULL.
148
ANR1432I
Updating device configuration

information to defined files.
Explanation: The server is updating device

configuration information for the files or data sets
specified with the DEVCONFIG option in the server
options file.
ANR1433I ANR1439E
ANR1433I
Device configuration information

successfully written to file name.
Explanation: Device configuration information was

successfully written to the file specified.
proper authority to write to the file indicated and that

there is sufficient space in the file system for the file.
On MVS, make sure that the data set has been allocated
and that the server has authority to write to the data
set. After the problem has been corrected, use the
BACKUP DEVCONFIG command to write device
configuration information to the file.

ANR1437E
ANR1434W
No files have been identified for

automatically storing device
configuration information.
Explanation: The server is unable to automatically

update device configuration file. No files were
identified using the DEVCONFIG option in the server
options file.
User response: If you would like to have the server
automatically record device configuration information
to assist in server recovery, use the DEVCONFIG
option in the server options file to specify where device
configuration information should be written. If you
update the options file, halt and then restart the server
so the changes can take effect.
ANR1435E
Server could not write device

configuration information to devconfig
file name.
Explanation: While attempting to write device

configuration information to defined files, the server
cannot write to the file name specified.
System action: The server cannot write device
configuration information to the specified file.
User response: Examine error messages that may have
been displayed prior to this message and correct any
problems, if possible. Make sure that the server has
BACKUP DEVCONFIG command to write device
configuration information to the file.
ANR1436E
Device configuration file devconfig file

name cannot be opened.
Explanation: While attempting to write device

configuration information to device configuration files,
the server cannot open the file name specified.
System action: The server does not write device
configuration information to the file specified.
No device configuration files could be

used.
Explanation: The server attempts to read device

configuration information from defined files and cannot
open any of the files.
System action: The operation is ended.
problems, if possible. Ensure that the defined device
configuration files have been created. If you can start
the server, you can create the files by using the
BACKUP DEVCONFIG command. If you cannot start
the server, you will need to create a device
configuration file by editing the file and adding the
appropriate DEFINE commands for the device class,
drive, and library definitions. The contents and
requirements for this file are described in the
Administrators Guide. Make sure that the server has
proper authority to read from the defined device
configuration files.
ANR1438W
Skipping device configuration file:

devconfig file name.
Explanation: While attempting to read device

configuration information from a defined device
configuration file, the server encounters problems in
processing the definitions included in the file.
System action: The specified file is skipped, and the
next one specified in the server options file will be
used.
been displayed prior to this message to understand
why the file could not be used. When you can start the
server again, you can refresh this file by using the
BACKUP DEVCONFIG command.
ANR1439E
Allocate prohibited - transaction failed.
Explanation: While attempting to preallocate storage

on a storage pool, the server detected that the
transaction for this operation has previously failed. This
error may occur when a large file is selected for backup
and the client did not properly estimate the file size.
There may not be enough space in the storage pool for
the file.
System action: An internal error is reported by the
server and the operation being performed is ended.
149
ANR1440I ANR1451E
been displayed prior to this message for more
information.
available to run the command in parallel. The

command will be executed serially.
System action: The SCRIPT continues.
ANR1440I
All drives in use. Process process number

being preempted by higher priority
operation.

attempted to find an available drive, all the drives were
in use. To make a drive available for this operation, the
indicated process is being cancelled by the system.
System action: The lower priority process is cancelled
to make a mount point (drive) available.
User response: When a drive again becomes available,
restart the process that was cancelled. If the process
was a migration or reclamation process, it will be
automatically restarted when needed. If this message
appears frequently, you may want to increase the
number of drives available. See the MOUNTLIMIT
parameter on the UPDATE DEVCLASS command.
User response: Increase the resources available to the

server or reduce the number of parallel commands or
scripts that are running on the server at any one time.
ANR1448I
Explanation: This message is issued during a RUN

command (VERBOSE=YES) to indicate that a SERIAL
command was encountered and following SCRIPT
commands will be executed serially.
System action: The SCRIPT command continues.
User response: See the output of the commands
following the SERIAL command to determine their
results.
ANR1449I
ANR1441I
Volume volume name is in use. Process

process number being preempted by
higher priority operation.

attempted to use a volume, it was in use. To make a
volume available for this operation, the indicated
process is being cancelled by the system.
System action: The lower priority process is cancelled
to the volume available.
User response: Restart the process that was cancelled.
It will wait until the higher priority process is finished
with the volume. If the cancelled process was a
migration or reclamation process, it will be
automatically restarted when needed.
ANR1442E
Invalid storage pool for store operation:

storage pool.
Explanation: The storage pool selected for a store

operation (for example, backup or archive) was not a
NATIVE or NONBLOCK data format storage pool. This
may be caused by an incorrect management class being
assigned to an object.
User response: Ensure that the copy group destination
storage pool of the assigned management class has the
appropriate NATIVE or NONBLOCK data format.
ANR1447W
command name: The server is not able to

begin a new thread to execute the
command on line line number in parallel.
The command will run serially.

command to indicate that thread resources are not
150
command name: Beginning serial SCRIPT

command execution on line line number.
command name: Beginning parallel

SCRIPT command execution on line line
number.

command (VERBOSE=YES) to indicate that a
PARALLEL command was encountered and following
SCRIPT commands will be executed in parallel.
System action: The SCRIPT command continues.
User response: See the output of the commands
following the PARALLEL command to determine their
results.
ANR1450E
command name: Invalid command script

name: command script name.
Explanation: An invalid script name was specified for

a DEFINE, UPDATE, or DELETE SCRIPT command.
User response: Reenter the command specifying a
valid command name.
ANR1451E
command name: Invalid command:

command.
Explanation: An invalid command was specified for a

DEFINE, UPDATE, or DELETE SCRIPT command.
valid server command.
ANR1452E ANR1463E
ANR1452E
command name: Invalid line number: line

number.
Explanation: An invalid line number was specified for

a DEFINE, UPDATE, or DELETE SCRIPT command.
valid line number.
ANR1458I
command name: Line line number was

deleted from command script command
script name.
Explanation: The specified line number was deleted

from the command script as a result of a DELETE
SCRIPT command.
System action: None
User response: None
ANR1453E
command name: Command script command

script name already exists.
ANR1459E
Explanation: The script name specified in a DEFINE

SCRIPT command already exists.
different command name.
ANR1454I

script name defined.
Explanation: The script name specified in a DEFINE

SCRIPT command was successfully defined.
Explanation: The line in command script name

specified in a UPDATE, or DELETE SCRIPT command
does not exist.
different line number.
ANR1460I
System action: None

User response: None
ANR1455E

script name does not exist.

script name, line line number does not
exist.

script name copied to new command script
name.
Explanation: The specified command script was

copied to a new script with the COPY SCRIPT
command.
System action: None
Explanation: The script name specified in a DEFINE,

UPDATE, or DELETE SCRIPT command does not exist.
User response: None
ANR1461I

different command name.
ANR1456I

script name updated.
Explanation: The script name specified in an UPDATE

SCRIPT command was successfully updated.
Explanation: The specified command script is being

executed as a result of a RUN command.
System action: None
User response: None
ANR1462I
System action: None

User response: None
ANR1457I

script name deleted.
Explanation: The script name specified in a DELETE

COMMAND command was successfully deleted.
System action: None
User response: None
command name: Executing command

script command script name.

script name completed successfully.
Explanation: The specified command script, started

with a RUN command, has successfully completed.
System action: None
User response: None
ANR1463E

script name completed in error.

with a RUN command, encountered errors.
System action: Part or all of the command lines in the
script ended in error. Command processing is
terminated.
151
ANR1464E ANR1473E
User response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
command script and reissue the command.
ANR1464E

script name, line line number, parameter
parameter number was not specified:
command line.
Explanation: All parameters required to execute a

command script were not specified in the RUN
command.
ANR1469E

script name, Line line number is an
INVALID command : command line.
Explanation: The specified line for the command

script is not a valid server command. This message is
displayed when a RUN command is executed with the
PREVIEW=YES parameter specified.
System action: Command Preview processing fails
User response: Correct the script and reenter the RUN
command.

User response: Reenter the RUN command specifying
all required parameters.
ANR1465E

script name, line line number, parameter is
invalid: command line.
ANR1470I

script name completed successfully
(PREVIEW mode).

with a RUN command, has successfully completed.
Explanation: An invalid parameter was encountered

in a command script.
ANR1471E
User response: Correct the script definition and

reexecute the RUN command.
ANR1466I

script name, Line line number : command
line.
Explanation: The specified line for the command

script is being executed. The contects of the line being
executed are displayed.
System action: None
User response: None
ANR1467E

script name, did not end in a
non-continued line command line.
Explanation: The specified command script did not

end in a line that had no continuation character (-).
User response: Correct the specified script so that it
ends in a line that is not continued to the next line.
ANR1468E

script name, continued line is too long
Explanation: The specified command script with

continuation lines is too long to be executed.
User response: Correct the specified command script
so that it is shorter.
152

script name completed in error
(PREVIEW mode).

with a RUN command, encountered errors.
System action: Part or all of the command lines in the
command script ended in error. Command processing
is terminated.
User response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
script and reissue the command.
ANR1472I

script name renamed to new command
script name.
Explanation: The specified command script was

renamed with the RENAME SCRIPT command.
ANR1473E
command name: A command line cannot

be specified when the FILE= parameter
is used.
Explanation: The FILE= parameter was specified in

the DEFINE SCRIPT command AND a command line
was also specified for the SCRIPT. When the FILE=
parameter is specified, a command line cannot be
specified.
User response: Reenter the command without the
command line OR the FILE= parameter.
ANR1474E ANR1483I
ANR1474E
command name: A line number cannot be

specified when the FILE= parameter is
used.
Explanation: The FILE= parameter was specified in

the DEFINE SCRIPT command AND a line number
was also specified for the SCRIPT. When the FILE=
parameter is specified, a line number cannot be
specified.
User response: Reenter the command without the line
number OR the FILE= parameter.
ANR1478E
Explanation: An error was encountered while writing

to the file specified.
User response: Examine any messages that might
appear prior to this one in the activity log to determine
if the error can be found. Ensure that the filesystem has
sufficient space and that the server has authority to
create the file in the location specified.
ANR1479I
ANR1475E
command name: File file name could not be

opened.
Explanation: A filename was specified in a command

but the specified file could not be opened by the server.
User response: Examine any messages that might
appear prior to this one in the activity log to determine
if the error can be found. If the file was to exist for use
by the command, ensure that the file does exists and
that the server has proper authority to access the file. If
the file was to be created by the command, ensure that
the filesystem has sufficient space and that the server
has authority to create the file in the location specified.
ANR1476E
command name: File file name contains no

data.
Explanation: The FILE= parameter was specified in a

command but the specified file did not contain script
command lines.
User response: Add script command lines to the file
or specify another file and reenter the command.
ANR1477E
command name: The OUTPUTFILE

parameter may only be specified when
FORMAT=RAW is specified.
command name: Error writing to file file

name.
command name: Query output was

written to file file name.
Explanation: The output from the specified query was

successfully written to the specified file.
System action: The command completes successfully.
ANR1480E
command name: Description text is too

long.
Explanation: The specified description text is too long

for a command that allows description text to be
specified.
shorter description.
ANR1481E
command name: A command line or

description must be specified.
Explanation: An UPDATE SCRIPT command was

specified with out a command line (script line) or
description text.
command line or description text.
command name: Found label statement label
on line line number and continuing.
Explanation: The OUTPUTFILE parameter was

specified in a QUERY SCRIPT command but the
FORMAT parameter did not specify RAW output.
When outputting the QUERY to a file, you MUST
specify RAW output format.
ANR1482I
System action: Command processing continues.
User response: Reenter the command specifyingthe

proper value for the FORMAT parameter or do not
specify the OUTPUTFILE parameter.

command (VERBOSE=YES) to indicate that the target
label for a GOTO statement was found.
ANR1483I
command name: Line line number

condition IF(condition) is NOT true statement is skipped.

command (VERBOSE=YES) to indicate that the a return
153
ANR1484I ANR1492E
code condition check failed and the IF(..) statement is
skipped.
conditions for the IF() statement.
ANR1489E

ANR1484I

condition IF(condition) is TRUE statement will be executed.

command (VERBOSE=YES) to indicate that the a return
code condition check succeeded and the IF(..) statement
is executed.
command name: Line line number is a

GOTO to a label (label name) that does
not exist or is associated with a line
prior to line line number.
Explanation: This message is issued if a GOTO

statment in a SCRIPT does not specify a label that
exists in the SCRIPT, or that does exist but is associated
with a line prior to the line that contains the GOTO
statement.
System action: Command processing fails.
User response: Correct the SCRIPT definition and
reenter the RUN command.

ANR1490W
ANR1485I
command name: Ending SCRIPT with

EXIT statement on line line number.

command (VERBOSE=YES) to indicate that an EXIT
statement was encountered and SCRIPT termination
will end.
System action: The SCRIPT command ends.
ANR1486I
command name: Executing line line number

GOTO label name.

command (VERBOSE=YES) to indicate that a GOTO
statment was encountered and processing will skip to
the named label.
System action: SCRIPT processing continues.
ANR1487I
command name: Command return code is

symbolic return code (return code severity).

command (VERBOSE=YES) to indicate the return code
that was returned from the latest command.
ANR1488E

condition IF(condition) is not a valid
condition.
Explanation: This message is issued if an IF()

statement in a SCRIPT does not specify proper
condition values.
User response: Reenter the command using valid
154

script name does not contain any
commands.
Explanation: The script name specified in a RUN

command does not contain any commands.
System action: The RUN operation fails (has nothing
to do).
User response: Server command Scripts that contain
no commands will not execute. Add command lines to
the Script and reenter the RUN command.
ANR1491E
Server command scripts cannot be

started from the server console.
Explanation: A server command script RUN

command was issued from the server console. Server
command scripts cannot be started from the server
console because they may require a long time complete
and the server console should be available to control
other server functions.
User response: Start the server command script from
an administrative client or schedule it for execution
using the administrative command scheduler.
ANR1492E
command name: A loop has been detected

in server command script RUN
commands - command failed.
Explanation: A server command script DEFINE or

UPDATE command has created a situation where one
or more scripts invoke each other in a loop that can
cause the scripts to run idefinitely.
System action: The command fails to update the
server command script.
User response: Server command scripts can invoke
each other, but not in a fashion that causes a potential
loop in their execution. Specify the scripts in a manner
ANR1493E ANR1503I
that does not cause them to invoke each other in a
loop.
ANR1493E
Command: Administrator administrator

name is not authorized to update or
delete command script command script
name.
Explanation: The specified administrator has entered

the indicated command, but this administrator does not
have the proper authority necessary to update or delete
this command script. If an administrator does not have
system authority, they must have previously created or
updated the script.
ANR1498E
Explanation: The ISSUE MESSAGE command with a
severity indicator of ERROR was issued.
ANR1499S
severity indicator of SEVERE was issued.

command.

authorized administrator ID, or contact the
administrator that created the script.
ANR1500I
ANR1494I
command name: Command return code is

numeric return code.

command (VERBOSE=YES) to indicate the numeric
return code that was returned from the latest
command.
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.
User response: Reenter the command when the script
is not running.
Policy domain domain name defined.
Explanation: In response to the DEFINE DOMAIN

command, the policy domain domain name has been
defined in the server database.
ANR1501I
Policy domain domain name deleted.
Explanation: In response to the DELETE DOMAIN

deleted from the server database. All policy sets,
management classes, copy groups, and schedules
related to the domain have also been removed.
ANR1502I
Policy domain domain name updated.
Explanation: In response to the UPDATE DOMAIN

updated in the server database.
ANR1496I

severity indicator of INFORMATION was issued.
ANR1503I

ANR1497W
Policy domain domain name copied to

domain target domain.
Explanation: In response to the COPY DOMAIN

copied to a new policy domain named target domain.
All policy sets, management classes, and copy groups
are also copied to the target domain policy domain.

severity indicator of WARNING was issued.
155
ANR1504I ANR1511I
ANR1504I
Command: No matching domains.
Explanation: The server cannot find any policy

domains with names that match the specification
entered in the command command.
User response: Reissue the command with a
specification that matches an existing policy domain
name. Use the QUERY DOMAIN command to obtain a
list of the names of existing policy domains.
ANR1505W
The BACKUP copy group in

specifies a table of contents destination
storage pool : storage pool name that does
not exist. If this pool does not exist
when policy set policy set name is
activated, the creation of the table of
contents may fail for an image backup
when this management class is used for
the backup.
Explanation: This message may be returned from the

DEFINE COPYGROUP, UPDATE COPYGROUP,
VALIDATE POLICYSET or ACTIVATE POLICYSET
command. During the indicated command processing,
the server has found a backup copy group that has a
table of contents (TOC) destination referring to an
undefined storage pool named storage pool name. If this
storage pool is undefined when the policy set is
activated, the creation of the TOC for an image backup
will fail if its TOC creation binds to the management
class whose copy groups reference this pool.
ANR1507I
Table of contents load retention is set to

number of minutes minutes.
Explanation: The number of minutes that the

unreferenced table of contents (TOC) data will remain
loaded in the server database has been set to the value
indicated with the SET TOCLOADRETENTION
command.
ANR1508E
Command: An incorrect table of contents

load retention retention value was
specified.
Explanation: A SET TOCLOADRETENTION

command has been entered that specifies an invalid
table of contents (TOC) retention period.
command.
retention period.
ANR1509I
Express upgrade status is set to state.
Explanation: The upgrade status of the server

showing whether it was upgraded from TSM Express
has been changed to the value indicated with the SET
EXPRESSUPGRADESTATUS command.

User response: To locate the copy groups that refer to
the undefined storage pool, issue the QUERY
COPYGROUP command. To change the TOC
destination to refer to an existing storage pool, issue
the UPDATE COPYGROUP command. To define the
storage pool, an authorized administrator can issue the
DEFINE STGPOOL command.
ANR1506E
Command: An incorrect storage pool

name - storage pool name was specified
for the TOC destination.
Explanation: Server processing for the command

command fails because the storage pool name pool name
specified for the table of contents (TOC) is an invalid
destination storage pool type. A copy storage pool or
an active-data storage pool is not a valid copy group
TOC destination.
User response: Reissue the command using a storage
pool name that is not a copy pool or active-data pool.
For a list of names of defined storage pools, issue the
QUERY STGPOOL command.
156
ANR1510I
Policy set set name defined in policy

domain domain name.
Explanation: In response to the DEFINE POLICYSET

command, the policy set named set name has been
defined in the policy domain named domain name in the
server database.
ANR1511I
Policy set set name deleted from policy

domain domain name.
Explanation: In response to the DELETE POLICYSET

command, the policy set set name has been deleted from
the policy domain domain name in the server database.
ANR1512I ANR1523I
ANR1512I
Policy set set name updated in policy

domain domain name.
Explanation: In response to the UPDATE POLICYSET

command, the policy set set name has been updated in
the policy domain domain name in the server database.
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
domain name. All management classes and copy groups
are also copied to the policy set new set name.
User response: If you are satisfied with any warning

messages that may have been issued prior to this
message concerning any possible discrepancies in the
policy set, issue the ACTIVATE POLICYSET command
to activate the policy set in the policy domain.
Otherwise, correct the discrepancies prior to activating
the policy set. Before the ACTIVATE POLICYSET
command is used to activate the policy set, use the
validate command to check policy set contents.
ANR1520I
Management class class name defined in

policy domain domain name, set set name.
Explanation: In response to the DEFINE

MGMTCLASS command, the management class named
class name has been defined in the policy set set name
belonging to the policy domain named domain name.

ANR1521I
ANR1514I
Policy set set name activated in policy

domain domain name.
Management class class name deleted

from policy domain domain name, set set
name.
Explanation: In response to the ACTIVATE

POLICYSET command, the policy set set name has been
activated in the policy domain domain name. All
management class and copy group definitions in the
policy set will be used by clients that start sessions
after this command is committed. Clients that currently
have sessions established with the server will use the
policy definitions in the previously active policy set for
the domain.
Explanation: In response to a DELETE MGMTCLASS

command, the management class named class name has
been deleted from the policy set set name belonging to
the policy domain domain name. All copy groups
defined for the management class are also removed.
System action: The server replaces the active

management class and copy group definitions for the
policy domain with the definitions found in the
specified policy set. These values are returned to client
nodes that start a session with the server after this
command is committed to the server database.
ANR1522I

ANR1515I
Policy set set name validated in domain

domain name (ready for activation).
Explanation: This message may be displayed in

response to a VALIDATE POLICYSET command. The
policy set set name has been checked in the domain
domain name to see if the management class and copy
group definitions are adequate for activating the policy
set. This message indicates that the policy set may be
activated. Warning messages may be issued prior to
this message if there are discrepancies in the policy set
with respect to the set that is currently active in the
policy domain.
System action: The server checks its definitions to
determine the policy sets qualifications for activation.
The server does not activate the policy set.

Management class class name updated in
policy domain domain name, set set name.
Explanation: In response to the UPDATE

MGMTCLASS command, the management class named
class name has been updated in the policy domain
domain name, policy set set name.
ANR1523I
Management class class name copied to

class new class name in policy domain
Explanation: In response to the COPY MGMTCLASS

command, the management class named class name has
been copied to a new management class named new
class name in policy set set name belonging to policy
domain domain name. All copy groups defined for
management class class name are also copied to
management class new class name.
157
ANR1530I ANR1550W
ANR1530I
Backup copy group group name defined

in policy domain domain name, set set
name, management class class name.

COPYGROUP command, a backup copy group named
group name has been defined for the management class
named class name in the policy set set name belonging to
ANR1531I
Backup copy group group name deleted

Explanation: In response to the DELETE

COPYGROUP command, the backup copy group
named group name has been deleted from the
management class named class name in the policy set set
name belonging to policy domain domain name.
ANR1532I
Backup copy group group name updated


COPYGROUP command, the backup copy group
named group name has been updated in the
ANR1535I
Archive copy group group name defined


COPYGROUP command, an archive copy group named
group name has been defined for the management class
named class name in the policy set set name belonging to
ANR1536I
Archive copy group group name deleted


COPYGROUP command, the archive copy group
named group name has been deleted from the
158

ANR1537I
Archive copy group group name updated


COPYGROUP command, the archive copy group
named group name has been updated in the
ANR1538I
Default management class set to class

name for policy domain domain name, set
set name.
Explanation: The default management class for the

policy set set name in policy domain domain name has
been set to the management class named class name.
System action: If this policy set is activated, clients
use this management class for backup-archive
processing by default, or if other management classes
specified for binding do not exist in the policy set.
ANR1550W
Management class class name is NOT

defined in policy set set name but IS
defined in the ACTIVE policy set for
domain domain name: files bound to this
management class will be REBOUND to
the default management class if/when
this set is activated.

command. During policy set validation processing, the
server has found a management class named class name
in the currently active policy set, but not defined in the
policy set being validated or activated (set name). If
policy set set name is activated, files bound to this
management class in domain domain name are
automatically rebound to the default management class
in policy set set name.
User response: If you do not want files to be rebound
to the default management class, define a management
class with the name specified in the message for the
policy set. To define the proper copy group attributes,
reference the management class definition in the
ACTIVE policy set or copy the management class class
name from the ACTIVE policy set to policy set set name
using the COPY MGMTCLAS command.
ANR1551W ANR1554W
ANR1551W
BACKUP copygroup group name in

management class class name is NOT
defined in policy set set name but is
domain domain name: files bound to this
management class will no longer be
backed up if/when set name is activated.

server has found a backup copy group named group
name for management class class name in the currently
active policy set, but the copy group is not defined for
the management class in the policy set being validated
or activated (set name). If policy set set name is
activated, files bound to management class class name in
domain domain name will no longer be eligible for
backup processing.
User response: If you want files bound to this
management class to be eligible for backup processing,
define an archive copy group for management class
class name by using the DEFINE COPYGROUP
command.
ANR1552W
ARCHIVE copygroup group name in

management class class name is NOT
defined in policy set set name but is
domain domain name: attempting to
archive files specifiying this
management class will fail if set name is
activated.

server has found an archive copy group named group
name for management class class name in the currently
active policy set, but the copy group is not defined for
the management class in the policy set being validated
or activated (set name). If policy set set name is
activated, attempting to archive files specifiying this
management class will fail. Existing archives bound to
this management class on the TSM server will be
expired based on the defmgmtclass values, or the
archive retention grace period for the policy domain, if
the default management class does not contain an
archive copygroup.
ANR1553W
DEFAULT Management class class name

in policy set domain name set name does
not have a BACKUP copygroup: files
will not be backed up by default if this
set is activated.

command. During policy set validation for policy set
set name in policy domain domain name, the server has
found that the default management class named class
name does not have a backup copy group. This message
warns the administrator that activation of this policy
set results in client files not being backed up, unless
they are bound to a management class (which has a
copy group) other than the default.
User response: To define a backup copy group for the
management class, issue the DEFINE COPYGROUP
command. To assign a different default management
class for the domain, issue the ASSIGN
DEFMGMTCLASS command. Take either action if you
want files to be backed up by default.
ANR1554W
DEFAULT Management class class name

in policy set domain name set name does
not have an ARCHIVE copygroup: files
will not be archived by default if this
set is activated.

command. During policy set validation for policy set
set name in policy domain domain name, the server has
found that the default management class named class
name does not have an archive copy group. This
message warns the administrator that activation of this
policy set will result in client files not being allowed
archive processing unless they are bound to a
management class (which has an archive copy group)
other than the default.
User response: To define a backup copy group for the
management class, issue the DEFINE COPYGROUP
command. To assign a different default management
class for the domain, issue the ASSIGN
DEFMGMTCLASS command. Take either action if you
want files to be eligible for archive processing by
default.

User response: To archive files specifying this
management class, define an archive copy group for
management class class name by using the DEFINE
COPYGROUP command.
159
ANR1555W ANR1559E
ANR1555W
The BACKUP copy group in

specifies a destination that does not
refer to a defined storage pool: storage
pool name. If this pool does not exist
activated, clients will fail when using
this management class to backup files to
the server.

command. During policy set validation for set name, the
server has found a backup copy group destination that
references an undefined storage pool named pool name.
If this storage pool is undefined when the policy set is
activated, backup or archive operations will fail for
clients with files bound to the management class whose
copy groups reference this pool.
COPYGROUP command. To change the destination to
refer to an existing storage pool, issue the UPDATE
COPYGROUP command. To define the storage pool, an
authorized administrator can issue the DEFINE
STGPOOL command.
ANR1556W
The ARCHIVE copy group in

specifies a destination that does not
refer to a defined storage pool: storage
pool name. If this pool does not exist
activated, clients will fail when using
this management class to archive files to
the server.

server has found a archive copy group destination that
references an undefined storage pool named pool name.
If this storage pool is undefined when the policy set is
activated, backup or archive operations will fail for
clients with files bound to the management class whose
copy groups reference this pool.
COPYGROUP command. To change the destination to
COPYGROUP command. To define the storage pool, an
STGPOOL command.
ANR1557W
The space management migration

destination in management class
management class name does not refer to a
defined storage pool: storage pool name. If
this pool does not exist when policy set
policy set name is activated, clients will
fail when using this management class
to migrate space-managed files to the
server.

server has found a space management migration
destination that references an undefined storage pool
named pool name. If this storage pool is undefined
when the policy set is activated, space management
migration operations will fail for clients with files
bound to the management class that references this
pool.
User response: To locate the management class that
refers to the undefined storage pool, issue the QUERY
MGMTCLASS command. To change the destination to
MGMTCLASS command. To define the storage pool, an
STGPOOL command.
ANR1558E
The space management migration

destination in management class
management class name in policy set policy
set name refers to copy storage pool:
storage pool name. Copy storage pools are
not a valid migration destination.

server has found a space management migration
destination that references a copy storage pool named
pool name.
System action: Server operation continues. The policy
set is not activated.
refers to the copy storage pool, issue the QUERY
refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.
ANR1559E
The copy group destination for type

copy group type in management class
management class name in policy set policy
set name refers to copy storage pool:
storage pool name. Copy storage pools are
not a valid copy group destination.

160
ANR1560E ANR1566E
server has found a copy group destination that
references a copy storage pool named pool name.
System action: Server operation continues. The policy
set is not activated.
refers to the copy storage pool, issue the QUERY
refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.
ANR1560E
Command: Invalid policy domain name domain name.

command fails because the policy domain name domain
name specified does not contain valid characters or
contains too many characters.
System action: Database changes for the command are
rolled back and server operation continues. The
command is not successful in changing the server
database.
policy domain name that conforms to these name
requirements. For information on the character and
length specifications for valid policy domain names,
platform.
ANR1561E
Command: Missing policy domain name.

command fails because the required policy domain
parameter has not been specified.
database.
valid policy domain name.
ANR1562E
Command: Policy domain description

exceeds length limit characters.

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

BACKRETN parameter - retention value.
Explanation: Server processing for the copy group

command command fails because the value (retention
value) specified for the BACKRETN parameter is not
valid.
database.
valid BACKRETN value. For valid BACKRETN values
for the DEFINE COPYGROUP or UPDATE
COPYGROUP commands, refer to the Administrators
Reference for your particular platform.
ANR1564E

ARCHRETN parameter - retention value.

value) specified for the ARCHRETN parameter is not
valid.
database.
valid ARCHRETN value. For valid ARCHRETN values
ANR1565E
Command: Invalid policy set name - set

name.

command fails because the policy set name set name
specified does not contain valid characters or contains
too many characters.
database.
policy set name that conforms to valid name
length specifications for valid policy set names, refer to
the Administrators Reference for your particular
platform.
ANR1566E
Command: Policy set description exceeds

length limit characters.

command fails because the policy set description
161
ANR1567E ANR1572E
characters allowed.
database.
shorter policy set description.
ANR1567E
Command: Invalid management class

name - class name.

command fails because the management class name class
database.
management class name that conforms to valid name
length specifications for valid management class names,
platform.
ANR1568E
Command: Management class description

exceeds length limit characters.

command fails because the management class
description specified is longer than the length limit
number of characters allowed.
database.
shorter management class description. Refer to the
Administrators Guide for your particular platform for
more information.
ANR1569E
Command: Invalid copy group name group name.

command fails because the copy group name group name
specified does not contain valid characters or contains
too many characters.
database.
copy group name that conforms to valid name
162

length specifications for valid copy group names, refer
to the Administrators Reference for your particular
platform.
ANR1570E
Command: Invalid copy frequency frequency value.

command command fails because the value (frequency
value) specified for the FREQUENCY parameter is not
valid.
database.
valid FREQUENCY value. For valid FREQUENCY
values for the DEFINE COPYGROUP or UPDATE
ANR1571E
Command: Invalid copy destination - pool

name.

specified for the copy group destination or for the table
of contents (TOC) destination does not contain valid
characters or contains too many characters.
database.
storage pool name that conforms to valid name
length specifications for valid storage pool names, refer
to the Administrators Reference for your particular
platform. For a list of names of defined storage pools,
issue the QUERY STGPOOL command.
ANR1572E
Command: Missing copy destination.

command command fails because the required copy
group destination is not specified.
database.
required copy group destination (DEST).
ANR1573E ANR1579E
ANR1573E
Command: Invalid copy type - type value.

command command fails because the value (type value)
specified for the TYPE parameter is not valid.
database.
valid TYPE value. For valid TYPE values for the
DEFINE COPYGROUP or UPDATE COPYGROUP
commands, refer to the Administrators Reference for
your particular platform.
ANR1574E
Command: Invalid version count for

VEREXISTS parameter - version value.

command command fails because the value (version
value) specified for the VEREXISTS parameter is not
valid.
database.
valid VEREXISTS value. For valid VEREXISTS values
ANR1575E

VERDELETED parameter - version value.

command command fails because the value (version
value) specified for the VERDELETED parameter is not
valid.
database.
valid VERDELETED value. For valid VERDELETED
values for the DEFINE COPYGROUP or UPDATE
ANR1576E

RETEXTRA parameter - retention value.

value) specified for the RETEXTRA parameter is not
valid.

database.
valid RETEXTRA value. For valid RETEXTRA values
ANR1577E

RETONLY parameter - retention value.

value) specified for the RETONLY parameter is not
valid.
database.
valid RETONLY value. For valid RETONLY values for
the DEFINE COPYGROUP or UPDATE COPYGROUP
ANR1578E

RETVER parameter - retention value.

value) specified for the RETVER parameter is not valid.
database.
valid RETVER value. For valid RETVER values for the
ANR1579E
Command: Invalid copy mode - mode

value.

command command fails because the value (mode value)
specified for the MODE parameter is not valid.
database.
valid MODE value. For valid MODE values for the
163
ANR1580E ANR1585E
ANR1580E
Command: Invalid copy serialization

mode - serialization value.

command command fails because the value (serialization
value) specified for the SERIALIZATION parameter is
not valid.
database.
valid SERIALIZATION value. For valid
SERIALIZATION values for the DEFINE COPYGROUP
or UPDATE COPYGROUP commands, refer to the
ANR1581E
Command: The option option is valid only

for backup copy groups.
Explanation: Server processing for the archive copy

group command command fails because the option
specified is only valid for backup copy group
definitions.
database.
User response: Reissue the command specifying valid
archive copy group options, or specify TYPE=BACKUP
if the intent is to operate on a backup copy group. For
valid archive copy group options, refer to the
Administrators Reference and Administrators Guide for
ANR1582E
Command: The option option is valid only

for archive copy groups.
Explanation: Server processing for the backup copy

group command command fails because the option
specified is only valid for archive copy group
definitions.
database.
User response: Reissue the command specifying valid
backup copy group options, or specifying
TYPE=ARCHIVE if the intent is to operate on an
archive copy group. For valid backup copy group
options, refer to the Administrators Reference and
Administrators Guide for your particular platform.
ANR1583E
Command: Copy frequency for archive

copy groups must be CMD - frequency
value is not valid.

group command command fails because a value other
than CMD has been specified for the FREQUENCY
parameter. The only value that may be specified for the
archive copy group FREQUENCY parameter is CMD.
database.
User response: Reissue the command specifying CMD
for the FREQUENCY parameter, or omitting the
FREQUENCY parameter because the default value for
FREQUENCY is CMD for archive copy groups. For
valid archive copy group options, refer to the
Administrators Reference and Administrators Guide for
ANR1584E
Command: Copy mode for archive copy

groups must be ABSOLUTE - mode value
is not valid.

group command command fails because a value other
than ABSOLUTE has been specified for the MODE
parameter. The only value that may be specified for the
archive copy group MODE parameter is ABSOLUTE.
database.
ABSOLUTE for the MODE parameter, or omitting the
MODE parameter because the default value for MODE
is ABSOLUTE for archive copy groups. For valid
archive copy group options, refer to the Administrators
Reference and Administrators Guide for your particular
platform.
ANR1585E
Command: Policy set ACTIVE cannot be

modified.

command fails because the policy set name ACTIVE is
specified. Objects in the ACTIVE policy set for a
domain may only be changed through activation of
another policy set.
database.
User response: Reissue the command specifying a
policy set other than ACTIVE. To copy the ACTIVE
policy set for a policy domain to another name so that
commands may be used to change its contents, issue
164
ANR1586E ANR1594E
the COPY POLICYSET command. Then to activate the
changes, issue the ACTIVATE POLICYSET command.
ANR1586E
Command: Invalid migration destination

- pool name.

specified for the migration destination is a copy pool. A
copy pool is not a valid migration destination.
database.
pool name that is not a copy pool. For a list of names
of defined storage pools, issue the QUERY STGPOOL
command.
ANR1587E
Command: Invalid copy group

destination - pool name.

specified for the copy group destination is a copy pool
or active-data pool. A copy pool or active-data pool is
not a valid copy group destination.
database.
pool name that is a primary pool, not a copy pool or
active-data pool. For a list of names of defined storage
pools, issue the QUERY STGPOOL command.
ANR1590E
Command: Policy domain domain name is

not defined.

name specified does not refer to a defined policy
domain in the server database.
database.
policy domain name that is defined in the server
database. For a list of the names of defined policy
domains in the server database, issue the QUERY
DOMAIN command.
ANR1591E
Command: Policy domain domain name is

already defined.

name specified refers to a policy domain that is already
database.
policy domain name that is not defined in the server
database. For a list of the names of defined policy
domains in the server database, issue the QUERY
DOMAIN command.
ANR1592E
Command: Policy domain domain name

still contains at least one policy set.
Explanation: Server processing for the delete

command command fails because the policy domain
name domain name specified refers to a policy domain
that still contains at least one policy set.
database.
User response: To delete the policy set from the policy
domain, issue the DELETE POLICYSET command.
ANR1593E

still contains at least one node.

command command fails because the policy domain
name domain name specified refers to a policy domain
that still contains at least one node. A policy domain
cannot be deleted if one or more client nodes are still
assigned to the domain.
database.
User response: To remove remaining nodes from the
policy domain, issue the REMOVE NODE command.
After all nodes are removed, issue the delete command
again.
ANR1594E

has no active policy set.
Explanation: Server processing for the update or

register node command command fails because the
policy domain name domain name specified refers to a
policy domain that does not have an active policy set
defined. Nodes cannot be assigned to policy domains
that do not have an active policy set.
165
ANR1595E ANR1600E
database.
User response: To activate a policy set for the
specified policy domain, issue the ACTIVATE
POLICYSET command. After a policy set has been
activated, client nodes may be assigned to the policy
domain.
ANR1595E
Command: Policy set set name is not

defined in policy domain domain name.

specified does not refer to a defined set in policy
domain domain name in the server database.
database.
policy set name that is defined in the policy domain.
For a list of the names of defined policy sets in the
policy domain, issue the QUERY POLICYSET
command.
ANR1596E
Command: Policy set set name is already

ANR1598E
Command: No default management class

has been assigned for policy set set name
in domain domain name.

command fails because the policy set set name in policy
domain domain name does not have a default
management class assigned.
database.
User response: To assign a default management class
in the policy set, issue the ASSIGN DEFMGMTCLASS
command.
ANR1599E
Command: Management class class name

is not defined in policy domain domain
name, set set name.

command fails because the management class name class
name specified does not refer to a defined management
class in policy set set name belonging to policy domain
domain name.
database.

specified refers to a policy set that is already defined in

policy set name that is defined in the policy domain.
For a list of the names of defined policy sets in the
policy domain, issue the QUERY POLICYSET
command.

database.
ANR1600E

policy set name that is not defined in the policy
domain. For a list of the names of defined policy sets in
the policy domain, issue the QUERY POLICYSET
command.
ANR1597E
policy set command: Policy set set name in

domain domain name still contains at
least one management class.
Explanation: The policy set command failed because the

set still contains at least one management class
definition.
User response: Remove the remaining management
classes from the policy set and reissue the command.
166
Command: Management class class name

is already defined in policy domain

command fails because the specified management class
name class name refers to a management class that is
already defined in policy set set name belonging to
database.
management class name that is not defined in the
policy set. For a list of the names of defined
management classes in the policy domain and policy
set, issue the QUERY MGMTCLASS command.
ANR1602E ANR1607E
ANR1602E
Command: Backup copy group group name

is not defined in policy domain domain
class name.

command fails because the backup copy group named
group name specified for management class class name
does not refer to a defined backup copy group in
policy set set name belonging to policy domain domain
name.
database.
copy group name that is defined. For a list of the
names of defined copy groups and management classes
in the policy domain or policy set, issue the QUERY
COPYGROUP command.
ANR1603E
Command: Backup copy group group name

is already defined in policy domain
domain name, set set name, management
class class name.

command fails because the specified backup copy group
named group name refers to a copy group that is
already defined for management class (class name) in
name.
database.
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
set, issue the QUERY COPYGROUP command.
ANR1604E
Command: Archive copy group group

name is not defined in policy domain
domain name, set set name, management
class class name.

command fails because the archive copy group named
group name specified for management class class name
does not refer to a defined archive copy group in policy
set set name belonging to policy domain domain name.
database.
names of defined copy groups and management classes

in the policy domain or policy set, issue the QUERY
COPYGROUP command.
ANR1605E
Command: Archive copy group group

name is already defined in policy
domain domain name, set set name,
management class class name.

command fails because the specified archive copy group
named group name refers to a copy group that is
already defined for management class class name in
name.
database.
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
set, issue the QUERY COPYGROUP command.
ANR1606E
Out of server LOG space in accessing

policy tables.

transaction for policy information because sufficient log
space is not available on the server.
System action: The policy operation is ended and
for use by the log and can issue the EXTEND LOG
volumes are used.
ANR1607E
Out of server DB space in accessing

policy tables.

transaction for policy information because sufficient
for use by the database and can issue the EXTEND DB

copy group name that is defined. For a list of the
167
ANR1608E ANR1614E
ANR1608E
Error fetching entry for domain domain

name, set set name.

database.
Explanation: An internal server database error occurs

while retrieving policy information for policy set set
name in domain domain name.

another management class name.

ANR1612E

representative.
ANR1609E
Policy error: unable to find management

class ID for class class name in policy set
set name belonging to domain domain
name.
Explanation: An internal server database error has

been encountered while retrieving policy information
for management class class name in policy set set name
belonging to policy domain domain name.
representative.
ANR1610E
Internal Server error: invalid copy type

copy type integer encountered in policy
set validation.
Explanation: An internal server database error has

been encountered while validating a policy set in
response to the VALIDATE POLICYSET or ACTIVATE
POLICYSET command.
representative.
ANR1611E
Command: Invalid management class

name - management class name.

command fails because the specified management class
name may not be used as a management class name.
168
Command: Management class management

class name in policy set set name, domain
domain name specifies
MIGREQUIRESBKUP=YES, but
contains no backup copy group.
Explanation: During policy set validation or activation

for policy set set name in policy domain domain name,
the server has found that the management class named
class name specifies the MIGREQUIRESBKUP=YES
parameter but does not contain a backup copy group.
Policy set validation or activation fails in this case
because it would not be possible to ensure that
space-managed client files are backed up prior to being
migrated to the server.
database.
User response: To define a backup copy group within
the management class, issue the DEFINE COPYGROUP
command. To change the MIGREQUIRESBKUP
parameter, issue the UPDATE MGMTCLASS command.
ANR1613E
Command: Invalid retention initiation retention initiation value.

initiation value) specified for the RETINIT parameter is
not valid.
User response: Issue the command again and specify
a valid RETINIT value. For valid RETINIT values for
the DEFINE copy group or UPDATE copy group
commands, refer to the Administrators Reference.
ANR1614E
Command: Invalid number of days for

RETMIN parameter - days value.
Explanation: The command fails.

database.
a valid RETMIN value. For valid RETMIN values for
ANR1615E ANR1621E
ANR1615E
Command: RETVER of NOLIMIT cannot

be specified with RETINIT value of
EVENT.

command command fails because the retain versions
value of NOLIMIT is not allowed with the retention
initiation value of EVENT. If this is the UPDATE copy
group command, at least one of the values might have
been defined already.
database.
a valid RETVER or RETMIN value. For valid values for
ANR1618W
Explanation: Processing for the copy group command

command detected that the new retain minimum
number of days is less than the number of days
currently stored for the copy group. The policy set
might not activate when archive retention protection is
active, because the retain minimum days value is not
allowed to decrease.
System action: The copy group is updated and system
User response: The copy group will be updated, but
the copy group might fail validation when the policy
set is validated or activated.
ANR1619E
ANR1616W
Command: the specified RETMIN value

(new days) will be ignored because the
RETINIT value is CREATION for
domain policy set management class.

command detected that a retain minimum number of
days value was specified either with the retention
initiation value of CREATION, or the current retention
initiation value stored for the copy group is
CREATION. The retain minimum number of days
value is not used when the retention initiation value is
CREATION. The copy group will be defined or
updated, but the RETMIN value will not be stored.
System action: The copy group is defined or updated
and system operation continues.
User response: The copy group will be defined or
updated, but the retain minimum number of days
value will not be stored. If you want to specify a
retention initiation value of EVENT, issue the update
command again.
ANR1617W
Command: the new RETVER value (new

days) is less than the value previously
stored (old days) for domain policy set
management class.

command detected that the new number of days to
retain versions is less than the number of days
currently stored for the copy group. If archive retention
protection is active, the policy set might not activate
because the retain versions value is not allowed to
decrease.
System action: The copy group is updated and system
User response: The copy group will be updated, but
the copy group might fail validation when the policy
set is validated or activated.
Command: the new RETMIN value (new

days) is less than the value previously
stored (old days) for domain policy set
management class.
The RETVER of NOLIMIT is not

allowed with the RETINIT value of
EVENT for domain policy set management
class.
Explanation: This message can be returned from the

server has found the the copy group in the policy has
specified an invalid combination of options. Retain
versions of NOLIMIT and retention initiation of
EVENT are not allowed. The policy will not be
validated or activated.
User response: Update the RETVER or REINIT values
in the copy group. For valid values, refer to the
Administrators Reference for your platform.
ANR1620E
The new RETVER value (new days) is

less than the value in the ACTIVE
policy (old days) for domain policy set
management class.

server has found that archive retention protection is
active and the copy group has a retain versions value
less than the value in the ACTIVE policy set. The
policy will not be validated or activated.
User response: Update the RETVER value in the copy
group.
ANR1621E
The new RETMIN value (new days) is

less than the value in the ACTIVE
policy (old days) for domain policy set
management class.

169
ANR1622E ANR1638W
server has found that archive retention protection is
active and the the copy group has a retain minimum
days value that is less than the value in the ACTIVE
policy set. The policy will not be validated or activated.
User response: Update the RETMIN value in the copy
group.
ANR1622E
Management class class name is not

defined in policy set set name, but is
defined in the active policy set for
domain domain name. Archive retention
protection is active, so validation fails.

server found a management class named class name in
the currently active policy set, but not defined in the
policy set being validated or activated (set name). When
archive retention protection is active, all management
classses in the active policy set must be included in the
policy set being validated. Policy validation will fail.
ANR1624E
Command: Invalid active pool list - active

pool list name.

command fails because the active pool list active pool list
specified does not contain valid pool.
database.
active pool list that conforms to these name
length specifications for valid active-data pool names,
platform.
ANR1635I
The server machine GUID, machine

GUID, has initialized.
Explanation: The specified globally unique identifier

(GUID) has initialized for the server machine.

User response: Define a management class with the
name specified in the message for the policy set. To
define the proper copy group attributes, reference the
management class definition in the active policy set or
copy the management class class name from the active
policy set to the policy set set name, using the COPY
MGMTCLAS command.
ANR1636W
The server machine GUID changed: old

value (old value), new value (new value).
Explanation: The globally unique identifier (GUID)

has changed for the server machine. The old and new
values are displayed.
ANR1623E
Management class class name in policy

set set name for domain domain name does
not have an archive copy group. Archive
retention protection is active, so
validation fails.

server found a management class named class name in
the policy set being validated or activated (set name).
The management class does not have an archive copy
group. When archive retention protection is active, all
management classses in the policy set being validated
must have an archive copy group. Policy validation
will fail.
User response: Define an archive copy group in
specified management class, then try the validation
again.
ANR1637W
Error (error) occurred initializing the

server machine GUID.
Explanation: An error occurred while initializing the

server machine globally unique identifier (GUID).
User response: Handle problems appropriately. A
write error may occur because the server needs root
authority to write the GUID. A read error may occur if
the server does not have authority to read the GUID.
Other error codes are received from the GUID utility.
ANR1638W
Error (error) occurred initializing the

server machine GUID. Old value was
old GUID.
Explanation: An error occurred while initializing the

server machine globally unique identifier (GUID). The
old value is displayed.
User response: Handle problems appropriately. A
170
ANR1639I ANR1647E
write error may occur because the server needs root
authority to write the GUID. A read error may occur if
the server does not have authority to read the GUID.
Other error codes are received from the GUID utility.
ANR1639I
Attributes changed for node nodeName:

changed attribute list.
Explanation: The TCP/IP name or address, or the

globally unique identifier (GUID) has changed for the
specified node. The old and new values are displayed
for entries that have changed.
ANR1640E
There is no data mover defined for node

node name.
Explanation: To perform the requested operation, the

specified node must have an associated data mover
defined.
ANR1644E
Explanation: A command has been issued to move

node data for the specified storage pool but there is
already a move node data operation in progress for one
or more nodes that have been specifed for that same
storage pool.
command.
User response: Check the activity log for a previous
MOVE NODEDATA command to determine what
processes for moving node data are in progress for the
storage pool. Reissue the command for the node(s) and
storage pool you desire that are not already in progress,
or, reissue the command after the move node data
process ends.
ANR1645I
System action: The requested operation fails.

User response: Define a data mover for the node and
retry the operation.
ANR1641E
command: The node node name has a type

that is not allowed for this command.
Command: Move node data operation

already in progress for storage pool
storage pool.
Command: Data for node node name,

filespace filespace name, FSID filespace ID
will be moved.
Explanation: The server will move data for the

specified filespace name and node name based on the
criteria entered in the MOVE NODEDATA command.
System action: The server moves data for the
specified node and filespaces.
Explanation: The node is not the correct type to be

used with this command.
ANR1646I
User response: Re-run the command with a node of

the correct type.
ANR1642E
command: The node node name is locked.
Command: Node Node name, no filespaces

found to move for this node.
Explanation: A node and filespace were entered in a

MOVE NODEDATA command but no filespaces were
found for the specifed node.
Explanation: The node is locked and cannot be used

in this command.
System action: The server continues to move other

filespaces for any other nodes specified in the MOVE
NODEDATA command.
User response: Unlock the node and re-run the

command.
ANR1647E
ANR1643I
Command: All file spaces for node node

name, will be moved.
Explanation: The server will attempt to move data for

all the file spaces for the specified node name based on
the criteria entered in the MOVE NODEDATA
command.
System action: Server moves data for the indicated
node.
Cannot find file space name for node

node ID, file space file space ID.
Explanation: The server could not obtain filespace

information for that node.
representative.
171
ANR1648W ANR1656E
ANR1648W
Command:This command will move data

for nodes stored in volumes in storage
pool source storage pool to other volumes
within the same storage pool; the data
will be inaccessible to users until the
operation completes.
Explanation: A MOVE NODEDATA command has

been entered that will move data to other volumes in
the same storage pool. While the data is being moved,
it will not be available to users.
System action: The administrator is asked whether to
continue.
User response: Enter 'Y' to continue or 'N' to end the
process.
ANR1649W
Command:This command will move data

for nodes stored in storage pool source
storage pool to storage pool destination
storage pool; the data will be inaccessible
to users until the operation completes.
Explanation: A MOVE NODEDATA command has

been entered that will move data from the source
storage pool to the destination storage pool shown.
While the data is being moved it, will not be available
to users.
continue.
User response: Enter 'Y' to continue or 'N' to end the
process.
ANR1650E
Server server name is not defined.
Explanation: The server name was not created using

the DEFINE SERVER command. This entry was created
using the REGISTER NODE NODETYPE=SERVER
command and is not a valid reference.
ANR1652E
Explanation: An attempt to a server definition for

server name from any device configuration files failed.
System action: The current action for the device class
referring to this server fails.
User response: Please verify the existence of a device
configuration file and the DEFINE SERVER stanza
within that file.
ANR1653E
ANR1651E
Server information for server name is not

available.
Explanation: The information for server name was not

available.
Resource lock acquisition for server

server name failed.
Explanation: The acquisition of the resource lock for

server server name failed.
User response: Retry the action referring to the device
class that refers to this server name. If the lock failure
persists, please contact your service representative.
ANR1654E
Server server name will not be written to

a device configuration file.
Explanation: An error occurred accessing the

information for server name while trying to write this
information to a device configuration file.
System action: This DEFINE SERVER entry is not
processing.
User response: Verify that the necessary DEFINE
SERVER entries were written to a device configuration
file. If this error persists, please contact your service
representative.
ANR1655E

User response: The device class referring to this node
as the SERVERNAME should be updated to refer to a
valid server entry. Specifically, it should refer to an
entry created using the DEFINE SERVER command.
Server information for server name could

not be read from a device configuration
file.
Failure processing password for Server

server name when writing a device
configuration file.
Explanation: An error occurred processing the

password for server name while trying to write this
System action: This DEFINE SERVER entry is written
to the device configuration file without the password.
User response: The password needs to be specified
after PASSWORD= for this DEFINE SERVER entry in
the device configuration file.
System action: The current server action fails.
ANR1656E
User response: Please review any other messages

prior to this message to determine the cause of the
failure.
Explanation: An error occurred writing the server

Failure writing server definitions to a

device configuration file.
System action: The BACKUP DEVCONFIG action

fails.
172
ANR1657E ANR1666E
User response: Check that the device configuration
file exists and that the file system the file resides on is
not out of space.
ANR1657E
Command: Invalid server or group name

- server or group name.
ANR1661I
Server server name deleted.
Explanation: In response to a DELETE SERVER

command, the requested server has been removed from
the system.
Explanation: The command shown specifies an invalid

server or server group name.

command.
ANR1662I

name.
ANR1658E
Command: Failure determining

NODENAME for server server name.
Explanation: The command shown was unable to

determine a node name either from the NODENAME=
parameter on this command or from the server name
previously set using the SET SERVERNAME command.
command.
node name parameter or else update the server name
using the SET SERVERNAME command so that a valid
name is available.
ANR1659E
Command: Server or server group server

or group name is already defined.
Explanation: A DEFINE SERVER or DEFINE

SERVERGROUP command has been entered that
specifies a server or server group name that already
exists. The name specified must be a unique name. It
must not duplicate a node name used by a registered
node, a server name used by a defined server, or a
server group name used by a defined server group.
command.
User response: To define the server or server group,
reissue the command and specify a different name.
ANR1660I
Server server name defined successfully.
Explanation: The requested server has been defined to

the system in response to a DEFINE SERVER
command.
Server server name updated.
Explanation: One or more attributes of a server have

been updated by an UPDATE SERVER command.
ANR1663E
command: Server server name not defined
Explanation: The server server name is not defined to

the system.
ANR1664W
Command: Server server name is currently

in use.
Explanation: The command shown specifies a server

that is currently in use. The server is referenced by one
or more of the following: a device class of
DEVTYPE=SERVER that specifies this server for the
SERVERNAME= parameter, it is defined as the event
server, or a connection with this server is currently
open and in use.
command.
User response: Reissue the command at a later time.
In order to delete the server specified, it must not be
currently connected to the server, it may not be
referenced in a device class, and it can not be defined
to be the event server.
ANR1665E
command: Failure updating password for

server server name.
Explanation: An error occurred updating the

password for server name.
User response: Re-try the command specifying a
different password.

ANR1666E
command: FILEAGGR not allowed with

NODETYPE=SERVER.
Explanation: The FILEAGGR= parameter may not be

specified with the NODETYPE=SERVER parameter also
being specified.
173
ANR1667E ANR1677I
User response: Reissue the command command
without the FILEAGGR= parameter if this is a
NODETYPE=SERVER.
ANR1667E
command: Action not permitted against

node node name.
Explanation: The command is not permitted against

the entry for node node name. This node entry has a
NODETYPE of SERVER.
ANR1672I
Explanation: A query was issued to get the name of

the event server; however, no event server is currently
defined.
User response: If an event server definition is desired,
use the DEFINE EVENTSERVER command.
ANR1673I

ANR1668E
command: Not allowed for server server

name.
Explanation: The DELETE SERVER command is not

permitted for server server name. The specified server is
either the event server or else it is a node entry rather
than a server definition.
User response: If the specified server is the event
server, and you want to delete it, issue the DELETE
EVENTSERVER command and then reissue the
DELETE SERVER command. To remove a node entry,
issue the REMOVE NODE command for the specified
name.
Server event server name is defined as the
event server.
Explanation: The specified server is defined.

ANR1670E
Server event server name is already

defined as the event server. You must
issue the DELETE EVENTSERVER
command before defining a new event
server.
Server group group name defined

successfully.
Explanation: The requested server group is defined to

the system in response to a DEFINE SERVERGROUP
command.
ANR1674I
Member member name defined

successfully in server group group name.
Explanation: The requested member is defined in the

server group in response to a DEFINE GRPMEMBER
command.
ANR1675I
ANR1669I
No event server is currently defined.
Server group server group name deleted.
Explanation: The requested server is removed from

the system in response to a DELETE SERVERGROUP
command.
ANR1676I
Member member name deleted from

server group server group name.
Explanation: The requested member is removed from

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
ANR1671I
Explanation: One or more attributes of a server group

is updated by an UPDATE SERVERGROUP command.
The event server definition has been

deleted.
Explanation: The event server definition has been

deleted.
User response: If an event server definition is desired,
use the DEFINE EVENTSERVER command.
174
Server group server group name updated.

ANR1678I ANR1688I
ANR1678I
Server group original server group name

renamed new server group name.
Explanation: A server group is renamed by a

RENAME SERVERGROUP command. The original
name is not valid.
ANR1679E
Command: Server group server group name

not defined.
Explanation: The server server group name is not

defined to the system.
User response: Retry the command specifying an
existing group.
User response: Retry the command specifying existing

server or group.
ANR1684E
Explanation: The command part of a routed command

may not contain route information itself. The allowable
syntax for routed commands is :. The command may
not contain route information. Only one level of routing
is allowed.
System action: Routed commands where the
command portion contains additional routing
information are not processed.
User response: Reissue the command without
specifying route information in the command portion
of this routed command.
ANR1685I
ANR1680E
Command: Member member name not

defined in server group server group
name.
Route:command: Routed commands

cannot be routed.
Server group server group copied to

server group new server group.
Explanation: The member member name is not defined

in server group server group name.

the COPY SERVERGROUP command. The server group
named server group is copied to the server group named
new server group.
User response: Retry the command specifying an

existing member of the group.

ANR1686I
ANR1681E
Command: Member member name is

already in server group server group
name.
Explanation: The member member name is defined in

server group server group name.
User response: Retry the command and specify a new
member name.
ANR1682E
A group cannot be a member of itself.
Explanation: The member and group name are the

same. A group may not be a member of itself.
User response: Retry the command and specify
another member name.
ANR1683E
Command: Member member name not

defined.
Member member name moved from

server group group name to server group
new group name.
Explanation: The requested member member name is

moved from server group group name to the server
group new server group in response to a MOVE
GRPMEMBER command.
ANR1687I
Output for command command issued

against server server name follows:
Explanation: The output for the command issued

against the indicated server follows this message.
ANR1688I

against server server name completed.
Explanation: The member member name is not defined

to the system. Server group members must be a
defined server or server group.
Explanation: This message marks the end of the

output for the command specified that was issued
against the indicated server.

175
ANR1689E ANR1697I
ANR1689E

against server server name terminated.
Explanation: An error condition occurred causing the

output for the command issued against the specified
server to be terminated.
User response: Retry the command against the
requested server once the error condition has been
resolved. If the cause of the error can not be
determined, please contact your local service
representative.
ANR1690E
Error sending command command to

server server name.
Explanation: An error was encountered sending the

specified command to the server indicated.
System action: This command is not issued against

the server specified. The process will attempt to issue
the command against any other servers that were
specified for the command routing information.
error. Retry routing this command to the indicated
server after the cause of the error has been determined
and resolved. If the error cannot be isolated and
resolved, contact your service representative.
ANR1694I
Server server name processed command

command and completed successfully.
Explanation: The server indicated processed the

command successfully.

representative.
ANR1691E
Error receiving response from server

server name for command command.
Explanation: An error was encountered receiving the

response from the server indicated for the command
that was issued against it.
ANR1695W

command but encountered warnings. However, the
warnings did not prevent the execution of the
command.
ANR1696E

representative.
ANR1692E
Response for command command from

server server name contains invalid data.
Explanation: The output returned from the specified

server for the command that was issued, contains
invalid output. The command response can not be
processed.
System action: Output processing for this command
response terminates.
User response: Please contact your local service
representative.
ANR1693E
Unable to issue command command

against server server name - failure
starting thread.
Explanation: A thread could not be started to issue

the specified command against the server indicated.
176
Server server name processed command

command but completed with warnings.
Server server name attempted to process

command command but encountered
errors.

command but encountered errors. These errors
prevented the successful completion of the command.
User response: Examine any error messages issued on
either the server sending the command or else the
server executing the command to determine the cause
of the failure. Reissue the command once these errors
are corrected.
ANR1697I
Command command processed by total

number for servers server(s): number of
successful servers successful, number of
servers with warnings with warnings, and
number of servers with errors with errors.
Explanation: The indicated command was processed

by the number of servers specified. For the total
number of servers, the number indicated were
successful, the number indicated encountered a
warning condition but processed anyway, and finally,
the number indicated encountered errors and could not
process.
ANR1698I ANR1706I
ANR1698I
Command command was not issued

against any other servers.
Explanation: The indicated command was not issued

against any other server. Either the routing information
did not resolve to any valid servers or else failures
occurred issuing the command against the required
servers.
User response: Check to see that valid route
information was provided for the command or else
check the activity log for error messages that indicate
why the command was not issued to the other servers.
ANR1699I
Resolved route information to number of

servers server(s) - issuing command
command against server(s).
Explanation: The route information was resolved to

the number of servers indicated. The specified
command will be issued against those servers.
ANR1700E
Unable to resolve route information to

any server(s).
Explanation: The route information provided for this

command did not resolve to any server names or group
names. Because of this, the command will not be
issued.
User response: Examine the route information
provided. Reissue the command providing correct route
information.
ANR1701E
Command: No matching servers defined.
Explanation: No matching servers are found for the

specified command.
User response: Issue the command and specify
different servers.
ANR1702W
Skipping server name - unable to

resolve to a valid server name.
Explanation: The server name specified is being

skipped because it could not be resolved to a valid
server name.
User response: Reissue the command providing the

correct server name.
ANR1703E
Failure resolving server names.
Explanation: An error occurred while resolving the

server names. Specifically, the resolution of the server
names has terminated because of a significant failure.
console for other messages about the cause of the
failure. Once the cause has been resolved, reissue the
command.
ANR1704E
Failure obtaining or using credentials

for administrator admin name.
Explanation: An error occurred obtaining or using the

credentials for the administrator referenced.
User response: If the administrator
SERVER_CONSOLE was being used for a PING or
VALIDATE LANFREE command, the command may
fail. The administrator SERVER_CONSOLE is not able
to perform these commands where the source server,
the target server, or both servers have authentication
enabled. The command should be retried using an
administrator other than SERVER_CONSOLE.
Check the activity log and server console for other
messages about the cause of the failure. Once the cause
has been resolved, reissue the command.
ANR1705W
Ping for server server name was not able

to establish a connection.
Explanation: The ping command was unable to

establish a connection to the server specified. This
could indicate a problem on the server issuing the ping,
a problem with the communication connection between
the two servers, or else it is a problem with the other
server.
on the server issuing this command. Next, check the
communication connection between the two servers.
Also, check the server definition and password on both
the server issuing the command and the server
specified. And finally, verify that the server specified is
running.
ANR1706I
Ping for server server name was able to

establish a connection.
Explanation: The ping command was able to establish

a connection to the server specified.
177
ANR1707I ANR1715E
on the server issuing this command. Next, check the
communication connection between the two srevers.
And finally, verify the operation of the server specified.
ANR1707I
Server information not complete,

crossdefine not allowed.
Explanation: The SERVERHLADDRESS,

SERVERLLADDRESS or SERVERPASSWORD has not
been set for this server. These are required for the
CROSSDEFINE option on the define server command.
User response: Use the QUERY STATUS command to
find what values need to be set. An authorized
administratormust issue the SET SERVERHLADDRESS,
SET and SERVERLLADDRESS or SET
SERVERPASSWORD command to set the missing
values.
User response: Retry the command specifying the

proper name.
ANR1711E
Error accessing the server or server

group name Name.
Explanation: A server operation attempted to access

the server name or server group name specified. An
error occurred while trying to access the information
for this server name or server group name.
System action: The server operation fails.
User response: Review the activity log to try to
determine the cause of the failure. If a cause can not be
determines, please contact your local service
representative.
ANR1712W
Command routing not allowed from

server console.
Explanation: Command routing is not allowed from

the server console.
ANR1708I
Define server for Server name failed

because the crossdefine failed.
Explanation: The define server command failed

because the crossdefine parameter was included, and
the crossdefine was not successful.
User response: Check this server, and the server being
defined for other messages indicating the reason for the
failure.
User response: Reissue the command from an

Administrative client.
ANR1713I
Command command issued against

server server name.
Explanation: The specified command has been sent to

the indicated server. The command is to terminate the
specified server, no confirmation will be recieved.
ANR1709E
Command.: Failure determining current

usage for server or group name Server
name.
ANR1714W
Explanation: The specified command failed to

determine the current use of the server name or server
group specified.
User response: Retry the command. If it continues to
fail and the cause of the failure can not be determined,
please contact your local service representative.
ANR1710E
Command.: Name Name not valid for this

command.
Explanation: The name specified for this command is

not valid for this operation. The first case is that a
server name was specified for a command requiring a
server group name. The other case is where a server
group name was specified for a command requiring a
server name.
178
The password for administrator

administartor name has expired. The
password for this administrator must be
updated on the configuration manager
server server name.
Explanation: The password for the named

administrator has expired, but the administrator is a
managed object on this server. The password must be
updated on the named configuration manager server.
System action: The administrator is allow access to
the server.
User response: Change the administrators password
on the named configuration manager server.
ANR1715E
Event server cannot be deleted - it is

currently active.
Explanation: The event server cannot be deleted since

it is currently active for event logging.
System action: The server does not delete the event
server entry.
ANR1716I ANR1724W
User response: In order to delete the event server, it
must not be currently active for event logging. To stop
event logging to the event server issue END
EVENTLOGGING EVENTSERVER. Then reissue the
DELETE EVENTSERVER command.
ANR1716I
Server cannot be crossdefined to itself,

crossdefine not allowed.
System action: The MOVE NODEDATA process fails.

User response: Provide a valid primary storage pool
name as the destination storage pool if the source pool
is a primary storage pool. If the source pool is a copy
storage pool do not specify a destination pool, or,
specify the same copy storage pool as the destination
pool.
Explanation: An attempt was made to crossdefine the

server to itself.
ANR1720I
Explanation: In response to the DEFINE PATH

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

ANR1717E
Command: Command failed Non-Compatible Filespace name types

have been specified.
Explanation: A server command has been entered but

cannot be processed because Non-Compatible Filespace
name types have been specified.
command.
User response: Specify compatible filespace names.
Unicode to Unicode or Non-Unicode to Non-Unicode.
ANR1718E
Command: Reconstruction of file

aggregates is supported only for
movement in which the source and
target storage pools are
sequential-access.
Explanation: The indicated command specifies that

file aggregates be reconstructed during a move
operation for which reconstruction is not supported.
Aggregates are reconstructed only when both the
source storage pool and the target storage pool are
sequential-access.
A path from source name to destination

name has been defined.

ANR1721I

name has been deleted.
Explanation: In response to the DELETE PATH

command or to an UPDATE DEVCLASS command
with the MOUNTLIMIT parameter, the path from the
source name to the destination name has been deleted
in the server database.
ANR1722I

name has been updated.
Explanation: In response to the UPDATE PATH

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

command.
User response: Reissue the command without

specifying that aggregates should be reconstructed.
Alternatively, specify a move operation involving
transfer of data within a sequential-access storage pool
or between two sequential-access storage pools.
ANR1723E
ANR1719E
Storage pool storage pool name specified

on the MOVE NODEDATA command is
not a valid pool name or pool type.
Explanation: If the source storage pool specified in the

command is a primary storage pool, then the
destination storage pool specified must also be a
primary storage pool. If the source storage pool is a
copy storage pool, then the specified destination
storage pool must be the same storage pool as the
source storage pool.
A path is already defined using source

name and destination name.

command, the server determines that a path with the
same source name and the same destination name
already exists in the server database.
User response: Correct the source name or destination
name and re-enter this command.
ANR1724W
Command: Server server name is currently

in use.
Explanation: The command shown specifies a server

that is currently in use. The server is referenced in a
179
ANR1725E ANR1734E
PATH used for LANFree access to a FILE device type
drive in a shared library.
the destination in a path that still exists in the server

database.

command.

In order to delete the server specified, it must not be
currently connected to the server, it may not be
referenced in a device class, it can not be defined to be
the event server, and it cannot be referenced within a
PATH definition as a FILE device type drive.
ANR1725E
resource name is not defined.

command, a resource name was provided that has not
been defined.
User response: Delete the existing path and reissue

this command.
ANR1730I
Explanation: The data mover has been defined in the

server database.
ANR1731I

User response: Define the source name or the
destination name and re-enter this command.
Data mover mover name has been

defined.

deleted.
Explanation: The data mover has been deleted in the

server database.
ANR1726E
A operation using the path from

sourcename to destname is currently being
used.
Explanation: This path was in use when the command

was entered. The attributes of a path may not be
changed while it is being used.
User response: Wait until the operation using this
path is complete, or cancel the operation using this
path, and then reissue the command.
ANR1727E
A path from sourcename to destname does

not exist.

ANR1732I

updated.
Explanation: The data mover has been updated in the

server database.
ANR1733E
Data mover mover name is already

defined.
Explanation: The path being updated or deleted does

not exist.
Explanation: A DEFINE DATAMOVER command was

entered for a data mover that already exists in the
server database.

source or destination name or define a new path.
User response: Use the UPDATE DATAMOVER to

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

mover must be attached to a SCSI library.
ANR1734E
Data mover mover name is not defined.
Explanation: An UPDATE DATAMOVER command

was entered for a data mover that does not exist in the
server database.

drive name.
ANR1729E
A path using the data mover source name

still exists.
Explanation: In the DELETE DATAMOVER command,

the data mover name supplied is either the source or
180
User response: Correct the data mover name or use

the DEFINE DATAMOVER command to define a new
data mover.
ANR1735E ANR1744E
ANR1735E
Data mover data mover is currently being

used.
Explanation: A data mover was in use when the

command was entered. The attributes of a data mover
may not be changed while it is being used.
User response: Wait until the operation using this
data mover is complete, or cancel the operation using
this data mover, and then reissue the command.
ANR1736E
Command: Parameter parameter length is

invalid.
Explanation: The specified server command has been

entered with a parameter that is longer or smaller in
length than the allowed length.
User response: Reissue the command and enter the
proper syntax.
ANR1737E
Command: Device name device specified

is invalid.
Explanation: The specified command has been entered

with an invalid device name.
ANR1740E
For the path defined from disk node

name disk name received lun actual lun
from client, expected expected lun.
Explanation: A client attempted to backup the disk,

but the server path definition was different than that
which was detected by the client.
User response: Correct the path definition from the
disk to a datamover.
ANR1741E
For the path defined from disk node

name disk name received serial number
actual serial from client, expected expected
serial.
Explanation: A client attempted to backup the disk,

but the server path definition was different than that
which was detected by the client.
User response: Correct the path definition from the
disk to a datamover.
ANR1742E
The disk node name disk name is not

online.
System action: The command failed.
Explanation: An operation requested the specified

disk. The disk cannot be used because it is not online.

device name.
ANR1738I
Unable to begin a server-free operation

with data mover data mover name;
received error error.
Explanation: The server attempted to begin a

server-free operation with the specified data mover but
was unable to do so.
User response: The server-free data movement will
fail and the client may retry the request using LAN or
LAN-free data transfer.
ANR1739I
Unable to update configuration of data

mover data mover name; received error
error.
Explanation: The server attempted to notify the

specified data mover that a change in the SAN requires
that the configuration be updated. The update failed
because the data mover was busy.
User response: The data mover must finish its current
operation before the configuration can be updated. The
server-free data movement will fail and the client will
retry the request using LAN or LAN-free data transfer.
User response: Determine the reason for the disk

being offline; if possible, update the disk status to
online.
ANR1743E
The path from data mover datamover

name to disk node name disk name is not
online.
Explanation: An operation requested the specified

disk. The disk cannot be used because the path from
the datamover to the disk is not online.
User response: Determine the reason for the path
being offline; if possible, update the path status to
online.
ANR1744E
The world wide name is invalid for the

destination of the path being defined.
Explanation: A path was being defined from a

datamover to a destination and that destination has an
incorrect world wide name specified.
User response: Update the destinations definition
with the correct world wide name.
181
ANR1745I ANR1754E
ANR1745I
Unable to discover SAN devices.

Function is busy.
Explanation: The SAN device discovery function is

busy. The requested query cannot be completed at this
time.
drive definition is correct and that the drive is

operational.
ANR1750E
The server detected an internal error,

return code = return code.
Explanation: An unexpected error occured during

server operation.
User response: Reissue the request when current

queries have completed.
ANR1746E
The path from data mover datamover

name to drive library name drive name is
not online.
Explanation: A server-free operation requested the

specified device. The device cannot be used because the
path from the datamover to the device is not online.
User response: Determine the reason for the path
being offline; if possible, update the path status to
online.
ANR1747W
The data mover datamover name was not

found on the SAN. The data mover
definition has been marked offline.
Explanation: During device discovery on a storage

area network a device was not found that has the same
serial number as the data mover defined to TSM.
User response: Verify that the serial number of the
data mover definition is correct and that the data
mover is operational.

found and resolved, retry the operation. If the failure
cannot be found, contact your service representative for
assistance in resolving the problem.
ANR1751I
Explanation: In response to the DEFINE DISK

command, the disk has been defined in the server
database.
ANR1752E
The disk node name disk name was not

found on the SAN. The path definition
for this disk has been marked offline.

serial number as the disk defined to TSM.
disk definition is correct and that the disk is
operational.
ANR1749W
The drive library name drive name was not

found on the SAN. The path definition
for this drive has been marked offline.

serial number as the drive defined to TSM.
182
Disk disk name is already defined.
Explanation: A DEFINE DISK command was entered

for a disk that already exists in the server database.
User response: Use the UPDATE DISK command to
change the attributes of this disk. Otherwise, use a
different disk name.
ANR1753E
ANR1748W
Disk disk name has been defined.
Disk disk name is currently being used.
Explanation: A disk was in use when the command

was entered. The attributes of a disk may not be
changed while it is being used.
User response: Wait until the operation using this disk
is complete, or cancel the operation using this disk, and
then reissue the command.
ANR1754E
Disk disk name is not defined.
Explanation: An UPDATE, DELETE or client function

requested the specified disk, but the disk has not been
defined to the server.
User response: Correct the disk name or use the
DEFINE DISK command to define a new disk.
ANR1755I ANR1763E
ANR1755I
Disk disk name has been updated.
Explanation: In response to the UPDATE DISK

command, the disk attributes have been updated in the
server database.
ANR1756I
Disk disk name has been deleted.
Explanation: In response to the DELETE DISK

command, the disk has been deleted in the server
database.
the destination storage pool was skipped. A storage

pool may be skipped because it does not have enough
available space, or because it has a MAXSIZE value
that is less than the size of the object to be inserted.
User response: Ensure that the destination storage
pool is available, has an adequate MAXSIZE setting,
and has adequate space. The MAXSIZE setting may be
changed using the UPDATE STGPOOL command.
Space may be added to the storage pool by checking in
scratch volumes or defining new volumes in the
storage pool. If volumes in the destination storage pool
are offline, use the VARY ONLINE command to vary
them online and make them available for use. Correct
the problem and reissue the command.

ANR1761E
ANR1757E
A path using the disk disk name still

exists.
Command: Command failed for node

node name, filespace filespace name storage media is inaccessible.
Explanation: The name supplied in a DELETE DISK

command is the destination in a path that still exists in
the server database.
Explanation: The indicated command failed because

required storage media is unavailable.
User response: Ensure that there are sufficient

volumes available for storing backups and that any
volumes required for restore are checked in and
available. Correct the problem and try the command
again.
User response: Delete the existing path using the

DELETE PATH command and re-enter the DELETE
DISK command.
ANR1758E
A path from disk node name disk name to

a datamover cannot be determined.
Explanation: During a backup operation a path from

the disk cannot be found.
ANR1762E

node name, filespace filespace name mount point unavailable.

sufficient mount points are not available.
User response: Define a path from the disk to a

datamover.
ANR1759E
Command: A device with SCSI

datamover capabilities was not found in
the system configuration for datamover
datamover name.
Explanation: The scsi address could not be

determined for a device that is capable of performing
datamover operations.
User response: Verify that the hardware that can
perform SCSI datamover operations is installed and
powered on.
ANR1760E

node name, filespace filespace name destination storage pool storage pool was
skipped.
User response: Ensure that sufficient mount points are

available and working correctly. Correct the problem
and try the command again.
ANR1763E
Command: Command failed - see

previous error messages or view the
activity log.
Explanation: The indicated server command has

failed. This message is always preceded by one or more
other error messages which provide more detail about
why the command failed.
to determine the source of the error. Use the QUERY
command again.

183
ANR1764E ANR1771E
ANR1764E
Command: Command failed - loadable

module module name is not available.
Explanation: The indicated server command has failed

because it requires the availability of the specified
loadable module, but the module is not loaded.
User response: Make sure the necessary loadable
module is available for your platform. Not all modules
are available on all platforms. If the module is available
for your platform and is installed, contact your service
representative for assistance.
ANR1765E
Command:The number of copy threads

entered, copythreads, exceed the
capabilities of the datamover.
Explanation: A datamover has an upper limit of the

number of copy threads that it is capable of executing.
The copythreads parameter provided is greater than
this limit.
User response: Make sure the value entered for the
copythreads parameter is less than the maximum for
this datamover. Using the default for the number of
copythreads sets the number of copythreads to the
datamovers maximum value.
ANR1766I
The number of sessions currently active

for datamover datamover, exceed the
number of copy threads defined for this
datamover.
Explanation: The datamover definition has a paramter

that is used to limit the number of operations involving
that datamover. This limit was reached.
System action: The operation continues using another
method.
User response: Verify that the number of copy threads
in the datamover definition is sufficient enough to
allow mutliple server-free operations, or define another
datamover to handle additional server-free operations.
datamover to the disks and drives. If a path is defined

from a datamover to a drive in a library then all drives
in that library should have paths defined from that
same datamover. A path may have to be updated to
specify online=yes.
ANR1768E
Explanation: The device name provided in the

command is already used by an existing path.
System action: The command is not processed.
User response: Specify a valid DEVICE parameter that
is not used by any other drive or library.
ANR1769E
A datamover with a online path to both

the disk, nodename diskname, and the
drive, libraryname drivename cannot be
found.
Explanation: To perform server-free data movement, a

path must exist from the datamover to both the disk
and the drive. If either path is not defined or is offline
to all datamovers defined then the data movement
cannot occur via server-free.
System action: The operation continues using another
method.
User response: Define the appropriate paths from a
184
Command: Command failed - multiple

actions between commit actions not
allowed.
Explanation: A server script that performs multiple

actions between commit actions is not allowed. For
example, deletion of multiple paths before each of the
deletions is committed is not allowed.
command.
User response: Rewrite the script or macro so that no
new command is issued until the previous command is
committed.
ANR1770E
Processing for session session id found

destination new destination. Expected
current destination.
Explanation: While processing a remote image

operation, the specified session was working with the
current destination. But the server received a client
request with a new destination name.
User response: From the client, quit the current
remote image request. Reissue the request, if desired.
ANR1771E
ANR1767W
Command: The device name provided

conflicts with a device name that is
already in use.
The path from remote server remote

server name to destination destination name
with the destination device type is not
valid.
Explanation: The library manager receives a command

to update the path for the remote server. The device
type field of the destination device is not valid. The
destination for update path from remote server must be
either drive or library.
User response: Determine why the device type field of
the destination device is not valid.
ANR1772E ANR1779I
ANR1772E
The path from source source name to

destination drive name is taken offline.
ANR1776I
Explanation: The path is now marked offline.

System action: The path is inaccessible.

updated, however a connection to the
data mover failed. Please check the
attributes of the file server specified in
the update command.
User response: Determine the reason the path is

inaccessible, such as a hardware problem. Make any
needed corrections. Then, issue the the UPDATE PATH
command with the ONLINE=YES option to make the
path online.
Explanation: The data mover has been updated in the

server database, however the server cannot connect to
the file server associated with the data mover. The
connection failed because of one of the following
possible reasons:
ANR1773W
v One of the parameters specified during datamover

update was incorrect: TCP/IP address of the file
server, user id, password, TCP/IP port
Unable to update the path in the

database path source name and drive drive
name .
v File server is not accessible
Explanation: The system is unable to update the path

information in the database table.
v NDMP server limits the number of opened NDMP

sessions
System action: .
System action: The data mover definition is updated.
User response: Check that the file server associated

with the data mover is accessible through the network;
check each of the attributes specified in the datamover
update command; check the number of open NDMP
sessions with the file server.
ANR1774E
The Query Status command failed, and

server initialization has not completed.
Allow server initialization to complete,
and then try the command again.
ANR1777I
Explanation: The command Query Status failed

because server initialization has not completed.
User response: Allow server initialization to complete,
and then try the command again.
module(offset): Object object id hi.object id lo

is object name for node node name (node
id), filespace filespace name (filespace id ).
Explanation: The server reported a problem with the

specified object. See accompanying messages for further
information.
ANR1775I

defined, however a connection to the
data mover failed. Please check the
attributes of the file server specified in
the definition of the data mover.
Explanation: The data mover has been defined in the

server database, however the server cannot connect to
the file server associated with the data mover. The
connection failed because of one of the following
possible reasons:
definition was incorrect: TCP/IP address of the file
sessions
System action: The data mover is defined to the
server.
User response: Check that the file server associated
with the data mover is accessible through the network;
check each of the attributes specified during datamover
definition; check the number of open NDMP sessions
with the file server.

ANR1778E
Command: Invalid or missing parameter.

entered with an invalid parameter, or, is missing a
required parameter.
proper syntax.
ANR1779I
backupset process name process completed:

successful count backupset(s) were
generated or defined out of total count
backupset(s) requested by the
commands specifications.
Explanation: A GENERATE or DEFINE BACKUPSET

command has finished successfully, and the backupsets
described in previous messages have been created.
System action: The backupsets described have been
created.
185
ANR1782W ANR1789W
ANR1782W
ESTIMATE DBREORG process process

number started - server performance may
be degraded while this process is
running.
Explanation: The ESTIMAGE DBREORG process has

been started as the reported process number. This
process estimates the amount of space that the database
will reduced by if a database reorganization is
performed.
System action: This process performs extensive
database I/O and may impact other server operations
and processes while it is running.
User response: This process may be monitored using
the QUERY PROCESS command. If this process needs
to be cancelled, issue the CANCEL PROCESS
command.
ANR1785I
ESTIMATE DBREORG process is

already running.
Explanation: The ESTIMAGE DBREORG process is

already running. The server does not allow more than
one instance of this process to be running at a time.
to monitor the existing process. If the existing process
needs to be cancelled, issue the CANCEL PROCESS
command.
ANR1786W
HBAAPI not able to get adapter name.
Explanation: The HBAAPI function getAdapterName

failed. The server will continue to access next adapter if
it exists.
ANR1783E
ESTIMATE DBREORG process process

number failed and only evaluated pages
evaluated database pages.
Explanation: The ESTIMATE DBREORG process failed

to complete successfully. It only evaluated pages
evaluated database pages.
User response: The Tivoli Storage Manager SAN

discovery will not work with this Host Bus Adapter.
For the list of supported HBAs and required driver
levels by operating system go to http://
WWW.IBM.COM/SUPPORT.
ANR1787W
User response: If the has been cancelled, this message

will be issued. If this processed failed to process but
was not cancelled, it is likely that it failed because it
was not able to acquire access to the necessary database
pages to perform the evaluation. Retry the operation.
Explanation: The HBAAPI function to open the host

bus adapter (HBA) failed.
ANR1784I
A database reorganization would reduce

the database utilization by an estimated
space recovered MB.
Explanation: The ESTIMATE DBREORGSTATS process

completed and determined that the database space
utilized would be reduced by space recovered megabytes
if a database reorganization were performed.
System action: Server operations continue normally,
and the ESTIMATE DBREORGSTATS process
completes.
User response: This message reports the estimated
database space recovered if a database reorganization
were to be performed. The Tivoli Storage Manager
administrator should evaluate this information relative
to their current database utilization, expected database
growth and changes, and determine whether or not a
database reorganization is needed for this server. To
reorganize the server database, refer to DSMSERV
UNLOADDB, DSMSERV LOADFORMAT, and
DSMSERV LOADDB in the Administrators Reference.
Not able to open adapter adapter name.

User response: The Tivoli Storage Manager SAN
discovery will not work with this Host Bus Adapter.
ANR1788W
Not able to get the adapter attributes for

adapter name.
Explanation: The HBAAPI function to get the

adapters attributes failed. For UNIX systems, this
error may be caused by the user not logging in as root.
User response: Log in as root and retry. If this does
not solve the problem, SAN discovery will not work for
this adapter. For the list of supported HBAs and
required driver levels by operating system go to
http://WWW.IBM.COM/SUPPORT.
ANR1789W
Get HBA target mapping failed.
Explanation: The HBAAPI function to get the target

mapping failed.
User response: SAN discovery will not work for this
adapter. For the list of supported HBAs and required
186
ANR1790W ANR1795I
driver levels by operating system go to
http://WWW.IBM.COM/SUPPORT.
ANR1790W
SAN discovery failed.
Explanation: SAN discovery failed.

User response: SAN discovery failed. This may be a
problem with the HBA firmware, HBA or the HBA
verdors HBAAPI driver. For the list of supported
HBAs and required driver levels by operating system
go to http://WWW.IBM.COM/SUPPORT.
ANR1791W
HBAAPI wrapper library file name failed

to load or is missing.
qla2x00
/usr/lib/libqlsdm.so
com.emulex.emulexapilibrary
/usr/lib/libemulexhbaapi.so
v For windows systems, this HBAAPI vendor library is
normally located in /winnt/system32 . For example,
this can be verified by:
HKEY_LOCAL_MACHINE
SOFTWARE
SNIA
HBA
QLA2X00
LibraryFile shows the location of c:\winnt\SYSTEM32\
qlsdm.dll
ANR1793W
TSM SAN discovery is not supported on

this platform or this version of OS.
Explanation: This library is provided by Tivoli Storage

Manager. It is required for discovery of devices on a
SAN.
Explanation: SAN discovery for this platform is

currently not supported.
v For windows, the HBAAPI wrapper library is

hbaapi.dll.
v For AIX, the HBAAPI wrapper library is

libHBAAPI.a.
v
For Solaris, the HBAAPI wrapper library is

libhbaapi32.so for 32 bit application and
libhbaapi64.so for 64 bit application.
For Linux, the HBAAPI wrapper library is
libhbaapi32.so for 32 bit application and
libhbaapi64.so for 64 bit application.

User response: Make sure the HBAAPI wrapper
library for this platform is in the same directory as the
IBM Tivoli Storage Manager server executable. AIX is
the only exception with HBAAPI wrapper library
libHBAAPI.a in /usr/lib.
ANR1792W
HBAAPI vendor library failed to load or

is missing.
Explanation: The HBAAPI vendor library failed to

load or is missing. This HBAAPI library is provided by
the Host Bus Adapter (HBA) vendor. It is required for
Tivoli Storage Manager server to discover devices on
the SAN.
User response: Please make sure the HBAAPI file
exists on the system. If the driver level on your system
is not supported, please go to the HBA vendors
website and download/install the HBA driver. For the
list of supported HBAs and required driver levels by
operating system go to http://WWW.IBM.COM/
SUPPORT. Following is an example of some of the
HBA vendors HBAAPI file:
v
For UNIX systems, This HBAAPI vendor librarys

location is indicated in /etc/hba.conf. For example:
User response: SAN discovery will not work for this

platform.
v For AIX, we only support AIX5.2F and above
v For HP, we do not support this platform yet.
v For Linux, we do not support Linux-zOS yet.
v For Windows, we do not support Windows 2003 64
bit yet.
ANR1794W
TSM SAN discovery is disabled by

options.
Explanation: SAN discovery is disabled by option

SANDISCOVERY OFF.
User response: SAN discovery is currently disabled by
default or with the server option SANDISCOVERY OFF
depending on the platform. For the list of supported
ANR1795I
The device driver has been updated

successfully for device old device name.
The new device name is new device name.

the CHANGE DEVDRIVER command. The device
driver for device old device name has been updated
successfully.
187
ANR1796E ANR1804W
ANR1796E
Invalid device name device name.
Explanation: The device name is not in the form of

TAPEx or CHANGERx.
User response: Change the device name to TAPEx or
CHANGERx and retry the command.
ANR1797E
Device device name is not supported by

the IBM Tivoli Storage Manager device
driver.
Explanation: Device device name is not supported by

the IBM Tivoli Storage Manager device driver. The
hardware ID was not found in the IBM Tivoli Storage
Manager device driver INF file, i.e. tsmlb.inf and
tsmmt.inf.
User response: Access the Tivoli Storage Manager
Web site at www.ibm.com/software/sysmgmt/
products/support/IBMTivoliStorageManager.html and
navigate to the device support information for the
servers operating system. Verify if the device is
supported. If the device is supported by the IBM Tivoli
Storage Manager device driver, contact your service
representative.
ANR1798E
Device driver update failed for device

device name.
Explanation: The CHANGE DEVDRIVER operation

failed for device device name.
fails.
ANR1799E
The Tivoli Storage Manager device

driver is not installed, or one or more
device driver files are missing.
Explanation: The server command has failed because

the Tivoli Storage Manager device driver is not
installed, or one or more device driver files are missing.
User response: Make sure the Tivoli Storage Manager
device driver is installed and the following files are not
missing. %WINDIR%\system32\drivers\tsmscsi.sys (or
tsmscsi64.sys for 64-bit Windows), %WINDIR%\inf\
tsmmt.inf, and %WINDIR%\inf\tsmlb.inf.
ANR1800E
Missing or invalid EVENTLOG

command parameter.
Explanation: The event logging command issued

contains an invalid parameter, or is missing a required
parameter.
188

User response: Reissue the command with the proper
parameters.
ANR1801E
Eventlog command: Invalid event or event

class - Event or event class name.
Explanation: An event logging command has been

entered which specifies an unknown event or event
class.
System action: The command is ignored for the
invalid event or event class. Any valid events or classes
specified are processed.
event or event class.
ANR1802E
Device device name was not found.
Explanation: The device was not found in the device

information set. The vendor ID and/or product ID, or
device name may be invalid, or the device has been
removed from the system.
fails.
vendor ID and product ID, or device name.
ANR1803W
TSM SAN discovery requires root

authority.
Explanation: SAN discovery is disabled by option

SANDISCOVERY OFF.
User response: SAN discovery is currently disabled by
default or with the server option SANDISCOVERY OFF
depending on the platform. For the list of supported
ANR1804W
Command: Process process number

skipping volume volume name in storage
pool pool name because the volume is in
use by another process.
Explanation: The command shown specifies the

volume to be processed, but that volume is currently
being used by another operation.
System action: The server skips the volume and
processes the next available volume.
User response: Check the activity log to determine
which operation was using the volume. If the operation
using the volume is complete reissue the Command to
process the skipped volume.
ANR1808E ANR1828E
ANR1808E
Unable to open event log file file spec for

appending.
Explanation: The server cannot write to a file which

has been specified for event logging.
System action: No logging will be done to the file
receiver.
permissions, or specify a different file for logging.
ANR1809E
Insufficient memory to activate event

logging.

ANR1823I
Event logging ended for all receivers.
Explanation: In response to an END

EVENTLOGGING command, event log records are no
longer being output to any receiver.
ANR1824E
Event logging is inactive for the

specified receiver.
Explanation: A BEGIN EVENTLOGGING command

has been entered, but the server has insufficient
memory available to activate logging.
Explanation: An END EVENTLOGGING command

has been entered, but logging is not active for the
specified receiver.
User response: If logging is required, make more

memory available to the server then restart the server.
User response: If logging is desired, use the ENABLE

EVENT and BEGIN EVENTLOGGING commands to
activate event logging.
ANR1810E
Eventlog command: Invalid receiver receiverName.

entered which specifies an unknown event log receiver
(maybe unknown just to this platform).
invalid receiver. Any valid receivers specified are
processed.
receiver.
ANR1821W
Event logging not started for the

receiverName receiver.
Explanation: In response to a BEGIN

EVENTLOGGING command, recording of event log
records to the specified receiver was attempted. The
event logging for the specified receiver was not started
because either the receiver is currently running or the
receiver was terminated previously and is still in the
process of writing the messages that were queued up
for processing.
User response: Check to see if the event log receiver is
already started. If it is not currently running then try to
start it again after a short delay.
ANR1822I
Event logging ended for the receiverName

receiver.
Explanation: In response to an END

EVENTLOGGING command or because an error
occurred, event log records are no longer being output
to the specified receiver.
ANR1825I
Event logging active for the receiverName

receiver.

EVENTLOGGING command, event log records are now
being output to the specified receiver.
ANR1826I
Event logging active for all receivers.

EVENTLOGGING command, event log records are now
being output to all receivers.
ANR1827E
Eventlog command: No valid receiver

specified.

entered, and no valid receivers were specified.
receiver.
ANR1828E
Eventlog command: No valid event

specified.

entered and no valid events or event classes were
specified.
189
ANR1829E ANR1852E
events or event classes.
ANR1844I
Eventlog command command processed.
Explanation: The specified command was processed.

ANR1829E
Eventlog command: Server events may not

be disabled for the activity log receiver.
Explanation: A DISABLE EVENT command has been

entered for the activity log receiver.
activity log receiver. Any valid receivers specified are
processed.

User response: If any previous messages indicate that
parts of the command failed, reissue the command for
those parts only.
ANR1850E

receiver.
ANR1830E
receiverName receiver options not defined

in the server options file.
Explanation: A BEGIN EVENTLOGGING command

has been entered for a receiver, but the required
receiver options were not specified in the server
options file.
System action: Logging is not started for the specified
receiver.
User response: Enter the receiver options in the server
options file and restart the server.
ANR1831I
Event logging of client events ended for

ACTLOG receiver.
Explanation: An END EVENTLOGGING command

has been entered for the activity log receiver.
System action: The server no longer records client
events in the activity log. Server events continue to be
recorded in the activity log.
ANR1842E
An error occurred on the receiverName

receiver.
Explanation: The server is attempting to log an event

which has previously been handled by the event server
that is currently defined.
System action: The event is not sent to the event
server. Other events will still be sent, and this message
will be issued periodically if this situation is detected
again.
User response: Determine what is wrong with the
server to server event logging setup, and fix the
problem.
ANR1851E
User response: Issue a BEGIN EVENTLOGGING

command for the receiver to attempt to start logging
events to the receiver again.
ANR1843I
Event log receiver initialization in

progress.
The source trail for server to server

event logging has exceeded the
maximum length of Maximum sourcetrail
length bytes.
Explanation: While attempting to log an event to the

event server, the server has found that the source trail
length is too long.
System action: The server continues to try to send the
event to the event server, but the source trail may be
truncated and appear something like:
Explanation: An error occurred on the specified

receiver.
System action: The server no longer sends events to
the receiver.
Circular event logging detected. The

event server has previously handled
event Event number from Source trail. To
prevent looping, events which have
already been logged by the event server
are not sent again. Please correct the
situation causing circular logging to
avoid wasting system resources.
name1
...
name1>...>namex>namey
where,
is the originator of the event.
is where intervening server name(s)
have been left off the source trail.
User response: Most likely you are using very long

server names and/or have excessive hops from server
to server. Either use shorter server names or change
your configuration to reduce the number of hops.
Explanation: Initialization is starting for the eventlog

receivers.
ANR1852E
Explanation: A network error has occurred in

attempting to send the event header to the Tivoli
Enterprise Console.
190
Unable to send header to TEC at TEC

server rc return code
ANR1853E ANR1860E
User response: Verify network connections and
contact your service representative if this error persists.
ANR1853E
Unable to send data to TEC at TEC


attempting to send the event data to the Tivoli
Enterprise Console.
ANR1854E
Unable to flush data to TEC at TEC


attempting to flush data to the Tivoli Enterprise
Console .
ANR1855E
Failure validating protocol between

client and server for node node on
session session number
Explanation: For a node having the VALIDATE

PROOTOCOL option set to either DATAONLY or
ALL, a validation error occurred. The transaction is
aborted and an indication is sent to the client indicating
the failure.
ANR1856W
Command: No volumes selected to

process.
Explanation: No volumes were eligible for processing

by the AUDIT VOLUME command based upon the
parameters specified.
System action: The AUDIT VOLUME process ends
without processing any volumes.
User response: Review the parameters specified for
the command. If there was an error specifying a
parameter, re-issue the command with the parameter
corrected.
ANR1857I
AUDIT VOLUME will start count repair

processes.
Explanation: The AUDIT VOLUME command will

process a range of volumes due to one or more of the
following parameters having been specified:
FROMDATE, TODATE, or STGPOOL. The AUDIT

VOLUME processing will start a process for each
volume that qualifies and process an AUDIT VOLUME
for each volume with FIX=YES specified.
System action: One or more volumes are audited and
inconsistent data is discarded.
continue.
User response: Enter 'Y' to audit the volume or 'N' to
stop the process.
ANR1858I
AUDIT VOLUME will start count

inspect processes.
Explanation: The AUDIT VOLUME command will

process a range of volumes due to one or more of the
following parameters having been specified:
FROMDATE, TODATE, or STGPOOL. The AUDIT
VOLUME processing will start a process for each
volume that qualifies and process an AUDIT VOLUME
for each volume with FIX=NO specified.
continue.
stop the process.
ANR1859W
Node node on session session id received

CRC protocol validation information
when it is not configured to do so.
Explanation: The server received protocol validation

information for the session and node specified. The
settings for this node are not configured to perform
protocol validation and any CRC information received
will be ignored.
User response: The server administrator should
evaluate whether or not this node should perform
protocol validation. If so, issue the UPDATE NODE
command and specify the VALIDATEPROTOCOL
option with the appropriate setting to enable protocol
validation.
If this is a TYPE=SERVER node for the target of a
virtual volume operation and protocol validation is not
desired, the server definition on the source server
should be updated with VALIDATEPROTOCOL=NO
set. Otherwise, if protocol validate is desired, the
SERVER type node on the target server should be
updated using the UPDATE NODE command with
VALIDATEPROTOCOL=ALL.
ANR1860E
Drive with serial serial element element

port port and target target lun lun does
not match with the library libraryPath .
Explanation:
191
ANR1861E ANR1869W
System action:
ANR1867I
User response:
ANR1861E
Drive with element element port port and

target target lun lun does not match with
the library libraryPath .
Explanation:
System action:
User response:
ANR1863E
library libraryPath and serial serial does

not support Read Element Status
command. It is very old and should be
replaced with newer model.

has completed with status status. If the status is
INCOMPLETE, some files have been skipped due to
errors reading or writing the file.
command completes. Statistics on the number and type
of objects moved, together with the total number of
bytes copied, are displayed on the server console
following this message. A summary of the number of
files that were skipped is also displayed.
ANR1868I
Explanation:
System action:
User response:
ANR1864E
library libraryPath does not support Read

Element Status command and it does
not have a serial number. It is very old
and should be replaced with newer
model.
Explanation:
System action:
User response:
ANR1865I
export command : Summary for

Restartable Export operation export
identifier :
Explanation: A summary of the total number of

objects transmitted in the restartable export operation
with export identifier is displayed following this
message.
System action: Export processing for the command
ends. Server operation continues.
ANR1866I

suspended with status status.

command command was suspended with a SUSPEND
command.
stops. Statistics on the number and type of objects
message.
192

completed with status status.
Export/import command: Copied filespace

number file spaces archive number archive
files, backup number backup files, and
spacemg number space managed files.

copies filespace number client file space definitions,
archive number archive file copies, backup number backup
file copies, and spacemg number space-managed files
from either the server database to export media or from
import media into the server database. Data is not
actually moved if Preview=Yes is specified in the
command export/import command.
ANR1869W
Export/import command: Skipped archive

number archive files, backup number
backup files, and spacemg number space
managed files.

skipped archive number archive file copies, backup
number backup file copies, and spacemg number
space-managed files from either the server database to
export media or from import media into the server
database. Data is not actually moved if Preview=Yes is
User response: Check previous messages for the
names of the files that were not exported or imported,
and problem determination information.
ANR1870I ANR1901E
ANR1870I

bytes of data.

copies number bytes of data from the server database
and data storage to the export media or from the
export media to the server database and data storage.
Data is not moved if Preview=Yes is specified in the
command export/import command. This figure can be
used during export preview processing to estimate the
number of removable media volumes needed to hold
the exported information from the server.
ANR1871I

kilobytes of data.

copies number kilobytes of data from the server
the server.
ANR1872I

megabytes of data.

copies number megabytes of data from the server
the server.

the server.
ANR1874I

terabytes of data.

copies number terabytes of data from the server
the server.
ANR1875I
Export/import command: Detected number

errors.

detects number errors while copying information from
the server database and data storage to the export
media or from the export media to the server database
and data storage.
prior to this message to view the error. Use the QUERY
for messages.
ANR1900E
Command: Export node name node name is

not defined.
Explanation: The command shown specifies an NFS

export that is not registered with the server.


command.
ANR1873I

gigabytes of data.

copies number gigabytes of data from the server
ANR1901E
Command: Export export name access name

is already defined.
Explanation: A Export NFS command has been

entered that specifies an export that already exists.
command.
193
ANR1902I ANR1999I
ANR1902I
Export node name node name was

removed.
Explanation: None.
ANR1903E
Export export name not defined.
Explanation: An NFS client attempted to mount the

specified name as a mount point. The specified name is
not currently being exported by the server.
System action: The server does not provide an export
of the specified directory.
User response: Ensure that an NFS ADDEXPORT
command was issued for the specified node.
ANR1994I
Activity log pruning started: removing

delete megabytes M based on current size
current size megabytes M and retention
setting retention size megabytes M.
Explanation: Server activity log exceeds the retention

size by the delete megabytes specified. The activity log
pruning will delete as many records as necessary to
reduce the current activity log size by the delete
megabytes size.
ANR1996E
Command: Invalid volume name prefix volume name. Room for additional
characters is required.
Explanation: The command is being used for multiple

volume names. The suffix for the names is being
generated in the indicated command. When the suffix
is taken into account, the specified name is too long by
the indicated number of characters. Three characters
must be allowed for the suffix.
command.
User response: Reissue the command with a prefix
short enough to allow for the suffix. Three extra
characters are needed for the suffix.
ANR1997E
Command: The Formatsize parameter

must be specified when more than 1
volume is created.
Explanation: The command specified the createion of

more than one volume with the Numberofvolumes
parameter. When multiple volumes are created, the
Formatsize parameter must also be specified to provide
the size of the volumes. Each volume will be created
with the same size.
command.
User response: Reissue the command with the
Formatsize parameter or define a single volume
without the Formatsize parameter.

ANR1998E
ANR1995E
Command: Invalid Formatsize value formatsize value for device class Device
Class
Explanation: A value was specified for the Formatsize

parameter which is larger than the maximum capacity
value for the device class indicated in the message. The
device class is associated with the storage pool
specified in the DEFINE VOLUME command and is a
FILE device type. The maximum capacity value of the
device class is the limit of data that the server will
write to the volume.
command.
User response: Reissue the command with a
Formatsize value which is less than the maximum
capacity value of the storage pool. The maximum
capacity can be displayed with the QUERY DEVCLASS
classname F=D command.
194
Command: Invalid value for parameter

parameter - parameter value.

the (parameter) parameter in command command is not a
valid value for this parameter.
valid parameter value. For information on valid values
for the parameter for the command, refer to the
ANR1999I
Command completed successfully.
Explanation: Processing for the specified command

ANR2000E ANR2009E
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.
ANR2006E

User response: Reissue the correct command.
ANR2001E
Insufficient server memory to initiate

command.
Explanation: A command has been entered, but the

server cannot obtain enough internal memory to
process the command.
Activity log process was not started, the

default output stream cannot be opened.
Explanation: The process that monitors the default

(console) output stream and maintains the activity log
cannot access that output stream.
System action: The server does not update the activity
log.
ANR2007E


cannot start due to a server internal error.
ANR2002E

log.
Missing closing quote character.
Explanation: A server command that contains a

quoted parameter has been entered, but a matching
closing quote is missing.
User response: Reissue the command with properly
matched quotes.

representative.
ANR2008E
ANR2003E
Illegal use of keyword parameter

character (=) - parameter.
Explanation: A server command contains the

parameter shown followed by an equal sign (=), but the
parameter is not a keyword parameter.
proper syntax.
ANR2004E
Missing value for keyword parameter parameter.
Explanation: A server command containing a keyword

parameter has been entered, but the value for the
parameter is missing.
Activity log process was not started, due

to an internal error.
Activity log process has stopped database transaction could not be

started.

cannot continue due to a server transaction failure. This
may be a memory shortage error.
System action: The server stops updating the activity
log.
ANR2009E
Activity log process has stopped database error.
User response: Reissue the command and supply a

value for the keyword parameter.

cannot continue due to a server database error.
ANR2005E

log.
Keyword parameter character (=) may

not be surrounded by blanks.
Explanation: A server command contains a keyword

parameter followed by an equal sign (=), but the equal
sign is preceded or followed by a blank, or both.
195
ANR2010W ANR2017I
ANR2010W
Server is out of LOG space in adding

entries to the Activity Log. Console
messages will not be logged until LOG
space is available.
User response: The server may be low on available

memory. Allocate additional storage to the server. For

cannot update the activity log due to a lack of recovery
log space.
ANR2014E

log.
Explanation: The process that removes expired records

from the server activity log cannot begin execution due
to a server internal error.

volumes are used.
ANR2011W
Server is out of DB space in adding

entries to the Activity Log. Console
messages will not be logged until DB
space is available.

cannot update the activity log due to a lack of database
space.
log.
ANR2012W
Activity log process has encountered

unexpected table data output in the
default output stream.

has detected invalid data in the console stream.
Activity log pruning process could not

be started, due to an internal error.
System action: The server does not prune the activity

log.
representative.
ANR2015E
Activity log failure - database

transaction could not be started.

from the server activity log has failed due to a database
transaction failure, which may be a memory shortage
error.
System action: The server ends activity log pruning.
ANR2016E
Activity log failure - database error.

from the server activity log has failed due to a server
database error.
System action: The server ends activity log pruning.

log.
ANR2017I
ANR2013E
Explanation: This message records the fact that the

named administrator issued the command specified.
The messages is issued and logged to provide an audit
trail for administrative commands.
The activity log process has encountered

unexpected output data in the console
output stream. The process will be
restarted.
Explanation: The process that monitors console output

and maintains the activity log has detected invalid data
(unknown data type) in the console stream.
System action: The server restarts the activity log
recording process. While the process is restarting, the
server may not be able to record some console
messages in the activity log.
196
Administrator Administrator Name issued

command: Command
System action: Server operation continues

ANR2018E ANR2027E
ANR2018E
Administrator Command: Unicode

conversion failed for argument Command
Argument
Explanation: The specified command argument could

not be converted to a Unicode string. Conversion can
fail if the string includes characters that are not
available in the server code page, or if the server has a
problem accessing system conversion routines.
System action: Server command fails.
User response: Make sure that the servers locale is
properly configured.

proper syntax.
ANR2024E
Explanation: The specified server command contains

more positional parameters than is allowed.
proper syntax.
ANR2025E
ANR2019I
Command: No nodes updated.
Explanation: An UPDATE NODE command has been

entered, but no objects were updated.
ANR2020E
Command: Invalid parameter - parameter.

entered with an invalid parameter.
proper syntax.
ANR2021E
Command: Missing subcommand

keyword.

entered without a valid subcommand (second
parameter).
proper syntax.
ANR2022E
Command: One or more parameters are

missing.

entered without all required parameters.
proper syntax.
ANR2023E
Command: Extraneous parameter parameter.
Command: Too many parameters

specified.
Command: Command failed - server

thread resource not available.
Explanation: A server command, which has a

requirement to start a server thread, has been entered
but cannot be executed because no server thread is
available.
User response: Reissue the command. If the command
fails with the same error, wait for server activity to
decrease and try again.
ANR2026E
Command: Command failed - sufficient

server memory is not available.

cannot be processed because sufficient memory is not
command.
ANR2027E

server recovery log space is not
available.

cannot be processed because sufficient recovery log
command.
volumes are used.
Explanation: The specified server command contains

more positional parameters than is allowed.
197
ANR2028E ANR2035E
ANR2028E

server database space is not available.

cannot be processed because sufficient database space
is not available. For certain operations, like SQL
commands, this message can be issued when the
database has space, but it is unusable for the current
request due to the DB allocation history. In this case,
the database query will show a Maximum Reduction of
0.
command.
new volumes are used. If the database has space, but
the Maximum Reduction is 0, then a database
reorganization can also be used to solve the problem.
See the IBM Tivoli Storage Manager Guide, Managing
the Database and Recovery Log for information on how
to reorganize the database.
ANR2029E
Command: Transaction failed; command

not executed.
Explanation: A command that is part of the current

transaction has failed; therefore, any additional
commands fail.
command.
User response: Stop the administrative session, restart
it, and try the command again. If this problem persists,
ANR2030E
Commit not accepted; transaction failed.
Explanation: A command that is part of the current

transaction has failed; therefore, a COMMIT command
cannot be processed.
COMMIT command.
User response: Stop the administrative session, restart
it, and try the command again. If this problem persists,
ANR2031E
Command: At least one attribute must be

specified for update.
Explanation: The specified UPDATE command has

been entered, but no attributes have been specified for
updating.
User response: Reissue the UPDATE command with
one or more attributes to be updated.
198
ANR2032E
Command: Command failed - internal

Explanation: An internal error has occurred during an

attempt to process a server command. This message
command.
representative.
ANR2033E
Command: Command failed - lock

conflict.
Explanation: A server command that requires the

server to lock a system resource has been entered. The
command cannot be executed because the resource is
already in use by another command or process.
command.
User response: Try the command again at a later time.
ANR2034E
Command: No match found using this

criteria.
Explanation: The specified command has been

entered, but no objects that match the criteria can be
found.
User response: Verify that all the specified parameter
values are correct. If a mistake is found, correct it and
reissue the command.
ANR2035E

name is not authorized to issue this
command.

have the proper authority necessary to run the
command. Note: This message can be issued as a result
of the server option REQSYSAUTHOUTFILE YES being
in effect.
command.
User response: Examine previous messages for any
additional information. Issue the command from a
properly authorized administrator ID, or contact the
system administrator to have additional authority
granted to the current administrator ID.
ANR2036E ANR2042E
ANR2036E
Command: Process could not be started sufficient memory is not available.
Explanation: A background process cannot be started

for the indicated command because sufficient memory
is not available to the server.

representative.
ANR2040W
System action: A new process is not started to execute

this command.
ANR2037E
Command: Process could not be started lock conflict.

for the indicated command because a required system
resource is already locked by another command or
process.
this command. If other processes have been started for
this command, these processes may execute
successfully.
User response: If necessary, try the command again at
a later time.
ANR2038E

successfully.
User response: If necessary, reissue the command. If
the command fails with the same error, wait for server
activity to decrease and try again.
ANR2039E
Explanation: Issuing the RESTORE STGPOOL

command will result in deletion of existing files in the
indicated primary storage pool after these files have
been restored from a copy storage pool. If a volume
with access mode destroyed becomes empty because all
files on the volume have been restored to another
location, the destroyed volume will be deleted from the
database.
continue.
User response: Enter 'Y' to restore the storage pool,
'N' otherwise.
ANR2041W
Command: Process could not be started server thread resource not available.

for the indicated command because no server thread is
available.
Command: Process could not be started internal server error detected.

for the indicated command because an internal error
has occurred.
successfully.
This command attempts to restore all

files in storage pool storage pool which
have previously been found to be
damaged or which reside on a volume
with access mode destroyed; existing
references to files in storage pool storage
pool will be deleted from the database
after the files have been restored.
This command attempts to restore all

files in storage pool storage pool which
reside on one of the volumes specified
in the command; existing references to
files on these volumes will be deleted
from the database after the files have
been restored.
Explanation: Issuing the RESTORE VOLUME

command causes the access mode of the specified
volumes to be updated to destroyed. Existing files will
be deleted from the specified volumes after these files
have been restored from a copy storage pool. If a
volume with access mode destroyed becomes empty
because all files on the volume have been restored to
another location, the destroyed volume will be deleted
from the database.
continue.
User response: Enter 'Y' to restore the volumes, 'N'
otherwise.
ANR2042E
Command: Copied parameter not valid

for pool type storage pool volume.
Explanation: The QUERY CONTENT server command

has been entered with an invalid parameter. COPIED is
not a valid parameter when the volume specified
belongs to a copy or active-data type storage pool.
User response: Reissue the command without the
COPIED parameter.
199
ANR2043E ANR2053I
ANR2043E
Command: WAIT parameter not allowed

from server console.
Explanation: The WAIT parameter is not allowed for

commands issued from the server console.

ANR2049E

User response: Either reissue the command without
the WAIT parameter or else reissue the command from
an administrator using an Administrative Client.
ANR2044E
Command: Invalid options value Options value.
Command: Optionset optionset name is not

defined.
Explanation: The command shown specifies an

optionset that is not defined in the server.
command.
Explanation: The set option command has been

entered with an invalid value.
ANR2050I

command.
Explanation: The requested option has been added to

the specified optionset in response to a DEFINE
OPTIONSET command.

value.
Command: Option option name defined in

optionset option set name.

ANR2045E
Command: An error (error code) occurred

during a write operation.
ANR2051E
Explanation: The server detects an error while

attempting a write operation.
User response: Refer to the other displayed messages
to determine why the write operation has failed.
ANR2046I
optionset name: Optionset optionset name

defined.
Explanation: The requested option set has been added

to the system in response to a DEFINE OPTIONSET
command.
Explanation: The requested option already exists in

the optionset specified by the DEFINE CLIENTOPT
command.
command.
ANR2052E

ANR2047E
Command: Optionset optionset name is

already defined.
Explanation: A DEFINE OPTIONSET command has

been entered that specifies an optionset name already
command.
User response: To define the optionset, reissue the
command and specify a different optionset name.
ANR2048I
Command: Optionset optionset name

deleted.
Explanation: The requested option set has been

deleted from the system in response to a DELETE
OPTIONSET command.
200
Command: Option option name, sequence

number sequence number is already
defined in optionset option set name.

number sequence number is not defined
in optionset option set name.
Explanation: The requested option is not defined in

the optionset specified by the DELETE CLIENTOPT
command.
command.
ANR2053I

number sequence number, has been
deleted from optionset option set name.
Explanation: The requested option has been deleted

from the specified optionset in response to a DELETE
CLIENTOPT command.
ANR2054I ANR2063I
ANR2054I
Command: Optionset optionset name

updated.
Explanation: The requested option set has been

updated in the system in response to an UPDATE
OPTIONSET command.
ANR2055I
Command: Optionset source optionset name

copied to optionset target optionset name.

the COPY OPTIONSET command. The optionset
named source optionset name has been copied to the
optionset named target optionset name.
User response: None. The requested option set has
been added to the system in response to a COPY
OPTIONSET command.
ANR2059W
Command: Error occurs when writing to

Filespec - user needs to update the file
manually.
Explanation: An error occurs when trying to write the

new value to the server options file.
System action: The command is processed but the
option is not updated in the options file.
User response: Use a text editor to update the server
options file if the user wants to use this value when the
server restarts later. If the user does not update the file,
the current value in the options file will be used when
the server restarts.
ANR2060I
Node node name registered in policy

domain domain name.
Explanation: The requested backup-archive node has

been added to the system in response to a REGISTER
NODE command and has been assigned to the policy
domain indicated.
ANR2056E
Command: Invalid option name - option

name. Retry using the full optionname.

option name.
command.
option name.
ANR2057E
Command: Invalid option value - option

value.

option value.

ANR2061I
Node node name removed from policy

domain domain name.
Explanation: In response to a REMOVE NODE

command, the requested backup-archive node has been
ANR2062I
Node node name renamed to new node

name.

command.
Explanation: In response to a RENAME NODE

renamed to the new name shown.

option value.

ANR2058W
Command: Options file Filespec not found

- user needs to update the file manually.
Explanation: The server options file cannot be opened

or found.
System action: The command is processed but the
option is not updated in the options file.
User response: Use a text editor to update the server
options file if the user wants to use this value when the
server restarts later. If the user does not update the file,
the current value in the options file will be used when
the server restarts.
ANR2063I
Node node name updated.
Explanation: One or more attributes of a

backup-archive node have been updated by an
201
ANR2064I ANR2076I
ANR2064I
Node node name locked.
Explanation: In response to a LOCK NODE command,

the indicated backup-archive node has been locked.
ANR2065I
Node node name is already locked.
Explanation: The indicated backup-archive node

referenced in the LOCK NODE command is already
locked.
ANR2066I
Node node name unlocked.
Explanation: In response to an UNLOCK NODE

command, the indicated backup-archive node is
unlocked.
ANR2067I
Node node name is already unlocked.
Explanation: The indicated backup-archive node

referenced in the UNLOCK NODE command is not
locked.
ANR2068I
Administrator administrator ID registered.
Explanation: In response to a REGISTER ADMIN

command, the requested administrator ID has been
added to the system.
ANR2069I
Administrator administrator ID removed.
Explanation: In response to a REMOVE ADMIN

ANR2070I
Administrator administrator ID renamed

to new administrator ID.
Explanation: In response to a RENAME ADMIN

changed to the new name shown.
202

ANR2071I
Administrator administrator ID updated.
Explanation: One or more attributes of an

administrative user have been updated by an UPDATE
ADMIN command.
ANR2072I
Administrator administrator ID locked.
Explanation: In response to a LOCK ADMIN

command, the indicated administrator ID has been
locked.
ANR2073I
Administrator administrator ID is already

locked.
Explanation: The indicated administrator ID

referenced in the LOCK ADMIN command is already
locked.
ANR2074I
Administrator administrator ID unlocked.
Explanation: In response to an UNLOCK ADMIN

command, the indicated administrator ID is unlocked.
ANR2075I
Administrator administrator ID is already

unlocked.
Explanation: The indicated administrator ID

referenced in the UNLOCK ADMIN command is not
locked.
ANR2076I
System privilege granted to

administrator administrator ID.
Explanation: In response to a GRANT AUTHORITY

command, system privilege class has been granted to
the indicated administrator.
ANR2077I ANR2087I
ANR2077I
Unrestricted policy privilege granted to


command, unrestricted policy privilege has been
granted to the indicated administrator.
ANR2078I
Restricted policy privilege granted to

administrator administrator ID - policy
domain domain name.

command, restricted policy privilege for the specified
policy domain has been granted to the indicated
administrator.

ANR2083I
System privilege revoked for

Explanation: In response to a REVOKE AUTHORITY

command, system privilege class has been revoked
from the indicated administrator.
ANR2084I
Policy privilege revoked for


command, policy privilege class for all policy domains
has been revoked from the indicated administrator.

ANR2079I
Unrestricted storage privilege granted to


command, unrestricted storage privilege has been
granted to the indicated administrator.
ANR2080I
Restricted storage privilege granted to

administrator administrator ID - storage
pool storage pool name.

command, restricted storage privilege for the specified
storage pool has been granted to the indicated
administrator.
ANR2085I
Restricted policy privilege revoked for

administrator administrator ID - policy
domain domain name.

command, restricted policy privilege for the specified
policy domain has been revoked from the indicated
administrator.
ANR2086I
Storage privilege revoked for


command, storage privilege class for all storage pools
has been revoked from the indicated administrator.

ANR2081I
Analyst privilege granted to


command, analyst privilege class has been granted to
ANR2082I
Operator privilege granted to

ANR2087I
Restricted storage privilege revoked for

administrator administrator ID - storage

command, restricted storage privilege for the storage
pool indicated has been revoked from the indicated
administrator.

command, operator privilege class has been granted to
203
ANR2088I ANR2099I
ANR2088I
Analyst privilege revoked for


command, analyst privilege class has been revoked
ANR2089I
Operator privilege revoked for


command, operator privilege class has been revoked
ANR2090I
Activity log retention set to value for

management by management style.
Explanation: The server activity log has been set to

the value indicated with the SET ACTLOGRETENTION
command for the indicated management style. If the
management style is DATE, the value is the number of
days that messages will be kept in the activity log
before being deleted. If the management style is SIZE,
the value is the size in megabytes that the activity log
will be allowed to occupy in the server database.

ANR2094I
Server name set to server name.
Explanation: The name that the server displays and

communicates to backup-archive nodes has been set to
the value indicated with the SET SERVERNAME
command.
ANR2095I
Authentication parameter set to value.
Explanation: The requirement for a node or

administrator to enter a password when establishing a
session with the server has been turned on or off as
indicated with the SET AUTHENTICATION command.
ANR2096I
Server now enabled for backup/archive

client access.
Explanation: The server has been made available for

use by backup-archive clients with the ENABLE
command.

ANR2097I
ANR2091I
Accounting parameter set to value.
Server now disabled for backup/archive

client access.
Explanation: Accounting record generation has been

turned on or off as indicated with the SET
ACCOUNTING command.
Explanation: The server has been made unavailable

for use by backup-archive clients with the DISABLE
command.
ANR2092I
ANR2098E
Password expiration period set to

number of days days.
Explanation: The number of days that a password can

be used before it must be changed has been set to the
value indicated with the SET PASSEXP command.
Command: Invalid URL specification url.
Explanation: The specified URL is too long.

User response: Reissue the command and enter a URL
value that is 200 characters or less.

ANR2099I
ANR2093I
Registration parameter set to registration

method.
Explanation: Backup-archive node registration has

been set to the method indicated with the SET
REGISTRATION command.
204
Administrative userid admininstrator

name defined for OWNER access to node
node name.
Explanation: An administrator with the specified

name was created having OWNER access to the client
node. This administrator is created for accessing the
client node from an interactive interface.
ANR2100I ANR2108I
ANR2105W

ANR2100I
Activity log process has started.
Command: Node was registered in excess

of license terms - node registration will
fail after 120% of the licensed quantity
of nodes have been registered.
Explanation: The server has detected the addition of a

node in excess of the terms under which the server is
licensed. The REGISTER NODE command will fail after
120% of the licensed number of nodes have been
registered.
Explanation: The automatic server process that

removes expired server activity log records has begun
processing.
ANR2101I
Activity log process stopped, activity log

retention set to 0.
Explanation: A SET ACTLOGRETENTION command

has set the retention period to zero days. As a result,
activity logging stops.
System action: The activity log process stops
recording console output in the server activity log.

compliance. You may remove nodes to reduce the
number of registered nodes or purchase additional
client node connections. If additional nodes have been
purchased, issue the AUDIT LICENSES command to
resynchronize the server configuration with license
terms.
Server HALT command: Quiescing
database update activity.
ANR2106I
ANR2102I
Explanation: The server is quiescing transactions that

update the database so that the database is in a
consistent state when the server is halted. This action
occurs when HALT QUIESCE is specified to halt the
server with the database in a consistent state.
Activity log pruning started: removing

entries prior to date time.
Explanation: Server activity log records older than the

date and time indicated are being removed from the
activity log.
System action: When database update transaction

activity has been stopped, the server program ends.
ANR2103I
Activity log pruning completed: number

of records records removed.
Explanation: All expired (older than the log archive

retention value) server activity log records have been
removed; the number of records deleted is shown.
ANR2107I
Server HALT command: Database update

activity is now quiesced.
Explanation: The server has stopped all database

update transaction activity. This action occurs when
HALT QUIESCE is specified to halt the server with the
database in a consistent state.
System action: The server program ends.

ANR2104I
Activity log process restarted - recovered

from an insufficient space condition in
the Log or Database.
Explanation: The process that records data in the

server activity log has failed because of insufficient
space in the server recovery log or database; space is
now available and the process is again recording data.
System action: Activity logging resumes.
ANR2108I
Server HALT command: Reattempting to

quiesce database update activity.
Explanation: The server is quiescing transactions that

update the database so that the database is in a
consistent state when the server is halted. The previous
attempt at quiescing database activity failed because of
the current transaction load on the server. The quiesce
operation is being reattempted. This action occurs when
HALT QUIESCE is specified to halt the server with the
database in a consistent state.
System action: When database update transaction
activity has been stopped, the server program ends.
205
ANR2109I ANR2116E
ANR2109I
Server HALT command: Database update

transaction activity could not be
successfully quiesced.
Explanation: After repeated attempts, server database

update transaction activity could not be quiesced. The
server is not halted with the HALT QUIESCE
command. Attempts to quiesce database update
transaction activity can fail if heavy transaction load is
on the server when a HALT QUIESCE command is
entered.
User response: You may disable the server, cancel all
client sessions accessing the server, cancel all processes,
and reenter the HALT QUIESCE command to stop
server processing. The HALT command may also be
used to stop server processing without quiescing
database transaction update activity. Server recovery
logic will be used when the server is restarted to
reconcile database transaction activity.
ANR2110I
Command started as process process ID.

to service the command command. The background

command.
User response: Reissue the command with a volume
in a primary pool.
ANR2113E
Command: Volume volume name does not

belong to the same storage pool (storage
pool name) as previously listed volumes.
Explanation: The indicated command accepts a list of

one or more volumes which belong to the same storage
pool. The named volume does not belong to the same
storage pool as the previously listed volumes.
command.
User response: Issue the command with a list of
volumes that belong to the same storage pool.
ANR2114I
Command: Access mode for volume

volume name updated to destroyed.
Explanation: A RESTORE VOLUME command has

updated the access mode of the indicated volume to
destroyed.
System action: Restore processing continues.
System action: The server processes the indicated

command.

number to specify this process.
ANR2115E
ANR2111W
Command: There is no data to process for

storage pool.
Explanation: The indicated command does not have

any data to process. This can occur if the command
specifies a storage pool with no volumes, or with no
volumes that contain data. This can also occur if there
are no volumes in the storage pool with an access state
of READWRITE or READONLY.
System action: The command ends without starting a
background process.
User response: Issue the QUERY VOLUME F=D
command to verify that there is at least one volume in
the storage pool that contains data, and that the storage
pool volumes have an access state of READWRITE or
READONLY.
ANR2112E
Command: Volume volume name is not in

a primary storage pool.

name of a volume that does not belong to a primary
storage pool. The command syntax requires that a
volume in a primary storage pool be specified.
206

volume name cannot be changed to
destroyed - volume is still online.
Explanation: A RESTORE VOLUME command cannot

change the access mode of the indicated volume to
destroyed because the volume is still online.
command.
User response: Issue the VARY OFFLINE command,
and reissue the RESTORE VOLUME command.
ANR2116E

destroyed - volume does not belong to
a primary storage pool.
Explanation: The access mode for the indicated

volume cannot be changed to destroyed because the
volume does not belong to a primary storage pool.
System action: The access mode for this volume is not
changed.
ANR2117E ANR2125I
ANR2117E

offsite - volume either does not belong
to a copy storage pool or from a device
class of DEVTYPE=SERVER.
Explanation: The server issues this warning when a

significant amount of database change activity has
occurred and the server database has not been backed
up.
Explanation: The access mode for the indicated

volume cannot be changed to offsite because the
volume either does not belong to a copy storage pool
or is of a device class with a DEVTYPE of SERVER.
User response: To provide for server database

recovery should a hardware or software problem affect
your database, use the BACKUP DB command to back
up the database.
System action: The access mode for this volume is not

changed.
ANR2122E

ANR2118E
Storage pool storage pool name specified

on the MOVE DATA command is not a
valid poolname and or pooltype for
volume volume name.
Explanation: If the volume belongs to a primary

storage pool, then the storage pool specified must also
be a primary storage pool. If the volume belongs to a
copy storage pool, then the specified storage pool must
be the same storage pool as that of the volume.
command name: The DOMAINS

parameter cannot be specified when the
NODES parameter is specified.
Explanation: Both the NODES and DOMAINS

parameters were specified. The NODES parameter may
be specified, or the DOMAINS parameter may be
specified, but both should not be specified at the same
time.
User response: Reenter the command specifying either
the NODES parameter or the DOMAINS parameter, but
not both.
System action: The MOVE DATA process fails.

User response: Provide a valid primary storage pool
name if the volume belongs to a primary storage pool.
If the volume belongs to a copy storage pool, remove
the storage pool name from the command.
ANR2119I
The Option option has been changed in

the options file.
Explanation: The option is updated in the server

options file.
System action: Server continues.
ANR2120E
Command: Invalid platform name platform name.

platform name.
command.
platform name.
ANR2121W
ATTENTION: More than amount changed

unit megabytes, gigabytes or terabytes of the
database has changed and the last
database backup was more than hours
name hours ago. Use the BACKUP DB
command to provide for database
recovery.
ANR2123E
command name: The NODES parameter

cannot be specified when the
DOMAINS parameter is specified.
Explanation: Both the NODES and DOMAINS

parameters were specified. The NODES parameter may
be specified, or the DOMAINS parameter may be
specfied, but both should not be specified at the same
time.
User response: Reenter the command specifying either
the NODES parameter or the DOMAINS parameter, but
not both.
ANR2124E
command name: Invalid Client authority

specified: authority.
Explanation: An invalid client authority was specified

in a GRANT AUTHORITY or REVOKE AUTHORITY
command when the CLASS=NODE parameter was
specified.
valid client authority.
ANR2125I
command name: Administrator

administrator name was granted OWNER
authority for client client name.
Explanation: The named administrator was granted

OWNER authority over the named client node as the
result of a GRANT AUTHORITY command.
207
ANR2126I ANR2136I
ANR2126I
command name: Administrator

administrator name was granted ACCESS
authority for client client name.
Explanation: The named administrator was granted

ACCESS authority over the named client node as the
result of a GRANT AUTHORITY command.
ANR2127I
command name: Owner authority for node

client node was revoked for administrator
administrator.
Explanation: OWNER authority over the named client

node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command.
ANR2128I
command name: Access authority for node

client node was revoked for administrator
administrator.
Explanation: ACCESS authority over the named client

node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command.
ANR2131I
Server password set.
Explanation: The password that the server uses to

allow other servers to communicate with it has been
set, changed or removed with the SET
SERVERPASSWORD command.
ANR2132I
Server hladdress set to hladdress.
Explanation: The high level address that other servers

use to communicate with this server has been set to the
value indicated with the SET SERVERHLADDRESS
command.
ANR2133I
Server lladdress set to lladdress.
Explanation: The low level address that other servers

use to communicate with this server has been set to the
value indicated with the SET SERVERLLADDRESS
command.
ANR2134I
Server url set to url.
Explanation: The url that other servers use to

communicate with this server has been set to the value
indicated with the SET SERVERURL command.
ANR2129I

name defined ONLY for authority over
node node name has been removed.
Explanation: The specified administrator has been

removed because the client node was removed and the
administrator only had OWNER access to the specified
node.
ANR2130S
Early Product Version has Expired.

Server is HALTing.
Explanation: This server is pre-release version of the

server. The pre-release versions expiration date has
been reached.
System action: The server halts.
User response: Install the product version of the
server.

ANR2135I
Crossdefine set to state.
Explanation: The ability for another server to

automatically define itself to this server has been
turned on or off as indicated with the SET
CROSSDEFINE command.
ANR2136I
Administrator administrator name already

has POLICY access for domain policy
domain name.
Explanation: The named administrator already has

POLICY authority over the named policy domain. An
attempt to grant client authority over this domain is
ignored.
System action: The policy domain is skipped.
208
ANR2137I ANR2146E
ANR2137I

has POLICY access for domain policy
domain name to which node node name
belongs.
Explanation: The named administrator already has

POLICY authority over the named policy domain. An
attempt to grant client authority for a client in this
domain is ignored.
System action: The client is skipped.
ANR2138I
Minimum password length set to length.
Explanation: The minimum length of a password a

node or administrator may send to the server is
indicated with the SET MINPWLENGTH command.
ANR2139E
Command: The value supplied for the

minimum password length is not valid length.
Explanation: A SET MINPWLENGTH command has

been entered that specifies a value for the length is not
valid. Valid values are from 0 to 64, inclusive.
command.
value.
ANR2140E
Command: Invalid activity log retention

period - retention value.
Explanation: A SET ACTLOGRETENTION command

has been entered that specifies an invalid log retention
period.
command.
retention period.
ANR2141E
Command: Invalid password expiration

period - days value.
Explanation: A SET PASSEXP command has been

entered that specifies an invalid days value.
command.
User response: Reissue the command with a password
expiration period.
ANR2142E
Command: Invalid server name - server

name.
Explanation: A SET SERVERNAME command has

been entered that specifies an invalid server name.
command.
server name.
ANR2143E
Command: Invalid node name - node

name.

node name.
command.
node name.
ANR2144E
Command: Invalid password - password.
Explanation: The command specifies an invalid node

password.
command.
User response: Ensure that the password adheres to
naming convention rules and meets the required
minimum password length as set by your
administrator. Then, reissue the command with a valid
password.
ANR2145E
Command: Contact information exceeds

maximum characters characters.
Explanation: A REGISTER NODE or REGISTER

ADMIN command has been entered that specifies a
contact information value that is too long. The
maximum valid length is shown in the command.
command.
User response: Reissue the command with less contact
information.
ANR2146E
Command: Node node name is not

registered.
Explanation: The command shown specifies a node

that is not registered with the server.
command.
209
ANR2147E ANR2156E
ANR2147E
Command: Node node name is already

registered.
ANR2152E
Command: Inventory references still exist

for node node name.
Explanation: A REGISTER NODE command has been

entered that specifies a node name already registered
with the server.
Explanation: A REMOVE NODE command has been

entered for a node for which the server is still storing
backup or archive data, or both.

command.

command.
User response: To register the node, reissue the

command and specify a different node name.
User response: To remove the node, delete all of its

file spaces and any virtual file space mapping
definitions from the server and reissue the command.
ANR2148E
Command: Administrator administrator ID

is not registered.

administrator ID that is not registered with the server.
command.
ANR2149E

is already registered.
Explanation: A REGISTER ADMIN command has

been entered that specifies an administrator ID already
registered with the server.
command.
User response: To register the administrator, reissue
the command and specify a different administrator ID.
ANR2150E
Command: Node node name is currently

accessing the server.
Explanation: The command shown specifies a node

that has an active session with the server.
command.
or if necessary, cancel the current session and reissue
the command.
ANR2151E

is currently accessing the server.
Explanation: An UPDATE ADMIN or REMOVE

ADMIN command has been entered that specifies an
administrator ID that is having an active session with
the server.
command.
or if necessary, cancel the current session and reissue
the command.
210
ANR2153E
Command: Invalid file space name filespace name.

entered with a file space name that is longer than
allowed.
command.
User response: Reissue the command with a valid file
space name.
ANR2154E
Command: Invalid administrator name administrator ID.

administrator ID.
command.
administrator ID.
ANR2155E
Command: Invalid privilege class privilege class.
Explanation: A command specifies an invalid

administrative privilege class.
command.
privilege class.
ANR2156E

has already been granted system
privilege.
Explanation: A GRANT AUTHORITY command has

been issued to grant system authority to an
administrator ID that already has system authority.
command.
ANR2157E ANR2166E
ANR2157E
Command: Other privileges cannot be

granted with system privilege.

been issued to grant system authority to an
administrator ID, and at the same time to grant other
privileges.
command.
User response: Reissue the GRANT AUTHORITY
command specifying only system privilege class.
ANR2158E
Command: Policy domains cannot be

specified for unrestricted policy
Explanation: A REVOKE AUTHORITY command has

been issued to revoke an administrators policy
authority over a specific policy domain, but the
administrator has unrestricted policy authority.
command.

command.
ANR2162E
Command: No privileges revoked for


been issued to revoke authority from an administrator
ID, but the administrator does not have any of the
privileges specified.
command.
ANR2163E
Command: Command is invalid for

administrator ID.
Explanation: The command specified cannot be issued

for the server console. For instance, the server console
administrator ID cannot be removed.
command.
ANR2159E
Command: Storage pools cannot be

specified for unrestricted storage

been issued to revoke an administrators storage
authority over a specific storage pool, but the
administrator has unrestricted storage authority.
command.
ANR2160E
Command: No new privileges granted to


been issued to grant authority to an administrator ID,
but the administrator already has all privileges
specified.
command.
ANR2161E
Command: Only system privilege can be

revoked for administrator administrator
ID.

been issued to revoke one or more of an
administrators privileges, but the administrator has
system authority.
ANR2164E
Command: Command rejected administrator ID is the only system

administrator.
Explanation: A REMOVE ADMIN or REVOKE

AUTHORITY command has been issued to remove or
revoke the authority of the last administrator who had
system authority.
command.
User response: To remove or revoke this ID, grant
system authority to another administrator ID before
reissuing the command.
ANR2165E
Command: Invalid begin date - date.
Explanation: A QUERY ACTLOG command has been

entered that specifies an invalid begin date as a search
criteria.
command.
begin date.
ANR2166E
Command: Invalid begin time - time.

entered that specifies an invalid begin time as a search
criteria.
211
ANR2167E ANR2176E
command.

command.

begin time.

date/time range.
ANR2167E
Command: Invalid end date - date.
ANR2172E
Command: No matching administrators.

entered that specifies an invalid end date as a search
criteria.
Explanation: The command shown specified an

administrator ID that does not match any administrator

command.
User response: Reissue the command with a valid end

date.
User response: If desired, reissue the command with a

different administrator ID.
ANR2173E
ANR2168E
Command: Invalid end time - time.

entered that specifies an invalid end time as a search
criteria.
command.
User response: Reissue the command with a valid end
time.
ANR2169E
Command: Invalid message number message number.

entered that specifies an invalid message number as a
search criteria.
command.
message number.
ANR2170E
Command: Invalid message search string

argument - search string.

entered that specifies an invalid search string as a
search criteria.
command.
search string.
ANR2171E
Command: Invalid time range - Begin:

date time End: date time.

entered that specifies an invalid beginning and ending
date/time range. This error can occur when the
beginning date/time is not before the ending
date/time.
212
Command: Location information exceeds

Explanation: A DEFINE or UPDATE VOLUME

command has been entered that specifies a location
information value that is too long. The maximum valid
length is shown in the command.
command.
User response: Reissue the command with less
location information.
ANR2174E
Administrator administrator ID is not

registered. Schedule schedule name is not
processed and is marked as failed.

administrator ID that is not registered with the server.
The schedule and related command are not processed.
command.
User response: Update the command schedule with a
valid administrator ID which has the proper authority
to execute the scheduled command.
ANR2175I
Invalid password limit set to password

attempts limit attempts.
Explanation: The maximum number of consecutive

invalid passwords a node or administrator may send to
the server is indicated with the SET INVALIDPWLIMIT
command.
ANR2176E

invalid password attempts limit is not
valid - password attempts limit.
Explanation: A SET INVALIDPWLIMIT command has

been entered that specifies a value for the consecutive
invalid password attempts limit that is not valid. Valid
ANR2177I ANR2183W
values are from 0 to 9999, inclusive.
command.
value.
ANR2177I
node/admin name has count invalid

sign-on attempts. The limit is limit.
Explanation: The server detected an invalid password

for the specified node during sign-on processing. The
node currently has sent count consecutive invalid
passwords. The maximum allowed is limit. The server
will lock the node when limit is reached.
System action: The node or administrator session will
be refused.
must unlock the node or administrator with the
UNLOCK NODE or UNLOCK ADMIN command.
ANR2178E
node/admin name has been locked. Invalid

sign-on attempt limit (limit) reached.
Explanation: The specified node has been locked by

the server. The limit for consecutive invalid passwords
has been reached.
System action: The node or administrator session will
be refused.
must unlock the node or administrator with the
UNLOCK NODE or UNLOCK ADMIN command.
ANR2179E
Administrator administrator should have

been locked, but was not.
Explanation: The indicated administrator reached the

limit for consecutive invalid passwords and should
have been locked. If it were locked, there would be no
means to execute commands requiring system
authority.
administrative session, but the last access date is not

updated.
volumes are used.
ANR2181W
Unable to update last access date for

administrator administrator ID insufficient database space.
Explanation: While establishing an administrative

session for the indicated ID, the server cannot update
the administrators date of last access due to
insufficient database space.
System action: The server establishes the
updated.
ANR2182W

administrator administrator ID - internal
server error.

session for the indicated ID, the server cannot update
the administrators date of last access due to a server
internal error.
updated.
representative.
System action: The administrator session will be

refused.
ANR2183W
User response: Sign-on again using the correct

password.

failed transaction.
ANR2180W

administrator administrator ID insufficient recovery log space.

session for the indicated ID, the server is unable to
update the administrators date of last access due to
insufficient recovery log space.

was aborted.

fails.

213
ANR2184W ANR2191E
ANR2184W

was aborted for command command.

commit for the specified server command. This
message should be preceded by other messages that
give additional information about the failed transaction.
fails.
ANR2185W
Transaction was aborted for command

command.

failed transaction.
fails.
ANR2186W
Transaction was aborted for session

platform).

failed transaction.

ANR2188W
A Transaction was aborted. The activity

is terminating.
Explanation: An error is detected during a transaction

failed transaction.
ends.
ANR2189W

was aborted for node/admin name.

commit for the specified node or administrator name.
This message should be preceded by other messages
that give additional information about the failed
transaction.
fails.
ANR2190E
command: Device class DISK cannot be

specified for this command.
Explanation: The DEVCLASS value DISK cannot be

specified for the command.

fails.



server.
ANR2187W
Transaction was aborted for node/admin

name.

commit for the specified node or administrator name.
This message should be preceded by other messages
that give additional information about the failed
transaction.
fails.
214
ANR2191E
command: Volume list contains defined

and undefined volumes.
Explanation: The list of volumes specified on the

SALVAGE VOLUME command must all be defined to
the server, or all not defined to the server.
valid list of volumes.
ANR2192E ANR2202I
ANR2192E
Command: Unable to start background

process.
Explanation: The server command processor is not

able to start a background process to perform the
command command.
ANR2197E
Explanation: A SET WEBAUTHTIMEOUT command

has been entered that specifies a value that is not valid.
Valid values are from 0 to 9999, inclusive.
command.
value.
ANR2198I
ANR2193E
Command: Invalid option set name option set name.

option set name.
command.
option set name.
ANR2194E
Command: Invalid option set description

- too long.

description. The description is too long.
command.
description.
ANR2195E
Command: Invalid option sequence

number - option sequence number name.

option sequence number.
command.
option sequence number.
Command: Option name and/or Option
value is missing for define.
Explanation: The specified DEFINE command has

been entered, but no attributes have been specified for
the definition.
Command: Web authentication time-out

set to time-out value minutes.
Explanation: The time-out value that determines how

often WEB browser administrative users need to
re-authenticate with the server has been set with the
SET WEBAUTHTIMEOUT command to the value
displayed.
ANR2199I
Password expiration period for node

node name set to number of days days.
Explanation: The number of days that the nodes

password can be used before it must be changed has
been set to the value indicated with the SET PASSEXP
command.
ANR2200I
Storage pool storage pool name defined

(device class device class name).
Explanation: A DEFINE STGPOOL command has

created the storage pool indicated of the device class
shown.
ANR2201I
ANR2196E

WEB authentication time out is not
valid - time-out value.
Storage pool storage pool name deleted.
Explanation: A DELETE STGPOOL command has

deleted the storage pool indicated.

command.
ANR2202I
User response: Reissue the DEFINE command with

one or more attributes to be defined
Explanation: An UPDATE STGPOOL command has

updated the storage pool indicated.
Storage pool storage pool name updated.
215
ANR2203I ANR2213I
ANR2203I
Device class device class name defined.
Explanation: A DEFINE DEVCLASS command has

created the device class indicated.
v The volume was an empty scratch WORM FILE

volume and deleted by RECLAMATION since the
retention of the volume has expired.

ANR2204I
Device class device class name deleted.
Explanation: A DELETE DEVCLASS command has

deleted the device class indicated.
ANR2209W
Volume volume name contains no data.
Explanation: The AUDIT VOLUME or MOVE DATA

command entered specifies a volume that contains no
data.
command.

ANR2210I
ANR2205I
Device class device class name updated.
Explanation: An UPDATE DEVCLASS command has

updated the device class indicated.
Vary online initiated for disk volume

volume name.
Explanation: A VARY ONLINE command for the

volume shown is being processed, and if no errors
occur the volume will be varied online.
ANR2206I
Volume volume name defined in storage

pool storage pool name (device class device
class name).
ANR2211I
Vary offline initiated for disk volume

volume name.
Explanation: A DEFINE VOLUME command has

defined the volume indicated in the storage pool
shown that belongs to the device class shown.
Explanation: A VARY OFFLINE command for the

volume shown is being processed and, if no errors
occur, the volume will be varied offline.
ANR2207I
Volume volume name updated.
ANR2212I
Command: No volumes updated.
Explanation: An UPDATE VOLUME command has

updated the volume indicated.
Explanation: An UPDATE VOLUME command has

been entered, but no objects were updated.
ANR2208I
Volume volume name deleted from

Explanation: The volume indicated has been deleted

by one of the following:
v A DELETE VOLUME command was issued.
v The volume was empty and the volumes access
mode was updated to destroyed.
v The volume was empty, scratch, and offsite, and the
access mode was changed to readwrite, readonly, or
unavailable.
v The volume was scratch, not offsite, and was
emptied by DELETE FILESPACE, RECLAMATION,
or RESTORE VOLUME/STGPOOL.
216
ANR2213I

renamed to storage pool name.
Explanation: A RENAME STGPOOL command has

been entered. The rename of the storage pool was
successful.
ANR2214E ANR2223I
ANR2214E
Command: Invalid backup set name backup set name.
ANR2219I

backup set name.
backup set name.
ANR2215E
Command: Description text is too long.
Explanation: The specified description text is too long

for a command that allows description text to be
specified.
Explanation: The process that deleted data for the

volume shown has ended, but the volume has not been
deleted because the volume access is marked as offsite.
User response: To delete the volume, change the
volume access to readwrite, readonly, or unavailable.
ANR2220W
System action: The command fails

shorter description
ANR2216E
Command: Device class must be a

sequential device class.
Explanation: The device class specified on the

command is not a sequential device class.
User response: Reissue the command specifying the
name of a sequential device class
ANR2217E
Command: Invalid backup set retention

Explanation: Server processing for the backup set

value) specified for the RETENTION parameter is not
valid.
valid RETENTION value.
Command: A device class must be
specified.
Explanation: The DEVCLASS parameter is not

specified in the command command name. A DEVCLASS
value must be specified.
server.
This command will delete volume

volume name from its storage pool after
verifying that the volume contains no
data.
Explanation: A DELETE VOLUME command with the

Discarddata=No option has been entered.
System action: The system asks whether you wish to
continue with the command.
User response: To process the DELETE VOLUME
command, enter 'Y' to continue or 'N' to stop the
process.
ANR2221W
This command will result in the

deletion of all inventory references to
the data on volume volume name, thereby
rendering the data unrecoverable.
Explanation: A DELETE VOLUME command with the

Discarddata=Yes option has been entered.
User response: To process the DELETE VOLUME
process.
ANR2222I
ANR2218E
Discard Data process ended for volume

volume name - volume is not deleted
from storage pool storage pool name
because the volume access is offsite.
Discard Data process started for volume

volume name (process ID process ID).
Explanation: As a result of a DELETE VOLUME

command with the Discarddata=Yes option, the process
whose ID is displayed has begun to delete the data on
the volume shown.
System action: The server deletes the data on the
volume.
ANR2223I
Discard Data process ended for volume

volume name - volume deleted from
Explanation: The process that deleted data for the

volume shown has ended, and the volume has been
deleted.
217
ANR2224W ANR2233W
ANR2228W

ANR2224W
Discard Data process terminated for

Explanation: The process that was deleting data for

the volume shown, in preparation for deleting the
volume, has been canceled.
System action: The server does not delete the volume.
ANR2225W
Discard Data process terminated for

volume volume name - volume still
contains data.

volume, has ended. However, the volume contains
data.
Discard data process terminated for

volume volume name - lock conflict
detected.

volume, has ended due to a locking conflict.
User response: Reissue the command at a later time. If
this problem persists, contact your service
representative.
ANR2229W

error detected.

volume, has ended due to a server internal error.
System action: The server does not delete the volume

ANR2232W
ANR2226W

This command will move all of the data

stored on volume volume name to other
volumes within the same storage pool;
the data will be inaccessible to users
until the operation completes.

volume, has ended due to a shortage of recovery log
space.
Explanation: A move data has been entered that will

move data from the indicated volume to other volumes
in the same storage pool. While the data is being
moved, it will not be available to users.

continue.

volumes are used.
User response: Enter 'Y' to continue with the

command or 'N' to end the process.
ANR2233W
ANR2227W

is not available.

volume, has ended due to a shortage of memory.
218
This command will move all of the data

stored on volume volume name to other
volumes in storage pool storage pool
name; the data will be inaccessible to
users until the operation completes.
Explanation: A 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.
continue.
User response: Enter 'Y' to continue with the
command or 'N' to end the process.
ANR2234W ANR2241I
ANR2234W
This command will halt the server; if

the command is issued from a remote
client, it may not be possible to restart
the server from the remote location.
ANR2237W
Explanation: A HALT command has been entered.

continue.
User response: Enter 'Y' to halt the server or 'N' to
leave the server activated.
ANR2235W
This command will remove

administrator adminName. This
administrator has defined or updated
schedules. Removing this authority
WILL cause these schedules to fail.
Explanation: A REMOVE ADMINISTRATOR

command has been entered for an administrator that
owns administrative schedules. If you confirm that you
want to proceed with this command, the schedules
owned by this administrator will fail when executed in
the future.
User response: To process the REMOVE
ADMINISTRATOR command, enter 'Y' to continue or
'N' to stop the process. To deal with schedules owned
by the administrator, use the QUERY SCHEDULE
command OR an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which
schedules were last updated by the administrator. Use
the UPDATE SCHEDULE command to update those
schedules under an administrator that has authority to
execute them, or use the DELETE SCHEDULE
command to remove the schedules.
ANR2236W
This command has removed

schedules. This WILL cause these
schedules to fail in the future.
Explanation: A REMOVE ADMINISTRATOR

command has been entered and the administrator
removed owns administrative schedules. The schedules
will fail when executed in the future because they do
not belong to a valid administrator.
System action: The system removes the administrator.
User response: Use the QUERY SCHEDULE command
OR an SQL SELECT statement on the
This command has revoked privileges

for administrator adminName. This
schedules. This may cause these
schedules to fail in the future.

been entered.
System action: The system removes the authority.
ANR2238W
This command will result in the

deletion of all inventory references to
the data on filespaces that match the
pattern filespace name for node node name
, whereby rendering the data
unrecoverable.
Explanation: A DELETE FILESPACE command has

been entered.
User response: To process the DELETE FILESPACE
command, enter 'Y'; otherwise, enter 'N'.
ANR2239W
This command will revoke privileges

for administrator adminName. This
schedules. Revoking this authority may
cause schedules to fail.

been entered.
User response: To process the REVOKE AUTHORITY
process.
ANR2240I
Database volume volume name defined.
Explanation: A DEFINE DBVOLUME command has

defined the database volume indicated.
ANR2241I
Database volume copy volume name

defined.
Explanation: A DEFINE DBCOPY command has

defined the database volume indicated.
219
ANR2242I ANR2253W
ANR2242I
Database volume copy volume name

defined; synchronization process started
(process ID process ID).

added the volume shown as a database copy volume.
The process whose ID is displayed will copy data to
the new volume to synchronize it with existing
volumes.
ANR2248I
Explanation: An EXTEND DB command has increased

the storage capacity of the database.
ANR2249I

ANR2243I
Database volume volume name deleted.
Explanation: A DELETE DBVOLUME command has

deleted the database volume indicated.
ANR2244I
Delete process initiated for database

volume volume name (process id process
ID).
Explanation: In response to a DELETE DBVOLUME

command, the process with the process ID shown has
been started to delete the volume.

online.
Explanation: A VARY ONLINE command has put the

database volume indicated into an online state.
Database extension process initiated

Explanation: In response to an EXTEND DB

been started to extend the database.
ANR2250I
Database assigned capacity has been

reduced.
Explanation: A REDUCE DB command has decreased

the storage capacity of the database.
ANR2251I

ANR2245I
Database assigned capacity has been

extended.
Database reduction process initiated

Explanation: In response to a REDUCE DB command,

the process with the process ID shown has been started
to reduce the database.

ANR2246I
Vary online process initiated for

database volume volume name (process
ID process ID).
Explanation: In response to a VARY ONLINE

been started to vary on the database volume indicated.
ANR2252W
Database volume copy volume name is

larger than volume volume name by count
megabyte(s).

defined a database copy volume whose size is larger
than the volume it mirrors by the amount shown.
System action: The excess capacity is ignored.

ANR2247I

offline.
Explanation: A VARY OFFLINE command has put the

indicated database volume into an offline state.
220
ANR2253W
The database volume copy to be defined

(volume name) is larger than volume
volume name; use of the volume will
result in count megabyte(s) of unusable
space.
Explanation: A DEFINE DBCOPY command is

attempting to define a database copy volume whose
size is larger than the volume it mirrors by the amount
shown. The excess capacity would not be used.
ANR2254E ANR2262I
continue.
system administrator to have additional authority

granted to the current administrator ID.
User response: Enter 'Y' to define the copy, 'N'

otherwise.
ANR2258E
ANR2254E
Command: The VOLUMENAMES

parameter must be specified when
SCRATCH=NO is specified.
Explanation: The SCRATCH parameter is specified as

NO for the command Command but the
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES
parameter must be specified to indicate the volumes
that can be used for the command.
valid VOLUMENAMES parameter.
ANR2255E
Command: The VOLUMENAMES

parameter must be specified.
Explanation: The VOLUMENAMES parameter must

be specified to indicate the volumes that can be used
for the command.
valid VOLUMENAMES parameter.
ANR2256E
Command: The RETENTION parameter

must be specified.
Explanation: The RETENTION parameter must be

specified to indicate the retention period to be used for
the command.
valid RETENTION parameter.
Command: Invalid summary retention

Explanation: A SET SUMMARYRETENTION

retention period.
command.
retention period.
ANR2259I
Summary retention period set to number

of days days.
Explanation: The number of days that activity sumary

records are kept in the server database has been set to
the value indicated with the SET
SUMMARYRETENTION command.
ANR2260I
Recovery log volume volume name

defined.
Explanation: A DEFINE LOGVOLUME command has

defined the recovery log volume indicated.
ANR2261I
Recovery log volume copy volume name

defined.
Explanation: A DEFINE LOGCOPY command has

defined the recovery log volume indicated.
ANR2257E

command for node node name.

command for the indicated node. Note: This message
can be issued as a result of the server option
REQSYSAUTHOUTFILE YES being in effect.
command for the indicated node. If multiple nodes
were specified on the command, the server may
continue processing the command for the other nodes.
ANR2262I

defined; synchronization process started

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: Examine previous messages for any

additional information. Issue the command from a
properly authorized administrator ID, or contact the
221
ANR2263I ANR2273W
ANR2263I
Recovery log volume volume name

deleted.
Explanation: A DELETE LOGVOLUME command has

removed the recovery log volume indicated.
ANR2269I
Recovery log extension process initiated

Explanation: In response to an EXTEND LOG

been started to extend the recovery log.
ANR2264I
Delete process initiated for recovery log

volume volume name (process id process
ID).
Explanation: In response to a DELETE LOGVOLUME

command, the process with process ID shown has been
started to delete the volume.
ANR2270I
Recovery log assigned capacity has been

reduced.
Explanation: A REDUCE LOG command has

decreased the storage capacity of the recovery log.

ANR2271I
ANR2265I

online.
Recovery log reduction process initiated

Explanation: A VARY ONLINE command has put the

recovery log volume indicated into an online state.
Explanation: In response to a REDUCE LOG

been started to reduce the recovery log.
ANR2266I
ANR2272W
Vary online process initiated for

recovery log volume volume name
Explanation: In response to a VARY ONLINE

command, the process with process ID shown has been
started to vary on the recovery log volume indicated.

is larger than volume volume name by
count megabytes.

defined a recovery log copy volume whose size is
larger than the volume it mirrors by the amount
shown.
System action: The excess capacity is ignored.
ANR2267I

offline.
Explanation: A VARY OFFLINE command has put the

recovery log volume indicated into an offline state.
ANR2268I
Recovery log assigned capacity has been

extended.
Explanation: An EXTEND LOG command has

increased the storage capacity of the recovery log.
222
ANR2273W
The recovery log volume copy to be

defined (volume name) is larger than
volume volume name; use of the volume
will result in count megabytes of
unusable space.
Explanation: A DEFINE LOGCOPY command is

attempting to define a recovery log copy volume whose
size is larger than the volume it mirrors by the amount
shown. The excess capacity would not be used.
continue.
User response: Enter 'Y' to define the copy or 'N' to
stop the process.
ANR2274I ANR2283I
ANR2274I
Data Base Space trigger defined and

enabled.
ANR2279I
Recovery Log Space trigger defined and

enabled.
Explanation: The database space trigger has been

defined with a DEFINE SPACETRIGGER command.
The percentage of utilization specified with the
FULLPCT parameter is used to automatically expand
the database.
Explanation: The recovery log space trigger has been

defined with a DEFINE SPACETRIGGER command.
The percentage of utilization specified with the
FULLPCT parameter is used to automatically expand
the recovery log.
ANR2275I
ANR2280I
Data Base Space trigger defined, but is

disabled.
Full database backup started as process

process ID.
Explanation: A database space trigger has been

defined, but because the space expansion percentage is
currently set to 0, the space trigger is disabled.

backup the contents of the database. The full database
backup process was assigned the process ID shown.
System action: The database backup process starts

User response: To activate the space trigger, use the

UPDATE SPACETRIGGER command to set the space
expansion percentage to a value greater than 0.
ANR2276I
Data Base Space trigger updated and

enabled.
Explanation: An UPDATE SPACETRIGGER command

has successfully completed for the data base space
trigger. The updated parameters specified on the
command are used to automatically trigger space
expansion for the database.
ANR2277I
Database Space trigger updated, but

disabled.

has successfully completed for the data base space
trigger. However, the space expansion percentage is
currently set to 0, which disables the space trigger.
UPDATE SPACETRIGGER command with the
SPACEexpansion parameter to set a value greater than
zero.

status of the database backup process by using the
QUERY PROCESS command, or cancel the process with
ANR2281I
Incremental database backup started as

process process ID.

backup the contents of the database. The incremental
database backup process was assigned the process ID
shown.
QUERY PROCESS command, or cancel the process with
ANR2282I
Database backup trigger defined and

enabled.
Explanation: A database backup trigger has been

defined with a DEFINE DBBACKUPTRIGGER
command. The percentage of recovery log utilization
specified with the LOGFULLPCT parameter is used to
automatically trigger database backups.
ANR2278I
Database Space trigger deleted.
Explanation: A DELETE SPACETRIGGER command

has successfully completed for the database space
trigger. Space expansions are no longer triggered
automatically for the database.

ANR2283I
Database backup trigger defined, but is

disabled.
Explanation: A database backup trigger has been

defined, but because the recovery log mode is currently
set to NORMAL, the database backup trigger is
disabled. Database backups can only be triggered when
223
ANR2284I ANR2292W
the log mode is set to ROLLFORWARD with a SET
LOGMODE command.
User response: To activate the database backup
trigger, use the SET LOGMODE ROLLFORWARD
command.
ANR2284I
Database backup trigger updated and

enabled.
Explanation: An UPDATE DBBACKUPTRIGGER

command has successfully completed. The updated
parameters specified on the command are used to
automatically trigger database backups.
ANR2288I
Subfile set to state.
Explanation: The SET SUBFILE command has been

used to specify whether this server will allow clients to
back up subfiles. If a value of CLIENT is specified,
clients are given the option of backing up subfiles. If a
value of NO is specified, clients are not allowed to back
up subfiles.
ANR2289I

name defined for authority over node
node name has not been removed.
Explanation: The specified administrator was not

removed.
ANR2285I
Database backup trigger updated, but

disabled.
Explanation: An UPDATE DBBACKUPTRIGGER

command has successfully completed, but because the
recovery log mode is currently set to NORMAL, the
database backup trigger is disabled. Database backups
can only be triggered when the log mode is set to
ROLLFORWARD with a SET LOGMODE command.
User response: To activate the database backup
trigger, use the SET LOGMODE ROLLFORWARD
command.
ANR2286I
Database backup trigger deleted.
Explanation: A DELETE DBBACKUPTRIGGER

command has successfully completed. Database
backups are no longer triggered automatically by
recovery log utilization.
ANR2287I
Snapshot database backup started as

process process ID.

backup the contents of the database. The snapshot
database backup process was assigned the process id
shown.
started process by using the QUERY PROCESS
command, or may cancel the process using the

ANR2290W
Changing the log mode to NORMAL

will prevent roll-forward recovery.
Explanation: The system has determined that

changing the recovery log mode from ROLLFORWARD
to NORMAL mode will cause the log records being
kept for ROLLFORWARD and single database volume
restore processing to be discarded. Without these log
records, only point-in-time database restores can be
performed.
continue.
User response: Enter 'Y' to change the LOGMODE, 'N'
otherwise.
ANR2291W
Changing the log mode to NORMAL

will disable the database backup trigger.
Explanation: Changing the recovery log mode from

ROLLFORWARD to NORMAL disables the setting
specified in the DEFINE DBBACKUPTRIGGER
command. Database backups can only be triggered
when the recovery log mode is set to ROLLFORWARD
with the SET LOGMODE command.
continue.
User response: Enter 'Y' to change the log mode, 'N'
otherwise. Responding 'Y' does not delete the DEFINE
DBBACKUPTRIGGER settings.
ANR2292W
Changing the log mode to

ROLLFORWARD will enable the
database backup trigger.
Explanation: Changing the recovery log mode from

NORMAL to ROLLFORWARD causes a previously
224
ANR2293I ANR2301E
issued DEFINE DBBACKUPTRIGGER command to
become effective, and immediately start a full database
backup. Database backups can only be triggered when
the recovery log mode is set to ROLLFORWARD with a
SET LOGMODE command.
log records needed to resume database processing if a

system failure occurs are saved in this mode. Database
backups can only be started using the BACKUP DB
command.

continue.
User response: Enter 'Y' to change the log mode, 'N'

otherwise.
ANR2297I
ANR2293I
Only point-in-time database recovery is

now possible.
Explanation: An administrator has changed the

recovery log mode from ROLLFORWARD to NORMAL
with a SET LOGMODE command. Only point-in-time
database restores can be performed. ROLLFORWARD
database restores and individual database volume
restores are not possible.
Explanation: The requested option sequence number

has been updated in response to an UPDATE
CLIENTOPT command.
ANR2298I

ANR2294I
Log mode set to log mode.
Explanation: The mode for saving recovery log

records has been set as indicated by the SET
LOGMODE command. When set to NORMAL, only
those log records needed to resume database processing
if a system failure occurs are saved. When set to
ROLLFORWARD, all log records created since the last
database backup are saved. ROLLFORWARD mode
also enables the database backup trigger to be used to
automatically start database backups based on the
percentage of recovery log utilization.
ANR2295I
Log mode set to ROLLFORWARD;

database backup trigger enabled.

records has been set to ROLLFORWARD, and a
previously defined database backup trigger has been
enabled. All log records created since the last database
backup are saved in this mode. The database backup
trigger will automatically start a database backup based
on the percentage of recovery log utilization.
Command: Optionset optionset name,

option option name, sequence number old
sequence number, has been changed to
new sequence number.
Command: Optionset optionset name,

option option name, sequence number old
sequence number, is not updated.
Explanation: The requested option sequence number

is not updated in response to an UPDATE CLIENTOPT
command.
User response: Reissue the UPDATE CLIENTOPT
command with a valid old sequence number.
ANR2299I
Password expiration period for

administrator administrator name set to
number of days days.
Explanation: The number of days that the

administrators password can be used before it must be
changed has been set to the value indicated with the
SET PASSEXP command.
ANR2300E
Could not open file spec the server help

file.
Explanation: The named help file could not be

accessed.
System action: The requested help text is not

displayed.
User response: Contact the system administrator.
ANR2296I
ANR2301E
Log mode set to NORMAL; database

backup trigger disabled.

records has been set to NORMAL mode, and the
defined database backup trigger is disabled. Only those
Errors were encountered while setting

up the index to the help text.
Explanation: Either insufficient memory or a help file

read failure has occurred during setup of the help
index.
225
ANR2302E ANR2309E
System action: The server does not display the
requested help text.
System action: The server does not process the HELP

command.
ANR2302E
The argument operand is not valid for

the HELP command.
Explanation: The argument supplied on the HELP

command is not an integer or the name of a command.
command.
User response: Issue the HELP command with no
operands and select from the numbered list displayed
in response.
ANR2303E

command.
User response: Issue the HELP command with no
operands and select from the numbered list (help
index) displayed in response.
I/O error reading help file name the file
of help text.
No help text could be found for this

message: message ID.
Explanation: The message ID you entered for the help

command does not match any message entry in the file
of help text.
System action: The help command is not processed.
ANR2308W
There is no help section numbered

section number.
Explanation: The numeric operand supplied on the

HELP command is either less than 1 or greater than the
highest-numbered entry in the help index.
ANR2304E
ANR2307E
Audit Volume marking damaged file as

damaged on volume volume name: Node
node name, Type file type, File space
filespace name, fsId filespace id, File Name
file name is number version of total
versions versions.
Explanation: As the result of an AUDIT VOLUME

command that specified FIX=YES for the volume
shown, the file whose information is displayed is
marked as damaged in the server. The file is marked as
damaged because it can be recovered from a copy
known to exist in a COPY storage pool. If this file
belongs to an aggregate, the entire aggregate is marked
damaged, and this message will be issued for every file
in the aggregate. The version numbers for the file are
numbered from most recent (1) to least recent (n, where
n is the total number of versions.
Explanation: An error is detected when reading help

text from the named file.
System action: The file is marked as damaged in the

server database.
System action: The server ends display of the help

text.
User response: To recover the damaged file use the

RESTORE STGPOOL or RESTORE VOLUME command.

ANR2309E
ANR2305E
No such command/subcommand:
command subcommand.
Explanation: The operands you entered for the HELP

command do not match any named entry into the file
of help text.
command.
User response: Check your input for a misspelled
command or subcommand name.
ANR2306E
No help text could be found for this

command/subcommand: command.
Explanation: The operands you entered for the HELP

command, although valid command/subcommand
names, do not match any named entry into the file of
help text.
226
The server log mode is currently set to

roll-forward. You may run out of log
space when auditing the server in this
mode. Specify LOGMODE=NORMAL
to set the log mode to NORMAL for the
audit operation, or
LOGMODE=ROLLFORWARD to force
the audit operation with the logmode
set to roll-forward.
Explanation: An AUDITDB operation was specified

and the server log mode is set to roll-forward mode.
When in roll-forward mode, the server may run out of
log space during the AUDITDB operation, requiring an
emergency extend of the recovery log to re-start the
server. The recommended log mode for executing an
AUDITDB operation is NORMAL.
System action: The AUDITDB operation fails
User response: To force the server log mode to
NORMAL for the AUDITDB operation, specify
LOGMODE=NORMAL on the AUDITDB command.
ANR2310W ANR2315I
Specify LOGMODE=ROLLFORWARD on the
AUDITDB command to allow the audit to run with a
roll-forward log mode setting.
ANR2310W
This command will compare all

inventory references to volume volume
name with the actual data stored on the
volume and will report any
discrepancies; the data will be
inaccessible to users until the operation
completes.
Explanation: During the execution of an AUDIT

VOLUME command, any data the volume named
would be unavailable to users.
continue.
stop the process.
ANR2311W
This command will discard any

inventory references to volume volume
name associated with missing or
inconsistent stored data, thereby
rendering the data unrecoverable; the
valid data on the volume will be
inaccessible to users until the operation
completes.
Explanation: During the execution of an AUDIT

VOLUME command, any data the volume named
would be unavailable to users. After the command has
ended, any inconsistent data found will be discarded.
continue.
stop the process.
ANR2312I
Audit Volume (Repair) process started

for volume volume name (process ID
process ID).

shown, the process whose ID is displayed has begun
auditing the volume.
System action: The volume is audited and
inconsistent data is discarded.
ANR2313I
Audit Volume (Inspect Only) process

started for volume volume name (process
ID process ID).
shown, the process whose ID is displayed has begun

auditing the volume.
System action: The volume is audited and
inconsistent data is displayed.
ANR2314I
Audit volume process ended for volume

volume name; file count files inspected, file
count damaged files deleted, file count
damaged files marked as damaged.
Explanation: The AUDIT VOLUME command

specifying FIX=YES for the volume shown has ended.
The number of files audited and the number of
inconsistent files deleted or marked as damaged are
displayed. The number of files marked as damaged
includes all files belonging to aggregates that were
marked damaged during the audit. Files are marked as
damaged in primary storage pools and not deleted
when backup copies for the files are known to exist in
COPY storage pools.
User response: To recover files that have been marked
as damaged on the volume, use the RESTORE
STGPOOL or RESTORE volume command.
ANR2315I

count damaged files found and marked
as damaged.

specifying FIX=NO for the volume shown has ended.
The number of files audited and the number of
inconsistent files found are displayed. The number of
files marked damaged includes all files belonging to
aggregates that were marked damaged during the
audit. Inconsistent files are marked as damaged in the
database and can be recovered by using the RESTORE
STGPOOL or RESTORE VOLUME command if copies
of the files reside in a COPY storage pool. Another
AUDIT VOLUME command may be able to access the
files and reset the damaged indicator in the database if
the audit volume process cannot access the files due to
hardware problems (for example, dirty tape heads).
User response: If you suspect that files were
inaccessible because of hardware problems such as
dirty tape heads, correct the hardware problem and
reissue the AUDIT VOLUME FIX=NO command for
this volume. To remove damaged file references, issue
the AUDIT VOLUME command and specify FIX=YES.

command that specified FIX=NO for the volume
227
ANR2316W ANR2324W
ANR2316W
Audit Volume deleting damaged file on

fsId filespace id, File Name file name is
number version of total versions versions.

shown, the file whose information is displayed is
deleted from the server. The version numbers for the
file are numbered from most recent (1) to least recent
(n, where n is the total number of versions.
System action: The file is deleted.
ANR2317W
Audit Volume found damaged file on

fsId filespace id, File name file name is
number version of total versions versions.

shown, the file whose information is displayed is found
to be in error and not accessible. If this file belongs to
an aggregate, the entire aggregate is marked damaged,
and this message will be issued for every file in the
aggregate. The version numbers for the file are
numbered from most recent (1) to least recent (n, where
n is the total number of versions.
ANR2318W
Audit volume process terminated for

Explanation: During processing of an AUDIT

VOLUME command for the volume shown, the process
performing the audit was canceled.
System action: The AUDIT VOLUME command is
ended.
ANR2319W

volume volume name - error reading
device.

VOLUME command for the volume shown, an
unrecoverable read error occurred on the volume.
ended.
User response: Attempt to correct the cause of the
read error, and reissue the command.
228
ANR2320W

volume volume name - data transfer
interrupted.

VOLUME command for the volume shown, a data
transfer operation has been interrupted and cannot be
continued.
ended.
cause of the interruption, and reissue the command.
ANR2321W

volume volume name - storage media
inaccessible.

VOLUME command for the volume shown, a required
volume cannot be mounted.
ended.
ANR2322W


VOLUME command for the volume shown, the server
does not have sufficient recovery log space to continue.
ended.
User response: If necessary, make more recovery log
space available to the server.
ANR2323W

volume volume name - sufficient database

does not have sufficient database space to continue.
ended.
User response: If necessary, make more database
space available to the server.
ANR2324W

volume volume name - thread resource
not available.

cannot start a thread for the audit process.
ANR2325W ANR2336W
ended.
User response: Reissue the AUDIT VOLUME
command. If the error persists, it may indicate a
ANR2325W

is not available.

does not have enough memory available to complete
the command.
ended.
User response: If necessary make more memory
ANR2326W

volume volume name - lock conflict
detected.

cannot obtain a required lock.
ended.
User response: Reissue the command.
ANR2327W

error detected.

VOLUME command for the volume shown, an internal
server error occurs.
ended.
ANR2332W
Object object.ID deleted by another

process during execution of an AUDIT
VOLUME command for volume volume
name.

VOLUME command, a data storage object was deleted
from the volume that was being audited. The AUDIT
VOLUME process was unable to locate this object on
the specified volume. Normally, this action is not
considered an error condition, because the object was
probably deleted by a process such as a DELETE
FILESPACE command.
System action: Processing of the AUDIT VOLUME
command continues.
User response: Check the activity log to verify that

some process (such as a DELETE FILESPACE
command) was in progress during the AUDIT
VOLUME command that would account for the deleted
object. If no such process can be identified, contact your
ANR2333W
Missing or incorrect information

detected by AUDIT VOLUME for
volume volume name.
Explanation: An AUDIT VOLUME command detects

missing or incorrect information for the specified
volume.
User response: Reissue the audit command with
FIX=YES so that the information can be created or
corrected.
ANR2334W
Missing or incorrect information

detected by AUDIT VOLUME for
volume volume name - information will
be created or corrected.
Explanation: An AUDIT VOLUME process detects

missing or incorrect information for the specified
volume. Because FIX=YES has been specified for the
audit command, the information is created or corrected.
ANR2335W
Audit Volume has encountered an I/O

error for volume volume name while
attempting to read: Node node name,
Type file type, Filespace filespace name,
fsId filespace id, File Name file name.
Explanation: The AUDIT VOLUME process

encountered an I/O error for the specified volume
while attempting to read the specified file. If this file
belongs to an aggregate, the entire aggregate is marked
damaged, and this message will be issued for every file
in the aggregate.
User response: Identify and resolve the I/O error for
the volume if possible. Verify that the volumes device
is functioning properly and that the volume is usable.
For example, if the volume is a tape volume, make sure
the drive is clean or that the tape volume is usable by
testing it by using a different drive.
ANR2336W
Audit Volume terminated for volume

volume name - insufficient number of
media.
Explanation: During Audit Volume for the indicated

229
ANR2337W ANR2345E
volume, the server could not allocate sufficient mount
points for the volume required.
System action: Audit Volume stops.
available.
ANR2337W
Header size is reset for object Object.ID,

verb type (Verb Type), from (Header Size)
to (Verb Length).
Explanation: The header size for the specified object

was recalculated while anditing a volume.
System action: If FIX=YES was specified, the header
size for the object will be updated. Processing
continues.
ANR2338E
Diagnostic(ID): Invalid header received

for object Object.ID, length Data Length.
Size (Header Size), pushed (Pushed
Length), skipped (Skipped Length), status
(New Retrieve). Found length (Verb
Length), type (Verb Type), size (Verb Size).
Explanation: An invalid header was detected for the

specified object while auditing a volume. Diagnostic
information is included in the message.
System action: If FIX=YES was specified, this object
will be marked damaged. Processing continues.
User response: Restore the volume or storage pool
that includes this object.
ANR2341E
Explanation: The command indicated requires a

storage pool name, but none has been entered.
command.
User response: Reissue the command with a storage
pool name.
ANR2342E
Command: Object sets still exist for node

node name.
Explanation: A REMOVE NODE command has been

entered for a node for which the server is still storing
backup sets. To remove a node, the node must not have
any files or backup sets stored on the server.
command.
User response: To remove the node, delete all backup
sets from the server and reissue the command.
ANR2340E
Command: Invalid storage pool name storage pool name.
Explanation: The command indicated contains an

invalid storage pool name.
command.
storage pool name.
230
Command: Storage pool description

exceeds maximum characters characters.
Explanation: The command indicated contains a

storage pool description that exceeds the maximum
length allowed.
command.
storage pool description.
ANR2343E
Command: Invalid device class name device class name.

invalid device class name.
command.
device class name.
ANR2344E
ANR2339E
Command: Missing next storage pool

name.
Command: The option option is not

valid for device class device class name.
Explanation: The command indicated specifies an

option shown that is not valid for a storage pool that
belongs to the device class shown.
command.
User response: Reissue the command with options
appropriate to the device class.
ANR2345E
Command: Invalid volume name - volume

name.

invalid volume name.
command.
volume name.
ANR2346E ANR2355E
ANR2346E
Command: Volume name volume name is

not valid for device class device class
name.

ANR2351E
Command: Device class device class name

is not defined.

name of a volume that cannot be used with the device
class shown.
Explanation: The command indicated references a

device class that does not exist.

command.

command.

volume name.
ANR2347E
Command: Volume name volume name is

ambiguous; resolves to multiple defined
volume names.
Explanation: The command shown was entered with a

volume name pattern that matches more than one
volume. The command can only process a single
volume.
ANR2352E

may not be deleted.
Explanation: A DELETE DEVCLASS command

specifies the class name DISK, which is a
system-defined device class and may not be deleted.
command.
User response: Reissue the command with a more

specific volume name.
ANR2353E
ANR2348E

valid for a volume assigned to a primary
storage pool.

option that is not valid for a volume in a primary
storage pool.
command.
Explanation: An UPDATE DEVCLASS command

specifies the class name DISK, which is a
system-defined device class and may not be changed.
command.
ANR2354E
User response: Reissue the command with valid

options for a volume in a primary storage pool.
ANR2349E

valid for a volume assigned to a copy
storage pool.

option that is not valid for a volume in a copy storage
pool.
command.
options for a volume in a copy storage pool.
ANR2350E

is already defined.
Explanation: The command indicated has attempted

to define a device class that already exists.
command.

may not be updated.

is still referenced by one or more
storage pools, or database backup, or
export volumes or backupset volumes.
Explanation: The DELETE DEVCLASS command has

attempted to delete a device class that has storage
pools assigned to it, or is referenced by database
backup, export volumes or backupset volumes.
command.
User response: Issue Q DEVCLASS to view the
storage pool reference count, Q STGPOOL to determine
which pool references the device class, and Q VOLHIST
to locate database backup or export volume or
backupset volume references.
ANR2355E
Command: Required parameter is

missing - missing parameter.

entered without the required parameter. The required
parameter is shown.
231
ANR2356E ANR2363E
proper syntax.
ANR2356E
Command: Incompatible parameters

specified - first parameter, second
parameter.

entered with mutually exclusive parameters. The two
parameters are listed.
proper syntax.
ANR2357E
Command: The DISK device class is not

supported for copy storage pools.
Explanation: An attempt is made to define a copy

storage pool using a device of DISK. Copy storage
pools can only be assigned to a sequential device class.
command.
sequential device class.
ANR2358E

is still referenced in the volume history
file.
ANR2360E

may not be used for database backup.
Explanation: The command specifies the DISK device

class, which cannot be used for database backup,
backup trigger, or restore operations.
command.
device class.
ANR2361E
Command: A full database backup is

required.
Explanation: A BACKUP DB command specified an

incremental backup, but a full backup is required.
command.
User response: Reissue the command specifying a full
backup.
ANR2362E
Command: Database backup is not

currently possible - compressed log
records exist in the current transaction
checkpoint.
Explanation: The DELETE DEVCLASS command has

attempted to delete a device class that is associate with
entries in the volume history file. These entries are for
volumes that contain database backup or export data.
Explanation: A BACKUP DB command was issued

but a database backup cannot be started. Log
compression has recently taken place, and the
compressed log records are still part of the current
transaction checkpoint. After these log records are no
longer part of the current checkpoint a backup can take
place.

command.

command.
User response: Use the DELETE VOLHIST command

to remove that entries before deleting the device class.

ANR2363E
ANR2359E
Command: Volume name volume name

must be specified with a DISK or FILE
STGPOOL.

name of a volume that must be specified with a storage
pool associated with a device class of type DISK or
FILE.
command.
volume name and storage pool.
232
Command: One of the following

parameter must be supplied but is
missing - missing parameter, missing
parameter, missing parameter, missing
parameter.

entered without one of the mutually exclusive required
parameters. One of the parameters from the list must
be specified.
proper syntax.
ANR2364E ANR2372E
ANR2364E
Command: Missing reclaim-storage pool

name.
Explanation: The command indicated requires a

storage pool name, but none has been entered.
command.
User response: Reissue the command with a storage
pool name.
ANR2365I
Backupset backup set name for node node

name (data type data type) has been
deleted.
Explanation: The backup set has been deleted.

System action: The server has deleted the backupset.
ANR2366I

name (data type data type) would have
been deleted.
Explanation: The backup set would have been deleted

as the result of a DELETE BACKUPSET command, but
the PREVIEW=YES parameter was specified.
ANR2369I
Database backup volume and recovery

plan file expiration starting under
process process ID.
Explanation: The server has started expiration

processing to remove expired database backup volumes
and recovery plan files created on a remote server. This
message is issued only if DRM is licensed on the
server. The DB backup volumes expired is based on the
value specified on the SET
DRMDBBACKUPEXPIREDAYS. The recovery plan files
expired is based on the value specified on the SET
DRMRPFEXPIREDAYS. Server inventory expiration
processing deletes the DB backup volumes and
recovery plan files only if the volumes or plan files are
created on the server to server virtual volumes.
expiration process is cancellable.
ANR2370E
Command: Database backup trigger is

already defined.
Explanation: The database backup trigger cannot be

defined because it is already defined.

command.
User response: If the backup set is to be deleted,

reissue the command without specifying
PREVIEW=YES.
User response: Use the UPDATE

DBBACKUPTRIGGER command to modify the
database backup trigger parameters.
ANR2367I
Retention period for backupset backup

set name for node node name (data type
data type) has been updated.
Explanation: The backup sets retention period has

been updated.
System action: The server has updated the
backupsets retention period.
ANR2371E

not defined.
Explanation: The database backup trigger cannot be

updated or deleted because it is not currently defined.
command.

ANR2372E
ANR2368I
Retention period for backupset backup

set name for node node name (data type
data type) would have been updated.
Explanation: The backup sets retention period would

have been updated as the result of an UPDATE
BACKUPSET command, but the PREVIEW=YES
parameter was specified.
Command: Database Space trigger is

already defined.
Explanation: The database space trigger cannot be

command.
User response: Use the UPDATE SPACETRIGGER
command to modify the indicated space trigger
parameters.
User response: If the backup set is to be updated,

reissue the command without specifying
PREVIEW=YES.
233
ANR2373E ANR2382E
ANR2373E

not defined.
Explanation: The database space trigger cannot be

command.
ANR2374E
Command: Recovery Log Space trigger is

already defined.
Explanation: The recovery log space trigger cannot be

command.
parameters.
ANR2375E
Command: Recovery Log trigger is not

defined.
Explanation: The recovery log space trigger cannot be

command.
ANR2378I
Recovery Log Space trigger updated, but

disabled.

has successfully completed for the recovery log space
trigger. However, the space expansion percentage is
currently set to 0, which disables the space trigger.
zero.
ANR2379I
Recovery Log Space trigger deleted.

trigger. Space expansions are no longer triggered
automatically for the recovery log.
ANR2380E

is not defined.

name of a nonexistent storage pool.

command.
ANR2376I

storage pool name.
Recovery Log Space trigger defined, but

is disabled.
Explanation: A recovery log space trigger has been

defined, but because the space expansion percentage is
currently set to 0, the space trigger is disabled.
ANR2381E

is already defined.
Explanation: A DEFINE STGPOOL command specifies

the name of a storage pool that already exists.


command.
ANR2377I
Recovery Log Space trigger updated and

enabled.

trigger. The updated parameters specified on the
expansion for the database.
234
ANR2382E

still contains at least one volume.
Explanation: A DELETE STGPOOL command specifies

a storage pool that has volumes assigned to it.
command.
User response: Delete the volume belonging to the
storage pool and reissue the command.
ANR2383E ANR2391E
ANR2383E

is currently in use by clients and/or data
management operations.

storage pool that is in use.
command.
ANR2384E
Command: Next or Reclaim storage pool

storage pool name introduces a cycle into
the storage pool chain.
Explanation: A DEFINE STGPOOL or UPDATE

STGPOOL command specifies a next storage pool that
eventually points to the pool being processed.
command.
next pool value.
ANR2385E

is in use as the next or reclaim pool for
one or more other storage pools.

command.
primary storage pool name.
ANR2388E

is not a copy or an active-data pool type
pool.

name of a storage pool which is not a copy pool or an
active-data pool. The command syntax requires that a
copy storage pool name or an active-data pool name be
specified.
command.
copy storage pool name or active-data pool name.
ANR2389E

valid for a primary storage pool.

option that is not valid for a primary storage pool.
command.

a pool that is the next pool or the reclaim pool for
other storage pools.

appropriate for a primary storage pool.

command.
ANR2390E
User response: If necessary, update other storage

pools so that they do not reference the pool to be
deleted, and reissue the command.
ANR2386E
Command: High migration threshold

must be set greater than or equal to the
low migration threshold.
Explanation: A DEFINE or UPDATE STGPOOL

command has attempted to set the storage pool low
migration threshold (LOWMIG) parameter greater than
the high migration threshold (HIGHMIG).
command.
User response: Reissue the command with a low
migration threshold less than or equal to the high
migration threshold.
ANR2387E

is not a primary pool.

name of a storage pool which is not a primary pool.
The command syntax requires that a primary storage
pool name be specified.

valid for a pool type storage pool.

option that is not valid for either a copy or active-data
type storage pool.
command.
appropriate for the specified storage pool type.
ANR2391E
Command: Server could not write device

configuration information to file name.
Explanation: The BACKUP DEVCONFIG command

does not successfully complete because the server
command.
User response: Make sure that the server has proper
authority to write to the file indicated and that
sufficient space is available in the file system for the
file. On MVS, make sure that the data set has been
allocated and that the server has authority to write to
the data set.
235
ANR2392E ANR2398E
ANR2392E
Command: An internal error was

encountered in writing device
configuration information to file name.

does not successfully complete because the server
would like to have device configuration information

recorded. If desired, you may configure files that
should be automatically updated with the
DEVCONFIG option and restart the server.
ANR2396E

command.
User response: Examine error messages on the server
console that may have been displayed prior to this
message and correct any problems, if possible. Make
sure that the server has proper authority to write to the
file indicated and that sufficient space is available in
the file system for the file. On MVS, make sure that the
data set has been allocated and that the server has
authority to write to the data set.
ANR2393I
Command: Server device configuration

information was written to file name.

the BACKUP DEVCONFIG command and indicates
that device configuration information was successfully
written to the file name indicated.
System action: The server records device
configuration information to the file name specified

does not complete successfully because the server
cannot write to one or more of the defined device
command.
ANR2397E

ANR2394I
Command: Server device configuration

information was written to all device

that device configuration information was successfully
written to all files that were specified in the server
options file.
System action: The server records device
configuration information to the device configuration
files.
Command: An I/O error was encountered

in writing device configuration
information to one or more of the
defined device configuration files.
Command: An internal server error was

encountered in writing device
configuration information to one or
more of the defined device

cannot write to one or more of the defined device
command.
message and correct any problems, if possible. Contact
your service representative if you are unable to resolve
the problem.

ANR2398E
ANR2395I
Command: Device configuration files

have NOT been defined for automatic
recording - specify a file name for
device configuration information.

that device configuration information cannot be written
because no files were specified in the options file.
System action: The device configuration information
is not written. Server operation continues.
User response: Reissue the BACKUP DEVCONFIG
command and specify the name of a file to which you
236
Command: The device configuration file

contains a statement with invalid
syntax.
Explanation: While processing the device

configuration information, an invalid statement has
been encountered.
System action: The server ends the operation being
performed.
message and correct any problems if you have
constructed the device configuration file manually.
Make sure the statements are in the proper order. If
you let the server construct the device configuration file
ANR2399E ANR2407E
automatically, restart the server, refresh the device
configuration file by issuing the BACKUP DEVCONFIG
command, and reissue the operation. If the problem
persists, contact your service representative.
ANR2399E

is not a sequential pool.

name of a storage pool which is not a sequential pool.
All storage pools are either fixed disk or sequential
archival. All tape devices, as well as optical and file
device classes, are sequential.
command.
sequential storage pool name.
ANR2400E
Command: Volume volume name is already

defined in a storage pool or has been
used previously to store export, database
dump, or database backup information.

ANR2403E
Command: Volume volume name is not

online.

name of a volume that is not online.
command.
ANR2404E

available.
Explanation: The command indicated has attempted

to access a volume that cannot be found.
command.
User response: Check the spelling of the volume name
to ensure it is correct. If the volume does not exist,
preallocate it with the appropriate mechanism for the
operating system on which the server is running.

name of a storage pool volume that already exists or
has been used to store server export, database dump,
or database backup information as recorded in the
server volume history file.
ANR2405E

command.

name of a data storage volume that is currently in use.
User response: Specify a volume that is not in use, is

not defined in a storage pool, and which has not been
previously used for an export, a database dump, or
volumes that have been used for export, a database

command.
ANR2401E

defined in a storage pool.
Command: Volume volume name is

currently in use by clients and/or data
management operations.
User response: Wait until the conflicting volume

activity has completed, and then reissue the command.
If the volume is currently mounted, but idle, you must
dismount it with the DISMOUNT VOLUME command
and then retry this operation.
ANR2406E
Command: Volume volume name still

contains data.
Explanation: The indicated command tries to delete a

data storage volume that contains data.

name of a storage pool volume that does not exist.

command.

command.
ANR2407E
ANR2402E

online.
Explanation: A VARY ONLINE command specifies the

name of a volume that is already online.
command.
Command: Maximum number of

mirrored copies exceeded.
Explanation: A DEFINE LOGCOPY or DEFINE

DBCOPY command has attempted to add a mirror
volume, but the maximum number of mirrors for the
target volume already exists.
command.
237
ANR2408E ANR2415E
ANR2408E
Command: Capacity of volume volume

name must be at least as large as
capacity of volume volume name.
Explanation: A DEFINE LOGCOPY or DEFINE

DBCOPY command has attempted to add a mirror
volume, but the size of the volume to be added is less
than the size of the target volume.
command.
User response: Use a larger mirror volume.
ANR2409E
Command: Capacity of volume volume

name must be at least 5 megabytes.
ANR2412E
Command: Audit operation already in

progress for volume volume name.
Explanation: The command specified a volume that is

currently in use by an audit volume operation.
System action: If the command is a MOVE
NODEDATA command the server will skip the volume
and continues moving node data on other volumes.
Other commands are not processed.
User response: Reissue the command after the audit
volume operation ends.
ANR2413E
Command: Audit operation already in

progress for associated volume volume
name.
Explanation: A define command for a database or log

volume or copy has specified a volume that is too
small to be used by the server for a database or log
volume. The minimum size for one of these volumes is
5 megabytes.
Explanation: The command shown would require

access to the volume whose name is displayed (because
data from the volume specified in the command spans
into this volume); the volume shown cannot be
accessed because it is in use by an audit volume
operation.

command.

command.

volume that is at least 5 megabytes in size.
User response: Reissue the command after the audit

ANR2410E
Command: Unable to access volume

volume name - access mode is set to
unavailable.

volume whose name is displayed, but the volume
cannot be accessed because its status is unavailable.
ANR2414E
Command: Deletion operation already in

progress for volume volume name.

currently 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

ANR2411E
Command: Unable to access associated

volume volume name - access mode is set
to unavailable.

accessed because its status is unavailable.
command.
238
ANR2415E
Command: Deletion operation already in

progress for associated volume volume
name.

accessed because it is in use by a delete volume
operation.
command.
User response: Reissue the command after the delete
ANR2416E ANR2424E
ANR2416E
Command: Move Data operation already

in progress for volume volume name.

currently in use by a move data operation.
User response: Reissue the command after the move
data process ends.
ANR2417E
Command: Move Data operation already

in progress for associated volume volume
name.

accessed because it is in use by a move data operation.
command.
User response: Reissue the command after the move
data operation ends.
ANR2418E
Command: Migration operation already

in progress for volume volume name.

currently in use by a migration operation.
User response: Reissue the command after the
migration ends.
ANR2420E
Explanation: The command specified a volume is

currently in use by a reclamation operation.
reclamation ends.
ANR2421E
Command: Migration operation already

in progress for associated volume volume
name.

accessed because it is in use by a migration operation.
command.
migration ends.
Command: Space reclamation operation

already in progress for associated
volume volume name.

accessed because it is in use by a reclamation operation.
command.
reclamation ends.
ANR2422E
Command: Volume volume name is not a

defined disk volume.
Explanation: The command shown specifies a volume

name that does not match any known disk volume.
command.
volume name.
ANR2423E
ANR2419E
Command: Space reclamation operation

already in progress for volume volume
name.
Command: Volume volume name is still

online.
Explanation: An UPDATE VOLUME command

specifies access=unavailable for a disk volume that is
still online.
command.
User response: Issue the VARY OFFLINE command,
and reissue the UPDATE VOLUME command.
ANR2424E

destroyed.

cannot be accessed because its status is destroyed.
239
ANR2425E ANR2434E
command.

ANR2430E
ANR2425E

offsite.

cannot be accessed because its status is offsite.
command.
ANR2426I
Backupset backup set name defined for

node node name (data type data type).
Explanation: The backup set has been defined for the

indicated node.
System action: The server has defined the backupset.
Explanation: A DEFINE DBVOLUME command

specifies the name of a database volume that already
exists.
command.
ANR2431E

name (data type data type) was not
deleted. Device class device class name
was not found.
Explanation: The specified backup set was not deleted

because the device class used to generate it was not
found.
System action: The backup set is not deleted.
User response: If the device class was inadvertently
deleted, redefine it, then delete the backup set again.
ANR2428E

name (data type data type) has not been
deleted due to error error code.
Explanation: The backup set has not been deleted.

System action: The server has not deleted the
backupset.
User response: Check related error messages.
ANR2429E
Command: Maximum database capacity

exceeded.
Explanation: Do not allocate any volume that would

cause the database to exceed 500GB. A subsequent
DEFINE DBVOLUME command for that volume would
fail.
command.
240

defined database volume.
Explanation: A DELETE DBVOLUME command

specifies the name of a database volume that does not
exist.
command.
ANR2432E

ANR2427E

defined as a database volume.
Command: Maximum number of

database volumes exceeded.
Explanation: A DEFINE DBVOLUME command has

attempted to add more database volumes than the
server can manage.
command.
ANR2433E
Command: A database define, delete,

extend, reduce, or backup operation is
already in progress.

while a command that is modifying or backing up the
database is already active.
command.
User response: Wait for other activity to end, and
ANR2434E
Command: Insufficient space on other

database volumes to delete volume
volume name.

been entered, but the data on the volume to be deleted
cannot be copied to other volumes due to insufficient
free space.
command.
ANR2435E ANR2444E
User response: Make more database space available,
and reissue the command.
ANR2435E
Command: Unable to delete database

volume volume name - mirrored copies
not synchronized.

been entered, but mirrors of the volume to be deleted
are not up to date.

command.
User response: Try the command at a later time (after
database volumes have been synchronized).
ANR2440E
Command: Unable to vary database

volume volume name offline - only copy.

command.
Explanation: A VARY OFFLINE command has been

entered, but the database volume has no mirrors and
therefore contains the only copy of the data on that
volume.

database volumes have been synchronized).

command.
ANR2436E
Command: Insufficient space to extend

database by requested amount.
Explanation: An EXTEND DB command has been

entered, but not enough allocated, unused space is
available to the database to add the amount of space
requested.
command.
User response: Make more database space available,
and reissue the command.
ANR2437E
Command: Output error encountered

while attempting to extend database.
Explanation: An EXTEND DB command has been

entered, but an I/O error occurs during the command.
command.
User response: Reissue the command. If the problem
persists, identify and remove or repair the volume that
caused the error.
ANR2441E
Explanation: A DEFINE LOGVOLUME command

specifies the name of a recovery log volume that
already exists.
command.
ANR2442E
Command: Insufficient database space

would be available following a
reduction by the requested amount.
Explanation: A REDUCE DB command has been

entered, but the database does not have enough free
space to reduce by the amount specified.

defined recovery log volume.
Explanation: A DELETE LOGVOLUME command

specifies the name of a recovery log volume that does
not exist.
command.
ANR2443E
ANR2438E

defined as a recovery log volume.
Command: Maximum number of recovery

log volumes exceeded.
Explanation: A DEFINE LOGVOLUME command

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

command.
ANR2444E
ANR2439E
Command: Unable to vary database

volume volume name offline - mirrored
copies not synchronized.

entered, but mirrors of the volume to be varied are not
up to date.
Command: A recovery log define, delete,

extend, or reduce operation is already in
progress.

while a command that is modifying the recovery log is
already active.
command.
241
ANR2445E ANR2453E
User response: Wait for other activity to end, and
ANR2445E
Command: Insufficient space on other

recovery log volumes to delete volume
volume name.

been entered, but the data on the volume to be deleted
cannot be copied to other volumes due to insufficient
free space.
command.
ANR2449E
Explanation: A REDUCE LOG command has been

entered, but the recovery log does not have enough free
space to reduce by the amount specified.
command.
ANR2450E
User response: Make more recovery log space

available, and reissue the command.
ANR2446E
Command: Unable to delete recovery log

volume volume name - mirrored copies
not synchronized.

are not up to date.
command.
recovery log volumes have been synchronized).
ANR2447E
Command: Insufficient space to extend

recovery log by requested amount.
Explanation: An EXTEND LOG command has been

entered, but there is not enough allocated, unused
space available to the recovery log to add the amount
of space requested.
command.
User response: Make more recovery log space
available, and reissue the command.
ANR2448E
Command: Output error encountered

while attempting to extend recovery log.
Command: Insufficient recovery log space

would be available following a
reduction by the requested amount.
Command: Unable to vary recovery log

volume volume name offline - mirrored
copies not synchronized.

are not up to date.
command.
recovery log volumes have been synchronized).
ANR2451E
Command: Unable to vary recovery log

volume volume name offline - only copy.

entered, but the recovery log volume has no mirrors
and contains the only copy of the data on that volume.
command.
ANR2452E
Command: Maximum recovery log

capacity exceeded.
Explanation: Do not allocate any volume that would

cause the recovery log to exceed 13GB. A subsequent
DEFINE LOGVOLUME command for that volume
would fail.
command.
Explanation: An EXTEND LOG command has been

entered, but an I/O error occurs during the command.

command.
ANR2453E
User response: Reissue the command. If the problem

persists, identify and remove or repair the volume that
caused the error.
Explanation: A REDUCE LOG command has been

entered, but the recovery log mode of the server is
currently set to ROLLFORWARD. The recovery log can
only be reduced when the log mode is set to NORMAL
with a SET LOGMODE command.
Command: Unable to reduce recovery log

- log mode must be set to NORMAL.

command.
User response: Set the log mode to NORMAL with
242
ANR2454E ANR2460E
the SET LOGMODE command, reissue the REDUCE
LOG command, and set the log mode back to
ROLLFORWARD with the SET LOGMODE command.
If you change the log mode to NORMAL, you can only
recover your database to the time of the last complete
database backup.
ANR2454E
Command: Unable to reduce database LOGMODE must be set to NORMAL.
Explanation: A REDUCE DB command has been

entered, but the recovery log mode of the server is
currently set to ROLLFORWARD. The database can
only be reduced when log mode is set to NORMAL
with the SET LOGMODE command.
command.
User response: Set the log mode to NORMAL with
the SET LOGMODE command, reissue the REDUCE
DB command, and reset the log mode to
ROLLFORWARD with the SET LOGMODE command.
If you change the log mode to NORMAL, you can only
recover your database to the time of the last complete
database backup.
ANR2455E

to destroyed.
Explanation: The specified command would require

accessed because its status is destroyed.
command.
ANR2456E

to offsite.

accessed because its status is offsite.
command.
ANR2457E
Command: Backup of primary storage

pool primary pool name to copy storage
pool copy pool name already in progress.
Explanation: The command shown specifies a backup

operation that is already in progress.
command.
User response: Reissue the command after the current
backup operation ends.
ANR2458E
Command: Restore of primary storage

pool primary pool name (or volumes in
that storage pool) already in progress.
Explanation: The command shown cannot be

processed because a restore operation involving the
indicated storage pool is already in progress. Either a
RESTORE STGPOOL command is in progress for the
indicated storage pool or a RESTORE VOLUME
command is in progress for volumes that belong to the
indicated storage pool.
command.
User response: Reissue the command after the current
restore operation ends.
ANR2459E
Command: Volume volume name cannot be

updated - a restore operation involving
that volume is in progress.
Explanation: The indicated volume has an access

mode of destroyed. Either a RESTORE STGPOOL
command or a RESTORE VOLUME command is in
progress to restore the contents of the indicated
volume.
command.
User response: If necessary, cancel the restore
processing and update the volume.
ANR2460E
Command: Server could not write

sequential volume history information
to File name.
Explanation: The BACKUP VOLHISTORY command

command.
User response: Make sure that the server has proper
authority to write to the file indicated and that
sufficient space is available in the file system for the
file. On MVS, make sure that the data set has been
allocated and that the server has authority to write to
the data set.
243
ANR2461E ANR2467I
ANR2461E
Command: An internal error was

encountered in writing sequential
volume history information to file name.

command and specify the name of a file for recording

sequential volume history information. If desired, you
may configure files that should be automatically
updated with the VOLUMEHISTORY parameter and
restart the server.
ANR2465E

command.
ANR2462I
Command: Server sequential volume

history information was written to file
name.

the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
successfully written to the file name indicated.
System action: The server records sequential volume
history information to the file name specified.

cannot write to one or more of the defined volume
history files.
command.
ANR2466E

ANR2463I
Command: Server sequential volume

history information was written to all
configured history files.

the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
successfully written to all files that were specified in
the server options file.
history information to the configured files.
ANR2464I
Command: Volume history files have

NOT been defined for automatic history
recording - specify a file name for
recording history information.

the BACKUP VOLHISTORY. It indicates that sequential
volume history information cannot automatically be
written because no files were defined in the server
options file for recording this information.
System action: The sequential volume history
information is not written. Server operation continues.
User response: Reissue the BACKUP VOLHISTORY
244
Command: An I/O error was encountered

in writing sequential volume history
information to one or more of the
defined volume history files.

encountered in writing sequential
volume history information to one or
more of the defined volume history
files.

cannot write to one or more of the defined volume
history files.
command.
message and correct any problems, if possible. Contact
your service representative if you are unable to resolve
the problem.
ANR2467I
Command: number of entries deleted

sequential volume history entries were
successfully deleted.
Explanation: The DELETE VOLHISTORY command

successfully deleted the number of entries specified.
ANR2468E ANR2476I
ANR2468E

encountered while deleting server
sequential volume history information.
Explanation: The DELETE VOLHISTORY command

fails because an internal server error has been
encountered.
System action: The DELETE VOLHISTORY command
fails, and server operation continues.
User response: Examine the messages in the activity
log or server console that were displayed prior to the
error to see if the error can be resolved. Contact your
service representative if this error cannot be resolved.
ANR2469E
Command: Invalid volume history type:

history type.
Explanation: The command failed because an invalid

sequential volume history type was specified for the
TYPE= parameter.
System action: The command fails, and server
User response: Refer to the Administrators Reference
for an explanation of the valid types for this command.
Reissue the command and specify a valid type value.
ANR2470I
Message output being re-directed to file

file name.
Explanation: The message output is being redirected

to the specified file instead of being displayed at the
console.
ANR2471E
Message output re-direction to file file

name failed - unable to open file.
Explanation: An error occurs while trying to open the

file. The message output will not be redirected to the
specified file.
User response: Determine the cause of the file open
failure and take corrective action.
ANR2473I
Command for volume volume name

completed.
Explanation: The command completed and the

volume history file has been updated.
history information.
ANR2474E
Command: Input volume names must be

specified with the VOLumenames=
parameter.
Explanation: The command failed because input

volume names were not specified with the
VOLumenames parameter.
User response: On some platforms, or with certain
device classes, the server cannot prompt to mount
input removable media volumes, so the names of the
required volumes must be specified in the command.
Reissue the command specifying the name(s) of
volumes that should be mounted for input.
ANR2475E
Command: File file name could not be

opened.
Explanation: The DSMSERV command could not be

completed successfully because the file specified (to
contain the list of volumes to be used) cannot be
opened.
System action: The DSMSERV command fails.
User response: Examine the file name that was
specified in the DSMSERV command. Correct the
specification, if necessary, so that it specifies the name
of a file that exists and is accessible by the server
program. Reissue the DSMSERV command if this can
be corrected. Contact your service representative if this
error cannot be resolved.
ANR2476I
License storage auditing is disabled, no

output available.
Explanation: The license storage occupancy function is

currently disabled.
ANR2472E
Command: Invalid volume specified:

volume name.

sequential history volume specified is not a DB DUMP,
DB BACKUP, or EXPORT volume.
User response: To obtain storage occupancy results,

remove the NOAUDITSTORAGE or AUDITSTORAGE
NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command.

valid volume name.
245
ANR2477I ANR2486E
ANR2477I
License storage auditing is disabled,

storage values may be outdated and
should be ignored.
Explanation: The license storage occupancy function is

currently disabled.
User response: To obtain storage occupancy results,
remove the NOAUDITSTORAGE or AUDITSTORAGE
NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command.
ANR2478E
Command: Command cannot be executed

in this session.
Explanation: The command indicated is not supported

by the session in which it was invoked. For example, a
DEFINE CURSOR command can not be invoked from
the servers primary console.
command.
User response: The command must be issued from a
standard administrator session.
ANR2479E
Command: Invalid SQL cursor name SQL cursor name.

invalid SQL cursor name.
command.
SQL cursor name.
ANR2480E
Command: SQL cursor name SQL cursor

name is already defined.
Explanation: The command indicated specifies an SQL

cursor name that has already been defined.
command.
different cursor name.
ANR2481E
Command: SQL cursor name SQL cursor

Explanation: The command indicated specifies an SQL

cursor name that has not been defined.
command.
User response: Use the DEFINE CURSOR command
to first define the cursor.
246
ANR2482E
Command: SQL cursor SQL cursor name is

already open.
Explanation: The command indicated failed because

an SQL cursor is already open.
command.
User response: Use the CLOSE CURSOR command to
first close the current cursor.
ANR2483E
Command: No SQL cursor is currently

open.

no SQL cursor is currently open.
command.
User response: Use the OPEN CURSOR command to
first open a cursor.
ANR2484E
Command: Invalid SQL date-time display

format - SQL date-time display format
name.

invalid SQL date-time display format name.
command.
SQL date-time format name.
ANR2485E
Command: Invalid SQL display format SQL display format name.

invalid SQL display format name.
command.
SQL display format name.
ANR2486E
Command: Invalid SQL character

arithmetic mode - SQL arithmetic mode.

invalid SQL arithmetic mode name.
command.
SQL arithmetic mode name.
ANR2487E ANR2503I
ANR2487E
Command: An SQL expression is

required.
Explanation: The command indicated requires that an

SQL expression be provided through the SQL keyword
parameter.
command.
User response: Reissue the command specifying an
SQL expression.
ANR2491I
Volume Creation Process starting for

volume name, Process Id process ID.
Explanation: As a result of a DEFINE VOLUME,

DEFINE DBVOLUME, or DEFINE LOGVOLUME
command with the SIZE=xxx parameter, a new volume
is being created. The process whose ID is displayed has
begun to create the volume shown.
System action: The server creates the volume and
adds it to the server.
ANR2488W
List file list file name could not be

opened.
Explanation: While attempting to read or write a

sequential file list, the server was unable to open the
file name specified.
System action: The server does not use the list file.
problems, if possible. For OUTFILE files, make sure
that the server has proper authority to write to the file
indicated and that there is sufficient space in the file
system for the file. On OS/390 and z/OS, make sure
that the server has authority to write to the data set.
ANR2489W
An error was encountered writing to

volume list file volume list file name.
Explanation: While attempting to write to the

sequential file for a volume list an error occurs on the
file name specified. The volume list is not be complete
and should not be used for input.
System action: The server stops writing to the file.
On MVS, make sure that the server has authority to
write to the data set. Obtain the volume list from
console messages, the QUERY VOLHISTORY command
or the volume history file, if it is used.
ANR2490E
Command: NODENAMES and

SERVERNAMES parameters cannot
both be specified in the same command.

both the nodenames parameter and the servernames
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
parameter specified.
ANR2500I
Schedule schedule name defined in policy

domain domain name.

the DEFINE SCHEDULE command. The schedule
named schedule name has been defined in the policy
domain named domain name in the server database.
ANR2501I
Schedule schedule name deleted from


the DELETE SCHEDULE command. The schedule
named schedule name has been deleted from the policy
ANR2502I
Schedule schedule name updated in


the UPDATE SCHEDULE command. The schedule
named schedule name has been updated in the policy
ANR2503I
Schedule schedule name in domain domain

name copied to schedule new schedule
name in domain new domain name.

the COPY SCHEDULE command. The schedule named
schedule name in policy domain domain name has been
copied to the schedule named new schedule name in the
policy domain named new domain name. Node
associations have not been copied.
247
ANR2504I ANR2512I
ANR2504I
Schedule schedule name deleted.

the DELETE SCHEDULE command. The schedule
named schedule name has been deleted from the server
database.
ANR2505I
number of schedules schedules were

defined for command.
Explanation: number of schedules were generated and

nodes successfully associated for the command issued.
User response: If the number is less than expected,
check the nodeList and domainList combination specified
to the DEFINE CLIENTACTION command. Schedules
are generated when at least one node in the nodeList
exists in a domain in the domainList.
ANR2508E
Explanation: Trace Tsmtrcfm doesnt output to console

System action: Trace wont start without a tracefile
name for Trace Tsmtrcfm
User response: Issue the command with a tracefile
name.
ANR2509E
Node node name associated with

schedule schedule name in policy domain
domain name processed. rc=return code.

the DEFINE CLIENTACTION WAIT=YES command.
Node node name is associated with the schedule named
schedule name in policy domain domain name has been
processed. name The result is indicated in the return
code return code.
User response: If the return code is non-zero, issue the
QUERY ACTLOG command to to view the activity log
and search for the error messages. After the error has
been resolved, restart the scheduled operations.
ANR2507I
Schedule schedule name for domain

domain name started at start timestamp for
node node name completed successfully
at timestamp.
Command: Invalid Virtual file space

name - vfs name.

entered with a virtual file space name that is longer
than allowed.
command.
virtual file space name.
ANR2510I
ANR2506I
Trace Tsmtrcfm failed: A tracefile name

is required.
Node node name associated with

domain name.

the DEFINE ASSOCIATION command. Node node name
is associated with the schedule named schedule name in
policy domain domain name. Schedule schedule name is
now applied to node node name.
ANR2511I
Node node name disassociated from

domain name.

the DELETE ASSOCIATION command. Node node name
is no longer associated with the schedule named
Explanation: The scheduled operation for the domain

name and schedule name specified was processed. It was
processed for node node name and completed
successfully at the indicated time.

the DELETE EVENT command. A total of record count
event records have been deleted from the database.
User response: This message is intended to report the

completion state of a scheduled client action. This
message indicates that the scheduled action completed
successfully.
248
ANR2512I
Event records deleted: record count.

ANR2513I ANR2522I
ANR2513I
Schedule schedule name copied to

schedule new schedule name.

the COPY SCHEDULE command. The schedule named
schedule name has been copied to the schedule named
new schedule name.
ANR2514E
Command: Virtual file space name vfs

name conflicts with file space on the
network attached storage (NAS) device.

entered with a virtual file space that has the same
name as a File space on the NAS device.
space name that has not already been defined for this
node.
ANR2518E

with a node, file space and path for which there is
already a virtual file space mapping defined.
User response: Issue the command using a file space
and path that does not already have a mapping
defined.
ANR2519E

command.
User response: Ensure that no virtual file space
mappings for this NAS device have the same name as
an actual file space that exists on the NAS device.
ANR2515I
Command: A virtual file space mapping

named vfs name for node node name has
been defined.

VIRTUALFSMAPPING command, a virtual file space
mapping for the specified node has been defined in the
server database.
ANR2516E
Command: The specified file space, fs

name, does not exist on the NAS device
associated with the node node name.

entered with a file space that does not exist on the
associate NAS device.
User response: Reissue the command with a valid file
space name from the NAS device.
ANR2517E
Command: The virtual file space vfs name

is already defined for node node name.

with a virtual file space name that has already been
defined for the indicated node.
User response: Issue the command using a virtual file

already exists to the specified node, file
space and path.
Command: The file space, fs name, does

not exist on the NAS device associated
with the node node name.
Explanation: During a Backup of a virtual file space

mapping for a NAS device, the server detected that the
file space upon which the virtual file space resides does
not exist on the associated NAS device.
User response: Use QUERY VIRTUALFSMAPPING to
verify that the virtual file space mapping is defined
correctly.
ANR2520I
Scheduled sessions set to percent

percent.

the SET MAXSCHEDSESSIONS command. It indicates
the percentage of total server sessions that can be used
for the processing of scheduled work.
ANR2521I
Event record retention period set to days

days.

the SET EVENTRETENTION command. It indicates the
number of days for which event records are retained in
the database.
ANR2522I
Randomization set to percent percent.

the SET RANDOMIZE command. It indicates the
percentage of the startup window over which the start
times for individual clients are distributed.
249
ANR2523I ANR2533I
ANR2523I
Schedule query period set to hours

hour(s).

the SET QUERYSCHEDPERIOD command. It indicates
the number of hours between attempts by the client to
contact the server for scheduled commands.

ANR2529I
Scheduling mode set to POLLING.

the SET SCHEDMODES command. With client-polling
scheduling, a client queries the server at prescribed
time intervals to obtain scheduled work or to ensure
that the schedules the client is waiting to process have
not changed.
ANR2524I
Schedule query period reset to value

determined by each client.

the SET QUERYSCHEDPERIOD command.
ANR2530I
Scheduling mode set to PROMPTED.

the SET SCHEDMODES command. With
server-prompted scheduling, the server contacts the
client when scheduled work needs to be performed and
a session is available.
ANR2525I
Maximum number of command retries

set to retries.

the SET MAXCMDRETRIES command. It indicates the
maximum number of times the client scheduler retries
a command after a failed attempt to process a
scheduled command.

ANR2531I
Scheduling mode set to ANY.

the SET SCHEDMODES command. The server now
allows clients to run in either the client-polling or the
server-prompted scheduling mode.
ANR2526I
Maximum number of command retries

reset to value determined by each client.

the SET MAXCMDRETRIES command.
ANR2527I
Retry period set to minutes minutes.

the SET RETRYPERIOD command. It indicates the
number of minutes between attempts by the client
scheduler to retry, after a failed attempt, to contact the
server or to process a scheduled command.
ANR2532I
Schedule schedule name updated.

the UPDATE SCHEDULE command. The schedule
named schedule name has been updated in the server
database.
ANR2533I
Client action schedule duration set to

days days.

the Set CLIENTACTDuration command. It indicates the
number of days for which schedules and associations
generated by the DEFine CLIENTAction are retained in
the database.
ANR2528I
Retry period reset to value determined

by each client.

the SET RETRYPERIOD command.
250
ANR2534I ANR2542E
ANR2534I
Client action schedule schedule name was

not executed by node name in domain
name.
Explanation: Immediate client action schedule name

was not executed by node node name, which is in
domain domain name. The schedule is being deleted.
ANR2535E
Command: The node node name cannot be

removed or renamed because it has an
associated data mover.
ANR2539E
Explanation: The data format of the indicated storage

pool is not valid for the requested operation. The
storage pool must have NATIVE or NONBLOCK data
format. The server is unable to perform the requested
operation.
User response: Choose a different storage pool with
the appropriate data format and reissue the command.
ANR2540E
Explanation: You attempted to remove or rename a

node that has an associated data mover.
System action: The server does not remove or rename
the node.
User response: To remove or rename the node, delete
the associated data mover and reissue the command.
ANR2536E

valid with the storage pools data
format.
Explanation: The command indicated includes an

option that is not valid with the specified (or defaulted)
data format for the storage pool.
command.
appropriate for the desired data format of the storage
pool.
ANR2537E

has a device type that is not allowed for
this operation.
Explanation: The device class in the indicated

command has a device type that is not allowed for this
operation.
command.
User response: Choose a different device class and
ANR2538E
Command: Backup set cannot be

generated for NAS node node name.
Explanation: Backup sets cannot be generated for

NAS nodes.
Command: Storage pool Storage Pool Name

does not have a valid data format.
Command: The option device class is not

valid with the storage pools data
format.
Explanation: The command indicated specifies a

device class that is not valid with the specified (or
defaulted) data format for the storage pool.
command.
User response: Reissue the command with a data class
appropriate for the desired data format of the storage
pool.
ANR2541E
Command: The storage pool specified

with option option is not compatible
with the options intended use.
Explanation: The command specifies a storage pool

whose device class is a Centera device. Such storage
pools are not available for use with data movement
operations such as reclaim or attributes such as copy,
active-data, or reclaim storage pools.
command.
User response: Issue the command again with a
storage pool appropriate for the desired function.
ANR2542E
Command: The storage pool is not

compatible with the operations
intended use.
Explanation: The command specifies a storage pool

whose device class is a Centera device. Such storage
pools are not available for use with data movement
operations, such as reclaim, or attributes, such as copy
or reclaim storage pools.
command.
storage pool appropriate for the desired function.
251
ANR2543E ANR2551I
ANR2543E
Command: The volume name is not

compatible with the operations
intended use.
Explanation: The command specifies a volume that

resides in a storage pool whose device class is a
Centera device. Such volumes are not available for use
with data movement operations, such as reclaim, or
attributes, such as copy or reclaim storage pools.
command.
volume appropriate for the desired function.
ANR2544E
Unable to open the centera device at hla

hla.
Explanation: The server cannot start communication

with the device at the specified HLA.
System action: The transaction needing this device
fails.
User response: Verify that the hla specified in the
device class is correct, verify that the centera device is
operational.
ANR2548I
Explanation: The NAS Backup process detected a

name conflict between the Virtual file space filespace
name and a file space on the NAS device associated
with the node node name. The Virtual file space is
renamed to the new filespace name. During a NAS
backup process, if the object to be backed up is a
Virtual file space, TSM will verify that this name does
not also exist as a file space on the NAS device. If a
name conflict exists, TSM will rename the existing
Virtual file space and the associated file space
definition, if one exists.
System action: NAS Backup processing for the
command continues.
User response: None; however, users should make
note of the original Virtual file space filespace name and
the new new filespace name so that they know where the
backup data for this Virtual file space is located. Note,
the RENAME FILESPACE command may be used to
rename the Virtual file space to a more appropriate
name.
ANR2549E
ANR2545E
The version of the centera library,

version, is not compatible with the
server.
Explanation: The centera library must be at least

version 2 to be able to be compatible with the server.
System action: The transaction fails.
NAS command: Renaming file space

filespace name for node node name to file
space new filespace name.
Command: Invalid virtual file space

name. A virtual file space mapping
name must have a forward slash as the
first character.

entered with a virtual file space name that is does not
have a forward slash as the first character.

command.
ANR2546E

virtual file space name.
The centera device is not capable of

performing the required operation,
version.
Explanation: The centera device must be capable of

reading, writing and deleting objects. The device is not
capable of performing at least one of these operations.
System action: The transaction fails.
ANR2547E
A Centera device (devclass) reported error

message,error during command Centera
command.
Explanation: The Centera device reported an error

while performing the specified command.
User response: Verify that the IP addresses specified
in the device class associated with the storage pool are
correct. Contact your service representative if the
problem persists.
252
ANR2550W
command name: Administrative schedule

schedule name does not have valid
activation information.
Explanation: This message is displayed during a

database audit and indicates that the ACTIVE=YES or
NO information is not recorded correctly for an
administrative schedule in the server database.
System action: Server database audit operation
continues.
User response: Execute the AUDITDB operation
specifying FIX=YES so that the activation information
can be corrected.
ANR2551I
command name: Administrative schedule

schedule name does not have valid
activation information - activation
information will be deleted.
ANR2552I ANR2558W
database audit and indicates that the ACTIVE=YES or
NO information is not recorded correctly for an
administrative schedule in the server database. The
audit operation corrects this discrepancy by removing
the invalid activation information.
continues.
User response: The named administrative schedule
will now appear to be inactive in the server database
(as if ACTIVE=NO was specified). If you want this
schedule to be active, execute the UPDATE SCHEDULE
command with the ACTIVE=YES parameter to activate
the schedule when the server is restarted.
ANR2552I
Server now enabled for session type

access.
Explanation: The server has been made available for

use by the specified session types with the ENABLE
command.
ANR2556W
Explanation: The managed server server name is

subscribed to domain domain name that contains client
schedule schedule name that uses enhanced style syntax.
The managed server is not capable of using an
enhanced style schedule. Only TSM servers that are at
least Version 5 Release 3 are capable of using enhanced
style schedules.
domain will not be propogated to the managed server.
User response: Consider upgrading the managed
server to at least TSM Version 5 Release 3.
ANR2557W

ANR2553I
Server now disabled for session type

access.
Explanation: The server has been made unavailable

for use by the specified session types with the
DISABLE command.
ANR2554I
Format lfvolume process process id ended

for storage pool pool name, number of
volumes requested volumes requested,
number of volumes formatted volumes
formatted.
Explanation: The FORMAT LFVOLUME process for

the storage pool shown has ended. The number of
volumes requested to be formatted, and the number of
volumes actually formatted are displayed.
User response: If the number of volumes formatted is
less than the number of volumes requested to be
formatted, check the activity log for messages
indicating the reason for the difference. Possible
reasons include the process was canceled, no more
scratch volumes are allowed in the storage pool, or an
error occurred processing a scratch volume.
The managed server server name is not

capable of using enhanced style client
name. The domain will not be
propogated to this server.
The managed server server name is not

capable of using the enhanced style
administrative schedule schedule name.
The administrative schedule will not be
propogated to this server.
Explanation: The managed server server name is

subscribed to an administrative schedule that uses
enhanced style syntax. The managed server is not
capable of using an enhanced style schedule. Only TSM
servers that are at least Version 5 Release 3 are capable
of using enhanced style schedules.
administrative schedule will not be propogated to the
managed server.
User response: Consider upgrading the managed
server to at least TSM Version 5 Release 3.
ANR2558W
command: One or more managed servers

that subscribe to domain domain name
which contains client schedule schedule
name are not capable of using an
enhanced style schedule.
Explanation: The client schedule schedule name uses

enhanced style schedule syntax. The schedule is in a
domain which is a managed object and one or more of
the managed servers that subscribe to it are not capable
of using an enhanced style schedule. Only TSM servers
that are at least Version 5 Release 3 are capable of using
enhanced style schedules. During configuration refresh
processing, the domain will not be propogated to
managed servers that are not capable of using it.
User response: Consider upgrading managed servers
to at least TSM Version 5 Release 3.
253
ANR2559W ANR2568E
ANR2559W
command: One or more managed servers

that subscribe to administrative
schedule schedule name are not capable of
using an enhanced style schedule.
Explanation: The administrative schedule schedule

name uses enhanced style schedule syntax. The
schedule is a managed object and one or more of the
managed servers that subscribe to it are not capable of
using an enhanced style schedule. Only TSM servers
that are at least Version 5 Release 3 are capable of using
enhanced style schedules. During configuration refresh
processing, The schedule will not be propogated to
managed servers that are not capable of using it.
ANR2564I
Automatic event record deletion ended record count records deleted.
Explanation: The event deletion process has ended. A

total of record count event records have been deleted
from the database.
ANR2565I
schedules schedules for immediate client

actions have been deleted.
Explanation: A total of schedules that were generated

by the DEFINE CLIENTACTION command have
expired and been deleted from the database.
User response: Consider upgrading managed servers

to at least TSM Version 5 Release 3.

ANR2560I
Schedule manager started.
Explanation: The schedule manager is started when

the server is initialized. The schedule manager
maintains entries of scheduled operations.
ANR2561I
Schedule prompter contacting node name

(session session number) to start a
scheduled operation.
Explanation: The schedule prompter contacts the

client scheduler for node node name because a
scheduled operation should be started for that node.
ANR2562I
Automatic event record deletion started.
Explanation: A process has been started to delete

event records for which the retention period has
elapsed.
ANR2563I
Removing event records dated prior to

date time.
Explanation: Events that were scheduled to start prior

to date time are automatically deleted unless their
startup window has not yet elapsed.
ANR2566E
An error occurred while deleting

immediate client action schedules.
Explanation: Processing did not complete for deleting

schedules that were generated by the DEFINE
CLIENTACTION command.
User response: Check the activity log for other
messages that might relate to this failure. Correct any
memory or space problems.
ANR2567W
Schedule prompter skipped contact

attempt with node name to start a
scheduled operation.
Explanation: The schedule prompter skipped the

contact attempt with the client scheduler for node node
name because the start-up window has passed for that
node, or the node was locked.
User response: Check the length of the schedule
start-up window to see if it needs to be increased.
Check the activity log for ANR2716E messages. These
messages are associated with failures to contact a client
scheduler. If there are an excessive number of these
messages the schedule window could have elapsed
waiting for TCP/IP timeouts from these failed
attempts. Also, check to see if the client node is locked.
The contact attempt would be skipped for a locked
node.
ANR2568E
Request for node node to start schedule

schedule at startTime is denied. Current
time is now.
Explanation: The client scheduler attempted to start

the specified instance of a schedule for a node. The
254
ANR2569E ANR2574W
request was denied because that instance is still in the
future.
System action: Server operation continues. The node
does not start the schedule.
User response: Check the client schedule and error
logs for problems with the network or the preschedule
command. Also, you may need to upgrade the client.
ANR2569E
Request by node node to report results

(result, code code) for schedule schedule at
startTime is denied. Current time is now.
Explanation: The client scheduler attempted to report

the results of executing the specified schedule.
However, the schedule occurs in the future. The results
will not be saved.
System action: Server operation continues. The results
will not be saved.
User response: Check the client schedule and error
logs for problems with the network or the preschedule
command. Also, you may need to upgrade the client.
ANR2570W
A scheduled session has been denied.

The schedule manager is not active.
Explanation: The client scheduler attempts to connect

with the server, but it is denied a session because the
schedule manager is not active.
System action: Server operation continues, but central
scheduling is not operational.
User response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
been specified in the server options file. If so,
scheduling can be enabled by updating the server
options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied
in the server options file, determine the source of the
error by examining the QUERY ACTLOG command to
view the activity log and search for messages. After the
error has been resolved, restart the server to restore
central scheduler operations. If the error cannot be
representative.
been specified in the server options file. If so,

scheduling can be enabled by updating the server
options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied
in the server options file, change the total number of
sessions by altering the MAXSESSIONS parameter in
the server options file and then restarting the server.
The percentage of sessions that are available for
scheduled operations can be increased by using the SET
MAXSCHEDSESSIONS command.
ANR2572W
Explanation: The server attempts to prompt the client

scheduler for node node name, but all sessions that have
been allocated for scheduled operations are already in
use.
System action: The server continues to attempt
contact with the client scheduler until the startup
window for the scheduled event has elapsed.
User response: To change the total number of
sessions, alter the MAXSESSIONS parameter in the
server options file and then restart the server. The
percentage of sessions that are available for scheduled
operations can be increased by using the SET
MAXSCHEDSESSIONS command.
ANR2573W
Scheduled session from node node name

(platform name) has been denied,
scheduled sessions are not currently
available.
Explanation: The client scheduler for node node name

attempts to connect with the server, but is denied a
session. All sessions that have been allocated for
scheduled operations are already in use.
User response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
Sufficient memory is not available for

the central scheduler - will retry in
Explanation: The server suspends central scheduler

processing because sufficient server memory is not
available.
scheduler operation will be retried after the specified
delay.
ANR2574W
ANR2571W
Schedule prompter session to node node

name has been denied, scheduled
sessions are not currently available.
Insufficient recovery log space available

for the central scheduler - will retry in

processing because sufficient recovery log space is not
available.
delay.
command, and can extend the size of the log by using
255
ANR2575W ANR2582E
ANR2575W
Insufficient database space available for

the central scheduler - will retry in

processing because sufficient database space is not
available.
delay.
DEFINE DBVOLUME command, and can extend the
size of the database by using the EXTEND DB
command.
ANR2576W
An attempt was made to update an

event record for a scheduled operation
which has already been executed multiple client schedulers may be active
for node node name.
Explanation: The server has attempted to update an

event record for a scheduled operation for the specified
client node. However, the existing event record shows
that this scheduled operation has already been
executed, either successfully or unsuccessfully. Two or
more client schedulers may be running for this node.
existing event record is not modified. No further
processing is performed for this scheduled operation.
User response: Contact the user for this client node,
and make sure that only one client scheduler is
running.
ANR2577I
Schedule schedule name defined.

the DEFINE SCHEDULE command. The schedule
named schedule name in the server database.
node node name has been initiated from the client to the
server. Refer to Administrators Guide and Administrators
Reference for more information on setting up scheduling
operations.
ANR2579E

name for node node name failed (return
code return code).
Explanation: This message is displayed when a client

reports failure in executing a scheduled action. The
return code reported by the client is displayed.
User response: Examine the nodes schedule log to
determine the cause for the failure.
ANR2580E

name for node node name failed.

server finds that a scheduled start window has elapsed
for a client schedule and the client is not currently
running the schedule.
User response: Examine the nodes schedule log to
determine the cause for the failure. Ensure that the
client scheduler is started.
ANR2581W
Schedule schedule name of an

administrative command has missed its
scheduled start up window.

scheduled startup window for this schedule has passed
and the schedule has not begun.
scheduled operation is not processed by the server.
User response: Ensure that the duration and period
specified in the schedule are long enough to allow the
schedule to start. Refer to Administrators Guide and
Administrators Reference for more information on setting
up scheduling operations.

ANR2578W

name for node node name has missed its
scheduled start up window.

scheduled startup window for this schedule has passed
and the schedule has not begun.
scheduled operation is not processed by the server.
User response: Ensure that a scheduled session for
256
ANR2582E
Command: Specified device class cannot

be used with storage pools with
different reclamation types.
Explanation: Storage pools can be defined with

RECLAMATIONTYPE=THRESHOLD or
RECLAMATIONTYPE=SNAPLOCK. A device class can
only be used with either
RECLAMATIONTYPE=SNAPLOCK storage pools. An
attempt was made to define a storage pool with one
type of reclamation type with a device class that is
already associated with another storage pool of the
other reclamation type.
ANR2583E ANR2588E
ANR2586W

another device class that is referenced by storage pools
with the same reclamation type as your new storage
pool. You may need to define another device class.
ANR2583E

is not a LAN-free storage pool.

name of a storage pool which is not a LAN-free pool.
The command syntax requires that a LAN-free storage
poolname be specified.
This command will set the server name

to serverName. Changing the server name
could adversely affect: communication
from the server to backup archive
nodes, event logging, virtual volumes,
library sharing, and storage agents used
for LAN-free and server-to-server
operations such as enterprise
configuration. See the administrators
guide for more information on these
areas and the impact of changing the
server name.
Explanation: A REGISTER NODE or REGISTER

ADMIN command has been entered that specifies a list
of email addresses, and one of those addresses is too
long. The maximum valid length for a single email
address is shown in the command.
Explanation: The name that the server displays and

communicates with has been set to the value indicated
with the SET SERVERNAME command.
Communication with the Tivoli Storage Manager server
is based on the name assigned to the server. If this is a
source server for a virtual volume operation, changing
this value can impact the ability of the source server to
access and manage the data it has stored on the
corresponding target server. Windows clients use the
server name to identify which passwords belong to
which servers. Changing the server name after the
clients are connected forces the clients to re-enter the
passwords. On a network where clients connect to
multiple servers, it is recommended that all of the
servers have unique names.

command.
System action: Tivoli Storage Manager prompts the

user to continue.
User response: Reissue the command with a shorter

email address.
User response: Enter 'Y' to change the server name.

Enter 'N' if you do not want to change the server name.

command.
LAN-free storage pool name.
ANR2584E
ANR2585E
Command: An email address exceeds

Command: An email address contains

invalid syntax.
Explanation: A REGISTER NODE, REGISTER

ADMIN, UPDATE NODE, or UPDATE ADMIN
email addresses. Email addresses must be in the format
name@domain, where the name must be between 1
and 64 characters long, and the domain must be
between 1 and 255 characters long.
command.
User response: Reissue the command with a correct
email address.
ANR2587W
TSM encountered a zero verb on

backupset volume Volume and skipped
to the next volume.
Explanation: TSM detected the problem described in

APAR PK12572 . The server options file contains
SKIPONZEROVERBBACKUPSET ON. TSM verified
there was no further data on the volume, and skipped
to the next volume.
User response: If the backupset volume was written
before TSM 5.2.7, or 5.3.3 was put on the system and
meets the PK12572 criteria, no action is required. If not,
the volume has encountered a read error, and should
read again on a server without the
SKIPONZEROVERBBACKUPSET ON option to get the
correct error messages for problem determination.
ANR2588E
Command: Storage pool StgPool cannot

have CACHE set to YES with a non zero
SHRED attribute.
Explanation: Storage pools can be defined or updated

with a non zero SHRED attribute only if the storage
pool CACHE attribute is NO. Existing storage pools
with CACHE attribute of YES cannot be updated with
257
ANR2589E ANR2601E
a non zero SHRED attribute. Likewise, existing storage
pools with a non zero SHRED attribute cannot be
updated with CACHE = YES. Existing storage pools
with CACHE set to YES cannot be updated with a non
zero SHRED attribute. New storage pools cannot be
define nor can existing storage pools be modified with
CACHE set to YES and a non zero SHRED value.
SHRED value of zero or CACHE = NO.
ANR2589E

name (data type data type) is in use and
cannot be deleted.
take corrective action if needed.

ANR2598W
Administrative command schedule

schedule name started processing at actual
start and is schedule state. The period
expired at expiration time.
Explanation: This message is displayed when an

administrative command schedule has started, the
period for the schedule expired, and the results for the
schedule have not been reported. Possible causes are:
v processing for the action is taking longer than the
scheduled period
v a problem occurred while performing the scheduled
action
v a problem occurred reporting the schedule results
Explanation: The server attempted to delete the

backup set, but the operation could not be completed,
because the backup set was in use by another process.

of the scheduled operation are unknown.

command.
User response: Administrators should consult the

server activity log, then take corrective action if needed.

ANR2599W
ANR2590E
Command: Parameter=Value is invalid for

storage pool Storage Pool.
Explanation: The command failed because one of

forllowing:
v Specify DELetedestroyedvolumes=No for a
random-access storage pool.
v Specify DELetedestroyedvolumes=No for a
sequential-access storage pool and the REUSEDELAY
parameter is not greater than 0.
The central scheduler is unable to

obtain a required lock and will retry in
Explanation: The server temporarily suspends central

scheduler processing because a required lock is not
available.
delay.

command.
User response: The server workload is high. If this

condition persists, you may need to consider adjusting
the server workload.
User response: Reissue the command with a proper

value.
ANR2600E
ANR2597W
Node node name in domain domain name

began schedule schedule name at actual
start and is schedule state. The period
expired at expiration time.
Explanation: This message is displayed when a node

started a schedule, the period for the schedule expired,
and the node has not reported results for the schedule.
Possible causes are:
Command: Invalid schedule name schedule name.

with an invalid schedule name.
schedule name.
v processing for the action is taking longer than the

schedule period
ANR2601E
v a problem occurred while the node was performing

the scheduled action

with a description that exceeds the maximum length.
v the node completed the scheduled action but did not

report the results to the server
of the scheduled operation are unknown.
User response: Administrators should consult the
server activity log and the client scheduler log, then
258
Command: Schedule description exceeds

maximum length characters.

description.
ANR2602E ANR2612E
ANR2602E
Command: Invalid action - action.

with an invalid action.
action.
ANR2603E
Command: Options string exceeds


with an options string that exceeds the maximum
length.
options string.
ANR2604E
Command: Objects string exceeds


with an objects string that exceeds the maximum
length.

start time.
ANR2608E
Command: Invalid duration - duration.

with an invalid duration.
duration.
ANR2609E
Command: Invalid duration units duration units.

with an invalid value for duration units.
value for duration units.
ANR2610E
Command: Invalid period - period.

with an invalid period.



objects string.

period.
ANR2605E
Command: Invalid priority - priority.

with an invalid priority.
priority.
ANR2606E
Command: Invalid period units - period

units.

with an invalid value for period units.
value for period units.
Command: Invalid start date - date.

with an invalid start date.
start date.
ANR2607E
ANR2611E
Command: Invalid start time - time.
ANR2612E
Command: Invalid day of week - day of

week.

with an invalid value for day of the week.
value for day of the week.

with an invalid start time.
259
ANR2613E ANR2622E
ANR2613E
Command: Invalid expiration - date.

with an invalid expiration date.
User response: Issue the command using a schedule

that has already been defined for this domain.
ANR2618E

expiration date.
ANR2614E
Command: Invalid combination of the

following parameters: duration, duration
units, period, period units.

with an invalid combination of the DURATION,
DURUNITS, PERIOD, and PERUNITS parameters. This
message may be displayed if the duration of the
startup window for the schedule is not shorter than the
period between windows. This message may also be
displayed if DURUNITS=INDefinite is specified, but
PERUNITS=Onetime is not specified.
ANR2615E
Command: Expiration date date has

elapsed.

with a schedule name that has already been defined for
the indicated policy domain.
that has not already been defined for this domain.
ANR2619E
User response: Issue the command and specify an

expiration date that has not already elapsed.
ANR2616E
Command: Start date start date must be

earlier than expiration date expiration.

with a start date that is not earlier than the expiration
date.
start date that is earlier than the expiration date.
ANR2617E
Command: Schedule schedule name is not

Command: Currently defined period

period is invalid with updated period
units.

with a value for period units that is not allowed with
the existing period.
User response: Issue the command and specify a new
period.
ANR2620E

with an elapsed expiration date date.
Command: Schedule schedule name is

already defined in policy domain domain
name.
Command: Currently defined duration

duration is invalid with updated
duration units.

with a value for duration units that is not allowed with
the existing duration.
User response: Issue the command and specify a new
duration.
ANR2621E
Command: No matching schedules.

but no matching schedules have been found.
different schedules.
ANR2622E
Command: No new node associations

added.

with a schedule name that has not been defined in the
indicated policy domain.

but no new node associations are defined.


command has no effect.
260
ANR2623E ANR2633E
different nodes.
ANR2623E
Command: No node associations deleted.

but no node associations are deleted.
different nodes.
ANR2624E
Command: No matching nodes registered.
Explanation: No matching nodes are found for the

specified command.
different nodes.
ANR2628E
Command: Invalid date - date.

with an invalid date.
User response: Issue the command with a valid date.
ANR2629E
Command: Invalid time - time.

with an invalid time.
User response: Issue the command with a valid time.
ANR2630E
Command: Event deletion is already in

process.

while event deletion is already in progress.
Command: No matching nodes registered

in policy domain domain name.

Explanation: The specified command has been issued,

but no matching nodes are registered in the indicated
policy domain.
User response: Wait for event deletion to complete

before issuing the command.

ANR2631E
ANR2625E

different nodes.
ANR2626E
Command: Invalid value for replace replace.

with an invalid value for replace.
User response: Issue the command using a valid value
for replace.
ANR2627E
Command: Invalid value for format format.

with an invalid value for format.
User response: Issue the command using a valid value
for format.
Command: Invalid begin date - date.

with an invalid begin date.
User response: Issue the command with a valid begin
date.
ANR2632E
Command: Invalid begin time - date.

with an invalid begin time.
User response: Issue the command with a valid begin
time.
ANR2633E
Command: Invalid end date - date.

with an invalid end date.
User response: Issue the command with a valid end
date.
261
ANR2634E ANR2647E
ANR2634E
Command: Invalid end time - time.

with an invalid end time.
User response: Issue the command with a valid end
time.
ANR2635E
Command: Invalid time range - Begin:

begin End: end.

with an invalid time range. This occurs if the date and
time for the beginning of the time range (begin) do not
precede the date and time for the end of the time range
(end).
User response: Issue the command with a valid time
range.
ANR2636E
Command: Invalid value for exceptions

only - exceptions only.

with an invalid value for exceptions only.
ANR2642E
Command: Invalid percentage for

randomization - value.

with an invalid value.
User response: Issue the command with a valid value.
ANR2643E
Command: Invalid schedule query period

- value.

ANR2644E
Command: Invalid maximum number of

command retries - value.


ANR2645E
User response: Issue the command with a valid value

for exceptions only.

ANR2640E
Command: Invalid percentage of sessions

for scheduled processing - value.

ANR2641E
Command: Invalid event record retention

period - value.

Command: Invalid retry period - value.

ANR2646E
Command: Invalid scheduling mode value.

ANR2647E
Command: Invalid type - type.

with an invalid type.
User response: Issue the command with a valid type.
262
ANR2648E ANR2656E
ANR2648E
Command: Type string exceeds maximum

length characters.

with a type string that exceeds the maximum length.

User response: Issue the command with a valid type

string.
Command: Node node name cannot be

processed because it is not registered or
does not belong to the specified
domain.
Command: Schedule schedule name is not

defined.
Explanation: This command cannot be processed for

the indicated node. Either the node is not registered or
it is not assigned to the required domain.
ANR2649E

with a schedule name that has not been defined.
User response: Issue the command with a schedule
that has already been defined.
ANR2650E
Command: Schedule schedule name is

already defined.

with a schedule name that has already been defined.
User response: Issue the command with a schedule
name that has not already been defined.
ANR2651E
Command: Invalid combination of one or

more of the following parameters: cmd,
type, action, objects, options.

with an invalid combination of the CMD, ACTION,
OBJECTS, and OPTIONS parameters. This message is
displayed when the CMD parameter is specified and
TYPE=CLIENT is not specified, or when
TYPE=ADMIN is specified, and one or more of the
following is specified: ACTION, OBJECTS, or
OPTIONS.
ANR2652E
Command: Invalid combination of one or

more of the following parameters:
active, cmd, type.

with an invalid combination of the TYPE, CMD, or
ACTIVE parameters. This message is displayed when
TYPE=CLIENT is specified and one or more of the
following is specified: ACTIVE, CMD.
ANR2653W
System action: The indicated node is not processed,

but other nodes may be processed if specified by this
command.
User response: If the node name was entered
incorrectly, reissue the command with the correct node
name.
ANR2654E
Command: The NODES parameter cannot

be used when querying administrative
schedules.
Explanation: A QUERY SCHEDULE command has

been issued with TYPE=ADMINISTRATIVE and the
NODES parameter both specified. The NODES
parameter cannot be specified when querying
administrative schedules.
User response: Issue the command without the
NODES parameter.
ANR2655E
Command: Invalid client action schedule

duration - days.

with an invalid number of days. Valid values are 1 to
9999 inclusive. days specifies the length of time during
which a schedule defined by the DEFine CLIENTAction
command must be executed by an associated node.
After that, the schedule will be deleted from the
database.
number of days.
ANR2656E
Command: Invalid schedule style

schedStyle.

with an invalid schedule style.
263
ANR2657E ANR2664E
schedule style.
ANR2657E
Command: Invalid month month.

with an invalid month.
month.
ANR2658E
Command: Invalid day of month month.

with an invalid day of month.
and DAYOFWEEK must not be specified with

DAYOFMONTH. WEEKEND or WEEKDAY must be
specified with the FIRST or LAST week of month.
User response: To see the options for the existing
schedule, issue: QUERY SCHEDULE
FORMAT=DETAILED for the client or administrative
schedule. Determine if the error was caused by one of
the following:
v a conflict between parameters to the update
command.
v a conflict between a parameter specified with the
update command and a value that already exists for
the schedule.

For the latter problem, also update the existing option

that is causing the problem. Correct the update
command and issue it again.

day of month.
ANR2662I
ANR2659E
Command: Invalid week of month month.

with an invalid week of month.
week of month.
ANR2660E
Command: Invalid combination of

enhanced schedule parameters or their
values: parm1 and parm2.

with an invalid combination of the DAYOFMONTH,
WEEKOFMONTH, and DAYOFWEEK parameters.
WEEKOFMONTH and DAYOFWEEK cannot be
specified with DAYOFMONTH. WEEKEND or
WEEKDAY must be specified with the FIRST or LAST
week of month.
Explanation: This message explains the standard

display for an enhanced schedule.
User response: Issue query schedule
format=detailed to display information about an
enhanced schedule.
ANR2663I
Command: Invalid combination of

enhanced schedule parameters or their
values, parm1 and parm2, found for
schedule name.
Explanation: The specified update command has been

issued with either an invalid combination of
parameters or their values, or a specified parameter or
value is not compatible with an option that is not being
updated for the existing schedule. WEEKOFMONTH
264
Command: resetting existing options

options for schedule name to default
values. .
Explanation: The update schedule command has reset

existing options for the schedule to default values. The
change is required by the parameters specified with the
update or audit commands.
ANR2664E
ANR2661E
(*) Query schedule format=standard

displays an asterisk in the day of week
column for enhanced schedules. The
period column is blank. Issue query
schedule format=detailed to display
complete information about an
enhanced schedule.
Command: Invalid parameter parm for

schedule style schedule style.
Explanation: A specified parameter is not valid for the

schedule style.
User response: Issue the command and with
parameters valid for the schedule style.
ANR2665W ANR2673E
ANR2665W
Command: Invalid month and day, month

day, detected.

with an invalid combination of MONTH and
DAYOFMONTH. If one month and one day were
specified in the command, the command will fail. If
there is at least one valid month and day combination,
the schedule will be defined and run on the valid
dates. The schedule will skip the invalid month and
day combinations.
User response: Determine the correct day and month
combinations. If the command failed, issue the define
command again. If the schedule was defined, use the
update command to change the month and day values.
ANR2666W
Command: Invalid month and day, month

day, detected for schedule name.
Explanation: The specified update command has been

issued with either an invalid combination of MONTH
and DAYOFMONTH, or a specified MONTH or
DAYOFMONTH value is incompatible with a MONTH
or DAYOFMONTH value that is not being updated for
the existing schedule. If there is just one month and
one day combination and that combination is invalid,
the command will fail. If there is at least one valid
month and day combination, the schedule will be
updated and run on the valid dates. The schedule will
skip the invalid month and day combinations.
User response: To see the options for the existing
schedule, issue q sched f=d for the client or
administrative schedule. Determine the correct day and
month combinations. If the the command failed, issue
the update command again.
ANR2671E

SCHEDSTYLE parameter for administrative schedule
schedule name.
exported data contains an unknown SCHEDSTYLE
server uses the default or existing SCHEDSTYLE value.
User response: Update the SCHEDSTYLE value for
Alternatively, the export data with the unknown value
can be used, and the SCHEDSTYLE value can be
checked and updated after import processing has been
performed.
ANR2672E

SCHEDSTYLE parameter detected while

SCHEDSTYLE parameter for schedule schedule name in
domain domain name.
exported data contains an unknown SCHEDSTYLE
default or existing SCHEDSTYLE value is used.
User response: Update the SCHEDSTYLE value for
value, and check and update the SCHEDSTYLE value

SCHEDSTYLE parameter in exported
data for schedule schedule name in
domain domain name.

default or existing SCHEDSTYLE value is used.
command, verify that the correct SCHEDSTYLE value
is used for this schedule.
ANR2673E
ANR2670E

SCHEDSTYLE parameter detected while

data - schedule schedule name in domain
domain name defined with default
SCHEDSTYLE value.

by using the default SCHEDSTYLE value for this
schedule.
User response: Verify that the correct SCHEDSTYLE
265
ANR2674E ANR2702E
ANR2674E

data - existing SCHEDSTYLE value for


schedule name.
by using the existing SCHEDSTYLE value for this
schedule.

by using the existing SCHEDSTYLE value for this
schedule.
ANR2679E

Explanation: While verifying the parameters of the

specified command, no valid node was found.
ANR2675E

data for administrative schedule schedule
name.
Command: All of the nodes provided are

invalid.
System action: The server ends the command.

User response: Verify that the nodes specified are
correct and all are registered. Then, reissue the
command.

schedule name.
ANR2700E

imported, the default or existing SCHEDSTYLE value is
used.

central scheduler is not operational.

command, verify that the correct SCHEDSTYLE value
is used for this schedule.
ANR2676E

data - administrative schedule schedule
name defined with default
SCHEDSTYLE value.

schedule name.
by using the default SCHEDSTYLE value for this
schedule.
ANR2677E

data - existing SCHEDSTYLE value for
administrative schedule schedule name
was not updated.
266
Schedule manager aborted.
Explanation: The schedule manager has ended

because of an error condition and is not able to
maintain entries for scheduled operations.

examine server messages issued prior to this message.
Issue the QUERY ACTLOG command to view the
activity log and search for messages. After the error has
been resolved, restart the server to restore central
scheduler operations. If the error cannot be isolated and
ANR2701E
The schedule manager could not be

started: diagcode.
Explanation: The schedule manager cannot be started

during initialization because sufficient memory is not
available. Diagnostic code diagcode is issued.
ANR2702E
The schedule prompter could not be

started: diagcode.
Explanation: The schedule prompter cannot be started

ANR2703E ANR2715E

ANR2703E
ANR2712E
Schedule prompter aborted.
Explanation: The schedule prompter ends because of a

processing error.
prompted scheduling is not operational.
examine server messages issued prior to this message.
Issue the QUERY ACTLOG command to view the
activity log and search for messages. After the error has
been resolved, restart the server to restore central
scheduler prompting operations. If the error cannot be
representative.
ANR2707E
Out of server log space in central

scheduler.

transaction for the central scheduler because sufficient
database update fails.
User response: An authorized administrator can use
volumes are used.
Explanation: A request for pending scheduled

operations has been sent from the client scheduler for
node node1. However, the request is for scheduling
information concerning another node node2.
client scheduler for node node1 will not be able to
process pending operations.
User response: Try restarting the client scheduler for
node node1. If the problem persists, contact your service
representative to resolve the client program error.
ANR2713E
Node node1 trying to start scheduled

operation for node node2 - session
rejected.
Explanation: The client scheduler for node node1 has

attempted to execute a scheduled operation for another
node, node2.
scheduled operation is not processed.
representative to resolve client program error.
ANR2714E
ANR2708E
Node node1 requested scheduling

information for node node2 - session
rejected.
Out of server database space in central

scheduler.
Node node1 trying to report scheduled

operation results for node node2 session rejected.

transaction for the central scheduler because sufficient
Explanation: The client scheduler for node node1 has

attempted to report the results of a scheduled operation
using another node name, node2.


results that were sent from node node1 are not be stored
in the servers database.

for use by the database and can use the EXTEND DB

representative to resolve the client program error.
ANR2715E
ANR2709E
Schedule manager : Unable to start

event record deletion.
Explanation: Event record deletion cannot be started

because sufficient memory is not available.
System action: Server operation continues, but event
records are not automatically deleted after their
retention period has elapsed.
Client node node id unable to register

valid address for server prompting: type
address type (high address low address).
Explanation: The client scheduler for node node id has

attempted to register an invalid address for
server-prompted central scheduling. The address was
type address type with high-level field high address and
low-level field low address. The only valid address type
is 1.
267
ANR2716E ANR2753I
node node id will not be prompted to perform
scheduled operations.
User response: Verify that the address type and
address are correct for this client. The only valid
address type is 1 (for TCP/IP). Make sure the client
scheduler is not using an invalid address obtained from
the clients options file or from the command line when
the client scheduler was started.
ANR2716E
Schedule prompter was not able to

contact client node name using type
address type (high address low address).
Explanation: The server has attempted to prompt the

client scheduler for node node name because a
scheduled operation should be started. The server is
unable to contact the client by using address type
address type, with high-level field high address and
low-level field low address.
System action: Server operation continues, but node
node name is not prompted to start the scheduled
operation. If operations should be started for other
nodes, the server will attempt to prompt the client
schedulers for these nodes. This error is usually caused
by network outages or the client scheduler program not
being run on the client node.
User response: Verify that the address type and
address are correct for this client. The only valid
address type is 1 (for TCP/IP). Make sure the client
scheduler is not using an invalid address, obtained at
the time the client scheduler was started, from either
the clients options file or from the command line.
Verify that the client scheduler for node node name is
running and that the necessary communication links to
that scheduler are operational.
ANR2717E
Schedule prompter cannot contact client

node name using address type (address
type).
Explanation: The server attempts to prompt the client

scheduler for node node name because scheduled work
should be started. However, either the server does not
support address type address type needed for
server-prompted scheduling, or the communication
method is not currently available. The only valid
address type is 1 (for TCP/IP).
server does not prompt node node name.
User response: If the server does not support the
address type specified, clients may only use the polling
mode of scheduling. If the communication method is
temporarily not available, prompted mode scheduling
will resume after the communication problem is fixed
and service restored. If the problem persists, contact
ANR2718W
Schedule manager disabled.
Explanation: The schedule manager has been disabled

because the DISABLESCHEDS YES option was
specified in the server options file.
central scheduler is not operational.
User response: To enable the schedule manager,
specify DISABLESCHEDS NO in the server options file
and restart the server.
ANR2750I
Starting scheduled command schedule

name ( scheduled command ).

server starts the execution of a scheduled command.
The name of the schedule and the actual command
scheduled is displayed.
scheduled command is processed.
ANR2751I
Scheduled command schedule name


server successfully completes processing of a scheduled
command.
ANR2752E

failed.

server encounters a failure in processing a scheduled
command.
scheduled command is ended.
User response: Examine messages issued prior to this
message and use the UPDATE SCHEDULE command
to correct the scheduled command. The QUERY EVENT
command may also be used to determine the cause of
the failure for this scheduled command.
ANR2753I
(Schedule name):command response
Explanation: This message is used to display the

server response to a scheduled command. The name of
the command schedule is included at the beginning of
the message in parentheses.
scheduled command is ended.
268
ANR2754E ANR2763E
ANR2754E
DEFINE SCHEDULE or UPDATE

SCHEDULE parameter CMD=command
- Unknown command.
Explanation: The specified command is not a valid

server command.
System action: The DEFINE SCHEDULE or UPDATE
SCHEDULE command is not processed.
User response: Reissue the correct command.
ANR2759I
Command: The virtual file space

definition vfs name for node node name
has been deleted.

VIRTUALFSMAPPING command, the virtual file space
mapping vfs name for the node node name has been
deleted in the server database.
ANR2755E
DEFINE SCHEDULE or UPDATE

SCHEDULE parameter CMD=command
- not eligible for scheduling.
ANR2760E
Explanation: The specified command is not eligible for

scheduling.
System action: The DEFINE SCHEDULE or UPDATE
SCHEDULE command is not processed.
ANR2756I

started successfully.

server successfully starts processing of a background
process for a scheduled command.
Explanation: The DELETE VIRTUALFSMAPPING

command has been entered, but the specified virtual
file space mapping vfs name for the node node name has
an associated file space definition in server database.
command.
User response: To delete the virtual file space
definition, first delete the filespace definition with the
same name.
ANR2761I

ANR2757E
Command: The NODES parameter cannot

be used when querying events for
Explanation: A QUERY EVENT command has been

issued with TYPE=ADMINISTRATIVE and the NODES
parameter both specified. The NODES parameter
cannot be specified when querying events for
Command: Unable to delete the virtual

file space definition vfs name for node
node name. A file space definition exists
with the same name.
Audit command: auditing inventory

virtual file space mappings.

database audit and indicates that server information
about virtual file space mappings is currently being
examined by the database audit process.
ANR2762I

named vfs name for node node name has
been updated.
User response: Issue the command without the

NODES parameter.

VIRTUALFSMAPPING command, a virtual file space
mapping for the specified node has been updated in
ANR2758E
Please specifiy a tracefile name with

less than 37 characters if it is fully
qualified or 26 characters if it is not
fully qualified.
Explanation: The .template file adds 9 more characters

to the end of the filename.
User response: Reduce the filename length to a
working range for s390 system

ANR2763E
Command: The hexadecimal string

entered for the path parameter is not
valid.

invalid Hexadecimal value for the path parameter.
command.
269
ANR2764E ANR2771E
User response: Check that the string representing the
path contains only valid hexadecimal characters and
contains an even number of characters. Reissue the
command with a valid Hex string for the path
parameter.
ANR2764E
command: Filespace filespace name cannot

be renamed to new filespace name; a
virtual file space with this name already
exists for node node name.
Explanation: The file space name specified as a target

name for the command was found to already exist as a
virtual file space for the node specified. The command
fails.
command fails.
target filespace name
ANR2765E
command: The node node name has an

invalid node type for virtual file space
definitions; the node type must be NAS.
ANR2768I
Explanation: The indicated data mover is being used

by the indicated process.
System action: The indicated data mover is being
used by the indicated process.
ANR2769E
User response: You might want to run this command

again, specifying a node of TYPE=NAS.
ANR2766W
Command: Virtual file space name vfs

name conflicts with file space on the
network attached storage (NAS) device.

entered with a virtual file space that has the same
name as a file space on the NAS device.
Command: Process process ID terminated data mover inaccessible.
Explanation: The indicated process terminated for the

indicated command because none of the data movers is
accessible.
System action: The indicated process terminates.
for possible reasons a remote session could not be
started.
ANR2770E
Explanation: A Define VirtualFSMapping command

was entered with an invalid node type.
command.
Process process ID will use data mover

datamover name for the operation.
Command: Process process ID skipped

restoring data from volume volume name
in storage pool name storage pool - drive
path unavailable.
Explanation: The indicated process skipped restoring

data from the indicated volume because none of the
NAS type datamovers is available.
System action: The data in the indicated volume is
not restored.
User response: Use QUERY STGPOOL to obtain the
device class to which the indicated source storage pool
belongs. Use QUERY DEVCLASS to obtain the library
containing the source storage pool. Then, use the
QUERY DATAMOVER and QUERY PATH commands
to verify that at least one NAS datamover has paths to
the drives in the library.

User response: Ensure that no virtual file space
mappings for this NAS device have the same name as
an actual file space that exists on the NAS device.
ANR2767E
Command: The data format of storage

pool Storage Pool Name does not match
the data format of storage pool Storage
Pool Name.
Explanation: The data format of the indicated storage

pools does not match. The requested operation failed.
User response: Use QUERY STGPOOL F=D to display
the data format for various pools and determine which
may be eligible for the operation. Choose a storage
pool that has the matching data format and re-issue the
command.
270
ANR2771E

volume volume name - data mover
inaccessible.
Explanation: Move data processing terminated for the

indicated volume because none of the data movers is
accessible.
System action: Move data ends for the indicated
volume.
for possible reasons a remote session could not be
started.
ANR2772E ANR2779I
ANR2772E
Command: Process process ID terminated drive path or data mover unavailable.
ANR2775W
Explanation: The indicated process terminated for the

indicated command for one of the following reasons:
v None of the data movers with paths to the drives in
the library containing the source storage pool is
available.
the library containing the target storage pool is
available.
device class to which the source or target storage pool
belongs. Use QUERY DEVCLASS to obtain the library
name that contains the source or target storage pool.
Then, use the QUERY DATAMOVER and QUERY
PATH commands to verify that at least one data mover
has paths to the drives in the library.
ANR2773E

volume volume name - drive path or data
mover unavailable.
Explanation: MOVE DATA processing terminated for

the indicated volume for one of the following reasons:
Command: Process Process id encountered

an output error. File on volume volume
name skipped - Node node name, type file
type, file space filespace name, file name
file name, fsId filespace id.
Explanation: During copy or move operation, an

output error was encountered. The indicated file was
skipped.
System action: The file will not be processed.
User response: If possible, correct the error and re-run
the command.
ANR2776I
Audit command: Inventory object

(object.ID) is part of an incomplete
group. The inventory entry will be
deleted.

inventory object that is part of an incomplete group.
Because FIX=YES has been specified for the command,
the inventory entry is deleted.
Audit command: Inventory object
(object.ID) is part of an incomplete
group.

the library containing the source storage pool is
available.
ANR2777I

the library containing the target storage pool is
available.

inventory object that is part of an incomplete group.

device class to which the source or target storage pool
belong. Use QUERY DEVCLASS to obtain the library
name that contains the source or target storage pool.
Then, use the QUERY DATAMOVER and QUERY
PATH commands to verify that at least one data mover
has paths to the drives in the library.
ANR2774E
Command: Process process ID terminated data format mismatch.
Explanation: During restore processing, a data format

mismatch occurred between the storage pool being
restored and the copy storage pool.
System action: The indicated restore process
terminates.
User response: Examine the previous error message to
determine the name of the copy storage pool used for
the restore. If possible, specify a copy storage pool that
has the same data format as the storage pool being
restored on the restore command.

User response: Run the audit command again with
FIX=YES, so that the error can be corrected.
ANR2778I
Audit command: Storage entry for an

inventory object (object.ID) cannot be
found. The inventory entry will be
deleted.
Explanation: A database audit process cannot find the

storage entry for the specified inventory object. Because
FIX=YES has been specified for the command, the
inventory entry is deleted.
ANR2779I
Audit command: Storage entry for an

inventory object (object.ID) cannot be
found.

storage entry for the specified inventory object.
User response: Run the audit command again with
271
ANR2780W ANR2806W
FIX=YES, so that the error can be corrected.
ANR2780W
Command: Updates for nodes previously

processed during this command will be
rolled back.
Explanation: An error has occurred during an

UPDATE NODE operation. If the UPDATE NODE
command was processing more than one node, updates
for nodes which were previously processed will be
rolled back.
User response: Correct the error and reissue the
command.
ANR2797E
The license value was skipped because

of a bad date range.
Explanation: One or more license values were skipped

due to the current system date not being valid for the
license. This message occurs when reading the
nodelock file. This can occur during server start-up,
license audit, or REGISTER LICENSE.
System action: Server operation fails.
User response: Verify the correct system date setting.
After you correct the system date, the licenses that are
registered with a quantity value will need to be
registered again.
ANR2798E
Server operation is denied - server is not

licensed for License required.
Explanation: The server refuses a server operation

because the server is not licensed with the appropriate
support.
System action: Server operation fails.

ANR2803I
License manager started.
Explanation: The license manager is started when the

server is initialized. The license manager monitors
license compliance.
ANR2804W
Insufficient memory is available for the

license manager - will retry in number of
seconds seconds.
Explanation: The server suspends license manager

processing because sufficient server memory is not
available.
System action: Server operation continues; the license
manager operation will be retried after the specified
delay.
ANR2805W
Insufficient recovery log space available

for the license manager - will retry in

processing because sufficient recovery log space is not
available.
User response: Obtain and register the appropriate

license.

delay.
ANR2799W

add log volumes using the DEFINE LOGVOLUME
command, and can extend the size of the log using the
EXTEND LOG command.
Server operation is in violation of server

license terms - server is not licensed for
License required.
Explanation: The server warns about a server

operation because the server is not licensed with the
appropriate support.
User response: Obtain and register the appropriate
license.
ANR2800E
The license manager cannot be started:

diagcode.
Explanation: The license manager cannot be started

272
ANR2806W
Insufficient database space available for

the license manager - will retry in

processing because sufficient database space is not
available.
delay.
ANR2807E ANR2817I
DEFINE DBVOLUME command, and can extend the
size of the log using the EXTEND DB command.
ANR2807E
Out of server log space in license

manager.

transaction for the license manager because sufficient
recovery log space is not available on the server.
volumes are used.
ANR2813I
Server is licensed for a capacity of

capacity gigabytes and number of clients
clients.
Explanation: This message is issued during server

startup.
ANR2814I
Audit command: License audit period

changed to number of days days.

the SET LICENSEAUDITPERIOD command used to
change the interval in days between automatic license
audits.
ANR2808E
Out of server database space in license

manager.
ANR2815E
Command: Invalid value specified for

interval between license audits - value.

transaction for the license manager because sufficient




for use by the database and can use the EXTEND DB
ANR2811I
Audit License completed - Server is in

Explanation: The results from the AUDIT LICENSES

command indicate the server is in compliance with the
terms of the current license.
ANR2812W
License Audit completed - ATTENTION:

Server is NOT in compliance with
license terms.

command indicate the server is not in compliance with
the terms of the current license.
REGISTER NODE command or backup-archive
requests, or both, will fail.
compliance.
ANR2816E
Command: License audit or register

operation already in progress.
Explanation: The server is currently performing a

register license or license audit.
specified command.
User response: Reissue the command after the license
audit process or the register license command ends.
Only one REGISTER LICENSE command or AUDIT
LICENSE process can be running at a time. The
REGISTER LICENSE command and the AUDIT
LICENSE process may not run at the same time.
ANR2817I
Command: License audit started as

process process ID.

to audit the server for license compliance.
System action: The server checks the existing
configuration for the server and compares it against the
values for which the server is licensed.
PROCESS command, or cancel the process with the
273
ANR2818I ANR2832I
ANR2818I
Command: Licensed capacity is capacity

GB with number of clients clients.
Explanation: This message displays the license

information that existed before issuing the REGISTER
LICENSE command.
ANR2823I
Have audited number of nodes nodes
Explanation: An AUDIT LICENSES operation is in

progress. The process has audited the specified number
of nodes. This message may be displayed in response
to a QUERY PROCESS command for an AUDIT
LICENSES operation.
ANR2819I
Command: Licensed capacity changed to

capacity GB with number of clients clients.
Explanation: The license information has been

changed to the indicated values with the REGISTER
LICENSE command.
User response: To implement the changed license
information, issue an AUDIT LICENSES command or
wait until an automatic license audit occurs.
ANR2820I
Automatic license audit started as

process process ID.

System action: The server checks storage utilization
and registered nodes for the server and licensed factors,
comparing these against the values for which the server
is licensed.
status of the background process using the QUERY
PROCESS command.
ANR2821E
Automatic license audit could not be

started: diagcode.
Explanation: The license manager cannot start an

automatic process to audit server licenses because
sufficient memory is not available. Diagnostic code
diagcode is issued.
ANR2824I
Explanation: A background server process to audit

server licenses has been canceled by using the
CANCEL PROCESS command. The number of nodes
that have been audited before the operation ended are
reported in the message.
ANR2825I
Cancel in progress
Explanation: The license audit operation has been

cancelled and will end when resources have been freed
for an AUDIT LICENSES operation.
274
License audit process process number

completed successfully - number of nodes
nodes audited.

server licenses has completed successfully after
auditing the specified number of nodes.
ANR2826I

terminated in error - number of nodes
nodes audited.

server licenses encounters an error and is ended. The
number of nodes that have been audited before the
operation ended is reported in the message.
ANR2832I
ANR2822I

canceled - number of nodes nodes audited.
Command: The License Manager has not

yet completed initialization - please
retry this command later.
Explanation: While attempting to process the specified

license command, the server detects that the licensing
component of the server had not completed
initialization. The licensing facility used on some
platforms may require some time to initialize because
network calls are involved, and waits may occur.
ANR2833I ANR2855I
User response: Reissue the command after waiting 10
minutes. If this message is displayed after a number of
retry attempts, contact your service representative.
ANR2833I
Command: Auditing license definitions.
Explanation: The server has started to audit database

definitions that describe licensing information.
continues.
ANR2834W
License Audit completed - WARNING:

Server is NOT in compliance with
license terms.

command indicate that the server is not in compliance
with the terms of the current license.
REGISTER NODE command fails.
compliance. Remove nodes or purchase additional
client node connections. After these actions have been
taken, reissue the AUDIT LICENSES command to
resynchronize the server configuration with license
terms.
ANR2836I
Command: License audit started as

process process ID.

System action: The server checks registered nodes for
the server and compares this against the value for
which the server is licensed.
status of the background process using the QUERY
PROCESS command, or cancel the process with the
ANR2841W
Explanation: This message is issued periodically when

the server configuration does not comply with the
terms for which it is licensed.
display the current server configuration with respect to
licensed terms to discover which factors of the
configuration do not conform to your license. Contact
your service representative to obtain more licenses, if
required.
ANR2852I
Automatic license audit started as

process process ID.

System action: The server checks registered nodes and
compares them against the value for which the server
is licensed.
Current license information:
Explanation: This message is issued during a

REGISTER LICENSE command to display the current
licensing information for the server before the new
license has been interpreted by the command. Messages
appearing after this message display the factors under
which the server is currently licensed.
ANR2853I
New license information:
Explanation: This message is issued during a

REGISTER LICENSE command to display the updated
licensing information for the server after the new
license has been interpreted by the command. Messages
appearing after this message display the updated
factors under which the server is licensed.
User response: Check to make sure that the new
license information includes the updates that you
intended for the REGISTER LICENSE command. If the
license terms do not change, check the parameters and
reissue the command, if you find that it was not
entered correctly. If the REGISTER LICENSE command
does not produce the desired updates in terms of
licensing, contact your service representative.
ANR2855I
ANR2839I
Server is NOT IN COMPLIANCE with

license terms.
Server is licensed to support Tivoli

Space Manager clients.

startup.

PROCESS command.
275
ANR2860I ANR2908E
ANR2860I
Server is licensed to support Tivoli

Disaster Recovery Manager.

startup.
ANR2900W
The character string string was

truncated during assignment.
Explanation: Truncation occurred during assignment

of an SQL character string. For example, the expression
CAST( Hello AS CHAR(2) ) will result in truncation
because the string Hello (length 5) can not fit in the
target type CHAR(2) without loss of trailing characters.
System action: This warning can occur before or after
SQL query processing, but does not terminate query
processing.
ANR2904E
Unexpected SQL key word token token.
Explanation: A syntax error occurred because an SQL

key word was found that can not legally be used at the
specified position within the SQL statement. Examples
of SQL key words are SELECT, FROM, and WHERE.
System action: The SQL query is terminated.
ANR2905E
Unexpected SQL identifier token token.

identifier was found that can not legally be used at the
specified position within the SQL statement. Examples
of SQL identifiers are table names and column names.

ANR2906E
ANR2901W
The result of character string

concatenation was truncated.
Explanation: Truncation occurred when the

concatenation of character strings resulted in a length
that exceeds the maximum character string length (250
for data type CHAR, and 2000 for data type
VARCHAR).
System action: This warning can occur before or after
SQL query processing, but does not terminate query
processing.
ANR2902E
Insufficient memory was available to

process the SQL statement.
Explanation: Sufficient memory was not available to

complete the processing of an SQL query.
Unexpected SQL literal token - token.

literal token was found that can not legally be used at
the specified position within the SQL statement.
Examples of SQL literal tokens are abc, 1.567, and
DATE 1/1/96.
ANR2907E
Unexpected SQL operator token - token.

operator token was found that can not legally be used
at the specified position within the SQL statement.
Examples of SQL operator tokens are +, *, <, and =.

ANR2903E
An SQL parser stack overflow occurred

while processing token token.
Explanation: The internal stack used by the SQL

query parser has overflowed. This typically occurs
when too many column names or expressions have
been specified in the SELECT clause.
276
ANR2908E
Unexpected SQL punctuation token token.

punctuation token was found that can not legally be
used at the specified position within the SQL statement.
Examples of SQL punctuation tokens are the period,
the comma, and the parenthesis.
ANR2909E ANR2919E
ANR2909E
The SQL statement is incomplete;

additional tokens are required.
Explanation: A syntax error occurred because,

although the syntax of the SQL query expression was
correct up to the end of the string, the parser expected
additional tokens in order to form a
syntactically-correct SQL statement.

ANR2915E
The SQL token beginning with token is

missing an ending delimiter.
Explanation: An SQL token was found that is missing

its ending delimiter. For example, each of the tokens
abc, abc, and Xabc is missing its ending delimiter.
ANR2910E
ANR2916E
Invalid SQL token - token.
Explanation: An invalid SQL token was found. For

example, the token formed by the character sequence
::! is not a valid SQL token.
ANR2911E
Invalid SQL numeric literal token token.
Explanation: An invalid SQL numeric literal token

was found. For example, the floating point literal
1.456E is not valid.
Explanation: The data types of the operands are not

compatible when used with the specified operator. For
example, the expression 3 + abc is not valid because
the operand data types INTEGER and CHAR(3) are not
compatible for the addition operator +.
ANR2917E

ANR2912E
Invalid character string literal token token.
Explanation: An invalid SQL character string literal

token was found. For example, the hexadecimal literal
X78FG is not valid because it contains the character
G.
The SQL data types data type and data

type are incompatible for operator
operator.
The SQL data type of expression

expression is data type; expecting an
integer expression.
Explanation: An SQL expression of data type

SMALLINT, INTEGER, or DECIMAL with scale zero is
expected.
ANR2918E

expression is data type; expecting a
Boolean expression.
Explanation: An SQL expression of data type

BOOLEAN is expected.
ANR2913E
Invalid SQL identifier token - token.
Explanation: An invalid SQL identifier token was

found. For example, the character sequence ABC.123
is not a valid identifier because the second part of the
identifier, 123, does not begin with a letter.
ANR2914E
SQL identifier token token is too long;

name or component exceeds 18
characters.

ANR2919E

numeric expression.
Explanation: An SQL expression of numeric data type

SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, or DOUBLE_PRECISION is expected.
Explanation: An SQL identifier token was found that

exceeds the maximum length of 18 characters per
component.
277
ANR2920E ANR2928E
ANR2920E

numeric or interval expression.
Explanation: An SQL expression of numeric data type

(SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, DOUBLE) or of interval data type (INTERVAL)
is expected.
of CHAR or VARCHAR, the expression must be a valid

character string representation of a date.
ANR2925E

ANR2921E

character string expression.

expression is data type; expecting a time
or character string time expression.
Explanation: An SQL expression was expected of one

of the types TIME, CHAR, or VARCHAR. In the case of
CHAR or VARCHAR, the expression must be a valid
character string representation of a time.
Explanation: An SQL expression of character string

type CHAR or VARCHAR is expected.
ANR2926E

ANR2922E

expression is data type; expecting a date,
timestamp, character string date,
character string timestamp, or interval
expression.

of the types DATE, TIMESTAMP, CHAR, VARCHAR,
or INTERVAL as the operand to the EXTRACT
function. In the case of CHAR or VARCHAR, the
expression must be a valid character string
representation of a date or a timestamp.

of the types DATE, TIMESTAMP, CHAR, or
VARCHAR. In the case of CHAR or VARCHAR, the
expression must be a valid character string
representation of a date or a timestamp.
ANR2927E

ANR2923E

expression is data type; expecting a time,
timestamp, character string time,
character string timestamp, or interval
expression.

of the types TIME, TIMESTAMP, CHAR, VARCHAR, or
INTERVAL as the operand to the EXTRACT function.
In the case of CHAR or VARCHAR, the expression
must be a valid character string representation of a
time or a timestamp.
ANR2924E

expression is data type; expecting a date
or character string date expression.

of the types DATE, CHAR, or VARCHAR. In the case
278

expression is data type; expecting a date,
timestamp, character string date, or
character string timestamp expression.

expression is data type; expecting an
interval containing a single date-time
field.
Explanation: An SQL expression was expected of data

type INTERVAL YEAR, INTERVAL MONTH,
INTERVAL DAY, INTERVAL HOUR, INTERVAL
MINUTE, or INTERVAL SECOND, all of which contain
a single date-time field. Multi-field interval types (for
example, INTERVAL DAY TO SECOND) are not
allowed.
ANR2928E
A number can not be converted to SQL

data type INTERVAL if the interval
contains multiple date-time fields.
Explanation: An attempt was made to convert a

number to the data type INTERVAL, but the target
interval contains multiple date-time fields (for example,
INTERVAL DAY TO SECOND). Only the single-field
interval types INTERVAL YEAR, INTERVAL MONTH,
INTERVAL DAY, INTERVAL HOUR, INTERVAL
MINUTE, or INTERVAL SECOND can be specified.
ANR2929E ANR2938E
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
constants. A decimal constant such as 1.67 is not valid.
expression can not be determined because all of the

THEN expressions and the ELSE expression (if present)
specifies the NULL key word.
ANR2935E

ANR2930E
A subquery used in an SQL expression

must specify a single result column.
Explanation: A subquery used in an expression can

not specify multiple result columns. For example, the
expression X > (select A,B from T) is invalid because it
specifies two result columns (A and B).
Explanation: The specified date-time field (YEAR,

MONTH, DAY, HOUR, MINUTE, or SECOND) is not
contained in the data type of the expression.
ANR2936E

ANR2931E
A subquery expression may not contain

a reference to a column name that is
contained in an outer query expression.
Explanation: A subquery contains a reference to a

column name in an outer query expression.
ANR2932E
The maximum nesting depth for

subquery expressions has been
exceeded.
The SQL aggregate function function can

not be nested within another aggregate
function.
Explanation: One of the aggregate functions COUNT,

MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was
found nested within another aggregate expression.
ANR2937E

The date-time field field is not present in

the expression expression (data type data
type).
An SQL subquery expression can not be

nested within an aggregate function.
Explanation: An expression containing a subquery

was found nested within one of the aggregate functions
COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
STDDEV.
Explanation: Too many nested subqueries were

specified.
ANR2938E

ANR2933E
The WHERE clause must not contain an

aggregate function.
Explanation: The use of the aggregate functions

STDDEV in the WHERE clause is not allowed.
The column column is not allowed in

this context; it must either be named in
the GROUP BY clause or be nested
within an aggregate function.
Explanation: A column reference was specified that is

neither a column specified in a GROUP BY clause nor
is a column nested in one of the aggregate functions
STDDEV. The use of the column reference is prohibited
because either 1) the GROUP BY clause has been
specified, 2) the HAVING clause has been specified, or
3) at least one aggregate function is present.
ANR2934E
The result data type of a CASE

expression can not be determined; at
least one non-null THEN or ELSE
expression must be specified.
Explanation: The result data type of a CASE

279
ANR2939E ANR2948E
ANR2939E
The reference reference is an unknown

SQL table name.
Explanation: The specified table reference is not one

of the base tables defined by the servers database. The
rows of the table SYSCAT.TABLES can be selected to
obtain a list of all of the valid base tables.
ANR2940E

SQL column name.
Explanation: The specified column reference is not

one of the base table columns defined by the servers
database. The rows of the table SYSCAT.COLUMNS
can be selected to obtain a list of all of the valid base
table columns. If a two-part (compound) column
reference such as X.Y is specified, then the correlation
name X must be one of the active correlation names for
the query.
ANR2941E
The column reference column reference

matches more than one SQL column
name.
Explanation: The specified column reference is

ambiguous because it matches the columns associated
with multiple tables.
ANR2942E
The column reference column reference is

not allowed in this context because it is
part of an outer SQL query expression.
Explanation: The specified column reference is not

allowed because it names a columns of some outer
query expression. Such references are not allowed when
contained within the expressions of the HAVING and
SELECT clauses.
ANR2944E

SQL scalar function name.
Explanation: The specified function reference is not

the name of a valid scalar function.
ANR2945E
Too few arguments are specified for

SQL scalar function function.
Explanation: Too few function arguments were

specified. For example, the expression LEFT(x) is
invalid because the LEFT function requires at least two
arguments.
ANR2946E
Too many arguments are specified for

SQL scalar function function.
Explanation: Too many function arguments were

specified. For example, the expression UPPER(x,y) is
invalid because the UPPER function requires exactly
one argument.
ANR2947E
Division by zero was detected for

operator operator.
Explanation: An attempt to divide by the number zero

was detected for the specified SQL operator. The most
likely cause of the problem is that one of the values of
a column is zero, and that column is used in the
denominator of a division operation. To protect against
this case the NULLIF function can be used. For
example, instead of the expression 1/X, specify
1/NULLIF(X,0), which will set the expression to null
whenever the value if X is zero.

ANR2943E
The column reference column reference is

a duplicate of another SQL column
name in the same list.
Explanation: A duplicate column reference was

specified within the same GROUP BY or ORDER BY
list of columns.
280
ANR2948E
The value value can not be assigned or

converted to SQL data type data type.
Explanation: A value could not assigned or converted

to a value in the specified SQL data type because either
1) the data type of the value can not be legally cast to
the target data type (for example, data type TIME can
not be converted to data type INTEGER); 2) the
assignment of the value results in overflow in the
target data type (for example, the decimal value
12345678.34 can not be assigned to data type
DECIMAL(3,2) because the precision of the target type
is exceeded); or 3) the syntax of a character string value
ANR2949E ANR2957E
is not appropriate for the target data type (for example,
the string abc can not be converted to data type
DATE).
ANR2953E

ANR2949E
Arithmetic overflow occurred for SQL

operator operator.
Explanation: An arithmetic overflow occurred for the

specified operator. Examples of this include: 1) the
application of the unary negation operator to the
smallest INTEGER value (-2147483648) causes overflow
because the result can not be represented in 2s
complement; 2) the sum of the set of INTEGER column
values applied to the SUM aggregate function can not
be represented within the precision of INTEGER type.
The value value (data type data type) is

not a valid character string
representation of an SQL time or a
timestamp for operator operator.
Explanation: An invalid character string

representation of a TIME or TIMESTAMP was
specified. For example, the string g pm is neither a
valid time nor a timestamp.
ANR2954E
An SQL subquery used in a scalar

expression must yield a table that
contains at most one row.
Explanation: This error results when a subquery used

in a scalar expression returns multiple rows, thereby
making it ambiguous as to which value should be
returned.
ANR2950E
Arithmetic or date-time overflow

occurred for SQL operator operator for
values value (data type data type) and
value (data type data type).
Explanation: An arithmetic or date-time overflow

occurred for the specified operator. The values that
caused the overflow (and their SQL data types) are
displayed.
ANR2951E

not a valid argument for operator
operator.
Explanation: An invalid value was specified as an

argument to an SQL operator. For example, the
expression SQRT(-1) is not valid because the argument
to the SQRT function is negative.
ANR2952E

not a valid character string
representation of an SQL date or a
timestamp for operator operator.
Explanation: An invalid character string

representation of a DATE or TIMESTAMP was
specified. For example, the string abc is neither a valid
date nor a timestamp.
User response: Respecify the subquery (for example,

using the WHERE clause) so that the subquery returns
at most one row.
ANR2955E
The SQL character string expression

expression must return a single
character.
Explanation: A single-character character string was

expected for the ESCAPE clause of the LIKE operator,
for the trim character of the TRIM operator, or for the
pad character of the LEFT or RIGHT function. For
example, the string Hello is invalid because it contains
multiple characters.
ANR2956E
Unable to access SQL base table table.
Explanation: An error occurred when attempting to

read rows from one of the SQL base tables. This
message is typically preceded by another error
describing the condition.
ANR2957E
An error occurred inserting a row in an

SQL temporary table. The server
database size may need to be increased
Explanation: An error occurred when attempting to

insert a row into a temporary table being used for an
SQL query. This message is typically preceded by
another error describing the condition. In many cases
this error can be resolved by increasing the size of the
281
ANR2958E ANR2964E
server database. Free space in the database is used to
store temporary tables created during the execution of
an SQL SELECT query.
ANR2958E
SQL temporary table storage has been

exhausted.
Explanation: The result of an SQL query could not be

computed because temporary table storage space was
unavailable. By issuing the QUERY DB command and
viewing the Maximum Reduction parameter, you can
determine the amount of space that is available for
temporary table storage space. If the parameter is less
than 4, the storage space becomes exhausted and the
SQL query can no longer run. Complex SQL queries
such as the ORDER BY clause, the GROUP BY clause,
and the DISTINCT operator can cause additional
temporary table space to be required.
User response: If your database is full, increase the
size of the database. If your database is fragmented
(Where the Available space parameter is greater than 4,
but the Maximum Reduction parameter is less than 4),
you must either unload and load your database or add
a volume.
ANR2959E
SQL temporary table row is too wide.
Explanation: A row could not be inserted into an SQL

temporary table because the row is too wide. This can
occur if 1) there are too many columns in the row being
inserted, or 2) the sum of the lengths of the columns in
the row is too wide. Temporary tables are used when 1)
the ORDER BY clause is specified; 2) the GROUP BY
clause is specified; or 3) the DISTINCT operator is
specified.
User response: Reduce the number of columns
specified in the ORDER BY and/or GROUP BY clauses.
ANR2960E
Unexpected SQL enumerated type name

token - token.

enumerated type name was found that can not legally
be used at the specified position within the SQL
statement. A list of all of the enumerated types declared
by the server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
ANR2961E
Invalid SQL enumerated type name name.

enumerated type name was expected, but the specified
name is not one of the declared enumerated types. For
example, the literal expression XXX::YYYY is illegal
because XXX is not a valid enumerated type name. A
list of all of the enumerated types declared by the
server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
ANR2962E
Unable to resolve SQL enumerated type

for value value.
Explanation: A syntax error occurred because an

unqualified SQL enumerated value name was specified,
but, because that value name is a member of more than
one enumerated type, its type could not be resolved.
For example, the enumerated value name YES belongs
to more than one enumerated type, and so the result
type of the expression YES = YES can not be resolved.
A list of all of the enumerated types declared by the
server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
ANR2963W
This SQL query may produce a very

large result table, or may require a
significant amount of time to compute.
Explanation: An SQL query has been posed that could

potentially cause a very large number of rows to be
returned and displayed, or may involve a large amount
of processing time before the first result table row can
be generated.
continue.
User response: Enter 'Y' to continue with SQL query
processing or 'N' to terminate the query.
ANR2964E
The reference reference is not a column

of the SQL result table.
Explanation: The ORDER BY clause specified a

column that is not part of the result table for the SQL
query. Only those columns named in the select list are
part of the result table.
282
ANR2965E ANR3003E
ANR2965E
An SQL temporary table cannot be

built. required columns columns are
needed. maximum columns is the
maximum.
Explanation: A temporary table required columns wide

is needed to complete processing for an SQL query. The
maximum degree of an SQL table is maximum columns.
The table will not be created.
User response: If the ORDER BY and/or GROUP BY
clauses were specified, reduce the number of columns
needed for the result table.
ANR2966E
Command/process: Database temporary

table storage has been exhausted.
Explanation: The named command or operation could

not be completed because insufficient temporary table
storage space was available. Free space in the server
database is used to store temporary tables created
during the execution of the named command or
process.
System action: The named command or process is
terminated.
User response: Extend the server datbase (after
adding database volumes if necessary) and rerun the
commmand or process.
ANR2996I
The server log is log full percentage

percent full. The server is no longer
delaying transactions.
Explanation: The server log utilization was

dangerously high and the server was delaying
transactions. The log utilization is now at a lower level
and the server is no longer delaying transactions.
User response: Continue to monitor server activity
and log usage. If log usage is low enough, you may
consider reducing the amount of space allocated to the
log.
ANR2997W

percent full. The server will delay
transactions by delay time milliseconds.
Explanation: The server log utilization is very high. In

order to prevent the server log from becoming full, the
server will begin delaying transactions by the specified
amount of time.
ANR2998W

percent full. The server has cancelled
the oldest transaction in the log.
Explanation: The server log utilization is dangerously

high. In order to prevent the server log from becoming
exhausted, the server has cancelled the oldest
transaction in the log. Once the server activity
associated with this transaction is able to perform
cleanup processing, log space will be freed.
User response: Monitor server activity and log usage.
If possible, delay adding new work to the server load.
ANR3000E
Command: Command can only be issued

on a configuration manager.
Explanation: The command can only be issued on a

server that is a configuration manager.
User response: Issue this command from a
configuration manager.
ANR3001E
Command: Command can only be issued

on a managed server.
Explanation: The command can only be issued on a

managed server.
User response: Issue this command from a managed
server.
ANR3002E
Command: Profile name exceeds maximum

length characters.
Explanation: The profile name specified in the

command is longer than the maximum length allowed.
User response: Select a profile name that does not
exceed the maximum length.
ANR3003E
Command: Profile description exceeds

Explanation: The profile description specified in the

command is longer than the maximum length allowed.

User response: Monitor server activity and log usage.

If possible, delay adding new work to the server load.
User response: Select a description that does not

exceed the maximum length.
283
ANR3004E ANR3014E
ANR3004E
Command: The configuration manager

name exceeds maximum length characters.
Explanation: The configuration manager name

specified in the command is longer than the maximum
length allowed.
will delete this object on subscribing managed servers.

User response: To process the command, enter 'Y' to
continue or 'N' to stop the process.
ANR3011E
User response: Select a configuration manager name

that does not exceed the maximum length.
ANR3005E
Command: The server name exceeds

Explanation: The configuration manager name

specified in the command is longer than the maximum
length allowed.
User response: Select a configuration manager name
that does not exceed the maximum length.
ANR3006E
Command: The configuration refresh

interval value must be between minimum
value and maximum value.
command: Subscription for profile profile

name was not deleted because one or
more objects could not be discarded.
Explanation: This message was issued because one or

more objects could not be discarded by the indicated
command. A previous message gives an explanation for
each object that could not be discarded.
System action: The system may discard some of the
managed objects that are associated with profile profile
name The subscription itself is not deleted.
determine the action that must be taken before
remaining objects can be discarded. Alternatively, you
can delete the subscription without using the
DISCARDOBJECTS=YES option.
ANR3012I
command: Configuration manager state

set to state.

with an invalid refresh interval.
Explanation: The command has successfully set the

configuration manager state.

System action: The command succeeded.

refresh interval value.
ANR3007E
Command: The option option must be

specified.

ANR3013W
command: Configuration manager state

already set to state.
Explanation: The specified state is already in force on

the server.
Explanation: When the command is issued on a a

server that is neither a configuration manager nor a
managed server, the specified option must be supplied.


User response: This server is already set to the

specified state. If the state should be set differently,
reissue the command specifying the new state value.

specified option.
ANR3010W
This command will delete an object that

is associated with one or more profiles
on a configuration manager. Subsequent
configuration refresh processing will
delete the object on managed servers
that subscribe to a profile with which
the object is associated.
Explanation: A command has been entered that will

delete an object from a configuration manager. Since
this object is associated with one or more profiles on a
configuration manager, configuration refresh processing
284
ANR3014E
command: One or more subscriptions still

exist.
Explanation: A configuration manager state cannot be

set to OFF is one or more subscription still exist. The
server still has a record of one or more subscriptions to
its profiles.
User response: Use the QUERY SUBSCRIBERS
command to determine which subscriptions still exist.
The DELETE SUBSCRIBER command can be used to
remove the record of these subscriptions. You may
ANR3015E ANR3024W
instead want to delete the actual subscription(s) on the
managed server(s). When there are no more
subscriptions recorded on the configuration manager,
you must then delete all the profiles. Once the profiles
have been deleted, you can reissue the command.
ANR3020E
command: Profile profile name not found.
Explanation: The profile specified could not be found.

Explanation: A configuration manager state cannot be

set to OFF is one or more profiles still exist.
User response: Check to see if the profile name was

specified correctly on the command. Use the QUERY
PROFILE command to check to see if the profile exists
on the configuration manager. Reissue the command
with the correct profile name.

ANR3021I
ANR3015E
command: One or more profiles still

exist.
User response: Use the QUERY PROFILE command to

determine which profiles still exist on the configuration
manager then use the DELETE PROFILE command.
After all the profiles have been deleted, reissue the
command.
ANR3016I
command: Configuration refresh interval

set to interval.
Explanation: The command has successfully set the

configuration refresh interval to the specified value.
Automatic configuration refresh processing will
immediatly be attempted and then will again be
performed after the specified number of minutes of
elapsed.
ANR3017I
command: Profile profile name copied to

profile profile name.
Explanation: The command has successfully copied

the first profile to the newly created second profile. All
the profile associations were also copied.
ANR3022E
command: The profile lock timeout

interval value must be between minimum
value and maximum value.

with an invalid lock timeout interval.
lock timeout interval value.
command: Profile profile name defined.
Explanation: The command has successfully define a

profile.
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.
ANR3018E
command: Profile profile name already

exists.
Explanation: The profile specified already exists on

the configuration manager.

ANR3024W
command: Profile profile already locked

with timeout interval greater than
interval.
User response: Decide on another profile name and

Explanation: An attempt was made to lock the

specified profile. The profile is already locked with a
timeout interval greater than the value specifed.
command: Profile profile name updated.
System action: The profile remains locked with the

original timeout interval.
ANR3019I
Explanation: The command has successfully updated

a profile.
User response: If you want to lower the timeout

interval, unlock the profile and then lock the profile
again specifying the lower value.
285
ANR3025I ANR3034E
ANR3025I
command: Profile profile name unlocked.
Explanation: The command has successfully unlocked

the profile. Configuration information can now be
propogated to the subscribers of the profile.
ANR3030I
command: Subscription defined for

Explanation: The command has successfully defined a

subscription to the specified profile. A refresh of the
configuration information has been initiated.
ANR3026I
command: Profile profile name deleted.
Explanation: The command has successfully deleted

the profile from the configuration manager.
ANR3027E
command: One or more subscriptions still

exist to profile profile name.
Explanation: An attempt was made to delete a profile

that still has subscriptions defined on one or more
managed servers. The configuration manager still has a
record of one or more subscriptions to the profiles.
User response: Use the QUERY SUBSCRIBERS
command to determine which subscriptions still exist.
Use the DELETE SUBSCRIPTION command on the
managed server(s) to delete the subscriptions, and then
reissue the DELETE PROFILE command on the
configuration manager. Alternatively, the FORCE=YES
option can be used on the DELETE PROFILE command
to delete the profile even if there are subscriptions to
the profile. In this case, messages will be issued when
the managed server requests updates for that profile,
informing the managed server that the profile has been
deleted.
ANR3028E
command: Profile profile name is locked.
Explanation: The specifed command cannot be

performed on a locked profile.
User response: Unlock the profile using the UNLOCK
PROFILE command and then reissue the command.
ANR3031W
Explanation: A subscription already exists for the

specified profile.
User response: Check to make sure you specified the
correction profile name, and reissue the command if
needed.
ANR3032E
command: Profile name not specified.
Explanation: A profile name must be specifed on this

command using the PROFILE= parameter.
profile name.
286
command: Server name not specified.
Explanation: A server name must be specifed on this

command using the SERVER= parameter. This
identifies the configuration manager.
server name.
ANR3033E
command: Server server is not the

managed servers configuration
manager.
Explanation: A server name was specified on the

command which does not match the current
configuration manager. A managed server may only
have one configuration manager.
User response: Reissue the command and leave off
the server parameter. It will default to use the current
configuration manager. A QUERY SUBSCRIPTION will
display the configuration manager currently in use.
ANR3034E
ANR3029E

name already exists.
command: Server server cannot be used as

this servers configuration manager.
Explanation: A server name was specified on the

command which cannot be used as a configuration
manager.
User response: Find out the currect name for the
configuration manager and then reissue the command.
ANR3035I ANR3043E
ANR3035I
command: Subscriber subscriber name

deleted.
Explanation: The command has successfully deleted a

subscriber from the record kept in the configuration
manager. If the subscriber (managed server) still has a
subscription to a valid profile, the record of the
subscription will reappear when it performs its next
configuration refresh.

User response: Use the QUERY ADMIN command to
check which administrators that are defined on the
server and then reissue to DEFINE
PROFASSOCIATION command.
ANR3040I

ANR3036E
command: Subscriber subscriber name not

found.
Explanation: The specified subscriber name was not

found in the configuration managers records as being a
valid subscriber of any profiles.
User response: Check to see that the subscriber
(managed server) name is correction. If you think the
name is correct, perhaps the managed server has not
yet successfully contacted the configuration manager to
inform it that the subscription exists.
ANR3037I
command: Subscription deleted for


subscription for the specified profile. A refresh of the
configuration information has been initiated.
Explanation: The command has successfully

associated all the administrators with the specified
profile. All administrator definitions will be
automatically propogated to managed servers which
subscribe to the profile. If an administrator is added to
the configuration manager in the future, its definition
will also be automatically propogated to the managed
servers.
ANR3041I

name not found.
command: Administrator admin associated

with profile profilename.

associated the administrator with the specified profile.
The administrator definition will be automatically
propogated to managed servers which subscribe to the
profile.
ANR3042W

ANR3038E
command: All administrators associated

command: No additional administrators

associated with profile profilename.
Explanation: No additional administrator were

associated with the profile. The administrator(s)
specified are already associated with the profile.
Explanation: A subscription was not found for the

specified profile.


User response: Use the QUERY ADMIN command to

check which administrators are defined on the server
and then reissue to DEFINE PROFASSOCIATION
command. The QUERY PROFASSOCIATION
FORMAT=DETAILED can be used to see which
administrators are already associated with the profile.
User response: Check to see that the profile name was

specified correctly. Issue the QUERY SUBSCRIPTION
command to check to see which profiles have
subscriptions. Reissue the command with the correct
profile name.
ANR3043E
ANR3039E
command: No matching administrators

found in configuration.
Explanation: No administrator definitions were found

on the configuration manager that match the admin(s)
specified on the DEFINE PROFASSOCIATION
command.
command: No matching domains found

in configuration.
Explanation: No domain definitions were found on

the configuration manager that match the domain(s)
command.
287
ANR3044I ANR3051E
User response: Use the QUERY DOMAIN command
to check which domains that are defined on the server
and then reissue to DEFINE PROFASSOCIATION
command.
ANR3044I
command: All domains associated with

profile profilename.

associated all the domains with the specified profile.
All domain definitions will be automatically
profile. If a domain is added to the configuration
manager in the future, its definition will also be
automatically propogated to the managed servers.
ANR3048I

associated all the admin schedules with the specified
profile. All admin schedule definitions will be
subscribe to the profile. If an admin schedule is added
to the configuration manager in the future, its
definition will also be automatically propogated to the
managed servers.
ANR3049I

ANR3045I
command: Domain domain associated with


associated the domain with the specified profile. The
domain definition will be automatically propogated to
managed servers which subscribe to the profile.
command: All admin schedules

command: Admin Schedule admin schedule


associated the admin schedule with the specified
profile. The admin schedule definition will be
subscribe to the profile.

ANR3046W
command: No additional domains

Explanation: No additional domains were associated

with the profile. The domain(s) specified are already
associated with the profile.
User response: Use the QUERY DOMAIN command
to check which domains are defined on the server and
then reissue to DEFINE PROFASSOCIATION
command. The QUERY PROFASSOCIATION
FORMAT=DETAILED can be used to see which
domains are already associated with the profile.
ANR3050W
Explanation: No additional admin schedules were

associated with the profile. The admin schedule(s)
User response: Use the QUERY SCHEDULE
TYPE=ADMIN command to check which admin
schedules are defined on the server and then reissue to
DEFINE PROFASSOCIATION command. The QUERY
PROFASSOCIATION FORMAT=DETAILED can be
used to see which admin schedules are already
ANR3051E
ANR3047E
command: No matching admin schedules

Explanation: No admin schedule definitions were

found on the configuration manager that match the
admin schedule(s) specified on the DEFINE
User response: Use the QUERY SCHEDULE
TYPE=ADMIN command to check which admin
schedules are defined on the server and then reissue to
DEFINE PROFASSOCIATION command.
288
command: No additional admin

scheduless associated with profile
profilename.
command: No matching scripts found in

configuration.
Explanation: No script definitions were found on the

configuration manager that match the script(s) specified
on the DEFINE PROFASSOCIATION command.
User response: Use the QUERY SCRIPT command to
check which scripts that are defined on the server and
command.
ANR3052I ANR3059E
ANR3052I
command: All scripts associated with


associated all the scripts with the specified profile. All
script definitions will be automatically propogated to
managed servers which subscribe to the profile. If a
script is added to the configuration manager in the
future, its definition will also be automatically
propogated to the managed servers.
ANR3056I
command: All client option sets


associated all the client option sets with the specified
profile. All client option set definitions will be
subscribe to the profile. If a client option set is added
to the configuration manager in the future, its
definition will also be automatically propogated to the
managed servers.
ANR3053I
command: Script script associated with


associated the script with the specified profile. The
script definition will be automatically propogated to
ANR3054W
command: No additional scripts

Explanation: No additional scripts were associated

with the profile. The script(s) specified are already
User response: Use the QUERY SCRIPT command to
check which scripts are defined on the server and then
reissue to DEFINE PROFASSOCIATION command. The
QUERY PROFASSOCIATION FORMAT=DETAILED
can be used to see which scripts are already associated
with the profile.
ANR3055E
command: No matching client option sets

Explanation: No client option set definitions were

found on the configuration manager that match the
client option set(s) specified on the DEFINE
User response: Use the QUERY CLOPTSET command
to check which client option sets that are defined on
the server and then reissue to DEFINE
ANR3057I
command: Client option set client option

set associated with profile profilename.

associated the client option set with the specified
profile. The client option set definition will be
subscribe to the profile.
ANR3058W
command: No additional client option

sets associated with profile profilename.
Explanation: No additional client option sets were

associated with the profile. The client option set(s)
User response: Use the QUERY CLOPTSET command
to check which client option sets are defined on the
server and then reissue to DEFINE
PROFASSOCIATION command. The QUERY
used to see which client option sets are already
ANR3059E
command: No matching servers found in

configuration.
Explanation: No server definitions were found on the

configuration manager that match the server(s)
command.
User response: Use the QUERY SERVER command to
check which servers that are defined on the server and
command.
289
ANR3060I ANR3067E
ANR3060I
command: All servers associated with


associated all the servers with the specified profile. All
server definitions will be automatically propogated to
managed servers which subscribe to the profile. If a
server is added to the configuration manager in the
future, its definition will also be automatically
propogated to the managed servers.
ANR3064I
command: All server groups associated


associated all the server groups with the specified
profile. All server group definitions will be
subscribe to the profile. If a server group is added to
the configuration manager in the future, its definition
will also be automatically propogated to the managed
servers.
ANR3061I
command: Server server associated with


associated the server with the specified profile. The
server definition will be automatically propogated to
ANR3062W
command: No additional servers

Explanation: No additional servers were associated

with the profile. The server(s) specified are already
User response: Use the QUERY SERVER command to
check which servers are defined on the server and then
reissue to DEFINE PROFASSOCIATION command. The
QUERY PROFASSOCIATION FORMAT=DETAILED
can be used to see which servers are already associated
with the profile.
ANR3063E
command: No matching server groups

Explanation: No server group definitions were found

on the configuration manager that match the server
group(s) specified on the DEFINE PROFASSOCIATION
command.
User response: Use the QUERY SERVERGROUP
command to check which server groups that are
defined on the server and then reissue to DEFINE
290
ANR3065I
command: Server group server group


associated the server group with the specified profile.
The server group definition will be automatically
profile.
ANR3066W
command: No additional server groups

Explanation: No additional server groups were

associated with the profile. The server group(s)
User response: Use the QUERY SERVERGROUP
command to check which server groups are defined on
the server and then reissue to DEFINE
PROFASSOCIATION command. The QUERY
used to see which server groups are already associated
with the profile.
ANR3067E
command: No matching administrators

associated with profile profile.
Explanation: No matching administrator definitions

are associated with the specified specified profile.
User response: Use the QUERY PROFASSOCIATION
command to check which administrators are associated
with the profile and then reissue to DELETE
ANR3068I ANR3077I
ANR3068I
command: All administrator associations

deleted from profile profilename.

all administrators associations from the specified
profile. This will automatically delete these
administrators from the managed servers that are
subscribed to this profile.
ANR3069I
command: Administrator association

admin deleted from profile profilename.

an administrator association from the specified profile.
This will automatically delete this administrator from
the managed servers that are subscribed to this profile.
ANR3073E
command: No matching admin schedules

Explanation: No matching admin schedule definitions

command to check which admin schedules are
associated with the profile and then reissue to DELETE
ANR3074I
command: All admin schedule

associations deleted from profile
profilename.

all admin schedules associations from the specified
profile. This will automatically delete these admin
schedules from the managed servers that are subscribed
to this profile.
ANR3070E
command: No matching domains

Explanation: No matching domain definitions are

associated with the specified specified profile.
command to check which domains are associated with
the profile and then reissue to DELETE

ANR3075I
command: Admin schedule association

admin schedule deleted from profile
profilename.

an admin schedule association from the specified
profile. This will automatically delete this admin
schedule from the managed servers that are subscribed
to this profile.
ANR3071I
command: All domain associations


all domains associations from the specified profile. This
will automatically delete these domains from the
managed servers that are subscribed to this profile.
ANR3072I
command: Domain association domain


domain association from the specified profile. This will
automatically delete this domain from the managed
servers that are subscribed to this profile.

ANR3076E
command: No matching scripts associated

with profile profile.
Explanation: No matching script definitions are

command to check which scripts are associated with
ANR3077I
command: All script associations deleted

from profile profilename.

all scripts associations from the specified profile. This
will automatically delete these scripts from the
291
ANR3078I ANR3087I
ANR3078I
command: Script association script deleted


script association from the specified profile. This will
automatically delete this script from the managed
servers that are subscribed to this profile.
ANR3079E
command: No matching client option sets

Explanation: No matching clent option set definitions

command to check which client option sets are
associated with the profile and then reissue to DELETE
ANR3080I
command: All client option set

associations deleted from profile
profilename.

all client option sets associations from the specified
profile. This will automatically delete these client
option sets from the managed servers that are
subscribed to this profile.
ANR3081I
command: Client option set association

client option set deleted from profile
profilename.

client option set association from the specified profile.
This will automatically delete this client option set from
command to check which servers are associated with

ANR3083I
command: All server associations deleted


all servers associations from the specified profile. This
will automatically delete these servers from the
ANR3084I
command: Server association server


server association from the specified profile. This will
automatically delete this server definition from the
ANR3085E
command: No matching server groups

Explanation: No matching server group definitions are

command to check which server groups are associated
with the profile and then reissue to DELETE
ANR3086I
command: All server group associations


all server groups associations from the specified profile.
This will automatically delete these server groups from

ANR3087I
ANR3082E
command: No matching servers

Explanation: No matching server definitions are

292
command: Server group association server

group deleted from profile profilename.

server group association from the specified profile. This
will automatically delete this server group from the
ANR3088W ANR3151E
ANR3088W
This command will cause the deletion

of objects on any managed server
subscribed to profile profile name.
Explanation: A DELETE PROFASSOCIATION

command option has been entered. This action will not
only delete the association from the profile, but it will
also result in the deletion of managed object(s) on any
managed server subscribing to this profile. The deletion
of these objects will occurr during the next
configuration refresh for that managed server.
User response: To process the DELETE
PROFASSOCATION command, enter 'Y' to continue or
'N' to stop the command.
ANR3089E
command: Command failed Server-to-server communication error

with server server name.
Explanation: The specified command failed while

attempting to communicate with the indicated server.
User response: Verify that the indicated server name
is correctly defined. Try reissuing the command. Use
the server PING command to see if the other server is
up. If the problem persists, consult with your network
administrator.
ANR3090E
command: Server server name is not a

Explanation: The specified command failed because it

tried to contact the specified server, and discovered that
the server is not a configuration manager.
correct configuration manager name.
ANR3092I
Explanation: A NOTIFY SUBSCRIBER process has

begun. The managed server(s) are being contacted,
asking them to immediately perform a configuration
refresh.
command succeeded.
ANR3093I
command: Profile list not specified.
Explanation: The specified command failed because

you did not specify a profile list on the command.
profile list.
command: No matching profiles or

subscriptions were found.
Explanation: No subscriptions were found for the

profiles specified. Either the profiles do not exist, or
there are no subscriptions to the profiles.
User response: Use the QUERY PROFILE and QUERY
SUBSCRIBER command to determine which profiles
exist and which profiles have subscribers. Reissue the
command specifying the correct profile name(s).
ANR3150E
Configuration refresh failed with

configuration manager server name. Will
retry in minutes minutes.
Explanation: While receiving configuration

information from the specified configuration manager,
processing failed because of a communications error.
configuration refresh process was stopped and will be
automatically retried.
User response: Perhaps the configuration manager is
not active. If the problem continues, contact the
administrator for the configuration manager, or contact
a network administrator. The refresh will automatically
retry several times and then give up until the
configuration refresh interval is reached again.
ANR3151E
ANR3091E
command: Subscriber notification

processing has begun.
Configuration refresh failed with

configuration manager server name.

processing failed.
configuration refresh process was stopped.
User response: Examine the activity log for other
messages that may explain why the configuration
refresh failed. The refresh will attempted again when
the configuration refresh interval is reached.
293
ANR3152I ANR3159E
ANR3152I
Configuration refresh started with

configuration manager server name.
Explanation: Configuration refresh processing has

started. A server-to-server session was opened to
receive configuration information from the
configuration manager. Updates will be sent for objects
associated with any subscribed-to profiles.
System action: Refresh processing continues.
ANR3153I
Configuration refresh ended

successfully with configuration manager
server name.
Explanation: Configuration refresh processing ended

successfully. All updates have been made to managed
objects associated with any subscribed-to profiles.
System action: Server processing continues. The next
automatic refresh will start when the configuration
refresh interval is reached.
ANR3154E
Communication error on notify to

managed server server name. Will retry in
minutes minutes.
Explanation: While attempting a notify subscriber

request to the specified managed server, a
communications error was detected.
System action: Server operation continues. The notify
subscriber request was stopped and will be
automatically retried.
User response: Perhaps the managed server is not
active. If the problem continues, contact the
administrator for the managed server, or contact a
network administrator. The notify subscriber request
will automatically retry several times and then give up.
ANR3155E
Error attempting notify subscribers

request to managed server server.
System action: Server operation continues. The notify

subscriber request failed.
User response: Examine the activity log for other
messages that may explain why the notify subscriber
request failed.
ANR3156E
Configuration refresh failed for

managed server server name.
Explanation: While sending configuration information

to the specified managed server, processing failed.
configuration refresh process ended.
User response: Examine the activity log of both the
294
managed server and the configuration manager for

other messages that may explain why the configuration
refresh failed. The refresh will attempted again by the
managed server when its configuration refresh interval
is reached.
ANR3157I
Configuration refresh started for

managed server server name.
Explanation: Configuration refresh processing has

started. A server to server session was opened by the
managed server to receive configuration information
from the configuration manager. Updates will be sent
for objects associated with any subscribed-to profiles.
System action: Refresh processing continues.
ANR3158I
Configuration refresh ended

successfully for managed server server
name.
Explanation: Configuration refresh processing ended

successfully. All updates have been made to managed
objects associated with any subscribed-to profiles on
the managed server.
ANR3159E
Managed server server name has newer

version for profile profile name.

to the specified managed server, it has been detected
that the managed server has a newer version of
configuration information for the specified profile than
does the configuration manager. This condition can
happen if the configuration managers database has
been restored to an earlier point in time. Another
possibility is that the profile was deleted on the
configuration manager and a new profile by the same
name was created.
System action: Server operation continues. No
configuration information for this profile will be sent to
the managed server until this condition is corrected.
User response: Before correcting the situation, you
may want to use QUERY PROFILE to examine the
profile associations defined on both the configuration
manager and the managed server. To correct the
situation, on the managed server delete the
subscription to the profile and define the subscription
again. This will cause the managed server to be
refreshed at the configuration managers current level.
ANR3160E ANR3167E
ANR3160E
Unable to receive confirmation of

refresh from managed server server name.
ANR3164E
Managed server server name aborted

configuration refresh processing due to
a lock conflict.

to the specified managed server, a communication error
occurred when trying to receive confirmation from the
managed server that information was processed
successfully.

to the specified managed server, processing ended
prematurely because of a lock conflict on the managed
server.

Configuration refresh processing ended.

User response: Determine if communication can be

established with the managed server by using the
server PING command. Use the NOTIFY
SUBSCRIBERS command to force the configuration
refresh to retry.
User response: Use the NOTIFY SUBSCRIBERS

command to retry the configuration refresh. If this
problem persists, contact your service representative.
ANR3161E
Premature end of configuration refresh

for managed server server server name.
ANR3165E

a protocol error.

prematurely because of on error.

prematurely because of a protocol error detected on the
managed server.


User response: Examine the activity log on the

managed server for any error messages that might
explain why the refresh failed. Use the NOTIFY
SUBSCRIBERS command on the configuration manager
to force the configuration refresh to retry.
User response: Use the NOTIFY SUBSCRIBERS

command to retry the configuration refresh. If this
ANR3162E

a low memory condition.

prematurely because of a low memory condition on the
managed server.
managed server.
ANR3163E

an internal error.

prematurely because of an internal error on the
managed server.
ANR3166E
Unable to receive configuration refresh

information from server server name.

processing ended prematurely because of a
communications error.
User response: Use the server PING command to see
if the configuration manager can be reached. If the
problem persists, contact your network administrator.
ANR3167E
Configuration manager server name

aborted configuration refresh processing
due to a low memory condition.

processing ended prematurely because of a low
memory condition on the configuration manager.
User response: Notify the administrator of the
User response: Examine the activity log of the

managed server for messages that explain the cause of
the internal error.
295
ANR3168E ANR3174E
ANR3168E

due to an internal error.

processing ended prematurely because of an internal
error on the configuration manager.
User response: Examine the activity log of the
configuration manager for messages that explain the
cause of the internal error.
ANR3169E

due to a lock conflict.

information from the specified managed server,
processing ended prematurely because of a lock conflict
on the configuration manager.
User response: Retry the configuration refresh by
issuing the SET CONFIGREFRESH command (using
the current refresh interval value). If this problem
ANR3170E

due to a protocol error.

processing ended prematurely because of a protocol
error detected on the configuration manager.
User response: Retry the configuration refresh by
issuing the SET CONFIGREFRESH command (using
the current refresh interval value). If this problem
ANR3171E
Configuration refresh with

configuration manager server name had
to skip processing for one or more
objects.

it became necessary to skip the creation or deletion of
one or more objects.
User response: Examine the managed servers activity
296
log for earlier messages that identfy the object, and

take the actions identified in those messages.
Configuration refresh processing will not complete
successfully until the problem is clear up.
ANR3172W
Subscription exists for deleted profile

profile name.

information from the configuration manager, it has
been detected that the managed server has a
subscription to an profile that no longer exists on the
configuration manager. This condition can exist because
the profile was deleted with FORCE=YES on the
configuration manager. This out-of-synch condition can
also occur because one of the servers database was
regressed because of a restore db.
User response: The DELETE SUBSCRIPTION
command is used to correct this situation. You need to
decide if you want the managed objects to remain on
the server. If you want them to be deleted, specify
DISCARD=YES. If you want the objects to remain on
the managed server as local objects, specify
DISCARD=NO.
ANR3173E
Server has newer version for profile

profile name than the configuration
manager server name.

information from the configuration manager, it has
been detected that the managed server has a newer
version of configuration information for the specified
profile than does the configuration manager. This
condition can happen if the configuration managers
database has been restored to an earlier point in time.
Another possibility is that the profile was deleted on
the configuration manager with FORCE=YES and a
new profile by the same name was created.
configuration information for this profile will be sent to
the managed server until this condition is corrected.
User response: Before correcting the situation, you
may want to use QUERY PROFILE to examine the
profile associations defined on both the configuration
manager and the managed server. To correct the
situation, on the managed server delete the
subscription to the profile and define the subscription
again. This will cause the managed server to be
refreshed at the configuration managers current level.
ANR3174E
Communication error with managed

server server name.
Explanation: While receiving or sending information

to the specified managed server, a communcations error
was experienced.
ANR3175W ANR3204E
operation in progress fails.
User response: If this error happens often, consult
with your network administrator. Also check to see that
the managed server is up.
ANR3175W
Profile profile name is locked and could

not be refreshed from configuration
manager server name.
Explanation: While receiving configuration refresh

information from the specified managed server, it was
detected that a subscribed-to profile is locked.
System action: Server operation continues. Refresh
processings skips over this profile.
User response: Normally, the profile will later be
unlocked automatically, or by an administrator. If you
think that it should not be locked, have ask the
configuration manager admin to unlock it using the
UNLOCK PROFILE command.
indicated managed domain. With the exception of

policy set activation, a managed domain can only be
modified using configuration information propagated
from the configuration manager.
ANR3201E
Explanation: The indicated domain is a managed

object and cannot be deleted on the managed server.
User response: To delete this object, you can delete
the subscription to the configuration profiles with
which domain domain name is associated.
ANR3202E
ANR3176W
Profile profile name is locked and could

not be refreshed for managed server
server name.
Explanation: While sending configuration refresh

information to the specified managed server, it was
detected that a subscribed-to profile is locked.
processings skips over this profile.
User response: If the profile should no longer be
locked, use the UNLOCK PROFILE command to
unlock it.
ANR3177W
Server level does not support object in

Explanation: While receiving configuration refresh

information from the configuration manager, an object
was received that is not supported on this managed
server.
processings skips over this object. The refresh for the
profile fails.
User response: The configuration manager is at a
higher release level than the managed server. The
managed server subscribed to a profile that contains an
unsupported object. Delete the subscription to this
profile until service can be applied to the server to
bring it to a higher release level.
ANR3200E
command: Command cannot be executed

- domain domain name is a managed
object.
command: Domain domain name is a

managed object and cannot be deleted.
command: Domain domain name is a

managed object and cannot be updated.
Explanation: The indicated domain is a managed

object and cannot be updated on the managed server.
User response: To update this object, you can delete
ANR3203E
command: Policy set set name in domain

domain name is a managed object and
cannot be deleted.
Explanation: The indicated policy set is a managed

ANR3204E
command: Policy set set name in domain

domain name is a managed object and
cannot be updated.
Explanation: The indicated policy set is a managed

Explanation: The specified command cannot be

executed because it would alter the contents of the
297
ANR3205E ANR3212E
ANR3205E
command: Management class class name in

domain domain name, policy set set name
is a managed object and cannot be
deleted.
ANR3209E
command: Backup copy group group name

in domain domain name, policy set set
name, management class class name is a
Explanation: The indicated management class is a

managed object and cannot be deleted on the managed
server.
Explanation: The indicated backup copy group is a

managed object and cannot be updated on the
managed server.




ANR3206E
command: Management class class name in

domain domain name, policy set set name
is a managed object and cannot be
updated.
ANR3210E
command: Archive copy group group name

Explanation: The indicated management class is a

managed server.
Explanation: The indicated archive copy group is a

managed server.




ANR3207E
command: Backup copy group group name

Explanation: The indicated backup copy group is a

server.
ANR3211E
Explanation: The indicated client schedule is a

server.
ANR3212E
ANR3208E
command: Archive copy group group name

Explanation: The indicated archive copy group is a

server.
298
command: Client schedule schedule name

in domain domain name is a managed
object and cannot be deleted.
command: Client schedule schedule name

in domain domain name is a managed
object and cannot be updated.
Explanation: The indicated client schedule is a

managed server.
ANR3213E ANR3220E
ANR3213E
command: Administrative schedule

schedule name is a managed object and
cannot be deleted.
Explanation: The indicated administrative schedule is

a managed object and cannot be deleted on the
managed server.
which the object is associated.
ANR3214E
command: Administrative schedule

schedule name is a managed object and
cannot be updated, except to activate or
deactivate the schedule.
Explanation: The indicated administrative schedule is

a managed object and cannot be updated on the
managed server, except to change the active state of the
schedule.
ANR3215W
Managed domain domain name contains

at least one node and cannot be
discarded.
Explanation: This message is issued while processing

a DELETE SUBSCRIPTION command with
DISCARDOBJECTS=YES. The indicated domain cannot
be discarded on the managed server because it still
contains one or more nodes.
System action: Domain domain name is not deleted.
Policy sets, management classes, copy groups, and
client schedules belonging to this domain are also not
deleted.
User response: Before this domain can be deleted,
nodes in the domain must be removed or assigned
another domain.
ANR3216W
Managed administrative schedule

schedule name is active and cannot be
discarded.

DISCARDOBJECTS=YES. The indicated administrative
schedule cannot be discarded on the managed server
because it is in the active state.
System action: Administrative schedule schedule name
is not deleted.
User response: Before this administrative schedule can

be deleted, it must be deactivated using the Update
Schedule command.
ANR3217E
command: Administrator administrator

name is a managed object and cannot be
removed.
Explanation: The indicated administrator is a

managed object and cannot be removed on the
managed server.
User response: To remove this administrator, you can
delete the subscription to the configuration profiles
with which the object is associated.
ANR3218E

updated.

managed server.
User response: To update this administrator, you can
ANR3219E

renamed.

managed object and cannot be renamed on the
managed server.
User response: To rename this administrator, you can
ANR3220E

name is a managed object - authority
cannot be granted.

managed object. Authority cannot be granted to this
administrator on the managed server.
User response: To grant authority to this
administrator, you can delete the subscription to the
configuration profiles with which the object is
associated.
299
ANR3221E ANR3229E
ANR3221E

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
associated.
User response: To update this script, you can delete

ANR3226E
ANR3222W
Managed administrator administrator

name is the only system administrator
and cannot be discarded.

DISCARDOBJECTS=YES. The indicated administrator
cannot be discarded on the managed server because it
is the only system administrator.
System action: Administrator administrator name is not
deleted.
User response: Before this administrator can be
deleted, another administrator must be given system
authority.
ANR3223W

name is currently accessing the server

DISCARDOBJECTS=YES. The indicated administrator
cannot be discarded on the managed server because it
has an active session with the server.

cannot be renamed.

managed object and cannot be renamed on the
managed server.
User response: To rename this script, you can delete
ANR3227E
command: Option set optionset name is a

Explanation: The indicated option set is a managed

User response: To delete this option set, you can
System action: Administrator administrator name is not

deleted.
ANR3228E
User response: Quit or cancel all sessions for this

administrator before discarding the administrator
definition.
Explanation: The indicated option set is a managed

ANR3224E

cannot be deleted.

server.
User response: To delete this script, you can delete the
subscription to the configuration profiles with which
the object is associated.
300
command: Option set optionset name is a


User response: To update this option set, you can
ANR3229E

- option set optionset name is a managed
object.

executed because it would alter the contents of the
indicated managed option set.
ANR3230E ANR3237W
ANR3230E
command: Server group group name is a

Explanation: The indicated server group is a managed

User response: To delete this server group, you can
ANR3231E


User response: To update this server group, you can
ANR3232E

managed object and cannot be renamed.

object and cannot be renamed on the managed server.
User response: To rename this server group, you can
ANR3233E

- server group group name is a managed
object.

executed because it would alter the membership of the
indicated managed server group.
ANR3234E
command: Server server name is a

Explanation: The indicated server is a managed object

and cannot be deleted on the managed server.

ANR3235E
command: Server server name is a

managed object - one or more specified
attributes cannot be updated.
Explanation: Because the indicated server is a

managed object, certain attributes cannot be updated
on the managed server. These attributes are:
SERVERPASSWORD, HLADDRESS, LLADDRESS,
COMMMETHOD, DESCRIPTION, URL, and
ALLOWREPLACE.
User response: You can restrict the update to
attributes that can be updated on the managed server.
For example, the PASSWORD, NODENAME,
FORCESYNC, and DELGRACEPERIOD attributes can
be updated, even if the server is a managed object.
Alternatively, you can delete the subscription to the
associated, so that the server is no longer a managed
object.
ANR3236W
Server server name is currently in use


DISCARDOBJECTS=YES. The indicated server cannot
be discarded on the managed server because server
name is in use. This could occur if the managed server
has an active connection to server name or if the
managed server has a device class with
DEVTYPE=SERVER that refers to server name.
System action: Server server name is not deleted.
User response: Before server name can be deleted, the
managed server must not have a connection to that
server and the managed server cannot have any
device-class references to that server.
ANR3237W
Server server name is the event server


DISCARDOBJECTS=YES. The indicated server cannot
be discarded because it is the event server for the
managed server.
System action: Server server name is not deleted.
DELETE EVENTSERVER command must be used to
remove the event server reference to server name.

301
ANR3238E ANR3354W
ANR3238E
command: This object cannot be renamed

because it is associated with one or
more configuration profiles.
Explanation: This message is issued on a

configuration manager when an attempt is made to
rename an object that is associated with one or more
configuration profiles. Associated objects cannot be
renamed because the enterprise configuration facility
does not support renaming of objects.
User response: If you must change the object name
you can delete the object, define it with a new name,
and then define a profile association to the new object
(unless a wildcard profile association already exists).
This will cause the object to be deleted and re-defined
on managed servers with subscriptions to the profiles
with which this object is associated.
ANR3239E
Error rc while creating device class device

class.
Explanation: This message is issued when a device

class could not be created, because there was an error
while processing the device configuration file.
User response: Look in the device configuration file
for errors, and look at the activity log for any previous
error messagess that might help determine the location
of these errors in the device configuration file.
ANR3350W
Locally defined domain domain name

contains at least one node and cannot be
replaced with a definition from the
Explanation: During configuration refresh processing

the indicated locally defined domain could not be
replaced with a definition from the configuration
manager. The domain definition was not replaced
because the domain still contains one or more assigned
nodes.
System action: Refresh processing continues, but this
domain is not replaced. The system will attempt to
replace the local domain during later configuration
refresh operations.
User response: If you want existing nodes to be
assigned to the domain from the configuration
manager, you can temporarily assign them to another
domain. After the domain definition has successfully
been propagated from the configuration manager,
reassign the nodes to the new domain. Alternatively, if
you want to prevent further attempts to replace the
local domain definition during configuration refresh
processing, delete the subscription to the profiles with
302
ANR3351W
Managed domain domain name contains

at least one node and cannot be deleted
during configuration refresh processing.
Explanation: During configuration refresh processing,

the enterprise configuration facility attempted to
remove the indicated domain because it has been
deleted from the configuration manager or because the
profile association no longer exists. The domain could
not be deleted on the managed server because it still
contains one or more nodes.
domain is not deleted. The system will attempt to
delete the domain during later configuration refresh
operations.
User response: Assign nodes in this domain to
another domain. Alternatively, you can delete the
subscription to the profiles with which domain domain
name is associated.
ANR3352I
Locally defined domain domain name

replaced during configuration refresh
processing.

a local domain definition was replaced with a
definition from the configuration manager. The system
also deleted all policy sets, management classes, copy
groups, and client schedules belonging to the locally
defined domain and added definitions from the
ANR3353I
Managed domain domain name deleted


the indicated managed domain was removed from the
managed server. This occurred either because the
domain has been deleted from the configuration
manager or because the profile association no longer
exists. The system also deleted all policy sets,
management classes, copy groups, and client schedules
belonging to the managed domain.
ANR3354W
Locally defined administrative schedule

replaced with a definition from the

the indicated locally defined administrative schedule
could not be replaced with a definition from the
configuration manager. The schedule definition was not
replaced because the schedule is in the active state.
ANR3355W ANR3359W
administrative schedule is not replaced. The system
will attempt to replace the local administrative
schedule during later configuration refresh operations.
removed from the managed server. This occurred either

because the schedule has been deleted from the
configuration manager or because the profile
association no longer exists.
User response: If you want this administrative

schedule to be replaced with the schedule definition
from the configuration manager, deactivate the local
schedule using the Update Schedule command. After
the administrative schedule definition has successfully
been propagated from the configuration manager, you
can activate the new schedule. Alternatively, if you
want to prevent further attempts to replace the local
schedule definition during configuration refresh
which the schedule name is associated.
ANR3355W

deleted during configuration refresh
processing.

remove the indicated administrative schedule because it
has been deleted from the configuration manager or
because the profile association no longer exists. The
schedule could not be deleted on the managed server
because the schedule is in the active state.
schedule is not deleted. The system will attempt to
delete the administrative schedule during later
configuration refresh operations.
User response: If you want this administrative
schedule to be deleted in accordance with changes that
have been made on the configuration manager,
deactivate the managed schedule using the Update
Schedule command. Alternatively, if you want to
prevent further attempts to delete the managed
schedule definition during configuration refresh
which the schedule name is associated.
ANR3356I
Locally defined administrative schedule

schedule name replaced during
configuration refresh processing.

a local administrative schedule definition was replaced
with a definition from the configuration manager.
ANR3357I

schedule name deleted during

ANR3358W
Locally defined administrator

administrator name is the only system
administrator and cannot be replaced
with a definition from the configuration
manager.

the indicated locally defined administrator could not be
replaced with a definition from the configuration
manager. The administrator definition was not replaced
because it is the only system administrator and the
definition from the configuration manager does not
include system authority.
administrator definition is not replaced. The system
will attempt to replace the local administrator
definition during later configuration refresh operations.
User response: If you want this administrator
definition to be replaced with a definition from the
configuration manager, you can grant system authority
to another administrator. Alternatively, if you want to
prevent further attempts to replace the local
administrator definition during configuration refresh
which administrator administrator name is associated.
ANR3359W
Managed system administrator

administrator and cannot be deleted

remove the indicated administrator because it has been
profile association no longer exists. The administrator
could not be deleted on the managed server because it
is the only system administrator.
administrator is not deleted. The system will attempt to
delete the administrator during later configuration
refresh operations.
User response: Grant system authority to another
administrator. Alternatively, you can delete the
subscription to the profiles with which administrator
administrator name is associated.

the indicated managed administrative schedule was
303
ANR3360W ANR3366I
ANR3360W
Managed system administrator

administrator - authority cannot be
revoked during configuration refresh
processing.

the enterprise configuration facility attempted to revoke
authority for the indicated administrator because
authority has been revoked on the configuration
manager. The authority of the administrator could not
be revoked on the managed server because this is the
only system administrator.
System action: Refresh processing continues, but
authority is not revoked for this administrator. The
system will attempt to revoke administrator during
later configuration refresh operations.
User response: Grant system authority to another
administrator. Alternatively, you can delete the
subscription to the profiles with which administrator
administrator name is associated.
ANR3361I
Locally defined administrator

administrator name replaced during

a local administrator definition was replaced with a
definition from the configuration manager.
ANR3362I

name deleted during configuration
refresh processing.

administrator is not deleted. The system will attempt to
delete the administrator during later configuration
refresh operations.
User response: Quit or cancel all sessions for the
indicated administrator. Alternatively, you can delete
the subscription to the profiles with which
administrator administrator name is associated.
ANR3364W
Administrator administrator name has

been removed. This administrator has
defined or updated administrative
schedules that will fail when executed.
Explanation: This message is issued during

configuration refresh processing or as a result of a
DELETE SUBSCRIPTION command with the
DISCARDOBJECTS=YES option. The indicated
managed administrator was removed from the server,
but this administrator owns one or more administrative
schedules. These schedules will fail when executed in
the future because they do not belong to a valid
administrator.
System action: The indicated administrator was
removed.
OR an SQL SELECT statement on the
ANR3365I
Locally defined command script

command script name replaced during

the indicated managed administrator was removed
from the managed server. This occurred either because
the administrator has been deleted from the

a local command script definition was replaced with a

ANR3366I
ANR3363W

name is currently accessing the server
and cannot be deleted during

remove the indicated administrator because it has been
profile association no longer exists. The administrator
could not be deleted on the managed server because it
currently has an active session with the server.
304
Managed command script command script

name deleted during configuration
refresh processing.

the indicated managed command script was removed
from the managed server. This occurred either because
the script has been deleted from the configuration
exists.
ANR3367I ANR3375W
ANR3367I
Locally defined option set option set name

processing.

a local option set definition was replaced with a
ANR3368I
Managed option set option set name

processing.

the indicated managed option set was removed from
the managed server. This occurred either because the
option set has been deleted from the configuration
exists.
definition with the same name already exists on the

managed server.
server group is not defined. The system will attempt to
define the server group during later configuration
refresh operations.
User response: You can delete the subscription to the
profile with which the indicated server group is
associated or delete the conflicting server definition on
the managed server. Alternatively, you can rename the
server group on the configuration manager, after first
deleting the profile association for that server group.
ANR3372I
Locally defined server server name

processing.

a local server definition was replaced with a definition
from the configuration manager.
ANR3369I
Locally defined server group group name

processing.

a local server group definition was replaced with a
ANR3370I
Managed server group group name

processing.
ANR3373I
Server server name deleted during


the definition for managed object server name was
removed from the managed server. This occurred either
because server name has been deleted from the
ANR3374I
Server group group name replaced with

server server name during configuration
refresh processing.

the indicated managed server group was removed from
the managed server. This occurred either because the
server group has been deleted from the configuration
exists.

a server group definition was replaced with a server
definition from the configuration manager. The server
has the same name as the deleted server group.
ANR3371W
Server group group name cannot be

defined during configuration refresh
processing because a server already
exists with this name.

the enterprise configuration facility attempted to define
the indicated server group on a managed server. The
server group could not be defined because a server
ANR3375W
Server server name is currently in use

cannot be deleted during configuration
refresh processing.

remove the indicated server definition because it has
been deleted from the configuration manager or
indicated server could not be deleted on the managed
305
ANR3376W ANR3474I
server because server name is in use. This could occur if
the managed server has an active connection to server
name or if the managed server has a device class with
DEVTYPE=SERVER that refers to server name.
server definition is not deleted. The system will attempt
to delete the server during later configuration refresh
operations.
managed server must not have a connection to that
server and the managed server cannot have any
device-class references to that server.
ANR3376W
Server server name is the event server

and cannot be deleted during

remove the indicated server definition because it has
been deleted from the configuration manager or
indicated server could not be deleted on the managed
server because it is the event server for the managed
server.
server definition is not deleted. The system will attempt
to delete the server during later configuration refresh
operations.
DELETE EVENTSERVER command must be used to
remove the event server reference to server name.
ANR3377W
Replacement of local server server name

with a definition from the configuration
manager is not allowed.

replace the indicated server definition with a definition
from the configuration manager. This operation could
not be performed because ALLOWREPLACE=NO for
the indicated server.
server definition is not replaced. The system will
attempt to replace the server definition during later
configuration refresh operations.
User response: Before the local server definition for
server name can be replaced with a definition from the
configuration manager, the UPDATE SERVER
command must be used to set the ALLOWREPLACE
attribute to ON.
ANR3470I
Command: Auditing enterprise

configuration definitions.
Explanation: The server has started to audit database

definitions used by the enterprise configuration facility.
continues.
ANR3471E
Audit command: Enterprise configuration

global attributes are missing.
Explanation: A database audit process finds that the

global attributes used by the enterprise configuration
facility are missing.
FIX=YES specified so that the enterprise configuration
global attributes can be recreated.
ANR3472I

global attributes are missing - attributes
will be recreated using available
database information or default values.

facility are missing. Because FIX=YES has been
specified on the AUDIT command, these attributes will
be recreated using available information from the
database or default values.
User response: When the audit completes, you can
use the QUERY STATUS command to examine the
values set for the enterprise configuration global
attributes. Then use the appropriate SET command to
change the attributes, if desired.
ANR3473E

global attribute(s) are incorrect.
Explanation: A database audit process finds that

facility are incorrect.
FIX=YES specified so that the enterprise configuration
global attributes can be corrected.
ANR3474I

global attribute(s) are incorrect attributes will be corrected using
available database information or
default values.
306
ANR3475E ANR3483E
facility are incorrect. Because FIX=YES has been
specified on the AUDIT command, these attributes will
be corrected using available information from the
database or default values.
values set for the enterprise configuration global
attributes. Then use the appropriate SET command to
change the attributes, if desired.
ANR3475E
Audit command: Extraneous profile

information found.
Explanation: A database audit process finds

extraneous configuration profile information.
FIX=YES so that the information is deleted.
ANR3476E

information found - information will be
deleted.

extraneous configuration profile information. Because
FIX=YES has been specified for the audit command, the
extraneous information will be deleted.
ANR3477E
Audit command: Profile information is

inconsistent.
ANR3479E
Audit command: Profile association

information is missing.
Explanation: A database audit process detects missing

profile association information. This information can be
recreated.
FIX=YES so that the information can be recreated.
ANR3480E
Audit command: Profile association

information is missing - it will be
recreated.

profile association information. Because FIX=YES has
been specified for the audit command, the information
will be recreated.
ANR3481E

association information found.

extraneous profile association information.
FIX=YES so that the information is deleted.
ANR3482E

association information found information will be deleted.
Explanation: A database audit process detects

inconsistent configuration profile information. This
information can be corrected.

extraneous profile association information. Because

FIX=YES so that the information can be corrected.

ANR3483E
ANR3478E
Audit command: Profile information is

inconsistent - it will be corrected.

inconsistent configuration profile information. Because
information will be corrected.
Audit command: Subscription information

is inconsistent.

inconsistent profile subscription information. This
FIX=YES so that the information can be corrected.
307
ANR3484E ANR3505I
ANR3484E
Audit command: Profile subscription

information is inconsistent - it will be
corrected.

inconsistent profile subscription information. Because
information will be corrected.
User response: Evaluate other server messages for an

indication of why the files where skipped. Files can be
skipped because of failures locking those files, having
no files to process, or for other more serious problems.
First, retry the command and see if it completes
without any skipped files. If you are unable to generate
the backup set without skipping files, please contact
your local service representative for assistance.

ANR3485E
Audit command: Profile subscriptions

were found to more than one
Explanation: A database audit process determines that

a managed server has subscriptions to more than one
configuration manager. This may cause the enterprise
configuration facility to behave in an unpredictable
manner.
User response: Delete subscriptions for all but one
configuration manager. To do this, it may be necessary
to delete subscriptions to all configuration managers
and then define the desired subscriptions.
ANR3500I
Backup set for node node name as set

name (data type data type) being
generated.
Explanation: The named object set is being created for

the specified node.
System action: The server generates a backup set.
ANR3501I
Backup set for node name as set name

(data type data type) completed
successfully - processed files files.
Explanation: The named object set was successfully

created for the specified node. The number of files
processed is specified.
ANR3502W

(data type data type) completed with file
processing errors - processed files files
with error files files skipped.
Explanation: The named object set was successfully

created for the specified node. However, during
processing errors were encountered accessing some files
- these files were skipped.
308
ANR3503E
Generation of backup set for node name

as set name (data type data type) failed.
Explanation: The named object for the specified node

was not created. An error was encountered causing the
creation of this object set not to complete successfully.
User response: Evaluate other messages that were
issued and try to determine the cause of the failure.
After determining the cause of the failure, retry the
command. If the cause can not be determined, please
contact your local service representative.
If ANR3504W was received, than an error occurred
while logging the volumes used to the server volume
history. It is possible to issue a DEFINE BACKUPSET
listing these volumes. That would cause the server to
create the necessary entries for this backup set on this
server.
ANR3504W
Backup set for node name as set name was

not able to log the volumes used for this
operation to the server volume history.

was created. However, when the process attempted to
add the volumes, used for this operation to the volume
history for the server, an error occurred and this could
not be completed.
User response: Review other messages issued to
determine which volumes where used for to generate
this backup set. The volumes can be inserted into the
server volume history for use by issuing a DEFINE
BACKUPSET and listing these volumes. This will also
allow this backup set to be queried from a client as
well since there is not a server entry for this backup
set. Only issue the DEFINE BACKUPSET if this
generate backup set operation completed successfully.
ANR3505I

used volume volume name.

used the specified volume.
ANR3507I ANR3515E
ANR3507I
Cancel in progress

a QUERY PROCESS command, and indicates that a
generate backupset process has been canceled. The
process will end shortly.
System action: The process terminates and server
ANR3508W

as set name (data type data type) failed no filespaces to process.

was not created. No filespaces were available to
process.
User response: Reissue the command against a node
that has filespaces associated with it. If no filespaces
exist for a given node, than there is no file data to
write to the backupset.
ANR3509E

data storage - device class device class

an error occurred because the specified device class is
not defined.
User response: Make sure the specified device class is
defined.
ANR3510E

data storage - disk volume specified.

an error occurred because a specified volume is a disk
volume rather than a tape volume.

volume name.
ANR3512E

data storage - insufficient number of
media.

the server cannot allocate sufficient mount points.
available.
ANR3513E
Command: Output error encountered in

Explanation: The command command operation ends

because an error has been encountered by the server in
writing to a device. Possible reasons include:
v I/O error writing to a device
v No storage space.
preceding this one to determine the cause of the error.
After the problem is corrected, the command can be
retried.
ANR3514E
Command: Data transfer was interrupted


command command operation failed because data
external event.


interrupted. Reissue the command command after the
problem is resolved.
User response: Make sure that all volumes specified

for the command command are tape volumes.
ANR3515E
ANR3511E

data storage - invalid volume name
specified.

accessing data storage while processing command
command. The error occurred because an attempt has
been made to access a volume with an invalid name.


export, database dump, or database backup operation
(as recorded in the volume history) or is in use by
another process.
309
ANR3516E ANR3522W
previously used for an export, database dump, or
volumes that have been used for export, database
ANR3516E

mounted.

writing to the sequential media. Command command
media for storing data and SCRATCH=NO has been
specified on command command.
System action: Command command processing ends.
SCRATCH=YES or specify additional volume names on
the command.
ANR3517E

data storage - required volume was not
mounted.

ANR3520E
Command: Internal error encountered in


in accessing data storage while processing command
command operation.
found and resolved, reissue the command command
operation. If the failure cannot be found, contact your
service representative for assistance in resolving the
problem.
ANR3521W
BackupSet command: Data storage retrieve

or restore failed - error detected.
Explanation: The server ends an backup set operation

because an error has been encountered on the server.
Some common reasons for the error are:

required volume cannot be mounted. The mount
request may have been canceled.


sure the necessary volumes are accessible.
System action: The server ends the backup set

operation and continues operation.
ANR3518I

completion.

message.
ANR3519E
Command: Insufficient memory available

Explanation: The server encounters a memory

shortage in accessing data storage during command
command operation.
310


ANR3522W
Command: Retrieve or restore failed - file

was deleted from data storage during
retrieval.

for the specified command because the file has been
System action: The server ends the command and
ANR3523W ANR3529W
Reissue the command after these processes have been
completed or canceled.
ANR3523W
Backup set command: Retrieve failed error on input storage device.
Explanation: The server ends a backup set operation

for the specified session because an I/O error has been
encountered by the server in reading from a device.
The object for which the I/O was issued is reported in
a later message.
ANR3526E
Explanation: During backup set processing, a volume

has been mounted but cannot be used.
System action: The backup set operation is ended and
User response: Query the activity log for messages
preceding this one that give additional information.
Make sure a usable volume is specified and mounted.
ANR3527E
System action: Backup set processing skips this file,

to be shut down with the HALT command to correct
the hardware problem.
ANR3524W
Backup set command: Transaction failed data transfer interrupted.

a backup set operation failed because data transfer to
or from data storage was interrupted by an external
event.
System action: The backup set operation is ended and
interrupted. Attempt the backup set operation again
after problem is resolved.
ANR3525W
Backup set command: Transaction failed storage media inaccessible.

backup set operation because storage volumes are not
available in the storage pools in which the client files
are to be stored.
Backup set command: Error encountered in

accessing data storage - volume cannot
be used.
Backup set command operation terminated

- it is acting on an empty volume or
volume content is not as expected.
Explanation: The volume content this command is

acting upon is not as expected, the volume is empty, or
the volume cannot be found.
System action: The command operation is ended.
sure the expected content is in the volumes or the
volume is not empty and exists.
ANR3528E
Backup set command: Media not accessible

Explanation: The server ends a transaction for a

backup set operation because storage volumes are not
available in the storage pools in which the client files
are to be stored.
ANR3529W
Generate backupset skipping damaged

name, fsId filespace id, File name file name.
Explanation: The backup set generation process

encountered a file that was previously found to be
damaged. The process encountered the file during a
sequential scan of all files on the storage pool volume;
the indicated file may or may not have been a
candidate for inclusion in the backup set.
If this file is part of an aggregate, it may have been
previously marked as damaged because an integrity
error was detected in some other file within the same
aggregate. AUDIT VOLUME can determine if this is the
case, and if so, will reset the damaged state for the file.
311
ANR3530E ANR3537E
System action: The damaged file is not added to the
backupset.
FIX=NO to determine if the file is actually damaged.
The audit will reset the files damaged state if the file is
not damaged. (If the file is part of an aggregate, and
none of the files within the aggregate are damaged, the
audit will also reset the entire aggregates damaged
state.)
If the file remains in the damaged state after the audit
completes, attempt to restore the damaged file by using
the RESTORE STGPOOL command. Note, however,
that this is only an option if the damaged file is in a
primary storage pool that had been previously backed
up to a copy storage pool.
If the audit resets the files damaged state, or the
damaged file was successfully restored using RESTORE
STGPOOL, and it is important for this file be included
in the backup set, then rerun the GENERATE
BACKUPSET command to generate a new backup set
containing the file.
ANR3530E
Audit command: A missing, incorrect, or,

invalid collocation group has been
detected.
ANR3533E

or incorrect information for a collocation group.
Because FIX=YES has been specified for the audit
command, the error will be corrected.
ANR3534E
User response: Issue the audit command again, and

specify FIX=YES so that the error can be corrected.
ANR3531E
Audit command: A missing or incorrect

collocation group has been detected; it
will be corrected.
Explanation: A database audit process found a

missing, incorrect, or invalid collocation group. Because
error will be corrected.
Audit command: Missing or incorrect

collocation group name for collocation
group id collocation group id has been
detected.
Explanation: A database audit process finds a missing

or incorrect collocation group name.
ANR3535E

missing, incorrect, or invalid collocation group.

collocation group id detected for
collocation group name - it will be
corrected.

collocation group name has been
detected for collocation group id
collocation group id - it will be corrected.

or incorrect information for a collocation group.
ANR3536E
Audit command: Inconsistent information

detected in collocation group
(Aggregate.ID).

inconsistent information for a collocation group. This
problem cannot be corrected by the audit process.
ANR3532E

collocation group identifier for
collocation group collocation group name
has been detected.
Explanation: A database audit process detects an

invalid, missing, or incorrect collocation group
identifier.
User response: Issue the audit command again and
312

ANR3537E

collocation group member has been
detected for collocation group ID
collocation group ID.
Explanation: A database audit process detects a

missing or incorrect member for a collocation group.
ANR3538E ANR3544E
ANR3538E

collocation group member has been
detected for collocation group id
collocation group id - it will be corrected.
Explanation: A database audit process detects a

missing or incorrect member for a collocation group.
Explanation: An error occurred while opening the

indicated object set.
System action: An error is returned to the client.
User response: Correct the problem reported by
previous messages, if possible.
ANR3542E

ANR3539E

as set name (data type data type) skipped
shreddable data object.

it generating.
Explanation: An error occurred while reading the

indicated object set.
User response: Correct the problem reported by
previous messages, if possible.
ANR3543E
Data retrieved from a shreddable storage pool was

skipped because the ALLOWSHREDDABLE=YES
parameter was not specified.
System action: Server operation is terminated.
User response: Check with your Storage
Administrator to ensure data retrieved from a
shreddable storage pool is a candidate for storing on a
backupset. Data stored on backupsets cannot be
shredded. Only data that resides in a shreddable
storage pool can be shredded. Check whether your
Storage Administrator allows shreddable data to be
stored on backupsets. Restart the operation and specify
the ALLOWSHREDDABLE=YES parameter.
A shreddable storage pool is a storage pool that has
been defined with a non zero SHRED attribute.
Alternatively, the storage pool from which the
backupset data is retrieved can be updated as a non
shreddable storage pool. This requires the storage pool
SHRED attribute to have a value of zero. Backupsets
generated from data retrieved from non shreddable
storage pools do not require the
ALLOWSHREDDABLE=YES parameter.
ANR3540E
Object set set node:set name:data type was

not found for session session number,
node.
Explanation: The indicated session id requested to

restore the object set. The object set was not found on
the server.
System action: The error is returned to the client.
ANR3541E
Error error code occurred reading object

set set node:set name:data type for session
session number, node.
Error error code occurred while sending

entries from object set set node:set
name:data type for session session number,
node.
Explanation: An error occurred while sending entries

for the indicated object set.
User response: Correct the problem reported by other
prior or subsequent messages related to this session,
and try the operation again.
ANR3544E

as set name (data type data type) skipped
shreddable data object in file space
filespace name (fsId filespace id), file name
file name, type file type.
Explanation: The named data object for the specified

node was skipped while generating a backupset.
The data object resides in a shreddable storage pool
and will not be included in the backupset because the
ALLOWSHREDDABLE=YES parameter was not
specified.
System action: Backupset generation continues.
User response: Check with your Storage
Administrator to ensure data residing in a shreddable
storage pool is a allowed to be stored on a backupset.
Data stored on backupsets cannot be shredded. Only
data that resides in a shreddable storage pool can be
shredded. If your Storage Administrator allows
shreddable data to be stored on backupsets, then restart
the operation and specify the
ALLOWSHREDDABLE=YES parameter.
Error error code occurred opening object

set set node:set name:data type for session
session number, node.
313
ANR3547I ANR3606E
ANR3547I
Backup set set name used volume volume

name.
Explanation: The named object used the specified

volume.
ANR3550E
Definition of backup set set name for

node name failed because it has an
unknown format.

was not defined. It was generated on a server that is at
a higher level than this server and contains data that
cannot be properly interpreted by this server.
User response: Define the object on a server that is
compatible with the server that generated the object, or
upgrade this server to be compatible with the server
that generated the object.
ANR3601W
Policy Domain release failed for domain

domain id due to communications failure.
Explanation: The storage agent was attempting to

inform the database server that it was finished with the
domain indicated by the domain id, but was unable to
communicate with the database server. The cached
policy information will be cleaned up when the storage
server terminates or re-starts or when the database
server re-starts.
System action: The storage agent continues operation.
The policy information is deleted from the storage
agent policy cache.
User response: Policy caches are cleaned up on the
storage agent or server re-start. Network
communication between the storage agent and database
server should be checked.
ANR3602E
Unable to communicate with database

server.

communicate with the database server but was unable
to do so.
System action: The storage agent operation fails.
User response: Check the configuration of the storage
agent and server to ensure that communication
parameters are correct. Ensure that the database server
is running and is accepting messages.
314
ANR3603E
Storage AgentStorage Agent name was

unable to load policy information due to
a protocol error.
Explanation: While receiving policy information from

a database server, processing ended prematurely
because of a protocol error.
System action: Server operation continues. Policy is
loaded from the database server database.
User response: If this problem persists, contact your
ANR3604E
This command is not supported in the

current operating environment.
Explanation: A command was issued that is valid

under most circumstances, but not in the current server
environment.
User response: Issue commands which are allowed in
the current environment.
ANR3605E
Unable to communicate with storage

agent.
Explanation: The database server was attempting to

communicate with the storage agent but was unable to
do so.
System action: The database server operation fails.
parameters are correct.
ANR3606E
The storage agent was communicating

with the database server on a restore
request with verb verb name and
received return code return code.
Explanation: The storage agent and database server

were coordinating a restore request. While
communicating using the indicated verb ( an internal
request mechanism between the storage agent and
database server ), an unexpected return code was
received. The verb name and return code are provided
for Tivoli support personnel.
System action: Database server and storage agent
continue. The restore request fails, but may be retried
by the client.
parameters are correct. If this problem persists, contact
ANR3607E ANR3999E
ANR3607E

with the client on a restore request with
verb verb name and received return code
return code.
Explanation: The storage agent was communicating

with a client for a restore request. While
communicating using the indicated verb ( an internal
request mechanism between the storage agent and
client ), an unexpected return code was received. The
verb name and return code are provided for Tivoli
support personnel.
continue. The restore request fails, but may be retried
by the client.
agent and client to ensure that communication
parameters are correct. If this problem persists, contact
ANR3608E

with the database server on a restore
request. An unexpected request (id verb )
was received from the database server.
Explanation: The storage agent and database server

were coordinating a restore request. While
communicating, the indicated verb ( an internal request
mechanism between the storage agent and database
server ), was unexpected. The verb number is provided
for Tivoli support personnel.
continue. The restore request may fail, but may be
retried by the client.
User response: If this problem persists, contact your
ANR3609E
The storage agent was handling a

restore request. A failure occurred in
starting a new thread. The return code
return code from the failing routine may
be useful to Tivoli service.
Explanation: The storage agent was handling a restore

request. A new thread could not be started. Without the
new thread the request could not be handled.
continue. The restore request has failed.
User response: Ensure that there is sufficient system
memory for the storage agent to operate properly.
Insufficient memory or paging/swap space can cause
problems in starting threads. If this problem persists,
ANR3610I
Domain Identifier domain identifier was

not found.
Explanation: The server was cleaning up cached

policy information after a restore request. A domain
with the indicated identifier was not found in an
internal list.
continue.
User response: No response is required if the message
is the result of starting a storage agent. The storage
agent requests that the server purge cached information
that it was using previously. It is possible that
information tracking policy caching has become stale.
In this case, no response is required. If the message
occurs without a storage agent connecting to the server,
ANR3611E
Storage Agent unable to contact server.

contact the server to start a session or run a command.
The storage agent was unable to contact the server to
start a transaction.
System action: The storage agent continues
processing. The server may be down or there may be a
communications problem.
User response: No response is required if the message
is the result of stopping a server. Ensure that the server
with which the storage agent communicates is running
and that there is connectivity between the systems. The
server must be restarted before you can start a new
administrator session with the storage agent.
ANR3612E
This command is not supported in the

Express environment.
Explanation: A command was issued that is valid

under most circumstances, but not in the current server
environment.
User response: Issue commands which are allowed in
the current environment.
ANR3999E
Failure validating database load:

expected numRecs records and numBV bit
vectors - loaded actNumRecs records and
actNumBV bit vectors.
Explanation: The database load process has ended

and the number of records, the number of bit vectors,
or both the number of records or number of bit vectors
loaded, failed to validate.
System action: The LOAD DB process completes with
a failure. The server database is not in a usable state.
User response: A number of possible causes exist. To
315
ANR4000I ANR4009E
recover from this situation, first retry the database load
process. If the error reoccurs, check the activity log or
other system logs to determine if there is a hardware or
media error. If a hardware or media error exists, correct
the error and retry the load process. If a hardware or
media error does not exist, it is likely the dump or
unload of the server database has encounted an error
resulting in the dump/unload server database image as
being unusable or that there is an error in the logic for
load db processing. Contact your service representative
for assistance.
ANR4000I
Dump command: Database dump process

started.
Explanation: The database dump process has started.

System action: The server dumps the contents of the
database to a file or removable media.
ANR4005E
Load command: Database load process

terminated due to error (error indicator).
Explanation: The database load process has ended

prematurely due to an error.
System action: The server ends load processing.
User response: Examine previously issued messages
to determine if an error can be corrected, such as a
syntax error. If you cannot resolve the error, contact
ANR4006I
Command: Volume volume number written

by process is volume name.
Explanation: A sequential data process wrote to the

volume named in the series of one or more volumes
that were used to store output. The volumes position
in the series in indicated by the volume number
reported.
System action: The server ends processing.
ANR4001I

completed.
Explanation: The database dump process has ended.

ANR4007E
System action: The server completes processing.

ANR4002I

terminated due to error (error indicator).
Explanation: The database dump process has ended

prematurely due to an error.
System action: The server ends dump processing.
to determine if an error can be corrected, such as an
output error. If you cannot resolve the error, contact
ANR4003I

started.
Explanation: The database load process has started.

System action: The server loads the contents of the
database from a file or removable media.
ANR4004I

completed.
Explanation: The database load process has ended.

System action: The server completes processing.
Command: A transaction error was

encountered in recording volume usage
history.
Explanation: The command process encounters a

database transaction error in recording the names of the
volumes used for the process in the server database.
System action: The server ends processing.
to determine if there is an error that can be corrected,
such as a syntax error. If you cannot resolve the error,
contact your service representative. The volumes used
by the process are valid for the corresponding input
process, but are not recorded in sequential volume
history lists generated by the server.
ANR4008W
Load command: Database object object

name does not exist.
Explanation: The database load process attempts to

delete a database object, but the object does not exist.
System action: Database processing continues.
ANR4009E
Load command: Database object object

name cannot be deleted because it is in
Explanation: The database load process attempts to

delete a database object, but the object is currently
being used by another process.
System action: Database processing ends.
User response: Reissue the command. If it fails,
316
ANR4010E ANR4017E
ANR4010E
Dump/load command: Database dump/load

processing failed - insufficient memory.
Explanation: The database dump/load process fails

due to insufficient memory.
System action: Database processing ends.
server. There are two ways to do this:
v Increase the size of the servers virtual machine (for
VM), or region size (for MVS). For AIX, ensure that
there is sufficient paging space. You may also use
SMIT to determine if the number of applications is
causing a memory shortage. For OS/2, ensure that
there is sufficient space for the OS/2 SWAPPER.DAT
file. Check your CONFIG.SYS for the SWAPPATH
statement to determine where your SWAPPER.DAT
file is located and then determine how much space is
left on the drive.
v Decrease the amount of space allocated to the
servers database or log buffer pool. To do this,
update the value of the BUFPOOLSIZE or
LOGPOOLSIZE parameters in the server options file
and restart the server. Note that each page causes an
additional 4K page to be allocated for the specified
buffer pool. Reducing the pool sizes requires more
I/O to service the same amount of data; some
performance degradation may result.
ANR4014E
Explanation: The specified volume does not contain a

dump created from the database dump command.
System action: Processing ends.
ANR4015E

error. On MVS or VM, the LOADDB command syntax
may be specified by using a ddname or by specifying a
device class name. You must use the same method that
was used when the database was originally dumped. If
you did not, this error message will be displayed. Try
loading the database by using the other method of
syntax (devclass). If the error cannot be isolated and
Dump command: Database page page

number is invalid - it will be skipped.
Explanation: The specified page is invalid, and it will

not be used during dump processing.
Load command: Invalid record format

(format code) detected.
Explanation: During processing of command load

command, an invalid record type is detected when
reading the dumped information from the dump
media.
ANR4016E
ANR4011W
Load command: The specified input

volume does not contain a server
database dump.
Load command: Invalid header sequence

number detected in database dump.
Expected expected sequence number; Actual
actual sequence number.
Explanation: During processing of command load

command, an invalid sequence number is detected when
reading the dumped information from the dump
media.
ANR4012W
Dump command: Database page page

number is damaged.
Explanation: The specified database page is damaged;

it will not be dumped.
ANR4013I
Dump command: Dumped number of

entries database entries (cumulative).
Explanation: This message indicates the number of

database entries that have been dumped so far during
database dump processing.
User response: Examine previously issued server

messages to determine the source of the error. If the
error cannot be isolated and resolved, contact your
ANR4017E
Load command: Invalid record type record

type read from database dump data.
Explanation: The server database load process

encounters an invalid record in reading data from the
dump media.
System action: The database load process ends.
User response: Examine previously issued server
messages to determine the source of the error. If the
317
ANR4018E ANR4028I
ANR4018E
Load command: Load processing failed insufficient recovery log space.
ANR4023E
Load command: Error (error code) occurred

during a read operation.
Explanation: The load process fails due to insufficient

recovery log space.
Explanation: The server database load process

encounters an error reading from the dump media.
System action: Database load processing ends.
System action: The database load operation ends.
User response: Reinstall the server and specify a

larger recovery log and reissue the database load
command.

to determine why the operation failed; correct the
problem and restart the process.
ANR4019E
Load command: Load processing failed insufficient database space.
ANR4025I
Explanation: The load process fails due to insufficient

database space.
System action: Load processing ends.
User response: Reinstall the server and specify a
larger database and reissue the database load
command.
ANR4020E
Load command: Batch database insert

failed.
Explanation: The database load process fails when it

attempts to insert a batch of rows into the database.
System action: Database load processing ends.
this one to determine if an error can be corrected. You
may wish to reinstall the server with a new recovery
log and database and reissue the load command. If the
Dumped number of pages database pages,

number of bit vectors bit vectors, and
number of database entries database entries;
number of bad pages bad database pages
have been encountered; number of bytes
copied.

a QUERY PROCESS command executed against an
online database dump process. The message displays
information about the progress of the dump.
System action: Database dump processing continues.
User response: None. You may cancel the dump
process with the CANCEL PROCESS command.
ANR4026I
Dump command: Process process number,

database dump has completed.
Explanation: The online server database dump process

started as process process number has completed.
System action: Database dump processing ends.
ANR4021E
Dump/load command: Error (error code)

occurred during an open operation.
Explanation: An error occurs while attempting an

open operation on the dump media for a database
dump/load operation.
ANR4027I
Explanation: The online server database dump process

started as process process number has been canceled
with the CANCEL PROCESS command.
System action: Database dump processing ends.
ANR4028I
ANR4022E
Dump command: Error (error code)

occurred during a write operation.

database dump was canceled.

Database dump terminated due to an
error (error code).
Explanation: The server database dump process

encounters an error while writing to the dump media.
Explanation: The online database dump process has

ended prematurely due to an error.
System action: Server processing continues, the dump

processing ends.
System action: The server ends dump processing.

318

this message to see if an error can be corrected, such as
output error. If you cannot resolve the error, contact
ANR4029I ANR4039I
ANR4029I
Dump command: Database checkpoint

started.
Explanation: The database dump process is flushing

updated database pages from the database buffer pool
to stable storage so that they can be dumped.
System action: Database dump or load processing

ends.
ANR4035I
System action: Database dump processing continues.

ANR4030I
Dump command: Database checkpoint

completed.
Explanation: The database dump process has flushed

all updated pages from the database buffer pool to
stable storage.
Dump/load command: Encountered number

of bad database records bad database
records.
Explanation: This message is displayed at the end of a

server database dump or load command to indicate the
number of invalid database records that have been
encountered.
ends.
System action: Database load processing continues.

ANR4031I
Dump/load command: Copied number of

pages database pages.

number of database pages copied.
ANR4036I

database entries database entries.

number of database entries that have been copied.
ends.

ends.
ANR4037I
ANR4032I

records database records.

number of database records copied.
Dump/load command: number of bytes

copied.

number of bytes that have been copied.
ends.

ends.
ANR4038I
ANR4033I
Dump/load command: Copied number of bit

vectors bit vectors.

number of database bit vectors copied.
ends.
Load command: Loading database

information dumped on dump date at
dump time.
Explanation: At the beginning of a server database

load process, this message indicates the date and time
that the dump took place for the database information
that is loaded into the server.

ANR4039I
ANR4034I

of bad database pages bad database pages.

number of invalid database pages that have been
encountered.
Load command: Loaded number of entries

database entries (cumulative).

database entries that have been loaded so far during
database load processing.
319
ANR4040I ANR4047I
ANR4040I
Audit command: Auditing client node and

administrator definitions.

database audit and indicates that the client node and
administrator definitions are being examined by the
database audit process.
you may want to check the domain assignment for this

node, and reassign the node to a different policy
domain, if desired.
ANR4044I

ANR4041I
Audit command: Node node name is

assigned to Domain domain name, but
not verified by server database policy
entries.
Explanation: A database audit process finds a node

assigned to a policy domain that is not recorded
properly in policy database entries.
Explanation: A database audit process cannot find an

appropriate policy domain for assigning the specified
node.
User response: When the audit command completes,
use the UPDATE NODE command to assign the
specified node to an appropriate policy domain.
ANR4045I

User response: If FIX=YES has not been specified for
the audit command, you may want to run this
command again, and specify FIX=YES so that the audit
process can correct the policy domain assignment for
the node.
ANR4042I
Audit command: Node node name is

assigned to Domain domain name, but
not found in server database policy
entries - attempting to assign the node
to domain domain name.

assigned to a policy domain that cannot be referenced
in database policy entries. Because FIX=YES has been
specified for the audit command, the audit function
will attempt to correct the policy domain assignment
for the node.
you may want to check the domain assignment for this
node, and reassign the node to a different policy
domain, if desired.
Audit command: Node node name
assignment failed - will attempt to
assign the node to domain domain name.

assigned to a policy domain that cannot be located in
database policy entries. Because FIX=YES has been
specified for the audit command, the audit function is
attempting to assign the node to an existing policy
domain. The function attempts to assign the node to
the domain name specified.
320
Audit command: Invalid compression

value encountered for node node name.
Explanation: A database audit process encounters an

invalid node compression value for the node indicated.
process can correct the problem.
ANR4046I
Audit command: Invalid compression

value encountered for node node name
the default value will be set.

invalid node compression value for the node indicated.
Because FIX=YES has been specified, the audit function
sets the nodes compression value to the default value.
User response: If you want the compression value for
the specified node to be set to a value other than the
default, use the UPDATE NODE command to change
the value after the audit command has completed.
ANR4047I
ANR4043I
Audit command: Could not assign Node

node name to a policy domain; use the
UPDATE NODE command to assign a
policy domain for this node.
Audit command: Invalid archive delete


invalid archive delete permission value for the node
indicated.
ANR4048I ANR4055I
ANR4048I
Audit command: Invalid archive delete


invalid archive delete permission value for the node
indicated. Because FIX=YES has been specified, the
audit function sets the nodes archive delete permission
value to the default value.
User response: If you want the archive delete value
for the specified node to be set to a value other than
the default, use the UPDATE NODE command to
change the value after the audit command has
completed.
ANR4049I
Audit command: Invalid backup delete


invalid backup delete permission value for the node
indicated.
ANR4050I
Audit command: Invalid backup delete


invalid backup delete permission value for the node
audit function sets the nodes backup delete permission
value to the default value.
User response: If you want the backup delete value
for the specified node to be set to a value other than
the default, use the UPDATE NODE command to
completed.
ANR4051I
Audit command: Invalid lock state

encountered for node node name.

invalid lock state value for the node indicated.
ANR4052I

encountered for node node name the
node will be unlocked.

invalid lock state value for the node indicated. Because
FIX=YES has been specified, the audit function sets the
nodes lock state to unlocked.
User response: If you want the lock state for the
specified node to be set to a value other than unlocked,
use the LOCK NODE command to change the value
after the audit command has completed.
ANR4053I
Audit command: Invalid Node conversion

state encountered for node node name.

invalid Node conversion state value for the node
indicated.
process can correct the problem. However, next time
this node logs onto the server, the node conversion
state will be reset.
ANR4054I
Audit command: Invalid conversion state

encountered for node node name the
node will be reset.

invalid conversion state value for the node indicated.
resets the conversion state.
ANR4055I

encountered for administrator
administrator name.

invalid lock state value for the administrator indicated.

321
ANR4056I ANR4063E
ANR4056I

encountered for administrator
administrator name the administrator will
be unlocked.
ANR4060I
Audit command: Administrative ID

assignments are incorrect - value(s) will
be corrected.

invalid lock state value for the administrator indicated.
sets the administrators lock state to unlocked.

global attributes used for server administrative
activities are incorrect. Because FIX=YES has been
specified on the AUDIT command, the attribute value
will be corrected in the server database.
User response: If you want the lock state for the

specified administrator to be set to a value other than
unlocked, use the LOCK ADMIN command to change
the value after the audit command has completed.
ANR4057E
Audit command: Administrative global

attributes are missing.

activities are missing.
FIX=YES specified so that the administrative global
attributes can be recreated.
ANR4058I

attributes are missing - default values
will be used to recreate the attributes.

activities are missing. Because FIX=YES has been
specified on the AUDIT command, default attribute
values will be used to recreate the administrative global
attributes.
values set for the administrative global attributes, and
use the appropriate SET command to change the
attributes, if desired.
ANR4059E
Audit command: Administrative ID

assignments are incorrect.

activities are incorrect.
attributes can be corrected.
322
ANR4061E

attribute(s) are incorrect.

ANR4062I

attribute(s) are incorrect - default values
will be set.

activities are incorrect. Because FIX=YES has been
specified on the AUDIT command, default attribute
values will be used to correct the administrative global
attributes.
ANR4063E
Audit command: Client node node number

not found in the server database.
Explanation: A database audit process finds a client

node reference that is not defined correctly in the
server database.
User response: If the audit command has not been
issued with FIX=YES specified, reissue the audit
function specifying FIX=YES so that the error can be
corrected.
ANR4064I ANR4071I
ANR4064I
Audit command: Client node node number

created as node node name assigned to
policy domain domain name in the server
database.

node reference that is not defined correctly in the
server database. Because FIX=YES has been specified
for the audit command, the audit function creates a
new node definition for the node with the name
specified.
User response: After the AUDIT command completes,
use the QUERY NODE command to examine the node
that was added. Use the RENAME NODE command to
rename the corrected node and the UPDATE NODE
command to set attributes for the corrected node, such
as its password. You can issue the QUERY FILESPACE
command for the node, to determine which node and
platform type was originally represented by the
corrected node.
ANR4065E
Audit command: Administrator

administrator number not found in the
server database.
Explanation: A database audit process finds an

administrator reference that is not defined correctly in
User response: Reissue the audit command and

ANR4068I
Audit command: Policy domain domain

name referenced by an administrator
authority does not exist - the authority
will be removed.
Explanation: A database audit process finds a policy

administrator reference to a policy domain that does
not exist. Because FIX=YES has been specified, the
authority will be removed.
User response: After the audit command completes,
review your administrator definitions with the QUERY
ADMIN command. You can then use the REGISTER
ADMIN, UPDATE ADMIN, and GRANT AUTHORITY
commands to change any definitions.
ANR4069E
Audit command: Storage pool storage pool

authority does not exist.
Explanation: A database audit process finds a storage

administrator reference to a storage pool that does not
exist.


ANR4070I
ANR4066I

administrator number not found in the
server database - reference will be
removed.

administrator reference that is not defined correctly in
the server database. The invalid reference will be
removed from the database.
ADMIN and UPDATE ADMIN commands to change
any definitions desired.
ANR4067E
Audit command: Domain domain name

referenced by an administrator authority
does not exist.

administrator reference to a policy domain that does
not exist.

authority does not exist - the authority
will be removed.

administrator reference to a storage pool that does not
exist. Because FIX=YES has been specified, the
authority will be removed.
ADMIN, UPDATE ADMIN, and GRANT AUTHORITY
commands to change any definitions.
ANR4071I
Audit command: Invalid sign-on attempts

is not valid for node/administrator name.

invalid sign-on attempts value that is not valid for the
node or administrator indicated.
323
ANR4072I ANR4081I
ANR4072I
Audit command: Invalid file aggregation

information encountered for node node
name.
Explanation: A database audit process encounters

invalid information used for controlling aggregation of
files for the node indicated.

ANR4077I
Audit command: Invalid client node count

detected for policy domain domain name
count will be corrected.

count of nodes recorded for the specified policy
domain do not match the actual number of nodes
assigned to the domain. Because FIX=YES has been
specified for the command, the node count will
automatically be corrected.
ANR4073I
Audit command: Invalid file aggregation

information encountered for node node
name - information will be corrected.
ANR4078E
Audit command: Invalid activation

indicators encountered for policy
domain domain name.

invalid information used for controlling aggregation of
files for the node specified. Because FIX=YES has been
specified, the audit function corrects the information.
Explanation: A database audit process finds incorrect

policy set activation entries for the specified policy
domain.

ANR4074I

of entries bad database entries.

number of invalid database entries that have been
encountered.
ends.
ANR4075I
Audit command: Auditing policy

definitions.

database audit and indicates that the server policy
information (domain, policy set, management classes,
and copy groups) are being examined by the database
audit process.
ANR4076E
Audit command: Invalid client node count

detected for policy domain domain name.

count of nodes recorded for the specified policy
domain do not match the actual number of nodes
assigned to the domain.
324
ANR4079I
Audit command: Invalid activation

indicators encountered for policy
domain domain name - entry will be
corrected.

policy set activation entries for the specified policy
domain. Because FIX=YES has been specified for the
audit command, the entry will be corrected.
ANR4080E
Audit command: Invalid grace period

backup retention value encountered for

incorrect grace period retention value for the specified
policy domain.
ANR4081I

backup retention value encountered for
policy domain domain name - default
value will be set.
ANR4082E ANR4089I
policy domain. Because FIX=YES has been specified for
the audit command, the default value will be set.
ANR4086E
Audit command: Invalid node node number

found assigned to domain domain name.

number assigned to a policy domain that does not
reference a valid client node definition.
ANR4082E

archive retention value encountered for

policy domain.
ANR4083I

archive retention value encountered for
policy domain domain name - default
value will be set.

policy domain. Because FIX=YES has been specified for
the audit command, the default value will be set.
ANR4084E
Audit command: Invalid administrator

update information encountered for

last updated information for the specified policy
domain.
ANR4085I

policy domain domain name - information
will be corrected.

last updated information for the specified policy
domain. Because FIX=YES has been specified for the
command, the information is corrected.

ANR4087I
Audit command: Invalid node node number

found assigned to domain domain name
reference will be deleted.

number assigned to a policy domain that does not
reference a valid client node definition. Because
ANR4088E
Audit command: Default management

class management class name specified for
policy set policy set name in domain
domain name does not exist.

set with a default management class specified that does
not exist.
ANR4089I
Audit command: Default management

class management class name specified for
policy set policy set name in domain
domain name does not exist - the
reference will be removed.

set with a default management class specified that does
not exist. Because FIX=YES has been specified for the
audit command, the reference will be removed from the
policy set.
examine the policy set specified, and set a new default
management class for the set. If the policy set is the
ACTIVE policy set, you must activate a new policy set
for the domain with a valid default management class.
325
ANR4090E ANR4098I
ANR4090E
Audit command: Active Policy set for

domain domain name does not contain a
valid default management class - policy
will fail for this domain. Please correct
the ACTIVE policy set.
Explanation: A database audit process finds an active

policy set for the specified policy domain that does not
have a valid active management class specified.

information for the specified management class. The
audit process generates an identifier, because FIX=YES
has been specified for the audit command.
ANR4095E

you must activate a new policy set for the domain with
a valid default management class.
ANR4091E

policy set set name in policy domain
domain name.

last updated information for the specified policy set.

information for the specified management class.
ANR4096E

ANR4092I

policy set set name in policy domain
domain name - information will be
corrected.

last updated information for the specified policy set.
the information is corrected.
Audit command: An invalid management

class identifier (actual identifier) was
encountered for management class
management class name in policy set set
name, domain domain name (expected
expected identifier).

encountered for management class
management class name in policy set set
name, domain domain name (expected
expected identifier) - the correct identifier
will be stored.

information for the specified management class. The
audit process corrects the identifier, because FIX=YES
has been specified for the audit command.

ANR4093E
Audit command: A management class

identifier is not defined for
in policy set set name, domain domain
name.
ANR4097E

in policy set set name in policy domain
domain name.

last updated information for the specified management
class.

information for the specified management class.


ANR4094E
326
Audit command: A management class

identifier is not defined for
in policy set set name, domain domain
name - an identifier will be generated
for this management class.
ANR4098I

in policy set set name in policy domain
domain name - information will be
corrected.
ANR4099E ANR4106E
last updated information for the specified management
class. Because FIX=YES has been specified for the

ANR4103I

ANR4099E
Audit command: Copy group copy group

class name, policy set set name, domain
domain name has an invalid name or
type.
Explanation: A database audit process encounters a

copy group that has an invalid name or copy group
type.
the audit command, reissue the command specifying
FIX=YES so that the error can be corrected.
ANR4100I
Audit command: Attempting to reinsert

the copy group as a BACKUP copy
group.

type. The process attempts to reinsert the definition as
a backup copy group.
ANR4101I
Audit command: A backup copy group

already exists - the invalid copy group
will be deleted.

type. While attempting to reinsert the copy group as a
backup copy group, the process discovers that a
backup copy group already exists for the management
class. The copy group is deleted.
you may examine the server copy groups using the
QUERY COPYGROUP command, and correct them
with the DEFINE COPYGROUP and UPDATE
COPYGROUP commands if desired.
ANR4102I
Audit command: Attempting to reinsert

the copy group as an ARCHIVE copy
group.

type. The process attempts to reinsert the definition as
an archive copy group.
Audit command: An archive copy group

already exists - the invalid copy group
will be deleted.

type. While attempting to reinsert the copy group as an
archive copy group, the process discovers that a backup
copy group already exists for the management class.
The copy group is deleted.
you may examine the server copy groups using the
QUERY COPYGROUP command, and correct them
with the DEFINE COPYGROUP and UPDATE
COPYGROUP commands, if desired.
ANR4104E

encountered for a copy group in
management class management class name,
policy set set name, domain domain name
(expected expected identifier).

information for the specified copy group.
ANR4105E

(expected expected identifier) - the correct
identifier will be stored.

information for the specified copy group. The audit
process corrects the identifier, since FIX=YES has been
specified for the audit command.
ANR4106E
Audit command: An invalid copy group

identifier (actual identifier) was
(expected expected identifier).

information for the specified copy group.
327
ANR4107E ANR4113E


the audit command, reissue the command and specify
FIX=YES so that the inconsistency can be corrected.
ANR4107E
Audit command: An invalid copy group

identifier (actual identifier) was
encountered for copy group name copy
group name (expected expected identifier).
ANR4111I

information for the specified copy group name.
ANR4108E
Audit command: Invalid backup copy

group attributes encountered for copy
group copy group name in management
class management class name, policy set set
name, domain domain name.

invalid backup copy group attributes for the specified
copy group.

invalid archive copy group attributes for the specified
copy group. Because FIX=YES has been specified for
the command, the copy group will be corrected using
default values for the attributes found in error.
examine the copy group by using the QUERY
COPYGROUP command, and correct the attributes
with the UPDATE COPYGROUP command, if desired.
ANR4112W

the audit command, reissue the command specifying
FIX=YES so that the inconsistency can be corrected.
ANR4109I
Audit command: Invalid backup copy

name, domain domain name - the copy
group will be corrected using default
attributes.

invalid backup copy group attributes for the specified
copy group. Because FIX=YES has been specified for
the command, the copy group will be corrected using
default values for the attributes found in error.
examine the copy group by using the QUERY
COPYGROUP command, and correct attributes with
the UPDATE COPYGROUP command, if desired.
ANR4110E
Audit command: Invalid archive copy

name, domain domain name.

invalid archive copy group attributes for the specified
copy group.
328
Audit command: Invalid archive copy

name, domain domain name - the copy
group will be corrected using default
attributes.

name, specified as a destination for copy
name, domain domain name, does not
exist.

storage pool specified for the destination of the
specified copy group that is not defined in the server
database. If this copy group is used in an active policy
set, then backup or archive operations will fail when
attempting to put client data in the destination.
use the DEFINE STGPOOL command to define the
missing storage pool or the UPDATE COPYGROUP
command to update the copy group to refer to an
existing storage pool.
ANR4113E

copy group copy group name in
policy set set name, policy domain domain
name.

last updated information for the specified copy group.
ANR4114I ANR4122E
ANR4114I

copy group copy group name in
policy set set name, policy domain domain
name - information will be corrected.

last updated information for the specified copy group.
the information is corrected.
ANR4115E

name is referenced, but not formally
defined.
Explanation: A database audit process finds a

reference to the specified policy domain, but the
domain is not formally defined in the server database.
ANR4118I
Audit command: Policy set set name in

domain domain name is referenced, but
not formally defined - a policy set with
this name will be created.

reference to the specified policy set, but the set is not
formally defined in the server database. Because
FIX=YES has been specified, the audit process will
create a new policy set with this name.
User response: After the audit command has
completed, you can view the attributes for this policy
set by using the QUERY POLICYSET command, and
update attributes with the UPDATE POLICYSET
command, if desired.
ANR4119E
Audit command: Management class class

name in policy set set name, domain
domain name is referenced, but not
formally defined.

reference to the specified management class, but the
class is not formally defined in the server database.
ANR4116I

name is referenced, but not formally
defined - a policy domain with default
attributes will be defined with this
name.

reference to the specified policy domain, but the
domain is not formally defined in the server database.
Because FIX=YES has been specified, a new policy
domain with this name will be defined by the audit
processor.
completed, you can view the attributes for this policy
domain using the QUERY DOMAIN command, and
update attributes with the UPDATE DOMAIN
command, if desired.
ANR4117E
Audit command: Policy set set name in

domain domain name is referenced, but
not formally defined.

reference to the specified policy set, but the set is not
formally defined in the server database.

ANR4120I

domain name is referenced, but not
formally defined - the management class
will be created.

reference to the specified management class, but the
class is not formally defined in the server database.
command, the audit process defines a management
class in the server with this name.
completed, you can view the attributes for this
management class by using the QUERY MGMTCLASS
command, and update attributes with the UPDATE
MGMTCLASS command, if desired.
ANR4122E
Audit command: The instance count for

management class class name does not
agree with the actual management class
data (number of instances instances).

reference count for the specified management class that
did not match the actual number of instances for this
class.
329
ANR4123I ANR4131W
ANR4127I

ANR4123I

management class class name does not
agree with the actual management class
data (number of instances instances) - the
number will be corrected.

reference count for the specified management class that
does not match the actual number of instances for this
class. The audit process corrects the count because
FIX=YES has been specified for the audit command.
Explanation: A database audit process is not able to

locate the global attributes for policy information in the
for the audit command, the attributes will be
regenerated.
ANR4128E

ANR4124E

copy group copy group name does not
agree with the actual copy group data
(number of instances instances).

reference count for the specified copy group that does
not match the actual number of instances for this copy
group.
Audit command: Policy global attributes

cannot be found - attributes will
recreated.
Audit command: Policy global high-water

marks do not match the identifiers in
use.
Explanation: A database audit process finds the

attributes used to track policy identifiers are incorrect.
ANR4129E
Audit command: Policy global high-water

use - they will be corrected.

attributes used to track policy identifiers are incorrect.
command, the attributes will be corrected.
ANR4125I

copy group copy group name does not
agree with the actual copy group data
(number of instances instances) - the
number will be corrected.

reference count for the specified copy group that does
not match the actual number of instances for this copy
group. The audit process corrects the count because
FIX=YES has been specified for the audit command.

ANR4130W
Audit Volume updating object

information for volume volume name:
filespace name, fsId filespace id , File Name
file name.

shown, object information for the specified file will be
updated.
System action: The object information is updated.

ANR4126E
Audit command: Policy global attributes

cannot be found.

locate the global attributes for policy information in the
server database.
330
ANR4131W
Audit Volume found incorrect object

information for volume volume name:
filespace name, fsId filespace id, File name
file name.

shown, object information for the specified file is found
to be in error.
ANR4132I ANR4137I
ANR4132I

count damaged files deleted, file count
damaged files marked as damaged, file
count files previously marked as
damaged reset to undamaged, file count
objects updated.

specifying FIX=YES for the volume shown has ended.
The following information is displayed:
the database if the audit volume process cannot access

the files due to hardware problems (for example, dirty
tape heads).
User response: If you suspect that files were
inaccessible because of hardware problems such as
dirty tape heads, correct the hardware problem and
reissue the AUDIT VOLUME FIX=NO command for
this volume. To remove damaged file references and
update the object information, issue the AUDIT
VOLUME command and specify FIX=YES.
ANR4134I
v The number of files audited

v The number of inconsistent files deleted
v The number of inconsistent files marked as damaged
v The number of files previously marked as damaged
that were reset to undamaged
v The number of updated objects
The number of files marked as damaged includes all
files belonging to aggregates that were marked
damaged during the audit. Files are marked as
damaged in primary storage pools and not deleted
when backup copies for the files are known to exist in
COPY storage pools.
AUDITDB: Processed number of entries

entries in database tables and number of
blocks blocks in bit vectors. Elapsed time
is elapsed time.
Explanation: This message reports the progress of a

database audit operation. While auditing database
tables, the number of entries processed will increase,
but the number of blocks processed in bit vectors will
not increase. While auditing bit vectors, the number of
blocks processed will increase, but the number of
entries processed will not increase. The number of
entries and the number of blocks are cumulative for the
entire audit operation. The elapsed time of the audit
operation is reported in hours, minutes, and seconds.
System action: Database audit processing continues.
User response: To recover files that have been marked

as damaged on the volume, use the RESTORE
STGPOOL or RESTORE volume command.
ANR4135I
ANR4133I

database audit and indicates that the server scheduling
information is examined by the database audit process.

count damaged files found and marked
as damaged, file count files previously
marked as damaged reset to undamaged,
file count objects need updating.
Audit command: Auditing central

scheduler definitions.


specifying FIX=NO for the volume shown has ended.
ANR4136I
The following information is displayed:

about client file spaces is currently being examined by
the database audit process.
v The number of files audited

v The number of inconsistent files marked as damaged
v The number of files previously marked as damaged
that were reset to undamaged
v The number of objects need updating
The number of files marked damaged includes all files
belonging to aggregates that were marked damaged
during the audit. Inconsistent files are marked as
damaged in the database and can be recovered by
using the RESTORE STGPOOL or RESTORE VOLUME
command if copies of the files reside in a COPY storage
pool. Another AUDIT VOLUME command may be able
to access the files and reset the damaged indicator in
Audit command: Auditing server

inventory.

ANR4137I
Audit command: Auditing inventory file

spaces.

about client file spaces is currently being examined by
the database audit process.
331
ANR4138I ANR4147E
ANR4143E

ANR4138I
Audit command: Auditing inventory

backup objects.

about client backup objects is currently being examined
by the database audit process.
Explanation: A database audit process cannot locate

the global attributes for scheduling information in the
server database.
ANR4144I

ANR4139I

archive objects.

about client archive objects is currently being examined
by the database audit process.
Audit command: Central scheduler global

attributes cannot be found.
Audit command: Central scheduler global

attributes cannot be found - attributes
will be recreated.
Explanation: A database audit process cannot locate

the global attributes for scheduler information in the
regenerated.

ANR4145E
ANR4140I
Audit command: Database audit process

started.

database audit and indicates that the audit process has
started.
ANR4141I

completed.

database audit and indicates that the database audit
has successfully completed.
System action: Audit processing ends.
ANR4142I

terminated in error.

database audit and indicates that the audit process
ended prematurely due to an internal server database
error.
System action: Audit processing ends.
this one to see if the error can be corrected. If the
situation cannot be resolved, contact your service
representative.
332
Audit command: One or more central

scheduler attributes are incorrect.

global attributes used for server scheduling activities
are incorrect.
specify FIX=YES so that the administrative global
ANR4146I
Audit command: One or more central

scheduler global attribute(s) are
incorrect - default values will be set.

global attributes used for server scheduling activities
are incorrect. Because FIX=YES has been specified on
the AUDIT command, default attribute values will be
used to correct the scheduling global attributes.
ANR4147E

name referenced by schedule schedule
name does not exist.

schedule that references a policy domain that is not
ANR4148I ANR4156I
ANR4152I

ANR4148I

name referenced by schedule schedule
name does not exist - the schedule will
be deleted.

schedule that references a policy domain that is not
defined in the server database. Because FIX=YES has
been specified for the audit command, the specified
schedule will be deleted from the server database.

schedule reference from a client node for a schedule
that is not defined in the server database. Because
schedule association will be deleted from the server
database.
ANR4153E

ANR4149E
Audit command: One or more attributes

for schedule schedule name in policy
domain domain name are incorrect.
Explanation: A database audit process finds one or

more invalid attributes for the specified schedule.
ANR4150I
Audit command: One or more attributes

for schedule schedule name in policy
domain domain name are incorrect default values will be set.
Explanation: A database audit process finds one or

more invalid attributes for the specified schedule.
command the invalid attributes will be set to default
values.
use the QUERY SCHEDULE command to examine the
values set for the schedule, and use the UPDATE
SCHEDULE command to change any attributes desired.
ANR4151E
Audit command: Schedule schedule name in

policy domain domain name not found,
but is referenced by a client node.

schedule reference from a client node for a schedule
that is not defined in the server database.

policy domain domain name not found,
but is referenced by a client node - the
schedule association will be deleted.

policy domain domain name references a
client node that does not exist.

schedule that references a client node that is not
ANR4154I

policy domain domain name references a
client node that does not exist - the
node reference will be deleted.

schedule that references a client node that is not
been specified for the audit command, the reference
will be removed from the server database.
ANR4155E

update information encountered for a
schedule assignment.

last updated information for a schedule-node
assignment.
ANR4156I

update information encountered for a
schedule assignment - information will
be corrected.

333
ANR4157E ANR4165I
last updated information for a schedule-node
assignment. Because FIX=YES has been specified for
the command, the information is corrected.
ANR4157E
Audit command: Scheduling callback

address is registered for a client node
that does not exist.

server-prompted-scheduling callback address for a node
that does not exist.
ANR4158I
Audit command: Scheduling callback

address is registered for a client node
that does not exist - callback

server-prompted-scheduling callback address for a node
that does not exist. Because FIX=YES has been specified
for the command, the callback information will be
deleted from the server database.
ANR4159I
Audit command: An inventory

authorization rule specifies an invalid
node (node ID) or file space (filespace ID)
- the rule will be deleted.

either a node ID or file space ID is invalid for an
authorization rule. Since FIX=YES has been specified,
the invalid authorization rule will be deleted.
ANR4160I
Audit command: An inventory

authorization rule specifies an invalid
node (node ID) or file space (filespace ID).

either a node ID or file space ID is invalid for an
authorization rule.
ANR4161I
Audit command: Inventory global

attributes could not be found - they will
be created.

inventory global attributes. Because FIX=YES has been
specified for the command, the information is corrected
by the creation of the global attributes.
ANR4162I
Audit command: Inventory global

attributes could not be found.

inventory global attributes.
ANR4163I
Audit command: Invalid object ID

high-water mark encountered for
inventory global attributes - the value
will be corrected.

object ID high-water mark for the inventory global
attributes is invalid. Because FIX=YES has been
specified for the command, the object ID high-water
mark is determined by the current inventory and set
accordingly.
ANR4164I
Audit command: Invalid object ID

high-water mark encountered for
inventory global attributes.

object ID high-water mark for the inventory global
attributes is invalid.
ANR4165I
Audit command: An inventory node

assignment entry was not found for
node node ID - an entry will be created.

node assignment entry corresponding to the specified
node. Since FIX=YES has been specified for the
command, the required inventory entry will be created
using default values.
334
ANR4166I ANR4175I
ANR4166I

node node ID.

node.
ANR4167I
Audit command: The file space

high-water mark for node node ID is
incorrect - the value will be corrected.

ANR4171I
Audit command: Primary backup entry for

an expiring object (object.ID) cannot be
found - the expiring object entry will be
deleted.

primary backup entry for the specified expiring object.
the information is corrected by deleting the expiring
object entry.
ANR4172I

found.
Explanation: A database audit process finds that a file

space high-water mark is incorrect for the specified
node ID. Since FIX=YES has been specified for the

primary backup entry for the specified expiring object.

ANR4168I

incorrect.
Explanation: A database audit process finds that a file

space high-water mark is incorrect for the specified
node ID.
ANR4173I
Audit command: Primary archive entry for

found - the expiring object entry will be
deleted.

primary archive entry for the specified expiring object.
object entry.
ANR4169I

incorrect - the value will be corrected.
Explanation: A database audit process finds that an

authorization rule high-water mark is incorrect for the
specified node ID. Since FIX=YES has been specified for
the command, the information is corrected.
ANR4170I
Audit command: The authorization rule

incorrect.

authorization rule high-water mark is incorrect for the
specified node ID.

ANR4174I

found.

primary archive entry for the specified expiring object.
ANR4175I
Audit command: Invalid copy type

encountered for an expiring objects
entry (object.ID) - the expiring object
entry will be deleted.

copy type for the specified expiring object is invalid.
335
ANR4176I ANR4184I
object entry. The entry will be recreated later if it is
necessary.
ANR4181I

ANR4176I

encountered for an expiring objects
entry (object.ID).

copy type for the specified expiring object is invalid.

encountered for object object.ID - object
found as a backup object - correcting
the invalid copy type

invalid copy type for the specified object ID but finds a
corresponding backup object for the entry. Because
invalid copy type is corrected.

ANR4177I

an object (object.ID) cannot be found entry will be deleted.

specified primary backup object. Because FIX=YES has
been specified for the command, the entry is deleted.
ANR4182I

found as an archive object - correcting
the invalid copy type

invalid copy type for the specified object ID but finds a
corresponding archive object for the entry. Because
invalid copy type is corrected.

ANR4183I
ANR4178I

an object (object.ID) cannot be found.

specified primary backup object.
ANR4179I

an object (object.ID) cannot be found entry will be deleted.

specified primary archive object. Because FIX=YES has
been specified for the command, the entry is deleted.
ANR4180I

an object (object.ID) cannot be found.

specified primary archive object.
336

encountered for object object.ID primary archive entry created for object

invalid copy type for the specified object ID and is
unable to find corresponding primary backup or
primary archive objects. Because FIX=YES has been
specified for the command, a primary archive entry is
created using default values.
ANR4184I

encountered for object object.ID.

invalid copy type for the specified object ID and is
unable to find corresponding primary backup or
primary archive objects.
ANR4185I ANR4194I
ANR4185I
Audit command: Object entry for backup

object object.ID not found - entry will be
created.

object entry for the specified backup object. Because
FIX=YES has been specified for the command, an object
entry is created using default values.
ANR4190I
Audit command: Expiring entry for

inactive backup object object.ID not
found.

expiring entry for the specified inactive backup entry.

ANR4191I
ANR4186I
Audit command: Object entry for backup

object object.ID not found.

object entry for the specified backup object.
Audit command: Object entry for archive

object object.ID not found - entry will be
created.

object entry for the specified archive object. Because
information is corrected by creating an object entry.
ANR4187I
Audit command: Inventory object fields

for object object.ID do not match the
primary backup entry - the object will
be updated.

the object fields for the specified object ID do not
match the fields for the corresponding primary backup
object. Because FIX=YES has specified for the
command, the incorrect object fields will be corrected.
ANR4192I
Audit command: Object entry for archive


object entry for the specified archive object.

ANR4188I

primary backup entry.

match the fields for the corresponding primary backup
object.
ANR4189I

inactive backup object object.ID not
found - the entry will be created.

expiring entry for the specified inactive backup entry.
an expiring entry will be created.
ANR4193I

primary archive entry - the object will
be updated.

match the fields for the corresponding primary archive
object. Because FIX=YES has been specified for the
command, the incorrect object fields will be corrected.
ANR4194I

primary archive entry.

match the fields for the corresponding primary archive
object.

337
ANR4195I ANR4204I
ANR4195I

archive object object.ID not found - the
entry will be created.

expiring entry for the specified archive object. Because
FIX=YES has been specified for the command, an
expiring entry will be created.
ANR4196I

archive object object.ID not found.

expiring entry for the specified archive object.
ANR4200I
Audit command: Expiring entry node ID

and file space filespace ID does not match
the object entry for object ID object.ID the entry will be deleted.

the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
the expiring object entry is deleted.
ANR4201I
Audit command: Expiring entry node ID

and file space filespace ID does not match
the object entry for object ID object.ID.

the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
ANR4197I
Audit command: File space entry filespace

ID not found for node node ID.
Explanation: A database audit process cannot find a

file space entry for the specified node.

ANR4202I

ANR4198I

ID not found for node node name - an
entry will be created.

file space entry for the specified node. Because
FIX=YES has been specified for the command, a file
space entry has been created.

the specified expiring object has a date that is not valid.
the expiring object entry is deleted.
ANR4203I

ANR4199I

ID not found for node node ID - unable
to create an entry.

file space entry for the specified node ID. Because
FIX=YES has been specified for the command, the audit
process has attempted to create a file space entry but is
not successful.
User response: Contact your system administrator.
Audit command: The base date for

expiration processing of entry object.ID is
not valid - the entry will be deleted.
Audit command: The base date for

expiration processing of object object.ID
is not valid.

the specified expiring object has a date value that is not
valid.
ANR4204I
Audit command: One or more date values

for a backup entry object.ID is not valid.

one or more of the date values is improperly formatted
or contains incorrect information for the specified
backup object.
338
ANR4205I ANR4214I
ANR4205I
Audit command: The insertion date value

for archive entry object.ID is not valid.

the insertion date for the specified archive object is
improperly formatted or contains incorrect information.
ANR4210I
Audit command: Auditing physical

volume repository definitions.

database audit and indicates that the physical volume
repository definitions are being examined by the
ANR4206I
Audit command: Object entry for expiring

object object.ID not found - expiring
object entry will be deleted.

object entry corresponding to the specified expiring
command, the expiring object entry for the specified
object ID is deleted.
ANR4211I
Audit command: Drive entry library name

for library drive name in the physical
volume repository is invalid.
Explanation: A database audit process finds that a

drive entry is missing a corresponding library entry.

ANR4212I
ANR4207I
Audit command: Object entry for expiring


object entry corresponding to the specified expiring
object.
Audit command: An object entry for

library library name and drive drive name
in the physical volume repository is
invalid - the entry will be deleted.

drive entry is missing a corresponding library entry.
the invalid drive entry is deleted.
ANR4208I

assignment entry is not valid for node
node ID - the entry will be deleted.
ANR4213I
Audit command: A device type for library

library name and drive drive name in the
physical volume repository is invalid.

node assignment entry for the specified node ID is not
valid. Since FIX=YES has been specified for the
command, the required inventory entry is deleted.

device type for the specified library and drive is
invalid.
User response: Contact the system administrator so

that appropriate action may be taken.
ANR4209I

node node ID.

node assignment entry for the specified node ID is not
valid.
ANR4214I
Audit command: A drive model for

library library name and drive drive name
in the physical volume repository is
invalid.

drive model for the specified library and drive is
invalid.
User response: Contact the system administrator so
that appropriate action may be taken.
339
ANR4215I ANR4222I
ANR4215I

library library name and volume volume
name in the physical volume repository
is invalid.

library inventory entry is missing a corresponding
library entry.
ANR4216I

is invalid - the entry will be deleted.

library inventory entry is missing a corresponding
library entry. Because FIX=YES has been specified for
the command, the invalid library inventory entry is
deleted.
ANR4219I
Audit command: A library type specified

for library library name in the physical
volume repository is invalid.

library type for the specified library is invalid.
ANR4220I
Audit command: A library type specified

for library library name in the physical
volume repository is invalid - the
library type has been changed to the
default of library type default.

library type for the specified library is invalid. Because
information is corrected by changing the library type to
the default type.

ANR4221I
ANR4217I
Audit command: The volume status for

is invalid.

volume status for the specified library and volume is
set to scratch. This is incorrect because storage agent
has a volume name for the library and volume
indicating that it should have a volume status of
private.
ANR4218I
Audit command: The volume status for

is invalid - the volume status will be
changed to private.

volume status for the specified library and volume is
set to scratch. This is incorrect because storage agents
has a volume name for the library and volume which
indicates that it should have a volume status of private.
the incorrect volume status is set to private.
340
Audit command: An error (error code) was

found with archive description for node
(node identifier), description (description),
objects (old object count,new object count),
count (old directory count,new directory
count) - entry will be deleted or updated.
Explanation: A database audit process has found an

error with the specified archive description. Because
FIX=YES has been specified for the command, the entry
is deleted or updated.
ANR4222I

found with archive description for node
(node identifier), description (description),
objects (old object count,new object count),
count (old directory count,new directory
count).

error with the specified archive description.
ANR4223I ANR4231E
ANR4223I

found with converted archive object for
node (node identifier), description
(description identifier), object (object.ID),
filespace (filespace identifier) - entry will
be deleted.

error with the specified converted archive object.
the entry is deleted.
ANR4227E

inconsistent information for a file aggregate. This
problem cannot be corrected by the audit process, but
the file data is not deleted.
ANR4228E

ANR4224I

found with converted archive object for
node (node identifier), description
(description identifier), object (object.ID),
filespace (filespace identifier).

error with the specified converted archive object.
Audit command: table entry for archive

object (object.ID), node (node identifier),
description (description), filespace
(filespace identifier) not found - the entry
will be created.

converted table table entry for the specified archive
command, an entry will be created.
ANR4226I
Audit command: table entry for archive

object (object.ID), node (node identifier),
description (description), filespace
(filespace identifier) not found.

information detected for file aggregate
(Aggregate.ID).

or incorrect information for a file aggregate. This
ANR4229E

ANR4225I
Audit command: Inconsistent information

detected for file aggregate (Aggregate.ID).

information detected for file aggregate
(Aggregate.ID) - It will be corrected.

or incorrect information for a file aggregate. Because
ANR4230I
Audit command: Auditing data storage

definitions.

database audit and indicates that the data storage
definitions are being examined by the database audit
process.
Audit command: Invalid device class
strategy strategy for device class device
class name.

converted table table entry for the specified archive
object.
ANR4231E
Explanation: A database audit process finds a device

class with an invalid access strategy.


FIX=YES so that the access strategy can be corrected.
341
ANR4232E ANR4240E
ANR4232E

strategy strategy for device class device
class name - information will be
corrected.
Explanation: A database audit process finds a device

class with an invalid access strategy. Because FIX=YES
has been specified for the audit command, the access
strategy will be corrected for this device class.
FIX=YES so that the attribute can be corrected.

ANR4237E
Audit command: An invalid access

strategy was encountered for storage
pool storage pool name - the strategy will
be corrected.

invalid device access strategy for the specified storage
pool. Because FIX=YES has been specified for the
command, the storage pool access strategy will be
corrected.
ANR4233E
Audit command: Pool ID information is

missing or incorrect for storage pool
storage pool name.

pool whose pool ID information is missing or incorrect.

examine the storage pool using the QUERY STGPOOL
command, and verify that the correct information is
displayed for this storage pool.
ANR4238E

FIX=YES so that the access strategy can be corrected.
ANR4234E
Audit command: Pool ID information is

missing or incorrect for storage pool
storage pool name - information will be
created or corrected.

pool whose pool ID information is missing or incorrect.
command, the pool ID information will be created or
corrected for this storage pool.
Explanation: The specified storage pool references an

invalid pool ID as its next storage pool.
to update the next pool. Alternatively, if the audit
command is reissued with FIX=YES, the reference to
the next pool will be deleted.
ANR4239E

ANR4235E
Audit command: Device class ID

referenced by storage pool storage pool
name is not defined - data in this pool
may not be available.

pool which references a device class ID which is not
defined.
ANR4236E

strategy was encountered for storage

invalid device access strategy for the specified storage
pool.
342

name specifies an undefined pool ID for
its next storage pool.

name specifies an undefined pool ID for
its next storage pool - reference will be
deleted.
Explanation: The specified storage pool references an

invalid pool ID as its next storage pool. Because
reference is deleted. The specified storage pool will not
have a next pool.
use the UPDATE STGPOOL command to assign a next
storage pool, if desired.
ANR4240E
Audit command: An invalid attribute was

encountered for storage pool storage pool
name.

invalid attribute for the specified storage pool.
ANR4241E ANR4248E
ANR4241E
Audit command: An invalid attribute was

encountered for storage pool storage pool
name - the attribute will be assigned its
default value.

invalid attribute for the specified storage pool. Because
storage pool will be corrected using the default value
for the attribute.
ANR4245E

strategy was encountered for volume
volume name.

invalid device access strategy for the specified volume.
FIX=YES so that the strategy can be corrected.

examine the storage pool using the QUERY STGPOOL
command, and correct attributes with the UPDATE
STGPOOL command, if desired.
ANR4242E


information pertaining to the last update for the
specified storage pool.
ANR4246E

invalid device access strategy for the specified volume.
the access strategy will be corrected for this volume.
ANR4247E

ANR4243E

storage pool storage pool name information will be corrected.

information pertaining to the last update for the
specified storage pool. Because FIX=YES has been
specified for the command, the information is
corrected.
ANR4244E
Audit command: Storage pool ID

referenced by volume volume name is not
defined - data on this volume may not
be available.
Explanation: A database audit process finds a data

storage volume which references a storage pool ID that
is not defined.

strategy was encountered for volume
volume name - the strategy will be
corrected.
Audit command: Missing information for

volume volume name cannot be created.
Delete the volume after optionally
moving any files from the volume.

missing database information for the specified volume.
Since FIX=YES has been specified for the audit
command, an attempt is made to create the missing
information where possible. However, some of the
information cannot be created, and the volume must be
deleted.
System action: The access mode for the volume is set
to UNAVAILABLE to prevent further attempts to write
to this volume. Audit processing continues.
User response: After audit processing completes, an
administrator should take the following actions to
eliminate the volume
v (Optional) Use the UPDATE VOLUME command to
set the access mode for the volume to READWRITE.
It may then be possible to use the MOVE DATA
command to move files from the volume so that
these files can be accessed by the server.
v (Required) Use the DELETE VOLUME command to
delete the volume from the database.
information for storage volume volume
name.
ANR4248E
User response: You can attempt to move data on the

specified volume to other volumes using the MOVE
DATA command; then delete the specified volume and
redefine it. If this does not work, contact your service
representative.

storage volume for which information is missing or
incorrect.
343
ANR4249E ANR4257E
corrected.
ANR4249E

information for storage volume volume
name - information will be created or
corrected.

storage volume for which information is missing or
incorrect. Since FIX=YES has been specified for the
audit command, the information will be created or
corrected.
ANR4253E

locate the global attributes for data storage in the
regenerated.
ANR4254E

ANR4250E
Audit command: Extraneous reference

found.

reference to a nonexistent entity such as a storage pool
or volume.
Audit command: Data storage global

attributes cannot be found - attributes
will be recreated.
Audit command: Data storage high-water

use.

information used to track data storage identifiers is
incorrect.

FIX=YES so that the non-existant entity is recreated, if
possible. If recreation is not possible, the extraneous
reference is deleted.
ANR4251E
Audit command: Extraneous reference

found - information will be recreated or
deleted.

reference to a nonexistent entity such as a storage pool
or volume. Since FIX=YES has been specified for the
audit command, the nonexistant entity will be
recreated, if possible. If recreation is not possible, the
ANR4255E
Audit command: Data storage high-water

use - they will be corrected.

information used to track data storage identifiers is
incorrect. Because FIX=YES has been specified for the
audit command, the error will be corrected.
ANR4256I

definitions for disk volumes.

database audit and indicates that the database
information relating to data storage disk volumes is
being examined by the database audit process.
ANR4252E
Audit command: Data storage global

attributes cannot be found.

locate the global attributes for data storage in the
server database.

ANR4257E
Audit command: A correctable

data-integrity error was detected on
volume volume name.

data-integrity error for a file stored on the specified
volume. This error is correctable.
344
ANR4258E ANR4267E
ANR4258E
Audit command: A data-integrity error

was detected on volume volume name the error will be corrected.

correctable data-integrity error for a file stored on the
specified volume. Because FIX=YES has been specified
for the audit command, the error will be corrected.
ANR4259E
Audit command: Invalid data encountered

for a file in data storage - data can be
corrected.
Explanation: A database audit process finds invalid

data for a file in data storage. The error should be
correctable.

User response: After audit processing has completed,
use the UPDATE VOLUME command to set the access
information for this volume, if desired.
ANR4263I

definitions for sequential volumes.

database audit and indicates that the database
information relating to data storage sequential volumes
is being examined by the database audit process.
ANR4264I
Audit command: Auditing file

information.

database audit and indicates that information on stored
files is being examined by the database audit process.
ANR4260E
Audit command: Invalid data encountered

for a file in data storage - the error will
be corrected.

data for a file in data storage. Because FIX=YES has
been specified for the audit command, the error will be
corrected.

ANR4265I
Audit command: Auditing disk file

information.

database audit and indicates that information on files
stored on disk media is being examined by the

ANR4261E
Audit command: Invalid access

information was encountered for
volume volume name.

invalid access information for the specified volume.
User response: After audit processing has completed,
use the UPDATE VOLUME command to set the access
information for this volume. Or reissue the audit
command with FIX=YES, which sets access to the
default value.
ANR4266I

database audit and indicates that information on files
stored on sequential media is being examined by the
ANR4267E
ANR4262E
Audit command: Invalid access

information was encountered for
volume volume name - the information
will be corrected.

invalid access information for the specified volume.
the information will be corrected by setting the default
value.
Audit command: Auditing sequential file

information.
Audit command: A storage pool

containing file data cannot be located file data may not be accessible.

database audit and indicates that the storage pool
containing a files data cannot be located or is not
defined. This problem cannot be corrected by the audit
process, but the file data is not deleted.
345
ANR4268E ANR4277E
ANR4268E
Audit command: A storage volume


database audit and indicates that the storage volume
defined. This problem cannot be corrected by the audit
process, and the file data is deleted.
ANR4269E
Audit command: Extraneous file data

reference found.

reference to a file that no longer exists.
FIX=YES so that the information can be deleted.
ANR4270E
Audit command: Extraneous file data

reference found - information will be
deleted.

reference to a file that no longer exists. Because
ANR4273E

was detected on volume volume name Issue the AUDIT VOLUME command to
correct the error.

data-integrity error for a file stored on the specified
volume.
User response: Issue the AUDIT VOLUME command
on the specified volume to correct the data-integrity
error.
ANR4274E
Audit command: A correctable

data-integrity error was detected.

data-integrity error for a stored file. This error can be
corrected.
ANR4275E

was detected - it will be corrected.

data-integrity error for a stored file. Because FIX=YES
has been specified for the audit command, the error
will be corrected.
ANR4271E

occupancy information detected.

or incorrect occupancy information for a data storage
pool or a data storage volume.
corrected.
ANR4272E

occupancy information detected information will be created or corrected.

or incorrect occupancy information for a data storage
pool or a data storage volume. Because FIX=YES has
been specified for the audit command, the information
will be created or corrected.
346
ANR4276E
Audit command: Invalid file storage

information detected - file data is not
accessible.

file storage information for a stored file, and it cannot
be corrected.
on all your volumes to correct the data-integrity error.
ANR4277E

information detected.

file storage information for a stored file. This
ANR4278E ANR4284I
ANR4278E

information detected - It will be
corrected.

file storage information for a stored file. Because
ANR4279E

administrator number assigned to more
than just system authority class.

administrator is assigned to other authority classes.
Being assigned with 'SYSTEM' authority supersedes all
other classes and the other privilege class entries
should be deleted.
ANR4282I

specified administrator is assigned as an unrestricted
policy administrator. The specified administrator is also
assigned as the restricted administrator for the
specified policy domain. The unrestricted policy
administration class supersedes any restricted policy
class definitions for an administrator. Because FIX=YES
has been specified for the command, the restricted
administrator policy class will be deleted.
ANR4283E

ANR4280I

administrator number assigned to more
than just system authority class - the
other class entries will be deleted.

administrator is assigned to other authority classes.
Being assigned with 'SYSTEM' authority supersedes all
other classes and the other privilege class entries
should be deleted. Because FIX=YES has been specified
for the command, any authority class other than system
will be deleted.

administrator number assigned as an
unrestricted policy administrator is also
assigned as administrator for domain
domain name - restricted class entry will
be deleted.

unrestricted storage administrator is also
assigned as a restricted administrator for

storage administrator. The specified administrator is
also assigned as the restricted administrator for the
specified storage pool. The unrestricted storage
administration class supersedes any restricted storage
class definitions for an administrator. The
administrators authority needs to be corrected.

ANR4281E

unrestricted policy administrator is also
domain domain name.

policy administrator. The specified administrator is also
assigned as the restricted administrator for the
specified policy domain. The unrestricted policy
administration class supersedes any restricted policy
class definitions for an administrator. The
administrators authority needs to be corrected.
ANR4284I

unrestricted storage administrator is also
storage pool storage pool name - restricted
class entry will be deleted.

storage administrator. The specified administrator is
also assigned as the restricted administrator for the
specified storage pool. The unrestricted storage
administration class supersedes any restricted storage
class definitions for an administrator. Because FIX=YES
has been specified for the command, the restricted
administrator storage class will be deleted.

347
ANR4285E ANR4294I
ANR4285E

was detected on a storage volume for
object (Object.ID).

data-integrity error for a file stored on a storage
volume, but the specific volume name is not known. If
fix=yes was specified, the audit process will attempt to
correct the data-integrity error.
ANR4290I
Audit command: License global attributes

could not be found - they will be
created.

license global attributes. Because FIX=YES has been
specified for the command, the information is corrected
by the creation of the global attributes.

ANR4291I
ANR4286E
Audit command: A correctable storage

allocation error detected for volume
volume name.

block allocation information for the specified storage
volume; the error can be corrected.
ANR4287E
Audit command: Storage allocation error

detected for volume volume name - It will
be corrected.

block allocation information for the specified storage
volume; the error will be corrected.
ANR4288E
Audit command: Multiple files allocated

the same disk storage block on volume
volume name.
Explanation: A database audit process finds multiple

files allocated the same disk storage block on the
specified volume; this error cannot be corrected by the
audit process.
Audit command: License global attributes

could not be found.

license global attributes.
ANR4292I
Audit command: Invalid table active

column encountered for license global
attribute - the value will be corrected.

active column license global attribute is invalid.
the active column is reset to a proper value.
ANR4293I
Audit command: Invalid table active

column encountered for license global
attributes.

active column license global attribute is invalid.

ANR4289E
Audit command: Multiple files allocated

the same disk storage block on volume
volume name.
Explanation: A database audit process finds multiple

files allocated the same disk storage block on the
specified volume; this error cannot be corrected by the
audit process.
348
ANR4294I
Audit command: A license node

node node ID - an entry will be created.

node. Since FIX=YES has been specified for the
command, the required license entry will be created
ANR4295I ANR4304E
ANR4295I
Audit command: A license node

node node ID.

node.
ANR4296I
Audit command: An invalid license node

assignment entry was found for node
node ID - the entry will be deleted.

license node assignment entry is invalid. Because
FIX=YES has been specified for the command, the node
entry is deleted.
ANR4297I
Audit command: An invalid license node

assignment entry was found for node
node ID.

license node assignment entry is invalid.
ANR4298I
Expiration thread already processing unable to begin another expiration

process.

ANR4300I
Audit command: Invalid audit interval

encountered for license global
attributes.

audit interval license global attribute is invalid.
ANR4301I
Audit command: Invalid last audit date

encountered for license global attribute the value will be set to 0.

last audit date license global attribute is invalid.
the last audit date is set to 0. The next execution of
AUDIT LICENSES will set a new last audit date.
ANR4302I
Audit command: Invalid last audit date

encountered for license global attribute.

last audit date license global attribute is invalid.
ANR4303E
Audit command: Inventory references for

object(Object.ID) deleted.
Explanation: The expiration thread is already

processing. The processing expiration thread is either
an EXPIRE INVENTORY command or is the automatic
background expiration process. In either case, another
expiration process cannot be started until the current
expiration process completes or is canceled.
Explanation: A database audit process deleted all

inventory references for the specified object ID. This
process corrects a data-integrity error if FIX=YES was
specified.
System action: Current expiration process continues.

to determine the status of the current expiration
process.
ANR4304E
ANR4299I
Audit command: Invalid audit interval

encountered for license global attribute the value will be set to the default.

audit interval license global attribute is invalid. Because
FIX=YES has been specified for the command, the audit
interval is reset to the default value.
Audit command: object name missing entry

for cluster cluster ID - cluster entries
deleted.
Explanation: A database audit process is missing a

corresponding entry for the specified comparison object
and cluster ID. This process indicates a data-integrity
error for the database cluster information. If FIX=YES
was specified, the invalid cluster information will be
deleted.
349
ANR4305E ANR4314I
ANR4305E
Audit command: object name missing entry

for cluster cluster ID.
Explanation: A database audit process is missing a

corresponding entry for the specified comparison object
and cluster ID. This indicates a data-integrity error for
the database cluster information.

ANR4310I

space-managed objects.

about space-managed client objects is currently being
ANR4306I
AUDITDB: Processed number of entries

database entries (cumulative).

database entries that have been processed during
database audit processing.
System action: Database audit processing continues.
ANR4311I
Audit command: Object entry for

space-managed object object.ID not
found - entry will be created.

object entry for the specified space-managed object.
an object entry is created by using default values.
ANR4307I

external space-managed objects.

about external space-managed client objects is currently
being examined by the database audit process.
ANR4308I
Audit command: External space-managed

entry for node node ID and file space
filespace ID is missing a corresponding
space-managed object entry - the
external space-managed entry will be
deleted.

external space-managed entry is missing a
corresponding space-managed entry. Because FIX=YES
has been specified, the orphaned external
space-managed entry is deleted.

ANR4312I
Audit command: Object entry for

space-managed object object.ID not
found.

object entry for the specified backup object.
ANR4313I
Audit command: Space-managed object

(object ID) for node node ID and file
space filespace ID has one or more
incorrect fields - the values will be
corrected.
Explanation: A database audit process determined

that one or more field values for the specified
space-managed object is not valid. Because FIX=YES
was specified the values are corrected.
ANR4309I

entry for node node ID and file space
filespace ID is missing a corresponding
space-managed object entry.

external space-managed entry is missing a
corresponding space-managed entry.
350
ANR4314I

space filespace ID has one or more
incorrect fields.

that one or more field values for the specified
space-managed object is not valid.
ANR4315I ANR4323E
ANR4315I

space filespace ID is missing the
corresponding external space managed
entry - the entry will be created.

the space-managed object entry is missing a
corresponding external space managed entry. Because
FIX=YES was specified, the missing entry will be
created.
ANR4319I

not found for object object.ID - object
entry will be deleted.

space-managed object entry for the specified object.
Because FIX=YES was specified the object entry will be
deleted.
ANR4320I

not found for object object.ID.

space-managed object entry for the specified object.
ANR4316I

space filespace ID is missing the
corresponding external space managed
entry.

ANR4321I

the space-managed object entry is missing a
corresponding external space-managed entry.
ANR4317I

object (object ID) for node node ID and
file space filespace ID has one or more
incorrect fields - the values will be
corrected.

that one or more field values for the specified external
space-managed object is not valid. Because FIX=YES
was specified, the values will be corrected.
ANR4318I

object (object ID) for node node ID and
file space filespace ID has one or more
incorrect fields.

that one or more field values for the specified external
space-managed object is not valid.

found as an space-managed object correcting the invalid copy type

invalid copy type for the specified object ID, but finds
a corresponding space-managed object for the entry.
the invalid copy type is corrected.
ANR4322E

domain name does not have a valid space
management technique defined.

management class that does not have a valid value
specified.
ANR4323E

domain name does not have a valid space
management technique defined - the
default value will be set.

specified. Because FIX=YES was specified for the
AUDITDB operation, the default space management
351
ANR4324E ANR4331E
technique value will be set for the management class
specified.
AUDITDB operation, the default MIGREQUIRESBKUP

value will be set for the management class specified.
User response: Refer to the DEFINE MGMTCLASS

command in the Administrators Reference for valid
values.

values.
ANR4324E

domain name does not have a valid
AUTOMIGNONUSE value specified.

specified.
ANR4325E

AUTOMIGNONUSE value defined - the

AUDITDB operation, the default AUTOMIGNONUSE
value will be set for the management class specified.
ANR4328W

storage pool specified for the space management
destination of the specified management class that is
not defined in the server database. If this management
class is used in an active policy set, then migration
operations will fail when attempting to put client data
in the destination.
missing storage pool or the UPDATE MGMTCLASS
command to update the management class to refer to
an existing storage pool.
ANR4329I

values.
ANR4326E

MIGREQUIRESBKUP value specified.

specified.
ANR4327E

MIGREQUIRESBKUP value defined the default value will be set.

352

name, specified as a space management
destination for management class
management class name, policy set set
exist.
Audit command: Inactive reference found

for active backup entry (Object.ID) - the
inactive reference will be deleted.
Explanation: A database audit process found that an

active backup entry for the specified object has a
corresponding inactive backup entry. Since FIX=YES
was specified for the command, the information is
corrected by deleting the inactive backup object entry.
ANR4330I
Audit command: Inactive reference found

for active backup entry (Object.ID).
Explanation: A database audit process found that an

active backup entry for the specified object has a
corresponding inactive backup entry.
ANR4331E
command process terminated, no

matching device classes.
Explanation: The server did not find any device class

names matching the specifications entered in the
RECONCILE VOLUMES command.
ANR4332W ANR4340W
User response: Use the QUERY DEVCLASS command
to determine which device classes are defined on the
server and reissue the RECONCILE VOLUMES
command.
the volumes associated with the given device class.

System action: The volumes are reconciled and
inconsistent volumes are displayed.
ANR4332W
This command will compare all volumes

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

process ID.
Explanation: The RECONCILE VOLUMES command

for the specified device class has ended.
Explanation: During the execution of a RECONCILE

VOLUMES command, any data a volume named
would be unavailable to users.
User response: For complete details on the results of

the RECONCILE VOLUMES command, examine the
previous messages.

continue.
ANR4337W
User response: Enter 'Y' to reconcile the volumes or

'N' to stop the process.
ANR4333W
This command will discard any

references to volumes used by the
specified device class(es) that are
missing from the associated server,
thereby rendering the data
unrecoverable; the valid volumes will
be inaccessible to users until the
Explanation: During the execution of a RECONCILE

VOLUMES command, any data on a volume being
reconciled would be unavailable to users. After the
command has ended, any inconsistent volumes found
will be discarded.
continue.
User response: Enter 'Y' to reconcile the volumes or
'N' to stop the process.
ANR4334I
command (Repair) process started,

process ID process ID.
Explanation: As the result of a RECONCILE

VOLUMES command that specified FIX=YES, the
process whose ID is displayed has begun reconciling
the volumes associated with the given device class.
invalid volumes are displayed.
ANR4335I
command (Inspect Only) process started,

process ID process ID.

VOLUMES command that specified FIX=NO, the
process whose ID is displayed has begun reconciling
command process terminated - process

canceled.
Explanation: During processing of a RECONCILE

VOLUMES command, the process performing the
reconcile was canceled.
System action: The RECONCILE VOLUMES
command is ended.
ANR4338W
command process terminated - sufficient

recovery log space is not available.

VOLUMES command, the source server does not have
sufficient recovery log space to continue.
command is ended.
User response: If necessary, make more recovery log
space available to the source server.
ANR4339W

database space is not available.

sufficient database space to continue.
command is ended.
User response: If necessary, make more database
space available to the source server.
ANR4340W
command process terminated - thread

resource not available.

VOLUMES command, the source server cannot start a
thread for the reconcile process.
command is ended.
353
ANR4341W ANR4354W
User response: Reissue the RECONCILE VOLUMES
command. If the error persists, it may indicate a
shortage of source server memory.
ANR4341W


enough memory available to complete the command.
command is ended.
User response: If necessary make more memory
available to the source server.
ANR4342W
command process terminated - lock

conflict detected.

VOLUMES command, the source server cannot obtain a
required lock.
command is ended.
User response: Reissue the RECONCILE VOLUMES
command.
ANR4343W
command process terminated - internal


VOLUMES command, an internal server error occurs
on the source server.
command is ended.
ANR4344I
command started for device class device

class (process ID process ID).
found or deleted are displayed.

the RECONCILE VOLUMES command for the shown
device class, examine the previous messages.
ANR4346I
command completed for device class

device class; (process ID process ID);
volume count volumes inspected, volume
count invalid volumes found.
Explanation: The RECONCILE VOLUMES process

whose ID is displayed has finished reconciling volumes
associated with the given device class. The number of
volumes reconciled and the number of invalid volumes
found are displayed.
the RECONCILE VOLUMES command for the shown
device class, examine the previous messages. If you
suspect that volumes were inaccessible because of
communications problems, correct the problems and
retry the RECONCILE VOLUMES command. If the
errors are valid, reissue the reconcile volumes
command with FIX=YES so that the source server can
attempt to correct the information.
ANR4352I
Contacting Server server name

reconciliation process is attempting to obtain volume
information from the shown server.
System action: The reconciliation process continues.
ANR4353I
Cancel in progress

whose ID is displayed has started reconciling volumes
associated with the given device class.

reconciliation process has been canceled. The process
will end shortly.

inconsistent volumes are displayed.
System action: The reconciliation process terminates

ANR4345I
command completed for device class

device class; (process ID process ID);
volume count volumes inspected, volume
count invalid volumes found, volume
count volumes deleted.

whose ID is displayed has finished reconciling volumes
associated with the given device class. The number of
volumes reconciled and the number of invalid volumes
354
ANR4354W
command: Source server not authorized

to reconcile target server server name.

VOLUMES command, the source server was not
permitted to reconcile volume on the shown target
server.
User response: If the source server should have
ANR4355W ANR4358W
permission to reconcile volumes on the shown target
server, issue the UPDATE SERVER command with
FORCESYNC=YES to cause the target server to accept
reconcile operations for the source server. Reissue the
RECONCILE VOLUMES command.
ANR4355W
command: Volume volume name not valid,

source server missing corresponding
entry for target server.

VOLUMES command, the volume shown was reported
by the target server and it has no matching volume on
the source server.
User response: The database on either the source or
target server has been regressed by either a RESTORE
DATABASE operation or some system facility external
to the server. Investigate the action that caused one or
both of the databases to be regressed to there current
condition. If a newer database images exist for that
server, consider restoring the server to that point in
time. If the condition of the database on each server is
acceptable and the RECONCILE VOLUMES command
was issued with FIX=NO, reissue the RECONCILE
VOLUMES command with FIX=Yes to have the volume
deleted from the target server.
ANR4356W

target server missing corresponding
entry for source server.

VOLUMES command, the volume shown was found on
the source server and it has no matching volume on the
target server.
target server has been regressed by either an RESTORE
condition. If a newer database images exist for that
time. If the RECONCILE VOLUMES command was
issued with FIX=Yes and the volume is defined in a
storage pool, the access mode of the volume will
changed to unavailable to prevent attempted mounts
on the source server. If the condition of the database on
each server is acceptable, issue the DELETE VOLUME
or DELETE VOLHISTORY command on the source
server to remove the volume from the database.
ANR4357W

target server volume refers to device
class device class that does not exist on
the source server.

the target server and it is associated with the device
class shown. The source server has NO corresponding
device class.
both of the databases to be regressed to their current
condition. If a newer database image exist for that
time. In the case of a volume in the VOLHISTORY, the
device class may have been deleted from the source
server. If possible, issue the DEFINE DEVCLASS
command to correct the situation. If the condition of
the database on each server is acceptable and the
RECONCILE VOLUMES command was issued with
FIX=NO, reissue the RECONCILE VOLUMES
command with FIX=Yes to have the volume deleted
from the target server.
ANR4358W

the attributes of the volume on target
server do not match the attributes on the
source server.

both the source and target server, but the attributes
describing the volume does not match.
target server has been regressed by either a RESTORE
acceptable, additional actions will have to be taken
because RECONCILE VOLUMES FIX=YES is unable to
correct this situation. In the case of a volume in the
VOLHISTORY, an IMPORT PREVIEW=YES or a
RESTORE DATABASE PREVIEW=YES will determine
the integrity of the volume. If the volume is in error, a
DELETE VOLHISTORY will remove the volume from
both the source and target servers. In the case of a
volume in a storage pool, an AUDIT VOLUME
FIX=NO will determine the integrity of the volume. If
errors are found, an AUDIT VOLUME FIX=YES may
make some data on the volume accessible. Otherwise,
issue the DELETE VOLUME command on the source
server to remove the volume from both the source and
target servers.

355
ANR4359W ANR4363W
ANR4359W

the size of the volume on target server
does not match the size on the source
server.

both the source and target server, but the size of the
volume does not match.
correct this situation. In the case of a volume in the
VOLHISTORY, an IMPORT PREVIEW=YES or a
RESTORE DATABASE PREVIEW=YES will determine
the integrity of the volume. If the volume is in error, a
DELETE VOLHISTORY will remove the volume from
both the source and target servers. In the case of a
volume in a storage pool, an AUDIT VOLUME
FIX=NO will determine the integrity of the volume. If
errors are found, an AUDIT VOLUME FIX=YES may
make some data on the volume accessible. Otherwise,
issue the DELETE VOLUME command on the source
server to remove the volume from both the source and
target servers.
ANR4360W

the type of the volume on target server
does not match the type on the source
server.

both the source and target server, but the type of the
volume does not match. For example, the volume on
the target server is defined in a storage pool, but the
target server indicates that volume was used for a
DATABASE BACKUP.
condition. If a newer database image exists for that
correct this situation. These actions may have to be
performed on one or both servers. Use the QUERY
356
VOLHISTORY and QUERY VOLUME commands on

both servers to determine the volume type on each
server. In the case of a volume in the VOLHISTORY, a
DELETE VOLHISTORY on the appropriate server that
will remove the volume on that server. In the case of a
volume in a storage pool, the DELETE VOLUME
command on the appropriate server will remove the
volume on that server.
ANR4361W

the target server has reported damage to
all or part of the volume.

both the source and target server, but the target server
has reported damage to all or part of the volume.
User response: On the target server, an audit with
FIX=NO of the volumes in the storage pool used by the
source server will indicate what which volume on the
target server is damaged. This AUDIT VOLUME
command may be able to reset the damaged indicator
in the database if the damage was temporary due to
hardware problems (for example, dirty tape heads). If
the volume on the target server is in a primary storage
pool that has previously been backed up to a copy
storage pool, attempt to correct the damage by using
the RESTORE STGPOOL command. If attempts to
correct the damage on the target server fail, an AUDIT
VOLUME command FIX=YES from the source server
will mark as damaged in the source server database
each file that is inaccessible and those files will not be
accessed for future operations. If the files are part of an
aggregate, the entire aggregate will be marked
damaged. If a usable copy of the file exists in another
storage pool, that copy may be accessed for future
operations involving the file.
ANR4362W
command: Invalid volume volume name

deleted from server server name for
device class device class.

volume shown whose information is displayed is
deleted from the target server.
ANR4363W
command: Volume volume name access

changed to access mode.

access mode of the source volume has been changed to
the value shown.
System action: The volumes access mode is changed.
ANR4364W ANR4371E
User response: Review any additional messages
issued by the RECONCILE VOLUMES command and
correct the errors that set the volume to unavailable, or
use the DELETE VOLUME command to remove it from
the system.
FIX=YES and the server will attempt to recreate the

missing volume definition. If the server cannot recreate
the missing volume information, the server will delete
the inaccessible file data.
ANR4368I
ANR4364W
command: Unable to connect to target

server server name.
Explanation: During processing of indicated

command, the source server was unable to maintain
communications with the shown target server.
System action: The command process continues.
User response: Check both the source server and the
target server for any additional messages that might
further describe the communications problem.
ANR4365W
command: Prefix for volume volume name

does not match the device class prefix.

both the source and target server, but the beginning
portion of the high-level archive file name (the prefix)
on the target server does not match the prefix in the
device class on the source server.
User response: Verify that the prefix in the device
class on the source server is correct and update it if
necessary. Use the RECONCILE VOLUMES FIX=YES
command on the source server to rename the target
archive objects to match the device class on the source
server.
ANR4366I
command: Prefix for volume volume name

was changed to match the device class
prefix.

VOLUMES FIX=YES command, the beginning portion
of the high-level archive file name (the prefix) on the
target server was changed to match the prefix in the
device class on the source server.
System action: The prefix is corrected.
Audit command: Attributes for group

group.ID and member member.ID are not
correct - the attributes are corrected.

attributes for the specified group ID and member ID do
not match attributes for the corresponding primary
backup object. Because FIX=YES was specified for the
command, the incorrect attributes are corrected.
ANR4369I
Audit command: Attributes for group

group.ID and member member.ID are not
correct.

attributes for the specified group ID and member ID do
not match attributes for the corresponding primary
backup object.
User response: The AUDITDB process should be
re-issued with FIX=YES specified.
ANR4370E
The source server is not authorized to

create volumes on target server server
name.
Explanation: The source server has attempted to

create a volume on the shown target server, but the
operation failed because the source server does not
have the authority to create volumes.
User response: If the source server should have
permission to create volumes on the shown target
server, issue the UPDATE SERVER command with
FORCESYNC=YES to cause the target server to accept
volume create operations for the source server. Retry
the failing operation.

ANR4371E
ANR4367E
Audit command: A storage volume


database audit and indicates that the storage volume
defined.
Information on the source server does

not match information on target server
server name.
Explanation: The source server has determined that

information contained on the shown target server no
longer matches information contained on the source
server.
User response: Issue the RECONCILE VOLUMES
command to determine the problem. If possible, correct
357
ANR4372E ANR4377E
the problem and retry the failing operation.
ANR4372E
The password on the source server does

not match the password on target server
server name.

update both the source password and the target
password. An error occurred that prevented the source
server from updating the target server. The passwords
no longer match.
User response: On the target server, issue the
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
command to change the password to match the new
password on the target server. Retry the failing
operation.
ANR4373E
Session rejected by target server server

name, reason: rejection reason.
Explanation: The source server has attempted to open

a session with the shown target server. The session was
rejected for the indicated reason.
further describe the reason the session was rejected. For
a reason of AUTHENTICATION FAILURE, ensure that
both the source and target servers are using the same
password. For a reason of NO RESOURCE, ensure that
the target server is enabled, has sufficient DB, LOG,
and memory resource to support the source server
session and that the node name of the source server is
not locked or in use. If this is a routed command, check
to make sure that the administator id being used to
route the command is not locked or in use. For a
reason of LICENSE FAILURE, ensure that the target
server is properly licensed to support the source server
session. For a reason of DOWN LEVEL, ensure that the
target server program is a level new enough to support
the source server session. For a reason of NODE TYPE,
the source server is not allowed to establish a session
with the given target server. The NODETYPE on the
target server is CLIENT. The NODENAME parameter
of the server definition on the source server is incorrect.
The NODETYPE parameter of the registered node on
the target server is incorrect and should be
NODETYPE=SERVER. For a reason of INTERNAL
ERROR, use the messages on the target server to
determine the problem and contact your service
representative. Retry the failing operation.
358
ANR4374E
Session failure, source server detected

an internal error.
Explanation: The source server ends the session

because an internal logic error is detected.
System action: The source server ends the session and
the administrator can examine server messages issued
prior to this message. The QUERY ACTLOG command
can be used to view the activity log and search for
messages. If the error cannot be isolated and resolved,
ANR4375E
Session failure, source server has


available.
ANR4376E
Session failure, target server server name

is locked on the source server.

because shown target server is locked from source
server access.
User response: Before the source server is permitted
to access the target server, a properly authorized
administrator must unlock the target server.
ANR4377E

is not defined on the source server.

because shown target server is not defined on the
source server.
User response: Before the source server is permitted
to access the target server, the target server must be
properly defined.
ANR4378E ANR4385I
ANR4378E
For device class device class, the retry of a

session with target server server name has
timed out.

re-establish a session with the shown target server, but
the RETRYPERIOD from the given device class has
been exceeded.
System action: The source server ends the operation.
User response: Ask an authorized administrator to

submit the request on the use of the target server using
REGISTER NODE command. Retry the failing
operation.
ANR4382E
Session failure, policy information from

target server server name is incomplete,
missing policy object.
User response: Determine it the target server is

having a problem or considering increasing the
RETRYPERIOD value.

because the shown target server has provided policy
information which is incomplete. The missing policy
object is shown.
ANR4379E

The source server was unable to update

the password on target server server
name.

update the target password. An error occurred that
prevented the source server from updating the target
server.
User response: Use the appropriate commands on the

target server to complete the policy definitions being
used by the source server. Retry the failing operation.
ANR4383E

User response: On the target server, determine the
cause of the problem and correct it. It may be necessary
for an administrator to correct the passwords with the
following actions. On the target server, issue the
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
command to change the password to match the new
password on the target server. Retry the failing
operation.
ANR4380E
The source server was unable to update

the server validation key on target
server server name.

update its server validation key on the target server.
An error occurred that prevented the source server
from updating the target server.
User response: On the target server, determine the
cause of the problem and correct it. It may be necessary
for an administrator to correct the keys with the
following actions. On the source server, issue the
UPDATE SERVER command with FORCESYNC=YES to
cause an attempt to synchronize the keys on both the
source and target servers. Retry the failing operation.

because the shown target server has aborted the current
transaction for the given reason.
further describe the reason the transaction was aborted.
Retry the failing operation.
ANR4384E
The source server was unable to register

with target server server name.

register with the shown target server. An error occurred
that prevented the source server from registering with
the target server.
Node node name is not allowed to

establish a session as a target server.
Explanation: The node specified has attempted to

establish a session with this system and this is not
permitted due to the NODETYPE for this node.
User response: To allow the specified node to
establish a session as a target server, the node must be
registered with a NODETYPE of SERVER. Or else
change the node name on the target server to a node
name that is allowed to establish a session using a
node name that was registered with the
NODETYPE=SERVER parameter specified.
ANR4385I
ANR4381E

has aborted current transaction; reason:
abort reason.
Session retry in progress with target

server server name.
Explanation: The source server is attempting to

re-establish a session with the shown target server.
Session retry processing occurs when the source server
has lost the connection with a target server and a
RETRYPERIOD value is specified,

359
ANR4386I ANR4397E
System action: The source server attempts to contact
the target server.
User response: Determine if the target server is

having a problem and considering canceling the
operation on the source server or correcting the
problem with the target server.
User response: Issue the command QUERY PROCESS

to determine the process number for the expiration
process and then issue the command CANCEL
PROCESS for that process number. This will cancel the
current expiration process.
ANR4386I
ANR4391I
Session retry was successful for target

server server name.
Explanation: The source server has re-establish a

session with the shown target server.
System action: Source server processing continues.
ANR4387E

name not registered as TYPE=CLIENT.

client session because the client node name is not
registered as a node of TYPE=CLIENT. This node name
is already in use either as a server definition as defined
by a DEFINE SERVER command or else as a node of
TYPE=SERVER using the REGISTER NODE command.
User response: Issue a QUERY NODE TYPE=SERVER
or a QUERY SERVER to determine which server
definition already is using this node name. This client
should be registered using the REGISTER NODE
TYPE=CLIENT command and specify a name that is
not in use by any other nodes or server defined to this
server.
ANR4388W
No expiration process to cancel.
Expiration processing node node name,

filespace filespace name, fsId filespace id,
domain domain name, and management
class management class name - for type
type files.
Explanation: Expiration processing is currently

evaluating information for the node, filespace, domain
name, and management class specified for the file type
indicated.
ANR4395I
Audit command: Invalid node type

encountered for node node name.

invalid node type for the node indicated, and FIX=YES
was not specified.
User response: You may want to run this command
again, specifying FIX=YES so that the audit process can
correct the problem.
ANR4396I
Audit command: Invalid node type

encountered for node node name. The
default type will be set.
Explanation: The CANCEL EXPIRATION command

was issued but there were no expiration processes
currently running.

invalid node type for the node indicated. Because
nodes type to the default value.
User response: If you want the node type for the

specified node to be other than the default, you must
remove and re-register the node with the correct type
ANR4389I
Expiration process cancelled.

was issued and successfully cancelled the current
process.
ANR4397E
Audit command: An invalid data format

was encountered for storage pool storage
pool name.

invalid data format for the specified storage pool.
ANR4390E
CANCEL EXPIRATION failed - unable

to cancel expiration process.

was issued but encountered an error. Due to this error,
the command was unable to cancel the process.
360

ANR4398E ANR4408I
ANR4398E
Audit command: An invalid data format

was encountered for storage pool storage
pool name - the data format will be
assigned its default value.

ANR4405I

invalid data format for the specified storage pool.
System action: Because FIX=YES has been specified
for the command, the audit process assigns the default
value to the data format. Audit processing continues.
User response: If you want the data format for the
specified storage pool to be other than the default, you
must delete and re-define the storage pool with the
desired type after the audit command has completed.
ANR4399I
Expiration processing node node name for backupset type files.
Explanation: Expiration processing is currently

evaluating information for backup sets for the node
specified.
Explanation: The database dump image loaded by the

LOAD command was not consistent. A database audit
(AUDITDB) with FIX=YES is required to return the
database to a consistent state.
System action: Server database load processing
completes.
User response: To check the database for
inconsistencies and correct any inconsistencies, use the
database audit (AUDITDB) utility as described in the
Administrators Reference.
ANR4406I

ANR4402I
Database Dump command: Database

update activity resumed
Database Load command: Loaded an

inconsistent dump image - a database
audit (AUDITDB) IS REQUIRED with
FIX=YES.
Audit command: Client option Client

option name sequence number option
sequence number is not a member of an
optionset. The option will be deleted.
Explanation: A database audit process found that the

specified client option does not have a corresponding
optionset. The option is deleted.
Explanation: Database update activities that were

suspended by the database dump process are restarted.
ANR4407I

ANR4403I
Database Load command: Database dump

image is consistent - a database audit
(AUDITDB) will NOT be required if
this load completes successfully.
Explanation: The database dump that is currently

being loaded by the LOADDB process is a consistent
database image. This process implies that a database
audit (AUDITDB) will not be required if the load
completes successfully.
continues.
User response: None
ANR4404I
Database Load command: Loaded a

consistent dump image - a database
audit (AUDITDB) is NOT required.
Explanation: The database dump image loaded by the

LOAD command was consistent. A database audit
(AUDITDB) is not required. The server may be started
normally.

sequence number is not a member of an
optionset.

specified client option does not have a corresponding
optionset. The option is deleted.
ANR4408I

sequence number in optionset optionset
name is not a valid option. The option
will be deleted.

specified client option is not a valid option. The option
is deleted.

completes.
361
ANR4409I ANR4417W
ANR4409I

sequence number in optionset option set is
not a valid option.

specified client option is not a valid option.
ANR4414I
Data Base Space expansion Is Needed,

megabytes needed Megabytes needed.
Explanation: The database is above the utilization

percentage defined in a DEFINE SPACETRIGGER DB
command. An expansion of the indicated number of
megabytes are needed to be above the space trigger
utilization value.
System action: Space expansion begins if supported
on this platform.
ANR4410I
Triggered space expansion will be

retried in number of seconds seconds.

during a triggered space expansion for the database
and/or recovery log, the current expansion stops but
will be retried after the time period shown.
period and then retries to expand the database and/or
recovery log.
stopped the expansion. If the problem persists, contact
ANR4411I
Triggered space expansion retry delay

ended; checking space trigger criteria.
Explanation: Because a triggered space expansion had

been stopped due to a problem, the system waited
before retrying. The retry wait period has ended, and
the system can now retry to expand space for the
database and/or recovery log.
System action: Space expansion begins.
ANR4412I
Data Base and Recovery Log Space

expansion triggered.
Explanation: A triggered space expansion had started.

ANR4413I
Recovery Log Space expansion Is

Needed, megabytes needed Megabytes
needed.
Explanation: The recovery log is above the utilization

percentage defined in a DEFINE SPACETRIGGER LOG
command. An expansion of the indicated number of
megabytes are needed to be above the space trigger
utilization value.
System action: Space expansion begins if supported
on this platform.
362
ANR4415I
Data Base and Recovery Log Space

Expansion Completed.
Explanation: A triggered space expansion had

completed.
System action: Normal operations resume.
ANR4416W
Unable to Determine Maximum Number

of Data Base Volume Copies, rc=return
code.
Explanation: The Data Base Space Trigger was in the

processing of expanding the data base by creating new
database volumes. In doing so, the maximum number
of copy volumes for any database volume is
determined. The process of determining this value
failed.
additional database copy volumes are created during
this database space expansion.
User response: Use the Query DBVOL command to
determine if your database volume configuration is
satisfactory. You may use the DEFINE DBCOPY
command to define additional database volume copies,
if necessary.
ANR4417W
Unable to Create Data Base Copy

Volume Data Base Copy Volume for
volume Data Base Volume.

database volumes. In doing so, database copy volumes
are created for mirroring. The indicated database copy
volume could not be created for the primary database
volume named.
System action: Server operation continues. A database
copy volume is not created for the indicated primary
volume.
ANR4418W ANR4424W
command to define additional database volume copies,
if necessary.
command to define additional recovery log volume

copies, if necessary.
ANR4418W
ANR4421W
Unable to Define Data Base Copy

Volume Data Base Copy Volume for
volume Data Base Volume.

database volumes. In doing so, database copy volumes
are created for mirroring. The indicated database copy
volume was created for the primary database volume
named, but could be registered with the server.
copy volumes is not registered for the indicated
primary volume. The database copy volume still exists
on the system.
command to retry the definition of the database
volume copy, if necessary.
ANR4419W
Unable to Determine Maximum Number

of Recovery Log Volume Copies,
rc=return code.
Explanation: The Recovery Log Space Trigger was in

the processing of expanding the recovery log by
creating new recovery log volumes. In doing so, the
maximum number of copy volumes for any recovery
log volume is determined. The process of determining
this value failed.
additional recovery log copy volumes are created
during this recovery log space expansion.
User response: Use the QUERY LOGVOL command to
determine if your recovery log volume configuration is
satisfactory. You may use the DEFINE LOGCOPY
command to define additional recovery log volume
copies, if necessary.
ANR4420W
Unable to Create Recovery Log Copy

Volume Recovery Log Copy Volume for
volume Recovery Log Volume.

creating new database volumes. In doing so, recovery
log copy volumes are created for mirroring. The
indicated recovery log copy volume could not be
created for the primary recovery log volume named.
System action: Server operation continues. A recovery
log copy volume is not created for the indicated
primary volume.
Unable to Define Recovery Log Copy

Volume Recovery Log Copy Volume for
volume Recovery Log Volume.

creating new recovery log volumes. In doing so,
recovery log copy volumes are created for mirroring.
The indicated recovery log copy volume was created
for the primary recovery log volume named, but could
be registered with the server.
log copy volume is not registered for the indicated
primary volume. The recovery log copy volume still
exists on the system.
command to retry the definition of the recovery log
volume copy, if necessary.
ANR4422I
AUDITDB: Insufficient database space

to optimze audit processing.
Explanation: A database audit process found that

insufficient database space is available to optimize
audit processing. If the audit can process, it will take
much longer to complete than if the space was
available.
System action: Audit processing continues of possible,
but may terminate if very little space is available.
User response: Use the dsmserv extend db command
to increase the size of the server datbase and restart the
database audit function.
ANR4423I
AUDITDB: Insufficient database space

to continue audit processing.
Explanation: A database audit process found that

insufficient database space is available to continue
audit processing.
System action: Audit processing terminates.
User response: Use the dsmserv extend db command
to increase the size of the server datbase and restart the
database audit function.
ANR4424W
Database has reached Maximum Size in

Space Trigger.
Explanation: The Data Base Space Trigger was

specified with a maximum size for the data base. That
value has been reached for the size of the database.
additional database space expansion will occur as a
363
ANR4425W ANR4430W
result of the database space trigger.
User response: None. You may review the space
trigger settings and use the UPDATE SPACETRIGGER
DB command to adjust space trigger values.
ANR4425W
Recovery Log has reached Maximum

Size in Space Trigger.
Explanation: The Recovery Log Space Trigger was

specified with a maximum size for the recovery log.
That value has been reached for the size of the recovery
log.
additional recovery log expansion will occur as a result
of the recovery log space trigger.
LOG command to adjust space trigger values.
ANR4426W
Recovery Log can no longer be

Expanded by the Space Trigger.
Explanation: The Recovery Log Space Trigger was

going to automatically expand the recovery log.
Expanding the recovery log would cause the recovery
logs size to exceed 13GB, which is beyond the server
maximum limit for the recovery log.
recovery log is not automatically expanded. No
additional recovery log expansion will occur as a result
of the recovery log space trigger.
LOG command to adjust space trigger values. You may
also backup the data base and/or setup a database
backup trigger to cause the database to be backed up
more often. Backing up the database will decrease the
recovery log utilization and you then use the REDUCE
LOG and DELETE LOGVOLUME command to
decrease the size of the recovery log.
ANR4427W
One or more Recovery Log Volumes

differ in number of copy volumes.
You may use the DEFINE LOGCOPY command to

define additional copy volumes, if necessary. You may
use the DELETE LOGCOPY command to delete
unnecessary copy volumes.
ANR4428W
One or more Data Base Volumes differs

in number of copy volumes.

volumes. In doing so, copy volumes are created for
mirroring, and existing volumes are examined for
mirroring. One or more data base volumes was found
to have a different number of copy volumes than other
volumes of the same type. It is recommended that the
same number of copy volumes be created for each
volume of the same type (database or log).
determine if your volume configuration is satisfactory.
You may use the DEFINE DBCOPY command to define
additional copy volumes, if necessary. You may use the
DELETE DBCOPY command to delete unnecessary
copy volumes.
ANR4429W
Unable to Define Recovery Log Volume

Recovery Log Volume.

creating new recovery log volumes. The indicated
recovery log volume was created, but could not be
log volume is not registered with the server. The
recovery log copy volume still exists on the system.
User response: Use the Query LOGVOL command to
command to retry the definition of the recovery log
volume copy, if necessary. There will be an additional
message in the activity log prior to this message
indicating the reason for the failure.

creating new volumes. . In doing so, copy volumes are
created for mirroring, and existing volumes are
examined for mirroring. One or more recovery log
volumes was found to have a different number of copy
volumes than other volumes of the same type. It is
recommended that the same number of copy volumes
be created for each volume of the same type (database
or log).
ANR4430W

satisfactory. You may use the DEFINE DBVOLUME
command for the database volume named, to retry the

determine if your volume configuration is satisfactory.
364
Unable to Define Data Base Volume

Data Base Volume.

database volumes. The indicated database volume was
created, but could not be registered with the server.
volume is not registered with the server. The database
volume still exists on the system.
ANR4431I ANR4437I
definition of the database volume copy, if necessary.
There will be an additional message in the activity log
prior to this message indicating the reason for the
failure.
ANR4431I
Recovery Log now Eligible for

Expansion.
Explanation: The Recovery Log Space Trigger has

previously hit a point where expanding the recovery
log would have caused the recovery logs size to
exceed 13GB, which is beyond the server maximum
limit for the recovery log. This caused automatic
recovery log expansion to be halted. The recovery log
size has shrunk but once again needs expansion and is
now eligible for expansion.
System action: Server operation continues, and the
automatic recovery log expansion will proceed.
User response: None. None.
password expiration period for a client node, but the

client node is not defined correctly in the server
database.
corrected.
ANR4435I
Audit command: Password expiration

period deleted for unknown client node
node name.

password expiration period for a client node, but the
client node is not defined correctly in the server
database. Because FIX=YES has been specified for the
audit command, the audit function deletes the
password expiration period.
ANR4432W
Data Base can no longer be Expanded

by the Space Trigger.
Explanation: The Data Base Space Trigger was going

to automatically expand the data base. Expanding the
database would cause the size of the database to
exceed 500GB, which is beyond the server maximum
limit for the database.
database is not automatically expanded. No additional
database expansion will occur as a result of the
recovery log space trigger until the database size is less
than the maximum size and the trigger attributes allow
it to be expanded to a size less than the maxium.
DB command to adjust space trigger values. You may
also reduce the database size, if possible.
ANR4433I
Data Base now Eligible for Expansion.
Explanation: The Data Base Space Trigger has

previously hit a point where expanding the database
would have caused the size of the database to exceed
500GB, which is beyond the server maximum limit for
the database. This caused automatic database expansion
to be halted. The database size has shrunk or the space
trigger values have been adjusted to allow expansion.
System action: Server operation continues, and
automatic database expansion may proceed.
ANR4434E

ANR4436E
Audit command: Invalid password

expiration password expiration period for
Explanation: A database audit process finds an invalid

password expiration period for a client node.
corrected.
ANR4437I

expiration period password expiration
period deleted for client node node name.

password expiration period for a client node. Because
audit function deletes the password expiration period,
causing the default, global password expiration period
to take effect for the client node.
that was updated. Use the UPDATE NODE command
to set the correct password expiration period for the
node.

found for unknown client node node
name.

365
ANR4438E ANR4446I
ANR4438E

found for unknown administrator
administrator name.

password expiration period for an administrator, but
the administrator is not defined correctly in the server
database.
corrected.
ANR4439I

period deleted for unknown

password expiration period for an administrator, but
the administrator is not defined correctly in the server
database. Because FIX=YES has been specified for the
audit command, the audit function deletes the
ANR4442E

extended attribute type that is not supported.
corrected.
ANR4443I

expiration password expiration period for

password expiration period for an administrator.
corrected.
ANR4441I

expiration period password expiration
period deleted for administrator
administrator name.

password expiration period for an administrator.
command, the audit function deletes the password
expiration period, causing the default, global password
expiration period to take effect for the administrator.
use the QUERY ADMIN command to examine the
administrator that was updated. Use the UPDATE
ADMIN command to set the correct password
expiration period for the administrator.
366
Audit command: Invalid extended

attribute extended attribute type has been
deleted.

extended attribute type that is not supported. Because
audit function deletes extended attribute.
ANR4444W

ANR4440E
Audit command: Extended attribute

extended attribute type is not a valid
attribute type.
Command: Input volume volume name

Explanation: During a DSMSERV DISPLAY

DBBACKUPVOLUME command, the server cannot
display the necessary information about the specified
backup volume.
System action: The volume is not processed.
Processing continues for all the volumes in the given
volume list.
User response: Examine previous error messages for
the cause of failure.
ANR4445I
Context parameter set to value.
Explanation: Determines if context reporting will be

generated when an ANR9999D error occures. This is
turned on or off with the SET CONTEXTmessaging
command.
ANR4446I
Audit command: Auditing address

definitions.

database audit and indicates that the name address
definitions are being examined by the database audit
process.
ANR4447E ANR4455E
ANR4447E
Audit command: An invalid data mover

type was encountered for data mover
name.

invalid data mover type for the specified data mover.
ANR4448E

type was encountered for data mover
datamover name - the data mover entry
will be removed.

invalid data mover type for the specified data mover.
for the command, the data mover entry will be
removed. Audit processing continues.
User response: If you want the data mover entry to be
defined you must redefine this data mover after the
audit command has completed.
ANR4449E

attribute was encountered for data mover
name.
Explanation: A database audit process encountered an

invalid data mover attribute for the specified data
mover.
ANR4450E

attribute was encountered for data
mover data mover name - the data mover
entry will be removed.

invalid data mover attribute for the specified data
mover.

ANR4452E
Audit command: An invalid disk attribute

was encountered for disk name - the disk

invalid disk attribute for the specified disk. Because
FIX=YES has been specified for the command, the disk
User response: If you want the disk entry to be
defined you must redefine this disk after the audit
command has completed.
ANR4453E
Audit command: An invalid source

attribute was encountered for source
name and destination destination name

invalid source attribute in a path definiton with the
specified source name and destination name.
ANR4454E
Audit command: An invalid source

name and destination destination name the path entry will be removed.

invalid source attribute in a path definition with the
specified source name and destination name. Because
FIX=YES has been specified for the command, the path
User response: If you want the TSM server to use this
path you must redefine the source name, verify the
destination name exists, and then redefine the path

for the command, the data mover entry will be
removed. Audit processing continues.
ANR4455E
Audit command: An invalid destination

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

invalid destination attribute in a path definiton with
the specified source name and destination name.
ANR4451E
Audit command: An invalid disk attribute

was encountered for disk name.


invalid disk attribute for the specified disk.
367
ANR4456E ANR4463E
ANR4456E
Audit command: An invalid destination

name and destination destination name the path entry will be removed.
ANR4460I
Audit command: Invalid KEEPMP setting

KEEPMP setting deleted for client node
node name.

invalid destination attribute in a path definition with
the specified source name and destination name.
the path entry will be removed.

invalid KEEPMP setting for a client node. Because
audit function has deleted the KEEPMP setting, causing
the default, KEEPMP setting to take effect for the client
node.
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

to set the correct KEEPMP setting for the node.
ANR4457E
Audit command: KEEPMP found for

unknown client node node name.

KEEPMP setting for a client node, but the client node is
not defined correctly in the server database.
corrected.
ANR4458I
Audit command: KEEPMP setting deleted

for unknown client node node name.

KEEPMP setting for a client node, but the client node is
not defined correctly in the server database. Because
audit function has deleted the KEEPMP setting.
ANR4459E
Audit command: Invalid KEEPMP setting

KEEPMP setting for client node node
name.

invalid KEEPMP setting for a client node.
corrected.
ANR4461E
Audit command: TCP name, address and

GUID found for unknown client node
node name.
Explanation: A database audit process found a TCP

name, address and globally unique identifer for a client
node, but the client node is not defined correctly in the
server database.
corrected.
ANR4462I
Audit command: TCP name, address and

GUID deleted for unknown client node
node name.
Explanation: A database audit process found a TCP

name, address and globally unique identifer for a client
node, but the client node is not defined correctly in the
for the audit command, the audit function deletes the
TCP name, address and GUID.
ANR4463E
Audit command: Invalid TCP name,

address or GUID length invalid length for

invalid TCP name, address or globally unique identifer
length for a client node.
corrected.
368
ANR4464I ANR4473E
ANR4464I
Audit command: Invalid TCP name,

address or GUID length invalid length
deleted for client node node name.

invalid TCP name, address or globally unique identifer
length for a client node. Because FIX=YES has been
specified for the audit command, the audit function
sets the TCP name, address and GUID to blank. The
values will be reset when the client signs on to the
server.
that was updated. The values should be blank.
ANR4465I
Audit command: An incorrect transaction

group size was found for node node
name.

invalid information used for controlling the transaction
group size for the node indicated.
corrected.
ANR4466I
Audit command: An incorrect transaction

group was found for node node name.
This information will be corrected.

invalid information used for controlling the transaction
group size for the node specified. Because FIX=YES has
been specified, the audit function corrects the
information.
ANR4467E
Audit command: Data Path Type Path was

found for unknown client node node
name.
Explanation: A database audit process found a Data

Path setting for a client node, but the client node is not
defined correctly in the server database.
corrected.
ANR4468I
Audit command: The Data Path Type Path

setting was deleted for unknown client
node node name.
Explanation: A database audit process found a Data

Path setting for a client node, but the client node is not
defined correctly in the server database. Because
audit function has deleted the KEEPMP setting.
ANR4471E
Audit command: Invalid TCP address (

server-prompted scheduling ) or length
invalid length for client node node name.

invalid TCP address or length for a client nodes
server-prompted scheduling..
corrected.
ANR4472I
Audit command: Invalid TCP name or

length for server-prompted
scheduling.invalid length deleted for

invalid TCP name or length for a client nodes
server-prompted scheduling attributes. Because
audit function sets the TCP information to blank. The
values must be reset with the UPDATE NODE
command.
that was updated. The values should be blank.
ANR4473E
Audit command: Node missing from

session initiation attribute for client
node node name.
Explanation: A database audit process found a session

initiation value for a client nodes server-prompted
scheduling but the node definition was missing.
corrected.
369
ANR4474I ANR4481I
ANR4474I

session initiation value for
server-prompted scheduling. Attribute
Explanation: A database audit process found a value

for a client nodes server-prompted session iniiating
attributes, but the node definition was mising. Because
audit function sets the value to the default. The
attribute must be redefined with the REGISTER or
UPDATE NODE commands.
that was updated.
ANR4475E

client address attribute for client node
node name.
Explanation: A database audit process found client

node addressing information for a client nodes
server-prompted scheduling but the node definition
was missing.
corrected.

function, specifying FIX=YES so that the error can be
corrected.
ANR4478I

invalid data path setting for a client node. Because
audit function has deleted the Data Path setting,
causing the default Data Path setting to take effect for
the client node.
to set the correct data path setting for the node.
ANR4479I

session initiation value for
server-prompted scheduling. Attribute
Explanation: A database audit process found client

node addressing information for a client nodes
server-prompted scheduling but the node definition
was missing.
command, the audit function deletes the value. The
information must be redefined with the REGISTER or
UPDATE NODE commands.
that was updated.
ANR4477E
Audit command: An invalid data path type

path setting was found for client node
node name.

incorrect data path setting for a client node.
370
Extraneous or incorrect entry found for a

backup group member.
Explanation: An extraneous or incorrect entry was

found for a member of a backup group.
User response: Issue the AUDITDB command again,
using the FIX=YES parameter.
ANR4480I
ANR4476I
Audit command: An incorrect data path

type path setting was deleted for client
node node name.
Extraneous or incorrect entry fixed for a

backup group member.

found for a member of a backup group. If this was an
incorrect entry, it was fixed. If this was an extraneous
entry, it was deleted.
User response: None, becasue the AUDITDB
processing performed the necessary corrective action.
ANR4481I
Command: Extraneous or incorrect entry

found for a proxy association. Target:
node_id_1 Agent: node_id_2

found for a proxy association.
User response: Issue the AUDITDB command again,
using the FIX=YES parameter.
ANR4482I ANR4490I
ANR4482I
Command: Extraneous or incorrect entry

found for a proxy association. Target:
node_id_1 Agent: node_id_2

found for a proxy association. The entry will be
removed.
User response: None, because the AUDITDB
processing performed the necessary corrective action.
ANR4483I
Node node name issued command: Set

Access copy type file space namehigh-level
addresslow-level address authorized node
name ,authorized owner name.
Explanation: The SET ACCESS command completed.

ANR4484I
Node node name issued command: Delete

Access copy type file space namehigh-level
addresslow-level address authorized node
name ,authorized owner name.
Explanation: The DELETE ACCESS command

completed.
ANR4487I
Explanation: A storage pool space trigger has been

defined for the indicated storage pool, but because the
space expansion percentage is currently set to 0, the
space trigger is disabled.
ANR4488I
A storage pool space trigger has been

defined and enabled for storage pool
storage pool name.
Explanation: A storage pool space trigger has been

defined with a DEFINE SPACETRIGGER command for
the specified storage pool.
The default storage pool space trigger is

defined, but it is disabled.
Explanation: A default storage pool space trigger has

been defined for storage pools associated with a
devtype=DISK or devtype=FILE device class. But it has
been defined without a space trigger; because the space
expansion percentage is currently set to 0, the space
trigger is disabled.
ANR4489I

ANR4485I
The storage pool space trigger is defined

for storage pool storage pool name, but is
disabled.
The storage pool space trigger has been

deleted for storage pool storage pool
name.

has successfully completed for the indicated storage
pool space trigger. Space expansions are no longer
triggered automatically for the specified storage pool. If
a default storage pool space trigger exists, it will apply
to the specified storage pool.

ANR4490I
ANR4486I
A default storage pool space trigger has

been defined and enabled.
The default storage pool space trigger

has been deleted.
Explanation: A default storage pool space trigger has

been defined and enabled. It will be effective for any
storage pools associated with a devtype=DISK device
class or a devtype=FILE device class.

has successfully completed for the default storage pool
space trigger. Space expansions are no longer triggered
automatically for storage pool without a specific space
trigger.
371
ANR4491I ANR4498E
ANR4491I
The storage pool space trigger is

updated and enabled for storage pool
storage pool name.

has successfully completed for the specified storage
pool space trigger. The updated parameters specified
on the command are used to automatically trigger
space expansion for the storage pool.
ANR4495E
Command: Storage pool space trigger is

not defined.
Explanation: The storage pool space trigger cannot be

If a storage pool was not specified, an attempt was
made to delete the default storage pool space trigger,
but no default storage pool space trigger is defined.

command.
ANR4492I
ANR4496E

updated and enabled.

space trigger. The updated parameters specified on the
expansion for storage pools without a specific storage
pool space trigger and which are associated with a
devtype=FILE or devtype=DISK device class.
Command: Storage pool space trigger is

already defined.

defined because it is already defined for the storage
pool. If a default storage pool trigger is being defined,
a default storage pool trigger already exists.
command.

parameters.
ANR4493I
ANR4497E
The storage pool space trigger is

updated, but disabled for storage pool
storage pool name.

has successfully completed for the specified storage
pool space trigger. However, the space expansion
percentage is currently set to 0, which disables the
space trigger.
zero.
ANR4494I

updated, but disabled.

space trigger. However, the space expansion percentage
is currently set to 0, which disables the space trigger.
zero.
372
Command: EXPansionprefix not valid for

storage pool space trigger with storage
pool Storage Pool.

defined with an EXPansionprefix parameter because the
specified storage pool is not associated with a
DISK-type device class. Sequential access storage pools
use their associated directories for creating space when
a space trigger is activated.
command.
command to create a space trigger without using the
EXPansionprefix parameter.
ANR4498E
Command: STGPOOL Storage Pool is not

eligible for a storage pool space trigger.
Explanation: The indicated storage pool cannot have a

space trigger defined, because it is not associated with
a DISK-type or a FILE-type device class, or it is a
RECLAMATIONTYPE=SNAPLOCK storage pool.
command.
User response: Use the DEFINE SPACETRIGGER
command to create a space trigger with a storage pool
whose device class is of type DISK or FILE, or is not a
RECLAMATIONTYPE=SNAPLOCK storage pool.
ANR4499E ANR4506W
ANR4499E
Command: Base backup set name Backup

Set Name could not be found.
Explanation: No full backup sets whose name begins

with the specified backup set name prefix could be
found.
command.
User response: Use the QUERY BACKUPSET
command to list available full backup sets and reissue
the command with the backup set name prefix of an
existing full backup set. If no full backup set exists,
then do not specify the BASE parameter until after a
full backup set has been generated.
ANR4500I
Writing sequential volume history

information to defined files.
Explanation: The server is updating all sequential

volume history files defined in the server options file
with information on sequential volume usage
information. The files updated are those specified with
the VOLUMEHISTORY option in the server options
file.
ANR4503W
The server current date current date is

earlier than the date in a server record
server date.
Explanation: The server has detected that the current

system date is an earlier date than the date in a server
record that is being processed. Possible causes for this
problem are the current system date is invalid, the
server was previously run with a future date, or there
is an error in the server record. If the server was run
with a future date, this message will continue to appear
until that date has passed, or all records with the future
date have been deleted from the server.
System action: Processing continues. The processing
for the current object may not occur as expected.
User response: On the machine on which the server is
running, verify that the system date is correct.
ANR4504E
Command: The specified point in time is

earlier than the point in time of the base
backup set.
Explanation: The point in time specified for the

differential backup set is earlier than the point in time
of its base backup set.

command.
ANR4501I
User response: Reissue the command, specifying a

later point in time.
Sequential volume history information

successfully written to file name.
Explanation: The server is updating all sequential

volume history files defined in the server options file
with information on sequential volume usage
information. Volume history information was
successfully written to the file specified.
ANR4502W
No files have been defined for

automatically storing sequential volume
history information.
Explanation: The server is attempting to update all

sequential volume history files defined in the server
options file with information on sequential volume
usage information. Because no files were configured for
receiving this information, the automatic operation
fails.
User response: To have the server automatically
record sequential volume history information to assist
in server recovery, use the VOLUMEHISTORY option
in the server options file to specify where history
information should be written. If you update the
options file, restart the server.
ANR4505E
Required table of contents could not be

created for backup set for node name as
set name (data type data type).
Explanation: A table of contents could not be created

for the named object set, but a table of contents was
required (TOC=YES was specified or implied).
System action: The backup set is deleted.
User response: Correct the problem that prevented the
table of contents from being created and generate the
backup set again.
ANR4506W

(data type data type) requires a table of
contents.
Explanation: The specified backup set requires a table

of contents, but TOC=YES was not specified.
System action: The server will attempt to create a
table of contents for the backup set. If the table of
contents creation fails, the backup set will be deleted.
373
ANR4510E ANR4516E
ANR4510E
Server could not write sequential

volume history information to volume
history file name.
ANR4513E
A database lock conflict was

encountered in processing sequential
volume history information.
Explanation: While attempting to write sequential

volume history information to defined history files, the
server could not write to the file name specified.
Explanation: While attempting to process sequential

volume history information, the server encountered a
database locking conflict.
System action: The server does not write volume

history information to the file specified
System action: The operation fails. This usually means

that usage for a sequential volume was not properly
recorded for later reference

BACKUP VOLHISTORY command to write sequential
volume history information to the file.
ANR4511E
Volume history file volume history file

name could not be opened.
Explanation: While attempting to write sequential

volume history information to or read information from
defined history files, the server cannot open the file
name specified.
System action: The server does not write volume
history information to or read volume history
information from the file specified
set.
ANR4512E
A database transaction failure was

encountered in processing sequential
volume history information.

volume history information, the server encountered a
database transaction error.
System action: The operation fails. Usage for a
sequential volume was not properly recorded for later
reference.
problems, if possible. If this does not resolve the
problem, contact your support representative.

problems, if possible. If this does not resolve the
problem, contact your support representative.
ANR4514E
Sufficient database space is not

available for the server while processing

volume history information, the server found that
sufficient database space was not available for updates.
reference.
the database by using the EXTEND DB command.
ANR4515E
Sufficient recovery log space is not

available for the server while processing

volume history information, the server finds that
sufficient recovery log space is not available for
updates.
reference.
DEFINE LOGVOLUME command, and extend the size
of the database by using the EXTEND LOG command.
ANR4516E
Server could not read sequential volume

history information from any defined
files.
Explanation: While attempting to read sequential

volume history information from defined history files,
the server finds that it cannot open any of the files
defined in the server options file.
System action: The server does not read volume
374
ANR4517E ANR4524I
history information. If the current server task requires
this information, the task ends.
proper authority to read from the defined volume
history files. If you are doing a database restore, issue
RESTORE DB DEVCLASS=VOL.
ANR4517E
No files have been defined for storing

sequential volume history information information cannot be read.
Explanation: The server is attempting to read from at

least one of the volume history files defined in the
server options file. Since no files were defined for this
information the read operation fails.
System action: Server operation ends.
User response: You can restore the database specifying
the volume names for each restore operation (in order)
up to the desired point-in-time. If a volume history file
is available, specify its name in the server options file
and retry the operation.
ANR4518E
Explanation: A request for storage was made in the

indicated storage pool. The storage pool has a capacity
of the number of megabytes shown. The requested
amount can not be satisfied in the storage pool being
skipped. The next storage pool, if any, will be tried in
an attempt to satisfy the request.
System action: The storage server skips the indicated
storage pool and tries to allocate storage in a next
pool.
User response: More space can be created in the
storage pool by increasing the number of scratch
volumes allowed (use the UPDATE STGPOOL
poolname MAXSCRATCH=xx command), by creating
private volumes in the storage pool (use the DEFINE
VOLUME poolname volname command ), or by
creating a storage pool space trigger to monitor storage
in the storage pool. The storage pool space trigger can
also automatically create new FILE volumes when
space triggers are exceeded (use the DEFINE
SPACETRIGGER STG STGPOOL=poolname command).
ANR4523I
Volume history file file name line line

number does not have the proper format
- read operation fails.
Explanation: The server is attempting to read from a

volume history file and encounters a record that does
not have the proper format.
System action: Server operation terminates.
User response: Examine the file specified to determine
if the invalid record can be located and corrected. If the
file is corrupted or does not contain valid volume
history entries, it cannot be used for the desired
operation.
Storage Pool Space expansion triggered.

Storage Pool storage pool name with
capacity of capacity megabytes requires
percentage percent expansion for
expansion amount bytes of additional
space.
Explanation: A triggered space expansion has started

for the indicated storage pool. The storage pool has a
capacity of the number of megabytes shown. It is being
expanded by the indicated percentage as directed by
the storage pool space trigger for this storage pool, or
by the default storage space trigger if this storage pool
has no dedicated trigger of its own. The percentage is
represented by the additional amount of space
indicated.
ANR4519W
Volume History File does not reflect

latest Storage Agent Updates
Explanation: The storage agent failed to have the

volume history file on the server updated with the
latest changes from the storage agent.
System action: The storage agent continues
processing.
User response: To bypass the problem, a BACKUP
VOLHIST command can be issued from an admin
client connected to the server. The problem may be due
to a temporary loss of communication with the server.
ANR4524I
Volume volume name defined in Storage

Pool storage pool name as a result of
storage pool triggered space expansion.
Explanation: A triggered space expansion has caused

the indicated volume to be created in the storage
shown in the message. The volume definition is the
result of a storage pool space trigger definition which
allocates new space when the space trigger space
threshold is met.
ANR4520I
Storage Pool storage pool name is being

skipped during a space allocation. A
request for request amount megabytes
was made but only available amount
megabytes were available.
375
ANR4525E ANR4539E
ANR4525E
Failure to define volume volume name in

Storage Pool storage pool name. Return
codereturn code.
Explanation: A triggered space expansion has caused

an attempt to create the indicated in the storage pool
shown in the message. The volume creation failed with
the indicated return code. The volume was not added
to the storage pool. Additional messages with specific
information on the failure are displayed from the
volume creation process.
User response: It might be necessary to take action
based on the failure message from the volume creation
process. Such actions might include changing the
storage space trigger definiton, ensuring that hardware
is function properly, or ensuring that the server is set
up with sufficient permissions to access and create files
on the file system to which Tivoli Storage Manager is
writing.
ANR4526E
Storage Pool Space trigger for storage

pool name is ended; the thread resource
not available.
Explanation: The server cannot start a thread to

handle storage pool expansion for the indicated storage
pool.
System action: Server processing continues but the
storage pool is not expanded.
information online or see Appendix B. Allocating
ANR4527W
Storage Pool Space trigger for storage

pool name is disabled after volume
definition failures expansion failures.
Insufficient space for pool expansion.
Explanation: The server failed to complete a storage

pool expansion for the indicated storage pool. The
number of failures in pool expansion is also displayed.
storage pool is not expanded. The storage pool space
trigger for the indicated storage pool is disabled.
User response: Allocate additional storage space to
the server. For storage pools of device type FILE,
additional directories may be added to the list of
directories that the associated device class uses for
storage. If this action is taken, the corresponding
storage agent directories should be added via the
UPDATE PATH command. The storage pool space
trigger may be re-enabled with the UPDATE
SPACETRIGGER STG STPOOL=xx command, where xx
is the storage pool for which expansion has failed ( no
space trigger parameters need be updated ).
376
ANR4528W
Storage Pool Space Expansion for storage

pool name is disabled due to previous
expansion failures. After addressing
space requirements, an UPDATE
SPACETRIGGER STG command must
be issued to allow automatic stgpool
expansion.
Explanation: The server failed to complete a storage

pool expansion for the indicated storage pool. The
storage pool space trigger is disabled due to previous
expansion failures. The storage pool space trigger may
be re-enabled with the UPDATE SPACETRIGGER STG
STPOOL=xx command, where xx is the storage pool for
which expansion has failed ( no space trigger
parameters need be updated ).
storage pool is not expanded. The storage pool space
trigger for the indicated storage pool remains disabled.
This message is re-issued periodically when expansion
is required but the storage pool space trigger remains
disabled.
User response: Allocate additional storage space to
the server. For storage pools of device type FILE,
additional directories may be added to the list of
directories that the associated device class uses for
storage. If this action is taken, the corresponding
storage agent directories should be added via the
UPDATE PATH command. The storage pool space
trigger may be re-enabled with the UPDATE
SPACETRIGGER STG STPOOL=xx command, where xx
is the storage pool for which expansion has failed ( no
space trigger parameters need be updated ).
ANR4539E
There is a mismatch in directory count

between Device Class device class name
and Path Definition for Server server
name. The device class has directory count
directories while the path definition has
path directory count directories.
Explanation: The server was assigning a shared FILE

library volume to a server or storage agent. Share FILE
libraries require a matching number of directories in
the PATH definition for the server or storage agents
access to FILE drives and the servers device class
definition. For example, if the server has the following
device class definition: DEFINE DEVCLASS SFILE
DEVTYPE=FILE MOUNTL=10 SHARED=YES
DIR=D:\DIR1,E:\DIR2,F:\DIR3 a FILE library name
SFILE will be created along with 10 drives named
SFILE1 to SFILE10 in shared library SFILE. Each of
these drives might have scratch volumes created in
directories D:\DIR1, E:\DIR2 or F:\DIR3. (For UNIX
Platforms, substitute UNIX style names in the
example).
For library clients and storage agents, the appropriate
directory paths from those systems must be defined
using the DEFINE PATH command. An example, in
ANR4540E ANR4544E
this case, might be DEFINE PATH STA1 SFILE1
SRCTYPE=SERVER DESTTYPE=DRIVE
DIR=V:\DIR1,W:\DIR2,X:\DIR3 LIBRARY=SFILE
which means that server (or storage agent) STA1
accesses directory D:\DIR1 using V:\DIR1 from the
STA1 system, E:\DIR2 on the server is accessed using
W:\DIR2 on STA1, and that F:\DIR3 is accessed using
X:\DIR3 on STA1. If the number of directories between
the PATH and DEVCLASS do not match, there could
be problem in accessing the resulting file in the future.
System action: Processing continues. Another
directory path is chosen. This might result in a
subsequent access failure by the storage agent.
User response: Use the QUERY DEVCLASS classname
F=D and the QUERY PATH pathname F=D commands
to compare the directory lists for the device class and
the path and ensure that they are synchronized.
ANR4540E

device class id found in DevClass.Dirs
table.

non-existent device class or a device class with an
invalid access strategy for a record in the
Devclasses.Dirs table.
ANR4542E

directory entry with a server which is either not
defined or has an invalid length in the DevClass.Dirs
table. This table relates directories to device classes and
paths. The class ID of the table entry is shown, along
with the server name. However, if the server name has
an invalid length, only blanks are shown.
User response: If the FIX=YES parameter was
specified, the data base record with the incorrect entry
will be deleted. Otherwise, reissue the audit command
with FIX=YES, so that the incorrect record can be
deleted. After records with incorrect entries have been
removed, review directories associated with device
classes and paths with the following commands:
QUERY DEVCLASS F=D QUERY PATH F=D
ANR4543E

removed, review directories associated with Device
classes and Paths with the following commands:
ANR4541E
Audit command: Invalid directory for

device class device class id in
DevClass.Dirs table.

directory entry whose length is longer than allowed for
the indicated device class id in the DevClass.Dirs table,
which relates directories to device classes and paths.
Audit command: Invalid server for device

class device class id in DevClass.Dirs
table. The server name in the table is
server name.
Audit command: Mismatched server for

device class device class id in
DevClass.Dirs table. Server ID in table
is server id. Server ID in data base is
found server id.

directory entry with a server which does not match the
path source name in the DevClass.Dirs table. This table
relates directories to device classes and paths. The class
ID of the table entry is shown, along with the server ID
in the table and the ID that was found when searching
using the source name.

with FIX=YES so that the incorrect record can be
ANR4544E
Audit command: Invalid library for device

class device class id in the DevClass.Dirs
table.

directory entry with a DEST name where the associated
library can not be found. This record is in the
DevClass.Dirs table. This table relates directories to
device classes and paths. The class ID of the table entry
is shown.
specified, the database record with the incorrect entry
377
ANR4545E ANR4555I
has completed. The output volumes used in this

backup may be used in conjunction with any preceding
volumes in the backup series during a database restore
operation.
ANR4545E
Audit command: Invalid drive for device

class device class id in the DevClass.Dirs
table.

directory entry with a DEST name where the associated
drive (DESTNAME ) can not be found. This record is in
the DevClass.Dirs table. This table relates directories to
device classes and paths. The class ID of the table entry
is shown.
specified, the database record with the incorrect entry
ANR4549I
Database dump command: A database

dump is already in progress.
Explanation: This message is issued in response to a

database dump command and indicates that a database
dump cannot be started because a dump is already in
progress.
requested database dump is not started.
User response: Only one database dump can be
started at one time. Use the QUERY PROCESS
command to monitor the dump that is in progress.
When completed, issue the database dump command
to start another database dump if required.
ANR4550I
Full database backup (process process ID)

complete, number of database pages pages
copied.
ANR4552I
Full database backup triggered; started

Explanation: A background process, triggered by the

LOGFULLPCT parameter on a DEFINE
DBBACKUPTRIGGER command, was started to back
up the full contents of the database. The full database
backup process is assigned the process ID shown.
QUERY PROCESS command, or cancel the process by
using the CANCEL PROCESS command.
ANR4553I
Incremental database backup triggered;

Explanation: A background process, triggered by the

LOGFULLPCT parameter on a DEFINE
DBBACKUPTRIGGER command, was started to
incrementally back up the contents of the database. The
incremental database backup process was assigned the
process ID shown.
QUERY PROCESS command, or cancel the process by
using the CANCEL PROCESS command.
ANR4554I
Backed up number of pages backed up of

number of pages to back up in current
operation database pages.
Explanation: Periodically, during a database backup,

the server displays the number of pages backed up.
Explanation: A full database backup process has

completed. The output volumes used in this backup
may be used during a database restore operation.
ANR4555I

ANR4551I
Incremental database backup (process

process ID) complete, number of database
pages pages copied.
Explanation: An incremental database backup process
378

Database backup process process ID
canceled.
Explanation: The database backup process was

canceled by an administrator with the CANCEL
PROCESS command.
System action: The database backup process is ended.
ANR4556W ANR4570E
ANR4556W
Attention: the database backup

operation did not free sufficient
recovery log space to lower utilization
below the database backup trigger. The
recovery log size may need to be
increased or the database backup trigger
parameters may need to be adjusted.
Explanation: A database backup process has

completed. The server is running in roll-forward mode
and the recovery log utilization remains above that
specified in the database backup trigger.
System action: A database backup operation will be
triggered. Unless this situation is corrected, database
backups will be triggered rapidly, one after the other.
User response: If a database backup operation does
not free up enough recovery log space to reset
utilization below the database backup trigger, the
recovery log needs to be extended or the database
backup trigger updated to a higher log full percentage
or a higher log free percentage or a higher minimum
interval.
ANR4560I
Triggered database backup will be

retried in number of seconds seconds.

during a triggered database backup, the current backup
stops but will be retried after the time period shown.
backup trigger criteria is met before triggering another

database backup.
ANR4563I
Unable to trigger database backup - a

database define, delete, extend, reduce,
or backup operation is already in
progress.
Explanation: A database backup was triggered, but a

command that is modifying or backing up the database
is already active.
System action: The backup stops and the server waits
for the retry period to expire and then tries the
database backup again.
ANR4564I
Unable to trigger database backup sufficient memory is not available.
Explanation: A database backup was triggered, but

there is not enough server memory available.

period and then retries a database backup.
ANR4565E

stopped the database backup. If the problem persists,
Explanation: A database backup was triggered, but

the server cannot start a thread for the backup process.
ANR4561I

Triggered database backup retry delay

ended; checking database backup trigger
criteria.
Explanation: Because a triggered database backup had

the system can now retry the database backup.
System action: Database backup begins.
ANR4562I
Database backup criteria is no longer

met; triggered database backup
canceled.
Explanation: Because a triggered database backup had

the system determined that the criteria for triggering a
database backup was no longer met.
System action: The system waits until the database
Unable to trigger database backup thread resource not available.
User response: If the error persists, it may indicate a

shortage of server memory. Allocate additional server
memory.
ANR4570E
Database backup/restore terminated device class device class name not defined.
Explanation: During database backup or restore

processing, an error occurred because the specified
device class is not defined.
System action: If the database backup was started
with the BACKUP DB command, the database backup
is ended and server operation continues. If the database
backup was triggered automatically, the backup stops
and the server waits for the retry period to expire and
then tries the database backup again. A database
restore is terminated.
User response: For database backup, make sure the
specified device class is defined. For database restore
processing, make sure the device class has a definition
379
ANR4571E ANR4577E
in a device configuration file that is pointed to in the
server options file.
ANR4571E
Database backup/restore terminated insufficient number of mount points

Explanation: During database backup or restore, the

server cannot allocate sufficient mount points for the
volumes required.
restore is ended.
User response: For database backup, make more
mount points available if necessary. For database
restore processing, make sure the device class has
sufficient mount points defined in the device
configuration information file that is pointed to in the
ANR4572E
Database restore terminated - excessive

read errors encountered.
Explanation: During database restore, read errors


restore is ended.
cause of the interruption. If the problem cannot be
corrected, contact your service representative.
ANR4575E
Explanation: During a database backup or restore

operation, the server runs out of recovery log space.
server recovery log space available, if necessary. For
database restore, contact your service representative.
ANR4576E
System action: Database restore processing stops.

User response: Use a different device for the restore
operation. If the problem persists, contact your service
representative.
ANR4573E
Database backup terminated - excessive

write errors encountered.
Explanation: During database backup, write errors

then tries the database backup again.
cause of the write errors. If the problem cannot be
corrected, contact your service representative.
Database backup/restore terminated sufficient recovery log space is not

available.
Database backup/restore terminated sufficient database space is not

available.

operation, the server runs out of database space.
then tries the database backup again. The database
restore process attempts to set the database capacity to
the required capacity to hold the database being
restored. If this fails, the restore operation is ended.
server database space available, if necessary. For
database restore, make sure that the size of the online
database is at least the same capacity as the database
being restored.
ANR4577E
Database backup terminated - volume

already in use.

operation, a data transfer operation has been
interrupted and cannot be continued.
Explanation: During a database backup operation, a

export, a database dump, or a database backup
operation (as recorded in the volume history) or is in


ANR4574E
380
Database backup/restore terminated data transfer interrupted.
ANR4578E ANR4583E
then tries the database backup again.
previously used for an export, a database dump, or a
volume history information. The QUERY VOLUME
command may be used to display the names of
volumes that are defined to server storage pools. The
QUERY VOLHISTORY command may be used to
display the names of volumes that have been used for
export, database dump, or database backup operations.
ANR4578E
Database backup/restore terminated required volume was not mounted.

operation, a required volume cannot be mounted,
because the mount request was canceled.
User response: Issue the command again or wait for
the server to retry the backup and make sure the
necessary volumes are accessible. If you are restoring a
database to a given date or doing a roll-forward
restore, restart the entire restore operation. If you are
restoring a single database backup with COMMIT=NO,
reissue the restore command. If you are restoring a
database backup with COMMIT=YES, restore the
complete backup series from the beginning.
ANR4579E
Database backup/restore terminated thread resource not available.

operation, the server cannot start a thread for the
backup process.
User response: Retry the command or wait for the
server to retry the backup if it was started by the
backup trigger. If the error persists, it may indicate a
ANR4580E
Database backup/restore terminated insufficient memory available.

operation, there was not enough server memory
available.
ANR4581W
Database backup/restore terminated internal server error detected.

operation, the server encounters an internal error.
ANR4582E
Database restore terminated - volume

cannot be used.
Explanation: During a database restore operation, a

volume has been mounted but cannot be used.
System action: The restore operation is terminated.
User response: If a volume list was specified on the
command, make sure the correct volume is being
specified and mounted. If no volume list was specified,
ANR4583E
Database backup terminated - output

media full and scratch media could not
be mounted.
Explanation: During a database backup operation, an

out-of-space condition occurred writing to the
sequential media, and a scratch volume cannot be
mounted.
System action: The database backup is ended and
additional volume names on the command, or specify
SCRATCH=YES.
381
ANR4584E ANR4612E
ANR4584E
Database restore terminated incomplete input volume list.
Explanation: The list of volumes needed for the

restore operation was incomplete. At least one volume
needed for the restore operation is missing from the
end of the list.
System action: The database restore is terminated.
User response: If you are using a DSMSERV
RESTORE DB command with the VOLUMENAMES
parameter specified, verify that all the volumes within
a database backup operation are included in the list.
Ensure that all the volume names are specified in the
correct sequential order. For a restore with
COMMIT=NO, reissue the last restore command. For a
restore with COMMIT=YES, restart the restore from the
beginning of the full backup. If you are using a
DSMSERV RESTORE DB command with the TODATE
parameter specified, the server created a list of volumes
needed for the restore operation. Examine the volume
history files to try to determine the error or use a
different volume history file if available. You can also
restore the database by specifying the volume names
for each restore operation up to the desired point in
time.
ANR4590I
Backup type backup series backup series

number operation backup operation in series
stream backup stream within operation
(always 1) sequence backup volume
sequence number in operation taken on date
at time.
System action: The server tries to build the list again

using a different volume history file specified in the
server options file. If no other volume history files are
available, the server stops processing.
User response: If the problem persists, examine the
volume history files to try and determine the error. You
can also restore the database by specifying the volume
names for each restore operation up to the desired
point in time.
ANR4602E
No volumes found for TODATE date

time.
Explanation: No volumes were found in the volume

history files that meet the date and time parameters
specified.
command.
date and time.
ANR4610E
Database volume DB volume name not

found in current configuration.
Explanation: The command specified the name of a

nonexistent database volume.
command.
database volume name.
Explanation: During a DSMSERV DISPLAY

DBBACKUPVOL command, the server displays the
necessary information about a backup volume.
ANR4611E
System action: Processing continues for all volumes in

the given volume list.
Explanation: The command specified that the database

be restored and all updates rolled forward to the most
current state. This process cannot be accomplished
because the server recovery log mode was not set to
ROLLFORWARD; therefore, no update information
exists.
User response: You can use this information to create

a list of volumes for a database restore when a volume
history backup file is not available.
ANR4600I
Processing volume history file file name.
Explanation: During a DSMSERV RESTORE DB

command with the TODATE parameter specified, the
server is processing the listed file in order to build a
list of volumes needed for the restore operation.
ANR4601E
Incomplete volume list found for

TODATE date time - retrying.
Explanation: During a DSMSERV RESTORE DB

command with the TODATE parameter specified, the
server created a list of volumes needed for the restore
operation, but the list was incomplete.
382
Unable to restore database and roll

forward updates - log mode was not
previously set to ROLLFORWARD.

command.
point in time (TODATE/TOTIME) for restore.
ANR4612E
Unable to restore database and roll

forward updates.
Explanation: The command specified that the database

be restored and all updates rolled forward to the most
current state. This process cannot be accomplished
because the internal list of volumes for the most recent
full/incremental backup series is not available. Possible
reasons include:
ANR4619I ANR4634I
v No full backup was taken after setting the recovery
log mode to ROLLFORWARD with a SET
LOGMODE command.
v Only snapshot database backups were created.
command.
point in time (TODATE/TOTIME) for restore.
ANR4619I
Snapshot database backup series

snapshot database backup series using
device class device class.
ANR4630I
Starting point-in-time database restore

(commit).
Explanation: A point-in-time database restore with a

specified list of volumes has started. When this restore
is complete, the database will be committed to the
point in time of this backup.
User response: If you inadvertently specified
COMMIT=YES, restart the restore process from the
beginning, starting with restoring the full backup
(backup operation 0).
Explanation: The device class used for the snapshot

database backup is shown.
ANR4631I

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

ANR4620I
Database backup series Backup series

operation backup operation device class
device class.
Point-in-time database restore (commit)

complete, restore date date time.

Explanation: The device class used for the backup is

shown.
ANR4632I

specified list of volumes has started. When this restore
is complete, the database will not yet be usable.

ANR4621I
Database backup device class device class.
Explanation: The device class for the backup is

shown.
ANR4622I
Volume volume sequence number in backup

operation: volume name.
Explanation: The volume sequence and name for a

full or an incremental database backup are shown.

(no commit).

User response: To complete a database restore where
a volume list is specified, specify COMMIT=YES on the
command when restoring the last set of backup
volumes. If you forgot to specify COMMIT=YES on the
command, issue the last restore command again with
COMMIT=YES.
ANR4633I
Point-in-time database restore (no

commit) complete.

specified list of volumes is complete. The database is
not yet usable.
ANR4623I
Stream stream number in backup operation

volume volume sequence number in backup
stream: Volume name.
Explanation: The stream number, volume sequence

and name for a full or an incremental database backup
are shown.
User response: To complete a database restore where

a volume list is specified, specify COMMIT=YES on the
command when restoring the last set of backup
volumes. If you forgot to specify COMMIT=YES on the
command, issue the last restore command again with
COMMIT=YES.
ANR4634I

to date date time.
Explanation: A point-in-time database restore with the

TODATE parameter specified has begun. When this
restore is complete, the database will be committed to
383
ANR4635I ANR4644I
the point in time of this backup.
ANR4640I

ANR4635I
Point-in-time database restore complete,

restore date date time.
Explanation: A point-in-time database restore with the

TODATE parameter specified has completed. The
database is committed to the point in time of this
backup, which may be different than the TODATE
specified. If this is the case, an additional message will
be displayed.
ANR4636I
Starting roll-forward database restore.
Explanation: A roll-forward database restore has

begun. When this restore is complete, the database will
be returned to its most recent state.
Restored number of database pages pages

from backup series backup series number
operation backup operation in series.
Explanation: At the end of each restored backup, the

server displays the number of database pages restored.
ANR4641I
Sequential media log redo pass in

progress.
Explanation: During a DSMSERV RESTORE DB, the

process of committing incomplete database updates has
begun.
ANR4642I
Sequential media log undo pass in

progress.

process of rolling back incomplete transactions has
begun.
ANR4637I
Roll-forward database restore complete.
Explanation: A roll-forward database restore has

ended. All database backups in the most current
backup series have been restored, and all updates to
the database since the most recent backup have been
rolled forward. The database has been returned to its
most recent state.
ANR4638I
Restore of backup series backup series

number operation backup operation in series
in progress.

server displays the backup series and operation
currently being restored.

ANR4643I
Processed number of log records log

records.
Explanation: Periodically, during the commit of a

point-in-time restore or while rolling forward updates
during a roll forward restore, the server displays the
number of log records processed.
ANR4644I
A full backup will be required for the

next database backup operation.
Explanation: During a point-in-time restore of a

database, this message is displayed to notify the
administrator that the next database backup taken
during normal operation must be a full backup. This
process is normal for point-in-time database restores.
ANR4639I
Restored number of pages restored of

number of pages to restore from current
backup operation database pages.
Explanation: Periodically, during a DSMSERV

RESTORE DB, the server displays the number of pages
restored from the current backup being restored.
384
User response: At the next server restart, do a full

database backup. A full database backup is started
automatically if a DBBACKUPTRIGGER is defined.
ANR4645I ANR4652E
ANR4645I
The restore date reflects the most recent

backup available up to the specified
TODATE.
Explanation: During a DSMSERV RESTORE DB with

the TODATE parameter, the date of the restored backup
was not identical to the date specified on the
command. The backup series that was restored is the
most recent backup series up to and including the
specified date.
ANR4649I
Reducing database assigned capacity to

number of megabytes megabytes.

database, the assigned capacity of the online database
is larger than that of the database being restored.
System action: The assigned capacity of the online
database is reduced to the size required for restore.

User response: Make sure the date of the restored
database is satisfactory. If it is not, restore the database
again by specifying a different TODATE or by restoring
individual database backups.
ANR4646I
Database capacity required for restore is


database, the size of the database being restored is
displayed. The available capacity of the online database
volumes must be at least this size.
ANR4647I
Database available capacity is number of

megabytes megabytes.

database, the available capacity of the online database
volumes is displayed. This capacity must be as large as
the size of the database being restored.
System action: If the available capacity of the online
database volumes is not at least this size, the restore
cannot continue.
User response: If the available capacity of the online
database is not sufficient, reinstall the server with the
required database size, and try the restore operation
again.
ANR4648I
Extending database assigned capacity to

ANR4650E
Restore of backup series current series

operation current operation is not in
sequence; last restored backup was
series previous series operation previous
operation.
Explanation: During a DSMSERV RESTORE DB, a

backup volume was mounted that is not in the correct
sequence.
User response: Ensure volume names are specified in
the correct sequential order. For a restore with
COMMIT=NO, reissue the last restore command. For a
restore with COMMIT=YES, restart the restore from the
beginning of the full backup.
ANR4651E
Restore of backup series current series

operation current operation is not in
sequence; backup is part of another log
epoch.
Explanation: During a DSMSERV RESTORE DB, a

backup volume was mounted that is not in the correct
sequence. The current backup operation cannot be
restored in this series because it belongs to the same
backup series from another point in time.
User response: Restart the database restore from the
beginning of the full backup. Omit all backups from the
offending backup and later from the restore.
ANR4652E
No system message queues available for

shared memory communications.

database, the assigned capacity of the online database
is smaller than that of the database being restored.
However, the available capacity of the online database
volumes is sufficient for restore.
Explanation: While initializing a shared memory

communications session, an attempt to acquire a system
message queue failed with errno 28. This usually
means the system-imposed limit on message queues
has been reached.
System action: The assigned capacity of the online

database is extended to the size required for restore.
System action: The shared memory communications

session is not initialized due to lack of system
resources.
User response: Increase the maximum number of

message queues on the system and try the connection
again. On linux systems, increase the kernel.msgmni
value.
385
ANR4657E ANR4664W
ANR4657E
SNMP: Failed to connect to server at

address address, port port.
Explanation: The SNMP client was attempting to run

a session with the server at the indicated address and
port number in response to an SNMP Get Request,
which causes a Server Script to be run. The subagent
failed to connect to the server.
System action: The SNMP subagent ends this attempt
to run the script and continues operation.
User response: Ensure that the indicated server is up
and able to initiate admin clients using the TCP/IP
protocol.
ANR4659E
SNMP: Communications failure: bad

verb received (verb type).
Explanation: The SNMP client encountered an invalid

communications verb during a session with the server
and is not able to continue processing the session.
System action: The SNMP session ends and subagent
ANR4660I
Connected to SNMP subagent at SNMP

subagent address on port port number.
Explanation: The server has successfully connected to

the SNMP subagent at the indicated address and port.
System action: The server will now register with the
subagent.
ANR4661E
SNMP communication with the

subagent failed because a thread
resource was not available.
Explanation: The server could not continue with

SNMP communication to the SNMP subagent because
sufficient memory is not available for starting
additional processes on the server.
System action: The server discontinues SNMP
information online or see the appendix Allocating
ANR4662W
Failure sending message to SNMP

subagent.
Explanation: The server experienced an error return

code from TCP/IP while sending to the SNMP
subagent. This message is also issued when the SNMP
subagent has an error sending a verb to the server
when acting as an SNMP client. This may be a normal
386
event if either side of the connection is abruptly ended,

as in the case of terminating the subagent program. The
error is reflected in another message for TCP/IP which
further describes the error.
System action: The session is ended. Server operation
continues. If a message is being forwarded to an SNMP
managing node, the message is not sent. If a heartbeat
message was being sent to the subagent, this heartbeat
message is lost and the server attempts to re-start its
session with the SNMP subagent.
User response: If the session is ended as a result of
intentionally stopping either the subagent, no response
is required. Otherwise, ensure that the TCP/IP protocol
stack is functioning by using the tools that come with
the particular TCP/IP suite on the platform in use.
ANR4663W
Failure receiving message from SNMP

subagent.

code from TCP/IP while receiving data from the SNMP
subagent. This may be a normal event if either side of
the connection is abruptly ended, as in the case of
terminating the subagent program. The error is
reflected in another message for TCP/IP which further
describes the error.
continues. If a heartbeat message was being sent to the
subagent, this heartbeat message is lost and the server
attempts to re-start its session with the SNMP
subagent. If the server was attempting to register to the
SNMP subagent, heartbeat messaging will be disabled
until the server is re-started.
intentionally stopping either the subagent, no response
is required. Otherwise, ensure that the TCP/IP protocol
stack is functioning by using the tools that come with
the particular TCP/IP suite on the platform in use.
ANR4664W
Failure in registering with SNMP

subagent.
Explanation: The server experienced a problem while

attempting to register with the SNMP subagent. This
may be due to problems with communication or the
SNMP subagent being unavailable.
System action: Heartbeat messaging will be disabled
until the server is re-started.
User response: Ensure that the subagent is running
and that the TCP/IP protocol stack is functioning by
using the tools that come with the particular TCP/IP
suite on the platform in use.
ANR4665W ANR4672W
ANR4665W
Failure retrying registration with SNMP

subagent.

attempting to re-register with the SNMP subagent after
losing contact. This may be due to problems with
communication or the SNMP subagent being
unavailable.
System action: Registration is re-tried for a number of
attempts before giving up.
ANR4666W
Failure sending heartbeat message to

SNMP subagent.

attempting to send a heartbeat message to the SNMP
subagent. This may be due to problems with
unavailable.
System action: The server will attempt to contact the
SNMP subagent again and re-synchronize.

ANR4669W
Heartbeat message was not accepted by

SNMP subagent.

subagent. The SNMP subagent was unable to accept the
heartbeat message. If the subagent was stopped and
re-started, this is a normal message.
System action: The server will attempt to contact the
SNMP subagent again and re-synchronize.
ANR4670W
Failure in opening session with SNMP

subagent.

attempting to open a session with the SNMP subagent.
System action: Processing continues. Heartbeat and
message forwarding function will not be available.


suite on the platform in use. If heartbeat and message
forwarding functions are required, re-start the server.
ANR4667W
ANR4671W
Failure retrying heartbeat message to

SNMP subagent.

subagent. This may be due to problems with
unavailable.
System action: The server attempted to contact the
SNMP subagent again and re-synchronize, but this too
failed. Heartbeat functions are disabled until the server
is re-started.
suite on the platform in use. Re-start the server if the
heartbeat function is required.
ANR4668I
Connection successfully re-established

with SNMP subagent.

subagent.
System action: The server was able to successfully
resynchronize with the SNMP subagent.
SNMP subagent did not accept

registration of this server.

attempting to open a session with the SNMP subagent.
The subagent is available but disallowed registration by
this server.
System action: Processing continues. Heartbeat and
message forwarding function will not be available.
User response: It may be necessary to stop the
subagent and re-start it. Then stop the server and
re-start it if heartbeat and message forwarding
functions are required.
ANR4672W
SNMP message forwarding to the

SNMP subagent was not started because
a thread resource was not available.
Explanation: The server could not continue with

SNMP communication to the SNMP subagent for
message forwarding because sufficient memory is not
available for starting additional processes on the server.
System action: The server discontinues SNMP
message processing and server operation continues.
387
ANR4673E ANR4682W
information online or see the appendix Allocating

ANR4679W
ANR4673E
Insufficient memory for subagent

initialization (the portion of initialization
where the allocation of memory failed).
Explanation: The SNMP subagent could not initialize

due to the inability to obtain the required memory.
System action: Initialization of the subagent fails.
User response: Allocate additonal storage to the
subagent.
ANR4674E
Error starting DPI thread - Return code:

Return code received from called routine.
Explanation: The SNMP subagent could not start the

DPI thread.
Messages are no longer being forwarded

to the SNMP subagent.
Explanation: The server has encountered multiple

errors in forwarding messages to the SNMP subagent.
Messages are no longer being forwarded.
System action: The server continues operating, but
messages are no longer being forwarded.
User response: Message forwarding can be
re-initialized by either stopping the server and
re-starting it. Message forwarding will also be
re-started if the heartbeat function is in use and the
server re-synchronizes with the subagent. This
re-synchronization occurs if the subagent, dsmsnmp, is
stopped for longer than a single heartbeat interval (the
heartbeat interval is a server option and appears in the
output of the QUERY OPT command) and then
restarted.

ANR4680I
ANR4675E
Server/subagent protocol violation invalid (where the protocol breakdown

occurred).
Explanation: The SNMP subagent received an

unexpected request from the server.
System action: The subagent will stop processing
requests from the server sending the invalid requests.
DPI subagent (The subagent name.):

Connected or reconnected, ready to
receive requests.
Explanation: The subagent has successfully connected

or reconnected to the SNMP agent.
System action: The subagent is ready to receive
requests from servers.

ANR4681W
ANR4676E
Unable to register another server.
Explanation: The SNMP subagent received a request

to register a new server and was unable to allocate the
memory necessary to register the new server.
System action: The subagent will not register the new
server.
Connect to SNMP agent failed, will

keep trying.
Explanation: The subagent has failed in an attempt to

connect to the SNMP agent.
System action: The subagent keeps retrying the
connection.
User response: Make sure that the SNMP daemon is

up, running and correctly configured.
ANR4677I
ANR4682W
Session established with server name:

The name of the registered server..
Explanation: The SNMP subagent completed the

registration of the identified server.
System action: The subagent will wait for additional
requests from the server.
ANR4678I
Session closed with server name: The

name of the deregistered server..
Explanation: The SNMP subagent completed the

deregistration of the identified server.
388
A SNMP agent connection error

occurred. Attempting to re-establish
connection.
Explanation: An error has occurred in the

communication between the subagent and the SNMP
agent.
System action: The subagent will attempt to
reconnect.
ANR4683E ANR4693I
ANR4683E
Unable to open trace file file name.
Explanation: An error occurred while opening the file

for writing trace data.
System action: The subagent continues operation
without tracing.
User response: Ensure there is adequate space on the
drive from which you are running the subagent and
retry the program.
ANR4684E
Trap request failed - RC: Return code from

the trap request. Server index: Server index
number..

process a trap request from a server. data.
System action: The subagent processing continues.
ANR4688E
Server/subagent protocol violation incorrect request header version.
Explanation: The SNMP subagent received a request

from a server that was not at the same maintenance
level as the subagent.
User response: Ensure the server and subagent are at
the same maintenance level. If they are, contact your
ANR4689E
Invalid request type received (The value

of the request that was received.).
Explanation: The SNMP subagent received an

unexpected request from the server.
ANR4685E
Insufficient memory for subagent

initialization.
ANR4690E
Explanation: The SNMP subagent could not initialize

due to the inability to obtain the required memory.
User response: Allocate additional memory to the
subagent.
ANR4686E
Insufficient memory for subagent trace

initialization.
Explanation: The SNMP subagent trace could not

initialize due to the inability to obtain the required
memory.
User response: Allocate additional memory to the
subagent.
Unexpected request type (The value of the

request that was received.) in trap data
header.
Explanation: The SNMP subagent received an invalid

trap request from a server.
ANR4691I

connected, ready to receive requests.
Explanation: The subagent has successfully connected

to the SNMP agent.
request from servers.
ANR4687E
Server/subagent protocol violation expecting registration request. Received

request: The value of the request that was
received.
Explanation: The SNMP subagent was expecting a

registration request. It actually received something
other than a registration request.
ANR4692I

reconnected, ready to receive requests.
Explanation: The subagent has successfully

reconnected to the SNMP agent.
request from servers.
ANR4693I
Interface Driver information will be

loaded in quiet mode: Only warning
and error messages will be displayed.
Explanation: The server is loading information needed

for the Administrative WEB Interface. To minimize
389
ANR4694E ANR4701I
message traffic, only error and warning messages will
be displayed.
System action: When the command completes, WEB
administrative information will be loaded into the
server.
ANR4694E
SNMP Subagent Port Confirmation Has

Failed.
Explanation: The server was communicating

configuration data to the SNMP subagent. An error
occurred in the exchange. The server could not
communicate interface information to the subagent.
System action: The server continues operation. The
SNMP administrative interface is inoperative.
User response: The most likely cause of this problem
is a temporary network failure. The server should be
re-started to retry the connection to the SNMP
subagent. If this problem occurs repeatedly, please
contact you service representative.
ANR4695E
SNMP: Communications Failure in

Receiving verb type verb.
Explanation: The SNMP client encountered a

communications error in using the verb type verb to
transfer information to or from the server and an
SNMP client.
System action: The SNMP session ends and server
User response: This may not be a problem if the
SNMP subagent was terminated while the session was
in progress. Otherwise, ensure that TCP/IP
communications is running normally.
ANR4698E
SNMP: Communications Failure in

Sending verb type verb (command).
Explanation: The SNMP client encountered a

communications error in using the verb type verb to
issue command command.
System action: The SNMP client session ends and
subagent operation continues.
ANR4699E
SNMP: Receive Buffer overflow.
Explanation: The SNMP client encountered an

overflow error in transferring information to or from
the server.
System action: The SNMP client session ends and
subagent operation continues.
ANR4700I
The server move batch size has been set

to new batch size. Move operations that
start after this point will use the new
value.
Explanation: A SETOPT commmand was used to set

the value for the move batch size value. This setting
determines the maximum number of files that are
moved on the server in one database transaction,
dependent also on the setting for the move size
thrshold. The setting influences file movement for
server migration, reclmation, storage pool backup, and
move data operations.
System action: The server uses this new setting for
move operations that are started after this message is
issued.
ANR4697E
SNMP: Failed to authenticate to server

at address address, port port.
Explanation: The SNMP client was attempting to run

a session with the server at the indicated address and
port number in response to an SNMP Get Request,
which causes a Server Script to be run. The subagent
connected to the indicated server, but failed in
authentication.
System action: The SNMP subagent ends this attempt
to run the script and continues operation.
User response: Ensure that the indicated server has an
an administrative id of SNMPADMIN and that this
adminstrative id has sufficient authority to run the
script and commands it contains.
ANR4701I
The server move size threshold has been

set to new threshold. Move operations
that start after this point will use the
new value.

the value for the move size threshold value. This
setting determines the maximum number of megabytes
that are moved on the server in one database
transaction, dependent also on the setting for the move
batch size. The setting influences file movement for
server migration, reclmation, storage pool backup, and
move data operations.
move operations that are started after this message is
issued.
390
ANR4702I ANR4709W
ANR4702I
The server transaction group maximum

has been set to new value. Client sessions
that are started after this point will use
the new value.

the value for the maxmimum number of files that can
be sent from the client in a single database transaction.
client sessions that are started after this message is
issued.
ANR4703E
Invalid key ring filename Key Ring

Filename
ANR4706W
Explanation: A web browser requested a file and the

server could not find the file on the local file system.
Special note, some files requested from the server are
not vaild and are caused by a browser error. For
example, a request for CommandLineBeanInfo.class is
not a valid file request. However, a request of a GIF
image or HTML page should not produce this error.
User response: Verify that permission for the file are
set correctly and file exists.
ANR4707E
Explanation: The key ring filename specified did not

contain the .kyr extention.
User response: Rename your key ring filename to
contain the .kyr extention. Reexcute the command with
the new filename.
ANR4704I
Key ring filename and password have

been set. Restart the server to use the
new settings
Explanation: The key ring filename have been set to

the new value specified in the DEFINE KEYRING
command.
User response: Restart the server to use the new key
ring information.
ANR4705I
The server IDL definitions have not

been installed. These definitions will
need to be installed for the Web
Administrator interface to work.
Explanation: The server attempted to query the server

IDL interface and found no definitions defined. Because
of this error the HTTP engine returns a 404 not found
message.
User response: If you would like to use the server
web administrator interface you will need to:
1.
Halt the server.
2.
Issue the command DSMSERV RUNFILE

dsmserv.idl. For AS/400 command see next step.
3.
For AS/400, issue the command STRSVRADSM

SVRMODE(*PRPWEB).
4.
Restart the server.
Unable to open file Filename to satisfy

web session Session ID.
Import/Loaddb command operation

terminated - incomplete input volume
list.
Explanation: The list of volumes needed to process

the command was incomplete. At least one volume
needed for the operation is missing from the end of the
list.
System action: The command operation is ended.
sure the necessary volumes are included in the volume
list.
ANR4708I
Native SSL support has been disabled,

please use the web proxy.
Explanation: Starting in this version of this product

native Secure Socket Layer support has been removed.
This feature has been replace with the web proxy.
Support for non-secure http request (COMMMETHOD
HTTP) has not been disabled.
User response:
1. Remove COMMMETHOD HTTPS from your option
file.
2. Install and configure the web proxy. See Quick Start
Appendices for more information on how to install
and configure the web proxy.
ANR4709W
Intervention required to mount volume

Volume Name on Library Manager Server
Server Name.
Explanation: A volume mount is awaiting operator

intervention on the specified library manager server.
System action: The volume mount operation waits for
operator intervention.
User response: Refer to the server consol and/ir
activity log on the named library manaer server to
determine the action that needs to be performed to
complete the mount operation.
391
ANR4710W ANR4718I
ANR4710W
Library manager Server Name could not

be contacted to control library Library
Name.
Explanation: The specified library manager server

could not be contacted for control of the named library.
System action: The server will continue to contact the
named library manager server. Volume mounts in the
library will fail until communication is successful.
User response: Determine why the named server is
not running or why the network prevents
communication with te named server.
ANR4712E
Command: The DEVCLASS parameter is

only valid for volume history types
DBBACKUP or DBSNAPSHOT.

volume history type was specified for the TYPE=
parameter.
User response: Re-issue the command and specify a
valid type value.
ANR4713E
Command: The option string is not valid

for the Hex Filespace Field.
Explanation: The command indicated specifies a value

that is not valid for the Hex Filespace parameter.
command.
entry for the Hex Filespace parameter.
ANR4714I
Command filename for filespace filespace

name of node node name started as
process process ID.
Explanation: A file deletion process has started to

delete one or more files from the given filespace for the
for given node. The process is assigned the ID specified
in the message.
to perform the operation in response to the DELETE
FILE command entered by an administrator.
User response: To obtain status on the file deletion
process, issue the QUERY PROCESS command. The
process may be canceled with the CANCEL PROCESS
command.
ANR4715I
DELETE FILE file name (backup/archive

data) for filespace filespace name of node
node name started.

(on the server) to delete files from the given filespace
for the given node.
backup and archive objects that match the given file
name while server operation continues.
process may be canceled by an authorized
ANR4716I
DELETE FILE file name (backup data) for

filespace filespace name of node node name
started.

for the given node.
backup objects that match the given file name while
ANR4717I
DELETE FILE file name (archive data) for

started.

for the given node.
archive objects that match the given file name while
ANR4718I
DELETE FILE file name canceled for

: number of objects objects deleted.

been deleting files for the given fliespace of the given
node is canceled by the CANCEL PROCESS command.
The number of objects deleted before the cancel ended
the operation are reported in the message.
392
ANR4719I ANR4728E
administrator can issue the DELETE FILE command to
delete the remaining files desired.
ANR4719I
DELETE FILE file name complete for

: number of objects objects deleted.
Explanation: A server process deleting file space data

for the node specified has completed. The total number
of objects deleted is reported in the message.
ANR4726I
Explanation: The module indicated has been

successfully loaded. Operations involving this module
may be performed by the server.
System action: Functions which depend on this
module may now be performed on the server.
ANR4727E

ANR4723E
Session rejected for down level storage

agent storage agent name.
Explanation: A down level storage agent attempted to

connect to this server. The server can not support all
previous versions of the storage agent.
System action: The server will not support
connections by storage agents at a specific lower
versions of the product. Review the README for an
explanation of supported storage agent levels for this
server. The storage agent will not startup and will
report ANR0454W indicating that it is down level.
ANR4724E
During the backup of node node (Node

id) filespace filespace name (filespace id) a
deletion activity occurred.
Explanation: During full or incremental backup

processing, files were deleted from the file space. The
files were not deleted by expiration, but by some other
process. DELETE FILESPACE, DELETE VOLUME,
AUDIT VOLUME, or some other administrator
command can cause files to be deleted. The file space
image on the server will not be consistent with the
client until an incremental backup is completed for the
node.
System action: The server will continue processing.
User response: Perform an incremental backup for the
client node.
ANR4725E
Source file(line number): Server lock

Locktype, mode Lockmode failed.
Explanation: An internal error occurred in an attempt

to obtain a lock during processing.
fails.
User response: Retry the process. If the process fails
The support module has been loaded.
Server Server name is incompatible with

this server. Please update the server to
the same level as this storage agent.
Explanation: The storage agent attempted to connect

to a downlevel server. The server version, release, and
fix level must exactly match, otherwise data corruption
may occur. For example, a version 4.2.0.0 storage agent
cannot connect to a version 4.1.0.0 server.
System action: Upgrade the TSM server to the same
level as the storage agent.
ANR4728E
Server connection to file server File

server name failed. Please check the
attributes of the file server specified
during definition of the datamover.
Explanation: The server attempted to connect to a file

server. The connection failed because of one of the
following possible reasons:
definition was incorrect: TCP/IP address of the file
v File server does not support requested NDMP
version
sessions
v An unsupported model of the filer server was
detected
v If the message specifies address 127.0.0.1 or the
address of the server system, the
NDMPCONTROLPORT and/or NDMPPORTRANGE
options may be set to port numbers or ranges which
are already in use.
System action: TSM server backup/restore of the file
server fails.
User response: Check if file server is accessible
through the network; check each of the attributes
specified during datamover definition; check NDMP
versions supported by the file server; check the number
of open NDMP sessions with the file server, verify that
file server model is supported by TSM server. If the
servers address is in the message ensure that the ports
specified or defaulted for options
NDMPCONTROLPORT and/or NDMPPORTRANGE
393
ANR4729E ANR4734W
are available for use. Depending on the operating
system, the netstat operating system command may be
used to determine in-use port numbers.
ANR4729E
Server connection to file server File

server name failed. The level of the file
server operating system is unsupported
by TSM server. Please upgrade the file
server to the level of the operating
system supported by the server.
ANR4732E
Command: The storage pool storage pool

name is not a pool type storage pool.

STGPOOL command contained a storage pool name
that is not a copy or active-data type storage pool.
Explanation: The TSM server was trying to connect to

a file server with an unsupported level of the operating
system. The server can establish NDMP connection
only to a file server with supported level of the
operating system. Please check the following site for
supported levels of file server operating systems:
http://www.tivoli.com/storage
User response: Verify that the copy or active-data

storage pool name stated in the error message is correct
or remove the storage pool name from the list. If using
the COPYSTGPOOLS parameter, correct the problem by
using a copy storage pool that already exists or define
the copy storage pool. If using the
ACTIVEDATAPOOLS parameter, correct the problem
by using an active-data storage pool that already exists
or define the active-data storage pool. Retry the
command.
System action: The TSM server backup/restore of the

file server fails.
ANR4733E
User response: Upgrade the file server to a supported

level of the operating system.
ANR4730E
Command: The number of pool type

storage pool names specified with the
parameter name parameter exceeds the
maximum number allowed for
simultaneous write.
Explanation: The number of copy storage pools

combined with the number of active-data pools for a
given primary storage pool is limited to three. Earlier
versions allowed up to ten copy storage pools in the
copy storage pool list.
total of three or fewer copy storage pool names and
active-data storage pool names.
ANR4731E
Command: The pool type storage pool

storage pool name is not defined.

STGPOOL command contained a storage pool that is
not defined as either a copy storage pool or an
active-data storage pool.
User response: Verify that the copy or active-data
storage pool name stated in the error message is
correct. If using the COPYSTGPOOLS parameter,
correct the problem by using a copy storage pool that
already exists or define the copy storage pool. If using
the ACTIVEDATAPOOLS parameter, correct the
problem by using an active-data storage pool that
already exists or define the active-data storage pool.
Retry the command.
394
Command: The pool type storage pool

contains a pool type storage pool name
that introduces a cycle into the storage
pool chain.

STGPOOL command contained a copy or active-data
storage pool that eventually points to the storage pool
being processed.
User response: Remove the storage pool name from
the copy or active-data storage pool list and retry the
command.
ANR4734W
The pool type storage pool pool name was

removed from the storage pool list
because of a failure for session Session
Id.
Explanation: The named storage pool was removed

from the storage pool list for the current session
backup/archive/space management operation because
of an error. This removal is only for the session
indicated in the message and does not effect other
session operation.
User response: The error that occured could be one of
many failure. Look for the following items in the active
log or on the server console. 1. Is the named storage
pool currently unavailable? 2. Have any I/O error
occured on the destination devices (disk or tape
drives)? 3. Is the mount limit on the device class
correctly set? 4. Is the nodes MAXNUMMP value
sufficient to satisfy the request?
ANR4735W ANR4741W
ANR4735W
Server-free processing is not available.

Initialization failed.
Explanation: An error occurred while initializing

server-free processing. Server-free data transfer is not
available to backup and restore images.
System action: Client backup and restore image
requests will use lan-based data transfer.
User response: Check for messages during server
initialization and correct the error.
ANR4736E
Set serverfree is not allowed when

server-free is not available.
Explanation: Server-free processing did not initialize.

Changing the status is not allowed.
User response: Server-free status may be changed
when the status is ON or OFF.
ANR4737E

platform) - the copy continue attribute for
storage pool storage pool name prevented
further retries.
Explanation: During a backup session one or more

copy storage pools associated with the indicated
storage pool had a failure. The operation was halted
because the copy continue option for the indicated
storage pool caused the process to stop.
User response: Verify the following: 1. Does the
device class(es) have enough mount points to satisfy
the request? 2. Was the nodes MAXNUMMP value
sufficient to satisfy the request? 3. Were there any
errors reported during the transaction regarding I/O or
related issues?
ANR4738E

is in use as a copy or active-data storage
pool by one or more other storage pools.

a pool that is a copy storage pool and listed as one of
the copy storage pools of other storage pool via the
DEFINE STGPOOL or UPDATE STGPOOLs
COPYSTGPOOL parameter, or, a DELETE STGPOOL
command specifies a pool that is an active-data storage
pool and listed as one of the active-data storage pools
of other storage pools via the DEFINE STGPOOL or
UPDATE STGPOOLs ACTIVEDATAPOOLS parameter.
command.
User response: If necessary, issue the UPDATE
STGPOOL command to update other storage pools so
that they do not reference the pool to be deleted, and

ANR4739E
Either the high-level address (hladdress),

low-level address (lladdress), or both
were entered in error.
Explanation: The high-level or low-level addresses

supplied are incorrect.
command.
User response: Both the high-level address and
low-level address are required for an address to be
valid. For an update, both high-level address and
low-level address are required for the update to
succeed. For a new definition, both high-level address
and low-level address are required when
SESSIONINIT=SERVERONLY. Either the high-level
address or low-level address is missing from this
command. Issue the command again and supply the
missing address represented by a ? in this message.
ANR4740W
Either the high level address, low level

address, or both were never entered for
the specified node( nodename ) and the
session initiation status is being
changed.
Explanation: When the session initiation status of a

node is changed by using the SESSIONINIT parameter
on the UPDATE NODE command, the scheduling table
is updated to reflect the address specified with HLA
and LLA keywords of the UPDATE NODE command.
If one or both of these keywords have never been used
to provide addressing information for the node,
server-initiated scheduling will not be able to contact
this node.
System action: The server does not update the
scheduling table. Subsequent server initiated sessions
with the node are likely to fail, unless an additional
UPDATE NODE command provides both the
HLADDRESS and LLA parameters with correct address
information.
User response: Both the high level address and low
level address are required for an address to be valid.
Issue the UPDATE NODE command for this node with
complete addressing information through the
HLADDRESS parameter for the node address, and the
LLADDRESS parameter for the node listen port
information.
ANR4741W
This command will rename

schedules. Renaming this administrator
will cause these schedules to fail.
Explanation: A RENAME ADMINISTRATOR

command has been entered for an administrator that
395
ANR4742W ANR4747W
owns administrative schedules. If you confirm that you
want to proceed with this command, the schedules
owned by this administrator will fail when executed in
the future.
User response: To process the RENAME
ADMINISTRATOR command, enter 'Y' to continue or
'N' to stop the process. To deal with schedules owned
by the administrator, use the QUERY SCHEDULE
command, or an SQL SELECT statement on the
schedules contolled by an administrator that has
authority to execute them, or use the DELETE
SCHEDULE command to remove the schedules.
ANR4742W
This command has renamed

administrator adminName to
newAdminName. This administrator has
defined or updated schedules. This will
cause these schedules to fail in the
future.
Explanation: A RENAME ADMINISTRATOR

command has been entered and the administrator
renamed owns the administrative schedules. The
schedules will fail when executed in the future because
they do not belong to the administrators new name.
System action: The system renames the administrator.
or an SQL SELECT statement on the
schedules controlled by an administrator that has
authority to execute them, or use the DELETE
SCHEDULE command to remove the schedules.
ANR4743W
An insufficient number of mount points

are available in device class device class
name.
Explanation: During simultaneous write processing,

the server cannot allocate sufficient mount points for
the specified device class. Possible reasons include:
v The mount limit specified for the device class does
not provide a sufficient number of mount points to
support the simultaneous write operation.
v The drives that service the device class are
inaccessible.
User response: Ensure that:
v The mount limit specified for the device class
provides a sufficient number of mount points to
support the simultaneous write operation.
396
v Enough drives are defined and on-line for the library

that services the device class.
ANR4744W
The server cannot acquire a sufficient

number of mount points.
Explanation: During simultaneous write processing,

the server cannot acquire a sufficient number of mount
points to satisfy the request.
User response: Examine error messages that might
have been displayed prior to, and after this message.
Correct any problems, if possible.
ANR4745E
Server server name

(version.release.modification level.fix level) is
not compatible with storage agent
storage agent name
(version.release.modification level.fix level).
Explanation: The server and storage agent are not

compatible. The storage agent must be at the same
version and release as the server. It must also be at the
same modification level, or the same modification level
minus one. For example, a server at version 5.2.1
would allow connections from a storage agent at
version 5.2.1 or version 5.2.0.
System action: If the storage agent and server are not
at the same version and release, update the storage
agent to the same version and release as the server.
Once the storage agent is at the same version and
release as the server, upgrade it to either the same
modification level or the same modification level minus
one.
ANR4746E
Session rejected for up level storage

agent storage agent name.
Explanation: An up level storage agent attempted to

connect to this server. The storage agent can not be at
higher level than the server.
System action: The server will not support
connections by storage agents at a higher version, at
the same version with a higher release, or at the same
version and release with a higher modification level.
The storage agent will not startup and will report
ANR0454W indicating that no resources are available.
ANR4747W
The web administrative interface is no

longer supported. Begin using the
Integrated Solutions Console instead.
Explanation: The web administrative interface is no

longer supported. It has been replaced by an
ANR4748E ANR4756I
administrative interface based on the Integrated
Solutions Console.
ANR4753E
System action: The web administrative interfaces web

page is not displayed.
User response: Install the IBM Tivoli Storage Manager
support for the Integrated Solutions Console and begin
using it to manage your servers.
ANR4748E
A NAS operation requiring NDMP

Version 4 was attempted for file server
File server name , however the current
NDMP session uses NDMP Version 3.
Please verfiy that file server supports
NDMP version 4.
Explanation: A NAS operation which requires NDMP

Version 4 was attempted for a file server that is
currently configured to run NDMP Version 3.
Explanation: The REPAIR STGVOL process has ended.

It processed volumes processed out of total volumes total
volumes to be processed. The repaired volumes indicates
the number of volumes that needed database repairs
and were repaired. The failed volumes are volumes that
either failed during evaluation or during database
repair if it was needed.
User response: If there were failed volumes, review the
activity log for more information about the failure.
ANR4754I
System action: The TSM server backup/restore or

other operation on the file server fails.
User response: Verify that the file server supports
NDMP Version 4. Verify that the file server is
configured to accept connections using NDMP Version
4.
ANR4749I
Key ring filename and password have

been deleted from the server database.
Explanation: The key ring filename and password

have been deleted. Upon restart the server will attempt
to generate a new password and new keyring file if
options SSLTCPPORT or SSLTCPADMINPORT are set
and the key ring files cert.kdb,cert.crl,cert.rdb do not
exist.
User response: Before restarting the server you should
delete the corresponding cert.kdb,cert.crl,cert.rdb and
cert.arm files from the server execution directory if they
exist. Restart the server to generate and use the new
key ring information.
ANR4752I
REPAIR STGVOL process process number

started for number of volumes volumes.
Explanation: The REPAIR STGVOL process has been

started as the reported process number. This will
evaluate and if needed repair the indicated number of
volumes.
User response: This process may be monitored using
the QUERY PROCESS command. If this process needs
to be cancelled, issue the CANCEL PROCESS
command.

ended, processed volumes processed of
total volumes total volumes with repaired
volumes repaired and failed volumes
failures.

volumes repaired.

and were repaired.
ANR4755W

volumes repaired.

and were repaired.
User response: If the volumes processed is less than the
total volumes, this may be because the process was
cancelled before it could process all the needed
volumes. Review the activity log to determine if this is
the case and re-issue the command to complete this
processing. Or if volumes were reclaimed or deleted
while this process was running, there may have been
fewer actual volumes to process than what was
calculated when the process started. If this is the case
no further action is necessary.
ANR4756I
REPAIR STGVOL selected volume

volume name.
Explanation: The REPAIR STGVOL selected volume

name volume to process. This volume will be evaluated
for database reference errors and if any are
397
ANR4757I ANR4781E
encountered, they will be corrected.
ANR4761E

ANR4757I
REPAIR STGVOL finished evaluating

volume volume name, no repair was
needed.
Explanation: The REPAIR STGVOL finished

evaluating volume name volume. No repair actions were
taken for the database because there were no errors
detected.
REPAIR STGVOL reset processing

history failed.
Explanation: The REPAIR STGVOL command was

issued with RESET=YES. This resets the processing
history. However, the reset of the processing history
failed.
User response: The server is likely out of memory or
resources. This command should be re-issued after
either halting and restarting the server or after halting
the server, rebooting the server machine, and than
restarting the server. If the reset still fails after these
steps, contact your IBM service representative.

ANR4762E
ANR4758W
REPAIR STGVOL repaired volume

volume name, database reference errors
were found and corrected.
Explanation: The REPAIR STGVOL evaluated volume

name volume and determined that repair actions were
needed. The necessary repairs were done successfully.
ANR4759E
REPAIR STGVOL failed to process

volume name.
Explanation: The REPAIR STGVOL failed for volume

name volume. This process either failed while
evaluating this volume or it had determined that repair
actions were needed and it failed performing those
actions.
User response: Review the activity log for an
indication of why processing for this volume failed. Try
issuing REPAIR STGVOL VOLNAME=volume name to
process this volume again. If this volume was deleted
from the server, this message can be ignored.
ANR4760I
REPAIR STGVOL reset processing

history.
Explanation: The REPAIR STGVOL command was

issued with RESET=YES. This resets the processing
history. Resetting the processing allows the command
to be rerun and causes previously evaluated volumes to
be re-evaluated.
User response: An administrator may want to
periodically reset the processing history and re-evaluate
all volume in the server as a means of validating the
server database.
398
Command: The SPACEMANAGED or

ARCHIVE type parameters are not valid
for active data storage pool volumes.
Explanation: The QUERY CONTENT server command

has been entered with an invalid type parameter. The
SPACEMANAGED or ARCHIVE parameters are not
valid when the volume specified belongs to an
active-data type storage pool.
User response: Reissue the command with correct
TYPE parameter for active data storage pool.
ANR4780I
Node group node group name defined.
Explanation: A DEFINE NODEGROUP command has

created the node group indicated.
ANR4781E
Command: Invalid node group name node group name.

command fails because the node group name node group
database.
a node group name that conforms to the name
length specifications for valid node group names, refer
ANR4782E ANR4791E
ANR4782E
Command: Description exceeds maximum

length of length limit characters.

command fails because the description specified is
longer than the length limit number of characters
allowed.
database.
a shorter description.
ANR4783E
Command: Node group node group name is

not defined.

name specified does not refer to a defined node group
database.
User response: Issue the command again, specifying a
node group name that is defined in the server database.
For a list of the names of defined node groups in the
server database, issue the QUERY NODEGROUP
command.

database.
node group, issue the DELETE NODEGROUPMEMBER
command. After all nodes are removed, issue the delete
command again.
ANR4787I
Explanation: A DEFINE NODEGROUPMEMBER

command has created the specified number of members
in the indicated node group.
ANR4788I

Node group node group name updated.

NODEGROUP command, the node group node group
name has been updated in the server database.
ANR4785I
Node group node group name deleted.

NODEGROUP command, the node group node group
name has been deleted from the server database.
Command: number of nodes members

deleted from node group node group
name.
Explanation: A DELETE NODEGROUPMEMBER

command has deleted the specified number of
members from the indicated node group.
ANR4789I
ANR4784I

defined in the node group node group
name.
Node node name associated to node

group node group name.

the DEFINE NODEGROUPMEMBER command. Node
node name is associated with the node group name node
group name.
ANR4790I
Node node name disassociated from node

group node group name.

the DELETE NODEGROUPMEMBER command. Node
node name is no longer associated with the node group
name node group name.
ANR4786E
Command: Node group node group name

still contains at least one node.

command command fails because the node group node
group name specified refers to a node group that still
contains at least one node. A node group cannot be
deleted if one or more client nodes are still assigned to
the node group.

ANR4791E
Command: Node group node group name is

already defined.

name specified refers to a node group that is already
399
ANR4792E ANR4798E
database.
node group name that is not defined in the server
database. For a list of the names of defined node
groups in the server database, issue the QUERY
NODEGROUP command.
System action: The TSM server backup operation on

the file server fails.
User response: Verify that the NAS file server is
capable of starting outbound network connections to
the TSM server. Verify that the file server supports
NDMP 3-way operations. Verify that the network
configuration of the system running the TSM server is
reporting a valid TCP/IP host address. .
ANR4795E
ANR4792E
MDMP Tape server unable to initialize

due to error in LISTENing on port Port
Explanation: The server failed in attempting to listen

for session requests on the servers internal tape server.
System action: Server operation continues, but NDMP
operations may fail.
User response: Ensure that the
NDMPCONTROLPORT option defaults to or is set to a
port number which is available in the system. The
QUERY OPTION command can be used to determine
the port number associated with the
NDMPCONTROLPORT option. If this value requires
change, the server will have to be restarted after setting
the option in the server options file.
ANR4793E
MDMP Tape server is terminating due

to an error in accepting a new session
on Port Port
The TSM tape server failed to open an

NDMP data connection to the NAS file
server File server name .
Explanation: During a NAS filer-to-server restore

operation the data connection from the TSM server to
the NAS file server failed. This may occur if the NAS
file server is not properly configured to support NDMP
3-way restore operations.
System action: The TSM server restore operation on
the file server fails.
User response: Verify that the file server supports
NDMP 3-way restore operations. .
ANR4797E
Drive driveName is missing path

information. Please check that all
related paths are defined properly.
Explanation: A drive does not have sufficient path

information for the operation to complete. This is
typically due to a path not being defined.
Explanation: The server failed in attempting to accept

a new session on the servers internal tape server.
System action: The server fails the storage operation.
System action: Server operation continues, but NDMP

operations may fail.
User response: Verify that all applicable paths are

defined for the drive. Also verify that the information
contained in the paths is correct.
User response: Ensure that the

NDMPCONTROLPORT option defaults to or is set to a
port number which is available in the system. The
QUERY OPTION command can be used to determine
the port number associated with the
NDMPCONTROLPORT option. If this value requires
change, the server will have to be restarted after setting
the option in the server options file.
ANR4794E
The NAS file server File server name

failed to open an NDMP data
connection to the TSM tape server.
Please verify that the file server is
capable of outbound data connections.
Explanation: During a NAS filer-to-server backup

operation the data connection from the file server to the
TSM server failed. This may occur because a firewall
exists between the file server and the TSM server and
is preventing outbound network connections on the file
server. This may also occur if the network configuration
of the system running the TSM server is reporting an
invalid TCP/IP host address, for example 127.0.0.1.
400
ANR4798E
Server-free operation type operation had a

target failure. Please refer to
accompanying messages and Message
Reference Manual for further
information.
Explanation: The server-free operation encountered a

target failure. This is typically due to one of three
conditions: 1. A SCSI error was encountered in either
the source, target or datamover. 2. There was a problem
with the HBA issuing the SCSI command 3. An I-O
error caused the operation to time out.
System action: The server does not complete the
server-free operation and attempts to trigger a failover
operation by the client.
User response: If a SCSI error was encountered, please
refer to the sense information and correct for the
indicated problem. If the HBA had an error while
issuing command, please refer to the accompanying
message for appropriate action. If the operation timed
out, please verify the datamover operation and SAN
connections.
ANR4799E ANR4807W
ANR4799E
The server-free operation type from device

source name through data mover data
mover name to device target name failed
after issue.
Explanation: The server-free operation failed after

issuing the SCSI command. This might be because the
value for the HBA (host bus adapter) scatter-gather list
is not large enough.
System action: The server does not perform the
server-free operation. The server will attempt either a
LAN-free or classic LAN operation.
User response: Perform either, or both, of the
following steps to allow server-free operations:
v Change the serverfree batchsize to a lower value.
v Change the MAXIMUMSGLIST value for the HBA
within the Windows registry, or run the DSMMAXSG
utility to change the MaximumSGList value to
0x41(65) for all HBAs.
ANR4800E
The server-free operation from device

mover name to device target name
encountered an I/O error. The following
information was returned from sense
device name: KEY=Key value ASC=Asc
value ASCQ=Ascq value SENSE=Sense info
ANR4802I
Password expiration period for node

node name has been reset.
Explanation: The nodes password expiration period

has been reset to the common password expiration
period.
ANR4803I
Password expiration period for

administrator administrator name has
been reset.
Explanation: The administrators password expiration

period has been reset to the common password
expiration period.
ANR4804I
Node node name already uses the

common password expiration period.
Explanation: The nodes password expiration period is

currently set to the common password expiration
period.
Explanation: The server-free process did not complete

due to an I/O error.
System action: The server will attempt to recover

from the error and if possible retry the server-free data
transfer.
ANR4805I
User response: The device reference manual provided

with the device usually contains tables that explain the
values of the KEY, ASC, and ASCQ fields. If the
problem persists, contact your device service
representative and provide the internal code values and
sense data from this message.

period is currently set to the common password
expiration period.
ANR4801E
ANR4806W
The server-free operation from device

mover name to device target name
encountered an error. This sense
information is typically generated by
configuration issues, please verify the
device definitions.

due to the target being unreachable.
System action: The server will fail the transfer.
User response: For the devices involved in this
operation, please verify that the device and path
defintions are correct. If this message has been issued
after the definitions have been verified, please verify
that the hardware is operating correctly and that the
data mover can see both target devices.

uses the common password expiration
period.

The password expiration period for node
name cannot be reset to the common
Explanation: The nodes password expiration period

could not be reset to the common password expiration
period at this time.
User response: Attempt to reset the nodes password
expiration period at a later time.
ANR4807W
The server is unable to reset

administrator name password expiration
period to the common password
expiration period.

401
ANR4808W ANR4816I
period could not be reset to the common password
expiration period at this time.
ANR4812I

User response: Attempt to reset the nodes password
expiration period at a later time.
ANR4808W
The password expiration period for all

administrators and nodes has been reset
to the common password expiration
period.
Explanation: All administrators not managed by a

profile and nodes on this server have had their
password expiration period reset to the common
ANR4809I
Audit command: Node group node group

name has the same name as a node. The
node group entry must be corrected.
Explanation: During Audit processing, a node group

was found with the same name as an existing node.
Because FIX=NO has been specified for the command,
the node group entry is not corrected.
ANR4810I
Audit command: Nodeid nodeid found for

missing node group node group name.
The node group entry must be corrected.
Explanation: During Audit processing, a node was

found for a node group that does not exist. Because
FIX=NO has been specified for the command, the node
group entry is not corrected.
ANR4811I
Audit command: Nodeid Node Id in node

group node group name does not exist.

found in a node group, but the node does not exist.
the node group entry is not corrected.
Audit command: Nodeid nodeid found in

inconsistent node group node group name.

found in a node group that is inconsistent. Because
FIX=NO has been specified for the command, the node
group entry is not corrected.
ANR4813I
Audit command: Node group node group

name has the same name as a node. The
node group entry will be corrected.
Explanation: During Audit processing, a node group

was found with the same name as an existing node.
the node group entry is deleted.
ANR4814I

missing node group node group name.
The node group entry will be corrected.

found for a node group that does not exist. Because
group entry is deleted.
ANR4815I
Audit command: Nodeid Node Id in node

group node group name does not exist.

found in a node group, but the node does not exist.
the node group entry is deleted.
ANR4816I

inconsistent node group node group name.

found in a node group that is inconsistent. Because
group entry is deleted.
402
ANR4817E ANR4825E
ANR4817E
Command Command: Administrator

admin is not allowed to issue this
command while the system date is
suspect. Correct the system date or use
the ACCEPT DATE command to
establish the current date as valid.
Explanation: The server has noted that the current

system date is suspect. An admin client session may
issue the ACCEPT DATE command to establish the
current date as valid. No other commands are allowed
until the system date is corrected or the current date is
established as valid.

creation date.
ANR4822E
Command: The creation time date is not

valid.

with an invalid creation time.
creation time.

User response: If the current system date is not valid,
reset the date. Otherwise, use the ACCEPT DATE
command to establish the current date as valid on the
server. Reissue the command.
ANR4823E
Accepting an invalid date can cause any of the

following problems:
Explanation: The server ends a table of contents

(TOC) loading or reading for the specified node and
file space because sufficient memory is not available on
the server.
v Premature deletion of data

v Excessive retention of data
v Scheduling problems
v Event record problems
v Password expiration problems
ANR4819E

name is not authorized to a table of
contents session.
System action: The TOC loading or reading is ended

information online or see Appendix. Allocating
ANR4824E
Explanation: A client attempted to work with a table

of contents (TOC) session, but the node lacks proper
authorization. The server will not perform the request.
System action: The server will not perform the
request.
User response: Complete the work using a node with
proper authorization.
ANR4820E
Command The creation date and creation

time are both required to be specified.

due to the target being unreachable.
User response: Reissue the command, specifying both
creation date and creation time, or neither of them.
The loading or reading of a table of

file space name failed because sufficient

file space name failed because of a lock
conflict.

file space because the requested resource is already in
User response: Try the operation again at a later time.
ANR4825E
More than one table of contents is

requested but they are not for the same
node node name and same file space file
space name.
Command: The creation date - date. is not

valid

(TOC) loading for the requested TOCs. The requested
TOCs have to be for the same file space in the same
node name.

with an invalid creation date.


User response: Try the TOC loading specifying the

TOCs in the same node for the same filespace.
ANR4821E
403
ANR4826E ANR4833W
ANR4826E
The object for the table of contents is

not found in the server for node node
name, file space file space name.

(TOC) loading or reading for the object in the specified
node and file space, because the server cannot find the
object for the TOC.
and server operation continues. The TOC object could
be deleted from the server during server expiration or
volume deletion operation.
User response: Make sure a correct TOC object is
specified.
ANR4827E
The loading of a table of contents for

node node name, file space file space name
failed because a thread resource not
available.

(TOC) loading for the specified node and file space
because sufficient memory is not available for starting
additional processes on the server.
System action: The table of contents (TOC) loading or

reading is ended and server operation continues.
ANR4830E

sufficient mount points to read the table of contents
(TOC).
available.
ANR4831E
System action: The TOC loading is ended and server

information online or see Appendix. Allocating
ANR4828E

file space name failed because an internal
server error was detected.

file space because an internal logic error is detected.
representative.
ANR4829E

file space name failed. The transaction is
stopped.

failed transaction.
404

file space name failed. Insufficient mount
points are available to satisfy the
request.
The loading or reading of a Table of

Contents for node node name, file space
file space name failed. The input volume
is already in use.
Explanation: During the TOC loading or reading

operation, the requested input volume is already in use
by another process.
ANR4832E

file space name failed. The required
volume was not mounted.
Explanation: During the table of contents (TOC)

loading or reading operation, a required volume cannot
be mounted. The mount request may have been
canceled.
User response: Try the TOC loading or reading again
and make sure the necessary volumes are accessible.
ANR4833W

file space name failed. The file was
deleted from server storage.
Explanation: During the table of contents (TOC)

loading or reading operation the file has been deleted
from server storage by another process before the
loading or reading is complete.
ANR4834E ANR4841E
processes can delete files in server storage during TOC
loading or reading.
ANR4837I
The loading for the table of contents for

started.
Explanation: The loading for the table of contents

(TOC) in the specified node and file space has been
started.
ANR4834E

file space name failed. The data transfer is
interrupted.

file space because data transfer to or from data storage
was interrupted by an external event.
System action: The TOC reading is ended and server
interrupted. Attempt the operation again if the problem
can be resolved.
ANR4835E
The reading of a table of contents for

failed. A data integrity error was
detected.
Explanation: The server stops reading a table of

contents (TOC) for the specified node and file space
because a data integrity has been encountered on the
server.
this message and contact your service representative.
ANR4836E
The reading of a table of contents for

failed. There was an error in reading
from a device.

(TOC) reading for the specified node and file space
because an I/O error has been encountered by the
server in reading from a device.
this message that specify the device that is failing. The
server may need to be shut down with a HALT
command to correct the hardware problem.

ANR4838I

was successful: total entries loaded
number of entries.

successfully finished.
ANR4839E

failed. See previous messages.

(TOC) in the specified node and file space has failed.
System action: The TOC loading is ended and the
this message to determine the source of the problem.
ANR4840I

was cancelled.

cancelled by the user.
ANR4841E

failed. An invalid object type detected.

(TOC) in the specified node and file space failed
because the object type given is different than the one
User response: Re-try the Table of Contents loading,
specifying a valid object type.
405
ANR4842E ANR4848I
ANR4842E
The loading of a table of contents for

node node name failed. The file space
name was not found.

(TOC) loading for the specified node because the server
could not find the file space name for the TOC object to
be loaded.
System action: The TOC loading is ended and server
User response: The file space could be deleted during
the TOC loading operation. Issue QUERY FILESPACE
command to verify if the file space is deleted. Make
sure the correct file space name is specified. You can
issue a QUERY FILESPACE to ensure that the file space
exists. Re-issue the request with the correct file space
name.
ANR4843I
Command: Displayed number of objects

objects, number of errors errors were
encountered.
Explanation: QUERY TOC has completed. The

number of objects displayed and the error count are
displayed.
System action: The QUERY TOC command ends and
User response: If the error count is not equal to 0,
examine the object name displayed. The error count
represents the number of objects that have their names
displayed as .... This is because the conversion from a
UTF-8 to a local code page for the file name failed. If
this is the case, re-issue the QUERY TOC command
with FORMAT=DETAILED. The object name will be
displayed in a hexadecimal format when the
FORMAT=DETAILED is specified. The file may contain
an invalid character and may need to be renamed. A
new backup copy has to be made for the renamed file
so that the file can be displayed correctly and restored
later.
ANR4844I
Command: The specified table of

file space name contains no entries.
Explanation: The specified table of contents (TOC)

exists, but it is empty. No entries are displayed.
Explanation: During a backup of a NAS filesystem,

the server received a file history record from the NAS
device with a directory path length which exceeded the
maximum length supported by ITSM. The server is
unable to create a TOC for a NAS filesystem which
contains directory that is longer than 1024 bytes. If the
TOC parameter on the BACKUP NODE command is
PREFERRED, the backup continues. If the TOC
parameter was YES, the backup fails.
System action: The TOC creation is ended and server
User response: If TOC=YES was specified on the
BACKUP NODE command, retry the command with
TOC=NO.
ANR4846E
Operation process process ID terminated The server is unable to create a table of

file space.
Explanation: While attempting to create a table of

contents (TOC) for the specified node and file space in
the indicated TOC destination pool, a failure occurred.
System action: The operation fails because TOC
creation is set to YES.
User response: Look for previous messages giving a
specific reason for the failure. Take corrective action as
appropriate.
ANR4847I
Audit command: Invalid nodeid nodeid

found during email address audit. The
email entry must be corrected.
Explanation: During Audit processing, a non-existent

nodeid was found associated with an email address.
the email address entry is not corrected.
ANR4848I
Audit command: An email address

associated with node node name is
invalid. The email entry must be
corrected.
Explanation: During Audit processing, an invalid

email address was found for the specified node.
ANR4845E
406
The writing of the of the table of

file space name failed: a directory path
exceeds max characters bytes in length.
File: lowLevel name, NDMP Node ID:
node id hi .node id lo, NDMP Parent Node
ID:Parent id hi. Parent id lo.
ANR4849I ANR4861W
ANR4849I
Audit command: Invalid nodeid nodeid

email entry will be corrected.

nodeid was found associated with an email address.
the email address entry is deleted.

ANR4854I

associated with administrator
administrator is invalid. The email entry
will be corrected.

email address was found for the specified
administrator. Because FIX=YES has been specified for
the command, the email address entry is deleted.
ANR4850I

associated with node node name is
invalid. The email entry will be
corrected.

ANR4860W

email address was found for the specified node.
ANR4851I
Audit command: Invalid adminid admin id

email entry must be corrected.

adminid was found associated with an email address.
ANR4852I

associated with administrator
administrator is invalid. The email entry
must be corrected.

email address was found for the specified
administrator. Because FIX=NO has been specified for
the command, the email address entry is not corrected.
ANR4853I
Audit command: Invalid adminid adminid

email entry will be corrected.

adminid was found associated with an email address.
The correct value of ARCHRETENTION

for domain domain name will not be sent
to the managed servers. Please upgrade
the managed servers to be at least the
same level as that of the configuration
manager.
Explanation: The configuration manager has an

ARCHRETENTION value that is greater than the
managed server can manage. This is because the
managed server is at a lower level than the
configuration manager. The value of the
ARCHRETENTION for the indicated domain is set to
the maximum value that the managed server can
process.
User response: To correctly send the value of the
ARCHRETENTION to the managed servers, please
upgrade the managed servers to at least the same level
as that of the configuration manager.
ANR4861W
The correct value of RETVER for the

archive copy group domain name policy set
name mgmt class name cg name will not be
sent to the managed servers. Upgrade
the managed servers to at least the same
level as that of the configuration
manager.
Explanation: The configuration manager has a

RETVER value that is greater than what the managed
server can process. This is because the managed server
is at a lower level than the configuration manager. The
value of the RETVER for the indicated copy group is
set to NOLIMIT in the managed server.
User response: To correctly send the value of RETVER
for the copy group to the managed servers, please
upgrade the managed servers to at least the same level
as that of the configuration manager.
407
ANR4870W ANR4877E
ANR4870W

name, specified as a Table of Contents
(TOC) destination for copy group copy
group name in management class
management class name, policy set set
exist.

pool specified for the Table of Contents (TOC)
destination of the specified copy group that is not
defined in the server database. If this copy group is
used in an active policy set, then the NDMP backup
with a TOC creation operation may fail when
attempting to put TOC entries in the destination.
missing storage pool, or the UPDATE COPYGROUP
command to update the copy group to refer to an
existing storage pool.
ANR4871I
Collocation group collocation group name

defined.

database.
a shorter collocation group description.
ANR4874I

updated.

COLLOCGROUP command, the collocation group
collocation group name has been updated in the server
database.
ANR4875I

deleted.

COLLOCGROUP command, the collocation group
collocation group name has been deleted from the server
database.
Explanation: A DEFINE COLLOCGROUP command

has created the collocation group indicated.
ANR4876W

ANR4872E
Command: Invalid collocation group

name - collocation group name.

command fails because the collocation group name
collocation group name specified does not contain valid
characters or contains too many characters.
database.
a collocation group name that conforms to the name
length specifications for valid collocation group names,
refer to the Administrators Reference.
ANR4873E
Command: Collocation group description

exceeds maximum length of length limit
characters.

command fails because the collocation group description
characters allowed.
408

processed because it is not registered.
Explanation: This command cannot be processed for

the indicated node. The node is not registered. The
other nodes can be processed if specified by the
command.
but other nodes can be processed if specified by this
command.
incorrectly, issue the command again with the correct
node name.
ANR4877E
Command: Collocation group collocation

group name is not defined.

collocation group name specified does not refer to a
defined collocation group in the server database.
database.
collocation group name that is defined in the server
database. For a list of the names of defined collocation
COLLOCGROUP command.
ANR4878I ANR4886E
ANR4878I

defined in the collocation group
collocation group name.
Explanation: A DEFINE COLLOCMEMBER command

has created the specified number of members in the
indicated collocation group.
ANR4879I

deleted from collocation group collocation
group name.
still assigned to the collocation group.

database.
collocation group, issue the DELETE
COLLOCMEMBER command. After all nodes are
removed, issue the delete command again.
ANR4883I
Node node name associated to collocation

group collocation group name.
Explanation: A DELETE COLLOCMEMBER command

has deleted the specified number of members from the
indicated collocation group.

the DEFINE COLLOCMEMBER command. Node node
name is associated with the collocation group name
collocation group name.
ANR4880I

collocation group collocation group name.

the DELETE COLLOCMEMBER command. Node node
name is no longer associated with the collocation group
name collocation group name.
ANR4881E

group name is already defined.

collocation group name specified refers to a collocation
group that is already defined in the server database.
database.
collocation group name that is not defined in the server
database. For a list of the names of defined collocation
COLLOCGROUP command.
ANR4882E

group name still contains at least one
node.

command command fails because the collocation group
collocation group name specified refers to a collocation
group that still contains at least one node. A collocation
group cannot be deleted if one or more client nodes are
ANR4884W
Node node name already associated to

collocation group collocation group name.

the DEFINE COLLOCMEMBER command. Node node
name is already associated with the collocation group
name collocation group name. The indicated node is not
processed. The other nodes can be processed if
specified by the command.
incorrectly, issue the command again with the correct
node name.
ANR4885E
Command: Either node name or

collocation group name must be
specified.

neither node name nor collocation group name is
specified or the node name and the collocation group
name both are specified.
System action: The indicated command fails. The
User response: Issue the command again, by
specifying either the node name or the collocation
group name.
ANR4886E

collocation group id has been detected
for node node id.

or incorrect collocation group identifier for the specified
node member.
409
ANR4887E ANR4894I
ANR4887E

collocation group id has been detected
for node node id - it will be corrected.

or incorrect collocation group identifier for the specified
node member. Because FIX=YES has been specified for
the audit command, the error will be corrected.

inventory name object that is incomplete. If FIX=YES
has been specified for the command, the inventory
ANR4892I

ANR4888E
Audit command: Collocation group global

high-water mark does not match the
identifier in use.

attribute used to track collocation group identifiers are
incorrect.
ANR4889E
Audit command: Collocation group global

high-water mark does not match the
identifiers in use; it will be corrected.

inventory name object that has no parent entry. To
ensure that the object is restorable, the entry will be
linked to the root directory for the file space if FIX=YES
was specified for the DSMSERV AUDITDB command.
The user should query the server to determine which
objects have been moved to the root directory. The next
backup operation from the client will create objects
with the correct path name.
ANR4893I

attributes used to track collocation group identifiers are
incorrect. Because FIX=YES has been specified for the
audit command, the attributes will be corrected.
ANR4890I
Audit command: Inventory name object

(name.ID) belonging to node NodeId and
filespace FilespaceId has a missing
database element. It will be corrected if
FIX=YES was specified for the
DSMSERV AUDITDB command.

inventory name object that is incomplete. If FIX=YES
has been specified for the command, the inventory
ANR4891I
410
Audit command: Inventory name reverse

lookup object (name.ID) belonging to
node NodeId and filespace FilespaceId has
a missing database element. It will be
corrected if FIX=YES was specified for
the DSMSERV AUDITDB command.
Audit command: Inventory name object

(name.ID) belonging to node NodeId and
filespace FilespaceId has a missing parent
element. If FIX=YES was specified for
the DSMSERV AUDITDB command,
the name entry will be related to the
root directory for the file space.
Audit command: An inventory backup

object corresponding to name ID nameId
belonging to node NodeId and filespace
FilespaceId has a missing name. If
FIX=YES was specified for the
DSMSERV AUDITDB command, the
name entry will be related to the root
directory as object name for the file
space.

inventory backup object that has no name entry. To
ensure that the object is restorable, the entry will be
linked to the root directory for the file space if FIX=YES
was specified for the DSMSERV AUDITDB command.
The user should query the server to determine which
objects have been moved to the root directory. The next
backup operation from the client will create objects
with the correct path name.
ANR4894I

names.

about client backup object names is currently being
ANR4920E ANR4928E
ANR4920E

command for storage pool pool name.

command for the indicated pool. The indicated pool
could be the storage pool being migrated or being
reclaimed, or the storage pool to which files are
migrated or reclaimed.
command.
ANR4921E
Command: Primary storage pool pool name

does not have a target pool.
Explanation: The specified primary storage pool does

not have a target storage pool for the specified
operation.
command.
User response: Define a target storage pool for the
pool specified on the command and re-issue the
command.
ANR4922E
Command: Migration is currently

running for the storage pool pool name.
Explanation: The migration operation is already

running for the specified storage pool.
ANR4924I
Command: Migration is not needed for

the storage pool pool name.
Explanation: Either the current percentage utilization

of the specified storage pool is less than the low
migration threshold or the number of volumes
containing data has not reached the low migration
threshold.
command.
User response: Re-issue the command when migration
is needed for the pool.
ANR4925W

for storage pool storage pool name duration exceeded.

storage pool, a process performing the migration has
been terminated because the migration duration has
exceeded.
System action: The migration process is terminated.
ANR4926W
Migration terminated for volume volume

name - duration exceeded.

volume, the duration for the migration has been
exceeded.
System action: The volume migration is terminated.
ANR4927W
Reclamation terminated for volume

volume name - duration exceeded.

command.

volume, the duration for the reclamation has been
exceeded.

is not running.
System action: The volume reclamation is terminated.

ANR4923E
Command: Reclamation is currently

running for the storage pool pool name.
Explanation: The reclamation operation is already

running for the specified storage pool.
command.
User response: Re-issue the command when
reclamation is not running.
ANR4928E
Command: Reclamation is not allowed

for the storage pool pool name.
Explanation: The high reclamation threshold

(percentage) is set to 100 to prevent reclamation for the
command.
411
ANR4929E ANR4937E
ANR4929E
Command: The storage pool pool name is

not a sequential-access pool.
Explanation: The specified storage pool is not a

sequential-access storage media for the specified
operation. The specified operation only applies to a
sequential-access storage media.
command.
User response: Re-issue the command for a
sequential-access storage media.
ANR4930I
Reclamation process process ID started

for primary storage pool storage pool
name automatically or manually,
threshold=threshold value,
duration=duration.
Explanation: Because the high reclamation threshold

for the storage pool shown has been exceeded, a
process has been started to reclaim files from the
storage pool. Note: a duration value of None means
that the duration is not specified and hence the
reclamation runs without duration.
to the same pool or to the reclaim storage pool.
ANR4931I
Reclamation process process ID started

for copy storage pool storage pool name
automatically or manually,
threshold=threshold value,
offsiteRclmLimit=limit value,
duration=duration.
Explanation: Because the high reclamation threshold

for the storage pool shown has been exceeded, a
process has been started to reclaim files from the
storage pool. Note: a duration value of None means
that the duration is not specified and hence the
reclamation runs without duration.
to the same pool or to the reclaim storage pool.
ANR4932I
Reclamation process process ID ended for

Explanation: A reclamation process for the named

storage pool ends. This action can occur because the
threshold for the storage pool has been reached or
because the duration has been exceeded.
ANR4933I
Space reclamation ended for offsite

volume volume name.
Explanation: Space reclamation for the named offsite

volume is complete.
ANR4934I
Offsite reclamation ended for storage

pool pool name, Number Processes
number of processes, Number Volumes
Reclaimed number of volume reclaimed,
Elapsed Time seconds seconds.
Explanation: Offsite reclamation ended successfully.

ANR4935I
Migration of primary storage pool

primary pool name has ended. Files
migrated: number of files, Bytes migrated:
number of bytes, Unreadable Files: number
of unreadable files.
Explanation: Migration processing for the specified

determine whether all migration processes ended
successfully.
ANR4936I
Reclamation of storage pool pool name

has ended. Files reclaimed: number of
files, Bytes reclaimed: number of bytes,
Files reconstructed: number of
reconstructed files, Unreadable files:
number of unreadable files.
Explanation: Reclamation processing for the specified

determine whether all reclamation processes ended
successfully.
ANR4937E
Command: Reclamation will not run delete filespace is currently running.
Explanation: A delete filespace operation is running.

To Avoid the resource contention, reclamation will not
run when delete filespace is running.
command.
User response: Re-issue the command when delete
filespace is not running.
412
ANR4938E ANR4943E
ANR4938E

command for target storage pool pool
name.

command for the indicated pool. The indicated pool is
the pool that to which files are migrated or reclaimed.
command.
ANR4939E

valid for a DISK storage pool.

option that is not valid for a DISK storage pool.
command.
Storage Manager is running.

Verify that the reported Unicode name is valid. Note
that the Unicode name is encoded in little-endian
UCS-2 and is reported in hexadecimal notation. If the
Unicode name is not valid, the problem may usually be
corrected by deleting or renaming the corresponding
file or directory on the Network Appliance file server.
The node identifier and parent node identifier are
provided by the Network Appliance NDMP server.
Their values are NDMP-server implementation
dependent but will typically be the inode number of
the file or directory. For more information about the
Unicode name or the node identifiers, including using
them to locate and correct the invalid file or directory,
contact Network Appliance for support.
If possible, configure the Network Appliance file server
to always encode file and directory names as UTF-8.
For additional information about using international
characters with Network Appliance file servers, see the
:cit.ADSM Administrators Guide:ecit. for your
Once the problem has been corrected, try the operation
again.
Command: Volume Volume Name is not
defined. The file name doesnt exist or
has no space.

appropriate for a DISK storage pool.
ANR4942E
ANR4940E
Explanation: A define volume command was issued

for the indicated volume name. The volume name was
specified without the FORMATSIZE parameter, but was
found to either not exist, or to exist but as a file of size
0.
Reclamation is ended for storage pool

storage pool name. There is an insufficient
removable media.

storage pool the server could not allocate sufficient
mount points in the storage pool.
System action: Volume definition fails.

available.
User response: Either use the FORMATSIZE

parameter to have the server pre-allocate space for the
new volume, or use the dsmfmt utility prior to
specifying the DEFINE VOLUME command so that the
volume has space pre-allocated.
ANR4941E
ANR4943E
System action: Reclamation stops.
The server is unable to translate the

Unicode name while building table of
file space name, Unicode name unicode
name node identifier node id, parent node
identifier parent node id. Table of
contents creation fails.
Explanation: While creating a table of contents (TOC)

for a Network Appliance file server, the TSM server
attempted to translate the Unicode name in the file
history message from UCS-2 to UTF-8. The translation
failed.
Command: Volumes cannot be deleted

from
RECLAMATIONTYPE=SNAPLOCK
storage pools.
Explanation: Deleting volumes from

RECLAMATIONTYPE=SNAPLOCK storage pools is
not allowed. Rather, deletion of empty volumes occurs
automatically during reclamation processing.
User response: Allow deletion of empty volumes to
be done automatically during reclamation processing.
System action: The TOC creation fails.

User response: Verify that the required support for
translations between UCS-2 and UTF-8 is properly
installed and configured on the system where the Tivoli
413
ANR4944E ANR4950E
ANR4944E
Command: Volumes cannot be defined in

RECLAMATIONTYPE=SNAPLOCK
storage pools.
Explanation: Defining volumes on

RECLAMATIONTYPE=SNAPLOCK storage pools is
not allowed. Rather, the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands is
used to make storage pool space available for these
storage pools.
User response: Use the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands to
create space in the storage pool.
ANR4945E
Command:The volume named volume

name is larger than is allowed for a
volume on your system.
Explanation: While attempting to define a volume on

volume name the server detected that the volume size
exceeds the maximum allowed.
the server attempted to translate the Unicode path

name in the file history message from UCS-2 to UTF-8.
The translation failed.
User response: Verify that the required support for
translations between UCS-2 and UTF-8 is properly
installed and configured on the system where the Tivoli
Storage Manager is running. Try the operation again.
ANR4948E
Explanation: While reading a list file, the server

detects that the number of entries exceeds the
maximum allowed.
User response: Consider breaking up the operation
into multiple commands, each handling a subset of the
required entries.
ANR4949E

User response: Consider defining 2 smaller volumes.
ANR4946W
The character encoding of NDMP file

history messages for node node name, file
system file system name is unknown. The
Tivoli Storage Manager server will use
the UTF-8 encoding to build a table of
contents.
Explanation: While initializing a backup with a table

of contents (TOC) for the specified node and file
system, the TSM server determines that the character
encoding of file history information from the NAS file
server is unknown. The Tivoli Storage Manager server
will assume file history information is encoded as
UTF-8 in order to build a TOC.
If the character encoding is not UTF-8 and non-English
characters are present, the names will be improperly
displayed and probably unreadable, making recovery
difficult.
User response: Verify that the encoding of file history
information is UTF-8. For Network Appliance NAS file
servers, verify that the volume language for the
specified node and file space is UTF-8, or a subset of
UTF-8 (for example 7-bit ASCII).
ANR4947E
The server is unable to translate the

Unicode path name while building table
of contents for node node name, file
space file space name. Table of contents
creation fails.
Explanation: While creating a table of contents (TOC),
414
The list file named list file name contains

more than max entry count entries.
The server is unable to write to table

table name because there is not enough
temporary space in the database. Table
of contents operation for node node
name, file space file space name fails.
Explanation: While operating on a table of contents

(TOC), the server attempted to insert data into the
specified temporary database table, but there is not
enough temporary space in the servers database.
System action: The TOC operation fails.
User response: Ensure that sufficient temporary space
is available in the servers database. To increase the
amount of database space available to the server, an
authorized administrator can add database volumes by
using the DEFINE DBVOLUME command, and extend
the size of the database by using the EXTEND DB
command.
ANR4950E
The server is unable to retrieve NDMP

file history information while building
table of contents for node node name, file
space file space name. NDMP node ID is
NDMP node ID. Table of contents
creation fails.
Explanation: While creating a table of contents (TOC),

the server attempted to retrieve information contained
in a previous NDMP file history message. The
information was not found. This could be caused by a
problem with the NAS file server that is sending file
history messages. The NDMP node ID reported in the
message is the node ID referenced in the current
NDMP file history message.
User response: Verify that the NDMP server is
ANR4951E ANR4956E
properly sending file history information. Otherwise,
ANR4951E
The writing of a table of contents for

failed. The object is excluded from
storage pool pool name and all successor
pools because of its size.

(TOC) creation for the specified node. The size of the
TOC is larger than that allowed in the storage pool
specified by the TOC destination attribute of the
assigned management class backup copy group. No
successor storage pools to the one specified on the copy
group can accept the large TOC.
User response: Increase the maximum file size for one
or more of the storage pools in the storage hierarchy to
accommodate the TOC. An authorized administrator
can increase the MAXSIZE parameter by issuing the
UPDATE STGPOOL command.
ANR4952E

failed. No space is available in storage
pool pool name and all successor pools.

(TOC) creation for the specified node. The storage pool
specified by the TOC destination attribute of the
backup copy group in the assigned management class
does not contain enough free space to hold the TOC.
No successor storage pools to the one specified on the
copy group contain enough free space.
or more storage pools in the storage hierarchy. This
action may also involve creating storage space by using
an operating system-specific utility.
ANR4953E

failed. The server encountered an error
when writing to the storage device.

(TOC) creation for the specified node because an I/O
error has been encountered by the server in writing to
a device.
the VARY command), or the server may need to be

halted to correct the hardware problem. After the
problem is corrected, try the operation again.
ANR4954E

failed. The data transfer was
interrupted.

(TOC) creation for the specified node because data
external event.
interrupted. Attempt the operation again if the problem
can be resolved.
ANR4955E

failed. The storage media is not
available.

(TOC) creation for the specified node because storage
volumes are not available in the storage pools in which
the TOC is to be stored.
make them available for TOC storage.
ANR4956E

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

(TOC) creation for the specified node because sufficient
volumes are used.

preceding this one that specify the failing device.
415
ANR4957E ANR4963E
ANR4957E

sufficient database space.


representative.
ANR4961E


failed. The server could not commit the
transaction.

for use by the database. Also,an administrator can issue
the EXTEND DB command to extend the size of the
database so that the new volumes are used.

failed transaction.
ANR4958E
System action: The table of contents (TOC) creation is


failed. The server is unable to start a
new thread.


ANR4962E


sufficient mount points available to
satisfy the request.

information online, or see Appendix. Allocating

sufficient mount points to write the table of contents
(TOC).
ANR4959E


sufficient memory.

information online, or see Appendix. Allocating
ANR4960E

failed. The server detected an internal
error.

(TOC) creation for the specified node because an
internal logic error is detected.
416

available.
ANR4963E

failed. See previous messages.

(TOC) creation for the specified node because a
previous error has occurred.
representative.
ANR4964I ANR4970E
ANR4964I
Space reclamation deleted number of

volumes WORM FILE volumes for

storage pool, the server deleted the indicated number
of empty WORM FILE volumes that have exceeded
their retention date.
System action: Reclamation and server operations
continue.
ANR4965E
operation is ended for storage pool storage

pool name. Sufficient database space is
not available.
Explanation: Insufficient server database space has

been encountered during the indicated operation for
the indicated storage pool.
System action: Either the Migration or Reclamation
stops, or the operation specified in the message stops.
ANR4968W
Reclamation failed on WORM FILE

volume volume name.
Explanation: During space reclamation, server failed

to move the files from the indicated WORM FILE
volume. The files on the volume might not be protected
if the reclamation period is exceeded.
System action: Reclamation continues on other
volumes.
User response: Examine the server activity logs to
find out why the reclamation does not move the valid
data to another WORM FILE volume for protection. To
determine when the reclamation period is expired,
issue a QUERY VOLUME command for the indicated
volume.
ANR4969W
Conversion from the server code page to

UTF-8 fails. Verify the installation of the
UTF-8 code page and tools for your
operating system.
operation is ended for storage pool storage

pool name; sufficient recovery log space
is not available.
Explanation: Converting the command results from

the servers code page to UTF-8 fails. Problems with
operating system conversion tool or missing code page
conversion tool might cause this problem. The server
will attempt to recover from the situation. However, the
recovery might result in unreadable characters or no
output to appear on the web interface or interfaces that
use the administrative API. Consult the language
support information of the operating system for
information on how to install UTF-8 code page,
conversion tool support, and ICONV support.
Explanation: Insufficient server recovery log space has

been encountered during the indicated operation for
the indicated storage pool.
System action: The server operation continues without

converting the command output from the servers code
page to UTF-8.
System action: Either the Migration or Reclamation

stops, or the operation specified in the message stops.
User response: Install the UTF-8 code page support on

the operating system. This is normally available by
installing the UTF-8 locale for your language.

DEFINE DBVOLUME command and can extend the
size of the database using the EXTEND DB command.
ANR4966E
User response: To increase the amount of recovery log

administrator can add log volumes using the DEFINE
LOGVOLUME command and can extend the size of the
log volumes using the EXTEND LOG command.
ANR4967W
Expired WORM FILE volume volume

name still contains valid data; data will
not be protected.
Explanation: During space reclamation, the server

detected the retention of the indicated WORM FILE
volume has expired but the volume still contains valid
data. The data on the volume will not be protected.
System action: Reclamation continues.
User response: Examine the server activity logs to
find out why the reclamation does not move the valid
data to another WORM FILE volume for protection.
ANR4970E

reclamation retention date for WORM
FILE volume volume name; run AUDIT
VOLUME FIX=YES for correction.
Explanation: The indicated audit process finds a

WORM FILE storage volume for which the reclamation
retention date is missing or incorrect. To fix the missing
or incorrect date, issue the AUDIT VOLUME with
FIX=YES command for the indicated volume. During
AUDIT VOLUME processing, the server will indeed
have interface to the Network Appliance filer to obtain
the retention date of the SnapLock Log Volume for
correction of the missing or incorrect date.
with FIX=YES, so that the reclamation retention date
can be created or corrected.
417
ANR4971E ANR4982I
ANR4971E

reclamation retention date for WORM
FILE volume volume name. The
reclamation retention date will be
created or corrected.
Explanation: The indicated audit process finds a

WORM FILE storage volume for which the reclamation
retention date is missing or incorrect. Since FIX=YES
has been specified for the audit command, the date will
be created or corrected.
ANR4972I
Command: Migration is not needed for

the storage pool pool name.
Explanation: Migration is not needed for the specified

storage pool because of one of the following reasons:
v The high migration threshold (percentage) is set to
100 to prevent migration.
v If the specified storage pool uses random-access disk
or sequential-access disk, the data capacity utilization
is less than the low migration threshold.
v If the specified storage pool uses tape or optical
media, the ratio of volumes that contain data to the
total number of volumes in the storage pool is less
than the low migration threshold.
command.
ANR4973I
Command: Reclamation is not allowed

for the storage pool pool name.
ANR4975E
No Tcp port available for backup from

NAS node to server.
Explanation: The server was unable to set up a

TCP/IP port for use in backing up or restoring from or
to NAS nodes and the server. The server uses a range
of ports as defined by the NDMPPORTRANGE option.
If none of these ports can be set up for use, backups or
restores from or to NAS nodes and server native
storage pools will fail. If the NDMPPORTRANGE
option is not specified, the server uses ephemeral ports
( ports that the operating system assigns from a
dynamic pool ). If the system runs out of usable ports,
operations to or from NAS nodes and server native
storage pools will fail.
System action: The specific operation is ended and
User response: Operating specific utilities, e.g. netstat,
may be used to examine ports which are in use. It may
be necessary to specify the NDMPPORTRANGE option
( which requires a server restart ), to provide a
sufficient number of ports.
ANR4980I
Auditing Interface Driver definitions.
Explanation: The server is beginning an audit of the

definitions for Web interface.
System action: The server will audit all definitions for
the Web interface and report any problems.
ANR4981E
Interface Driver audit completed Inconsistencies were found.
Explanation: The server found errors during the audit

of the definitions for Web interface.
Explanation: The high reclamation threshold

(percentage) is set to 100 to prevent reclamation for the
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.

command.
User response: Ensure you are using the correct IDL

file for the server level you are running. Examine error
messages that may have been displayed before and/or
after this message and correct any problems, if possible.
If the cause of this can not be determined or resolved,
contact your support representative.

ANR4974W

was cancelled.

(TOC) creation for the specified node because the
process was cancelled.
418
ANR4982I
Interface Driver audit completed definitions are consistent.
Explanation: The server successfully completed the

installation of the definitions for the Web interface.
System action: The Web Interface is now installed.
The server may be run without any problems.
ANR4983I ANR4994E
ANR4983I
Auditing Interface Driver Groups.
Explanation: The server is auditing the driver groups.

System action: The server will audit the driver groups
and proceed to the next step.
ANR4989I
Auditing Interface Driver Operations.
Explanation: The server is auditing the driver

operations.
System action: The server will audit the driver
operations and proceed to the next step.
ANR4984E
Error description
Explanation: The server found errors during the audit

of the definitions for Web interface.
System action: The audit will fail.
User response: Ensure you are using the correct IDL
file for the server level you are running. Examine error
messages that may have been displayed before this
message and correct any problems, if possible. If the
cause of this can not be determined or resolved, contact
your support representative. If you contact your
support representative, the entire text of this message
should be reported.
ANR4985I
Auditing Interface Driver Group

Members.
Explanation: The server is auditing the driver group

members.
System action: The server will audit the driver group
members and proceed to the next step.
ANR4990I
Auditing Interface Driver Operation

Parameters.
Explanation: The server is auditing the driver

operation parameters.
System action: The server will audit the driver
operation parameters and proceed to the next step.
ANR4991I
Auditing Interface Driver Tasks.
Explanation: The server is auditing the driver tasks.

System action: The server will audit the driver tasks
ANR4992I
Auditing Interface Driver Task

Members.
Explanation: The server is auditing the driver task

members.
ANR4986I
System action: The server will audit the driver task

members and proceed to the next step.
Auditing Interface Driver Classes.
Explanation: The server is auditing the driver classes.
System action: The server will audit the driver classes

ANR4993E

ANR4987E
Audit processing failed: sufficient

memory is not available for processing.
Explanation: At RUNFILE time, the server is unable

to process the IDL data due to insufficient memory.
The client platform platform name is

currently not supported by the TSM
Storage Agent.
Explanation: At this point in time the storage agent

does not accept the incomming client platform.
System action: Server runfile stops.

User response: Restart the server runfile process with
more memory available.
ANR4988I
Auditing Interface Driver Complex

Class containers.
ANR4994E
Query whether the volume volume name

is in the library library name failed.
Explanation: An attempt to query if the indicated

volume is in the specified library failed. It could be the
library is offline or the library manager is down in a
library sharing environment.
Explanation: The server is auditing the driver class

containers.
System action: The requested operation failed.
System action: The server will audit the driver class

containers and proceed to the next step.
User response: Re-attempt the request when the

library is brought up or when the library manager is
up and running in a library sharing environment.

419
ANR5000E ANR5032E
ANR5000E
Unable to load tape deletion exit.
Explanation: The tape deletion exit module specified

in the options file cannot be loaded.
reattached to the servers virtual machine.

ANR5026E

User response: Ensure that the tape deletion exit
module is in the system linklist or in the
JOBLIB/STEPLIB for the server.
ANR5021E
Unable to perform I/O to disk vaddr internal error code on IUCV send.
Explanation: The IUCV SEND error code is received

when the server attempts to perform I/O to a disk.
An attempt to open data set data set name

failed, return code return code, reason
code reason code.
Explanation: The data set was not opened. The return

code and reason code can provide clues to the problem.
User response: Verify that data set name is a VSAM
linear data set. If data set name is a valid VSAM linear
data set, and if the return code and reason code do not
provide clues to the solution, contact your service
representative.

User response: For a description of the IUCV SEND
error code, refer to the IUCV documentation in the CP
Programming Services publication for your specific
operating system.
ANR5022E
Unable to perform I/O to disk vaddr permanent error writing to block block.
Explanation: The server encounters a permanent error

while writing to the specified disk and block.
User response: Reformat or replace the disk.
ANR5023E
Unable to perform I/O to disk vaddr permanent error reading from block
block.
Explanation: The server encounters a permanent error

while reading from the specified disk and block.
User response: Reformat or replace the disk.
ANR5024E
Unable to perform I/O to disk vaddr format error detected.
Explanation: The server encounters a format error on

the specified disk.
User response: Reformat the disk by using the
DSMDISK exec.
ANR5028E

failed; the data set contains zero pages.
Explanation: The VSAM linear data set has no space.

This message appears in the following cases:
v You issue def vol|dbvol|logvol for a volume that has
not been formatted using the dsmfmt utility
v You run the dsmfmt utility against a data set that is
too small
v An existing data set has been corrupted
User response: Run the dsmfmt utility, or reallocate the
VSAM linear data set as appropriate.
ANR5030E
Dynamic allocation of data set data set

name failed, return code return code, error
code error code, information code
information code.
Explanation: The dynamic allocation of the data set

failed. The return code return code, error code error code
and information code information code, are displayed in
decimal value and can be found in the Dynamic
Allocation section of MVS/ESA Programming:
Authorized Assembler Services Guide.
User response: Ensure that the data set is available for
allocation by the server.
ANR5032E
Unable to free data set data set name,

return code return code, error code error
code, information code information code.
Explanation: A disk is reset during operation because

a CP RESET or DETACH command has been entered
from the servers console.
Explanation: The dynamic deallocation of the data set

failed. The return code return code, error code error code
and information code info code are displayed in decimal
value and can be found in the Dynamic Allocation
section of MVS/ESA Programming: Authorized Assembler
Services Guide.
System action: The disk is marked off-line.
User response: Ensure that the disk is properly
User response: If the return code and reason code do
ANR5025E
420
Disk vaddr has been reset and is no

longer available.
ANR5033E ANR5049E
not provide clues to the solution, contact your service
representative.
ANR5033E
An attempt to close data set data set name

failed, return code return code, reason
code reason code.
OS/390 R10 or higher. Do not use database backup or

database dump volumes until the system is upgraded
to OS/390 R10 or higher.
ANR5045E
Explanation: The data set was not closed. The return

code and reason code can provide clues to the problem.
User response: Verify that data set name is a VSAM
linear data set. If data set name is a valid VSAM linear
data set, and the return code and reason code do not
provide clues to the solution, contact your service
representative.
ANR5035E
Dynamic allocation of tape unit unit

name failed, return code return code, error
code error code, information code
information code.
Explanation: The dynamic allocation of a tape unit

failed. The return code return code, error code error code,
and information code information code are in decimal
value and can be found in the Dynamic Allocation
section of MVS/ESA Programming: Authorized Assembler
Services Guide.
User response: Examine the MVS messages preceding
this message. They should explain the cause of the
allocation problem; otherwise, contact your service
representative.
Explanation: The server did not open the data set. The
VSAM high-used and high-allocated attributes are
outside of the range expected by the server. The values
may have been corrupted by moving the dataset using
anything other than a logical move.
System action: Volume is marked read-only, or
volume is not brought online. Server operation
continues.
User response: Issue listcat entry(data set name) all to
check the high-used and high-allocated values. If you
moved the dataset, verify that a logical move was
performed.
ANR5046I
An attempt to open tape unit unit name

(data set data set name) failed, return
code return code.
Explanation: The data set was not opened. The return

code and other messages can provide clues to the
problem.
User response: Examine the MVS messages preceding
this message. The ANR1401W message and the volume
name will explain the problem. If necessary, contact
ANR5038E
Volume volume name cannot be processed

at this version of the operating system.
Explanation: The volume was created on a version of

the operating system that had BSAM Large Block
support. The current version of the operating system
cannot process the volume.
User response: Mark storage pool volumes as
unavailable until the operating system is upgraded to
Dynamic allocation of tape unit unit

name was cancelled by the operator.
Explanation: The dynamic allocation of a tape unit

was cancelled by the operator.
System action: Server operation continues, tape mount
fails.
ANR5048E
ANR5036E

failed. Error detected with the VSAM
high-used (VSAM high-used value) or
high-allocated (VSAM high-allocated value)
values.
Tape dataset allocation of block size

changed from server value to current value.
Explanation: The server allocated the block size of its

tape data set as server value, but it has been changed to
current value.
System action: Current tape operation fails.
User response: Check for MVS or system application
messages preceding this message that indicate what
caused the change to the block size. Check for any
system exits that may change the block size (for
example, IEFDB401). Ensure that the server can use its
original value for the block size.
ANR5049E
Tape data set allocation of data set

organization changed from hexadecimal
value server value to hexadecimal value
current value.
Explanation: The server allocated the data set

organization of its tape data set as server value, but it
has been changed to current value in the data control
block (DCB).
421
ANR5050E ANR5224E
caused the change to the data set organization. Check
for any system exits that may change the data set
organization (for example, IEFDB401). Ensure that the
server can use its original value for the data set
organization. See MVS/DFP V3R3 Macro Instructions
for Data Sets for valid values.
ANR5050E
Tape data set allocation of record format

changed from hexadecimal value server
value to hexadecimal value current value.
ANR5209I
Dismounting volume volser (read-only

access).
Explanation: The volume volser is dismounted after

read-only access by the server. Possible reasons for the
dismount include:
v The volume was found idle and the drive was
needed for another volume
v The volume is dismounted as a result of the
DISMOUNT VOLUME command
v The volume is dismounted because of a previously
reported error condition.
Explanation: The server allocated the record format of

its tape data set as server value, but it has been changed
to current value in the data control block (DCB).
ANR5216I

caused the change to the record format. Check for any
system exits that may change the record format (for
example, IEFDB401). Ensure that the server can use its
original value for the record format. See MVS/DFP
V3R3 Macro Instructions for Data Sets for valid values.
ANR5051E
Tape data set allocation of logical record

length changed from server value to
current value.
Explanation: The server allocated the logical record

length of its tape data set as server value, but it has been
changed to current value.
caused the change to the logical record length. Check
for any system exits that may change the logical record
length (for example, IEFDB401). Ensure that the server
can use its original value for the logical record length.
ANR5208I
Dismounting volume volser (updated).
Type volser is expected to be mounted

(mode).
Explanation: The server requires the volume volser be

in read/write or read/only mode as indicated by mode
on a device type indicated by type.
User response: Locate the specified volume and be
prepared to make it available to the server.
ANR5217I
Dismounting volume volser - retention

minute mount retention expired.
Explanation: The volume volser is dismounted because

the MOUNTRETENTION value retention specified for
this device class has elapsed without activity on this
volume.
ANR5220I
Deleting type volser from Storage Pool

pool.
Explanation: The volume volser of device type type has

been removed from storage pool pool.
Explanation: The volume volser is dismounted after

being updated (written to) by the server. Possible
reasons for the dismount include:
v The volume was found idle and the drive was
needed for another volume
v The volume is dismounted as a result of the
DISMOUNT VOLUME command
v The volume is dismounted because of a previously
reported error condition.
Explanation: The deletion of volume volser in storage

pool pool fails.
User response: The server no longer uses the volume

specified. You can return the volume to the scratch
pool.
ANR5224E
Deletion Exit for volser (storage pool

pool) failed - ExitRc=rc,
Rc=abend-indicated.

User response: If the exit return code rc is nonzero,
check the documentation for the tape deletion exit
specified in the server options file. If the tape deletion
422
ANR5226E ANR5270I
exit has abended, the indicator abend-indicated is
nonzero.
ANR5226E

pool) failed - unable to start background
thread.

pool pool has failed due to an internal server error.

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
specified in the message will have to be deleted by
issuing the appropriate RACF commands. For
Information on the return codes and reason code, see
External Security Interface (RACROUTE) Macro Reference
for MVS.

ANR5227E

pool) failed - insufficient memory.

pool pool fails due to lack of available storage.
User response: Increase the region or virtual machine
size for the server or reduce the MAXSESSIONS value
ANR5228I
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.
User response: The server no longer tracks the
volume specified. You can return the volume to the
scratch pool.
ANR5229W
RACROUTE Delete failed for volser,

SAF return code System Authorized
Facility return code, return code RACF
return code, reason code RACF reason code.
Explanation: The deletion of the profile for volume

volser failed. The return codes and reason code are the
result of a RACROUTE call. The codes are in hex. The
SAF return code is designated as x0yy where yy is the
SAF return code and x indicates the call as follows:
x=1 RACROUTE REQUEST=DEFINE, TYPE=DELETE,
CLASS='TAPEVOL', ENTITY=volume
x=2 RACROUTE REQUEST=STAT, CLASS='TAPEVOL'
x=3 RACROUTE REQUEST=DEFINE, TYPE=DELETE,
CLASS='DATASET', VOLSER=volume, ENTITY=tape
dataset name
The failure of the profile deletion is not an error if the
volume did not have a profile. No profile will exist for
a volume if the server was not set up to request a
profile (DEVCLASS parameter PROTECTION=NO)
when the volume was first used, or if the server never
used the volume.
ANR5260E
Command: Volume volume name not

found.
Explanation: A DISMOUNT VOLUME command was

issued, but the volume to be dismounted cannot be
found.
User response: Ensure that you dismount the correct
volume.
ANR5261E
Command: Volume volume is not Idle.
Explanation: A DISMOUNT VOLUME command has

been issued, but the volume is in use and cannot be
dismounted.
User response: If it is necessary to dismount the
volume, cancel the session or process that is using the
ANR5262E
Command: Device address not found.
Explanation: A DISMOUNT DEVICE command has

been issued, but the device to be dismounted cannot be
found.
User response: Ensure that the correct device has been
specified.
ANR5263E
Command: Device address is not Idle.

been issued, but the device is in use and cannot be
dismounted.
device, cancel the session or process that is using the
ANR5270I
SMFWTM macro return code 40 (buffer

shortage).
Explanation: SMFWTM completed with return code

40. This indicates a buffer shortage.
System action: The server continues to operate.
423
ANR5280I ANR5305E
User response: Increase the SMF buffer limit or
disable server accounting.
ANR5294I
ANR5280I
Explanation: Volume volume, which is in device class

class in mode mode, is eligible for dismounting or reuse.
Command accepted.
Explanation: The server accepts a DSMOP REPLY

command.
System action: The server processes the DSMOP
REPLY command.
ANR5289I
Volume volume (class class) mounted

mode on raddr, status: Idle.
Explanation: Volume volume, which is of device class

class and is mounted at address raddr in mode mode, is
eligible for dismounting or reuse.

ANR5295I

mode on raddr, status: In Use.
Explanation: Volume volume, which is of device class

in use by the server.

ANR5296I
ANR5291I

mode on raddr, status: Dismounting.

in the process of dismounting.

mode, status: Dismounting.

class in mode mode, is in the process of dismounting.
ANR5297I


mode, status: In Use.

class in mode mode, is in use by the server.

ANR5290I

mode, status: Idle.

mode, status: In Retry.

class in mode mode, is currently in RETRY. An attempt
is being made to re-establish communications with
another server. If the volume remains in retry status for
the amount of time specified by the device class retry
period, the operation will fail and the volume will be
automatically dismounted.

ANR5305E
ANR5292I
number volume(s) found.
Explanation: A QUERY MOUNT command has been

issued; number volumes are mounted.
ANR5293I
Cancelling mount for volume volume

name.
Explanation: A CANCEL MOUNT command has been

issued for volume volume name. The CANCEL
command is being processed.
User response: Query the activity log to verify that
the mount request has been cancelled.
424
Request number: Device real address is not

a supported device class device.
Explanation: A device is attached to the server to

satisfy a mount request, but it is not a supported
device class. For example, a CARTRIDGE device has
been used when the request is for a REEL device.
System action: The server dismounts the volume,
detaches the device, and requests the original volume
again.
User response: Make sure the device used to satisfy a
mount request is the same type as the device requested.
ANR5307E ANR5326E
ANR5307E
Request number: Volume on real address is

write-protected.
Explanation: The mounted volume is not enabled for

writing.
again.
User response: Enable the volume for writing and
reply to the mount again.
ANR5308E
Request number: Volume on real address is

not write protected.

detaches the device, and reissues the original request.
User response: Mount a volume not already in use by
the server.
ANR5321I
End of volume reached for volume ID on

device real address.
Explanation: During processing of a read/write tape

volume, the end of the tape volume has been reached.
System action: The volume is marked read-only and
kept mounted for later use.
Explanation: The mounted volume is not write

protected.
ANR5323I

again.
Explanation: The server has assigned the mounted

volume to be used as the requested scratch volume.
User response: Disable the volume for writing and

reply to the mount again.
ANR5317I
Make device real address ready.
Assigning volume volume ID to

SCRTCH.
System action: The server dynamically adds the

volume label of the mounted volume to the storage
pool.
Explanation: The device is not ready.

System action: The server sends a message requesting
intervention to the mount operator user IDs listed in
the DSMSERV OPT file.
User response: Make the device ready.
ANR5318I
Intervention cleared on device real

address.
ANR5324I
Assigning volume volume ID to EXPORT.

volume to be used as the requested export volume.
System action: The server uses the volume for the
EXPORT operation.
Explanation: The device that required operator

intervention is now ready.
ANR5325I
System action: The task waiting for the device

continues.

volume to be used as the requested import volume.

IMPORT operation.
ANR5319I
Intervention required on device real

address.

IMPORT.
Explanation: The device requires operator

intervention.
ANR5326E
System action: The task waits until the device is made

ready.
Explanation: During mount processing, the volume ID

the server reads on the mounted volume does not
match the specifically requested, partially full volume.
User response: Make the device ready.

ANR5320I
Volume volume ID already in use.
Explanation: A tape volume has been mounted for use

by the server; after mounting the volume, the server
determined that the volume was already in use by the
server and could not be used to satisfy the current
mount request.
Volume label on real addr (volume ID

found) does not match volume ID expected.

again.
User response: Make sure you are mounting the
correct volume.
425
ANR5329I ANR5336E
ANR5329I

DUMPDB.
Explanation: The server assigns the mounted volume

for use as the requested DUMPDB volume.
DUMPDB operation.
ANR5334W
Volume volume ID reached end of tape.
Explanation: The server has detected end of tape for

the specified volume. The volume reached the end of
tape before the maximum capacity value specified in
the device class was reached.
System action: The server requests another volume if
one is available. The current process stops writing to

for use as the requested LOADDB volume.
User response: Reduce the maximum capacity in the

device class. The QUERY VOLUME command will
indicate the actual capacity of the volume after it is full.
Use the UPDATE DEVCLASS command to change the
maximum capacity for the device class.

LOADDB operation.
ANR5335E
ANR5330I

LOADDB.

ANR5331S
Volume volume ID is damaged. Recovery

is required.
Explanation: The server detects an error on the

specified volume. The volume has been unexpectedly
or incorrectly repositioned during write processing.
Data might have been lost.
System action: The server halts the process that is
using the volume and marks the volume as read-only.
User response: For EXPORT, DBBACKUP, or
DBDUMP tapes, restart the export, backup, or dump
operation. Do not use the tape for an IMPORT,
DSMSERV RESTORE DB, or DSMSERV LOADDB
operation. If the tape is a storage pool volume, you can
attempt to recover the data with the following steps:
1. To identify any missing data, issue the AUDIT
VOLUME command by specifying FIX=NO.
2. If recoverable data exists on the tape, delete
references to the missing data from the database by
issuing the AUDIT VOLUME command and
specifying FIX=YES.
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.
ANR5333I

DBBKUP.
Volume volume ID already used.
Explanation: A tape volume is mounted as scratch for

use by the server. After mounting the volume, the
server determines that the volume has already been
used by the server and cannot be used to satisfy the
current mount request. Mounting the volume as scratch
may have destroyed some of the data previously
written on that volume.
detaches the device, and reissues the original request.
User response: Mount a volume not already in use by
the server. The damaged volume must be replaced,
restored, or deleted from the volume history file.
v If the volume is an Export, Database Dump or
Database Backup volume that contains data that is
no longer needed, use the DELETE VOLHISTORY
command to make the volume available to the server
for reuse.
v If the volume mounted is an Export or Database
Dump, the tapes are no longer good and another
export or dump must be taken. If the tape is a
current Database Backup volume, a full backup must
be done to insure a complete backup exists.
v If the volume is a storage pool volume, audit the
volume. If it is a primary volume and a copypool
exists, restore the volume. If it is a copypool volume,
backup the storage pool again to insure a backup
copy exists for all files.
It is strongly recommended that you use the
DEVCLASS EXPIRATION or RETENTION parameter
to protect your tapes and prevent damage to tapes you
create in the future.
Volume volume ID must be read-only on
3590 device.

for use as the requested DBBKUP volume.
ANR5336E

DBBKUP operation.
Explanation: The server requests a volume in a mode

other than read-only. The 3590 device that is used to
satisfy the mount cannot be used to write to the
volume.
426
ANR5337I ANR5373I
System action: The server cancels the current
operation.
User response: Update the volume access to
READONLY or mount the volume with the appropriate
device.
ANR5337I
Assigning volume volume ID to backup

set.

volume to be used as the requested backup set volume.
backup set operation.
ANR5338E
DEVCLASS device class mounted device

real address, cannot write to volume.
ANR5354E
Block block number sequence error on

device real address.
Explanation: During a read operation, the block ID of

the block being read does not match the block ID
stored in the data block header.
System action: The server places the volume in an
I/O error state.
User response: The integrity of the volume may have
been compromised. Reset the error condition with the
UPDATE VOLUME command and attempt the
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
option.
ANR5370E
Invalid block header on device real

address.
Explanation: The server requested a volume with a

specific format. The device cannot write to the volume
using the requested format.
Explanation: During a read operation, the block

header of the block read does not contain data
recognized by the server.

again.
System action: The server may place the volume in an

I/O error state.
User response: Check the UNIT parameter of the

DEVCLASS option, and ensure that the device can
write with the format type defined.
ANR5351E
Error reading BlockID on device real

address.
Explanation: A Read Block ID CCW failed.

System action: The server marks the volume in an
I/O error condition and requests another volume be
mounted.
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
DELETE VOLUME command with the DISCARD=NO
option to remove the volume from the storage pool.
ANR5352E
Synchronize failed on device real address.
Explanation: A Synchronize CCW failed.

System action: The server marks the volume in an
I/O error condition, and requests another volume be
mounted.
User response: Reply to the new mount request. Reset
the error condition with the UPDATE VOLUME
command. The original volume can be corrupted. To
delete the volume, issue the DELETE VOLUME
command with the DISCARD=NO option.
User response: The volume can be corrupted. Reset

the error condition with the UPDATE VOLUME
command and attempt the operation on a different tape
drive. If the problem persists, try to audit the volume
by using the AUDIT VOLUME command to see if any
files on the volume can be recovered. If not, you can
delete the volume with the DELETE VOLUME
command, by using the DISCARD=NO option.
If a LOADDB operation was being performed, specify
the command syntax by either using a ddname or by
specifying a device class name. You must use the same
method that was used when the data base was
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
specified the correct volume name. The integrity of the
volume may have been compromised. In this case, the
volume cannot be used by the LOADDB operation.
ANR5373I
Cannot allocate tape drive of unit type

unit type for tape volume ID. Reply C
(cancel), R (retry), or W (wait).
Explanation: The server attempts to allocate a tape

drive. The allocation attempt fails because no
acceptable tape drive is available. An acceptable tape
drive has the unit type indicated in the message.
Before more attempts are made to allocate the tape
drive, the operator is prompted to indicate whether or
not the tape drive allocation request can be satisfied.
The unit type and the VOLSER of the tape volume
volser to be used for the pending request are provided
in the message text.
427
ANR5404I ANR5414E
System action: If the operator replies R (meaning
retry), the server will retry the tape drive allocation. If
no acceptable drive is available after retrying the
allocation, the server will reissue this message.
If the operator replies W (meaning wait), the server
will retry the tape drive allocation. If the allocation
request cannot be satisfied immediately, the server will
wait while MVS Allocation Recovery issues message
IEF238D. After IEF238D is issued, none of the following
can occur in the server until the allocation completes or
is canceled:
v dynamic allocations or deallocations
ANR5411I
Explanation: The server has detected an

end-of-volume condition for the given volume.
System action: The volume is marked full. If more
data must be stored, the server accesses another
volume.
ANR5412I
v file opens or closes

v tape volume changes between read mode and write
mode
If the operator replies C (meaning cancel), the server
will fail the tape drive allocation and its associated
server request.
Any other reply will cause the server to reissue this
message. Determine if there are any tape drives which
can be used to satisfy this request (either online or
offline) prior to responding to this message.
ANR5404I
System action: Read or write operations, or both, will

commence for the volume.
ANR5405I
End-of-volume reached for SERVER

volume volume name.

data must be stored, the server accesses another
volume.
FILE volume volume name

MAXCAPACITY larger than allowed
maximum. Overriding maximum
capacity to FILE maximum capacityMB.
Explanation: The maximum capacity specified for the

listed volume is larger than the maximum allowed for
the FILE device class.
System action: The volume capacity is set to the
maximum allowed for the FILE device class.
User response: Update the device class of the volume
MAXCAPACITY value to less than or equal the
maximum allowed for the FILE device class.
ANR5413E
SERVER volume volume name mounted.
Explanation: The server has mounted the given

volume.
End-of-volume reached for FILE volume

volume name.
Dynamic allocation of FILE volume

volume on unit=unit volser=volser
returned rc=rc, info code=info code, error
code=error code.
Explanation: The dynamic allocation of FILE volume

volume on unit unit and volume serial volser fails. The
server uses the unit and volser device class parameters
when allocating new FILE volumes, and always
catalogs the actual MVS data sets. If these parameters
are not defined, Dynamic Allocation uses system
defaults to select a device on which to create the MVS
sequential data set.
For previously allocated FILE volumes, the server
allows Dynamic Allocation to locate the actual MVS
data set using catalog services.
The return code rc, information code info code and error
code error code are in decimal and can be found in the
Dynamic Allocation section of MVS/ESA Programming:
Authorized Assembler Services Guide.
ANR5410I
FILE volume volume name mounted.
Explanation: The server has opened the given file to

simulate a tape volume.
User response: For new FILE volumes, verify that all

device class parameters are defined correctly and are
compatible, and that space is available on the target
DASD.
ANR5414E
Error error code returned while opening

FILE volume volume
Explanation: The BSAM OPEN fails. Error code error

code is returned. Check for accompanying MVS error
messages.
428
ANR5415E ANR5419E
Error codes greater than eight are MVS ABEND codes,
documented in MVS/ESA System Codes, GC28-1486.
User response: For previously allocated FILE volumes,
verify that the MVS data set used for the FILE volume
exists on the physical device designated by the catalog.
Check the accompanying MVS system messages.
ANR5415E
System return code return code received

opening volume server volume name with
file name file name
Explanation: The server or storage agent attempted to

access the file name indicated but failed to open the
volume. The indicated system return code was
received. The actual volume name corresponds to the
file name that the server uses. The server volume name
and the file name may be the same when the server
experiences a failure in opening the file.
System action: The volume is not opened.
User response: The server or storage agent can
recover from some failures by requesting access to
different volumes. If there is a directory definition
problem, this message may be displayed multiple times
during retries with different volumes. The directory
names associated with the device class definition in the
server should be checked for correctness in the number
and names of directory entries. PATH definitions for
each of the FILE drives should be checked that the
number of directories in the PATH definition match the
number in the servers device class definition and that
directories exist and are accessible to servers and
storage agents accessing server directories via their
own path names. For example, if the server has the
following definition:
DEFINE DEVCLASS FILE DEVTYPE=FILE
DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a
storage agent has the following PATH definition:
DEFINE PATH STA FILE1 SRCTYPE=SERVER
DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE
DIR=X:\DIR1,X:\DIR2 then system STA must have
drive X set to access directory L:\FILECLASS on the
server so that directories DIR1 and DIR2 correspond to
the correct destinations on the storage agent and that
the number of directories match between the PATH and
the DEVCLASS definitions.
ANR5416I
Device type volume volume name

mounted.
Explanation: The server has mounted the volume.

ANR5417I
I/O is being bypassed for volume volume

name.
Explanation: The indicated volume is mounted but

the server is bypassing actual I/O operations for the
volume. The pool associated with the volume matches
the NULLPOOLNAME option in the options file or
NULLFILEDEVCLASS YES has been specified in the
options file.
ANR5418I
End-of-volume reached for device type

volume volume name.

data must be stored, the server will access another
volume for it.
ANR5419E
A failure occurred in writing to volume

server volume name.
Explanation: The server or storage agent was writing

to the indicated volume name when a failure occurred.
System action: The server or storage agent stops
writing to the specified volume.
and names of directory entries.
The permissions associated with newly created files
should be checked to ensure the server and storage
agent can write to newly created files. Depending on
the system, a mask value may need to be adjusted. The
system error or event log should be checked for
indications of hardware or software errors from file
systems.
For a remotely mounted file system, as when SANergy
is used, ensure that the remote file system is mounted
and useable to the storage agent. The file system
should be checked to ensure that sufficient space is
available. While the server checks space, multiple
device classes or servers using the same file system can
cause the servers space checking to underestimate
available space.
For storage agents, PATH definitions for each of the
FILEHFS drives should be checked to ensure that the
number of directories in the PATH definition matches
the number in the servers device class definition and
429
ANR5420W ANR5423W
that directories exist and are accessible to servers and
own path names.
For example, assume the server has the following
definition:
DEFINE DEVCLASS FILE DEVTYPE=FILEHFS
DIR=X:\DIR1,X:\DIR2
With this assumption, system STA must have drive X
set to access directory L:\FILECLASS on the server so
that directories DIR1 and DIR2 correspond to the
correct destinations on the storage agent. In addition,
the PATH and the DEVCLASS definitions must have
the same number of directories.
ANR5420W
FILE FILE name not deleted from system,

return code return code.
Explanation: A volume associated with a device class

defined with DEVTYPE=FILE was deleted from the
server, but the associated CMS file or MVS data set
FILE name could not be deleted.
System action: Server operation continues. No other
attempts will be made to delete the volume from the
system.
User response: If the volume was created and never
used, a CMS file or an MVS dataset may not have been
created and no action is required. If the CMS file or the
MVS dataset FILE name exists it will have to be deleted
manually.
ANR5421E
Out-of-space in file system for device

type volume volume name.
Explanation: The server detected an out-of-space

condition for the file system in which the volume
resides.
User response: The file system must be expanded to
accommodate volume growth.
ANR5422E
A failure occurred when flushing data

to volume server volume name.

The failure occurred during a flush operation when the
server was attempting to synchronize its progress of
data written with that of the file system. If the file
system becomes full, it is possible to receive no error
indications until the flush operation is attempted.
430
writing to the specified volume. The transaction in

progress is rolled back.
systems.
available space.
FILEHFS drives should be checked to ensure that the
own path names.
For example, assume the server has the following
definition:
DEFINE DEVCLASS FILE DEVTYPE=FILEHFS
DIR=X:\DIR1,X:\DIR2
Then system STA must have drive X set to access
directory L:\FILECLASS on the server so that
directories DIR1 and DIR2 correspond to the correct
destinations on the storage agent. In addition, the
PATH and the DEVCLASS definitions must have the
same number of directories.
ANR5423W
Insufficient space for new volume in

directory directory for device class device
class name.
Explanation: The server found that the indicated

directory had insufficient space to create a new volume.
System action: Other directories available to the
device class are used. If no directories with space are
available, the operation fails. This message is issued
ANR5424E ANR5502E
periodically as requests are made for space in this
directory.
contain any valuable data, delete it and retry the

backup operation.

ANR5456E
ANR5424E
Unable to validate directory name

directory name for parameter command
Explanation: The specified directory name was being

used in the indicated command. The server attempted
to validate that the directory was accessible so that it
could be used in the command definition. The server
was unable to validate that the directory was
accessible.
System action: The command fails. The server
continues.
User response: Make sure that the directory exists and
can be accessed by the server.
ANR5453E
Device type volume volume name cannot

be overwritten by EXPORT operation.
Explanation: The specified volume already exists or

contains data. The server does not allow new export
data to be written to the volume.
System action: The server detects that the given
volume already contains some data that would be
overwritten by the requested export operation.
User response: If the specified volume does not
contain any valuable data, delete it and retry the export
operation.
ANR5454E

be overwritten by DUMPDB operation.

contains data. The server does not allow new dump
overwritten by the requested dump operation.
contain any valuable data, delete it and retry the dump
operation.
ANR5455E

be overwritten by BACKUP DB
operation.

contains data. The server does not allow new backup

be overwritten by backup set operation.

contains data. The server does not allow new backup
set data to be written to the volume.
overwritten by the requested backup set operation.
ANR5500E
Command: Device type not specified.
Explanation: The command command has been issued,

but without the DEVTYPE keyword.
User response: Reissue the command, and specify the
DEVTYPE keyword and any additional parameters that
are required for the command. The HELP DEFINE or
HELP UPDATE commands may be used to obtain
syntax assistance.
ANR5501E
Command: attribute is invalid for device

type.
Explanation: The command command has been issued

with an incompatible combination of device type and
attribute.
User response: Reissue the command, and specify a
compatible set of attributes. The HELP DEFINE or
syntax assistance.
ANR5502E
Command: LENGTH is invalid with

3480 and 3480XF formats.

with an incompatible combination of device type,
FORMAT, and LENGTH. A length specification is
invalid with 3480 and 3480XF formats.
compatible set of attributes. For 3480 and 3480XF
formats, reenter the command without a LENGTH
keyword. The HELP DEFINE or HELP UPDATE
commands may be used to obtain syntax assistance.

overwritten by the requested backup operation.
431
ANR5503E ANR5511E
ANR5503E
Command: Invalid parameter for update parameter.
ANR5507E
Command: Device type devtype not

supported on this platform.
Explanation: The command command has been issued.

However, the parameter is not an attribute that must be
updated.
Explanation: An unsupported device type has been

specified for command. In MVS, for example, the REEL
device type is not supported.

compatible set of attributes. The HELP UPDATE
command may be used to obtain syntax assistance.
User response: Specify a valid device type for the

platform. The HELP DEFINE command may be used to
obtain syntax assistance.
ANR5504E
Command: new attribute conflicts with

existing old attribute.
ANR5508E
Device class device class not defined in

device configuration file.
Explanation: The command command has been issued.

However, new attribute conflicts with old attribute in
updating the device class.
Explanation: The issued command requires that the

specified device class be defined in the device
configuration file. The definition was not found.

compatible set of attributes. You may have to specify
additional keywords to update the device class in a
compatible manner. The HELP UPDATE command may
be used to obtain syntax assistance.

valid device class. You may also want to refresh your
device configuration file by issuing the BACKUP
DEVCONFIG command.
ANR5509E
ANR5505E
Command: MOUNTLIMIT is less than

current number of mounted volumes.

that specifies a MOUNTLIMIT smaller than the existing
number of volumes that are already allocated.
User response: You may wait until volumes are no
longer in use to reissue the command. Alternatively,
you may cancel sessions or processes that are using
volumes; then issue DISMOUNT commands to free
allocated volumes before reissuing the command. The
QUERY MOUNT command can be issued to determine
which volumes are mounted for use by the server.
ANR5506E
Command: Conflicting parameters

parm1 and parm2.

that specifies conflicting parameters parm1 and parm2.
Conflicting parameters include specifying FORMAT
and LENGTH with DENSITY, and RETENTION with
EXPIRATION.
compatible set of parameters. The HELP DEFINE or
syntax assistance.
432
Command: Parameter Parameter is larger

than the allowed maximum of Maximum
valueM.
Explanation: The specified parameter is larger than

the allowed maximum for this device class.
parameter less than or equal to the allowed maximum.
ANR5510E
Data set namedata set name is not valid, a

server tape operation failed.
Explanation: Data set name data set name is not valid.

System action: Server operation continues. Current
operation can fail.
User response: Check for other messages. Ensure that
the DEVCLASS PREFIX setting is valid.
ANR5511E
Unit nameunit name is not valid, a server

tape operation failed.
Explanation: Unit unit is not valid.

operation can fail.
the DEVCLASS UNIT setting is valid.
ANR5512E ANR5954W
ANR5512E
Volume serial volume serial is not valid, a

server tape operation failed.
Explanation: Volume serial volser is not valid.

operation can fail.
User response: Check for other messages. If you
defined a volume manually, or entered a command
with a volume name, ensure the name is valid.
ANR5513E
Expiration date date is not valid, a server

tape operation failed.
Explanation: Expiration date date is not valid.

operation can fail.
the DEVCLASS EXPIRATION setting is valid.
ANR5514E
Retention period retention period is not

valid, a server tape operation failed.
Explanation: Retention period retention period is not

valid.
operation can fail.
the DEVCLASS RETENTION setting is valid.
library, reissue the command with a different library

name.
ANR5518E
Command: Incorrect value for parameter

parameter.
Explanation: An incorrect value has been provided for

the specified parameter.
valid parameter value.
ANR5519I
Library library name updated.
Explanation: The designated library has been

successfully updated.
System action: The library is updated and recorded in
the database.
User response: If you want to update an additional
name.
ANR5520I
Library library name deleted.

System action: The library is deleted and removed
from the database.
ANR5515I
Library library name defined.

successfully defined.
System action: The library is defined and recorded in
the database.
ANR5516E
Command: Incorrect library name library

name.
Explanation: The designated library name is incorrect;

either it contains too many characters, or some of the
characters are incorrect.
User response: Reissue the command using a valid
library name.
ANR5517E
Command: Library library name is already

defined.
Explanation: The designated library cannot be defined

because it already exists.
User response: If you want to define an additional
ANR5953W
Unable to generate accounting record ACCT option not specified in CP

directory.
Explanation: The SET ACNT ON command has been

entered, but the server is unable to generate an
accounting record because the ACCT option has not
been specified in the servers CP directory entry.
accounting record is generated.
User response: Add the ACCT option to the servers
CP directory entry. To suppress these messages until
the CP directory can be updated, enter the SET ACNT
OFF command.
ANR5954W
Unable to generate accounting record insufficient memory.
Explanation: The SET ACNT ON command has been

entered, but the server is unable to generate an
accounting record due to a lack of memory (virtual
storage). In some cases a 4096-byte buffer is required
for accounting operations, and it is this buffer that
cannot be allocated.
accounting record is generated.
433
ANR5959E ANR6203I
server virtual machine. There are three ways to do this:
User response: Delete all paths to this library, and

1. Increase the size of the servers virtual machine.

This requires that the default storage size be
updated in the servers CP directory entry.
ANR5985E
2. Reduce the maximum number of client sessions

permitted. To do this, edit the DSMSERV OPT file
and reduce the value specified for the
MAXSESSIONS statement. Note that each client
session causes an additional 64KB of memory to be
allocated.
3. Decrease the amount of space allocated to the
servers database buffer pool. To do this, edit the
DSMSERV OPT file and reduce the value specified
for the BUFPOOLSIZE statement. Note that each
buffer pool page causes an additional 4 KB of
memory to be allocated.
Note that the server must be shut down (with the
HALT command) before changes can be made to the
DSMSERV OPT file.
ANR5959E
The server is not running with APF

authorization. The server and all
JOBLIB/STEPLIB libraries (C library
and other libraries) must be authorized.
Explanation: The server is not running with MVS

authorization.
Command: Library library name is not

defined.
Explanation: The designated library has not been

defined.
User response: Reissue the command using a different
library name, or define the library before retrying the
command.
ANR6200I
Command name: Level compression audit

level compression audit started as
process process ID.
Explanation: A compression audit at the specified

level has been started as a background server process
with the process identifier reported.
background audit attempts to identify client files that
may be affected by the client compression problem.
ANR6201I
System action: Server operation ends.
Command name: Level compression audit

level compression audit starting as
background process process ID.
User response: Ensure that all library data sets

required by the server are authorized.
Explanation: A compression audit at the specified

level was started as a background server process
having the process identifier reported.
ANR5960E

background audit attempts to identify client files that
may be affected by the client compression problem.
The server is unable to register with

PRS. Return code rc from PRS
Explanation: The server is not registered with PRS.
System action: Server operation continues without

PRS support.
ANR6202I

ANR5967W
Accounting record not produced, return

code rc.
Explanation: There was a problem generating the

accounting record.
ANR5984E
Command: One or more paths are still

defined to library library name.
Explanation: The designated library cannot be deleted

because there are still paths defined to it.
434
Command name: Verifying candidates

from last audit.
Explanation: A compression audit has started to verify

the client file candidates that were identified in a
previous compression audit execution. The verification
process eliminates compression candidates that are now
found to be expired by policy on the server.
System action: The audit operation continues.
ANR6203I
Command name: Starting level audit level

compression audit from qualifying
entries in the candidates list.
Explanation: A compression audit is starting to check

qualifying candidates from the candidates list for the
audit level specified. Client files that were identified as
compression candidates at a lower level will be tested,
ANR6204I ANR6210I
subject to the qualifications that were specified for the
command.
ANR6207I

User response: The compression candidate list can be
displayed with the QUERY COMPRESSION command.
The QUERY PROCESS command can be used to
monitor the progress of the audit operation.
ANR6204I
Command name: Process process ID, level

audit level audit, ended successfully compression suspects = total number of
compression suspects.
Explanation: A compression audit ended and is

reporting the total number of suspect client files that
have been found.
System action: The audit operation completes.
ANR6205I
Command name: Process process ID,

continuing Level 1 compression audit
with object object ID high order
number.object ID low order number.
Explanation: A level 1 compression audit is starting to

evaluate client files for signs that they may be affected
by the client compression problem. Since a previous
level 1 audit has been executed, this audit will continue
where the last audit stopped starting with the object
whose identifier is specified.
ANR6206I

starting base level 1 compression audit.
Explanation: A level 1 compression audit is starting to

evaluate client files for signs that they may be affected
by the client compression problem. The audit starts
with the first client file found on the server, even if
previous level 1 audits have been executed.
System action: The audit operation continues

audit level analysis detected candidate
file high-level object name low-level object
name in file space client filespace name for
node client node name.
Explanation: A compression audit has found a

candidate file at the audit level specified. The name of
the client node, file space, and file are displayed. This
message is issued whenever a candidate file is detected
during a compression audit that was started with the
VERBOSE=YES parameter specified.
ANR6208I
Command name: Process process ID, was

cancelled - number of candidate files
candidate files were found in number of
files examined files examined prior to
cancellation.
Explanation: A compression audit operation was

canceled with the CANCEL PROCESS command before
completion. The number of candidate files that were
found prior to the cancellation are displayed.
System action: The audit operation ends.
User response: The compression audit may be
restarted with the AUDIT COMPRESSION command.
The compression candidate list can be displayed with
the QUERY COMPRESSION command.
ANR6209I

audit level audit completed successfully number of candidate files candidate files
were found in number of files examined
files examined.
Explanation: A compression audit operation

completed successfully. The number of candidate files
that were found are displayed.
ANR6210I

audit level audit completed successfully number of candidate files candidate files
were found.

that have been found are displayed.
435
ANR6211I ANR6221I
ANR6211I

audit level analysis detected candidate
file object name in file space client filespace
name for node client node name.
Explanation: A compression audit has found a

candidate file at the audit level specified. The name of
the client node, file space, and file are displayed. This
message is issued whenever a candidate file is detected
during a compression audit that was started with the
ANR6212I

audit level analysis eliminated level
candidate level candidate file object name
in filespace client filespace name for node
client node name from candidate status.
Explanation: A compression audit at the level

specified has eliminated a candidate file through
further analysis. The name of the client node, file space,
and file are displayed. This message is issued whenever
a candidate file is eliminated from consideration during
a compression audit that was started with the
ANR6213I
Command name: Process process ID, was

cancelled - number of files promoted
candidate files were promoted as
candidates at level audit level, number of
files eliminated files were eliminated as
candidates, and number of files expired
candidates were eliminated because they
were found to be expired on the server.
Explanation: A compression audit operation was

cancelled with the CANCEL PROCESS command
before completion. The number of candidate files that
were promoted as candidates at this level of audit,
eliminated as candidates at this level of audit, and
found to be expired before the cancellation are
reported.
compression candidate list can be displayed with the

QUERY COMPRESSION command.
ANR6214I

completed successfully - number of files
promoted candidate files were promoted
as candidates at level audit level, number
of files eliminated files were eliminated as
candidates, and number of files expired
candidates were eliminated because they
were found to be expired on the server.

that were promoted as candidates at this level of audit,
found to be expired are reported.
ANR6215I
Command name: Backup for file high-level

object name low-level object name in
filespace client filespace name for node
client node name could not be forced.
Explanation: It is not possible to force a backup for

the specified file using the FORCE BACKUP command.
This file was either backed up using an API client or by
an ADSM version 2 client or higher.
System action: The force backup operation continues,
the state of the compression record for this file is
updated.
User response: If the file was backed up using a
Version 2 client, or higher, you may remove this entry
as a candidate, using the REMOVE COMPRESSION
command. If the file was backed up using an API
client, notify the client owner to again back this file up.
Do not remove this entry until it becomes an inactive
entry.
ANR6220I
Delete compression operation started as

process process ID.
Explanation: A compression deletion operation was

started as a background server process with the
indicated identifier.
ANR6221I
Force backup operation started as

process process ID.
Explanation: A force backup operation was started as

a background server process with the indicated
identifier.
User response: The compression audit can be restarted

with the AUDIT COMPRESSION command. The
436
ANR6222I ANR6300E
ANR6222I
Command name: Process process ID was

cancelled - number of files files were
processed prior to cancellation.
Explanation: The indicated process was cancelled

prior to completion. This message displays the
indicated number of files that were processed before
the operation was cancelled.
System action: The process ends.
User response: The operation may be restarted by
reissuing the indicated command.
ANR6223I
Delete compression process process ID

has completed - number of files files were
deleted.
Explanation: The indicated process has completed

processing. All database references have been deleted
for the indicated number of files.
User response: The CANCEL PROCESS command can

be used to cancel the compression cleanup operation.
The QUERY PROCESS command may be used to query
the status of the operation.
ANR6227I
Explanation: A compression cleanup operation has

been started to remove compression candidate
information and temporary database entries from the
server database. Client files are not affected by this
operation.
User response: The CANCEL PROCESS command can
be used to cancel the compression cleanup operation.
The QUERY PROCESS command may be used to query
the status of the operation.
ANR6228W

ANR6224I
Force backup process process ID has

completed - number of files files were
marked for forced backup.
cleanup process name operation starting as

process process ID.
Cleanup process name: Process process ID

has been cancelled - cleanup processing
is incomplete.

been cancelled prior to successful completion.
User response: The CLEANUP COMPRESSION
command can be used to restart the cleanup operation.
Explanation: The indicated process has completed

processing. The indicated number of files have been
marked for forced backup. These files will be backed
up during the next incremental backup.
ANR6229I

successfully completed.

ANR6225I
File identifier removed as a suspect for

compression errors.
Explanation: The file with the specified identifier has

been removed from the database information
concerning files with possible compression errors.
Other database information concerning the file is not
affected.

System action: The cleanup process ends.

ANR6300E
Command name: Insufficient server

memory available for the operation.
Explanation: A compression testing routine cannot

continue because sufficient memory is not available on
the server.
User response: Increase the memory available to the

server by increasing the server region size, virtual
machine size, paging space available on the system, or
relocating the memory swap file, depending upon the
platform on which the server is executing. Additional
memory may also be made available by limiting server
activity (sessions, migration, and other activities) while
this operation is processing.
ANR6226I
Command name: Started as background

process process ID.

been started to remove compression candidate
information and temporary database entries from the
server database. Client files are not affected by this
operation.
437
ANR6301E ANR6601E
ANR6301E
Command name: Invalid LEVEL specified.

This command only supports a value of
1 or 2 for the LEVEL parameter.
Explanation: An invalid LEVEL= parameter has been

specified for the command.
value of 1 or 2 for the LEVEL parameter.
ANR6302E
Command name: Process process ID, failed

- number of candidate files candidate files
were found in number of files examined
files examined prior to failure.
Explanation: A compression audit operation failed

were found prior to the failure are displayed.
User response: Examine message that appear before
this message on the server console or in the activity log
to determine the source of the failure. If the error can
be corrected, re-execute the compression audit. If the
failure cannot be determined or corrected, contact your
service representative. The compression candidate list
can be displayed with the QUERY COMPRESSION
command.
ANR6303E
Command name: Process process ID, failed

- number of files promoted candidate files
were promoted as candidates at level
audit level, number of files eliminated files
were eliminated as candidates, and
number of files expired candidates were
eliminated because they were found to
be expired on the server.
Explanation: A compression audit operation failed

were promoted as candidates at this level of audit,
found to be expired before the audit failure are
reported.
User response: Examine message that appear before
this message on the server console or in the activity log
to determine the source of the failure. If the error can
be corrected, re-execute the compression audit. If the
failure cannot be determined or corrected, contact your
service representative. The compression candidate list
can be displayed with the QUERY COMPRESSION
command.
ANR6304E
Command name: Command cannot be

processed until compression audit is
performed.
Explanation: The indicated command cannot be

processed until a compression audit is performed using
the AUDIT COMPRESSION command.
User response: Issue the AUDIT COMPRESSION
command and then repeat the attempted operation.
ANR6305E
Command name: File identifier is not a

suspect for compression errors.
Explanation: The file with the specified identifier is

not listed in the database as a suspect for compression
errors. The file cannot be removed from the suspect list.
User response: Use the QUERY COMPRESSION
command to obtain the correct identifier for the file to
be removed.
ANR6306E

failed due to server error - cleanup
processing is incomplete.

failed before successful completion.
System action: The cleanup process ends.
User response: Examine messages that appear on the
server console or in the server activity log prior to this
message to determine the cause of the error. If the error
can be identified and corrected, restart the cleanup
operation with the CLEANUP COMPRESSION
command. If the error cannot be corrected, contact your
ANR6600E
Command: Invalid machine name machine name.
Explanation: The machine name specified in the

command is invalid.
command.
a valid machine name.
ANR6601E
Command: Description information

exceeds maximum length characters.
Explanation: The description specified in the

command exceeds the maximum length of allowable
characters.
command.
438
ANR6602E ANR6611E
a valid description.
ANR6602E
Command: Recovery instructions file

name exceeds maximum length characters.
Explanation: The recovery instructions file name

specified in the command exceeds the maximum length
of allowable characters.
command.
a valid recovery instructions file name.
ANR6603E
Command: Characteristics file name

Explanation: The characteristics file name specified in

the command exceeds the maximum length of
allowable characters.
command.
a valid characteristics file name.
ANR6604E
Command: Invalid building identifier building.
Explanation: The building identifier specified in the

command is invalid.
command.
a valid building identifier.
ANR6605E
Command: Invalid floor identifier - floor.
Explanation: The floor identifier specified in the

command is invalid.
command.
a valid floor identifier.
ANR6606E
Command: Invalid room identifier - room.
Explanation: The room identifier specified in the

command is invalid.
command.
ANR6607E
Command: Machine machine name is

already defined.
Explanation: The machine specified in the command

is already defined to the server.
command.
another machine.
ANR6608E
Command: A machine containing a server

is already defined.
Explanation: The ADSMSERVER=YES parameter

specified in the command is invalid because another
machine has already been defined with this parameter.
Only one machine can be defined to the server as
containing a server.
command.
User response: Issue the command again and do not
specify ADSMSERVER=YES as a parameter.
ANR6609I
Machine machine name defined.
Explanation: A DEFINE MACHINE command has

added the requested machine to the server.
ANR6610E
Command: Invalid recovery media name recovery media name.
Explanation: The recovery media name specified in

the command is invalid.
command.
a valid recovery media name.
ANR6611E
Command: Location information exceeds

Explanation: The location specified in the command

exceeds the maximum length of allowable characters.
command.
a valid location.

a valid room identifier.
439
ANR6612I ANR6622E
ANR6612I
Machine machine name updated.
Explanation: An UPDATE MACHINE command has

updated one or more attributes of a machine.
ANR6613I
Machine machine name deleted.
Explanation: A DELETE MACHINE command has

deleted the requested machine from the server.

a valid registered node.
ANR6618E
Command: No matching node registered.
Explanation: The node specified in the command does

not match any node registered to the server.
command.
a valid node.

ANR6614E
Command: Machine machine name is not

defined.

is not defined to the server.
ANR6619I
Node node name associated with machine

machine name.
Explanation: A DEFINE MACHNODEASSOCIATION

command has associated the specified node with the
specified machine. The node node name is associated
with the machine machine name.

command.

a valid machine.
ANR6620E
ANR6615E
Command: Failed to open input file - file

name.
Explanation: The input file specified in the command

cannot be opened by the server.
command.
an input file that is in a file system accessible by the
server.
ANR6616E
Command: Invalid sequence number sequence number.
Explanation: The sequence number specified in the

command is invalid.
Command: Machine and node association

is already defined.
Explanation: The machine and node association

specified in the command is already defined to the
server.
System action: The server operation continues, but the
a valid node.
ANR6621I

machine machine name.
Explanation: A DELETE MACHNODEASSOCIATION

command has deleted the requested association from
the server. The node node name is not associated with
the machine machine name.

command.

a valid sequence number.
ANR6622E
ANR6617W

processed because it is not registered.
Explanation: The node indicated in the message

cannot be processed because it is not registered.
but another node can be processed if specified by this
command.
440
Command: Recovery media recovery media

Explanation: The recovery media specified in the

command is not defined to the server.
command.
a valid recovery media.
ANR6623W ANR6632I
ANR6623W
Command: Machine machine name cannot

be processed because it is not defined.
Explanation: The machine indicated in the message is

not defined to the server.
System action: The indicated machine is not
processed, but another machine can be processed if
specified by this command.
a valid machine.
ANR6624E
Command: No matching machine

defined.

does not match any machine defined to the server.
command.
a valid machine.
ANR6625I
Machine machine name associated with

recovery media recovery media name.
Explanation: A DEFINE
RECOVERYMEDIAMACHASSOCIATION command
has associated the specified machine with the specified
recovery media. The machine machine name is
associated with the recovery media recovery media name.
ANR6626E
Command: Recovery media/machine

association is already defined.
ANR6628E
Command: Volume list exceeds maximum

length characters.
Explanation: The volume list specified in the

characters.
command.
a valid volume list.
ANR6629E
Command: Product name exceeds

Explanation: The product name specified in the

characters.
command.
a valid product name.
ANR6630E
Command: Product information exceeds

Explanation: The product information specified in the

characters.
command.
valid product information.
ANR6631E
Command: Missing volume list for boot

recovery media.
Explanation: The recovery media/machine association

specified in the command is already defined to the
server.
Explanation: Boot recovery media cannot be defined

to the server without specifying a volume list.


command.

a valid machine.

the volume list for the boot recovery media.
ANR6627I
Machine machine name disassociated

from recovery media recovery media name.
Explanation: A DELETE
RECOVERYMEDIAMACHASSOCIATION command
has deleted the requested association from the server.
Machine machine name is not associated with the
recovery media recovery media name.
ANR6632I
Recovery media recovery media name

defined.
Explanation: A DEFINE RECOVERYMEDIA command

has defined the recovery media to the server.

441
ANR6633I ANR6641E
ANR6633I

updated.
Explanation: An UPDATE RECOVERYMEDIA

command has updated one or more attributes of the
recovery media.
ANR6634I

deleted.
Explanation: A DELETE RECOVERYMEDIA

command has deleted the requested recovery media
from the server.
ANR6638E
Explanation: The characteristics for the machine

specified in the command are already defined to the
server.
command.
User response: If the specified machine is defined to
the server, issue an UPDATE MACHINE command to
update the existing characteristics. If the machine is not
defined to the server, run AUDIT DRM FIX to delete
the characteristics.
ANR6639E

ANR6635E
Command: Recovery media recovery media

name is already defined.
Command: The characteristics for

machine machine name are already
defined.
Command: The recovery instructions for

machine machine name are already
defined.
Explanation: The recovery instructions for the

machine specified in the command are already defined
to the server.
Explanation: The recovery media specified in the

command is already defined to the server.

command.

command.
User response: If the specified machine is defined to

the server, issue an UPDATE MACHINE command to
update the existing recovery instructions. If the
machine is not defined to the server, run AUDIT DRM
FIX to delete the recovery instructions.

a different recovery media.
ANR6636E
Command: The characteristics specified

for machine machine name exceeds
ANR6640E
Command: Cannot delete volume list for

boot recovery media.
Explanation: The characteristics specified in the

characters.
Explanation: A volume list cannot be deleted for boot

recovery media. A volume list must exist for each boot
recovery media defined to the server.

command.

command.

valid characteristics.
User response: To delete the volume list, issue an

UPDATE RECOVERYMEDIA command and specify a
recovery media type of OTHER and VOLUMES=. To
change the recovery media type to BOOT, issue an
UPDATE RECOVERYMEDIA command and specify the
volume list containing the boot recovery media and
TYPE=BOOT.
ANR6637E
Command: The recovery instructions

specified for machine machine name
Explanation: The recovery instructions specified in the

characters.
ANR6641E

command.
Explanation: No association found for the machine

and node pair specified in the command.

valid recovery instructions.

Command: No association found for

machine and node pair specified.

a valid machine and node pair.
442
ANR6642E ANR6651I
ANR6642E
Command: No association found for

recovery media and machine pair
specified.
Explanation: No association found for the recovery

media and machine pair specified in the command.
a valid recovery media and machine pair.
ANR6647E

global attributes used for server DRM activities are
missing.
FIX=YES to recreate the DRM global attributes.
ANR6648I
ANR6643E
Command: Invalid parameter value parameter value.
Explanation: The parameter issued in the command is

invalid.
command.
a valid parameter.
Audit command: DRM global attributes

are missing.
Audit command: DRM global attributes

are missing - default values will be used
to recreate the attributes.

global attributes used for server DRM activities are
missing. Because FIX=YES has been specified on the
AUDIT command, default attribute values will be used
to recreate the administrative global attributes.
ANR6644E
Command: A character string must be

specified.
Explanation: The INSERT command is invalid. A

character string must be specified.
command.
a valid character string.
ANR6645W
Node node name has already been

associated with machine machine name.
Explanation: The node specified in the DEFINE

MACHNODEASSOCIATION command is invalid. The
node is already associated with another machine shown
in the message. A node can only be associated with one
machine.
but another node can be processed if specified by the
command.
a valid node name.
ANR6646I
Audit command: Auditing disaster

recovery manager definitions.

database audit and indicates that the disaster recovery
manager definitions are being examined by the
ANR6649E
Audit command: DRM machine ID


global attributes machine ID used for server DRM
FIX=YES specified so that the DRM global attributes
can be corrected.
ANR6650I

Assignments are incorrect - values will
be corrected.

global attributes machine ID used for server DRM
activities are incorrect. Since FIX=YES has been
User response: None
ANR6651I
Audit command: Invalid priority value

encountered for machine machine name.

invalid priority value for the machine indicated.
FIX=YES to correct the priority. Or, issue an UPDATE
MACHINE command and specify a new priority value.
443
ANR6652I ANR6660I
ANR6652I
Audit command: Invalid priority value

encountered for machine machine name the default value will be set.

invalid machine priority value for the machine
audit function sets the machine priority value to the
default value.
FIX=YES has been specified, the audit function removes

the machine floor value.
User response: To set the floor value to another value,
issue an UPDATE MACHINE command after the audit
command has completed.
ANR6657I

User response: To override the default value, issue an
UPDATE MACHINE command to change the value
ANR6653I
Audit command: Invalid building value


invalid building value for the machine indicated.
FIX=YES to correct the building value. Or, issue an
UPDATE MACHINE command and specify a new
building value.
ANR6654I
Audit command: Invalid building value

encountered for machine machine name the building value will be removed.

invalid building value for the machine indicated.
removes the machine building value.

invalid room value for the machine indicated.
FIX=YES to correct the room value. Or, issue an
room value.
ANR6658I
ANR6655I
Audit command: Invalid floor value


invalid floor value for the machine indicated.
FIX=YES to correct the floor value. Or, issue an
UPDATE MACHINE command and specify a new floor
value.
ANR6656I
Audit command: Invalid floor value

encountered for machine machine name the floor value will be removed.

invalid floor value for the machine indicated. Because
444
Audit command: Invalid room value

encountered for machine machine name the room value will be removed.

invalid room value for the machine indicated. Because
FIX=YES has been specified, the audit function removes
the machine room value.
User response: To set the room value for the specified
machine to another value, use the UPDATE MACHINE
command after the audit command has completed.
ANR6659I

User response: To set the building value to another
value, issue an UPDATE MACHINE command after the
Audit command: Invalid room value

Audit command: Invalid server value


invalid server value for the machine indicated.
FIX=YES to correct the server value. Or, issue an
server value.
ANR6660I
Audit command: Invalid server value

encountered for machine machine name the default value will be set.

invalid server value for the machine indicated. Because
machine server value to the default value.
UPDATE MACHINE command to change the value
ANR6661I ANR6669I
ANR6661I
Audit command: Multiple machines are

indicated as servers. Only one machine
should have the server indicator set to
YES.

more than one machine with the server indicator set to
YES.
User response: For a list of machines with the server
indicator set to YES, issue a QUERY MACHINE
ADSMSERVER=YES command. Issue an UPDATE
MACHINE command for each machine that is not a
server.
ANR6662I
Audit command: Characteristics for

machine machine name not found.

characteristics reference from a machine for
characteristics that are not in the server database.
invalid access value for the recovery media indicated.

sets the recovery media access value to the default
value.
UPDATE RECOVERYMEDIA command to change the
value after the audit command has completed.
ANR6666I
Audit command: Invalid type value

encountered for recovery media recovery
media name.

invalid type value for the recovery media indicated.
FIX=YES to correct the type value. Or, issue an
new type value.

User response: Issue an UPDATE MACHINE
command to load the characteristics into the database
ANR6663I
Audit command: Recovery instructions for

machine machine name not found.

recovery instructions reference from a machine for
recovery instructions that are not in the server
database.
User response: Issue an UPDATE MACHINE
command to load the recovery instructions into the
database after the audit command has completed.
ANR6664I
Audit command: Invalid access value

media name.
ANR6667I
Audit command: Invalid type value

media name - the default value will be
set.

invalid type value for the recovery media indicated.
sets the recovery media type value to the default value.
UPDATE RECOVERYMEDIA command to change the
ANR6668E
Audit command: Machine is not found for

internal machine ID machine ID, which
is referenced by recovery media.
Explanation: A database audit process finds recovery

media that references a machine that is not defined in

invalid access value for the recovery media indicated.

FIX=YES to correct recovery media attributes.

FIX=YES to correct the access value. Or, issue an
new access value.
ANR6669I
ANR6665I
Audit command: Invalid access value

media name - the default value will be
set.
Audit command: Machine is not found for

is referenced by recovery media - the
machine reference will be deleted.

media that references a machine that is not defined in
the server database. Because FIX=YES has been
specified for the audit command, the reference will be
removed from the server database.
445
ANR6670E ANR6678E
ANR6674E

ANR6670E
Audit command: Recovery media not

found for internal recovery media ID
recovery media ID, which is referenced by
a machine.
Explanation: A database audit process finds a machine

that references recovery media that is not defined in the
server database.

node that references a machine that is not defined in
FIX=YES to correct the machine attributes.
ANR6675I

FIX=YES to correct the recovery media attributes.
ANR6671I
Audit command: Recovery media not

found for internal recovery media ID
recovery media ID, which is referenced by
a machine - the recovery media
Explanation: A database audit process finds m

machine that references recovery media that is not
will be deleted from the server database.
ANR6672E
Audit command: Client node not found

for internal node ID node ID, which is
referenced by a machine.

that references a client node that is not defined in the
server database.

ANR6676E
Audit command: Client node not found

for internal node ID node ID, which is
referenced by a machine - the client
node reference will be deleted.

that references a client node that is not defined in the
for the audit command, the reference will be removed
from the server database.
Audit command: Machine not found for

is referenced by characteristics.

characteristics that reference a machine that is not
ANR6677I

ANR6673I

is referenced by a client node - the

node that references a machine that is not defined in
the server database. Because FIX=YES has been


is referenced by a client node.

is referenced by characteristics - the

characteristics that reference a machine that is not
will be removed from the server database.
ANR6678E

is referenced by recovery instructions.

instructions that reference a machine that is not defined
446
ANR6679I ANR6687E
ANR6679I

is referenced by recovery instructions the machine reference will be deleted.

instructions that reference a machine that is not defined
in the server database. Because FIX=YES has been
ANR6680E
Audit command: Missing or invalid

internal database attribute encountered
for machine machine name.
ANR6684I
Command: Volume volume name was

deleted.
Explanation: The MOVE DRMEDIA *

WHERESTATE=COURIERRETRIEVE command
displays the message. Volume volume name is deleted
from the server database. For database backup volume,
after its expiration days have elapsed, the volume
history record is deleted when it is returned onsite. For
an empty scratch copy storage pool volume, the
volume record is deleted when it is returned onsite.
System action: The volume record is deleted from the
server database.
User response: Issue the CHECKIN LIBVOLUME
command for each volume returned onsite if the
volume is reused by the server.
ANR6685E

defined.

attribute for the specified machine.
Explanation: Volume volume name is not defined to the

server.
System action: The indicated command is not

processed if the volume name is explicitly specified on
the command. If a volume pattern is specified on the
command, the volume shown is not processed, but the
other volumes are processed.

ANR6681I
Audit command: Missing or invalid

internal database attribute encountered
for machine machine name - the attribute
will be corrected.

attribute for the specified machine. Because FIX=YES
has been specified for the audit command the invalid
attribute will be corrected.
ANR6682I
Command command ended: number of

volumes volumes processed.
Explanation: The indicated command ended. The total

number of volumes successfully processed is shown in
the message.
System action: The indicated command ends.

valid volume name.
ANR6686E
Command: Volume volume name in use.
Explanation: The MOVE DRMEDIA *

WHERESTATE=MOUNTABLE command displays the
message. Volume volume name is used for another
operation.
System action: The command is not processed if the
volume is explicitly specified on the command. If a
volume pattern is specified on the command, the
indicated volume is not processed, but the other
volumes are processed.
If the volume is currently mounted, but idle, dismount
the volume by using a DISMOUNT VOLUME
command and then retry this operation.

ANR6687E
ANR6683I
Command: Volume volume name was

moved from from state state to to state.
Command: Executable command string

Explanation: Volume volume name is successfully

moved from state1 to state2 by the indicated command.
Explanation: The length of the executable command

string specified with the CMD parameter exceeds the
maximum length of allowable characters (255).
System action: The indicated volume is moved to the

destination state.
System action: The server stops processing the

command.

447
ANR6688E ANR6698E
a valid executable command with the CMD parameter.
ANR6688E
command: The specified command failed

because the entry/exit port of library
library name is full. Please remove the
volume(s) from the entry/exit port and
re-issue the command name command.
Explanation: The indicated operation has failed

because the entry/exit port of the specified library is
full.
User response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
any remaining eligible volumes.
ANR6690E
Command: Copy storage pool cstgp name

not defined for Offsite Recovery Media.
Explanation: The MOVE DRMEDIA or QUERY

DRMEDIA command displays the message. The
indicated command was issued with a copy storage
pool name specified, but the specified pool name is not
defined to DRM for Offsite Recovery Media.
System action: The indicated command is not
processed.
User response: Reissue the command, after defining
the specified copy storage pool to DRM for Offsite
Recovery Media.
ANR6695E
Explanation: The MOVE DRMEDIA or QUERY

DRMEDIA command displays the message. The
volume being processed has associated with the device
class name shown that is not defined to the server.
System action: The command is not processed if the
volume is explicitly specified on the command. If a
volume pattern is specified on the command, the
indicated volume is not processed, but the other
volumes not associated with the indicated class are
processed.
indicated device class is defined to the server.
ANR6696I
System action: The server starts the operation in

response to the indicated command entered by an
administrator.
User response: For SCSI library users, remove the
volume from the slot and issue a REPLY command,
along with the request ID, to tell the server the volume
was removed from the library.
Command: No match is found for this

move.
Explanation: The indicated command was issued, but

no matching volumes are defined to the server or the
volume specified is not managed by the command.
User response: Reissue the command specifying the
valid volume.
ANR6694E
Command: The ORM state state is invalid

for a volume with access mode access
mode.
Explanation: The indicated command specifies an

Offsite Recovery Media state that is invalid for a
volume with the access mode shown. Specify
COURIER or COURIERRETRIEVE for a volume that
has access mode of OFFSITE.
command.
COURIER or COURIERRETRIEVE as the state for a
volume that has access mode of OFFSITE.
448
command: operation for volume volume

name in library library name starting.
Explanation: The indicated operation is being started

for the volume shown in the given library.
ANR6697I
ANR6691E

not defined for volume volume name.

name in library library name completed
successfully.
Explanation: The indicated operation has completed

successfully for the volume shown in the given library.
System action: The volume is either deleted from the
library inventory (if its status is something other than
DATA) or marked not present (if its status is DATA).
ANR6698E

name in library library name failed.
Explanation: The indicated operation has failed for the

volume shown in the given library. This message
should be preceded by another error message which
provides more detail about the error.
User response: Check for additional message and
eliminate the condition that caused the failure, then
retry the command.
ANR6699I ANR6708W
ANR6699I
Cancel in progress.
Explanation: The MOVE DRMEDIA command has

been canceled and will end when resources have been
freed for the background process. This message may be
for a MOVE DRMEDIA command.
ANR6700I
Command command completed

successfully.
Explanation: The indicated command completed

successfully.

plan instructions prefix.
ANR6705E
Explanation: The indicated command has been

entered with an invalid character that is to be added to
the volumes names in the recovery plan file.
command.
character.
ANR6706E

ANR6701E
Command: Invalid courier name - courier

name.
Command: Invalid character for volume

postfix - postfix character.
Command: Invalid vault name - vault

name.

entered with an invalid vault name.
command.

entered with an invalid courier name.

vault name.

command.
ANR6707W

courier name.
ANR6702E
Command: Invalid expiration days value

- days value.

entered that specifies an invalid expiration days value.
command.
expiration days value.
ANR6703E
Command: Invalid recovery plan prefix prefix.

entered with an invalid recovery plan prefix.
command.
recovery plan prefix.
ANR6704E
Command: Invalid plan instructions

prefix - prefix.

entered with an invalid plan instructions prefix.
command.
Command: The state, access and location

attributes of the copy storage pool
volume volume name were not updated.
Explanation: The MOVE DRMEDIA command could

not update the state, access and location of volume
volume name because it was in use by another server
operation.
System action: If the volume was in an automated
library, the MOVE DRMEDIA command may have
checked the volume out of the library.
If a volume pattern is specified on the command, the
server continues processing the other volumes.
activity has completed, and then reissue the MOVE
DRMEDIA command.
ANR6708W
Command: Copy pool volume volume

name was not processed. The volume
was in use.
Explanation: The MOVE DRMEDIA command did not

process volume volume name because it was in use by
another server operation.
System action: The indicated command ends, if the
volume was explicitly specified in the command. If a
volume pattern was specified in the command, the
server continues processing other volumes that match
the pattern.
activity has completed, and then reissue the MOVE
DRMEDIA command.
449
ANR6711E ANR6719E
ANR6711E
Audit command: An invalid database

backup series expiration days
encountered.

invalid value for database backup series expiration
days.
FIX=YES to correct the expiration days. Or, issue an
SET DRMDBBACKUPEXPIREDAYS command and
specify a new expiration days value.
ANR6712I
Audit command: An invalid database

backup series expiration days
encountered - the default value will be
set.

invalid value for database backup series expiration
days. Because FIX=YES has been specified, the audit
function sets the expiration days value to the default
value.
User response: To override the default value, issue a
SET DRMDBBACKUPEXPIREDAYS command to
completed.
ANR6713E
Audit command: An invalid check label

value encountered.

invalid check label value.
FIX=YES to correct the check label value. Or, issue a
SET DRMCHECKLABEL command and specify a new
check label value.
ANR6714I
Audit command: An invalid check label

value encountered - the default value
will be set.

invalid check label value. Because FIX=YES has been
specified, the audit function sets the check label value
to the default value.
ANR6715E
Audit command: An invalid file process

value encountered.

invalid file process value.
FIX=YES to correct the file process value. Or, issue a
SET DRMFILEPROCESS command and specify a new
file process value.
ANR6716I
Audit command: An invalid file process

value encountered - the default value
will be set.

invalid file process value. Because FIX=YES has been
specified, the audit function sets the file process value
to the default value.
SET DRMFILEPROCESS command to change the value
ANR6717E
Audit command: Extraneous DRM global

attribute encountered.

nonexistent DRM global attribute.
FIX=YES to delete the extraneous attribute.
ANR6718I
Audit command: Extraneous DRM global

attribute encountered - the attribute will
be deleted.

nonexistent DRM global attribute. Since FIX=YES has
been specified, the extraneous attribute will be deleted.
ANR6719E

assignments not found.
Explanation: A database audit process finds no entries

in server database for DRM internal machine ID
assignments.

SET DRMCHECKLABEL command to change the value
450

FIX=YES to correct the error.
ANR6720I ANR6728I
ANR6720I

assignments not found - entry will be
created.

in server database for DRM internal machine ID
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry
in the server database for the machine ID assignments.
ANR6721E
Audit command: DRM recovery media ID

assignments not found.

in server database for DRM internal recovery media ID
assignments.
FIX=YES to correct the error.
ANR6722I

assignments not found - entry will be
created.

in server database for DRM internal recovery media ID
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry
in the server database for the recovery media ID
assignments.

SET DRMPLANFILEPREFIX command to change the
ANR6725E
Audit command: Prefix for DRM recovery

plan instructions not found.

in server database for DRM recovery plan instructions
prefix definitions.
specify FIX=YES to correct the error.
ANR6726I

plan instructions not found - entry will
be created.

in server database for DRM recovery plan instructions
prefix definitions. Because FIX=YES has been specified
for the audit command, the audit function creates an
entry using the default value in the server database for
the recovery plan instructions file prefix.
SET DRMPLANINSTRPREFIX command to change the
ANR6727E
Audit command: Postfix for DRM

replacement volumes names not found.

in server database for DRM postfix definitions for
replacement volumes names.
ANR6723E

plan not found.

in server database for DRM recovery plan prefix
definitions.
ANR6724I

plan not found - entry will be created.

in server database for DRM recovery plan prefix
definitions. Because FIX=YES has been specified for the
audit command, the audit function creates an entry
using the default value in the server database for the
recovery plan file prefix.

ANR6728I
Audit command: Postfix for DRM

replacement volumes names not found entry will be created.

in server database for DRM postfix definitions for
replacement volumes names. Because FIX=YES has
been specified for the audit command, the audit
function creates an entry using the default value in the
server database for the replacement volumes postfix.
SET DRMPLANVPOSTFIX command to change the
451
ANR6729E ANR6737E
ANR6729E
Audit command: Primary storage pools to

be restored by DRM not found.
System action: The indicated command is ended and

server processing continues.


ANR6734E

in server database for primary storage pools to be
restored by DRM.
ANR6730I
Audit command: Primary storage pools to

be restored by DRM not found - entry
will be created.

in server database for primary storage pools to be
restored by DRM. Because FIX=YES has been specified
the primary storage pools to be restored by DRM.
SET DRMPRIMSTGPOOL command to change the
ANR6731E
Audit command: Copy storage pools to be

managed by DRM not found.

in server database for copy storage pools to be
managed by DRM.
ANR6732I
Audit command: Copy storage pools to be

managed by DRM not found - entry
will be created.

in server database for copy storage pools to be
managed by DRM. Because FIX=YES has been specified
the copy storage pools to be managed by DRM.
SET DRMCOPYSTGPOOL command to change the
ANR6733E
Command: Cannot complete initialization

for process name process.
Explanation: The indicated process fails during

process initialization.
452

processed: library library name not
defined.
Explanation: The indicated volume is not processed

since the designated library has not been defined or has
been deleted.
command.
ANR6735E
Audit command: Courier information for

ORM not found.

in server database for courier name definitions used by
DRM Offsite Recovery Media (ORM).
ANR6736I
Audit command: Courier information for

ORM not found - entry will be created.

in server database for courier name definitions used by
DRM Offsite Recovery Media (ORM). Because FIX=YES
has been specified for the audit command, the audit
server database for the courier name definitions.
SET DRMCOURIERNAME command to change the
ANR6737E
Audit command: Vault name for ORM not

found.

in server database for vault name definitions used by
ANR6738I ANR6746I
ANR6738I
Audit command: Vault name for ORM not

found - entry will be created.
ANR6742I
Audit command: Check label indicator for


in server database for vault name definitions used by
server database for the vault name definitions.

in server database for check label definitions used by
DRM Offsite Recovery Media (ORM ). Because
audit function creates an entry using the default value
in the server database for the check label definitions.

SET DRMVAULTNAME command to change the value

SET DRMCHECKLABEL command to change the value
ANR6739E
Audit command: Database backup series

expiration days for ORM not found.

in server database for database backup series expiration
days definitions used by DRM Offsite Recovery Media
(ORM).
ANR6743E

in server database for file process definitions used by
ANR6744I
ANR6740I
Audit command: Database backup series

expiration days for ORM not found entry will be created.

in server database for database backup series expiration
days definitions used by DRM Offsite Recovery Media
(ORM). Because FIX=YES has been specified for the
database backup series expiration days definitions.
SET DRMDBBACKUPEXPIREDAYS command to
completed.
ANR6741E
Audit command: Check label indicator for

ORM not found.

in server database for check label definitions used by
Audit command: File process indicator for

ORM not found.
Audit command: File process indicator for


in server database for file process definitions used by
server database for the file process definitions.
SET DRMFILEPROCESS command to change the value
ANR6745E


global attributes recovery media id used for server
DRM activities are incorrect.
FIX=YES specified so that the DRM global attributes
can be corrected.
ANR6746I

assignments are incorrect - values will
be corrected.

global attributes recovery media ID used for server
DRM activities are incorrect. Since FIX=YES has been
453
ANR6747I ANR6754I
ANR6751E

ANR6747I
Number of volumes processed: number

processed the number of volumes displayed. This
PROCESS command for a MOVE DRMEDIA command.
ANR6748I
Number of volumes processed: number.

Checking out volume volume name from
library library name.
Explanation: The MOVE DRMEDIA command

displays the number of volumes already processed and
the name of the volume currently being checked out
from the indicated library. This message may be
for a MOVE DRMEDIA command.
ANR6749I
Command: process process ID terminated

before completion - process canceled.
Explanation: The indicated background process

performing the command shown has been canceled.
System action: If other processes are executing, these
processes continue.
Disaster recovery manager operation

command being processed is denied - server
is not licensed for disaster recovery
manager support.
Explanation: The server refuses a disaster recovery

manager operation because the server is not licensed to
support the disaster recovery manager.
User response: Obtain the license to support the
disaster recovery manager from your service provider
or reseller. Issue the REGISTER LICENSE command
with this license to enable the disaster recovery
manager support.
ANR6752W

Command being processed is in violation of
server license terms - server is not
licensed for disaster recovery manager
support.
Explanation: The server warns about a disaster

recovery manager operation because the server is not
licensed to support disaster recovery manager.
User response: Obtain the license to support disaster
recovery manager from your service provider or
reseller. Issue the REGISTER LICENSE command with
this license to enable disaster recovery manager
support.
ANR6753E
command being processed encountered an

internal server error while checking
license compliance.

in determining whether the server is in compliance
with license terms.
ANR6750E

command being processed is denied - server
is not in compliance with license terms.

manager operation because the current server
configuration is not in compliance with the license
terms.
System action: Server operation continues. Disaster
recovery operations cannot be performed until the
server is licensed for the Tivoli Disaster Recovery
Manager product.
User response: Issue a QUERY LICENSE command to
determine which license terms are not in compliance.
User response: Issue the QUERY LICENSE and

QUERY STATUS commands to determine if the server
is in compliance with license terms. Start an AUDIT
LICENSES process to adjust server license information.
When this process completes, start the session again. If
the problem persists, contact your service
representative.
ANR6754I
Machine machine name characteristics

deleted.

deleted the requested characteristics from the server.
454
ANR6755I ANR6762E
ANR6755I
Machine machine name recovery

instructions deleted.

deleted the requested recovery instructions from the
server.

ANR6760E

ANR6756E
Machine machine name characteristics not

Explanation: A DELETE MACHINE command cannot

delete the requested characteristics from the server. The
characteristics for the specified machine are not defined
to the server.
a machine that has characteristics defined to the server.
ANR6757E
Machine machine name recovery

instructions not defined to the server.
Explanation: A DELETE MACHINE command cannot

delete the requested recovery instructions from the
server. The recovery instructions for the specified
machine are not defined to the server.
a machine that has recovery instructions defined to the
server.
ANR6758E
Command: Only one character string can

be specified.
Explanation: The INSERT command is invalid. Either

a characteristics string can be specified or a recovery
instructions string can be specified on the command.
Both types of strings cannot be specified on the
command at the same time.
command.
one valid character string.
ANR6759E

command being processed is denied disaster recovery manager support is not
available for server platform platform.

manager operation because disaster recovery manager
support is not available for the indicated server
platform.
Command: Executable command line

exceeds maximum length characters for
volume volume name.
Explanation: While writing to a command file, one of

the following conditions occurred:
v The length of the command line written to the
command file exceeds the LRECL specified for MVS
or exceeds the default length for the command line
written (255).
v The length of the command created after replacing
the substitution variables &VOL, &VOLDSN, &NL,
and &LOC exceeds the server allowable command
line length (1500).
command.
a valid executable command with the CMD parameter.
In the case where volumes are being ejected from the
library, it is possible the server database does not reflect
the true state of the volume. For MOVE DRMEDIA,
rerun the command after determining the cause of the
error. For MOVE MEDIA, an update volume command
should be issued setting the access of the volume to
read only.
If this message is issued by a MOVE or QUERY
DRMEDIA command and the volume record has been
deleted from the server database, you can not use the
MOVE or QUERY DRMEDIA commands to create the
command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6761E
Command: WHERESTATE parameter is

required.
Explanation: The indicated command specifies a

volume name containing a pattern matching character
and the TOSTATE parameter. The WHERESTATE
parameter is not specified. The specification is invalid.
Pattern-matching for volume names is only allowed
when the WHERESTATE parameter is specified.
command.
specific volume name or by specifying the
WHERESTATE parameter along with the TOSTATE
parameter.
ANR6762E
Command: The specified destination state

tostate is invalid for volume volume name
in current state state.
Explanation: The indicated command specifies a

455
ANR6763I ANR6771E
destination state that is invalid for the volume name
shown in the indicated current state.
volume.
a valid destination state for the volume name shown.
ANR6763I
Command: The specified command has

been written to file file name.
Explanation: The command string specified with the

CMD parameter on the command shown is written to
the indicated file for each volume successfully
processed.
User response: Execute the commands written to the
file.
ANR6764E
command: Command file name exceeds

Explanation: The file name specified for containing

the executable commands generated by DRM exceeds
the maximum valid length shown.
command.
valid file name.
ANR6767E
Command: Invalid command file name command file name.

entered with an invalid command file name.
command.
command file name.
ANR6768E
command: Prefix exceeds maximum

characters characters.
Explanation: The prefix specified for recovery plan

files or for plan instructions files exceeds the maximum
valid length. The maximum valid length is shown in
the message.
command.
valid prefix.
ANR6769E
Audit command: Not mountable name

information for ORM not found.

in server database for not mountable location name
definitions used by DRM Offsite Recovery Media
(ORM).
ANR6765E
Command: Invalid not mountable

location name - not mountable name.

entered with an invalid not mountable location name.

ANR6770I

command.
User response: Reissue the command with a valid not
mountable location name.
ANR6766E
Command: No command string is

specified for FORMAT=CMD.

entered with a FORMAT=CMD to write a command
string to a file, but no command string is specified.
command.
command string to be written to a file.
Audit command: Not mountable name

information for ORM not found - entry
will be created.

in server database for not mountable location name
definitions used by DRM Offsite Recovery Media
(ORM). Because FIX=YES has been specified for the
courier name definitions.
SET DRMNOTMOUNTABLENAME command to
completed.
ANR6771E
Audit command: Command file name

information for ORM not found.

in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM).
456
ANR6772I ANR6778E
ANR6772I
Audit command: Command file name

information for ORM not found - entry
will be created.

in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM). Because
audit function creates an entry using the default value
in the server database for the command file name
definitions.
SET DRMCMDFILENAME command to change the
ANR6773E
Command: Unable to open file command

file name for output.

command file name shown. The file name shown in the
message is specified with the indicated command, the
SET command, or the default name generated by the
indicated command.
ANR6775E
Command: Error writing to file file name

for volume volume name.

file name shown for the indicated volume.
command.
proper authority to write to the file indicated. Reissue
the command after determining the cause of the error.
In the case where volumes are being ejected from the
library, it is possible the server database does not reflect
the true state of the volume. For MOVE DRMEDIA,
rerun the command after determining the cause of the
error. For MOVE MEDIA, an update volume command
should be issued setting the access of the volume to
read only.
If this message is issued by a MOVE or QUERY
DRMEDIA command and the volume record has been
deleted from the server database, you can not use the
MOVE or QUERY DRMEDIA commands to create the
command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6776E
Command: Could not delete file: file name

indicated command.
Explanation: The indicated command failed but the

file created could not be deleted.

proper authority to write to the file indicated. In AIX,
make sure that the file name specified in the command
or in the SET command is a full path file name, not a
directory path name. In MVS, make sure that the file
name specified in the command or in the SET
command is a valid MVS file name. Reissue the
command after determining the cause of the error.
ANR6774E
Command: Invalid volume transition

states - from specified WHERESTATE
state to specified TOSTATE state.
User response: Delete the file shown.

ANR6777E
Command: Command file file name

already in use.

command file name that is in use. The command file
name shown is selected for use by the server in the
following order:
v The file name specified on the indicated command.
v The file name specified on the SET command.
v The file name generated by the server (AIX only).
Explanation: The TOSTATE specified is an invalid

destination state for the WHERESTATE specified.

command.

command.
User response: Reissue the command at a later time

or reissue the command specifying a different
command file name.

a valid destination state.
ANR6778E

processed: device type device type not
supported.

because the device type shown is not supported by the
function.
457
ANR6779E ANR6901I
System action: The indicated volume is not processed.

recovery plan file expiration days definitions.
ANR6779E

command being processed is denied disaster recovery manager support is not
available for server platform.

manager operation because disaster recovery manager
support is not available for the server platform.

SET DRMRPFEXPIREDAYS command to change the
ANR6784I

ANR6780E
Audit command: An invalid recovery plan

file expiration days encountered.

invalid value for recovery plan file expiration days.
FIX=YES to correct the expiration days. Or, issue an
SET DRMRPFEXPIREDAYS command and specify a
new expiration days value.
ANR6781I

SET DRMRPFEXPIREDAYS command to change the
ANR6782E
Audit command: Recovery plan file

expiration days not found.

in server database for recovery plan file expiration days
definitions.
ANR6783I
Audit command: Recovery plan file

expiration days not found - entry will
be created.

in server database for recovery plan file expiration days
definitions. Because FIX=YES has been specified for the
458

processed the number of volumes shown. Currently, the
MOVE DRMEDIA command has sent for processing
the number of volumes shown to the library shown.
This message may be displayed in response to a
QUERY PROCESS command for a MOVE DRMEDIA
command.
ANR6785W
Audit command: An invalid recovery plan

file expiration days encountered - the

invalid value for recovery plan file expiration days.
sets the expiration days value to the default value.

volumes processed. Volumes sent to library
library name for checkout: number volumes
sent.
Warning: The ADSM V3 Disaster

Recovery Manager Disk Image Dump
function is not supported in the Tivoli
Disaster Recovery Manager. The ADSM
V3 DRM Disk Image Restore function
has been stabilized with no new
maintenance or hardware support
planned.
Explanation: None.
System action: DRM Disk Image Dump and Restore
function continues.
ANR6900I
Command: The recovery plan file file

name was created.
Explanation: The recovery plan file was created.

ANR6901I
Number of plan stanzas processed:

number.
Explanation: The PREPARE command has processed

the number of stanzas displayed. This message may be
for a PREPARE command.
ANR6902I ANR6920W
ANR6902I
Number of plan stanzas processed:

number. Currently processing stanza:
recovery plan stanza name.
Explanation: The PREPARE command displays the

number of stanzas already processed and the name of
the stanza currently being processed. This message may
be displayed in response to a QUERY PROCESS
command for a PREPARE command.
ANR6913W
Command: No volumes with backup data

exist in copy storage pool storage pool
name.
Explanation: A copy storage pool does not contain

any volumes with usable data.
System action: Stanzas in the recovery plan do not
include recovery information for any volumes in the
storage pool.
User response: Determine why this storage pool has

no volumes with usable data.
ANR6903I
ANR6915W
Cancel in progress.
Explanation: The PREPARE command has been

for a PREPARE command.

storage pool type is not defined to the
server.
Explanation: A storage pool that is not defined to the

server was specified by SET DRMPRIMSTGPOOL, SET
DRMCOPYSTGPOOL, or on the PREPARE command
line.

include recovery information for the storage pool.
ANR6904I
User response: Correct the storage pool specification

or define the storage pool to the server.
Sending recovery plan file to target

server.
Explanation: The PREPARE command is sending the

recovery plan file to the target server. This message
may be displayed in response to a QUERY PROCESS
command for a PREPARE command.
ANR6905I
Command: Recovery plan file RPF volume

name was created. Specified device class
device class name.
Explanation: The recovery plan file was created on the

target server.
ANR6912W
Command: The database was not backed

up.
ANR6916W
Command: No copy storage pools are

defined.
Explanation: The server has no copy storage pools

defined.
System action: Recovery plan file will not contain
copy storage pool information.
User response: Define copy storage pools in the
server.
ANR6918W
Command: Recovery instructions file file

name not found.
Explanation: A source file for recovery instructions

was not found.
System action: The recovery plan will not contain
recovery instructions.
Explanation: No backups have been made of the

server data base.
User response: To get recovery instructions in the

recovery plan, ensure the corresponding instructions
source file exists. If it does, check authorizations to the
file.

include database recovery information.
ANR6920W
User response: Backup the server data base by issuing

the BACKUP DB command.
Command: Generated replacement

volume name volume name is not valid
for server device type device type.
Original volume name: volume name.
Stanza is stanza name.
Explanation: Appending the replacement volume

name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name
459
ANR6921W ANR6927W
has created a name that is not valid for the server
device type shown.
System action: Replacement volume name is used in
the recovery plan stanza.
User response: Devise a naming convention that
allows the use of the replacement volume name postfix
or at restore time manually update the generated
recovery plan with a legal replacement name. For
additional information and related commands, refer to
platform.
ANR6921W
Command: Cannot locate server options

file file name.
ANR6924W
Command: No recovery instructions

defined for machine machine name.
Explanation: No recovery instructions have been

defined to the server for the specified machine.
System action: The recovery plan file does not contain
the machine recovery instructions stanza.
User response: If you want to include the machine
recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command
after the appropriate commands have been issued to
define the recovery media. For additional information
and related commands, refer to the Administrators
Explanation: The Prepare command cannot open the

specified server options file.
ANR6925W
System action: VOLHISTORY and DEVCONFIG

options are added to the recovery plan file stanza
DSMSERV.OPT.FILE.
Explanation: No characteristics have been defined to

the server for the specified machine.

the machine characteristics stanza.
ANR6922W
Command: No machine information was

defined for the machine that contains
server server name.
Explanation: The machine information has not been

saved in the server data base.
the machine and recovery media information stanzas.
information in the recovery plan file, issue the DEFINE
MACHINE command to save the machine information
in the server data base and reissue the PREPARE
command.
ANR6923W
Command: No recovery media defined

for machine machine name.
Command: No machine characteristics

defined for machine machine name.

recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command
after the appropriate commands have been issued to
define the recovery media. For additional information
and related commands, refer to the Administrators
ANR6926W
Command: There is at least one invalid

generated volume name associated with
storage pool storage pool server device
type device type in stanza stanza name.

name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name
has created a name that is not valid for the server
device type shown.
Explanation: No recovery media has been defined to

the server for the specified machine.


the machine recovery media stanza.
User response: Devise a naming convention that

allows the use of the replacement volume name postfix
or at restore time manually update the generated
recovery plan with a legal replacement name. For
additional information and related commands, refer to
platform.

recovery media information in the recovery plan file,
issue the DEFINE RECOVERYMEDIA command.
Reissue the PREPARE command after the appropriate
commands have been issued to define the recovery
media. For additional information and related
ANR6927W
Command: Primary storage pool storage

pool name, storage pool data format, is not
managed by DRM.
Explanation: A SET DRMPRIMSTGPOOL or the

PREPARE command specified a primary storage pool
that is used for backing up NAS file servers, using
460
ANR6928W ANR6942E
NDMP. DRM does not manage a storage pool with this
data format.

command.


parameter from the web.
User response: Correct the storage pool specification.

ANR6938I
ANR6928W
Command: No eligible primary storage

pools match the specified storage pool
name storage pool name .
Explanation: The storage pool specified by the SET

DRMPRIMSTGPOOL or on PREPARE command does
not match any eligible primary storage pool. Possible
reasons include:
v Primary storage pools were not defined.
v Primary storage pools were defined, but their data
formats are for NAS file servers, or their device
classes use the CENTERA device type.
v The name specified does not match eligible primary
storage pool names.
include recovery information for the storage pools.
User response: Correct the storage pool specification
or define eligible storage pools to the server.
Explanation: No information found for recovery plan

file stanza shown.
System action: The server does not display the
information for the stanza.
User response: None
ANR6939E
Command: No eligible primary storage

pools are defined to the server.
Explanation: The server has no eligible primary

storage pools defined.
Command: Invalid recovery plan file

stanza name - stanza name.
Explanation: The specified recovery plan file stanza

name is invalid.
command.
a valid recovery plan file stanza name.
ANR6940E
ANR6929W
No information found for stanza stanza

name.
command command not allowed from

server console.
Explanation: The indicated command is not allowed

to be issued from the server console.
System action: Recovery plan file will not contain

primary storage pool information.
User response: Reissue the command from an

administrator using an Administrative Client.
User response: Define eligible primary storage pools

to the server.
ANR6941E
ANR6930W
Command: Primary storage pool storage

pool name, whose device class uses the
CENTERA device type, is not managed
by DRM.
Query recovery plan file content is

waiting for mount point in device class
device class name.
Explanation: Query recovery plan file content has

begun to wait for a mount point that can be used for a
volume in the device class shown.
Explanation: The SET DRMPRIMSTGPOOL or the

PREPARE command specified a primary storage pool
whose device class uses the CENTERA device type.
DRM does not manage storage pools that use the
CENTERA device type.
System action: The function waits for the mount

point.

ANR6942E
User response: Correct the storage pool specification.

ANR6937E
command: parameter name parameter not

allowed from the command line.
Explanation: The parameter shown is not allowed

from the command line interface.

waiting for access to input volume
volume name.

begun to wait for availability of the input volume
shown.
System action: The function waits for the volume to
become available.
461
ANR6943E ANR6951E
ANR6943E

waiting for mount of input volume
volume name.

begun to wait for the mount of the input volume
shown.
System action: The function waits for mount.
ANR6944E
Command: Invalid recovery plan file

name - recovery plan file name.
Explanation: The recovery plan file name specified in

the command is invalid.
command.
a valid recovery plan file name.
ANR6945E
Command: Cannot find filespace filespace

name for recovery plan file recovery plan
file name.
Explanation: The server cannot find the filespace

(ADSM.SERVER) for recovery plan file specified in the
server.
System action: The retrieve operation ends, and the
User response: Issue QUERY FILESPACE command
on the target server to see if there is any filespaces
created for the recovery plan file. The filespace name
for the recovery plan file is ADSM.SERVER.
ANR6946E
Command: Retrieve failed for recovery

plan file name - error on input storage
device.
Explanation: The server ends an retrieve operation

because an I/O error has been encountered by the
server in reading from a device.
The server may need to be shut down with the HALT
command to correct the hardware problem.
ANR6948E
Explanation: The server cannot find the specified

recovery plan file.
command.
a valid recovery plan file name. Use the QUERY
RPFILE command to view the name of the recovery
plan file that you are interested in displaying its
content.
ANR6949E
Command: Data storage retrieve failed

for recovery plan file name - error detected.
Explanation: The server ends the retrieve operation

because an error has been encountered on the server.
Some common reasons for the error are:
462
Command: No matching device class

defined.
Explanation: The device class specified in the

command does not match any device class defined to
the server.
command.
a valid device class.
ANR6950E
Command: The recovery plan file was not

created.
Explanation: Due to a processing error, a recovery

plan file was not created.
System action: Recovery plan file not created.
problems, if possible. Reissue the command, after
determining the cause of the error.
ANR6951E
ANR6947E
Command: Cannot find the recovery plan

file for Recovery plan file name.
Command: Recovery plan file file name

was not created.

plan file was not created.
ANR6952E ANR6966E
Reissue the command, after determining the cause of
the error.
ANR6962E
Command: Query database failed.
Explanation: A server database query error occurred.

System action: The recovery plan file was not created.
ANR6952E
Command: File name file name already

exists.
Explanation: File already exits.

User response: Determine why file already exists. If
possible, delete it. Reissue the command, after
ANR6953E
Command: File write error.

recovery plan file.
problems, if possible. Make sure that there is sufficient
space in the file system for the file. Reissue the
command after determining the cause of the error.
ANR6954E
Command: Unable to open file file name

for output.

recovery plan file for output.
proper authority to write to the file indicated. Reissue
the command after determining the cause of the error.
ANR6959E
Command: Plan instructions prefix

instructions prefix is not valid.
Explanation: The prefix specified for recovery

instructions is not valid.
valid prefix.
ANR6960E
Command: Recovery plan prefix plan

prefix is not valid.
Explanation: The prefix specified for the recovery plan

file is too long.
valid prefix.
User response: Issue a QUERY ACTLOG command to

view the activity log and search for messages. If the
ANR6963E
Command: Query log failed.

ANR6964E
Command: Query storage pool failed.
Explanation: An server database query error occurred.

ANR6965E
Command: Query volume failed.

ANR6966E
Command: Query database volume failed.

463
ANR6967E ANR6976E
ANR6967E
Command: Query log volume failed.
ANR6972E
Command: Query machine failed.

Explanation: A server machine query error occurred.



ANR6968E
Command: Query volume history failed.

ANR6969E

Command: A recovery plan file is already
being created.
Explanation: The server command processor will not

start a background process to execute another
PREPARE command.
User response: Reissue the command after the first
PREPARE command has completed.
ANR6971E
Command: Query recovery media failed.
Explanation: A server recovery media query error

occurred. This message always accompanies another
error message and provides more detail about that
error.
Command: Query device class failed.

ANR6970E
ANR6973E
Command: Could not delete plan file plan

file name.
Explanation: Prepare command failed but the plan file

created could not be deleted.
User response: Delete the plan file.
ANR6974E
Command: Unable to open file file name.
Explanation: An error occurred while PREPARE was

attempting to open the local recovery plan file copy in
order to send it to the target server.
System action: The recovery plan file is not stored on
the target server.
problems, if possible. Reissue the command after
ANR6975E
Command: Unable to read file file name.
Explanation: An error occurred while PREPARE was

attempting to read the local recovery plan file copy in
order to send it to the target server.
System action: The recovery plan file is not stored on
the target server.
problems, if possible. Reissue the command after
ANR6976E
Command: The recovery plan file was not

stored on another server and the local
copy file name cannot be deleted.

plan file was not stored on target server and the local
copy of the plan file cannot be deleted.
System action: PREPARE processing ends.
464
ANR6977E ANR7800I
problems, if possible. After determining the cause of
the error, re-issue the PREPARE command and delete
the local recovery plan file.
ANR6977E
Command: Device class name device class

name exceeds maximum characters
characters.
Explanation: The command shown has been entered

and specifies a device class name that is too long. The
maximum valid length for a device class name is
shown in the message.
command.
valid device class name.
ANR6978E
Command: Invalid device class device class

name.
Explanation: The specified device class cannot be used

by the command shown. Possible reasons include:
v The device class is not defined.
v The device class is defined but not of type SERVER.
v The name specified is an invalid device class name.
command.
device class.
ANR6979E
Command: Recovery plan file was not

created. Specified device class device class
name.
Explanation: A recovery plan file cannot be not

created using the specified device class.
problems, if possible. Reissue the command, after
ANR6984E
Explanation: During command PREPARE processing,

writing to the sequential media. Command PREPARE
media for storing data.
System action: Command PREPARE processing ends.
User response: Increase the device class maximum
capacity and reissue the PREPARE command. If an
object was created on the target server, issue the
RECONCILE VOLUMES FIX=YES to delete the object
from the target server.
ANR6985E
Command: Prefix prefix exceeds maximum

Explanation: The command shown has been entered

and specifies a plan or instructions prefix that is too
long. The maximum valid length is shown in the
message.


export, database dump, database backup, or DRM
prepare operation or is in use by another process.
User response: Re-issue the PREPARE command.
ANR6986E
Command: The DELETELATEST

parameter is only valid for volume
history types RPFILE or
RPFSNAPSHOT.

volume history type was specified for the TYPE=
parameter.
User response: Re-issue the command and specify a
valid type value.
ANR7800I
ANR6980E

mounted. Specified device class device
class name; maximum capacity: number of
bytes bytes.
DSMSERV generated at time on date.
Explanation: The server module was generated at the

indicated date and time.

command.
shorter prefix.
465
ANR7800I ANR7803E
ANR7800I
DSMSERV generated at time on date.


ANR7801I (HP-UX) Subsystem (master) process ID is
process identifier.
Explanation: The servers master HP-UX process has
the indicated process identifier.
ANR7800I (HP-UX) DSMSERV generated at time on

date.

ANR7801I (Linux) Subsystem process ID is process
identifier.
Explanation: The server process has the indicated
process identifier.
ANR7800I (Linux) DSMSERV generated at time on

date.

ANR7801I (Solaris) Subsystem process ID is process
identifier.
Explanation: The server process has the indicated
process identifier.
ANR7800I (Solaris) DSMSERV generated at time on

date.

ANR7802E

Shared memory segments for a server

running in the current directory already
exist. The -F parameter can be used to
overwrite.

Explanation: Shared memory segments are created for

each instance of the server based on the current
directory. This message indicates that the shared
memory segments already exist. A server is presently
running from the current directory or a server running
from the current directory ended abnormally.
System action: The server terminates.
User response: If the server running in the current

directory terminated abnormally, start dsmserv with the
-F parameter to force the existing shared memory
segments to be overwritten. If you want to run
multiple instances of the server, each instance must be
run from a separate directory with a separate
dsmserv.dsk file and have separate log, database, and
storage volumes.
ANR7800I (Windows) DSMSERV generated at time

on date.
ANR7801I
Subsystem (master) PID is process

identifier.
Explanation: The server kernel extension process has

ANR7801I
Subsystem (master) PID is process

identifier.
Explanation: The server kernel extension process has

466
ANR7803E
Attempt to overwrite a shared memory

segment, as directed with the -F
parameter, FAILED.
Explanation: The server has been started with the -F

parameter and unsuccessfully attempted to overwrite
existing shared memory segments. This error occurs
when the user that starts the server with -F parameter
ANR7804I ANR7805E (Linux)

is not the owner of the shared memory segments and
lacks the required authority.
System action: Server terminates.
ANR7805E
Volume volume name is in use by another

server.
User response: Resolve the authorization problem and

restart the server.
Explanation: The server has attempted to open a disk

volume but has discovered that the volume is in use by
another server.
ANR7804I
System action: The open operation fails for the

volume.
A server is already running from this

directory.
Explanation: The server has attempted to open the

adsmserv.lock file in the current directory but failed to
do so because an existing server already has the file
open.
User response: Examine the contents of the
adsmserv.lock file. The process ID for the server that is
running is recorded in this file. Two servers cannot be
started from the same directory. You may remove the
adsmserv.lock file and attempt to start the server ONLY
if the recorded process ID is NOT currently running
dsmserv. The 'ps -e' z/OS command can be used to
display processes that are currently running.
ANR7804I
An server is already running from this

directory.

open.
dsmserv. The 'ps -e' AIX command can be used to
display processes that are currently running.
ANR7804I (HP-UX) A server is already running from
this directory.
open.
dsmserv. The 'ps -e' command can be used to display
processes that are currently running.
User response: To prevent concurrent RAW volume

access by more than one server, files are created in the
/tmp directory to 'lock' these volumes. The names of
these temporary files are /tmp/
adsm.disk.dev.<volumename> where <volumename> is
the name of the RAW volume defined in the /dev
directory. Please note that the name for the logical
volume as defined in SMIT is represented in the /dev
directory with a leading 'r' character (for example, a
raw volume defined in SMIT as dsmstg1 will be
represented in the /dev directory as the file
/dev/rdsmstg1).
You may use the z/OS 'ps -e' command to determine if
other dsmserv processes are running. You may remove
the temporary lock files and attempt to re-start the
server ONLY if there are no other dsmserv processes
running
ANR7805E
Volume volume name is in use by another

server.

another server.
volume.
directory. Please note that the name for the logical
volume as defined in SMIT is represented in the /dev
directory with a leading 'r' character (for example, a
raw volume defined in SMIT as dsmstg1 will be
represented in the /dev directory as the file
/dev/rdsmstg1).
You may use the AIX 'ps -e' command to determine if
other dsmserv processes are running. You may remove
the temporary lock files and attempt to re-start the
server ONLY if there are no other dsmserv processes
running
ANR7805E (Linux) Volume volume name is in use by
another server.
another server.
467
ANR7805E (Solaris) ANR7806W (Linux)

volume.
directory. Please note that the name for a RAW logical
volume as defined in Solaris is in the /dev directory
with a leading 'r' character (for example, a raw volume
defined in Solaris on a regular SCSI drive as
dsk/c0t0d0s0 will be represented in the /dev directory
as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
volume, the server automatically locks/unlocks a
volume. Different linked file names pointing to the
same volume will cause this message since the server
locks the linked volume, not the link name itself.
You may use the Solaris 'ps -ef | grep dsmserv'
command to determine if other dsmserv processes are
running. You may remove the temporary lock files for
RAW volumes and attempt to re-start the server ONLY
if there are no other dsmserv processes are running.
ANR7805E (Solaris) Volume volume name is in use by
another server.
another server.
volume.
directory. Please note that the name for a RAW logical
volume as defined in Solaris is in the /dev directory
with a leading 'r' character (for example, a raw volume
defined in Solaris on a regular SCSI drive as
dsk/c0t0d0s0 will be represented in the /dev directory
as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
volume, the server automatically locks/unlocks a
volume. Different linked file names pointing to the
same volume will cause this message since the server
locks the linked volume, not the link name itself.
You may use the Solaris 'ps -ef | grep dsmserv'
command to determine if other dsmserv processes are
running. You may remove the temporary lock files for
RAW volumes and attempt to re-start the server ONLY
if there are no other dsmserv processes are running.
468
ANR7806W
Unable to open file file.
Explanation: The server was unable to open the

indicated file.
System action: The operation that was to use the
indicated file fails. A subsequent unnumbered message
had details from the system.
User response: Determine the reason for being unable
to open the file and re-attempt the operation. Common
reasons for being unable to open the file include
providing the wrong name, having insufficient
authorization to open the file and not being the files
owner.
ANR7806W
Unable to open file file.

indicated file.
owner.
ANR7806W (HP-UX) Unable to open file file.
indicated file.
owner.
ANR7806W (Linux) Unable to open file file.
indicated file.
owner.
ANR7806W (Solaris) ANR7808W

ANR7806W (Solaris) Unable to open file file.
indicated file.
owner.
ANR7807W (HP-UX) Unable to get information for

file file.
Explanation: The server was unable to get information
about the indicated file.
indicated file fails. A subsequent, unnumbered message
has details from the system.
to access the file and re-attempt the operation.
Common reasons for being unable to access the file
include providing the wrong name, having insufficient
owner.
ANR7806W (Windows) Unable to open file file.

indicated file.
owner. The file may be already opened by the server or
another program.
ANR7807W
Unable to get information for file file.

owner.
ANR7807W
Unable to get information for file file.

owner.
ANR7807W (Linux) Unable to get information for

file file.
authorization to open the file, not being the files
owner, or too many soft links to the file. If trying to
access a RAW partition, the server must be started with
superuser privileges.
ANR7807W (Solaris) Unable to get information for
file file.
authorization to open the file, not being the files
owner, or too many soft links to the file. If trying to
access a RAW partition, the server must be started with
superuser privileges.
ANR7808W
root user authority required for

non-default scheduling policy.
Explanation: The server was unable to use the

scheduling policy specified in the options file. The
server must be running with root authority to use any
scheduling policy other than the default.
469
ANR7808W ANR7811E (HP-UX)

System action: Operation continues but with the
default scheduling policy.
User response: Run the server with root authority or
dont specify a scheduling policy in the options file.
ANR7808W
root user authority required for

non-default scheduling policy.
Explanation: The server was unable to use the

scheduling policy specified in the options file. The
server must be running with root authority to use any
scheduling policy other than the default.
System action: Operation continues but with the
default scheduling policy.
User response: Run the server with root authority or
dont specify a scheduling policy in the options file.
number of applications is causing a memory shortage.

It may be necessary to decrease the maximum number
of client sessions by changing the MAXSESSIONS
option in the server options file.
ANR7810E (HP-UX) Error creating console input
thread.
Explanation: Unable to start console input thread.
System action: Server operation stops.
User response: See other issued messages.
ANR7810E (Linux) Error creating console input
thread.
ANR7809I
Using scheduling policy policy.
Explanation: All threads in the server will use the

specified scheduling policy.
System action: Operations continue
User response: None

ANR7810E (Solaris) Error creating console input
thread.
ANR7809I
Using scheduling policy policy.
Explanation: All threads in the server will use the

specified scheduling policy.

ANR7811E
System action: Operations continue.

User response: None
ANR7810E
Error creating console input thread.

ANR7810W
Unable to create a new child process.
Explanation: The server cannot create a new child

thread.
System action: Server processing continues. Other
error messages from the server component are
displayed.
User response: Ensure that sufficient paging space is
available for AIX. If the server has been started from a
non-root user ID, ensure that the AIX process limit per
user is sufficient for the server. The server requires
approximately 24 processes, in addition to one process
per client session, and one process for each background
operation. Each thread started by the server is an AIX
process. To change the number of processes per user,
use the SMIT menus for System Environment, and
choose Change / Show Characteristics of Operating
System. You may also use SMIT to determine if the
470
Insufficient memory for console

initialization.
Explanation: The server is unable to allocate enough

memory for console initialization.
User response: Ensure that there is sufficient paging
space. It may be necessary to reduce the maximum
number of client sessions by changing the
MAXSESSIONS option in the server options file.
ANR7811I
Using instance directory instance

directory.
Explanation: The server is operating out of the

indicated directory.
ANR7811E (HP-UX) Insufficient memory for console
initialization.
space for HP-UX. It may be necessary to reduce the
maximum number of client sessions by changing the
ANR7811E (Linux) ANR7813W (Linux)

ANR7811E (Linux) Insufficient memory for console
initialization.
ANR7811E (Solaris) Insufficient memory for console
initialization.

ANR7812E (Solaris) Insufficient memory to buffer
console input. The following input line
was discarded: discarded console input.
Explanation: An error occurs during an attempt to
allocate a buffer to hold the specified console input.
System action: The console input is discarded.
space for Sun Solaris. It may be necessary to reduce the
ANR7813W

space for Sun Solaris. It may be necessary to reduce the
ANR7812E
Insufficient memory to buffer console

input. The following input line was
discarded: discarded console input.

ANR7812E (HP-UX) Insufficient memory to buffer
The server mode-bit server is not

supported on a kernel mode-bit kernel.
Explanation: The 32-bit server is supported only when

running with the 32-bit kernel, and the 64-bit server is
supported only when running the 64-bit kernel.
User response: You must match the server mode with
the kernel mode by either switching the kernel mode or
installing the correct server fileset.
ANR7813W
The server mode-bit server is not

supported on a kernel mode-bit kernel.
Explanation: The 32-bit server is supported only when

running with the 32-bit kernel, and the 64-bit server is
supported only when running the 64-bit kernel.
User response: You must match the server mode with
the kernel mode by either switching the kernel mode or
installing the correct server fileset.
ANR7813W (Linux) Unable to create a new child
thread.

thread.

space for HP-UX. It may be necessary to reduce the

displayed.
ANR7812E (Linux) Insufficient memory to buffer

User response: Ensure that sufficient swap space is

available for Solaris. The amount of swap available can
be obtained by executing 'swap -l'. If the number of
free blocks is low, you can add swap files while the
system is running by executing 'mkfile' and then 'swap
-a'. See the Solaris man pages on 'mkfile' and 'swap' for
more details.
If the server has been started from a non-root user ID,
ensure that the process limit per user is sufficient to
471
ANR7813W (Solaris) ANR7820S (Linux)

accomodate the server. You can tune the 'maxusers=##'
parameter in the /etc/system file to increase the
number of number of users that can be on the system
at one time. This will also force the kernel to allocate
more memory/swap for user-processes.
A system reboot with the 'reconfigure' option is
required for the new user settings to take effect. It may
be necessary to decrease the maximum number of
client sessions by changing the MAXSESSIONS option
ANR7813W (Solaris) Unable to create a new child
thread.
thread.
displayed.
User response: Ensure that sufficient swap space is
available for Solaris. The amount of swap available can
be obtain by executing swap -l. If the number of free
blocks is low, you can add swap files while the system
is running by executing mkfile and then swap -a. See
the Solaris man pages on mkfile and swap for more
details. If the server has been started from a non-root
user ID, ensure that the Solaris process limit per user is
sufficient for the server. You can tune the maxusers=##
parameter in the /etc/system file to increase the
number of number of users that can be on the system
at one time. This will also force the kernel to allocate
more memory/swap for user-processes. A system
reboot with the reconfigure option is required for the
new user settings to take effect. It may be necessary to
decrease the maximum number of client sessions by
changing the MAXSESSIONS option in the server
options file.
ANR7814I (HP-UX) Using instance directory instance
directory.
ANR7814I (Linux) Using instance directory instance
directory.
ANR7814I (Solaris) Using instance directory instance

directory.
ANR7820E

input; the following input line was
Explanation: An error occured during an attempt to

allocate a buffer large enough to read console input.
available for z/OS. It may be necessary to decrease the
ANR7820E

input; the following input line was

allocate a buffer large enough to read console input.
available for AIX. You may also use SMIT to determine
if the number of applications is causing a memory
shortage. It may be necessary to decrease the maximum
ANR7820S (HP-UX) Server thread thread ID
terminated in response to program
abort.
Explanation: The thread has ended due to a program
abort.
System action: The server completes termination
processing.
User response: Note the associated messages and
ANR7820S (Linux) Thread thread ID terminated in
response to program abort.
abort.
processing.
User response: Note the associated messages and call
472
ANR7820S (Solaris) ANR7822I (Solaris)

ANR7820S (Solaris) Server thread thread ID
terminated in response to program
abort.
ANR7821W (Windows) Unable to create directory

when creating volume file name.

abort.
Explanation: The server was attempting to create a file

with the indicated name. A new directory was being
created as well, but its creation failed.

processing.
System action: Server processing continues. The file

creation request fails.
User response: Note the associated messages and call

User response: Specify a file name in an existing

directory or change the name request to specify a
different directory name.
ANR7820W (Windows) Insufficient Space Available

for file file name.
with the indicated name. There was insufficient space
for the file on the disk.
User response: Free additional space on the drive to
accomodate the file, specify a file name on a drive with
sufficient space, or change the space request to a value
consistent with the drive. Retry the operation.
ANR7822E

ANR7822E

ANR7821I (HP-UX) Server thread thread ID

terminated in response to external
signal.
Explanation: The thread has ended due to an external
signal.
processing.
ANR7822I (HP-UX) Server thread thread ID

terminated in response to server
shutdown.
Explanation: The thread has ended due to a server
shutdown.
processing.
ANR7821I (Linux) Thread thread ID terminated in

response to external signal.
signal.
processing.
ANR7822I (Linux) Thread thread ID terminated in

response to server shutdown.
shutdown.
processing.
ANR7821I (Solaris) Server thread thread ID

terminated in response to external
signal.
signal.
processing.
ANR7822I (Solaris) Server thread thread ID

terminated in response to server
shutdown.
shutdown.
processing.
473
ANR7822W (Windows) ANR7825E

ANR7822W (Windows) File Already exists when
creating volume file name.
ANR7824E

with the indicated name. The file already exists.
Explanation: The server attempted to load the Async

I/O support module, but the load failed. Refer to
accompanying error message for details on the load
failure.

User response: Specify a new file name. The server
will not use an existing file name when creating a file.
ANR7823E

initialization.
Explanation: Unable to allocate enough memory for

console initialization.
available for z/OS. It may be necessary to decrease the
ANR7823E

initialization.
Explanation: Unable to allocate enough memory for

console initialization.
Error loading Async I/O support

module.

without Async I/O support.
User response: Ensure that the correct support
module exists in the server bin directory and that the
aio subsystem has been configured on AIX, and that
AIX was rebooted after the configuration.
ANR7824S (HP-UX) Server operation terminated.
Explanation: An error occurs that causes server
operation to stop.
ANR7824S (Linux) Server operation terminated.
operation to stop.
ANR7824S (Solaris) Server operation terminated.
operation to stop.
ANR7823S (Linux) Internal error internal error

detected.
Explanation: An internal error is detected during

server initialization or operation.
ANR7824W (Windows) Unable to write volume file

name.

with the indicated name. The server was able to
partially write to the file before running out of space.

ANR7823W (Windows) Unable to create file file name.
with the indicated name. The system reported an error
in creating the file.
System action: The server continues processing. The
file creation request fails.
User response: Specify a new file name.

file creation request fails. The file is still present on the
system.
User response: Specify a new file name where there is
sufficient space.
ANR7825E
The SAN discovery module module name

is not installed correctly.
Explanation: The server attempted to load the SAN

discovery module, but the permissions or ownership of
the file are incorrect.
System action: The server operation continues, but
without the SAN discovery function.
474
ANR7825E (Linux) ANR7831E (Linux)

User response: Ensure that the SAN discovery module
can be started, has the setuid bit turned on, and is
owned by root. The SAN discovery module is called
dsmqsan and must be located in the server or storage
agent executable directory.
ANR7825E (Linux) Server unable to allocate a shared
memory segment of size Client requested
shared memory size.
Explanation: A shared memory client has requested a
shared memory segment size that Solaris is unable to
fulfill.
System action: Client is not allowed to logon
User response: See the shared memory tuning guide
for Solaris (a Sun document). You may need to increase
the number/size of shared memory segments and/or
message queues.
ANR7825E (Solaris) Server unable to allocate a
shared memory segment of size Client
requested shared memory size.
Explanation: A shared memory client has requested a
shared memory segment size that Solaris is unable to
fulfill.
System action: Client is not allowed to logon
User response: See the shared memory tuning guide
for Solaris (a Sun document). You may need to increase
the number/size of shared memory segments and/or
message queues.
ANR7826W (Windows) Creation of Volume file name

failed. Process was cancelled.
with the indicated name. The attempt was cancelled by
a cancel process command.
User response: The DEFINE command may be
re-entered.
ANR7827E
The SAN discovery module (pid process

ID) has terminated with exit code exit
code.
Explanation: The SAN discovery module (dsmqsan)

has terminated abnormally. The exit code indicates the
reason for the termination. Exit code 11 means the
program was killed by another process. Exit codes 12
and 13 mean the program cancelled. Exit code 14
means the program was stopped.
current SAN discovery function failed.
ANR7830E (Linux) Invalid RAW Partition Name: A
valid raw partition name is in the form
of /dev/.../rdsk/.../* , where ... means 0 or
more directories.
Explanation: Use the proper format for specifying a
Raw partition. The ... means zero or more directories.
ANR7825W (Windows) Unable to create volume file

name. Return code= return code.
System action: Inform the user to use the right RAW

partition specification.

with the indicated name. The attempt failed with the
indicated return code. The return code is an internal
code from the server.
User response: Have user reenter the RAW partition

with the proper partition name.

User response: Specify a new file name. The return
code may also be provided to your service
representative for interpretation.
ANR7826E
An error occurred communicating with

the SAN discovery module.
Explanation: While communicating with the SAN

discovery module (dsmqsan), an error occurred and the
connection is lost.
current SAN discovery function is terminated.
ANR7830E (Solaris) Invalid RAW Partition Name: A

valid raw partition name is in the form
of /dev/.../rdsk/.../* , where ... means 0 or
more directories.
Explanation: Use the proper format for specifying a
Raw partition. The ... means zero or more directories.
System action: Inform the user to use the right RAW
partition specification.
User response: Have user reenter the RAW partition
with the proper partition name.
ANR7831E (Linux) raw partition name has an existing
filesystem.
Explanation: The RAW partition specified has an
existing Solaris file system on it. Writing to this
Partition may/and most likely will destroy this
filesystem.
475
ANR7831E (Solaris) ANR7833E (Linux)

System action: Warn the user that an existing
filesystem for the raw partition specified may be
destroyed if written to.
User response: Determine if user still wants the valid
filesystem data. If not, user needs to destroy the
filesystem by either formatting the partition, create a
program to destroy the filesystem header information
so that the server will not be able to detect the
filesystem header information, or rearrange the starting
and ending blocks of a partition by using the Solaris
format() command. The user can read the format()
function in the Sun manuals for further details on
filesystems.
ANR7831E (Solaris) raw partition name has an existing
filesystem.
existing Solaris file system on it. Writing to this
partition will most likely destroy this filesystem.
System action: Warn the user that an existing
filesystem for the raw partition specified may be
destroyed if written to.
User response: Determine if user still wants the valid
filesystem data. If not, user needs to destroy the
filesystem by either formatting the partition, create a
program to destroy the filesystem header information
so that the server will not be able to detect the
filesystem header information, or rearrange the starting
and ending blocks of a partition by using the Solaris
format() command. The user can read the format()
function in the Sun manuals for further details on
filesystems.
ANR7832I
The thread process ID terminated with

exit code program exit code.
Explanation: The process has ended with the

indicated exit code. This error is due to the problem
caused and indicated by a preceding message.
processing.
ANR7832I
The thread process ID terminated with

exit code program exit code.
ANR7832E (Linux) raw partition name corresponds to a

protected filesystem, such as / or /usr.
existing file system on it. This filesystem is the / or
/usr partition. If the SERVER writes to it, it will most
likely crash the whole operating system.
System action: Disallow access to this raw partition.
User response: Have user specify another RAW
partition that is not the / or /usr. It may be possible
that this is not the actual / or /usr partition of the boot
disk. Check, using the Solaris format() command, if
your partition name tag is labeled incorrectly as / or
/usr.
ANR7832E (Solaris) raw partition name corresponds to
a protected filesystem, such as / or /usr.
existing file system on it. This filesystem is the / or
/usr partition. If the SERVER writes to it, it will most
likely crash the whole operating system.
User response: Have user specify another RAW
partition that is not the / or /usr. It may be possible
that this is not the actual / or /usr partition of the boot
disk. Check, using the Solaris format() command, if
your partition name tag is labeled incorrectly as / or
/usr.
ANR7833S
The process thread ID terminated in


abort.
processing.
ANR7833S
The process thread ID terminated in


abort.
processing.
Explanation: The process has ended with the

indicated exit code. This error is due to the problem
caused and indicated by a preceding message.

processing.
ANR7833E (Linux) symbolic links has too many

symbolic links - the maximum
allowable is 10.
Explanation: The file specified has too many symbolic

links. The server will follow at most 10 links before
ending this symbolic link name resolution.
System action: Disallow access to this file.
476
ANR7833E (Solaris) ANR7835E (Solaris)

User response: Have the user specify the actual file,
where the file is not a symbolic link. Using ls -l, one
can see if the file is a symbolic link.
User response: Have the system administrator change

the starting cylinder of this partition to a number
greater than 0.
ANR7833E (Solaris) symbolic links has too many

symbolic links - the server only
supports a maximum of 10.
ANR7834I (Windows) The server thread thread ID (tid

Windows NT thread ID) terminated in

Explanation: The thread has terminated due to an

external signal.
System action: Disallow access to this file

ANR7834I
The thread thread ID terminated in


signal.
processing.
ANR7834I
The thread thread ID terminated in


signal.
processing.
ANR7834E (Linux) Specified raw partition name raw
partition cannot contain the 0th disk
cylinder.
Explanation: The raw partition specified has the 0th
disk cylinder. The server should not be allowed to
write into the 0th cylinder. If allowed, the disk label
would be corrupted.
the starting cylinder of this partition to a number
greater than 0.
ANR7834E (Solaris) Specified raw partition name raw
partition cannot contain the 0th disk
cylinder.
Explanation: The raw partition specified has the 0th
disk cylinder. The server should not be allowed to
write into the 0th cylinder. It allowed, the disk label
would be corrupted.
System action: Disallow access to this raw partition

processing.
ANR7835I
The server thread thread ID terminated

in response to server shutdown.

shutdown.
processing.
ANR7835I
The server thread thread ID terminated

in response to server shutdown.

shutdown.
processing.
ANR7835E (Linux) Specified raw partition name raw
partition is too big for this operating
system to handle.
Explanation: The raw partition specified has greater
than 2GB and the operating system is running below
Solaris 2.6. Operating system below Solaris 2.6 cannot
handle files natively more than 2GB. For operating
system that is at Solaris 2.6 or above, the limit is 1TB.
the RAW partition size to be less than 2GB (4194303
512-byte disk blocks) for Solaris 2.5.1 or below, less
than 1TB (2147483647 512-byte disk blocks) for Solaris
2.6 and above.
ANR7835E (Solaris) Specified raw partition name raw
partition is too big for this operating
system to handle.
Explanation: The raw partition specified has greater
than 2GB and the operating system is running below
Solaris 2.6. Operating system below Solaris 2.6 cannot
handle files natively more than 2GB. For operating
477
ANR7835I (Windows) ANR7841S

system that is at Solaris 2.6 or above, the limit is 1TB.
System action: Disallow access to this raw partition
the RAW partition size to be less than 2GB (4194303
512-byte disk blocks) for Solaris 2.5.1 or below, less
than 1TB (2147483647 512-byte disk blocks) for Solaris
2.6 and above.
ANR7835I (Windows) The server thread thread ID (tid
Windows NT thread ID) terminated in
response to server shutdown.
Explanation: The thread has terminated due to a
server shutdown.
processing.
ANR7837S (Windows) Internal error The internal error

that was detected. detected.
Explanation: An internal error was detected during
System action: Server operation will halt.
The user needs to extend the log file with dsmserv
extend log logname size when he gets ANR7837S,
LOGSEG871 errors.
ANR7838S
Server operation terminated.

operation to stop.
ANR7836S
ANR7838S
Server initialization terminated.
Server operation terminated.

initialization to end.

operation to stop.
ANR7836S
ANR7839E
Server initialization terminated.

initialization to end.
ANR7837S
Internal error internal error detected.

symbolic links has too many symbolic

links - the maximum allowable is 10.

System action: Disallow access to this file.
ANR7841S
Insufficient kernel memory available.

LOGSEG871 errors.
Explanation: An error occurs due to insufficient kernel

memory.
ANR7837S
Internal error internal error detected.

LOGSEG871 errors.
478
ANR7841S
Insufficient kernel memory available.
Explanation: An error occurs due to insufficient kernel

memory.
ANR7842S ANR7849I
ANR7842S
Monitor kernel extension not initialized.
Explanation: The monitor kernel extension is not

initialized.
ANR7842S
Monitor kernel extension not initialized.
Explanation: The monitor kernel extension is not

initialized.
ANR7843W
Unable to determine real memory size.
Explanation: The server checks the amount of real

memory in the system to optimize use of storage in the
database buffer pool. The server uses Object Data
Manager (ODM) to determine how much real memory
is installed on the system. The routines used to call
ODM failed or were unable to return the real memory
size.
System action: Server operation continues. The server
allows the data base buffer pool size to grow withoug
taking into account real memory.
User response: The server may need to run as a root

user to obtain this information.
ANR7843W (Linux) Unable to determine real
memory size.
is installed on the system. The routine s used to call
size.
ANR7843W (Solaris) Unable to determine real
memory size.
database buffer pool. The routines used to obtain this
information returned a failing return code or were
unable to return the real memory size.


ANR7843W

Unable to determine real memory size.

is installed on the system. The routines used to call
size.
ANR7843W (HP-UX) Unable to determine real
memory size.
ANR7843W (Windows) Unable to determine real

memory size.
ANR7849I
Server operation terminated - kernel

extension has been reset.
Explanation: The kernel extension has been

reinitialized by the server in response to a previous
condition for which a message has been issued.
479
ANR7849I ANR7859W
ANR7849I
Server operation terminated - kernel

extension has been reset.
Explanation: The kernel extension has been

reinitialized by the server in response to a previous
condition for which a message has been issued.
ANR7853W (Windows) Could not obtain the current

process affinity mask. Reason: NT return
code..
Explanation: A problem was encounterd while
obtaining the current process affinity.
ANR7850I
The process process ID has terminated on

signal signal number (signal name).
Explanation: The specified process has ended due to

the specified signal.
ANR7854W (Windows) The process affinity mask

(0xAffinity mask.) specified in
dsmserv.opt is out of range.
Explanation: The affinity mask value was out of
range.
ANR7850I
The process process ID has terminated on

signal signal number (signal name).
Explanation: The specified process has ended due to

the specified signal.
ANR7855W (Windows) Could not set new process

affinity mask. Reason: NT return code.
Explanation: A problem was encounterd in setting a
new process affinity mask.
ANR7851S
Error resetting handler for signal signal

number (signal name).
Explanation: An error occurs resetting the specified

signal handler.
ANR7856W (Windows) The affinity mask (0xNT

return code.) was set to a value other than
what was requested
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).
Explanation: An error occurs resetting the specified

signal handler.
ANR7859W

read from standard input.

ANR7852I (Windows) The current process affinity
mask is: 0xThe process affinity mask..
Explanation: The server is running on the processors
indicated by the mask.
Error reading from standard input.
System action: The console input thread is terminated.

User response: This is normal if the server is running
as part of the installation, in a cron job, or is started in
the background. This can occur if the server is started
in a telnet or ssh session and that session is killed
effectively creating a background process. If this is
unintended, stop the server and restart in the
foreground.

ANR7859W
Error reading from standard input.

480
ANR7859W (HP-UX) ANR7860W (Solaris)

foreground.
ANR7859W (HP-UX) Error reading from standard
input.
foreground.
ANR7859W (Linux) Error reading from standard
input.
foreground.
ANR7859W (Solaris) Error reading from standard
input.
foreground.
ANR7860W
Insufficient Space Available for file file

name.

for the file in the filesystem.

ANR7860W
Insufficient Space Available for file file

name.

ANR7860W (HP-UX) Insufficient Space Available for
file file name.
ANR7860W (Linux) Insufficient Space Available for
file file name.
ANR7860W (Solaris) Insufficient Space Available for
file file name.
481
ANR7861W ANR7862W (Linux)

ANR7861W
Unable to create directory when creating

volume file name.
ANR7861W (Solaris) Unable to create directory when





directory or or change the name request to specify a

ANR7861W
Unable to create directory when creating

volume file name.

ANR7862W
File Already exists when creating

volume file name.

ANR7862W
File Already exists when creating

volume file name.

ANR7861W (HP-UX) Unable to create directory when





ANR7862W (HP-UX) File Already exists when



ANR7861W (Linux) Unable to create directory when


ANR7862W (Linux) File Already exists when creating
volume file name.
482
ANR7862W (Solaris) ANR7864W (Solaris)

ANR7862W (Solaris) File Already exists when
ANR7863W
Unable to write volume file name.

system.
sufficient space.
Unable to create file file name.

ANR7863W
ANR7864W

ANR7863W (HP-UX) Unable to create file file name.
ANR7863W (Linux) Unable to create file file name.
ANR7864W
Unable to write volume file name.

system.
sufficient space.
ANR7864W (HP-UX) Unable to write volume file
name.
system.
sufficient space.
ANR7864W (Linux) Unable to write volume file name.
system.
sufficient space.
ANR7864W (Solaris) Unable to write volume file

name.
ANR7863W (Solaris) Unable to create file file name.



system.

483
ANR7865W ANR7866W (Linux)

sufficient space.
ANR7865W
Unable to create volume file name.

Return code=return code.

indicated return code. The return code is an the server
internal code.
ANR7865W
Unable to create volume file name.

Return code=return code.

indicated return code. The return code is an the server
internal code.
ANR7865W (HP-UX) Unable to create volume file
name. Return code=return code.
indicated return code. The return code is a server
internal code.
ANR7865W (Solaris) Unable to create volume file

indicated return code. The return code is a server
internal code.
ANR7866W
Creation of Volume file name failed.

Process was cancelled.

re-entered.
ANR7866W
Creation of Volume file name failed.

Process was cancelled.

re-entered.

ANR7866W (HP-UX) Creation of Volume file name



ANR7865W (Linux) Unable to create volume file

indicated return code. The return code is an internal
code from the server.
484

re-entered.
ANR7866W (Linux) Creation of Volume file name
ANR7866W (Solaris) ANR7870W

re-entered.
ANR7866W (Solaris) Creation of Volume file name
re-entered.
ANR7867I
file name is not a multiple of disk block

size block size. File size is file size, but
usable space is rounded down to usable
file size.
Explanation: The server was attempting to open a

random access file with the indicated name. The usable
space was rounded down to the indicated value so that
the amount of space is an even multiple of the disk
block size. This facilitates improved performance in
reading and writing the file.
System action: The server continues processing. Some
space in the file will go unused.
User response: No action is required. To use all space
in the file, server utilities can be used to offload
existing data to other volumes. The volume can then be
deleted and re-created using a multiple of the disks
block size.
ANR7867I (Linux) file name is not a multiple of disk
block size block size. File size is file size,
but usable space is rounded down to
usable file size.





block size.

block size.
ANR7867I
file name is not a multiple of disk block

size block size. File size is file size, but
usable space is rounded down to usable
file size.
ANR7867I (Solaris) file name is not a multiple of disk

usable file size.





block size.

block size.
ANR7867I (HP-UX) file name is not a multiple of disk

usable file size.
ANR7870W
Unable to initialize odm query. Error

message from odm is odm message.
Explanation: The server uses the AIX Object Data

Manager (ODM) to check information about AIX. For
example, the server uses ODM to detemine how much
485
ANR7871W ANR8191W
real memory is installed on the system. The routine
used to initialize an ODM query failed. ODM returned
an error message as indicated.
makes assumptions concerning information it could not
obtain.
ANR7871W
Unable to complete odm query. Error

message from odm is odm message.
Explanation: The server uses the AIX Object Data

Manager (ODM) to check information about AIX. For
example, the server uses ODM to detemine how much
real memory is installed on the system. The routine
used to perform and ODM query failed. ODM returned
an error message as indicated.
makes assumptions concerning information it could not
obtain.
ANR8190I (Linux) HTTP driver ready for connection

with clients on port port number.
Explanation: The server is now able to accept sessions
with clients that use the HTTP protocol on the
indicated port number.
ANR8190I (Solaris) HTTP driver ready for
connection with clients on port port
number.
ANR8191W

ANR8190I
HTTP driver ready for connection with

clients on port port number.

ANR8190I
HTTP driver ready for connection with


HTTP driver unable to initialize due to

error in using port port, reason code
reason code.
Explanation: While initializing HTTP communications,

the server has failed to connect to a master TCP/IP
socket on which to listen for clients. The reason code is
the return code from the TCP/IP bind API.
server cannot accept sessions from administrative
clients using HTTP protocol.
User response: Ensure that no other application is
using the port number specified in the server options
file with the HTTPPORT 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 HTTP
communications. This may be done by issuing the
TCP/IP netstat -s command. If the server is brought
down and then started immediately, you may be within
the TCP/IP one minute timeout period for port
reusage. Bring down the server, wait one minute, and
then restart the server. If that does not work, it may be
necessary to restart Windows NT.
ANR8190I (HP-UX) HTTP driver ready for

number.
ANR8191W



HTTP driver unable to initialize due to

reason code.

486
ANR8191W (HP-UX) ANR8192I (Solaris)

necessary to restart Windows NT.
ANR8191W (HP-UX) HTTP driver unable to
initialize due to error in using Port port,
reason code reason code.
reusage. Bring down the sever, wait one minute, and
necessary to restart HP-UX.
ANR8191W (Linux) HTTP driver unable to initialize
due to error in using port port, reason
code reason code.
file with the TCPPORT or TCPADMINPORT options. If
TCP/IP is also in use for client sessions, ensure that the
same port number is not specified for both TCP/IP and
HTTP communications. This may be done by issuing
the TCP/IP netstat -s command. If the server is brought
then restart the server.
ANR8191W (Solaris) HTTP driver unable to

initialize due to error in BINDing to
Port port, reason code reason code.
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 HTTP communications.
This may be done by issuing the TCP/IP netstat -s
command. If the server is brought down and then
started immediately, you may be within the TCP/IP
one minute timeout period for port reusage. Bring
down the sever, wait one minute, and then restart the
server.
ANR8192I (HP-UX) HTTPS driver ready for
number.
with clients that use the HTTPS protocol on the
ANR8192I (Linux) HTTPS driver ready for
number.
ANR8192I (Solaris) HTTPS driver ready for
number.
487
ANR8193W (HP-UX) ANR8195I (Windows)

ANR8193W (HP-UX) HTTPS driver unable to
Explanation: While initializing HTTPS
communications, the server has failed to connect to a
master TCP/IP socket on which to listen for clients.
The reason code is the return code from the TCP/IP
bind API.
clients using HTTPS protocol.
file with the HTTPSPORT option. If TCP/IP is also in
number is not specified for both TCP/IP and HTTPS
necessary to restart HP-UX.
ANR8193W (Linux) HTTPS driver unable to
initialize due to error in using port port,
bind API.
file with the HTTPSPORT option. If TCP/IP is also in
number is not specified for both TCP/IP and HTTPS
necessary to restart Solaris
ANR8193W (Solaris) HTTPS driver unable to
bind API.
488

specified for both TCP/IP and HTTPS communications.
server. If that does not work, it may be necessary to
restart Solaris
ANR8194W (HP-UX) HTTPS driver unable to
initialize due to error in secure data
initialization, reason code reason code.
communications, the server has failed initialize of the
secure data certificate information.
User response: Ensure the keyring file name and
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.
ANR8195I
The SSL TCP/IP Version 4 driver is

ready for connection with clients on
port port number.
Explanation: The server can now accept sessions with

clients using the SSL TCP/IP protocol on the indicated
port number.
ANR8195I (Windows) The SSL TCP/IP Version 4
driver is ready for connection with
port number.
ANR8196I ANR8200I (Solaris)

ANR8196I
The SSL TCP/IP administrative driver is

port port number.

administrative clients using the SSL TCP/IP protocol
on the indicated port number.

ANR8200I
TCP/IP driver ready for connection with


with clients that use the TCP/IP protocol on the
ANR8196I (Windows) The SSL TCP/IP

administrative driver is ready for
number.
ANR8200I
TCP/IP Version 4 driver ready for

number.


clients using the TCP/IP Version 4 protocol on the
ANR8198E
ANR8200I (HP-UX) TCP/IP Version 4 driver ready

for connection with clients on port port
number.
The SSL environment has not been

established. The GSK module gsk module
return code is gsk return code.
Explanation: Initialization of the SSL environment has

failed. Connections to SSL ports are not possible.
User response: Stop and restart the server.

with clients using the TCP/IP Version 4 protocol on the
ANR8198E (Windows) The SSL environment has not

been established. The GSK module gsk
module return code is gsk return code.
User response: Stop and restart the server.
ANR8199I
The SSL TCP/IP driver could not be

initialized on port port number.
Explanation: A problem with the SSL environment

prevents Tivoli Storage Manager from establishing the
SSL protocol on the indicated port number.
ANR8200I (Linux) TCP/IP Version 4 driver ready for

number.
ANR8200I (Solaris) TCP/IP Version 4 driver ready
number.
ANR8199I (Windows) The SSL TCP/IP driver could

not be initialized on port port number.
Explanation: A problem with the SSL environment

prevents Tivoli Storage Manager from establishing the
SSL protocol on the indicated port number.
489
ANR8200I (Windows) ANR8202W

ANR8200I (Windows) TCP/IP Version 4 driver ready
number.
ANR8201W
Unable to initialize TCP/IP driver due

to insufficient memory.
Explanation: Because the operating system rejects a

memory allocation request, the server cannot start
communications through TCP/IP.
server cannot accept sessions from clients using the
TCP/IP protocol.
available for a/OS. Decrease the maximum number of
ANR8201W
Unable to initialize TCP/IP driver insufficient memory.

TCP/IP protocol.
ANR8201E (HP-UX) Unable to initialize TCP/IP
driver - socket creation failed; error error
code.
Explanation: The server is unable to initialize the
TCP/IP driver due to a socket creation error.
TCP/IP support is inoperative.
User response: Ensure that TCP/IP is operational on
your system by using the ping command with your
TCP/IP address as a target. If TCP/IP is not active on
your system, you must activate it; then halt and restart
the server.
ANR8201E (Linux) Unable to initialize TCP/IP driver

- socket creation failed; error error code.
the server.
ANR8201E (Solaris) Unable to initialize TCP/IP
driver - socket creation failed; error error
code.
the server.
ANR8201W (Windows) Unable to initialize TCP/IP
driver - insufficient memory.
Explanation: The server is unable to communicate by
way of TCP/IP. A memory allocation request has been
rejected by the operating system.
TCP/IP protocol.
User response: Ensure that there is sufficient space for
the Windows paging file. Click on the system icon in
the Windows control panel and then click on the
virtual memory button. Refer to the online help for
instructions on how to increase the amount of virtual
memory.
ANR8202W
Unable to initialize TCP/IP driver - error

creating acceptor socket. Reason code
reason code.
Explanation: Because TCP/IP rejects a request for a

socket on which to listen, the server cannot start
TCP/IP protocol.
TCP/IP address as a target. If TCP/IP is not started,
490
ANR8202W ANR8203W
use the HALT command from a server prompt to stop
the server and restart it.
ANR8202W
Unable to initialize TCP/IP driver - error

creating acceptor socket. Reason code
reason code.
Explanation: Because TCP/IP rejects a request for a

TCP/IP protocol.
use the HALT command from a server prompt to stop
the server and restart it.
driver - socket bind operation for port
TCP port number failed; error error code.
TCP/IP driver due to a socket binding error.
the server. This message may also result from more
than one server running on the same machine with the
same TCP/IP port number. Make sure that the
dsmserv.opt file TCPPort option is different for each
server.
ANR8202E (Linux) TCP/IP driver unable to initialize
due to error in using port TCP port
number; error error code.
server. Make sure TCPPORT and HTTPORT and
TCPADMINPORT do not specify or default to the same
values.

driver - socket bind operation for port
TCP port number failed; error error code.
server.
ANR8202W (Windows) Unable to initialize TCP/IP
driver - error creating acceptor socket.
Reason code reason code.
Explanation: The server is unable to communicate by
way of TCP/IP. TCP/IP has rejected a request for a
socket on which the server listens.
TCP/IP protocol.
issue the HALT command to stop the server, and then
restart the server.
ANR8203W
Unable to establish TCP connection accept error.
Explanation: The server cannot accept a client session

due to a failure in TCP/IP.
TCP/IP protocol.
use the HALT command from a server prompt to
terminate the server and restart it.
ANR8203W
Unable to establish TCP connection accept error.

due to a failure in TCP/IP.
TCP/IP protocol.
491
ANR8203E (HP-UX) ANR8204E (Linux)

use the HALT command from a server prompt to
terminate the server and restart it.

issue the HALT command to stop the server, and then
restart the server.
ANR8204W

driver - listen operation failed; error
error code.
TCP/IP driver due to a socket listen error.
the server.
- listen operation failed; error error code.
the server.
driver - listen operation failed; error
error code.
Unable to establish TCP connection due

to insufficient memory.

due to a memory allocation request failure.
session request for this session fails.
available for z/OS. You can also decrease the maximum
number of sessions that the server can accept with the
ANR8204W
Unable to establish TCP connection insufficient memory.

shortage. You may also decrease the maximum number
of sessions that the server can accept with the
driver - thread creation failed.
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.

- thread creation failed.
ANR8203W (Windows) Unable to establish TCP

connection - accept error.


due to failure in TCP/IP.


TCP/IP protocol.
492

ANR8204E (Solaris) ANR8206W

driver - thread creation failed.
connection - insufficient memory.
Explanation: The server is unable to accept a client
session due to a memory allocation request failure.
User response: Ensure that there is sufficient space for
the Windows paging file. Click on the system icon in
the Windows control panel and then click on the
memory. You may also wish to cut down on the
maximum number of sessions that the server can
accept with the MAXSESSIONS option in the server
options file.
ANR8205W
Unable to establish TCP connection server HALT in progress.

due to server HALT processing that is in progress.
ANR8205W
Unable to establish TCP connection server HALT in progress.

the server.
ANR8205E (Linux) Terminating TCP/IP driver socket accept operation failed; error error
code.
TCP/IP driver due to a socket accept error.
the server.
ANR8205E (Solaris) Terminating TCP/IP driver socket accept operation failed; error error
code.
the server.
connection - server HALT in progress.
Explanation: The server is unable to accept a client
session due to server HALT processing that is in
progress.


ANR8206W
Explanation: The server detects that the indicated

session on the specified TCP/IP socket is closed outside
of the server.
ANR8205E (HP-UX) Terminating TCP/IP driver accept operation failed; error error code.
Socket socket (session session number)

closed abruptly.

session is ended.

493

ANR8206W
Socket socket (session session number)

closed abruptly.
Explanation: The server detects that the indicated

session on the specified TCP/IP socket is closed outside
of the server.
session is ended.
ANR8206I (Windows) TCP/IP Version 4

administrative driver ready for
number.
administrative clients using the TCP/IP Version 4
protocol on the indicated port number.
ANR8206E (HP-UX) Unable to establish TCP/IP

session - invalid host address IP host
address (port port number).
Explanation: The server is unable to establish a
session because the designated address or port number
is not valid.
User response: Ensure that the specified host name is
valid and is accessible over the network. If the
TCPCLIENTPort option is specified for the remote
system, ensure it does not conflict with another
application.
ANR8206E (Linux) Unable to establish TCP/IP
is not valid.
application.
ANR8206E (Solaris) Unable to establish TCP/IP
is not valid.
application.
494
ANR8207W
TCP/IP driver unable to initialize due to

socket initialization error. Reason code
reason code.
Explanation: While initializing TCP/IP

communications, the server fails to set up an interface
with TCP/IP.
TCP/IP protocol.
User response: Ensure that TCP/IP has been started
and is active on your system. You can issue the TCP/IP
ping command to your own address to verify that
TCP/IP is both started and active.
ANR8207W

reason code.

communications, the server fails to set up an interface
with TCP/IP.
TCP/IP protocol.
and is active on your system. You may issue the
TCP/IP ping command to your own address to verify
that TCP/IP is both started and active.
session with IP host address due to
memory shortage.
session because of a memory shortage condition.
User response: Ensure that your system has sufficient
paging space to support the current level of system
activities.
ANR8207E (Linux) ANR8208E (Solaris)

memory shortage.
were active, it may be necessary to terminate the client

sessions on the client systems before the port can be
freed.
ANR8208W

reason code.

activities.

communications, the server fails to connect to a master

memory shortage.

TCP/IP protocol.


file with the HTTPPORT option by issuing the TCP/IP
netstat command. If HTTP is also in use for client
sessions, ensure that the same port number is not
If the server was brought down and client sessions
were active, it may be necessary to terminate the client
freed.

activities.
ANR8207W (Windows) TCP/IP driver unable to
initialize due to socket initialization
error. Reason code reason code.
communications, the server has failed to set up an
interface with TCP/IP for Windows.
TCP/IP protocol.

session with IP host address - socket
creation failed; error error code.
session because of a socket creation error.
User response: Ensure that TCP/IP is properly

installed on your system. Ensure that TCP/IP has been
started on your system. Issue the TCP/IP ping
command to your own address to verify that TCP/IP is
both installed and active.

the server.
ANR8208W


reason code.

communications, the server fails to connect to a master
TCP/IP protocol.
file with the HTTPPORT option by issuing the TCP/IP
netstat command. If HTTP is also in use for client
If the server was brought down and client sessions

the server.
495
ANR8208W (Windows) ANR8209W (Windows)

the server.
master socket on which to listen for clients. The reason
code is the return code from the TCP/IP bind API.
TCP/IP protocol.
file with the TCPPORT option. If HTTP is also in use
for client sessions, ensure that the same port number is
not specified for both TCP/IP and HTTP
necessary to restart Windows.
ANR8209W

error in LISTENing on the specified
Port, reason code reason code.
Explanation: While attempting to listen for session

requests from clients using TCP/IP, TCP/IP returns an
error. The reason code is the return code from the
TCP/IP listen API.
server cannot accept additional sessions from clients
using the TCP/IP protocol.
User response: Ensure that TCP/IP is running
properly by issuing the TCP/IP netstat -s and ping
commands to other nodes on your network. It may be
possible to bring the server down and restart it to
allow additional client sessions to start.
ANR8209W

error in LISTENing on the specified
Port, reason code reason code.

TCP/IP listen API.
496

session with IP host address - connection
refused.
session because the remote system refused the
connection request.
User response: Ensure that the specified remote
system is operational and is properly configured to run
TCP/IP. Ensure that the client options file specifies the
correct TCPServeraddress and TCPPort of the server
you are attempting to contact.
refused.
connection request.
refused.
connection request.
initialize due to error in LISTENing on
the specified Port, reason code reason
code.
ANR8210W ANR8210W (Windows)

TCP/IP listen API.
properly. This may be done by issuing the TCP/IP
netstat -s and ping commands to other nodes on your
network. It may be possible to correct this condition by
restarting the server.
ANR8210W
TCP/IP driver is terminating due to

error in accepting a new session, reason
code reason code.
Explanation: While attempting to accept a session

request from a client using TCP/IP, TCP/IP returns an
TCP/IP accept API.
network. It may be possible to bring the server down
and restart it to allow additional client sessions to start.
ANR8210W

error in accepting a new session, reason
code reason code.
v The specified remote system is operational and is

properly configured to run TCP/IP.
v The client options file specifies the correct
TCPServeraddress and TCPPort of the server you are
attempting to contact.
v Necessary gateways and routers are functioning
properly.
request timed out.
session because the remote system did not respond to
the connection request.
User response: Ensure the following:
properly.
request timed out.

TCP/IP accept API.




properly.

request timed out.

ANR8210W (Windows) TCP/IP driver is terminating

due to error in accepting a new session,
TCP/IP accept API.
497
ANR8211W ANR8212W
ANR8211W

error in creating a new thread.
Explanation: The server cannot initialize because it

cannot create a new thread of execution.
TCP/IP communications is inoperative.
User response: The most likely cause is a lack of
memory. Ensure that sufficient paging space is available
for z/OS. You can also decrease the maximum number
ANR8211W

error in creating a new thread.
Explanation: The server cannot initialize due to the

inability to create a new thread of execution.
for AIX. You may also use SMIT to determine if the
You may also decrease the maximum number of
sessions that the server can accept with the
session with IP host address system/network unreachable.
session because the remote system or network is
unreachable.
TCP/IP. Also, ensure that necessary gateways and
routers are functioning properly.

unreachable.
ANR8211W (Windows) TCP/IP driver is terminating
due to error in creating a new thread.
Explanation: The server cannot initialize due its
memory. Ensure that there is sufficient space for the
Windows paging file. Click on the system icon in the
Windows NT control panel and then click on the
options file.
ANR8212W
Explanation: The server attempts to obtain a TCP/IP

address for the indicated node name. The attempt is
unsuccessful.
System action: The attempt to communicate with the
indicated node fails. Server operation continues.
User response: Ensure that the node name is properly
specified and that it is accessible over the network. Use
the TCP/IP ping command for this purpose.
ANR8212W

unreachable.
498
Unable to resolve address for node name.
Unable to resolve address for node name.

unsuccessful.
ANR8212E (HP-UX) ANR8213W (Windows)

session with IP host address - connect
failed; error error code.
session because of a connection error.
TCP/IP.
ANR8213W
Session open with node name timed out.
Explanation: The server attempts to contact the

indicated node name. The attempt is unsuccessful.
indicated node fails.
ANR8213E (HP-UX) Session Session identifier aborted
due to send error; error error code.
Explanation: The session between the server and the
specified client system experienced a disruptive error
sending data.
System action: The session with the remote system is

ended.

TCP/IP.

TCP/IP.

ANR8213E (Linux) Socket Socket identifier aborted due

to send error; error error code.

TCP/IP.
ANR8212W (Windows) Unable to resolve address for
node name.
unsuccessful.
ANR8213W

specified client system experienced a fatal error sending
data.
ended.
TCP/IP.
ANR8213E (Solaris) Socket Socket identifier aborted
due to send error; error error code.
specified client system experienced a fatal error sending
data.
ended.
TCP/IP.
Session open with node name timed out.

ANR8213W (Windows) Session open with node name

timed out.
499
ANR8214E ANR8215W
ANR8214E
Session open with IP host address failed

due to connection refusal.

connection request.
ANR8214E

due to connection refusal.

connection request.
ANR8214E (HP-UX) The session stopped when no
data was read on socket socket number.
Explanation: The server is unable to read data on the
indicated socket. This might be a normal event if either
side of the connection is abruptly ended.
continues.
intentionally stopping either the client or server, no
response is required. Otherwise, ensure that the client
and server can communicate through such means as
Telnet or FTP applications, which are part of the
TCP/IP suite.

TCP/IP suite.
ANR8214E (Solaris) Session terminated when no
data was read on socket socket number.
indicated socket. This may be a normal event if either
continues.
TCP/IP suite.
ANR8214E (Windows) Session open with IP host
address failed due to connection refusal.
connection request.
ANR8215W

session because the remote system is unreachable.
User response: Ensure that the IP host address is
properly specified and that it is accessible over the
network. Use the TCP/IP ping command for this
purpose.
ANR8215W
ANR8214E (Linux) Session terminated when no data

was read on socket socket number.
continues.
500

as unreachable.

as unreachable.

purpose.
ANR8215E (HP-UX) ANR8216E (Solaris)

specified client system experienced a disruptive error
receiving data.

TCP/IP suite.

ended.
ANR8216W
ANR8215E (HP-UX) Session Session identifier aborted

due to receive error; error error code.

TCP/IP.
ANR8215E (Linux) Session Session identifier aborted
specified client system experienced a fatal error
receiving data.
ended.
TCP/IP.
ANR8215E (Solaris) Session Session identifier aborted
specified client system experienced a fatal error
receiving data.
ended.
TCP/IP.
ANR8215W (Windows) Session open with IP host
address failed as unreachable.
purpose.
ANR8216W
Error sending data on socket socket

number. Reason return code.
Explanation: The server experiences an error return

code from TCP/IP while sending data over the
continues.
Error sending data on socket socket


continues.
TCP/IP suite.
session with IP host address due to thread
creation error.
session because of an error creating a thread.
activities.
creation error.
activities.
creation error.
activities.
501

ANR8216W (Windows) Error sending data on socket
socket number. Reason return code.
continues.
TCP/IP suite.
ANR8217W
Error receiving data on socket socket


code from TCP/IP while receiving data on the
continues.
TCP/IP suite.
ANR8217W
Error receiving data on socket socket


continues.
TCP/IP suite.
ANR8217W (HP-UX) TCP/IP driver is unable to set
the window size to TCPWindowsize for
client client. The default value will be
used.
Explanation: The server cannot set the window size
for the indicated client to the requested size shown.
The server uses the default window size for the
indicated session. There may be a lack of memory for
TCP/IP buffers.
502
System action: Server operation continues and the

session continues with the default window size.
User response: Retry the session with a smaller
window size in the options file. Issue the QUERY
OPTION command to determine the setting of the
server TCPWindowsize.
ANR8217W (Linux) Unable to initialize TCP/IP
TCP/IP protocol.
available for Solaris. You may also use ps -ef to
determine if the number of applications is causing a
memory shortage. It may be necessary to decrease the
ANR8217W (Solaris) Unable to initialize TCP/IP
TCP/IP protocol.
available for Solaris. You may also use ps -ef to
ANR8217W (Windows) Error receiving data on
socket socket number. Reason return code.
continues.
TCP/IP suite.
ANR8218W ANR8219W
ANR8218W
Session terminated when no data was

read on socket socket number.

continues.
TCP/IP suite.
ANR8218W

read on socket socket number.

continues.
TCP/IP suite.
ANR8218W (HP-UX) TCP/IP driver is unable to use
the TCP/IP NODELAY option for client
client.

ANR8218W (Solaris) Unable to resolve address for
node name.
unsuccessful.
ANR8218W (Windows) Session terminated when no
data read on socket socket number.
Explanation: The server cannot read on the indicated
socket. This may be a normal event if either side of the
connection is abruptly ended.
continues.
TCP/IP suite.
Explanation: The server cannot set TCP/IP NODELAY

for the indicated client. The session proceeds with
TCP/IP Delay processing in effect. This causes TCP/IP
to buffer data prior to sending it to clients.
ANR8219W

session continues with the delay processing on.

with the client at the indicated address because it
cannot create a new thread.
User response: Further details for use in contacting

your service representative can be obtained by issuing
the following trace commands from an administrative
session or from the server console (proper
administrative authority is required): TRACE ENABLE
TCPINFO TRACE BEGIN tcptrace.out. After a session
starts and displays message ANR8218W, issue the
following commands: TRACE FLUSH TRACE END.
This will create trace data in file tcptrace.out and will
terminate the trace. This file should be supplied to your
server representative on request.
ANR8218W (Linux) Unable to resolve address for
node name.
unsuccessful.
TCP/IP driver is unable to accept a new

session with client at address TCP/IP
address due to an error creating a new
thread.
System action: Server operation continues, the session

request fails.
User response: The most likely cause is lack of
for z/OS. You can also decrease the maximum number
ANR8219W
TCP/IP driver is unable to accept a new

session with client at address TCP/IP
address due to an error in creating a new
thread.

with the client at the indicated address due to an
inability to create a new thread.
503
ANR8219W (HP-UX) ANR8220W (HP-UX)

request fails.
for AIX. You may also use SMIT to determine if the
ANR8219W (HP-UX) Unable to initialize TCP/IP
TCP/IP protocol.
available for HP-UX. You may also use SMIT to
ANR8219W (Linux) Unable to establish TCP
available for Solaris. You may also use 'swap -l' to
determine the amount of swap available. You may also
decrease the maximum number of sessions that the
server can accept with the MAXSESSIONS option in
ANR8219W (Solaris) Unable to establish TCP
available for Solaris. You may also use swap -l to
determine the amount of swap available. You may also
decrease the maximum number of sessions that the
ANR8219W (Windows) TCP/IP driver is unable to

accept a new session due to error in
creating a new thread.
due to the inability to create a new thread.
request fails.
memory. You may also wish to to cut down on the
options file.
ANR8220W
TCP/IP driver is unable to set the

window size to TCPWindowsize for client
client. The default value will be used.

TCP/IP buffers.
ANR8220W

window size to TCPWindowsize for client
client. The default value will be used.

TCP/IP buffers.
ANR8220W (HP-UX) Unable to establish TCP
504
ANR8220W (Linux) ANR8221I (HP-UX)

available for HP-UX. You may also use SMIT to
memory shortage. You may also decrease the maximum
ANR8220W (Linux) TCP/IP driver is unable to set
used.
TCP/IP buffers.
ANR8221W
TCP/IP driver is unable to use the

TCP/IP NODELAY option for client
client.

TCPINFO TRACE BEGIN. After a session starts and
displays message ANR8221W, issue the commands
TRACE FLUSH TRACE END. This will create trace
data in file tcptrace.out and will terminate the trace.
This file should be supplied to your service
representative on request.
ANR8221W
TCP/IP driver is unable to use the

TCP/IP NODELAY option for client
client.
ANR8220W (Solaris) TCP/IP driver is unable to set

used.


TCP/IP buffers.



TCPINFO TRACE BEGIN. After a session starts and
displays message ANR8221W, issue the commands
TRACE FLUSH TRACE END. This will create trace
data in file tcptrace.out and will terminate the trace.
This file should be supplied to your service
representative on request.

contact node name due to an output
reason code
ANR8221I (HP-UX) TCP/IP Version 4 administrative

driver ready for connection with clients
on port port number.

indicated node name. The attempt is unsuccessful due
to the inability to initialize a local socket.


User response: Ensure that TCP/IP is operating

properly on this node and that it can communicate
remotely. Use the TCP/IP ping command for this
purpose.
505
ANR8221W (Linux) ANR8222W (HP-UX)

ANR8221W (Linux) TCP/IP driver is unable to use
client.
TCP/IP delay processing in effect. This causes TCP/IP
session continues with delay processing on.
User response: Further details for use when
contacting your service representative can be obtained
by issuing the following trace commands from an
administrative session or from the console (proper
TCPINFO TRACE BEGIN tcptrace.out. After a session
following commands: TRACE FLUSH TRACE END.
service representative on request.
ANR8221W (Solaris) TCP/IP driver is unable to use
client.
issue the QUERY OPTION command to display the

current setting of the TCP window size.
ANR8222W

window size to TCPWindowsize for the
server master socket. The default value
will be used.

for the socket on which the server listens to the
requested size shown. The server uses the default
window size for listening for sessions. There may be a
lack of memory for TCP/IP buffers.
System action: Server operation continues with the
default window size.
User response: Restart the server with a smaller
window size in the options file if necessary. Issue the
QUERY OPTION command to determine the setting of
the server TCPWindowsize.
ANR8222W

window size to TCPWindowsize for the
server master socket. The default value
will be used.





TCPINFO TRACE BEGIN tcptrace.out After a session
following commands: TRACE FLUSH TRACE END


set the window size to TCPWindowsize
for session session, client client. The
default value will be used.
for the indicated session/client to the requested size
shown. The server will use the default window size for
the indicated session.
memory for TCP/IP buffers. You may retry with a
smaller TCP window size in the options file. You can
506
ANR8222W (HP-UX) The TCP/IP administrative

driver was unable to initialize due to
error using Port port, reason code reason
code.
communications for administrative sessions, the server
failed to connect to a master socket to listen for clients.
bind API.
server cannot accept administrative sessions from
clients using the TCP/IP protocol. This also includes
server-server sessions, storage agent to server sessions,
and library client to server sesssions.
file with the TCPADMINPORT option. If HTTP is also
in use for client sessions, ensure that the same port
communications. To do this, issue the TCP/IP netstat
ANR8222W (Linux) ANR8223W (Linux)

command. If the server was brought down and client
sessions were active, it can be necessary to end the
client sessions on the client systems before the port can
be freed.
User response: TCP/IP return code are listed in file

/usr/include/sys/errno.h and may provide a pointer
to the underlying problem. /usr/include/sys/errno.h
is part of fileset bos.adt.include.
ANR8222W (Linux) Unable to establish TCP

ANR8223W

ANR8222W (Solaris) Unable to establish TCP
use the TCP/IP NODELAY option for
client client.
TCPINFO TRACE BEGIN tcptrace.out After a session
following commands: TRACE FLUSH TRACE END
ANR8223W
Unable to connect to remote system

RemoteSystem due to unexpected return
code ReturnCode
Explanation: The server was unable to connect to a

remote system due to an unexpected return code from
the connect Application Programming Interface.
Common return code are handled with specific
messages. This return code was unexpected.
System action: Server operation continues but the
connection to the remote system fails.
Unable to connect to remote system

RemoteSystem due to unexpected return
code ReturnCode

to the underlying problem. /usr/include/sys/errno.h
is part of fileset bos.adt.include.
ANR8223W (HP-UX) The TCP/IP driver is unable to
accept a new session with the client at
address TCP/IP address, due to an error
in creating a new thread.
session request fails.
User response: The cause is probably lack of memory.
Ensure that sufficient paging space is available for AIX.
You might also use SMIT to determine if the number of
applications is causing a memory shortage. You might
also decrease the maximum number of sessions that the
ANR8223W (Linux) TCP/IP driver is unable to accept
a new session with client at address
TCP/IP address due to an error in creating
a new thread.
request fails.
for Solaris. You may also use ps -ef to determine if the
507
ANR8223W (Solaris) ANR8224W (Linux)

ANR8223W (Solaris) TCP/IP driver is unable to
accept a new session with client at
address TCP/IP address due to an error in
creating a new thread.
request fails.
for Solaris. You may also use ps -ef to determine if the
ANR8223W (Windows) Failed to connect to system at
address address port port.
Explanation: The server attempted to contact the
indicated node name at the specified port. The attempt
is unsuccessful. The target port is not valid at the target
node.
User response: Ensure that the node name still has
TCP/IP running and that the client is active in
SCHEDULE mode. If the server is attempting contact
with the SNMP subagent, ensure that the hostname and
port number for the subagent is correct in the server
options file.
ANR8224W
TCP/IP Administrative driver was

unable to initialize due to error in using
port port, reason code reason code.

has failed to connect to a master socket on which to
listen for clients. The reason code is the return code
from the TCP/IP bind API.
server to server sessions, storage agent to server
sessions, and library client to server sesssions.
file with the TCPADMINPORT, TCPPORT, or
HTTPPORT options. If HTTP is also in use for client
This may be done by issuing the TCP/IP netstat
command.If the server was brought down and client
sessions were active, it may be necessary to terminate
508
the client sessions on the client systems before the port

can be freed.
ANR8224W
TCP/IP Administrative driver was

unable to initialize due to error in using
port port, reason code reason code.

This may be done by issuing the TCP/IP netstat
command.If the server was brought down and client
can be freed.
ANR8224E (HP-UX) The server is unable to open the
file due to the system limit .
Explanation: An error occurs when the server
attempts to open a file.
System action: Server operation continues, but files
cannot be opened until the problem is fixed.
User response: Use the System Administrator
Manager (SAM) program to increase the value of the
maxfiles parameter. This value determines the
maximum number of files a process is allowed to open
at one time. For proper server operation, increase the
maxfiles value to at least 512.
ANR8224W (Linux) TCP/IP driver is unable to set
the server master socket. The default
value will be used.
ANR8224W (Solaris) ANR8225I (Windows)

ANR8225I
ANR8224W (Solaris) TCP/IP driver is unable to set

the server master socket. The default
value will be used.


ANR8224W (Windows) TCP/IP Administrative driver
was unable to initialize due to error in
using Port port, reason code reason code.
sessions, and library client to server sessions.
file with the TCPADMINPORT option. If HTTP is also
in use for client sessions, ensure that the same port
communications. Do this by issuing the TCP/IP netstat
-s command. If the server is brought down and then
started immediately, you can be within the TCP/IP one
minute timeout period for port reusage. Bring down
the server, wait one minute, and then restart the server.
If that does not work, it may be necessary to restart
Windows.
ANR8225I
TCP/IP administrative driver ready for

number.
TCP/IP Version 4 administrative driver

port port number.

ANR8225W (Linux) TCP/IP Administrative driver
using port port, reason code reason code.
To do this, issue the TCP/IP netstat command.If the
server was brought down and client sessions were
active, it may be necessary to terminate the client
freed.
ANR8225I (Solaris) TCP/IP Version 4 administrative
ANR8225I (Windows) TCP/IP Version 6 driver ready
number.

administrative clients using the TCP/IP protocol on the

509
ANR8226E ANR8227W (Linux)

ANR8226E
Error errno detecting version of

HBA-API library.
Explanation: The server attempted to determine the

level of the devices.common.IBM.fc.hba-api fileset and
encountered an error.
without accurate SAN device mapping.
ANR8226E
Error errno detecting version of

HBA-API library.
Explanation: The server attempted to determine the

level of the devices.common.IBM.fc.hba-api fileset and
before the port can be freed.

ANR8226W (Windows) Unable to initialize
NETBIOS driver on adapter network
adapter number.
Explanation: The server cannot obtain sufficient
NETBIOS resources to initialize communications on the
indicated network adapter.
server will not accept sessions from clients that use the
NETBIOS protocol.
User response: Ensure that NETBIOS is configured on
the system. Ensure that all NETBIOS resources are not
already in use. If the LAN Server or LAN Requester
application is running, you have NETBIOS configured.
In that case, starting the server prior to starting LAN
Server or LAN Requester may allow the server to
obtain the necessary NETBIOS resources.

ANR8227E
ANR8226I (Linux) TCP/IP Version 4 administrative
Fileset devices.common.IBM.fc.hba-api
is not at the required level.
Explanation: The specified fileset is at a level that is

incompatible with TSM operations. Install the latest
maintenance for this fileset if you use SAN devices.

ANR8227E
ANR8226W (Solaris) TCP/IP Administrative driver
using port port, reason code reason code.
Explanation: The TCP/IP administrative driver was
unable to initialize due to an error in running the BIND
API to port port, reason code reason code.
server-server sessions, storage agent to server sessions,
and library client-server sesssions.
file with the TCPADMINPORT or TCPPORT options. If
HTTP is also in use for client sessions, ensure that the
same port number is not specified for both TCP/IP and
HTTP communications. To do this, issue the TCP/IP
netstat command. If the server was brought down and
client sessions were active, it can be necessary to
terminate the client sessions on the client systems
510
Fileset devices.common.IBM.fc.hba-api
is not at the required level.
Explanation: The specified fileset is at a level that is

incompatible with TSM operations. Install the latest
maintenance for this fileset if you use SAN devices.
ANR8227W (Linux) Unable to connect to remote
system RemoteSystem due to unexpected
return code ReturnCode
/usr/include/asm/errno.h and may provide a pointer
to the underlying problem.
ANR8227W (Solaris) ANR8230I (Solaris)

ANR8227W (Solaris) Unable to connect to remote
system RemoteSystem due to unexpected
return code ReturnCode
is the presence of another system on the network that

is using the same name for NETBIOS communications.
This may be another server or client or a LAN
Requester node. Changing or adding the
NETBIOSNAME option for this adapter in your server
options file and restarting the server may allow this
adapter to be used with NETBIOS communications.
ANR8230I

to the underlying problem.
TCP/IP Version 6 driver ready for

number.

ANR8227W (Windows) NETBIOS connection

terminated - insufficient memory,
network adapter network adapter number.
Explanation: The server cannot listen for client
sessions on the specified network adapter due to a
memory allocation request failure.
sessions will not be accepted on the specified adapter.
Other network adapters remain unaffected.
memory.
ANR8228W (Windows) NETBIOS connection
terminated - server HALT in progress.

ANR8230I
The TCP/IP Version 6 driver is ready for

number.

ANR8230I (HP-UX) The TCP/IP Version 6 driver is
port port number.
with clients using the TCP/IP Version 6 protocol on the
ANR8230I (Linux) TCP/IP Version 6 driver ready for

number.
ANR8229W (Windows) Unable to add server name

server name to adapter network adapter
number.

Explanation: The server cannot initialize

communications processing using the NETBIOS
protocol on the indicated network adapter because the
server name cannot be added as a NETBIOS name on
the adapter.
System action: Server operation continues, but client

sessions from clients using the NETBIOS protocol will
not be accepted on this adapter. Other adapters are not
affected.
User response: The most likely cause for this message

ANR8230I (Solaris) TCP/IP Version 6 driver ready
number.
511
ANR8230W (Windows) ANR8233E (Linux)

ANR8230W (Windows) Insufficient memory to start
NETBIOS session on adapter network
adapter number.
due to a memory allocation request failure on the
specified adapter.
accept with the MAXSESSIONS or the
NETBIOSSESSIONS option, or both, in the server
options file.
ANR8231W (Windows) Unable to create thread to
accept NETBIOS sessions.
NETBIOS communications is inoperative.
options file.
listen for NETBIOS sessions on adapter
network adapter number.
inability to create a new thread of execution to monitor
the indicated network adapter.
NETBIOS communications is inoperative on the
indicated adapter. Other adapters remain unaffected.
512

options file.
ANR8233E
Unable to acquire local port

information. getaddrinfo return code
return code.
Explanation: The server or storage agent used the

system getaddrinfo API to determine which TCP/IP
protocols could be used. A failure occurred, as
indicated by the system error code that is shown. The
server was initializing TCP/IP communications.
System action: TCP/IP communications is inoperatve.
User response: System information concerning return
codes from the getaddrinfo system API should be
consulted. Ensure that TCP/IP networking for either
TCP/IP version 4 or version 6 is operating correctly.
ANR8233E
Unable to acquire local port

return code.

ANR8233E (HP-UX) Unable to acquire local port
return code.
ANR8233E (Linux) Unable to acquire local port
return code.
ANR8233E (Solaris) ANR8234I (Windows)

ANR8234I
The TCP/IP Version 6 administrative


ANR8233E (Solaris) Unable to acquire local port

return code.
ANR8234I (HP-UX) The TCP/IP Version 6

administrative driver is ready for
number.


handle NETBIOS session session number
on adapter network adapter number.
Explanation: The server cannot start a new client
session on the indicated adapter due to an inability to
start a separate thread of execution for the indicated
session.
System action: Server operation continues, but this
options file.
ANR8234I
TCP/IP Version 6 administrative driver

port port number.

ANR8234I (Linux) TCP/IP Version 6 administrative

ANR8234I (Solaris) TCP/IP Version 6 administrative
ANR8234I (Windows) TCP/IP Version 6
administrative driver ready for
number.

513

ANR8235W (Windows) Requested number of
NETBIOS sessions are not available on
adapter network adapter number,
proceeding with available sessions.
Explanation: The server cannot acquire the requested
number of NETBIOS sessions for the indicated adapter.
The server attempts to acquire the number of NETBIOS
sessions as indicated by the NETBIOSSESSIONS
parameter of the server options file or, if this option is
not specified, by the MAXSESSIONS option.
maximum number of NETBIOS sessions is limited to
the number of sessions that are acquired.
User response: Ensure that the required number of
NETBIOS resources are not already in use. If the LAN
Server or LAN Requester application is running, you
have NETBIOS configured. In that case, starting the
server prior to starting LAN Server or LAN Requester
may allow the server to obtain the requested NETBIOS
resources.
ANR8236W (Windows) Failure while listening for
NETBIOS sessions on adapter network
adapter number, NETBIOS listen return
code=listen return code.
Explanation: The server cannot listen for NETBIOS
sessions on the indicated adapter. The indicated listen
return code was received from the NETBIOS listen API.
If the return code is 24, (hex 18), the listen is retried.
System action: Server operation continues. If the
return code is 24 (hex 18), a new listen is setup because
return code 24 indicates a temporary failure. Otherwise,
no additional NETBIOS sessions will start using the
indicated adapter until the problem is corrected and the
server is restarted.
User response: A NETBIOS listen failure is an
indication of a network problem, an adapter problem,
or a NETBIOS configuration problem. The following
system configuration and system environment listen
return codes (in hex) and resolution actions for a listen
failure are found in the IBM Local Area Network
Technical Reference:
Return Code Description
11
The local session table is full. The
maximum number of sessions are in
use. Change NETBIOS configuration to
increase the maximum number of
sessions.
19
Name conflict. Ensure that the Server
NETBIOS name is not in use elsewhere
on the network.
514
Return Code Description

22
There are too many commands pending.
The maximum number of sessions are in
use. Change NETBIOS configuration to
increase the maximum number of
sessions.
35
The operating system resources are
exhausted. A reboot is probably
required.
ANR8237E (Windows) Unable to acquire local port

return code.
server was initialize TCP/IP communications.
ANR8260I (Windows) Named Pipes driver ready for
connection with clients.
with clients using the Named Pipes protocol.
ANR8261W (Windows) Named Pipes connection
terminated - insufficient memory.
System action: Server operation continues. Named
Pipes communications is inoperative.
options file.

ANR8262W (Windows) Named Pipes driver is
terminating due to error in creating a
new thread.
System action: Server operation continues, but Named
Pipes communications is inoperative.
options file.
ANR8263W (Windows) Error sending data on Named
Pipes, session session number.WriteFile
Return code is return code.
code from the WriteFile Windows NT API while
writing data to Named Pipes over the indicated
session. This may be a normal event if either side of the
connection is abruptly ended.
continues.
response is required.
ANR8264W (Windows) Error reading data on Named
Pipes, session session number. ReadFile
return code is return code.
code from the ReadFile Windows API while reading
data from Named Pipes in the indicated session. This
may be a normal event if either side of the connection
is ended abruptly.
continues.
ANR8265W (Windows) Error open Named Pipes
Named Pipes name, CreateNamedPipe
return code return code.
code when trying to open the indicated Named Pipes
name for Named Pipes communication with a client.
The return code shown is returned by the Windows
CreateNamedPipe API.

continues. Named Pipes communications is inoperative.
User response: The server may have run out of file
handles. Stop and restart the server to reenable Named
Pipes communications. It is not normal to run out of
file handles. A system or logic error may be the
underlying cause.
ANR8266W (Windows) Error accepting connection
on Named Pipes Named Pipes name,
ConnectNamedPipe return code return
code.
code when trying to complete a connection on the
indicated Named Pipes name for Named Pipes
communication with a client. The return code shown is
returned by the Windows ConnectNamedPipe API.
User response: A system problem may be preventing
use of Named Pipes. Stop and restart the server to
reenable Named Pipes communications.
ANR8267W (Windows) Error initializing a security
descriptor for Named Pipes Named Pipes
name, reason: System message.
code when trying to initialize the indicated Named
Pipe for Named Pipes communication with a client.
The reason shown is returned by the Windows
FormatMessage API.
User response: Administrator Privileges are required.
Login using an account wit h Administrator privileges
and restart the server to reenable Named Pipes
communications.
ANR8268W (Windows) Named Pipe communications
were not enabled due to an error
looking up the following Windows
group name: Windows group name. Use
the Windows User manager to add the
specified group. Members of the group
will then use Windows unified logon to
access the server over Named pipes.
code when trying to initialize the indicated Named
Pipe for Named Pipes communication with a client.
The system could not find the Windows Account name
User response: To use Windows unified logon specify
515

the name of a valid Windows account or group name.
Restart the server to reenable Named Pipes
communications.
ANR8269W (Windows) Error opening Named Pipe
Named Pipes name, reason: System message.
code when trying to open the indicated Named Pipe
name for Named Pipes communication with a client.
The reason shown is returned by the Windows
FormatMessage API.

options file.
ANR8276W (Windows) Shared memory connection
terminated - unable to initialize. Key
channel key, Reason: reason code.
due being unable to initialize shared memory.

System action: Server operation continues. Shared

memory communications are inoperative.
User response: Consider the reason text and take

appropriate action. Stop and restart the server to
reenable Named Pipes communications.
User response: Try a different shared memory session.
ANR8273I (Windows) Shared memory driver ready

number.
with clients using the shared memory protocol on the
indicated port.
ANR8277E (Windows) Shared memory unable to

initialize - Port: shm port number, Reason:
reason code.
because it could not intialize a communication channel.
Make sure no other server or storage agent running on
the same machine is using the same shm port number.

memory communications are inoperative.
User response: Try a different shared memory session.
ANR8274W (Windows) Shared memory

communications driver is terminating
ANR8280I (Windows) HTTP driver ready for

number.


clients using the HTTP protocol on the indicated port
number.
System action: Server operation continues, but shared

memory communications is inoperative.
memory.
ANR8275W (Windows) Shared memory connection
memory communications is inoperative.
516

ANR8281W (Windows) HTTP driver unable to
ANR8282I (HP-UX) ANR8283W (Windows)

restart Windows.
ANR8282I (HP-UX) SNMP driver ready for
connection with subagent on port port
number.
SNMP subagents on the indicated port number.
ANR8282I (Linux) SNMP driver ready for connection
with subagent on port port number.
ANR8282I (Solaris) SNMP driver ready for
number.
ANR8282I (Windows) HTTPS driver ready for
number.
clients using the HTTPS protocol on the indicated port
number.
ANR8283W (HP-UX) SNMP driver unable to
master TCP/IP socket on which to listen to SNMP
subagents. The reason code is the return code from the
TCP/IP bind API.
server cannot accept sessions from SNMP subagents to
run macro commands.

file with the SNMPSUBAGENT PORT option. If
TCP/IP or HTTP is also in use for client sessions,
ensure that the same port number is not specified for
TCP/IP or HTTP communications and SNMP
TCP/IP netstat command.
ANR8283W (Linux) SNMP driver unable to initialize
due to error in BINDing to Port port,
TCP/IP bind API.
run macro commands.
file with the PORT option. If TCP/IP or HTTP is also in
number is not specified for TCP/IP or HTTP
communications and SNMP communications.
ANR8283W (Solaris) SNMP driver unable to
TCP/IP bind API.
run macro commands.
communications and SNMP communications.
ANR8283W (Windows) HTTPS driver unable to
bind API.
517
ANR8284E ANR8285I (HP-UX)

specified for both TCP/IP and HTTPS communications.
restart Windows.

the cause of the failure.
ANR8284E

The Shared Memory Communications

Protocol could not initialize.
Explanation: The server was unable to initialize the

Shared Memory Communications Protocol due to an
error.
Shared Memory Communications.
ANR8284E
The Shared Memory Communications

Protocol could not initialize.

error.
ANR8284E (HP-UX) The Shared Memory
Communications Protocol could not
initialize.
error.
ANR8284E (Solaris) The Shared Memory

initialize.
error.
ANR8284W (Windows) HTTPS driver unable to

initialize due to error in secure data
initialization, reason code reason code.
communications, the server has failed to initialize the
secure data certificate information.
User response: Ensure the keyring file name and
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


with clients using the Shared Memory protocol.
ANR8285I
Shared Memory driver ready for


ANR8284E (Linux) The Shared Memory

initialize.
ANR8285I (HP-UX) Shared Memory driver ready for


error.


518
ANR8285I (Linux) ANR8286W (Windows)

ANR8285I (Linux) Shared Memory driver ready for
ANR8286W (HP-UX) Unable to initialize Shared

Memory driver - insufficient memory.

Explanation: Because the operating system rejected a

communications through the Shared Memory protocol.

ANR8285I (Solaris) Shared Memory driver ready for

Shared Memory protocol.
space for HP-UX. You may also use SAM to determine
shortage. It may be necessary to cut down on the

ANR8285I (Windows) SNMP driver ready for
number.
ANR8286W
Unable to initialize Shared Memory

driver due to insufficient memory.
ANR8286W (Linux) Unable to initialize Shared

User response: Ensure that there is sufficient swap
space for Solaris. It may be necessary to cut down on
the maximum number of client sessions by changing
the MAXSESSIONS option in the server options file.

ANR8286W (Solaris) Unable to initialize Shared




space for z/OS. Decrease the maximum number of

ANR8286W


space for AIX. You may also use SMIT to determine if
the number of applications is causing a memory
shortage. It may be necessary to cut down on the

space for Solaris. It may be necessary to cut down on
the maximum number of client sessions by changing
the MAXSESSIONS option in the server options file.
ANR8286W (Windows) SNMP driver unable to
TCP/IP bind API.
run macro commands.
519
ANR8287W ANR8288W
communications and SNMP communications. This may
be done by issuing the TCP/IP netstat -s command. If
the server is brought down and then started
immediately, you may be within the TCP/IP one
minute timeout period for port reusage. Bring down
the sever, wait one minute, and then restart the server.
If that does not work, it may be necessary to restart
Windows.
ANR8287W

Explanation: Because TCP/IP rejected a request for a

communications through Shared Memory.
User response: If TCP/IP is not started, use the HALT
command from any server prompt to stop the server,
and restart it.
ANR8287W


and restart it.
ANR8287W (HP-UX) Unable to initialize Shared
Memory driver - error creating acceptor
socket. Reason code reason code.
and restart it.
520
ANR8287W (Linux) Unable to initialize Shared

command from any prompt to stop the server, and
restart it.
ANR8287W (Solaris) Unable to initialize Shared
and restart it.
ANR8288W
Unable to establish Shared Memory

connection due to insufficient memory.

space for z/OS. You can also decrease the maximum
number of sessions that the server can accept by
decreasing the MAXSESSIONS option in the server
options file.
ANR8288W
Unable to establish Shared Memory


space for AIX. You may also use SMIT to determine if
the number of applications is causing a memory
shortage. You may also wish to cut down on the
options file.
ANR8288W (HP-UX) ANR8289W (Solaris)

ANR8288W (HP-UX) Unable to establish Shared
Memory connection - insufficient
memory.
space for HP-UX. You may also use SAM to determine
shortage. You may also wish to cut down on the
options file.
ANR8288W (Linux) Unable to establish Shared
memory.
space for Solaris. You may also wish to cut down on
the maximum number of sessions that the server can
options file.
ANR8288W (Solaris) Unable to establish Shared
memory.
space for Solaris. You may also wish to cut down on
the maximum number of sessions that the server can
options file.
ANR8289W
Shared Memory driver is terminating

due to error creating a new thread.
Explanation: The server cannot initialize because it

cannot create a new thread of execution.
System action: Server operation continues, but Shared
Memory communications is inoperative.
memory. Ensure that there is sufficient paging space for
z/OS. You can also decrease the maximum number of
sessions that the server can accept by decreasing the
ANR8289W


AIX. You may also use SMIT to determine if the
You may also wish to cut down on the maximum
ANR8289W (HP-UX) Shared Memory driver is
new thread.
HP-UX. You may also use SAM to determine if the
You may also wish to cut down on the maximum
ANR8289W (Linux) Shared Memory driver is
new thread.
memory. Ensure that there is sufficient swap space for
Solaris. You may also wish to cut down on the
options file.
ANR8289W (Solaris) Shared Memory driver is
new thread.
memory. Ensure that there is sufficient swap space for
521
ANR8290W ANR8291W (HP-UX)

Solaris. You may also wish to cut down on the
options file.
ANR8290W
Error sending data through Shared

Memory. Reason return code.

code while sending data through shared memory. This
is abruptly ended.
continues.
ANR8290W
Error sending data through Shared


is abruptly ended.
continues.
ANR8290W (HP-UX) Error sending data through
Shared Memory. Reason return code.
is abruptly ended.
continues.
ANR8290W (Linux) Error sending data through
is abruptly ended.
continues.
522
ANR8290W (Solaris) Error sending data through

is abruptly ended.
continues.
ANR8290I (Windows) IPX/SPX driver ready for
connection with clients on socket IPX
socket number.
with clients using the IPX/SPX protocol on the
indicated socket number.
ANR8291W
Error receiving data through Shared


code while receiving data through the Shared Memory
protocol. This may be a normal event if either side of
the connection is abruptly ended.
continues.
ANR8291W
Error receiving data through Shared


continues.
ANR8291W (HP-UX) Error receiving data through
ANR8291W (Linux) ANR8292W (Solaris)

continues.

continues.


ANR8291W (Linux) Error receiving data through

ANR8292W

Explanation: The server is unable to read data from

Shared Memory. This may be a normal event if either

continues.
ANR8291W (Solaris) Error receiving data through
continues.
ANR8291W (Windows) Unable to bind to IPX/SPX
master socket. Return code = return code.
Explanation: The server cannot initiate
communications on the socket number designated for
its use.
communications using the IPX/SPX protocol is
inoperative.
User response: Ensure that SPX has been configured
to run on this system through the requester
configuration program. Ensure that there is no other
instance of the server running on the same system that
is using the same socket number. This is likely to be the
case if the return code is zero. Also ensure that the
number of SPX sessions (as specified in your NET.CFG
file) has not been exceeded through other applications
using the IPX/SPX protocol.
ANR8292W

read through Shared Memory.

read through Shared Memory.

continues.
ANR8292W (HP-UX) Session terminated when no
data was read through Shared Memory.
continues.
ANR8292W (Linux) Session terminated when no data
was read through Shared Memory.
continues.
ANR8292W (Solaris) Session terminated when no
data was read through Shared Memory.
continues.

523

ANR8292W (Windows) IPX/SPX connection
options file.
ANR8293W
Shared Memory driver unable to

error.
Explanation: While initializing Shared Memory

communications, the server failed to set up an interface
with TCP/IP.
ANR8293W

error.

with TCP/IP.

ANR8293W (Linux) Shared Memory driver unable to
error.
with TCP/IP.
ANR8293W (Solaris) Shared Memory driver unable
to initialize due to socket initialization
error.
with TCP/IP.
ANR8293W (Windows) IPX/SPX driver unable to
the master socket, return code = return
code.
requests from clients using IPX/SPX, the server


using the IPX/SPX protocol.
ANR8293W (HP-UX) Shared Memory driver unable

to initialize due to socket initialization
error.
User response: Ensure that IPX/SPX is still running

properly and that it has not been intentionally or
unintentionally stopped. This may be done by using
the getipxad command to determine if an endpoint can
still be opened and bound; also determine if you can
still connect to a NetWare server.

with TCP/IP.
524
ANR8294W ANR8295W
ANR8294W
Shared Memory session unable to

initialize.
Explanation: While initializing a Shared Memory

communications session, an error occurred during
initial setup.
session is terminated.
User response: Contact your service representative for
assistance in resolving the error.
ANR8294W (Windows) Unable to establish IPX/SPX

connection - accept error. Return code =
tli error.
due to a failure in accepting the connection from
IPX/SPX.
System action: Server operation continues, but this

initial setup.
User response: Ensure that SPX has been configured

to run on this system through the requester
configuration program. Ensure that there is no other
instance of the server running on the same system that
is using the same socket number. Also ensure that the
number of SPX sessions has not been exceeded through
other applications using the IPX/SPX protocol, such as
NetWare applications.

ANR8295W
ANR8294W
Shared Memory session unable to

initialize.


ANR8294W (HP-UX) Shared Memory session unable

to initialize.

communications, the server failed to connect to a

initial setup.


User response: Ensure that no application is using the

port number specified in the server options file with
the SHMPORT option by issuing the TCP/IP netstat
can be freed.

ANR8294W (Linux) Shared Memory session unable
to initialize.
initial setup.
ANR8295W


ANR8294W (Solaris) Shared Memory session unable

to initialize.


initial setup.


can be freed.
525
ANR8295W (HP-UX) ANR8296W (HP-UX)

to initialize due to error in using Port
port, reason code reason code.
can be freed.
ANR8295W (Windows) Error sending data on session

session number. Reason return code.
code from IPX/SPX while sending data on the
indicated session. This may be a normal event if either
continues.
response is required. Otherwise, ensure that IPX/SPX is
still active.
ANR8296W

code.


TCP/IP listen API.


using the Shared Memory protocol.

can be freed.
to initialize due to error in BINDing to
can be freed.
526

ANR8296W

code.

TCP/IP listen API.
to initialize due to error in LISTENing
on the specified Port, reason code reason
code.
ANR8296W (Linux) ANR8297W (Linux)

TCP/IP listen API.
code.
TCP/IP listen API.
to initialize due to error in LISTENing
on the specified Port, reason code reason
code.
TCP/IP listen API.
ANR8297W


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.

ANR8297W


ANR8297W (HP-UX) Shared Memory driver is
terminating due to error in accepting a
new session, reason code reason code.
ANR8297W (Linux) Shared Memory driver is
527
ANR8297W (Solaris) ANR8306I

ANR8297W (Solaris) Shared Memory driver is
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
Appendix C in the Messages manual
for recommended action.
operating on the specified drive.

User response: Ensure that the DEVICE parameter
associated with the drive was identified correctly in the
DEFINE PATH command and that the drive is
currently powered on and ready. The drive reference
manual usually contains tables that explain the values
of the KEY, ASC, and ASCQ fields.
ANR8303E
I/O error on drive drive name

(OP=internal code, SENSE=internal code).
Explanation: An I/O error has occurred while

operating on the specified drive.
currently powered on and ready.
ANR8304E
Time out error on drive drive name in


operating on the specified library.
Explanation: A time out condition occurred while

waiting for the given drive to become ready so that
automated library operations could be performed.

associated with the library was identified correctly in
the DEFINE PATH command and that the library is
currently powered on and ready. If the library has an
access door, make sure it is closed. The library
reference manual usually contains tables that explain
the values of the KEY, ASC, and ASCQ fields.

DEFINE PATH command, and that the device is
currently powered on and ready.
I/O error on library library name

(OP=internal code, SENSE=internal code).
Explanation: The specified automated library device is

either not ready or not in an operational state.
ANR8301E

operating on the specified library.
the DEFINE PATH command and that the library is
access door, make sure it is closed.
ANR8302E
I/O error on drive drive name with

volume volume name (OP=internal code,
Error Number=internal code, CC=internal
code, KEY=internal code, ASC=internal
code, ASCQ=internal code, SENSE=sense
data, Description=error description). Refer
to Appendix C in the Messages manual
528
ANR8305E
Library library name is not ready or not

operational.
System action: Initialization of the library device fails.

User response: Ensure that the library is powered on
and ready for automated operations. Further
initialization attempts for the given library will usually
be postponed until the next attempt is made to access
the library for an automated operation. During server
startup, however, initialization may be retried after a
short waiting period.
ANR8306I
Request number: Insert device type volume

volume name mount mode into the slot
with element number slot element of
library library name within time limit
minutes; issue REPLY along with the
request ID when ready.
Explanation: A CHECKIN LIBVOLUME or a LABEL

LIBVOLUME command is in progress, and the
specified volume is needed. The server expects the
ANR8307I ANR8313E
volume to be inserted into the slot with the specified
element number of the given library within the time
limit specified in the message. For the slot and element
number diagram of your library, refer to the
documentation provided with the current ptf level or
refer to the Administrators Guide for your release and
platform.
System action: The server waits until a REPLY
command is issued, or until the time limit expires.
User response: Insert the volume into the slot and
issue a REPLY command, along with the request ID, to
tell the server that the volume has been inserted.
ANR8307I
Request number: Remove device type

volume volume name from slot with
element number slot name of library
library name; issue REPLY along with
the request ID when ready.
Explanation: A CHECKOUT LIBVOLUME command

has completed. You can remove the volume from the
slot with the specified element number and store it
outside the library. For the slot and element number
diagram of your library, refer to the documentation
provided with the current ptf level or refer to the
Administrators Guide manual for your release and
platform.
command is issued.
User response: Remove the volume from the slot and
store it in a safe place. Issue a REPLY command, along
with the request ID, to tell the server that the volume
has been removed. The volume can be returned to the
library with the CHECKIN LIBVOLUME command.
ANR8308I
Request number: device type volume volume

name is required for use in library library
name; CHECKIN LIBVOLUME required
within time limit minutes.
Explanation: A mount request has been made for a

volume that is defined in a storage pool, but which is
currently checked out of the given library.
ANR8309E
Mount attempt failed - library library

Explanation: An attempt has been made to mount a

volume, but the attempt fails because the specified
library is not defined.
User response: Ensure that the LIBRARY attribute of
the device class associated with the mount operation
identifies a defined library. If not, correct the value of
the LIBRARY attribute, or define the specified library
ANR8310E
An I/O error occurred while accessing

Explanation: An I/O error occurs while accessing the

designated library.
associated with the library is identified correctly in the
DEFINE PATH command, and that the library is
access door, make sure it is closed. After checking and
correcting these potential problems, retry the operation.
ANR8311E

drive drive name for low-level operation
operation, errno = drive errno.
Explanation: An I/O error occurs while performing

the operation on the specified drive.
associated with the drive is identified correctly in the
DEFINE PATH command, and that the drive is
currently powered on and ready. After checking and
ANR8312E
Volume volume name could not be

located in library library name.
System action: The server waits until it detects that

the volume has been checked into the library, or the
time limit expires.
Explanation: The designated volume cannot be found

at its expected location in the given 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 the CHECKIN
LIBVOLUME command if the library is currently full;
this process allows the server to select an appropriate
volume to be swapped out in order to make room for
the required volume.
User response: Perform an AUDIT LIBRARY

operation on the designated library, which forces the
server to reevaluate its inventory information for
volumes in the library.
ANR8313E
Volume volume name is not present in

Explanation: A mount request is made for the given

volume in the specified library, but the volume is not
currently checked into the library.
529
ANR8314E ANR8321I
System action: The mount operation fails. If the
volume is being mounted for storage pool I/O (as
opposed to import/export I/O), its ACCESS attribute is
changed to UNAVAILABLE to prevent further mount
requests.
User response: Issue a CHECKIN LIBVOLUME
command to return the volume into the library, and
update the volumes ACCESS attribute to READONLY
or READWRITE using the UPDATE VOLUME
command. Retry the mount request.
ANR8314E
Library library name is full.
Explanation: A library operation fails because all of

the librarys storage locations are occupied.
User response: Issue a CHECKOUT LIBVOLUME
command to make room in the library. Retry the library
operation.
ANR8315E
Command: The device type of drive drive

name is not supported in library type
libraries.
Explanation: Drives of the type identified in the

command are not supported in the given type of
library.
User response: Determine whether the drive and
library combination is supported by the installed level
of the server. If so, contact your service representative.
User response: Physically eject the volume from the

drive.
ANR8318I
Explanation: The server requires that the specified

volume be mounted as requested. Since the volume is
two-sided, this message specifies which side (A or B) is
needed by the server for I/O operations.
System action: The server waits for the volume to be
mounted.
User response: Mount the volume in the specified
drive.
ANR8319I
System action: The server waits until the volume is in

the library, or until the time limit expires.
User response: Insert the specified volume into the
library. If the volume has already been inserted into the
library, no user action is necessary.
Selecting swap volume to be checked

out of library library name.
Explanation: A CHECKIN LIBVOL command was

issued for a library that has no empty slots to hold the
new cartridge. The SWAP=YES parameter was included
in the command.
System action: A CHECKOUT LIBVOL command will
be automatically be issued, specifying either a scratch
volume or, if there are none, a volume with the lowest
number of mounts.
User response: Use a supported type of drive. volume
from the library and store it in a safe place. Issue a
REPLY command to tell the server that the volume has
been removed. The volume can be introduced back into
the library with the CHECKIN LIBVOLUME command.
ANR8317I
The volume in device type drive drive

name must be manually ejected.
Explanation: This device type does not automatically

eject the volume when it is dismounted and requires
that the volume be manually ejected from the drive.
530

volume name mount mode into library
library name within time limit minute(s).
Explanation: A CHECKIN LIBVOLUME command is

in progress, and the specified volume is needed. The
server expects the volume to be inserted into the
library with the convenience I/O station mechanism.
ANR8320I
ANR8316E
Request number: Mount side side of device

type volume volume name mount mode in
drive drive name of library library name
within time limit< minutes.

volume name mount mode in drive drive
name of library library name within time
limit minute(s); issue REPLY along
with the request ID when ready.

specified volume is needed. The server expects the
volume to be inserted in the designated drive of the
given library within the time limit specified in the
message.
User response: Insert the volume into the drive, and
then issue a REPLY command, along with the request
ID, to tell the server that the volume has been inserted.
ANR8321I

volume volume name from drive drive
name of library library name; issue
REPLY along with the request ID when
ready.
Explanation: A CHECKOUT LIBVOLUME or a

LABEL LIBVOLUME command has completed. You can
ANR8322I ANR8329I
remove the specified volume from the designated drive
and store it outside the library.
requests that it be mounted.

command is issued.
ANR8325I
User response: Remove the volume from the drive

and store it in a safe place. Issue a REPLY command,
along with the request ID, to tell the server that the
volume has been removed. The volume can be returned
to the library with the CHECKIN LIBVOLUME
command.
ANR8322I

volume volume name from entry/exit port
of library library name; issue REPLY
along with the request ID when ready.

has completed. You can remove the specified volume
from the entry/exit port of the given library and store
it elsewhere.
command is issued.
User response: Remove the volume from the library
and store it in a safe place. Issue a REPLY command,
along with the request ID, to tell the server that the
volume has been removed. The volume can be returned
to the library with the CHECKIN LIBVOLUME
command.
ANR8323I

volume name mount mode into entry/exit
port of library library name within time
limit minute(s); issue REPLY along with

specified volume is needed. Mount the volume in the
entry/exit port of the given library within the time
limit specified in the message.
Dismounting volume volume name mount retention period minute mount

retention expired.
Explanation: The specified volume is dismounted

because the given mount retention period has expired.
System action: The volume is dismounted.
ANR8326I
Request number: Mount device type volume

volume name mount mode in drive drive
name of library library name within time
limit minutes.
Explanation: If the volume name includes the names

EXP, IMP, DUMP, or DBBK, the request is for a scratch
volume.
System action: The server waits for the volume to be
mounted.
User response: Mount the volume in the specified
drive.
ANR8327E
Command: Cannot cancel request request

number.
Explanation: The request, whose number is specified

by the given command, cannot be canceled. The
requested operation must be completed.
System action: The cancel request command is not
processed.
User response: Proceed with the requested operation.
ANR8328I

name mounted in drive drive name.
Explanation: The server verifies that a requested

volume has been mounted properly in the given drive.

System action: The volume is accessed for reading or

writing, or both.
User response: Insert the volume into the librarys

entry/exit port; and issue a REPLY command, along
with the request ID, to tell the server that the volume
has been inserted.
ANR8324I
Device type volume volume name is

expected to be mounted (mount mode).
Explanation: The specified volume is expected to be

mounted in the near future so the server can access it
for reading or writing.
User response: If the volume is stored offline, retrieve
it so that it is readily accessible when the server
ANR8329I

mounted mount mode in drive drive name,
status: IDLE.
Explanation: In response to a QUERY MOUNT

command, the server indicates that the given volume is
mounted in the specified drive. The volume is currently
idle, meaning no active operations are being performed.
If the volume remains in the idle state for the amount
of time specified by the device class mount retention
period, it will be automatically dismounted.
531
ANR8330I ANR8339E
ANR8330I

status: IN USE.

in use, meaning that read or write operations, or both,
are being performed.

ANR8335I
Request number: Verifying label of device

type volume volume name in drive drive
name.
Explanation: The server verifies the label of the

volume that has been requested by an earlier mount
message. This is done to ensure that the correct volume
has been mounted by the operator.
System action: The server reads the volume label and

checks it for validity.
ANR8331I

status: DISMOUNTING.

being dismounted by the server.
ANR8336I
Verifying label of device type volume

volume name in drive drive name.
Explanation: The server verifies the label of a volume

that is needed for read or write operations, or both.
This is done to ensure that the correct volume has been
mounted.
System action: The server reads the volume label and

checks it for validity.
ANR8332I

mounted mount mode, status: IDLE.

mounted for I/O operations. The volume is currently
idle, meaning no active operations are being performed.
If the volume remains in the idle state for the amount
of time specified by the device class mount retention
period, it will be automatically dismounted.
ANR8333I

mounted mount mode, status: IN USE.

mounted for I/O operations. The volume is currently in
use, meaning that read or write operations, or both are
being performed.
ANR8334I
Number of matches matches found.
Explanation: This is a summary message for the

QUERY MOUNT command. It indicates the total
number of mount points that have been reported in the
command output.
532
ANR8337I
Device type volume volume name mounted

in drive drive name.
Explanation: The server verifies that the specified

mount request has been completed properly. Read or
write operations, or both, can be performed on the
volume.
System action: The label of the volume has been
verified.
ANR8338E

be overwritten by EXPORT operation.

contains data, so that the server cannot allow new
export data to be written to it.
overwritten by the requested export operation.
contain any valuable data, delete it and retry the export
operation.
ANR8339E
Device type volume intended volume name

in drive drive name was replaced with
volume incorrect volume name.
Explanation: The server detects that a previously

mounted and verified volume (the desired volume) has
been replaced with a different volume (the incorrect
ANR8340I ANR8349E
volume). No further read or write operations, or both,
can occur on the given drive, because data corruption
may occur.
User response: Issue the command with the correct

request number.
System action: The server dismounts the volume from

the drive.
ANR8345E
User response: Mount the correct volume again if it is

in a manual library and retry the operation.
Explanation: The request number specified by the

command is not in the list of outstanding mount
requests.
ANR8340I
Device type volume volume name

mounted.
Command: No match found for this

request number.

command.
Explanation: The server has mounted the given

volume.
User response: Issue the command with the correct

request number.

ANR8346I

ANR8341I
End-of-volume reached for device type

volume volume name.
Command: No requests are outstanding.
Explanation: A QUERY REQUEST or CANCEL

REQUEST command has been entered although no
mount requests are outstanding.


data must be stored, the server will access another
volume for it.
ANR8347E
Command: Volume volume not found.
Explanation: A DISMOUNT VOLUME command is

issued, but the volume to be dismounted cannot be
found.
ANR8342I
Request request number for volume

volume name canceled by administrator
name.
Explanation: A mount request is canceled by the given

administrator.
System action: The system cancels the mount request.
User response: Ensure that the correct volume name is

entered.
ANR8348E
Command: Volume volume is not Idle.
Explanation: A DISMOUNT VOLUME command has

been issued, but the volume is still in use and cannot
be dismounted.
ANR8343I
Request request number for volume

volume name canceled (PERMANENT) by
administrator name.
Explanation: A mount request is successfully canceled

with the PERMANENT option.
System action: The system cancels the mount request
and marks the volume as unavailable.

volume, cancel the session or process that is using the
ANR8349E
Command: Device device not found.

been issued, but the device to be dismounted cannot be
found.
ANR8344E
Command: Invalid request number request number.
User response: Ensure that the correct device has been

specified.
Explanation: A command has been entered with an

incorrect request number.
command.
533
ANR8350E ANR8357I
ANR8350E
Command: Device device is not Idle.

been issued, but the device is still in use and cannot be
dismounted.
device, cancel the session or process that is using the
device, and reissue the command.
ANR8351E
Request number: Mount request for

volume volume name has timed out.
Explanation: The mount request has not been satisfied

in the requested time.
System action: The server fails the mount request.
User response: Retry the mount request and ensure
that the volume is mounted within the time limit for
the manual library. For an automated library, retry the
mount request and increase the mount wait time for
the device class.
ANR8354E
Request number: Incorrect volume (volume

name) mounted in drive drive name.
Explanation: The user has inserted the named volume

into the indicated drive, but it is not the one requested
by the server.
System action: The volume is ejected, and the server
continues to wait for the requested volume to be
mounted.
User response: Ensure that the requested volume is
inserted properly into the designated drive.
ANR8355E
I/O error reading label for volume


reading/verifying the volume label for the volume in
the specified drive.
System action: The volume is dismounted by the
server.
Explanation: This message provides a list of currently

outstanding mount requests.
v Check the integrity of the data on the volume by

issuing an AUDIT VOLUME command. If this error
occurs on a volume that is stored inside a SCSI
library, the library itself may need to be audited by
using the AUDIT LIBRARY command.
System action: The server lists all outstanding mount

requests or the one specified on the QUERY REQUEST
command.
v The DEVICE parameter associated with the drive is

identified correctly in the DEFINE PATH command,
and the drive is currently powered on and ready.
After checking and correcting these potential problems,

ANR8352I
ANR8353E
Requests outstanding:
Request number: I/O error reading label

of volume in drive drive name.
Explanation: The server detects an error while reading

the volume label from the volume in the specified
drive.
mounted.
v The requested volume is properly inserted in the
designated drive.
v The volume has been labeled by using the
DSMLABEL utility program before you attempt to
use it with the server.
ANR8356E
Incorrect volume mounted volume name

was mounted instead of volume expected
volume name in library library name.
Explanation: The incorrect volume has been mounted

in the designated library. This error can occur if the
library inventory has been altered due to manual
intervention or movement of volumes, or both.
System action: The volume is dismounted; the
expected volume may be marked unavailable if this
error occurs during normal volume mount activity.
User response: Use the AUDIT LIBRARY command to
force the library to reevaluate its inventory of volumes.
v The DEVICE parameter associated with the drive is

identified correctly in the DEFINE PATH command,
and the drive is currently powered on and ready.
ANR8357I
Error reading label of volume from

slot-element element address in drive drive
name of library library name.
After checking and correcting these potential problems,

Explanation: While processing a search-mode

CHECKIN LIBVOLUME command for the designated
library, the server finds a volume whose label cannot be
read.
System action: The volume is dismounted and is not
checked into the library.
534
ANR8358E ANR8366E
and ensure that it is properly labeled. After doing so,
the volume can be checked into the library.
ANR8358E
Audit operation is required for library

library name.
ANR8362E
Command: The parameter parameter is

invalid for device type device type.
Explanation: The specified parameter is not valid for a

device class with the given device type.
Explanation: The server encounters a problem

managing the given library, and determines that an
AUDIT LIBRARY operation should be performed.
User response: Reissue the command with a correct

parameter.
System action: The server may continue to access the

library, but some volumes may not be accessible until
an AUDIT LIBRARY command is issued against the
library.
ANR8363E
User response: Issue an AUDIT LIBRARY command

against the library.
ANR8359E
Media fault detected on device type

volume volume name in drive drive name
of library library name.
Explanation: The server encounters a media fault

while accessing the given volume using the specified
drive.
System action: The operation that is attempting to
access the volume will fail, and the volume will be
immediately dismounted from the drive.
User response: In some cases, the server will
automatically mark the volume unavailable. If this does
not happen automatically, issue an UPDATE VOLUME
command to set the volumes access value to
unavailable. This will prevent the server from trying to
mount the volume to satisfy user requests. Issue an
AUDIT VOLUME command to determine if any data
has been lost due to the media failure.
ANR8360I
Volume volume name has been deleted

from MANUAL library library name.
Explanation: The specified volume has been deleted

by the server. It can be returned to a scratch pool by
the mount operator if desired.
System action: The volume is removed from the
servers inventory.

required for device type device type.
Explanation: The specified command requires that the

given parameter be supplied when the indicated device
type is used.
User response: Reissue the command, providing the
required parameter value.
ANR8364E
Command: Cannot reduce MOUNTLIMIT

below number of volumes currently
mounted.
Explanation: The MOUNTLIMIT value cannot be

reduced below the number of currently mounted
volumes.
User response: Wait until the server finishes using
some of the mounted volumes, or force the server to
dismount idle volumes using the DISMOUNT
VOLUME command, then retry this command.
ANR8365E
Command: The parameter parameter

cannot be changed.
Explanation: The specified parameter cannot be

changed from the value that was provided with the
associated DEFINE command.
User response: If it is necessary to use a different
value for the given parameter, the associated object
must be deleted and then redefined using the new
parameter value.

ANR8366E
ANR8361E
Command: Device type not specified.
Command: Invalid value for parameter

parameter.

DEVTYPE parameter be supplied.
Explanation: An invalid value has been provided for


valid DEVTYPE parameter.

valid parameter value. If this is for the ELEMENT
parameter on DEFINE DRIVE with AUTODETECT, this
message can be issued because the library doesnt
support the ability to determine the element number
535
ANR8367E ANR8374E
dynamically. In this case, supply the actual element
number instead of using AUTODETECT for the
ELEMENT parameter. If this is for the
SCALECAPACITY parameter on a 3592 device class,
verify that this device class has the attribute
WORM=NO as WORM and SCALECAPACITY are not
compatible.
ANR8367E
Command: Multiple parameter values are

not allowed.
ANR8371I
I/O is being bypassed for volume volume

name.
Explanation: The indicated volume is mounted but

the server is bypassing actual I/O operations for the
volume. The pool associated with the volume matches
the NULLPOOLNAME option in the options file or
NULLFILEDEVCLASS YES has been specified in the
options file.
Explanation: The designated parameter is specified

more than once in the command; this is not allowed.
ANR8372I
User response: Reissue the command, but specify the

given parameter only once.
ANR8368E
Request number: Incorrect side (side) of

volume volume name mounted in drive
drive name.

volume volume name from drive drive
name of library library name.
Explanation: A LABEL LIBVOLUME command has

completed. You can remove the specified volume from
the designated drive and store it outside the library.
Explanation: The user inserted the wrong side of the

requested volume into the indicated drive.
User response: Remove the volume from the drive

and store it in a safe place.

continues to wait for the requested side of the volume
to be mounted.
ANR8373I
User response: Insert the correct side of the requested

volume into the designated drive.
ANR8369E
Library library name is not defined.
Explanation: The designated library is not defined,

but has been referenced in a mount request.
System action: The mount request is rejected.
User response: Define the given library, or update the
LIBRARY parameter of the device class that references
it.
ANR8370I

mounted mount mode, status: RETRY.

mounted for I/O operations. The volume is currently in
RETRY, meaning an attempt is being made to
re-establish communications with another server. If the
volume remains in the retry state for the amount of
time specified by the device class retry period, the
operation will fail and the volume will be automatically
dismounted.
536
Request number: Fill the bulk entry/exit

port of library library name with all device
type volumes to be processed within time
limit minute(s); issue REPLY along with
Explanation: A CHECKIN LIBVOLUME or LABEL

LIBVOL command with SEARCH=BULK is in progress.
Load all volumes to be processed into the multi-slot
entry/exit port of the given library within the time
limit specified in the message.
User response: Insert the volumes into the librarys
entry/exit port; and issue a REPLY command, along
with the request ID, to tell the server that the volumes
have been inserted.
ANR8374E
Unable to unmount mountpoint

mountpoint name.
Explanation: A removable file device class mountpoint

had to be unmounted using the operating system
unmount function. The server did not have permission
to unmount the directory specified.
System action: The server continues, but cannot use
the mountpoint for removable file support until the
directory is unmounted.
User response: It may be necessary to run the server
as a root user to mounted directories to be unmounted.
ANR8375E ANR8383E
ANR8375E

be overwritten by BACKUPSET
operation.

backup set data to be written to it.
overwritten by the requested backup set operation.
ANR8376I
Mount point reserved in device class

Device class name, status: RESERVED.

ANR8380I

status: RETRY DISMOUNT FAILURE.
Explanation: Because of the failure of a previous

dismount, the server is retrying the dismount of the
specified volume from the specified drive. In response
to a QUERY MOUNT command, the server indicates
that the volume is mounted in the drive.
ANR8381E
Device type volume volume name could

not be mounted in drive drive name.

command, the server indicates that there is a mount
point reserved for future I/O operations in the given
device class.
Explanation: The server could not complete the

specified mount request due to an error. Examine
previous messages for additional information regarding
the specified volume and the operation.
User response: Examine previous messages for

additional information regarding the specified volume
and the operation.
ANR8377I

mounted mount mode, status:
DISMOUNTING.

currently being dismounted.
ANR8378I

mounted mount mode, status: RETRY
DISMOUNT FAILURE.

command, the server indicates that it is currently
retrying the dismount of the given volume because of a
failure during the previous dismount.
ANR8379I
Mount point in device class Device class

name is waiting for the volume mount to
complete, status: WAITING FOR
VOLUME.

command, the server indicates that there is a mount
point in the given device class waiting for the volume
mount to complete.
ANR8382W
Library library name is now full.
Explanation: During a library check-in operation from

a multi-slot entry/exit station, the last storage location
was filled before checking the remainder of the
entry/exit slots.
System action: The operation stops, but is considered
successful if at least one volume is checked in.
User response: If more volumes remain to be checked
in, issue a CHECKOUT LIBVOLUME command to
make room in the library. Retry the library operation.
ANR8383E
Device class device class name directory

directory name is not a SnapLock
directory.
Explanation: When processing the named device class,

it was discovered that a directory was specified for the
device class that is not a NetApp SnapLock WORM
Volume. All directories used by a device class for a
storage pool with RECLAMATIONTYPE=SNAPLOCK
must be Snaplock directories.
System action: If you are trying to define a storage
pool with RECLAMATIONTYPE=SNAPLOCK, the
command fails. If you are trying to update a device
class that is pointed to by a
RECLAMATIONTYPE=SNAPLOCK storage pool, the
command fails.
User response: If you are trying to define a storage
pool with RECLAMATIONTYPE=SNAPLOCK, you
537
ANR8384E ANR8389E
need to specify a device class which has all directories
which are NetApp SnapLock WORM Volumes. You
may select another device class which has all SnapLock
directories specified in it. Or you may use the UPDATE
DEVCLASS command to remove non-SnapLock
directories from the device class DIR list. If you modify
an existing device class, you need to ensure that no
data is stored in directories that are to be removed
from the device class. If this message is issued when
you are trying to update a device class, ensure that all
directories specified in the directory are SnapLock
directories.
ANR8384E
Request number: Incorrect volume (volume

name) inserted into library library name.
Explanation: The user has inserted the named volume

into the indicated library, but it is not the one requested
by the server.
System action: The volume is skipped, and the server
inserted.
User response: Ensure that the requested volume is
inserted properly into the designated location in the
library.
ANR8385E
All entry/exit ports of library library

name are empty.
Explanation: The entry/exit ports of the library do not

contain a volume that can be processed.
User response: Ensure that the volume is inserted
properly into the entry/exit port of the library and that
the library indicates the volume is inserted and issue
the command again. Contact the hardware vendor if
the volume is inserted correctly and this error occurs.
ANR8386W
Slot element number of library library

Explanation: The slot in the library could not be

physically accessed at this time.
System action: The slot is skipped and processing
continues with the next slot.
User response: If there is a volume in the slot that
needs to be processed, verify that the Entry/Exit door
is closed, the slot is accessible, and the device has not
logged any device errors before trying the command
again. Contact the hardware vendor if slots are
incorrectly being reported as inaccessible.
ANR8387I
538
Request number: All entry/exit ports of

library library name are full or
inaccessible. Empty the entry/exit ports,
close the entry/exit port door, and make
the ports accessible.

cannot find an empty and available entry/exit port to
place the volume to be removed.
System action: The server waits until the operator
performs the actions requested.
User response: Make at least one entry/exit port
empty and accessible. Check the entry/exit ports or the
library. Make sure the entry/exit door is closed. If all
the entry/exit ports are full remove at least one volume
from the entry/exit port. If any of entry/exit are empty
then the empty entry/exit ports are inaccessible. Check
the librarys documentation on how to make the
entry/exit port accessible. If the library is incorrectly
reporting the status of the entry/exit port contact the
library vendor.
ANR8388E
Device class device class name has no

directories specified.

which is referenced by a storage pool of type
RECLAMATIONTYPE=SNAPLOCK, it was discovered
that there were no directories specified for it. One or
more directories must be specified for a device class
that is used by a storage pool with
RECLAMATIONTYPE=SNAPLOCK, and all directories
must be NetApp SnapLock WORM Volumes.
User response: A device class that is referenced by a
storage pool of type
RECLAMATIONTYPE=SNAPLOCK needs to specify
one or more directories which are NetApp SnapLock
WORM Volumes. Use the UPDATE DEVCLASS
command to define appropriate directories to the
device class and retry your request.
ANR8389E
Device class device class name has storage

pools using it with inconsistent
RECLAMATIONTYPE parameters, or
invalid directories specified in it.

it was discovered that it was not configured properly. A
device class can be referenced by storage pools of type
RECLAMATIONTYPE=SNAPLOCK. For storage pools
of type RECLAMATIONTYPE=SNAPLOCK, all
directories specified in the device class must be on
NetApp SnapLock WORM Volumes.
System action: If the Tivoli Storage Manager server is
starting, the server continues; however, attempts made
to read from or write to that storage pool will fail until
the storage pools referencing the device class and the
device class are properly configured.
User response: Check the activity log for ANR8502,
ANR8383E, and ANR8388E messages. If these messages
have been issued, follow the instructions in the User
ANR8390W ANR8402E
Response section of those messages to resolve the
issues.
If the problem is not resolved, use the QUERY
DEVCLASS command with the FORMAT=DETAILED
option to obtain the specified directories for the device
class. Verify that each directory is available to the Tivoli
Storage Manager server, e.g., on-line, in read-write
mode, configured properly, etc.
If the problem is not resolved, for a device class used
by RECLAMATIONTYPE=SNAPLOCK storage pools,
check that each directory is a NetApp SnapLock
WORM Volume. If not, use the UPDATE DEVCLASS
command to update the device class directory structure
appropriately.
If the problem is not resolved, use the QUERY
STGPOOL command with the FORMAT=DETAILED
option to determine which storage pools are pointing to
the device class. Verify that storage pools of either type
RECLAMATIONTYPE=SNAPLOCK are using the
device class. If storage pools of both types are using the
device class, modify the storage pool definitions such
that only one type of storage pool uses the device class.
If you wish to have storage pools of both reclamation
types pointing to the same directory structure, you may
create two device classes with the same directory
structure, and have storage pools of one reclamation
type use one device class while storage pools of the
other reclamation type uses the other device class.
If you have made updates to the storage pools and
device classes and the problem is not resolved, you
may need to restart the Tivoli Storage Manager server.
the file is present on the system and that file

permissions allow the server to invoke the file.
ANR8392E
Explanation: The external library manager listed for

this library was not found. The path or the file name is
not correct.
System action: The library management operation
fails.
User response: Verify the path and the name of the
external library mentioned. If it is correct, verify that
the file is present on the system and that the file
permissions allow the server to invoke the file.
ANR8393E
Failure connecting to library client

library client to manage volume volume.
Explanation: The library manager failed to contact the

designated library client for a management operation
for the specified volume.
Failed to communicate with the external

library library name through its defined
external library manager path.
Explanation: The external library manager executable

file did not start or exited immediately.
fails.
User response: Verify the path and the file name of
this librarys external library manager. If it is correct,
verify that the file is present on the system and that the
the file permissions allow the server to invoke the file.
The path and file name can be found by using the
QUERY PATH command.
ANR8400I
ANR8390W
The external library manager file name

does not have executable permission.
The library library name is not available.
Library library name defined.

successfully defined.
System action: The library is defined and recorded in
the database.

fails.
User response: Review the other messages in the

activity log relating to this library client and this
volume to determine which operations were affected by
this failure.
ANR8401E
ANR8391E
The external library manager file name

can not be found. The library library
name is not available.
Explanation: The external library manager listed for

this library was not found. The path or the file name is
not correct.
fails.
User response: Verify the path and the name of the
external library mentioned. If it is correct, verify that
Command: Invalid library name library

name.
Explanation: The designated library name is invalid;

characters are invalid.
library name.
ANR8402E
Command: Library library name is already

defined.
Explanation: The designated library cannot be defined

because it already exists.
539
ANR8403E ANR8413E
name.
ANR8403E
Command: Operation not allowed for

library type libraries.
Explanation: The requested operation is not allowed

for libraries of the given type.
ANR8408E
Command: The DEVICE parameter is

required for this command.
Explanation: The DEVICE parameter has not been

provided; it is required.
User response: Reissue the command using the
DEVICE parameter.

ANR8404I
Drive Drive name defined in library

library name.
Explanation: The designated drive has been

successfully defined as a member of the specified
library.
System action: The drive is defined and recorded in
the database.
ANR8405E
Command: Invalid drive name drive name.
Explanation: The designated drive name is invalid;

characters are invalid.
drive name.
ANR8406E
Command: Drive drive name is already

defined in library library name.
Explanation: The designated drive cannot be defined

because it has already been defined for the specified
library.
ANR8409E
Explanation: The designated library has not been

defined.
command.
ANR8410I
ANR8407E
Command: The MODEL parameter is

Explanation: The MODEL parameter has not been

provided; it is required.
Library library name deleted.
Explanation: The designated library has been deleted

successfully.
System action: The library is deleted.
ANR8411E
Command: One or more drives are still


because there are still drives defined within it.
User response: Delete all drives from the library, and
ANR8412I

drive, reissue the command with a different drive
name.

defined.
Drive drive name deleted from library

library name.
Explanation: The designated drive has been deleted

successfully from the specified library.
System action: The drive is deleted.
ANR8413E
Command: Drive drive name is currently

in use.
Explanation: The designated drive cannot be deleted

or updated because it is currently in use.
User response: Reissue the command using the

MODEL parameter.

User response: Wait until the drive is no longer in
use, and reissue the command.
540
ANR8414E ANR8423I
ANR8414E
Command: Drive drive name is not

Explanation: The designated drive has not been

defined in the given library.
drive name. If appropriate, define the drive before
retrying the command.
ANR8415E

Explanation: The specified parameter must be

provided when processing the given command.
ANR8419E
Command: The drive or element conflicts

with an existing drive in library library
name.
Explanation: Either there are no more physical drives

in the library, or the specified ELEMENT parameter
conflicts with an existing defined drive in the given
library.
User response: Specify a valid ELEMENT parameter
that is not used by any other drive in the library.
ANR8420E
Command: An I/O error occurred while

accessing drive drive name.

specified drive.
User response: Reissue the command, providing the

required parameter value.
ANR8416E

invalid for library type library type.
Explanation: The specified parameter is not valid for

libraries of the given type. The scratch category must
be at lest 2 less than the private category for 349x
libraries.
User response: Reissue the command, using only the
proper parameters. If using the scratch category make
sure it is at least 2 less than the private category.
ANR8417E

invalid for drives in library type libraries.
Explanation: The specified parameter is not allowed

when defining or updating drives in a library of the
given type.
User response: Reissue the command, using only the
proper parameters.
ANR8418E
Command: An I/O error occurred while

accessing library library name.

designated library.
associated with the library is identified correctly in the
DEFINE PATH command, and that the library is
access door, make sure it is closed. After checking and

associated with the drive is identified correctly in the
DEFINE PATH command, and that the drive is
currently powered on and ready. After checking and
correcting these potential problems, retry the command.
ANR8421E
Command: Unable to start a process for

this command.
Explanation: The server cannot start a background

process to carry out the designated command.
User response: Check for and correct memory
shortages or other server resource constraints, and
ANR8422I
Command: Operation for library library

Explanation: A volume check-in process has been

started to handle the insertion of a volume into the
given library. The process is assigned the ID specified
in the message.
to perform the operation in response to the CHECKIN
LIBVOLUME command entered by an administrator.
User response: To obtain status on the process, issue
the QUERY PROCESS command. The process may be
canceled with the CANCEL PROCESS command.
ANR8423I
CHECKIN LIBVOLUME process for

library library name has been canceled.

been working to check in one or more volumes for the
given library is canceled by the CANCEL PROCESS
command.
541
ANR8424I ANR8432E
ANR8424I
Checking in volume volume name in

Explanation: In response to a QUERY PROCESS

command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. The
given volume is being checked in to the designated
library.
ANR8428E
Command: The STATUS parameter is

Explanation: The STATUS parameter must be

provided with the given command.
User response: Reissue the command, and provide a
valid STATUS parameter value.
ANR8429E
Command: No drives are currently

System action: The background process operation

continues.
Explanation: The command cannot be issued until at

least one drive has been defined in the given library.
User response: None. The process may be canceled by

an authorized administrator using the CANCEL
PROCESS command.
ANR8425I
Checking in volumes in search mode in


CHECKIN LIBVOLUME process on the server. Volumes
are being checked into the given library automatically
using a search for previously-unknown volumes.
continues.
PROCESS command.
User response: Define a drive in the library, using the

DEFINE DRIVE command, as well as a path to the
drive, using the DEFINE PATH command. Then retry
the failed command.
ANR8430I
Explanation: A search-mode CHECKIN LIBVOLUME

process has found the given volume and automatically
checked it into the library.
System action: The volume is added to the given
librarys inventory.
ANR8431I
ANR8426E
CHECKIN LIBVOLUME for volume

volume name in library library name failed.
Explanation: The background process for a CHECKIN

LIBVOLUME command has failed.
System action: The background process ends, but the
volume has not been checked into the library.
User response: Make sure the library and drive
devices associated with this command are powered on
and ready, and then reissue the command.
CHECKIN LIBVOLUME for volume
volume name in library library name
Explanation: The specified volume was successfully

checked in to the library during processing of a
CHECKIN LIBVOLUME or LABEL LIBVOLUME
command.
System action: The volume is made available for
mounting in the given library.
542
CHECKIN LIBVOLUME process

completed for library library name; volume
count volume(s) found.
Explanation: A search-mode CHECKIN LIBVOLUME

process is completed. The specified number of volumes
have been successfully added to the librarys inventory.
System action: The volumes are made available for
use by the server.
ANR8432E
ANR8427I
Volume volume name has been checked

into library library name.

present in library library name.
Explanation: The specified volume cannot be checked

into the given library because it is already present.
User response: Provide the name of a volume that is
not already present in the given library. Use the
QUERY LIBVOLUME command to obtain a full list of
volumes that have already been checked into the
library.
ANR8433E ANR8441E
ANR8433E

present in library library name.
ANR8437E
CHECKOUT LIBVOLUME for volume

volume name in library library name failed.
Explanation: The specified volume cannot be checked

out of the given library because it is not present.
Explanation: The background process for a

CHECKOUT LIBVOLUME command has failed.

volume has not been checked out of the library.
User response: Provide the name of a volume that is

present in the given library. Use the QUERY
LIBVOLUME command to obtain a full list of volumes
that reside in the library.
ANR8434I
Command: Operation for volume volume

name in library library name started as
process process ID.
Explanation: A volume check-out process has been

started to handle the removal of a volume from the
given library. The process is assigned the ID specified
in the message.
to perform the operation in response to the
CHECKOUT LIBVOLUME command entered by an
administrator.
ANR8435I

volume name in library library name has
been canceled.

been working to check out the volume from the given
library is canceled by the CANCEL PROCESS
command.
ANR8436I
Checking out volume volume name from


CHECKOUT LIBVOLUME process on the server.

and ready, then retry the command.
ANR8438I

volume name in library library name
Explanation: The background process for a

CHECKOUT LIBVOLUME command has completed
successfully.
librarys inventory (if its status is something other than
ANR8439I
SCSI library library name is ready for

operations.
Explanation: The initialization process for the given

library has completed successfully, and the library is
ready for use.
System action: The library is made ready for use.
ANR8440E
Initialization failed for SCSI library

library name; will retry in delay time
minute(s).

library has failed. It will be retried automatically after
the specified amount of time has elapsed.
System action: The initialization will be retried later.
User response: Ensure that the library device is
powered on and ready. If the library has an access
door, make sure it is in the closed position.

continues.
ANR8441E

PROCESS command.

library has failed, and will not be retried until the next
time the server needs to access the library.
Initialization failed for SCSI library

library name.
System action: The library is made temporarily

unavailable.
User response: Make sure the library is powered on
and attached.
543
ANR8442E ANR8449E
ANR8442E
Command: Volume volume name in library

library name is currently in use.
Explanation: The command cannot be processed

because the specified volume is already being used for
another operation.
If the volume is currently mounted, but idle, you can
dismount it with the DISMOUNT VOLUME command
and then retry this operation.
ANR8443E

library name cannot be assigned a status
of SCRATCH.
Explanation: The volume cannot be assigned to the

given librarys scratch pool because there is a storage
pool volume defined or a volume in the volume history
file with this volume name. Such a volume may still
contain valid data. Assigning the volume to the
librarys scratch pool might result in a destructive
overwrite of the volumes data.
User response: Reissue the command, specifying that
the volume be assigned a status of PRIVATE.
ANR8444E
Command: Library library name is

currently unavailable.
Explanation: The requested operation cannot be

completed because the specified library is unavailable
for I/O operations. The library may still be carrying
out its initialization operations.
User response: Wait until the library initialization
completes or the library becomes ready.
ANR8445I
Volume volume name in library library

name updated.
Explanation: The specified library volume has been

updated successfully.
System action: The library volume inventory is
updated.
User response: If the library has an access door, make

sure it is in the closed position. If it has a cartridge
carousel, make sure the carousel is installed. The server
automatically detects when the appropriate action has
been taken; it will then continue its operations.
ANR8447E
No drives are currently available in

Explanation: The attempted operation cannot be

completed on the specified library because there are no
available drives. A drive may be unavailable because
an application other than the server may have the
driver opened. This message may also be issued if a
CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
because all the drives are mounted by other processes
or sessions, or the device type was incorrectly specified.
System action: The attempted operation is terminated.
User response: Use the QUERY DRIVE command to
check the online status of the drives. Drives that are
marked Unavailable since hh:mm yy/mm/dd are
drives taken offline by the server at the time specified
because of hardware failures or the inability to open
the drive. If the attempted operation is a CHECKIN or
LABEL command, use the QUERY MOUNT command
to determine if all the drives in the library are mounted
and wait until one of these is available. If there are
mounted volumes with an IDLE status, use the
DISMOUNT VOLUME command to free its drive, and
retry the original operation.
ANR8448E
Scratch volume volume name from library

library name rejected - volume name is
already in use.
Explanation: The designated volume has been used to

satisfy a scratch mount, but the volume is already
defined in a storage pool, or has been used to store
server export, database dump, or database backup
information as recorded in the server volume history
file.
System action: The volume is rejected.
User response: Use a volume that is not in use, or
check out and relabel the rejected volume, assigning it
a new name in the process, or delete the existing
volume that caused the name conflict.
ANR8449E
ANR8446W
Explanation: The designated volume has been used to

satisfy a scratch mount, but the volume is already
defined in a storage pool, or has been used to store
server export, database dump, or database backup
information as recorded in the server volume history
file.
Manual intervention required for library

library name.
Explanation: The specified library requires manual

intervention.
System action: Current library activity will be delayed
until the required intervention occurs.
544
Scratch volume volume name rejected volume name is already in use.
ANR8450E ANR8458I
User response: Use a volume that is not in use, or
rename the rejected volume or delete the existing
volume that caused the name conflict.
ANR8450E
Command: Library library name is

currently in use.

or updated because it is currently in use for an I/O
operation.
User response: Wait until the library is no longer in
use, and then retry the command.
ANR8451I
349X library library name is ready for

operations.

ready for use.
ANR8452E
Initialization failed for 349X library

minute(s).

library has failed. It is retried automatically after the
specified amount of time has elapsed.
powered on and ready.
ANR8453E
Initialization failed for 349X library

library name.

library has failed and will not be retried until the next
unavailable.
ANR8455E

located during audit of library library
name. Volume has been removed from
the library inventory.
Explanation: While processing an AUDIT LIBRARY

command for the given library, the server cannot find
the given volume in the library.
System action: The volume is removed from the
library inventory.
User response: If the volume is needed, it should be
located and checked into the library using the
CHECKIN LIBVOLUME command.
ANR8456E
Multiple volumes named volume name

were found during audit of library
library name.
Explanation: While processing an AUDIT LIBRARY

command for the given library, multiple physical
volumes are found to have the same name.
System action: The first instance of the volume is
retained in the server inventory; all other instances are
ignored.
User response: Remove all of the redundant instances
of the volume from the library. If the volume which the
server retained is found to be the incorrect one, it can
be checked out with the CHECKOUT LIBVOLUME
command; then the correct instance can be checked into
the library with a CHECKIN LIBVOLUME command.
ANR8457I

Explanation: A library audit process has been started

for the given library. The process is assigned the ID
specified in the message.
to perform the operation in response to the AUDIT
LIBRARY command entered by an administrator.

ANR8458I
ANR8454E
Mismatch detected between external

label (volume name from external label) and
media label (volume name from media label)
in 349X library library name.
Explanation: The external label of a volume was

found to differ from its media label in the designated
library.
System action: The volume will not be accessed.
AUDIT LIBRARY process for library

library name has been canceled.

been working to audit the given library is canceled by

and ensure that it is properly labeled.
545
ANR8459I ANR8468I
ANR8459I
Auditing volume inventory for library

library name.

command, this message displays the status for an
AUDIT LIBRARY process on the server.
PROCESS command.
ANR8460E

library name failed.
Explanation: The background process for an AUDIT

LIBRARY command has failed.
ANR8464E
command: Invalid update request for

Explanation: An invalid update request has been

made for the given library. This can occur if a new
device name is given and the characteristics of the
device do not match the characteristics of the original
device.
command.
User response: If a different type of library device has
been installed, the old library definition must be
deleted with a DELETE LIBRARY command, and a
new library must be defined. The UPDATE LIBRARY
command cannot be used in this case.
Library library name updated.
System action: The background process ends.
ANR8465I

and ready, then reissue the command.
Explanation: An UPDATE LIBRARY request has been

successfully processed for the given library.
ANR8461I

library name completed successfully.
Explanation: The background process for an AUDIT

LIBRARY command has completed successfully.
System action: The library inventory is updated to
match the contents of the library as found during the
audit operation.
ANR8462I
End-of-side reached for device type

volume volume name.
Explanation: The server has detected an end-of-side

condition for the given two sided volume.
System action: The server will access the second side
of the volume.
System action: The server updates its information

about the library.
ANR8466E
command: Invalid update request for

drive drive name in library library name.
Explanation: An invalid update request has been

made for the given drive. This can occur if a new
device name is given and the characteristics of the
device do not match the characteristics of the original
device.
command.
User response: If a different type of drive has been
installed, the old drive definition must be deleted with
a DELETE DRIVE operation, and a new drive must be
defined. The UPDATE DRIVE command cannot be
used in this case.

ANR8467I
ANR8463E
Device type volume volume name is write

protected.
Explanation: The server has detected a write-protect

condition for the given volume.
System action: The server will dismount the volume
and continue processing with another volume.
User response: Adjust the write-protect switch on the
volume so that writing is allowed. If the volume is an
optical volume and the write-protect switch is already
set to allow writing, use the MOVE DATA command to
move the data off of the volume. Rewritable volumes
may be reformatted and reused after the data is moved
to another volume.
Drive drive name in library library name

updated.
Explanation: An UPDATE DRIVE request has been

successfully processed for the given drive.
about the drive.
ANR8468I
device type volume volume name

dismounted from drive drive name in
Explanation: The specified volume has been

dismounted from the given drive.
546
ANR8469E ANR8475I
User response: If the type of the given library is
MANUAL, the operator may elect to remove the
volume (which has already been ejected) from the drive
and store it in an appropriate location. For automated
libraries, this message is purely informational.
ANR8469E
Dismount of device type volume volume

name from drive drive name in library
Explanation: An attempt to dismount the designated

volume failed due to an I/O error.
library, the server finds a volume whose label cannot be

read.
System action: The volume is dismounted and is not
checked into the library.
and ensure that it is properly labeled. After doing so,
the volume can be checked into the library.
ANR8473I

User response: If the type of the given library is
MANUAL, the volume can be manually ejected and
removed from the drive. For automated libraries,
manual intervention may be required to correct the
problem.
ANR8470W
Initialization failure on drive drive name

in library library name.
Explanation: The specified drive could not be

initialized at this time.
System action: The initialization of the specified
library continues.
additional information regarding the specified drive.
ANR8471E
Server no longer polling drive drive name

in library library name - path path will be
marked off-line.
Explanation: The server is unable to use the

mentioned drive via the specified path. This may be for
the following reasons:
v The drive cannot be opened
v In the case of a 3494 or a library that can be
partitioned, the drive may be unavailable to the
library manager, may be in use by another
application, or may be loaded with a cartridge not
labeled for server use.
System action: The path to the drive is offline and is
not used for tape operations.
User response: Determine the reason the path to the
drive is inaccessible, such as hardware errors reported
in the system logs. Render any needed corrections to
the hardware. Then the path may be made online by
issuing the UPDATE PATH command with the
ONLINE=YES option.
ANR8472I
Error reading label of volume in drive

drive name of library library name.
Explanation: While processing a search-mode

CHECKIN LIBVOLUME command for the designated
Volume volume name was found in

storage element slot element address in
library library name. It may still be in the
drive.
Explanation: The specified volume was found in the

storage slot of a cleaner cartridge. After it was loaded
into a drive for cleaning, TSM determined that it is not
a cleaner cartridge. TSM encountered an error trying to
move the cartridge back to the storage slot of the
cleaner cartridge. If the volume is a storage pool
volume, TSM already attempted to make it unavailable.
Review the output of the QUERY VOLUME F=D
command for storage pool volumes. Review the output
of the QUERY VOLHISTORY command for non-storage
pool volumes.
User response: Verify all other cleaner cartridges are
in the correct storage slots. Issue the QUERY
LIBVOLUME command to obtain the storage slots of
all the cartridges currently checked into TSM. Remove
the cartridge in the storage slot identified in the
ANR8911W message. Remove the specified volume
from the drive. Issue an AUDIT LIBRARY command
against the library.
ANR8474E

defined to library library name.

because there are still paths defined to it.
User response: Delete all paths to this library, and
ANR8475I
Dismount of volume volume name failed.

It may still be in the drive.
Explanation: The specified volume could not be

dismounted. TSM encountered an error trying to
dismount the volume. If the volume is a storage pool
volume, TSM already attempted to make it unavailable.
Review the output of the QUERY VOLUME F=D
command for storage pool volumes. Review the output
of the QUERY VOLHISTORY command for non-storage
pool volumes.
User response: Review message ANR8469E in the
547
ANR8476E ANR8495E
activity log. Check if the volume is still loaded in the
drive. If the volume is not in the drive, determine
where the volume is located in the library.
ANR8476E
Operation is not supported for the

libtype of library library name.
Explanation: The operation failed because the libtype

of the library is not supported for the operation.
User response: Use a different libtype such as
MANUAL to perform the operation.
ANR8477E
Device type device type is incorrect for

drive drive name.
Explanation: The device type of the specified drive on

the library client is not compatible with the device type
for the same drive on the library manager.
User response: Delete the drive definition on the
library client, and re-define the drive specifying the
correct device. If this does not correct the problem,
contact your service representative for assistance.
ANR8478W
Invalid home slot address in inventory

for library library name; volume = volume
name;slot = slot number.
Explanation: The specified volumes home slot in the

library inventory does not match the database
inventory.
User response: Run audit library against the
specified library.
ANR8479W
Unable to audit slot-element slot-element

of library library name.
Explanation: The library audit process was unable to

audit storage slot with the specified element address.
This is probably due to no drive device being available
into which to load the cartridge. It can also be due to
library or drive I/O errors occurring during the audit
process.
System action: The AUDIT LIBRARY command fails.
User response: Verify that for every type of cartridge
in the library at least one drive is defined that can read
the media, and that the drive is online and working
properly. Check the activity log for I/O errors related
to hardware failure and repair.
ANR8480E
The drive Drive Name was not found for

library Library Name.
Explanation: The missing drive needs to be defined to

successfully run the current operation.
User response: Make sure that the drive is defined. If
macros are being used, the COMMIT command needs
to be issued after the DEFINE DRIVE. Otherwise, this
could indicate a server internal error.
ANR8481I
The library library name already has an

AUDIT LIBRARY operation pending
mount activity.
Explanation: Libraries of type SHARED can only have

one AUDIT LIBRARY operation waiting on mount
activity. All subsequent AUDIT LIBRARY operations
will be canceled.
ANR8493I
device type volume volume name mounted

in drive drive name in library library
name.
Explanation: The specified volume has been mounted

in the specified drive.
User response: For automated libraries, this message
is purely informational.
ANR8494E
Command: An option specified is not

valid for library type libraries.
Explanation: A requested option is not valid for

libraries of the given type for the specified command.
ANR8495E

be written by BACKUP DB operation.

BACKUP DB data to be written to it. Or there is no
space available on the destination filespace to write this
backup to.
overwritten by the requested BACKUP DB command,
or that there is not enough space available.
548
ANR8496E ANR8501E
BACKUP DB command.
ANR8496E
Device class device class not defined in

device configuration information file.
Explanation: The command that has been issued

requires that the specified device class be defined in the
device configuration information file. This definition
was not found or the statements in the file are in the
wrong order.
valid device class. Refresh your device configuration
information file by issuing the BACKUP DEVCONFIG
command.
ANR8497E
Library library not defined in device

configuration information file.

specified library be defined in the device configuration
information file. This definition was not found or the
statements in the file are in the wrong order.
User response: Refresh your device configuration
command. Make sure a library is defined for the device
class. Reissue the command.
ANR8500E
No valid path is defined for library

library name or any of its drives in device
configuration information file.
Explanation: The specified command requires that a

path be defined in the device configuration information
file for the specified library and its drive. This valid
definition was not found, or the statements in the file
are in the wrong order.
command. Make sure a path is defined for the library
and its drive associated with the device class. Verify the
correct source is used in these path definitions. If the
default server name is not used as the source, a SET
SERVERNAME command is required in the device
configruation information file. Reissue the command.
ANR8501E
System return code return code received

opening volume server volume name with
file name file name
Explanation: The server or storage agent attempted to

access the file name indicated but failed to open the
volume. The indicated system return code was
received. The actual volume name corresponds to the
file name that the server uses. The server volume name
and the file name may be the same when the server
experiences a failure in opening the file.
System action: The volume is not opened.
ANR8498E
Drive not defined for library library in

device configuration information file.

specified drive be defined in the device configuration
information file for the specified library. This definition
was not found or the statements in the file are in the
wrong order.
command. Make sure a drive is defined for the library
associated with the device class. Reissue the command.
ANR8499I
Command accepted.
Explanation: The command is accepted and processed

by the server.
System action: The server processes the command.

and names of directory entries. PATH definitions for
each of the FILE drives should be checked that the
number of directories in the PATH definition match the
number in the servers device class definition and that
directories exist and are accessible to servers and
549
ANR8502E ANR8504E
ANR8502E
Errno errno received checking WORM

directory directory name on Filer.
Explanation: The server attempted to access the

named directory on the NetApp SnapLock Filer, but the
attempt failed with the indicated error code.
System action: If you were trying to define a storage
pool or update a device class associated with a storage
pool, the command fails. If this error is encountered
during server initialization, server initialization
continues, but operations involving this storage pool
will not be allowed until the issue is resolved.
User response: This may be caused by an error in the
NetApp Filer or with the communications between
your server and the NetApp Filer. Verify that the
network is operational, that the SnapLock Filer is
accessible from your server, and consult NetApp
SnapLock Filer documentation to resolve the issue;
then, retry the command.
ANR8503E
A failure occurred in writing to volume

server volume name.

writing to the specified volume.
systems.
available space.
FILE drives should be checked to ensure that the
550

ANR8504E
A failure occurred in flushing data to

volume server volume name.

The failure occurred during a flush operation when the
server was attempting to synchronize its progress of
data written with that of the file system. If the file
system becomes full, it is possible to receive no error
indications until the flush operation is attempted.
writing to the specified volume. The transaction in
progress is rolled back.
systems.
available space.
FILE drives should be checked to ensure that the
ANR8505I ANR8550E (Linux)

ANR8505I
Verifying path definitions for library

library name between storage agent
storage agent and library manager primary
library manager. Processing library count
out of total library count libraries.
Explanation: The specified library path definition is

being verified for storage agent initialization.
System action: The server processes the verification
for the specified library.
User response: If the server does not finish
verification for all the counted shared libraries, verify
connectivity and configuration of the primary library
manager paths. Check the library manager of the last
storage agent displayed in the library path verification
message.
ANR8506E
The library library name is not

compatible with stand-alone, utility
operations.
Explanation: The specified library cannot operate in

stand-alone mode such as DUMPDB or RESTORE DB.
User response: If this is a FILE library, use a device
class that does not use a FILE library. A FILE device
class does not need a library, and thus, can be updated
with LIBRARY= and SHARED=NO. Update your
device configuration file appropriately for the
stand-alone operation, and then if needed, return the
device class to its original state using a FILE library or
with SHARED=YES when the server is running.
ANR8507W
Volume volume name is using an

encryption key that is not unique and
therefore is not secure.
Explanation: Each volume should have a unique

encryption key. This volume inappropriately shares an
encryption key with other volumes.
System action: The operation completes.
User response: Moving the data from this volume to
new volume will create a unique encryption key for the
new volume and make the data more secure. Before
moving the data, mark this volume READONLY to
prevent Tivoli Storage Manager from appending data to
the volume. Then, use the MOVE DATA command to

move the data from this volume to a new volume in
your encryption storage pool.
ANR8550E
Error opening filespec.

open operation.
User response:
v Refer to the other displayed messages to determine
why the open operation has failed. Correct the
v If you have entered a file name ensure that the file
name is correct and that it exists.
ANR8550E
Error opening filespec.

open operation.
User response:
ANR8550E (HP-UX) Error opening file name.
Explanation: An error occurs while the server
attempts a file open operation.
User response:
ANR8550E (Linux) Error opening file name.
User response:
551
ANR8550E (Solaris) ANR8552E

ANR8550E (Solaris) Error opening file name.
User response:
ANR8550E (Windows) Error opening filespec.
attempting an open operation.
User response:
ANR8551E
An error (error code) occurred during a

write operation.
Explanation: An error occurs while attempting a write

operation.
ANR8551E (Linux) An error (error code) occurred

attempts a write operation.
to determine why the write operation failed; correct the
ANR8551E (Solaris) An error (error code) occurred
to determine why the write operation failed. Correct
the problem and restart the process.
ANR8551E (Windows) An error (error code) occurred
attempting a write operation.
to determine why the write operation has failed.
Correct the problem and restart the process.

ANR8551E

write operation.
Explanation: An error occurs while attempting a write

operation.
ANR8552E

read operation.
Explanation: An error occurs while attempting a read

operation.
to determine why the read operation failed; correct the

ANR8551E (HP-UX) An error (error code) occurred
to determine why the write operation failed. Correct
552
ANR8552E

read operation.
Explanation: An error occurs while attempting a read

operation.
ANR8552E (HP-UX) ANR8553E (Windows)

ANR8552E (HP-UX) An error (error code) occurred
attempts a read operation.
to determine why the read operation failed. Correct the
ANR8552E (Linux) An error (error code) occurred
ANR8552E (Solaris) An error (error code) occurred
to determine why the read operation failed. Correct the
attempting a read operation.
to determine why the read operation has failed. Correct
ANR8553E

be overwritten by DUMPDB operation.

DUMPDB data to be written to it.
System action: The server has detected that the given
overwritten by the requested DUMPDB operation.
DUMPDB operation.
ANR8553E (HP-UX) Device type volume volume name

cannot be overwritten by DUMPDB
operation.
volume already contains data that would be
DUMPDB operation, or specify a different volume
name.
ANR8553E (Linux) Device type volume volume name
operation.
name.
ANR8553E (Solaris) Device type volume volume name
operation.
name.
ANR8553E (Windows) Device type volume volume
name cannot be overwritten by
DUMPDB operation.
553

DUMPDB operation.
ANR8554W
Dump/load command: Device class device

class name not defined. Devtype of FILE
is assumed.
Explanation: The specified device class name is not

defined with the DUMPLOADDB DEVCLASS option,
to the server in the server options file or the server is
not able to define the specified device class.

System action: Processing continues. The dump/load
process assumes the device class is devtype=FILE and
writes to or reads from a file.
to determine why the device class is not defined.
Correct the problem and restart the command if you do
not wish to write to or read from a file.

ANR8554W (Solaris) Dump/load command: Device

class device class name not defined.
Devtype of FILE is assumed.


ANR8554W
Dump/load command: Device class device

class name not defined. Devtype of FILE
is assumed.



ANR8555E

Explanation: An error occured while attempting a

read from disk.
ANR8554W (HP-UX) Dump/load command: Device

class device class name not defined.
Devtype of FILE is assumed.
Error error code (error string) occurred

during a read operation from disk disk
name.

User response: Correct the problem and start the
process again.
ANR8555E

name.

read from disk.
process again.
ANR8555E (HP-UX) An error (error code, error string)
occurred during a read operation from
disk disk name.
ANR8554W (Linux) Dump/load command: Device class

device class name not defined. Devtype of
FILE is assumed.

read from disk.

User response: Correct the problem and restart the

process.
554
ANR8555E (Linux) ANR8557W

ANR8555E (Linux) An error (error code, error string)
disk disk name.
ANR8556E (HP-UX) An error (error code, error string)

occurred during a write operation to
disk disk name.

read from disk.

write to disk.

process.

process.
ANR8555E (Solaris) An error (error code, error string)

disk disk name.
ANR8556E (Linux) An error (error code, error string)

disk disk name.

read from disk.

write to disk.

process.

process.

name.
ANR8556E (Solaris) An error (error code, error string)

disk disk name.

read from disk.

write to disk.

process.

process.
ANR8556E

during a write operation to disk disk
name.

name.

write to disk.

write to disk.

process.

process.
ANR8556E

name.

write to disk.
process.
ANR8557W
Retrying failed I/O operation for disk

disk name, errno errno.
Explanation: An error occured while attempting an

I/O operation on a disk volume. The request will be
retried.
System action: The failed I/O operation is attempted
again.
User response: Correct the problem being reported to
avoid more errors in the future, or contact z/OS
support for assistance.
555
ANR8557W ANR8571E (Solaris)

ANR8557W
Retrying failed I/O operation for disk

disk name, error number number.
Explanation: An error occured while attempting an

I/O operation on a disk volume. The request will be
retried.
System action: The HTTPS COMMMethod is not

initialized.
User response: Ensure server has access to keyring file
and password. Re-start the server.
System action: The failed I/O operation is attempted

again.
ANR8570E (Solaris) HTTPS Initialization failed. No

keyring file or keyring password were
specified.
User response: Correct the problem being reported to

avoid more errors in the future, or contact AIX support
for assistance.
Explanation: HTTPS required keyring file and keyring

password are not found.
ANR8558E
I/O vector element bufP: buffer address,

len: buffer length, offset: file offset, errno:
errno.
Explanation: This is a diagnostic message showing

details of an AIO request which had an error. This
message is normally proceeded by ANR8555E or
ANR8556E and offers additional information related to
the I/O error.

initialized.
ANR8570E (Windows) HTTPS Initialization failed.
No keyring file or keyring password
were specified.


process again.

initialized.
ANR8558E
I/O vector element bufP: buffer address,

len: buffer length, offset: file offset, errno:
errno.
Explanation: This is a diagnostic message showing

details of an AIO request which had an error. This
message is normally proceeded by ANR8555E or
ANR8556E and offers additional information related to
the I/O error.

ANR8571E (HP-UX) HTTPS Initialization failed. The
keyring file format is invalid.
Explanation: HTTPS required keyring file has an
invalid format.

initialized.

process again.
User response: Keyring file may be corrupted. Obtain

new copy of the keyring file, then re-start the server.
ANR8570E (HP-UX) HTTPS Initialization failed. No

specified.
ANR8571E (Linux) HTTPS Initialization failed. The

Explanation: The HTTPS required keyring file and

keyring password are not found.
initialized.
User response: Ensure server has access to the keyring
file and password. Restart the server.
ANR8570E (Linux) HTTPS Initialization failed. No
specified.

invalid format.
initialized.
ANR8571E (Solaris) HTTPS Initialization failed. The
invalid format.
initialized.
556
ANR8571E (Windows) ANR8574E (HP-UX)

The keyring file format is invalid.
invalid format.
initialized.
keyring file password is invalid.
Explanation: An invalid password was specified for
the HTTPS keyring file.
initialized.
User response: Obtain the correct password for the
keyring file. Then re-start the server.
initialized.
initialized.
ANR8572E (Windows) SSL Initialization failed. The
ANR8573E (HP-UX) HTTPS Initialization failed. I/O

error occurred reading the keyring file.
Explanation: An unknown I/O error occurred reading
the keyring file.
initialized.
ANR8573E (Linux) HTTPS Initialization failed. I/O
the keyring file.
initialized.
ANR8573E (Solaris) HTTPS Initialization failed. I/O
the keyring file.
initialized.
I/O error occurred reading the keyring
file.
the keyring file.
initialized.
ANR8574E (HP-UX) HTTPS Initialization failed.
Could not open the the keyring file.
Explanation: The keyring file could not be found or
did not allow access.
System action: SSL is not initialized.

initialized.

User response: Ensure the keyring file is present and

has read access allowed. Then re-start the server.
557
ANR8574E (Linux) ANR8576E (Solaris)

ANR8574E (Linux) HTTPS Initialization failed.
initialized.
ANR8574E (Solaris) HTTPS Initialization failed.
initialized.
initialized.
specified certificate within the keyring
file has expired.
Explanation: The default or specified certificate within
the keyring file has expired.
initialized.
User response: The certificate must be renewed and
re-instated into the keyring file. Then re-start the server.
file has expired.

file has expired.
initialized.
The specified certificate within the
keyring file has expired.
initialized.
specified cert within the keyring file has
as an invalid distinguished name.
Explanation: The distinguished name for the specified
cert is invalid.
initialized.
User response: Ensure the correct keyring has been
specified and that the keyring contains the correct
distinguished name. Then re-start the server.
cert is invalid. access.
initialized.

initialized.



cert is invalid.
initialized.
558
ANR8576E (Windows) ANR8580E (Windows)

The specified cert within the keyring
file has as an invalid distinguished
name.
ANR8578E (Windows) The Tivoli Storage Manager

database does not have a password for
the SSL key ring file.
failed. Connections to SSL ports will not be possible.

cert is invalid.
User response: Delete the keyring file so that TSM can

generate a new one.

initialized.
ANR8579E

ANR8577E
Tivoli Storage Manager was not able to

open the SSL keyring file file name. The
GSKit return code is return code.

User response: Verify that the correct SSL keyring file
is in the server instance directory. If the problem
persists then delete the keyring file and run the
DELETE KEYRING server command so that the server
can generate a new keyring file.
The SSL key ring file does not exist, but

the Tivoli Storage Manager database
contains a password for it.

User response: Restore a copy of the key ring file or
use DELETE KEYRING so that Tivoli Storage Manager
can generate a new keyring file and password.
ANR8579E (Windows) The SSL key ring file does
not exist, but the Tivoli Storage
Manager database contains a password
for it.
ANR8577E (Windows) Tivoli Storage Manager was

not able to open the SSL keyring file file
name. The GSKit key management
User response: Restore a copy of the key ring file or

use DELETE KEYRING so that Tivoli Storage Manager
can generate a new keyring file and password.

ANR8580E
An SSL write error occurred on session

session. The GSKit return code is gsk
return code.
User response: Verify that the correct SSL keyring file

is in the server instance directory. If problem persists
then delete the keyring file and run the DELETE
KEYRING server command so that Tivoli Storage
Manager can generate a new one.
Explanation: An error occurred during an SSL write

operation.
ANR8578E
ANR8580E (Windows) An SSL write error occurred

on session session. The GSKit return
code is gsk return code.
The Tivoli Storage Manager database

does not have a password for the SSL
key ring file.

User response: Retry the operation.

Explanation: An error occurred during an SSL write

operation.
User response: Delete the keyring file so that TSM can

generate a new one.
559
ANR8581E ANR8586E
ANR8581E
An SSL read error occurred on session

session. The GSKit return code is gsk
return code.
configured for SSL and retry the operation.

ANR8584I
Explanation: An error occurred during an SSL read

operation.

port port number.

port number.
ANR8581E (Windows) An SSL read error occurred on

session session. The GSKit return code is
gsk return code.
Explanation: An error occurred during an SSL read
operation.


port number.
ANR8582E
An SSL open socket error occurred on

session session. The GSKit return code is
gsk return code.
Explanation: An error occurred during an SSL socket

open operation.

ANR8585I

ANR8582E (Windows) An SSL open socket error
occurred on session session. The GSKit
Explanation: An error occurred during an SSL socket
open operation.
ANR8583E
An SSL socket initialization error

occurred on session session. The GSKit
Explanation: An error occurred during an SSL

handshake process.

ready for connection with administrative

administrative clients on port port
number.

User response: Verify that the client is properly
configured for SSL and retry the operation.
ANR8583E (Windows) An SSL socket initialization
error occurred on session session. The
GSKit return code is gsk return code.
Explanation: An error occurred during an SSL
handshake process.
User response: Verify that the client is properly
560
ANR8586E
The server was not able to create the

keyring file file name. The GSKit key
management return code is return code.

User response: Verify that permissions to the server
instance directory are correct.
ANR8586E (Windows) ANR8675E

ANR8586E (Windows) The server was not able to
create the keyring file file name. The
GSKit key management return code is
return code.
ANR8589E

Explanation: The GSKit key management subsystem

could not be initialized.

User response: Verify that permissions to execute the

GSKit key management dynamic-link libraries are
correct.
ANR8587E
The server was not able to create the

SSL self-signed certificate. The GSKit
key management return code is return
code.

User response: Check the GSKit return code and take
appropriate action.
create the SSL self signed certificate.
The GSKit key management return code
is return code.
The server was not able to initialize the

GSKit key management environment.
The GSKit key management return code
is return code.

initialize the GSKit key management
environment. The GSKit key
management return code is return code.
Explanation: The GSKit key management subsystem
could not be initialized.
User response: Verify that permissions to execute the
GSKit key management dll are correct.
ANR8590I
Session session connection is using SSL

version SSL version cipher specification
cipher specification.

Explanation: An SSL connection has been established

using the listed SSL version and cipher specification.
User response: Check the GSKit return code.
ANR8588E
ANR8590I (Windows) Session session connection is

using SSL version SSL version cipher
specification cipher specification.
The server was not able to export to the

SSL public certificate file file name. The
GSKit key management return code is
return code.
Explanation: The certificate export file could not be

generated for use by the Storage Manager clients.
export to the SSL public certificate file
file name. The GSKit key management
Explanation: The certificate export file could not be
generated for use by the Storage Manager clients.
Explanation: An SSL connection has been established

using the listed SSL version and cipher specification.
ANR8591E (Windows) IBM GSKIT version 7 must
be installed on the system.
Explanation: The server requires IBM GSKit version 7.
User response: Install IBM GSKIT version 7 and
restart the server.
ANR8675E
File name with environment variable

DSMSERV_DIR: File already exists for
File or Filetext Exit.
Explanation: The specified file already exists and the

file-exit option was set to PRESERVE.
561
ANR8675E ANR8677E (Linux)

System action: Server continues running.
ANR8677E
User response: Specify a non-existent file.

ANR8675E
File name: File already exists for File or

Filetext Exit.
Server cannot load user module module

name. z/OS system error error number.
Explanation: The server was unable to load the

module specified. The module is not a properly
compiled and linked dynamic module.

System action: Server initialization stops or server

continues running if already up.
User response: Use the server supplied sample

makefile and export files to compile-link the user
module. Make sure the export.ref file contains the
server-defined function name, and the module actually
contains the server-defined function name, with one
void parameter declared.

ANR8675E (HP-UX) File name with environment variable
File or FileText Exit.
User specified module: Cannot load into

server, AIX system error number number.

ANR8677E

C-compiled and linked dynamic module.

ANR8675E (Linux) File name with environment variable
File/FileText Exit, overwrite option not
set to YES.
overwrite option was not set to Yes.
User response: Specify another file or set the
overwrite option to YES in the server options file.
ANR8675E (Solaris) File name with environment variable
File/FileText Exit, overwrite option not
set to YES.
overwrite option was not set to Yes.
User response: Specify another file or set the
overwrite option to YES in the server options file.
ANR8675E (Windows) File name with path within
registry.: File already exists for File or
FileText Exit.
File/FileText exit option was set to PRESERVE.

makefile and export files to compile-link the user-exit
ANR8677E (HP-UX) User specified module, with
environment variable DSMSERV_DIR:
Cannot load into server, system errno =
Error number generated by HP-UX.
ANR8677E (Linux) User specified module, with
Error number generated by Solaris.
562
ANR8677E (Solaris) ANR8678E (Solaris)

User response: Use the supplied sample makefile, c ,
and h files to generate the user-exit module. Make sure
the module contains product-defined function name
adsmV3UserExit, and the module actually contains the
product-defined function name, with one void *
parameter declared, and returns void.

contains the server-defined function name, with 1 void
parameter declared. The module may contain a global
variable name that conflicts with the servers.
ANR8677E (Solaris) User specified module, with

Error number generated by Solaris.
ANR8678E (HP-UX) Cannot bind User specified

module, with environment variable
DSMSERV_DIR into server, system errno
= Error number generated by HP-UX.

Explanation: The server was unable to bind with the

module specified.

makefile, c, and h files to generate the user-exit
module. Make sure the module contains server-defined
function name adsmV3UserExit, and the module
actually contains the server-defined function name,
with one void * parameter declared, and returns void.
ANR8677E (Windows) User specified module, with path
within registry: Cannot load into server,
system errno = Error number generated by
Windows.
makefile compile-link the user-exit module.
ANR8678E
Error number error number, writing to a

type (devtype) FILE volume volume name,
writing bytes written of bytes attempted
bytes .
Explanation: The server was not able to complete a

write operation to a volume of type (devtype) FILE.
Out of space conditions can cause this problem.
System action: The server fails the current operation.
User response: Check the job log for associated TSM
or system messages. Correct any problems. If the
problem persists, contact IBM Support.
ANR8678E
Cannot bind User specified module into

server. AIX system error number.

module specified.

void parameter declared. The module may contain a
global variable name that conflicts with the servers.
ANR8678E (Linux) Cannot bind User specified module,
with environment variable DSMSERV_DIR
into server, system errno = Error number
generated by Solaris.
module specified. The server could not find a function
named adsmV3UserExit in the module.
User response: Use the supplied sample makefile, c
and header files to create the user exit module. Make
sure the shared library module contains a function
named adsmV3UserExit of type void, with one
parameter of a void *.
ANR8678E (Solaris) Cannot bind User specified module,
with environment variable DSMSERV_DIR
into server, system errno = Error number
module specified. The server could not find a function
named adsmV3UserExit in the module.
makefile, c and header files to create the user exit
module. Make sure the shared library module contains
a function named adsmV3UserExit of type void, with
one parameter of a void *.

563
ANR8678E (Windows) ANR8680W (HP-UX)

ANR8678E (Windows) Cannot find/set User specified
function name within DLL. in User specified
DLL library name, with registry path,
system errno = Error number generated by
Windows.
Explanation: The server was unable to find and/or
bind with the function name in the DLL specified.
makefile to compile-link the user-exit module. Make
sure there is a function name in the DLL as specified in
the server options file. Make sure the function only
accepts one argument, a void pointer.
ANR8679E
Error number error number, closing a

type (devtype) FILE volume volume name.
User response: The server should be stopped at the

earliest possible time before the user exit is to be
reactivated.
ANR8679W (Solaris) Unable to unload user exit
module: system errno = Error number
Explanation: The server was not able to unload the
user-exit module.
User response: The server should be stopped at the
earliest possible time before the user exit is to be
reactivated.
ANR8679W (Windows) There is already an user-exit
loaded.
Explanation: The server received an error during a

close operation on a volume of type (devtype) FILE.
This may be the result of a previous error.
Explanation: There was a previous successful load of

an user-exit module, thus server cannot load another
one.
System action: The server continues.
User response: Check the job log for associated TSM

or system messages. Correct any problems. If the
problem persists, contact IBM Support.
User response: To load a new user-exit module, halt

the server and then restart the server with the new
user-exit module.
ANR8679W
ANR8680W
A user-exit module is already loaded.
Explanation: A user-exit module was loaded

previously. Another user-exit module cannot be loaded.
System action: Server initilization stops or server
user-exit module.
ANR8679W (HP-UX) There is already an user-exit
loaded.
one.
User response: To load a new user-exit module, the
server must be halted and then restart the server with
the new user-exit module.
There is already a file used for the file

or filetext exit.
Explanation: There was a previous file open for the

file or filetext exit. The server cannot open another one.
User response: To start a new file for the file or
filetext exit, halt the server, then restart the server with
the new file name.
ANR8680W
A file used for the file or filetext exit is

already opened.
Explanation: A file for the file or filetext exit was

previously opened. The server cannot open another
one.
the new file name.
ANR8679W (Linux) Unable to unload user exit

module: system errno = Error number
ANR8680W (HP-UX) There is already a file used for

the file or filetext exit.
Explanation: The server was not able to unload the

user-exit module.


564
ANR8680W (Linux) ANR8682E

a new file name.
ANR8680W (Linux) There is already a file used for
the file or filetext exit.
User response: To start a new file for the exit, halt the
server, then restart the server with a new file name.
ANR8680W (Solaris) There is already a named file
used for the file or filetext exit.
User response: To start a new file for the file or the
a new file name.
ANR8680W (Windows) There is already a file used
for the file or filetext exit.
ANR8681I (HP-UX) Connected to Tivoli event server

at node name on port port.
Explanation: The server successfully established a
connection with the Tivoli event server on the specified
node name and port.
System action: The server sends events to the Tivoli
event server using this connection.
ANR8681I (Linux) Connected to Tivoli event server
node name and port.
ANR8681I (Solaris) Connected to Tivoli event server
node name and port.

User response: To start a new file for the exit, halt the
server, then restart the server with a new file name.
ANR8681I
Connected to Tivoli event server at node

name on port port.

node name and port.
ANR8681I
Connected to Tivoli event server at node

name on port port.

node name and port.
ANR8681I (Windows) Connected to Tivoli event

server at node name on port port.
node name and port.
ANR8682E
Unable to determine port of Tivoli event

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.
System action: Event logging to the Tivoli event
server is disabled.
User response: Ensure that the Tivoli event server is
running on the specified system. If the system on
which the event server is running does not support the
TCP/IP Portmapper, then ensure that TECPORT is
565
ANR8682E ANR8683E (HP-UX)

ANR8682E
Unable to determine port of Tivoli event

server on node node name.
ANR8682E (Windows) Unable to determine port of

Tivoli event server on node name.

TCP/IP port for the Tivoli event server on node node
name.

name is listening.

server is disabled.

server is disabled.


ANR8682E (HP-UX) Unable to determine port of

ANR8683E

name is listening.
Explanation: The server was unable to establish a

TCP/IP connection with the Tivoli event server on node
name at port port.

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 (Linux) Unable to determine port of

name is listening.
server is disabled.
ANR8682E (Solaris) Unable to determine port of
name is listening.
server is disabled.
566
ANR8683E
Unable to connect to the Tivoli event

server at node name on port port.

server at node node name on port port.

TCP/IP connection with the Tivoli event server on
node node name at port port.
server is disabled.
correct.
ANR8683E (HP-UX) Unable to connect to the Tivoli
event server at node name on port port.
name at port port.
server is disabled.
ANR8683E (Linux) ANR8684E (Linux)

correct.
User response:
ANR8683E (Linux) Unable to connect to the Tivoli

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.

name at port port.
server is disabled.
correct.
ANR8683E (Solaris) Unable to connect to the Tivoli
name at port port.
server is disabled.
correct.
ANR8683E (Windows) Unable to connect to the
Tivoli event server at node name on port
port.
name at port port.
server is disabled.
correct.
ANR8684E

server because TCP/IP is not available.

TCP/IP connection with the Tivoli event server because
TCP/IP services were not available.
server is disabled.
v Ensure that COMMMETHOD TCPIP is specified in

ANR8684E

server because TCP/IP is not available.

server is disabled.
User response:
v Ensure that COMMMETHOD TCPIP is specified in
v If COMMMETHOD TCPIP was specified, use the
ANR8684E (HP-UX) Unable to connect to the Tivoli
event server because TCP/IP is not
available.
server is disabled.
User response:
v Ensure that COMMMETHOD=TCPIP is specified in
the server options file, or that
COMMMETHOD=NONE is not specified.
v If COMMMETHOD=TCPIP was specified, use the
ANR8684E (Linux) Unable to connect to the Tivoli
available.
server is disabled.
User response:
567
ANR8684E (Solaris) ANR8689I


ANR8686I
Core dump successfully generated
ANR8684E (Solaris) Unable to connect to the Tivoli

available.
Explanation: The server has successfully generated the

requested core dump.


server is disabled.
User response:
ANR8684E (Windows) Unable to connect to the
Tivoli event server because TCP/IP is
not available.
server is disabled.
User response:
ANR8685I
Core dump being generated to file core;

dump file
Explanation: The server has started generating a

coredump to the specified file as a result of a user
request.
ANR8685I
Core dump being generated to file core

dump file
Explanation: The server has started generating a

coredump to the specified file as a result of a user
request.
568
ANR8686I
Core dump successfully generated
Explanation: The server has successfully generated the

requested core dump.
ANR8687E
Error generating core dump, system

error number error number.
Explanation: The server was unable to generate the

requested core dump. The error number indicates the
reason z/OS was unable to complete the request.
ANR8687E
Error generating core dump, errno system

errno.
Explanation: The server was unable to generate the

requested core dump. The errno indicates the reason
AIX was unable to complete the request.
ANR8688W
There is already an user-exit loaded.

one.
System action: Server initilization stops or server
user-exit module.
ANR8689I
Product registration for owner product

name Vversion.release.modification pid.
Explanation: The server has registered for subcapacity

pricing.
ANR8740W ANR8748I
ANR8740W
Number of automated library slots (slots

in use) exceeds license terms (slots
licensed).
Explanation: The number of slots in use within

automated libraries exceeds the licensed value.
System action: The operation completes.
User response: Contact your service representative to
update license values for slots in automated libraries,
or reduce the number of slots in use by issuing
CHECKOUT LIBVOLUME commands as necessary.
ANR8741E
CHECKIN LIBVOLUME not permitted

with current license terms.
Explanation: The CHECKIN LIBVOLUME operation is

not permitted because the current license terms do not
allow it.
update license values for slots in automated libraries,
or reduce the number of slots in use by issuing
CHECKOUT LIBVOLUME commands as necessary.
ANR8744E
Explanation: The specified command failed because

the current license terms do not permit it.
update the server license terms so that the requested
operation can be processed.
ANR8745E
This server is not licensed to support

the device type device type. Device
Support Module module number is
required.
Explanation: A DEFINE DRIVE command or a

volume mount operation cannot be processed because
the server is not licensed to support the required device
type.
Support for the 3590 device type is

disabled for library library name.
Explanation: The requested operation fails because

support for the 3590 device type is not currently
enabled for the specified library.
User response: Make sure the ENABLE3590LIBRARY
option is specified in the server options file, and that
the scratch category number for 3590 volumes does not
conflict with the private category or the CARTRIDGE
volume scratch category.
ANR8746E
ANR8742E
Command: Current license terms do not

permit this operation.
Device type device type is not supported

in this release.
Explanation: The specified device type cannot be used

by this release/platform of the server.
System action: The device cannot be used.
User response: Contact your sales or service
representative to upgrade to the latest release of the
server.

update the server license terms so that support for the
required device type is enabled.
ANR8743E

library device name. Device Support
Module module number is required.
Explanation: Either a DEFINE LIBRARY command, a

volume mount operation, or library initialization cannot
be processed because the server is not licensed to
support the given library.
given library device is enabled.
ANR8747I
Checking in volume volume name in

library library name- CANCEL
PENDING.

CHECKIN LIBVOLUME process on the server. The
given volume was being checked in to the designated
library, but the process was canceled by an
administrator.
System action: The background process operation is in
a wait queue. When the process comes off the queue, it
will be terminated.
ANR8748I
Checking in volumes in search mode in

library library name- CANCEL
PENDING.

CHECKIN LIBVOLUME process on the server. Volumes
were being checked into the given library in search
569
ANR8749E ANR8756E
mode, but the process was canceled by an
administrator.
System action: The background process operation is
being terminated.
ANR8749E
Library order sequence check on library

library name.
Explanation: An attempt has been made to mount or

demount a volume, but the attempt fails for one of the
following reasons:
v Mount is already in progress or a volume is already
mounted.
ANR8752W

library device type. Managed Library
license is required.
Explanation: This message is issued when a DEFINE

LIBRARY command or a volume mount operation uses
a device class that is not licensed on the server.
System action: The operation fails if this is a
try-and-buy server. For purchased servers, this message
is to warn you that you are not in compliance with
registered license terms.
v Mount is already pending.

v Demount is already pending.
ANR8753W
v Demount was requested but no volume is mounted.

User response: This error usually occurs when a
demount fails and a cartridge is left in the drive. All
subsequent mounts fail while attempting to insert
another cartridge into the same drive. Demount the
cartridge using the library manager or perform an
AUDIT LIBRARY operation on the designated library.
Retry the operation.
ANR8750E
Volume is incompatible with specified

device type in library library name.
Explanation: An attempt has been made to mount or

check in a volume, but the attempt fails because the
cartridge being mounted is not compatible with the
drive (For example, attempting to mount a 3590
cartridge on a 3490 drive).

library library name. Library Sharing is
required.

LIBRARY command or library initialization for a
library that requires library sharing and library sharing
is not licensed on the server.
ANR8754E
Command: There is already a request to

delete library libary name.

or updated because there is a request to delete the
library already.
User response: Ensure the DEVTYPE parameter on

the CHECKIN command matches the device type of
the drive. Retry the operation.
ANR8751W
ANR8755E

the device type device type. Managed
Library license is required.

DRIVE command or a volume mount operation uses a
device class that is not licensed on the server.

update library library name.

because there is a request to update the library already.
ANR8756E
For optical libraries, you must specify

CHECKLABEL=YES.
Explanation: Optical libraries require the

CHECKLABEL parameter to be set to YES
570
ANR8757W ANR8766I
CHECKLABEL=YES option.
ANR8757W

command.

library device type. Extended Edition
license is required.

LIBRARY command or a volume mount operation uses
a device class that is not licensed on the server.
ANR8764E


since the requested operation is not allowed for
libraries of the given type.


ANR8765I
ANR8760I
Cancel in progress.
Explanation: The MOVE MEDIA command has been

for a MOVE MEDIA command.
ANR8761I
Explanation: The MOVE MEDIA command has

processed the number of volumes displayed. This
PROCESS command for a MOVE MEDIA command.
ANR8762I
Number of volumes processed: number.

Ejecting volume volume name from
Explanation: The MOVE MEDIA command displays

the number of volumes already processed and the
name of the volume currently being ejected from the
indicated library. This message may be displayed in
response to a QUERY PROCESS command for a MOVE
MEDIA command.
ANR8763E

processed: library library name not
defined.

since the designated library has not been defined or has
been deleted.

processed: the operation is not allowed
for library type library type.

name in location location name is required
for use in library library name; CHECKIN
LIBVOLUME required within time limit
minutes.
Explanation: A mount request has been made for a

volume that is defined in a storage pool, but which is
currently checked out of the given library and stored in
the location shown.
System action: The server waits until it detects that
the volume has been checked into the library, or the
time limit expires.
User response: Obtain the required volume from the
indicated location, and insert it into the library by
issuing a CHECKIN LIBVOLUME command. Use the
SWAP=YES option of the CHECKIN LIBVOLUME
command if the library is currently full; this process
allows the server to select an appropriate volume to be
swapped out in order to make room for the required
volume.
ANR8766I
MOVE MEDIA command: CHECKOUT

LIBVOLUME command for volume volume
successfully; Place the ejected volume in
location location name.
Explanation: The CHECKOUT LIBVOLUME operation

has completed successfully for the indicated volume in
the given library. Place the ejected volume in the
indicated location.
library inventory (if its status is something other than
User response: If an *UNKNOWN* location is
displayed, issue UPDATE STGPOOL OVFLOCATION
command to define an overflow location name to be
used on the subsequent MOVE MEDIA command. For
the volumes ejected with an *UNKNOWN* location,
use UPDATE VOLUME LOCATION command to
update its location to your overflow location name.
571
ANR8767I ANR8774W
ANR8767I

volumes processed. Volumes sent to library
library name for checkout: number volumes
sent.
Explanation: The MOVE MEDIA command has

processed the number of volumes shown. Currently, the
MOVE MEDIA command has sent for processing the
number of volumes shown to the library shown. This
PROCESS command for a MOVE MEDIA command.
ANR8768E
File file name on volume drive name could

not be found.
Explanation: The server was unable to find the

specified file name on the indicated volume. For
removable file device classes, each volume maintains
data using a file name which is the same as the volume
name and the label value on the volume.
User response: Ensure that the proper volume has
been placed into the drive. If you are creating a
removable file device class volume by copying data
from a FILE device class volume, the media must have
a label which is the same as the volume name. The file
which is copied to the volume must be renamed to
have the same name as the label.
ANR8769E
External media management function

request type returned result=result.
Explanation: A request of the indicated function type

was sent to the external library manager program,
which returned a result code which was not SUCCESS.
System action: The server continues, but the server
operation that was being attempted fails.
User response: Consult the documentation for the
external media management program to determine how
to recover from the error condition. Then attempt the
server operation again.
ANR8770W
Unable to load external library manager

filespec.
Explanation: A library of LIBTYPE=EXTERNAL is

defined but the server cannot load the external library
manager.
System action: The server continues, but the external
library cannot be accessed.
User response: Verify that the EXTERNALMANAGER
parameter for the external library is specified correctly
on the DEFINE LIBRARY or UPDATE LIBRARY
command.
572
ANR8771E
Volume volume name in library library

name is deleted. External Library is not
synchronized with the server. Audit
required.
Explanation: The server deleted a volume from its

inventory, and its attempt to inform the external library
manager has failed.
System action: The server may continue to access the
library, but some volumes may not be accessible until
the external library is synchronized with the server.
User response: Perform the appropriate type of
processing on the external library in order to
synchronize it with the server.
ANR8772I
Moving volume volume name (if known)

from drive drive name to slot slot element
number in library library name.
Explanation: A volume found in the drive during

library initialization is being moved to the slot.
System action: The volume is moved from the drive
to the slot.
ANR8773E
Incompatible options
CHECKLABEL=NO and SEARCH=YES
for SCSI libraries.
Explanation: If a barcode reader is not installed and

detected by the server, the server requires the ability to
check the tape label when searching for new volumes
in a SCSI tape library. The CHECKLABEL=NO and
SEARCH=YES parameters on the CHECKIN LIBVOL
command are not compatible.
User response: Reissue the CHECKIN LIBVOL
command and specify CHECKLABEL=YES.
ANR8774W
Volume volume name not checked into

library library name but is using category
category number.
Explanation: While processing a DEFINE LIBRARY or

AUDIT LIBRARY command for the given library, the
server found a volume that was not checked into the
library (with the CHECKIN LIBVOL command), but is
assigned to one of the categories in use by that library.
System action: If the volume category equals the
value of the library SCRATCHCAT the category is
changed to the value of the library PRIVATECAT. This
is to prevent the library from loading the volume when
a scratch volume is requested.
User response: If the volume is to be used by the
server, it does not have to be reassigned but it must be
checked into the library with the CHECKIN LIBVOL
ANR8775I ANR8779E
command. If the volume is not to be used by the
server, use the mtlib program to reassign the volume to
its correct category. For details about the mtlib
program, refer to the documentation provided with the
library device.
ANR8775I
Drive drive name unavailable at library

manager.
Explanation: The specified drive availability status at

the library manager has changed from available to
unavailable.
System action: The drive status on the server is
updated to reflect the availability to that of the library
manager. The drive will not be considered as a
candidate for the mount or demount request.
determine the cause of the drive becoming unavailable.
Once the service representative has determined the
cause and changed the availability status to available at
the library manager, the server will resume use of the
drive.
ANR8776W
Volume volume name in drive drive name

contains lost VCR data; performance
may be degraded.
Explanation: The Vital Cartridge Records of the

cartridge in the drive are lost or corrupted. This results
in the inability of the drive to do fast locates to file
positions on the cartridge, which causes the locate
performance for read or append operations to become
degraded.
System action: The server continues the operation.
User response: There are two methods to restore the
VCR data. The first method uses the MOVE DATA
command to move the data off the tape and to return
the tape to scratch or empty status. The VCR data is
rebuilt when the empty tape is rewritten from the
beginning-of-tape. The second method rebuilds the
VCR by loading the tape and locating directly to the
end-of-data. This is done by the server in normal use
when new data is appended to the end of the tape. It
can also be done independent of the server by loading
the tape in an unused drive and using the tapeutil
program. Select the tapeutil option Space to
End-of-Data.
ANR8777E
Mount for volume volume name failed;

media performance is degraded.
Explanation: The VCR data on the volume is lost or

corrupted, resulting in degraded tape positioning. The
mount fails because the tape drive was configured to
fail mounts that indicate this condition.
the user can issue the UPDATE VOLUME command to

make the volume unavailable. There are two methods
to restore the VCR data. The first method uses the
MOVE DATA command to move the data off the tape
and to return the tape to scratch or empty status. The
VCR data is rebuilt when the empty tape is rewritten
from the beginning-of-tape. The second method
rebuilds the VCR by loading the tape and locating
directly to the end-of-data. This is done by the server in
normal use whenever data is appended to the end of
the tape. It can also be done independent of the server
by loading the tape in an unused drive and using the
tapeutil program. Select the tapeutil option Space to
End-of-Data.
ANR8778W
Scratch volume volume name changed to

Private Status to prevent re-access.
Explanation: The scratch volume encountered an error

during mount processing that makes it unusable. The
status of the volume is changed to private so that it is
not selected for future scratch mounts. (Although the
status has become private, it is not defined to a storage
pool.)
System action: Processing continues with another
scratch volume.
User response: See previous error messages to
determine the cause of the mount failure, and correct
the problem. If the problem is a mislabeled volume or
unreadable label, relabel the scratch volume using the
dsmlabel utility with the -overwrite option. If the
volume is missing from its home slot, issue the AUDIT
LIBRARY command against the library. If the volume
has lost or corrupted VCR-data, relabel the volume.
(This reinitializes the VCR-data by writing to the
volume from beginning-of-tape.) Once the problem is
corrected, update the status of the volume to scratch by
using the UPDATE LIBVOL command.
ANR8779E
Unable to open drive drive name, error

number=errno value from open system call.
Explanation: The drive cannot be opened by the

server. In AIX, error number is the value of errno
returned by the operating system. In OS/2, it is the
value of the return code from the call to DosOpen.
System action: The transaction needing the drive fails.
User response: Use the error number in conjunction
with operating system documentation to narrow the
scope of the cause. Inspect the drive. Ensure the drive
is powered on and ready, the cables are properly
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.
User response: Until the VCR data can be restored,
573
ANR8780E ANR8787W
ANR8780E
Volume in drive drive name has no label.
Explanation: The volume in the indicated drive does

not have a label. The server requires that all media be
uniquely labeled.
System action: The volume is rejected and the server
prompts for a new volume.
User response: Use the appropriate labeling utility to
label the media. In OS/2 and Windows NT, the LABEL
command is used to label removable disk cartridges,
diskettes and other media which appear as drive
letters.
ANR8781E
Volume in drive drive name has invalid

label label.
Explanation: The volume in the indicated drive has

the label shown. The name does not conform with
server requirements. The server requires that all media
be uniquely labeled and, for removable media, that the
label with file naming conventions. The label found
exceeded the maximum label size for removable media
or did not conform to server labeling requirements. If
????? is shown for the label, it indicates that server was
unable to read the label.
letters. This label must still conform to server
requirements.
ANR8782E
System action: The operation fails. The access mode of

the volume is changed to UNAVAILABLE.
User response: Ensure that the cartridge is physically
in the library, and reinventory the library. If the volume
location is resolved, restore the access mode of the
volume to its previous value using the UPDATE
VOLUME command.
Label on volume in drive drive name
could not be read.
Explanation: The server was unable to read the label

on the indicated drive.
574
ANR8784E
File file name on volume drive name could

not be created.
Explanation: The server was unable to create the

indicated file on the indicated volume. The server
creates a file on removable media in which to store
data.
User response: Ensure that the media is not defective,
and is properly formatted. Ensure that there are not
large numbers of files already in the root of the file
system. Some file systems have limits on the number of
files that may be created in the root directory.
ANR8785E
Out-of-space in file system for device

type volume volume name.
Explanation: The server detected an out-of-space

condition for the file system in which the given volume
resides.
ANR8786I

accessed by library library name.
Explanation: The designated volume is in the

inventory of the Library Manager, but the physical
location is either inaccessible or unknown.
ANR8783E

letters. This label must still conform to server
requirements.

volume from entry/exit port; insert
volume volume name mount mode into
entry/exit port of library library name
within time limit minute(s); issue
REPLY along with the request ID when
ready.
Explanation: A CHECKIN LIBVOLUME command is

in progress, and the specified volume is needed.
However, there is a volume awaiting to be removed
from the entry/exit port before the specified volume is
inserted into the port of the given library.
command is issued.
and insert the correct volume into the entry/exit port.
Issue a REPLY command, along with the request ID, to
tell the server that the volume has been removed and a
new volume has been inserted.
ANR8787W
Unable to read the barcode label(s) in

Explanation: A command is issued with the

CHECKLABEL=BARCODE option. The library is
unable to detect that the cartridges have valid barcode
labels. The barcode reader is disabled or it is unable to
read the labels.
ANR8788W ANR8795I
System action: Unless the command is checking in
cleaning cartridges, the process continues by loading
the cartridges into the librarys drives and reading the
label from the tape. Cleaning cartridges have no
internal label that can be checked by loading it in the
drive.
User response: Cancel the process if you do not want
to load all of the cartridges into the librarys drives.
Examine the cartridges to ensure they have barcode
labels and they are compatible with the barcode reader.
Not all vendors labels are readable by all libraries.
Check that the barcode reader is configured and
functioning properly, if necessary.
ANR8791E
Explanation: Dynamic drive recovery was being

attempted on the volume, but was unable to move the
volume to another drive.
System action: The originating process terminates.
determine the cause of the DDR failure, and correct the
problem. If the problem is an unreadable label, any
data on the volume may be lost.
ANR8792E
ANR8788W
Unable to read the barcode of cartridge

in slot-id Element number of slot in library
library name; loading in drive to read
label.
Unable to move device type volume

volume name to another drive.
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.
Explanation: The library barcode reader is unable to

read the label of a tape cartridge. The cartridge is
found in the slot with the given element number.
User response: Service the drive for failures. Delete

and redefine the drive to bring it back online.
System action: The cartridge is loaded into a drive

and its label will be read from the tape.
ANR8793E
User response: Cancel the process if you do not want

to load any cartridges into the librarys drives. Examine
the cartridge to ensure it has a barcode label and that it
is compatible with the barcode reader. Not all vendors
labels are readable by all libraries. Check that the
barcode reader is configured and is functioning
properly, if necessary.
ANR8789W
Dynamic drive recovery being attempted

on device type volume volume name due to
errors.
Dynamic drive recovery failed for device

type volume volume name because not
enough drives are available.
Explanation: To recover a volume on another drive,

there must be at least one other drive available that is
not associated with the transaction which is driving the
recovery. In addition, the maximum number of drives
that can have dynamic drive recovery performed at the
same time is one less than the number of drives. This is
to prevent deadlock from occurring between two
recovering transactions. One of these criteria has failed.
System action: No DDR is performed and the
transaction fails.
Explanation: Due to a drive or media fault, the server

is moving the volume to a new drive.
User response: Restart the transaction.
System action: Read or write operations resume on

the volume once it is remounted.
ANR8794E

ANR8790I
device type volume volume name

re-mounted in drive drive name.
Explanation: Due to a drive or media fault, the server

has moved the volume to the specified drive. Read or
write operations resume on the volume.
System action: The label of the volume has been
verified.
Retry of operation name operation failed

for device type volume volume name.
Explanation: After successfully mounting the volume

on another drive, due to an I/O error, the original
operation fails when retried.
System action: No further recovery is performed and
the transaction fails.
User response: Restart the transaction.
ANR8795I
Retry of operation name operation for

device type volume volume name is
successful.
Explanation: After mounting the volume on another

drive, due to an I/O error, the operation is tried
successfully.
System action: The transaction continues from the
point of interruption from the failure.
575
ANR8796W ANR8803I
ANR8796W
Drive drive name of library library name is

not online; UPDATE DRIVE required.
Explanation: During the initialization of a library, the

server finds that the drive was updated to be offline.
System action: The drive will not be accessible by the
library during tape operations.
User response: The drive may be made online by
issuing the UPDATE DRIVE command with the
ONLINE=YES option.
ANR8797W
command: Drive drive name of library

library name is inaccessible.

mentioned drive. This may be for the following
reasons:
v The drive cannot be opened.
System action: The drive is temporarily made offline
and is not used for tape operations. The server polls
the drive at one-half minute intervals to check if the
condition has cleared. Once the drives is accessible
again, the drive is brought online.
User response: Determine the reason the drive is
inaccessible, such as hardware errors reported in the
system logs. Render any needed corrections to the
drive. The drive will be brought online automatically
when the polling process detects that is has become
accessible.
ANR8798W
Drive drive name in library library name is

busy; some transactions may fail.
Explanation: The drive being made offline is currently

mounted with an open tape volume. If the transaction
using the volume requires subsequent tape mounts and
is unable to acquire a drive, the transaction will fail.
System action: If this tape volume is one of a
sequence of volumes that are required to process a
transaction, a drive must be available for each mount.
This may be any drive in the library, but if all other
library drives are currently busy and are still busy at
the time the new tape must be mounted, the
transaction will fail.
User response: If possible, make the drive online until
the transaction using it ends. If there is an idle volume
on the drive, dismount the volume first.
576
ANR8799I

Explanation: A LABEL process has been started to

write the label on the specified volume in the given
library. The process is assigned the ID specified in the
message.
to perform the operation in response to the LABEL
command entered by an administrator.
ANR8800I
LABEL LIBVOLUME for volume volume

successfully.
Explanation: The background process to LABEL a

volume has succeeded.
System action: The volumes label has been rewritten.
ANR8801I
LABEL LIBVOLUME process process Id

for library library name completed; count
of labeled volumes volume(s) labeled, count
of checked in volumes volume(s)
checked-in.
Explanation: A search-mode process to LABEL

volumes has succeeded.
System action: The volumes have been labeled.
ANR8802E
LABEL LIBVOLUME process process Id

for library library name failed.
Explanation: The Label process terminated with a

failure.
determine the cause of the failure, and correct the
problem.
ANR8803I
LABEL VOLUME process process Id for

library library name has been canceled;
count of labeled volumes volume(s) labeled,
count of checked in volumes volume(s)
checked-in.

been working to label the volumes for the given library
is canceled by the CANCEL PROCESS command. The
counts provided are for any volumes processed prior to
the cancel.
ANR8804I ANR8811E

parameters.

ANR8808E
ANR8804I
Labeling volume volume name in library

library name.

LABEL process on the server.
System action: The background process continues.
PROCESS command.
ANR8805I
Labeling volumes in library library name;

volume count volume(s) labeled.

command, this message displays the status of a LABEL
process with the SEARCH option.
System action: The background process continues.
Explanation: An attempt was made to overwrite the

label of a volume that is still defined to a storage pool
or is still found in the volume history file. Such a
volume may still contain valid data.
User response: It is usually not necessary to re-label
volumes. If the volume must be relabeled, that volume
must first be removed from the storage pool or volume
history file where it is defined.
ANR8809I

PROCESS command.
ANR8806E
Could not write volume label volume

name on the tape in library library name.
Could not write label label name on the

volume in drive drive name of library
library name because that volume is
already labeled with volume name which
is still defined in a storage pool or
volume history.
Request number: Please provide the label

name for the volume in slot element slot
element number of library library name by
issuing REPLY n LABEL=xxx within time
limit minutes, where n is the request ID
and xxx is the desired label name.
Explanation: A LABEL LIBVOLUME command is in

progress, and the name of the next volume is needed.
Explanation: The Label process could not write the

label on the tape specified.

command is issued.
System action: For a LABEL operation with

SEARCH=YES, the background process continues to the
next volume. For an individual volume, the process
ends. The volume is not labeled and is not checked into
the library.
User response: Issue a REPLY command, along with

the request ID, and the volume name for the next
cartridge.

ANR8807W
Could not write label volume name on

the volume in drive drive name of library
library name because volume is already
labeled existing volume name.
Explanation: The check in or label process could not

write the label on the tape specified because the
volume is already labeled.
System action: The check in process will not overwrite
volumes that are already labeled, and the label process
will only overwrite volumes when OVERWRITE=YES
is specified. The volume is not labeled and cannot be
checked in to the library. If SEARCH=YES, the process
continues to the next volume. For an individual
volume, the process ends.
ANR8810I
Volume volume name has been labeled in

Explanation: The Label process with the search option

has found and labeled a volume.
ANR8811E
Command: The LABELSOURCE

parameter is required when using
SEARCH with this command.
Explanation: The LABELSOURCE parameter must be

provided with the given command.
valid LABELSOURCE parameter value.
577
ANR8812E ANR8819E
ANR8812E
Command: The SEARCH parameter is

required when using LABELSOURCE
with this command.
Explanation: When using the LABELSOURCE option

with this command, the SEARCH parameter must be
also provided.
valid SEARCH parameter value.
ANR8813W
Unable to read the barcode of cartridge

in slot element Element number of slot in

read the label of a tape cartridge. The cartridge is
found in the slot with the given element number.
System action: When LABELSOURCE=BARCODE is
specified on the LABEL LIBVOLUME command,
volumes without a barcode cannot be labeled. When
the VOLRANGE or VOLLIST option is specified on the
CHECKIN LIBVOLUME command, volumes without a
barcode cannot be checked in.
User response: Examine the cartridge to ensure it has
a barcode label and that it is compatible with the
barcode reader. Not all vendors labels are readable by
all libraries. Check that the barcode reader is
configured and is functioning properly, if necessary.
ANR8814I
Remove volume Volume name from slot

element Slot element number of library
Library name.
Explanation: LABEL LIBVOLUME has ended for the

specified volume and that volume must be removed
from the library because either it was not checked in or
there was an error.
ANR8816E

volume cannot be used because there is a storage pool
volume defined or a volume in the volume history file
with this volume name. Such a volume may still
contain valid data. Applying the volume name to the
cartridge can overwrite data and or cause library
inventory corruption. If the volume is in the volume
history file, it has been previously used by for an
export, database dump, database backup operation, or
by a library client (as recorded in the volume history).
System action: If the SEARCH=YES option was
specified, the current volume is skipped and command
processing continues with the next volume found. If
SEARCH=NO was specified, command processing
terminates.
User response: If the volume is present in an
automated library, it should either be removed or
checked into the librarys inventory in the PRIVATE
category.
ANR8817E
ANR8815I
Remove volume Volume name from port

element Port element number of library
Library name.
Explanation: LABEL LIBVOLUME has ended for the

specified volume and that volume must be removed
from the library because either it was not checked in or
there was an error.
System action: The server continues normal operation.
User response: Remove the specified volume from the
library.
Name length for volume Volume name

invalid; max is Maximum name length.
Explanation: During LABEL LIBVOL processing, the

volume name provided to be written on the label
exceeds the maximum length for the type of cartridge.
System action: The label process fails for that
cartridge.
User response: Reissue the LABEL LIBVOL command
and provide a volume name that is not longer than the
maximum listed.
ANR8818E
System action: The server continues normal operation.

User response: Remove the specified volume from the
library.
command: Volume Volume name in library

Library name cannot be labeled because
it is currently defined in a storage pool
or in the volume history file.
I/O Error on library library name; request

for op. operation/function to the 3494
Library Manager has timed out.
Explanation: A command for the operation was issued

to the Library Manager and a response was not
received within the maximum timeout period.
System action: The operation and the transaction fails.
User response: Verify that communications with the
library is operational, that it is online and ready for
commands. Increase the time-out limit of the Library
Manager Control Point device driver. If the problem
persists, provide your service representative with the
3494 Library Manager transaction logs.
ANR8819E
Unable to read the barcode label(s) in

Explanation: A LABEL command was issued with the

LABELSOURCE=BARCODE option. The library was
unable to detect that the cartridges had valid barcode
578
ANR8820W ANR8827E
labels or the library did not have a barcode reader. If a
barcode reader is present the reader might be disabled
or it is unable to read the labels.
System action: Examine the cartridges to ensure they
have barcode labels and they are compatible with the
configured and functioning properly.
ANR8820W
Repairing VCR data for Volume volume

name in drive drive name; dismount may
be delayed.
Explanation: The Vital Cartridge Records of the

cartridge in the drive are lost or corrupted, which
results in the inability of the drive to do fast locates to
file positions on the cartridge. The VCR is being rebuilt
during the volume dismount process in order to avoid
performance degradation on future mounts of the
volume.
System action: The server continues the dismount
operation. There may be a long delay because the VCR
is rebuilt by spacing the tape forward to the
end-of-data.
have not yet been configured to the operating system,

or to the library. The library must have at least one
drive and multiple slots when properly configured in
order to be defined to the server.
User response: Configure the drives to the operating
system, and reinitialize the library.
ANR8824E
Explanation: A command for the operation was issued

to the Library Manager and a response was not
received within the maximum timeout period.
System action: The operation and the transaction fails.
User response: Verify that communications with the
library is operational, that it is online and ready for
commands. If the problem persists, provide your
service representative with the 3494 Library Manager
transaction logs and the request id from the failed
operation.
ANR8825E

ANR8821E
Barcode of element slot element address,

hardware barcode string, exceeds maximum
length characters in length.
Explanation: A barcode is encountered that was

longer than a valid volume name.
System action: The barcode is not considered valid
and will not be used for the server process.
User response: Replace the cartridges barcode with
one that is supported by the library and whose number
of characters does not exceed the maximum length.
ANR8822E
Volume name is not a valid volume

name.
Explanation: The specified string is not a valid

volume name.
System action: The program prompts for a new
volume name.
User response: Enter a volume name that is within
the length constraints for the media type being labeled,
and which contains only alphanumeric characters.
ANR8823E
Hardware configuration error in library

library name: number of drives drives,
number of storage slots storage slots.
Explanation: The library device returned a count of

zero for either the drives or the slots. The drives may
I/O Error on library library name; request

request id for operation operation/function
to the 3494 Library Manager been lost.
Volume range is not a valid volume

range.

volume range.
volume range.
User response: Enter the volume names in the range
that is within the length constraints for the media type
being labeled, and which contains only alphanumeric
characters. The volume names of the beginning and
ending volume must be the same in length and the
incrementals must be in digits.
ANR8826E
No Entry/Exit found on library library

name.
Explanation: A CHECKIN LIBVOLUME

SEARCH=BULK command was issued on a library that
has no Entry/Exit ports.
ANR8827E
No Entry/Exit port is available on

Explanation: A CHECKOUT LIBVOL command was

issued on a library where all its Entry/Exit Ports were
found to be full or inaccessible.
User response: Empty all the entry/exit ports on the
library, close the entry/exit port door, make sure the
579
ANR8828E ANR8835W
ports are accessible, and try the command again.
ANR8828E
Slot element number of library library

ore resolved, contact your support representative.

Return the tape to scratch or dispose of it.
ANR8832E
Explanation: The slot in the library could not be

physically accessed at this time.
CHECKIN LIBVOLUME for volumes in

search mode in library library name
failed.
Explanation: The background process for a CHECKIN

LIBVOLUME command has failed.
User response: Verify that the Entry/Exit door is

closed and the device has not logged any device errors
before trying the command again.
System action: The background process ends, but

volumes have not been checked into the library.
ANR8829I
Remove volume volume name from slot

element number of library library name at
your convenience.
Explanation: A volume has been checked out from the

library and placed in a multiple entry/exit port library.
The volume needs to be removed from the library, but
the operation is not critical.
User response: Remove the volume from the
entry/exit slot.
ANR8830E
Internal Device type drive diagnostics

detect excessive media failures for
volume Volume name (MIM MIM Code).
Access mode is now set to read-only.
Explanation: The tape drives microcode performed an

analysis of the media during the prior mount of the
volume and determined that the number of temporary
errors and other indicators exceed the threshold for
reliable data recording.
System action: The volume is made read-only.
User response: Check system error logs for entries
made by the device relative to media errors. It is
recommended to move the data off the volume in order
to minimize the impact of future errors and further
damage to the media.
ANR8831W
Because of media errors for volume

Volume name, data should be removed as
soon as possible.
Explanation: Errors previously encountered on the

volume leave the access to the data in a questionable
state. The errors may be permanent temporary media
failures such as the corruption of the Volume Control
Region of a Magstar drive.
User response: Move the data off the volume. This
can be done with the MOVE DATA command. In some
cases the tape is reusable by returning it to scratch.
Check system error logs for entries made by the device
relative to media errors. If the errors cannot be isolated
580

ANR8833E

library name is currently being checked
in or checked out.

because the specified volume is being checked in or
checked out of the library.
User response: Wait until the conflicting checkin or
checkout has completed, and then reissue the
command.
ANR8834E
Library volume volume name is still

present in library library name drive drive
name, and must be removed manually.
Explanation: Library operations cannot be performed

using the drive because a volume is still mounted in it.
This may be due to a prior dismount failure that
occurred on the drive.
System action: The command fails. The drive may be
taken offline.
User response: See previous error messages and the
system error logs to determine the cause of the
dismount failure or any other reason the volume would
still be loaded in the drive. Hardware diagnostics may
be required. If necessary, remove the volume manually
and place it in its storage cell. If the storage cell is
unknown, place the volume in any cell and issue the
AUDIT LIBRARY command. Use the QUERY DRIVE
command to determine the online status of the drive. If
the drive is still functioning, change the status with the
UPDATE DRIVE command.
ANR8835W
Error returning volume volume name to

scratch.
Explanation: The server external library manager sent

a RELEASE request to the external agent for the named
volume, but the external agent was unable comply with
the request. The server, however, marked the volume
scratched in its inventory; consequently, the server
ANR8836E ANR8842E
inventory and the external agent inventory are not
consistent. This message is issued to inform the
customer that the external agent inventory must be
made consistent with the server inventory using the
facilities of the external agent.
System action: The drive is left offline and is not used

for tape operations.
User response: Issue the UPDATE DRIVE command
to bring the drive back online.
System action: The server has returned the volume to

scratch status.
ANR8840E
User response: Consult the documentation for the

external agent and take the appropriate action to make
the agent inventory consistent with the server
inventory.
Explanation: The library was inaccessible, thus

causing a open request to fail. This will in turn cause
the pending request to fail.
ANR8836E
Function RSM_function failed in

server_function processing, return return
code, call call number.
Explanation: The library function that uses the API to

the Windows NT Removable Storage Manager failed
with a return code from the API. The call number
represents the exact API call issued in the program.
Unable to open device device name with

error error number.
System action: A drive is marked inaccessible and the

server starts polling the drive to determine if the
library and drive are inaccessible. In most case, the
library had a temporary failure and recovers. When the
server determines that the library is available, the drive
will be brought back online.
User response: Verify the library is online. Verify cable
connections between the library and the server. If the
problem persists contact your service representative.
System action: The function fails.

User response: Use the RSM documentation to
determine the source of the problem.
ANR8837E
RSM Library Library Name not supported

on this Windows platform.
Explanation: The libtype=RSM was used on a

Windows platform that does not support RSM.
System action: The function fails.
User response: Use another library type to define the
library.
ANR8838E
I/O error on drive drive name: excessive

unit attentions received from device.
Explanation: An operation to the drive failed with a

device unit attention. These are normally cleared when
the operation is retried, but in this case subsequent
recover and retry attempts persistently fail with unit
attention. This indicates a device failure.
User response: See accompanying error messages and
the system error logs to determine any reason for the
drive failure. Hardware diagnostics may be required. It
may be necessary to manually unload the volume and
mark the drive offline with the UPDATE DRIVE
command.
ANR8839W

accessible.
Explanation: The server is now able to use the

mentioned drive that was inaccessible. However, the
administrator has marked the drive offline while the
drive was being polled.
ANR8841I
Remove volume from slot element number

of library library name at your
convenience.
Explanation: A volume has been placed in a multiple

entry/exit port library because the volume should be
placed back in the entry/exit port as result of the
successful completion of a server command, or there
was a problem during a server command. The volume
needs to be removed from the library, but the operation
is not critical.
entry/exit slot. Examine previous messages for
additional information regarding the specified volume
and the command.
ANR8842E
The Device type drive detected a

marginal sector and could not reallocate
the sector for volume Volume name.
Access mode is now set to read-only.
Explanation: The optical drive detected a marginal

sector (media error) while reading the volume. The
drive read the sector successfully but could not
reallocate the sector because of a previous media error.
System action: The volume is made read-only.
User response: Check system error logs for entries
made by the device relative to media errors. It is
recommended to move the data off the volume in order
to minimize the impact of future errors and further
damage to the media.
581
ANR8843E ANR8848W
ANR8843E
Initialization failed for library type

library library name - the library will be
inaccessible.

library has failed. The server is unable to use the
library. This may be for the following reasons:
v The library is defined without a path.
v The device for the library is removed by a DELETE
PATH command.
v The data mover controlling the library is offline.
v The path to the library is offline.
System action: The library is made offline and will
not be used for any library operations.
User response: Determine the reason the library is
inaccessible. Render any needed corrections to the
library, shut down the server, and re-bring up the
server so that the library can be completely initialized.
ANR8844E
Unable to open remote drive drive name,

error code=error value from server plugin.
Explanation: The indicated remote drive cannot be

opened by the server. The error code displayed is the
return code from server plugin routine.
System action: The transaction needing the drive fails.
User response: Use the return code displayed to
determine the cause of the open failure or any other
reason the drive cannot be opened. Hardware
diagnostics may be required. Inspect the drive. Ensure
that the drive is powered on and ready, the cables are
properly connected and terminated, and the device is
properly configured to the operating system.
ANR8845E
Loadable module module name is

required for remote operation.
Explanation: The indicated loadable module is

required by the server to perform an operation on a
remote drive or library, but the module has not loaded.
Message ANR4726I is issued during server initialization
when the module is loaded.
System action: The remote operation fails.
User response: Check the server activity log for
message ANR4726I, indicating if the module was
loaded. If you see this message during server
initialization for this module, please contact your
service representative. If you do not see this message,
make sure the loadable module has not been delete, or
cannot proceed because it is assigned to a category

other than the insert, private, or scratch category used
by the library.
User response: Use the mtlib utility to query the
volumes category. If the volume is not in use by
another library, use mtlib to reassign the category or
choose another volume that is assigned to the proper
category.
ANR8847E
No device type-type drives are currently

available in library library name.
Explanation: The attempted operation cannot be

completed on the specified library because there are no
available drives of the specified type. A drive may be
unavailable because a different application has the
drive opened. This message may also be issued if a
CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
because all the drives are mounted by other processes
or sessions, or the device type was incorrectly specified.
This can also be issued when incorrect barcode labels
are placed on the wrong type of media (e.g. LTO2
barcode label on an LTO1 cartridge).
check the online status of the drives. Drives that are
marked Unavailable since hh:mm yy/mm/dd are
drives taken offline by the server at the time specified
because of hardware failures or the inability to open
the drive. If the attempted operation is a CHECKIN or
LABEL command, use the QUERY MOUNT command
to determine if all the drives in the library are mounted
and wait until one of these is available. If there are
mounted volumes with an IDLE status, use the
DISMOUNT VOLUME command to free its drive, and
retry the original operation. Finally, the DEVTYPE
parameter is required for CHECKIN and LABEL
commands specifying 3590 volumes in a 349X library
that also contains 3490 drives. This is because this
library also supports 3490 volumes, and the default
device type on CHECKIN and LABEL commands is
CART (3490).
ANR8848W

inaccessible; server has begun polling
drive.

mentioned drive. This may be for the following
reasons:
v The drive cannot be opened
ANR8846E
Volume volume name is assigned to a

category that does not belong to library
library name.
Explanation: The attempted operation on the volume
582

ANR8849E ANR8856E
system logs. Render any needed corrections to the
accessible.
ANR8849E

delete drive drive name.

or updated because there is a request to delete the
drive already.
ANR8850I
ACSLS library library name is ready for

operations.

ready for use.
ANR8851E
Initialization failed for ACSLS library

minute(s).

library has failed. It is retried automatically after the
specified amount of time has elapsed.
powered on and ready.
ANR8852E
Initialization failed for ACSLS library

library name.

library has failed and will not be retried until the next
unavailable.
ANR8853E
Incompatible options
CHECKLABEL=NO and SEARCH=YES
for ACSLS libraries.
Explanation: The CHECKLABEL=NO and

SEARCH=YES parameters on the CHECKIN LIBVOL
command are not compatible.
command and specify CHECKLABEL=YES.
ANR8854E
ACSAPI(command name) invocation

failed, status=acs status.
Explanation: The ACSLS library API invocation for

the given command failed.
System action: Depends on the server function and
command, library may be unavailable.
User response: Contact your ACS System
Administrator and perform ACSLS library problem
determination.
ANR8855E
ACSAPI(command name) response with

unsuccessful status, status=acs status.
Explanation: The ACSLS library API responded with

an unsuccessful status as indicated.
User response: If the status indicates
STATUS_CAP_IN_USE, it might be CAP priorities not
set to non-zero. It might also be CAPs are not set to
automatic mode, or CAPs are in manual mode during
manual checkin. If CAP mode and priorities are set
correctly, contact your ACS System Administrator and
perform ACSLS library problem determination.
ANR8856E
ACSAPI sequence(sequence number)

request(request number) timed out, elapse
time=hours:minutes:seconds.
Explanation: The ACSLS client has received no

response from the ACSLS server for the period as
indicated in the elapsed time. The ACSLS library API
function with the associated sequence number is
canceled if the request number is non-zero.
determination.
583
ANR8857I ANR8866E
ANR8857I
ACS access control set to user_id - user

id, status=acs status.
Explanation: The ACSLS ACCESSID structure for

command and volume access control is set the user_id
as indicated.
User response: Ensure the indicated user_id is the
same as specified in the environment variable
ACSAPI_USER_ID.
ANR8858W
Unable to lock drive drive id,drive id,drive

id,drive id, status=acs status.
User response: Monitor the ACSSA console and wait.

ANR8862I
Unable to access ACS volume volume id.
Explanation: The specified ACSLS volume can not be

accessed in the library. The possible reasons might be
the volume is in use, the user is not authorized, the
volume does not exist in the library.
command, library volume is unavailable.
determination if the problem persist..
Explanation: The ACSLS library function

acs_lock_drive failed for the specified drive.
ANR8863I

command, library drive may be unavailable. or may be
temporary unavailable in a shared library environment.
Explanation: The volumes of the specified library are

being unlocked from the ACSLS server.

determination if the problem persists.
Unlocking library library name volumes

from the ACSLS server.
System action: The operation continues. The process

may take a while depends on the number of volumes
in the library.
ANR8859W
Unable to lock volume volume id,

status=acs status.
Explanation: The ACSLS library function

acs_lock_volume failed for the specified volume.
command, library volume is unavailable.
determination if the problem persist.
ANR8864I
ACSLS library library name is being

re-initialized.
Explanation: The specified ACSLS library is being

re-initialized.
System action: The operation continues. The process
may take a while depends on the number of volumes
in the library. All volumes in the library are being
locked.
ANR8860W
Volume volume id is already locked by

user id.
Explanation: The specified volume is already locked

by other user or has a different lock id.
System action: Depends on the function, the volume
maybe bypassed or the process maybe terminated.
User response: This may not be an error in a shared
configuration. However, if the existing volume lock is
not needed. contact your ACSLS system administrator
to clear the lock the volume.
ANR8865W
Explanation: The specified volume is bypassed. The

volume is not in a valid status for the specified
function.
User response: Determine the volume status from the
ACSSA and re-issue the command if necessary.
ANR8866E
ANR8861I
Wait and monitor the ACSSA console

message to remove volume volume id
from CAP.
Explanation: The specified volume is about to put into

CAP for removal. Monitor the ACSSA console and
removed the volume after it has been placed into the
CAP as indicated in the ACSSA message.
584
Volume volume name bypassed for

command, status=acs_status.
Incompatible option REMOVE=BULK

for ACSLS libraries.
Explanation: The REMOVE=BULK option is not

supported for ACSLS libraries. The final response of
ACSAPI acs_eject does not return to the application
until the volume is removed from CAP.
User response: Reissue the CHECKOUT LIBVOL
command and specify REMOVE=YES or NO.
ANR8867I ANR8875E
ANR8867I
Processing volume volume id for the

command command.
Explanation: The specified volume is being processed

for the specified command.
User response: Ensure that a path is defined to the

drive. If there is a path defined to the drive, make sure
that the path is online and that the source of the path is
also online. Run the AUDIT LIBRARY command after
the problem is corrected.

ANR8868E
Ejecting Volume volume name Failed,

status = acs_status.
Explanation: The volume is failed to be ejected from

the library due to the status as indicated
User response: Determine the volume status from the
message and do something as needed
ANR8869E

update drive drive name.
ANR8873E
Explanation: There is problem using the indicated

path. The path is now marked offline.
System action: The path is inaccessible.
User response: Determine the reason the path is
inaccessible, such as hardware problem. Render any
needed corrections. Then, the path may be made online
by issuing the UPDATE PATH command with the
ONLINE=YES option.
ANR8874E

because there is a request to update the drive already.
ANR8870E
The path to the library library name is

unavailable.
Explanation: There is no path to the given library, or

the path to the library is offline, or the source entity of
the path to the library is offline.
System action: The library is inaccessible.
User response: Ensure that a path is defined to the
library. If there is path defined to the library, make sure
the path is online and the source entity of the path is
also online.
The device name device name specified
has been changed to device name.
Explanation: The specified device name on the

DEFINE PATH or UPDATE PATH command has been
changed to recommended device name.
ANR8872E
No path is available for drive drive name

- could not unload volume volume name
from drive.
The type of device used by the media in

element element number of library library
name cannot be determined by the
hardware. Volume is not processed.
Explanation: The librarys mechanism for determining

the type of media in a slot or EE port failed. This is
usually the barcode reader or some other sensor that is
part of the robotics.
System action: The volume is skipped by the process.
User response: Determine the reason the library could
not determine the media type, such as deteriorated
barcode, scanner failure, or other hardware problem as
determined by system engineer. If the barcode label is
replaced on a private volume containing data, it must
be with a label having the volume name. Scratch
volumes or empty private volumes can be replaced
with any barcode but they must be re-labeled if the
barcode name changes.
ANR8875E
ANR8871I
The path from source source name to

destination drive name is taken offline.
An illegal move was attempted

involving the media in element element
number of library library name. Its type is
incompatible with the destination
element element number.
Explanation: The server tried to move one type of

volume into a drive or slot of another type that is
incompatible. This is most likely because another
volume has taken its slot, or the servers information
for this volume has otherwise been corrupted.
System action: The process fails.
User response: Issue the AUDIT LIBRARY command,
Explanation: There is no path to the given drive or

the path to the drive is offline or the source of the path
to the drive is offline. The indicated volume may be
still on the drive.
System action: The drive is inaccessible.
585
ANR8876E ANR8883W
ANR8876E
The media in element element number of

library library name is a cleaner.
Explanation: The library hardware has determined

that the media in the stated slot is a cleaner cartridge.
It cannot be processed by the CHECKIN command
without the STATUS=CLEANER parameter, and it
cannot be labeled by the LABEL command.
System action: The process skips the media, or if it is
the only media being processed the process fails.
User response: Issue the AUDIT LIBRARY command,
ANR8880W
Device type of drive Drive name in

library Library name was determined to
be GENERIC_TAPE.
Explanation: The device type of a drive is determined

when the path for that drive is defined. If the wrong
device file was used in the device parameter of
DEFINE PATH the device type of the drive will often
be GENERIC_TAPE. If you are using the TSM device
driver or the IBMTape device driver, then you should
not have a device type of GENERIC_TAPE. You should
only have a device type of GENERIC_TAPE if you are
using the native OS device driver.
ANR8877E
Volume volume name is incompatible

type with device class devclass name in
Explanation: An attempt has been made to service a

mount request, but the attempt fails because the media
type of the cartridge being mounted is not compatible
with the devclass requesting the mount. This is usually
a conflict between WORM and Read-Write
characteristics.
User response: Verify that GENERIC_TAPE is the

desired device type for this drive. While the device
type GENERIC_TAPE is valid, it is often a mistake, and
thus, should be verified that it is the intended device
type. If GENERIC_TAPE is not the intended device
type, all paths for this drive and the drive itself will
have to be deleted and redefined.
ANR8881W

User response: If this is not a 3592 device or media,
The volume was probably not checked in with the
CHECKLABEL=YES parameter of the CHECKIN
command. Check the volume out (the REMOVE=NO
may be useful) and check the volume back into the
library with this parameter to ensure that the
mediatype is determined and saved. If this is a 3592
device or media, the volume probably has an incorrect
barcode label indicating that it had the wrong WORM
property. The label needs to be swapped for the
opposite WORM type (e.g. WORM to non-WORM or
non-WORM to WORM) or simply removed entirely
from the library.
Explanation: The server found that the indicated

directory had insufficient space in which to create a
new volume.
System action: Other directories available to the
device class are used, if any. If no directories with
space are available, the operation fails. This message is
issued periodically as requests are made for space in
this directory.
ANR8882I
ANR8878E
Failed to close the remote library library

name(device name).
Explanation: An attempt to close a remote Library

device attached to a NAS File Server failed.
additional information regarding the specified library.
ANR8879E
Failed to close the SCSI session for the

remote library library name(device name).
Explanation: An attempt to close a SCSI session for a

remote Library device attached to a NAS File Server
failed.
additional information regarding the specified library.
Insufficient space for new volume in

directory directory for device class device
class name.
Request number: Please provide the label

name for the volume in drive drive name
of library library name by issuing REPLY
n LABEL=xxx within time limit minutes,
where n is the request ID and xxx is the
desired label name.
Explanation: A mount is in progress with

AUTOLABEL, and the name of the volume is needed.
command is issued.
User response: Issue a REPLY command, along with
the request ID, and the volume name for the cartridge.
ANR8883W
The volume volume name in slot element

number is in the library library name but
not in the TSMs inventory database.
Please either check in this volume or
remove it from the library;
Explanation: .
586
ANR8884W ANR8907E
System action: .
User response: The Audit Library command found
this volume in this library but they are not in TSMs
inventory database. This volume can be either checked
in or removed from this library.
ANR8903E
Command: Missing CLEANINGS

parameter for cleaner cartridge checkin.
Explanation: When checking in a cleaner cartridge, the

CLEANINGS parameter is required.
ANR8884W
Attempted to label a written WORM

medium in the drive drive name with
volume volume name (OP=internal code,
Error Number=internal code, CC=internal
code, KEY=internal code, ASC=internal
code, ASCQ=internal code, SENSE=sense
data, Description=error description). Refer
to Appendix C in the Messages manual
Explanation: An I/O error has occurred while labeling

on the written WORM medium.
User response: Ensure the WORM medium in the
drive is not a written WROM medium.
ANR8901E
Command: Incompatible options

STATUS=CLEANER and
CHECKLABEL=YES.

command and specify a value for the CLEANINGS
parameter which is used to determine the number of
times a cleaner can be mounted to clean a drive.
ANR8904I
Command: Cleaning operation for drive

drive name in library library name started
Explanation: A command-driven process is started to

clean the specified drive. The process is assigned the ID
that is in the message.
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.
Explanation: Cleaner cartridges do not have internal

labels that can be checked by loading them into the
drive.
ANR8905I
Explanation: A background server process is has been

working to clean the specified drive and is canceled by

command and include the parameter,
CHECKLABEL=BARCODE (with SEARCH=YES
specified), or include the parameter
CHECKLABEL=NO (with the required volume name
specified in the CHECKIN command).
System action: The cleaning process is ended.

ANR8906I
ANR8902W
Unable to read the barcode of cleaner

cartridge in slot-id Element number of slot
in library library name; cleaner not
checked in.

read the label of a cartridge that is checked in as a
cleaner. The cartridge is found in the slot with the
given element number.
System action: The cartridge is not checked in. If the
library is being searched, the checkin process continues
with the next volume.
User response: Examine the cartridge to ensure it has
a barcode label and that it is compatible with the
configured and is functioning properly. The cleaner
cartridge can be checked in without use of the barcode
label by issuing the CHECKIN LIBVOL command.
CLEAN DRIVE process for drive drive

name in library library name is been
canceled.
Cleaning drive drive name in library

library name.

CLEAN DRIVE process on the server. The given
volume is being checked in to the designated library.
continues. The process may be canceled by an
authorized administrator using the CANCEL PROCESS
command.
PROCESS command.
ANR8907E
CLEAN DRIVE for drive drive name in

library library name failed.
Explanation: The background process for a CLEAN

DRIVE fails.
587
ANR8908I ANR8915I
drive is not cleaned.
cleaner volume status. If necessary a cleaner cartridge

should be checked in to replace it.

and ready. Reissue the command.
ANR8912E
ANR8908I
CLEAN DRIVE for drive drive name in

library library name completed
successfully.
Explanation: The specified drive is successfully

cleaned in the library during processing of a CLEAN
DRIVE command.
System action: The drive is available for normal
library operations.
Unable to verify the label of volume

from slot-element element-address in drive
drive name in library library name.
Explanation: The volume from the slot that is

identified by the element address is loaded into a drive.
The drive cannot be opened following the load. The
label cannot be read to process the volume.
System action: The volume is stored, and processing
continues with the next available slot.

CLEAN DRIVE process on the server.
User response: Check the system error logs for errors

reported by the drive that are related to this volume.
Make sure that the cartridge is not a cleaner cartridge
that would have been loaded by mistake. If the
cartridge is a cleaner, issue the QUERY LIBVOL
command to get the correct storage slot for the cleaner
and move the cleaner to that slot. If the cleaner is not
in the librarys inventory, use the CHECKIN LIBVOL to
check the cleaner in. During Audit Library, remove the
bad volume from the reported slot and run Audit
Library again.

terminated.
ANR8913I

ANR8909I
Cleaning drive drive name in library

library name- CANCEL PENDING.

ANR8910I
No cleaner, or no cleaner with cleanings

left, found in library library name.
Explanation: A drive is selected to be loaded with a

cleaner cartridge, but no cleaner, or cleaner with
cleanings left, is found in the librarys inventory.
library operations.
User response: A cleaner should be checked in to the
library by issuing the CHECKIN LIBVOL command.
ANR8911W
The cartridge in storage element slot

element address in library library name is
not a cleaner cartridge as was expected.
Explanation: The cartridge is listed in the librarys

inventory with a cleaner volume status. After loading
the cartridge in the specified storage cell into a drive
for cleaning, it is determined that it is not a cleaner
cartridge.
library operations.
User response: Verify all other cleaner cartridges are
in the correct storage cells. Issue the QUERY
LIBVOLUME command to obtain the storage cells of all
the cartridges currently checked into TSM. The
cartridge should be checked out of the library by
issuing the CHECKOUT LIBVOL command if the
cartridge is still listed in the librarys inventory with a
588
Drive drive name in library library name is

currently busy; Cleaning is scheduled.
Explanation: A background process to clean the drive

is unable to acquire the drive because the drive is busy.
completes. The drive is scheduled to be cleaned when
it is unloaded.
ANR8914I

needs to be cleaned.
Explanation: The drive has returned indicating to the

server that it needs to be cleaned.
System action: The server marks the drive to be
cleaned. If the drive is enabled for server-managed
cleaning, and a cleaner cartridge is checked into the
library, the server will load the cleaner into the drive
after the current volume is dismounted. See the
DEFINE DRIVE and QUERY DRIVE commands for
information on enabling server-managed cleaning. See
the CHECKIN LIBVOL command for checking a
cleaner into the library.
ANR8915I
Cleaning cartridge cleaner name in library

library name is near end of life; has
cleanings left uses left.
Explanation: A cleaner cartridge is found and used,

but its number of uses it has left is nearly exhausted.
ANR8916I ANR8925W
System action: The cleaning operation continues.
User response: As the cleaner is used, monitor the
number of cleanings that remain with the QUERY
LIBVOL command. Remove the cleaner when all
cleanings are exhausted. A new cleaner may be checked
in so that the library is not left without a useful cleaner
when the old cleaner is exhausted.
ANR8916I
Drivemapping for drive Drive name in

library library name on storage agent
storage agent name defined.
Explanation: A drive mapping has been successfully

defined for the specified drive.
System action: The drivemapping is defined and
recorded in the database.
ANR8917I
Drive mapping for drive Drive name in

storage agent name updated.
Explanation: An UPDATE DRIVEMAPPING request

has been successfully processed for the given drive.
about the drive mapping.
ANR8918I
Drive mapping for drive Drive name in

storage agent name deleted.
Explanation: The drive mapping for the specified

storage agent, library, and drive has been deleted
successfully.
System action: The drive mapping is deleted.
ANR8920I
Initialization and recovery has ended for

shared library library name.
Explanation: Initialization or recovery has ended the

library manager and library client should be
synchronized.
User response: The drives previously owned by the
library client should now indicate they are free on the
library manager. Verify this with the QUERY DRIVE
command on the library manager. If ownership of the
drives is still in question restart the library client and
library manager.
ANR8921E
Unable to start library polling thread .
Explanation: Library sharing requires that this polling

thread starts. This thread keeps the library manager
and library client synchronized with regards to drive
ownership. These thread are started when the library is
defined or when the server is first initialized.
User response: Since the polling thread did not start,
the user must restart the server in order for library
sharing to correctly work. Failure to restart the server
and get these polling services running can cause
unusual results for library clients.
ANR8922I
A device class for library library name

was not found.
Explanation: A library client request a mount

operation to be performed by the library manager. The
library manager is missing a device class definition for
that library.
User response: Define a device class for the library

using the DEFINE DEVCLASS command.
ANR8919I
ANR8923I
Initialization and recovery has started

for shared library library name.
Explanation: The shared library has started to

initialize or recover to resynchronize the library
manager and library client.
User response: This process should resynchronize all
of the drives that are currently being used by this
library client. This process might also start after a
communication error or if the library client has not
been able to verify drive status with the library
manager.
Dismount failed because drive drive

name in library library name is not
currently owned by drive owner name.
Explanation: A library client attempted to dismount a

drive that was not currently owned by the library
client.
ANR8925W

has not been confirmed for use by
server server name for over elapsed time
seconds. Drive will be reclaimed for use
by others.
Explanation: The library server was unable to contact

589
ANR8926W ANR8931W
the library client for the given interval to verify that the
library client is still using the drive. At this point the
error recovery logic of the library manager will reclaim
the drive (including dismounting the clients volume if
possible) and allow other to use the drive.
User response: Verify that the library client with the
above server name is still running. Verify that the
sessions have not been disabled and the network is still
working between the two host machines. Verify that
the server definition (QUERY SERVER) on both the
library manger and the library client are correct.
ANR8926W
An Error was encountered while

confirming the use of drive drive name in
shared library library name.
Explanation: The library client was unable to confirm

the usage of the drive to the with the library manager.
ANR8929E
Explanation: A pre-existing library was specified for a

new shared file device class. However, the existing
library was not created with the LIBTYPE=FILE
parameter.
System action: None. The device class is not created.
User response: Specify a library name that was
created with the LIBTYPE=FILE and SHARED=YES
parameters, or specify a library name which does not
exist, in which case, the library will be created. You can
also not specify the LIBRARY parameter, a library name
will be created.
ANR8930W

User response: Verify that the sessions have not been
disabled and the network is still working between the
two host machines. Verify that the server definition
(QUERY SERVER) on both the library manger and the
library client are correct.
ANR8927W
This library client has been unable to

contact the library manager for elapsed
time seconds. Releasing ownership of all
drives in the shared library library name.
Explanation: The library client was unable to confirm

the usage of the drive with the library manager. The
library client will now dismount all volumes that it
currently owns.
User response: Verify that the sessions have not been
disabled and the network is still working between the
two host machines. Verify that the server definition
(QUERY SERVER) on both the library manger and the
library client are correct.
ANR8928W
Library library name specified for shared

file device class device class name was not
defined as shared. The device class will
not be shareable unless the library is
updated.
Explanation: A pre-existing library was specified for a

new shared file device class. However, files in the
device class cannot be shared unless the library is also
shared.
User response: Issue the UPDATE LIBRARY libname
SHARED=YES command to make the library shared.
590
Library library name specified for shared

file device class device class name was not
defined as a FILE library.
An attempt to define drives to create

drives failed for library library name. The
device class has a mount limit of mount
limit but the number of drives in the
associated library is less than the mount
limit.
Explanation: When a shared device class is created or

updated, an attempt is made to define additional file
drives in the associated library up to the mount limit, if
the number of drives is less than the mount limit. One
or more failures occurred in defining additional drives.
The number of drives does not correspond to the
mount limit for the associated device class. This can
cause resource balancing problems between the server
and storage agents.
System action: The server continues operation.
get the names of the drives associated with the library.
Use the QUERY DEVCLASS deviceclass F=D command
to find the mount limit of the associated device class.
Use the DEFINE DRIVE command along with the
DEFINE PATH command for this new drive with
DEVICE=FILE to define additional drives in the file
library to match the mountlimit of the associated device
class.
ANR8931W
An attempt to delete drives to delete

drives failed for library library name. The
device class has a mount limit of mount
limit but the number of drives in the
associated library is greater than the
mount limit.
Explanation: When a shared device class is updated

and the number of drives in the associated library is
greater than the mount limit of the device class, an
attempt is made to delete drives so that there are as
many drives as the mount limit. One or more failures
occurred in deleting drives. The number of drives does
not correspond to the mount limit for the associated
device class. This can cause resource balancing
problems between the server and storage agents.
ANR8932W ANR8937W
get the names of the drives associated with the library.
Use the QUERY DEVCLASS deviceclass F=D command
to find the mount limit of the associated device class.
Use the DELETE DRIVE command to delete drives
until the number of drives in the library corresponds to
the device classs mount limit.
ANR8932W
The drive map for server servername,

library library name, drive name drive
name has directory directory which is
different than other drive maps for
drives within the same library.
Explanation: A shared file was about to be created. In

doing so, it was determined that there are differing
definitions for the directories associated with the drive
maps between the indicated drive map and other drive
maps for drives in the same library. This could cause
data to be written in unanticipated locations or may
prevent data from being written.
System action: The server continues operation using
the indicated directory.
User response: Use the QUERY DRIVEMAP command
with the F=D parameter to list the directories
associated with drive maps for drives in the indicated
library and ensure that the directories are correct and
identical. Use the UPDATE DRIVEMAP command to
update any incorrect directory entries.
ANR8933W
File volumename in library library does

not exist in the expected directory.
Explanation: A FILE volume was being dismounted

from a file drive. The file does not exist in the directory
in which it was expected to be found.
User response: It is possible that a drive mapping is
incorrect and that a storage agent is using a valid, but
different directory than that of the server. In this case,
the storage agent can access the file, but the server
cannot. Use the QUERY PATH command with the F=D
parameter to list the directories associated with drive
maps for drives in the indicated library and ensure that
the directories are correct and identical. Use the
UPDATE PATH command to update any incorrect
directory entries. To move the file into the correct
directory, use the Windows move command or the
Unix mv command, depending on your platform.
ANR8934W
File volumename in library library

associated with device class device class
could not be inserted into the library
inventory.
directory associated with the device class that

references the library. However, an entry for the
indicated file name is already in the library inventory.
User response: It is possible that a drive mapping is
incorrect and that a storage agent is using a valid, but
different directory than that of the server. In this case,
the storage agent can access the file, but the server
cannot. Use the QUERY DRIVEMAP command with
the F=D parameter to list the directories associated
with drive maps for drives in the indicated library and
ensure that the directories are correct and identical. Use
the UPDATE DRIVEMAP command to update any
incorrect directory entries. To move the file into the
correct directory, use the Windows move command or
the Unix mv command, depending on your platform.
ANR8935E
A compatible device class for shared

library library name on server server name
was not found.
Explanation: The library client server has a device

class definition that is not compatible with the device
class definition on this server. The device type and
recording format need to be the same on both servers
or one of the servers can have a device type of generic
tape.
ANR8936W
The path conversion of drive drive name

in library library name with device name
device name failed. UPDATE DRIVE
required.
Explanation: During the initialization of a library, the

server finds that the drive path was removed.
library during tape operations.
User response: The drive may be made accessible by
DEVICE= option.
ANR8937W
The device name for drive drive name in

library library name is missing. UPDATE
DRIVE required.
Explanation: The device name for a drive was found

to be missing.
server for tape operations.
User response: The drive may be made accessible by
DEVICE= option.
Explanation: A FILE volume was being inserted into

the library inventory. The file was not found in the
591
ANR8938E ANR8943E
ANR8938E
Initialization failed for Shared library

library name; will retry within delay time
minute(s).

library has failed. It will be retried automatically in the
specified time.
User response: Ensure that the library manager server
is running, and the library is initialized.
from the perspective of the specific server or storage

agent. The list of directories must have entries for each
directory in which file volumes are to be read or
written by the specified server or storage agent.
System action: The operation will fail.
User response: Ensure that DIRECTORY attribute of
the above path definition contains matching directories
for each of the directories in the servers device class
definition.
ANR8941W
ANR8939E
The adapter for tape drive drive name

cannot handle the block size needed to
use the volume.
Explanation: The adapter cannot read and write the

block size need for the volume because the
MAXIMUMSGLIST parameter of the adapter is set to
less than hex 41.
System action: The volume will not be mounted in
the drive.
User response: The adapter must be updated to
handle a larger block size. The setting is usually
MAXIMUMSGLIST in the Windows registry under:
HKEY_LOCAL_MACHINE->SYSTEM->Current Control
Set->Services->{vendor device name}->Parameters>Device
Note that {vendor device name} should be substituted
with the name of the vendors device. For example, the
Qlogic 2200 would use Ql2200 for the respective
vendor device name.
MAXIMUMSGLIST should be set to hex 41 to work
properly with Tivoli Storage Manager.
You can also run the DSMMAXSG utility to set the
MaximumSGList value to 0x41(65) for all HBAs.
For additional information, see the HBA documentation
or contact the vendor for the HBA.
For additional questions, contact IBM support.
ANR8940E
Path definition for file drive drive name

in library library name for server server or
storage agent name does not have a
matching directory in the device class
directory attribute for volume volume
name.
Explanation: A library client or storage agent

requested a mount of a file volume in a drive that is
contained in a file library but the path definition does
not contain a matching directory name. There must be
a matching directory in the PATH definition for each
drive in a file library and the corresponding directories
in the device class associated with the library. The
directories in the PATH definition must point to the
same storage as those of the device class definition,
592
The volume from slot-element

element-address in drive drive name in
library library name is blank.
Explanation: The volume in the slot is not labeled and

is blank.
System action: The volume is skipped, and processing
continues with the next available slot. If the volume is
checked in, it is removed from the inventory.
User response: Label the volume using LABEL
LIBVOL, and check it in using CHECKIN LIBVOL.
ANR8942E
Could not move volume volume name

from slot-element element-address to
slot-element element-address.
Explanation: Could Not move volume from slot to

slot.
System action: Move volume operation failed.
ANR8943E
Hardware or media 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 Appendix C in the
Messages manual for recommended
action.
Explanation: A hardware or media error has occurred

while operating on the specified library.
the DEFINE PATH command and that the library
device is currently powered on and ready. If the library
has an access door, make sure it is closed. The library
reference manual usually contains tables that explain
the values of the KEY, ASC, and ASCQ fields.
ANR8944E ANR8951I
ANR8944E
Hardware or media error on drive drive

name with volume volume
name(OP=internal code, Error Number=
internal code, CC=internal code,
KEY=internal code, ASC=internal code,
ASCQ=internal code, SENSE=sense data,
Description=error description). Refer to
Appendix C in the Messages manual
Explanation: A hardware or media error has occurred

while operating on the specified drive.
currently powered on and ready. The drive reference
manual usually contains tables that explain the values
of the KEY, ASC, and ASCQ fields.
ANR8945W
Scratch volume mount failed volume

name.
Explanation: Scratch volume mount failed.

System action: Scratch volume mount operation
failed.
ANR8946W
There were more labels in the vollist

than volumes available to label.
Explanation: Label Libvolume command still finishes

without error, but the last labels provided were not
used. Labeling finished when there were no more
volumes available.
System action: All available volumes were labeled,
but additional volume names were not utilized from
the vollist.
ANR8947W
There were less labels in the vollist than

volumes available.
Explanation: Label Libvolume command still finishes

without error, but volumes are left unlabeled.
System action: Additional volumes were left
unlabeled.
ANR8948S
Device device, volume volume name has

issued the following Critical TapeAlert:
alertmessage
Explanation: The specified device while loaded with

the named volume has issued a TapeAlert critical
message. This message is a feature of the hardware and
is from the device, not the TSM server. It is surfaced at

the termination of the current operation but is
independent of the operation.
System action: The operation may or may not fail,
depending on other error indications such as check
conditions from the device. The TapeAlert message
does not by itself indicate failure. See other messages
related to the device or volume in the activity log.
User response: Proper response may be indicated in
the text of the TapeAlert. The context of the TapeAlert
may need to be determined from other activity log
messages in order to follow its recommendations.
ANR8949E
Device device, volume volume has issued

the following Critical TapeAlert:
alertmessage
Explanation: The specified device regardless loaded or

not without the named volume has issued a TapeAlert
critical message. This message is a feature of the
hardware and is from the host interface, not the TSM
server. It is surfaced at the termination of the current
operation but is independent of the operation.
System action: The operation will fail. The TapeAlert
message does not by itself indicate failure. See other
messages related to the device or volume in the activity
log.
ANR8950W

the following Warning TapeAlert:
alertmessage
Explanation: The specified device without the volume

name has issued a TapeAlert Warning message. This
message is a feature of the hardware and is from the
device, not the TSM server. It is surfaced at the
termination of the current operation but is independent
of the operation.
System action: The operation will fail. See other
messages related to the device or volume in the activity
log.
ANR8951I

the following Information TapeAlert:
alertmessage
Explanation: The specified device while loaded with

the named volume has issued a TapeAlert information
message. This message is a feature of the hardware and
is from the device, not the TSM server. It is surfaced at
593
ANR8952E ANR8959W
the termination of the current operation but is
independent of the operation.
System action: The operation may or may not fail,
depending on other error indications such as check
conditions from the device. The TapeAlert message
does not by itself indicate failure. See other messages
related to the device or volume in the activity log.
ANR8952E
Library serial number does not match

that defined for library name .
Explanation: The serial number defined for the

specified library does not match the serial number
discovered. The pending operation will fail.
System action: The library is taken offline when the
mismatch is discovered. Verify the serial number and
the device name for the library against those defined. If
they do not match, the definitions for the library are
incorrect and need updated. Once the serial number is
updated, the library will be brought back online.
User response: Update the serial number or device
name for the specified library with the correct values.
ANR8953I
Library library name with serial number

serial number is updated with the newly
discovered serial number serial number .
Explanation: The serial number for the library defined

does not match with the serial number discovered. The
newly discovered serial number will replace the
existing definition for this library since autodetect is on.
System action: The existing serial number for the
specified library is replaced by the newly discovered
serial number.
ANR8955I
Explanation: The serial number for the drive defined

does not match with the serial number discovered. The
newly discovered serial number will replace the
existing definition for this drive since autodetect is on.
System action:
ANR8956E
Failed to obtain a path for drive drive

name for library library name.
Explanation: An attempt to acquire a path for the

drive failed. This most likely means that a path is not
defined for this drive.
User response: Ensure that a path is defined for this
drive. If one is defined, make sure it is defined
correctly: correct source and destination type, etc.
Serial number defined for library library

name does not match the discovered
serial number.
Explanation: The serial number for the library defined

does not match the serial number discovered due to
autodetect is set to NO. The pending operation will fail.
System action: A mismatch between the serial number
for library and the newly discovered serial number is
detected.
User response: Update the serial number for the
specified library with the correct values.
ANR8957E
Command: Autodetect is OFF and the

serial number reported by the library
did not match the serial number in the
library definition.

ANR8958E

ANR8954E

with serial number serial number is
updated with the newly discovered
serial number serial number .
Command: Autodetect is OFF and the

serial number reported by the drive did
not match the serial number in the drive
definition.

ANR8959W
Path to the library or the device does

not exist.
Explanation: A path to the library or the device does

not exist yet.
System action: This may not be an error.
594
ANR8960I ANR8968E
ANR8960I
Command: The display of Tape Alerts

from SCSI devices is status.
Explanation: Whether the status of Tape Alerts from

SCSI devices will be display.
System action: The command is processed.
ANR8964W
Unable to update the path in the

database path source name and drive drive
name .
Explanation: The system is not able to update the

path information in the database.
System action: .
ANR8961E

name and drive drive name is blank and
does not match the discovered drive
serial number serial number.
Explanation: A device has been swapped and we are

not able to get the new path.
System action: .
ANR8962E

name is blank and does not match the
discovered library serial number.
Explanation: A device has been swapped and we are

not able to get the new path.
System action: .
ANR8963E
Unable to find path to match the serial

number defined for drive drive name in
library library name .
Explanation: A device has hardware problems or a

device path has been changed and the TSM server
cannot find the new path with the SAN Discovery
option set to OFF. The TSM server cannot get device
information when it cannot open the device. Therefore,
the TSM server cannot validate the drive serial number
to see if this drive with the failed open operation is the
same drive as it previously used. The causes of this
failed open device can be a bad cable, a bad drive or a
bad HBA card. However, if an incorrect drive is used
(for example, an incorrect device path) and with the
SAN discovery option set to OFF, the TSM server will
not search the SAN environment to get a proper device.
System action: The server marks this device offline.
User response: Check the server option file first. If
SAN discovery option is set to OFF, set it to ON and
check for hardware errors on the device. If the SAN
discovery option is set to ON, then check the device to
see if there is a hardware problem.
ANR8965W
The server is unable to automatically

determine the serial number for the
device.
Explanation: The server did not receive a serial

number from the device, so the server is not able to
automatically correct the path for the device.
User response: Verify that the device name in the path
definition is correct.
ANR8966E
Cannot get device number for the drive

drive name.
Explanation: The server is unable to obtain the device

number for the specified drive. This could occur if an
invalid device name is specified for the drive or if there
is hardware errors.
system logs or an invalid device name was specified
for the drive. Render any needed corrections to the
accessible.
ANR8967E
Command: The drive serial conflicts with

an existing drive in library library name.
Explanation: The serial number already exists in the

drives in the given library.
User response: Specify a valid serial parameter for
this drive.
ANR8968E
Unable to create path for device device.
Explanation: An attempt to contact the drive with a

given device name failed. This probably means the
device name is incorrect, but this attempt can also fail
for other reasons.
System action: Operation failed.
595
ANR8969E ANR8975I
User response: The device parameter is probably not
valid. This could be temporary, but not necessarily. If
this occurs while upgrading from Tivoli Storage
Manager Version 4.1 or previous (where paths were not
used), then the drive needs to be deleted, redefined,
and a new path needs to be defined with a valid device
parameter. If this occurs on a Tivoli Storage Manager
server that already has paths (Version 4.2 or higher),
then just update the drive to online. The device
parameter on the drive path can also be updated before
the drive is turned online, if you know the device
parameter should be changed.
ANR8969E
The owner of volume Volume name can

not be updated to owner Owner name.
Explanation: A command was issued updating

ownership of a volume. The owner of this particular
volume can not be changed.
ANR8972E
Explanation: Because the drive serial number does not

match any drive serial number in the serial/element
number map reported by the library, the element
number cannot be determined.
User response: Make sure the serial number entered
for the drive is correct if AUTODETECT is not active. If
AUTODETECT is active, the drive serial number might
be incorrect or the library reported an incorrect
serial/element number map. Contact your service
representative.
ANR8973E

ANR8970E
Unable to open special file specialfile for

tracing parameter device driver; errno =
errno.
Explanation: The special file created by the device

driver for tracing purposes could not be opened by the
server. This file should be created when the device
driver is configured on the system
System action: Device driver tracing could not be
started.
User response: Make sure that the special file exists
and can be accessed by the server. If the device driver
has not been completely configured and special files
created for all devices, do so. The device driver can
also be traced by specifying the name of a library or
drive that has been defined to the TSM Server.
ANR8971E
Unable to validate directory name

directory name for parameter command
Explanation: The specified directory name was being

used in the indicated command. The server attempted
to validate that the directory was accessible so that it
could be used in the command definition. The server
was unable to validate that the directory was
accessible.
System action: The command fails. The server
continues.
User response: Make sure that the directory exists and
can be accessed by the server.
command: Unable to find the element

number for drive drive name in library
library name.
Reset has failed to break the reservation

set by another system for device device
name with path path name.
Explanation: The attempt to reset the device

reservation set by another system has failed.
System action: .
User response: If this tape device is a Fibre Channel
direct attached device on Windows 2003, please make
sure the HBA driver is a StorPort driver by checking
the HBA vendors support web site. The device reset
(LUN Reset) on Windows 2003 requires StorPort driver.
Otherwise, the device may have to be rebooted to reset
the reservation. If not rebooted, this device will not be
accessible. If RESETDrive keyword for the update
library command is set to NO, device reset will not be
attempted.
ANR8974I
Found new path for path source name and

target name target name old path old path
name new path new path name. Path
information will be updated remotely.
Explanation: A new path has been found for the

device on the library client or storage agent. Will try to
update the path information on the library manager.
System action: .
User response: The path change may be caused by
system reboot or cable swap or device addition or
removal.
ANR8975I
Found new path for path source name and

target name target name old path old path
name new path new path name. Path
information is updated.
Explanation: A new path has been found for the

device and the path information has been updated.
System action: .
User response: The path change may be caused by
596
ANR8976E ANR8984E
system reboot or cable swap or device addition or
removal.
ANR8976E
Unable to open special file specialfile for

LUN reset with errno = errno.
Explanation: The special file created by the device

driver for LUN reset purposes could not be opened by
the server. This file should be created when the device
driver is configured on the system
System action: LUN reset could not be started.
User response: Make sure that the special file exists
and can be accessed by the server. If the device driver
has not been completely configured with special files
created for all devices, resolve the device driver
configuration.
LIBRARY command entered by an administrator.

ANR8980I

been working to scan the given library is canceled by
ANR8981I
ANR8977W
The volume loaded into library library

name did not have a valid label. Please
load a scratch volume with a valid label.
SCAN LIBRARY process for library

library name has been canceled.
Scanning for library library name.

command, this message displays the status for an
SCAN LIBRARY process on the server.
Explanation: During normal operations a MANUAL

library will prompt the user for the desired volume
name if the volume does not have a valid label and the
AUTOLABEL parameter is turned on. However, the
utility mode of DUMPDB cannot prompt the user for a
desired volume name.
System action: The server unloads the volume and

asks for a new scratch volume with a valid label.
ANR8982E
User response: The user needs to insert scratch

volumes with valid labels or reissue the DUMPDB
command and specify the desired volume name on the
command line with the VOLUMENAMES parameter.
See the DUMPDB documentation.
Explanation: The background process for an SCAN

LIBRARY command has failed.
ANR8978W
The number of drives in library library

name has been increased from original
drive count to new drive count Please
restart the TSM server to update the
configuration;
Explanation: The number of drives in the library has

been increased. The new configuration will be recorded
if TSM server is restarted.
System action: .
User response: Number of drives in the library has
been increased. The user needs to restart the TSM
server to capture the new configuration.
ANR8979I

Explanation: A sacn library process has been started

for the given library. The process is assigned the ID
specified in the message.
to perform the operation in response to the SCAN

PROCESS command.
System action: The background process ends.

and ready, then reissue the command.
ANR8983I

library name completed successfully.
Explanation: The background process for an SCAN

LIBRARY command has completed successfully.
System action: The library has been scaned.
ANR8984E
The drive drive name in library library

name is incapable of performing any
drive encryption operations.
Explanation: The server queried the drives encryption

capability, and the query failed or the query showed
that the drive does not have encryption capabilities.
System action: The mount operation fails.
User response: If this message occurs on a scratch
mount and drive encryption has not been utilized yet,
you can turn drive encryption off by updating the
DRIVEENCRYPTION parameter on the device class.
597
ANR8985E ANR9579W (Solaris)

Otherwise, verify your hardware configuration. First,
verify that all the drives in this logical library support
drive encryption. Second, verify that the device driver
controlling all of the drives in this library also supports
drive encryption. If both the drives and the device
driver support drive encryption, call your drive
hardware support.
ANR8985E
The drive drive name in library library

name is using an encryption method that
is incompatible with the current server
settings.
Explanation: The server requires the drive to use

various drive encryption methods based on the
DRIVEENCRYPTION device class parameter for empty
volumes or based on the previous encryption method
used for filling volumes. The server is unable to
properly handle the volumes encryption key without
resolving this conflict.
User response: If this message occurs while mounting
an empty volume the encryption method setup in your
hardware environment is incompatible with the
DRIVEENCRYPTION setting in your device class.
Either update the device class or your hardwares
encryption method such that these setting no longer
conflict. If this message occurs while mounting a filling
volume, either update your hardware configuration to
the same method used while originally backing up this
volume, which can be determined by the QUERY
VOLUME FORMAT=DETAIL command, or update this
volumes access to UNAVAILABLE.
ANR8986E
The server currently doesnt allow AES

encryption which is required for drive
encryption support with the
DRIVEENCRYPTION=ON parameter on
the device class.
Explanation: Without AES encryption support the

server cannot generate adequately strong enough
encryption keys for drive encryption.
User response: Update the DRIVEENCRYPTION
parameter on the device class to a value other than
ON.
ANR8987W
The server will not encrypt the volume

volume name.
Explanation: Drive encryption with the device class

parameter setting of DRIVEENCRYPTION=ON will
only encrypt storage pool volumes. Thus, backupsets,
DB backups, and export volumes will not be encrypted.
System action: The mount continues, but encryption is
not used.
User response: If encryption is needed for this volume
598
or other backupsets, DB backups, or export volumes,

use a different method of encryption: use a device class
parameter of DRIVEENCRYPTION=ALLOW and a
hardware method of Library or System (do not use
the Application method).
ANR9579W (HP-UX) Command: Unable to locate file
file name.
Explanation: The specified file cannot be found. Note:
PREPARE assumes that the volume formatting program
(dsmfmt) is located in the same directory as the server
executable file.
System action: PREPARE uses the following default
file names in the plan file:
v For the server executable the default is
/opt/tivoli/tsm/server/bin/dsmserv.
v For the volume formatting program the default is
/opt/tivoli/tsm/server/bin/dsmfmt.
User response: Determine why file does not exist;
create if necessary.
ANR9579W (Linux) command: Unable to locate file file
name.
Explanation: The specified file cannot be found.
:Note.PREPARE assumes that the volume formatting
program (dsmfmt) is located in the same directory as
the server executable file.
/opt/IBMadsm-s/bin/dsmserv.
/opt/IBMadsm-s/bin/dsmfmt.
ANR9579W (Solaris) Command: Unable to locate file
file name.
(dsmfmt) is located in the same directory as the server
executable file.
/opt/tivoli/tsm/server/bin/dsmserv.
/opt/tivoli/tsm/server/bin/dsmfmt.
ANR9580W (Linux) ANR9582E (Solaris)

ANR9580W (Linux) Command: Generated replacement
volume name volume name may not be a
valid raw partition name. Original
volume name:volume name. Stanza is
stanza name.
name postfix to the original volume name has created a
name that may not be a valid raw partition name.
User response: Manually update the generated
recovery plan stanza with a legal replacement name.
The replacement name can be another raw partition
name or a regular file name.
ANR9580W (Solaris) Command: Generated
replacement volume name volume name
may not be a valid raw partition name.
Original volume name:volume name.
Stanza is stanza name.
name postfix to the original volume name has created a
name that may not be a valid raw partition name.
User response: Manually update the generated
recovery plan stanza with a legal replacement name.
The replacement name can be another raw partition
name or a regular file name.
ANR9581W (HP-UX) Command: Volume file name not
found while building stanza recovery
plan stanza name.
Explanation: This volume is defined to the server but
does not exist. The device class associated with the
volume is DISK or the device class device type is FILE.
System action: The entry for the volume is not
included in the recovery plan stanza.
ANR9581W (Solaris) Command: Volume file name not

plan stanza name.
ANR9582E (HP-UX) Command: Generated file name
too long. Length of directory or prefix
prefix plus name exceeds maximum
Explanation: The file name generated is too long. The
maximum valid length is shown in the message.
valid prefix. The following commands are used to
specify the prefix:
v SET DRMPLANPREFIX
v SET DRMINSTRPREFIX
v PREPARE
ANR9582E (Linux) command: Generated file name too
long. Length of directory or prefix
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9581W (Linux) command: Volume file name not

plan stanza name.
ANR9582E (Solaris) Command: Generated file name

too long. Length of directory or prefix




specify the prefix:
v SET DRMPLANPREFIX
599
ANR9583E (HP-UX) ANR9586E (HP-UX)

v PREPARE
ANR9583E (HP-UX) Command: Cannot generate fully
qualified file name for name.
Explanation: A failure occurred expanding the
specified file name.
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9583E (Linux) command: Cannot generate fully
specify the prefix:
v SET DRMPLANPREFIX
ANR9584E (Linux) command: Cannot generate server

options file name.
Explanation: A failure occurred generating the server
options file name.
information.
ANR9584E (Solaris) Command: Cannot generate
server options file name.
options file name.
information.
ANR9585E (HP-UX) Command: Cannot generate a
volume history file name.
Explanation: A failure occurred generating the volume
history file name.
information.
v PREPARE
ANR9585E (Linux) command: Cannot generate a

ANR9583E (Solaris) Command: Cannot generate fully


history file name.


information.

specify the prefix:
ANR9585E (Solaris) Command: Cannot generate a

v SET DRMPLANPREFIX

history file name.
v PREPARE
ANR9584E (HP-UX) command: Cannot generate server

options file name.

information.

options file name.
ANR9586E (HP-UX) Command: Cannot generate a

device configuration file name.
Explanation: A failure occurred generating the device

configuration file name.

information.

information.
600
ANR9586E (Linux) ANR9602E

ANR9586E (Linux) command: Cannot generate a
ANR9601E

Explanation: The server licensing functions

encountered an internal error in accessing license
information for the server storage capacity and number
of registered clients.

information.
ANR9586E (Solaris) Command: Cannot generate a
information.
ANR9600E
Invalid information passed to NETLS

license interface.

The NETLS license interface was not

initialized properly.
System action: Server operation continues. New

licensing information is not used by the server.
ANR9601E
The NETLS license interface was not

initialized properly.


ANR9601E (Solaris) Failed to allocate message queue

for the shared memory communications
Error: error text.

Explanation: An error has occurred when attempting

to get memory for the shared communications option.
ANR9600E
System action: Shared memory communications will

not be activated.
Invalid information passed to NETLS

license interface.

User response: If the error given is ENOSPC, the

maximum number of system message queue have
likely been exceeded. update /etc/system with set
shmsys:msginfo_msgmni=100. Any other error
suggests an internal problem and shoud be reported.

ANR9602E

ANR9600E (Solaris) Failed to allocate memory for
shared memory communications. Error:
error text.
not be activated.
User response: The maximum shared memory is, most
likely, too small. To increase on SUN, update
/etc/system with set
shmsys:shminfo_shmmax=268435456 (a recommended
size).
Invalid JOB information passed to the

NETLS Interface.

ANR9602E
Invalid JOB information passed to the

NETLS Interface.

601
ANR9602E (Solaris) ANR9606E

ANR9602E (Solaris) Error errno while attaching
memory segment for shared memory
communications.
attach a shared memory segment for a shared
communications session.
session does not initialize.
User response: Check the SUN documentation for the
shmat subroutine and determine what the errno
indicates, and take the appropriate action to correct the
error.
ANR9603E
The NETLS Nodelock file could not be

created.
Explanation: The server was not able to create the file

/usr/lib/netls/conf/nodelock which is used for storing
license password information.
User response: If the server is not running with root
authority, make sure that directory authorities in the
/usr/lib/netls/conf path are set so that the user ID
under which the server is running can create, read, and
write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your
service representative for assistance in resolving this
problem.
ANR9603E
The NETLS Nodelock file could not be

created.
Explanation: The server was not able to create the file

/usr/lib/netls/conf/nodelock which is used for storing
license password information.
problem.
ANR9604E
The NETLS license interface

encountered an internal error.

ANR9604E
The NETLS license interface

encountered an internal error.

ANR9605E
An invalid vendor ID was passed to

NETLS.

ANR9605E
An invalid vendor ID was passed to

NETLS.

ANR9606E
NETLS failed to find socket families to

contact a server.

602
ANR9606E ANR9610E
ANR9606E
NETLS failed to find socket families to

contact a server.


ANR9609E
Incorrect license entered: Password

entered = password Annotation entered =
annotation.

Explanation: The license information entered for a

REGISTER LICENSE command is not correct.

ANR9607E
No NETLS Servers found.

User response: Register the license again with the

REGISTER LICENSE command. Be sure to correctly
enter the license information.
ANR9609E
Incorrect license entered: Password

entered = password Annotation entered =
annotation.

Explanation: The license information entered for a

REGISTER LICENSE command is not correct.

ANR9607E
No NETLS Servers found.

ANR9608E
A NETLS Security Breach was

encountered.

User response: Register the license again with the

REGISTER LICENSE command. Be sure to correctly
enter the license information.
ANR9610E
Unable to create directory: directory.
Explanation: The REGISTER LICENSE command is

unable to either create or verify the specified directory
structure.
problem.
ANR9610E
Unable to create directory: directory.

structure.
ANR9608E
A NETLS Security Breach was

encountered.


603
ANR9610E (Linux) ANR9613W

problem.
ANR9610E (Linux) Unable to create directory:
directory.
structure.

problem.
ANR9612E
Error writing to NODELOCK file.
Explanation: The REGISTER LICENSE command fails

writing to the nodelock file.

given directory path are set so that the user under
which the server is running can create, read, and write
to the servers license file. If the server is running with
root authority, contact your service representative for
assistance in resolving this problem.

problem.
ANR9610E (Solaris) Unable to create directory:

directory.
structure.
given directory path are set so that the user under
which the server is running can create, read, and write
to the servers license file. If the server is running with
root authority, contact your service representative for
assistance in resolving this problem.
ANR9611E
Unable to open NODELOCK file: file.

unable to either create or open the nodelock file.
problem.
ANR9611E
Unable to open NODELOCK file: file.

unable to either create or open the nodelock file.
604
ANR9612E
Error writing to NODELOCK file.

writing to the nodelock file.
problem.
ANR9613W
Error loading modname for Licensing

function: error string.
Explanation: The server cannot load file module

modname to initialize licensing functions due to error
error string.
System action: Server operation continues. Default
licensing values are in effect for running the server.
User response: The dsmreg.lic module is accessed as
part of the load process for licensing. It should be in
the same directory as the dsmserv executable or it must
be in a directory that is pointed to by the
DSMSERV_DIR environment variable. The dsmreg.lic
module is only installed when you purchase the
product.
ANR9613W
Error loading modname for Licensing

function: error string.

error string.
ANR9613W (HP-UX) ANR9615E

product.
ANR9613W (HP-UX) Error loading modname for
Licensing function: error string.
error string.
product.
ANR9613W (Linux) Error loading modname for
Licensing function.
modname to initialize licensing functions.
User response: dsmreg.lic is accessed as part of the
load process for licensing. It should be in the same
directory as the dsmserv executable file or it must be in
a directory that is pointed to by the DSMSERV_DIR
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9613W (Solaris) Error loading modname for
Licensing function: error string.
error string.
User response: dsmreg.lic is accessed as part of the
load process for licensing. It should be in the same
directory as the dsmserv executable file or it must be in
a directory that is pointed to by the DSMSERV_DIR
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9614E
Unable to open license file: file.

unable to create or open the server license file.
User response: Make sure that the user ID under
which the server is running has the authority required
to create or write, or both, to the license file in the
directory in which the server is running. If this does
not resolve the problem, contact your service
ANR9614E
Unable to open license file: file.

unable to create or open the server license file.
ANR9614E (Linux) Unable to open license file: file.
unable to either create or open the server license file.
ANR9614E (Solaris) Unable to open license file: file.
unable to either create or open the server license file.
ANR9615E
Error writing to adsmserv.licenses file.

writing to the server license file.
605
ANR9615E ANR9617I
directory in which the server is running. Also, ensure
that free space is available in the file system so that the
license information can be written to the file. If this
does not resolve the problem, contact your service
System action: The invalid record is ignored.
ANR9615E
Explanation: The license manager found an invalid

record in the server license file (adsmserv.licenses). The
record is ignored.
Error writing to adsmserv.licenses file.

directory in which the server is running. Also, ensure
that free space is available in the file system so that the
license information can be written to the file. If this
does not resolve the problem, contact your service
ANR9615E (Linux) Error writing to adsmserv.licenses
file.
User response: Erase the adsmserv.licenses file and

reregister your licenses.
ANR9616I
Invalid license record record value found

in license file - it will be skipped.

reregister your licenses.
ANR9616W (Linux) Invalid license record record value
found in license file - it will be ignored.
record is ignored.
reregister your licenses. Refer to the licenses provided
to you to ensure that only valid licenses are specified
with the REGISTER LICENSE command.

User response: Make sure that the userid under which
the server is running has the authority required to
create and/or write to the license file in the directory in
which the server is running. Also ensure that there is
free space available in the filesystem so that the license
information can be written to the file. If this does not
resolve the problem contact your service representative
for assistance.
ANR9615E (Solaris) Error writing to
adsmserv.licenses file.
User response: Make sure that the userid under which
the server is running has the authority required to
create and/or write to the license file in the directory in
which the server is running. Also ensure that there is
free space available in the filesystem so that the license
information can be written to the file. If this does not
resolve the problem contact your service representative
for assistance.
ANR9616I
Invalid license record record value found

in license file - it will be skipped.

record is ignored.
606
ANR9616W (Solaris) Invalid license record record

value found in license file - it will be
ignored.
record is ignored.
reregister your licenses. Refer to the licenses provided
to you to ensure that only valid licenses are specified
with the REGISTER LICENSE command.
ANR9617I
Invalid license authorization:

authorization string.
Explanation: The license authorization specified for a

REGISTER LICENSE command is not valid.
System action: Server operation continues; licensing
terms are not changed by the REGISTER LICENSE
command.
User response: Examine the license authorization
string that was entered with the REGISTER LICENSE
command. Reenter the command if the license
authorization was not specified correctly. If the license
authorization has been specified correctly, contact your
ANR9617I ANR9618E (Solaris)

ANR9617I
Invalid license authorization:


command.
User response: Examine the license authorization
string that was entered with the REGISTER LICENSE
command. Reenter the command if the license
authorization was not specified correctly. If the license
authorization has been specified correctly, contact your
ANR9617W (Linux) Invalid license authorization:
command.
User response: Examine the license authorization that
was entered using the REGISTER LICENSE command.
Reenter the command if the license authorization was
not specified correctly. If the license authorization has
been specified correctly, contact your service
representative.
ANR9617W (Solaris) Invalid license authorization:
command.
User response: Examine the license authorization that
was entered using the REGISTER LICENSE command.
Reenter the command if the license authorization was
not specified correctly. If the license authorization has
been specified correctly, contact your service
representative.
ANR9618E
License registration is not supported on

this server.
Explanation: The REGISTER LICENSE command

failed because the license authorization module cannot
be found.
command.
User response: The license authorization file is
required for formal licensing for the z/OS server. The
file is delivered when the product is purchased, but it

is not available in the product service stream or with
demonstration copies of the server. If you have
purchased the server, contact your service
representative for assistance in resolving this problem.
ANR9618E

this server.

because the license authorization module cannot be
found.
command.
required for formal licensing for the AIX/6000 server.
The file is delivered when the product is purchased,
but it is not available in the product service stream or
with demonstration copies of the server. If you have
ANR9618E (Linux) License registration is not
supported on this server.
failed because the license authorization module could
not be found.
command.
required for formal licensing for the server. The file is
delivered when the product is purchased, but is not
available in the product service stream or with
purchased the server, please contact your service
representation for assistance in resolving this problem.
ANR9618E (Solaris) License registration is not
failed because the license authorization module could
not be found.
command.
delivered when the server is purchased, but is not
purchased the server, please contact your service
representation for assistance in resolving this problem.
607
ANR9622I ANR9624E
Explanation: The z/OS server is distributed with an

evaluation license for Space Management support. If no
formal license is found for the server and the
evaluation period has not lapsed, this message is
displayed each time the server checks the server license
terms.
regarding machines and recovery media, allows

management of offsite recovery media, collects and
stores information in the server for server recovery and
allows data base and storage pool backups to a device
class of type server. The server checks this license when
machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked
and when a data base backup or storage pool backup
to a device class of type server are performed to ensure
that the server is licensed to perform this function.
System action: The Space Management license allows

clients to utilize the server for storing files migrated
during space management. The server checks this
license when files are migrated to the server from client
nodes to ensure that the server is licensed to perform
this function.
User response: If you are interested in using the

server, contact your service representative to obtain
formal licenses for the server before the evaluation
period has elapsed. Without formal licenses, the server
will not support Disaster Recovery Manager after the
expiration date shown.
ANR9622I
An EVALUATION LICENSE for support

of Space Management will expire on
expiration date.

will not support Space Management after the expiration
date shown.
ANR9622I

of Tivoli Space Management will expire
on expiration date.
Explanation: The AIX/6000 server is distributed with

an evaluation license for Tivoli Space Management
support. If no formal license is found for the server and
the evaluation period has not lapsed, this message is
terms.
System action: The Tivoli Space Management license
allows clients to utilize the server for storing files
migrated during space management. The server checks
this license when files are migrated to the server from
client nodes to ensure that the server is licensed to
perform this function.
will not support Tivoli Space Management after the
ANR9623I

of Disaster Recovery Manager will
expire on expiration date.
Explanation: The z/OS server is distributed with an

evaluation license for Disaster Recovery Manager
terms.
System action: The Disaster Recovery Manager license
allows customers to store information in the server
608
ANR9623I

of Tivoli Disaster Recovery Manager
will expire on expiration date.
Explanation: The AIX/6000 server is distributed with

an evaluation license for Tivoli Disaster Recovery
Manager support. If no formal license is found for the
server and the evaluation period has not lapsed, this
message is displayed each time the server checks the
server license terms.
System action: The Tivoli Disaster Recovery Manager
license allows customers to store information in the
server regarding machines and recovery media, allows
will not support Tivoli Disaster Recovery Manager after
the expiration date shown.
ANR9624E
Unexpected error encountered in iFor/LS

(SystemView License Use Management)
routine license interface name
status=xreported status code.
Explanation: The server encountered an unexpected

error in accessing the SystemView License Use
Management function specified.
System action: The server license monitoring
operation fails
User response: The SystemView License Use
Management product is installed during normal z/OS
ANR9624E ANR9624I (Windows)

server installation. Check to make sure that the server
was installed correctly. If the installation was
successful, re-boot your z/OS system and re-start the
server. If this message continues to be issued, contact
ANR9624E
Unexpected error encountered in iFor/LS

(SystemView License Use Management)
routine license interface name
status=xreported status code.

operation fails
Management product is installed during normal AIX
server installation. Check to make sure that server was
installed correctly. If the installation was successful,
re-boot your AIX system and re-start the server. If this
message continues to be issued, contact your service
representative.
ANR9624I (HP-UX) An EVALUATION LICENSE for
support of Tivoli Space Management
Explanation: The server is distributed with an
evaluation license for Tivoli Space Management
terms.
ANR9624I (Linux) An EVALUATION LICENSE for
terms.

ANR9624I (Solaris) An EVALUATION LICENSE for
terms.
ANR9624I (Windows) An EVALUATION LICENSE
for support of Tivoli Space Management
terms.

609
ANR9625E ANR9625I (Solaris)

ANR9625E
Could not open file file name.
Explanation: The server could not open the license

certificate file specified.
System action: The license registration command fails.
User response: Examine the file specification entered,
including wildcard characters, to determine if it names
the license certificate file(s) you intended to use. If an
error is found, re-try the command with the corrected
specification. If an error cannot be found, contact your
ANR9625E
Could not open file file name.

ANR9625I (HP-UX) An EVALUATION LICENSE for
support of Tivoli Disaster Recovery
Manager will expire on expiration date.
evaluation license for Tivoli Disaster Recovery Manager
terms.
610
ANR9625I (Linux) An EVALUATION LICENSE for

support. If no formal license is found for the server,
and the evaluation period has not lapsed, this message
is displayed each time the server checks the server
license terms.
stores information in the server for server recovery, and
when PREPARE or MOVE DRMMEDIA are invoked,
ANR9625I (Solaris) An EVALUATION LICENSE for
terms.
ANR9625I (Windows) ANR9628E (Windows)

ANR9625I (Windows) An EVALUATION LICENSE
for support of Tivoli Disaster Recovery
terms.
ANR9626E
Invalid license certificate file: file name.
Explanation: The specified file does not contain valid

license certificate information.
System action: The license registration command
ignores the contents of the file.
ANR9626E
Invalid license certificate file: file name.
ANR9627E
Cannot access node license lock file: file

name.
Explanation: The server was not able to access the

specified file. The node lock file contains licensing
information for the server.
System action: The license function fails.
User response: Examine the file specification
displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is
either in the directory from which the server is started,
or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSERV_DIR
environment variable if this specification is in error.
Also ensure that there is sufficient space on the drive
specified for the file. If the problem persists after these
corrections have been made, contact your service
representative.
ANR9627E
Cannot access node license lock file: file

name.

representative.
ANR9628E (Windows) Unexpected error encountered
in iFor/LS (SystemView License Use
Management) routine license interface
name status=xreported status code.




operation fails


Management product is installed during normal server
installation. Check to make sure that the product was
re-boot your system and re-start the server. If this
representative.
611
ANR9629E (Windows) ANR9634E (HP-UX)

ANR9629E (Windows) Could not open file file name.
ANR9630E (Windows) Invalid license certificate file:
file name.
ANR9631E (Windows) Cannot access node license
lock file: file name.
environment variable. Re-specify the DSMSER-DIR
representative.
ANR9632I (Windows) Cannot load licensing DLL
library: DLL file name : the server will
assume evaluation licensing mode.
Explanation: The server was not able to load the
specified dynamic link library.
System action: Server licensing asumes Try and Buy
mode with licenses for 180 days.
User response: The named DLL library(ies) are
required for the server to support feature licensing. If
you are running an evaluation copy of the server, this
612
message should not cause concern and is normal. If the

libraries are installed and this message continues to be
issued, contact a support representative for assistance.
ANR9634E
command name: No license certificate

files were found with the file name
specification specification.
Explanation: The server did not find any license

certificate file(s) with the file name specification
entered.
the license certificate file(s) you intended to use. The
file name specification indicates the fully qualified file
name the server was trying to read. The directory used
to locate the license certificate files when no explicit
path is provided is determined as follows:
v The directory path pointed by the environmental
variable DSMSERV_DIR if this variable is defined
v The current working directory of the server process if
the DSMSERV_DIR variable is not defined
If an error is found, re-try the command with the
corrected specification. If an error cannot be found,
ANR9634E
command name: No license certificate

files were found with the file name
specification specification.

entered.
the license certificate file(s) you intended to use. The
file name specification indicates the fully qualified file
name the server was trying to read. The directory used
to locate the license certificate files when no explicit
path is provided is determined as follows:
v The directory path pointed by the environmental
variable DSMSERV_DIR if this variable is defined
v The current working directory of the server process if
the DSMSERV_DIR variable is not defined
If an error is found, re-try the command with the
corrected specification. If an error cannot be found,
ANR9634E (HP-UX) command name: No license
certificate files were found with the file
name specification specification.
ANR9634E (Linux) ANR9635E (Windows)

entered.
ANR9634E (Linux) command name: No license
ANR9635E (HP-UX) Invalid license certificate file:

file name.

entered.
ANR9635E (Linux) Invalid license certificate file: file

name.


ANR9634E (Solaris) command name: No license
entered.
ANR9634E (Windows) command name: No license
entered.

ANR9635E (Solaris) Invalid license certificate file: file
name.
ANR9635E (Windows) Invalid license certificate file:
file name.
613
ANR9636E (HP-UX) ANR9637E (Windows)

ANR9636E (HP-UX) Could not open file file name.
ANR9636E (Linux) Could not open file file name.
ANR9636E (Solaris) Could not open file file name.

representative.
ANR9637E (Linux) Cannot access node license lock
file: file name.
environment variable. Re-specify the DSMSERV-DIR
representative.
ANR9637E (Solaris) Cannot access node license lock
file: file name.
ANR9636E (Windows) Could not open file file name.


environment variable. Re-specify the DSMSERV-DIR
representative.
ANR9637E (HP-UX) Cannot access node license lock

file: file name.
ANR9637E (Windows) Cannot access node license

lock file: file name.



614
ANR9638W ANR9639W (HP-UX)

environment variable. Re-specify the DSMSER-DIR
representative.
ANR9638W

this server.

found.
command.
delivered when the product is purchased, but it is not
ANR9638W (HP-UX) License registration is not
found.
command.
required for formal licensing for the HP-UX server. The
file is delivered when the server is purchased, but it is
not available in the product service stream or with
ANR9638W (Linux) License registration is not
found.
command.

ANR9638W (Solaris) License registration is not
found.
command.
required for formal licensing for the Sun Solaris server.
The file is delivered when the server is purchased, but
it is not available in the product service stream or with
ANR9638W (Windows) License registration is not
found.
command.
required for formal licensing for the Windows server.
The file is delivered when the product is purchased,
but it is not available in the product service stream or
with demonstration copies of the server. If you have
ANR9639W (HP-UX) Unable to load shared library
shared library.
Explanation: The server module is unable to load the
indicated shared library.
function that requires the shared library will be
inoperative.
User response: Ensure that the shared library is
accessible. If this is an evaluation copy of the server,
then this message is normal for the DSMREG library,
since the library is only provided with purchased
servers. The server licensing will assume Try and Buy
mode with sample licensed options for a period of
time.

delivered when the product is purchased, but it is not
615
ANR9639W (Linux) ANR9641W (Solaris)

ANR9639W (Linux) Unable to load Shared License
File shared library.
Explanation: The server was unable to loaded the
shared library.
functions that require the shared library will be
inoperative.
User response: Make sure the shared library is
accessible/readable. This message is normal for those
servers in the Try-N-Buy mode.
ANR9639W (Solaris) Unable to load Shared License
File shared library.
Explanation: The server was unable to loaded the
shared library.
functions that require the shared library will be
inoperative.
User response: Make sure the shared library is
accessible/readable. This message is normal for those
servers in the Try and Buy mode.
ANR9640E (HP-UX) Unable to load procedure
address from shared library shared
library.
address of a routine in the indicated shared library.
inoperative.
accessible. If the problem persists, contact your service
representative.
ANR9640E (Linux) Unable to load procedure address
from shared library shared library license
module.
address of a routine in the indicated shared library for
license loading.
inoperative.
accessible. If the problem persists, contact your
Customer Service Representative.
616
ANR9640E (Solaris) Unable to load procedure

address from shared library shared library
license module.
address of a routine in the indicated shared library for
license loading.
inoperative.
accessible. If the problem persists, contact your
customer service representative.
ANR9641W (HP-UX) One or more EVALUATION
LICENSES will expire on expiration date.
Explanation: Although you are running with a
purchased version of the server, there are one or more
licenses registered that will expire on the date specified.
This is usually the case when you have been using
evaluation licenses prior to purchasing the product.
User response: Halt the server and erase the nodelock
file in the server startup directory. After restarting the
server, use the REGISTER LICENSE command to define
the licensed features that you have purchased with
your server. These licenses should NOT have an
expiration date, so this message should not appear after
re-registering the proper licenses. If this message
ANR9641W (Linux) One or more EVALUATION
ANR9641W (Solaris) One or more EVALUATION
ANR9642E (HP-UX) ANR9655E (Solaris)

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
invalid.
System action: No additional licenses are registered.
User response: Obtain a valid license authorization
code and try the command again.
ANR9642E (Linux) The specified license
authorization code (license authorization
code) is invalid.
Explanation: The license authorization code which
you entered using the REGISTER LICENSE command is
invalid.
System action: No additional licenses are registered.
User response: Obtain a valid license authorization
code and try the command again.
ANR9653E (HP-UX) Unexpected error encountered in
iFor/LS (SystemView License Use
operation fails
representative.
ANR9653E (Solaris) Unexpected error encountered in
iFor/LS (SystemView License Use
operation fails

representative.
ANR9654E (HP-UX) Could not open file file name.
ANR9654E (Solaris) Could not open file file name.
ANR9655E (HP-UX) Invalid license certificate file:
file name.
ANR9655E (Solaris) Invalid license certificate file: file
name.
617
ANR9656E (HP-UX) ANR9677E

Error errno attaching memory segment
for shared memory communications.
ANR9656E (HP-UX) Cannot access node license lock

file: file name.
ANR9676E




representative.
ANR9656E (Solaris) Cannot access node license lock
file: file name.
representative.
ANR9676E
Error errno attaching memory segment

for shared memory communications.

User response: Check the z/OS documentation for the
shmat subroutine and determine what the error
number indicates. On z/OS, if the error number is
EMFILE, make sure the EXTSHM environment variable
is set to ON before starting the server. This allows the
server to support more than 3 concurrent shared
memory sessions.
User response: Check the AIX documentation for the

number indicates. On AIX, if the error number is
memory sessions.
ANR9676E (HP-UX) Error errno attaching memory
segment for shared memory
communications.
memory sessions.
ANR9676E (Linux) Error errno attaching memory
segment for shared memory
communications.
memory sessions.
ANR9677E
Failed to allocate memory for shared

memory communications. Error: error
text.

618
ANR9677E ANR9679W
not be activated.

not be activated.
ANR9677E
Failed to allocate memory for shared

memory communications. Error: error
text.

not be activated.
ANR9677E (HP-UX) Failed to allocate memory for
error text.
not be activated.
ANR9677E (Linux) Failed to allocate memory for
error text.
not be activated.
ANR9678E
Failed to allocate message queue for the

shared memory communications Error:
error text.

not be activated.
ANR9678E
Failed to allocate message queue for the

shared memory communications Error:
error text.

not be activated.
ANR9678E (HP-UX) Failed to allocate message queue
Error: error text.
ANR9678E (Linux) Failed to allocate message queue

Error: error text.
not be activated.
ANR9678W (Windows) File name used for server
executable. A server is currently running
as a service.
Explanation: The name of the executable used when
the server is running as a service cannot be used in the
plan file.
System action: PREPARE uses file name identified in
the message within the plan file and generation of the
plan file continues.
ANR9679W
Command: Unable to locate file file name.

(dsmfmt), is located in the same directory as the server
executable file.
/usr/tivoli/tsm/server/bin/dsmserv.
/usr/tivoli/tsm/server/bin/dsmfmt.
ANR9679W
Command: Unable to locate file file name.

(dsmfmt), is located in the same directory as the server
executable file.
/usr/tivoli/tsm/server/bin/dsmserv.
/usr/tivoli/tsm/server/bin/dsmfmt.
619

ANR9679W (Windows) Command: Unable to locate
file file name.
Explanation: The specified file cannot be found.
c:\progra~1\tivoli\tsm\server\dsmserv.
ANR9680W
Command: Catalog information cannot be

obtained for file file name.
Explanation: Catalog information cannot be obtained

for the file specified in the message. DRM does not
support creation of JCL for a file that is not catalogued.
System action: The stanzas, where JCL is created, for
this file will not contain volume or unit information.
User response: Catalog the file.
ANR9680W
Command: Could not obtain AIX logical

volume information for volume name
while building stanza recovery plan stanza
name.

PREPARE can not obtain AIX logical volume
information for it from the AIX Object Data Manager
(ODM).
User response: This message should be preceded by
another error message which contains the ODM error
code.
ANR9680W (HP-UX) Command: Could not obtain
logical volume information for volume
name while building stanza recovery plan
stanza name.
PREPARE can not obtain logical volume information
for it.
another error message which contains an error code.
ANR9680W (Solaris) Command: Could not obtain
logical volume information for volume
name while building stanza recovery plan
stanza name.
PREPARE can not obtain logical volume information

for it.
another error message which contains an error code.
ANR9680W (Windows) Unable to locate path for
component in registry.
Explanation: The path to the component could not be
found in the registry.
path names in the plan file:
v For the components installation directory the default
is c:\progra~1\tivoli\tsm\server\
v For the administrative command line client the
default is c:\progra~1\tivoli\tsm\baclient\
v For the disk formatting utility the default is
c:\progra~1\tivoli\tsm\utils\
User response: Determine why path does not exist;
install components if necessary.
ANR9681W
Command: Volume file name not found

name.

ANR9681W
Command: Volume file name not found

name.

User response: Determine why the file does not exist;
create it if necessary.
ANR9681W (Windows) Command: Volume file name
not found while building stanza recovery
plan stanza name.
620
ANR9682E ANR9684E
ANR9682E
Command: Generated file name too long.

Length of directory or prefix prefix plus
name exceeds maximum characters
characters.

history or device configuration file specified in the

message could not be determined. Either the volume
history or device configuration file specified in the plan
file does not exist or some other error has occurred.
System action: Recovery plan file was created using
the substitute name.
User response: Reissue the command after the volume
history or device configuration file has been backed up.
ANR9683E

specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
Command: Cannot generate fully

qualified file name for 'name'.

specify the prefix:
v SET DRMPLANPREFIX
ANR9682E
Command: Generated file name too long.

Length of directory or prefix 'prefix' plus
'name' exceeds maximum characters
characters.

specify the prefix:
v PREPARE
ANR9683E (Windows) Command: Cannot generate
fully qualified file name for name.
v SET DRMPLANPREFIX

specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
v PREPARE
ANR9682E (Windows) Command: Generated file

name too long. Length of directory or
prefix prefix plus name exceeds
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9683W

qualified file name for name. Prepare
will substitute file name default name.
Explanation: The fully qualified name for the volume
ANR9684E

Explanation: A failure occurred creating the specified

file name.
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9684E
Command: Cannot generate server

options file name.

options file name.
621
ANR9684E (Windows) ANR9713E


information.

information.
ANR9684E (Windows) Command: Cannot generate

server options file name.
ANR9690W
Command: Cannot obtain help file name.

options file name.
Explanation: Help file name cannot be obtained.

HLPAMENG will not be included in the
START.SERVER stanza of the plan file.

information.

ANR9691W
ANR9685E
Command: Catalog information cannot be

found for options file file name.
Explanation: The options file name specified in the

message is not cataloged. The options file must be
cataloged.
Command: Cannot obtain image file

name.
Explanation: Image file name cannot be obtained.

IMAGES will not be included in the START.SERVER
stanza of the plan file.
User response: Catalog the options file.

ANR9710E
ANR9685E
Command: Cannot generate a volume

history file name.

history file name.
information.
Explanation: There is not enough memory to operate

the label utility program.
System action: The program is halted.
User response: Provide more memory for the program
to use.
ANR9711E
ANR9685E (Windows) Command: Cannot generate a

Insufficient memory to continue

operations.
Unrecognized argument argument.
Explanation: The specified argument is not recognized

as one that is supported by the label utility program.

history file name.
User response: Retry the label utility program with

the correct argument syntax.

information.
ANR9686E
Command: Cannot generate a device


information.
ANR9686E (Windows) Command: Cannot generate a
622
ANR9712E
Argument has invalid value argument.
Explanation: The value specified for the given

argument is not valid.
ANR9713E
Only one library can be specified.
Explanation: Only one library can be specified in the

argument list for the label utility program.
ANR9714E ANR9723I
ANR9714E
No drives were specified.
Explanation: At least one drive must be specified for

use by the label utility (DSMLABEL) program.
program can be invoked with the -help argument to

determine this maximum value.
ANR9720I

ANR9715E
Error starting label activity for drive

drive name.
Explanation: The label utility is unable to start its

activity for the given drive.
Volume volume name was labeled

successfully using drive drive name.
Explanation: The volume is successfully labeled.

System action: The program continues operation.
ANR9721E
Volume name is not a valid volume

name.

volume name.
User response: Increase the number of allowed

threads or processes in the system, then retry the
operation.

volume name.
ANR9716E
Device library name is not accessible, or

is not recognized as a supported library
type.
Explanation: The device specified for the library

cannot be accessed or is not recognized as a supported
device.
User response: Enter a volume name that is within

the length constraints for the media type being labeled,
and which contains only alphanumeric characters.
ANR9722I

User response: Retry the operation, specifying a valid
supported library.
ANR9717E
Element address element address is not

valid for drive drive name.
Explanation: The specified element address does not

represent a valid drive location in the associated library.
element address for the drive.
ANR9718E
Device drive name is not recognized as a

supported drive type.
Explanation: The device specified for the drive is not

recognized as a supported device.
Insert a new volume in drive drive

name, then enter the name (1-maximum
length characters) to be used for its label;
or just press ENTER to quit this
program:
Explanation: The program prompts for a new volume

to be mounted in the given drive so that a label can be
written to it.
System action: The program waits for the volume
name to be entered.
User response: Mount a new volume, then type a
volume name for it and press ENTER; or, if you want
to quit the program, press ENTER without entering a
volume name.
ANR9723I
Insert side A of a new volume in drive

drive name, then enter the name
(1-maximum length characters) to be used
for its label; or just press ENTER to quit
this program:

written to it.

supported drive.

name to be entered.
ANR9719E
Too many drives were specified.
Explanation: The number of drives specified on the

command line exceeds the limits of the program.
User response: Mount side A of a new volume, then

type a volume name for it and press ENTER; or, if you
want to quit the program, press ENTER without
entering a volume name.

User response: Retry the operation, specifying only up
to the maximum number of supported drives. The
623
ANR9724I ANR9732I
ANR9724I
Flip the volume in drive drive name to

side B, then press ENTER.
ANR9729E
I/O error formatting volume volume

name in drive drive name.
Explanation: The program prompts for a two-sided

volume to be flipped so that its second side can be
labeled.
Explanation: An I/O error occurs while attempting to

format the media for the specified volume in the given
drive.
System action: The program waits for the ENTER key

to be pressed.
System action: The volume is not labeled.
User response: Flip the volume in the drive, and press

ENTER.
ANR9725E
The volume in drive drive name is

already labeled (volume name).
User response: Ensure that the volume is not write

protected, that the drive is powered on and ready, and
that the media is not damaged.
ANR9730I
Manual intervention required for library

device library device name.
Explanation: The volume in the specified drive cannot

be labeled because it already contains a valid label with
the given name.
Explanation: The specified library device requires

manual intervention before it can be accessed for
normal operations.
System action: The operation will be retried

periodically until either the required action is
performed or a timeout occurs.
User response: If an overwrite of the existing label

with a new label is desired, restart the DSMLABEL
utility program by using the -overwrite argument.
ANR9726E
I/O error writing label for volume

Explanation: An I/O error occurs while attempting to

write the label for the specified volume in the given
drive.
User response: If the library has an access door, make

sure it is in the closed position. If it has a cartridge
carousel, make sure the carousel is installed.
ANR9731I
Insert a new volume into the entry/exit

port of library library device name, then
enter the name (1-maximum length
characters) to be used for its label; or
just press ENTER to quit this program:
User response: Ensure that the volume is not write

protected, the drive is powered on and ready, and the
device parameter has the correct value.

to be mounted in the entry/exit port of the given
library so that a label can be written to it.
ANR9727E

name to be entered.
Media fault detected on volume volume

name in drive drive name.
Explanation: A media fault condition is detected for

the specified volume in the given drive.
User response: Insert a new volume into the

entry/exit port, then type a volume name for it and
press ENTER; or, if you want to quit the program,
press ENTER without entering a volume name.
User response: Remove the volume from use, since

the media is questionable. If the media in question
requires formatting, such as an unformatted optical
disk, retry the operation by starting the program with
the '-format' argument.
ANR9732I
ANR9728E

to be mounted in the entry/exit port of the given
library so that a label can be written to it.
Error ejecting volume from drive drive

name.
Explanation: An error occurs while ejecting the

volume from the given drive.
System action: All further activity on the given drive
is suspended.
User response: Ensure that the drive is in proper
operating condition before resuming its use.
624
Insert a new volume in the entry/exit

port of library library device name with
side A facing up, then enter the name
this program:

name to be entered.
User response: Insert a new volume into the
entry/exit port, then type a volume name for it and
ANR9733I ANR9740E
ANR9733I
Insert a new volume in drive drive name

of library library device name, then enter
the name (1-maximum length characters)
to be used for its label; or just press
ENTER to quit this program:

written to it.
name to be entered.
User response: Mount a new volume, close the library
access door, and then type a volume name for it and
ANR9734I
Insert side A of a new volume in drive

drive name of library library device
name, then enter the name (1-maximum
length characters) to be used for its label;
or just press ENTER to quit this
program:

written to it.
name to be entered.
User response: Mount side A of a new volume, close
the library access door, and then type a volume name
for it and press ENTER; or, if you want to quit the
program, press ENTER without entering a volume
name.
ANR9735I
Enter the name (1-maximum length

characters) for the next volume to label
in library library device name; or just
press ENTER to quit this program:
powered on and ready, any access doors are closed, the

device parameter has the correct value, and then retry
the operation that was in progress when the error
occurred.
ANR9737I
Remove the volume from drive drive

name in library library device name, then
press ENTER.
Explanation: All activity associated with the volume

in the given drive is complete, so it should be removed.
System action: The program waits until the ENTER
key is pressed.
User response: Remove the volume from the specified
drive, then close the library access door and press
ENTER.
ANR9738I
Remove the volume from the entry/exit

port of library library device name, then
press ENTER.

in the entry/exit port is complete, so it should be
removed.
key is pressed.
entry/exit port, and press ENTER.
ANR9739I
Initializing library device library device

name.
Explanation: The specified library device is being

initialized for use by the labeling utility program.
System action: The library device is prepared for use.
Volume volume name is not in the
INSERT category.
Explanation: The program prompts for the name of

the next volume to be labeled in the given library.
ANR9740E

name to be entered.
Explanation: The specified volume cannot be labeled

because it is not in the librarys insert category. This
restriction is provided as a safeguard against labeling
volumes that are in use, and possibly destroying valid
data.
User response: Type the name for the next volume to

be labeled and then press ENTER; or, if you want to
quit the program, press ENTER without entering a
volume name.
ANR9736E

library device library device name.
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 then
reinserted with the librarys convenience I/O station.
This will cause the volumes category code to be
changed to the INSERT category, and thus allow the
labeling operation to work.
System action: If the error is noncritical, operation

continues; otherwise, the program is halted.
625
ANR9741E ANR9749I
ANR9741E
Drives drive name and drive name

cannot use the same element address.
Explanation: The element addresses specified for the

given drives are the same. This is not allowed, since the
element address is the only way in which the robot can
distinguish between different drives in a SCSI library.
System action: The program is stopped.
User response: Restart the program, providing valid
and unique element addresses. Appropriate values can
be determined with the worksheets in Administrators
Guide.
ANR9742E
The element address for drive drive

name is missing or invalid.
Explanation: The element address value for the

specified drive is omitted, or an illegal value has been
provided.
System action: The program is stopped.
ANR9746E
Explanation: An error occurs while opening the

specified file for writing trace data.
User response: Retry the program, specifying a valid
file name for the trace file.
ANR9747I
Attempting to label volume volume

name using drive drive name...
Explanation: The specified volume is in the process of

being labeled in the given drive.
System action: Labeling activity continues.
ANR9744E
Volume volume name is not present in

Explanation: The specified volume is not present in

the given library, so it cannot be labeled.
System action: Labeling activity continues for other
volumes.
User response: Insert the volume into the library, then
ANR9745E
Only one trace argument is allowed.
Explanation: More than one trace argument has been

encountered, but only one is allowed.
User response: Retry the program, specifying at most
one trace argument.
Unable to write to trace file.
Explanation: An error occurs while writing data to the

trace file.
System action: The program continues, but trace data
may be lost.
User response: Make sure the disk that contains the
trace file is not full or defective and then retry the
operation.
ANR9748I
User response: Restart the program, providing a valid

element address. Appropriate values can be determined
with the worksheets in Administrators Guide.
ANR9743I
Unable to open trace file file name.
Insert a new volume into slot with

element number slot element address of
library library device name, then enter
the name (1-maximum length characters)
to be used for its label; or just press
ENTER to quit this program:

to be inserted into the given slot with the specified
element number so that a label can be written to it. For
the slot and element number diagram of your library,
refer to the documentation provided with the current
PTF level or refer to the Administrators Guide for your
release and platform.
name to be entered.
User response: Insert a new volume, close the library
access door, type a volume name for it, and press
ENTER; or, if you want to quit the program, press
ENTER without entering a volume name.
ANR9749I
Insert a new volume into slot with

element number slot element address of
library library device name with side A
facing up, then enter the name
this program:

to be inserted into the slot with the specified element
number so that a label can be written to it. For the slot
and element number diagram of your library, refer to
the documentation provided with the current PTF level
or refer to the Installing the Server and Administrative
Client manual for your release and platform.
name to be entered.
626
ANR9750I ANR9758W
User response: Insert side A of a new volume, close
the library access door, type a volume name for it, and
ANR9750I
Remove the volume from slot with

element number slot element address in
library library device name, then press
ENTER.

in the given slot with the specified element number is
complete, so it should be removed. For the slot and
element number diagram of your library, refer to the
documentation provided with the current PTF level or
refer to the Administrators Guide for your release and
platform.
ANR9754I
Barcode of element slot element address,

hardware barcode string, exceeds maximum
length characters in length.
Explanation: A barcode is encountered that was

longer than a valid volume name.
System action: The barcode is not considered valid
and will not be used for the server process.
User response: Replace the cartridges barcode with
one that is supported by the library and whose number
of characters does not exceed the maximum length.
ANR9755E
There are no barcodes available.
Explanation: The hardware did not return any valid

barcode data for any cartridge.

key is pressed.
System action: The program terminates without

attempting to label any cartridges.
User response: Remove the volume from the specified

slot, close the library access door, and press ENTER.
User response: Make sure the hardware supports

barcodes, or that barcode labels have been affixed to
the cartridges.
ANR9751E
The volume in drive drive name is not

compatible with the drive.
Explanation: The volume cannot be used in the drive.

It is most likely an outdated media type that the drive
cannot write.
User response: Remove the volume; replace it with a
different type known to work in the drive, or press
ENTER to end the program.
ANR9752E
Could not access drive drive name. It

may be in use by another application.
ANR9756I
Explanation: No volumes are found in the library.

This means that in a 349x ATL, no volumes were found
in the insert category (xFF00), and that in a SCSI
autochanger, no cartridges were loaded into the library.
System action: The program terminates normally.
User response: Insert cartridges into the library. For a
349x ATL, this may involve changing the category of
previously inserted cartridges to be relabeled.
ANR9757E
Explanation: The specified drive cannot be accessed.

User response: Ensure that the drive name is correct
and the device is not in use by another application,
then retry the operation.
ANR9753E
Skipping slot element address slot

element address, which has no barcode.
Explanation: The cartridge in the indicated slot will

not be labeled, since it does not have a valid barcode.
System action: The program attempts to label the next
cartridge.
User response: Examine the cartridge to see if it has a
barcode. Add a barcode if required.
No volumes were found.
ACS drive id ACS drive id is not valid

for drive drive name.
Explanation: The specified ACS drive id does not

represent a valid drive location in the associated library.
drive id for the drive.
ANR9758W
Error mounting volume volume name.
Explanation: An error occurs while mounting the

volume to the drive. This may not be an error since the
volume or drive maybe in use or locked in a shared
environment.
System action: The specified volume is bypassed for
labeling.
User response: Ensure that the volume is not locked
or in use if label is required.
627
ANR9759E ANR9776I
ANR9759E
unsuccessful ACSAPI response,

status=acs status.
Explanation: The ACSLS library API responded with

an unsuccessful status as indicated.
System action: Depends on the ACS API for labeling,
the process may continue as the error may not be a
problem.
User response: If the label process terminates, contact
your ACS System Administrator and perform ACSLS
library problem determination.
ANR9760I
Wait and monitor the ACSSA console

message to remove volume volume id
from CAP.
Explanation: The specified volume is about to put into

CAP for removal. Monitor the ACSSA console and
removed the volume after it has been placed into the
CAP as indicated in the ACSSA message.
User response: Monitor the ACSSA console and wait.
ANR9761E
The path of drive drive name in library

library name has been changed from
original drive path to new drive path The
new path will not be updated because
we can not get the model type using
new path.
Explanation: The drives new path can not be updated

because we detect a different device type compared to
the Database using this new path. The problem may be
the new path has an incorrect format for the device
driver.
System action: .
User response: The user needs to check if there are
two device special file names for the same drive. For
AIX, please make sure the IBM drive is /dev/rmt and
TSM drive is /dev/mt. For Solaris, please make sure
the Solaris native device driver is not installed.
ANR9771E
Volume volume name has an incorrect

barcode label describing the volumes
WORM type.
Explanation: In an attempt to CHECKIN or LABEL a

volume it was discovered that the volumes true
WORM characteristic didnt match that described by its
barcode label.
System action: The volume is not checked in.
User response: The volume was probably mislabeled.
Find the volume in the library. Simply remove the
volume, or swap the barcode label with a label of the
opposite WORM characteristic (WORM for non-WORM
or vice versa) and retry the check in command.
628
ANR9773E
Hardware configuration error in library

library name: number of drives drives,
number of storage slots storage slots.
Explanation: The library device returned a count of

zero for either the drives or the slots. The drives may
have not yet been configured to the operating system,
or to the library. The library must have at least one
drive and multiple slots when properly configured in
order to be defined to the server.
User response: Configure the drives to the operating
system, and reinitialize the library.
ANR9774W
Volume volume name should be freed of

data as soon as possible.
Explanation: The server has received an indication

from the 3995 that the indicated volume is out of spare
sectors for re-allocation. Spare sectors are reserved to
take the place of sectors that experience I/O problems.
The re-allocation can take place on either a read or
write.
System action: The indicated volume is marked
read-only by the server.
User response: A MOVE DATA command should be
used as soon as possible to move the data from this
cartridge to other cartridges in the library. This
cartridge should NOT be marked read-write again
through the UPDATE VOLUME command.
ANR9775E
Error while writing on volume volume

name (RC=internal code).
Explanation: An I/O error has occurred while writing

on the specified volume.
User response: Ensure that the 3995 volume is
accessible and that the media is usable. Diagnostics
may have to be run on the 3995 with the specified
volume. If the problem persists, contact your service
representative and provide the internal code values
from this message. The internal code is returned to the
server from the OS/2 operating system.
ANR9776I
File file name is being erased and

deleted. Data erasure may take several
minutes.
Explanation: A file is being deleted from an optical

library cartridge. The file is deleted when a LAN3995
device class volume is deleted. File deletion includes
erasure of data. The erasure process can take several
minutes to complete.
ANR9778E ANR9786E
ANR9778E
Unable to establish a communication

session with the primary library
manager.
Explanation: The requested operation required that a

communication session be established with a library
manager. The library manager was found to be
unavailable at this time.
User response: Verify the primary library manager is
up and operational. Once the server is verified to be
operational, retry the operation.
ANR9779E
Unable to acquire a drive for volume

volume name from the library manager.
Explanation: The library manager was unable to

assign a drive to the library client. There are a couple
of situations that can cause this error.
v All drives are currently allocated to other library
clients or the library manager.
v The request for a specific drive cannot be satisfied.
This can occur if a drive on the library client side is
marked offline or is currently busy with another
process.
v A communication error occurred during the request
to mount a volume.
v The requested volume was not present in the library
managers inventory
User response: Verify that a drive is available on the
library manager side and the drive is currently not
busy or marked offline on the library client. Set the
mount retention on the device class on the library
manager and the library clients to a lower value. Using
a lower mount retention value can free up drives.
ANR9780E
Volume volume name is not mounted in

drive from the library drive name.
Explanation: A communication error occurred while

dismount the volume.
User response: Verify that the volume has been

dismounted.
ANR9782E
Primary Library Manager primary library

manager name is NOT defined as a
server.
Explanation: The primary library manager server has

not be defined to this server.
User response: Define the server to this server using
the DEFINE SERVER command.
ANR9783E
Primary Library Manager does not

contain a valid value.
Explanation: The primary library manager server has

not be defined to this server.
ANR9784E
Secondary Library Manager secondary

library manager name is NOT defined as a
server.
Explanation: The secondary library manager server

name has not be defined to this server.
ANR9785E
Drive drive name, is not defined on the

library manager.
Explanation: A drive is being defined that does not

exist or is being managed by the library manager.
User response: Verify drive name with the library
manager.
ANR9786E
User response: Verify the library manager is up and

operational. Verify that the library manager and library
client can communicate using command routing.
Explanation: A communication error occurred.
ANR9781E
Volser volume name was not found to be

mounted on the library manager.
Explanation: According to the library manager the

requested volume is no longer mounted. The can
occurred if the library manager forced the volume to be
dismounted because of a communication error.
A communication error has occurred.

Operation ending.

User response: Verify the library manager is up and
operational. Verify that the library manager and library
client can communicate using command routing.
629
ANR9787E ANR9796E
ANR9787E
The owner name specified is not

defined to this server.
Explanation: A command was issued specifying

ownership of a volume. The name of the owner given
was not defined to this server.
ANR9788E

defined - the primary library manager
not defined.
Explanation: The designated library is not defined

because the primary library manager is not defined as a
server to this server.
ANR9789E

defined - the secondary library manager
not defined.
Explanation: The designated library is not defined

because the secondary library manager is not defined
as a server to this server.
ANR9790W
Request to mount volume Volume Name

for library client Library Client Name
failed.
Explanation: A library client requested a volume to be

mount by the library manager, which in turn failed.
User response: Verify the status of all drives are
currently online and not in use by other library clients
or the library manager itself. Free up drive resources as
needed.
ANR9791I
Volume Volume Name in library Library

Name ownership is changing from
Current volume owner to New Volume
owner.
Explanation: In a shared library, the volume

ownership has been changed from current owner to
new owner.
630
ANR9792E
Library Library Name on library manager

Library Manager Name is currently not
being shared.
Explanation: A define library command attempted to

define a shared library that was not being shared by
the library manager.
User response: Verify the library on the library
manager is being shared. If the library is not being
shared, update the library shared status to yes.
ANR9793I
process name in library library nameCANCEL PENDING.

process on the server. The command was started, but
the process was canceled by an administrator.
being terminated.
ANR9794E
Unable to load the RSM dynamic link

library dynamic link library.

indicated dynamic link library.
function that requires the dynamic link library will be
inoperative.
User response: Ensure that the installed Windows
version supports RSM. Ensure that the Removable
Storage Manager is installed and the system DLL is
accessible.
ANR9795E
Command: Invalid storage agent name

storage agent name.
Explanation: The designated storage agent name is

invalid; either it contains too many characters, or some
of the characters are invalid.
storage agent name.
ANR9796E
Command: Drive mapping is already

defined for drive drive name in library
library name on storage agent storage agent
name.
Explanation: The designated drive mapping cannot be

defined because it has already been defined for the
specified drive, library, and storage agent.
ANR9797E ANR9900W
drive mapping, reissue the command with a different
drive name.
ANR9797E
Command: Drive mapping for drive drive

name is not defined in library library
name on storage agent storage agent name.
Explanation: The designated drive map has not been

defined for the given drive in the given library on the
given storage agent.
drive name. If appropriate, define the drive before
retrying the command.
ANR9798E

defined for drive drive name in library
library name.

because there are still paths defined for it.
User response: Delete all paths for the drive, and
ANR9799E
Command: Library Library Name is

currently not being shared.
Explanation: The command attempted to perform an

operation that is not allowed unless the library is
allowed to be shared.
shared, update the library shared parameter to yes.
ANR9800E
Library Library Name is currently not

being shared and attempted an
operation only allowed for shared
libraries.
Explanation: The command attempted to perform an

operation that is not allowed unless the library is
allowed to be shared.
shared, update the library shared parameter to yes.
ANR9801I (Windows) ANR9801: Ready for
operations.
Explanation: The device driver has successfully
initialized and is ready to accept requests from the
server.

ANR9803W (Windows) ANR9803: ERROR!
Insufficient free memory to initialize
driver.
Explanation: The server device driver is unable to
initialize due to an inability to acquire dynamic storage.
System action: Processing continues. The device
driver is not available to process requests from the
server.
User response: For minimum storage requirements,
refer to Licensed Program Specifications/2. You must have
sufficient memory in your system to initialize Windows
and the device drivers you want to use.
ANR9810I (Windows) ANR9810: SCSI Tape Device
Driver Initializing...
Explanation: The server SCSI tape device driver has
been invoked by the system and is initializing.
ANR9820I (Windows) ANR9820: SCSI Autochanger
Device Driver Initializing...
Explanation: The server SCSI automatic changer
device driver has been invoked by the system and is
initializing.
ANR9900W
Attention -- Accounting records could

not be written to the file: filespec.
Explanation: The server detects an error while trying

to open the accounting file.
User response: Ensure that there is sufficient disk
space and that the accounting file is not marked as
read-only.
ANR9900W


read-only.
631
ANR9900W (HP-UX) ANR9901W (Windows)

ANR9900W (HP-UX) Attention -- Accounting records
could not be written to the file: file name.
ANR9901W


to write an accounting record.
System action: Server processing continues, but no

accounting records are written.

read-only.
ANR9900W (Linux) Attention -- Accounting records
read-only.
ANR9900W (Solaris) Attention -- Accounting records


read-only.
read-only.



read-only.

read-only.
ANR9900W (Windows) Attention -- Accounting
records could not be written to the file:
filespec.
read-only.
ANR9901W


read-only.
632

read-only.
filespec.
read-only.
ANR9902W ANR9905W
ANR9902W


to close the accounting file.
User response: Ensure that sufficient disk space is
available and that the accounting file is not marked as
read-only.
ANR9902W


available and that the accounting file is not marked as
read-only.
read-only.
read-only.

filespec.
read-only.
ANR9903W (HP-UX) Create thread failed. Your
system is configured for a maximum of
thread count threads. Consider
configuring a maximum of 1024 threads.
Explanation: The server is unable to create a new
thread.
User response: Consider increasing the maximum
thread count on the system.
ANR9904W
Need to run as root for function function

to open the HBA for failover support.
Explanation: There will be no tape failover support

function since this TSM server does not run as root.
User response: Ensure to login as root for TSM tape
failver function to open HBA.
ANR9904W
Need to run as root for function function

to open the HBA for failover support.
Explanation: There will be no tape failover support

function since this TSM server does not run as root.
User response: Ensure to login as root for TSM tape
failver function to open HBA.

ANR9904W (HP-UX) Create thread failed. Try the

operation again later.

Explanation: The server is unable to create a new

thread due to resource constraints.

read-only.
User response: Try the operation again later.

ANR9905W
Unable to open file file. z/OS system

error message: Error message message

indicated file.
System action: The operation that attempted to open
the file fails.
633
ANR9905W ANR9952E (Windows)

User response: Determine the reason for the file open
failure and re-attempt the operation. Common reasons
for being unable to open the file include providing the
wrong name, having insufficient authorization to open
the file and not being the files owner.
ANR9905W
Unable to open file file. Error message

generated by AIX

owner.
ANR9950W
Attention -- License option could not be

written to the file: filespec.

indicated file.

to write to the options file.

indicated file fails.

owner.
ANR9905W (HP-UX) Unable to open file file. Error
message generated by HP-UX.
indicated file.
owner.
ANR9905W (Linux) Unable to open file file. Error
message generated by Linux.
indicated file.
owner.

available and that the options file is not marked as
read-only.
ANR9950W (Windows) Attention -- License option
could not be written to the file: filespec.
space and that the options file is not marked as
read-only.
ANR9951W
Attention -- License option could not be

written to the file: filespec.

available and that the options file is not marked as
read-only.
ANR9951W (Windows) Attention -- License option
could not be written to the file: filespec.
to close the options file.
space and that the options file is not marked as
read-only.
ANR9905W (Solaris) Unable to open file file. Error

message generated by Solaris.
ANR9952E (Windows) Command: Invalid value

specified for licensed storage capacity value.

indicated file.



634
ANR9953E (Windows) ANR9961W (Windows)

User response: Issue the command using a valid
value.
ANR9953E (Windows) Command: Invalid value
specified for number of licensed clients
- value.
User response: Issue the command using a valid
value.
ANR9955W (Windows) Unable to load dynamic link
library dynamic link library.
indicated dynamic link library.
inoperative.
User response: Ensure that the dynamic link library
directories are accessible. If this is an evaluation copy
of the server, then this message is normal for the
DSMREG library, since the library is only provided
with purchased Windows servers. The server licensing
will assume Try and Buy mode with sample licensed
options for a period of time.
ANR9956E (Windows) Unable to load procedure
address from dynamic link library
dynamic link library.
address of a routine in the indicated dynamic link
library.
inoperative.
User response: Ensure that the dynamic link library
directories are accessible. If the problem persists,
contact you service representative.
ANR9957W (Windows) One or more EVALUATION
Explanation: Although you are running with a
purchased version of the server, there are one or more
licenses registered that will expire on the date specified.
This i usually the case when you have been using
evaluation licenses prior to purchasing the server for
Windows.

your Windows server. These licenses should NOT have
an expiration date, so this message should not appear
after re-registering the proper licenses. If this message
ANR9958W (Windows) Node entry node name was
removed from this servers definition in
Active Directory.
removed from this servers definition in Active
Directory.
not removed from this servers
definition in Active Directory.
command, the requested backup-archive node has not
been removed from this servers definition in Active
Directory.
User response: To remove a node entry in the Active
Directory, the option adunregister has to be set to
yes in the server options file. A domain controller
must also be available. The Active Directory
Configuration wizard can be used to manually update
the server definition.
ANR9960W (Windows) Node entry node name has
been added to this servers definition in
Active Directory.
Explanation: The requested backup-archive node entry
has been added to this servers definition in Active
Directory in response to a REGISTER NODE command.
ANR9961W (Windows) Node entry node name has not
been added to this servers definition in
Active Directory.
Explanation: The requested backup-archive node entry
has not been added to this servers definition in Active
Directory in response to a REGISTER NODE command.
User response: To register a node entry in the Active
Directory, the option adregister has to be set to yes
in the server options file. A domain controller must also
be available. The Active Directory Configuration wizard
635
ANR9962W (Windows) ANR9999D

can be used to manually update the server definition.
renamed in this servers definition in
Active Directory.
renamed to the new name shown.
ANR9966I (Windows) NodeName node name.

Explanation: The NodeName is registered in Active
Directory.
ANR9967I (Windows) Server server name was defined
in Active Directory.
Explanation: The server is registered in Active

Directory.

not renamed in this servers definition
in Active Directory.


command, the requested backup-archive node has not
been renamed.
ANR9968I (Windows) Success accessing Active

Directory.
Explanation: Active Directory Server could be

contacted.
User response: To Rename Node in the Active

Directory, the options adregister and adunregister
have to be set to yes in the server options file. A
domain controller must also be available. The Active
Directory Configuration wizard can be used to
manually update the server definition.
ANR9964W (Windows) Failed to access Active
Directory. RC: return code
Explanation: Could not communicate with an Active
Directory server.
User response: Try using the option adsetdc in the
server options file to explicitly provide the TCP/IP
address of the domain controller where Active
Directory is located.
ANR9965W (Windows) Could not create the inital
node list in Active Directory for this
server.
Explanation: At startup the servers registered nodes
could not be added to the server definition in Active
Directory
User response: Try using the option adsetdc in the
server options file to explicitly provide the TCP/IP
address of the domain controller where Active
Directory is located.
System action:
ANR9969E (Windows) Unable to open volume
volume name. The most likely reason is
that another TSM server is running and
has the volume allocated.
Explanation: Only one TSM server can have a given
volume open at a time.
System action: The TSM server does not start.
User response: See if another TSM server is already
running and if so use it.
ANR9999D
(component)(code):(text)
Explanation: The diagnostic text of this message is

related to a server process or algorithm. The
information is intended for reporting processing
exceptions and other non-standard situations that occur
on the server. The (component), (code), and (text) vary,
and server processing may continue, depending upon
the cause of the message and the server process or
algorithm issuing the message.
System action: Issue the SET CONTEXTMESSAGING
command and set the message context reporting to ON.
This allows you to receive additional information when
the server produces its message. See the Administrators
Reference for more information.
User response: Examine any error messages that were
displayed before or after this message and correct any
problems, if possible. If you cannot determine or
resolve the cause of this message, contact your support
representative. Report the entire text of this message
when contacting your support representative.
636
Chapter 4. Client Events Logged to Server (ANE40004999)

ANE4000E
Error processing filespace-name: file

space does not exist
Explanation: The specified file space (domain) is
incorrect or does not exist on the workstation.
System action: Processing stopped.
User response: Retry the operation specifying an
existing domain (drive letter or file system name).
ANE4001E

space not known to server
Explanation: The number defining the correspondence
between drive letter or file (domain name) and volume
label is not known to the server.
User response: Report the program error to your
ANE4002E
Error processing filespace-name: volume

label does not exist
Explanation: The selected drive does not have a label.
System action: Tivoli Storage Manager is unable to do
the requested operation without a drive or label
entered.
User response: If the drive is a floppy drive, place a
disk with a volume label in it and retry the operation.
If the disk is a hard drive, ensure the drive has a
volume label, and retry the operation.
ANE4003E
Error processing filespace-name:

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

namepath-namefile-name: destination file
or directory is write locked
Explanation: The file or directory being restored or
retrieved from the server cannot be written to because
the destination is write locked. Another operation
might have the file open and will not allow it to be
updated.
System action: File skipped.
User response: Either determine which operation has
the file write locked, or restore the file to another name

or location.
ANE4005E

namepath-namefile-name: file not found
Explanation: The file being processed for backup,
archive or migrate no longer exists on the client.
Another process deletes the file before it can be backed
up, archived or migrated by Tivoli Storage Manager.
ANE4006E

namepath-namefile-name: directory path
not found
Explanation: You specified an incorrect directory path.
User response: Correct the syntax specified on the call
ANE4007E

namepath-namefile-name: access to the
object is denied
Explanation: Access to the specified file or directory is
denied. You tried to read from or write to a file and
you do not have access permission for either the file or
the directory.
User response: Ensure that you specified the correct
file or directory name, correct the permissions, or
specify a new location.
ANE4008E

namepath-namefile-name: file is
temporarily unavailable
Explanation: File is temporarily unavailable.
User response: Check and see if file is locked by other
process. If not, retry the command.
ANE4009E

namepath-namefile-name: disk full
condition
Explanation: No more files can be restored or
retrieved because the destination disk is full.
User response: Free up disk space, or restore or
retrieve the file to another disk.
ANE4010E

namepath-namefile-name: stale NFS handle
Explanation: An NFS file system becomes stale.
637
System action: File system skipped.

User response: Check the NFS mounted filesystem.
ANE4011E

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

namepath-namefile-name: file already
exists
Explanation: The file being restored or retrieved
exists.
System action: File is replaced or skipped depending
on client options.
ANE4016E

namepath-namefile-name: file is being
executed; write permission denied
Explanation: The current file cannot be opened to
write to because it is currently being run by another
operation.
User response: Stop the operation that is running the
file and retry the operation, or restore or retrieve the
file to a different name or directory.
ANE4017E

namepath-namefile-name: too many
symbolic links were detected while
resolving name
Explanation: While trying to resolve the file name, too
many symbolic links were found.
User response: Ensure that you do not have a looping
symbolic link for the file.

namepath-namefile-name: invalid file
handle
Explanation: An internal system error occurred. A file
operation failed because an invalid file handle was
passed.
User response: Report the problem to your system
administrator, and then retry the operation.
ANE4018E

namepath-namefile-name: file name too
long
Explanation: The file name specified is too long to be
handled by Tivoli Storage Manager.
System action: File is skipped.
User response: See the appropriate Using the
Backup-Archive Client book for the particular operating
system, for the file names that are handled by Tivoli
Storage Manager.
ANE4014E
ANE4019E
ANE4013E

namepath-namefile-name: unknown system
error (error-code) encountered. Program
ending.
Explanation: An unknown and unexpected error-code
occurred within the client program. This is a
programming failure and the client program ends.
User response: Retry the operation. If the problem
continues, see your administrator.
ANE4015E

namepath-namefile-name: unexpected error
(error-code) encountered
Explanation: An unexpected error occurred. This
might be a low-level system or communication error
that Tivoli Storage Manager cannot handle or recover
from.
continues, determine where the problem exists. See
your system administrator for further help.
638

namepath-namefile-name: file system is
locked by system
Explanation: File system cannot be accessed because it
is locked by the system.
System action: Tivoli Storage Manager cannot
complete the operation.
User response: See your system administrator.
ANE4020E

namepath-namefile-name: format unknown
Explanation: Tivoli Storage Manager tried to restore or
retrieve a file, but it had an unknown format.
ANE4021E

namepath-namefile-name: file system not
ready
Explanation: The file system/drive was not ready for
access.
User response: Ensure that the drive is available to
Tivoli Storage Manager, and then retry the operation.
ANE4022E

invalid
Explanation: The drive was not available for access. A
directory exists that does not have either a '.' or '..'
entry.
User response: Ensure that the drive is operational,
and then retry the operation. If unsuccessful, have your
service representative check the error log.
ANE4023E

namepath-namefile-name: file input/output
error
Explanation: An error was found while reading from
or writing to the file.
User response: Check your system to ensure that it is
operating properly. For OS/2, run CHKDSK /F for the
failing drive which can be found in dsmerror.log.
ANE4024E

namepath-namefile-name: file write error
Explanation: An error was found while writing to the
file.
operating properly.
ANE4025E

namepath-namefile-name: file exceeds user
or system file limit
Explanation: A file being backed up/restored or
archived/retrieved exceeds system set limits for this
user. Shown below are the filesize limits corresponding
to various platforms.
AIX
68,589,453,312 (64GB)
HP-UX 1,099,511,627,775 (1TB-1)

Linux
2,147,483,647 (2GB)
Mac pre-OS9
2,147,482,624 (2GB-1K)
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 95 (FAT16)
2,147,483,647 (2GB)
Windows 98 (FAT32)
4,294,967,295 (4GB)
Windows NT/2000 (NTFS)
17,592,185,978,880 (16TB-64K)
User response: Ensure that the system limits are set
properly.
ANE4026W

namepath-namefile-name: size of file-size
exceeded the maximum file size limit on
your system
Explanation: You tried to restore or retrieve a file that
has exceeded the maximum file size limitation on your
system.
System action: Tivoli Storage Manager cannot restore
or retrieve the file.
User response: Restore or retrieve this file on a system
that supports the file size. See your system
administrator.
ANE4027S

namepath-namefile-name: internal program
message value encountered
Explanation: An unexpected catastrophic program
failure occurred, indicated by value.
continues, see your system administrator or service
representative.
ANE4028E

namepath-namefile-name: cannot create
file/directory entry
Explanation: The directory path for files being
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.
ANE4029E

namepath-namefile-name: unable to build
a directory path; a file exists with the
same name asa directory
Explanation: Tivoli Storage Manager tried to create a
directory path, but is unable to because a file exists that
has the same name as a directory.
User response: Remove the file that has the same
name as the directory. Refer to the last restore/retrieve
operation and check all directories along the path.
639
ANE4030E

namepath-namefile-name: disk space limit
for this process reached
Explanation: The disk space allocated for the client
owner is full.
User response: Free up disk space and retry the
restore or retrieve operation.
ANE4031E

namepath-namefile-name: destination
directory path length exceeds system
maximum
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.
User response: Specify a destination path that, when
combined, is less than the system maximum.
ANE4032E

namepath-namefile-name: file is not
compressed.
Explanation: A file that was flagged as compressed
was not compressed, and the system failed.
User response: See your system administrator to
report this problem. This error is a system failure.
namepath-namefile-name: file compressed
on a different client machine that has
more memory
Explanation: You are trying to restore a file that was
backed up and compressed on another client
workstation that had more memory than your client
workstation. You cannot restore this file. When the file
is restored, it is expanded and your workstation does
not have enough memory.
System action: Tivoli Storage Manager canceled the
operation.
User response: Obtain a machine with more memory
ANE4035W

namepath-namefile-name: file currently
unavailable on server.
is currently not available from the server.
System action: Tivoli Storage Manager cannot restore
or retrieve the file.
determine why the file is unavailable and then try your
operation again.
ANE4036E
An error occurred saving the registry

key.
Explanation: The active registry key cannot be saved.
System action: Registry backup operation terminates.
ANE4037E
File file-namefile-namefile-name changed

during processing. File skipped.
Explanation: The specified file-name was skipped
during backup, archive, or migrate because it was
changing during the attempt to process it.
System action: Tivoli Storage Manager skipped the
file.
User response: If you want the file backed up,
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.
ANE4033E
ANE4034E

error
Explanation: An unknown error occurred. This might
be a low-level system or communication error that
Tivoli Storage Manager cannot handle or recover from.
640
ANE4038E
An error occurred processing file system

filespace name.
Explanation: File system filespace name is corrupted
or contains one or more corrupted directories and
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
dsmerror.log.
ANE4040E

namepath-namefile-name: file system
filespace name has exceeded its space
management quota.
Explanation: Tivoli Storage Manager detects that the
file system has exceeded its quota. No more data can
be migrated out of this file system.
System action: Tivoli Storage Manager will not
migrate files from this file system.
User response: Recall some files, or ask the system
administrator to increase the quota for this file system.
ANE4041W

namepath-namefile-name: Out of free
space or inodes in file system filespace
name to migrate or recall.
Explanation: The file system is full. No more free
space or free inodes are available to be allocated for the
transaction file that is needed when a file is being
migrated or recalled.
System action: Tivoli Storage Manager terminates the
current operation for this file system.
User response: Remove some files in the file system,
and then run reconciliation. Retry the operation.
ANE4042E
Object name filespace

namepath-namefile-name contains one or
more unrecognized characters and is not
valid.
Explanation: The filename, directory name, or volume
label syntax is incorrect.
User response: You need to check the disk for errors.
ANE4991I
appType appmsgId msg
ANE4992W
ANE4993E
ANE4994S
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
ANE4999E
Schedule schedule name has opened a

new session with the server.
Explanation: A scheduled event ended due to a
connection failure. The scheduled event had to be
restarted outside of its normal start-up window to
continue the operation.
System action: Be advised that there are multiple
sessions associated with the scheduled event.
ANE4900W
Error processing filespace namepath-name

file-name: the object is in use by another
process
the directory.
ANE4987E
File filespace namepath-namefile-name is

currently unavailable on server and has
been skipped.
is currently not available from the TSM server.
System action: TSM cannot restore or retrieve the file.
User response: Try to restore or retrieve after the file
was made available on the server. See your system
administrator.
ANE4988W
641
642
Part 3. Client Messages
643
644
Chapter 5. Client Messages (ANS0100ANS9999)

This section contains a listing of messages for the following clients:
v TSM administrative clients
v Application program interface clients
v BackupArchive and Space Management (HSM) clients
v Data Protection clients:
DB2 UDB and Hardware Devices Snapshot Integration Modules
Microsoft Exchange VSS and Hardware Devices Snapshot Integration
Modules
The messages for these clients contain a common ANS message prefix and a
unique message number. The messages are listed in numeric order.
This section also contains Diagnosis, Modification, or Tuning Information. Some of
these messages include information about the Tivoli Storage Manager error log that
you can use when working with your service representative.
ANS0101E
Unable to open English message

repository file name.
Explanation: The default English message repository

file cannot be opened. Either the file access permissions
prevent reading the file or the file is not present in the
expected location.
System action: TSM is unable to complete the
requested operation. Processing is terminated.
User response: Make sure the file in your DSM_DIR is
set up properly. If the problem continues, see your
system administrator for further help.
ANS0102W
Unable to open the message repository

file name. The American English
repository will be used instead.
Explanation: The default message repository file for

the current locale cannot be opened. Either the file
access permissions prevent reading the file, the file is
not present in the expected location, or the language
specified in the option file is not supported on this
workstation.

requested operation.
User response: Make sure the file has not been altered
from the installation. If the problem continues, see your
ANS0105E
Error trying to read index for message

number from repository file name.
Explanation: The message text for the specified

message number cannot be read.
ANS0106E
Message index not found for message

number.
Explanation: The message repository file does not

contain the message text for the message number.
System action: TSM continues processing using the

English language message repository.

User response: Make sure the file in your DSM_DIR is

set up properly. If the problem continues, see your
User response: Make sure the DSM_DIR is set up

properly and it does not point to an old copy. If the
problem continues, see your system administrator for
further help.
ANS0103E
Error trying to read header record from

message repository file name.
Explanation: The message repository file header

record cannot be obtained.
ANS0107E
Error trying to read header for message

Explanation: The message header information cannot
645
ANS0108E ANS0202E
be obtained for the message number in the message
file.
ANS0108E
Error trying to read text for message

Explanation: The message text cannot be obtained for

the message number in the message file.
ANS0118E
Unable to open schedule log file file

name for output.
Explanation: The schedule log file cannot be opened

for output.
User response: Stop TSM and restart TSM. Then retry
the operation. If unsuccessful, make sure the file has
not been locked by another application.
ANS0119E
Error trying to read response string for

message number from repository file
name.
Explanation: The response string information for the

message number cannot be obtained from the message
repository file. It is possible the message repository has
been corrupted.
ANS0109E

Insufficient memory for allocation of

message structure.
Explanation: There is not enough memory in your

system to allocate the storage needed for the message
text.
User response: Stop TSM and restart TSM. Then retry
the operation. If unsuccessful, close all unneeded
applications and retry the operation.
ANS0110E
Unable to open error log file file name

for output.
Explanation: The error log cannot be opened for

output.
requested operation. File permissions may be set such
that writing is not allowed.
User response: Stop and restart TSM. Then retry the
operation. If unsuccessful, make sure the file is not
being locked by another application and that file
permissions allow write access.
ANS0113E
Message repository file name has an

invalid control record.
Explanation: The message repository file contains an

incorrect control information.
User response: Make sure the message file was not
altered from the installation. Check DSM_DIR to make
sure it is set up properly.
646
User response: Make sure the message file was not

altered from the installation. Check DSM_DIR to make
sure it is set up properly.
ANS0120E
Message number number contains an

invalid multibyte sequence for the
current locale.
Explanation: An illegal multibyte sequence for the

current locale was found in the message. Either the
message repository has been corrupted or is coded in a
language other than that of the current locale.
User response: If the message repository is not
corrupted, process the operation in the supported
locale.
ANS0201E
Invalid parameter was found.
Explanation: The system encountered an internal

program error due to an invalid parameter.
System action: The system returns to the calling
procedure.
User response: Ask your service representative to
check the error log.
ANS0202E
Not authorized to restore the other

nodes data.
Explanation: The client is not authorized to restore the

other node's data.
procedure.
ANS0203E ANS0213E
User response: Get authorization from the other node.
ANS0203E
The objName field has no leading

directory separator.
Explanation: The objName field does not have a

leading directory separator.
procedure.
User response: Correct the value for the objName.
ANS0204E
Wildcards are not allowed in the

objName directory path.
Explanation: Wildcards are not allowed in the

procedure.
ANS0208E
The TCP/IP WINSOCK.DLL file cannot

be found.
Explanation: The TCP/IP WINSOCK.DLL file cannot

be found.
User response: Verify your TCP/IP installation.
ANS0209E
An error occurred while loading a

library.
Explanation: An error occurred while loading a

library. The TCP/IP DLL load failed.
ANS0210E
The TCP/IP load function failed.
Explanation: An error occurred while locating a

function. The TCP/IP load function failed.
ANS0205E
Unable to open error log file.
Explanation: The system is unable to open the error

log file.

procedure.
ANS0211E
User response: Verify the DSMI_LOG value and

access permission. On the AS/400 platform, verify the
value specified for ERRORLOGNAME in the API
options file.
ANS0206E
The log file cannot be written to.
Explanation: There was an error writing to the log

file.
procedure.
access permission. on the AS/400 platform, verify the
options file.
ANS0207E
The log file name was not specified.
The object name pointer is NULL.
Explanation: There is no value provided for the object

name pointer.
procedure.
User response: Provide an address for the
dsmObjName structure.
ANS0212E
The data block pointer is NULL.
Explanation: There is no value provided for the data

block pointer.
procedure.
User response: Provide an address for the DataBlk
structure.
ANS0213E
The object attribute pointer is NULL.

log file.

attribute pointer.

procedure.

procedure.

options file.
User response: Provide an address for the ObjAttr

structure.
647
ANS0214E ANS0224E
ANS0214E
There is no server session information.
ANS0220E
An invalid option was found during

option parsing.
Explanation: The server did not respond with the

session information.
Explanation: An invalid option was found.

procedure.

procedure.
User response: Verify the server status.
User response: Verify the options in dsm.opt, 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).
ANS0215E
There is no server policy information.

policy information.
procedure.
ANS0221E
There was an error in the TSM API

internals.
User response: Verify the server policy definitions.
Explanation: The system encountered an error in the

API internals.
ANS0216E

procedure.
The dataBlk bufferLen value is zero.

procedure.
User response: Shut down the process and retry the

operation. Verify that any previous dsmInit calls were
cleaned up and terminated by a dsmTerminate call. If
the problem continues, contact your system
administrator or service representative.
User response: Provide a non-zero value for the

bufferLen.
ANS0222E
Explanation: The value for the dataBlk bufferLen is

zero.
ANS0217E
The dataBlk bufferPtr is NULL.
Explanation: There is no value provided for the

dataBlk bufferPtr.
procedure.
User response: Provide an address for the bufferPtr.
The repository type is invalid.
Explanation: The repository type is invalid.

procedure.
User response: For dsmDeleteFS the repository must
be one of the following:
v DSM_ARCHIVE_REP
v DSM_BACKUP_REP
v DSM_REPOS_ALL.
ANS0218E
The objType is invalid.
Explanation: The value for the objType is invalid.
ANS0223E

procedure.
Explanation: The filespace name is invalid.
User response: The value for dsmObjName.objType

must be:

procedure.
DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for

Backup, or
Filespace name should start with the

directory delimiter.
User response: Filespace name should start with the

DSM_OBJ_FILE for Archive.

ANS0224E
ANS0219E
The dsmEndTxn vote is invalid.
Explanation: The dsmEndTxn vote is invalid.

procedure.
User response: The vote must be
DSM_VOTE_COMMIT or DSM_VOTE_ABORT.
648
The object name is either an empty

string or has no leading delimiter.
Explanation: The object name is invalid because of an

empty string or there is no leading delimiter.
procedure.
User response: Verify the format of the dsmObjName
full path.
ANS0225E ANS0234E
ANS0225E
Low level qualifier of the object name

should start with the directory delimiter.
Explanation: The low level qualifier for the object

name is invalid.
procedure.
User response: Start the low level qualifier of the
object name with the directory delimiter.
ANS0226E
The object owner is invalid.
Explanation: The object owner must be either the root

user, or the object owner must be the same as the
session owner.
procedure.
User response: Verify the session owner and object
owner.
ANS0227E

procedure.
User response: The sendType must be one of the
following:
stBackup
stArchive
stBackupMountWait
stArchiveMountWait
The dsmSendObj sendType is invalid.
Explanation: The dsmSendObj sendType is invalid.

procedure.
following:
stBackup
stArchive
stBackupMountWait
stArchiveMountWait
ANS0229E
The query Backup objState is invalid.
Explanation: The query Backup objState is invalid.

procedure.
User response: The qryBackupData.objState must be
one of the following:
DSM_ACTIVE
DSM_INACTIVE
DSM_ANY_MATCH
ANS0231E
The management class name was not

found.
Explanation: A query or send operation is unable to

find the management class name.
procedure.
User response: Verify the management class name.
The dsmBindMC sendType is invalid.
Explanation: The dsmBindMC sendType is invalid.
ANS0228E
ANS0230E
The dsmDeleteObj delType is invalid.
ANS0232E
The drive letter is not an alphabetic

character.
Explanation: The drive letter is not an alphabetic

character. This return code is valid on Microsoft
Windows only.
procedure.
User response: Verify that the drive designation is an
alphabetic character. The referenced field is
dsmDosFSAttrib.driveLetter.
ANS0233E
The Register Filespace name is NULL.

Register Filespace name.
procedure.
User response: Provide a filespace name on
dsmRegisterFS.
ANS0234E
The new password value is NULL or

blank.
Explanation: There is no value provided for new

password.
Explanation: The dsmDeleteObj delType is invalid.

procedure.

procedure.
User response: Provide a new password on

dsmChangePW.
User response: The delType must be dtBackup or

dtArchive.
649
ANS0235E ANS0243E
ANS0235E
The old password value is NULL or

blank.
ANS0239E
On dsmSendObj, wildcards are not

allowed for the objName.
Explanation: There is no value provided for old

password.
Explanation: On dsmSendObj, wildcards are not


procedure.

procedure.
User response: Provide an old password on

dsmChangePW.
User response: Provide a fs, hl, and ll on the

dsmObjName.
ANS0236E
ANS0240E
On dsmInit, the owner is not allowed to

establish a session when
PASSWORDACCESS=generate.
Explanation: PASSWORDACCESS=GENERATE
establishes a session with the current login user as the
owner. The application should set clientOwnerNameP
to NULL when PASSWORDACCESS=GENERATE is in
effect.
procedure. Whether the application can continue
processing depends on how the application handles the
error.
User response: This message applies to applications
that utilize the TSM API, and is intended primarily for
the vendor of the application for which the message is
issued. Depending on the application, this could be a
configuration issue.
Consult the documentation for the application and
verify that the application is configured correctly. If the
problem persists, contact the application vendor for
further assistance.
ANS0237E
On dsmInit, the node is not allowed

when PASSWORDACCESS=generate.
Explanation: PASSWORDACCESS=generate
establishes a session with the current hostname as the
node.
The filespace to delete/set access cannot

be found.
Explanation: The filespace to delete cannot be found.

procedure.
User response: Verify the filespace name.
ANS0241E
On dsmSendObj, dsmDeleteObj, or
dsmUpdateFS the filespace is not
registered.
Explanation: On dsmSendObj, dsmDeleteObj, or

dsmUpdateFS, the filespace is not registered.
procedure.
ANS0242W
On dsmRegisterFS the filespace is

already registered.
Explanation: On dsmRegisterFS the filespace is

already registered.
procedure.

procedure.
ANS0243E
User response: When using

PASSWORDACCESS=generate, set clientNodeNameP to
NULL.
Explanation: On dsmBeginGetData, the objID is

NULL.
ANS0238E
User response: Verify the following:
The sequence of calls is invalid.
On dsmBeginGetData the objID is

NULL.

procedure.
Explanation: The sequence of calls is invalid.
The dsmGetList is not NULL.

procedure.
Each objID is not NULL.
User response: Verify the transaction call sequence.
650
The dsmGetList numObjId is not zero.
ANS0244E ANS0254E
ANS0244E
On dsmInit the callers API version is

different than the TSM library version.
ANS0249E
The archive object does not have a copy

group.
Explanation: On dsmInit the caller's API version has a

higher value than the TSM library version.
Explanation: The archive object does not have a copy

group.

procedure.

procedure.
User response: Install the latest TSM API library and

trusted agent module.
User response: Verify server policy definitions.

ANS0250E
ANS0245E
The callers structure version is different

than the TSM library version.
Explanation: The caller's structure version is different

procedure.
User response: Ensure that the stVersion field is set
with the value in the header file. Recompile the
application with the latest header files.
Explanation: Memory used by the TSM API has been

corrupted.
procedure.
continues, contact your system administrator or service
representative.
ANS0251E
ANS0246E
Issue dsmEndTxn and then begin a new

transaction session.
Explanation: This transaction must be ended and a

new one must be started due to one of the following
reasons:
The destination changed.
The byte limit is exceeded
The maximum number of objects is exceeded.
Memory used by the TSM API has been

corrupted.
The sendObj Archive description is too

long.
Explanation: The sendObj Archive description is too

long.
procedure.
User response: The sndArchiveData.descr string must
be less than or equal to DSM_MAX_DESCR_LENGTH.

procedure.
ANS0252E
User response: Issue dsmEndTxn and start a new

Explanation: The sendObj ObjAttr.objInfo is too long.
ANS0247E
The backup or archive object is

excluded from processing.
Explanation: The backup or archive object is excluded

from processing.
procedure.
User response: Verify the objName and Exclude lists.
ANS0248E
The backup object does not have a copy

group.
Explanation: The backup object does not have a copy

group.
procedure.
The sendObj ObjAttr.objInfo is too

long.

procedure.
User response: The objInfo field must be less than or
equal to DSM_MAX_OBJINFO_LENGTH.
ANS0253E
The sendObj dsmObjName.hl is too

long.
Explanation: The sendObj dsmObjName.hl is too long.

procedure.
User response: The hl field must be less than or equal
to DSM_MAX_HL_LENGTH.
ANS0254E
The password, or encryptionPassword

string provided is too long.
Explanation: The value provided for password or

encryptionPassword is too long.
procedure.
651
ANS0255E ANS0264E
User response: The password or encrypionPassword
field must be less than
DSM_MAX_VERIFIER_LENGTH.
ANS0255E
The sendObj dsmObjName.fs is too

long.
Explanation: The sendObj dsmObjName.fs is too long.

procedure.
ANS0260E
An invalid option keyword was found

during option parsing.
Explanation: An invalid option keyword was found in

the dsmInit configuration file, the option string,
dsm.sys, or dsm.opt.
procedure.
User response: The fs field must be less than or equal

to DSM_MAX_FS_LENGTH.
User response: Correct the spelling of the option

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.
ANS0256E
ANS0261E
The sendObj dsmObjName.ll is too

long.
Explanation: The sendObj dsmObjName.ll is too long.

procedure.
User response: The ll field must be less than or equal
to DSM_MAX_LL_LENGTH.
ANS0257E
On RegisterFS or UpdateFS the fsAttrs

fsInfo is too long.
The configuration file specified on

dsmInit cannot be opened.
Explanation: The configuration file specified on

procedure.
User response: Verify the file name.
ANS0262E
The Include/Exclude definition file was

not found.
Explanation: On RegisterFS or UpdateFS the fsAttr's

fsInfo is too long.
Explanation: The Include/Exclude definition file was

not found.

procedure.

procedure.
User response: The fsInfo field must be less than or

equal to DSM_MAX_FSINFO_LENGTH.
User response: Verify the file name on the Inclexcl

option.
ANS0258I
ANS0263E
On dsmGetNextQObj or dsmGetData
there is more available data.
Explanation: On dsmGetNextQObj or dsmGetData

procedure.
User response: Call the function again.
ANS0259E
The dataBlk buffer is too small for the

query response.
Explanation: The dataBlk buffer is too small for the

query response.
procedure.
User response: On dsmGetNextQObj ensure that the
dataBlk buffer is at least as big as the query response
structure.
Either the dsm.sys file was not found, or

the Inclexcl file specified in dsm.sys
was not found.
Explanation: Either the dsm.sys file was not found, or

the Inclexcl file specified in dsm.sys was not found.
procedure.
User response: The dsm.sys file must be in the
directory referenced by the environment variable
DSMI_DIR. Verify the file name on the Inclexcl option
in the dsm.sys file.
ANS0264E
Only a UNIX root user can execute

dsmChangePW or dsmDeleteFS.
Explanation: Only a UNIX root user can execute

procedure.
User response: Run this program as a root user.
652
ANS0265E ANS0276S
ANS0265E
You must issue dsmBindMC before

dsmSendObj.
Explanation: You must issue dsmBindMC before

dsmSendObj.
procedure.
User response: Modify your program.

continues, contact your system administrator.
ANS0271E
No more files can be restored or

retrieved since the destination directory
is full.

retrieved since the destination directory is full.
ANS0266I
The dsmEndTxn vote is ABORT, so

check the reason field.
Explanation: After a dsmEndTxn call, the transaction

is aborted by either the server or client with a
DSM_VOTE_ABORT and the reason is returned.
procedure.
User response: Check the reason field for the code
which explains why the transaction has been aborted.
ANS0267E
Invalid command line option/value:

option

ANS0272I
The operation is finished.
Explanation: The operation is finished.

procedure.
User response: Proceed with next function call.
ANS0273E
The trusted agent execution/owner

permissions are invalid.
Explanation: The option is not valid on this command

line.
Explanation: The trusted agent execution/owner

System action: Processing stops
User response: Verify that the option and value are

not misspelled and are valid with the current
command.
User response: Have your system administrator check

the installation instructions for the client to ensure that
the trusted agent permissions are set correctly.
ANS0268E
ANS0274S
Server problem: Destination not

defined.
Process killed.
Explanation: Server problem: Destination not defined.
Explanation: Processing stopped. This is a

User response: Have your service representative check

the error log.

ANS0269S
ANS0275S
The structured file data type is

unknown.
Explanation: An unknown and unexpected error code

occurred within the client program. The structured file
data type is unknown. This is a programming failure
and the client program ends.
Explanation: The trusted agent blocks the operation.

This is a programming failure and the client program
ends.
ANS0276S
ANS0270S
The data buffer overflowed.
Explanation: The data buffer overflowed. This is a

Trusted agent would block the

operation.
The area for the include/exclude pattern

is too small.
Explanation: The area for the include/exclude pattern

is too small. This is a programming failure and the
client program ends.
653
ANS0277S ANS0286E
ANS0277S
There is no closing bracket in the

pattern.
ANS0282E
Password file is not available.
Explanation: The file containing the stored password

for the specified server-name is unavailable.
System action: TSM ends.
Explanation: There is no closing bracket in the

pattern. This is a programming failure and the client
program ends.
User response: The root user must set and store a new
password.
ANS0283E

ANS0278S
The transaction will be aborted.
Explanation: The server encountered an error and will

abort the transaction.
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.
ANS0279I
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.
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: Verify the application sets the
mountWait value correctly on dsmBeginGetData.
ANS0280E
Explanation: The high level qualifier for the object

name is invalid.
procedure.
User response: High level qualifier of the object name
ANS0284E
The number of objects on

dsmBeginGetData exceeds
DSM_MAX_GET_OBJ |
DSM_MAX_PARTIAL_GET_OBJ.
Explanation: The number of objects (numObjId)

specified on the dsmBeginGetData call exceeds
DSM_MAX_GET_OBJ |
procedure.
User response: Check the number of objects before
calling dsmBeginGetData. If it is greater than
DSM_MAX_GET_OBJ |
DSM_MAX_PARTIAL_GET_OBJ, then issue multiple
Get call sequences.
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.
User response: Make sure the Trusted Agent module
is in the directory specified by DSMI_DIR.
ANS0281E
High level qualifier of the object name

Access denied for dsmapitca.
ANS0285E
The update action is invalid.
Explanation: The dsmUpdateFS or dsmUpdateObj

action is invalid.
procedure.
User response: Correct the action value. Valid values
are defined in dsmapitd.h and documented in our
Using the API book.
Explanation: An attempt to access a system function

has been denied.
ANS0286E
Explanation: The key file for IBM Tivoli Storage

Manager for Data Retention application client for
Oracle cannot be found.
The key file is missing.

procedure.
User response: Ensure that you have ordered the IBM
Tivoli Storage Manager for Data Retention application
654
ANS0287E ANS0307I
client which contains TDP for Oracle, and install the
key file.
ANS0301E
ANS0287E
Explanation: The TSM DLL dsm3270.dll cannot be

found in the user's path.
The key file content is invalid.
The TSM DLL dsm3270.dll cannot be

found in the users path.
Explanation: The key file content for IBM Tivoli

Storage Manager for Data Retention application client
for Oracle is invalid.
System action: Communications link is not

established.

procedure.
User response: Make sure that the TSM DLL

dsm3270.dll is in a directory that is included in the
user's path.

client which contains the TDP for Oracle, and install
the key file.
ANS0302I
Successfully done.
Explanation: The operation successfully completed.

ANS0296I
Encryption key passwords are not the

same. Please try again...
Explanation: TSM found that the encryption key

passwords do not match.
System action: You are prompted for the encryption
key password.
User response: Enter the correct encryption key
password.

ANS0304E
Unable to generate password because

password access is not set to
GENERATE.
Explanation: User issued the Generate Password

command, but password access is not set to
GENERATE in the options file.
System action: TSM none.
ANS0297E
Error opening specified file.
Explanation: The specified file could not be located or

opened.
System action: Attempts to open file failed.
User response: Add PASSWORDACCESS GENERATE

to your dsm.opt file .
ANS0305E
User response: Make sure the file exists.

ANS0298E
Session Rejected: The specified user id

is currently locked
Explanation: The user id you specified is currently

locked on the server.
System action: Session was not started.
Unable to generate password because no

NAS Node was specified.

command with class=NAS, but no NAS node was
specified.
User response: Retry the command and use the
-nasnodename option.
User response: Check with your system administrator

to find out why your user id is locked.
ANS0306E
ANS0299E

command with an invalid or unknown class.
Scheduler cannot be started manually

because the value of
MANAGEDSERVICES option is
SCHEDULE.
Explanation: if MANAGEDSERVICES SCHEDULE is

indicated in the option file, the TSM scheduler cannot
be started in the traditional manner.
Unable to generate password because

Class type is invalid or unknown.

User response: Retry the command and use a
supported class type option (class=CLIENT or
class=NAS).
System action: Scheduler stopped.
ANS0307I
User response: If you are not going to use dsmcad to

manage the schedule anymore, stop dsmcad and
remove MANAGEDSERVICES option from the option
file.

command and it was successful.
Password generated.

655
ANS0308E ANS0318E
ANS0308E
Remote operation failed to start on

obj-name. Status: status reason: reason
Explanation: The request to start a remote operation

has failed for the indicated node and filespace. The
status and the reason for the failure are shown.
System action: TSM ended the current operation.
User response: Contact your system administrator for
more information.
ANS0309E
Remote operation failed to start on

obj-name. Status: status
Explanation: The request to start a remote operation

has failed for the indicated node and filespace. The
status of the failure is shown.
System action: IBM Tivoli Storage Manager ended the
current operation.
more information.
ANS0311E
The tsmBuffHandle is invalid, or the

value of dataPtr is invalid.
Explanation: An invalid value for a handle or dataPtr

has been passed into the API.
procedure.
User response: There is a problem with the calling
application. Verify the values of the tsmBuffHandle and
dataptr passed to the API.
ANS0312E
The number of bytes copied into the

tsmBuffer is larger than the allowed
value.
Explanation: An invalid number of bytes was copied

to a tsmBuffer.
procedure.
application. Verify the number of bytes copied into the
tsmBuffer.
ANS0313E
dsmTerminate cannot finish because the

application is holding on to 1 or more
tsmBuffers.
Explanation: An application is trying to terminate a

session, but is still holding some tsmBuffers.
procedure.
User response: The application must return all buffers
for this session by calling tsmReleaseBuffer, and then
issue dsmTerminate.
656
ANS0314E
An internal error occurred in the

tsmBuffer array.
Explanation: An internal API buffer array error

occurred.
procedure.
User response: Try the operation again. If the problem
representative.
ANS0315E
Unable to open message text file.
Explanation: The system is unable to open the

message txt file (dscenu.txt or dsmclientV3.cat for AIX).
On the AS/400 platform this file is
QANSAPI/QAANSENU(TXT).
procedure.
User response: Verify that the dscenu.txt file is in the
directory pointed to by DSMI_DIR. For AIX, verify that
the dsmclientV3.cat file has a symbolic link to
/usr/lib/nls/msg/<locale>/dsmclientV3.cat .
ANS0316E
Unable to use message text file.
Explanation: The system is unable to use the message

text file (dscenu.txt or dsmclientV3.cat for AIX) because
of an invalid header. On the AS/400 platform this file
is QANSAPI/QAANSENU(TXT).
procedure.
User response: Install the message text file again.
ANS0317E

txt file (dscenu.txt or dsmclientV3.cat for AIX) because
of an invalid control record. On the AS/400 platform
this file is QANSAPI/QAANSENU(TXT).
procedure.
ANS0318E
Invalid value for DATEFORMAT

specified.
Explanation: An invalid value is specified for

DATEFORMAT.
procedure.
User response: Specify a valid value.
ANS0319E ANS0330E
ANS0319E
Invalid value for TIMEFORMAT

specified.
ANS0325E
Partial Object Retrieve is not supported

on this server.

TIMEFORMAT.
Explanation: The TSM server specified by the user

does not support partial object retrieve.

procedure.

procedure.
User response: Specify a TSM server which supports

the partial object retrieve function.
ANS0320E
Invalid value for NUMBERFORMAT

specified.

NUMBERFORMAT.
procedure.
ANS0321E
msg parameter for dsmRCMsg is a

NULL pointer.
ANS0326E
This node has exceeded its maximum

number of mount points.
Explanation: Either no tape or sequential disk mount

points are permitted for this operation, or the
maximum number of mount points allowed are already
in use. The operation can not be completed. The TSM
administrator defines the maximum number of mount
points with the MAXNUMMP property of your node
definition.
System action: The object is skipped

procedure.
User response: If you are performing any other TSM

operations that might be using mount points, wait until
those operations are complete, then try the failed
operation again. Otherwise contact your TSM
administrator for further assistance
User response: Allocate enough space for the message

parameter.
ANS0327E
Explanation: The message parameter for dsmRCMsg

is a NULL pointer.
ANS0322E
no text available for this return code.
Explanation: The dsmRC parameter for dsmRCMsg is

an unsupported return code.
procedure.
A duplicate object was found, operation

cannot complete.
Explanation: A duplicate object was found, operation

cannot complete.
User response: Try the operation with a different file
specification.

ANS0328E
ANS0323E
partialObjOffset value for partial object

retrieve is invalid.
Explanation: The partialObjOffset value for partial

object retrieve is invalid.
procedure.
The specified objects failed the merge

test.
Explanation: The specified objects failed the merge

test, operation cannot complete.
User response: See documentation for the merge test
parameters.

ANS0330E
ANS0324E
partialObjLength value for partial object

The dsmSetAccess access Type is

invalid.
Explanation: The dsmSetAccess accessType is invalid.
Explanation: partialObjLength value for partial object


procedure.

procedure.
User response: The accessType must be one of the

following:
atBackup
atArchive
657
ANS0331E ANS0342E
ANS0331E
No files have been previously backed

up for this filename/filespace.
Explanation: You tried to set access to files when no

files for the specified filename, drive or file system
were previously backed up.
User response: Ensure that the correct drive or file
system was specified and that files are backed up for
you to set access.
ANS0332E
No files have been previously archived

for this filename/filespace.

were previously archived.

more information.
ANS0337E
Server plugin detected unsupported

NAS filer operating system.
Explanation: A plugin module detected that a NAS

filer is running an unsupported operating system or
operating system level.
more information.
ANS0338E
An invalid operation was attempted on

a node
Explanation: The operation is not valid.

system was specified and that files are archived for you
to set access.

more information.
ANS0339E
ANS0333E
Unknown Remote Mover type
Explanation: The specified Remote Mover type is

unknown.
more information.
Explanation: The storage pool is not defined.

more information.
ANS0340E
ANS0334E
An Operation for the requested node

and filespace is already in progress.

mover to perform an operation for the indicated node
and filespace. Since an operation for this node and
filespace is already in progress, the new operation
cannot be performed.
The specified target storage pool is not

defined.
A target storage pool does not have the

correct data format for the given node
type.
Explanation: none
more information.

User response: Retry the operation at a later time.
ANS0341E
ANS0335E
Explanation: none
System resource in use
Explanation: A required resource is in use by another

command or process.
ANS0336E
Server plugin communication error
Explanation: Communication between a server plugin

module and a NAS filer failed.
No associated data mover is defined for

the given node.

more information.
ANS0342E
The CRC received from the Server does

not match the CRC calculated by the
client.
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
failure.
System action: In some cases, the client can indicate
658
ANS0343E ANS0352E
the failure to the server and retry the operation.
User response: Check the trace log for additional
information and retry the operation. If the problem
persists, contact your system administrator.
operation, like backup or archive failed because the

copy continue option was set to NO. The sysadmin will
need to resolve the problem on the server end.
ANS0349E
ANS0343E
An invalid operation was attempted on

a group leader or group member.
Transaction failed because of a problem

during a store operation.
System action: The current operation stops.
Explanation: Transaction failed because of a problem

during a store operation. This error is typical when the
next storage pool has a different copy storage pool list
and we switch to this pool in the middle of a
transaction.
User response: Retry a valid operation.
System action: Transaction is aborted.
Explanation: An invalid operation was attempted on a

logical group.
User response: Resend objects in separate transactions.

ANS0344E
Cannot Send data with a zero byte

sizeEstimate.
ANS0350E
Explanation: You cannot send data for an object with

size estimate = 0.
procedure.
The current client configuration does

not comply with the value of the
DATAWRITEPATH or
DATAREADPATH server option for this
node.
Explanation: An operation was attempted on a remote

disk that is not defined.
Explanation: The values of the DATAWRITEPATH

and DATAREADPATH server options specify where the
client is allowed to send data, and where data is read
from. The values for the specified node name should
correspond with the client configuration. For example,
you will get this error message if DATAWRITEPATH
contains a LAN value and the client is configured to
use LAN-free protocol, or vice versa.
User response: Define the proper remote disk.
User response: Check the client, server, and storage

agent logs to determine why the client was not able to
send data LAN-free. Make sure the client configuration
and server options are compatible.
User response: Set size estimate greater than 0 in

dsmSendObj.
ANS0345E
ANS0346E
Remote disk not defined.
Input destination does not match

expected destination.
Explanation: Input destination does not match

User response: Retry operation with proper
destination.
ANS0347E
Data mover is not available.
Explanation: Data mover is not available.

User response: Retry operation with a proper Data
mover.
ANS0348E
Operation failed because the copy

continue option was set to NO.
Explanation: Operation failed because the copy

ANS0351E
The node or user does not have proper

authority to perform this operation
Explanation: The node or user does not have proper

authority to perform this operation.
System action: The transaction is ended.
User response: Check the authority for the specified
object.
ANS0352E
The operation is not permitted due to

server licenses values.
Explanation: The node or user is trying to perform an

operation that either exceeds license values, or is not
licensed.
System action: The session is rejected or the
transaction is cancelled, ending the current operation.

User response: This abort code indicates that a store
659
ANS0353E ANS0361I
ANS0353E
When using useTsmBuffers, dataBlk

must be NULL in calls to dsmSendObj
and dsmGetObj.
ANS0358E
Explanation: The value for dataBlk must be NULL

when using useTsmBuffers.
procedure.
application. Contact your application provider
ANS0354E
Encryption is not allowed when using

useTsmBuffers.
Explanation: useTsmBuffers does not support

encryption.
procedure.
User response: Try the operation again, without using
useTsmBuffers, or disable encryption for this operation.
ANS0355E
This object cannot be restored/retrieved

using useTsmBuffers, because it is
compressed.

compression.
procedure.
useTsmBuffers.
ANS0356E
This object cannot be restored/retrieved

using useTsmBuffers, because it is
encrypted.

encryption.
procedure.
useTsmBuffers.
Explanation: There was no encryption key found in

the password file, or no key was provided by the
application.
procedure.
User response: If you are using -encryptkey=prompt,
make sure there is a value in encryptionPasswordP and
that bEncryptKeyEnabled is set to true.
ANS0359E
When using useTsmBuffers, a

restore/retrieve with partial object
restore is not allowed.
Explanation: useTsmBuffers does not support partial

object restore.
procedure.
User response: Make sure the calling application is
either using Partial object restore or useTsmBuffers.
660
Conflicting encryption key options have

been specified.
Explanation: When using the ENABLEENCRYPTKEY

option, the parameter bEncryptKeyEnabled for the TSM
API dsmInitExIn_t and tsmInitExIn_t structures cannot
be set to bTrue.
procedure.
User response: Either remove the
ENABLEENCRYPTKEY option from the options file, or
set the parameter bEncryptKeyEnabled to bFalse in the
program using the TSM API.
ANS0360E
The CAD cannot start because the value

of the MANAGEDSERVICES option is
NONE.
Explanation: The CAD will not start if

MANAGEDSERVICES NONE is set in the option file.
The CAD is designed to manage the web client or TSM
schedules. By specifying NONE, the CAD will not
manage any services.
System action: The CAD will stop processing.
User response: Specify either WEBCLIENT or
SCHEDULER for the MANAGEDSERVICES option in
the option file then restart the CAD.
ANS0361I
ANS0357E
No encryption key was found. If you

are using -encryptkey=prompt make
sure there is a value in the
encryptionPasswordP field and that
bEncryptKeyEnabled is set to true.
DIAG:
Explanation: The message text is provided for

diagnostic purposes and is meant to provide
information to IBM support in problem determination.
ANS0400E ANS0416E
ANS0400E
License file could not be opened.
Explanation: The license file was not found, or could

not be opened because of permissions or the file is
corrupted.
ANS0410E
Oracle passed invalid mode
Explanation: Invalid mode passed by Oracle.

procedure.

procedure.
User response: Check permissions on file. See if the

license file is in the correct place.
ANS0411E
Oracle passed null file name
Explanation: Null filename passed by Oracle.

ANS0401E
Read failure on the license file.

not be opened because of permissions, or the file is
corrupted.
procedure.
ANS0402E
Write failure on the license file.

procedure.
ANS0412E
Wrong data block size
Explanation: Wrong Block Size

procedure.

corrupted.
ANS0413E

procedure.

procedure.
User response: Check permissions on file. See if

User response: If backing up an object, be sure to

generate a unique object name.
ANS0403E
ANS0414E
Data in the license file is not in a valid

format.
Object exists
Explanation: Backup or Restore Object already exists.
Not same Oracle handle
Explanation: The license file is not valid.
Explanation: The handle passed from Oracle is not the

same handle that TSM passed back.

procedure.

procedure.
User response: User needs to obtain a new license.
ANS0404E
ANS0415E
The checksum in the license file does

not match the licenseregistration string.
Explanation: The registration string is not valid.

procedure.
Explanation: End of file reached.

procedure.
User response: None
ANS0416E
ANS0405E
This is an expired try and buy license.

procedure.
End of file reached
Wrong Read State
Explanation: The operation must be in READ state.

procedure.
661
ANS0417E ANS1003E
ANS0417E
Runtime API version is outdated
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.
ANS0418E
Wrong write state
Explanation: The operation must be in WRITE state.

procedure.
ANS0419E
Invalid flag passed
Explanation: Invalid flag passed from Oracle.

procedure.
ANS0420W
Warning! Restoring inactive system state

objects is not recommended. Do you
wish to continue?
Explanation: Restoring inactive system state objects

may cause system instability. Examples of possible
problems include:
v Applications that were installed after the time the
system state was backed up cannot function properly
after restoring the inactive system state
v Critical operating system updates installed after the
inactive system state backup was made can no
longer be available, or may not function correctly.
v You did not specify the -OPTFILE option when

starting the TSM client, and
v the environment variable DSM_CONFIG was not set.
System action: TSM client assumes default values for
all client options and continues processing, using the
default server name and associated options found in
the dsm.sys file.
User response: If the default system action is
acceptable, you can eliminate this message by creating
an empty dsm.opt file in the installation directory.
If you have a client user options file (dsm.opt), either
place it in the installation directory or set the
DSM_CONFIG environment variable to the
fully-qualified path and file name of your options file.
Review the information on configuring TSM in the
TSM client manual specific to your operating system. If
the problem persists, ask your TSM administrator for
further assistance.
ANS1000E
An unsupported communications
method was specified.
Explanation: None.
System action: processing stops.
User response: Specify a communications interface
that is supported by the TSM client on your operating
system. See the TSM client manual for your operating
system for further information on configuring TSM
client communications.
ANS1001E
Volume being backed up was not a

system volume. Skipped.
Explanation: User specified to back up system volume

only. This volume was not backed up since this volume
is not a system volume.
System action: Volume was not backed up.
Restoring inactive system state objects is not

recommended unless you are certain that this is what
you need to do.
User response: Use All option or use image backup

command to backup this volume.
System action: If user responds with yes, the client

will restore the object. If user responds with no, the
client will cancel the operation.
ANS1002I
User response: Reply to the prompt. If you are

unsure, reply no, and consult your system
administrator or operating system vendor before
proceeding further.
MOS image is being created. It may

take a while.
Explanation: Mini Operating System image is being

created. It may take a while to create it.
System action: TSM is gathering necessary
information.
ANS0990W
Options file file-name could not be

found. Default option values will be
used.
Explanation: Common reasons for this warning

include:
v The default options file does not exist, and
662
ANS1003E
Backup failed to start for node =

node-name, file system = fs-name, errno =
error-code, reason : error-reason
Explanation: An attempt to start backup for remote

node failed.
ANS1004W ANS1009W
System action: Backup fails.
persists, contact the server administrator.
ANS1004W
Node has exceeded max tape mounts

allowed. Operation for filespace-name
will be tried again later.
Explanation: Node has exceeded max tape mounts

allowed. The operation will be tried again later.
System action: The operation will be retried.
User response: Increase the number of allowed tape
mounts for this node on the server to avoid this
situation again.
ANS1005I
TCP/IP read error on socket = socket-id,

errno = error-code, reason : error-reason.
Explanation: An attempt to receive data using TCP/IP

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
than the IDLETIMEOUT value set on the server.
System action: TCP/IP connection to server fails.
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
transferring the data, and send statistics. You can also
consider increasing the IDLETIMEOUT value in the
ANS1006I
TCP/IP write error on socket = socket-id,

errno = error-code, reason : error-reason
v If the file is being bound to the default management

class, make sure the management class has a backup
copy group.
v If the file is being bound to a management class
specified in an INCLUDE statement, make sure that
the management class has a backup copy group.
v If you have more than one TSM server, make sure
you are connecting to the correct server.
v If you are unable to find a suitable management
class, contact your TSM administrator for further
assistance.
ANS1008E
Sending of object object-nameobjectnameobject-name failed: No Archive Copy

Group
Explanation: The management class for this file

(object-name) did not have an archive copy group
specified.
System action: TSM did not back up the file.
ANS1009W
An error occurred processing the

operating system include/exclude
statements. The error was detected
while processing: subsystemname.
Explanation: The client encountered an error while

obtaining the automatic include/exclude statements
from the operating system. Possible reasons for this
error include:
v The specified registry key cannot be opened for
reading
v The entry under this key has incorrect data
Explanation: An attempt to send data using TCP/IP

connection failed.
System action: Processing continues without the full

list of operating system include/exclude statements.
System action: Connection to server fails.
User response: Ensure that you have access to the

specified registry key and that entries are a MULTISZ
values that contain:

v Individual files
ANS1007E
Sending of object object-nameobjectnameobject-name failed. There is no

backup copy group.
Explanation: The management class for this file

(object-name) does not have a backup copy group. Either
the default management class does not have a backup
copy group, or an INCLUDE statement is attempting to
bind the file to a management class that does not have
a backup copy group.
v Directories
v Wild card entries
v Environment variables
v /s switch (the /s switch is used on directory and/or
wild card entries and signifies that all subdirectories
of this directory should be excluded)
If the cause of this message can not be determined or
resolved, contact IBM technical support for further
assistance.

User response: Run DSMC QUERY MGMTCLASS
-DETAIL to view information about available
management classes.
663
ANS1010E ANS1022E
ANS1010E

Unsupported file system operation.
Explanation: The file system does not support an

operation required to process the file or directory.
System action: The file or directory is skipped.
Depending on the specific error encountered,
processing on Solaris clients might stop.
User response: Verify that the file system is supported
by the TSM client. If a restore or retrieve failed, retry
the operation to another location. If the problem
persists, look for other indications of system problems.
It may be necessary to run the operating system utility
that checks and repairs file system inconsistencies. If
the problem still cannot be resolved, contact your TSM
administrator for further assistance.
ANS1015E
The session is rejected. The server does

not allow a signon of a client that is not
archive-retention protection enabled.
Explanation: The client cannot establish a connection

to the server because the server is archive-retention
protection enabled and the client is not.
ANS1018E
Port port number is already in use
Explanation: The port specified by the

TCPCLIENTPORT option is in use by a different
process.
User response: Contact the server administrator to set
up a different port for server-initiated connections.
Update the TCPCLIENTPORT with this new port
number.
ANS1019E
The volume could not be opened.
Explanation: An error occurred when TSM tried to

open the volume for a backup or restore operation.
System action: The requested operation does not run.
User response: Examine the client error log for
additional messages related to this error. Verify that the
volume is available, and is not locked by another
process. Try the operation again. If the problem
persists, contact IBM technical support for further
assistance.
System action: The session is not started.
ANS1020E
Explanation: An error occurred while backing up

Windows system object files. The backup did not
complete.
ANS1016I
No eligible files were found.
Explanation: The backup or archive operation

completed, but no files were processed. Possible
reasons for this include:
The directory that was backed up or archived
contains no files
System object backup failed.

User response: Ask your system administrator to
check the error log. Restart the Windows service
associated with the system object indicated in the error
log, and retry the backup operation
The files are excluded from backup or archive

System action: None
User response: Check the path you entered.
ANS1017E
Session rejected: TCP/IP connection

failure
Explanation: An attempt to connect to the server

using TCP/IP communications failed. This error can
occur if the LAN connection went down or if your
system administrator canceled a backup operation.
System action: Session rejected. Processing stopped.
User response: Retry the operation, or wait until the
server comes back up and retry the operation. If the
further help.
ANS1021E
System object restore failed.
Explanation: An error occurred while restoring

Windows system object files. The restore did not
complete.
check the error log. Restart the machine, and then
restore the system object indicated in the error log
again.
ANS1022E
Cancel failed for node: node-name

filesystem: fs-name operation: op-type
error: error
Explanation: The request to cancel a remote operation

has failed. The node, filespace, operation and reason for
the failure are shown.
System action: TSM operation not cancelled.
more information.
664
ANS1023E ANS1030E
ANS1023E
Session rejected: Node type mismatch
Explanation: Your node name is associated with a

different type of operating system (such as OS/2 or
AIX) and cannot be used on this system.
System action: TSM canceled the current operation.
User response: If you need a new node name, see
your system administrator to assign a new one to you.
Generally, you have a unique node name for each
machine and operating system pair that requires access
to the server.
persists, contact your TSM administrator or IBM

technical support for further assistance.
ANS1029E
Communication with the TSM server is

lost.
Explanation: This message is issued after the session

with the TSM server is unexpectedly lost. The client
error log might contain additional information
regarding this problem.
User response:
ANS1024E
Failed to update backup attributes on

server for backup type backup for
filespace namepath-namefile-name, object
id object-id:object-id return code return
code.
Explanation: TSM failed to update attributes for the

named backup object on the server. The server may not
reflect correct state of the backup.
User response: Check preceding error messages in
error log for more information. Retry the operation. If
problem continues, contact your TSM administrator.
ANS1025E
Session rejected: Authentication failure
Explanation: Authentication failure. You entered an

incorrect password.
User response: Enter your correct password. If you
cannot remember the correct password, see your
system administrator to have a new one assigned for
your node name.
ANS1026E
The session is rejected: There was a

communications protocol error.
Explanation: An unexpected network message was

received by the client. This could be caused by network
problems or a programming error.
v Restart the TSM client and retry the operation.

v If the problem persists, review the client error log for
other messages that might be related to this problem.
v Verify that network connectivity exists between the
TSM client machine and the TSM server machine.
v Contact your TSM administrator for further
assistance. The TSM administrator can review the
TSM server activity log for additional information
about the problem.
ANS1030E
The operating system refused a TSM

request for memory allocation.
Explanation: TSM requires access to memory in order

to store information as processing proceeds. In this
case, more memory was requested than the operating
system would allocate. Possible reasons include:
The system is low on memory.
The process in which the program runs has
exceeded the maximum memory that it is allowed
to allocate.
Some other error condition occurred that caused the
program to think it is out of memory.
System action: TSM cannot complete the requested
operation.
User response: Close all unneeded applications and
try the operation again. If the operation still fails, try
dividing the task into several smaller units. For
example, if a file specification contains several high
level directories, run the TSM task serially for each
directory. If the TSM task is an incremental backup, use
the option -memoryefficientbackup=yes.
User response: Verify that your communication path

is functioning properly and try the operation again. If
the problem persists, contact your TSM administrator
for further assistance.
For UNIX systems that support resource limits, check

to see b if the memory resource limit is too low by
entering the following command: ulimit -a
ANS1028S
Based on the resulting data, you can ask the UNIX

system root user to increase resource limits so that it
will override the current default. The UNIX system root
user has the authority to increase resource limits.
An internal program error occurred.
Explanation: TSM encountered an unexpected

condition and can not continue the operation. This
might be a programming error.
665
ANS1031E ANS1038S
ANS1031E
The attempt to establish a TCP/IP

connection timed out before the
connection was made.
ANS1034E
The specified TCP/IP host name is

unreachable
Explanation: None.
Explanation: The TCP/IP host name specified in the

TCPSERVERADDRESS statement cannot be reached.
User response:
User response: Check your options file for the correct

TCPSERVERADDRESS statement. See your
administrator for the correct name of the server.

v Check the client options file and verify that
TCPSERVERADDRESS and TCPPORT specify the
correct TCP/IP address and port number for your
TSM server.
v If the problem persists, see your TSM administrator
ANS1032E
An attempt to establish a TCP/IP

connection was rejected by the host
Explanation: An attempt to establish a TCP/IP

connection was rejected by the server.
User response: The server was not fully initialized, is
not currently running, was not enabled for TCP/IP
communications, or an incorrect TCP/IP port number
was specified. If the problem continues, see your
system administrator.
ANS1035S
Explanation: Common reasons for this error include:

v The default options file does not exist.
v You specified the -OPTFILE option when starting the
TSM client, but the options file you provided does
not exist.
v The DSM_CONFIG (or DSMI_CONFIG if you are
using the TSM API) environment variable specifies
an options file that does not exist.
System action: TSM client processing stops.
User response: Make sure that the options file you
want to use exists. Review the information on
configuring TSM in the TSM client manual specific to
your operating system. If the problem persists, ask
your TSM administrator for further assistance.
ANS1036S
ANS1033E
An invalid TCP/IP address was

specified.
Explanation: The TCP/IP address specified by the

TSM clients TCPSERVERADDRESS setting could not
be found on the network. Common reasons for this
error include:
v The TCPSERVERADDRESS client option specifies the
wrong TCP/IP address for the TSM server.
v The machine that hosts the TSM server is not on the
network.
v A network problem is preventing the TSM client
from reaching the machine that hosts the TSM server.
User response: Verify that the TCPSERVERADDRESS
and TCPPORT settings have the correct values for your
TSM server. Use your operating systems ping (or
similar) utility to ensure that your machine can locate
the machine that hosts the TSM server across the
network. Try the operating again. If the problem
persists, ask your TSM administrator for further
assistance.
Options file file-name could not be

found.
The option option or the value supplied

for it is not valid. It was found in
options file file-name at line number:
number The complete entry: entry
Explanation: The specified option in the TSM options

file (file-name) is in error. Either the option itself or its
value are invalid.
User response: Correct the options file entry.
ANS1037S
Invalid keyword specified
Explanation: TSM found an incorrect keyword in the

options file.
User response: Correct the options file with valid
entries.
ANS1038S
Invalid option specified
Explanation: An incorrect option was specified to

TSM.
User response: Correct the options used for running
TSM.
666
ANS1039S ANS1049E
ANS1039S
The include or exclude pattern cannot

be parsed.
Explanation: The pattern is formatted incorrectly or is

too complex for TSM to interpret.
User response: Verify that the include or exclude
pattern is specified correctly. If the pattern is correct,
then contact IBM technical support for further
assistance.
ANS1040S
Include/Exclude pattern is missing a

closing bracket
Explanation: The include or exclude pattern is

incorrectly constructed. The closing bracket is missing.
options file and use a valid environment variable. Retry

the operation.
ANS1045S
Explanation: Incorrect syntax is specified in the

options file. Make sure that the variable is enclosed in
curly braces.
System action: TSM attempts to continue the current
operation.
User response: Check the syntax of environment
variable in the options file. Correct it and retry the
operation.
ANS1046S

User response: Correct the syntax for the pattern.
ANS1041S
Include/Exclude pattern must start with

a directory delimiter
Explanation: The include or exclude pattern must start

with a directory delimiter.
Environment variable syntax error.
Environment string for variable

environment-name too long. Anything
beyond 1024 characters is being ignored
Explanation: Environment variable expanded to a

string which is too long. Make sure that the string is no
more than 1023 characters long.
operation.
User response: Check the length of environment
string and break it up into smaller strings using
multiple environment variables.

ANS1047E
ANS1042S
Include/Exclude pattern has a ...

without beginning/ending directory
delimiter
Explanation: The include/exclude pattern has a ...

without a beginning or ending directory delimiter.
The destination file system is

unavailable. The following object was
skipped: File space:filespace-name
Pathname:path-name Filename:file-name
Explanation: The client is trying to restore or retrieve

the specified object to a destination that is not valid,
does not exist, or cannot be reached.
System action: The object is not restored or retrieved.

Processing continues with the next object.
ANS1043S
User response: Try the command again using a

different destination.
Quotes are not matched
Explanation: The quotes specified in the pattern are

not the same and do not make a set.
User response: Correct the pattern by using matching
quotes in the syntax.
ANS1044S
Unresolved environment name

environment-name.This filespace is being
ignored. Processing Continues.
Explanation: The specified environment-name in the

options file is invalid.
operation.
User response: Check the environment variable in the
ANS1048E
Device volname is not local
Explanation: The selected path is not a local device

and therefore is not a valid object for image operations.
System action: The requested logical volume
User response: Choose another object.
ANS1049E
filename is not a valid destination file

for image restore
Explanation: The filename you specified is not a valid

name for a file or it is a directory.
System action: Restore processing stopped.
667
ANS1050E ANS1058E
User response: Specify a correct filename for image
restore.
ANS1050E
The volume volume-name could not be

locked.
resolved, contact IBM technical support for additional

assistance.
ANS1055I
Explanation: An error occurred when TSM tried to

open the volume for a backup or restore operation.
additional messages related to this error. Verify that the
volume is available, and is not locked by another
process. Try the operation again. If the problem
assistance.
ANS1051I
Invalid password
Explanation: You entered an invalid password.

System action: TSM cannot connect to the server
without the correct password.
User response: Enter the password, or ask your
system administrator for the correct password.
ANS1052E
Direct connection to the Storage Agent

is not allowed.
Explanation: You cannot connect directly to the

Storage Agent.
User response: To perform Lanfree operations using
the Storage Agent, specify the ENABLELANFREE
option in your options file, and restart the process.
ANS1053I
Existing filespace name filespace-name

has been renamed to filespace-name
Explanation: The existing filespace name using the

volume label has been renamed to the UNC format
naming convention.
ANS1054E
Existing filespace filespace-name cannot

be renamed to new filespace
filespace-name. TSM return code = retcode.
Trying to rename existing filespace

filespace-name to new filespace
filespace-name, but drive letters do not
match, old=drive-letter, new=drive-letter.
Ignore the old filespace and backup to
the new filespace.
Explanation: Trying to rename the existing filespace

name using the volume label to the UNC format
naming convention but the drive letters do not match.
Leave the existing filespace alone and create a new
filespace.
ANS1056E
Share/network path cannot be resolved.

Path does not exist.
Explanation: For backup: Trying to backup

share/network, which either does not exist or does not
have the correct privilege to access the share. For
restore : Trying to restore to a share/network path that
cannot be resolved. The directory path does not exist.
User response: Retry the command and specify a
destination, or restore the directory tree first before
trying to restore the share point.
ANS1057I
File space filespace-name cannot be

renamed to new file space filespace-name,
because the new file space already
exists.
Explanation: The client was unable to migrate a file

space name from the volume label naming convention
to the UNC naming convention because the new file
space already exists on the TSM server.
System action: The operation proceeds using the new
file space. The old file space is ignored.
User response: No action is necessary, but if the data
in the old file space is no longer needed, it can be
deleted from the TSM server.
ANS1058E
The restore destination cannot be

reached.
Explanation: The client was unable to migrate a file

space name from the volume label naming convention
to the UNC naming convention.
Explanation: Either the destination file system is

invalid or it cannot be reached.
User response: Check the client error log and the TSM
server activity log for any other messages that might
help identify the problem. If the problem cannot be
User response: Try the command again using a

different destination.
668
ANS1059E ANS1067E
ANS1059E
Two inactive objects with the same

image name were selected. Process
terminates
Explanation: You selected more than one inactive

version of the same image object (logical volume). The
system has no way to decide which you want to
restore.
System action: The requested logical volume restore is
not performed.
User response: Retry the operation, selecting an active
version or only one inactive version of the volume you
wish to restore.
ANS1063E
The specified path is not a valid file

system or logical volume name.
Explanation: None.
System action: The logical volume operation is not
performed.
User response: Try the operation again using a valid
path.
ANS1064E
An unexpected error occurred while

processing the image operation.
Explanation: None.
ANS1060E
The specified path is not a mounted

filesystem
Explanation: You entered a file system name that does

not correspond to a mounted file system for this
system. It is possible the file system name is
misspelled, or simply that the file system is not
currently mounted.
User response: Examine the client error log for any

additional messages that may have been issued before
or after this message. Correct any problems, if possible.
If the cause of this message can not be determined or
resolved, contact IBM technical support for further
assistance.

ANS1065E
User response: Retry the operation, using name of a

mounted file system.
Explanation: The current system has a mix of installed

components.
ANS1061E

The specified device corresponds to a

mounted file system; you must specify
the file system by name.
Library version of the image utility does

not match that of the TSM API
User response: Re-install all TSM components
Explanation: You entered a logical device name that is

mapped to a mounted file system. This volume must
only be referenced by its file system name.
ANS1066E

Explanation: None.
User response: Try the operation again, using the file

system name instead of the device name.
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
image into a single destination volume. When more
than one object is selected, each must be restored to its
original location.
System action: The requested logical volume restore is
not performed.
User response: Retry the operation, selecting one
object to be restored to the given destination, or retry
the operation without entering the destination.
The restore operation completed

successfully, but the file system could
not be remounted.
System action: The file system is left unmounted.

User response: Use the mount command to mount the
file system. On AIX, run fsck if requested by the
operating system.
ANS1067E
A call to a system function returned an

unexpected error.
Explanation: If you are performing a JFS2 snapshot

based operation, it is possible that the snapshot was not
large enough to contain all the changes made to the
filesystem after the snapshot was created. This could
cause the snapshot to become invalid thereby
preventing TSM client from reading the snapshot.
additional messages related to this error. Try the
operation again. If the problem persists, contact IBM
If you are performing a JFS2 snapshot based operation,
669
ANS1068E ANS1075E
please use the default snapshotcachesize of 100% and
ensure that the volume group has sufficient disk space
to allocate snapshots at least as large as the file system
ANS1068E
Device is not local
Explanation: The selected path is not a local device

and therefore is not a valid object for image operations
User response: Choose another object.
ANS1069E
An error occurred while reading data

from the device
Explanation: An error occurred while reading data

from the device. Windows Only: This could be due to
bad sectors on the drive.
User response: Retry the operation, then check the
error log for more information. Windows Only: Please
run chkdsk /r and retry the operation. If the problem
persists, a possible workaround is to back up the entire
drive using a regular (non-image) backup. Please
ensure that all your data is backed up. Then format the
drive using a full format (without the /q quick format
option). Then restore the data and retry the image
backup operation.
ANS1070E
Write error
ANS1072E
Unable to continue operation; Drive

drive-name has no volume label.
Explanation: The specified drive-name in the domain

list does not have a volume label.
User response: Use the system format utility to place
a unique volume label on all drives on which you
intend to run TSM.
ANS1073E
The file space for domain domain-name

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

be found on the server, but it no longer exists. It is
possible that a command was issued to delete the file
space from the server while the current operation was
in progress.
System action: TSM processing stops.
recurs, check the error log for any other messages that
might indicate a reason for the failure. Try to correct
any indicated problems, then try the operation again. If
the problem persists, contact IBM technical support for
further assistance.
ANS1074W
The operation was stopped by the user.
Explanation: The operation was stopped at the request

of the user. This usually occurs when the Q key is
pressed two times.
Explanation: An error occurred while writing data to

the device.

ANS1075E
User response: Re-try the operation, check error log

for more information.

to allocate.
ANS1071E
Invalid domain name entered:

domain-name
Explanation: You entered an invalid domain

domain-name. Check whether the domain name is a file
system and the file system is mounted. A directory
cannot be specified in the domain option, unless it is a
virtual mount point.
System action: Processing continues if there are other
file systems in the domain option to back up.
User response: Enter a valid drive or file system name
(domain).
670
()The operating system refused a TSM


operation.
ANS1076E ANS1087E
For UNIX systems that support resource limits, you can
check if the memory resource limit is too low by
ANS1076E
The specified directory path could not

be found.
Explanation: An invalid or unreachable directory path

was specified.
directory path.

User response: Enter a correct file specification as
described in the appropriate Using the Backup-Archive
Client book for the particular operating system.
ANS1083E
Explanation: You tried to retrieve files when no files

for the specified drive or file system (filespace-name)
to retrieve.
ANS1084E
ANS1078S
Unknown system error error-code

occurred.
No files have previously been archived

for filespace-name
No files have previously been backed

up for filespace-name
Explanation: An error unknown to TSM error-code

occurred within the client program.
Explanation: You tried to restore files when no files

for the specified drive or file system (filespace-name)
System action: The client stops.
User response: Check the error log for any other

messages that might indicate a reason for the failure.
Try to correct any indicated problems, then try the

you to restore.
ANS1079E
No file specification entered
Explanation: You did not enter a file specification as

prompted.
System action: TSM did not continue with the
ANS1085E
No memory available to store Archive

Management Class override name
Explanation: Not enough memory was available for

the operation.
User response: Retry the operation or restart the
system with fewer programs in memory.
User response: Enter a file specification to continue.

ANS1086E
ANS1081E
Invalid search file specification string

entered
Explanation: You entered a file specification or search

string that contains incorrect characters or contains
wildcard characters in the drive specification or file
system name.
described in the appropriate Using the Backup-Archive
ANS1082E
Invalid destination file specification

file-name entered
Explanation: You entered a destination file-name

specification that contains incorrect characters or has
wildcard characters in the specification.
File not found during Backup, Archive

or Migrate processing

Another process deleted the file before it could be
backed up, archived or migrated by TSM.
ANS1087E
Access to the specified file or directory

is denied

the directory.
671
ANS1088E ANS1097E
ANS1093E
Your TSM server does not support

point-in-time processing.

incorrect or does not exist on the machine.
Explanation: The client has requested a point-in-time

query or restore operation, but the TSM server to
which the client is connected does not support
point-in-time operations.

User response: Make sure that you are connected to

the correct TSM server. If you are connected to the
correct server, then try the command again without
specifying any point-in-time options.
ANS1088E
ANS1089E
File space filespace-name does not exist
Destination directory path length

exceeds system maximum

ANS1090E
The LVM1 device is no longer

supported by this client.
Explanation: The selected path refers to a volume

device managed by LVM version 1. LVM 1 is no longer
supported by this version of client and therefore is not
a valid object for image operations.
User response: Use earlier versions of the client that
support LVM1 to perform the logical volume operation.
Alternatively, you can upgrade to LVM2 and migrate
the volume to LVM2. LVM2 is supported by this client
for logical volume operations.
ANS1091E
Communications error with server

during object query
Explanation: An unexpected communications error

occurred during an object query to the server.
User response: Verify that communications are active
between the client and server machines. Server outages,
processor outages, and communication controller
outages can cause this error.
ANS1092W
No files matching search criteria were

found
Explanation: You entered a search pattern or file name

that cannot be found in the server database.
User response: Ensure that your search pattern is
correct, or specify a new search string.
672
ANS1094E
Server does not support Query Node

command.
Explanation: The server to which you are connected

does not support Query Node command.
User response: Use a TSM Server that supports Query
Node command.
ANS1096S
Either the node does not exist on the

server or there is no active policy set for
the node.
Explanation: This error occurs when you try to access

another nodes data. Either the node is not registered
with the TSM server, or there is no active policy set for
the node.
System action: Processing stops.
User response: Verify that the node whose data you
are trying to access is registered with the TSM server. If
you have more than one TSM server, make sure you
are connecting to the correct server, then try the
operation again. If the problem persists, contact your
TSM administrator for further assistance.
ANS1097E
The client help text cannot be read from

the help file.
Explanation: The help file was opened successfully

and its table of contents are available, but there is a
problem reading the text from the help file.
User response: If the DSM_DIR environment variable
is set, verify that it points to the directory containing
the current level of TSM program files, then try the
operation again. If the problem recurs, re-install the
TSM client software. If the problem persists, IBM
ANS1098E ANS1106E
ANS1098E
Process terminated; Program memory

exhausted.
Explanation: The program used all available storage.

User response: Free any unnecessary programs (TSRs)
that are running, and retry the operation. Reducing the
scope of queries and the amount of data returned can
also solve the problem.
ANS1099E
File filename not previously archived
Note: The TSM Client operates much more efficiently if

it expands wild cards internally, rather than accepting
the expanded list from the shell.
User response: Reduce the number of arguments and
retry the operation. For UNIX-based systems, ensure
that you have surrounded the specification containing
pattern matching characters with quotes. As an
alternative, use the -REMOVEOPERANDLIMIT option
on the failing archive, incremental, or selective
command.
Explanation: You tried to give access to a file, which

is not stored on the server.
ANS1103E
Explanation: You entered an invalid management

class.
User response: Ensure that the correct filename is

specified.
ANS1100E
File filename not previously backed up
Explanation: You tried to give access to a file, which

is not stored on the server.
System action: TSM is unable to do the requested

operation.
User response: Retry the operation using a valid
management class.
ANS1104E

User response: Ensure that the correct filename is
specified.
ANS1101E
User is not authorized to encrypt

filename.
Explanation: The user is not authorized to encrypt the

file. Normally, only a TSM authorized user or a root
user can use TSM encryption. However, a certain
combination of PASSWORDACCESS and
ENCRYPTKEY options may allow encryption
operations by a non-authorized user.
System action: The file is not backed up or restored.
User response: Log in as a root or TSM authorized
user and retry the operation. Refer to Backup-Archive
Client Installation and Users Guide for the correct usage
of the ENCRYPTKEY option.
ANS1102E
An excessive number of command line

arguments are passed to the program.
Explanation: This command processing routine

received more operands than it can use. The rules are:
v Query can contain only one file specification.
v Restore and Retrieve can contain two file
specifications.
v Archive, Incremental, and Selective can contain a
maximum of 20 file specifications. To bypass the
20-operand limit, use the -REMOVEOPERANDLIMIT
option on the failing archive, incremental, or
selective command.
Invalid management class entered
The management class for this file does

not have a valid archive copy group.
This file will not be archived.
Explanation: The management class for this file does

not have an archive copy group specified. This file will
not be archived.
User response: Add a valid archive copy group to the
management class, and then retry the operation.
ANS1105E
The management class for this file does

not have a valid backup copy group.
This file will not be backed up.

not have a backup copy group specified. This file will
not be backed up.
User response: Add a valid backup copy group to the
ANS1106E
ENCRYPTKEY SAVE not configured

correctly. Encryption not used.
Explanation: This message is issued for TSM

Authorized Users and root users when ENCRYPTKEY
SAVE and PASSWORDACCESS PROMPT options are
set. Please note that these are the default values. These
values do not allow encryption.
System action: The file is not encrypted.
User response: To save encryption keys, you must
change configuration values. Add PASSWORDACCESS
GENERATE to your system option file.
673
ANS1107E ANS1116E
ANS1107E
Invalid option/value: option
Explanation: You specified an incorrect TSM option or

option value option.
System action: For the command line client:
Processing stops.
For the native GUI client: There is a small set of
options critical to the initialization of the client. If an
error is found in one of these, this message is presented
and the client terminates without further processing.
User response: Specify a correct TSM option as
defined in the appropriate Using the Backup-Archive
ANS1108E
Invalid option (option) for the function

command
Explanation: There are two possible reasons for this

message:
v The option option was specified for a command or
subcommand (function) that cannot make use of that
option.
v The option appears on the initial command line and
is not valid there.
User response: See the Backup-Archive Client
Installation and Users Guide for correct use of the named
option.
ANS1109E
User is not authorized to encrypt the

file.

ANS1110E
The client help file file-name could not

be opened.
Explanation: This usually occurs when the help file

file-name cannot be found.
674

ANS1111E
The table of contents cannot be read

from the help file.
Explanation: The help file was opened successfully

but there was a problem reading the table of contents.
ANS1113E
The snapshot cache location is not valid.
Explanation: The snapshot cache location must point

to a local volume that is formatted with NTFS. The
default cache location is on the same volume where the
snapshot is being performed. The operation will
continue without snapshot support.
System action: The client does not execute the
snapshot backup operation.
User response: Specify a different snapshot cache
location using the SNAPSHOTCACHELOCATION
option.
ANS1114I
Waiting for mount of offline media.
Explanation: The server is waiting for the requested

media to become available before the operation can
continue.
System action: TSM waits for requested data.
ANS1115W
File file-namefile-namefile-name excluded

by Include/Exclude list
Explanation: You can not back up, archive, or migrate

files that are excluded.
System action: TSM does not process the file.
User response: If the file is intentionally excluded,
then this message can be ignored. Otherwise modify
the include/exclude list, restart the client, and try the
operation again. Contact your TSM administrator for
further assistance.
ANS1116E
The process is running in a

non-interactive mode, but requires user
input.
Explanation: This process requires keyboard input,

but non-interactive processes are unable to read input
from keyboard.
ANS1117E ANS1127E
User response: Perform the following actions to
resolve this error:
ANS1122W
v Run the product in interactive mode.

v Ensure your password is set correctly.
ANS1117E
The PICK and LATEST options are not

valid together
Explanation: During a restore, PICK and LATEST

options cannot be used together.
User response: Try again using either the PICK or the
LATEST option.
Explanation: The specified filespace-name does not exist

on the server. Your system administrator deleted the
file space or another client using your clients node
name might have deleted it.
ANS1123E
ANS1118I
Invalid file space number entered. Try

again.
Explanation: The number that represents a file space

was incorrect while you were using the PICK option.
System action: TSM waits for your specification.

on the server. The file space might have
been deleted by another client using
your clients node name or an
administrator.
The vertical screen dimension is too

small to display the Help directory.
Increase your window height.
Explanation: Execution of the HELP command

requires space for both the user prompts and at least
one line of the HELP directory.
User response: Enter a correct file space number.
System action: The help directory is not displayed,

and the help command cannot complete.
ANS1119I
User response: Increase the size of your display

window to allow more rows of text to be displayed.
Initiating the removal of filespace-name

file space.
Explanation: Indicates that file space deletion has

started on the specified filespace-name.
ANS1125E
Unmatched Quotes: string

ANS1120E
User response: Correct the pattern using matching

Removal of file space filespace-name

failed
Explanation: None.
ANS1126E
The file space cannot be deleted because

this node does not have permission to
delete archived or backed up data.
User response: Try to remove the file space again. If

the problem continues, ask your TSM administrator to
delete the file space for you.
Explanation: You cannot delete the file space data

unless your TSM administrator has authorized your
node to do so. Authorization permits you to delete
backup data, archive data, or both.
ANS1121I
System action: Delete processing fails.
A request for removal of file space

filespace-name has been successfully sent
to the server.
Explanation: TSM has requested deletion of the

specified filespace-name. The deletion process may not
have actually been completed when this message is
displayed. To verify successful deletion, consult the
server logs.
User response: Use the DSMC QUERY SESSION

command to verify your authorization. Ask your TSM
administrator to provide the necessary authorization or
to delete the file space for you.
ANS1127E
Your node does not have permission to

delete archived files.
It is possible for errors to occur on the server during

the deletion process, or the file space might contain
archive objects in deletion-hold status. In either case,
the file space will not be deleted.
Explanation: You cannot delete archived files unless

your TSM administrator has authorized your node to
do so.
System action: TSM does not delete the archived files.

675
ANS1128S ANS1135E
administrator to provide the necessary authorization.
ANS1128S
The management class assigned to

directories does not exist.
Explanation: The management class named on the

DIRMC option does not exist in your assigned policy
set on the server. The error log contains an entry
showing the invalid management class name.
User response: Remove the current DIRMC option
from the client options file, then run DSMC QUERY
MGMTCLASS -DETAIL to view information about
available management classes. Make sure the
management class you select has a backup copy group.
If you have more than one TSM server, make sure you
are connecting to the correct server. If you are unable to
find a suitable management class, contact your TSM

User response: Change the volume labels on the
removable media volumes so that there are no
duplicate labels. Then restart TSM and try the
operation again.
ANS1132E
Explanation: You are trying to define authorization for

the specified node, which already has authorization
defined.
System action: TSM did not redefine authorization for
the specified node.
User response: Update the authorization, or delete the
old rule and define a new one, or use the current
authorization.
ANS1133W
ANS1129S
There is no backup copy group in the

management class used for directories.
Explanation: The DIRMC option names a

management class that contains no backup copy group.
ANS1130E
The drive has no label. The operation

cannot continue.
Explanation: Backup or archive of removable media

requires that the media have a volume label. An
attempt was made to back up or archive data on a
removable volume that has no label.
User response: Create a volume label on the
removable media, then try the operation again.
ANS1131E
A duplicate volume label exists. The

operation cannot continue.
Explanation: For removable media, TSM uses the

volume label as the file space name. To prevent data
from different volumes being stored in the same file
space on the TSM server, backup or archive of
removable media volumes having duplicate volume
labels is not allowed.
676
Access rule Access Rule already defined

for node node. Old rule must be
deleted before new one can be defined.
An expression might contain a wildcard

not enclosed in quotes.

because a UNIX shell expands a wildcard expression,
such as an asterisk (*) or a question mark (?), that has
no quotes.
If the expression contains no wildcard characters and
you wish to place more than the stated limit of
operands on the Archive, Selective, or Incremental
command, add the -REMOVEOPERANDLIMIT option
to the command, and try it again.
System action: Command dependent.
User response: Enclose the wildcard expression in
quotes, or add the -REMOVEOPERANDLIMIT option
and enter the command again.
ANS1134E
Drive drive-name is an invalid drive

specification
Explanation: The specified drive-name was found to be

invalid; the drive probably has not been defined.
System action: TSM skips the invalid drive and
continues to the next drive.
User response: Check the invalid drive.
ANS1135E
Drive drive-name1 is a virtual drive of

drive-name2. It cannot be backed up or
archived.
Explanation: Drive drive-name1 was found to be a

substitute (SUBST) of drive drive-name2. The SUBST
drive cannot be backed up or archived.
System action: The SUBST drive is skipped.
Processing continues with the next drive.
User response: Do not specify any file specifications
ANS1136E ANS1147E
for a drive that is a substitute of another drive. Remove
any explicit substitute drives from the DOMAIN
statement or use the -<drive:> notation to remove a
substitute drive if ALL-LOCAL is specified.
ANS1136E
Not file owner
Explanation: The file cannot be backed up because the

client is not the file owner.
System action: TSM skips the file.
ANS1141W
Unknown command - command-name
Explanation: You entered an incorrect command-name.

User response: Enter the correct command.
ANS1143E
The DIRSONLY and FILESONLY

options are not valid together
Explanation: The DIRSONLY and FILESONLY options

cannot be used together.
ANS1137W
Invalid Index number skipped.
Explanation: An incorrect number was entered for the

Index.
User response: Try again using either the DIRSONLY

or the FILESONLY option.
ANS1144W
User response: Correct the Index entry and retry the

operation.
Explanation: None.
Password authentication not active on

server

ANS1138E
The command-name command must be

followed by a subcommand
Explanation: You entered an incomplete

command-name.
User response: Because password authentication is

turned off on the server, you do not need to update the
password.
ANS1145E
User response: Enter the correct syntax of the

command and continue.
The maximum macro nesting level has

been exceeded. Macros may be nested
up to 10 levels.
Explanation: None.
ANS1139W
object-nameobject-nameobject-name was
restored as temp-name. A reboot is
required to complete the restore.
Explanation: The file being restored was in use by

another application, so it could not be immediately
replaced. The file will be replaced during the next
reboot of the operating system. It is important to note
that until the reboot occurs, the system or its
applications might be unstable. The degree of
instability depends on the criticality of the file to the
operating system or applications.
System action: TSM restored the file with a temporary
name, and instructed the operating system to replace
the original file with the restored file during the next
boot of the operating system.
User response: Reboot the machine as soon as
possible after the TSM restore operation ends.
ANS1140E
Invalid format for Set Access command.
Explanation: None.
System action: The macro is ignored and an error is

returned.
User response: Reduce the level of macro nesting.
ANS1146E
Macro file file spec cannot be opened.
Explanation: A macro command has been entered that

specifies the macro file name shown. However, that file
cannot be opened for reading.
returned.
User response: Enter the command with the proper
macro name.
ANS1147E
File is temporarily unavailable.


User response: Enter the SET ACCESS command
using the correct syntax.
677
ANS1148I ANS1155E
ANS1148I
Command-name command successfully

completed
ANS1152W
Explanation: The specified command-name was

successfully completed.
The kernel level is below the required

level for LVM support. No LVM
volumes will be available for image
operations.
User response: Continue with normal operations.
Explanation: The LVM support for image operations

requires kernel level to be minimum at 2.6. LVM
volumes will not be recognized by the TSM client.
ANS1149E
System action: All subsequent logical volume

operations on LVM volumes will fail.
System action: TSM completed the command.
No domain is available for incremental

backup. The domain may be empty or
all file systems in the domain are
excluded.
Explanation: An incremental backup was started, but

no domain was selected. There are two possible reasons
for this message:
v The client is a diskless workstation for which no
local file systems exist.
v An attempt was made to back up a file system that is
excluded with the EXCLUDE.FS option.
User response: Choose a domain and restart the
incremental backup. Make sure that the DOMAIN
statement specifies the file systems you wish to back
up. Prevent this message by not trying to back up the
file system that is excluded with EXCLUDE.FS. If this
file system should be backed up, then remove the
EXCLUDE.FS option.
User response: Use earlier versions of the client that

support LVM1 to perform the logical volume
operations. Alternatively, you can upgrade the kernel to
the required level to fully utilize logical volume
operations on LVM2.
ANS1153E
Explanation: The indicated file system is a cluster

disk. Because the CLUSTERNODE option is set to NO,
the file system cannot be backed up or archived.
User response: If the CLUSTERNODE option is
incorrectly set to NO, then change the option to YES
and try the operation again. Otherwise see the client
manual for further information about configuring the
TSM client to run in a cluster environment.
ANS1154E
ANS1150E
Unable to restore current user profile

because you are running as a local
system account.
Explanation: The local system account does not have a

profile. Therefore you cannot restore its profile.
User response: Log on to the user whose profile you
want to restore.
ANS1151E
drive-name1 is not a cluster disk.
drive-name1 is a cluster disk.

namepath-namefile-name contains an
invalid multibyte sequence for the
current locale.
Explanation: An illegal multibyte sequence for the

current locale was found in the object name. Either the
path or file name has been corrupted or is coded in a
language other than that of the current locale.
System action: Object skipped.
User response: If the file name and path are not
corrupted, process the file in the locale for which it is
valid.
Explanation: The indicated file system is not a cluster

disk. Because the CLUSTERNODE option is set to YES,
the file system cannot be backed up or archived.
ANS1155E
Explanation: An image backup was started, but no

domain was specified.

incorrectly set to YES, then change the option to NO
678
No domain is available for image

backup.

User response: Choose a domain and restart the
image backup. Set the image domain using the
domain.image option in your dsm.opt file, either
manually, or by using the GUI preferences editor.
ANS1156E ANS1168E
ANS1156E
NODENAME cannot be the local

machine name when CLUSTERNODE is
set to YES
Explanation: When TSM is running as a cluster node,

the node name cannot be the local machine name.
User response: Change the node name either to the
cluster name or to any other name, and restart TSM.
ANS1157E
The registry cannot be backed up or

restored when the client is running as a
cluster node.
Explanation: When the CLUSTERNODE option is set

to YES, the registry cannot be backed up or restored.
System action: The registry is not backed up or
restored.
ANS1158E
The event logs cannot be backed up or

restored when the client is running as a
cluster node.
Explanation: When the CLUSTERNODE option is set

to YES, the event logs cannot be backed up or restored.
file system. On AIX, run fsck if requested by the

operating system.
ANS1163E
Filesystem could not be unmounted.
Explanation: The system call to unmount the file

system failed.
performed.
User response: Make sure the device or file system is
not being accessed, then retry the operation.
ANS1164E
Filesystem is not mounted
Explanation: The named file system is not currently

mounted. It must be mounted for TSM to perform an
image backup.
performed.
User response: Mount the file system.
ANS1165E
Destination is smaller than source
Explanation: The space allocation for the selected

destination is smaller than the source.
System action: The restore operation is not performed.
User response: Choose a different, bigger destination
or increase the size of the destination file space.
System action: The event logs are not backed up or

restored.
ANS1166E

Explanation: The source and destination file system

types do not match.
ANS1159E
The specified file is being used by

another process
Source and destination are not the same

file system type.

User response: Choose a destination that has the same
file system type as the source.
Explanation: The specified file is being used by

another process. You tried to read from or write to a
file that is currently being used by another process.
ANS1168E
v The image command was executed by a non-root

user

ANS1162E
Filesystem could not be mounted
Explanation: The system call to mount the file system

failed.
ERROR: could not create image object.
Explanation: Creation of the image object failed for

one of the following reasons:
v The image plugin library was not found.

User response: Retry the operation after correcting the
cause for failure.
System action: The requested logical volume function
is not performed.
System action: The file system remains unmounted.

User response: Use the mount command to mount the
679
ANS1169W ANS1190E
ANS1169W
There is no table of contents for

image-name.
ANS1184W
The command subcommand command is

not supported on this client.
Explanation: The image item for which a table of

contents was requested is either a RAW logical volume
or it was backed up without the -TOC option.
Explanation: The command subcommand command is

not supported for the client running on this operating
system on this computer.
System action: No table of contents is displayed.
User response: Select another image object for TOC

display.

ANS1185W
ANS1170I
Invalid selection number entered. Try

again.
Explanation: You entered a number not shown in the

list of images. It is either less than one or greater than
the highest item number displayed.
System action: TSM waits for you to enter a valid
selection.
User response: Enter a number from the list or Q to
quit.
ANS1177E

User response: Specify a valid path and execute the
command again.
There was a communication failure with
the journal service.
Explanation: An error occurred using named pipe

communication with the journal service.
User response: Restart the journal service, then try the
ANS1183E
An unknown error occurred while

processing system object sys-obj-name:
MS API function func-name failed with
error error (error)
Explanation: An unknown error occurred while

processing a system object. The error information
captured indicates the reason for the failure. This
information can be used to diagnose the problem.
more information.
680
Explanation: The TSM server that the TSM client has

opened a session with is not capable of server-free data
movement, either because it is not supported by the
servers level or platform, or because the appropriate
license is not installed on the server.
System action: The operation is tried again, using
LAN-free (if available) or LAN-based data movement.
User response: Remove the ENABLESERVERFREE
option from the system option file.
Must specify a path for this operation.
Explanation: A path must be specified for this

operation to execute successfully.
ANS1181E
The server is not capable of server-free

data movement.
ANS1188E
The selected filesystem is managed by

HSM, and therefore is not a valid object
for image operations
Explanation: Due to the nature of HSM, image backup

is not allowed on managed filesystems.
ANS1189E
The DIRSONLY and V2ARCHIVE

options are not valid together
Explanation: The DIRSONLY and V2ARCHIVE

options cannot be used together.
User response: Try again using either the DIRSONLY
or the V2ARCHIVE option.
ANS1190E
Symbolic link linkname to target was

Explanation: Log linkname cannot be a symbolic link.

System action: The symbolic link linkname is deleted,
the log is recreated, and processing stops.
User response: Check the location of the new file. To
specify the location of log files, refer to the users
manual for the errorlogname option, the
schedlogname option, and the DSM_LOG
environmental variable.
ANS1191E ANS1200W
ANS1191E
Unable to delete symbolic link link.
ANS1198E

User response: Delete the symbolic link linkname.
An invalid snapshot cache location was

entered: .
Explanation: The SNAPSHOTCACHELocation option

value entered for this volume is not valid. The value
for this option must be an existing, full directory path.
ANS1192E
Specifying the error log link as a

symbolic link is not allowed.
Explanation: Error log linkname cannot be a symbolic

link.
the error log is recreated, and processing stops.
User response: Check the location of the new error
log. To specify the location of the error logs, refer to the
users manual for the errorlogname option and
DSM_LOG environmental variable.
ANS1193E
Specifying the trace file link as a

Explanation: For reasons of security and system

integrity, the trace file linkname cannot be a symbolic
link.
the trace file is recreated, and processing stops.
User response: Use the TRACEFILE option to specify
the actual trace file location without the use of
symbolic links.
ANS1194E
Specifying the schedule log link as a

Explanation: Schedule log linkname cannot be a

symbolic link.
the schedule log is recreated, and processing stops.
User response: Check the location of the new schedule
log. To specify the location of the schedule log, refer to
the users manual for the schedlogname option.
ANS1197E
The snapshot cache size was exceeded

during the snapshot backup.
Explanation: The image snapshot backup was not able

to complete because while creating the snapshot TSM
exceeded the snapshot cache size allowed via the
SNAPSHOTCACHESize option.
User response: Increase the SNAPSHOTCACHESize
value for this volume and retry the operation.
User response: Please enter a valid

SNAPSHOTCACHELocation value and retry the
operation.
ANS1199E
The PRESNAPSHOTCMD command

failed. The image snapshot backup will
not be executed.
Explanation: The command specified by the

PRESNAPSHOTCMD option must complete
successfully in order to execute the image snapshot
backup. If the command completed with a return code
of 0 (zero), it is considered to have completed
successfully. If the command completed with any other
return code, it is considered to have failed. If the
command failed then the image snapshot backup is not
executed.
System action: The client does not execute the image
User response: Identify and repair the problem that
caused the command to fail. If a non-zero return code
is normal for this command, then consider wrapping
the command in a script that always exits with a return
code of zero.
ANS1200W
The POSTSNAPSHOTCMD command

completed with a non-zero return code.
Explanation: If the command specified by the

POSTSNAPSHOTCMD option completed with a
non-zero return code, then the image snapshot backup
operation will continue, but with a warning-level
result. Note that the result of the
POSTSNAPSHOTCMD command will not supercede a
higher result from the image snapshot backup
command. For example, if the image snapshot backup
command completed with a return code of 12, the
image snapshot backup will be considered to have
completed with a return code of 12, regardless of the
outcome of the POSTSNAPSHOTCMD command.
System action: The image snapshot backup continues,
but with a warning return code of at least 8.
code of zero.
681
ANS1201E ANS1214E
ANS1201E
TSM cannot build a directory path

because a file exists with the same name
as the directory.
Explanation: None
User response: Remove or rename the file that has the
same name as the directory. Alternatively, you can
restore the directory to a different location.
ANS1202E
TOC backup for the image failed. Check

log files.
ANS1206E
TOC backup of a raw device is not

supported. But the raw device is backed
up.
Explanation: TOC backup of a raw device is not

supported. But the raw device is backed up.
System action: Raw device is backed up with no TOC
object.
User response: NONE.
ANS1207E
No TOC has been previously backed up

for this file system.
Explanation: An error occurred during backup of the

table of contents. Check the error log for more
information.
Explanation: The user is trying to query the TOC of a

file system. TOC backup for that file system has not
been previously done.

System action: Query stopped.
User response: Check error log.
User response: Backup the file system again with

-TOC option.
ANS1203E
ANS1212I
Table of Contents not available for

selected backup set. Please contact
server administrator.
Explanation: There is no TOC for selected backup set

System action: Expansion of selected backup set will
not be possible. Will only be able to restore the whole
backup set.
User response: Please contact server administrator to
regenerate TOC for backup set before backup set can be
expanded.

list of processes. It is either less than one or greater
than the highest item number displayed.
selection.
quit.
ANS1213W
ANS1204E
This client is not supported by the TSM

express server
Explanation: This client is not supported by the TSM

express server. This can occur if:
1. the client is configured as an TSM express client
using the CLIENTVIEW option
2. the client is trying to connect to an TSM express
server.
User response: Log in using a supported TSM express
client.
ANS1205E
This is not a supported TSM express

platform
Explanation: This is not a supported TSM express

platform.
User response: Log in using a supported TSM express
client.
Invalid Process number entered. Try

again.
Snapshot image backup is not possible

for device device-name. starting static
image backup.
Explanation: On Linux platforms, snapshot image

backup is only possible for logical volumes created by
the Linux logical volume manager (LVM). Since the
default image backup type is snapshot, backing up a
partition which is not created using LVM automatically
leads to a static image backup.
System action: Snapshot image backup will failover to
static image backup
User response: To avoid this message, use the
imagetype option to specify static or dynamic image
backup.
ANS1214E
The logical volume group does not have

enough free space to contain the volume
snapshot.
Explanation: The snapshot is created in the volume

group that contains the logical volume being backed
up. There is insufficient free space in the volume group
to contain the snapshot.
System action: The operation ends.
682
ANS1215E ANS1222E
User response: Decrease the SNAPSHOTCACHESIZE
value or make additional space available in the logical
volume group. Then try the operation again.
trying to connect, has a valid TCPSERVERADDRESS

defined in the system options file.
ANS1219E
ANS1215E
On volumes that are RAW or formatted

FAT32 the snapshot cache location
cannot be located on the same volume
that is being backed up.
Explanation: When the snapshot cache location is

located on the same volume that is being backed up the
volume must be formatted with NTFS. The default
cache location is on the same volume where the
snapshot is being performed.
A virtual node name must not equal

either a node name or the system host
name.
Explanation: A VIRTUALNODENAME option was

entered with a name the same as either a NODENAME
option or the system host name.
System action: Initialization fails and the program
ends.

option.
User response: If the virtual node name entered was

the same as the host name, remove the virtual node
name option. If it was the same as the node name
option, you can remove either one, depending upon the
intended usage. Node name is used to assign an
alternate name to your system. Virtual node name is
used to access another systems server data.
ANS1216E
ANS1220E
System action: The client does not execute the image

Not authorized to run TSM. See the

administrator for your system.
Explanation: The system options file for the server

that you are attempting to connect to contains a user
entry, a group entry, or both a user and group entry.
Your user ID, or group ID, was not found in any of the
entries. You are currently not authorized to run TSM to
this server.
System action: TSM initialization fails and the
program ends.
User response: See the TSM administrator for your
system, and ask to be added to the user or group list
for this server.
ANS1217E
Server name not found in System

Options File
The TSM server is out of resources.
Explanation: A lack of a storage resource or a

maximum value condition does not allow any new
activity.
If the problem continues, contact your TSM
administrator to isolate what resource is unavailable.
The TSM administrator can check the TSM server
activity log for messages that might explain the
problem.
ANS1221E
Transaction aborted
Explanation: The current transaction between the

server and the client stopped. A server, client, or
communication failure cannot be recovered.
Explanation: The system options file does not contain

the SERVERNAME option.

program ends.

continues, see your system administrator to isolate the
problem.

system, and make sure that the system options file
contains the server name.
ANS1218E
TCPSERVERADDRESS not defined for

this server in the System Options File
Explanation: The TCPSERVERADDRESS for this

server is not defined in the server name stanza in the
system options file.
ANS1222E
Disk space limit for this process reached

owner is full.

program ends.
system, and make sure that the server to which you are
683
ANS1223E ANS1232E
ANS1223E
File is not compressed; System failure.

ANS1224E
File compressed on a different client

machine that has more memory

System action: TSM canceled the operation.
ANS1225E
Insufficient memory for file

compression/expansion
Explanation: Not enough memory is available to do

data compression or expansion. For a restore or
retrieve, the file cannot be recalled from the server until
more storage is made available. For a backup or
archive, try running without compression if storage
cannot be made available.
ANS1228E
Sending of object object-nameobjectnameobject-name failed
Explanation: The specified file (object-name) cannot be

sent to the server. This message is accompanied by at
least one other message that has more specific
information about why the file could not be processed.
User response: Check previous messages pertaining to
this file that indicate the reason for the failure. Where
applicable, correct the conditions that prevented the file
from being sent to the server. The specific corrective
actions will depend on the reason for the failure.
ANS1229E
MODE=INCREMENTAL is not valid on

file-space. Image backup not processed.
Explanation: Because the file space has been the

subject of at least one progressive incremental backup,
the MODE=INCREMENTAL option (incremental by
image date) cannot be used with the backup image
command.
User response: If an image backup of the named file
space is desired, retry the command without the
MODE=INCREMENTAL option. To prevent this
behavior in the future, delete the file space from the
server and do only BACKUP IMAGE -mode=selective
and BACKUP IMAGE -mode=incremental from that
point on.

User response: Free up extra storage for the operation
to continue, or run the backup or archive process
without compression enabled.
ANS1226E
Destination file or directory is write

locked

updated.
or location.
ANS1227E
Processing stopped; Disk full condition
ANS1230E
Stale NFS File Handle

ANS1231E
No file handles available

ANS1232E
The file exists and cannot be

overwritten.

Explanation: The file being restored or retrieved exists

and cannot be overwritten due to lack of authority or
access permissions.
System action: The file is skipped.

User response: Verify that you have sufficient access

permissions to overwrite the file, then try the operation
684
ANS1233E ANS1243E
again. If the problem persists, contact your system
administrator or TSM administrator for further
assistance.
ANS1233E
An invalid file handle was passed;

system error.
Explanation: An internal system error occurred: A file

operation failed because of an invalid file handle.
User response: Try the operation again. If the failure
persists, obtain a service trace that captures the
problem and contact IBM technical support for
additional assistance. Your TSM administrator can help
you configure the trace.
ANS1237E
Explanation: The TSM client error log and the TSM

server activity log might contain additional information
about this error.
persists, examine the TSM client error log and TSM
server activity log for additional information about this
error. If the problem cannot be resolved, then obtain a
SERVICE trace that captures the problem and contact
IBM technical support for additional assistance. Your
TSM administrator can help you configure the trace.
ANS1238S
ANS1234E
A problem has occurred on the TSM

server.
Protocol violation
A policy management problem has

occurred on the TSM server.
Explanation: A communications protocol error

occurred. The communication subsystem is not
properly defined or is itself in error.
Explanation: The TSM client error log and TSM server

activity log may contain additional information about
this error.
System action: Processing is stops.
User response: Verify that the communication

processes are operating properly, and then retry the
operation.

ANS1235E
An unknown system error has occurred

from which TSM cannot recover.

be a low-level system or communication error from
which TSM cannot recover.
ANS1241E

operation.

persists, review the TSM error log for any related
messages. Obtain a service trace that captures the
ANS1236E
An unexpected error occurred.
File is in use; Write permission denied.

ANS1242E
Too many symbolic links were detected

while resolving name
Explanation: This is usually caused by a low-level

system error or communication error from which TSM
cannot recover.


additional messages that might be related to this
problem. Try the operation again. If the problem
persists, contact TSM technical support for further
assistance.

ANS1243E
The file name is too long and can not be

processed by TSM
Explanation: None.
User response: See the client manual for the operating
685
ANS1244E ANS1256E
system on which you are receiving this error. The File
specification syntax section of the manual explains file
name lengths supported by TSM.
ANS1244E
File system is locked by system

System action: TSM cannot complete the operation.
ANS1245E

User response: The file was either backed up by
another application, or the data is invalid. If the file
belongs to this system, try the operation again. If the
problem persists, contact IBM technical support for
further assistance.
A command-line argument exceeded the
maximum length (maximum length) for a
single token.
Explanation: Command-line arguments may not

exceed maximum length characters.
User response: Correct the command and retry the
operation.
ANS1247I
Server cannot restart the last restore

request. Do you want to restore without
restart or abort the request?
Explanation: The restart restore token has expired.

The server cannot restart the restore from where it last
ended.
System action: Processing stopped; waiting for user
intervention.
User response: Retry the request without restart or
abort the request.
The file has an unknown format.
Explanation: TSM tried to restore or retrieve a file, but

it had an unknown format.
ANS1246E
ANS1249W
Waiting for files from the server...
Explanation: Restore request has been sent to the

server. The wait time depends on how many files you
are restoring.
System action: TSM waits for files to restore from the
server.
ANS1251E
File system/drive not ready

access.
TSM, and then retry the operation.
ANS1253E
File input/output error

System action: File or file system is skipped.
ANS1254E
File write error

file.
operating properly.
ANS1255E
File exceeds system/user file limits
Explanation: A file being restored or retrieved exceeds

system set limits for this user.
ANS1248E
An active restore for the same source

file specification exists. Unable to
continue with this request.
Explanation: Currently, there is an active restore for

the same source file specification. Another restore of the
same source file specification cannot be started.

properly.
ANS1256E
Cannot make file/directory
System action: The requested restore fails.

User response: Start another restore with a different

source file specification.

restored or retrieved. Make sure that you have write
access.
686
ANS1257E ANS1265E
ANS1257E
An error occurred while preparing the

system object for restore.
Explanation: This message is typically issued when

the client is unable to delete the ADSM.SYS staging
directory in preparation for restoring the system object.
description option is ignored.

User response: None. Specify at least one character in
the description
ANS1262I
System action: The system object is not restored.

messages that might indicate a reason for the failure,
correct any indicated problems, then try the operation
again. If the problem occurs again, manually delete the
ADSM.SYS directory, then try the operation again. If
the problem cannot be resolved, contact IBM technical
support for further assistance.
ANS1258E
The image snapshot operation failed.
Password is not updated. Either an

invalid current password was supplied
or the new password does not fulfill the
server password requirements.
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
server.
Explanation: TSM was not able to take a snapshot of

User response: Enter another password.
ANS1263E

ANS1259E

Diagnostic text: .
Explanation: An error was encountered during image

backup snapshot processing. The diagnostic text can
vary, depending on the error.
The active policy set does not contain

any backup copy groups. The backup
operation can not continue.
Explanation: In order to back up files, the policy set

must contain at last one backup copy group.
System action: TSM did not backup the file.
User response: The TSM administrator needs to
update or define at least one management class in your
policy set that contains a backup copy group, or else
assign you to a different policy domain that contains at
least one backup copy group. Contact your TSM

additional messages that might indicate the reason for
the problem. Take any corrective action suggested by
the messages, then try the operation again. If the
further assistance.
ANS1260E
File is being recalled or has been

recalled.
Explanation: The file is being recalled by another

process or has been recalled.
User response: None
ANS1261W
The archive description you specified is

the empty string. TSM will use the
default description (Archive Date:
current date).
Explanation: The description option on the archive

command may not specify a null string.
System action: Processing continues, and the
ANS1264E
The active policy set does not contain

any archive copy group. The archive
operation cannot continue.
Explanation: In order to archive files, the policy set

must contain at least one archive copy group.
System action: TSM did not archive the file.
User response: The TSM administrator needs to
update or define at least one management class in your
policy set that contains an archive copy group, or else
assign you to a different policy domain that contains at
least one archive copy group. Contact your TSM
ANS1265E
Encountered bad mount or filesystem,

processing stopped.
Explanation: The getmnt system call returned an error

indication. Error was encountered trying to determine
what the mounted file systems are.
System action: Processing stopped. Cannot recover.
User response: There is a bad file system or mount
point on your system. Look at file systems and mounts,
687
ANS1266E ANS1273E
and correct any errors. If unsuccessful, see your system
administrator for more information.
ENABLESERVERFREE option from the system option

file, or set COMPRESSION off in the option file.
ANS1266E
ANS1271E
Encountered bad mount or filesystem,

processing stopped.
Explanation: An error was encountered trying to

determine what the mounted file systems are.
System action: Processing stopped. Cannot recover.
User response: Please, see your system administrator
ANS1267E
The management class for file file-name

does not allow migration. This file will
not be migrated.

not allow migration
User response: Either have the TSM administrator
change the Space Management Technique within the
management class to a value other than NONE or
change the include/exclude list to specify a
management class with the appropriate Space
Management Technique value.
ANS1268E
This file has been migrated.
Explanation: File has been migrated. If files that are

hard linked together are migrated then files subsequent
to the first one encountered get this.
Explanation: The compressed file cannot be expanded

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

ANS1269I
File is implicitly excluded.
Explanation: You tried to back up or migrate a file

that is implicitly excluded.
System action: TSM will not back up or migrate an
implicitly excluded file.
ANS1270I
Forcing compression off to enable future

server-free restore.
Explanation: Because ENABLESERVERFREE had been

specified, and an attempted server-free data movement
fell back to non-server-free, the TSM client is forcing
compression off. This is to enable future server-free
restore of the object backed up, when the problems
preventing a server-free backup from occurring have
been resolved.
System action: The operation continues without
compression.
User response: Either Remove the
688
The compressed file is corrupted and

cannot be expanded correctly.
Adaptive subfile backup has been

configured on the client but the server
doesnt allow this type of backup.
Adaptive subfile backup will not be
used for this operation.
Explanation: Adaptive subfile backup forced off by

the server.
User response: Set up the server to allow clients to
back up subfiles.
ANS1273E
The image plugin was not able to

acquire an exclusive lock on volume:
Explanation: To perform an off-line image backup or

an image restore TSM requires exclusive use of the
volume.
User response: Please verify that no other application
is accessing the volume. If this volume is being
accessed by applications that can not be shutdown
during backup then perform an online image backup
(snapshot with LVSA) instead. During restore of an
image TSM must have exclusive use of the volume.
ANS1274E ANS1289W
ANS1274E
Error Loading WINSOCK.DLL
Explanation: Error loading the Windows socket

support file into memory. This error only applies when
using TCP/IP communications.
User response: Delete the virtual mount point.

ANS1279W
Virtual mount point filespace-name

cannot be used in a file system handled
by automounter and is ignored.
User response: Because this error is caused by

insufficient memory, shut down running applications
and retry. If the problem persists, see your system
administrator.
Explanation: Virtual mount points cannot be used in a

file system handled by automounter. If virtual mount
points reside in a file system that is processed from an
automounter, the backed up files underneath the
virtual mount points will be expired when the file
system is unmounted.
ANS1275E
System action: The virtual mount point is ignored.
Error Loading Function(s) from

WINSOCK.DLL
Explanation: Error loading one or more functions

from the Windows socket support file.
User response: Delete the virtual mount point.

ANS1286E

User response: Since this might possibly be caused by
insufficient memory, shut down running applications
and retry. If the problem persists, see your system
administrator.
ANS1276I
\Log on as a service\ right granted to

account
Explanation: You specified a Windows user account

which did not have the security right to run as a
service
System action: TSM granted the log on as a service
right to the account you specified.
User response: No action required.
ANS1277E
Error occurred while granting \log on

as a service\ right to account
Explanation: You specified a Windows user account

which did not have the security right to run as a
service. TSM encountered a problem attempting to
grant this right automatically.
System action: The log on as a service right is not
granted to the account specified.
User response: Insure the account from which you are
configuring the service has authority to grant rights
and retry the request. Alternatively run the Windows
policy editor from an administrative account to grant
the log on as a service right to the account that is
associated with the service you are configuring.
Explanation: User issued a NAS related command and

NASNodename option is missing.
System action: Operation aborted.
User response: Use -nasnodename option with the
command or place nasnodename option in the option
file.
ANS1287E
Virtual mount point filespace-name is a

file system. It will be backed up as a
file system.
Explanation: A virtual mount point that is a file

system is invalid and should be deleted.
System action: The virtual mount point is ignored.
Volume could not be locked.
Explanation: The system call to lock the volume

failed.
User response: Please verify that no other application
is accessing the volume. If this volume is being
accessed by applications that can not be shutdown
during backup then perform an online image backup
(snapshot with LVSA) instead. During restore of an
image TSM must have exclusive use of the volume.
ANS1288E
The (-TYPE) option is required with the

SET EVENT command.
Explanation: There is no default value for the -TYPE

option. It must be explicitly entered with the command.
System action: Current command ends.
User response: Enter the SET EVENT command again
with the TYPE option and a value of HOLD, RELEASE,
or ACTIVATERETENTION.
ANS1289W
ANS1278W
-nasnodename option required for this

operation.
Bad areas on volume between sectors

hi:lo and hi:lo
Explanation: Some bad sectors within the specified

range were detected on the volume during image
operation.
User response: Make sure the volume data is not
689
ANS1300E ANS1307E
corrupt by using system tools like chkdsk (Windows)
or fsck (UNIX).
ANS1300E
File cannot be reconstructed because a

necessary component was not restored.
Explanation: The subfile backup technique was used

to back up this file. During the restore, a portion of the
file could not be obtained from the server.
System action: The file indicated in the message is not
restored. Restore for all other files continues.
User response: Try to restore the file again by
selecting the file for restore from the user interface. If
this doesnt resolve the problem, check the client error
log and the server activity log for any messages related
to the file indicated in the message.
ANS1301E
Server detected system error
Explanation: The server detected a system error and

notified the clients.
User response: See your system administrator for
further information on server activity.
ANS1302E
No objects on server match query
Explanation: No objects on the server match the query

operation being performed. If this object is part of a
backupset generated on a node, and the node name is
changed on the server, any backup set objects that were
generated prior to the name change will not match the
new node name.
User response: Ensure the names are properly
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
was generated.
ANS1303E
Client ended transaction
Explanation: The client system ended the operation

with the server and ended the current transaction.
system at the same time. If one of the processes expires

a file, then the TSM server will make that file inactive.
If the second process subsequently attempts to expire
that same file, the TSM server will not find an active
version of the file, so the second process will issue this
message for that file.
System action: The object is not expired. Processing
continues with the next object.
User response:
v Review the console output, schedule log, or error log
and locate the ANS1228E message that immediately
precedes this message. ANS1228E will identify the
object that could not be expired.
v Examine the conditions under which the problem
occurred and assess whether those conditions explain
the occurrence of this message. For example, this
message could appear if multiple instances of the
client were attempting to back up the file system
concurrently.
v If the reason this message occurred can not be
determined and the message occurs when the
operation is tried again, then contact IBM support for
further assistance. Also try searching for this message
number on http://www.ibm.com for possible
solutions.
ANS1305E
The TSM server has no data for the

object.
Explanation: TSM tried to do a restore or retrieve on

an object that has no data associated with it. If a
corrective action is possible, it is with the TSM server.
System action: TSM ends the current operation.
User response: Ask the TSM administrator to check
the TSM activity log for any messages related to this
error that might help identify the problem.
ANS1306E
You entered an incorrect password.
Explanation: None.
User response: Retry the session with the correct
password. If this fails or you have forgotten your
password, ask the TSM administrator to assign a new
password.
User response: Restart the session.

ANS1307E
ANS1304W
An active backup version could not be

found.
Explanation: An attempt was made to expire an

object, but the TSM server was unable to find an active
backup version of the object. This message is preceded
by message ANS1228E which specifies the object name.
For instance, this message could be issued if two
separate client processes are backing up the same file
690
Node in use
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: Retry the operation, or see your
system administrator to see what other operations are
running for your node.
ANS1308E ANS1315W
ANS1308E
Expiration date must be greater than

todays date
ANS1312E
Server media mount not possible
Explanation: Archive expiration date is too low, the

date must be greater than todays date.
Explanation: Server media mount not possible. The

server timed out waiting for a mount of an offline
volume.
User response: Retry archiving the file with an

expiration date that is higher than todays date.
User response: Retry later when server volumes can

be mounted. Ensure that the MAXNUMMP (maximum
number of mount points) defined on the server for this
node is greater than 0.
ANS1309I
The requested data is offline.
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
depends on your sites offline storage management
policies.
System action: TSM waits for offline storage media to
become available and then continues.
ANS1310E
Object too large for server limits
Explanation: The object is too large. The configuration

of the server does not have any data storage space that
accepts the object.
ANS1313E
Size estimate exceeded
Explanation: The total amount of data for a backup or

archive operation exceeds the estimated size originally
sent to the server for allocating data storage space. This
happens when many files are growing by large
amounts while the backup or archive operation is in
session.
continues, check what other processes are running on
the client machine that are generating large amounts of
data. Disable those operations while the backup or
archive operation is taking place.

determine the maximum file (object) size for which
your sites server is configured.
ANS1311E
Server out of data storage space
Explanation: The server does not have any space

available to store the object.
User response: You can take any of the following
actions:
v Request the system administrator to add space to the
storage pool.
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
during compression.
v For API Applications, consult the applications
documentation for recommendations regarding
compression.
v Turn off disk caching in the disk storage pool, and
issue MOVE DATA commands to each disk pool
volume to clear out the cached bitfiles.
ANS1314E
File data currently unavailable on server
Explanation: The file data is currently unavailable on

the server. A retrieve or restore operation was
attempted. Possible causes are:
v Data was corrupted at the server
v Server found a read error
v File is temporarily involved in a reclaim operation at
the server
v Server requested a tape volume that was marked
unavailable.
continues, see your system administrator to determine
the problem from the server console or the activity log.
Check whether any requests were made for a tape
volume that was unavailable. A tape volume may be
marked unavailable if prior read errors were
encountered or the volume is checked out of the tape
library.
ANS1315W
Unexpected retry request. The server

found an error while writing the data.
Explanation: None.
System action: The client retries the operation.
691
ANS1316E ANS1327W
ANS1316E
The server does not have enough

recovery log space to continue the
current operation
Explanation: The server ran out of recovery log space.

User response: This error is a temporary problem.
Retry later or see your system administrator.
ANS1317E

database space to continue the current
operation
Explanation: The server ran out of database space.

ANS1321S
Open Registration failed because the

specified node name is defined in the
server
Explanation: Open registration failed because a node

is defined in the server with the same name.
User response: Retry with another node name.
ANS1322S
Open Registration failed because no

default domain exists
Explanation: Open registration failed because a

default policy domain does not exist for you to place
your node.
ANS1318E

memory to continue the current
operation.
Explanation: The server ran out of memory.

User response: This is a temporary problem. Retry
later or see your system administrator.
ANS1319E
An error occurred on the TSM server

while trying to rename file space
ANS1323S
Explanation: Open registration failed because the

specified node name contains invalid characters.
User response: Retry with another node name that
does not have any invalid characters.
ANS1326S
Explanation: None.
System action: Because the file space cannot be
renamed, the operation stops.
User response: Check the client error log and the TSM
server activity log for any other messages that might
help identify the problem. If the problem cannot be
resolved, contact IBM technical support for additional
assistance.
ANS1320E
The specified file space does not exist

on the server. The file space might have
been deleted by another client or an
administrator.
Explanation: The specified file space does not exist on

the server. Your system administrator deleted the file
space or another client using your clients node name
deleted it.
Open Registration failed because an

invalid node name was specified
The TSM server does not currently have

space in the storage pool for this file.
This may be a temporary condition.

the storage pool in which the data is being placed does
not have sufficient space to store the data, but the
space will be available soon. For example, a storage
pool migration might free up sufficient space to store
the data.
User response: Try the operation at a later time. If this
fails, contact the TSM administrator and request more
storage pool space.
ANS1327W
The snapshot operation for volname

failed with error code: retcode.
Explanation: A snapshot could not be taken of the

specified volume.
System action: Snapshot processing stopped.
User response: Check the file space name to see if it is

correct, and retry the operation.
User response: Check the client error log for any other
messages that might help identify the problem. If the
problem cannot be resolved, contact IBM technical
support for additional assistance.
692
ANS1328W ANS1334W
ANS1328W
An error occurred generating delta file

for file-name. The return code is retcode.
ANS1331E
Only a TSM authorized user can

perform this Action.
Explanation: An error occurred that prevented the

creation of the delta file. Possible reasons for this error
include:
Explanation: User must be a TSM authorized user to

perform this action. User is not password authorized
and this action requires authorization.
v The base file cannot be opened for reading
v The file being backed up cannot be opened for

reading
v The delta file cannot be opened for writing
v The file being backed up has grown to a size larger
than 2 GB
v A memory file mapping of the file cannot be created
User response: User must be root user, or user must

be the owner of the executable and the set effective
user id bit is set to on (s bit).
ANS1332E
Run the ... for Administrators version

of the application.
System action: A full backup of the file is made, and a

new version of the reference file is stored in the subfile
cache.
Explanation: The user must be root or a system

administrator and use the provided authorization tools
to start IBM Tivoli Storage Manager
User response: If the message indicates return code

4504, check the delta subfile cache directory for any
residual delta files. The delta subfile cache directory is
specified by the client option SUBFILECACHEPATH.
Search the directory for files named \.dXXXXXXXX\
where \XXXXXXXX\ is an eight-digit number. If
there are no backup operations in progress, there
should not be any files in the SUBFILECACHEPATH
with this name. If there are no backup operations in
progress and these files exist, they can safely be
removed. If you continue to receive this message but
there are no residual delta files in the subfile cache
directory and the file has not grown to a size larger
than 2 GB, then contact IBM technical support for
further assistance.
System action: IBM Tivoli Storage Manager

terminates.
ANS1329S
Explanation: The server does not have space available

to store the object.
User response: Report to your system administrator
that a storage pool on the server is full.
ANS1330S
This node currently has a pending

restartable restore session. The
requested operation cannot complete
until this session either completes or is
canceled.
Explanation: This operation can not be completed

because a restartable restore session is pending. The
operation is not allowed because the restartable session
and the current operation affect the same file space.
User response: Issue a query restore to see the
conflict. Issue the cancel restore command to delete any
unneeded restartable restore sessions.
User response: The user must login as the root user or

be a system administrator and use one of the following
authorization tools to start IBM Tivoli Storage Manager:
v TSM Backup for Administrators
v TSM Scheduler for Administrators
v TSM Scheduler Daemon for Administrators
ANS1333I
Used block list used for the snapshot

image backup of is different than list
acquired before the start of snapshot.
Explanation: The snapshot image backup used block

list is taken before and after the start of the snapshot
for informational purposes.
ANS1334W
Volume mount point filespace

namepath-namedir-name was not restored
because the target directory is not
empty.
Explanation: Volume mount points can only be

restored if the target directory does not already exist, or
if the target directory exists but is empty. If the target
directory exists and is not empty, or already is a
junction point, then the volume mount point cannot be
restored. On Windows Vista, it is normal to see these
warnings during system drive restore as there are
many junction points that point to the
%systemroot%\Users folder.
System action: The volume mount point is not
restored. Processing continues with the next object.
User response: Correct the conflict with the
non-empty directory, then try the operation again. This
is especially important when this message is issued for
a volume mount point that resides in the SYSVOL,
693
ANS1335E ANS1345E
since an incomplete SYSVOL restore can result in
system stability problems. See the reference information
for the RESTORE command in the client manual for
additional information about restoring volume mount
points.
ANS1335E
The RSM database files could not be

restored.
Explanation: None.
System action: The RSM database is not restored.
Otherwise, processing continues.
messages that might help identify the problem. Reboot
the system, then try the RSM restore operation again. If
the problem cannot be resolved, contact IBM technical
ANS1336I
RSM service must be restarted for

changes to become effective.
Explanation: RSM database files have been restored

from the server and imported. The RSM service must
be restarted for the updates to become effective.
ANS1340E
Explanation: An error occurred while backing up the

RSM database files. The database will not be backed
up.
messages that might help identify the problem. Try the
ANS1341E
Restarting the RSM service...

from the server and imported. TSM is about to stop
then restart the RSM service.
An invalid character appears in the

operand: operand.
Explanation: The operand contains a character that is

not valid in the current locale and code page. It cannot
be translated to its internal wide-character format.
User response: Change the locale of the workstation
to match the language in which the operand is
recorded, and try the command again.
ANS1342E

ANS1337I
An error occurred while backing up the

RSM database.
Client cache is locked; unable to

continue with operation.
Explanation: The client cache is currently locked by

another process.
User response: Report the program error to your

ANS1338I
Restart of the RSM service is completed.

from the server and imported. TSM has restarted the
RSM service on the users behalf.
ANS1344E
Job is running in the background.

Cannot prompt for the Key.
Explanation: When jobs are run in the background,

the client cannot prompt for the key.
User response: Run the Job in the foreground.

ANS1339E
Restart of the RSM service failed.

Restart the RSM service manually.

from the TSM server and imported. TSM has tried to
restart the RSM service on the users behalf but has run
into a problem.
User response: Restart the RSM service manually.
694
ANS1345E
No objects on server match

object-nameobject-nameobject-name
Explanation: The specified file (object-name) does not

have a match on the server.
User response: Backup the file and retry the
operation. If the problem continues, see your system
administrator to isolate the problem through use of the
server console.
ANS1346E ANS1352E
ANS1346E

The SNAPSHOTCACHELocation does
not contain enough space for this
snapshot image backup.

the specified volume. The SNAPSHOTCACHELocation
points to a location which does not contain the space
necessary to manage the snapshot. This could be due to
an unexpected amount of disk activity which is
generating more changes than can be contained in the
available space at this particular point in time, or the
SNAPSHOTCACHELocation needs to be changed
because the specified location is not large enough to
handle the usual amount of changes to the volume.
Another reason for this failure can be that the specified
SNAPSHOTCACHESize is not set to a large enough
value to handle the usual amount of changes to the
volume during snapshot image backup.
User response: If the problem persists please increase
the SNAPSHOTCACHESize and/or change the value
of the SNAPSHOTCACHELocation.
ANS1347E

The percent of space to use, specified
via the SNAPSHOTCACHESize, has
been exceeded.
the SNAPSHOTFSIDLEWait and

SNAPSHOTFSIDLERetries options to better fit the
normal disk write activity of the volume being backed
up.
ANS1349E
An error occurred during Logical

Volume Snapshot Agent snapshot
processing.
Explanation: An unrecoverable error occurred during

snapshot processing. This can be caused by a variety of
errors, so the error and system event logs should be
checked for additional messages.
User response: Check the client error log and the
system event log for any other messages that might
help identify the problem. Try the operation again. If
further assistance.
ANS1350E
The logical volume snapshot agent

(LVSA) is currently busy performing a
snapshot on this same volume.
Explanation: Another IBM Tivoli Storage Manager

process is already performing a snapshot of this
volume.
System action: The operation is stopped.

the specified volume. The percent of space allotted via
the SNAPSHOTCACHESize option was not enough to
perform this snapshot image backup. This could be due
to an unexpected amount of disk activity which is
generating more changes than can be contained in the
allotted space at this particular point in time. Another
reason for this failure can be that the specified
SNAPSHOTCACHESize is not set to a large enough
value to handle the usual amount of changes to the
volume during snapshot image backup.
User response: Please wait until the other IBM Tivoli

Storage Manager process finishes with the volume and

continues, see your system administrator to increase the
number of concurrently active sessions to the server.
User response: If the problem persists please increase

the SNAPSHOTCACHESize or, for Windows, change
the value of the SNAPSHOTCACHELocation.
ANS1348E
Unable to satisfy the

SNAPSHOTFSIDLEWait and
SNAPSHOTFSIDLERetries options due
to volume write activity.

the specified volume. The Logical Volume Snapshot
Agent was not able to satisfy the
SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries
options before starting the snapshot of the specified
volume.
ANS1351E
Session rejected: All server sessions are

currently in use
Explanation: TSM has all available sessions in use and

cannot accept a new one at this time.
ANS1352E
The session is rejected. Your password

has expired.
Explanation: Your TSM password has expired.

You are not allowed to connect to the server until the
password is updated.
User response: Update your password. You may use
the SET PASSWORD command, or have the TSM
administrator update your node.

User response: If the problem persists please modify
695
ANS1353E ANS1362S
ANS1353E
Session rejected: Unknown or incorrect

ID entered
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
to access a migrated file, your node name must be the
same node which migrated the file.
User response: See your system administrator to see

what version of TSM to run for your location.
ANS1358S
Session rejected: Downlevel server code

version
Explanation: The server version and your client

version do not match. The server code is downlevel.
User response: Ensure that you entered your TSM

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
the server.
ANS1359E
ANS1354E
Session rejected: Duplicate ID entered
Explanation: Another process using this node name is

active with the server.
System action: TSM cannot connect to the server. TSM
canceled the current operation.
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
node name is unique to the server so that it cannot be
used by another person. See your system administrator
to identify the owner of that node name.
ANS1355E
Session rejected: Server disabled
Explanation: The server is in a disabled state and

cannot be accessed for normal activity.
User response: Retry the operation after the server
returns to an enabled state. If the problem continues,
see your system administrator.
ANS1356E
The server is not configured to allow

open registration
Session Rejected: The specified node

name is currently in use
Explanation: The node name you specified is in use

on the server.
User response: The server is probably performing a

task that prevents your node from establishing a
session. Retry later or check with your system
administrator.
ANS1360I
Compressed Data Grew
Explanation: The size of the file after compression is

greater than the size of the file before compressed.
System action: Even though the size of the file
increased, the file is compressed.
ANS1361E
Session Rejected: The specified node

name is currently locked
Explanation: The node name you specified is currently

to find out why your node name is locked.
Explanation: No authorization. Registration is

required by your system administrator. The server is
not configured to allow open registration.
ANS1362S
System action: Session not started.
Explanation: Adding a new enrollment will exceed the

product license count for TSM.
User response: You must obtain a TSM node and

password from your system administrator.
ANS1357S
Session rejected: Downlevel client code

version

version do not match. The client code is downlevel.
696
SLM LICENSE EXCEEDED: The client

licenses for TSM are exceeded. See your
System action: Execution of the client enrollment or

connection request ends.
ANS1363E ANS1373W
ANS1363E
Session Rejected: The server does not

have enough memory to allow a
connection to be established.
Explanation: The server does not have enough

memory to allow your client to establish a connection
with the server.
User response: Retry later or see your system
administrator.
ANS1364E

have enough recovery log space to allow
a connection to be established.

ANS1369E
Explanation: The server administrator canceled the

current client session.
System action: Execution of the client connection
request ends.
ANS1370E

Session Rejected: The session was

canceled by the server administrator.
The user ID entered does not have the

correct level of authority to access the
client machine.
Explanation: The user ID entered cannot access this

TSM client.
System action: The TSM operation ends.
ANS1365E

have enough database space to allow a
connection to be established.
User response: Grant authority to this user ID on the

TSM server so that it can access this TSM client.
ANS1371E
File cannot be reconstructed from

subfile components.
Explanation: An error occurred while reconstructing

this file from its subfile components.
ANS1366E
System action: The file indicated in the message is not

restored. Restore for all other files continues.
The session is rejected. The TSM server

has an internal error.

to the TSM server because of an internal server error.
System action: The session was not started.
User response: Notify your TSM administrator of this
error.
User response: Try to restore the file again by

selecting the file for restore from the user interface. If
this doesnt resolve the problem, check the client error
log and the server activity log for any messages related
to the file indicated in the message.
ANS1372E
ANS1367E
The client is unable to sign on to the

TSM server because the server does not
allow sign-on of Unicode clients.
Explanation: The client is not allowed to connect to

the TSM server.
System action: The session does not start.
User response: Contact your TSM administrator for
assistance in configuring a working TSM client for your
environment.
ANS1368S
Session Rejected: The server is not

licensed for this platform type. See your
Explanation: The server is not licensed for the

requesting client type.
An inconsistency was detected between

the client node and the node that is
registered to the TSM server.
Explanation: The user has probably coded the node

option incorrectly. For instance, the node that is
registered to the TSM server might be a type of NAS,
but the node is actually a non-NAS client.
User response: Ensure that the node name is correct
in the client options file. Make sure to use a node of
type NAS only with the nasnodename option.
ANS1373W
The PRESNAPSHOTCMD command

failed.

PRESNAPSHOTCMD option must complete
successfully in order to perform the snapshot
backup/archive operation. If the command completed
697
ANS1374W ANS1379E
with a return code of 0 (zero), it has completed
successfully. If the command completed with any other
return code, it has failed. If the command failed, then
the backup is still performed, but without the benefit of
the snapshot technology.
System action: The client executes the backup/archive
operation, but without using a snapshot.
User response: Identify and fix the problem that
code of zero.
ANS1374W
The POSTSNAPSHOTCMD command

completed with a non-zero return code.

POSTSNAPSHOTCMD option completed with a
non-zero return code, then the snapshot operation will
continue, but with a warning-level result. Note that the
result of the POSTSNAPSHOTCMD command will not
supercede a higher result from the backup/archive
command. For example, if the backup command
completed with a return code of 12, the backup will be
considered to have completed with a return code of 12,
regardless of the outcome of the POSTSNAPSHOTCMD
command.
System action: The backup/archive operation
continues, but with a warning return code of at least 8.
code of zero.
ANS1375E
The snapshot operation failed.
Explanation: The client was unable to take a snapshot

of the volume.
System action: Snapshot processing stopped.
ANS1376W
The client was unable to obtain a

snapshot of the file system. The
operation will continue without
snapshot support.
Explanation: None.
System action: The operation continues without
snapshot support.
698

ANS1377W
The client was unable to obtain a

snapshot of volname. The operation will
Explanation: TSM client was unable to create a

snapshot of the volume due to some reason. Instead of
failing the operation, TSM client will perform a
non-snapshot based backup.
System action: Snapshot processing stops.
ANS1378E
The snapshot operation failed. The

SNAPSHOTCACHELocation does not
contain enough space for this snapshot
operation.
Explanation: IBM Tivoli Storage Manager was not able

to take a snapshot of the specified volume. The
SNAPSHOTCACHELocation points to a location which
does not contain the space necessary to manage the
snapshot. Reasons for failure include:
v An unexpected amount of disk activity which is
generating more changes than can be contained in
the available space at this particular point in time.
v The SNAPSHOTCACHELocation is not large enough
to handle the usual amount of changes to the
volume.
v The specified SNAPSHOTCACHESize is not set to a
large enough value to handle the usual amount of
changes to the volume during snapshot backup or
archive operation.
User response: If the problem persists, increase the
SNAPSHOTCACHESize or change the value of the
SNAPSHOTCACHELocation.
ANS1379E

percent of space to use for the
SNAPSHOTCACHELocation, specified
via the SNAPSHOTCACHESize, has
been exceeded.

to take a snapshot of the specified volume. The percent
of space allotted via the SNAPSHOTCACHESize option
was not enough to perform this snapshot
backup/archive operation. Reasons for failure include:
v The SNAPSHOTCACHELocation is not large enough
to handle the usual amount of changes to the
volume.
ANS1380W ANS1387E
v The specified SNAPSHOTCACHESize is not set to a
large enough value to handle the usual amount of
changes to the volume during snapshot backup or
archive operation.
User response: If the problem persists, increase the
SNAPSHOTCACHESize or change the value of the
SNAPSHOTCACHELocation.
ANS1380W

filesystem write activity prevented the
Logical Volume Snapshot Agent from
satisfying the SNAPSHOTFSIDLEWait
and SNAPSHOTFSIDLERetries options.

to take a snapshot of the specified volume. The Logical
Volume Snapshot Agent was not able to satisfy the
options before starting the snapshot of the specified
volume.
the SESSIONINITIATION option and run the client

scheduler.
ANS1383E
Wrong server port.
Explanation: You were trying to open a

backup/archive client session on the server port set up
for administrative sessions only.
System action: The IBM Tivoli Storage Manager
operation ends.
User response: Contact your systems administrator
and/or use the correct values for TCP port and TCP
Admin Port.
ANS1384E
An object in the transaction has been

bound to an invalid management class.
Explanation: One of the objects in the transaction is

bound to a management class that is not part of this
nodes policy, or the management class type is not
supported for this client level.
System action: The current operation ends.
User response: If the problem persists, modify the

options to better fit the normal disk write activity of
the volume being backed up.
User response: Make sure all objects are bound to a

valid management class, or upgrade the client to the
proper level.
ANS1385E
ANS1381W
On volumes that are RAW or formatted

FAT32 the snapshot cache location
cannot be located on the same volume
that is being backed up.
Explanation: When the snapshot cache location is

located on the same volume that is being backed up the
volume must be formatted with NTFS. The default
cache location is on the same volume where the
snapshot operation.
location, using the SNAPSHOTCACHELOCATION
option.
ANS1382E
Server does not allow client-initiated

connections for this node.
Explanation: The node is not allowed to initiate

connections due to the configuration parameters for
this node on the server. Server is able to initiate
connections to the client scheduler running in
prompted mode.
operation ends.
User response: Contact your systems administrator to
enable client-initiated sessions for your node or update
This server does not support backup

operations.
Explanation: This server only supports archive

operations, backup is not allowed.
System action: Current operation ends.
User response: Use only archive operations with this
server.
ANS1386E
Deleting this object: fshlll is not

allowed.
Explanation: The object is either under a hold and

cannot be deleted, or it is on a retention-protection
enabled server and has not expired.
System action: The object is skipped and processing
continues.
User response: Check the status of the object through
a query to see if it is held, or when it expires.
ANS1387E
The number of objects in this

transaction exceed TXNGROUPMAX
values.
Explanation: There are too many objects in this

transaction.
User response: Try the operation again with fewer
objects in the transaction, or increase the
699
ANS1388E ANS1395E
TXNGROUPMAX value on the server.
ANS1388E
fshlll is already under hold.
Explanation: The specified object is already under

hold, and it cannot be placed under a new hold.
User response: Contact your system administrator so

the permissions can be corrected. A System
Administrator should use the TSM Backup for
Administrators application to update the permissions.
ANS1392W
System action: This object is skipped and processing

continues.
User response: Issue a query to see the status of the
objects, and try the operation again, without the object
that is already held.
ANS1389W
Invalid option (option) for the scheduled

function command
Explanation: There are two possible reasons for this

message:
v The option option was specified for a scheduled
command or subcommand (function) that cannot
make use of that option.
v The option appears on a scheduled command but is
valid only on the client scheduler initial command
line, not on commands in a schedule from the server.
System action: The option is ignored.
User response: See the Backup-Archive Client
Installation and Users Guide for correct use of the named
option. The system administrator should remove the
invalid option from the schedule definition on the
server.
ANS1390I
A TSM authorized user must configure

the TSM client acceptor daemon and the
TSM client scheduler.
Explanation: The installation of the TSM client

acceptor daemon requires access to system locations,
which require full access to the system. The TSM client
acceptor daemon is installed as a startup item in
/Library/StartupItems, and a link is added to /usr/bin
for the dsmcad tool.
System action: The setup assistant cannot be used to
configure the IBM Tivoli Storage Manager scheduler or
the TSM client acceptor daemon.
User response: To acquire this access, system
administrators must use the TSM Backup for
Administrators application.
ANS1391W
The TCA file permissions are not

correct.
Explanation: The TCA is a tool used by TSM to

provide secure access to the password file for
non-administrators. If the permissions are not set
correctly, and PASSWORDACCESS GENERATE is set,
TSM cannot be used.
700
The TCA file permissions are not

correct. Would you like to update the
permissions?
Explanation: The TCA is a tool used by TSM to

provide secure access to the password file for
non-administrators. If the permissions are not set
correctly, TSM cannot be used. The dsmtca application
needs to be owned by root and have 4755 permissions.
System action: If you select yes, TSM will set the
owner of the TCA to root and the permissions to 4755.
If you select no, the permissions will not be changed.
In either case, processing continues.
User response: Select yes when you are prompted so
TSM can repair the permissions of the file. If you select
no, PASSWORDACCESS GENERATE will not work for
non-TSM Authorized users.
ANS1393W
The command line tools are not

installed. The command line tools
include the TSM client acceptor daemon
and the TSM client scheduler.
Explanation: The command line tools are required for

the IBM Tivoli Storage Manager scheduler. The
dsmcad application or the put in
/Library/Startupitems folder could not be located.
System action: The setup assistant cannot be used to
configure the IBM Tivoli Storage Manager scheduler.
User response: A System Administrator must reinstall
IBM Tivoli Storage Manager the command line tools.
ANS1394E
The node name contains periods. Would

you like to remove them? Select no if
this is an existing node name.
Explanation: A node name with periods complicates

the management of the node.
System action: IBM Tivoli Storage Manager prompts
to remove the periods.
User response: Respond to the prompt. If this is a
new node, select yes, so the node is created without
the periods in the name. For existing nodes, select no,
so the node name is not changed.
ANS1395E
The destination filespace or drive letter

is unavailable. The following object was
not processed: Filespace:filespace-name
Explanation: The system is trying to restore or retrieve

to a destination that cannot be reached. The specified
filespace name or drive letter is not valid, or does not
ANS1396E ANS1402W
exist, or you are specifying a local share name that
cannot be resolved.
System action: Objects which are part of this filespace
are not processed.
ANS1399W
The logical volume snapshot agent

(LVSA) is currently busy performing a
snapshot on this same volume.
User response: Try the command again, and specify a

different destination for the object that was not
processed.

to take a snapshot of the specified volume because
another process is already performing a snapshot of
this volume. The operation continues without snapshot
support.
ANS1396E
Access to the specified log or trace file

(filename) is denied.
Explanation: Access to the specified file is denied. You

specified a log or trace file name that cannot be written
by the current user.
User response: Wait until the other IBM Tivoli Storage

Manager process finishes with the volume and then try
the operation again.
ANS1400W

Explanation: The snapshot cache location must point

to a local volume that is formatted with NTFS. The
default cache location is on the same volume where the
ANS1397W
The snapshot cannot be taken because

the SNAPSHOTCACHELocation does
not have enough space for this snapshot
operation.

to take a snapshot of the specified volume. The
SNAPSHOTCACHELocation points to a location which
does not contain the space necessary to create the
snapshot; the disk is probably full. The operation
continues without snapshot support.
snapshot operation.
User response: Change the value of the
SNAPSHOTCACHELocation, or clean the disk to which
the SNAPSHOTCACHELocation points.
ANS1398E
Initialization functions cannot open one

of the Tivoli Storage Manager logs or a
related file: log-name. errno = errno-value,
Explanation: The file log-name could not be opened

during initialization. The system set the error code
errno-value. If the reason given is access denied, the
current user does not have permission to write to the
log in the directory specified. It is also possible that no
space is available at the given log location.
On Unix systems, the log may not be placed in the root
directory. Attempts to do so will result in an access
denied error.
System action: Processing terminates.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory into which the
current user can write. You may also use the
ERRORLOGNAME option to specify a file to which the
current user has write permission.
The snapshot cache location is not valid.

option.
ANS1401W
The snapshot virtual volume is not

accessible.
Explanation: The logical volume snapshot agent

(LVSA) cannot access the virtual volume during
OFS-enabled backup/archive operation because IBM
Tivoli Storage Manager was probably started via
terminal services. The operation continues without
snapshot support.
User response: Do not use terminal services for the
snapshot. Try the operation again on the local machine.
ANS1402W
The snapshot is not supported on a

remote, removable, or SAN drive.

to take a snapshot of the specified volume because
open file support is only supported on local fixed
volumes, including volume mountpoints. The operation
continues without snapshot support.
snapshot operation.
User response: To take advantage of the open file
support, you may try the operation again on the local
machine.
701
ANS1403E ANS1413W
ANS1403E
Error loading a required DLL

dynamic link library. The DLL load failed.
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
previous operation required the machine to be restarted

for the changes to take effect, but the machine has not
been restarted. The operation will continue without
snapshot support.
snapshot operation.
User response: Restart the machine and then try the
operation again.
ANS1409E
The remote copy process process ID on

server could not be canceled.

function from a dynamic link library. The DLL load
failed.
Explanation: A remote copy operation with process id

process ID, which is in progress on server, could not be
canceled. Check your error log to see cause of failure.
User response: Verify that your system software is up

to date.
User response: Contact your TSM administrator.

ANS1410E
ANS1405I
service-name service needs to be

restarted.
Explanation: The service must be restarted for the

restored changes to take effect.
Unable to access the network path.
Explanation: The network path cannot be accessed

due to a possible network problem.
System action: The client terminates.
User response: Restart the service.
User response: Ensure that the network is up and the

path can be accessed using a system command, and
ANS1406I
ANS1411E
System action: Changes are not effected.
Performing operation using

point-in-time copy of the filesystem:
volname.
Explanation: IBM Tivoli Storage Manager is taking a

snapshot of the specified volume during the backup or
archive operation. This allows the IBM Tivoli Storage
Manager to access locked or in-use files.
A communication session was dropped.
Explanation: A communication session was dropped

due to a possible network problem.
User response: Ensure that the network is up and
System action: Operation proceeds.

ANS1407I
Performing operation using

point-in-time copy of the filesystem.
Explanation: IBM Tivoli Storage Manager is taking a

snapshot of the specified volume during the backup or
archive operation. This allows the IBM Tivoli Storage
Manager to access locked or in-use files.
ANS1412E
Directory or file has bad EA data or

inconsistent data.
Explanation: Directory or file has bad EA data or

inconsistent data.
User response: Check failing directory or file for bad
EA data. Copy the directory to a new location and retry
the operation.
System action: Operation proceeds.

ANS1408W
Previous changes have not been

commited. The machine must be
restarted before the snapshot can be
taken

to take a snapshot of the specified volume because a
702
ANS1413W

not recognized by the system as a disk
file and cannot be processed. The file is
skipped.
Explanation: The client is unable to process file types

that are not disk, such as character and pipe. This
message is typically, but not always, issued for file
names that are normally reserved for the operating
system. In the Windows environment, reserved names
ANS1414W ANS1421E
include AUX, CON, NUL, PRN, COMx or LPTx, where
x is any digit from 1 to 9 (for example, COM1, LPT3,
etc.).
with out server-free data movement.

User response: Contact your TSM administrator to
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
options to prevent the client from trying to process the
file. In the Windows environment, normal delete
commands will most likely not work. You will need to
prefix the file name with the characters \\.\. For
example, del c:\mydir\lpt4 will not work, but del
\\.\c:\mydir\lpt4 will work.
ANS1414W
Dont have sufficient authority to delete

open group on server.
Explanation: An open image group exists on the TSM

server and cannot be deleted due to missing backup
delete rights for this node.
ANS1418W
A call to TSM API API-name failed.
Explanation: An unexpected error occurred while

performing server-free data movement.
System action: The requested operation will be retried
ANS1419W
Remote copy operation for volume

filespace-name failed or could not be
restarted, return code retcode.
Explanation: An error occurred on server when

starting or during the remote copy operation for
volume filespace-name.
User response: Ask your TSM administrator to grant

backup delete rights for your node.

ANS1415W

Resetting enableserverfree option. This

operation will continue without
server-free data movement.
Explanation: Server-free data movement is not

possible due to the reason described by the preceding
message.
System action: The requested operation will continue
without server-free data movement.
ANS1416W
Management class name to which

volume filespace-name is bound does not
allow server-free data movement.
Explanation: The management class to which this

filespace-name is bound does not have a server-free path
to the destination storage pool. This message is also
reported when server-free data movement is not
enabled on server using set serverfree status=on.
System action: The requested operation will continue
allow server-free data movement from this system.
ANS1417W
An error occurred while obtaining

physical extent map for volume
filespace-name.
Explanation: An error occurred while obtaining

volumes filespace-name logical and physical layout.
ANS1420W
Server-free path is not available for one

or more disks for volume filespace-name.
Explanation: Either one or more disks used for

volume filespace-name, or its OBF file in case of an
online backup, does not have a server-free path
available or the disk serial number and LUN detected
by the TSM client does not match with the disk
definition on the TSM server.
with out server-free data movement. If server-free data
movement failed only for the OBF file, only the OBF
file will be re-transferred.
ANS1421E
The image object object-type was not

found on server.
Explanation: The specified image object of type

object-type could not be located on the server. The
operation cannot complete without this object.
additional messages that might indicate the reason for
the problem. Take any corrective action suggested by
the messages, then try the operation again. If the
further assistance.

703
ANS1422W ANS1431E
ANS1422W
The image data for volume filespace-name

is either compressed or its compression
information can not be determined.
Explanation: The image data was backed up either

with compression or by an older client version. This
data format cannot be restored on server-free path.
without server-free data movement.
ANS1423W
The image for volume filespace-name was

backed-up in old format.
Explanation: The image data was backed up in old

image (single object) format. This data format cannot be
restored on server-free path.
System action: The Windows Registry is not backed

up.
messages that might have been logged when this
message was written, and take the corrective action (if
any) suggested by those messages. Make sure that
account under which the operation runs has sufficient
privileges. Ensure that the system has sufficient
memory to run TSM. Remove the ADSM.SYS directory
from the root of your system drive, then try the
ANS1427I
Registry Backup function completed

successfully.
Explanation: Registry backup was successful.


ANS1428E
ANS1424W
Retrying failed image operation for

volume filespace-name.
Explanation: The transaction for image operation for

volume filespace-name failed due to reason described by
earlier message(s).
System action: The requested image operation will be
retried again.
Backup of the registry failed.
Explanation: None.
System action: The registry is not backed up.
ANS1429I
ANS1425E
Explanation: Registry Restore was successful.
The image operation for volume

filespace-name cannot be retried because
of a severe error.
Explanation: None.
System action: The image operation fails for the
indicated volume.
ANS1426E
An error occurred creating the Registry

backup directory structure
Explanation: The TSM client uses an intermediate

directory structure on the client machine as part of the
Windows Registry backup process. The client was
unable to create this intermediate directory structure, so
the Windows Registry could not be backed up. This
problem can occur if you do not have sufficient
privileges to perform the backup operations, if the
client is unable to allocate more memory from the
system, or if a component within the directory
structure already exists as a file.
704
Registry Restore function completed

successfully.

ANS1430W
The machine must be rebooted for the

changes to take effect.
Explanation: The TSM restore operation made changes

that will not be in effect until the machine is rebooted.
It is important to note that until the reboot occurs, the
system or its applications might be unstable.
System action: None
ANS1431E
Restore of the registry failed.
Explanation: None.
System action: The registry is not restored.
ANS1432E ANS1443E
ANS1432E
Keyword Expected after keyword

keyword.
Explanation: A registry command was incorrectly

entered.
ANS1438E
Backup of the event logs failed.
Explanation: None.
System action: The event logs are not backed up.
User response: Refer to the command reference for

this command.
ANS1433E
ANS1439I
System action: Registry function is not invoked.
Extraneous argument input after

keyword keyword

entered.
System action: Registry function not invoked.
this command.
ANS1434E
Invalid argument input after keyword

keyword

entered.
System action: Registry function not invoked.
this command.
ANS1435E
An error occurred saving a registry key.
Event Log Restore function completed

successfully.
Explanation: Event Log Restore was successful.

ANS1440E
Restore of the event logs failed.
Explanation: None.
System action: The event logs are not restored.
ANS1441E
Keyword Expected after keyword

keyword.
Explanation: None.
Explanation: A event log command was incorrectly

entered.
System action: The registry is not backed up.
System action: Event Log function is not invoked.

this command.
ANS1436E
An error occurred replacing a registry

key.
Explanation: None.
System action: The registry key is restored from the
server, but cannot be activated in the registry. The
current registry key remains active.
ANS1437I
Event Log Backup function completed

successfully.
Explanation: Event Log backup was successful.
ANS1442E
Extraneous argument input after

keyword keyword

entered.
System action: Event Log function not invoked.
this command.
ANS1443E
Invalid argument input after keyword

keyword

entered.
System action: Event Log function not invoked.
this command.

705
ANS1444E ANS1451W
ANS1444E
An error occurred creating the Event Log

backup directory structure
Explanation: The TSM client uses an intermediate

directory structure on the client machine as part of the
Windows Event Log backup process. The client was
unable to create this intermediate directory structure, so
the Windows Event Logs could not be backed up. This
problem can occur if you do not have sufficient
privileges to perform the backup operations, if the
client is unable to allocate more memory from the
system, or if a component within the directory
structure already exists as a file.
System action: The Windows Event Logs are not
backed up.
any) suggested by those messages. Make sure that
account under which the operation runs has sufficient
privileges. Ensure that the system has sufficient
memory to run TSM. Remove the ADSM.SYS directory
from the root of your system drive, then try the
ANS1445E

ANS1448E
The command command is not supported

by the current server.
Explanation: The server to which the client is

connected does not support the command.
1. If the command is set event, the server does not
support event-based policy. This command requires
that the server support event-based policy. That
support is available only at TSM Server levels 5.2.2
and above.
2. If the message displays any other command, the
server is configured to support archive retention
protection and cannot process operations not
associated with that facility.
System action: The command is skipped and other
User response: Log in to an appropriate server and
retry the command.
ANS1449W
ERROR: could not create NAS image

object.
Explanation: Creation of the NAS image object failed

for one of following reasons:
v An unauthorized user invoked the NAS command
A non-critical, unexpected error was

encountered. Deletion of a
snapshot(Set/Volume) failed. Probable
cause, snapshot does not exists anymore.
Continuing Process... TSM snapShot ID
: snapshot-id TSM function name :
function-name TSM function :
function-desc TSM return code : TSM-rc
TSM file : file-name (line-number)
v NAS operations are not supported on the current

platform
Explanation: None.
v Cannot find the NAS plugin library.
System action: The requested NAS operation is not

performed.
User response: Contact the TSM administrator with

the information provided in this message.
User response: Retry the operation after correcting the

cause for failure.
ANS1450W
ANS1446W
The volume layout of name is not

supported by server-free.
Explanation: The logical volume layout is not

currently supported by server-free.
System action: Processing continues using
non-server-free data movement.
User response: Refer to the documentation for
information on what volume layouts are supported by
server-free.
Explanation: The -FILENAME option was specified,

but the file name was omitted.
System action: The output is written to the default
file.
valid file name, or use the information that was written
to the default file.
ANS1451W
ANS1447I
Current user does not need to back up

the default profile.
Explanation: You are currently using the default

profile, and there is no need to back it up.
706
The -FILENAME option was specified

without a file name. Output will be
written to filename.
name: this type of mirrored volume is

not supported by server-free.
Explanation: This layout of mirrored volume is not

currently supported by server-free.
ANS1452W ANS1462E
information on what volume layouts are supported by
server-free.
ANS1452W
Server-free backup of FAT volumes is

not supported.
Explanation: Backup of FAT volumes is not supported

by server-free.
ANS1457E
Mirror synchronization failed.
Explanation: Synchronization of the volumes mirrors

failed.
User response: Check the error log for more errors.
Contact your systems administrator.

ANS1458I
OBF file for volume name is too small

for server-free data transfer.

information on what filesystems are supported by
server-free.
Explanation: The OBF file for volume is very small to

initiate a server-free data transfer. Hence this file will
not be transferred via a server-free data path.
ANS1453W
The IMAGEGAPSIZE option is not

supported for non-NTFS file systems.
The entire volume will be backed up.
Explanation: None.

ANS1460W
System action: The entire volume is backed up.

User response: Refer to the client manual for
additional information regarding the IMAGEGAPSIZE
option.
ANS1454W
Used blocks information could not be

obtained for name. The entire volume
will be backed up.
Explanation: None.
The file segment size entered is greater

than the max size. Please increase the
max size or decrease the file segment
size.
Explanation: The user has enabled both trace

wrapping and trace spanning but has entered a
segment size greater than the max size.
System action: Allow the user to re-enter the max size
or reduce the segment size.
User response: The user should either increase the
max size or reduce the segment size.

ANS1455I
Resynching mirrors. Please wait.
Explanation: The destination volume for server-free

restore has mirrored layout. The mirrors are being
resynched after the data restored.
User response:
ANS1461E

namepath-namefile-name: unsupported
encryption type.
Explanation: The files you are trying to restore or

retrieve have been backed up or archived by a later
version of the TSM client. The file encryption method is
not supported by the current client.
User response: Restore or retrieve the file with the
most recent version of the TSM client.
ANS1462E
Unsupported encryption type
Explanation: Synchronization of the volumes mirrors


User response:

ANS1456I
Mirror synchronization completed.
707
ANS1463E ANS1471E
ANS1463E
Unexpected error in cryptography

library.
Explanation: There was an unexpected error in the

cryptography library. See the error log for more
information.
User response: Check the error log for ANS1467E to
determine the cause of failure. Verify you TSM client is
installed properly. If needed, reinstall client and/or
API. If the problem still exists, contact TSM technical
support.
ANS1464S
Cannot load ICC encryption library.
Explanation: TSM is using cryptography library which

is installed automatically with the client and is being
loaded at runtime. The client cannot proceed if the
library is not loaded.
System action: Client exits.
support.
ANS1465E
Conflicting options ERRORLOGMAX

and ERRORLOGRETENTION were
specified.
Explanation: Values were specified for both the

ERRORLOGMAX and the ERRORLOGRETENTION
options. These options are mutually exclusive.
User response: Specify a nonzero value for
ERRORLOGMAX if you wish to have the TSM error
log wrap when it reaches the specified maximum
value. Use ERRORLOGRETENTION if you wish you
have the error log limited in size on a time-based
schedule.
ANS1466E
Conflicting options SCHEDLOGMAX

and SCHEDLOGRETENTION were
specified.
ANS1467E
ICC routine icc-routine returned: majRC

= majRC, minRC = minRC, desc = desc.
Explanation: There was an error within an ICC

cryptography library. This message reports return codes
and problem description which can be used by TSM
technical support personnel to determine the cause of
the error.
System action: Client exits.
User response: Verify you TSM client is installed
properly. If needed, reinstall client and/or API. If the
problem still exists, contact TSM technical support.
ANS1468E
Backing up Automated System Recovery

(ASR) files failed. No files will be
backed up.
Explanation: An error occurred while backing up the

files needed for Automated System Recovery (ASR). No
files were backed up.
check the error log. Verify that the Windows account
from which you are running this command has
administrator authority and try the command again.
ANS1469E

namepath-namefile-name; invalid
encryption key.
Explanation: The key you entered does not match the

key that was used to encrypt the file during backup.
The file can not be restored unless the matching key is
entered.
User response: Try the restore operation again and
provide the correct key.
ANS1470E
Shared library libgpfs.so is not loaded

for GPFS support: skip path_name
Explanation: The load library that is provided to

handle the GPFS ACL is not available on this system.
Explanation: Values were specified for both the

SCHEDLOGMAX and the SCHEDLOGRETENTION
options. These options are mutually exclusive.
User response: Ensure that the GPFS software is

installed on the system.
ANS1471E
User response: Specify a nonzero value for

SCHEDLOGMAX if you wish to have the TSM
scheduler log wrap when it reaches the specified
maximum value. Use SCHEDLOGRETENTION if you
wish you have the scheduler log limited in size on a
time-based schedule.
Explanation: An error occurred while creating the

system information file (asr.sif) needed for Automated
System Recovery (ASR). The ASR backup is
unsuccessful.
708
ASR system information file creation

failed. ASR backup is unsuccessful.
ANS1472E ANS1479E
administrator authority and that you have access to the
system object staging directory <system drive>
:\adsm.sys. Try the command again.
ANS1472E
Could not add entry to the ASR system

information file. ASR backup is
unsuccessful.
segment (and thus to the server).

System action: The session is rejected and processing
stops.
User response: Run the command under the uid of
the processing running dsmserv, if possible. Otherwise
contact your system administrator for further help.
ANS1476E
CLUSTERNODE is set to YES but the

Cluster Information Daemon is
notstarted.
Explanation: An error occurred while adding an entry

to the system information file (asr.sif) needed for
Automated System Recovery (ASR). The ASR backup is
unsuccessful.
Explanation: The Cluster Information Daemon must

be started in order to specify the CLUSTERNODE
option.

administrator authority and try the command again.
User response: Start the HACMP Cluster Information

Dameon.
ANS1473E
Session rejected: TCP/IP connection

failure for Shared Memory
Explanation: An attempt to connect to the local server

using the Shared Memory protocol has failed during
initial TCP/IP communications. This error can occur if
the server is not listening on the correct port, or if the
server is down.
ANS1477E

cluster load library is not valid.
Explanation: The load library that the operating

system provides to obtain the cluster name is not valid.
A possible cause is an out-of-date load library which
does not contain the proper routines this product
expects.
User response: Ensure that the latest cluster software

is installed on the system.

further help.
ANS1478E
ANS1474E
An error occurred using the Shared

Memory protocol
Explanation: An error has occurred while reading or

writing data through the Shared Memory
communications protocol.
operation.
continues, see your system administrator for further
help.
ANS1475E
Insufficient authority to connect to the

shared memory region
Explanation: The user issuing the command does not

have authority to connect to the shared memory
segment. When the shared memory segment is created
by the server, it will be owned by the effective uid of
the server process (dsmserv). Only processes running
under this uid or root will be allowed to connect to the

cluster software is not availableon this
system.

systems provides to obtain the cluster name is not
available on this system.
User response: Ensure that the cluster software is
ANS1479E
CLUSTERNODE is set to YES but this

machine is not a member of acluster.
Explanation: This machine is not a member of a

cluster node. Possible causes are that the cluster service
has not been configured correctly, or that the cluster is
in the process of initialization.
configured properly. If the cluster is in the process of
initialization, retry the operation at a later time.
709
ANS1480E ANS1491E
ANS1480E

cluster service is not enabledon this
system.
Explanation: The cluster service has not been enabled

on this system.
User response: Enable the cluster service on the
system.
ANS1481E
The CLUSTERNODE option is not

supported on this system.
log might contain additional information related to this

error.
User response: Examine the Windows event log and
TSM error log for messages related to Windows
Management Instrumentation (WMI). Ensure that the
WMI is started.
ANS1487E
An error occurred while backing up the

WMI repository. The database will not
be backed up.
Explanation: This option is not supported on this

system.
Explanation: The Windows event log and TSM error

log might contain additional information related to this
error.
User response: Disable the CLUSTERNODE option in

the local options file.

TSM error log for messages related to WMI. Ensure
that the Windows Management Instrumentation service
is started.
ANS1482E
An unexpected error (retcode) occurred

while the program was trying to obtain
the cluster name from the system.
Explanation: An unknown error occurred while the

program was trying to obtain the cluster name from the
cluster service. The error code is the reason code
provided directly from the cluster service being used in
this operating system environment.
User response: Consult the documentation for your
clustering software for an explanation of the reason
code. Insure that your clustering service is operational,
then try the TSM operation again.
ANS1483I
ANS1489E
The WMI service failed to stop. No files

will be restored.
Explanation: An error occurred while stopping the

Windows Management Instrumentation (WMI) service.
The database will not be restored.
TSM error log for messages related to Windows
Management Instrumentation (WMI). You might need
to quiesce WMI activity or reboot the machine in order
to free resources which are preventing the WMI service
from stopping.
Schedule log pruning started.
Explanation: The schedule log pruning function has

begun.
System action: The schedule log is pruned.
ANS1490W
File specification file-spec ignored. A

file list has already been specified.
Explanation: A non-option argument (file

specification) was encountered after the -FILELIST has
been processed.
System action: The argument is ignored.
ANS1484I
Schedule log pruning finished

successfully.
Explanation: The schedule log pruning function

completed with no errors.
User response: You may have either a -FILELIST or

explicit file specifications on this command, but not
both.
ANS1491E
Explanation: The -FILELIST option may only be

specified once per command
ANS1486E
An error occurred while restoring the

WMI repository. The database will not
be updated.
Explanation: The Windows event log and TSM error
710
Only one -FILELIST option allowed.
User response: Enter only one -FILELIST option on

the command.
ANS1492S ANS1500E
ANS1492S
Invalid virtual mountpoint filespace-name:

File not found.
Explanation: The specified VIRTUALMOUNTPOINT

in the system options file is invalid because it could not
be found in the file system.
User response: Verify if you obtained the desired

results. If not, you need to correct the client options file
by removing the duplicate option statement.
ANS1497W

operation.
User response: Check the virtual mountpoint in the
system options file and make sure it exists in the file
system. Retry the operation.
Duplicate include/exclude option option

file-name found while processing the
client options passed by the server. This
might produce unexpected results.
Explanation: TSM found a duplicate statement while

processing the client options by the server, which might
produce unexpected results.
ANS1493S

Access denied.

in the system options file is invalid because access to it
is denied.
operation.
User response: Check the VIRTUALMOUNTPOINT in
the system options file and make sure it is accessible.
User response: Verify if you obtained the desired

results. If not, you need to correct either the client
options file or the client options passed by the server.
ANS1498E
The IIS services failed to stop. No files

will be restored.
Explanation: An error occurred while stopping the

Internet Information Services (IIS) services. The
metabase will not be restored.

in the system options file is invalid because it is a
symbolic link and FOLLOWSYMBOLIC is not set.

TSM error log for messages related to Internet
Information Services (IIS). You might need to quiesce
IIS activity or reboot the machine in order to free
resources which are preventing the IIS service from
stopping.

operation.
ANS1499E
User response: Set the option FOLLOWSYMBOLIC to

YES in the user options file. Retry the operation.
Explanation: A failure occurred on the server during

creation of the table of contents.
ANS1494S

Symbolic link.
Creation of table of contents failed.
System action: The table of contents was not created.

ANS1495S

Other error, rc = return-code.

in the system options file is invalid.
User response: This abort code indicates there was a

problem creating a table of contents on the server. The
sysadmin will need to consult the activity log on the
server to determine the cause.

operation.
ANS1500E
User response: Make sure the virtual mountpoint is a

directory and accessible from the shell, and retry the
operation.
ANS1496W
Duplicate include/exclude option option

file-name found while processing the
client options file. This might produce
unexpected results.
Explanation: TSM found a duplicate statement while

processing the client options file, which might produce
unexpected results.
Module dsmtca not found in secure

directory.
Explanation: TSM cannot find the Trusted

Communication Agent module (dsmtca) in the
appropriate directory.
User response: Log on as root user, then create a link
to dsmtca module in /usr/bin with the command: ln -s
/usr/tivoli/tsm/client/ba/bin/dsmtca
/usr/bin/dsmtca
711
ANS1501E ANS1510I
ANS1501E
Trusted agent execution/owner

permissions are invalid
Explanation: The Trusted Communication Agent

execution/owner permissions are invalid.
the Trusted Communication Agent permissions are set
correctly. This error can be caused by installing TSM as
a non-root user. For the UNIX platforms that have the
installation program (dsm.install), you must run
dsm.install while logged in as the root user.
ANS1502E
Access to system function required to

run has been denied
Explanation: The permissions of the Trusted

Communication Agent do not allow it to be accessed
by the user of the TSM client.
necessary fixes that are required to support used block

image backup.
User response: Please upgrade to AIX 5300-06-04 or
later in order to perform used block image backup.
ANS1506E
Explanation: The Trusted Communication Agent is

invoked by the TSM client and has received an
unknown request argument in the call.
User response: It is possible the Trusted
Communication Agent was mistakenly invoked by a
process other than the TSM client. If that is not the
case, then this is an internal error. If the problem
recurs, contact your IBM service representative.
ANS1507E

ANS1503E
Valid password not available for server

server-name. The administrator for your
system must run TSM and enter the
password to store it locally.

for the specified server server-name is unavailable.
The TSM Trusted Communication Agent

received an invalid request.
This action requires TSM administrative

authority on this system.
Explanation: An activity has been attempted that must

be performed by the TSM administrator (for example,
open registration, filespace delete or password update).
User response: If the activity is required, the
administrator for this system must perform it.
ANS1508E
User response: The administrator for your system

must set and store a new password.
Explanation: An error has occurred because the

semaphores you are attempting to allocate have become
insufficient.
ANS1504E
Error starting the Trusted

Communication Agent process.
Explanation: An error has occurred starting the

Trusted Communication Agent process; specifically, the
fork() function has failed.
User response: Probable system error. If the problem
persists, restart the workstation.
ANS1505W
Performing image backup of the entire

volume for volume name. The
IMAGEGAPSIZE option value of image
gap size is being ignored as this level of
the operating system does not support
used block image backup. Please
upgrade to AIX 5300-06-04 or later in
order to perform used block image
backup.
Explanation: AIX 5300-06-04 or later has some
712
Error allocating semaphores.
User response: Ask your system administrator for

assistance, and possibly increase the number of
semaphores in your system.
ANS1509E
Error setting semaphore value or

waiting on semaphore.
Explanation: An error has occurred while attempting

to set or wait on a semaphore.
ANS1510I
The specified backupset either does not

exist, or does not contain a backupset of
type file for the specified nodename.
Explanation: The specified backupset either does not

exist, or does not contain a backupset with file data for
the node name specified. The restore backupset
ANS1511I ANS1521E
command is limited to backupsets that contain file
data. To restore an image backup from a backupset, use
see the restore image command.
User response: If an incorrect backupset name was
specified, retry the command with the correct
backupset name. If you are trying to restore an image
from a backupset, refer to the restore image command
for the correct syntax.
The creation date for LN and SN dont match.

The short name attribute for LN doesnt match SN.
If you are unable to determine what is wrong, report
the problem to your service representative.
ANS1514W
Encryption key passwords are not the

same.
Explanation: The key passwords are different.

System action: TSM allows you to try again.
ANS1511I
Invalid Restore session number entered.

Try again.
User response: Enter the correct password.

list of restartable restores. The number you entered is
either less than one or greater than the highest item
number displayed.
ANS1515E

selection.
System action: The table of contents was not loaded.

quit.
ANS1512E
Scheduled event event failed. Return

code = value.
Explanation: One or more error conditions were

encountered that prevented the schedule from
completing successfully. This message is preceded by
other messages that indicate the specific problems
encountered during the operation.
System action: Scheduled event failed.
User response: Check the schedule and error log files
for the messages that specify what problems were
encountered during the operation. Correct the
conditions that caused those messages to be issued. The
specific corrective actions will depend on the specific
errors encountered.
ANS1513E
The object is skipped from rename.

Error_condition.
Explanation: TSM skips the specified object from

renaming because the object with the same long name
but with different attributes exists on the server.
Loading a table of contents failed.
Explanation: A failure occurred on the server during

loading of the table of contents.
User response: This abort code indicates there was a

problem loading a table of contents on the server. The
sysadmin will need to consult the activity log on the
server to determine the cause.
ANS1519E

delete backup files
Explanation: The server does not allow your node to

delete backup files.
System action: TSM did not delete the backup files.
ANS1520E
Failure writing to the Tivoli Storage

Manager error log: errno = errno-value,
Explanation: A failure was encountered when writing

to the dsmerror log or dsierror log. The system set the
error code errno-value. It is possible that no space is
available at the given log location.
environment variable to a directory with adequate
space to write the log data.
System action: The backup operation will continue.

The specified object will be expired during the next
incremental backup.
ANS1521E
User response: The object is skipped if one of the

following condition takes place:

to one of the log files or a related file named file-name.
The system set the error code errno-value. reason is the
system explanation of that error code. Among other
things, it is possible that no space is available at the
given log location.
The long name object(LN) has more recent insert

date than the short name object(SN).
The management classes for LN and SN dont
match.
Failure writing to a Tivoli Storage

Manager log or log-related file: file-name,
errno = errno-value, reason
The copygroups for LN and SN dont match.
LN and SN have different owners.

713
ANS1522E ANS1535E
SCHEDLOGMAX is not specified for this log, so its

format must be changed and old data saved.
System action: Transition processing continues.
ANS1522E
It is not possible to authenticate with

the client node client-node ! The Space
Management Agent version agent-version
running on client-node does not match
with the Space Management Console
version console-version you are running !
Explanation: The version of the Space Management

Console does not match with the version of the Space
Management Agent running on the client node
machine. To avoid incompatibleness it is necessary to
run the console and the agent with the same version.
System action: The Space Management Console exits.

ANS1530I
count log records processed.
Explanation: This is just a progress report to let you

know the process is still ongoing.
ANS1532E
Proxy Rejected: Proxy authority has not

been granted to this node.
User response: Use Space Management Console with

the same version like the Space Management Agent
running on the HSM node you want to manage.
Explanation: The node has not been granted proxy

authority to access the node named by the
ASNODENAME option. The TSM administrator must
first grant proxy authority.
ANS1523E
An error occurred while connecting to

TSA/SMDR service.
Explanation: An error was encountered during a call

to the TSA/SMDR service. This message usually
follows previous messages that contain more specific
information about the problem.
User response: Refer to previous messages in
dsmerror.log for further information. If those messages
are not helpful in identifying the cause of the problem,
see your system administrator for further assistance.
ANS1528I
TSM is converting the log-file from

continuous (pruning) mode to wrapping
mode. This process may take several
minutes.
Explanation: The log-file was previously in continuous

mode where the only size control was through the use
of ERRORLOGRETENTION or
SCHEDLOGRETENTION option. This is the first
occasion where ERRORLOGMAX or SCHEDLOGMAX
is specified for this log, so its format must be changed
and old data saved.
ANS1529I
TSM is converting the log-file from

wrapping mode to continuous (pruning)
minutes.
Explanation: The log-file was previously in wrapping

mode where the size control was through the use of the
ERRORLOGMAX or SCHEDLOGMAX option. This is
the first occasion where ERRORLOGMAX or
714
User response: The TSM server administrator must

grant proxy authority for this node. See the
administrator command Grant Proxynode.
ANS1533E
Proxy Rejected: The node name you

specified in the ASNODENAME option
is locked.
Explanation: The TSM administrator has locked the

node you specified as the ASNODENAME option.
unlock the node before you can access it. Try the
operation later, or check with your TSM administrator.
ANS1534E
Proxy Rejected: The TSM server has run

out of memory.
Explanation: There is not enough memory available to

allow this operation to continue.
amount of memory of the server.
ANS1535E
Proxy Rejected: ASNODENAME and

NODENAME are identical.
Explanation: TSM does not allow the ASNODENAME

and NODENAME option values to be the same.
User response: Use the ASNODENAME option only
to access another node. It is not necessary to set
ASNODENAME option to access your own node.
ANS1536E ANS1546W
Remove ASNODENAME from your option file unless
you are actually trying to access a node that you have
been granted authority to access with the
administrative command Grant Proxynode.
ANS1536E
Proxy Rejected: The server has an

internal error.
Explanation: The client cannot proxy to the node

named by the ASNODENAME option because of an
ANS1541E
Node entered has been federated into a

Network Deployment, federated nodes
cannot be backed up.
Explanation: Node entered has been federated into a

Network Deployment, federated nodes cannot be
backed up.
System action: None
User response: Run dsmc q was -wastype=local to
see the nodes that may be backed up.

User response: See your system administrator
immediately.
ANS1537E
The ASNODENAME option is not valid

with the FROMNODE option.
Explanation: None.
User response: Remove the ASNODENAME option
from the options file or do not use the FROMNODE
option.
ANS1538E
The operation that is being attempted

cannot be invoked using the
ASNODENAME option.
Explanation: None.
ANS1539E
The ASNODENAME option cannot be

used with the CLUSTERNODE option.
Explanation: None.
ANS1540E
The ASNODENAME option cannot be

used with the ENABLESERVERFREE
option.
Explanation: None.
ANS1542E
Incorrect WAS backup type entered, no

node of that name and type exists.
Explanation: There is no node with the WAS backup

type that was entered.
System action: None
User response: Check the wastype that was entered.
Run dsmc q was -wastype=local to see the nodes that
may be backed up.
ANS1543E
Incorrect WAS node entered, no node

exists with that name.
Explanation: There is no node with the WAS backup

type that was entered.
System action: None
User response: Check the node name that was
entered. Run dsmc q was -wastype=local to see the
nodes that may be backed up.
ANS1544E
An error in WAS processing has

occurred.
Explanation: None.
System action: None
User response: Run the following command to see the
nodes that can be backed up: dsmc query was
-wastype=local Make sure the results are correct for
your environment, then try the operation again. If the
problem persists, contact TSM technical support for
further assistance.
ANS1546W
TSM failed to lock the WebSphere

configuration repository.
Explanation: None.
System action: The lock of the WebSphere
configuration repository fails.
User response: Ensure that the WebSphere server is
running. If the server is already running, ensure that
the repository is unlocked. Ensure that you are backing
up the correct node. To see a list of available nodes that
can be backed up, enter: dsmc q was -wastype=local.
715
ANS1547W ANS1555E
ANS1547W
TSM failed to unlock the WebSphere

Configuration Repository.
ANS1552W
Explanation: None.
System action: The unlock of the WebSphere
Configuration Repository fails.
User response: Make sure that the WebSphere server
is running. If the repository is locked, then unlock it
and try the operation again. Ensure that the correct
node is being backed up. To see a list of available
nodes that can be backed up, run: dsmc q was
-wastype=local.
ANS1548E
A supported version of WebSphere is

not installed on this machine.
Explanation: A supported version of WebSphere is not

installed on this machine. The only version of
WebSphere that is supported is 5.0.x.
System action: None
User response: Install WebSphere 5.0 on the machine.
ANS1549E
No application server instances were

found. Unable to perform backup.
Explanation: The application server is not installed on

this machine.
System action: Backup is not performed.
A user name and a password have not

been provided to Data Protection for
WebSphere.
Explanation: The dsmc set WASPassword command

has not been run to provide the user name and the
password for Data Protection for WebSphere. Data
Protection for WebSphere needs the user name and
password to be able to run when WebSphere security is
turned on.
System action: Data Protection for WebSphere cannot
run.
User response: Run the dsmc set WASPassword
command to set the WebSphere security user name and
password.
ANS1553W
The user name and password that have

been provided to Data Protection for
WebSphere are invalid.
Explanation: None.
System action: Data Protection for WebSphere cannot
run.
User response: Run the dsmc set WASPassword
command to set the WebSphere security user name and
password.
ANS1554W
User response: Install the application server.
The WASOffline option has been

ignored.
Explanation: Deployment manager is not installed on

this machine.
Explanation: When a WebSphere server is running,

Data Protection for WebSphere contacts WebSphere and
locks the Configuration Repository. The WASOffline
option is only valid when a WebSphere server is not
running. If a WebSphere server is running, then
WASOffline is ignored.
System action: Back up is not performed.
System action: The WASOffline option is ignored.
User response: Install the network deployment

manager.
User response: Remove the WASOffline option from

the options file.
ANS1551E
ANS1555E
ANS1550E
No network deployment manager

instances were found to back up.
A TSM authorized user must configure

IBM Tivoli Storage Manager before
individual users can use it.
Explanation: IBM Tivoli Storage Manager was not

started by a TSM authorized user and the TSM System
Preferences file could not be located.
System action: IBM Tivoli Storage Manager exits.
User response: The initial setup and configuration of
IBM Tivoli Storage Manager must be done by a TSM
authorized user. To become a TSM authorized user,
system administrators must use the TSM Backup for
Administrators application. Refer to the Backup-Archive
Client Installation and Users Guide for a complete
discussion of the TSM authorized user.
716
The WebSphere Application Server

(WAS) plug-in level must be at 5.2.1 or
greater to set the WebSphere user and
password.
Explanation: You must have the backup-archive client

and the WAS plug-in at a level of 5.2.1 or higher to be
able to connect to WebSphere when security is enabled.
System action: WebSphere does not set the user and
password.
User response: Upgrade the WAS plug-in to 5.2.1 or
greater.
ANS1556E ANS1566E
ANS1556E
Setting the WAS user and password

failed.
Explanation: Password validation for the WAS user

and password failed.
System action: WAS password validation fails.
User response: Rerun the set WASPassword command
with the correct values for user and password.
ANS1557W
The WAS Server was not running, and

the password file was saved without
validation.
Explanation: If the WAS server is down, then it is not

possible to connect to the server and validate the
user-entered password. The password has still been
saved, but no validation has been performed.
System action: The set WAS password command did
not validate the password. The password has still been
saved, but no validation has been performed. The
password may be incorrect.
ANS1560W
The WebSphere server is not running.
Explanation: The WebSphere server is not running.

The WAS server is running for backup operations.
System action: The WebSphere server is not running.
User response: Start the WAS server and run the
backup again.
ANS1561I
Loading the Java Runtime Environment,

please wait.
ANS1562E
WAS Restore failed during EAR

Expansion.
Explanation: EAR Expansion is performed for a

WebSphere Application server after the files have been
restored.
System action: WAS restore fails.
User response: Run the restore again.
User response: There are two options:
ANS1563W
v Try a backup. If the backup performs a failover, and

there is a incorrect password message in the error
log, then the password that was entered is incorrect.
Explanation: The itsm.was.properties file is used to

store the WebSphere security user name and password.
v Start the WAS server and rerun the set password

command. Since the server is now up, validation will
be performed as normal and the user notified if a
good/bad password was entered.
ANS1558W
The WebSphere backup is failing over

to an offline backup.
Explanation: If there is an error locking the

WebSphere configuration repository, then Data
Protection for WAS will still get a backup and not lock
the repository.
System action: The WebSphere backup fails over to an
offline backup.

User response: Run the dsmc set waspassword
command to create this file.
ANS1564I
v The repository is already locked

v Security is turned on and there is no WAS
user/password file
v Security is turned on and the information in the
WAS user/password file is bad.
Running the WebSphere EAR

expansion, please wait.
Explanation: An APP server must have the restored

EARS expanded for the server to work.
ANS1565E
User response: Check the error log to see the nature

of the lock error. The lock operation can fail because:
v The WAS server is not running
The itsm.was.properties file does not

exist.
No WebSphere EARExpander was

found. Copy the EARExpander tool
from the base WebSphere bin directory
to the instance bin directory, then run
the restore operation again.
Explanation: The EAR files are expanded for an

instance of an Application server and the EARExpander
tool does not exist in the instance bin directory.
System action: No WebSphere EARExpander found.
Correct the lock error.
User response: Copy the WAS EARExpander tool

from the base installs bin directory to the bin directory
of the instance. Then run the WAS restore operation
again, after the EARExpander tool has been copied.
ANS1559I
ANS1566E
Set WAS password completed

successfully.
The version of WebSphere on the

machine does not match the version of
WebSphere that was backed up. These
versions must match for a WAS restore
operation.
717
ANS1567I ANS1573E
Explanation: The version of WebSphere on the
machine does not match the version of WebSphere that
was backed up. These versions must match for a WAS
restore operation.
System action: The WAS restore operation fails.
User response: Install the correct version of
WebSphere on the machine before performing the
restore operation.
ANS1567I
A 5.2.2 or higher client is restoring data

backed up from a 5.2.0 client. No
version check can be performed before
the restore.
Explanation: WebSpheres version information was

not stored as part of the backup for 5.2.0. So, a 5.2.2
client cannot ensure that the version of WAS that is
being restored is the same version of WAS that is on
the machine. A version of WAS that is restored may be
incompatible with the version of WAS on the machine
and can cause errors in WAS.
continue, but some functions of the CAD may not be

working properly.
User response: Use TCPCADADDRESS in the client
option file to indicate the proper TCP/IP address for
this CAD. Loopback address is not valid.
ANS1570E
Registering this instance of the Cad

with the server failed. Cad process
continues.
Explanation: The CAD failed to register address

information to the server, due to an error. There should
be a message immediately preceding this message that
would indicate the problem more precisely.
System action: The server did not register the
information for the CAD. CAD processing will
working properly.
User response: Look at messages immediately
preceding this message to help determine what error
occurred.
System action: No version check is performed.

User response: Make sure that the version of WAS
that is being restored is the same as the version of WAS
that is installed on the machine.
ANS1568E
The CAD attempted to register its

tcpport and tcpip address without using
the TCPCADADDRESS option.
Explanation: The CAD sent the port and address

information to the server, however, there was a
problem registering the information with the server.
The problem occurred because no default value for the
tcpip address was provided. The server was unable to
determine a default value for the tcpip address because
the communication method was not tcpip.
System action: The server cannot register the
working properly.
User response: Use TCPCADADDRESS in the client
option file to indicate the proper TCP/IP address for
this CAD.
ANS1569E
The CAD attempted to register its

tcpport and tcpip address but the
TCP/IP address resolved to the loopback
address and was rejected by the server.
Explanation: The CAD sent the port and address

information to the server, however, there was a
problem registering the information with the server.
The problem occurred because the server detected that
the address provided resolved to the loopback address.
System action: The server did not register the
718
ANS1571E
The time-option option cannot be used

without specifying the date-option option
Explanation: If the to/from/pit time options is

specified then the corresponding to/from/pit date
MUST also be specified.
User response: Either remove the to/from/pit time
option or add the corresponding to/from/pit date
option.
ANS1572E
An unexpected error was received from

the server query, RC=re tcode.
Explanation: An unexpected error was received by the

client. This could be caused by network problems or a
programming error.
ANS1573E
FROMDATE and TODATE cannot be

used with PITDATE.
Explanation: The PITDATE option specifies different

and conflicting date selection criteria from the
FROMDATE and TODATE options. Therefore these
options cannot be combined.
System action: The restore operation is not performed.
User response: Determine whether you require the
functionality of PITDATE or FROMDATE and
TODATE, then try the operation again. If you want to
ANS1574E ANS1581W
restore files as of a certain date and time, use PITDATE
and PITTIME. If you want to restore files from a given
range of dates, use FROMDATE, TODATE,
FROMTIME, and TOTIME. Refer to the TSM client
manual for your operating system for additional
information about these options.
ANS1574E
Journal Query Failed.
Explanation: The journal daemon was unable to

process the requested journal query.
v Ctrl-C - This indicates either the user entered the

ctrl-c sequence or that one of the Windows services
was stopped.
ANS1578E
The specified path path is not valid for

backup or archive.
User response: Retry the backup, check the journal

daemon errorlog for the cause of the failure. Backup of
other file systems in the domain will continue.
Explanation: The specified path is a special file system

or part of a special file system. Special file systems
contain dynamic information generated by the
operating system and should not be backed up or
archived. Refer to the TSM client manual for a
complete list of special file systems for your operating
system.
ANS1575E
System action: Processing continues if there are other

file systems to back up.
System action: Journal backup processing is

interrupted.
Journal Daemon Communications Error.
Explanation: An error occurred communicating with

the journal daemon.
User response: Do not specify special file systems for

backup or archive.
System action: Journal backup processing is

interrupted.
ANS1579E
User response: Retry the backup, check the journal

daemon and client errorlogs for the cause of the failure.
ANS1576W
Space Management Agent version

mismatch. The Space Management
Agent (hsmagent) version agent-version
running on client-node client node does
not match with the Space Management
Console (GUI) version console-version
you are running! To avoid compatibility
problems, please use the same version
for the Space Management Console and
the Space Management Agent. Do you
want to proceed?
Explanation: The version of the Space Management

Console does not match with the version of the Space
Management Agent running on the client node
machine. To avoid compatibility problems, please use
the same version for the Space Management Console
(GUI) and the Space Management Agent (hsmagent).
System action: Prompt the user to exit or continue.
User response: Use Space Management Console (GUI)
with the same version like the Space Management
Agent (hsmagent) running on the HSM node you want
to manage.
Explanation: A GSKit function has failed with the

specified error code.
System action: Processing stopped
User response: Make sure you have configured the
key database for SSL communication as described in
the documentation. If the problem persists, contact TSM
customer support.
ANS1580W
The Windows console event handler

received a event console event.
Explanation: A console event was received by one of

the IBM Tivoli Storage Manager processes or programs.
The following events can be received:
An Include.Fs statement with

performance algorithm set already exists
for the drive specified. Do you want to
replace the statement?
Explanation: The user tried to create a duplicate

Include.Fs entry on a drive that already has a
performance algorithm associated with it. This is
applicable to the Preference Editor on the MFC GUI
System action: The user can replace the statement
with the new one or they can cancel out of this
operation
User response: The user is prompted to replace the
statement with the new one or they can say No to
cancel out of this operation.
ANS1581W
ANS1577I
GSKit function func-name failed with

error-code: session
object-name was restored as temp-name.

A reboot is required to complete the
restore.
Explanation: This is a system file restored and could

not be immediately replaced. The file will be replaced
during the next reboot of the operating system. It is
important to note that until the reboot occurs, the
719
ANS1583E ANS1593E
changes will not be in effect.
System action: TSM restored the file with a temporary
name, and instructed the operating system to replace
the original file with the restored file during the next
boot of the operating system.
ANS1588W
I/O error reading file attribute: attr-name

for: file-name. errno = errno-value,

Explanation: The attribute attr-name of the file

file-name could not be retrieved. The system set the
error code errno-value. If the reason given is access
denied, the current user does not have permission to
read the file attributes.
ANS1583E
System action: Processing continues without backing

up the specified file attribute.
The Hardware Utility plug-in module

was not found or could not be loaded.
Explanation: Processing stops.
User response: Correct the condition causing the

physical error.

User response: Run dsmc show plugins at the TSM
command-line client prompt to see the available
plug-ins on the system and verify the path which is
being used to load the plug-ins. If the plugin path is
available and the Hardware Utility plug-in,
libPiHDW.a, is present, ensure that the LIBPATH
variable is set to the Hardware products library path,
for example, LIBPTH=/usr/opt/db2_08_01/lib.
ANS1584E
Error loading system library

libdevmapper.so required for image
operations for LVM2 volumes.
Explanation: The system library libdevmapper.so

required for LVM2 image operations could not be
loaded. This error can occur when library does not
exist on the system, or it is an earlier level than is
required, or it could not be opened by the TSM clienti
process.
System action: The image operations for LVM2
volumes will not be available.
User response: Check the installed packages and the
library versions on the system. If correct versions is
installed, check for access related issues. If system does
not have these library installed please contact your
Linux OS distributer.
ANS1587W
I/O error reading file attributes for:

file-name. errno = errno-value,
Explanation: The attributes of the file file-name could

not be retrieved. The system set the error code
current user does not have permission to read the file
attributes.
System action: Processing continues without backing
up the file attributes.
physical error.
ANS1589W
I/O error writing file attributes for:

file-name. errno = errno-value,
Explanation: The attributes of the file file-name could

not be set. The system set the error code errno-value. If
the reason given is access denied, the current user
does not have permission to set the file attributes.
System action: Processing continues without restoring
the file attributes.
physical error.
ANS1590W
I/O error writing file attribute: attr-name

for: file-name. errno = errno-value,
Explanation: The attribute attr-name of the file

file-name could not be set. The system set the error code
current user does not have permission to set the file
attributes.
System action: Processing continues without restoring
the specified file attribute.
physical error.
ANS1592E
Failed to initialize SSL protocol.
Explanation: TSM was unable to initialize SSL

protocol.
User response: Check for GSKit related messages in
the error log. Make sure you have configured the key
database for SSL communication as described in the
documentation. If the problem persists, contact TSM
customer support.
ANS1593E
Cannot open the key database.
Explanation: TSM was unable to open the keyfile that

is expected to contain the server certificate for SSL
communications.
720
ANS1594E ANS1602E
the documentation. If the problem persists, contact TSM
customer support.
ANS1594E
Wrong key database password.
Explanation: The key database that contains the server

certificate has been set up with the wrong password.
the documentation.
ANS1595E
Bad server certificate.
Explanation: TSM was unable to open SSL connection

to server because of a bad certificate. This error usually
occurs when the server certificate cannot be verified by
the client.
ANS1598E
-deltype=all is not valid for this file

specification.
Explanation: -deltype=all is used to delete an entire

directory tree. You must specify a fully wildcard
directory when using -deltype=all.
User response: Try the operation again with a valid
combination of options. If you want to delete all
backup versions of an entire directory tree, use
-deltype=all and a fully wildcarded file specification. If
you want to delete backup versions of partially
qualified file names, use -deltype=inactive or
-deltype=active. Also use -subdir=yes if you want to
delete backup versions in subdirectories of the file
specification. See the client manual or command line
help for additional information.
ANS1599E
Cannot load SSL runtime library.
Explanation: TSM failed to dynamically load SSL

runtime library necessary for SSL protocol

the documentation. Make sure to import the correct
certificate from the TSM server you are trying to
connect to.
ANS1596E
ANS1600E
SSL protocol is not supported.
Explanation: SSL protocol is not supported on this

platform.
User response: Refer to TSM documentation for the
list of supported platforms.
ANS1597E
The -pick and -deltype=all options are

not valid together.
Explanation: -deltype=all is used to delete an entire

directory tree. You cannot use -pick to select individual
objects from the tree. -pick is valid only with
-deltype=active or -deltype=inactive.
User response: Make sure TSM client is properly

installed. Try to reinstall the client software. If the
problem persists, contact TSM customer support.
Unable to load the Data Protection for
Lotus Domino library.
Explanation: The Datt Protection for Lotus Domino

library could not be loaded.
User response: Ensure that Domino plugin is properly
configured and check the error log on the client
machine for more information.
ANS1601E
The Domino plugin operation failed

because of an internal error.
Explanation: A Domino plugin internal error has

occurred.
User response: Try the operation again with a valid

combination of options. If you want to delete an entire
tree, use -deltype=all, but do not use -pick. If you want
to select which backup versions to delete, specify
-deltype=active or -deltype=inactive, and use the -pick
option. Also use -subdir=yes if you want the file
selection to include files in subdirectories of the file
specification. See the client manual or command line
help for additional information.
User response: Check the error log on the client

ANS1602E

because the preferences file was not
found.
Explanation: The Data Protection for Lotus Domino

preference file could not be found.
User response: The Data Protection for Lotus for
Domino configuration file (default name domdsm.cfg)
721
ANS1603E ANS1611E
could not be found. Check the error log on the client
ANS1603E

because of an internal TCP/IP error.
Explanation: A TCP/IP error has occurred.

User response: Check the error log on the client
ANS1604E

trying to start the dsmdomp address
space.
Explanation: The dsmdomp address space could not

be started. This is probably an installation error.
User response: Ensure that the lotus/bin directory has
a symbolic link to the tools directory for dsmdomp and
the lotus/notes directory has a symbolic link to the
dsmdomp executable. If the problem persists, contact
your System Administrator for further assistance.
ANS1607E
Explanation: The plugin is not loaded, and processing

continues.
System action: The plugin is not loaded, and
User response: This probably is an installation error.
Ensure that the plugins directory contains valid plugin
libraries, and that the correct level of the TSM client
has been installed. If the problem persists, contact your
System Administrator for further assistance.
ANS1608E

while initializing communications with
the dsmdomp address space.
Explanation: The Domino plugin communication

initialization failed.
User response: The dsmdomp address space failed
during its initialization. This is likely to be an
installation error. Ensure that the lotus/bin directory
has a symbolic link to the tools directory for dsmdomp
and the lotus/notes directory has a symbolic link to the
dsmdomp executable. If the problem persists, contact
your System Administrator for further assistance.
ANS1606E

while starting up the dsmdomp address
space.
Explanation: The dsmdomp address space could not

be started.
System action: The TDP for Domino processing stops.
User response: The dsmdomp address space failed
during its initialization. This is likely to be an
installation error. Ensure that the lotus/bin directory
has a symbolic link to the tools directory for dsmdomp
and the lotus/notes directory has a symbolic link to the
dsmdomp executable. Examine the file
/tmp/dsmdomp* for more information. If the problem
persists, contact your System Administrator for further
assistance.
722
Domino plugin operation failed with

the following message: messsage
Explanation: A Domino plugin operation error

occurred.
User response: Correct the error that caused the
operation to fail.
ANS1609E
ANS1605E
A plugin found in the plugins library is

not supported by the current level of the
TSM client.
Domino plugin process failed. The

following messages are associated with
the error. messsage.
Explanation: A Domino plugin operation error

occurred.
User response: Correct the error that caused the
operation to fail.
ANS1610E
The domnode option has not been

properly specified for the node
node_name.
Explanation: The domnode option has not been

properly specified in the dsm.sys file for the node
shown.
System action: Processing for this request stops.
User response: This is likely to be an installation error.
Ensure that the domnode option has been properly
specified for the node in question. If the problem
persists, contact your System Administrator for further
assistance.
ANS1611E
A plugin operation failed because of an

internal error.
Explanation: A plugin internal error has occurred.

System action: The plugin operation stops.
User response: If the error persists, run with tracing
enabled and contact your System Administrator and
IBM for further assistance.
ANS1612E ANS1621E
ANS1612E

because of a TSM API error.
ANS1618E
Explanation: An TSM API error occurred .
A Domino plugin operation is already

in progress. Please wait for operation to
complete.
Explanation: A Domino plugin operation is in

progress.
User response: Check error log on the client machine

System action: The Domino plugin operation stops.
ANS1613E
>Could not load the TSM API.
User response: Please wait for the Domino plugin

operation to complete before starting a new Domino
plugin operation.
Explanation: The TSM API could not be loaded.

ANS1619E

ANS1614E
The Domino plugin Try and Buy

license has expired.
Explanation: The Try and Buy license that was

detected has expired.
User response: This product is no longer valid for use.
A valid license must be obtained before running the
product.
Explanation: The version of the Domino plugin

currently installed on the system is older than the
version used to build the IBM Tivoli Storage Manager
application client.
User response: Install a version of the Domino plugin
at or later than the level of the IBM Tivoli Storage
Manager application client.
ANS1620I
ANS1615E

due to a license error.
Explanation: Domino plugin license verification failed.

User response: Check the error log for further
information.
ANS1616E

because the Lotus Domino API could
not be loaded.
Explanation: The Lotus Domino API could not be

loaded.
User response: Ensure the Lotus Domino Server is
installed correctly.
ANS1617E

because of a Data Protection for Domino
API error.
Explanation: A Data Protection for Domino API error

occurred during a Domino plugin operation.
The IBM Tivoli Storage Manager

application client cannot work with the
version of the Domino plugin you have
installed.
Backup version for filespace

namepath-namefile-name, object id object-id:object-id is not consistent with
local repository. Its being deleted.
Explanation: The specified backup instance of the

named object is not valid with local repository contents.
This could happen if local repository is modified or got
corrupted on the client system. This backup can not be
restored, therefore it will be deleted on the server.
System action: The specified backup object will be
deleted on the server. Processing will continue.
ANS1621E
Failed to update backup attributes on

server for local backup for filespace
namepath-namefile-name, object id object-id:object-id return code return
code.
Explanation: TSM failed to update attributes for the

named backup object on the server. The server may not
reflect correct state of the backup.
User response: Check preceding error messages in
error log for more information. Retry the operation. If
problem continues, contact your TSM administrator.

723
ANS1622I ANS1630E
ANS1622I
Number of backup objects cleaned up

on server: number number of local
snapshot resources made available
:number.
Explanation: While performing consistency check for

servers database and the local repository maintained
on the client system, reported inconsistencies were
found. Inconsistent backups cannot be restored,
therefore TSM deletes all inconsistent backup objects
and frees the space occupied in the local repository.
User response: Check error log for further details on
which objects on server were deleted. If numbers look
unusually high check your configuration and if it
continues, contact your TSM administrator.
ANS1623W
Backup of NSF DB2 database was

skipped. NSF DB2 databases not
supported.
Explanation: This version of DP for Domino plugin

does not support NSF DB2 databases.
System action: Backup of NSF DB2 databases is
skipped.
User response: Exclude NSF DB2 databases from
backup.
ANS1624W
You have chosen to proceed with the

restore operation.New logical volumes
added after backup will be removed
during this restore process. Please
restore these logical volumes manually
before performing rollforward recovery.
Explanation: Database configuration has been changed

since the previous backup by the addition of new
logical volumes. User has requested a local restore
operation which will remove these newly added logical
volumes. Please restore them after the local restore
command has completed, before performing
rollforward recovery. You can find the list of logical
volumes removed in the dsmerror.log file.
System action: This message is a warning to the user
to perform certain action after the local restore
command completes successfully.
User response: User MUST take the action specified in
this warning before proceeding with rollforward
recovery.
ANS1625I
Number of volumes to be FlashCopied:

v1
Explanation: Number of volumes to be flashcopied.

724
ANS1626E
An unexpected error was encountered

when processing a TSM for Hardware
function. TSM function name :
Explanation: None.
ANS1627E
SVC virtual disk v1 is not valid.
Explanation: The specified virtual disk is not found in

the list of virtual disks provided by the connected SVC
cluster.
System action: Process stops.
User response: Ensure that this virtual disk exists in
the SVC.
ANS1628E
The source v1 and target v2 virtual disks

are in different SVC clusters.
Explanation: The SVC source and target virtual disks

have to be assigned to the same SVC cluster.
User response: Ensure that the source and target
virtual disks are in the same SVC.
ANS1629E

are of different size.

have to be of the same size.
virtual disks are the same size.
ANS1630E
An error was returned calling an

operation of the Common Interface
Model(CIM). TSM function name :
function-desc TSM CIM return code:
0xCIM-rc TSM file : file-name
(line-number)
Explanation: An error occurred when calling a CIM

operation of the disk subsystem.
User response: Please see the section about the CIM
return codes and their descriptions in the product
publication.
ANS1631E ANS1656I
ANS1631E
A memory allocation error has occurred

in file filename, line number linenumber.
Explanation: Enough memory was not available to

continue processing.
real and virtual memory. Close unnecessary
applications.
ANS1651I
Explanation: The backup operation for the object was

successful.
System action: This message is for auditing purposes
only.
User response: This message is for auditing purposes
only.
ANS1652I
ANS1632I
Changing copyType to copy for

LOCAL SAN Volume Controller
incremental backup operation.
Explanation: When backup destination is LOCAL,

snapshot incremental type defaults to COPY type
operation. This is due to the lack of INCREMENTAL
snapshot support on SAN Volume Controller.
Backed Up: fshlll
Archived: fshlll
Explanation: The archive operation for the object was

successful.
only.
only.
System action: This message is informational.

User response: Do not specify incremental option
for LOCAL backups when using SAN Volume
Controller or use any. This will allow TSM to pick the
appropriate default value of copyType.
ANS1647I
DB2 Partition Volume Information:

Database configuration Name: db2 cfg
name Database Partition Number: db2
partition num DB2 Host Name: db2 host
name TSM Node Name: tsm node name
Volume List: volume list
Explanation: None.
ANS1648I
DB2 Backup Host Volume Information:

Database configuration Name: db2 cfg
name Backup Host Machine Name: db2
partition num Backup TSM Node Name:
db2 host name Volume List: volume list
Explanation: None.
ANS1650I
Command: command-string
ANS1653I
Updated: fshlll
Explanation: The update operation for the object was

successful.
only.
only.
ANS1654E
Failed: fshlll
Explanation: The backup, archive, restore or retrieve

operation for the object failed.
only.
only. For information about the failure refer to the TSM
Backup-Archive Client error log.
ANS1655I
Restored: fshlll
Explanation: The restore operation for the object was

successful.
only.
only.
Explanation: The command string listed in the

messagewas issued by the TSM Backup-Archive client.
ANS1656I

only.
Explanation: The retrieve operation for the object was

successful.

only.

only.
Retrieved: fshlll

only.
725
ANS1657I ANS1753E
ANS1657I
Expired: fshlll
Explanation: The active version of the object was

expired in the TSM database.
only.
only.
ANS1658I
Deleted: fshlll
Explanation: The object was deleted from the TSM

database.
only.
only.
ANS1659I
Skipped: fshlll
Explanation: The object was skipped by the user

during backup or archive processing.
only.
only.
ANS1660I
Excluded: fshlll
Explanation: The object was excluded from backup or

archive processing.
only.
only.
ANS1661I
Unchanged: fshlll
Explanation: The object has not changed since the last

incremental backup was performed and does not need
to be resent.
only.
only.
ANS1662I
Agent Node: agent_node Target Node:

target_node
Explanation: Proxy nodes information.

System action: None
User response: None
726
ANS1751E
Error processing filespace name: The file

system can not be accessed.
Explanation: The client is unable to access the file

system. Two common reasons for this are the account
under which the client is running does not have access
to the root of the file system, or the file system does
not exist.
System action: The inaccessible file system is skipped.
Processing continues with the next file system.
User response: Check the error log for additional
messages that might yield additional information about
the problem that prevents access to the file system.
Correct the problem, then retry the operation. If the
account does not have access to the file system, then
either the system administrator needs to grant access,
or an account that has access to the file system must be
used. If the file system does not exist, then remove or
correct the file system specification.
ANS1752E
The file system can not be accessed.
Explanation: The client is unable to access the file

system. Two common reasons for this are the account
under which the client is running does not have access
to the root of the file system, or the file system does
not exist.
System action: The inaccessible file system is ignored.
the problem that prevents access to the file system.
Correct the problem, then retry the operation. If the
account does not have access to the file system, then
either the system administrator needs to grant access,
or an account that has access to the file system must be
used. If the file system does not exist, then remove or
correct the file system specification.
ANS1753E
File space filespace name was backed up

by an older client version, and cannot
be restored with this client version. The
file space will be skipped.
Explanation: The backup set format in earlier client

versions for SYSTEM STATE and SYSTEM SERVICES is
incompatible with the current client version. Those file
spaces will be skipped. The restore might appear to
pause while the client skips past the objects in those
file spaces. Other remaining file space data will be
restored.
System action: Objects in this file space are skipped.
Other remaining file space data will be restored.
User response: Restore this specific file space in the
backupset with a prior level client.
ANS1754E ANS1763W
ANS1754E
File space filespace name cannot be

restored when ASNODENAME option
is in affect. The file space will be
skipped.
Explanation: System state data of another node should

not be restored to a different node. Those file spaces
will be skipped. The restore might appear to pause
while the client skips past the objects in those file
spaces. Other remaining file space data will be restored.
System action: Objects in this file space are skipped.
Other remaining file space data will be restored.
User response: Remove ASNODENAME option before
restoring this specific file space in the backupset or use
the node name that was used to backup system state
data to restore.
ANS1756W
The Journal for backup-specification has

been reset: The server filespace was
deleted since the last backup completed.
Explanation: The client has reset the journal because

the corresponding server filespace was deleted since
the last backup completed.
System action: The journal is reset, the current backup
wont use the journal, and the journal wont be
available for backup until a full incremental backup
successfully completes.
ANS1759W
Explanation: The client has reset the journal for the

specified file system because the node policy set was
updated since the last backup completed.
ANS1760I


ANS1758W


Journal for backup-specification enabled

for node nodename and server
servername
Explanation: The journal for the specified file system

is now valid and will be used by the next full
incremental backup by the specified TSM node and
server.
System action: The next full incremental backup of
the file system will use the journal.
ANS1761I

ANS1757W

been reset: The policy set was updated
since the last backup completed.
Journal for backup-specification will be

enabled upon successful completion of
the backup.
Explanation: An active but invalid journal is present

for the file system being backed up. Once the backup
successfully completes the journal will available for use
by the next full incremental backup of the file system
with the same TSM node and server.
ANS1763W
Unable to unmount snapshot mount

point snapshot mountpoint during cleanup
of snapshot snapshot of volume
volume.Error is error.Operation will
continue. Please manually unmount,
remove the snapshot mount point
directory and delete the snapshot after
backup is completed.
Explanation: During the termination phase of TSM

client operation, it was not possible to unmount the
snapshot for some reason. However, TSM operation
was completed successfully.
System action: Processing continues, and the unmount
error is ignored.
User response: Please manually cleanup the snapshots
as follows: Query the snapshot: snapshot -q -c: <source
FS>. Snapshot name will be of the format:
tsmxxxxxxxxxx. Check if it is mounted: df -k | grep
727
ANS1764W ANS1767E
tsmxxxxxxxxxx. Unmount the snapshot: umount -f
tsmxxxxxxxxxx. Remove snapshot mount point: rmdir
tsmxxxxxxxxxx. Delete the snapshot: snapshot -d
/dev/tsmxxxxxxxxxx. If snapshot delete fails with
Device Busy or some other error, unmount the
snapshot source filesystem: umount -f <source FS>.
Retry snapshot delete: snapshot -d
/dev/tsmxxxxxxxxxx. Check if any logical volumes are
remaining: ls -l /dev/tsm*. Remove any remaining
logical volumes: rmlv -f tsmxxxxxxxxxx. Remount
source file system, if previously unmounted: mount
<source FS>.
ANS1764W
Unable to remove the snapshot mount

point directory snapshot mountpoint
during cleanup of snapshot snapshot of
volume volume.Error is error.Operation
will continue. Please manually remove
the snapshot mount directory and delete
the snapshot after backup is completed.

<source FS>.
ANS1766W
Unable to remove the snapshot logical

volume during cleanup of snapshot
snapshot of volume volume.Error is
error.Operation will continue. Please
manually remove the snapshot logical
volume after backup is completed.

client operation, it was not possible to remove the
mount point directory for the snapshot for some
reason. However, TSM operation was completed
successfully.

client operation, it was not possible to remove the
snapshot logical volume for some reason. However,
TSM operation was completed successfully.
System action: Processing continues, and the rmdir

error is ignored.
System action: Processing continues, and the snapshot

logical volume remove error is ignored.

<source FS>.

<source FS>.
ANS1765W
ANS1767E
Unable to delete the snapshot during

cleanup of snapshot snapshot of volume
volume.Error is error.Operation will
continue. Please manually delete the
snapshot after backup is completed.

client operation, it was not possible to delete the
snapshot for some reason. However, TSM operation
was completed successfully.
Unable to create a snapshot logical

volume using command: cmd.Error is
error.Please ensure that the volume
group has sufficient free partitions to
fulfill the allocation request.
Explanation: During the initialization phase of TSM

client operation, it was not possible to create a logical
volume for the snapshot.
System action: Processing continues, and the snapshot

delete error is ignored.
System action: Processing continues, and the create

snapshot logical volume error is ignored. TSM
operation will be performed without the snapshot.

User response: Please ensure that the volume group

has sufficient free partitions to fulfill the mklv
728
ANS1768E ANS1800W
allocation reuest and retry the operation.
ANS1768E
TSM was unable to find space for a new

snapshot. TSM function name :
object-name. The error code indicates the reason for the

failure. This information can be used to diagnose the
problem.
System action: The TSM client may or may not fail
the operation, depending on the error code.
more information.
Explanation: None.
User response: Previous backups may still be
pending. If problem persists contact the TSM
administrator with the information provided in this
message.
ANS1770E
Unable to resolve address . Error = ,
ANS1798W
An error occurred while accessing

encrypted data of the object object-name,
skipping object. Windows system error
code error, reason error-reason
Explanation: An error occurred while processing

encrypted data of the object. The error information
Explanation: The system was not able to get the

TCP/IP v6 address.

more information.
User response: Verify the address shown is a TCP/IP

v6 address and can be resolved with ping or ping6.
ANS1796I
The short name for fullpath-name could

not be set to original short name
file-name: Windows function func-name
failed with return code return-code
Explanation: The client cannot set the short name for

the specified object. This is usually because the short
name is already in use by another object located in the
same directory. Another possible reason is that the
account under which the client is running does not
have the SE_RESTORE_NAME privilege.
System action: The short name for the specified object
is not set. The object will retain the default short name.
Otherwise processing continues.
User response: This message is informational and can
be safely ignored. If you require that the object be
restored with its original short name, you will need to
move or delete the conflicting object. From an
operating system command prompt, change to the
directory that contains the object you want to restore.
Then use the \dir /x\ command to identify the
conflicting object. Also make sure that you have the
SE_RESTORE_NAME privilege. If you need assistance,
see your system administrator. After the conflict has
been resolved, try to restore the file again.
ANS1797E
Function function-name received an

unexpected error from the Microsoft API
MS-function-name: rc=error while
attempting to access the object
object-name. Error occurred in file
file-name (line-number).
Explanation: An error occurred while processing the
ANS1799I
The last access date for fullpath-name

could not be reset because the file is
read-only.
Explanation: Option PRESERVELASTACCESSDATE

YES is in effect, but the TSM client was unable to reset
the last access date for the specified file because the
files read only attribute is enabled. The client cannot
reset the last access date for read only files.
System action: The last access date for the specified
file is not reset. Otherwise processing continues.
User response: This message is informational and can
be safely ignored. You might want to turn off the read
only attribute for the file so that subsequent backups
can reset the last access date. Before turning off the
attribute, you should verify that doing so will not
impact the integrity of the file or the applications that
use the file. You should also make sure that turning off
the attribute will not conflict with the file management
policies of your organization.
ANS1800W
The last access date for fullpath-name

could not be reset: function func-name
failed with return code return-code
Explanation: Option PRESERVELASTACCESSDATE

YES is in effect, but the TSM client was unable to reset
the last access date for the specified file. The message
includes the name of the function that failed and the
return code from that function.
System action: The last access date for the specified
file is not reset. Otherwise processing continues.
User response: If the problem is reproducible, obtain a
SERVICE trace that captures an instance of this
problem. Run the QUERY SYSTEMINFO command and
729
ANS1802E ANS1809W
collect the dsminfo.txt file. Contact IBM support and
report the exact text of this error message. Be sure to
provide support with the dsminfo.txt and dsmerror.log
files and (if available) the SERVICE trace.
ANS1802E
Incremental backup of file-name

finished with number failure
Explanation: This message is issued after completion

of an incremental backup operation for the named file
specification when one or more objects in that file
specification could not be backed up.
ANS1806W
Size exceeded the maximum file size

limit on your system for filespace
namepath-namefile-name of file-size.

system.
administrator.

additional messages that indicate the reasons that each
failed object could not be backed up. Take any
corrective action as suggested by the messages.
ANS1803E
Archive processing of file-space name

finished with failures.

of an archive operation for the named file specification
when one or more objects in that file specification
could not be archived.
failed object could not be archived. Take corrective
action as suggested by the messages.
ANS1804E
Selective Backup processing of file-space

name finished with failures.

of a selective backup operation for the named file
specification when one or more objects in that file
specification could not be backed up.
ANS1807E
Explanation: Unable to recall file. The recall daemon

reported an error while trying to recall a file. Look in
the recall daemons error log for more information. This
can happen if the server is down, the connection is
broken, or the file is missing on the server. It is also
possible that the migration server in the system option
file has been changed to a different server. The recall
daemon does not check the system option file for
changes once it has started.
User response: See if the server is up, and retry. If the
problem still exists, look in the error log. Also have the
workstation administrator run dsmreconcile against the
file system and see if the file shows up in the
.SpaceMan/orphan.stubs file. If system option file has
been changed, stop all recall daemons and restart the
master recall daemon to pick up the changes.
ANS1808E

failed object could not be backed up. Take any
corrective action suggested by those messages.
ANS1805E
Unable to restore symbolic link

file-name.
Unable to recall file from server due to

error from recall daemon.
The Logical Volume Snapshot Agent is

not at the correct level. It is possible
that the Client was upgraded to a newer
level but the LVSA driver was not
updated at the same time. Use the Setup
Wizard to configure either Online Image
or Open File support and choose Update
the Logical Volume Snapshot Agent.
Explanation: The selected operation requires the

current level of the Logical Volume Snapshot Agent.
Use the Setup Wizard to update the LVSA.
System action: The selected operation is not
performed.
Explanation: The client operating system is not able to

create a symbolic link because the link points to a
filename that is not given.
User response: Retry the operation after updating the

Logical Volume Snapshot Agent.
ANS1809W
User response: Try the restore on a different operating

system.
730
A session with the TSM server has been

disconnected. An attempt will be made
to reestablish the connection.
Explanation: This message is issued after the session

with the TSM server is unexpectedly lost. Some
possible reasons that this message might be issued: There is a problem with the network. - The TSM server
ANS1810I ANS1817E
was shut down. - The TSM server administrator
cancelled the client session.
System action: The client will try to reestablish a
connection with the server. If the TSM server
administrator cancelled the session, then the attempt to
reestablish the connection will fail and message
ANS1369E will be issued. If the attempt to reestablish
the connection is successful, then processing will
continue. If the attempt to reestablish the connection
fails, then the client will continue to try to reestablish a
connection according to the
COMMRESTARTDURATION and
COMMRESTARTINTERVAL client option settings.
User response: If the session was cancelled by the
TSM server administrator and you do not know why,
or if the client is unable to reestablish a session with
the TSM server, then contact your TSM server
administrator for further information. Frequent
occurrences of the ANS1809W message can indicate a
problem with the network. If this message is repeatedly
found in the dsmerror.log, investigate possible
networking trouble, such as a failing network interface
card or router problem. One common problem is the
media speed of the network adaptors: If the network
adaptors are set to auto-negotiate, try changing them
to 100%% full duplex. If the problem persists, then as
a temporary measure ask your TSM server
administrator increase the COMMTIMEOUT and
IDLETIMEOUT option settings on the TSM server. This
might reduce the frequency of this message.
ANS1810I
A session with the TSM server has been

reestablished.
Explanation: The session with the server has been

reestablished after a connection failure. This message is
usually preceded by message ANS1809W.
System action: Processing will continue.
User response: None. This message is informational
only.
ANS1813E
Explanation: The image backup operation failed. This

message is usually preceded by other messages
indicating the nature of the failure.
System action: The failing file space is skipped and
User response: Examine the messages preceding this
message and the TSM Client error log for more specific
indications about the problem. A common cause is that
a tape could not be mounted on the TSM server,
perhaps due to an insufficient number of mount points.
If there is a problem with the server, contact your
System Administrator for further assistance.
ANS1814E
TSM session could not be reestablished.
Explanation: The session with the server has been

lost. Attempts to reestablish the session were
unsuccessful. Possible causes include, but are not
limited to the following:
v The server has been halted.
Unable to start the scheduled event

event-name
Explanation: The scheduled event is no longer valid

on the server. Either the window has elapsed or the
schedule has been deleted.
System action: The client scheduler queries the server
to obtain the next scheduled event.
User response: If the problem continues, contact your
system administrator to correct the problem on the
server.
ANS1815E
Either the window has elapsed or the

schedule has been deleted
Explanation: Scheduled event was no longer valid on

the server.
System action: The client scheduler queries the server
to obtain the next scheduled event.
User response: If the problem continues, see your
system administrator to correct the problem on the
server.
ANS1816E
ANS1811S
Image Backup processing of

filespace-name finished with failures.
Invalid scheduling mode
Explanation: The mode entered for the scheduled

event was not correct.
System action: Event does not occur.
User response: Enter the correct scheduling mode and
v The network connection to the server is down.

v The communication program that TSM is interacting
with has encountered some problem.
ANS1817E
System action: Processing is stopped.
Explanation: An attempt to use the schedule function

failed because of improper authority.
User response: Check network connection to the

server. Insure that the TSM server is running. Insure
that the communication program underlying TSM is
working properly.
Schedule function can only be run by a

TSM authorized user.

User response: See the TSM authorized user for
schedule function information.
731
ANS1818E ANS1827W
ANS1818E
The SCHEDULE command is not

allowed in LOOP (interactive) mode.
Explanation: None.
User response: Retry the operation after reducing the

number of objects selected.
ANS1823E
System action: The client does not execute any

scheduled events.
User response: Start the scheduler from the OS
prompt. For example: dsmc schedule Windows clients
can also use the client scheduler service. Read the client
manual for information on how to use the SCHEDULE
command and how to use the TSM client scheduler
features.
ANS1819E
The TSM server was unable to register

the address for this node.
Explanation: This is a rare situation, and is usually an

indication of a problem with the TSM server.
Ask your TSM server administrator to check the TSM
server activity log for any messages that might indicate
a problem on the server. Try to correct any indicated
problems, then try the operation again. If the problem
assistance.
ANS1820E
Command line options must be

preceded by a -
Explanation: An option was specified without a ''

delimiter.
User response: Enter the command again with a dash
preceding each option.
ANS1821E
Unable to start POSTSCHEDULECMD/

PRESCHEDULECMD command
Explanation: The requested action required a new

process to be created. Either an option or a schedule
action that requested an operating system command
to be executed was entered.
System action: Request is ignored.
User response: Remove the request from the options
file or the schedule defined on the server.
ANS1822E
Too many objects were selected for

restore. Please select less than
max_objects objects
Explanation: The restore cannot be performed,

because too many objects were selected.
System action: The restore is not performed.
732
The TESTFLAGS or TRACEFLAGS

option specifies unknown flag name
keyword or the value supplied is invalid
for the named keyword.
Explanation: Either the testflag or traceflag name is

incorrectly spelled, or the value supplied for that flag is
not valid.
System action: If the TESTFLAGS or TRACEFLAGS
option was specified in the client options file or on the
command line during client initialization, the the client
program does not start. If the option was specified
from the command line client while running in LOOP
(interactive) mode, then the operation does not run.
User response: Correct the TESTFLAGS or
TRACEFLAGS flag name or correct the value specified
for the TESTFLAG keyword shown in the message.
These options are typically used at the direction of IBM
technical support or as specified in the TSM Problem
Determination Guide. If you are not sure which flag
names to use, review the TSM Problem Determination
Guide for additional information or contact IBM
ANS1824E
Invalid trace file name (name too long).
Explanation: A TRACEFILE option in the preferences

files used a file name that is too long.
System action: Client program did not initialize.
User response: Change the file name used as the
TRACEFILE so that it is equal to or less than 255
characters in length.
ANS1826E
Unable to open trace output file

file-name.
Explanation: A TRACEFILE option in the user

configuration file or on the command line used a
directory path and file-name combination to which you
do not have write access.
User response: Change the TRACEFILE value so that
it is a location to which you have write access.
ANS1827W
Directories cannot be selected with the

table of contents currently loaded on the
server.
Explanation: The table of contents that is currently

loaded on the server for this volume does not contain
objects corresponding to the one and only point-in-time
backup. It contains an incomplete point in time or
multiple points in time.
ANS1828E ANS1839E
System action: The directory is not selected for
restore.
space. If unsuccessful, see your system administrator.
User response: To be able to select an entire directory

for restore, select Use Latest or Use Point in Time
from the Point in Time dialog.
ANS1835E
ANS1828E
Screen size is too small for using the

PICK option.
Explanation: You cannot use the PICK option on a

workstation that has a screen smaller than 20 characters
across and 10 lines down.
System action: TSM did not complete the operation.
User response: Retry the operation using a
workstation that has a screen with the minimum size,
or do not use the PICK option.
ANS1830E
Unable to write to trace file tracefile.

Tracing disabled.
Explanation: An error occurred when writing to the

specified tracefile.
System action: Tracing is disabled. Processing
continues.
User response: Ensure the device that the tracefile
access is available and has sufficient space for the
tracefile. Retry the command.
Explanation: Either the password is not stored locally,

or it was changed at the server.
System action: TSM prompts you for the password if
TSM is running in the foreground.
User response: If TSM was running as a background
process, issue any TSM command from the foreground.
Enter the password in answer to the prompt. Then try
your background TSM command again.
ANS1836S
Password expired. The administrator for

this system must run TSM to update the
password.
Explanation: The password expired.

User response: The administrator for this system must
update the password.
ANS1832S
Unable to send generated password

using MailProg option
MailProg file-name failed with return

code = value.
Explanation: An error occurred with the specified

MailProg file-name.
User response: Check the return code for the
MailProg file-name. See your system administrator if
you are unable to resolve the problem.
ANS1837S
ANS1831E
PASSWORDACCESS is GENERATE,
but password needed for server
server-name. Either the password is not
stored locally, or it was changed at the
server.
File space filespace-name is ignored.

Processing continues.
Explanation: The specified filespace-name in the system

options file is invalid.
operation.
User response: Check the file space in the system
options file and use a valid file space. Retry the
operation.
ANS1838E
Error opening user specified options file

filespace-name .
Explanation: TSM cannot send the file containing the

generated password to the user ID specified in the
MailProg option.
Explanation: The specified options file-name could not

be located or opened.
System action: TSM attempts to open default option

file.

the error log for reasons why the file was not sent to
the user ID.
User response: Make sure specified option file exists

and is valid.
ANS1834S
Unable to write to file-name for storing

password
Explanation: TSM cannot write to the specified

file-name.
ANS1839E
Cannot read password.
Explanation: An error occurred in setting up the input

file (for example, the terminal) to be read.
User response: Check the attributes of the terminal.
User response: Check access permissions and disk

733
ANS1852E ANS1871W
ANS1852E
Server could not load the table of

contents. Status: status reason: reason
Explanation: A failure occurred when the server

attempted to load a file-level Table of contents for an
NDMP volume. No file-level queries can be performed
against the volume until the problem is solved.
System action: The table of contents is not loaded.
User response: Check the server Activity Log to
determine the cause of failure. Retry the operation after
correcting the problem.
ANS1853E
Server could not load the Table of

Contents. Status: status
Explanation: A failure occurred when the server

attempted to load a file-level Table of contents for an
NDMP volume. No file-level queries can be performed
against the volume until the problem is solved.
System action: The table of contents is not loaded.
User response: Check the server Activity Log to
determine the cause of failure. Retry the operation after
correcting the problem.
ANS1862W
No table of contents information is

available on the server for this volume.
Explanation: No objects for the selected volume exist

on the server that were backed up with table of
contents information. Consequently no file-level queries
can be performed against the volume.
System action: none
User response: If file-level information is desired, use
TOC option during backup.
ANS1865E
Session rejected: Named Pipes

connection failure.

using Named Pipes communications failed. This might
have occurred if an incorrect NAMEDPIPENAME was
specified in the options files or if your system
administrator canceled a backup operation.
ANS1867E
The server generated a CRC for verb

type CRC verb which does not match the
received verb verb received.
Explanation: A cyclic redundancy check (CRC) failed

between TSM client and server communication.
System action: The current object is skipped.
User response: This is an unusual condition, and
could indicate a communications problem between the
TSM client and server. Try the operation again. If the
problem persists, contact IBM for further assistance.
ANS1869E
The NDS object requires its parent, or

container, to be present before this
object can be restored. Try first restoring
the parent of this object.
Explanation: SMS requires the parent of the object

(container) to be present before the child or object can
be created.
User response: Retry restoring, but at least one level
up. For instance, restore 'dir\.o=ibm\*' instead of
'dir\ou=gpl.o=ibm\*'.
ANS1870E
NDS transport failure FFFDFEAF has

occurred. Contact Novell technical
Explanation: The failure is reported from the NDS

ResolveName() function. It indicates a communication
failure between TSANDS and the partition on which
the object resides.
User response: Check the TSM client README file for
information on required NetWare software levels, and
verify that those levels are installed. Reducing the
RESOURCEUTILIZATION client setting might also
help avoid this error. If the problem persists, contact
Novell technical support for further assistance
regarding the FFFDFEAF return code.
The server CRC version is server CRC
version which does not match the client
version client CRC version.
ANS1871W

server comes back up and retry the operation. Ensure
that the value specified on the NAMEDPIPENAME
option is the same as the one used by the server. If the
problem continues, contact your system administrator
for further help.
Explanation: This is a rare situation. The server and

client are using different versions of cyclic redundancy
check (CRC) algorithms.
System action: Processing continues without CRC
checking.
User response: Clients can be no more than one
version downlevel from the TSM server. Make sure the
client and server are at compatible levels. The
command line client displays both client and server
734
ANS1872E ANS1878E
versions when the client starts and connects to the
server. The QUERY SESSION command will also
display the server version. From the GUI, use the
\Help/About\ menu item to identify the client
version, and the \File/Connection Information\
menu item to identify the server version. If the client
and server versions are incompatible, then the TSM
server administrator can turn off CRC checking for
your node.
ANS1872E
Unable to connect to NetWare target

service server-name. Make sure the TSA
NLM is loaded on the specified
machine.
Explanation: TSM interacts with the Target Service

Agent (TSA) and the connection cannot be made to the
Netware server-name.
User response: Ensure that the TSA is loaded and
retry the TSM command.
ANS1876E
Explanation: The NetWare SMS return code was

unexpected.
User response: Messages ANS1874E, ANS1876E and
ANS2025E can all be issued due to related problems.
These problems might include: 1) The NetWare server
has an insufficient number of NetWare user licenses. 2)
The NetWare license files are corrupt. The NetWare
license files can be reinstalled. 3) A NetWare typeful
name is not being provided at the NetWare User
prompt. 4) The TSM password file is corrupt. In this
situation, quit all TSM processes, delete or move the
*.PWD files that are located in the TSM installation
directory, then load dsmc and run the following
commands: QUERY SESSION QUERY TSA QUERY
TSA NDS.
ANS1877E
ANS1873E

utility function func-name failed with
error error

processing a system object. The error information
more information.
ANS1874E
Login denied to NetWare Target Service

Agent server-name.
Explanation: The connection to the Target Service

Agent (TSA) requires a NetWare user name and a
password. The password you entered at the prompt
may be incorrect.
User response: Retry the TSM command, supplying
the correct LAN password.
ANS1875E
Unable to connect to target service. Out

of memory.
Explanation: Not enough memory to connect to the

Target Service Agent (TSA).
TSM is unable to connect to the

NetWare target service. NetWare SMS
return code = value.
The parsed string is too long for TSM to

process and has been truncated to
prevent a buffer overflow.
Explanation: This is a rare condition. A very long

string would have to be entered by the user in a
command line, dsm.opt file, or filelist. This string
exceeds the maximum input string size of 1024 bytes.
System action: TSM truncated the string to the
maximum possible length of 1024, then continued with
the operation. The operation may fail later due to this
truncation.
User response: Check the client error log for other
messages that might have been logged after this
message was written, and take any corrective action
suggested by those messages. If the problem persists,
contact IBM support for further assistance.
ANS1878E

Service service-name and its dependent
services could not be stopped.

processing a system object. The service listed in the
message and all of its dependent services could not be
stopped. Processing cannot complete until the service is
stopped.
User response: Manually stop the service and retry
the operation.
User response: Either add memory to the server or

free memory by unloading some programs, or by
restarting the server.
735
ANS1879E ANS1895I
ANS1879E
A NetWare NDS error occurred during

restore processing: object
nds_objectnds_object TSA error tsa_error,
tsa_error_text
Explanation: TSM received an unexpected error from

the Novell TSA interface. All TSA errors between
0xFFFDFE70 and 0xFFFDFEFF, inclusive, can generate
this error message.
System action: The object is skipped. Processing
continues.
User response: Check the Novell web site for any
additional information about the error, as a fix might
already be available. Contact Novell technical support
ANS1880E
TSA Connect error,

NWSMConnectToTargetService
TSA_Target_Service password file
password_file. Userid = NetWare_userid
failed with cc = TSA_ccode

the Novell TSA interface while processing the userid
and password from NWPWFILE.
System action: If the failure is a 'Login Denied' the
user will be prompted for a Novell NetWare Userid
and Password, and a password file will be created.
User response: The cc is returned from the TSA which
belongs to Novell NetWare. If you get cc = FFFDFFD7
'Login Denied', please check the following:
The user-id has been disabled.
System action: User will be prompted for Novell

NetWare Userid and Password, and password file will
be created.
User response: The file can be corrupted via another
application or hardware failures. If problem is
persistent contact your service representative. A copy of
the corrupted password file will be needed. This
corrupted file must be preserved before you enter a
new userid and password, because TSM will overwrite
the corrupted file with correct information.
ANS1882E
Explanation: The service could not be stopped by the

program.
User response: Manually stop the service and retry
the operation.
ANS1891W
The user-id has insufficient rights to files and

directories.
The user-id specified has a login restriction based
on time-0f-day.
The user-id specified has a Network address
restriction.
The user-id specified has a login restriction based
on number of concurrent connections.
NetWare is not allowing logins (DISABLE LOGIN
was issued at the console).
If you are unable to determine what is wrong, report
the problem to your service representative.
ANS1881E
TSM is unable to use NWPWFILE

password_file to connect TSA target
service TSA_Target_Service, the file is
corrupted.
Explanation: TSM could not use the NWPWFILE to

connect to Novell TSA interface. The file was
corrupted.
736
SUBDIR is not a valid option when

using FILELIST, SUBDIR will be
ignored.
Explanation: When Specifying FILELIST each entry is

a single object and so SUBDIR will not apply.
System action: The option SUBDIR is ignored.
User response: You may have either a -FILELIST or
SUBDIR on this command, but not both.
ANS1892W
The user-id/password is invalid or expired.

The user-id has inadequate security access.
Unable to stop service service-name;

error error
Expire command is not allowed on the

TSM journaled filespace filespace.
Explanation: You cannot expire files from the server

on a TSM journaled filespace.
System action: The expire command will not work on
this filespec
User response: If you want to expire this filepec
remove it from the local filesystem.
ANS1895I
Highest macro return code was return

code value.
Explanation: This message is issued after all

commands in a client macro have completed. The
return code represents the highest return code that was
issued during processing of the macro. In order of
increasing severity, the return code meanings are:
0 - The command completed successfully
4 - One or more files were skipped
8 - One or more warning messages were issued
12 - One or more error messages (except for skipped
files) were issued
User response: For return codes other than 0, the user
may wish to verify the results of the client operation(s)
ANS1896I ANS1903W
and take diagnostic and repair actions, as necessary.
ANS1896I
***** Restored number objects *****
Explanation: Indicates the number of objects TSM has

restored. During a restore session, the running total is
periodically printed to the screen of a command line
client.
System action: Continue with restore.
ANS1897I
***** Retrieved number objects *****
ANS1901I
Highest return code was return code

value.
Explanation: This message indicates the highest return

code of all the client commands that were executed. In
order of increasing severity, the return code meanings
are:
files) were issued
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
client.

may wish to verify the results of the client operation(s)
System action: Continue with retrieve.
ANS1902E

ANS1898I
***** Processed count files *****
Explanation: TSM has processed the specified number

of files.
ANS1899I
***** Examined count files *****
Explanation: TSM has examined the specified number

of files.
ANS1900I
Return code is return code value.
Explanation: The return code has been issued for the

preceding client command. In order of increasing
severity, the return code meanings are:
files) were issued
The return code indicates the highest severity message
that was issued during execution of the client
command. For a scheduled event, the event will be
considered successful if the return code is 0, 4, or 8.
The event will be considered to have failed if the return
code is 12.
may wish to verify the results of the client operation
The PRESCHEDULECMD command

failed. The scheduled event will not be
executed.

PRESCHEDULECMD option must complete
successfully in order to execute the scheduled event. If
the command completed with a return code of 0 (zero),
it is considered to have completed successfully. If the
command completed with any other return code, it is
considered to have failed. If the command failed then
the scheduled event is not executed.
scheduled event, and the result code of the scheduled
event will be 12.
caused the command to fail. If it is not necessary for
the command to complete before starting the scheduled
event, then consider using the PRENSCHEDULECMD
option, which does not require that the command
complete successfully. If a non-zero return code is
normal for this command, then consider wrapping the
command in a script that always exits with a return
code of zero.
ANS1903W
The POSTCHEDULECMD command

failed.

POSTSCHEDULECMD option completed with a
non-zero return code, then the scheduled event is
considered to have completed successfully, but with a
warning-level result. Note that the result of the
POSTSCHEDULECMD command will not supercede a
higher result from the scheduled client command. For
example, if the scheduled client command completed
with a return code of 12, the scheduled event will be
considered to have completed with a return code of 12,
regardless of the outcome of the POSTSCHEDULECMD
command.
737
ANS1904E ANS1914E
System action: At a minimum, the result code of the
scheduled event is 8.
caused the command to fail. If it is not necessary for
the command to complete before posting the result of
the scheduled event, then consider using the
PRENSCHEDULECMD option. If a non-zero return
code is normal for this command, then consider
wrapping the command in a script that always exits
with a return code of zero.
ANS1904E
The archive description may not contain

any wildcard characters like ? or *.
Explanation: Descriptions for archive files must not

contain wildcard characters.
User response: Enter an archive description that does
not contain wildcard characters.
ANS1905E
There was a NetWare SMS error

processing filespace-name
path-namefile-name: error-text

the Novell SMS interface.
System action: The object is skipped. Processing
continues.
User response: Check the Novell web site for any
additional information about the error, as a fix might
already be available. Contact Novell technical support
ANS1906I
Destination must be specified for this

operation when using FROMNODE.
assistance. For Unix or Windows: This error indicates

an authorization problem. Contact your TSM server
administrator for assistance. If the problem still cannot
be resolved, contact IBM technical support for further
assistance.
ANS1908I
The scheduled command completed

successfully.
Explanation: The scheduled command completed with

return code of zero, which is interpreted as success.
System action: The scheduled event is successful. The
result code for the event is 0.
ANS1909E
The scheduled command failed.
Explanation: The scheduled command completed with

a non-zero return code, which is interpreted as failure.
System action: The scheduled event is failed. The
result code for the event is 12.
code of zero.
ANS1912E
An invalid registry hive was specified.
Explanation: The specified registry hive is invalid.

operation.
ANS1913E
An invalid registry subkey was

specified.
Explanation: The user must specify a destination with

a Restore/Retrieve command when using FROMNODE
processing.
Explanation: The specified registry subkey is invalid.
User response: Retry the Restore/Retrieve command

with a destination specified.

operation.
ANS1907E
ANS1914E
An error occurred while trying to

perform an object merge operation on
the server.
Explanation: For NetWare clients: The TSM server is

unable to perform a NetWare long name conversion.
For Unix or Windows image backup: The group used
to store associated image components could not be
closed.
User response: For NetWare: It is possible that a more
current level of the TSM server can perform the
conversion. Contact your TSM server administrator for
738
The specified subkey isnt valid for the

specified hive.
Explanation: The specified registry subkey is invalid

for the specified registry hive.
operation.
ANS1915E ANS1926E
ANS1915E
Too many arguments specified for the

BACKUP REGISTRY command.
ANS1921E

RESTORE EVENTLOG command.
Explanation: Too many arguments were specified for

the BACKUP REGISTRY command.

the RESTORE EVENTLOG command.

operation.

operation.
ANS1916E
ANS1922E

RESTORE REGISTRY command.
Too few arguments specified for the

BACKUP EVENTLOG command.

the RESTORE REGISTRY command.
Explanation: Too few arguments were specified for

the BACKUP EVENTLOG command.

operation.

operation.
ANS1917E
ANS1923E

BACKUP REGISTRY command.

RESTORE EVENTLOG command.

the BACKUP REGISTRY command.

the RESTORE EVENTLOG command.

operation.

operation.
ANS1918E
ANS1924E

RESTORE REGISTRY command.
The specified system object is not valid.
Explanation: The specified system object is not valid.

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.
ANS1920E
ANS1926E

BACKUP EVENTLOG command.
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.
739
ANS1928E ANS1937E
ANS1928E
Server-initiated sessions are not

available in the LAN-free mode.
Explanation: Conflicting options

SESSIONINIT=serveronly and ENABLELANFREE=yes
were specified. This combination is not allowed.
keys were previously restored but the system was not

restarted.
User response: Use client-initiated sessions or disable

LAN-free.
User response: This error occurs because the registry

key or keys being replaced are exclusively held by
another process. This can happen if the registry keys
were previously restored but the system was not
rebooted. Reboot the system and attempt the restore
operation again.
ANS1929E
ANS1933E

key.
Explanation: The active registry key cannot be copied

to the ADSM.SYS staging directory.
System action: The registry backup operation stops.
User response: Check the space available on the
Windows boot partition to ensure there is room to
contain a copy of the Windows registry. This might
require several megabytes of free space. Also check the
Windows permissions on the ADSM.SYS staging
directory and ensure that the Windows user which you
are using to run TSM has full access to that directory
and its contents.
ANS1930W
TSM Express client view not supported

with a TSM Enterprise server.
CLIENTVIEW option ignored.
Explanation: The TSM Express client view is only

supported when going to a TSM Express server. When
a TSM Express client connects to a TSM Enterprise
server, the CLIENTVIEW option is ignored, and the
TSM Standard client view is displayed instead.
System action: The CLIENTVIEW option is ignored
and the TSM Enterprise client view is displayed.
User response: If you intend to use the TSM
Enterprise server, then update your CLIENTVIEW
option to a value of STANDARD. Otherwise, update
your TCPSERVERADDRESS option to point to your
TSM Express server.
ANS1931E
An error saving one or more eventlogs.
Explanation: An error occurred saving one or more

eventlogs.
Error accessing file or device name.
Explanation: An error has occurred while accessing

the file or device.
System action: Backup set operation is not completed.
User response: Verify that the file or device exists and
is accessible.
ANS1934E
Backup set name not found.
Explanation: The backup set name was not found on

the server.
System action: The backup set operation is not
processed.
User response: Verify that the backup set name is
correct.
ANS1935E

BACKUP NTDS command.

the BACKUP NTDS command.
operation.
ANS1936E
Not enough arguments specified for the

Explanation: Not enough arguments were specified

for the BACKUP NTDS command.
operation.

operation.
ANS1932E
An error occurred replacing one or more

registry keys.
Explanation: The registry key or keys being replaced

are exclusively held by another process. The registry
740
ANS1937E
No NTDS server name specified for the

Explanation: No NTDS server name was specified for

the BACKUP NTDS command.
User response: Specify NTDS server name at the
command and retry the operation.
ANS1938E ANS1946W
ANS1938E
NT Active Directory is not supported in

this OS level.
ANS1943E
The operation is not supported:

Downlevel server version.
Explanation: NT Active Directory is not supported in

this OS level.
Explanation: The operation cannot be performed

because server version is downlevel.
User response: Install Active Directory before

performing backup operation.
User response: Use correct server version.

ANS1944E
ANS1939E
File Replication Service backup failed.
Explanation: IBM Tivoli Storage Manager encountered

an error while backing up files under control of the
Windows 2000 File Replication Service
Error accessing file or device.
Explanation: An error has occurred while accessing

the file or device.
System action: Backup set operation is not completed.
User response: Verify that the file or device exists and

is accessible.
User response: Examine the Windows 2000 File

Replication Service Event log to insure the File
Replication Service is operating properly. Restart the
service and retry the backup operation.
ANS1945E
ANS1940E
File Replication Service restore failed.

an error while restoring files under control of the
service and retry the restore operation.
ANS1941E
System Volume backup failed.

an error while backing up files of the Windows 2000
System Volume
Replication Service Event log to insure the system
volume was successfully initialized. Restart the service
and retry the backup operation
ANS1942E
System Volume restore failed.

and retry the restore operation.
The long namespace has been removed

from the local filespace. If you wish to
proceed with the backup/archive
operation, rename your filespace on the
server.
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
up the volume using the short names, rename the
filespace on the server. If you would like to back up
using long names, add the long namespace support
back to the volume in question.
User response: Add the long namespace support to
the volume or rename(remove) the corresponding
server filespace.
ANS1946W
File exists, skipping
Explanation: The client tried to restore or retrieve the

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

specified directory, but the directory already existed in
the target restore location and the user chose not to
replace the existing directory.
System action: The directory is skipped, a message is
User response: The directory was skipped because
either REPLACE NO was in effect, causing all existing
files and directories to be skipped, or REPLACE
PROMPT was in effect, and when prompted, the user
chose to skip this directory or all existing directories
and files. No additional action is necessary if the
decision to skip the directory was deliberate. Otherwise
the operation can be retried using either REPLACE
ALL (automatically replace existing directories and
files) or REPLACE PROMPT (prompt the user whether
to replace the directory).
ANS1948E
The Microsoft volume shadow copy

system components could not be
queried.

an error while querying the system writers under
control of the Windows volume shadow copy service.
The TSM error log and Windows event log might
contain additional information about this error.
User response: Try the operation again. If the error
persists, review the TSM error log and Windows event
log for information related to this error. You might
need to restart the volume shadow copy service, then
try the operation again. It might be necessary to reboot
the machine to clear the volume shadow copy error
state.
ANS1949E
Microsoft volume shadow copy

snapshot initialization failed.

an error while initializing the Microsoft Volume
Shadow Copy Service for backup or restore. The TSM
error log and Windows event log might contain
additional information about this error.
persists, review the TSM error log and Windows event
log for information related to this error. Use the
Windows command VSSADMIN LIST WRITERS to
determine the status of the Volume Shadow Copy
service. It might be necessary to reboot the machine to
clear the volume shadow copy error state.
ANS1950E
Backup using Microsoft volume shadow

copy failed.

an error while performing a backup operation using the
Microsoft volume shadow copy service. The TSM error
log and Windows event log might contain additional
information about this error.
User response: Review the TSM error log and
Windows event log for information related to this error.
Restart any failing system service indicated in the
Windows event log. Restart the volume shadow copy
Service. You can use the Windows command
VSSADMIN LIST WRITERS to determine the status of
the volume shadow copy service. It might be necessary
to reboot the machine to clear the Volume Shadow
Copy error state.
ANS1951E
Restore using Microsoft volume shadow

copy failed.

an error while restoring with the Microsoft Volume
Shadow Copy Service.
User response: Review the TSM error log and
Windows event log for information related to this error.
Restart any failing system service indicated in the
Windows event log. Restart the volume shadow copy
Service. You can use the Windows command
VSSADMIN LIST WRITERS to determine the status of
the volume shadow copy service. It might be necessary
to reboot the machine to clear the Volume Shadow
Copy error state.
ANS1952E
Invalid symbolic link destination

file-name entered
Explanation: You entered a restore/retrieve

destination file-name specification that is a symbolic
link. To restore to symbolic link, make sure you set the
followsymbolic option to yes. Also, check where this
symbolic link points. You can restore/retrieve to a
symbolic link that points to an existing object.
User response: Enter a correct file specification.
ANS1954E
Backup processing of file-space name

finished with failures.
Explanation: This message indicates that the file

system backup has completed, but encountered errors
during backup processing.
742
ANS1956E ANS1971E
additional messages related to errors in backing up the
file system. Take any corrective action as suggested by
the messages.
ANS1956E

BACKUP GROUP command.

the BACKUP GROUP command.
ANS1961E
Could not detect any installation of the

WebSphere Deployment Manager or
Application Server.
Explanation: The application could not detect a

supported WebSphere component installed. At this
time, only the WebSphere Deployment Manager and
Application Server are supported.

operation.
User response: Verify that the intended WebSphere

component is installed on this machine, and retry the
operation.
ANS1957E
ANS1962E
Showmembers and inactive are

mutually exclusive parameters on a
query.
Explanation: Showmembers and inactive are mutually

exclusive parameters on a query.< /p>
User response: Specify one of the mutually exclusive
parameters on the query
ANS1958W
No base group found, attempting a full

backup.
Operation Failed.
Explanation: The attempted operation on the

WebSphere component failed.
User response: Check the error log for more details.
ANS1963E
WAS Filesweep failed for filespec name
Explanation: Could not obtain the list of files to be

backed up for the indicated filespec
Explanation: A differential backup requires a previous

full backup to have been performed.< /p>
User response: Verify that the process has access to

the indicated filespec and retry the operation.
System action: Processing continues, and a full

backup is attempted.
ANS1964E
User response: None. Perform a full backup before

attempting a differential backup
ANS1959W
Removing previous incomplete group

name Id:hi-lo
Explanation: A previous group backup failed without

cleaning up the temporary groups correctly.
System action: The previous incomplete groups are
removed and processing continues.
A failure occurred while contacting the

WebSphere component-name.
Explanation: The attempted operation on the

WebSphere component failed.
ANS1971E
The remote client agent (dsmagent)

could not be started.
Explanation: The remote client agent cannot be

started. This error message is usually preceded or
followed by other messages.
ANS1960I
Contacting the WebSphere

component-name. This step could take a
few minutes...
Explanation: The application needs to contact the

WebSphere component to obtain configuration
information.
System action: Processing continues

Verify that the web client is installed correctly. Try to
again. If the problem persists, contact IBM technical
743
ANS1972E ANS1981E
ANS1972E
The connection to the remote client

agent (dsmagent) failed. Either the port
number could not be read, or the port
number is invalid.
Explanation: An error occurred when trying to read

the port number. A connection to the remote client
agent cannot be made.
Verify that the web client is installed correctly. Try to
ANS1977E
Explanation: Dsmcad was unable to get the valid

scheduler information from the dsmc schedule process.
This could be due to some problems during the
scheduler initialization, such as incorrect option usage.
System action: Dsmcad will try to invoke the
scheduler again in 10 minutes in order to get the valid
information.
User response: Check the console and error logs to
determine what kind of error occurred during the dsmc
process and correct the problem.
ANS1978E
ANS1973I
VSS writer for system object name does

not exist. Restore skipped.
Explanation: Microsoft Volume Shadow Copy Service

does not detect a writer for this system component.
Either the component is not installed or is not running..
Dsmcad schedule invocation was

unsuccessful. This command will be
tried again in 10 minutes.
The TSM server is downlevel and does

not support the requested function. See
error log for version information.
Explanation: The function being used requires a more

current TSM Server.
User response: Install or enable the affected system

service and retry the operation.
User response: Upgrade your TSM Server to a level

that supports this function. See error log for version
information.
ANS1974W
ANS1979E
Error removing previous incomplete

group Id:hi-lo
Explanation: A previous group backup failed without

cleaning up the temporary groups correctly, and the
error still can not be cleaned up.
System action: The previous incomplete groups
remain and processing continues.
ANS1975W
TSM server error reason occurred closing

and renaming the group
Explanation: An error was encountered closing and

renaming the temporary group.

current TSM Storage Agent.
User response: Upgrade your TSM Storage Agent to a
level that supports this function. See error log for
version information.
ANS1980E
System action: The backup is unsuccessful.

User response: Ensure that the user has the proper
authority to update the group and try the operation
again.
ANS1976E
The specified system service is not

valid.
The TSM Storage Agent is downlevel

and does not support the requested
function. See error log for version
information.
The TSM Server and TSM Storage agent

are downlevel and do not support the
requested function. See error log for

current TSM Server and TSM Storage agent
User response: Upgrade your TSM Server and TSM
Storage agent to a level that supports this function. See
Explanation: The specified system service is not valid.

operation.
ANS1981E
Server :Version ver, Release rel, Level

lev.subl Storage Agent:Version SAver,
Release SArel, Level SAlev.SAsubl
Explanation: This message supplies extra detail to

downlevel messages.
744
ANS1986E ANS1999E
User response: This message supplies extra detail to
downlevel messages.
ANS1986E
Initialization functions cannot open the

trace file specified.
Explanation: The file tracefile-name could not be

opened during initialization. The specified path may be
incorrect. It is also possible that the current user does
not have permission to write to the tracefile in the
directory specified. It is also possible that no space is
available at the given tracefile location.
User response: Make sure the tracefile option points
to a valid path and that the user has proper
permissions to write to the file specified.
ANS1987E

User response: Re-issue the command without a
destination file specification.
No filespaces are selected for preview.
Explanation: You requested a preview operation

without selecting a client filespace.
System action: TSM cannot perform a preview
without a filespace selected.
User response: Select the volumes you want to
preview and retry the operation.
ANS1989E

Error Log file specified.
Explanation: The Error Log file could not be opened

during initialization. The specified path may be
not have permission to write to the logfile in the
available at the given logfile location.
User response: Make sure the logfile option points to
a valid path and that the user has proper permissions
to write to the file specified.
ANS1990W
System action: The inaccessible mount point is

skipped and processing continues. with the next mount
point or volume.
the problem that prevents access to the volume mount
point. Ensure that the TSM client is running under an
account which as access to the volume mount point.
Ensure that the mount point is not accessing a clustered
volume. Please refer to Microsoft KB Article 280297 for
more information about how to configure volume
mount points on a clustered server.
ANS1991E
A destination file specification is not

allowed with this command.
Explanation: None.
ANS1988W
have access to the volume mount point, or the volume

is mounted onto a cluster volume which is currently
not available.
The filesystem name volume mount

point can not be accessed. The TSM
return code is rc.
Explanation: The client is unable to access volume

mount point. The common reasons for this are that the
account under which the client is running does not
An error occurred processing registry

key key-name, data value value-name.
See the client error log for additional
information about this error.
Explanation: An unexpected error occurred when the

client tried to read or update the Windows registry.
Additional information regarding the error is usually
placed in the error log.
System action: The operation might not execute
correctly, depending on the error.
message was written, and take any corrective action
suggested by those messages. If the problem persists,
contact IBM support for further assistance.
ANS1995W
Objects of different types cannot be

deleted at the same time.
Explanation: Deleting objects of different types is not

allowed. For example, deleting Backup Sets and regular
file objects at the same time is not possible.
System action: No processing takes place.
User response: Select objects of the same type to
perform delete operation.
ANS1999E
type of the operation processing of

filespace-name stopped.
Explanation: The client has encountered a condition

where it can not continue processing the specified file
space. The TSM client error log or schedule log should
contain additional messages related to this error.
User response: Check the TSM client error log and
schedule log for any additional messages related to this
error. Take any corrective action that might be
suggested by the related messages, then try the
745
ANS2000I ANS2047E
id is performing pruning at the same time.

System action: Pruning stops, processing continues.
ANS2000I
Unable to convert file names because

MEMORYEFficientbackup option is ON.
Explanation: TSM has detected that a local name

space change has occurred on the volume that is
currently being backed up. TSM would convert the file
names to the new name space, but cannot because the
option MEMORYEFficientbackup, is on.
System action: TSM continues to backup using the old
name space.

current user can write.
ANS2037W
Schedule log pruning failed.
Explanation: The schedule log pruning function

completed with errors.
User response: Edit the dsm.opt file, and set

MEMORYEFficientbackup to OFF.
User response: Check error log for possible reasons of

failure.
ANS2025E
ANS2038W
Login failed to NetWare file server

server-name.
Explanation: TSM cannot establish an authorized

connection to the Netware file server through NDS.
Connection numbers might be exhausted.
User response: Messages ANS1874E, ANS1876E and
ANS2025E can all be issued due to related problems.
These problems might include: 1) The NetWare server
has an insufficient number of NetWare user licenses. 2)
The NetWare license files are corrupt. The NetWare
license files can be reinstalled. 3) A NetWare typeful
name is not being provided at the NetWare User
prompt. 4) The TSM password file is corrupt. In this
situation, quit all TSM processes, delete or move the
*.PWD files that are located in the TSM installation
directory, then load dsmc and run the following
commands: QUERY SESSION QUERY TSA QUERY
TSA NDS.
Explanation: The client received an invalid option

from the TSM servers client option set. Although most
syntax checking for client option set options is done by
the server, there are still errors that can only be
detected by the client. These errors include:
v Option value is not correct.
v Options that have been retired by newer versions of
the TSM client.
v Missing brackets or directory delimiters.
v Include and exclude patterns that are too complex.
System action: The option is ignored by the TSM
client.
User response: Contact the TSM server administrator
to determine if the option can be removed from the
client option set.
ANS2046S
ANS2026W
Bad sectors were detected on the volume

volname.
Explanation: Bad sectors are skipped during image

backup/restore operations.
Invalid option option-name received

from the TSM server client options set.
Error errtxt (errno=errno) occurred

trying to write to audit log file-name.
The audit log function is disabled.
Explanation: There was an error encountered writing

to the audit log (for example, there is not enough space
on the disk).
User response: Make sure the volume data is not

corrupt by using system tools like chkdsk (Windows)
or fsck (Unix).
System action: Audit logging is disabled for the rest

of the operation. The return code for the operation is
set to 12 to indicate that the contents of the audit log
are incomplete.
ANS2036W
User response: If this is an out of space condition

either free up space on the volume or try to write the
audit log to a volume with more space.
Pruning functions cannot open one of

the Tivoli Storage Manager prune files:
log-name. errno = errno-value,

during pruning. The system set the error code
file in the directory specified. It is also possible that no
space is available at the given file location or another
Tivoli Storage Manager process started by different user
746
ANS2047E

processing a system state/services
request. TSM function name :
TSM explanation : TSM-msg TSM file :
file-name (line-number)
ANS2048W ANS2056I
Explanation: None.
ANS2052E
System action: Processing the system state stops.
Information about the disk subsystem is

missing.

Explanation: The local snapshot repository could not

be initialized due to missing information about the disk
subsystem.
ANS2048W
Named stream of object

object-namepath-name file-name is corrupt.
Explanation: One or more of the files named streams

are corrupt.
User response: The application ensures that the disk

subsystem is initialized properly. Check for preceding
error messages.
System action: The named stream is not

restored/retrieved.
ANS2053E
User response: The backup copy of the named stream

is damaged. The file is restored to as great an extent as
possible, but the file should be examined to verify that
it is usable.

ANS2049W
Named stream of object object-name

may be corrupt.
Explanation: One or more of the files named streams

may be corrupt.
System action: The named stream is
restored/retrieved to as great an extent as possible.
User response: The backup copy of the named stream
may be damaged. The file is restored to as great an
extent as possible, but the file should be examined to
verify that it is usable.


applications.
ANS2054E
Operating system error errno: messagetext.
Explanation: The application encountered an

unexpected message error during the execution of a
system function. The respective operating system error
and message text will be displayed.
User response: Check the specific error message.
ANS2050E
TSM needs to prompt for the password

but cannot prompt because the process
is running in the background.
Explanation: If PASSWORDACCESS is PROMPT or

the password stored locally is incorrect, the user should
be prompted for the password. But when the process is
running in the background, prompting is not allowed
and the process cannot proceed without authentication.
User response: You may use RUNASSERVICE option
with PASSWORDACCESS PROMPT. Turn off
RUNASSERVICE to be able to get prompted
ANS2051W
The local snapshot repository was not

found on location.
Explanation: The specified directory for the local

snapshot location does not exist.
ANS2055I
The local snapshot manager could not

be locked.
Explanation: The local repository is locked by another

application. This process will proceed when the other
application unlock the local repository.
ANS2056I
Waiting maximal timeout seconds until

the lock is released by the other
application.
Explanation: During the local repository is locked by

another application, the program will wait a specific
period of time to proceed. In mySAP environment is
that time 1 hour.
User response: A new local snapshot repository will

be build in the specified directory.
747
ANS2057E ANS2065I
ANS2057E
Local snapshot manager not initialized.
Explanation: The local snapshot repository was used

without previous initialization.
User response: The system normally ensures that the
local repository is initialized. Check for preceding error
messages.
ANS2058E
The data container with ID dcID could

not be updated in the local repository.
Explanation: During a FlashCopy backup the target

set record in the local repository is updated with the
correspondent properties. A failure occurred during
that process.
ANS2061W
The target data container with ID dcid

was not found in the local repository.
Explanation: An inquire of the data container with the

specified ID could not be satisfied because that target
set does not exists in the local repository.
System action: Processing may continue.
User response: The application that is requesting the
inquire will decide whether or not the error should end
the program. Check for following messages.
ANS2062W
Could not find a target data container in

the state state to fulfill the requested
criteria.
Explanation: A data container in the specified state

was not found in the local repository to satisfy specific
criteria requested by the application.
User response: Check for preceding error messages

like memory allocation error or other system error.
ANS2059E
User response: Which criteria have been passed is

application specific. Check for following messages. The
application will decide whether or not that warning
should end the program.
Cannot find a target data container that

match with the source data container.
Explanation: During a FlashCopy backup, DP for

Hardware tries to find a target data container that
match to the source data container to satisfy the
FlashCopy backup. A matching target data container
could not be found.
User response: See the rules for select one of multiple
target data containers. For example, this message will
be displayed if the user is trying to start a FlashCopy
backup of type INCR and all the target sets are being
used for the FlashCopy type COPY. Make sure also
that the target volumes are available to the backup
system and the syntax is correct for the following setup
file parameters: 1. shark_target_volume 2.
shark_copy_service_code 3. java_home_directory 4.
primary_copyservices_servername 5. shark_username 6.
shark_password
ANS2063W
The local snapshot repository already

exists on the directory location.
Explanation: An application tried to create the local

repository in a directory that already exists.
User response: The application will decide whether or
not that warning should end the program. Check for
following messages.
ANS2064I
The local snapshot repository will be

created on the directory location.
Explanation: The local snapshot repository containing

information about the state of the data containers is
being created.
ANS2060W
Cannot find a volume in the target data

container dcID to match with the source
srcvol.
Explanation: This warning message indicates that for

the specific source not any target volume could be
found in this target data container that matches for a
FlashCopy operation. If multiple target data containers
are being used, the processing will continue checking
the volumes of the next target data container.
ANS2065I
User response: Look for a operating system error

message.
748
The local snapshot repository could not

be created on the directory location.
Explanation: A failure occurred creating the local

snapshot repository.
ANS2066E ANS2093E
ANS2066E
Cannot read the .fct file filename.
Explanation: The .fct file containing the target data

containers was not found or is not accessible.
User response: Check the name, the path and the
right of the file.
ANS2067E
The exception CLsmException was

thrown. Reason: txt.
Explanation: An unexpected error occurred processing

a function of the local snapshot repository.
ANS2071E
Explanation: The system keeps some information

about the state of the data containers locally in a file.
Inserting an entry for a new data container occurred an
error.
User response: This is an unexpected error. Check for
preceding error. If not any other error can be seen,
collect the logs and traces and contact the support.
ANS2072E

User response: Check the specific reason.
ANS2068E
No target LUNs were found for the data

container dcID in the .fct file filename.
Explanation: The program will search in the .fct file

for each specific data container a list of entries with the
label <PREFIX>TARGET_VOLUME where the prefix
depends on the hardware type. Either you have a
wrong label for the target volumes of the specified data
container or this data container in the .fct file does not
have any target LUNs.
ANS2069E
Cannot read the file filename of the local


This file was not found or is not accessible.

processing a Data Protection for
Hardware function. TSM function name
: function-name TSM function :
Explanation: None.
ANS2073E

User response: This error can only occurred if the
application does not have a GUI where the user
provides the input of the target data containers and the
format will automatically be checked. If so, please
check the format of the .fct file.
The data container dcID could not be

inserted in the local snapshot repository.
The file filename of the local snapshot

repository could not be opened for
writing.

about the state of the data containers in the local
snapshot repository. Opening a file of this repository
occurred an error.
User response: Check the rights permission of that
file.
ANS2074E
Cannot open user input FlashCopy

target file fct_file.
Explanation: The FlashCopy target file that the user

provided cannot be read.

right of the file.
ANS2070E
The repository state file filename is

empty or has a wrong format.

This file was found but the expected format of the data
in not correct.
User response: Normally the system ensures that the
format of this file is correct. Check for preceding error.
User response: Run the client configuration utility and

provide a valid FlashCopy target user input file.
ANS2093E
The remote file system agent is

downlevel and does not support this
operation. NODENAME : node
MULTI-NODE NAME : multi-node
hostname : host TCP/IP address :
tcpaddr:tcpport version :
version.release.level..mod
Explanation: None.
749
ANS2094W ANS2202E
User response: Upgrade the remote file system agent
to a supported level.
ANS2094W
Unable to assign any database partitions

for back up by the Backup Worker Node
bkupWrkr.
Explanation: The list of target LUNs specified by user

for this backup worker node did not match in size any
of the source LUNs for any of the database partitions.
Hence no database partitions could be assigned for
backup to this backup worker node.
ANS2098E
One or more of the node names in the

DB2 UDB TSM configuration file are
not registered correctly as proxynode
agents.
Explanation: None.
User response: Check the TSM error log for a list of
node names that have been configured incorrectly.
Correct the problem by executing the DB2 UDB
configuration wizard.

User response: Please assign target LUNs to backup
worker nodes so that they match in size with all the
source LUNs of a particular database partition. Also
distribute the target LUNs among all the backup
worker nodes so that there is a good load balancing of
the number of database partitions backed up by each
backup worker node.
ANS2099W
The node name nodename in the DB2

UDB TSM configuration file is not
registered as an agent for target node
name targetnode.
Explanation: None.
ANS2095E
JAVA HOME value target specified in

configuration is incorrect.
ANS2100E
Neither source volume id nor target

volume id is in the volume list.
Explanation: The path name specified for java home is

not correct.
Explanation: None.
User response: Please check the value of java home

specified during configuration to make sure it is a valid
path name of the directory where JRE is installed on
master backup node. Use configuration wizard to
update java home value for the configuration.
ANS2096E
Unable to read configuration

information for database name dbname.
Explanation: The system was unable to read

configuration information for the database name
specified in the (-DATABASENAME) option.
User response: Check the spelling of the
(-DATABASENAME) option specified and ensure the
DB2 UDB configuration wizard has been used to create
the configuration information for this name.
ANS2097E
Unable to establish a session with the

TSM server as target node target using
agent node agent.
ANS2200I
***** Filling Cache count files *****
Explanation: TSM the specified number of files have

been added to the disk cache.

ANS2201I
***** Inspecting Cache count files *****
Explanation: TSM the specified number of files have

been examined in the disk cache.
ANS2202E
Disk Full Error Accessing Disk Cache.
Explanation: None.
Explanation: A disk full error occurred attempting to

access or write to the specified disk cache file during a
disk cache incremental backup. See the client error log
for more detailed information. TSM.
User response: Ensure that the multi-node name exists

on the server and that the agent node has the proper
authority to target node listed.
750
ANS2203E ANS2223W
ANS2203E
Error Accessing Disk Cache.
Explanation: An error occurred attempting to access

the specified disk cache file during a disk cache
incremental backup. See the client error log for more
detailed information. TSM.
ANS2204E
Disk cache restarted.
Explanation: The length of an object name exceeded

the configured disk cache key length during a disk
cache incremental backup. The backup must be
restarted.. TSM.
System action: Backup is restarted with a larger key
length to accommodate the object name.
ANS2220E
Explanation: The system call to put the cluster disk in

maintenance mode failed.
continues, check the client error log for any other
any) suggested by those messages. Examine the
Windows event log which may contain additional
information. See your system administrator or TSM
administrator for further help.
ANS2221W
User response: None required. The name of the object

that caused the failure can be found in the dsmerror.log
file.
ANS2206W
The user must have root authority to use

the memory efficient backup disk cache
method. The operation will continue
using memory efficient backup method
without disk caching.
The cluster disk could not be put in

maintenance mode.
Java was not able to resolve the IP

address of your local machine due to
network misconfiguration problems!
Please verify your network and DNS
configuration are setup correctly. Note
that on UNIX machines the hostname
must be reported correctly (the same) for
IPv4 and IPv6 communication methods
in the /etc/hosts configuration file. TSM
Explanation: Java was not able to get the local host

address due to network misconfiguration problems.
Explanation: None.
System action: The operation continues without using

disk caching.
User response: Please verify your network and DNS

configuration are setup correctly. Note that on UNIX
machines the hostname must be reported correctly (the
same) for IPv4 and IPv6 communication methods in the
/etc/hosts configuration file. See your system
administrator or TSM administrator for further help.

ANS2213E
Error while querying volume properties

of volume volserial. Please verify that the
volume specified in the target volumes
file exists.
Explanation: None.
ANS2219E
Cannot backup or archive files into

filespace because it is owned by a TSM
API application.
Explanation: TSM Client cannot archive or backup

files into a file space that is used a TSM API
application.
User response: Use separate node names for TSM
Client and TSM API application(s).
ANS2223W
Rejected unauthenticated
server-initiated session from peer name.
Explanation: For security, the client will not accept

server-initiated sessions from servers that have
authentication turned off.
System action: The client-server session is not opened,
and the schedule is not executed. The scheduler
continues to wait for contact by a server that has
authentication turned on.
User response: If the client system is supposed to
accept scheduled events from the prompting TSM
server, either ask the TSM server administrator to turn
authentication on, or do not use server-initiated
sessions. If the client system is not supposed to accept
scheduled events from the prompting server, ask the
TSM server administrator to remove the client node
name from the schedule on the prompting server.
751
ANS2225W ANS2605S
ANS2225W
User has specified SNAPSHOTROOT

option. snapshot provider snapshot backup
is not valid in conjunction with this
option. SNAPSHOTROOT option will
take precedence and processing will
continue without the use of a snapshot
taken internally by TSM.
Explanation: The (-SNAPSHOTROOT) option is

incompatible with TSM snapshot providers such as
Logical Volume Snapshot Agent, VSS snapshot
provider, JFS2 snapshot provider etc. which provide a
comprehensive snapshot solution withot having to use
the (-SNAPSHOTROOT) option. It is strongly
recommended that the snapshot capabilities provided
by the TSM snapshot providers be used instead of
using the (-SNAPSHOTROOT) option. Processing will
continue without the use of the TSM snapshot
providers.
ANS2601S
Browser trying to establish connection

to client; received unknown host
exception: exception-name
Explanation: The browser received the exception

exception-name trying to connect to the TSM client
machine.
User response: Retry the operation. If it persists,
determine what might be causing this kind of a
problem. Determine if your LAN went down.
Determine if you are trying to connect to the correct
TSM client machine.
ANS2602S

to client; received IO exception:
exception-name
System action: Processing continues without the use

of the TSM snapshot providers.

machine.

Backup-Archive Client book for your operating system
for correct use of the named option.
ANS2226I
Filespace filespace-name is renamed to

old-filespace-name. unicode-filespace-name is
recreated as a Unicode enabled
filespace. The current operation will
continue using the Unicode enabled
filespace.
Explanation: TSM Unicode Client operates with

Unicode enabled filespace. In order to save your data
there needs to be a one time automatic rename of the
existing MBCS filespace on the server. A new Unicode
enabled filespace is created on the server and
backup/archive continues.
User response: Determine what might be causing this

kind of an exception. Retry the problem, and check if
the LAN is down.
ANS2603S

machine.
kind of an exception. Determine if the LAN may be
down, or if the TSM Client Acceptor Daemon on the
TSM machine is up and running.
ANS2604S
ANS2600S

to client; received socket exception:
exception-name

machine.
kind of an exception. Validate that the LAN is up and
that you are trying to connect to the correct port
number.

to client; received exception:
exception-name
The Web client agent was unable to

authenticate with the server.
Explanation: The TSM Web client agent was unable to

authenticate with the TSM server.
User response: One possible solution is to run the
command line client so that the client password can be
re-entered. Another approach is to check the error log
on the TSM Web client agent for any relevant messages.
ANS2605S
Browser could not re-establish

connection to client; received protocol
error.
Explanation: The browser received a protocol error

trying to re-connect to the TSM client machine.
752
ANS2606S ANS2614S
kind of an error. Determine if the TSM browser and the
TSM client code might be out of sync.
ANS2606S
An invalid password was sent to the

server.
Explanation: The TSM password that was sent to the

TSM server was invalid.
ANS2610S
TCP/IP communications failure between

the client and the server machine.
Explanation: This error can occur if the LAN

connection between the TSM client machine and the
server machine went down.
System action: The TSM client ends.
User response: Retry the operation and make sure the
LAN is up. Make sure that both the TSM server and
the TSM client are up and running.

User response: Make sure that you have the correct
password. Also make sure that it is valid, for example
it is not too short.
ANS2607S
Browser could not establish connection

to client.
Explanation: The TSM browser could not connect to

the TSM client machine.
ANS2611S
An unknown error occurred in the

browser.
Explanation: An unknown error occurred in the

applet running in the browser.
persists, turn on tracing and see if the trace to the
browser console gives the reason for the error.

kind of a problem. Determine if the LAN is down, or if
the TSM Client Acceptor Daemon on the TSM machine
is up and running.
ANS2608S
Nothing was selected so no operation

was performed.
Explanation: No object was selected in the GUI for the

operation to be performed upon.
ANS2612S
An unknown error occurred in the client

Please check the TSM Error Log for any
additional information
Explanation: An unknown error occurred in the TSM

client.
persists, check the TSM Error Log for any additional
information.

User response: Make sure you select one or more
objects (volume, directory or file) in the GUI before
clicking on the operation to be performed.
ANS2613S
A communications protocol error

occurred between the web browser and
the client.
Explanation: None.
ANS2609S
TCP/IP communications failure between

the browser and the client machine.
Explanation: This error can occur due to any of the

following:
v The LAN connection to the TSM client machine went
down.
v You are trying to connect to the TSM client machine
using the wrong port number.
v The Client Acceptor Daemon on the TSM client
machine is not up and running and accepting
connections.

occurs again, verify that the TSM web client is installed
and configured correctly, and make sure you are using
a supported browser. Flush the browser cache. Then try
the operation again. If the problem persists, enable
SERVICE traces on the web client on the target machine
and the TSM Java applet, then reproduce the problem.
Collect the traces and contact IBM for further
assistance.
ANS2614S
A protocol error occurred in

communications between the client and
the server.
User response: Retry the operation and make sure the

LAN is up. Also check that the port number is correct,
and that the Client Acceptor Daemon is started and
running on the TSM client machine, and that it is
listening on the correct port number.
Explanation: A protocol error happened between the

TSM client and the TSM server.
753
ANS2615S ANS2623S
persists, check the TSM Error Log for any additional
information. Verify that you are running the correct
applet with the appropriate level of the client.
ANS2615S
The user ID entered does not match the

node name configured on the client
machine.
Explanation: The user ID that was entered is not the

same as the node name on this TSM client.
User response: Verify that the node name entered is
configured correctly on the TSM client.
ANS2620W
Explanation: The expand entire branch operation

could take a long time and cannot be canceled once it
is started.
intervention.
User response: Answer 'Yes' to start the expand entire
branch operation. If you answer 'No', the current
operation will be canceled.
ANS2621W
ANS2616I

changes to take effect
Explanation: The machine must be started for the

restored registry changes to take effect.
System action: None
User response: Reboot the machine
ANS2617S
The destination directory specified is

invalid.
Explanation: The user specified a destination target

directory for restore or retrieve which is invalid.
User response: Retry the operation specifying a valid
directory name.
ANS2618S
Browser trying to retrieve resources;

received resource exception:
exception-name

exception-name trying to retrieve resources from the
TSM client machine.
User response: Verify that the resources are installed
correctly on the TSM client machine.
The Client Acceptor Daemon was
unable to start the Remote Client Agent.
Explanation: The TSM Client Acceptor Daemon could

not start the TSM Remote Client Agent.
User response: Check the error log on the TSM Web
client agent for any relevant messages. Then correct the
problem and retry.
754
This function is not available on the

client platform
Explanation: The browser received a request that is

not available on the TSM client machine. For example,
registry backup and restore are available only on the
Windows platform.
User response: Request only those functions that are
valid for the platform of the TSM client machine.
ANS2622S
An invalid ID or password submitted.
Explanation: Either the ID is not registered on the

TSM server, or the password for the ID is incorrect.
User response: Verify that the ID you are using exists
on the TSM server to which the remote client node
connects. The ID must have sufficient privileges to
access the remote client nodes data. Also make sure
that you have the correct password for the ID. If the ID
does not exist or if the password is unknown, contact
your TSM administrator. If the ID does not exist, then
the TSM administrator can use the REGISTER ADMIN
and GRANT AUTHORITY commands to register an ID
that can access the remote client nodes data. If the
password is unknown, the TSM administrator can use
the UPDATE ADMIN command to reset the password.
ANS2623S
ANS2619S
The expand entire branch operation may

take a long time, and cannot be canceled
once it has started. Are you willing to
wait for the operation to complete?
Web Client applet level is out of sync

with Web Client agent.
Explanation: The Web Client applet and Web Client

agents are at incompatible levels.
User response: Verify that you have the correct level
of the applet installed with the client, and that an
incorrect level of the applet was not placed in the
install directory.
ANS2624E ANS2703E
ANS2624E
This operation requires client owner

authority.
Explanation: Your user ID has insufficient authority to

perform this operation.
System action: Processing continues, but the user is
not allowed to do this operation.
User response: Do not perform this operation, or get a
higher authority level for your user ID in order to
perform this operation.
ANS2625E
Node does not support this image

operation.
Explanation: Node does not support or is not

configured to perform this image operation.
System action: Processing continues, but the user is
not allowed to do this operation.
User response: Verify whether this image related
operation is supported or configured on the target
platform.
ANS2699I
msg
Explanation: This message is reserved for DB2 UDB.

System action: Reserved.
User response: This message is reserved for DB2 UDB.
ANS2700E
The (-DATABASE) option must be

specified with the BACKUP, RESTORE,
QUERY and WITHDRAW DB2UDB
commands.
Explanation: None.
User response: Refer to the users guide of the
corresponding platform for the correct syntax of the
QUERY UDB command.
ANS2701E
The attempted database operation was

unsuccessful, check the TSM error log
for any additional information.

ANS2627W
The NTFS security attributes for object

full-name could not be set. Windows
system error code: error; reason:
error-reason. Default NTFS security
attributes have been set.
Explanation: TSM was unable to set the NTFS security

attributes of the file. The error information captured
indicates the reason for the failure. Default NTFS
security attributes have been set.
which explains why the NTFS security attributes have
not been set. Correct the condition causing the error
and try the operation again. If the problem persists,
contact your system administrator or TSM
administrator for further help.
ANS2628W
Failed to create named stream of object

filespace namepath-namefile-name.
Explanation: TSM was unable to create named stream.

System action: The named stream is not
restored/retrieved.
User response: The object is restored without named
stream, the object should be examined to verify that it
is usable. Check the client error log for ANS5250E error
message that should have been logged when this
message was written, take the corrective action and try
the operation again. If the problem persists, contact
your system administrator or TSM administrator for
further help.

User response: Check the TSM error log for
information regarding failure and take further action.
ANS2702E
The DB2 UDB Utility plug-in module

was not found or could not be loaded.

User response: Run dsmc show plugins at the TSM
command-line client prompt to see the available
plug-ins on the system and verify the path which is
being used to load the plug-ins. If the plugin path is
available and the DB2 UDB Utility plug-in, libPiDB2.a,
is present, ensure that the LIBPATH variable is set to
the DB2 UDB products library path, for example,
LIBPTH=/usr/opt/db2_08_01/lib.
ANS2703E
The (-DBHOSTNAME) option must be

specified when using the
(-DBPARTITIONNAME) option for the
RESTORE DB2UDB command.
Explanation: None.
755
ANS2704E ANS2710W
ANS2704E
The (-BACKUPDESTINATION) option

cannot be BOTH when issuing the
Explanation: When using the RESTORE DB2UDB

command, the (-BACKUPDESTINATION) option can
be set to TSM or LOCAL, but not BOTH unless
using the (-PICK) option. When using the (-PICK)
option the (-BACKUPDESTINATION) option can be
TSM, LOCAL, or BOTH.
ANS2705S

User response: Issue the TSM client command QUERY
DB2UDB command with the -DETAIL parameter using
the same database, file, and date criteria to see if any
database partitions are available for restore.
Alternatively restore the DB2 UDB database from a
different backup.
A DB2 UDB request failed. TSM
function name : function-name TSM
function : function-desc TSM return code
: TSM-rc TSM reason code : TSM-reason
DB2 return code : DB2-rc DB2 reason
code : DB2-reason SQL-msg
Explanation: None.
User response: Contact the DB2 UDB administrator
with the SQL information provided in this message.
ANS2707E
A failure occurred while initializing the

DB2 UDB application for db partition
part-num. The TSM return code is rc.
Explanation: None.
User response: Check the TSM error log for failures
prior to this message.

processing a DB2 UDB request. TSM
: TSM-rc TSM file : file-name (line-number)
Explanation: None.
ANS2709W
No DB2 UDB partitions are available for

restore.
Explanation: No DB2 UDB partitions are available on

the TSM server for restore. This is most likely due to a
previous backup that was aborted before the backup
completed. The DB2 UDB database and selected
partitions cannot be restored.
ANS2706E
ANS2708E
A duplicate disk ID disk-id was found

on the following DB2 database
partitions: partition partition-prefix1dbnum1 hostname host1 partition
partition-prefix1db-num1 hostname host2
These DB2 partitions cannot be restored
individually.
Explanation: Each DB2 database partition should have

its own set of physical resources and logical volume
groups. If the logical volume groups are shared by two
database partitions, an artificial dependency between
the two partitions is created at the logical volume
group level. If one DB2 database partition is restored
without restoring the other database partition, the latter
database partition could have information out of synch.
System action: Processing continues. The database
partition backup objects are marked so that they can
not be restored individually, in other words outside the
context of restoring the entire host or entire DB2
database.
User response: Contact the DB2 or storage
administrator to determine if the DB2 database
partitions can be segregated to their own volume
groups.
ANS2710W
A duplicate disk ID disk-id was found

on the following DB2 database
partitions: partition partition-prefix1dbnum1 hostname host1 partition
partition-prefix1db-num1 hostname host2
The DB2 partitions and DB2 hosts listed
cannot be restored individually.
Explanation: Each DB2 database partition should have

its own set of physical resources and logical volume
groups. If the logical volume groups are shared by two
database partitions, an artificial dependency between
the two partitions is created at the logical volume
group level. If one DB2 database partition is restored
without restoring the other database partition, or if one
DB2 database host is restored without restoring the
other database host, the latter database partition or host
could have information out of synch.
System action: Processing continues. The database
partition and database host backup objects are marked
so that they can not be restored individually, in other
756
ANS2711W ANS2718E
words outside the context of restoring the entire DB2
database.
User response: Contact the DB2 or storage
administrator to determine if the DB2 database
partitions and hosts can be segregated to their own
volume groups.
ANS2715I
The filespace filespace does not exist on

the server.
Explanation: The file system may not yet have been

created on the server or it might have been deleted.
ANS2711W
Unable to backup configuration files for

DB2 database backup db.
Explanation: The configuration files that are used by

the TSM client for DB2 database backups could not be
processed. Since these files are not critical to the
database backup processing continues normally.
persists contact the TSM administrator.
ANS2712E
A non-critical, unexpected error was

encountered processing a DB2 UDB
request. TSM function name :
Explanation: None.
ANS2713E

processing a DB2 UDB request. TSM
: TSM-rc TSM explanation : TSM-msg
Explanation: None.
ANS2714W
The management class mc specified for

the dest backup destination is invalid.
The default management class will be
used.
Explanation: None.
User response: Contact the TSM administrator to run
the configuration utility for DB2 UDB and specify a
valid management class.
ANS2716E
A background copy process is still

pending on local hardware. A restore
operation cannot be initiated until the
background copy process is completed.
Explanation: None.
User response: Wait until the background copy
process completes and retry the restore operation.
ANS2717E
The multi-node definition does not have

permission to delete its own backup
files from the server.
Explanation: All DB2 UDB commands require that the

multi-node definition has permission to delete its own
backup files from the server in order to properly
reconcile the local backup repository with the server
backup repository.
User response: Have the TSM administrator update
the multi-node definition so that it has permission to
delete its own backup files from the server. For
example, on the TSM administrative command-line
client:. dsmadmc update node <multi-node name>
backdelete=yes
ANS2718E
A previous incremental backup started

on datetime is still in progress.
Explanation: A new incremental local backup can not

be done until previous incremental backup completes.
User response: Wait until previous backup completes
before starting another incremental local backup.
Alternatively, use different copyType value to perform
a local backup with full copy. TSM local backup policy
only allows one incremental and one full background
copy to be pending at any time, before local backup
resources are reused for a new backup version. A new
local backup would result in a backup with
background copy in pending state.
757
ANS2719E ANS2726E
ANS2719E
A previous backup started on datetime,

is using the resources needed for new
backup is still pending.
Explanation: A new backup can not be done until

previous backup completes.

User response: Please validate TSM configuration by
running the configuration wizard.
ANS2723I

User response: Wait until previous backup completes
before starting another local backup. Alternatively, use
different copyType value to perform a local backup.
TSM local backup policy only allows one incremental
and one full background copy to be pending at any
time, before local backup resources are reused for a
new backup version. A new local backup would result
in a backup with background copy in pending state.
ANS2720E
One or more background copies are still

in progress.
Explanation: A new backup can not be done until all

full background copies are completed.

named object has been deleted on the server and in
local repository because the background copy
operations for this backup version was cancelled. It is
no longer available for restore.
ANS2724E

User response: Wait until previous backups complete
before starting another local backup. Alternatively, use
different copyType value to perform a local backup.
TSM local backup policy only allows one incremental
and one full background copy to be pending at any
time, before local backup resources are reused for a
new backup version. A new local backup would result
in a backup with background copy in pending state.
ANS2721I
A previous local backup version backup

date datetime copytype name has been
deleted for this backup operation (object
name=filespace namepath-namefile-name,
ID=object-id:object-id).
Explanation: The local resources needed for current

backup operation would be made available by expiring
a previous backup version referenced in the message as
defined in the local backup policy. Refer to TSM
documentation for additional information on local
backup policy.
A local backup version backup date

datetime is deleted because background
copy operation has been cancelled
(object name=/filespace
name/path-name/file-name, ID =
object-id:object-id).
The version of IBM Enterprise Storage

Server is not supported.
Explanation: This product only supports IBM ESS

microcode level 2.3 and 2.4.
User response: Ensure that ESS microcode level 2.3 or
2.4 is installed.
ANS2725W
The backup DB2 UDB preview

command indicates there are not enough
resources for a backup operation.
Explanation: None.
System action: check the TSM error log for additional
information about the problem.
User response: Correct the problem and re-issue the
BACKUP DB2UDB -PREVIEW command.
ANS2726E
The putenv command failed for path =

v1.
Explanation: There was not enough memory in the

environment to successfully set the environment.
ANS2722E
There is not enough space in the local

repository to complete this backup.
Explanation: This space available in the local

repository is not enough to perform snapshot for this
backup operation. It could happen if there is more
number of local versions kept by the management class
than there is space allocated in the local repository at
configuration time or application configuration has
changed such that previously allocated space is not
enough.
758

try the operation again. For UNIX systems that support
resource limits, check to see if the memory resource
limit is too low by entering the following command:
ulimit -a
ANS2727E ANS2736E
ANS2727E
ESS Lun ID v1 is not valid.
Explanation: Length of ESS LUN id must be 8

characters.
User response: Make sure the length of ESS Lun id is
8.
ANS2728E
The ESS jar file v1 cannot be found.
Explanation: The Enterprise Storage Sub-system Copy

Services JAR file could not be located.
ANS2732E
Explanation: One or more LUNs specified in the

message are in use by other flashcopy operation.
Therefore this flashcopy operation can not continue.
User response: Release ESS LUN in order to reuse
them.
ANS2733I

User response: In order to complete Enterprise
Storage Sub-system Copy Services functions the Copy
Services command line functions must be available.
Check the Copy Services command line is installed and
your Copy Services option setting is pointing to the
installation directory of the command line.
ANS2729E

User response: Check the return code from the
operating system for more information about the
failure. Issue the failing command manually to see if
the same failure occurs.
ANS2730E
The primary and secondary copy service

servers are down.
Explanation: None.

ANS2734E
ANS2731E
Cannot open the ESS command output

file v1 for writing.
Explanation: Cant open this file for writing.

User response: Make sure you have enough space on
your system and write permission to the file.
Withdraw command failed because a

TSM backup of this database instance is
in progress using the same snapshot
resources.
Explanation: The snapshot established can not be

withdrawn because a TSM backup is in progress from
the same local backup snapshot.
User response: You must wait until the TSM backup
completes and retry the withdraw command.
Alternatively, you may cancel the TSM backup and
retry the withdraw command.
ANS2735E

User response: Start at least one of the ESS copy
service servers. If copy server is already running, check
the value of java home specified during configuration
to make sure it is a valid path name of the directory
where JRE is installed on master backup node. Use
configuration wizard to update java home value for the
configuration.
The backup DB2 UDB preview

command indicates there are sufficient
resources for a backup operation.
Explanation: None.
Operating system command command

failed; rc=rc.
Explanation: None.
The ESS LUN Serial number string are

already in use.
DB2 UDB is running on different

operating system versions. database
partition partition: OS version os-1
catalog partition: OS version os-2
Explanation: DB2 UDB must be running on the same

operating system versions on all hosts.
User response: Upgrade the operating systems so that
all DB2 UDB hosts are running the same version.
ANS2736E
An unexpected response was received

from a remote TSM file system agent.
verb : verb remote host : host return code
: rc reason code : rs msg. string :
msg-string
Explanation: None.
759
ANS2737E ANS2746I
ANS2737E
A DB2 UDB database server is not

available. DB2 instance name: instance
DB2 database name: db db partition :
part
User response: Use the Configuration Wizard to create

the DB2 UDB configuration settings.
ANS2742I
Deleting local incremental backup

version.
ANS2743E
Unable to read configuration file

information for configuration
configname.
Explanation: None.
User response: Contact the DB2 database
administrator to have the database server made
available and retry the operation.
ANS2738E
The DB2 UDB log retain value is not set

to recovery. DB2 instance name:
instance DB2 database name: db db
partition : part
Explanation: None.
administrator to have the log retain value set to
recovery.
Explanation: One or more of the TSM DB2 UDB

configuration files could not be read. Refer to the TSM
error log for additional information.
User response: Review the additional messages in the
TSM error log. Launch the TSM configuration wizard
from the DB2 UDB production host which contains the
catalog node to resolve the problem.
ANS2744I
TESTFLAG DB2 enabled with the value

of value.
Explanation: None.
ANS2739E
The DB2 UDB user exit for archiving

logs is not enabled. DB2 instance name:
instance DB2 database name: db db
partition : part
Explanation: None.

ANS2745I

administrator to have the user exits for archiving logs
enabled.
ANS2740E
DB2 UDB is running different versions.

database partition partition: version
os-1 catalog partition: version os-2
Explanation: DB2 UDB must be running on the same

version on all hosts.
User response: Upgrade the DB2 UDB version so that
all DB2 UDB hosts are running the same version.
ANS2741I
DB2 UDB configuration settings

filename have either not been created
using the Configuration Wizard or they
are not readable. The TSM return code
is rc.
Explanation: DB2 UDB configuration settings are

required for the processing of DB2 UDB commands.
They have either not been created using the
Configuration Wizard or they do not have read
permission.
System action: DB2 UDB operations will fail.
760
Volume Group Configuration has been

modified.List of logical volumes added
to the Volume Group configuration of
the database since the time of
backup:value.
Explanation: Volume group configuration has been

changed since the time of backup by the addition of
new logical volumes.
System action: User will be prompted to select Yes
to continue the restore operation, or to select No to
stop the restore.
User response: User can select Yes to continue the
restore operation, in which case the newly added
logical volumes will be deleted. Otherwise, he can
select No to stop the restore, backup the newly added
logical volumes and then retry the restore. Thus he will
be able to recover the newly added logical volumes
after the restore.
ANS2746I
Volume Group Configuration has been

modified.List of physical volumes
added to the Volume Group
configuration of the database since the
time of backup:value.
Explanation: Volume group configuration has been

changed since the time of backup by the addition of
new physical volumes.
ANS2747I ANS2757I
stop the restore.
User response: User can select Yes to continue the

restore operation, in which case the newly added
physical volumes will be removed from the volume
group. User will have to add the physical volumes
once the restore operation is complete. Otherwise, he
can select No to stop the restore.
ANS2751I
ANS2747I
ANS2752I
DB2 storage config has changed since

previous backup. Retrying to find local
resources for this backup.
Verifying multi-node information.
Explanation: None.
Initializing DB2 UDB application on
part partition(s).
Explanation: None.
Explanation: None.

ANS2753I
ANS2748I
Changing copyType to default any for

no-copy snapshot for TSM backup
operation.
Explanation: When backup destination is TSM,

snapshot copy type defaults to no-copy operation. The
is done to optimize performance of the snapshot
operation required for TSM backup.
Explanation: None.
ANS2754I

User response: Do not specify copyType option for
TSM backups or use any. This will allow TSM to pick
the appropriate default value of copyType.
ANS2749E
The backup host backup_host listed in

the user FlashCopy target input file
cannot be found in the list of
configured backup hosts.
Explanation: The backup hosts specified in the user

FlashCopy target input file must be configured as
backup hosts.
Establishing inter-client communication

with node node(s).
Establishing inter-client communication

session. NODENAME : node
MULTI-NODE NAME : multi-node
hostname : host TCP/IP address :
tcpaddr:tcpport
Explanation: None.
ANS2755I
Established communications with DB2

catalog partition.
Explanation: None.
User response: Check the configuration wizard to

determine which backup host names have been
configured. Ensure that the backup hosts specified in
the user FlashCopy target input file appear in the
configuration wizard. If the backup hosts do not appear
in the configuration wizard, either add the backup host
in the configuration wizard or specify a different
backup host name in the user FlashCopy target input
file.
ANS2750I
func function invoked for DB2

configuration db_config. backup
destination : backupdest copy type :
copytype preview : preview
Explanation: None.
ANS2756I
Querying database configuration

information from type partition(s).
Explanation: None.
ANS2757I
Initializing DB2 UDB application on

backup hosts.
Explanation: None.
761
ANS2758I ANS2772I
ANS2758I
Established communications with

backup worker nodes.
Explanation: None.
ANS2765I
Quiescing the database partitions.
Explanation: None.

ANS2766I
ANS2759I
Policy settings for backup destination

dest. Management class : mgmtclass
Backup copygroup : backup_cg Data
versions : data_vers
Creating snapshot-type-name snapshot.
Explanation: None.
Explanation: None.
ANS2767I
Explanation: None.
Resuming the database partitions.

ANS2760I
Querying database tablespaces from

database partitions.
Explanation: None.

ANS2768I

Collecting metadata files from each

database partition.
Explanation: None.
ANS2761I
Mapping database tablespaces to logical

volumes.
Explanation: None.

ANS2769I

Distributing metadata files to backup

hosts.
Explanation: None.
ANS2762I
Mapping logical volumes to physical

entities.
Explanation: None.

ANS2770I

Configuring snapshot volumes on

backup nodes.
Explanation: None.
ANS2763I
Obtaining a list of target devices for

snapshot operation.
Explanation: None.

ANS2771I

Sending group objects for backup

destination dest to the server.
Explanation: None.
ANS2764I
Initializing snapshot-provider-name
snapshot.
Explanation: None.

ANS2772I
Local backup of DB2 UDB database

dbname completed pending completion
of background copy process.
Explanation: None.
762
ANS2773I ANS2786I
ANS2773I
ANS2780I
Unconfiguring snapshot volumes.
Explanation: None.
Withdraw requested for database

configuration config. DB2 database :
db2db DB2 instance : dinst Backup size :
bsize Backup date : bdatetime Backup
destination : bdest Active state : activ
Explanation: None.
ANS2774I
Unconfiguring snapshot volumes on

backup nodes.
Explanation: None.

ANS2781I
- Database db (object id objhi.objlo)
Explanation: None.
ANS2775I
Starting the backup of TSM

configuration files for DB2 UDB
database .
Explanation: None.
ANS2782I
- Host host (object id objhi.objlo)
Explanation: None.

ANS2783I
ANS2776I
Backing up data to TSM server for

backup_type backup.
Explanation: None.
ANS2777I
Monitoring image backup.
Explanation: None.
- Partition part (object id objhi.objlo)
Explanation: None.
ANS2784I
Restoring local hardware configuration

file filename.
Explanation: None.

ANS2785I
ANS2778I
TSM backup of DB2 UDB database

db-name completed successfully.
Explanation: None.
Gathering current DB2 configuration for

type restore.
Explanation: None.

ANS2786I
ANS2779I
Restore requested for database

configuration config. DB2 database :
db2db DB2 instance : dinst Backup size :
bsize Backup date : bdatetime Backup
destination : bdest Active state : activ
Verifying database configuration

information for type partition(s).
Explanation: None.
Explanation: None.
763
ANS2787I ANS2800W
ANS2787I
Sending metadata files to worker nodes.
ANS2795I
Explanation: None.
Withdraw of DB2 UDB database name

backup completed successfully.
Explanation: None.
ANS2788I
Verifying hardware configuration

information.
ANS2796I
Explanation: None.
The DB2 UDB operation has completed

successfully.
Explanation: None.
ANS2789I
Verifying volume manager configuration

information.
ANS2797I
Explanation: None.
ANS2790I
Stopping the database manager.
Current statistics for backup host host:

Total number of volumes in request:
volumes Total number of volumes
completed: complet Total number of
volumes in progress: inprogr Total
number of volumes remaining: remaing
Currently processing volumes: process
Total number of bytes transferred: totaltr
Explanation: None.
Explanation: None.
ANS2791I
ANS2798E
Starting the database manager.
Explanation: None.
Unable to start a session from client

node nodename multi-node multi-node
to client at address ip-address:ip-port.
The TSM return code is rc.
Explanation: None.
ANS2792I
Local restore of DB2 UDB database

dbname completed pending completion
of background copy process.
Explanation: None.

ANS2799E

ANS2793I
TSM restore of DB2 UDB database

dbname completed.
An error was encountered during a

session with another client. check the
TSM error log for any additional
information
Explanation: This message is reserved for DB2 UDB.

User response: This message is reserved for DB2 UDB.
Explanation: None.
ANS2800W
Explanation: The QUERY PIDS command was unable

to identify any known TSM processes running on the
system. If the -FILTER option was used, no processes
matching the filter specification were found.
ANS2794I
Monitoring image restore.
No TSM processes were found.
Explanation: None.
User response: If you need to use dsmtrace to enable

or disable tracing for a running client process, make
764
ANS2801E ANS3001E
sure that the client is already running. If you used the
-FILTER option, try the command again with a different
filter specification. You can use -FILTER=* to display all
processes running on the system.
ANS2801E
The dsmtrace utility was unable to

connect to the specified process.
Explanation: This message typically occurs when the

specified process ID is not active.
User response: If you need to use dsmtrace to enable
or disable tracing for a running client process, make
sure that the client is already running. Use the
dsmtrace QUERY PIDS command to identify running
client processes, then try the command again.
ANS2802I
Tracing has been disabled.
Explanation: None.
ANS2805I
Explanation: None.
ANS2806E
System action: No changes are made to the trace

status of the specified process.
User response: Review the messages that immediately
precede or follow this message for further information
about this error.
ANS2807E

Tracing could not be disabled.
Explanation: A problem occurred while trying to

disable tracing for the specified process. This message
is usually accompanied by other, more specific
messages immediately preceding or following this
message.
System action: No changes are made to the trace
status of the specified process.
User response: Review the messages that immediately
precede or follow this message for further information
about this error.
ANS2804W
Tracing is already enabled.

-TRACEFILE, -TRACEMAX, and
-TRACESEGSIZE are ignored.
Explanation: When tracing is already enabled for a

client process, only the -TRACEFLAGS option has any
effect.
System action: The -TRACEFLAGS options are set on
the client process. -TRACEFILE, -TRACEMAX, and
-TRACESEGSIZE are ignored.
User response: If you need to modify the
-TRACEFILE, -TRACEMAX, or -TRACESEGSIZE
settings, you must first use the dsmtrace DISABLE
command to disable tracing for the client process. Then
run the dsmtrace ENABLE command to configure the
desired trace settings. If it is not necessary to modify
these settings, then this message may be ignored.
Tracing could not be enabled.
Explanation: A problem occurred while trying to

enable tracing for the specified process. This message is
usually accompanied by other, more specific messages
immediately preceding or following this message.
ANS2803E
Tracing has been enabled.
An incorrect number of parameters was

specified for the command-name
command.
Explanation: The specified command was invoked

with too few or too many parameters.
User response: Try the command again with the
correct number of parameters. Run \dsmtrace help\
for additional information on dsmtrace command
syntax.
ANS2820E
An interrupt has occurred. The current

operation will end and the client will
shut down.
Explanation: This message is issued when the process

is interrupted by a break signal such as CTRL-BREAK
or CTRL-C.
System action: The TSM operation and process are
ended immediately.
User response: Restart the operation if desired.
ANS3000I
communication-type communications
available on port port-number.
Explanation: The specified communications are

available on the specified port number.
ANS3001E
Error initializing HTTPS

communications - Secure HTTP not
available.
Explanation: An error occurred initializing HTTPS

communications. Processing will continue, but secure
765
ANS3002I ANS3011E
HTTP communications will not be available.
System action: Processing continues, but secure HTTP
communications will not be available.
User response: Check the console and error logs to
determine why secure HTTP communications was
unable to start, correct the problem, and restart the
client.
ANS3007I
TSM client-name terminating - idle for

idle-minutes minutes.
Explanation: The specified client is terminating

because it has been idle for the specified time. It will be
automatically started when it is needed.
System action: The client program stops.
ANS3002I
Session started for user userid

(communication-method address).
Explanation: A session was started for the specified

user.
ANS3003I
Session ended for user userid.
Explanation: A session ended for the specified user.
ANS3008E

ANS3009E

ANS3004E
Session for user userid terminated invalid password entered.
Explanation: A session was terminated for the

specified user because an invalid password was
entered.
System action: The session with the specified user is
terminated.
User response: Re-start the remote client and enter the
correct password for the specified user.
ANS3005I
Session for user userid terminated - idle

for idle-minutes minutes.
Explanation: A session was terminated for the

specified user because there was no activity on the
session for the specified number of minutes.
System action: The session with the specified user is
terminated.
User response: Re-start the remote client to begin a
new session.
ANS3006I
Processing request for the TSM Web

Client (ip-address).
Explanation: A request for the Web Client is being

processed.
766
Too many symbolic links were detected

while resolving name file_name
The Logical Volume Snapshot Agent

plugin library was not found.
Explanation: The Logical Volume Snapshot Agent

(LVSA) plugin library should have been installed when
the client was installed, but it cannot be found.
performed.
recurs, re-install the TSM client software. If the problem
assistance.
ANS3010E
The snapshot wizard operation failed.
Explanation: The snapshot wizard operation failed

with a non-zero return code. Check the error log for
additional information.
performed.
User response: Review the error log for any error
messages, and then retry the operation after correcting
the cause for failure.
ANS3011E
Previous changes have not been

commited. The machine must be
rebooted before this operation can be
performed
Explanation: A previous operation required the

machine to be rebooted for the changes to take effect,
but the machine has not been rebooted. The machine
must be rebooted before this selected operation can be
performed.
performed.
ANS3012E ANS3406W
User response: Reboot the machine and then retry the
operation.
ANS3012E
The Logical Volume Snapshot Agent is

not installed. Use the Setup Wizard to
configure either Online Image or Open
File support and choose the Logical
Volume Snapshot Agent as the snapshot
provider.
Explanation: The selected operation requires the

Logical Volume Snapshot Agent, but it is not installed.
Use the Setup Wizard to install the LVSA.
performed.
User response: Retry the operation after installing the
Logical Volume Snapshot Agent.
ANS3013E
The specified snapshot provider is not

supported on this version of the
operating system.
Explanation: The specified snapshot provider is not

supported on the version of the operating system you
are currently running. If another snapshot provider is
available, select it and retry the operation.
performed.
User response: If another snapshot provider is
available, select it and retry the operation.
ANS3401W
The entity name is invalid.
Explanation: A volume with this name could not be

found or is not suitable for server-free operations.
ANS3403W
Volume name cannot be opened for

reading. System error code is err.
Explanation: The named volume could not be opened.

Examples of why this can occur include, but are not
limited to: the device is not a valid system device, the
device is locked by another application, or the user
does not have correct or permissions. The operating
system error code shown in the message indicates the
specific reason for the failure.
User response: Use your operating systems tools to
obtain the description of the error code. Also check the
error log for any other messages that might indicate a
reason for the failure. Try to correct any indicated
assistance.
ANS3404W
An error occured reading volume name.
Explanation: The named volume could not be read.

Examples of why this can occur include, but are not
limited to: the data being read is outside the valid
range of the volume, or the device is locked by another
application. The operating system error code shown in
the message indicates the specific reason for the failure.
System action: If server-free data movement is used,
processing continues using non-server-free data
movement. Otherwise processing stops.
assistance.
User response: Specify the correct name.

ANS3405W
ANS3402W
name: A system call func failed with code

rc.
Explanation: An error occurred while obtaining

information from the operating system. The volume
information could not be obtained.
System action: Processing can continue if the
information being obtained is not critical for the
operation or if it is expected behaviour in the context of
the operation being performed.
File system fs on volume name is

unknown.
Explanation: The file system on the volume is not

supported for the operation being performed.
System action: If server-free data movement is used,
processing continues using non-server-free data
movement. Otherwise processing stops.
ANS3406W
Physical mapping of the volume name is

not supported.
Explanation: The logical volume layout is not

currently supported for physical mapping.
767
ANS3407W ANS3414I
System action:
information on what volume layouts are supported for
physical mapping.
ANS3407W
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.
ANS3408E
System call umount failed for volume

volume with errno=error. Please take
suitable action based on errno and retry
the operation.
Explanation: Umount failed for the specified volume

with the indicated errno. Please take suitable action
based on errno and retry the operation.
User response: Check errno for umount failure and
take corrective action before retrying the operation.

operation.
dividing the task into serveral smaller units. For
ANS3411E
Invalid arguments were passed to

function name.
Explanation: The named function did not receive

correct arguments to proceed. Please check error log for
additional errors following this one for further
explanation.
ANS3409W
An error occurred writing to volume

name.
Explanation: TSM could not write to the named

volume. Examples of why this can occur include, but
are not limited to: the data being written is outside the
valid range of the volume, or the device is locked by
another application. The operating system error code
shown in the message indicates the specific reason for
the failure.
User response: Retry the operation. If problem persists

contant your TSM administrator.
ANS3412I
DiskMapper does not support name for

entity name.
Explanation: The requested function is not

implemented in DiskMapper at this time. Please report
this error to your TSM administrator.

assistance.
User response: Contact your TSM administrator.

ANS3413I
DiskMapper object name type name is

not valid.
Explanation: The named object is not valid on the

originating client system.
ANS3410E
The operating system refused a TSM


to allocate.
768

persists, review the client error log for other messages
that might be related to this problem. Contact your
TSM administrator for additional help.
ANS3414I
Disk name is not part of any container

defined on the system.
Explanation: None.
System action: None. This is informational message.
ANS3415W ANS4005E
ANS3415W
At least one of the disk containing data

for name has bad blocks.
Explanation: One or more physical disks containing

data blocks of the above object has bad blocks and the
requested operation can not continue.
System action: The system may find a work-around to
complete the requested operation, pleasecheck console
log and error log for additional information on
corrective actions taken or suggested user action..

further assistance.
ANS4002E
Error processing filespace-name: volume

label does not exist
Explanation: The selected drive does not have a label.

operation without a drive or label entered.
User response: Depending on the operation TSM may

suggest an alternate way to complete the operation.
Check your error log, sched log, or console log for

ANS3416E
ANS4003E
The volume name is currently in use by

other process.
Explanation: The operation requires exclusive access

to the volume. The most likely cause of this failure is
that other process on the system has the volume
opened.
User response: Check applications running on your
system to ensure that volume is not opened by any if
the process and then retry the operation.
ANS4000E

space does not exist.

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

volume label. Because TSM uses the volume label to
keep track of backup/archive information, it cannot
back up or archive files from a drive with a duplicate
volume label.
System action: TSM cannot select the drive.
the system, exit TSM, and assign a volume label to the
drive. Restart TSM and retry the operation.
ANS4004E

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

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

updated.
User response: Try the operation again, specifying an

existing domain (drive letter or file system name). If
the message resulted from improper use of the
MODE=INCREMENTAL option, try the command
again, omitting that option.

or location.
ANS4001E
The file space for domain filespace-name

could not be found on the TSM server.

in progress.
ANS4005E

namepath-namefile-name: file not found

Another process deletes the file before it can be backed
up, archived or migrated by TSM.

769
ANS4006E ANS4013E
ANS4006E

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

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

namepath-namefile-name: access to the
object is denied

the directory.
User response: Select the appropriate action for this

object. Create some free space on the destination disk
before you retry the operation. Another option is to
restore or retrieve the file to another disk.
ANS4010E

namepath-namefile-name: stale NFS handle

ANS4011E

namepath-namefile-name: no file handles
available

ANS4012E
filespace namepath-namefile-name already

exists. It will be skipped.

specified file, but the file already existed in the target
restore location and the user chose not to replace the
existing file.
System action: The file is skipped, a message is
User response: The file was skipped because either

REPLACE NO was in effect, causing all existing files
and directories to be skipped, or REPLACE PROMPT
was in effect, and when prompted, the user chose to
skip this file or all existing directories and files. No
additional action is necessary if the decision to skip the
file was deliberate. Otherwise the operation can be
retried using either REPLACE ALL REPLACE
PROMPT.

ANS4013E
ANS4008E

namepath-namefile-name: file is
temporarily unavailable
ANS4009E

namepath-namefile-name: disk full
condition

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

operation failed because an invalid file handle was
passed.

System action: The client prompts you for action:
User response: Report the problem to your system

administrator, and then retry the operation.
v Retry this object

v Skip this object
v Abort the action
770
ANS4014E ANS4022E
ANS4014E

error (error-code) encountered. Program
ending.
Explanation: An unrecognized and unexpected

error-code occurred within the client program. This is a

Backup-Archive Client book for the particular operating
system, for the file names that are handled by TSM.
ANS4019E

continues, report the error to your TSM administrator.

locked by system

ANS4015E

namepath-namefile-name: unexpected TSM
error (error-code) encountered

ANS4020E
Explanation: An unexpected error occurred. This

might be a low-level system or communication error
that TSM cannot handle or recover from.
The data format for object filespace

namepath-namefile-name is unknown. This
usually occurs when the file was backed
up or archived by a later version of
TSM.

continues, look for other indications of system
problems to determine where the problem exists. Most
systems have error or event logs which may contain
additional information. See your system administrator
or TSM administrator for further help.
Explanation: When a file is backed up or archived,

TSM includes some additional information about the
file. This message is issued if TSM cannot recognize the
information during a restore or retrieve operation. The
most likely cause is that the file was backed up or
archived with a version of TSM that is newer than the
version used to perform the restore or retrieve.
ANS4016E
System action: The file is not restored or retrieved.

Processing continues with the next file.

namepath-namefile-name: file is being
executed; write permission denied

operation.
ANS4017E

namepath-namefile-name: too many
symbolic links were detected while
resolving name

User response: Try the restore or retrieve operation

again with a current version of the TSM client software.
If the problem persists, contact IBM technical support
ANS4021E

namepath-namefile-name: file system not
ready

access.
ANS4022E

invalid.
Explanation: The drive was not available for access.

ANS4018E

namepath-namefile-name: file name too
long
User response: Ensure that the drive is operational,

and then try the operation again. If this is unsuccessful,
Explanation: The file name specified is too long to be

handled by TSM.
771
ANS4023E ANS4029E
ANS4023E

namepath-namefile-name: file input/output
error


properly.
ANS4026W

ANS4024E

namepath-namefile-name: file write error

file.

namepath-namefile-name: size of file-size
exceeded the maximum file size limit on
your system

system.
administrator.

operating properly.
ANS4027S
ANS4025E
Explanation: An unexpected catastrophic program

failure occurred, indicated by value.

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

archived/retrieved exceeds system set limits for this
user. Shown below are the filesize limits corresponding
to various platforms.
68,589,453,312 (64GB)
AIX

continues, see your system administrator or service
representative.
ANS4028E
HP-UX 1,099,511,627,775 (1TB-1)

2,147,483,647 (2GB)
Linux
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)

namepath-namefile-name: internal program
message value encountered

namepath-namefile-name: cannot create
file/directory entry

restored or retrieved.
ANS4029E

namepath-namefile-name: unable to build
a directory path; a file exists with the
same name as a directory
Solaris 2.6 or higher

1,099,511,627,775 (1TB-1)
Explanation: TSM tried to create a directory path, but

is unable to because a file exists that has the same
name as a directory.
Tru64 UNIX
1,099,511,627,776 (1TB)
UnixWare
2,147,483,647 (2GB)
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.
Windows ME (FAT32)
4,294,967,295 (4GB)
Windows NT/2000 (NTFS)
17,592,185,978,880 (16TB-64K)
772
ANS4030E ANS4037E
ANS4030E

namepath-namefile-name: disk space limit
for this process reached

owner is full.

ANS4034E
ANS4031E
Error processing
file_space_namepath_namefile_name. Name
exceeds an internal TSM limit.
Explanation: During a file operation, TSM

encountered a filename where at least one component
of the file name (file_space_name, path_name or
directory_name or file_name) exceeded an internal TSM
maximum. The internal TSM limits should not be
confused with the operating system limits for
file_space_name, path_name or directory_name,
file_name.

error

be a low-level system or communication error that TSM
cannot handle or recover from.
Shown below are the TSM internal file name limits for
various platforms.
ANS4035W
AIX HP-UX Solaris

File_space_name
Path_name or directory_name
File_name
1024
1023
256

is currently not available from the TSM server.
Linux
File_space_name
File_name
1024
768
256
Windows XP/2000/2003
File_space_name
File_name
1024
248
248
User response: Reduce the size of the filename so that

it is smaller that the TSM internal limits.
ANS4032E

namepath-namefile-name: file is not
compressed.

ANS4033E
System action: TSM Cannot restore or retrieve the file.

User response: Try to restore or retrieve after the file
was made available on the server. See your system
administrator.
ANS4036E

namepath-namefile-name: file compressed
on a different client machine that has
more memory
File filespace namepath-namefile-name

currently unavailable on server.

key.
Explanation: The active registry key cannot be copied

to the ADSM.SYS staging directory.
System action: Registry backup operation terminates.
User response: Check the space available on the
Windows boot partition to ensure there enough space
to contain a copy of the Windows registry. This might
require several megabytes of free space. Also check the
Windows permissions on the ADSM.SYS staging
directory and ensure that the Windows user under
which you are running TSM has full access to that
directory and its contents.
ANS4037E
Object file-namefile-namefile-name
changed during processing. Object
skipped.

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

ANS4041W
An error occurred processing file system

filespace name.
Explanation: File system filespace name is corrupted

or contains one or more corrupted directories and
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
dsmerror.log.

System action: TSM terminates the current operation
ANS4042E
ANS4039E

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

Server.
ethernet adapter on the Server please upgrade the card
ANS4040E

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

exceeded its quota. No more data can be migrated out
of this file system.
System action: TSM will not migrate files from this
file system.
774

namepath-namefile-name: Out of free
space or inodes in file system to migrate
or recall.

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

label syntax is incorrect.
User response: You need to check the disk for errors.
ANS4044E
Error processing filespace-namepathnamefile-name: Case-sensitive name

conflict exists.
Explanation: While processing the specified file on the

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

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

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

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

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

file-namefile-namefile-name. The file is
skipped.

during backup archive because the file could not be
read.
it is possible that the snapshot was not large enough to
contain all the changes made to the filesystem after the
snapshot was created. This could cause the snapshot to
become invalid thereby preventing TSM client from
reading the snapshot.
LAN-Free errors. Check your LAN-Free setup and

verify that all components are working properly.
ANS4050W
Explanation: One or more of the client options schedcmddisabled, srvprepostscheddisabled,

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

operating properly.
please use the default snapshotcachesize of 100% and
ensure that the volume group has sufficient disk space
to allocate snapshots at least as large as the file system
ANS4048W
LAN-Free connection failed.
Scheduled action schedule-action did not

execute for schedule schedule-nameas the
TSM administrator has been disabled
from executing the scheduled action on
the client.

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

an encrypted file system (EFS). The option is specified
to back-up or archive the file in decrypted form. The
user ID under which the back-up or archive is being
run does not have decryption rights for this file.
User response: There are three possible ways to make
decryption work:
Explanation: ENABLELANFREE option is set to YES

for this session, but an attempt to establish LAN-Free
connection failed.
v Re-encrypt the file under the encryption key of a

group to which both the owner and the
back-up/archive user IDs belong
System action: The TSM client will failover to non

LAN-Free support.
v Add the back-up/archive user ID to the list of users

authorized to decrypt this file
User response: Review the TSM error.log for

LAN-Free failures. Check your LAN-Free setup and
verify that all components are working properly.
v Run the back-up or archive under the owners user

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

for this session and the TSM client successfully
established LAN-Free connection with server, after the
LAN-Free connection was broken.
System action: The TSM client will communicate with
the server via LAN-Free.
User response: Review the TSM error.log for

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

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

namepath-namefile-name: The file cannot
be restored because the file system or
operating system does not support the
Encrypted File System data
Explanation: The specified object was backed-up as

raw Encrypted File System data. The client is trying to
restore or retrieve the object to a destination that does
not support the encrypted file system data. The
location may not support the encrypted file system
data for one of the following reasons:
v The operating system does not provide the support,
or is a release that does not include the support
v Encrypted File System support has not been
activated on the operating system
v The target file system is of a type that does not
support the Encypted File System data
System action: The object is not restored or retrieved.
User response: If this file must be restored, restore it
to an AIX operating system environment supporting
Encrypted File System data.
ANS4054E

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

an encrypted file system (EFS). The option is specified
to backup or archive the file in decrypted form. The
encryption key, required to decrypt the file, is not
loaded in the kernel keyring.
User response: There are three situations in which this
problem can occur:
v You just performed initial activation of EFS on the
AIX system, and have not logged out. AIX does load
the keys for the session running at the time of initial
activation. Solution: Logout and login again.
776
v The login password has been changed recently, and

you normally run with the EFS password the same
as the login password. AIX does not automatically
change the EFS password when you change the login
password. Solution: Issue efskeymgr -n to set the
EFS password to be the same as the login password.
v You need to run the decrypting backup when the
EFS password is different from the login password.
Solution: Issue efskeymgr -o ksh to launch a new
shell with the keys loaded. AIX will prompt you for
the EFS password as you launch the shell. Run the
backup from the new shell.
ANS4900W
Schedule schedule-name has opened a

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

connection failure. The scheduled event had to be
restarted outside its normal startup window to
continue the operation.
System action: The scheduled event is completed
using more than one session.
User response: None required. If this is a recurrent
condition, you may want to check for network
problems.
ANS4942E
The file specification string is invalid.
Explanation: The operating system indicated that the

file specification is invalid. One possible reason is that
the file specification contains unrecognized characters.
Another possible cause is incorrect use of quotation
marks in the file specification.
described in the Using the Backup-Archive Client book
for the particular operating system. Ensure that the file
specification contains valid characters. Verify correct
use of quotation marks for specifications that contain
blanks spaces. If multiple file specifications are used,
make sure that any use of quotation marks does not
cause the file specifications to be treated as a single file
specification.
ANS4973E
An error occurred accessing NTFS

security information for file filespace
namepath-namefile-name
Explanation: An access denied error occurred while

attempting to access NTFS security info rmation.
System action: The object is skipped.
User response: See your system administrator or
bypass the failing check by using SkipNTSecu rity
option.
ANS4974E ANS4997E
ANS4974E

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

possess a required NT user right/pr ivilege for
performing the current operation.
System action: The object is skipped.
User response: Your system administrator has the
authority to grant the needed privilege.
ANS4987E

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

ANS4991I
Application Type Application Message Id

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

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

Application Message


User response: Ensure that the file is not locked by
another process. If the file is not locked, retry the
command.
ANS4988W

currently unavailable on server and has
been skipped.

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

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

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

Application Message

ANS4994S

Application Message

ANS4997E

quota reached condition - no space left.

retrieved because the quota of the destination file
system has been reached.
System action: The client prompts you for action:
v Retry this object
v Skip this object
v Abort the action
User response: Select the appropriate action for this
object. Create some free space or increase the quota on
the destination file system before you retry the
operation. Another option is to restore or retrieve the
file to another file system.
777
ANS4999E ANS5007W
ANS4999E
The following message was too long to

log to the server: shortened message with
message number @msgnl;
Explanation: The message text and inserts are too

buffer.
System action: The message number message is written
to the local client error log, then shortened and sent to
the server as a part of this message. The message is
reduced in length by substituting ... in the middle of
the original message.
User response: The message referred to has been
shortened, but describes the error that occurred. Refer
to the documentation for that message for more
information.
ANS5000W
Unable to update password
Explanation: Intended new password cannot be

registered.
System action: The server did not replace the old
password with the new password.
User response: Update the password again. If
unsuccessful, see your system administrator.
ANS5001E
Open registration required. Root user

must run TSM to register with server
Explanation: This client must be registered with this

server.
User response: The root user must register the client
with the server.

ANS5004S

ANS5005E

User response: Start a new restore window to get
current information.
Open registration failed
Explanation: During the change password, update

password, or open register dialog, the open registration
failed.
System action: TSM did not register this system.
User response: Reenter the password, or see your
system administrator to register this system.
ANS5003S
The management class assigned to

directories does not exist.

778
Table of contents information is not

available for the selected images.
Explanation: An error occurred when the server tried

to load a table of contents. Requested image or table of
contents may have expired or been deleted on the
server.
ANS5006W
ANS5002E
There is no backup copy group in the

management class used for directories.
See the error log.
The policy set does not contain any

backup copy groups. TSM is unable to
continue the backup.
Explanation: You tried to back up the files using a

policy set that contained no backup management
information.
System action: TSM did not back up the files.
User response: See your TSM administrator for
assistance in associating your node with a policy set
containing a management class that has a backup copy
group. Then try the operation again.
ANS5007W
The policy set does not contain any

archive copy groups. TSM is unable to
continue the archive.
Explanation: You tried to archive the files using a

policy set that contains no archive management
information.
System action: TSM did not archive the files.
ANS5008W ANS5019I
assistance in associating your node with a policy set
containing a management class that has an archive
copy group. Then try the operation again.
ANS5008W
Incorrect password entered
Explanation: You entered a password that was

incorrect.
without the correct password.
ANS5014I
Backup completed
Explanation: The backup was completed.

System action: TSM backed up the files.
ANS5015I
Restore stopped by user
Explanation: You requested to stop the restore

operation.
User response: Reenter the password, or ask your

system administrator for the current password.
Attention: If you were restoring files with overwrite

option specified, the file you restored last can be
damaged (partially overwritten).
ANS5009W
System action: Restore stopped.
New password entries are not the same
Explanation: During the change password, update

password, or open registration dialog, the two entries
for the new password were not the same.
System action: The password was not changed on the
server.
User response: Backspace over both of the new
passwords and reenter them, ensuring that they match.
ANS5011I
Backup stopped by user
Explanation: You requested to stop the backup

operation.
System action: Backup stopped.
ANS5012E
Server out of backup data storage space
Explanation: The server ran out of space in its backup

data storage.
backup operation. Any files displayed on the lower half
of the backup activity panel were successfully backed
up.

ANS5016E
Not enough memory for restore

operation
Explanation: TSM cannot allocate memory for the

requested restore operation.
restore operation.
retry the operation. Reducing the scope of queries and
the amount of data returned can also help, or see your
ANS5017I
Restore completed
Explanation: A restore was completed.

System action: TSM restored the files.
ANS5018E
Not enough memory for archive

operation

requested archive operation.
ANS5013E
System action: TSM cannot complete the archive

operation.
Not enough memory for backup

operation

specified backup operation.
operation.
the amount of data returned might also help, or see
your system administrator.

ANS5019I
Archive stopped by user
Explanation: You requested to stop the archive

operation.
System action: Archive stopped.
779
ANS5020E ANS5093S
ANS5020E
The TSM server is out of archive data

storage space.
Explanation: The server ran out of space in its archive

data storage.
archive operation.
User response: Report the problem to your TSM
system administrator, who can allocate more resources
to archive storage.
ANS5021I
ANS5026W
MatchAllChar and MatchOneChar

options MUST precede Include/Exclude
options
Explanation: The MatchAllChar and MatchOneChar

options must precede any include-exclude options.
System action: The TSM client ends the current
application.
User response: Move the MatchAllChar and
MarchOneChar options before any include-exclude
options.
Archive completed
Explanation: An archive was completed.

System action: TSM archived the files.
ANS5083E
Drive specification contains wildcard

character.
Explanation: Drive name shouldnt contain wildcard

character.
System action: Wildcarded objects skipped.
ANS5022I
Retrieve stopped by user
Explanation: You requested to stop the retrieve

operation.
Attention: If you were retrieving files with
overwrite option specified, the file you retrieved last
can be damaged (partially overwritten).
System action: Retrieve stopped.
ANS5023E
Not enough memory for retrieve

operation

specified retrieve operation.
retrieve operation.
User response: Use valid drive specification.

ANS5091S
The TSM server does not currently have

space in the storage pool for this file.
This might be a temporary condition.

not have sufficient to store the data, but that the space
will be available soon. For example, a storage pool
migration may free up sufficient space to store the data.
User response: This is possibly a temporary condition.
Try the operation again at a later time. If the error
persists, contact your TSM administrator, who can
examine server console and error logs to locate the
cause of the problem.
ANS5092S
Server out of data storage space.
Explanation: The server does not have any more space

ANS5024I
Retrieve completed
Explanation: A retrieve was completed.

System action: TSM retrieved the files.
ANS5025E
The node name contains invalid

characters.

ANS5093S
SLM_LICENSE_EXCEEDED: The client

licenses for TSM are exceeded. See your
TSM administrator.

product license count for this TSM server.
Explanation: The specified node name has invalid

characters.
System action: The client enrollment or connection

request ends.
User response: See your TSM administrator to delete

unused enrollments or negotiate an increase in the
number of allowed licenses for your server.

has valid characters.
780
ANS5094E ANS5132I
ANS5094E
Session Rejected. Sufficient server


with the server.
administrator.
ANS5122E
The specified filespace does not exist on

the server. The filespace might have
been deleted by another client or an
administrator.
Explanation: The specified filespace does not exist on

the server. Your administrator might have already
deleted the filespace or another client using your
client's node name might have deleted it.
User response: The filespace you selected does not
exist any more. See your TSM administrator for help in
finding how the filespace was deleted.
ANS5123S
Open registration failed because the

specified node name is already defined
in the server.

is defined on the server with the same name.
ANS5126S
Filespaces with duplicate names are not

supported. Please unmount the
duplicate filespace.
Explanation: The selected filespace has a duplicate

volume label. Because TSM uses the volume label to
keep track of backup/archive information, it cannot
back up or archive files from a filespace with a
duplicate volume label.
System action: TSM cannot select the volume.
User response: If the filespace needs to be available to
the system, exit TSM, and assign a volume label to the
filespace. Restart TSM and retry the operation.
Otherwise, unmount the duplicate filespace.
ANS5128E
The management class for this file did

not have a backup copy group.
Explanation: For backup operations, a file may only

be bound to a management class that has a backup
copy group.
User response: See your TSM system administrator
for assistance in finding a management class with the
required copy group. The administrator may also
define such a management class for you.
ANS5129E
The management class for this file did

not have an archive copy group
specified.
Explanation: For archive operations, a file may only

be bound to a management class that has an archive
copy group.
ANS5124S
System action: TSM did not archive the file.
Open registration failed because there is

no default domain.

default policy domain does not exist in which to place
your node. A default policy domain is required to fully
support open node registration.
User response: See your TSM system administrator

for assistance in finding a management class with the
required copy group. The administrator may also
define such a management class for you.
System action: TSM cancels the current operation.
ANS5130W

assistance in registering your node.
Explanation: You requested a deletion operation

without selecting a client domain.
ANS5125S
System action: TSM cannot perform a deletion

without a domain selected.
Open registration failed because an

invalid node name was specified.

specified node name has invalid characters.
No filespaces selected for deletion
User response: Select the volumes you want to delete

ANS5132I
Filespace deletion canceled by user

Explanation: You requested to cancel the filespace

deletion operation.
System action: The filespace deletion operation
stopped.
781
ANS5133I ANS5150E
ANS5133I
Filespace filespace was deleted
Explanation: The specified filespace was successfully

deleted.
System action: TSM deleted the filespace.
ANS5134E
The administrator has authority to delete archived files,

and can also grant that authority to your node.
Unable to delete the filespace because

this node does not have permission to
delete archived data and/or backed up
data.
Explanation: You tried to delete a filespace that you

do not have permission to access.
ANS5145W
Explanation: The restart restore token has expired.

The server cannot restart the restore from where it last
ended.
intervention.
User response: Retry the request without restart or
abort the request.
ANS5146W

User response: Ensure that you specify the correct
filespace, or specify a filespace you have access to.
ANS5135I
Archive delete stopped by user
Explanation: You requested to stop the archive delete

operation.
System action: Archive delete stopped.
Server cannot restart the last restore

request. Do you want to restore without
restart?
You cannot perform this operation while

accessing data for another node. Do you
wish to switch back to accessing your
own node?
Explanation: The user cannot perform the selected

operation while accessing another users data.
intervention.
User response: Answer Yes to switch back to
accessing the server as the original node.

ANS5148W
ANS5136E
Not enough memory for archive delete

operation

specified archive delete operation.
System action: TSM cannot continue with the
requested archive delete operation.
ANS5138I
Archive delete completed
Explanation: An archive delete was completed.

System action: TSM deleted the archived files.
ANS5139E

delete archived files.
Explanation: Your node is registered at the server

with the ARCHDELETE option set to no. Therefore
your node is not allowed by the server to delete
archived files.
System action: TSM did not delete the archived files.
User response: See your TSM system administrator.
782
The server needs to do a one-time

conversion of your archive data before
you can continue. This operation may
take a long time, and cannot be canceled
once it has started. Are you willing to
wait for the conversion to complete?
Explanation: The server must do a conversion of the

archive data before continuing. The conversion could
take a long time, and cannot be canceled once it is
started.
intervention.
User response: Answer Yes to start the archive data
conversion. If you answer No, the current operation
will be canceled.
ANS5150E
An active restore for the same source

file specification exists. Unable to
continue with this request.
Explanation: Currently, there is an active restore for

the same source file specification. Another restore of the
same source file specification cannot be started.
System action: The requested restore fails.
User response: Start another restore with a different
source file specification.
ANS5151S ANS5166E
ANS5151S
This node currently has a pending

restartable restore session. The
requested operation cannot complete
until this session either completes or is
canceled.

because a restartable restore session is pending. The
operation is not allowed because the restartable session
and the current operation affect the same file space.
User response: Issue a query restart to see the conflict.
Issue the cancel restore command to delete any
unneeded restartable restore sessions.
ANS5152S
Session Rejected: The server is not

licensed for this platform type. See your
TSM administrator.
Explanation: The server license governs the types of

client that can connect to it. The license for this server
does not include the requesting client type.
system must set and store a new password.

ANS5157E
This action requires TSM administrative

authority on this system.

User response: If the activity is required, the TSM
ANS5158S
Filespace deletion is in progress. Try

again later.
Explanation: The filespace is in the process of being

deleted.
operation.
System action: The client enrollment or connection

request ends.
User response: Try the operation again later. If the

filespace was being deleted, it could take awhile for it
to complete. If the problem continues, report the
problem to your system administrator.
User response: See your TSM administrator who must

upgrade the server license to accept your client type.
ANS5164E
ANS5153E

allow a signon as a Unicode enabled
client.

to the server because of a unicode enabling mismatch
between server and client.
Backup or archive of drives with

duplicate volume labels is not allowed.
Explanation: You tried to back up or archive a drive

that has a duplicate volume label. Because TSM uses
the volume label to keep track of backup or archive
System action: TSM cannot select the drive for backup
or archive operations.

immediately.

the system, exit TSM and assign a unique volume label
to the drive. Restart TSM and try the operation again.
ANS5154I
ANS5165E
File is implicitly excluded
Explanation: You tried to back up or migrate a file

that is implicitly excluded.
System action: TSM will not back up or migrate an
implicitly excluded file.
ANS5155E
Valid password not available. The TSM

administrator for your system must run
TSM and enter the password to store it
locally.

for the specified server server-name is unavailable.
User response: The TSM administrator for your
Drive has no volume label.

Backup/Archive not allowed.
Explanation: You tried to backup or archive a drive

that has no volume label.
System action: TSM rejected the selected drive.
ANS5166E
An error occurred while removing

include-exclude statement statement.
Please try again.
Explanation: There was a problem with removing the

include-exclude statement. Make sure that your
include-exclude statement is valid.
783
ANS5169E ANS5186E
System action: No include-exclude statement was
removed. Waiting for user action.
User response: Retry your operation. If you see this
error message again, contact your system administrator
ANS5169E
The destination path must contain a

drive letter
Explanation: The entered path must begin with a

drive letter, colon, and root slash.
User response: Enter the destination path in the
correct format.
ANS5173E
An error occurred accessing NTFS

security information.
ANS5181E
Invalid selection; A specific backup set

must be selected.
Explanation: A selection was made that might result

in multiple backup sets being restored at the same
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
restored.
ANS5182E
Multiple backup sets can not be

restored at the same time.
Explanation: Multiple backup sets were selected to be

restored, but restoring multiple backup sets at the same
time is not supported.

access NTFS security information.
System action: The backup set restore was not

performed.
System action: Object will not be processed.
User response: Select a specific backup set to be

restored.
User response: See your system administrator or

bypass by using SkipNTSecurity option.
ANS5183W
ANS5174E
A required NT privilege is not held.
Explanation: The user account running TSM does not

possess a required NT user right/privilege for
performing the current operation.
System action: Object will not be processed.
Objects of different types cannot be

Explanation: Restoring objects of different types is not

allowed. For example, restoring Backup Sets and
regular file objects at the same time is not possible.
User response: Select objects of the same type to

perform restore operation.
ANS5178E
ANS5184E
Restart of the RSM service failed.

Restart the RSM service manually.
Illegal Operation On Following Object:

object

from the TSM server and imported. TSM has tried to
restart the RSM service on the users behalf but has run
into a problem.
Explanation: Requested operation cannot be

performed on this object.
User response: Try another operation on this object, or

try the same operation on another object.
User response: Restart the RSM service manually.

ANS5179E
TSM is unable to continue. Exiting

program.
Explanation: TSM ran into a problem and is unable to

continue. This error message is usually preceded by
other error messages. Resolve those errors and try
again.
System action: Program terminates.
User response: Fix the problem(s) that preceded this
message and then restart TSM.
784
ANS5186E
Server is downlevel, System Services

and System State backup disabled for
this session.
Explanation: The operation cannot be performed

because server version is downlevel.
System action: System Service and System State
backup is disabled for this session.
User response: Must use level 5.2.0 or higher server.
ANS5187E ANS5198E
ANS5187E
Unable to set SHAREAS extended

attribute for file: pathname Return code:
returncode strerror Reason code:
reasoncode
Explanation: You must be the file owner or have

superuser authority.
System action: File processed without setting
attribute.
ANS5192E
NT Active Directory is online. Online

restore is not supported.
Explanation: NT Active Directory is online when

performing a restore operation. Online restore is not
supported.
User response: Reboot computer and enter Active
Directory repair mode, then try the operation again.
User response: The attribute must be set manually.

ANS5193E
ANS5188E
Unable to clear SHAREAS extended

attribute for file: pathname Return code:
returncode strerror Reason code:
reasoncode
Explanation: You must be the file owner or have

superuser authority.
attribute.
ANS5189E
Unable to set APF extended attribute for

file:pathnameReturn code: returncode
strerrorReason code: reasoncode
Explanation: You must have at least READ access to

the BPX.FILEATTR.APF facility class profile andyou
must be the file owner or have superuser authority.
attribute.
Certificate Services is not online.

Offline backup is not supported.
Explanation: Certificate Services is not online when

performing a backup operation. Offline backup is not
supported.
User response: Start Certificate Services and try the
operation again.
ANS5194E
Certificate Services is online. Online

restore is not supported.
Explanation: Certificate Services is online when

performing a restore operation. Online restore is not
supported.
User response: Stop Certificate Services and try the
operation again.
ANS5196W
Invalid key password entered.
Explanation: The key password is invalid.

ANS5190E
Unable to set PROGCTL extended

attribute for file:pathnameReturn code:
returncode strerrorReason code:
reasoncode
System action: TSM allows you to try again.

User response: Enter the correct password.
Explanation: You must have at least READ access to

the BPX.FILEATTR.PROGCTL facility class profile
andyou must be the file owner or have superuser
authority.
ANS5197E

attribute.

ANS5191E
NT Active Directory is not online.

Offline backup is not supported.
Explanation: NT Active Directory is not online when

performing a backup operation. Offline backup is not
supported.
User response: Reboot computer and turn on Active
Directory, and try the operation again.
File Replication Service backup failed.

an error while backing up files under control of the

service and retry the backup operation.
ANS5198E
File Replication Service restore failed.

785
ANS5199I ANS5209E
service and retry the restore operation.
ANS5199I

changes to take effect. Would you like
to reboot the machine now?
Explanation: The machine must be rebooted for the

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.
System action: TSM None.
User response: Select YES to reboot the machine
immediately.
ANS5200I
service-name service needs to be

restarted.
Explanation: The service must be restarted for the

restored changes to take effect.
System action: Changes are not effected.
User response: Restart the service.
ANS5201E
The specified function is not

implemented
Explanation: The specified function is not

implemented.
ANS5204W
Only one backup set may be selected

for restore.
Explanation: Restoring multiple backup sets is not

allowed. Only one backup set may be selected and
restored.
User response: Only one backup set may be selected
for restore.
ANS5205E
An error saving one or more eventlogs
Explanation: An error occurred saving one or more

eventlogs.
operation.
ANS5206E

registry keys.

are exclusively held by another process. This can
happen if the registry keys were previously restored
but the system was not restarted.
User response: Restart the system and try the restore
operation again.

operation.
ANS5202I
One or more system objects were

excluded from processing by entries in
the include-exclude list.
Explanation: One or more system objects were

excluded from processing by entries in the
include-exclude list and the client did not process them.
System action: Excluded objects skipped.
ANS5203E
An error occurred saving one or more

registry keys
Explanation: None.
ANS5207I

changes to take effect
Explanation: The machine must be started for the

changes to take effect.
System action: TSM backed up the files.
User response: Reboot the machine
ANS5208E
An invalid date or time was entered.
Explanation: An invalid date or time value was

entered. Either the syntax of the value was not correct,
or an actual value (for example, 45 for month) was
invalid.
User response: Identify and correct the invalid date or
time value. Refer to the users guide of the
corresponding platform for the correct date syntax.
ANS5209E
System Volume backup failed.

an error while backing up files of the Windows 2000
System Volume
786
ANS5210E ANS5222E
and retry the backup operation
ANS5210E
System Volume restore failed.

an error while restoring files of the Windows 2000
System Volume
ANS5215E
function-type is not allowed on object

object. Object is not sent to the server.
Explanation: The requested operation cannot be

performed on this object. The object is not sent to the
server.
System action: This object is skipped.
User response: Try another operation on this object, or
try the same operation on another object.

and retry the restore operation.
ANS5211E
The Cluster Service is offline. The

Cluster Service must be online to
perform a restore operation.
Explanation: The Cluster Service is offline. The

Cluster Service must be online to restore the cluster
database.
User response: Start the Cluster Service and retry the
operation.
ANS5212E
An error occurred while trying to

rename file space.

because the file space could not be renamed.
ANS5216E
Could not establish a TCP/IP connection

with address tcp-addr:tcp-port. The
TCP/IP error is tcp-err-string (errno =
errno).
Explanation: A TCP/IP connection was attempted

with a server or agent program and failed.
User response: Ensure that the target TCP/IP address
and port number is correct. Check to ensure that a TSM
server or agent has been started at the target TCP/IP
address and is configured to listen at the port listed in
the message.
ANS5217E

delete backed up files.
Explanation: You cannot delete backed up files unless

your TSM administrator has authorized your node to
do so.
System action: TSM does not delete the backed up
files.
User response: Contact system administrator for more

information.

administrator to provide the necessary authorization.
ANS5213W
ANS5219W
NAS objects cannot be selected with

other objects for backup.
Objects of different groups cannot be

Explanation: Backing up NAS objects with other types

of objects is not allowed.
Explanation: Restoring objects of different groups is

not allowed.
User response: Select NAS objects without other

objects to perform backup NAS operation.
User response: Select objects of the same group to

perform restore operation.
ANS5214W
ANS5222E
NAS objects cannot be selected with

other objects for restore.
The archive description exceeds 254

characters.
Explanation: Restoring NAS objects with other types

of objects is not allowed.
Explanation: TSM places a maximum length of 254

characters on the archive description.
User response: Select NAS objects without other

objects to perform restore NAS operation.

a shorter valid archive description.
787
ANS5250E ANS5259W
ANS5250E
An unexpected error was encountered.

TSM function name : function-name TSM
: TSM-rc TSM file : file-name (line-number)
Explanation: None.
ANS5255E
Unable to copy local file local-file to

remote location remote-file.
Explanation: An attempt to transfer a file to a remote

system failed..

User response: Ensure that the directory path on the

remote system exists and that the TSM application has
the proper authority to write to that location.
ANS5251E
ANS5256E
The snapshot provider is not available

for this operation.
Unable to copy remote file remote-file to

local location local-file.
Explanation: TSM was not able to take a snapshot

because the snapshot provider is not available.
Explanation: An attempt to transfer a file from a

remote system failed..
User response: If you are attempting an operation

using the Microsoft Volume Shadow Copy service make
sure that Volume Shadow Copy service is installed on
the system and also ensure that the TSM snapshot
plugin pivss.dll is present.
User response: Ensure that the directory path on the

remote system exists and that the TSM application has
the proper authority to read from that location.
ANS5252E
TSM attempted to execute a system

command which failed. command :
command rc : rc
ANS5257E
The volume volume does not support

the requested VSS operation.
Explanation: The volume does not support the

requested VSS operation. Some reasons for this error
include:
Explanation: TSM needed to execute a system

command in conjunction with a snapshot operation.
v For off-load backup requests, a hardware provider

cannot be found
v For off-load backup requests, the provider does not

support transportable media

ANS5253W
The system could not create Volume

Shadow Copy Services staging directory
dir.
Explanation: The system was unable to create a

user-specified location for the Volume Shadow Copy
Services staging area. The default staging area on the
system drive will be used instead.
v For local backup requests, the provider does not

support persistent snapshots
User response: Retry the request using a supported
backup destination.
ANS5258E

User response: Check the option to specify the staging
area for Volume Shadow Copy Services operations and
specify a valid location.
ANS5254E
The Volume Shadow Copy Services

snapshot plugin pivss.dll was not
found.
Explanation: The system cannot find the VSS snapshot

plugin pivss.dll in any of the plugin locations.
User response: Check the TSM installation to ensure
the plugin was installed correctly.
An error occurred initializing a VSS

request. For more information, see the
TSM client error log.
Explanation: None.
User response: Refer to the TSM client error log for
ANS5259W
Failed to update volume volume for

read-write access used for volume.
Explanation: Changing the volume to read-write

access requires exclusive access to the volume. If the
volume is opened by any application, this operation
will fail.
User response: Close all the applications using the
788
ANS5260W ANS5268W
volumes and use operating systems interface to mount
failed volume for read-write access.
ANS5260W
Restore object volume has volume

either source volume or target volume
volume that has already been selected
for restore from a different snapshot
volumes. It will be restore using
file-level copy.
Explanation: This error can occur when multiple

objects are selected for snapshot restore and have data
overlapping on the volumes and were selected for
restore from different backup versions. Snapshot restore
can only be performed from one local backup.
ANS5264W
Explanation: The snapshot restore requires a plugin

for the specified snapshot provider type. The plugin
must be installed under TSM directory.
System action: Restore will failover to alternate
restore method of file-level copy from snapshot
volume.
obtain and install the required plugin module.
ANS5265W
System action: The restore object identified in the

message will be restored using the file-level copy after
snapshot restore is completed.
User response: Retry the restore of identified object
separately for faster restore using snapshot.
ANS5261W
An attempt to create a snapshot has

failed. Another attempt will be made to
create the snapshot in time seconds.
Explanation: An attempt to create a snapshot has

failed with a retryable error. The program will wait for
a short time and retry the operation.
ANS5262I
Snapshot restore will failover to

file-level copy from snapshot volume.
Explanation: Snapshot restore is not possible due to

an error at this time. TSMwill automatically fails over
to other restore method to complete the restore
operation.
User response: Check TSM error log for more
information from messages preceding this one to
identify the error condition.
ANS5263E
Snapshot module for snapshot provider

failed with error error msg.
Explanation: The snapshot module for identified

snapshot provider failed to perform the operation and
returned with the identified error.
System action: Restore may automatically failover to
alternate restore method file-level copy from snapshot
volume if possible. Otherwise, processing stops.
information from messages preceding this one. Use
snapshot provider interface to identify and correct the
problem.
No snapshot plugin found for snapshot

provider snapshot provider.
Snapshot restore has already been

initialized using snapshot provider
provider module. Another module for
snapshot provider provider can not be
loaded at the same time for restore of
object name.
Explanation: This error occurs when restoring

multiple LOCAL backup objects that were created
using different snapshot providers. Snapshot restore
can only be done using one snapshot interface.
System action: Restore will failover to file-level copy
restore from snapshot volume.
User response: If snapshot restore is desired for the
object identified in the message, restore it using a
separate command.
ANS5266E
File-level copy restore of object name

failed.
Explanation: Data files could not be copied from the

local backup to their destination, causing restore to fail.
System action: Processing continues to another object,
if multiple objects are selected for restore.
information from messages preceding this one.
ANS5267E
Disk Mapper module failed for the

operation.
Explanation: An underlying TSM operation has failed

to perform the operation due to system error.
information from messages preceding this one to
identify cause of the failure. Contact TSM administrator
ANS5268W
The Microsoft Volume Shadow Copy

Services writer name current state (state)
is not valid for the current operation.
Explanation: None.
System action: The system will retry the operation
789
ANS5269E ANS5278W
automatically after thirty seconds up to three times to
allow the writer to return to the proper state. If after
three attempts the writer is still in the incorrect state,
the operation will fail.
User response: Determine if there are other Volume
Shadow Copy Services operations that are occurring
concurrently with the current operation.
ANS5269E
The Microsoft Volume Shadow Copy

Services writer name current state (state)
is not valid for the current operation or
cannot be determined. The last error
reported is error.
Explanation: None.
User response: Check the Microsoft event log to
determine if there are any problems with the writer.
ANS5270E
A VSS restore request with timestamp

time1 conflicts with a restore request
with timestamp time2
Explanation: A VSS restore request was issued which

requires restoring multiple components which reside in
VSS backup documents with different backup
timestamps. For example, a user backs up Exchange
storage group STG1 on Monday and Exchange storage
group STG2 on Tuesday. On Wednesday, the user tries
to restore STG1 and STG2.
ANS5273E
Explanation: None.
User response: See the TSM error log for additional
information.
ANS5274E
ANS5271E
A Microsoft Volume Shadow Copy

Services writer is in an invalid state
before snapshot initialization.

after backup completion.
Explanation: None.
information.
ANS5275E

before restore initialization.
Explanation: None.
information.
ANS5276E

User response: Resubmit the restore request as
separate requests for each component. For example, if
you receive this error trying to restore Exchange
storage groups STG1 and STG2, resubmit a restore
request for storage group STG1 and a separate restore
request for storage group STG2.

after taking a snapshot.

after preparing for a restore operation.
Explanation: None.
information.
ANS5277E

after restore termination.
Explanation: None.
Explanation: None.

information.

information.
ANS5272E
ANS5278W

after snapshot initialization.
Explanation: None.
information.
790
Error processing filename: file not

found.

archive or migrate, no longer exists on the client.
ANS5279E ANS6001S
ANS5279E
Error processing filename: file not

found.

archive or migrate, no longer exists on the client.
ANS5280E
Object enumeration from a file set or

file list failed.
Explanation: For more information, see the IBM Tivoli

Storage Manager client error log.
is complete and retry the command.

ANS5299E
A Flashcopy association exists between

source volume: and a different target
volume: .
Explanation: A Flashcopy association exists between

the source volume and a target other than the
designated target volume.
System action: Restore command will fail.
User response: Please withdraw the Flashcopy
association between the source volume and the target
volume and retry the restore command.
ANS5876I
SET EVENT Activate Retention

completed
User response: See the user response based on other

messages in the client error log.
Explanation: The Data Retention ACTIVATE

transaction has completed.
ANS5281E
System action: TSM activated the objects that were

selected.
A remote backup failure has occurred.

remote node name : node remote address
: address multi-node name : multi-node
error message : msg return code : rc

Storage Manager client error log on the remote system.

ANS5877I
SET EVENT Hold completed
Explanation: The Data Retention HOLD transaction

has completed.
System action: TSM held the objects that were
selected.
ANS5282E
A remote backup failure has occurred.

Storage Manager client error log.
ANS5878I
SET EVENT Release completed
Explanation: The Data Retention RELEASE transaction

has completed.
System action: TSM released the objects that were
selected.
ANS5283E
The operation was unsuccessful.
Explanation: None.
ANS5298E
A Flashcopy background copy is in

progress between source volume: and
target volume: .
Explanation: A Flashcopy background copy from a

previous operation is not complete for the given source
and target volumes.
ANS6001S
NULL character found in the name of

folder/file filename.
Explanation: A NULL character was found in the

name of a file or folder. Some products place a NULL
character in a file name so that the file is sorted
alphabetically to the top of a list. TSM cannot
backup/restore such files.
operation.
User response: Remove the NULL character by
renaming the file or folder.
System action: Command will fail.

User response: Please wait until the background copy
791
ANS7421W ANS7508W
ANS7421W
The archive attribute for file filename

cannot be reset. The return code from
Windows API function
SetFileAttributes() is rc.
Explanation: The client was unable to reset the

archive attribute for the file indicated in the message.
This error is due to an error received from the
Windows API function SetFileAttributes().
ANS7503W
Invalid drive entry
Explanation: An invalid entry is entered on the Drive

field.
System action: TSM prompts you to enter a valid
drive letter.
User response: Enter a valid drive letter or see your
system administrator for the correct syntax.

persists, it may be indicative of a problem with the file.
Contact your system administrator or TSM
ANS7500W
Object object-name could not be bound

to management class mgmt-specified
specified in an option statement.
Explanation: The management class specified in an

include statement was not valid. If the include
statement is an INCLUDE.SIZE statement the
warning message will be issued if an appropriate
copygroup is defined for the management class. For
example, this warning will be issued on a backup
operation if no backup copygroup is defined for the
management class or this message will be issued on an
archive operation if no archive copygroup is defined
for the management class.
System action: The management class on the include
statement is ignored and processing continues.
User response: Contact the TSM administrator to
correct the appropriate copygroup definition on the
TSM Server.
ANS7501E
An invalid host address was received.

Host address is too long.
ANS7504W
Invalid directory entry
Explanation: An invalid entry is entered on the

Directory field.
directory.
User response: Enter a valid directory or see your
ANS7505W
Invalid filename entry
Explanation: An invalid entry is entered on the

Filename field.
System action: TSM prompts you to enter a valid file
name.
User response: Enter a valid file name or see your
ANS7506W
Invalid label entry
Explanation: An invalid entry is entered on the Label

field.
volume label.
User response: Enter a valid volume label or see your
system administrator for correct syntax.
Explanation: An invalid host parameter was found in

the HTTP Request. The parameter is too long. The
maximum length for a host address is 64 characters.
ANS7507W
System action: TSM returns HTTP error code 400 Bad

Request.
Explanation: An invalid entry is entered on the Node

Name field.
User response: Use a host machine with a

valid/shorter host address.

node name.
ANS7502E
User response: Enter a valid node name or see your

An invalid filename was received.

Filename is too long.
Explanation: A filename passed to the dsmcad service

is too long and thus invalid.
System action: TSM returns HTTP error code 400 Bad
Request.
User response: Retry connecting to dsmcad but use a
valid/shorter filename.
792
ANS7508W
The node name entry is invalid. Please

try again.
Duplicate authorization
Explanation: The authorization rule entered by the

user is already defined. Duplicate rules are not allowed.
System action: TSM allows you to enter a different
rule.
User response: Enter an authorization rule that has
ANS7509W ANS7531E
not been defined yet or cancel defining authorization
rules.
ANS7509W
Drive and/or volume label do not exist
Explanation: Either the drive or the volume label or

both do not match the existing ones. Rules must be
defined on existing drives and volumes.
System action: TSM prompts you to reenter drives
and/or volumes or cancel defining authorization rules.
User response: Enter an existing drive and volume to
define the desire rule.
ANS7510E
A NAS node cannot be used for this

operation.
ANS7527E
Explanation: The (-SNAPSHOTROOT) option must be

used in conjunction with only one file specification. It
cannot be used with zero file specification (e.g., an
INCREMENTAL command with no file specifications)
or with more than one file specification.
ANS7528W
Explanation: NAS nodes cannot be used for

operations like Access Another Node.
node name.
The (-SNAPSHOTROOT) option is not

valid in conjunction with num-specs file
specifications.

valid in conjunction with the Logical
Volume Snapshot Agent. Processing will
continue without the use of the Logical
Volume Snapshot Agent.

incompatible with the Logical Volume Snapshot Agent.
The Logical Volume Snapshot Agent provides a
comprehensive snapshot solution without having to use
the (-SNAPSHOTROOT) option. It is strongly
recommended that the snapshot capabilities provided
by the Logical Volume Snapshot Agent be used instead
of using the (-SNAPSHOTROOT) option. Processing
continues without the use of the Logical Volume
Snapshot Agent.
User response: Set the environment variable and

restart TSM processes then retry the operation.
System action: Processing continues without the use

of the Logical Volume Snapshot Agent.
User response: Enter a valid, non-NAS, TSM node

name.
ANS7522E
Environment variable name is not set.
Explanation: Required environment variable as

indicated in the message is not set for TSM processes.
ANS7523E
The hardware type number is not known

to TSM.
Explanation: Due to a configuration or internal error,

underlying snapshot hardware type is not set correctly.

ANS7530E
The snapshot_volume_name cannot end

User response: Check your configuration and error

log file for more information. If unresolved, contact
your TSM administrator for help.
Explanation: The snapshot_volume_name cannot end

with a directory delimiter. This name should specify
the root of a logical volume, e.g., /snapshot, x:,
\\machine\x$, SNAP_VOL:, etc.
ANS7526E

valid in conjunction with any of the
following options: -FILELIST,
-GROUPNAME, and
-VIRTUALFSNAME.

incompatible with the -FILELIST, -GROUPNAME, and
-VIRTUALFSNAME options and cannot be used in
conjunction with any one of those options.

ANS7531E
The (-SNAPSHOTROOT) option is

invalid when processing the NetWare
NDS or Server Specific Information.
Explanation: The (-SNAPSHOTROOT) option is only

intended with NetWare file server volumes and is not
compatible with processing the NDS or Server Specific
Information on NetWare.
793
ANS7532E ANS7560E
ANS7532E
The logical file system specified with

the (-SNAPSHOTROOT) option cannot
be a remote NetWare file system.
Explanation: The (-SNAPSHOTROOT) option is only

intended with local NetWare file server volumes and is
not compatible with remote NetWare volumes.
ANS7533E
The specified file system obj-name does

not exist or is not local.
Explanation: When you use the (-SNAPSHOTROOT)

option, the target and source file systems must be valid,
local file systems. The file systems cannot be non-local,
such as a remote NetWare drive, a remote Windows
drive, or an NFS mount. The (-SNAPSHOTROOT)
option is valid for local operations only.
User response: For the correct use of the
(-SNAPSHOTROOT) option, see the appropriate
Backup-Archive Client Installation and Users Guide book
for your operating system.
ANS7534W
Initialization functions cannot open

/dev/tty special file. errno = errno-value,
Explanation: Special file /dev/tty, required by

command line internal editor could not be opened
errno-value.
System action: Processing continues as if EDITOR
option was set to NO
ANS7543E
Error: Scout is not available for object

query. Please restart the scout deamon.
Explanation: The reconcile process needs the scout

deamon to do a query for all migrated files. If the scout
deamon is nut running it is not possible to run the
reconcile tool in the orphan check mode.
System action: Processing stop.
User response: Ensure that the scout deamon is
running. If the scout deamon is not running, restart is
ANS7551E
The source path cannot contain a drive

letter
Explanation: The entered path cannot contain a drive

letter.
User response: Enter the source path in the correct
format.
ANS7555E
The destination path must contain a

drive letter
Explanation: The entered path must begin with a

drive letter, colon, and root slash.
User response: Enter the destination path in the
correct format.
ANS7556E
An invalid drive letter was entered
Explanation: You entered an invalid drive letter.

System action: TSM prompts you for the correct drive
ID.
User response: Reenter the drive ID in the correct
format.
User response: Check your terminal settings.

ANS7560E
ANS7535W
Command line internal editor can not

be initialized.
Explanation: EDITOR option is set to YES in the

options file, but command line internal editor can not
be started.
System action: Processing continues as if EDITOR
option was set to NO
User response: Check previous messages to determine
the reason why the internal editor could not be started.
794
Drive drive-name has no volume label.

Backup/Archive not allowed.
Explanation: The specified drive-name selected cannot

be backed up.
System action: TSM rejected the selected drive.
ANS7561E ANS8002I
ANS7561E
Drive drive-name is unavailable
keys were previously restored but the system was not

restarted.
Explanation: In an attempt to process a file, the

specified drive-name was found unavailable.
System action: TSM did not process the file.
User response: Restart the system and try the restore

operation again.
User response: Determine why the drive was not

available, make it ready, and retry the operation.
ANS7564E
Backup or archive of drives with

duplicate volume labels is not allowed.
Explanation: You tried to back up or archive a drive

that has a duplicate volume label. Because TSM uses
the volume label to keep track of backup or archive
System action: TSM cannot select the drive for backup
or archive operations.
the system, exit TSM and assign a unique volume label
to the drive. Restart TSM and try the operation again.
ANS7701E
The specified directory cannot be

created.
Explanation: The directory contains invalid characters,

or you are not authorized to create the directory.
System action: The directory selection dialog remains
open so that you can specify another directory name.
User response: Specify another directory name.
Ensure that the directory contains valid characters and
that you have proper authorization to create the
directory.
ANS7709E
Restore operation failed. Not all files

were restored.
Explanation: Restore operation failed due to an error.

ANS7642E
An error occurred creating the registry

directory structure.
Explanation: An error occurred while creating the

directory structure to save or replace a registry key.
System action: Registry function fails.
User response: Ensure that the user account that is
running the backup of the registry has the proper
authority. If the user account has the proper authority,
you might need to restart the machine. There might be
operations that are pending which have a file or files in
the registry directory structure locked.
System action: Operation completed.

ANS8000I
Server command: command
Explanation: The specified command is being sent to

the server. This message is displayed when the
command is generated from a macro or when the client
is running in batch mode.
System action: The command is sent to the server for
processing.
ANS7650E
The user does not have sufficient

privileges to execute IBM Tivoli Storage
Manager.
Explanation: The user account used to execute IBM

Tivoli Storage Manager must have the Back up files
and directories and the Restore files and directories
security settings assigned.
User response: Assign the Back up files and
directories and the Restore files and directories
security settings to the account using the Windows
Local Security Settings tool or use a different user-id to
execute IBM Tivoli Storage Manager.
ANS7660E

registry keys.

are exclusively held by another process. The registry
ANS8001I
Return code return code value.
Explanation: The error code shown has been returned

from the preceding server command. This message is
preceded by a server message explaining the reason for
the error code.
ANS8002I
Highest return code was return code

value.
Explanation: At exit from the client, the highest return

code encountered during the session is displayed.
System action: This value is used as the program exit
code.
795
ANS8003I ANS8017E
ANS8003I
Process number process ID started.
ANS8013I
Invalid encryption key password
Explanation: As a result of the preceding server

command, the process whose ID is shown starts to
execute the command. The process can be monitored
using the QUERY PROCESS command.

entered.
System action: User is prompted for encryption key

password.

ANS8008W
Redirection inside macro whose output

is redirected is ignored.
Explanation: An output redirection symbol has been

encountered inside a macro. However, the output of the
macro itself (or a higher level macro) is already being
redirected.
System action: The redirection request is ignored.
ANS8009E
Exiting due to command or option

errors.
Explanation: Because of errors in command line or

option file parameters displayed earlier, the
administrative client session is ending.
System action: The client exits.
User response: Enter the correct encryption key

password.
ANS8014E
Insufficient information to connect to

host.
Explanation: The client options file or command line,

or both, do not contain enough communications
information to successfully connect to the server
system. For example, with TCP/IP both the TCPPort
number and TCPServer address are required to make a
connection.
System action: The administrative client session is
ended.
User response: Determine what information is needed
to establish a connection for your communications
method and then specify all that information in your
client options file or on the administrative client
command line.
User response: Fix the option file parameter in error

and restart the client, or restart the client with proper
command line parameters.
ANS8015E
ANS8010E
Explanation: An unknown error code is returned from

the routine that processes the client options file.
An attempt to backup or archive a file

has exceed the maximum number of
retries.
Explanation: After five unsuccessful attempts to

backup or archive a file, the client will no longer
attempt to send the file to the server.
User response: Check the console or schedule log for
additional information. Retry the operation at a later
time.
ANS8012E
Option processing storage exhausted.
File file spec, error code error code from

options processing.

ended.
User response: Attempt to determine the error and
correct it. If the problem persists, contact your service
representative.
ANS8016E
Command line parameter parameter

number: parameter is too long.
Explanation: The specified command line parameter

exceeds the maximum length for a command line
parameter.
Explanation: During processing of the client options

file, the client runs out of memory.

ended.
User response: Reissue the command with a shorter

parameter.
User response: Make more memory available and

restart the administrative client.
ANS8017E
Command line parameter parameter

number: parameter is not valid.
Explanation: The command line parameter shown is

not a valid administrative client parameter.
796
ANS8018E ANS8027E
ended.
User response: Allow processing to continue or exit

the session and correct the file name.

parameters.
ANS8023E
ANS8018E
Administrative command not valid in

Console mode.
Explanation: The Console Mode option has been

specified but the client encounters what appears to be a
server command on the command line.
Unable to establish session with server.
Explanation: The administrative client cannot start a

session with the requested server. This message is
preceded by another message that explains the reason
for the error.
ended.

ended.
User response: Attempt to correct the error. If the

User response: Reissue the command with no server

command.
ANS8024E
ANS8019E
Id and password must be supplied in

Batch mode.
Explanation: A server command has been encountered

on the command line, but no administrator ID or
password, or both, are specified.
End of macro after continued command

line.
Explanation: A macro containing a continuation line

has been executed, but no more lines are found in the
macro file.
System action: The continued command is ignored,
and an error return code is set for the macro.

ended.
User response: Correct the macro in error.
User response: Reissue the command and include the

-ID and -PASSWORD parameters on the command line.
ANS8025E
ANS8020E
Unable to open file file spec for output.
Explanation: The file name specified in the -OUTFILE

option cannot be opened.
I/O Error reading command input.
Explanation: The client is unable to read an input

command from the terminal.
ended.
System action: The -OUTFILE parameter is ignored.
User response: Correct the problem on the terminal

and retry the administrative session.
User response: Allow processing to continue or exit

the session and correct the file name.
ANS8026E
ANS8021E
Exiting Batch mode session due to

output file error.
Explanation: The file specified in the -OUTFILE

parameter cannot be opened for a session running in
Batch mode.
ended.
output file name or make space available for the output
file.
Input line longer than maximum of max

length characters. Use continuation.
Explanation: An input command line is longer than

the maximum input line length allowed.
System action: The input command is ignored.
User response: Reissue the command with several
lines using continuation characters.
ANS8027E
Unterminated comment in command.
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
to the standard output stream.
User response: Reissue the command with matching

comment marks.
System action: Output that would have been written

to the output file is written to the standard output
stream.
797
ANS8028E ANS8038E
ANS8028E
Command longer than maximum of max

length characters.
ANS8034E
Your administrator ID is not recognized

by this server.
Explanation: An input command longer than the

maximum command length allowed has been entered.
Explanation: The administrator ID entered is not

known to the requested server.
System action: The administrative session terminates.
User response: Reissue the command with fewer

characters. This could mean replacing series of
repeating blanks with a single blank.
User response: Ensure that you are using a registered

administrative ID for the server to which you are
connecting.
ANS8029E
ANS8035E
Macro processing terminated.
Explanation: An error occurs during processing of a

macro because the -ITEMCOMMIT option is not
specified on the command line. Processing of this
macro and any higher level macro is terminated.
System action: All current macro processing ends.
User response: Specify the -ITEMCOMMIT option on
the command line to ensure that the server commits
each command in the macro individually.
ANS8030E
Substituted command longer than

maximum of max length characters.
Explanation: After variable substitution, an input

command is longer than the maximum command
length allowed.
User response: Reissue the command with fewer
characters. This may require replacing a series of
repeating blanks with a single blank.
ANS8031E
Missing name of macro to execute.
Explanation: A macro command is encountered that

does not contain a macro name.
User response: Reissue the macro command with a
macro file name.
Explanation: During an administrative session, a

keyboard interrupt or break sequence is entered.
System action: The administrative session is
terminated.
User response: Restart the administrative client
session.
ANS8036E
Could not allocate storage to process

macro file spec.
Administrative command not valid in

Mount mode.
Explanation: The Mount Mode option has been

specified but the client encounters what appears to be a
server command on the command line.
ended.
User response: Reissue the command with no server
command.
ANS8037E
Missing name for redirection file.
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
file name.
ANS8038E
ANS8032E
Interrupted by user.
Unable to open file file spec for

redirection.
Explanation: The client cannot allocate enough

memory to process the macro shown.
Explanation: A command has been entered that

specifies an output redirection file, but the file cannot
be opened.

returned.
System action: The command is ignored and an error

is returned.

client and retry the macro command.

output file name or make space available for the output
file.
798
ANS8041E ANS8054E
ANS8041E
The server connection has been lost and

cannot be re-established.
Explanation: During an administrative session, the

client discovers that the connection with the server has
been severed; an attempt to reestablish the connection
fails.
User response: Determine the cause of the failure;
then try to restart the session at a later time. If the
ANS8045E
Communications error.

occurs during an administrative session.
ANS8046E
The client connection with the server

has ended due to an unexpected error.
Explanation: The TSM error log might contain other

messages related to this error.
System action: The client session ends.
User response: Check the communication link
between the client and server to ensure that it is
operational. Examine the client error log for additional
ANS8047E
The client connection with the server

has ended due to a communications
buffer overflow.


ANS8050E
The TSM server is not accepting

administrative sessions on the client
port. You must use the port number
designated for administrative sessions.
Explanation: The TSM server is configured to not

allow administrative sessions on the client TCP/IP
port. A different port number has been designated for
use by administrative sessions.
System action: The administrative session is not
established.
User response: Use the TCPADMINPORT client
option to specify the TCP/IP port number that the TSM
server uses for administrative sessions. See your TSM
server administrator if you do not know the correct
port number.
ANS8051E
User is not authorized to get prompted

for encryption key
Explanation: The current passwordaccess option

setting and user authority do not allow encryption.
System action: You are not prompted to set the
encryption key password.
User response: Request the TSM authorized user to
set passwordaccess=GENERATE in dsm.sys and set the
encryption key password. (The encryption key
password is set the first time that the TSM authorized
user backs up a file).
ANS8052E
Unable to decrypt file filespace

namepath-namefile-name ....Please try to
restore this file individually
Explanation: File could not be decrypted and restored.

System action: File is not restored.
User response: Restore the file separately.

User response: Try the operation again. Check the
communication link between the client and server to
ensure that it is operational. Examine the client error
log for additional messages related to this error.
ANS8049E
A connection with the server cannot be

established due to a communications
time-out.

between the client and server to ensure that it is
ANS8053E
The network cannot be accessed.

between the client and server to ensure it is
messages related to this error. Try the operation again.
ANS8054E
No memory available to service request.
Explanation: Sufficient server memory is not available.

User response: Retry the administrative session. If the
799
ANS8055E ANS8064E
ANS8055E
ANS8060W
The server has insufficient resources to

perform the operation.
Explanation: The server ran out of resources. A lack of

storage or other problem condition does not allow any
new activity. The server activity log might contain
additional information about this problem.
User response: The TSM administrator should
examine the TSM server activity log to determine the
source of the resource constraints. Try the operation
again when the server is under less load.
ANS8056E
Your administrator ID is locked.
Explanation: The administrative ID entered has been

locked by a system administrator and cannot be used.
User response: Contact your system administrator to
unlock your ID.
ANS8057E
The requested language files are not

available.
Explanation: The NLS repository for the language

specified is not available.
User response: Use a different language or obtain a
copy of the NLS repository for the language desired.
ANS8059E
The TCP/IP functions have not been

linked into this module.
Explanation: The ADSM TSO administrative client

cannot find the TCP/IP functions required to support
TCP/IP communications.
System action: The connection to the server fails.
User response: The TCP/IP functions must be
included in the DSMADMC/ANSADM module. Refer
to the Program Directory for this product for
instructions on how to include the TCP/IP functions in
the DSMADMC/ANSADM module.
A previously established incremental

flashcopy relationship for local backup
version with backup date datetime for
database configuration dbconfig has
been withdrawn for this backup
operation. The reason for this is that the
local backup policy defined for this
database specifies a single backup
version. This backup operation is
requesting a copytype of NOINCR
forcing the reuse of the single set of
target volumes.
Explanation: The local backup policy defined for this

database specifies a single backup version. The target
volume set defined for this backup version is currently
engaged in an incremental flashcopy relationship. This
backup operation is requesting a copytype of NOINCR
forcing the withdraw of the incremental flashcopy
relationship. Refer to TSM documentation for
additional information on local backup policy.
ANS8061E

allow a signon as a Unicode enabled
administrative client
Explanation: The administrative client is unable to

establish a connection to the server because of a
unicode enabling mismatch between server and client.
User response: Register a new administrator from a
different administrative client or the server console, and
signon with the new administrator ID.
ANS8062E
C2C is not allowed to take place when

server authentication is turned off.
Explanation: C2C is not allowed to take place when

server authentication is turned off.
User response: Turn server authentication on.
ANS8064E
Communication timeout. Reissue the

command.
Explanation: The connection to the server is ended

because of a communication timeout from the server.
command.
User response: Reissue the command. If necessary,
increase the values of IDLETIMEOUT and
COMMTIMEOUT options in the server options file.
800
ANS8104W ANS8516E
ANS8104W
Cannot determine EFS status of the file

system file-system name, errno=errnor
number, processing data normally.
Explanation: IBM Tivoli Storage Manager cannot

determine EFS status on the specified filesystem. No
EFS specific processing will take place for files on this
filesystem. If EFS is indeed enabled on the filesystem,
all accessaible files will be backedup in cleartext.
System action: The filesystem will be processed as a
regular filesystem.
User response: Contact your system administrator to
determine the cause of the error reported in the
message.
ANS8500I
User action cannot be completed due to

the following error:
Explanation: An error has occurred while processing

your requested action, user action. The message
displaying with this message identifies the error.
System action: The system does not process your
requested action.
User response: See Explanation for the message
displaying with ANS8000I.
ANS8501E
Internal error in this graphical user

interface. Try one of the following in
the order listed: 1) close this window
and reopen it 2) close this object and
reopen it 3) shut down this graphical
user interface and restart it 4) save
dsmerror.log residing in the directory
specified by DSMG_LOG and contact
your service representative for
assistance.|Graphical User Interface Internal error
directory if DSMG_LOG is not specified, and contact

your service representative for assistance.
ANS8502S
Due to this error, processing cannot

continue. This graphical user interface
will shut down.
Explanation: A severe error has occurred. The

message displaying with this message identifies the
actual error.
System action: The TSM Administrators graphical
user interface closes.
User response:
v Restart the TSM Administrators graphical user
interface.
v If this problem persists, save the dsmerror.log file
residing in the directory specified by the
environment variable DSMG_LOG or in the current
directory if DSMG_LOG is not specified, and contact
your service representative for assistance.
ANS8503I
No matching option found for pattern:

pattern.
Explanation: You specified a pattern which does not

match the name of any supported option.
System action: This message is the only response to
your query.
User response: Specify a different pattern or omit the
pattern to display all options.
ANS8504E
A message related to this window or

your requested action cannot be
displayed due to an internal error in
this graphical user interface. Refresh
this window or request the action again.
Explanation: An internal processing error has

occurred in the TSM Administrators graphical user
interface while processing your requested action.
Message ANS8000I, which displays with this message,
identifies your requested action.

occurred in the TSM Administrators graphical user
interface while attempting to display an informational,
warning, or error message related to the current
window or your requested action.

requested action.
System action: The system may or may not process

your requested action.
User response:
User response: View the Activity Log window in the

Server object to find out if your requested action has
completed. If it has completed successfully, refresh the
current window to show its results. If it has not
completed successfully, make your request again.
v Close the window in which your failed request was

made and reopen it.
v If this problem persists, close all windows associated
with the object toward which your failed request was
directed and reopen them.
v If this problem persists, shut down the TSM
Administrators graphical user interface and restart
it.
v If this problem persists, save the dsmerror.log file
residing in the directory specified by the
environment variable DSMG_LOG or in the current
ANS8516E
The values entered for the New

Password and Reenter New Password
fields do not match. Type the same
value into both fields.
Explanation: You have entered different values into

the New Password and Reenter New Password fields.
801
ANS8566E ANS8781E
requested action.
ANS8778E
User response: Enter the same value into the New

Password and Reenter New Password fields.
ANS8566E
You have not entered or selected a value

for this required field. Enter or select a
value for this field.
A browser program cannot be found or

cannot be started. An error occurred
executing the command.command Verify
that a browser is installed and works
correctly on your local machine.
Explanation: A browser program cannot be found, so

it is not possible to access the IBM Tivoli Web site and
online documentation.
Explanation: You have not entered or selected a value

for a required field.
System action: TSM continues to process user

requests.

requested action.
User response: For the Windows platform, the default

system browser is used. Verify that a browser is
installed on your machine.
User response: Enter or select a valid value for this

required field.
ANS8779E
ANS8776E
The IBM Tivoli Enterprise Space

Management Console cannot be started.
Java Runtime Environment version
version by company has been detected on
machine. A Java Runtime Environment
version or higher is required to run this
program. If you have already installed
Java version on this machine, please
ensure that the correct Java executable is
on your PATH, otherwise you can
download it from webAddress and start
the program again.
Explanation: IBM Tivoli Enterprise Space

Management Console cannot be started because the
Java runtime environment does not meet the
requirements.
System action: A confirmation dialog is displayed for
you to close the application, or to open a browser with
a link to the Web site where you can download the
correct version of Java.
User response: Verify that the correct java executable
is on your PATH or install the required version of Java
runtime environment and start the program again.
ANS8777E
The IBM Tivoli Enterprise Space

Management Console cannot be started.
An error occurred trying to load Tivoli
look and feel. Verify that the product is
correctly installed.
Explanation: IBM Tivoli Enterprise Space Management

Console cannot be started because the library that
defines the Tivoli look and feel cannot be found.
System action: The IBM Tivoli Enterprise Space
Management Console shuts down.
User response: Verify that the product is correctly
installed. If IBM Tivoli Enterprise Space Management
Console still cannot be started, contact your system
802

cannot be started. One of the following
browsers is required: browser-list Verify
that one of these browsers is installed
and works correctly on your local
machine.

it is not possible to access the IBM Tivoli Web site and
online documentation.
requests.
User response: For UNIX platforms, a list of
supported browsers is provided in the README.
Install the required browser to access the IBM Tivoli
Web sites and online documentation.
ANS8780E

cannot be started. Check the file-name
file on your local machine for more
information.

it is not possible to access the Web site or online
documentation.
requests.
User response: Install a browser to access the Web site
or online documentation.
ANS8781E
The system could not log on to TSM

client node node-name on machine-name.
Make sure your data and password are
correct and that caps lock key is not on.
The Space Management Agent must be
running at the specified port on the
machine to which you are attempting to
log on to.
Explanation: The system was not able to connect to

the specified client node.
ANS8782E ANS8785E
requests.
the cause of the problem, then see your system

User response: Verify that:

v the information provided to connect is correct
ANS8784E
v the machine is reachable in the network

v HSM is installed on the specified machine and a
Space Management Agent is running at the specified
port.
ANS8782E
An error occurred while loading file

system information on fs-name. Verify
that the Space Management agent is
running on the client node machine.
Check also the local-log-file file in the
installation directory of your local
machine and the $DSM_DIR/error-file
file on machine if present. If this does
not identify the cause of the problem,
contact your system administrator
and/or TSM technical support for
further assistance.
Explanation: An error occurred while loading file

system information on the selected client node
System action: Disconnects the client node.
User response: Verify that the Space Management
agent is running on the client node machine. Check
also the dsmsm.log file in the installation directory of
your local machine and the $DSM_DIR/dsmerror.log
file on the client node machine if present. If this does
not identify the cause of the problem, contact your
system administrator and/or TSM technical support for
further assistance.
ANS8783E
An error occurred loading file system

properties of fsName required to show
space usage graphical information.
Verify that the Space Management agent
is running on the client node machine.
further assistance.
Explanation: An error occurred while loading file

system properties on the selected client node.
System action: Continue to process other file system
properties.
An error occurred initializing the client

nodes table. Your local configuration file
config-file might be corrupted. Remove
it from your installation directory and
start the program again. Check also the
log-file file on your local machine for
more information.
Explanation: The client nodes table cannot be

initialized.
System action: The IBM Tivoli Enterprise Space
Management Console shuts down.
User response: It is possible that your local settings
file dsmsm.cfg is corrupted. Try to remove it from
your installation directory and start the program again.
Check the dsmsm.log file in the installation directory of
file on the client node machine if present. If this does
not identify the cause of the problem, contact your
system administrator and/or TSM technical support for
further assistance.
ANS8785E
An error occurred disconnecting the

system from the client node node-name.
The Client node is being disconnected
without deleting internal HsmSystem
objects. Verify that the Space
Management agent is running on the
client node machine. Check also the
local-log-file file in the installation
directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the
cause of the problem, contact your
system administrator and/or TSM
Explanation: An error occurred disconnecting the

system from the client node. It was not possible to
delete internal HsmSystem objects.
System action: The client node disconnected without
deleting HsmSystem objects.
agent is running on the client node machine. Check the
dsmsm.log file in the installation directory of your local
machine and the $DSM_DIR/dsmerror.log file on the
client node machine if present. If this does not identify
the cause of the problem, contact your system
administrator and/or TSM technical support for further
assistance.

agent is running on the client node machine. Check
also the dsmsm.log file in the installation directory of
file on the client node machine. If this does not identify
803
ANS8786E ANS8790E
ANS8786E

information from the selected client
node. Verify that the Space Management
agent is running on the client node
machine. Check also the local-log-file file
in the installation directory of your local
file in the client node machine if
ANS8788E
An error occurred starting manually

threshold migration on file-system. Verify
that the Space Management agent is
running on the client node machine.
further assistance.
Explanation: An error occurred loading file system

information from the selected client node.
Explanation: An error occurred starting the manually

threshold migration on the selected client node.
System action: File System information is not loaded
System action: Threshold migration is not started

manually.

assistance.
User response: Check the dsmsm.log file in the

installation directory of your local machine and the
$DSM_DIR/dsmerror.log file on the client node
machine if present. If this does not identify the cause of
the problem, contact your system administrator and/or
TSM technical support for further assistance.
ANS8789E
ANS8787E

information from nodename client node.
The client node is being disconnected.
further assistance.
Explanation: An error occurred loading file system

information from the selected client node.
System action: The client node is disconnected
assistance.
An error occurred trying to deactivate all

managed file systems of client-node.
further assistance.
Explanation: An error occurred trying to deactivate all

managed file systems of the selected client node.
System action: File systems are not deactivated.
ANS8790E
An error occurred trying to reactivate all

managed file systems of client-node.
further assistance.
Explanation: An error occurred trying to reactivate all

managed file systems of the selected client node.
804
ANS8791E ANS8795E
System action: File systems are not reactivated.
ANS8793E

ANS8791E
An error occurred trying to add space

management to fs-name file system.
further assistance.
Explanation: An error occurred trying to add space

management to the selected file system.
System action: Space management is not added to the
selected file system.
Explanation: An error occurred trying to deactivate

the selected file system.
System action: The selected file system is not
deactivated.
ANS8794E

ANS8792E
An error occurred trying to remove

space management from file-system file
system. Verify that the Space
Management agent is running on the
client node machine. Check also the
Explanation: An error occurred trying to remove

space management from the selected file system.
System action: Space management is not removed
from the selected file system.
An error occurred trying to deactivate

file-system file system. Verify that the
Space Management agent is running on
the client node machine. Check also the
An error occurred trying to reactivate

file-system file system. Verify that the
Space Management agent is running on
the client node machine. Check also the
Explanation: An error occurred trying to reactivate the

selected file system.
System action: The selected file system is not
reactivated.
ANS8795E
An error occurred trying to save your

settings to config-file configuration file
on your local machine. Check the log-file
file in the installation directory of your
local machine for more information.
Explanation: An error occurred trying to save your

settings to dsmsm.cfg configuration file on your local
machine.
System action: Customized GUI settings are not saved
to the local machine
805
ANS8818E ANS8826E
ANS8818E
An error occurred trying to apply your

changes. Your changes have not been
applied to the system. Contact your
Explanation: An error occurred trying to apply your

changes.
System action: User changes are not applied.
ANS8819E
ANS8822E
Explanation: Space Management agent was not able to

process a HSM File System function, because no HSM
File System object was found.
System action: Last operation is skipped.
User response: Reconnect to the Space Management
agent. If this does not solve the problem restart the
Space Management agent.
ANS8823E
The following trace flag(s) are not valid:

trace-flag-list. Correct them before
continuing.
Explanation: One or more of the trace flags are not

valid.
System action: Prompts the user to correct the trace
flags.
User response: Correct the wrong trace flags.
HSM File System Object was not found

on Space Management agent. The error
occurred when calling function:
function-name The last operation was not
processed correctly.
A Protocol error occurred in

communication with the Space
Management agent This error occurs
when a session with the Space
Management agent was lost, or network
error caused synchronization problem
between the Space Management console
and the agent.
Explanation: Space Management console and Space

Management agent has different session and
transaction key in the communication header.
ANS8820E
The HSM System Object was not found

on the Space Management agent. The
error occurred when calling function:
function-name. The last operation was not
processed correctly.
Explanation: The Space Management agent was

unable to process a HSM System function, because the
HSM System object was not found.
System action: The last operation is skipped.
User response: Reconnect to the Space Management
agent. If this does not solve the problem restart the
Space Management agent.
ANS8821E
Unable to create requested HSM object

on Space Management agent. The last
operation was not processed correctly.
The problem is caused from a memory
problem. Try to free memory on the
system where the Space Management
agent is running. Or restart the Space
Management agent.
Explanation: Space Management agent was not able to

create a requested HSM object because not enough free
space was found on the system.
User response: Try to free more memory on the
system where the Space Management agent is running,
or restart the Space Management agent.
806
User response: Restart Space Management console

and Space Management agent.
ANS8824E
A internal error occurred in the Space

Management agent. The error occurred
in function : function-name
Explanation: Not defined exception caused a internal

error in the Space Management agent.
User response: Restart Space Management agent. If
this does not solve the problem contact TSM technical
support.
ANS8825E
The Space Management API was unable

to locate option object The error
occurred in function : function-name
Explanation: Not defined exception caused this

internal error in the Space Management API.
User response: Contact TSM technical support.
ANS8826E

to query a HSM device. This error
occurs because the HSM kernel
extension was not loaded correctly
Explanation: Because of a wrong configuration HSM
ANS8827E ANS8832E
was not able the load the kernel extension. This causes
to fail the query for global activation of the HSM
system.
System action: Query for global HSM activation is
skipped.
ANS8830W
Different server name stanzas

(HSM-stanza and BA-stanza) for
file-system-name file system for space
management and backup-archive.
User response: Check the configuration of the HSM

system. If you can not find any problem in the
configuration contact TSM technical support.
Explanation: The server name stanzas you specified

for the space management (HSM) client and the
backup-archive (BA) client are different. The inline
backup and stub restore features will be unavailable for
the file system.
ANS8827E

to locate global control block. The error
occurred in function : function-name
User response: Contact TSM technical support.
User response: If you want to allow inline backup and

stub restore for the file system, the MIGRATESERVER
and DEFAULTSERVER options must specify the same
SERVERNAME stanza in dsm.sys. You may also choose
to supply a server stanza name using the
SERVERNAME option in dsm.opt or on the command
line. In either case the stanza name must match the
stanza specified in the MIGRATESERVER option.
ANS8828E
ANS8831E
Explanation: Not defined exception caused this

internal error in the Space Management API.
System action: Load connection settings function is
skipped.
The Space Management API lost the

session with the server. This problem is
caused by a connection failure with the
server. Check to see if your Space
Management Client machine has a
network connection to the TSM server.
Explanation: This error occurs when the Space

Management API has connection problems with the
TSM server.
System action: Session with server gets lost and
server operation is skipped.
User response: Check the network connection with
TSM server machine. See the error log file for
additional information why the session gets lost.
Restart the Space Management Agent if the connection
re-established automatically.
ANS8829E

to initialize the HSM system. The error
is caused from a problem to initialize a
DMAPI session.
Explanation: This error is caused from a problem to

initialize a DMAPI session.
System action: The HSM system cannot be initialized
and the Space Management Console is ended.
User response: Try to restart Space Management
Agent. If this does not solve the problem, see the error
log for additional information and contact TSM
technical support.
The Space Management API could not

find file system : function-name An
incorrect file system name was passed to
the Space Management API. Ensure that
the file system that was selected in the
file system list is still valid. Refresh the
file system view in the Space
Management Console by pressing F5 on
your keyboard or select Refresh` under
the View menu.
Explanation: The Space Management API could not

find the file system that was specified in the Space
Management Console. A reason could be that the file
system was unmounted and is not longer existing on
the system.
System action: Getting file system information for the
specified file system name is skipped.
User response: Update the file system list in the Space
Management Console by pressing F5 on your keyboard
or selecting Refresh in the View menu.
ANS8832E

retrieve TSM policy settings from the
server.
Explanation: The Space Management API tried to get

TSM policy settings from the server and failed for a
unknown reason.
System action: Getting TSM policy settings fails and
policy information fields are not filled up in the Space
Management Console.
User response: See the error log file for additional
information.
807
ANS8833E ANS8839E
ANS8833E

retrieve TSM policy settings from the
already loaded list.
Explanation: The Space Management API tried to get

TSM policy settings from the management list and
failed for a unknown reason.
System action: Getting TSM policy settings fails and
policy information fields are not filled up in the Space
Management Console.
information.
ANS8834E

to get file system information for file
system : filesystem-name.
User response: Free more memory on the system

where the Space Management agent is running, or
restart the Space Management agent.
ANS8837E

to get configuration data from managed
file system : filesystem-name. The
problem is caused from a error when
reading dsmmigfs table entry.
Explanation: The Space Management API reads

information from dsmmigfs table to get HSM managed
files system configuration. This error occurs when the
API is unable to read an entry from this table.
System action: Getting HSM managed file system
configuration fails and information is not displayed in
the Space Management Console.

retrieve the file system information for a selected file
system.
User response: See the error log for additional

information on errors occurring when reading entries
from the dsmmigfs table.
System action: Getting file system information fails

and information are not displayed in the Space
Management Console.
ANS8838E

information.
ANS8835E

to get file system status for file system :
filesystem-name. System call to get file
system status returned with error.

retrieve the file system status for a selected file system.
The error is caused from a failed system call on the file
system.
System action: Getting file system status fails and
information are not displayed in the Space
Management Console.
information.
ANS8836E
An object creation error occurred in the

Space Management API The error
occurred in function : function-name. The
problem is caused from a memory
problem. Try to free memory on the
system where the Space Management
agent is running. Or restart the Space
Management agent.
Explanation: Caused from a out of memory problem

the Space Management API could not create a
requested object.
System action: The requested function fails and
cannot retrieve information to the Space Management
Console.
808
The Space Management API can not set

HSM managed file system configuration
for file system : filesystem-name. The
configuration cannot be set because this
file system is NOT HSM managed.
Check to see if the managed file system
that was selected in the file system list
is still HSM managed. Refresh the file
system view in the Space Management
Console by pressing F5 on your
keyboard or select Refresh` under the
View menu.
Explanation: The file system that you selected from

the file system list in the Space Management console is
not longer HSM managed and no configuration can bet
set for it. A reason could be that the file system was
unmanaged from a other user.
System action: Setting HSM managed file system
configuration fails.
ANS8839E
A wrong stub file size was passed to the

Space Management API for file system :
filesystem-name. The stub file size that
was entered in the file system properties
dialog is not supported by this file
system. Correct the stub file size value
in the file system properties dialog of
Explanation: The Stub file size that you has specified

is not supported by this file system.
System action: Wrong stub file size is not applied to
the file system.
ANS8840E ANS8847E
User response: Correct the stub file size in the file
system properties dialog of the Space Management
Console.
ANS8840E
The maximum number of candidates

that was specified for file system :
filesystem-name is out of range. The
maximum number of candidates value
that was entered in the file system
properties dialog is out of range. Correct
the maximum number of candidates
value in the file system properties
dialog of the Space Management
Console.
Explanation: The maximum number of candidates

value that was specified is out of range for this file
system.
System action: Wrong maximum number of
candidates value is not applied to the file system.
User response: Correct the maximum number of
candidates value in the file system properties dialog of
ANS8841E
The server name that was specified for

the file system : optfile-name is not valid.
Correct the server name value in the
client node properties dialog of the
Space Management Console.
Explanation: The server name that was specified is

not valid.
System action: Wrong server name value is not
applied to the system options file.
User response: Correct the server name value in the
client node properties dialog of the Space Management
Console.
ANS8842E
The Space Management API was not

able to modify system options file :
optfile-name because of insufficient
privilege. Use root user to change HSM
managed file system configuration.
Explanation: User has no rights to modify system

options file.
System action: Changes are not applied to the system
options file.
system options file are not correct.

options file.
User response: Correct the include/exclude list in the
ANS8844E
A incorrect preferred node or server

name was specified in the HSM
configuration for filesystem-name. Correct
the preferred node and server name
value in the HSM configuration.

change preferred node settings because a wrong value
was specified
options file.
User response: Correct the preferred node and server
settings in Space Management Configuration.
ANS8845E
A incorrect owner node or server name

was specified in the HSM configuration
for filesystem-name. Correct the owner
node and server name value in the HSM
configuration.

change owner node settings because a wrong value was
specified
options file.
User response: Correct the owner node and server
settings in Space Management Configuration.
ANS8846E

able to update the HSM managed file

apply configuration changes to the HSM managed file
system.
System action: Changes are not applied to HSM
managed file system.
User response: See error log file for additional
information why the update of the file system fails.
User response: Run as root user to change HSM

managed file system configuration.
ANS8847E
ANS8843E

lock the SDR file for the file system.
No correct include/exclude settings are

found in system options file :
optfile-name. Correct the include/exclude
list in the system options file.
Explanation: The include/exclude settings in the

able to obtain a lock on SDR file for file
System action: Changes are not applied to HSM

managed file system.
809
ANS8848E ANS8854E
information on why the lock on the SDR file fails.
ANS8848E

open file system status file to retrieve
managed file system statistics for :
filesystem-name. Reason could be
insufficient permissions or that the file
does not exist. The managed file system
statistics are not retrieved from the
HSM system.

retrieve managed file system information from file
system status file. The error occurred when the API
tries to open the file for reading.
ANS8851E

able to add HSM to file system :
filesystem-name. This error occurs because
selected file system is not supported to
add HSM.

add HSM to a unsupported file system.
System action: The add HSM operation fails and HSM
is not added to the selected file system.
User response: Select a supported file system to add
HSM.
ANS8852E
System action: Managed file system statistics are not

retrieved and information is not displayed in the Space
Management Console.

selected file system is already HSM
managed.

information on why opening the file system status file
fails.
Explanation: The Space Management API attempt to

manage a already HSM managed file system.
ANS8849E
System action: The add HSM operation fails and the

selected file system stays HSM managed.

able to load HSM managed file system
statistics for : filesystem-name. Check to
see if the managed file system that was
selected in the file system list is still
HSM managed. Refresh the file system
view in the Space Management Console
by pressing F5 on your keyboard or
select Refresh` under the View menu.

load managed file system statistics from selected file
system. The reason could be that the file system is not
longer HSM managed.
System action: Managed file system statistics are not
retrieved and information is not displayed in the Space
Management Console.
ANS8850E

selected file system is not mounted. You
must mount the file system before you
can add HSM.
User response: Select a not managed file system to

add HSM.
ANS8853E

filesystem-name.

manage file system and fails for a unknown reason.
User response: Retry the add HSM operation. If this
does not solve the problem, see the error log file for
additional information and contact TSM technical
support.
ANS8854E

able to remove HSM from file system :
filesystem-name. The error occurs when
the Space Management API tries to lock
the SDR file and fails.

unmanage (remove) file system and fails for a
unknown reason.

add HSM to a file system, because it is not mounted.
System action: The remove HSM operation fails and

HSM is not removed from the selected file system.

User response: Try the remove HSM operation again.

If this does not solve the problem, see the error log file
for additional information and contact TSM technical
support.
User response: Mount the selected file system before

adding HSM.
810
ANS8855E ANS9016E
ANS8855E

able to start automatic migration on the
file system : filesystem-name.
Explanation: The Space Management API tries to start

automatic migration on a file system and fails for a
unknown reason.
System action: The automatic migration is not started
for the file system.
information and contact TSM technical support.
ANS8856E

able to start reconciliation process on
the file system : filesystem-name.
System action: The selected file is not recalled from

the server.
information.
ANS8939E
Explanation: The filter was not applied to the

directory tree.
System action: The directory tree is not filtered.
further assistance.
ANS8945E

reconciliation process on a file system and fails for a
unknown reason.
System action: The reconciliation process is not
started for the file system.
information, and contact TSM technical support.
ANS8857E

able to start scout process on the file

scout process on a file system and fails for a unknown
reason.
An unexpected error occurred trying to

filter the directory tree. rc=return-code
An unexpected error occurred analyzing

the directory tree. The list of files
matching your search criteria is not
completed. rc=return-code
Explanation: It was not possible to search all items

matching the search criteria on the directory tree due to
an unexpected error.
System action: The search results table shows only the
items found until the error is occurred.
further assistance.
ANS8946E
RPC call failed.
Explanation: Unable to connect receiver recall

daemon.
System action: The scout process is not started for the

file system.

information, and contact TSM technical support.
User response: System is not operating correctly or

recall daemons are not started.
ANS8858E
ANS9012E

able to migrate the file : file-name. The
error occurred in function :
function-name.
Explanation: The Space Management API tries to

migrate a file and fails in the displayed API function.
System action: The selected file is not migrated to the
server.
information.
ANS8859E

able to recall the file : file-name. The
error occurred in function :
function-name.
Explanation: The Space Management API tries to

recall a file and fails in the displayed API function.
error-program: Command must be run by

root user.
Explanation: TSM requires that a root user perform

this operation.
System action: TSM terminates the operation.
User response: Change to root user, and then retry the
operation.
ANS9016E
Cannot get space management migration

status for path.
Explanation: An error occurred while trying to get the

space management migration status. Either the
permissions for the status file are not set correctly, or
the status file is damaged.
User response: The root user should check the
permissions of the status file, or contact the service
representative.
811
ANS9017W ANS9028E
ANS9017W
error-program: Minimum number of

recall daemons min-dsmrecalld cannot be
greater than maximum number of recall
daemons max-dsmrecalld; defaulting to
minimum min-dsmrecalld and maximum
max-dsmrecalld.
ANS9022E
error-program Recall daemon (pid

process-ID) ended abnormally, status:
status.
Explanation: A recall daemon stopped abnormally.

System action: The operation does not complete.
Explanation: A minimum number of recall daemons

has been entered that is greater than the maximum
number of recall daemons.

persists, send the core file to IBM technical support for
analysis.
System action: TSM uses defaults instead of the

values specified in the client system options file
(dsm.sys).
ANS9023I
User response: Correct the MINRECALLDAEMONS

and MAXRECALLDAEMONS options in the client
system options file and retry the operation.
Explanation: The process is interrupted and exiting.

The user has terminated the process.
ANS9018W
program-name: option option value value

invalid, range min-value to max-value.
Explanation: An invalid value has been entered. Value

should be in the range specified by the message.
System action: TSM detected an interrupt. The recall

daemon is terminated and exiting.
ANS9024E
System action: TSM uses defaults instead of the value

specified by the user.
User response: Correct the invalid input value.
ANS9019W
program-name: unable to parse option

value argument
Explanation: Input is incorrect or is not in correct

format.
System action: TSM continues.
User response: Retry operation with correct usage
syntax.
ANS9020E

User response: Check the TSM error log for
communications failures such as TCP/IP, shared
memory, or named pipe errors.
ANS9021E
error-program Unknown recall daemon

(pid process-ID) terminated abnormally,
status: status.
Explanation: A recall daemon stops abnormally.
Starting with this release all candidate

processing is done internally by the
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
dsmmonitord.
System action: TSM detected an invalid option.
dsmreconcile is exiting.
User response: Dont use options -c and -Candidates
with dsmreconcile anymore.
ANS9025E
Could not establish a session with a

TSM server or client agent. The TSM
return code is tsm-error;.
Explanation: None.
error-program: Subsidiary recall daemon

process exiting.
The Data Protection for WebSphere

plug-in version and the backup-archive
client version do not match. Please
upgrade your Data Protection for
WebSphere plug-in.
Explanation: The release and version of the Data

Protection for WebSphere plug-in is downlevel from the
release and version of the Backup-Archive Client.
System action: None
User response: Upgrade Data Protection for
WebSphere to the proper release and version.
ANS9028E
program-name: cannot determine the file

system name for fsid (file-system-ID,
file-system-ID).
Explanation: TSM is unable to determine the name of

the file system with the specified file-system-id.

persists, send the core file to IBM technical support for
analysis.
System action: TSM is unable to recall the requested

file.
User response: Determine if the file system which
812
ANS9029E ANS9059E
contains the file has an entry in /etc/adsm/SpaceMan/
config/dsmmigfstab. Typically this problem should not
occur unless the dsmmigfstab file was manually
updated after the file system was mounted, and the
entry was either removed or commented out. Once the
entry is added back to dsmmigfstab, try the file recall
again.
ANS9029E
The WebSphere server is running, but

the server must be shut down for a
restore operation. Shut down the
WebSphere server and try the restore
operation again.
Explanation: The WebSphere server must be brought

down to perform a restore.
System action: The restore operation does not

complete.
User response: Perform the restore procedure in the
DP for WebSphere book.
ANS9036W
program-name: migrated file(s) are

missing on server for number stub file(s).
Look in file-spec for file names.
Explanation: TSM cannot find the migrated file(s) on

the server.
User response: Look in the path mentioned in the
message for the file name. Also ensure that you are
working with the correct server for this file.
System action: The restore operation fails.

User response: Shut down the WebSphere server and
try the restore operation again.
ANS9054E
ANS9030W
System action: None
Cannot set conflicting attributes to file

file-name.
Explanation: TSM cannot set the file attributes

because the requested attributes are in conflict with one
another.
System action: TSM does not set the file attributes.
User response: Retry this operation with attributes
that do not conflict with each other.
ANS9031W
File file-name is not a migrated file.
Explanation: TSM can only set file attributes to a

migrated file. This file has not been migrated.
User response: Migrate this file, and then retry the
operation.
ANS9032W
File file-name is not in an HSM managed

file system.
Explanation: TSM detects that the file is not in an

HSM managed file system, and therefore, it cannot
perform the operation requested.
User response: Add space management to the file
system, migrate the file, and then retry the operation.
ANS9034E
The restore operation did not complete,

due to a change in the original
WebSphere environment.
Explanation: The data must be restored to the same

environment that it was backed up from. This includes
items such as cell name, node name, and the location
where WebSphere is installed.
The plug-in was not found.
Explanation: None.
User response: Run dsmc show plugins at the

command prompt to see the available plug-ins on the
system.
ANS9057W
error-program: cannot get space

information for file-system: error.
Explanation: TSM cannot get the space information

User response: Verify that space management has
been added to the file system.
ANS9058E
error-program: cannot close file-spec: error.
Explanation: TSM cannot close the file. This problem

occurs while the dsmmonitor daemon examines
available space on the file system.
System action: TSM terminates the current operation.
User response: Confirm that file system is still
mounted and managed by HSM. If the problem
persists, reboot the system. If that does not resolve the
problem, contact IBM technical support for further
assistance. Provide the operating system error code and
the output of the df, dsmdf, and mount Unix shell
commands.
ANS9059E
error-program: process cannot detach to

become a daemon.
Explanation: TSM process cannot detach itself to

become a daemon.
System action: TSM cannot start the daemon as
requested. TSM stops.
813
ANS9060W ANS9072W
ANS9060W
error-program: cannot get and increase

limit of open files.
Explanation: TSM either cannot get the limit of the

number of open files, or cannot increase the limit of the
number of open files.
System action: TSM cannot increase the number of
open files, and was not able to complete the operation.
User response: Free some file space by ending some
processes or removing some files, and retry the
operation.
ANS9067W
Explanation: TSM found an error in updating the

dsmmigfstab file for this file system.
System action: TSM does not update the dsmmigfstab
file.
User response: See the preceding error message and
correct the error if possible. Then, retry the operation. If
problem persists, contact your system administrator.
ANS9068I
ANS9062E
File filename has changed during the

backup.
Explanation: A file changed during the backup. Check

the dsmerror.log file for a list of files that have
changed.
System action: The backup fails.
User response: Try the backup again.
ANS9063E
error-program: file system file-system is out

of inodes.
Explanation: TSM cannot get space for the file system

because the file system is out of inodes.
System action: TSM cannot get space via migration.
User response: Remove some files to make more
inodes available and retry.
ANS9064E
error-program: Cannot fork a new

process: error.
Explanation: TSM cannot fork a new process that is

needed. If the operating system errno is EAGAIN, then
the limit on the total number of processes running on
the system or by a single user has been exceeded, or
the system does not have the resources necessary to
create another process. If the errno is ENOMEM, then
there is not enough memory to create the process.
error-program: error updating

dsmmigfstab file for file-system.
program-name: dsmmigfstab file updated

for file system file-system.
Explanation: TSM successfully updated the

dsmmigfstab file for the file system.
User response: Continue with normal operation.
ANS9069I
program-name: all file systems are

reactivated to previous states.
Explanation: TSM has reactivated all file systems

managed by HSM to their previous states before the
global deactivation.
ANS9070I
program-name: space management is now

deactivated for all HSM file systems.
Explanation: TSM has deactivated space management

for all file systems listed in the dsmmigfstab file.
ANS9071W
program-name: error reactivating space

management for all HSM file systems.

operation.
Explanation: TSM found an error in trying to

reactivate space management.
User response: Depending on the error code (errno),

either allocate additional virtual memory (swap space)
or increase the operating system process limit. Then
restart the HSM daemons or reboot the system.
System action: TSM does not reactivate space

management for HSM file systems.
ANS9065E
ANS9072W
File filename or file filename2 has been

added or removed during the backup.
User response: Make sure space management is

installed correctly and retry the operation.
error-program: error deactivating space
management for all FSM file systems.
Explanation: A file was added or removed during the

backup.

deactivate space management.
System action: TSM does not deactivate space

management for FSM file systems.
814
ANS9073W ANS9082W
ANS9073W
program-name: error deactivating space

management for file system file-system.

deactivate the file system.
System action: TSM does not deactivate space
management for the file system.
ANS9074I
program-name: Space management for file

system file-system is now deactivated.
Explanation: TSM has deactivated space management

ANS9075W
program-name: error reactivating space

management for file system file-system.
ANS9078W
Space management is not removed from

file system file-system.
Explanation: TSM was not able to remove space

management from this file system. Possible causes:
Kernel extension is downlevel.
Program is downlevel.
Insufficient disk space.
User response: Refer to the immediately preceding
error message and retry the operation.
ANS9079W
program-name: no migrated files

matching search criteria found.
Explanation: TSM did not find any migrated files

matching the search criteria.
operation.
User response: Retry the operation with a different
search criteria.

reactivate space management for the file system.
ANS9080E
System action: TSM does not reactivate space

Explanation: TSM detects there is not enough space in

the file system to hold all the migrated files if all are
recalled.
User response: Verify that the specified file system is

mounted and that HSM is enabled for this file system.
Then try the operation again. If the problem persists,
contact IBM technical support for additional assistance.
Provide the /etc/filesystems (or equivalent file) and the
output from the mount and dsmdf commands.
ANS9076I
program-name: space management is now

active for file system file-system.
Explanation: TSM has reactivated space management

ANS9077I
program-name: removed space

management from file system file-system.
Explanation: TSM removed space management. The

file system is now a native file system.
program-name: not enough space to recall

all migrated files.
System action: TSM does not attempt to recall all the

migrated files.
User response: Make room in the file system by
increasing the file system size or removing some files.
ANS9081W
program-name: orphaned stub file(s)

detected in file system 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
migrated, or the migration server database is damaged.
System action: TSM does not attempt to remove space
management from the file system.
User response: Determine the cause of orphaned stub
files. Switch to the correct migration server and recall
the migrated files. Retry the operation.
ANS9082W
program-name: error encountered while

reconciling file system file-system.
Explanation: TSM encountered an error performing

reconciliation on the file system.
User response: Refer to other messages displayed or
815
ANS9083W ANS9092W
messages in the log to correct the problem. Then retry
the operation.
ANS9083W
program-name: cannot deactivate space

management on file system file-system.
Explanation: TSM cannot deactivate space

management on the file system.
User response: Correct the error if possible and retry
the operation.
ANS9084E
program-name: file-system is not managed

or not locally managed by space
management.
Explanation: There is no entry for the file system in

the dsmmigfstab file or the file system is managed by
another node.
System action: TSM will not perform space
management functions on this file system.
system, if appropriate, and then retry the operation. If
the file system is not locally managed, retry the
operation on the node managing the file system.
ANS9085E
program-name: file system file-system is

not managed by space management.
ANS9088W
program-name: an entry for file system

file-system is already in the dsmmigfstab
file.
Explanation: TSM found that the file system is already

listed in the dsmmigfstab file.
ANS9089E
The group backup validation failed.

One or more files were added, removed,
or changed during the backup.
Explanation: One or more files have been added,

removed, or changed from the time WebSphere was
queried to the time that all the data was sent to the
TSM server. Check the dsmerror.log file for a list of
files that were added, removed, or changed.
ANS9090E
program-name: file-system is not a valid

file system name.
Explanation: TSM received an invalid file system

name. The file system is not mounted, or is not
mounted correctly.
Explanation: There is no entry for the file system in

the dsmmigfstab file.
User response: Correct the file system name, and retry

the operation.
System action: TSM will not perform space

management functions on this file system.
ANS9091E

system, if appropriate, and then retry the operation.
ANS9086E
program-name: error adding space

management to file system file-system.
Explanation: TSM encountered an error and cannot

add space management to the file system.
The WebSphere backup validation

failed. One or more files were added,
removed, or changed during the backup.
Explanation: One or more files have been added,

removed, or changed from the time WebSphere was
queried to the time that all the data was sent to the
TSM server. Check the dsmerror.log file for a list of
files that were added, removed, or changed.
User response: Refer to the preceding error message

User response: Try the backup again. Do not install

new WebSphere applications or change the WebSphere
configuration while in the backup window.
ANS9087I
ANS9092W
Space management is successfully

added to file system file-system.
Explanation: TSM has added space management to

the file system, and will now monitor its space usage.
You can also perform other space management
operations on this file system.
816
AES 128-bit Encryption is not being

used.
Explanation: AES 128-bit encryption is not being used.

DES 56-bit encryption is being used instead.
System action: DES 56-bit Encryption is used instead
of AES 128-bit encryption.
User response: If the user wants to use AES
encryption, then the user must install the IBM JRE in
order to enable AES encryption for the web client.
ANS9093W ANS9130W
ANS9093W
program-name: cannot update migration

candidates list file-name.
Explanation: TSM cannot update the migration

candidates list because not enough memory is available
to create a temporary file.
User response: Make some memory available by
ending some processes, and then retry the operation.
ANS9094W
program-name: no candidates found in

file system file-system.
User response: Output will not be saved. Please

specify different file or check permissions on chose file.
ANS9101I
No migrated files matching file-name

were found.

that cannot be found in the server database as a
migrated file.
Explanation: TSM found no files eligible for migration

in the file system after running dsmreconcile.
ANS9121I
Explanation: A Domino activate databases operation

was completed.

ANS9096E
User is not the owner of file

filesystem-namedirectory-namefile-name so
file is skipped.
System action: TSM activated the databases.

ANS9126E
Explanation: The user does not own this file and

cannot perform this operation.
User response: None, or if you have root-user
authority, switch to root user and retry the operation.
ANS9098E
program-name: space management does

not support file system 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).
Space management does not support other types of file
systems (AFS, NFS, etc).
System action: Processing of the file system stopped.
ANS9099E
program-name: space management is not

active for file system file-system.
Explanation: TSM found the file system did not have

space management activated.
System action: Processing of that file system stopped.
User response: Reactivate space management for the
file system.
ANS9100E
Unable to open file filename for output.
Explanation: The file name specified cannot be

opened.
System action: Make sure that user has access to write
to specified file, or use different file name.
Activate completed.
program-name: cannot determine whether

space management is active or inactive
for file-system due to error: error.
Explanation: The program program-name indicated

in the message text was unable to obtain statistics for
file system file-system. Therefore the program cannot
determine whether space management is activated,
deactivated, or globally deactivated on that file system.
The message text includes a description of the Unix
errno error that occurred while trying to get the state of
space management.
System action: TSM stops the operation.
User response: Verify that the file system is mounted
and accessible. Using the appropriate tools for that file
system, check whether there are any I/O or other
integrity errors on that file system. Then try the
operation again. If the operation fails, then a system
reboot might clear the error condition. If, after taking
these actions the problem persists, contact IBM
technical support for assistance.
ANS9128I
Inactivate logs completed.
Explanation: A Domino inactivate log operation was

completed.
System action: TSM inactivated the log.
ANS9130W
program-name: High threshold (value) less

than low threshold (value).
Explanation: TSM detects that the high threshold is

lower than the low threshold. The high threshold must
be higher than or equal to the low threshold.
System action: TSM logs the condition and continues
817
ANS9131W ANS9145W
processing other parameters.
ANS9137W

ANS9131W
program-name: invalid size factor (value).
Explanation: An invalid value has been entered for

the size factor.

low threshold.
System action: TSM logs the condition and continues.
ANS9140W

ANS9132W
program-name: invalid stub file size

(value).

the stub file size setting.
program-name: invalid quota factor

(value).

the quota setting for the file system.
program-name: invalid size factor (value)

for file-system, range value..value.

the size factor setting. Value should be in the range
specified by the message.
System action: TSM does not change value.
ANS9141W

ANS9133W
program-name: invalid low threshold

(value).
program-name: invalid age factor (value)

for file-system, range value..value.

the age factor setting. Value should be in the range
specified by the message.
System action: TSM does not change the value.

ANS9134W
program-name: invalid age factor (value).

the age factor setting.
ANS9135W
ANS9142W
program-name: invalid premigration

percentage (value).

premigration percentage.
Explanation: TSM detects that high and low threshold

values specified for the file system are invalid. The
high threshold must be greater than or equal to the low
threshold.
System action: TSM logs the condition and stops the
dsmmigfs add or update operation.
User response: Try the dsmmigfs command again,
specifying valid values for the high and low thresholds.
ANS9144W

ANS9136W
program-name: invalid high threshold

(value).

high threshold.
program-name: file-spec: high threshold

(value) less than low threshold (value) for
file-system.
program-name: file-spec: invalid high

threshold (value) for file-system, range
0..100.
Explanation: TSM detects an invalid high threshold

value for the file system.
System action: TSM logs the condition and stops.
User response: Enter a valid value for the high
threshold.
ANS9145W
program-name: file-spec: invalid low

threshold (value) for file-system, range
0..100.
Explanation: TSM detects an invalid low threshold

value for the file system.
818
ANS9146E ANS9153E
System action: TSM logs the condition and stops.
User response: Enter a valid value for the low
threshold.
ANS9146E
program-name: file-spec: expecting value

field(s) in line line-number, found value
field(s).
Explanation: TSM detects too many or too few fields

in an entry in the dsmmigfstab file.
ANS9150I
Explanation: A Domino archive log operation was

completed.
System action: TSM archived the log.
ANS9151E

operation.
User response: Edit the dsmmigfstab file manually,
and then retry the operation. Note:Do not manually
edit the dsmmigfstab file unless specifically instructed
by a message.
ANS9147E
program-name: cannot read file-spec: error.
Archive log completed.
An unexpected program error was

encountered . TSM function name :
Explanation: None.
User response: Check error log for more information.
Contact the TSM administrator with the information
provided in this message.
Explanation: TSM cannot read this file.

System action: TSM cannot fully complete the
User response: An error occurred reading an HSM
managed file system status file. Verify that the file
system is mounted and enabled for HSM and is
actually managed by HSM and then try the operation
support for further assistance. Provide the output from
the mount, dsmdf and ls -l [file system name]
commands.
ANS9148E
program-name: cannot find mount point

Explanation: TSM cannot find file system mount

point.
operation.
User response: The specified file system is not
currently mounted. Mount the file system and try the
operation again.
ANS9149W
program-name: invalid
MINMIGFILESIZE option value (value)
has been specified.
Explanation: An invalid MINMIGFILESIZE option

value has been specified.
ANS9152E

management for whole system: error.
Explanation: Space management cannot be

deactivated for the whole machine.
System action: TSM cannot deactivate space
management support.
User response: The HSM global status is inaccessible,
possibly due to concurrent access. Try the operation
again. If the problem continues, examine the output of
the shell command ps -aef as well as the contents of
/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. If
a pid is stored in this file and it does correspond to a
running process, remove the dmiFSGlobalState.pid file
and retry the operation. If the problem persists, reboot
the system and repeat the appropriate analysis for your
file system type.
ANS9153E
program-name: cannot reactivate space

management for whole system: error.
Explanation: Space management cannot be reactivated

for the whole machine.
System action: TSM cannot reactivate space
management support.
User response: The HSM global status is inaccessible,
possibly due to concurrent access. Try the operation
again. If the problem continues, examine the output of
the shell command ps -aef as well as the contents of
/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. If
a pid is stored in this file and it does correspond to a
running process, remove the dmiFSGlobalState.pid file
and retry the operation. If the problem persists, reboot
the system and repeat the appropriate analysis for your
file system type.
819
ANS9154E ANS9162E
ANS9154E

management for file system file-system:
error.
Explanation: Space management cannot be

deactivated for the file system.
System action: TSM unable to deactivate space
management support for the file system.
User response: The HSM file system status is
inaccessible, possibly due to concurrent access. Try the
operation again. If the problem continues verify that
the file system is mounted and that HSM is enabled on
the file system with the Unix shell commands mount
and dsmdf. If the problem persists, reboot the system
ANS9155E
program-name: cannot reactivate space

management for file system file-system:
error.
Explanation: Space management cannot be reactivated

System action: TSM cannot reactivate space
management support to the file system.
User response: The HSM file system status is
inaccessible, possibly due to concurrent access. Try the
operation again. If the problem continues, verify that
the file system is mounted and that HSM is enabled on
the file system with the Unix shell commands mount
and dsmdf. If the problem persists, reboot the system
ANS9156I
System action: TSM rollforward the Domino DB2

database log.
Please enter a valid filespace location
Explanation: This message will be seen when you run

the Pref editor from MFC GUI. This means that user
has not entered a required field which is filespace
location path.
System action: TSM Enter required field
User response: Operation will not proceed till user
enters required field
ANS9158W
program-name: cannot turn on ENOSPC

checking in kernel: error.
Explanation: TSM cannot turn on ENOSPC checking.

System action: TSM cannot turn on ENOSPC
checking. Processing continues.
820
ANS9159E
program-name: unable to create temporary

file.
Explanation: TSM cannot create a temporary file.

System action: TSM cannot complete its operation.
User response: Check with the Unix mount shell
command that /tmp and /etc exist as separate file
systems on your system. Use the df command to check
whether they are full. Create additional space by
deleting files or increasing the file system size.
ANS9160E
program-name: cannot write to temporary

file or status filefile-spec: error.
Explanation: TSM cannot complete writing to the

temporary file.
operation.
User response: The Unix error code may provide
guidance as to why the write failed. Use the Unix
mount and df shell commands to verify that the
associated file system is mounted and has space
available. If this message resulted from a shell
command, mount the file system and create additional
space if necessary, then retry the operation. If the
message did not result from a shell command, restart
the daemons. If the problem persists, reboot the system.
Rollforward completed.
Explanation: A Domino DB2 rollforward operation

was completed.
ANS9157W
User response: Verify that the AIX JFS HSM fsm

kernel extension is loaded, then try the operation again.
If the problem persists, reboot the system and try the
operation again.
ANS9161E
Invalid backupset file or device name

entered.
Explanation: The backupset file or device name

specified does not contain a valid backupset.
User response: Specify a file name or device that
contains a valid backupset and retry the operation.
ANS9162E
program-name: file-spec invalid: not found

in path/path.
Explanation: TSM cannot find an entry for the file

system in the dsmmigfstab file.
operation.
User response: Specify a file system that is currently
managed by HSM.
ANS9163W ANS9171E
ANS9163W
program-name: Could not acquire the

recall daemon session id.
Explanation: Could not set up the event disposition

for the file system, because the recall daemon session
could not be acquired. It seems the recall daemon is not
running. Recall requests will not be handled, which
means the TSM client for space management cant react
to recall requests for this file system.
System action: TSM could not set up the recall event
handling. The recall event handling is not enabled for
this filesystem.
User response: Start or restart the recall daemon.
ANS9164W
program-name: Could not acquire the

monitor daemon session id.
Explanation: Could not set up the event disposition

for the file system, because the monitor daemon session
could not be acquired. It seems the monitor daemon is
not running. Thus the thresholds for file system usage
will not be monitored and the NOSPACE event will not
be handled, which means the file system may run out
of space.
System action: TSM could not set up the NOSPACE
event handling. The NOSPACE event handling is not
enabled for this filesystem.
User response: Start or restart the monitor daemon.
ANS9165E
program-name cannot open directory

directory-spec due to the following error:
error.
Explanation: The directory indicated in the message

text cannot be opened. The message text includes a
description of the error that occurred.
System action: The requested operation is not
completed.
User response: Try to correct the error condition that
is indicated in the message text, then try the operation
ANS9166I
A backup type backup version backup

date datetime is not consistent with
local repository and has been deleted
from the server (object name=filespace
namepath-namefile-name, ID =
object-id:object-id).

named object is not valid with local repository contents.
This could happen if local repository is modified or got
corrupted on the client system. This backup can not be
restored, therefore it will be deleted on the server.
System action: The specified backup object will be
deleted on the server. Processing will continue.

ANS9167W
The client cache for adaptive subfile

backup is corrupt and cannot be used.
Explanation: The adaptive subfile cache has become

corrupt. While the backup client can detect the
corruption, the reason for the corruption cannot be
determined.
System action: The TSM client will proceed with
standard selective or incremental backup. The cache
will be rebuilt so that subsequent backups will use the
adaptive subfile technique.
User response: If the problem persists, contact IBM
technical support for assistance. Be prepared to provide
the client error log, which will contain additional
messages that might be useful for support to help
identify the problem.
ANS9168E
program-name cannot open database

file-spec due to the following error: error.
Explanation: The database specified in the message

text could not be opened. The reason for the error is
included in the message text.
System action: The requested operation does not
complete.
User response: Make sure that the file system has
sufficient available space, then try the operation again.
If the problem persists, contact IBM technical support
ANS9169E
program-name: cannot create directory

directory-spec, reason.
Explanation: TSM cannot create this directory.

System action: TSM does not create this directory.
User response: Verify that this directory does not
already exist, and that its parent directory has proper
permissions.
ANS9170E
program-name: file-system is not a

mounted local file system.
Explanation: TSM did not find that this file system is

properly mounted.
System action: TSM ignores the file system.
User response: Verify that this file system is local and
mounted and activated properly.
ANS9171E
An error internal to TSM has occurred.

The following string is too long: error.
Explanation: None.
complete.
821
ANS9172I ANS9180W
User response: A system reboot might clear up the
problem, after which the operation should be tried
ANS9177T
Reconciling local snapshot repository

with TSM server....
Explanation: None.
ANS9172I
Backup system component is excluded

from processing.
Explanation: You tried to back up the system

component that was specified to be excluded from
backup.
System action: IBM Tivoli Storage Manager did not
back up the system component.
User response: Verify the input keyword or the writer
name via the command line client and the Exclude lists.
ANS9173I
Backup system component doesnt

exist.
Explanation: You tried to back up the system

component that is not installed or is not started.
System action: IBM Tivoli Storage Manager did not
back up the system component.
User response: Verify the input keyword or the writer
name by using the GUI interface to expand the System
State or System Services node.
ANS9174I
A backup delete completed.
Explanation: A Backup delete was completed.

System action: TSM deleted backup files.
ANS9175E
There is not enough memory for the

backup delete operation

specified backup delete operation.
System action: TSM cannot continue with the
requested backup delete operation.
try the operation again. Reducing the scope of queries
and the amount of data returned might also help, or
ANS9176I
Backup delete is stopped by the user.

ANS9178E
program-name cannot open file file-spec

due to the following error: error.
Explanation: The program indicated in the message

text was unable to open the specified file. The message
text also includes a description of the error that
occurred when it tried to open the file.
complete.
User response: Verify that the file system on which
the file resides is mounted, then try the operation
again. A system reboot might clear up the problem. If
further assistance.
ANS9179W
Database log path is overlapping with

the path for data.value.
Explanation: When log path overlaps database data

path, the logs will be overwritten upon local restore
causing rollforward recovery to fail.
stop the restore.
User response: User should select No to stop the
restore operation and backup the logs to an alternate
location. The restore operation can then be retried. Now
the User can select Yes to continue the restore
operation, in which case the logs will be overwritten.
User will have to copy the logs back to the original
location once the restore operation is complete. The
rollforward operation can then be performed
successfully.
ANS9180W
An entry in the password file could not

be decrypted.
Explanation: The password failed decryption

validation.
System action: Archive delete stopped.
System action: The password in the password file will

be ignored. You will be prompted for the password,
unless the process is running in the background, such
as in scheduling mode.
User response: Enter the password when prompted.
Explanation: You requested the backup delete

operation be stopped.
822
ANS9181I ANS9188E
ANS9181I
Current statistics for DB2 restore host

host: Total number of volumes in
request: volumes Total number of
volumes completed: complet Total
number of volumes in progress: inprogr
Total number of volumes remaining:
remaing Currently processing volumes:
process Total number of bytes in request:
totalda Total number of bytes
transferred: totaltr
Explanation: None.
ANS9182W
Your customized client nodes list

already contains this node. Would you
like to update it?
Explanation: The list of client nodes contains already

the specified client node. You cannot have two client
nodes with the same client node name in the same
machine.
System action: Updates or does not update the client
node, depending on the user response.
User response: Select yes to update the client node.
Select no to cancel this operation.
ANS9183W
Removing Space Management from

file-system file system means that all
migrated data will be recalled from
TSM Server server-name Make sure that
enough free space is present on this file
system for the recalled data. Do you
want to remove Space Management
from client-node now?
Explanation: Removing Space Management from the

selected file system means that all migrated data will
be recalled from the server.
System action: Prompts the user to confirm when
removing Space Management from the selected file
system.
User response: Make sure that enough free space is
present on this file system for the recalled data.
ANS9184E
program-name cannot allocate memory

due to the following error: error.
Explanation: A memory allocation error occurred. The

message text includes a description of the error that
occurred.
the operation again. If the problem continues to occur,

use your operating systems administrative tools to
check virtual memory (swap space) on your system,
and increase it if necessary. Check whether an
application is consuming available virtual memory. A
system reboot might also clear up the problem. If the
further assistance.
ANS9185W
Master scout daemon is not running!
Explanation: A list of candidates files eligible for

migration cannot be built because the master scout
daemon is not running on the selected client node.
System action: Files are not automatically migrated to
the TSM server.
User response: Restart the master scout daemon
manually using the dsmscoutd command from a
command shell on the machine where Space
Management Agent is running.
ANS9186E
program-name: cannot open mounted file

system file-system: error.
Explanation: TSM cannot open mounted file system.

System action: TSM ignores the file system.
User response: Verify that this file system is mounted
and activated properly.
ANS9187W
Monitor daemon is not running!
Explanation: Files cannot be automatically migrated to

the TSM server or recalled from TSM server because
the monitor daemon is not running on the selected
client node.
System action: Files are not automatically migrated or
recalled from the TSM server.
User response: Restart the monitor daemon manually
using the dsmmonitord command from a command
shell on the machine where Space Management Agent
is running.
ANS9188E
Not enough memory for recall operation
Explanation: TSM cannot allocate storage for the

requested recall operation.
operation.
User response: Retry the recall operation. If the
problem continues, check with your system
administrator.

complete.
occurs in an HSM daemon, restart the daemon, then try
823
ANS9189I ANS9203E
ANS9189I
Recall stopped by user
ANS9196W
Explanation: You requested that TSM stop the recall

operation.
System action: Recall stopped.
ANS9191E
Error checking file system state
Explanation: The system cannot open /dev/dsm or

cannot open the file system.
The PASSWORDACCESS option in

your dsm.sys file is not set to
GENERATE. Reset it to GENERATE and
restart the HSM client.
Explanation: The PASSWORDACCESS option in your

dsm.sys file is set to PROMPT. It must be set to
GENERATE in order for automatic space management
services to work.
System action: TSM terminates the client.
System action: Transaction stopped.
User response: The root user must set the

PASSWORDACCESS option to GENERATE in the
dsm.sys file.

continues, check with your system administrator.
ANS9197E
ANS9192I
Cannot disable file-system.
Explanation: TSM cannot disable the file system. This

message is issued only from the Motif HSM GUI,
which is no longer supported.
File: file-name has already been recalled.
Explanation: You tried to recall the a file that has

already been recalled.
System action: TSM does not highlight the file.
System action: TSM ignores the request.

User response: Use the dsm Unix shell commands.
ANS9198E
File: file-name is a resident file.
Explanation: You tried to recall a file that is resident.

ANS9193I
Cannot open file-system.
Explanation: TSM cannot open the file system. This

User response: Use the dsm Unix shell commands.
System action: TSM will not highlight the file.

ANS9199S
Cannot open /dev/fsm
Explanation: TSM cannot open the space management

device file, /dev/fsm.
ANS9194W
A selective migration is in progress.

Wait until it completes and retry the
recall.
Explanation: You tried a recall operation while a

selective migration is in progress.
User response: Wait until the selective migration is
complete and retry the recall operation.
ANS9195W
A selective recall is in progress. Wait

until it completes and retry the
migration.
Explanation: You initiated a migration operation while

a selective recall is in progress.
User response: Wait until the selective recall is
complete and retry the migration operation.
User response: Check to see whether TSM is installed

correctly and that the /dev/fsm file exists. Correct the
problem and retry the operation.
ANS9201W
LAN-free path failed.
Explanation: A LAN-free connection could not be

made.
System action: The system will connect to the server
without using the LAN-free path.
User response: Verify your LAN-free setup.
ANS9203E
ENABLELANFREE can not be used

when HSM is installed.
Explanation: The TSM Client has detected that HSM

is installed on the system. LAN-free is not a valid
option when HSM is installed.
v This error occurs on AIX when this file is found:
/usr/tivoli/tsm/client/hsm/bin/dsmrecalld
v This error occurs on Solaris when this file is found:
/opt/tivoli/tsm/client/hsm/bin/dsmrecalld
824
ANS9206W ANS9240W
System action: An invalid option is detected and
processing stops.
ANS9231E
User response: Remove the ENABLELANFREE option

from the system option file. ENABLELANFREE can
only be used when HSM is not installed.
Explanation: An unexpected error is occurred due to

some processing communication error.
ANS9206W
User quota is reached!
Processing error detected in the

migration phase of this process!
System action: TSM will not migrate or premigrate

files from this file system.
System action: Files cannot be migrated to TSM

server.

User response: Use the File System Properties dialog

to specify a different quota value.
ANS9233E
Explanation: The maximum amount of data that can

be migrated and premigrated from this file system to
the TSM Server is reached.
ANS9220W
Recall daemon is not running!
Explanation: Files cannot be recalled from TSM server

because the recall daemon is not running on the
selected client node.
System action: Files are not recalled from the TSM
server.
Processing error detected in the

premigration phase of this process!

some processing communication error in the
premigration phase.
System action: TSM will not premigrate files from this
file system.
User response: Restart the recall daemon manually

using the dsmrecalld command by a command shell
on the machine where Space Management Agent is
running.

ANS9227E
ANS9236E
Internal error loading the status:

error-message
Error detected performing reconciliation

on this file system!
Explanation: An exception has been detected loading

the status of space management activities.
Explanation: An error is occurred performing

reconciliation on the selected file system.
System action: The status of the related activity is not

loaded. The process continues to load the status at the
next refresh interval.
System action: TSM will not reconcile this file system

with TSM server.

ANS9230E
Communication error detected in the

migration phase of this process!

ANS9240W
Could not acquire the serial number of

disk disk-name at LUN LUN-id.

server communication error in migration phase.
Explanation: TSM was not able to determine the serial

number of the specified disk. The disk may not support
SCSI inquiries of the Vital Product Data on page 0x80.

file system.
System action: Server-free data movement will not be

possible for data residing on the specified disk.

825
ANS9249E ANS9265E
ANS9249E
File file-namefile-namefile-name accessed

during migration. File skipped.
Explanation: The specified file-name was not migrated

because the file was accessed by another process during
the attempt to migrate it.
System action: TSM left the file resident.
User response: If you want the file migrated, stop the
process which is accessing the file and retry the
migration.
ANS9250I
File system file-system reconciliation

completed.
Explanation: TSM has finished reconciling the file

system.
the error is corrected in the table.

User response: Find the invalid values in the table
entry and correct them using the dsmmigfs command
or the HSM graphical user interface.
ANS9256E
File file-namefile-namefile-name is
currently opened by another process.
File skipped.

because the file was open by one or more other
processes.
processes which currently have the file open and retry
the migration.

ANS9251E
ProgramName: Cannot parse

command-line options correctly.
Explanation: An internal program error occurred

trying to parse the command-line arguments.
System action: The program is not able to process the
request.
User response: Use the -h or -help option to see what
options are allowed on the command-line, then retry
the request.
ANS9252I
Value of environment variable: envVar.
Explanation: None.
ANS9254E
An error was encountered while adding

implicit excludes to the include-exclude
list.
Explanation: None.
System action: TSM cannot proceed.
User response: If HSM control file exclusion conflicted
with other include/exclude directives, correct the
explicit include/exclude directives to allow for
exclusion of HSM control files and directories. Ensure
that all HSM file systems are mounted.
ANS9255E
program-name: invalid value found in the

dsmmigfstab file for file system file-spec.
Explanation: TSM detects invalid values in the

dsmmigfstab file. The entry that contains the invalid
values is for file system file-spec
System action: TSM cannot perform migration until
826
ANS9257E
Server server-name does not support

space management.
Explanation: The specified server-name does not

support space management. It is a downlevel server, or
a platform that does not support space management.
System action: TSM failed the operation.
User response: If you want to use the space
management function, make sure you connect to a
server that supports space management.
ANS9263W
You cannot restore both active and

inactive versions of System State.
Explanation: Restoring an active copy and inactive

copy of System State is not allowed.
User response: Select either the active copy or the
inactive copy to perform restore operation.
ANS9264E
Incremental backup of Virtual Machine

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

machine volumes failed.
System action: The backup of the virtual machine
finished with failures. The next virtual machine in the
vmlist will be processed. The reason for the failure is
written to the local client error log.
User response: Check the local client error log for
reason for the failure.
ANS9265E
Failure mounting Virtual Machine

vmname with vcbMounter command.
RC=rc
Explanation: The VMware vcbmount command failed

to mount virtual machine disk.
ANS9266E ANS9285K
System action: The backup of the virtual machine can
not continue. The next virtual machine in the vmlist
will be processed. The output of the vcbMounter
command will show the reason for the failure.
System action: The backup of the virtual machine can

not continue. The next virtual machine in the vmlist
will be processed. The output of the vcbMounter
command will show the reason for the failure.
User response: Issue a vcbMounter command for the

virtual machine to determine the reason for the failure.
Refer to the documentation for that message for more
information.

information.
ANS9266E
ANS9280E
Failure initializing virtual machine

environment. Can not find
vcbMounter.exe command. RC=rc
Explanation: Failure initializing virtual machine

environment. Can not find vcbMounter.exe command.
The VMware Consolidated Backup Framework not
installed or vcbMounter.exe command is not located in
current PATH environment variable.
System action: The backup can not continue. The
output of the vcbMounter command will show the
reason for the failure.
information. The VMware Consolidated Backup
Framework must be installed on the Backup Proxy
machine. The installed location and the vcbMounter.exe
must be located in the PATH environment variable. The
default location is C:\Program Files\VMware\VMware
Consolidated Backup Framework.
ANS9267E
program-name: File system file-system has

exceeded its quota.

exceeded its quota. No more data can be migrated out
of this file system.
file system.
ANS9278E
Failure processing vmList option. RC=rc
Explanation: Failure processing vmList option.

System action: The backup can not continue.
User response: Check for errors in the vmList option
value. Refer to the documentation for the vmList option
ANS9279E
Failure locating Virtual Machine

vmname volumes. Failed with RC=rc
vmname option must be set when

running this operation.
Explanation: A required option for the command is

missing.
System action: The operation can not continue.
User response: Set the missing option using the
Preference Editor or the command line.
ANS9283K
Tivoli Space Manager is recalling a

migrated file.
Explanation: The space management kernel extension

is attempting to access a file that is not stored locally. If
the file is migrated, TSM is attempting to access it from
an TSM space management server.
System action: TSM waits for the kernel to access the
file.
ANS9284K
File access waiting for migration to

complete.
Explanation: The file being accessed is currently being

migrated. Access to this file must wait until the
migration process is finished.
System action: TSM waits until the file migration is
completed.
ANS9285K
Cannot complete remote file access.
Explanation: The space management kernel extension

cannot complete the remote file access. The file may be
migrated to an TSM migration server. The file cannot
be recalled to the local machine. The server could be
temporarily disabled.
User response: Check to see whether the server has
been disabled by the system administrator, then retry
the operation.
Explanation: Virtual machine volumes can not found.

Volume mount points are not available on Backup
Proxy machine.
827
ANS9286K ANS9294I
ANS9286K
File migration has been discontinued.
ANS9291E
Explanation: Migration stops because the file is being

migrated by another process.
ANS9287E
Invalid or unsupported device.
Explanation: The logical volume device is either

invalid or unsupported. Refer to the documentation for
device type support for image backup.
performed.
User response: For image backup source or image
restore destination, specify a device of one of the
supported types.
ANS9288I
File file-name of size file-size is too small

to qualify for migration.
Explanation: The file is smaller than the minimum

size required for migration. A file is considered for
migration only if its size is greater than both the stub
file size specified for the file system plus 1 byte and the
block size defined for the file system.
System action: TSM does not migrate this file because
it will not free additional space.
program-name: A conflicting space

management program is already running
in the file-system file system. Re-run this
program later in this file system.
Explanation: TSM detected another program running

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:
dsmreconcile
dsmautomig
dsmmigfs remove.
Also, dsmmigfs remove cannot run while a migration
process is running in the file system.
System action: TSM will not run the program at this
time.
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
at the same time.
time.
User response: Check the permissions on the

directories leading up to the lock file and also the
permissions on the program executable.
ANS9289I
ANS9293E
Object dir-name is a directory. It is

skipped for migration.
Explanation: The object is a directory. It is not

migrated. Space management does not migrate
directories.
System action: TSM does not migrate this object
because it is a directory.
ANS9290I
File file-name of type file-type is skipped

for migration.
Explanation: The file either cannot be read, is not a

regular file, or its type is unknown to space
management. Space management only migrates regular
files and does not migrate directories.
System action: TSM does not migrate this file.
TSM space management cannot access

ERRORPROG error-program:error
Explanation: TSM encountered an error trying to

access the program specified with the ERRORPROG
option in your client system options file (dsm.sys). This
message will appear only the first time this error
occurs.
System action: TSM cannot send a severe error
message to the specified error message program.
User response: Check to make sure the program exists
and that it accepts standard input when run. It is
usually best if ERRORPROG specifies the fully
qualified file name of the program.
ANS9294I
No files matching file-name were found.

that cannot be found in the local file system.
828
ANS9296W ANS9313E
ANS9296W
Performing image backup of the entire

volume for volume name. The
IMAGEGAPSIZE option and used block
image backup is not supported for
non-JFS2 file systems on AIX.
User response: Run reconciliation to reconcile the file

system. Retry operation.
ANS9300I
Explanation: None.
User response: Refer to the client manual for
additional information regarding the IMAGEGAPSIZE
option and used block image backup.
ANS9297I
File file-name is skipped for migration:

No backup copy found.
Explanation: A management class is assigned to the

file with the attribute MIGREQUIRESBKUP set to YES.
This requires a current backup copy of the file before
migration. However, there is no backup copy found on
the migration server. This file will not be migrated.
Note: TSM checks only the migration server for a
backup copy. If the migration server and backup server
are different servers, TSM does not find a backup copy
of the file.
User response: Back up this file on the migration
server, or assign a management class to this file that
does not require a current backup copy. Retry the
operation.
ANS9298I
File file-name is skipped for migration:

Backup copy found is not current.

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
for a backup copy. If the migration server and backup
server are different servers, there must be a valid
backup copy of the file on the migration server.
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
the operation.
ANS9299I
Cannot get the number of migrated files

Explanation: Failed to get the number of migrated

files on the file system. The number is stored in the
status file for the file system.
Migrated files found in file system

file-system. Check for any error
encountered during recall.
Explanation: Remove space management failed

because there are migrated files in the file system. TSM
was unable to recall any files, or some of the migrated
files may have failed during a recall operation.
System action: TSM remove processing stops.
User response: Check for error messages that occurred
during the recall process, correct any problems, and
retry the remove process.
ANS9301I
Cannot remove the entry for file-system

from the dsmmigfstab file.
Explanation: The entry for the file system in the

dsmmigfstab file cannot be removed. Possible reasons:
v Not enough memory to create temporary file name
for temporary file system table.
v Not enough free space or inodes to create temporary
file system table
v Cannot open the real and/or temporary file system
table files.
System action: TSM does not remove the entry from
the dsmmigfstab file.
User response: Manually edit the dsmmigfstab file
and delete the entry.
ANS9312S
program-name: Cannot change

owner/group on file: file-name: error
Explanation: TSM cannot change the ownership or

group, or both for the specified file. This change is
necessary for space management to run properly.
System action: TSM cannot continue processing.
User response: Ensure that directory permissions
allow the file owner or group to be changed. Reissue
the command.
ANS9313E
program-name: The TMP directory is full.
Explanation: The TMP directory from the operating

system is full.
System action: TSM stops.
User response: Delete some files in the TMP directory
System action: If you are removing space

management from the file system, processing stops.
Space management is not removed.
829
ANS9316T ANS9405W
ANS9316T
File system file-system undelete

completed.
Explanation: TSM has finished undeleting the file

system.
ANS9318W
program-name: error encountered while

undeleting file system file-system.
Explanation: TSM encountered an error performing

undelete on the file system.

ANS9401E
program-name: Cannot kill recall daemon.
Explanation: TSM A request for killing the recall

daemon failed. This may occur during node failover.
System action: none.
User response: Continue with normal operation unless
further errors occur.
ANS9402E
program-name: Cannot notify to recover

HSM operations on a failure node.
Explanation: In order to assume the functionality of a

failing partner node, the dsmwatchd must notify the
local daemons.
System action: none.
ANS9349I
Selective Recall completed
User response: Communication cannot be established

with the HSM daemon specified in this message. Check
whether the target daemon is running. Start or restart
the target daemon as appropriate. If the problem
persists, reboot the GPFS cluster.
ANS9353I
ANS9403E
Explanation: The selective recall was completed.

System action: TSM recalled the files.
Selective Recall stopped by user.
Explanation: You requested to stop the selective recall

operation.
System action: Selective recall stopped.
ANS9357E
The dsmscout executable cannot be used

on the user level.
Explanation: The dsmscout process is exclusively

started by the dsmmonitord.
System action: TSM aborts the operation.
ANS9399W
program-name: lock file access error for

operation value on path value value with
errno text value.
program-name: The local HSM

functionality cannot be recovered.
Trying to initiate failover to another
node.
Explanation: TSM If the GPFS daemon crashes or the

local HSM daemons cannot perform their function for
whatever reason the dsmwatchd will try to migrate the
functionality to another node.
System action: Migrate HSM functionality to another
node.
User response: Check failure node. It may be
necessary to recover the local GPFS daemon.
ANS9404W
program-name: Received failover request

from node ID . Trying to takeover
remote filesystems.
Explanation: A lock file operation has failed.
Explanation: TSM The local dsmwatchd received a

notification about a failing HSM node. It will try to
takeover its managed filesystems.

processing, or exits if directory not found.
System action: HSM will try to takeover the managed

filesystems from a failure node.
User response: Correct the configuration.
User response: Check failure node.
ANS9400W
program-name: Recovered program-name.

The daemon was either not started or in
corrupted state.
Explanation: TSM HSM daemon breakdown with

automatic recovery by the dsmwatchd.
System action: Restarting the daemon.
830
ANS9405W
program-name: The takeover of filesystem

file system started.
Explanation: The local activation of the specified file

system started successfully.
System action: TSM on the local node will try to
activate the file system that is space managed on
another node.
ANS9412E ANS9422W
ANS9412E
ANS9418W
program-name: Failover is disabled on the

local machine. Aborting failover ...
Explanation: TSM Failover operations were disabled

either by the system or the user.
User response: Check failover policy if necessary.
program-name: File file-name could not be

acquired at the moment. It may be
locked, or the var filesystem may be
full. Will try to acquire the SDR lock
again in a few seconds.
Explanation: SP-wide files are stored in the SDR.

These files can be accessed as soon as it is possible to
set a certain SDR lock. If a 2nd process holds this lock,
access to the file is denied till the lock is released.
ANS9413W
program-name: The remote node was able

to recover from failure situation.
Aborting takeover ...
Explanation: The remote dsmwatchd was able to

recover from the failure situation during the local
takeover operation.
User response: Check failure node for consistency.
ANS9414E
program-name: Unable to create file-name

in the SDR. Aborting ...
User response: Wait. If the situation does not get

resolved within a reasonable amount of time (about 1
min.), examine the var file system. If it is full, free up
some space. Otherwise execute dsmmigfs SDRreset.
This will reset all activated locks in the SDR for the
local GFPS node set.
ANS9419E
program-name:The filesystem
filesystem-name is either already managed
locally or under the control of a remote
HSM instance.
Explanation: An update of an SDR object failed.
Explanation: A GPFS filesystem can be managed just

once.
System action: Aborting operation.
User response: Check SDR consistency.
User response: Execute dsmmigfs query -detail to

have a look at the current HSM configuration within
the local GFPS node set.
ANS9415W
program-name: The HSM service provider

on Node ID: node with Frame ID: frame
left the failover group voluntarily.
ANS9420E
Explanation: Failover was disabled on a remote HSM

node.
program-name: An update of the

configuration files in the SDR is not
allowed as long as failover is disabled
on the local machine.
Explanation: You cannot update configuration files in

the SDR when failover is disabled on the local machine.
System action: TSM Aborting operation.
ANS9416W

on Node ID: node joined the failover
group.
Explanation: TSM Failover was activated on a remote

HSM node.
User response: Do nothing, or activate failover by

using dsmmigfs enableFailover before running
dsmmigfs SDRupdate.
ANS9421W

ANS9417W

on Node ID: node left the failover group
unvoluntarily.
program-name: Recovered from Lock on

SDR File file-name
Explanation: This output relates to ANS9418W. A

previously blocked SDR file got unlocked.
Explanation: dsmwatchd has lost connection to the

group services.
ANS9422W
System action: dsmwatchd will try to reconnect.

system started successfully.
User response: Ensure that the RSCT peer domain is

online on all HSM client nodes.
program-name: The rollback of filesystem

file system started.
System action: TSM on the local node will try to

831
ANS9423E ANS9443E
activate the file system that is space managed on
another node.
ANS9432E

ANS9423E
program-name: Setting the default

partition name failed! Aborting
operation ...
Explanation: The application needs to have access to

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 node consistency.
ANS9424E
program-name: It was not possible to

send a message to the SP Group
Services. This is a severe error.
Explanation: The Failover environment requires

proper access to the SP Group Services. The
distribution of a message failed.
It was not possible to start the

dispatcher thread for the communication
with the SP Group Services. The
failover environment is in corrupted
state now. This is a severe error.
Explanation: Unable to start required thread.

User response: Verify that virtual memory (swap
space) has sufficient space. Verify that the system
process thread limit is reasonable and has not been met
or exceeded. If the thread limit is reasonable, but has
been exceeded, or the problem otherwise persists,
reboot the GPFS cluster.
ANS9433E
program-name: dm_send_msg failed with

errno Errno.
Explanation: Unable to execute DMApi call.

User response: Check consistency of the GPFS
daemon.

User response: If the problem persists, verify SP
Group Service is accessible and is not overwhelmed. If
the problem persists, reboot the GPFS cluster.
ANS9425E
program-name: It was not possible to

notify the dsmwatchd in order to
distribute a message within the failover
group. The data of the current operation
may get lost.
Explanation: Some HSM commands need to inform

the dsmwatchd about the current operation. This
notification failed.
User response: Restart the GPFS daemon and check
that the DMApi support is active by executing
/usr/lpp/mmfs/bin/mmlsfs deviceName.
ANS9428E
program-name: The takeover of filesystem

file system failed to start.

system failed to start. Please, note that only file systems
which are space managed on another node within the
same cluster can be taken over. Additionally, the file
system must be mounted locally.
System action: TSM will not take over the file system.
User response: Make sure the file system is mounted
locally and managed with the TSM client for space
management on another node within the same cluster
832
ANS9442E
program-name: It appears that another

dsmmigfs add/rem/update command is
in process within the local GPFS
nodeset. Please wait a few moments,
then repeat the operation. If a previous
dsmmigfs command was aborted, there
could be a stale lock in the SDR. If so,
run dsmmigfs SDRreset to fix the
problem.
Explanation: There can only be one instance of

dsmmigfs add/rem/update running within a GPFS
nodeset at the same time.
User response: Wait for a bit and try again. If no other
instance of dsmmigfs is running within the local GPFS
nodeset run dsmmigfs SDRreset.
ANS9443E
program-name: The operation cannot be

executed in a deactivated failover
environment.
Explanation: The operation relies on an active failover

environment.
User response: Run dsmmigfs enableFailover on the
local node and repeat the operation.
ANS9449W ANS9469E
ANS9449W
program-name: Forced deactivation of the

local failover environment!
ANS9455E
program-name: Unable to join the local

failover group with rc=return-code!
Explanation: TSM Failover was initiated or a problem

with the group services occurred.
Explanation: SP Group services reported a problem

accessing/creating an HSM group.
System action: Continuing failover or aborting

operation.
User response: Check HSM and SP Group Services

environments. Execute dsmmigfs enableFailover after
resolving the problem.
ANS9450W
program-name: No eligible filesystem for

takeover.
Explanation: None of the locally mounted GPFS

filesystems matches with the remotely managed
filesystems of the failure node.
User response: Check PSSP environment on the local

node.
ANS9458I
program-name: Joined successfully to the

local failover group.
Explanation: Joining the Group Services HSM failover

group was successful.
System action: Aborting takeover operation.

User response: Check that the filesystems of the
remote failure node get managed elsewhere within the
node set.
ANS9451E
ANS9459E
program-name: GPFS or the SP switch is

down locally. Aborting takeover
activities ...
Explanation: TSM GPFS is not functional locally.

User response: Check switch and VSD status. The
local system must be unfenced.
Using the specified MAXCANDIDATES

parameter would produce an
out-of-space condition in the parent
filesystem of /etc/adsm/SpaceMan/
candidatesPool. Based on the current
free space situation the maximum value
for the MAXCANDIDATES parameter is
value.
Explanation: TSM The automigration candidate pools

for the selected filesystem require
MAXCANDIDATES/10 KB plus a safety buffer of 5 MB
of memory under /etc/adsm/SpaceMan/
candidatesPool, which exceeds the available space.
System action: TSM Abort operation.
ANS9452E
program-name: The DMApi is not

functional locally. Aborting takeover
activities ...
Explanation: The operation stopped because the

DMApi interface is not accessible.
User response: Check GPFS status.
ANS9454W
program-name: Performing
synchronization between the local and
global file event handling.
Explanation: The local node received a request from a

remote node to synchronize with the global file event
handling (DMApi event disposition).
System action: Synchronization proceeds.
User response: Increase the filesystem size or choose a

smaller value for the MAXCANDIDATES parameter.
You may also create a dedicated filesystem with
sufficient space for the migration pools under
/etc/adsm/SpaceMan/candidatesPool. Kill the
dsmscout processes after performing this option.
ANS9462E
Failover functionality is not supported

with this HSM release.
Explanation: The TSM user ran dsmmigfs with the

failover flag on an unsupported platform.
System action: TSM ends the operation.
ANS9469E
Warning! Unable to write a complete

migration candidate list due to low
space in the parent filesystem of name.
Explanation: TSM Low space in filesystem which

stores the migration candidates files.
System action: TSM The executable writes a partial
migration candidates list.
833
ANS9472I ANS9500W
User response: Increase the filesystem size or create a
dedicated filesystem with sufficient size under the
given path.
ANS9472I
program-name: Updating failover

information for Node ID: node
Explanation: Failover status information for remote

node was updated.
ANS9474E
of the block size for the current files system. In this

case of a invalid value the default stub size for the file
system will be used.
System action: TSM default value for the stub size is
used.
User response: Correct the invalid stub size value.
ANS9486W
program-name: Lost my session with

errno: errno . Trying to recover.
Explanation: The DMAPI session is not valid.

System action: Trying to recover session.
User response: Check the failure node. You might
have to recover the local GPFS daemon.
ANS9475E
program-name: Group Services joining

was rejected for Node ID: node with
summary code = gs_summary_code.
Explanation: Failover was disabled on a remote HSM

node. Takeover will take place.

the stub size setting. Value should be a multiple of the
system fragment size for the current files system. In
this case of a invalid value the default stub size for the
file system will be used.
used.
ANS9487W
System action: Migrate HSM functionality to another

node.
User response: Check the failure node. You might
have to recover the local GPFS daemon.
ANS9476I
program-name: Recovered my DM session

sid.
Explanation: DMAPI session is recovered.

ANS9480E
program-name: The rollback of filesystem

file system failed to start.

system failed to start. Please, note that a rollback can
only be performed after the space management of the
file system was moved from the local node to another
node during failover. Additionally, the file system must
be mounted locally.
System action: TSM will not roll back the file system.
User response: Make sure the file system is mounted
locally and managed with the TSM client for space
management on another node within the same cluster
ANS9485W
program-name: invalid stub size (value)

for file system file-system. Valid values
for your file system are zero or a
multiple of the file system block size.
The default stub size will be used.

the stub size setting. Value should be zero or a multiple
834

for your file system are a multiple of
the file system fragment size. The
default stub size will be used.

for your file system are 1 or a multiple
of the file system block size. The
default stub size will be used.

the stub size setting. Value should be 1 or a multiple of
the block size for the current files system. In this case
of a invalid value the default stub size for the file
system will be used.
used.
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.
ANS9501W ANS9511E
ANS9501W
program-name: cannot set event

disposition on session session for file
system mountdir token = token. Reason :
error
Explanation: Events could not be dispositioned on the

file system. No events will be received for this
filesystem. HSM is not enabled for this file system.
User response: If you are running TSM as a non-root

user and you have TSM space management client
installed, please, make sure that the dsmrootd daemon
is up and running, then retry the operation. If you
dont have TSM space management client installed,
retry the operation under the root user authority.
ANS9507E

User response: The file system must be one of the
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
and remount the file system.
program-name: cannot request the right

on session session for file handle
filehandle token = token. Reason : error
Explanation: TSM space management cannot request

the required right on a file.
System action: Processing of the file is interrupted.
ANS9502W
program-name: cannot remove event

disposition on session session for file
system mountdir token = token. Reason :
error
ANS9508W
program-name: cannot release the right on

session session for file handle = filehandle
token = token. Reason : error
Explanation: Event dispositions could not be removed

from the file system.
Explanation: TSM space management cannot release

the right on a file.
User response: Verify that the file system is mounted

and that dmapi is enabled on that file system. If the
problem persists, unmount and remount the file
system, then try the operation again. If the problem still
persists, reboot the system.
ANS9503I
program-name: events have been set and

dispositioned on session session for file
system filesystem-name
ANS9509W
program-name: received an unexpected

event of type event-type on session
session.
Explanation: TSM space management daemon

received an unexpected event. This event has not been
dispositioned.
Explanation: Setting events and dispositioning these

on a DM session enables the file system for TSM space
management support.
System action: TSM ignores event and continues.
ANS9510E

ANS9504W
program-name: The file system

filesystem-name is not mounted or is
mounted with wrong options.
Explanation: Either the file system is not mounted or

it has been mounted with incorrect options.
User response: Mount the file system or remount it
with corrected mount options.
ANS9505E
program-name: cannot initialize the

DMAPI interface. Reason: error
Explanation: TSM client failed to perform

implementation-defined initialization of the DMAPI
interface.
System action: The dm_init_service() function failed.
program-name: cannot get event messages

from session session, expected max
message-length = msglen, returned
message-length = return-length. Reason :
error
Explanation: TSM space management encountered an

error while trying to receive a message on a DM
session.
ANS9511E
program-name: cannot read DM attributes

on session session for file: name = name
handle = handle token = token. Reason :
error
Explanation: TSM space management cannot read the

DM attributes of a DM object, usually a file. If the file
name is not available, it will be displayed as an empty
string or as <NA>.
835
ANS9512E ANS9521E
ANS9517I

ANS9512E
program-name: cannot set DM attributes

on session session for file handle =
filehandle token = token. Reason : error
Explanation: TSM space management cannot set DM

attributes for a DM object, usually a file.
program-name: cleared event messages

from session session. Reason: error
Explanation: TSM space management is in the process

of destroying a DM session. There are still unexpected
event messages on this session that were responded to.
System action: TSM DM session is not destroyed.
User response: This message is informational. If the
session could not be destroyed, try the operation again.
If the problem persists, reboot the system.

ANS9518E
ANS9513E
program-name: cannot remove DM

attributes on session session for file
handle = filehandle token = token. Reason
: error
Explanation: TSM space management cannot remove

DM attributes for a DM object, usually a file.
ANS9514E
program-name: cannot create a file handle

from path. Reason: error
Explanation: TSM space management cannot create a

file handle from the given file.
program-name: cannot respond to an

event message on session session using
token token Reason : error
Explanation: An event message could not be

responded to (returned to the system).
System action: TSM space management continues.
User response: If a user process is unexpectedly
blocked and cannot be killed, see your system
administrator.
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
system on this file system.
ANS9515E
program-name: cannot set the migration

information. Reason: error
Explanation: TSM space management cannot set the

migration information of a file, because space
management cannot create a file handle from the file
and/or from the file system.
ANS9516E
program-name: cannot create an user

event message on session session.
Reason: error
Explanation: TSM space management cannot create an

user event message, needed to reference rights on a file
to be processed.

persists, verify that the file system is mounted with
dmapi enabled. If the problem still persists, reboot the
system.
ANS9520E
program-name: cannot set a managed

region on session session for file handle
= filehandle token = token. Reason : error
Explanation: A managed region could not be set on a

file. No events will be generated for this file.
system.
ANS9521E
program-name: cannot get the file

attributes on session session for file
handle = handle token = token. Reason :
error
Explanation: TSM space management cannot read the

attributes of a file.
836
ANS9522E ANS9530W
system.
ANS9522E
program-name: can not create a file

system handle from path. Reason: error
Explanation: TSM can not create a file system handle

from the file system name. If Reason is Operation not
permitted, the dmapi functionality may be disabled for
the file system.
System action: Processing of the file system is
interrupted.
User response: If Reason is Operation not permitted,
enable dmapi functionality for the file system and retry.

dmapi enabled. If the problem still persists, restart the
system.
ANS9527E
Explanation: TSM space management could not write

to the state file.
System action: TSM stops processing.
system.
ANS9528W
ANS9523E
program-name: is unable to verify the

stub size for the file on session session
file handle = filehandle token = token.
Reason : error
Explanation: A correct stub size could not be

determined by the system.
System action: TSM stops migration of the file.
system.
ANS9524W
program-name: adjusted stubsize to an

allowed value on session session file
handle = filehandle token = token old
stubsize = old-size new stubsize =
new-size
Explanation: The predefined stubsize for the file was

not valid. The system corrected the stubsize.
ANS9525E
program-name: is unable to create a stub

file on session session for file handle =
handle token = token. Reason : error
Explanation: An error occurred while creating a stub

file.
ANS9526E
program-name: cannot open the state file

filename for writing. Reason: error
Explanation: The global or file system state file could

not be opened.
program-name: cannot write to the state

file filename. Reason: error
program-name: cannot read from the state

file filename. Reason: error
Explanation: TSM space management could not read

from the state file.
system.
ANS9529W
program-name: cannot obtain the handle

of a file system state file
Explanation: TSM space management could not find

the handle of a file system state file that is stored in the
global state file. This can occur if either space
management is querying a file system that has no HSM
support added, or the file system state file is corrupted,
or the global state file is corrupted.
System action: TSM continues or stops processing,
depending on the situation.
system.
ANS9530W
program-name: cannot remove an entry

for file-system from the global state file.
Explanation: The entry for the file system in the

dmiFSGlobalState file cannot be removed. Possible
reasons:
v There is not enough memory to create temporary file
name for temporary file system table.
v There is not enough free space or inodes to create
temporary file system table
v The real or temporary file system table files cannot
be opened.
System action: TSM does not remove the entry from
the global state file.
837
ANS9531E ANS9543W
system.
ANS9531E
program-name: cannot create a DM

session: old session = oldsession session
info = session-info. Reason : error
Explanation: TSM space management could not create

a DM session.

system.
ANS9536E
program-name: cannot query an event

message on session session. Reason: error
Explanation: TSM space management cannot query an

event message, needed to determine whether nfs call.

persists restart the system.
ANS9532W
program-name: cannot destroy the session

session. Reason: error
ANS9538W
program-name: request request for DM file

attributes not recognized
Explanation: An unknown request type has been

encountered that cannot be handled.
Explanation: TSM space management could not

destroy a DM session.
ANS9539E

system.
Explanation: A file system handle could not be

created from a file handle.
program-name: cannot create a file system

handle from the file handle = filehandle.
Reason : error

ANS9533W
program-name: failed getting all sessions.

Reason: error
Explanation: TSM space management could not get all

DM sessions on the system.

ANS9542E

system.
ANS9534W
program-name: cannot query a session.

Reason: error
Explanation: TSM space management could not query

a DM session on the system.
ANS9535E
program-name: a file handle could not be

created from the file descriptor
file-descriptor. Reason: error
Explanation: TSM space management could not create

a file handle.
program-name: the file attributes could

not be set on session session for file
handle = filehandle token = token flag =
flag Reason : error
Explanation: TSM space management could not

update file attributes.
system.
ANS9543W
program-name: cannot reserve

(blocks-num1) blocks for nospace
condition on file system filesystem-name,
errno: error-num, reason: error-str.
Currently, (blocks-num2) blocks are
available.
Explanation: Either the TSM client is not able to get

status information for the file system or there is
insufficient space in the file system. The message
reports zero blocks if the file system status information
is not available.
User response: If there is insufficient space in the file
838
ANS9545E ANS9613E
system, free the required space or increase the file
system capacity. If this is due to an input output error,
perform an appropriate file system check. Then, retry
the operation.
User response: Temporary file can be copied to the

appropriate .SpaceMan directory when space is made
available.
ANS9554E
ANS9545E
program-name: cannot get a lock for

lockdirlockfile to continue processing.
Explanation: TSM space management could not obtain

a lock for a file.
User response: Try the operation again. If problem
persists, restart HSM. If problem still persists, restart
the system.
ANS9548W
Cannot complete remote file access.
Explanation: TSM space management cannot complete

the remote file access. The file may be migrated to an
TSM migration server. The file cannot be recalled to the
local machine. The server could be temporarily
disabled.
User response: Check to see whether the server has
been disabled by the system administrator, then retry
the operation.
ANS9550W
File recall has been discontinued.
program-name: command for file system

mountdir Reason : error
Explanation: An attempt to enable or disable xdsm

api functionality on the file system failed. If the attempt
was to enable HSM, then HSM is not enabled for this
file system.
User response: The file system must be of type JFS2 in
order for the TSM Space Management to successfully
set the managed attribute. Verify that the file system is
of the correct type.
ANS9576E
Not enough space in filesystem to create

meta data file!At least space space
required!
Explanation: A disk full error occurred attempting to

create the metadata file. Please migrate some files in
filesystem to free at least space kb.
ANS9577E
An exception msg!Unable to use meta

file!
Explanation: Recall stops because the file being

recalled would cause the file system to run out of
space.
Explanation: An internal error occurred. The dsmscout

is unable to use the meta data file!
User response: Increase the file system space, or

remove unneeded files, or wait until space
management has migrated files off the file system by
demand or threshold migration, or manually migrate
files. Then retry the operation.
ANS9552E
program-name: cannot add space

management to file-system; path includes
non-local file system.
Explanation: An attempt was made to add space

management to a file system whose path contains
non-local elements.
User response: File system must be entirely local.
ANS9578E
An unknown error occurred!
Explanation: An internal error has occurred. The

dsmscout is unable to use the meta data file! The file
has been deleted. A new meta data file will be created.
ANS9613E
program-name: Stub size of stubsize bytes

is not supported on filesystem.
Explanation: The given stub size value not a multiple

of the file system block size and cannot be supported.
System action: The program aborts the operation.
ANS9553I
Wrote temporary candidates list to

file-name.
User response: Use a correct stub size.
Explanation: Due to out of space condition, the

candidates list was written to the named temporary
file.
System action: Temporary file created.
839
ANS9641S ANS9740S
ANS9641S
Invalid option option found in options

file file-name at line number : number
Invalid entry : entry
Explanation: The specified option in the TSM options

file (file-name) is in error.
User response: Correct the options file entry.
ANS9732E
No Backup Copy Group for

Management Class: management-class

not have a backup copy group specified. This message
is issued only from the Motif HSM GUI, which is no
longer supported.
User response: Use the HSM Unix shell commands
instead.
ANS9733E
File: File-name excluded by the

Include/Exclude list
Explanation: You tried to back up the named file-name

that was specified to be excluded from backup.
User response: Specify the file using the Include
option and retry the operation.
ANS9734E
There are number file(s) not selected.

Click on file to find out reason.
Explanation: There are files that cannot be selected.

System action: These files will not be selected for
migrate or recall.
User response: Click on the files to find out the reason
these files are not selected, for example, inclexcl list.
ANS9735E
Error doing realtime initialization
Explanation: TSM ran out of resource (either processes

or shared storage) that prevents it from starting a
migrate or recall operation. Your file selections remain
intact. This message is issued only from the Motif HSM
GUI, which is no longer supported.
System action: TSM cannot start the migrate or recall
operation.
instead.
ANS9736E
Not enough memory for authorization

list table
Explanation: TSM cannot allocate enough storage for

the authorization list. This message is issued only from
the Motif HSM GUI, which is no longer supported.
operation.
instead.
ANS9737E
Authentication failed -- Exit TSM to

retry
Explanation: You typed an incorrect password four

times in a row. This message is issued only from the
Motif HSM GUI, which is no longer supported.
without a correct password.
instead.
ANS9738S
Out of memory
Explanation: TSM found an error allocating storage at

initialization. This message is issued only from the
System action: TSM cannot continue.
instead.
ANS9739E
Cannot get shared memory
Explanation: The system ran out of shared storage

resources.
System action: TSM cannot continue without a shared
storage segment.
User response: Check the output of the ipcs
program to see if there are many new shared storage
segments. Use ipcrm to remove them. If this problem
continues, configure UNIX to allow more shared
storage segments.
ANS9740S
This program is not installed correctly.

Place the application defaults file
(file-name) into the application default
directory (usually directory-name), or set
the XAPPLRESDIR environment
variable to the directory containing the
file-name defaults file.
Explanation: TSM cannot find its resource file (Sm) in

the default directory (directory-name). A problem may
have occurred during installation. This message is
issued only from the Motif HSM GUI, which is no
longer supported.
840
ANS9741E ANS9782S
System action: TSM cannot start.
instead.
ANS9741E
Not enough memory to hold directory

structure
Explanation: TSM cannot allocate storage for the

requested directory structure. This error can happen
under migrate or recall operations. This message is
longer supported.
operation.
instead.
ANS9742E
Error reading directory structure
Explanation: TSM cannot load the requested directory

structure. This error is due to a corrupted file system or
a storage shortage. This can happen under selective
migrate or selective recall. This message is issued only
from the Motif HSM GUI, which is no longer
supported.
operation.
instead.
ANS9743W
No files selected in directory tree
Explanation: You did not select any files to list for

migrate or recall.
operation.
User response: Select files and retry the operation.
ANS9744W
Size exceeds limit
Explanation: You tried to recall a file that has

exceeded the maximum file size limitation on your
system.
System action: TSM cannot recall the file.
User response: Recall this file on a system that
supports the file size. See your system administrator.
ANS9778E
Errors were detected in options file:

Do you want TSM to comment out all
lines with errors?
Explanation: Invalid options or option values were

encountered while reading the options file.
User response: Click Yes to allow TSM to turn the

invalid lines into comments. If you click No, you will
exit immediately.
ANS9779E
Unable to open options file for

writing.
Explanation: An error occurred while TSM tried to

open options file for writing to update it.
System action: Program exits.
User response: Check file and directory access
permissions or correct invalid entries in your options
file manually.
ANS9780E
Unable to update options file .
Explanation: TSM was unable to update your options

file, possibly because of disk full condition.
User response: Check if you have enough disk space
or correct invalid entries in your options file manually.
ANS9781E
After completing repair TSM found an

invalid option, keyword or parameter in
your options file.
Explanation: A final check of your options file found

that an invalid option, keyword, or parameter still
remains. It is possible your options file was modified
by another application.
User response: Make sure no other application
modified your options file and restart TSM. You may
also use a text editor to correct invalid entries in your
options file.
ANS9782S
The selected backupset was generated

by a newer version of the backup server,
and the new backupset version is not
supported by this client; The backupset
data cannot be restored by this version
of the client.
Explanation: The backupset you are attempting to

restore was generated by a newer server that has a
different level of functionality. The client you are using
does not recognize this newer format so it cannot
restore the data from the backupset.
User response: Restore the backupset with a client
that is at the same or higher level as the server that
was used to generate the backupset.
System action: This message is displayed. Further

action depends on your response.
841
ANS9790I ANS9801W
ANS9790I
File is skipped for migration: No

backup copy found.

migration. However, there is no backup copy found on
the migration server. This file will not be migrated.
Note: TSM checks only the migration server for a
backup copy. If the migration server and backup server
are different servers, TSM does not find a backup copy
of the file.
User response: Back up this file on the migration
server, or assign a management class to this file that
does not require a current backup copy. Retry the
operation.
ANS9791I
File is skipped for migration: Backup

copy found is not current.

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
for a backup copy. If the migration server and backup
server are different servers, there must be a valid
backup copy of the file on the migration server.
User response: Check the permissions on the

directories leading up to the lock file and also the
permissions on the program executable.
ANS9797E
A conflicting space management process

is already running in the file-system file
system. Rerun this process at a later
time.
Explanation: TSM detects that another process that

conflicts with the process you are trying to run is
running in the file system. The following processes
cannot be run at the same time for a file system:
dsmreconcile
dsmautomig
dsmmigfs remove.
Also dsmmigfs remove cannot run while a migration
process is running in the file system.
System action: TSM will not run the process at this
time.
User response: Try running the process again later.
ANS9799W
Cannot open temp file for mount

command.
Explanation: TSM cannot open a temporary file to

process the mount command for this file system. This
System action: TSM cannot add space management to

the file system.
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
the operation.

instead.
ANS9800W
ANS9792W
A tree view of a file system is being

built. Please wait until it completes, and
Explanation: You tried to choose Selective Migration

or Selective Recall when a tree view of a file system is
being built.
Cannot create temp file for mount

command.
Explanation: TSM cannot create a temporary file to

process the mount command for this file system. This

the file system.
User response: Wait until the tree view build

completes, and then retry the operation.

instead.
ANS9796E
Cannot access lock file for file-system file

system.
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
at the same time.
time.
842
ANS9801W
Cannot create transaction file.
Explanation: Cannot create transaction file for this file

system. This message is issued only from the Motif
HSM GUI, which is no longer supported.
the file system.
instead.
ANS9802W ANS9812I
ANS9802W
Cannot create status file.
Explanation: Cannot create status file for this file

system. This message is issued only from the Motif
the file system.
instead.
ANS9803W
Cannot create premigration database.
Explanation: Cannot create a premigration database

for this file system. This message is issued only from
the file system.
instead.
ANS9804W
Cannot create migration candidates list.
Explanation: Cannot create a migration candidates list

for this file system. This message is issued only from
ANS9807I
The specified backupset file does not

contain a backupset of type file for the
specified nodename.
Explanation: Local backupset support is limited to

backupsets that contain file data; Image backupsets are
not supported locally. The specified backupset does not
contain a backupset with file data for the node name
specified.
User response: Specify a different backupset file to
restore file data from a backupset. To restore an image
from a backupset, access the backupset from a TSM
server.
ANS9808W
Invalid field in the dsmmigfstab file.
Explanation: There is an invalid field in the

dsmmigfstab file entry for the file system. This message
longer supported.
the file system.
instead.

the file system.
ANS9809W

instead.
Explanation: TSM cannot open the dsmmigfstab file.

This message is issued only from the Motif HSM GUI,
ANS9805W

the file system.
Cannot create .SpaceMan directory.
Explanation: Cannot create .SpaceMan directory for

this file system. This message is issued only from the
Cannot open the dsmmigfstab file.

instead.

the file system.
ANS9811W

instead.
Explanation: Server did not respond.
Server did not respond. Check the

server connection. Select OK to exit.

ANS9806W
The file system type is not supported.
Explanation: The file system is not a type supported

by space management.
User response: Exit dsmhsm. Check the server

connection and try again later.

the file system.
ANS9812I
Files not found in current directory.

Refresh file systems.
User response: There is a mismatch between the HSM

client and the file system type specified. If the file
system type is consistent with the intent, install an
HSM client that supports it, then try the operation
again. Only one HSM client can be installed at a time.
Explanation: Some files are not found in the local file

system.
System action: The transaction will show incorrect
results.
User response: Refresh the file systems to reflect local
file systems.
843
ANS9813W ANS9822W
ANS9813W
Incorrect data shown. Run reconcile.
Explanation: Information in the space management

status file is not synchronized with the file system.
System action: TSM continues processing.
User response: To correct the information, run
reconcile, and then refresh the current window.
ANS9814W
ANS9818W
A selective recall is in progress. Stop the

recall, and then close the window.
Explanation: You tried to close the Selective Recall

Status window while a selective recall was in progress.
User response: Stop the selective recall process, and
then close the window.
Cannot create migration object ID.

space can be allocated for the migration object ID when
a file is being migrated or recalled.
ANS9819W
A selective migration is in progress.

Stop the process, and then close the
window.

Explanation: You tried to close the Selective Migration

Status window while a selective migration was in
progress.

ANS9815W
Out of free space or inodes in file

system to migrate or recall.

ANS9816W
File system has exceeded its quota.

exceeded its quota. No more files can be migrated to
TSM storage for this file system.
file system.
User response: Either recall some files to the local file
system, or ask the system administrator to increase the
quota for this file system.
ANS9817W
file-system is globally deactivated. Please

wait until the file system is globally
reactivated.
Explanation: The file system is in a global inactive

state.
System action: TSM cannot continue the process.
User response: Wait until the system administrator
globally reactivates the file system.
844
User response: Stop the selective migration process,

and then close the window.
ANS9820W
A selective recall or a selective

migration is in progress. Wait until it
completes, and then retry the operation.
Explanation: You tried to perform one of the

following while a selective recall or selective migration
process was in progress:
Add space management
Deactivate or reactivate space management
Global deactivate or reactivate space management
Display policy information
Change password
User response: Wait until the selective recall or
selective migration process is complete, and then retry
the operation.
ANS9821W
New password is not re-entered.
Explanation: You did not re-enter the new password.

System action: The Change password dialog will
display again.
User response: Re-enter the new password.
ANS9822W
New password is not entered.
Explanation: You did not enter the new password.

display again.
User response: Enter the new password.
ANS9823W ANS9843E
ANS9823W
Current password is not entered.
ANS9829W
Recall daemon is not running.
Explanation: You did not enter the current password.
Explanation: An TSM recall daemon is not running.

display again.
System action: TSM recall fails.
User response: Enter the current password.
User response: Ask the system administrator to start a

recall daemon by issuing the dsmrecalld command.
ANS9824W
ANS9830W
Cannot update space management

settings for file-system
Explanation: You tried to update space management

settings for a file system, and the update failed. This
System action: TSM continues with normal operation.
instead.
Explanation: The space monitor daemon is not

running.
System action: TSM is unable to perform space
management functions.
User response: Ask the system administrator to start
the space monitor daemon by issuing the dsmmonitord
command.
ANS9840I
ANS9825W
Total migrated space is greater than

quota for file system.
Space monitor daemon is not running.
This command is not currently

supported for local backupsets.
Explanation: TSM total migrated space is greater than

quota.
Explanation: Local backupset support is limited to

only a few commands and the command you specified
is not one of the supported commands.
User response: You can remove this warning message

by increasing the quota for the file system.
User response: To perform this command on a

backupset, access the backupset from a TSM server.
ANS9827W
ANS9841E
Error accessing the Recall daemon lock

file: file name.
Explanation: There is a problem accessing the recall

daemon lock file.
System action: TSM cannot determine whether the
recall daemon is running. Because the recall daemon is
needed to perform file recalls, the recall fails.
User response: Check with the system administrator.
The recall process needs read access to the
/etc/adsm/SpaceMan/dsmrecalld.pid file.
ANS9828W
Error processing the space monitor

daemon: reason.
Explanation: There is a problem accessing the space

monitor daemon.
System action: TSM cannot perform automatic space
management functions.
User response: Check with the system administrator.
The space monitor daemon is normally installed as
/usr/lpp/adsm/bin/dsmmonitord.
Cannot get user name for the user ID.
Explanation: TSM cannot get the user name for the

user ID. This message is issued only from the Motif
System action: TSM terminates the requested process
and returns to normal operation.
instead.
ANS9842E
The watch daemon is not running

properly.
Explanation: An TSM watch daemon is either not

running, has no dmapi session, or is not connected to
group services.
System action: The TSM action fails.
User response: Ask the system administrator to check
GPFS and the group services and to restart a watch
daemon by issuing the dsmwatchd command.
ANS9843E
Cannot connect to migration server.
Explanation: TSM cannot connect to the migration

server specified in your client system options file. This
System action: TSM terminates the requested process
845
ANS9844E ANS9854W
instead.
ANS9844E
Cannot close the premigrated files

database.
Explanation: TSM cannot close the premigrated files

database for the file system. The premigrated files
database resides in the .SpaceMan subdirectory of the
file systems root directory. This message is issued only
from the Motif HSM GUI, which is no longer
supported.
System action: TSM terminates the requested process,
instead.
ANS9845E
Space management action ends.
Explanation: TSM The requested space management

operation is ended because the watch daemon is not
working properly.
operation.
User response: Look for previous messages.
ANS9846W
Cannot add space management to file

system.
Explanation: TSM cannot add space management to

the file system. This message is issued only from the
instead.
ANS9848W
Cannot activate file system file system.
User response: To restore specific volumes, directories,

and files from a backupset, restore the backupset from
the TSM server.
ANS9850E
Tape read error; Max Blocksize is

blocksize. Attempted to read blocksize
blocksize. Run dsmmaxsg to update scsi
driver max blocksize allowed and retry
operation.
Explanation: An attempt to read from tape at the

specified blocksize failed; Tha maximum blocksize
allowed for the scsi driver is shown.
User response: If the maximum blocksize is less than
the blocksize used by the operation, run the dsmmaxsg
utility to update the maximum blocksize allowed for
the scsi driver, and then retry the operation. If the
maximum blocksize is greater than or equal to the
blocksize used, then verify that the tape installed and
operating correctly and retry the operation.
ANS9852E
Cannot query the level of client and

kernel.
Explanation: The space management GUI client fails

to query the level of kernel and client code. This
instead.
ANS9853W
The space management client program

is downlevel.
Explanation: The space management client is

downlevel compared to the kernel level. This message
longer supported.
Explanation: TSM cannot activate space management

for the specified file system. This message is issued
only from the Motif HSM GUI, which is no longer
supported.
System action: TSM file system state is not changed.
ANS9854W

instead.
ANS9849I
Local backupset cannot be expanded;

Only full backupset restore is supported
locally.
Explanation: Local backupsets cannot be expanded to

show volumes, directories, and files. Only full
backupset restore is supported from local backupsets.
846

instead.
The space management kernel is
downlevel.
Explanation: The space management kernel is

downlevel compared to the client level. This message is
longer supported.
instead.
ANS9855W ANS9877W
ANS9855W
File is accessed during migration. File

skipped.

process which is accessing the file and retry the
migration operation.
ANS9856E
File is currently opened by another

process. File skipped. File has already
been migrated or is currently being
migrated by another process.
Explanation: The specified file was not migrated

because the file was opened by one or more other
processes.
ANS9862W
Do you want to exit TSM space

management?
Explanation: You have selected Exit from the File

menu bar option.
System action: TSM waits for your response.
User response: If you want to exit the program, select
OK. Otherwise, select Cancel.
ANS9871W
Specified column width is smaller than

the largest attribute value. Data will be
truncated.
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,
increase the column width.

processes which currently have the file open, and retry
the migration operation.
ANS9857W
The restored HSM for Windows stub

file may be an orphan: stub file name
ANS9873W
This function should not be used on

large file systems. Continue anyway ?
Explanation: You have decided to open selective recall

or selective migration window, but these functions may
take too long for large file systems.
System action: TSM waits for your response.
Explanation: The restored stub file may not be

accessible in the HSM client archive and thus it
possibly cannot be recalled.
User response: If you want to continue, select OK.

Otherwise, select Cancel.
System action: Stub file is restored.
ANS9875W
User response: Check if the stub file can be accessed.

ANS9858E
Bit file for image on push button cannot

be found. Please check to make sure the
pixmap file exists in your TSM installed
directory.
Explanation: TSM failed to find the pixmap file

defined for the push button.
Refresh time must be numeric value and

within 0 - 14400 minutes or 0 - 240 hours
(10 days).
Explanation: You have entered an invalid value for

Refresh time. It must be a positive number between 0
and 14400.
User response: Enter a positive number between 0
and 14400.

User response: Check to see whether the pixmap file
exists in the TSM installation directory.
ANS9860W
Some selected files are hidden. Change

View option to see all.
Explanation: You have selected all files in a directory

or in all subdirectories. Due to the current View option,
only certain types of files are shown (either migrated,
resident, or premigrated files).
System action: TSM proceeds normally.
User response: If you want to see all selected files,
change the View option from the View menu bar
option.
ANS9876W
Refresh time must be a positive number.

Refresh time. It must be a positive number between 0
and 14400.
and 14400.
ANS9877W
Size Factor must be a numeric value

between 0 - 999999999.

Size Factor. It must be a positive number between 0
and 999999999.
847
ANS9878W ANS9887W
and 999999999.
ANS9878W
Size Factor must be a positive number.

Size Factor. It must be a positive number between 0
and 999999999.
ANS9883W
Quota must be a numeric value between

0 - 999999999.

Quota. It must be a positive number between 0 and
999999999.
and 999999999.

and 999999999.
ANS9879W
Age Factor must be a numeric value

between 0 - 999999999.

Age Factor. It must be a positive number between 0
and 999999999.
ANS9884W

Quota. It must be a positive number between 0 and
999999999.
and 999999999.
ANS9885I

and 999999999.
ANS9880W
Age Factor must be a positive number.

Age Factor. It must be a positive number between 0
and 999999999.
Quota must be a positive number.
The premigration percentage will not be

updated until you select the Update
push button on the Update window or
the Add push button on the Add
window.
Explanation: While you have just selected 'OK' in the

Advanced Feature dialog, the premigration percentage
is not activated until you select 'Add' or 'Update' in the
'Add space management', or the 'Update space
management' dialog.

and 999999999.
System action: TSM waits until you select 'Add' or

'Update' to apply your premigration percentage to the
system.
ANS9881W
User response: When you have changed the space

management attribute, select 'Add' or 'Update', and
then the system will apply your new premigration
percentage.
Premigration Percent must be a numeric

value between 0 - 100.

Premigration Percentage. It must be a positive number
between 0 and 100.
ANS9886W
Enter a positive number for Column

Width.

and 100.

Column Width. It must be a positive number between 0
and 18.
ANS9882W
Premigration Percent must be a positive

number.

Premigration Percentage. It must be a positive number
between 0 and 100.
and 100.

and 18.
ANS9887W
Enter a positive number for Space

Between Column.

Space Between Column. It must be a positive number
between 0 and 18.
848
ANS9889W ANS9915I
and 18.
ANS9889W
Space management has not been added

to file-system file system. Do you want to
build the directory tree anyway?
Explanation: You selected a file system that is not

managed by HSM.
System action: TSM builds the directory tree if you
select the OK button. Otherwise, it will not.
User response: You can add space management to the
file system by selecting the Space Manager push button
in the TSM main window, and then selecting Add
under the Selected menu option.
ANS9904E
Transaction failed, migration aborted.

System action: TSM migration is aborted.
process that is accessing the file, and then retry the
migration.
ANS9908E
System Error.
Explanation: TSM detects an error in reading the state

of the file system. This message is issued only from the
System action: TSM proceeds with normal operation.
ANS9891W
Please mark either or both check boxes

before proceeding.
Explanation: You have not marked either of the check

boxes.
System action: TSM does not proceed with reconcile
processing.
User response: Mark either or both check boxes.
ANS9895W
Space management in file system file

system is not active.
Explanation: You tried to select a file in a file system

for which space management is inactive.
file system, and then proceed with selecting files.
ANS9901E
Cannot migrate TSM system internal

file.
Explanation: You tried to select files that are used

internally by the HSM client. You cannot migrate TSM
internal files.
System action: TSM ignores your request.
ANS9903E
Space management is deactivated for

this file system.
Explanation: You tried to migrate a file in a file

system for which space management is inactive.
System action: TSM continues to migrate files only in
active file systems.

instead.
ANS9909I
Error in accessing migration candidates

list file.
Explanation: TSM detects an error in reading the

migration candidates list file. This file resides in the
.SpaceMan directory of the file system. This message is
longer supported.
System action: TSM proceeds with normal operation.
instead.
ANS9914I
Space management settings have been

modified successfully on file-system file
system.
Explanation: Space management settings have been

updated successfully.
System action: TSM updated space management
settings for the file system.
ANS9915I
Space management has been added

successfully to file-system file system.
Explanation: Space management has been added

successfully.
System action: TSM added and activated space

file system, and retry the migration operation.
849
ANS9918E ANS9941I
ANS9918E
Cannot open migration candidates list

for file-system.
ANS9935I
Explanation: TSM cannot access the migration

candidates list for the specified file system.
System action: TSM continues normal operation.
User response: Select OK to return.
ANS9928I
Space management has been deactivated

successfully on file-system file system.
Explanation: Space management is deactivated

successfully.
System action: TSM deactivated space management
Explanation: You tried to start Threshold Migration on

a Native file system (a file system to which space
management has not been added). You must add space
management to the file system first.
User response: Select OK to return. Select Add if
you want to add space management to the file system.
ANS9936I

ANS9929I
Space management has been reactivated

successfully on file-system file system.
Explanation: Space management is reactivated

successfully.
System action: TSM reactivated space management for
the file system.
Start Threshold Migration only works

on an Active file system. If you want
to make file-system file system Active,
select Add Space Management.
Start Threshold Migration only works

on an Active file system. If you want
to make file-system file system Active,
select Reactivate.
Explanation: You tried to start Threshold Migration on

an Inactive file system (a file system for which space
management has been deactivated). You must reactivate
space management for your file system first.
User response: Select OK to return. Select 'Reactivate'
to reactivate space management for the file system.

ANS9938I
ANS9933I
Migration candidates list only exists in

an Active file system. If you want to
make file-system file system Active,
select Add Space Management.
Explanation: You tried to display the migration

candidates list for a Native file system (a file system
to which space management has not been added).
User response: Select OK to return. Select Add Space
Management if you want to add space management to
the file system.
ANS9934I
Reconcile only works on an Active file

system. If you want to make file-system
file system Active, select Add Space
Management.
Explanation: You tried to start reconciliation on a

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

to file-system file system. You do not
need to deactivate space management.
Explanation: You tried to deactivate space

management on a file system to which space
management has not been added.
ANS9941I

to file-system. If you want to add space
management, select Add space
management option. The file system
will automatically be activated when
you add space management.
Explanation: You tried to activate space management

on a file system to which space management has not
been added. You must first add space management.
The file system will automatically be activated when
the add process is complete.
ANS9942S ANS9954E
ANS9942S

to file-system file system. Do you want to
add space management now?
Explanation: You tried to update space management

settings for a file system to which space management
has not been added.
User response: Select OK to add space management to
the file system. Select Cancel to return.
ANS9943I
Space management has already been

added to file-system file system.
ANS9948E
File: file-spec size is less than the

minimum size required for migration.
Explanation: You tried to migrate a file that is smaller

than the minimum size required for migration. To be
eligible for migration, a file must be larger than both
the stub file size specified for the file system plus one
byte and the block size defined for the 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
been added.
Explanation: You tried to migrate a file that is not a

regular file. It might be a FIFO file, a special file, a
directory or a symbolic link.
ANS9944I
ANS9950E
Space management has been deactivated

on file-system file system. You must
reactivate space management before you
can remove it.
Explanation: You tried to remove space management

from a file system for which space management has
been deactivated. You must reactivate space
management for the file system before you can remove
it.
User response: Select OK to return. Select
Reactivate, and then select Remove to remove
space management.
ANS9945I

to file-system file system. You do not
need to remove space management.
Explanation: You tried to remove space management

from a file system to which space management has not
been added.
Explanation: The Space Management Technique

attribute in the management class is set to None, which
does not allow a file to be migrated.
User response: Assign a management class to the file
that specifies Automatic or Selective for the Space
Management Technique attribute.
ANS9951E
File: file-spec is in a file system to which

space management has not been added.
Explanation: You tried to migrate a file that resides in

a file system to which space management has not been
added.
System action: TSM will not highlight/process the
file.
User response: Switch over to the Space Manager
window, and add space management to the file system.
File: file-name file has already been

migrated.
Explanation: You tried to migrate a file that is already

migrated.
ANS9953E

ANS9947E
File: file-spec is not qualified for

migration because the Space
Management Technique attribute is set
to None.
The management class assigned to this

file does not allow migration.
Explanation: The management class assigned to this

file does not allow migration.
System action: TSM does not migrate the file.
ANS9954E
This file has already been migrated.
Explanation: The file has been previously migrated.

851
ANS9958E ANS9998E
ANS9958E
File file-namefile-namefile-name has not yet

reached the age for migration. File
skipped.
Explanation: This file cannot be migrated because it

has not yet reached the age for migration.
ANS9960W
ANS9965S
Explanation: You did not select any file system for the
Migrate window.
System action: TSM ignores this request and
continues.
User response: Select a file system, a directory, and all
files you want to migrate, and then select the Migrate
button to start the process.
No files selected for migrate or recall.
Explanation: You requested a migrate or recall

operation without selecting files from the presented
directory tree.
System action: TSM cannot do the migration or recall
without selected files.
User response: Select the files that you want to
migrate or recall, and retry the operation.
ANS9966S
System action: TSM ignores the request and

continues.
User response: Select at least one file system and retry
the operation
Server out of migrate data storage space.
Explanation: The server ran out of space in its migrate

data storage. This message is issued only from the
System action: TSM cannot complete the migrate
operation. Any files displayed in the Successful list of
the Migrate Status window were successfully migrated.
instead.
ANS9962I
Migration stopped by user.
Explanation: You requested that TSM stop the migrate

operation.
System action: TSM waits for your response before

proceeding with the remove process.
User response: Select Yes to remove space
management from the selected file system, or select
Cancel to skip the remove.
ANS9997W

Selective Recall completed. Check
failure list for possible errors.
As part of the remove process, all

migrated files in file-system will be
recalled from TSM server. Do you want
to continue with the remove process
now?
Explanation: When you remove space management

from a file system, TSM recalls all migrated files.
System action: Migration stopped.
ANS9963I
No file system has been selected.
Explanation: You did not select a file system.
ANS9988S
ANS9961E
Please select a file system first.
The selective migration, selective recall,

or policy information window is
displayed. Stop any operations, close the
window, and then retry the operation.
Explanation: When a node is contacting more than

one server for space management services, the selective
migration, selective recall, and policy information
windows may not be displayed at the same time.
Explanation: The recall was completed.
System action: TSM recalled the files.
User response: Close the selective migration, selective

recall, or policy information window, and then retry the
operation.

ANS9964I
Selective Migration completed. Check

failure list for possible errors.
Explanation: The migration was completed.

System action: TSM migrated the files.
ANS9998E
The migration server changed after the

selective migration or selective recall
window was displayed. Close the
window, and then retry the operation.
Explanation: A migrate or recall operation will not be

allowed to proceed if the user changed the migration
server after the selective migration or selective recall
window was displayed.
System action: No files will be migrated or recalled.
852
ANS9999E
User response: Close the selective migration or
selective recall window, and then retry the operation.
ANS9999E
():
Explanation: This message carries diagnostic text

relating to a client process or algorithm. This
information is intended for reporting processing
exceptions and other non-standard situations that occur
on the TSM client. The (component), (code), and (text)
will vary depending upon the cause of the message
and the client process or algorithm that issues the
message.
System action: Client processing may or may not
continue depending upon the cause of this message.
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
support representative, the entire text of this message
should be reported.
853
854
Part 4. Data Protection Products Messages

This section contains messages for the following Data Protection products:
v Data Protection for Lotus Domino Server
v Data Protection for Microsoft Exchange Server
v Data Protection for Microsoft SQL Server
v Data Protection for Oracle Version 5.4.1
v Data Protection for SAP (DB2 and Oracle)
v Data Protection for Snapshot Devices for mySAP for DB2 UDB Version 5.4.1
v Data Protection for Snapshot Devices for mySAP for Oracle Version 5.4.1
v Data Protection for Disk Storage and SAN VC for Oracle Version 5.3
For each 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 Tivoli Storage Manager error log that
you can use when working with your service representative.
855
856
Chapter 6. Data Protection for Lotus Domino Server

(ACD0000ACD9999)
This chapter describes the messages issued by Data Protection for Lotus Domino
Server. The messages begin with the prefix ACD and are listed in numerical order.
ACD0003S
An internal processing error has

occurred.

occurred.
User response: Retry the operation. If this error
ACD0004E
An unknown error has been detected.

occurred that prevents the generation of a message for
a return code.
ACD0005E
Out of memory. Stop other processes

Explanation: The machine has run out of memory.

User response: Close unnecessary processes and try
ACD0053E
License file (licensefile) could not be

opened.
Explanation: An attempt to read from the license file

failed.
Explanation: An attempt to write to the license file

failed.
User response: Make sure enough space exists on the
workstation to write to the license file. If enough space
exists, run the command again.
ACD0056E
Data in the license file (licensefile) is not

in a valid format.
Explanation: An attempt to read information from the

license file failed.
User response: Install the product again.
ACD0057E
The checksum in the license file

(licensefile) does not match the license
string text.
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
correct level.
User response: Reinstall the product.
ACD0058E
The Try and Buy license has expired.
Explanation: This Try and Buy license that was

User response: Install the product again. This ensures

that the correct license file is installed.

product.
ACD0054E
ACD0100E
Read failure on license file (licensefile).
Incomplete command:
Explanation: An attempt was made to read from the

license file. This attempt failed.
Explanation: This message displays the incomplete

command that was entered.
User response: Reinstall the product. This will ensure

User response: Re-enter the complete command.

ACD0101E
ACD0055E
Write failure on license file (licensefile).
Invalid argument:
Explanation: This message displays the command that
857
ACD0102E ACD0152I
was entered, up to and including the invalid command
or option argument that was detected.
ACD0133W
Could not locate installation directory.

Attempting to continue...
User response: Re-enter the command specifying a

valid argument for the command or option.
Explanation: An attempt was made to read the

registry to determine where the Tivoli Data Protection
application client was installed. This attempt failed.
ACD0102E
System action: Processing will continue with the

command entered.
Invalid command:
Explanation: This message displays the invalid

User response: Re-enter a valid command.
ACD0103E
Invalid option for the specified

command:

was entered, up to and including the option that was
detected as invalid for the command.
User response: Re-enter the command specifying valid
command options.
ACD0104E
Invalid option:

was entered, up to and including the invalid option
that was detected.
command options.
ACD0105E
Missing argument:

was entered, up to and including the command or
option whose required argument is missing.
ACD0132W
Tracing could not be started. Processing

will continue.
User response: There should be other messages along

with this one. Refer to the other messages to determine
the problem. If the problem can not be determined, it
may be necessary to reinstall the application client
code. This will ensure that the registry entries are set
up correctly.
ACD0134W
Could not locate log directory.

Processing will continue...

application client log is located. This attempt failed.
command entered.
up correctly.
ACD0150I
Operation canceled by user.
Explanation: The user has requested that the Data

Protection for Lotus Domino application client end by
entering ctrl-C.
User response: None
ACD0151E
Errors occurred while processing the

request.
Explanation: Attempting to process the request

entered, an error occurred.
Explanation: A problem prevented tracing from

beginning.
User response: Attempt to determine the source of the

errors from viewing the log file. Correct the problems
and try running the command again.

command entered.
ACD0152I
User response: Refer to the other messages that

display with this message to determine the problem.
Performance stats: seconds seconds spent

in apicall API calls
Explanation: The indicated number of seconds were

spent making API calls for the indicated system.
User response: None
858
ACD0153I ACD0200E
ACD0153I

in function

spent the named function.
User response: None
ACD0154E
The Data Protection for Lotus Domino

version of the Tivoli Storage Manager
API you have installed. Please install
version version.release.level or greater.
Explanation: The version of the Tivoli Storage

Manager API currently installed on the system is older
than the version used to build the Data Protection for
Lotus Domino application client.
ACD0160E
An authentication error occurred with

your stored Tivoli Storage Manager
password.
Explanation: You were unable to log on to the Tivoli

Storage Manager server due an authentication error.
User response: The stored Tivoli Storage Manager
password may have become corrupted. Contact your
Tivoli Storage Manager server administrator.
ACD0161E
Authentication error. The password

entered is not valid. You are not logged
on to the Tivoli Storage Manager server.
Explanation: An incorrect password was entered.

User response: Enter the correct Tivoli Storage

Manager password and try again.
User response: Install a version of the Tivoli Storage

Manager API at or later than the indicated level. A
copy is distributed with the Data Protection for Lotus
Domino application client.
ACD0162E
The passwords entered do not match.

Please enter them again.

ACD0155E
The Data Protection for Lotus Domino

release of Tivoli Storage Manager API
you have installed. Please install release
version.release.l evel or greater.
Explanation: The release of the Tivoli Storage

than the release used to build the Data Protection for
Lotus Domino application client.
User response: Install a release of the Tivoli Storage
copy is distributed with the Data Protection for Lotus
Domino application client.
ACD0156E
Could not load the Tivoli Storage

Manager API.
Explanation: The Tivoli Storage Manager API could

not be loaded.
User response: Ensure the Tivoli Storage Manager API
is correctly installed. Run the Data Protection for Lotus
Domino application client with the
/TRACEFLAGS=API /TRACEFILE=filename options
and view the tracefile to determine why it could not be
loaded. Another possible cause is that the TSMAPI.DLL
does not exist in the system directory. Re-install the
Tivoli Storage Manager API, if this is the case.

User response: Enter the passwords again.
ACD0163E
The directory path needs to be

fully-qualified.
Explanation: The /intopath option was specified

without a fully-qualified path.
User response: Enter the command again and specify
a fully-qualified path in the /intopath option.
ACD0167E
The fully-qualified file name is too

long.
Explanation: An attempt was made to use a

fully-qualified file name that was too long. This
attempt failed.
User response: None
ACD0200E
File (filename) could not be opened for

reading.
Explanation: An attempt was made to open a file for

reading. This attempt failed.
User response: None
859
ACD0201E ACD0213E
ACD0201E

writing.
ACD0208E
There is not enough disk space for the

operation attempted.

writing. This attempt failed.
Explanation: An attempted operation required more

disk space than was available. The attempt failed.
User response: None
User response: None
ACD0202E
ACD0209E
Read failure on file (filename).
Explanation: An attempt was made to read from a

file. This attempt failed.
User response: None
The rename of file (filename1) to

(filename2) failed.
Explanation: An attempt was made to rename a file.

This attempt failed.
User response: None
ACD0203E
Write failure on file (filename).
Explanation: An attempt was made to write to a file.

User response: None
ACD0210E
The Tivoli Storage Manager high level

qualifier is too long.
Explanation: An attempt was made to use a Tivoli

Storage Manager high level qualifier that was too long.
ACD0204E
File (filename) could not be closed.
Explanation: An attempt was made to close a file.

User response: None

ACD0211E

User response: None
ACD0205E
File (filename) statistics could not be

obtained.
The Tivoli Storage Manager low level


Storage Manager low level qualifier that was too long.
Explanation: An attempt was made to obtain file

statistics. This attempt failed.
User response: None
ACD0212E
User response: None

ACD0206E
Directory (directory) could not be created.
Explanation: An attempt was made to create a

directory. This attempt failed.
User response: None
ACD0207E
Directory path (directorypath) is too long.
Explanation: An attempt was made to use a directory

path that was too long. This attempt failed.
User response: None
The Tivoli Storage Manager filespace

name is too long.

Storage Manager filespace name that was too long. This
attempt failed.
User response: None
ACD0213E
The maximum number of objects

allowed per Tivoli Storage Manager
transaction is t oo small.
Explanation: In order to maintain backup data

integrity, multiple backup objects are sent to the Tivoli
Storage Manager server in a single transaction. The
Tivoli Storage Manager server has indicated that the
maximum number of objects allowed per transaction is
less than the minimum required by the Data Protection
for Lotus Domino application client.
860
ACD0214E ACD0259E
objects allowed per transaction on the Tivoli Storage
Manager server and retry the operation.
ACD0214E
The backup objects management class

backup copy group does not exist.
Explanation: The Tivoli Storage Manager server has

indicated that the backup objects management class
ACD0219E

qualifier is invalid.
Explanation: The low level qualifier name or directory

delimeter is invalid.
User response: Check that the low level qualifier
name length, characters, and directory delimeters are
valid.

User response: Contact your Tivoli Storage Manager
ACD0215E
All backup objects do not have the same

management class backup copy
destination.

Storage Manager server within a single transaction. All
backup objects within a single transaction are required
to have the same management class backup copy
destinations.
ACD0216E
ACD0256E
Unable to obtain space information for

volume (volumename).
Explanation: An attempt was made to obtain space

information for a volume. This attempt failed.
The password in your Tivoli Storage

Manager options file has expired. Please
change your password on the Tivoli
Storage Manager server using the
change password command and then
either change or remove the password
value in your options file.
Explanation: Your Tivoli Storage Manager password

has expired. You need to change your password.
User response: Obtain a new password for your Tivoli
Storage Manager server; node using the change
password command or by asking your Tivoli Storage
Manager Administrator to change your password.
ACD0257E
Your password has expired.

has expired. A new password needs to be obtained.
User response: None

Storage Manager node using the change password
command or by asking your Tivoli Storage Manager
Administrator to change your password.
ACD0217E
ACD0258E

name is invalid.
You did not enter a valid password.

Processing ends.
Explanation: The filespace name or directory

Explanation: The password that was entered was not

a valid password.
User response: Check that the filespace name length,

characters, and directory delimeters are valid.

valid password.
ACD0218E
ACD0259E

Explanation: The high level qualifier name or

directory delimeter is invalid.
User response: Check that the high level qualifier
valid.
The password you entered for

verification does not match the
password you entered for your new
password. Your password will not be
changed.
Explanation: The password you entered for

verification of your new password does not match the
new password that was entered.
861
ACD0260I ACD357E
User response: Try again to change your password
being sure to enter the same password for the new
password and for the verification password.
ACD0260I
Password successfully changed.
Explanation: The change password command

completed successfully
ACD0266E
Could not find the Tivoli Storage

Manager HTML books.

registry to determine where the Tivoli Storage Manager
books were installed. This attempt failed.
User response: None
User response: It may be necessary to reinstall the

application client code. This will ensure that the
registry entries are set up correctly.
ACD0261I
ACD0267E
There are no backups for the server

named servername.
The verify password entered does not

match the new password entered.
Explanation: There are no backups on the Tivoli

Storage Manager server for the specified server name.
Explanation: The verify password does not match the

new password.
User response: None
User response: Retry the command with a matching

verify password.
ACD0263E
Failed to start Web browser with a

return code of returncode.
Explanation: An attempt was made to start the web

browser to view the TSM HTML book. This attempt
failed.
User response: Start your web browser manually and
point it to bookfrm.htm in the agent htm directory.
ACD0264I
Could not find the default browser

defined. An attempt will be made to use
Microsoft Internet Explorer.

registry to determine the default browser. However, a
default browser is not defined. A determination will be
made where Microsoft Internet Explorer is installed.
ACD0300E
Invalid restore type.
Explanation: The type of restore requested is invalid.

valid restore type.
ACD0301E
Invalid backup type.
Explanation: The type of backup requested is invalid.

valid backup type.
ACD351E
Invalid trace keyword - keyword
Explanation: A TRACEFLAG option in the user

configuration file or on the command line is incorrect.
User response: It is possible that a default browser is

not defined for the system. This is okay. An attempt
will be made to use Microsoft Internet Explorer.
System action: Client program did not initialize or

tracing was not enabled in the applet.
User response: Correct the value.
ACD0265E
Could not find Internet Explorer.

registry to determine where Microsofts Internet
Explorer was installed. This attempt failed.
User response: Make sure that the registry is set up
correctly for Internet Explorer.
ACD357E

file-name.

862
ACD366E ACD495E
ACD366E
Unable to close trace output file

file-name.
Explanation: An error occurred during the closing of a

trace output file-name (for example, not enough disk
space).
ACD385E


User response: Check the options.doc file for a
description of possible causes of the error, or see your
ACD367E

Tracing disabled.

ACD476E
program-name: cannot open file file-spec:

error.
Explanation: DP cannot open the file.

System action: DP cannot complete the requested
operation.

continues.
ACD487E


link.
ACD368E

ACD383E

Explanation: Trace file linkname cannot be a symbolic

link.
User response: Specify the trace file location with the
tracefile option.
ACD384E




ACD488E

error log: log-name. errno = errno-value,

current has write permission.
ACD495E


given log location.
863
ACD496I ACD519E
ACD496I
DP is converting the log-file from

minutes.
Explanation: The log-file was previously in continouos

and old data saved.
ACD497I

minutes.

ACD498I

ACD515E
Explanation: The DSMAGENT Node specified is not

configured properly.
System action: The VSS operation stops.
User response: Verify that the DSMAGENT Node
specified is correct and that the Client Acceptor
Daemon (CAD) is running for the DSMAGENT Node.
If the error persists, contact your service representative.
ACD516I
Invalid Proxy Configuration Detected:

Target Node targetnode is not listed as a
valid node to proxy to for Node Name
nodename.
Explanation: The proxy node configuration on the

TSM Server is not correct to support this VSS
operation.
User response: Contact the TSM Server administrator
to have the correct TSM Server GRANT PROXY
commands issued to enable proxy authority for the
nodes. If the error persists, contact your service
representative.


the Data Protection for Lotus Domino processes or
programs. The following events can be recevied:
was stopped.
ACD517I

DP function name : function-name DP
function : function-desc DP return code :
TSM-rc DP file : file-name (line-number)
Explanation: None.
User response: Contact the DP administrator with the
information provided in this message.
ACD518E

ACD501E
Invalid DSMAGENT Node

configuration found for node
dsmagentnode.
Backups selected for restore must have

the same backup location (TSM or
LOCAL).
Explanation: A VSS restore operation was submitted

that specified multiple backup objects. The backup
objects chosen had different backup locations. This is
not allowed. All backup objects submitted in the same
VSS restore operation must have the same backup
location, either TSM or LOCAL, but not both.
System action: The VSS restore operation stops.
User response: Retry the VSS restore operation
specifying one backup object at a time.
ACD519E
The VSS operation failed with rc =

returncode.
Explanation: There was a failure when TSM

performed the VSS operation.
User response: Verify that the TSM Client Acceptor
864
ACD520E ACD5110E
Daemon (CAD) is installed, configured, and running
properly on the machine. Retry the operation. If the
error persists, contact your service representative.
ACD520E
Failed to connect to Local DSMAGENT

Node localdsmagentnode at address:port
address:portnumber. Verify that the TSM
Client Acceptor Daemon (CAD) is
installed, configured, and running
properly.
Explanation: An attempt was made to connect to the

TSM Client Acceptor Daemon (CAD) running on the
local machine. A communication error occurred when
this connection was attempted.
System action: The operation stops.
User response: In order to perform VSS operations,
you must have a TSM Client Acceptor Daemon (CAD)
and a TSM Remote Client Agent Service (DSMAGENT)
installed and configured properly. In addition, the TSM
Client Acceptor Daemon (CAD) must be running.
Verify that the TSM Client Acceptor Daemon (CAD) is
installed, configured, and running properly on the local
machine. If the error persists, contact your service
representative.
ACD521E


Tivoli Storager Manager process started by different
user id is performing pruning at the same time.
ACD522E
DIAG:

ACD524S


on the disk).
are incomplete.
ACD5022I
A new configuration file has been

created.
Explanation: The /configfile value specified a file

name that does not exist. A new file was created.
ACD5023W
The configuration file cannot be found,

using default settings.
Explanation: The /configfile value specified a file that

cannot be found. Default settings are used.
User response: Ensure the correct file name is
specified, then enter the command again.
ACD5025E
PASSWORDACCESS is Generate. Either

the stored password is incorrect or there
is no stored password. If you do not
have a stored password, use of the
-ADSMPWD=xxx option will set and
store your password.
Explanation: The PASSWORDACCESS option specifies

generate in the client options files. There is currently no
stored password. An initial password needs to be
stored.
User response: Invoke the command again using the
-ADSMPWD option. Subsequent commands should
now complete without specifying a password.
ACD5110E
Could not locate the Domino server

configuration file (notes.ini).

application client could not find the Domino server
configuration file (notes.ini) file.
User response: Ensure that either the notes.ini file is
specified in the PATH statement or that the
NOTESInipath configuration parameter is correct.
865
ACD5111E ACD5135E
ACD5111E
Error getting the name of the Domino

data directory.
Explanation: The Lotus Domino API could not return

the name of the Domino data directory.
User response: Ensure the Lotus Domino server is
ACD5115E
No databases were found that match the

file specification entered.
Explanation: The Lotus Domino Server was searched

for databases that matched the entered file
specification. No databases were found.
User response: Correct the file specification and try
ACD5125E
No DB2 groups were found that match

the group specification entered.
Explanation: The Lotus Domino Server was searched

for DB2 groups that matched the entered group
specification. No DB2 groups were found.
User response: Correct the group specification and try
ACD5128E
The user specified NotesIniPath does

not exist. Verify that the path setup for
the NotesIniPath preference really
exists.
Explanation: The IBM Tivoli Storage Manager for Mail

application client could not find the specified
NotesIniPath.
User response: Issue the DOMDSMC QUERY
PREFERENCES command to ensure that the
NotesIniPath is correctly specified in the preferences
file.
ACD5129E
The Lotus Domino Server program

executable directory was not found.

application client could not find the Lotus Domino
Server program executable directory.
User response: Ensure that the PATH statement
contains the Lotus Domino Server program executable
directory, then retry the operation.
866
ACD5130E
Could not initialize the connection to

Lotus Domino properly. error=errorcode

application client could not initialize Lotus Domino
properly. The error code is given.
User response: Ensure that Data Protection for Lotus
Domino and the Lotus Domino Server are properly
installed, then try the operation again.
ACD5132E
The DB2 group specification is invalid.

Specify a DB2 group name.
Explanation: A database file specification was entered

instead of DB2 group specification. Specify a DB2
group.
User response: Correct the group specification and try
ACD5134E
The Domino server is not DB2 enabled.
Explanation: Data Protection for Domino DB2

commands are available only when the Domino server
is DB2 enabled.
User response: Enable the Domino server for DB2.
ACD5135E
The DB2 backup TSM objects cannot be

found. Please verify that TSM API
options file used by DB2 specifies the
same NODENAME and
TCPSERVERADDRESS options as the
TSM options file used by Data
Protection for Domino. The
DSMI_CONFIG environment variable
specifies the TSM API options file used
by DB2.
Explanation: The DB2 API uses the TSM API options

file specified by the DSMI_CONFIG environment
variable. If the NODENAME and
TCPSERVERADDRESS options specified in this file do
not match those of the TSM options used by Data
Protection for Domino, then Data Protection for
Domino cannot manage DB2 backups.
User response: Update NODENAME and
TCPSERVERADDRESS options to match those use by
Data Protection for Domino, or, use specify the same
options file for Data Protection for Domino and for
DB2.
ACD5136E ACD5146E
ACD5136E
DB2 Database database cannot be found

in the DB2 pending file.
Explanation: There is no entry for the specified

database in the pending DB2 file.
User response: An entry in the DB2 pending file is
created only after a successfull restore is performed.
Restore the DB2 datatabase or DB2 group and then
rollforward the DB2 database.
ACD5137E
DB2 Database database is not in

rollforward pending state.
User response: Verify the DOMDB2 agent, domdb2c,

is correctly installed and check the log file errors.
ACD5142E
The alternate DB2 database already

exists.
Explanation: The db2restore operation failed because

the alternate DB2 database already exists.
User response: Set the DB2REPLACE option to Yes or
specify an alternate DB2 database that does not exist.
ACD5143E
The specified -INTO option is invalid.

The path must be a relative path.
Explanation: The DB2 database must be in rollforward

pending state. The DB2 database is in rollforward
pending state after a successfull restore.
Explanation: The command is not executed because

the value specified for the -INTO option is invalid.
User response: Restore the DB2 database or the DB2

group.
User response: Specify a relative path with the -INTO

option.
ACD5138E
ACD5144E
DB2 as a data store is not supported by

this Domino server.
Explanation: The Lotus Domino Server does not

support DB2 as a data store.
User response: The command is not supported for
this Domino server.
ACD5139E
There is no db2database entry in the

notes.ini file
Explanation: The name of the Lotus Domino Server

DB2 database was not found in the notes.ini file
correctly enabled for DB2 as a data store.
The specified point-in-time is invalid.

The roll forward point-in-time date :
date must be greater than the backup
date: time

the [date[,time]] specified with the -APPLYLogs option
is invalid.
User response: Specify a [date[,time]] that is later than
the backup date.
ACD5145E
The DB2USER configuration variable

must be specified.

the DB2USER preference is not specified in the
configuration file.
ACD5140E
There is no db2instance entry in the

notes.ini file

DB2 instance was not found in the notes.ini file
correctly enabled for DB2 as a data store.
ACD5141E
Unable to start the Data Protection for

Lotus Domino DB2 agent.
User response: Specify the DB2USER with the set

command.
ACD5146E
A DB2LOGPath must be specified.
Explanation: The command is not executed because a

DB2LOGPath has not been specified.
User response: Specify a DB2LOGPath and rerun the
command.
Explanation: The application was unable to start the

Data Protection for Lotus Domino DB2 agent.
867
ACD5147E ACD5206I
ACD5147E
A Domino server error was encountered

regenerating database links. reason.
Explanation: The links to the Domino DB2 databases

may be missing. The restore of the DB2 database was
successful.
System action: None

User response: None Centrally logged
ACD5202E

User response: Restore the links to the DB2 databases
if they are missing.
ACD5148E
A DB2LOGTarget must be specified.
Explanation: The command is not executed because a

DB2LOGTarget has not been specified.
User response: Specify a DB2LOGTarget and rerun the
command.
ACD5149E
The specified DB2 database is the

Domino DB2 database. This command
cannot be used to delete the Domino
DB2 database.
Explanation: The user specified the name of the

Domino DB2 database.
Explanation: This informational message is written to

the Tivoli Storage Manager Server activity log when a
database backup fails.
System action: None
ACD5203I
ACD5150E
The stored DB2 user password does not

match the entered password.
Explanation: The DB2 password can only be updated

if the current stored DB2 password is known.
User response: Re-enter the stored DB2 user
password.
ACD5200I
Data Protection for Domino: Starting

backup of database database from server
servername.

database backup begins.
System action: None
ACD5201I
Data Protection for Domino: Backup of

database database from server servername

database backup completes successfully.
868

archive of transaction log file
transactionlog from server servername.

transaction log file archive begins.
System action: None
ACD5204I

User response: Specify the name of an alternate DB2
database.

database database from server servername
failed.
Data Protection for Domino: Archive of

transaction log file transactionlog from
server servername completed successfully.

transaction log file archive completes successfully.
System action: None
ACD5205E
Data Protection for Domino: Archive of

transaction log file transactionlog from
server servername failed.

transaction log file archive fails.
System action: None
ACD5206I

incremental database backup from
server servername.

the Tivoli Storage Manager Server activity log when an
incremental backup begins.
System action: None
ACD5207I ACD5216E
ACD5207I
Data Protection for Domino:

Incremental database backup from
server servername complete. Total
Domino databases backed up: numberdbs
Total bytes transferred: bytes Elapsed
processing time: time Secs Throughput
rate: rate Kb/Sec

incremental backup ends.

transaction log archive ends.
System action: None
ACD5212I

restore for server servername.
System action: None

restore begins.
System action: None

ACD5208I

selective database backup from server
servername.
ACD5213I
Explanation: This is an informational message that is

written to the Tivoli Storage Manager Server activity
log when a selective backup is started.
System action: None
ACD5209I
Data Protection for Domino: Selective

database backup from server servername
complete. Total Domino databases
backed up: numberdbs Total bytes
transferred: bytes Elapsed processing
time: time Secs Throughput rate: rate
Kb/Sec
Data Protection for Domino: Restore

database from server servername to server
servername complete. Total Domino
databases restored: numberdbs Total bytes
Kb/Sec

restore ends.
System action: None
ACD5214I

full backup from server servername.
Explanation: This is informational message is written

to the Tivoli Storage Manager Server activity log when
a selective backup ends.

log when a full backup is started.
System action: None
System action: None
ACD5210I
ACD5215E

transaction log archive from server
servername.

transaction log archive begins.
An error occurred trying to set the

requested preference.

preferences file.
User response: View other messages that display.

Perform actions described in those messages, then run
the command again.
ACD5211I
ACD5216E
System action: None
Transaction log archive from server

servername complete. Total transaction
log files archived: transactionlogs Total
bytes transferred: bytes Elapsed
rate: rate Kb/Sec
The value for the preference preference is

not valid. See the DOMDSMC HELP
SET output or the Users Guide for
valid SET command parameters.
Explanation: The preference being set is not valid.

869
ACD5217I ACD5227W
User response: You can either run the command
domdsmc help set or view the Users Guide for valid
SET command parameters.
ACD5217I
The preference has been set

successfully.
Explanation: The preference was set successfully.

User response: None
ACD5218E
The Lotus Domino API could not be

loaded. Could not load the libraryname
ACD5223E
Explanation: The database was not placed into

pending state because the pending database list was in
use at the time or the permissions did not allow access.
System action: The database was not restored
correctly and is unusable.
User response: Try to restore the database again.
Contact your service representative if the error persists.
ACD5224E
Explanation: The Lotus Domino API could not be

loaded.
ACD5220I
The logfile log file could not be pruned.

Processing will continue.
The database could not be placed into

pending state. The pending database list
was in use.
Could not obtain the current pending

database list. The pending database list
was not available.
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: Try the operation again. Contact your
service representative if the error persists.
Explanation: An attempt to prune the log was

unsuccessful.
ACD5225E
Explanation: An unknown Domino API error code

was received. The error code is specified in the text of
the message.
User response: The log file may not exist. If the log
file does exist, view the log file for indications of what
may be the problem.
ACD5221I
The logfile log file has been pruned

successfully.
Explanation: The log mentioned pruned successfully.
Unknown Domino API error code

received: returncode

ACD5226E
The logfile log file cannot be opened for

writing.
Explanation: The log file mentioned could not be

opened for appends.
ACD5222W
The logfile name is greater than the

maximum allowed. Processing will
continue using a logfile name of logfile
in the current directory.
Explanation: The logfile name entered was not fully

qualified. When the fully qualified logfile name was
created, it was longer than the possible length of a
logfile.
System action: Processing continues creating and
using a logfile in the current directory.
User response: You may want to consider updating
the logfile name using a fully qualified path.
User response: Determine why the log file could not

be opened. The log file is either referring to a
non-existent drive or partition, or the file is designated
read-only.
ACD5227W

writing. The log was not pruned and
there will be no logging of events.
Explanation: The log file mentioned could not be

opened for appends. No logging is performed and the
request to prune now was ignored.
System action: Processing continues without logging
and without pruning.
be opened. The log file is either referring to a
870
ACD5228I ACD5237I
non-exixtent drive or partition, or the log file is
designated read-only.
ACD5228I

restore of database database to database on
server servername.

log when a database restore is started.
ACD5233E

Inactivation of transactionlog transaction
log archive failed.

inactivation of a transaction log file archive fails.
System action: None
System action: None

ACD5229I
Data Protection for Domino: Restore of

database database to server servername

database restore completes successfully.
ACD5234I

Inactivation of transactionlog transaction
log archive succeeded.

inactivation of a transaction log file archive succeeds.
System action: None
System action: None

ACD5230E

failed.

database restore fails.
ACD5235I

inactivation of transaction log archive
transactionlog.

inactivation of a transaction log file archive begins.
System action: None
System action: None

ACD5231I

inactivation of transaction log archives
for server servername.

inactivation of transaction log file archives begins.
ACD5236I

restore of transaction log files for server
servername.

restore of transaction log files begins.
System action: None
System action: None

ACD5232I
Data Protection for Domino: Ending

inactivation of transaction log archives
for server servername. There were
numberlogs transaction log archives
inactivated.

inactivation of transaction log file archives ends.
ACD5237I

log files for server servername complete.
Total Domino log files restored:
numberlogs Total bytes transferred: bytes
Elapsed processing time: time Secs

restore of transaction log files ends.
System action: None
System action: None

871
ACD5238I ACD5335I
ACD5238I

restore of transaction log file
transactionlog for server servername.

restore of a transaction log file begins.
ACD5243E
Transaction log files to be restored span

multiple log identifiers.
Explanation: All transaction log files to be restored

must have the same log identifier.
User response: Enter a seperate command for each set

of transaction log files that correspond to a unique log
identifier.
ACD5239E
ACD5246I
System action: None
Data Protection for DominoRestore of

transaction log file transactionlog failed.

restore of a transaction log file fails.
System action: None
ACD5240I

log file transactionlog succeeded.

restore of a transaction log file succeeds.
System action: None

a full backup ends.
System action: None
ACD5327I

ACD5241E
Data Protection for Domino error:

DPDmessage .
Data Protection for Domino: Full

database backup from server servername
complete. Total Domino NSF databases
backed up: numberdbs Domino DB2
database backed up: numberdb2db Total
bytes transferred: bytes Elapsed
rate: rate Kb/Sec
No databases match the following file

spec(s): filespec
Explanation: The Domino API could not find

databases that match this file specification.
System action: The file specification is ignored.

Data Protection message is produced.
User response: Check for a misspelled file

specification, then enter command again.
System action: None
ACD5332E

ACD5242I

transaction log files for server servername
complete. Total Domino transaction log
files restored: numberlogs Total bytes
Kb/Sec

restore of transaction log files ends.
System action: None
No transaction log file archives were

found that match the file specification
entered.
Explanation: The Tivoli Storage Manager Server was

searched for transaction log file archives that match the
entered file specification. No transaction log file
archives were found.
User response: Correct the file specification and retry
the operation.
ACD5335I
No Transaction Log Files match the

following file spec(s): filespec
Explanation: The TSM API could not find any

transaction log extents that match the entered file
specification.
System action: The file specification is ignored.
User response: Check for a misspelled file
specification, then enter the command again.
872
ACD5404E ACD5450E
ACD5404E
There is no keyfilename or
serverKeyfilename entry in the notes.ini
file

ID file was not found in the notes.ini file
determine the problem. If this file does not exist, the

TSM API may not be correctly installed. If this is the
case, install the TSM API again and then run the
command.
ACD5418I
There are no databases pending

activation.

Explanation: A query was issued to look at databases

that are pending activation. There are no databases
pending activation.
ACD5405E
There is no server name in the Lotus

Domino Server id file

was not found in the ID file.
ACD5406E
The directory directory does not exist
Explanation: The specified directory was not found.
User response: None

ACD5420E
Explanation: The specified file is not a database.

User response: Specify a valid database name, then
try the operation again.
ACD5421I

User response: Ensure the directory exists, then try
the command again.
ACD5407E
The database database does not exist
Explanation: The specified database was not found.

User response: Ensure the database exists, then try the
command again.
ACD5408E
The NotesInitExtended api failed with a

return code of returncode. The error
message text for this is not available.
File filename is not a database.
There are no backups matching the

filespec directorypathfilename and the
server name servername.
Explanation: There are no database backups on the

Tivoli Storage Manager Server for the specified server
name.
User response: None
ACD5432I
There are no restored DB2 databases.
Explanation: A query was issued to look at restored

DB2 databases rollforward status, but a DB2 database
restore operation has not yet been performed
Explanation: Notes initialization failed with the

indicated return code.
User response: None
ACD5437I

ACD5412W
An error was encountered with Tivoli

Storage Manager API initialization, rc =
returncode. Examine the dsierror.log for
more information or determine if the
TSM API is installed properly.
Explanation: Errors were encountered during an

atempt to run setup for the Tivoli Storage Manager
API.
User response: Examine the dsierror.log file to

activation.
Explanation: A query was issued to look at databases

that are pending activation. There are no databases
pending activation.
User response: None
ACD5450E
A failure occurred on TSM server

session number (session number), rc =
return code
Explanation: A failure occurred on the numbered TSM

server session.
873
ACD5551E ACD5704E
the problem.
ACD5551E
Screen size is too small for using the

PICK option.

horizontally and 10 lines vertically.
System action: The operation was not completed.
User response: You can either try the operation again
using a workstation with the minumum screen size or
do not use the PICK option.
ACD5612E
Unable to create or write to the file.

Domino return code: returncode.
until logging is turned on for your Domino server.

ACD5700E
The database file name is to be

generated from path (path) and filename
(filename) is too long.
Explanation: The database file name to be generated

is too long.
User response: Use the INTO option to specify an
alternate destination file name, then enter the command
again
ACD5701E
A Tivoli Storage Manager API error has

occurred.
Explanation: A Tivoli Storage Manager API error has

occurred.
Explanation: An attempt to create a file on the

Domino server failed.

User response: Determine and fix the problem.

ACD5702E
ACD5613E
You can only archive logs on a Domino

Server with archival logging on.
Explanation: An attempt was made to archive logs on

a Domino Server that is not running archival logging.
A Domino API error has occured.
Explanation: A Domino API error has occured.


User response: This operation cannot be performed
until archival logging is turned on for the Domino
server.
ACD5614E
The Domino Server is not running with

logging on. You cannot applylogs.
Explanation: An attempt was made to restore a

database and applylogs to this database. However,
logging has not been turned on for your Domino
server.
ACD5703E
The specified point-in-time is invalid.
Explanation: The specified point-in-time is invalid.

User response: Specifing a properly formatted
point-in-time value, then try the operation again.
ACD5704E
The requested transaction log file

archive was not found: Destination:
destination Logger Id :
OFlogid1:logid2-ONlogid3:logid4 Log
Number : lognumber

until logging is turned on for your Domino server.
Explanation: The Lotus Domino API that recovers

databases from the transaction log has requested a
transaction log file archive that was not found on the
Tivoli Storage Manager Server.
ACD5615E
You cannot archive a Domino Log file

when logging is turned off. Domino
return code: returncode.
Explanation: An attempt was made to archive a

Domino Log file for a Domino server that is not
running archival logging.
874
User response: Verify that the transaction log file

archive is on the Tivoli Storage Manager Server. If
transaction log file archive is not on the Tivoli Storage
Manager Server you may need to activate your
databases without applying logs.
ACD5707E ACD5716E
ACD5707E
The high level qualifier of the

transaction log file archive is invalid.
Explanation: The high level qualifier of a transaction

log file archive is invalid.
not a fully qualified path name.

System action: The transaction logs are restored to the
default path.
User response: Modify the value of
TRANSLOG_RECOVER_PATH to point to a fully
qualified path name.

ACD5712E
ACD5708I
The applylogs option is ignored when

activating databases restored from an
alternate Domino server.
Explanation: An attempt to apply transaction log files

to a database that was restored from an alternate
Domino server failed.
System action: The applylogs option is ignored and
the database is activated without applying any
transaction log file or files.
Wildcards are not allowed as part of the

database name specification:
Explanation: This message displays the incorrect

database name specification.
User response: Re-enter the command with the correct
database name specification.
ACD5713E
A DB2 API error has occured.
Explanation: A Domino API error has occured.

ACD5709E
The Domino environment variable

(environmentvariable) is missing or
invalid. Threshold criteria will be based
upon all available disk space on the log
volume.

ACD5714E
Explanation: An attempt to obtain the value of the

mentioned Domino environment variable from the
notes.ini file failed.
Table space backup cannot be

performed when the Domino server
DB2 database is not enabled for
rollforward recovery.
System action: Processing continues with thresholds

based upon all available transaction log disk space.
Explanation: Table space backups are not permitted

because the Domino server DB2 database is not enabled
for rollforward recovery.
User response: Define the mentioned Domino

environment variable correctly, then try the operation
again.
ACD5710E
The domino environment variable

(environmentvariable) is missing or
invalid. The destination path can not be
determined.
Explanation: An attempt to obtain the value of the

Domino environment variable TRANSLOG_Path from
the notes.ini file failed.
User response: You can either define the Domino
environment variable with a valid value or use the
/INTOPath option to specify the destination path. Try
ACD5711I
The alternate restore path,

alt_restore_path, is not a fully qualified
path name. The transaction logs will be
restored to the default path.
Explanation: The alternate restore path specified by

the notes.ini variable TRANSLOG_RECOVER_PATH is
User response: Enable the Domino server DB2

database for rollforward recovery and repeat the
operation.
ACD5715E
The database name specification is

invalid:
Explanation: The database name specification contains

invalid characters.
User response: Enter a valid database name
specification and rerun the command.
ACD5716E
Only one DB2 group can be specified

when restoring from DB2 group backup
images.
Explanation: The DB2RESTORE command can restore

only a single DB2 group at a time when restoring from
a DB2 group backup image. Use a full DB2 database
backup image to restore more than one DB2 group at a
time.
875
ACD5717E ACD5743W
User response: Re-enter the command and specify
only one DB2 Group.
ACD5717E

DB2 group name specification when
restoring from a DB2 group backup
image.
Explanation: Only one DB2 group can be specified

when restoring from a DB2 group backup image;
therefore, wildcards are no allowed. Use a full DB2
database backup image to restore more than one DB2
group at a time.
DB2 group name specification.
ACD5718E
The backup image does not contain the

following DB2 groups: db2groups
Explanation: The specified DB2 groups cannot be

found in the backup image. Use the query db2backup
command to determine the DB2 groups contained in
the backup image.
ACD5721E
The connection to the Data Protection

for Lotus Domino DB2 agent failed.
Explanation: The connection to the Data Protection for

Lotus Domino DB2 agent failed and there is no
connection the DB2 server
User response: Verify the Data Protection for Lotus
Domino DB2 agent is installed correctly. Verify that the
DB2 instance library path is included in the LIBPATH
and LD_LIBRARY_PATH environment variables for
AIX and Linux, respectively. Ex. LIBPATH=/home/
db2inst1/sqllib/lib32.
ACD5740E
Unable to load the IBM Tivoli Storage

Manager for Mail DLL, dll_name.
Explanation: Unable to load the DLL containing the

resources for the IBM Tivoli Storage Manager for Mail
GUI.
User response: Ensure that IBM Tivoli Storage
Manager for Mail is correctly installed.

DB2 group name specification.
ACD5719E
DB2 Group /INPLACE restore is not

supported.
ACD5741E
Error writing option_name preference to

the configuration file.
Explanation: The specified preference could not write

to the configuration file.
System action: Preferences processing ends.
Explanation: The DB2RESTORE command does not

support the /INPLACE option when a DB2 Group is
restored. A DB2 Group can only be restored to an
alternate DB2 database.
User response: Make sure you have a valid

configuration file, then try to update the preference
again.
ACD5742I
User response: Re-enter the command without

specifying the /INPLACE option.
ACD5720E
A DB2CONTainerpath must be specified

when DB2DIRECTORY is set in
notes.ini.
Explanation: The DB2RESTore command will fail

when the option DB2CONTainerpath is not set and the
Domino DB2 data location has been specified using the
notes.ini DB2DIRECTORY setting. The
DB2CONTainerpath specifies the location of the
Domino DB2 data for the alternate DB2 database.
User response: Specify a DB2CONTainerpath and
rerun the command.
The logfile_name log file did not need

pruning.
Explanation: The log file specified did not need to be

pruned.
User response: The log file will automatically be
pruned at a later date. If the log file is currently too
large, reduce the number of days the log entries are
retained.
ACD5743W
Changing from Selective Backup to

Incremental Backup will erase all
current selections for the Selective
Backup! You can only select ONE
directory at a time for the Incremental
Backup. Do you wish to continue?
Explanation: Incremental backup allows only one

directory to be backup each time.
System action: Processing continues once either Yes
or No is pressed.
876
ACD5764I ACD5773I
User response: User needs to understand how the
incremental and selective backup works.
User response: None

ACD5769I
ACD5764I
Changing this setting (to active only)

will refresh the view. All selections will
be lost. Do you want to continue?
Explanation: The user has selected the Active Only

toolbar button or pulldown menu item. The view must
be refreshed to activate this setting.
System action: Continues or ends processing as
requested.
User response: Select Yes to refresh the view or select
No to leave the current view unchanged.
Explanation: The user has selected databases pending

from a Domino Server other than the local Domino
Server and the Apply Logs box has been checked.
requested.
User response: Press Yes to continue or press No to
terminate the request.
ACD5770I
ACD5765I
Changing this setting (to active/inactive)

will refresh the view. All selections will
Explanation: The user has selected the Active/Inactive

toolbar button or pulldown menu item. The view must
be refreshed to activate this setting.
requested.
ACD5766I
When the view is refreshed all

selections will be lost and an attempt
will be made to expand the new tree to
the currently highlighted item. Do you
want to continue?

You have not selected any databases to

restore.
Explanation: The user has pressed the Restore button

but has not selected any databases to restore.
User response: Do not press the Restore button until
databases have been selected to restore.
ACD5771I
There are no databases to restore.
Explanation: The user has selected the Restore button

but there are no backed up databases.
User response: None
ACD5772E
Explanation: The user has selected the refresh toolbar

button or pulldown menu item.
requested.
Logs cannot be applied to databases

backed up from another Domino server.
Do you wish to continue?
More than one database has been

selected but only one restore location
has been specified. When more than one
database is selected the Restore Into
specification must contain an =.
Explanation: More than one database has been

selected and the Restore Into specification does not
contain an equal sign (=).
ACD5767I
You have not selected any pending

databases to activate.
Explanation: The user pressed the Activate button but

has not selected any pending databases to activate.
User response: Do not press the Activate button until
pending databases have been selected for activation.
ACD5768I

activation.
Explanation: The user has selected the Active button

but the list of pending databases is empty.
User response: Provide a valid Restore Into value and

try the operation again.
ACD5773I
You have selected multiple backups of

some databases to be restored. For these
databases, only the ones with the latest
backup dates will be restored. Do you
want to continue?
Explanation: More than one backup of at least one

database has been selected for restore. We will restore
the backup with the latest date.
requested.
877
ACD5774I ACD5816I
User response: Press Yes to continue. Press No to
ACD5774I
Changing the Point in Time or the By

Database Name settings will cause the
tree to be refreshed. All selections will
Explanation: The user has exited the Point in Time

dialog by pressing OK.
requested.
ACD5811I

name.
User response: None
ACD5812I

ACD5806W
The path specified does not contain a

notes.ini file. Do you still want to save
this?
There are no database backups matching

the filespec filespec and the server name
servername.
There are no transaction log file

archives matching the filespec filespec
and the server name servername.

name.
Explanation: A notes.ini file could not be found in the

specified directory path.
User response: None

requested.
ACD5813I
User response: Ensure the correct directory path is

specified.
Explanation: The user has pressed the Backup button

but has not selected any databases for a Selective
backup.
ACD5807W

successfully, however, the path specified
does not currently contain a notes.ini
file.
Explanation: A notes.ini file could not be found in the

System action: The preference has been set with the
User response: Ensure the correct directory path is
specified.
ACD5809I
There are no database backups for the

server named servername.

Storage Manager Server for the specified server name.
User response: None
You have not selected any databases for

Selective backup.
User response: Do not press the Backup button until

one or more databases have been selected for Selective
backup.
ACD5814E
Invalid incremental backup list was

created.
Explanation: An invalid incremental backup list was

created or found.
ACD5815I
You have not selected any databases for

Incremental backup.
Explanation: The user has pressed the Backup button

but has not selected a directory for Incremental backup.
ACD5810I
There are no transaction log file

archives for the server named servername.
Explanation: There are no transaction log file archives

on the Tivoli Storage Manager Server for the specified
server name.
User response: None
User response: Do not press the Backup button until a

directory has been selected for Incremental backup.
ACD5816I
You can only select ONE directory at a

time for Incremental backup.
Explanation: The user cannot select more than one

directory at a time for Incremental backup.
878
ACD5817E ACD5837I
User response: Do not press the Backup button until
only a directory has been selected for Incremental
backup.
ACD5817E
Invalid selective backup list was

created.
Explanation: An invalid selective backup list was

created or found.
ACD5818E
Insert to the Backup List failed.
Explanation: Cannot insert the database to the Backup

List.
with the latest date will be restored.

requested.
ACD5823I
Explanation: A query of the transaction log file

archives failed with an error.
ACD5827E

ACD5819E
Invalid Domino server name is selected.
Explanation: An invalid Domino server name is

selected.
A query for the transaction log file

archives failed.
The Restore Into name you entered is

too long. Please enter a name no longer
than numberofchars.
Explanation: The specified Restore Into name entered

is too long.
User response: Provide a valid Restore Into name,
then try the operation again.

ACD5820I
No transaction log file archives can be

found.
Explanation: There are no transaction log file archives.

The transaction log may not have been previously
archived.
User response: Ensure archival transaction logging is
in effect and archive some transaction log files before
re-attempting this operation.
ACD5821E
Invalid date. Please re-enter.
Explanation: An invalid date was entered.

System action: The current dialog remains active and
the focus is set to the invalid date.
ACD5830E
The Restore Into: field requires a

complete file name. Please enter the
field again with a complete filename or
an = (equals sign) representing the
complete file name.
Explanation: The Restore Into field requires a

complete filename. Directory names are not allowed.
User response: Provide a valid Restore Into name,
then try the operation again.
ACD5836I
The alternate DB2 database database was

Explanation: The specified alternate DB2 database was

deleted from the pending DB2 file and from the DB2
server.
User response: None
User response: Enter a valid date.

ACD5837I
ACD5822I
You have selected multiple archives of

some transaction log files to be restored.
For these log files, only the ones with
the latest archive dates will be restored.
Do you want to continue?
Explanation: More than one archive of at least one log

file has been selected for restore. The log file archive
There are no full DB2 database backups

for the server named servername.
Explanation: There are no full DB2 database backups

on the Tivoli Storage Manager Server for the specified
server name.
User response: None
879
ACD5838I ACD5847T
ACD5838I
There are no DB2 group backups

matching the groupspec filespec and the
Explanation: There are no DB2 group backups on the

name.
User response: None
ACD5839T
To rollforward the database to

point_in_time extract the required logs
with the following DB2 comand:
DB2ADUTL EXTRACT LOGS
BETWEEN first_log AND last_log DB
db2database Note: The command must be
issued from a DB2 window and from
the DB2 database log directory.
Explanation: A rollfoward command but a DB2

database restore operation has not yet been performed
ACD5843I
The DB2 logs required to rollforward

the DB2 database db2database to the
specified date are not archived to the
TSM server. Please archive the DB2 log
and re-issue the command.
Explanation: The database cannot be rollforward to

the specified date if the logs active on that date are not
archived.
User response: Archive the DB2 log.
ACD5844T
Issue the following DB2 command to

delete unneeded log archives: db2adutl
DELETE FULL OLDER THAN timestamp
DATABASE dbname
Explanation: The db2adutl command should be issued

from a DB2 command window to delete unneeded
backups.
User response: None
User response: None

ACD5845T
ACD5840T
DB2 Database db2database is ready for

rollforward. There is no need to extract
logs.
Explanation: No archived logs are required to

rollforward the database
User response: None
ACD5841E
A communication error with the DB2

agent has occurred.
Explanation: Some type of communication error has

occurred with the Data Protection for Lotus Domino
DB2 agent.

delete unneeded tablespace backups:
db2adutl DELETE TABLESPACE
OLDER THAN timestamp DATABASE
dbname

from a DB2 command window to delete unneeded
backups.
User response: None
ACD5846T

delete unneeded full database backups:
db2adutl DELETE LOGS BETWEEN
firstlog AND lastlog DATABASE dbname
User response: Repeat the operation.

from a DB2 command window to delete unneeded log
archives.
ACD5842E
The specified date is earlier than the

DB2 database backup date. Please
specify a date that is later than the
backup date.
Explanation: The rollforward to date must be greater

than the backup date.
User response: None

ACD5847T
There are no full database backups to

inactivate.
Explanation: No full database backups are ready for

inactivation.
User response: Specify a rollforward to date that is

greater thant the backup date.

User response: None
880
ACD5848T ACD5988W
ACD5848T
There are no tablespace backups to

inactivate.
Explanation: No tablespace backups are ready for

inactivation.
the symbolic link in /usr/lib directory that points to

the TSM API library.
User response: Complete the installation of the TSM
API, including updating the symbolic link in /usr/lib
and rerun the dominstall program.
User response: None

ACD5985E
ACD5849T
There are no log archives to inactivate.
Explanation: No logs archives are ready for

inactivation.
User response: None
ACD5850E
The alternate DB2 database database

cannot be found.
Explanation: The specified alternate DB2 database

could not be found in the DB2 pending file.
Explanation: The dominstall program encountered an

error while trying to read the symbolic link in the
/usr/lib directory that points to the TSM API library.
User response: Correct the error in the symbolic link
to the TSM API library in /usr/lib and run the
dominstall program again.
ACD5986W

User response: Verify that the specified alternate DB2
database exist in the DB2 pending file.
ACD5851T

delete unneeded log archives: db2adutl
DELETE LOGS BETWEEN firstlog AND
lastlog CHAIN chain DATABASE dbname

from a DB2 command window to delete unneeded log
archives.
Unable to read the symbolic link

linkname. error text.
Symbolic link /usr/lib/filename does not

point to installed file filename. Check if
the TSM API has been properly
installed.
Explanation: The symbolic link to the TSM API library

does not point to the TSM API library that the
dominstall program expects to use.
User response: This message does not indicate an
error. The dominstall program will continue install
processing. However, the installation should ensure
that the symbolic link in the /usr/lib directory points
to the correct version of the TSM API library.

User response: None
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.
ACD5987W
The Program Control attribute has not

been set for dsmc. This should be set if
you plan to use the TSM scheduler. and
the BPX.DAEMON facility has been
defined.
Explanation: The Program Control attribute has not

been set for dsmc.
User response: Set the Program Control attribute for
dsmc in order to use the scheduler

User response: Provide a valid value for the
-INTO=filename parameter, then try the operation
again.
ACD5984E
Can not find symbolic link linkname.

Check if the TSM API has been
properly installed.
Explanation: The dominstall program could not find
ACD5988W
The Program Control attribute has not

been set for dsmswitch. This should be
set if you plan to use the TSM
scheduler. and the BPX.DAEMON
facility has been defined.
Explanation: The Program Control attribute has not

been set for dsmswitch
User response: Set the Program Control attribute for
881
ACD5990E ACD6006E
dsmswitch in order to use the schduler.
ACD5990E
Change owner error for filename.
Explanation: An error occurred while trying to change

the owner of a file.
User response: Ensure the program has the proper
authorization to change the owner of the file, then run
the program again.
ACD5991E

User response: Correct the error and run the
ACD6000E
Error reading symbolic link linkname.
Explanation: An attempt to read the contents of the

symbolic link failed.
Change permissions error for filename.
Explanation: An error occurred while trying to change

the permissions of a file.
ACD6001E
Explanation: An attempt to read the contents of the

symbolic link failed.
User response: Ensure the program has the proper

authorization to change the permissions of the file, then
run the program again.
ACD5996E
The Data Protection for Domino

installation process did not complete
successfully. Please correct the error and
run this dominstall program again.
Explanation: The installation program completed

unsuccessfully.

ACD6002E

getpwuid() error for filename.
Explanation: The getpwuid() syscall could not find an

entry for the owner of the specified file.
Symbolic link linkname points to a
directory.
Explanation: The specified symbolic link points to a

directory. This is not a valid symbolic link and should
be removed before continuing.
ACD5999E
Symbolic link linkname points to an

unsupported file type.
Explanation: The specified symbolic link points to an

unsupported file type. This is not a valid symbolic link
and should be removed before continuing.
882
An error was encountered opening

directory directory name.
Explanation: An attempt to open a directory failed.

ACD6005E
ACD5998E
Unable to follow symbolic link linkname.
Explanation: The symbolic link points to a file that

does not exist.
ACD6003E
ACD5997E
A zero length symbolic link was

encountered for linkname.
Error removing file filename.
Explanation: An attempt to remove the file failed.

ACD6006E
Error creating symbolic link linkname to

filename.
Explanation: An attempt to create a symbolic link

failed.
ACD6007E ACD6028T
ACD6007E
A directory exists with the same name

as symbolic link to be created. Remove
or rename the directory directory name
before proceeding.

failed.
ACD6024E
Explanation: DP for Domino API could not be loaded.

User response: Ensure the DP for Domino API is
correctly installed. One possible cause is that the
TDPDOM.DLL (Windows) or libTdpDOM.(a,so) UNIX
does not exist in the system directory. Re-install DP for
Domino, if this is the case.
ACD6025T
ACD6008I
Symbolic link symoblic link to file name

already exists.
Explanation: A symlink to the file to be linked already

exists.
Could not load the DP for Domino API.
Make the suggested changes to the

dsm.sys file file name. Register the node
node name to the Tivoli Storage
Management server. Then issue the
following command to complete the
setup for this Domino server command
Explanation: The installation should perform the

suggested actions to complete the installation process.
ACD6010E
An unknown file type was encountered

when creating symlink linkname.

failed.
User response: Correct the error by either renaming
the file or removing the file, then run the program
again.
ACD6011E
Error on lstat to file filename.
Explanation: An attempt to obtain file information

from the system failed.
User response: Perform the suggested actions.

ACD6026T
Explanation: Choose the dsm.sys server entry (stanza)

used by the Tivoli Storage Manager Web client. This
entry will be used to complete the installation process.
User response: Reply with the number of the dsm.sys
entry to be used to complete the installation process.
ACD6027T

User response: Correct the error by removing the file,
then run the program again.
Choose the server entry used by the

Tivoli Storage Manager Web client.
Invalid entry. Please reply with a valid

entry number.
Explanation: The user replied with an entry number

outside of the range of the dsm.sys entries.
ACD6014E
You must run dominstall as a UID 0

(root) user. Switch to a UID 0 (root) user
before running this program.
Explanation: dominstall must be run run as a UID 0

(root) user.
User response: Switch to a UID 0 (root) user, then run
the program again.
ACD6023I
Changing the selection to Active and

Inactive backups. Note: This may result
in longer delays when displaying large
numbers of database backups. To
narrow down the list of displayed
databases, consider using the Filtering
Options on the Restore Tab. Do you
wish to continue?
User response: Reply with the correct number of the

dsm.sys entry to be used to complete the installation
process.
ACD6028T
The chosen entry is the following.
Explanation: The user replied with a valid dsm.sys

server entry number.
System action: Processing continues and the chosen
entry is displayed.
883
ACD6029T ACD7001I
ACD6029T
This entry appears to be already

configured with domnode = @1%s.; Do
you want to reconfigure this entry?;
Explanation: The user replied with a dsm.sys server

entry that has already been configured with a domnode
option.
continue installation without DB2 access configuration.

ACD6041T
Unrecognized or duplicate preference

options were found. @1%s
Explanation: An unrecognized or duplicate option

was found in the preference file.
System action: Processing continues with the chosen

entry or the user may choose a different entry.
User response: Reply Yes to choose this entry, or No

choose a different entry.
ACD6042E
ACD6030T
Is that correct?.;
Explanation: The user replied with a valid dsm.sys

server entry and the installation program is requesting
verification of the entry choosen.
System action: Processing continues with the chosen
entry or the user may choose a different entry.

Manager Client.
Explanation: The file dsmc was not found in the the

Tivoli Storage Manager client directory.
User response: Ensure the Tivoli Storage Manager
Client is correctly installed if you plan to use the web
client.
User response: Reply Yes to choose this entry, or No

choose a different entry.
ACD6043E
ACD6031T
Explanation: The dominstall program could not open

or create the silent output file specified.
Do you want to continue with the Tivoli

Storage Manager Web client
configuration?.
Explanation: The user replied NO for an already

configured entry, and the installation program is
requesting whether to continue the configuration
process.
Can not open silent install input file

filename. Check the fi le and directory
permissions.

User response: Correct the error, perhaps by trying to
create the file manually and then removing it and rerun
the dominstall program.
ACD6044E
Silent install error at line linenumber.
User response: Reply Yes to continue Tivoli Storage

Manager Web client processing, or No to continue
installation processing without Tivoli Storage Manager
Web client configuration.
Explanation: The silent input file has an incorrect

response at the specified line.
ACD6032T
User response: Correct the error in the input file and

and rerun the dominstall program.
The file @1%s exists. Reply Yes to

overwrite this file, or No to create the
file @2%s.
Explanation: The configuration file already exists in

the Notes specific directory. Replying yes will cause the
file to be over written, replying No will cause an
alternative configuration file to be created.
User response: Reply Yes to over write the existing
file, or No to create the alternative file.
ACD6039T
Is the Domino server DB2 enabled?
Explanation: The installation program is requesting

whether to configure access to the Domino DB2
database on DB2 enabled Domino servers.
User response: Reply Yes to set the DB2 user, or No to
884
ACD7000I

selective DB2 group backup from server
servername.

log when a selective DB2 group backup is started.
System action: None
ACD7001I

DB2 group backup from server
servername complete. Total Domino DB2
groups backed up: numberdbs Total bytes
Kb/Sec
ACD7002I ACD7023I

restore ends.
System action: None
System action: None
ACD7002I
ACD7007I

selective Domino DB2 database backup
from server servername.

log when a selective DB2 group backup is started.
System action: None

DB2 database from server servername to
server servername complete. Total bytes
Kb/Sec

restore ends.
System action: None
ACD7003I

Domino DB2 database backup from
Kb/Sec

ACD7020I

backup of DB2 group group from server
servername.


DB2 group backup begins.
System action: None
System action: None
ACD7004I
ACD7021I

DB2 group restore for server servername.

restore begins.
System action: None

DB2 group group from server servername

DB2 group backup completes successfully.
System action: None
ACD7005I

DB2 database restore for server
servername.

restore begins.
System action: None
ACD7022I

DB2 group group from server servername
failed.

DB2 group backup fails.
System action: None
ACD7006I

DB2 group from server servername to
Kb/Sec
ACD7023I

backup of DB2 database database from
server servername.

885
ACD7024I ACD7033I
DB2 database backup begins.
ACD7029I
System action: None

ACD7024I

DB2 database database from server
servername completed successfully.

DB2 database backup completes successfully.

System action: None
ACD7030I
System action: None

ACD7025I

DB2 database database from server
servername failed.

DB2 database backup fails.
System action: None

ACD7031I

restore of DB2 group group to DB2
databasedatabase on server servername.

System action: None

ACD7032I

DB2 group database to server servername

System action: None
ACD7028I

DB2 group group to server servername
failed.

System action: None
886

failed.

System action: None
ACD7027I

DB2 database database to server
servername completed successfully.

System action: None
ACD7026I

restore of DB2 database database to DB2
database database on server servername.

Domino DB2 database transaction log
archive from server servername.

System action: None
ACD7033I
Data Protection for Domino: Domino

DB2 database transaction log archive
from server servername succeeded.

System action: None
ACD7034I
ACD7034I
Data Protection for Domino: Domino

DB2 database transaction log archive
from server servername failed.

System action: None
887
888
Chapter 7. Data Protection for Microsoft Exchange Server

(ACN0000ACN9999)
This chapter describes the messages issued by Data Protection for Microsoft
Exchange Server. The messages begin with the prefix ACN and are listed in
numerical order.
ACN0003S

occurred.

occurred.
ACN0055E

failed.


ACN0004E
ACN0056E

in a valid format.

a return code.



ACN0057E
ACN0005E


ACN0053E

opened.

failed.
ACN0054E

string text.

correct level.
ACN0058E

product.

ACN0100E


Incomplete command:
889
ACN0101E ACN0152I
ACN0101E
Invalid argument:

ACN0102E
Invalid command:

ACN0133W


command entered.
up correctly.
ACN0134W
ACN0103E


command:

command options.
ACN0104E
Invalid option:

that was detected.
command options.
ACN0105E
Missing argument:



command entered.
up correctly.
ACN0150I

Protection for Microsoft Exchange Server application
client end by entering ctrl-C.
User response: None
ACN0151E

request.


ACN0132W

will continue.


beginning.
ACN0152I

command entered.


890

User response: None
ACN0153I ACN0200E
ACN0153I

in function

User response: None
ACN0154E
The Data Protection for Microsoft

Exchange Server application client
cannot work with the version of the
Tivoli Storage Manager API you have
installed. Please install version
version.release.level or greater.

Microsoft Exchange Server application client.
copy is distributed with the Data Protection for
ACN0160E

password.

ACN0161E


ACN0162E


ACN0155E
The Data Protection for Microsoft

Exchange Server application client
cannot work with the release of Tivoli
Storage Manager API you have
installed. Please install release

ACN0156E

Manager API.

ACN0163E

fully-qualified.

ACN0167E

long.

attempt failed.

not be loaded.
User response: None
ACN0200E

is correctly installed. Run the Data Protection for
Microsoft Exchange Server application client with the

reading.

User response: None
Chapter 7. Data Protection for Microsoft Exchange
891
ACN0201E ACN0213E
ACN0201E

writing.
ACN0208E



User response: None
User response: None
ACN0202E
ACN0209E

User response: None

(filename2) failed.

User response: None
ACN0203E

User response: None
ACN0210E


ACN0204E

User response: None

ACN0211E

User response: None
ACN0205E

obtained.



User response: None
ACN0212E
User response: None

ACN0206E

User response: None
ACN0207E

User response: None

name is too long.

attempt failed.
User response: None
ACN0213E


for Microsoft Exchange Server application client.
892
ACN0214E ACN0259E
ACN0214E


ACN0219E


valid.

ACN0215E

destination.

destinations.
ACN0216E
ACN0256E




ACN0257E

User response: None

ACN0217E
ACN0258E

name is invalid.

Processing ends.


a valid password.


valid password.
ACN0218E
ACN0259E


valid.

changed.

893
ACN0260I ACN357E
ACN0260I

ACN0266E

Manager HTML books.

User response: None

ACN0261I
ACN0267E

named servername.



new password.
User response: None

verify password.
ACN0263E


failed.
ACN0264I


ACN0300E

valid restore type.
ACN0301E

valid backup type.
ACN351E



ACN0265E

ACN357E

file-name.

894
ACN366E ACN495E
ACN366E

file-name.

space).
ACN385E


ACN367E

Tracing disabled.

ACN476E

error.

operation.

continues.
ACN487E


link.
ACN368E

ACN383E


link.
tracefile option.
ACN384E




ACN488E


ACN495E


given log location.
895
ACN496I ACN519E
ACN496I

minutes.

and old data saved.
ACN497I

minutes.

ACN515E

ACN516I
ACN498I


was stopped.
ACN517I

nodename.

operation.
representative.

Explanation: None.
ACN518E

ACN501E


the Data Protection for Microsoft Exchange Server
processes or programs. The following events can be
recevied:


dsmagentnode.

LOCAL).

ACN519E

returncode.

896
ACN520E ACN3503I
ACN520E

properly.

representative.
ACN521E


ACN522E
DIAG:

ACN524S


on the disk).
are incomplete.
ACN3500I
Data Protection for Exchange: Starting

backup type backup of object name from
server server name.

log when a backup is started.
System action: None
ACN3501I
Data Protection for Exchange: backup type

backup of object name from server server
name completed successfully. bytes bytes
sent in seconds seconds.

log when a backup completes successfully.
System action: None
ACN3502E

backup of object name from server server
name failed, rc = return code.

log when a backup fails.
System action: None
ACN3503I

backup of storage group name from server
server name was cancelled by the user.

log when a storage group backup was cancelled by the
user.
System action: None

897
ACN3504I ACN3513E
ACN3504I

restore for server servername.

log indicating the start of a restore.
System action: None
ACN3509I

restore of storage group storage group
name to server server name was cancelled
by the user.

log when a storage group restore was cancelled by the
user.
System action: None
ACN3505I
Data Protection for Exchange: Restore

from server servername to servername is
complete. Total backups restored: Total
bytes transferred: Elapsed processing
time: Secs Throughput rate: Kb/Sec

log indicating the end of a restore.
System action: None
ACN3506I

backup type restore of storage group
storage group name to server server name.

log indicating the start of a storage group restore.
System action: None
ACN3507E

name to server server name completed
successfully.

ACN3510I
Data Protection for Exchange:

Attempting to inactivate the object:
filespace - [filespace name], hl - [high level],
ll - [low level]

log indicating the attempt to inactivate an object.
System action: None
ACN3511I

Inactivation of the previous objects
succeeded.

log indicating the success of the inactivation of objects.
System action: None
ACN3512E

Inactivation of the previous objects
failed.

log when a storage group restore completes
successfully.

log indicating the failure of the inactivation of objects.
System action: None
System action: None
ACN3508E

name to server server name failed, rc =
return code.
ACN3513E

Inactivation of the previous objects was
canceled.

log when a storage group restore fails.

log indicating the failure of the inactivation of objects
because the task was canceled by the user.
System action: None
System action: None
898
ACN3514I ACN5056I
ACN3514I

backup for server servername.

log indicating the start of a backup.
System action: None
ACN3516I
Data Protection for Exchange: Backup of

server servername is complete. Total
storage groups backed up: Total bytes
transferred: Elapsed processing time:
Secs Throughput rate: Kb/Sec

log indicating the end of a backup request.
System action: Processing continues using default

settings.
User response: Ensure that the configuration file
exists, and enter the command again.
ACN5052E

preferences file.
User response: View any other messages that were
displayed. Fix any of the problems indicated and enter
the command again.
ACN5053E
System action: None

ACN3517E

server servername failed, rc = returncode.

log indicating the failure of a backup request.
System action: None
ACN3518I

server servername failed. The request was
canceled by the user.

log indicating the failure of a backup request. The user
canceled the backup.
System action: None

preference preference.
The value for the preference preference is

not valid. See the TDPEXCC HELP SET
output or the Users Guide for valid
SET command parameters.
Explanation: The preference being set is not valid.

User response: Run the tdpexcc help set command
or see the Users Guide for valid SET command
parameters.
ACN5054I

successfully.
Explanation: The preference was set successfully.

User response: 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
running on a later version of Microsoft Exchange, the
dll that is attempting to load is esebcli2.dll.
ACN5050I
A new configuration file has been

created.
Explanation: The /configfile value specified a file

name that does not exist. A new file has been created.
ACN5051I

Explanation: The /configfile value specified a file that

cannot be found. Default settings will be used.
User response: Ensure that the Microsoft Exchange

Server has been correctly installed.
ACN5056I


unsuccessful.
User response: Ensure that the log file name is valid
and that the log file exists. If a valid log file name was
specified, view the log for indications of what the
problem may be.
899
ACN5057I ACN5065E
ACN5057I
The logfile log file has been pruned

successfully.
Explanation: The specified log file was pruned

successfully.
ACN5058W
The length of the logf ile name is

greater than the maximum allowed.
Processing will continue using a log file
name of logfile in the current directory.
Explanation: The log file name entered was not fully

qualified. When the fully qualified log file name was
created, it was longer than the maximum allowed
length for a log file name.
ACN5062E
Explanation: IBM Tivoli Storage Manager for Mail has

detected a version of Microsoft Exchange Server that is
not supported.
User response: Refer to the software requirements
section of the product documentation to view a list of
the supported versions of Microsoft Exchange Server. If
the version of Microsoft Exchange Server running is a
supported version, try the operation again. If the error
ACN5063E
System action: Processing continues creating and

using a log file in the current directory.
User response: Update the log file name using a fully
qualified path.
ACN5059W

writing. There will be no logging of
events.
Explanation: The specified log file could not be

opened for append and logging of events will not
occur. The log file may be read-only or the log file
name is not valid.
An error occurred trying to get the

Microsoft Exchange version information.
It could be a problem with the registry.
Or, a Microsoft Exchange Server is not
installed on this machine.

registry to determine the level of Microsoft Exchange
that is currently running. This attempt failed.
User response: Determine if the registry has been
corrupted. Also, ensure that the Microsoft Exchange
Server is installed on this machine.
ACN5064W
System action: Processing continues without logging.

User response: Determine why the log could not be
opened. You may need to ensure that the log file is not
read-only, or ensure that a valid drive or partition is
specified in the log file name.
The version of Microsoft Exchange that

is running is not a supported version for
IBM Tivoli Storage Manager for Mail.
The service cannot be started when

doing a restore.
Explanation: A request was made to restore the listed

database. However, the service associated with this
database has already started. The service needs to be
stopped in order to do this restore.
ACN5060E

occurred.
Explanation: A Tivoli Storage Manager API api error

has occurred.
ACN5061E
A Microsoft Exchange api error has

occurred.
Explanation: A Microsoft Exchange api error has

occurred.
900
User response: Stop the associated service and enter

the restore command again.
ACN5065E
All of the services associated with this

restore are running.
Explanation: A request was made to restore several

databases. However, all of the services associated with
these databases are running. The services need to be
stopped in order to do this restore.
User response: Stop the associated services and enter
the restore command again.
ACN5066W ACN5076W
ACN5066W
The storage group <storagegroup> does

not exist.
Explanation: The storage group that was entered that

does not exist on the server specified.
User response: Enter the command specifying a
storage group that exists.
ACN5067E
None of the storage groups or databases

entered exist. Or, if they do exist, and
you are using Exchange 2000 or later, the
databases have not been dismounted.
Explanation: The storage groups that were entered

either do not exist on the Microsoft Exchange Server or
the databases within the storage groups have not been
dismounted.
User response: Verify that the storage groups or
databases exist and that the databases have been
dismounted before starting the restore.
ACN5068W
The database <databasename> does not

exist in the storage group <storagegroup>.
Explanation: The database that was entered does not

exist in the storage group that was entered.
User response: Enter the command again specifying a
valid database name that exists in a valid storage
group.
ACN5069W
The database <database> in the storage

group <storage group> is not dismounted.
Explanation: While examining the list of databases to

restore, it was determined that not all of the databases
within the specified storage groups were dismounted.
System action: Processing continues skipping over the
listed databases and storage groups.
User response: Ensure that the databases are
dismounted and enter the command again.
ACN5070W
The Directory Service is not running.

The Directory will not be backed up.
Explanation: A request was made to backup the

Directory service. However, the Directory service needs
to be running in order to do the backup.
User response: Start the Directory service and enter
the backup command again.
ACN5071W
The Information Store is not running.

The Information Store will not be
backed up.
Explanation: A request was made to backup the

Information Store. However, the Information Store
needs to be running in order to do the backup.
User response: Start the Information Store and enter
the backup command again.
ACN5072W
Databases in storage group <storage

group> are dismounted -- skipping.
Explanation: A request was made to backup a set of

storage groups. However, some databases in this
storage group are not mounted. All of the databases
need to be mounted in order to backup this storage
group.
System action: Processing continues, but dismounted
databases are skipped.
User response: Ensure that all of the databases are
mounted in the storage group and start the backup for
the storage group again.
ACN5073E
None of the storage groups entered are

in a state to be backed up.

storage groups. However, each of the storage groups
entered has at least one database that is dismounted.
User response: Ensure that all of the databases are
mounted in the storage groups and start the backup for
the storage groups again.
ACN5074E
None of the databases or storage groups

entered exist.

storage groups or databases that do not. The storage
group and database names might not have been
entered using the correct casing.
User response: Ensure that the correct casing is used
when entering the list of databases or storage groups to
be backed up. Enter the backup command again.
ACN5076W
Unable to inactivate all previous backup

objects.
Explanation: A request to inactivate some previous

backup objects failed.
User response: When the next full backup of the
901
ACN5083I ACN5228I
database is run, another attempt will be made to
inactivate the failed objects.
ACN5140I
ACN5083I
Explanation: The storage group that was specified by

the user is not found on this Exchange server.
All of the storage groups entered have

been excluded.
Explanation: An attempt was made to do a backup.

However, the storage groups or databases entered have
been excluded by an exclude statement in the options
file.
User response: If you want these storage groups or
databases backed up, modify the exclude statements in
your options file.
ACN5084W
IS was not input as one of the parts to

restore. The partial option will be
ignored.
Explanation: A request was made to restore either the

private or public part of the Information Store.
However, the IS was not input as one of the parts to
restore.
System action: Processing continues ignoring the
partial option.
User response: To restore either the public or private
part of the Information Store, enter IS as an input.
ACN5086W
None of the storage groups entered

exist. Or, if doing a DBCOPY backup,
the database entered does not exist.
Explanation: A storage group was entered that does

not exist on the server specified. Or, if a DBCOPY
backup was entered, the dbname specified does not
exist on the Microsoft Exchange Server.
User response: Enter the command specifying a
storage group or dbname that exists.
ACN5087E

have a stored password, use of the
-TSMPassword=xxx option will set and
Explanation: The client options file has the

PASSWORDACCESS option set to generate. Currently,
there is no password that has been stored. An initial
password needs to be stored.
-TSMPassword option. Any subsequent commands
should then complete without specifying a password.
902
Storage Group <storagegroup> does not

exist - skipping.
System action: This storage group is skipped.

User response: Ensure that the storage group name is
spelled correctly and enter the command again.
ACN5141I
Database <database>, Storage Group

<storagegroup> does not exist - skipping.
Explanation: This combination of storage group and

database name that was specified is not found on this
Microsoft Exchange server.
System action: The storage group and database are
skipped.
User response: Ensure that the the storage group
name and databse name are spelled correctly and enter
the command again.
ACN5142E
No storage group was found that

matches the request.
Explanation: The storage groups or databases could

not be found on this Microsoft Exchange server.
User response: Ensure that the storage group or
database names are spelled correctly and enter the
command again.
ACN5209I

server name servername and the
following filespecs:filespecs.

Tivoli Storage Manager server for the specified server
name.
User response: None
ACN5228I
Data Protection for Exchange is not

configured for VSS operations.
Explanation: Data Protection for Exchange has not

been configured to perform VSS operations.
the Tivoli Storage Manager for Copy Services Microsoft Exchange VSS Integration Module must be
installed and the Data Protection for Exchange
LOCALDSMAGENTNODE preference must be set
correctly. Refer to the Data Protection for Exchange
Users Guide for details on configuring the client for
VSS operations.
ACN5229E ACN5304E
ACN5229E
Error obtaining VSS information from

Local DSMAgent Node:
localdsmagentnode.
Explanation: Data Protection for Exchange attempted

to obtain VSS information through the specified
LOCALDSMAGENTNODE but failed. The error
message encountered is also displayed.
ACN5241E
The Microsoft Exchange Information

Store is currently not running.
Explanation: An attempt was made to retrieve the

Microsoft Exchange Server information. This attempt
failed.
User response: Refer to the error message displayed

along with this message.
User response: In order to retrieve the Microsoft

Exchange Server information, the Microsoft Exchange
Information Store needs to be running. Start this service
to get the requested information.
ACN5237E
ACN5301E
System action: VSS information is not displayed.
Unable to communicate with the

Microsoft Exchange Server.
Unable to get the value for the

Organization from the registry.
Explanation: An attempt was made to communicate

the with the Microsoft Exchange Server that was
entered. This attempt failed.

registry to determine the organization for the Microsoft
Exchange Server. This attempt failed.
User response: Ensure that the name of the Microsoft

Exchange server that was entered is valid. Also, ensure
that the Microsoft Exchange server is running.
User response: Determine if there is a problem with

the registry or ensure that the Microsoft Exchange
Server is installed properly.
ACN5238E
ACN5302E
Unable to retrieve the domain

information for the Microsoft Exchange
Server.

domain information for the Microsoft Exchange Server.
Unable to get the value for the Site from

the registry.

registry to determine the site for the Microsoft
Exchange Server. This attempt failed.

server is running.

ACN5239E
ACN5303E
Unable to retrieve the storage group

information.

storage group information for the Microsoft Exchange
Server. This attempt failed.
Server is running properly.
ACN5240E
Unable to retrieve the database

information.

database information for the storage group of the
Microsoft Exchange Server. This attempt failed.
Unable to get the value for Circular

Logging from the registry.

registry to determine the Circular Logging setting for
either the IS or the DIR of the Microsoft Exchange
Server. This attempt failed.
ACN5304E
Unable to open service to determine if

running or not.
Explanation: An attempt to open a service failed.

Server is running properly.

the Microsoft Exchange server.
903
ACN5305E ACN5359E
ACN5305E
Unable to query service information.
Explanation: An attempt to query specific service

information failed.
the Microsoft Exchange server.
ACN5350E
An unknown Exchange API error has

occurred.
Explanation: An Exchange API error has occurred but

the associated error message could not be found. The
Windows NT event log may contain more information.
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,
ACN5351E
The Exchange server application is not

registered for backup.
Explanation: The Exchange server application must be

registered for backup with the Windows Server. The
ACN5352E

registered for offline restore.

registered for offline restore with the Windows Server.
The Windows NT event log may contain more
information.

ACN5354E
The storage group was not found.
Explanation: The specified storage group name was

not found.
User response: Verify the command input and retry
the operation. If the error persists, contact your service
representative.
ACN5355E
The database was not found.
Explanation: The specified database name was not

found.
User response: Verify the command input and retry
the operation. If the error persists, contact your service
representative.
ACN5356E
The database file name is undefined.
Explanation: Every Microsoft Exchange database must

specify a database file name.
User response: Verify the database properties and
retry the operation. If the error persists, contact your
ACN5357W
The truncation of the transaction log

failed.
Explanation: The truncation of the transaction log

failed.
User response: Refer to other messages that are
displayed to determine the problem.

ACN5353E

registered for online restore.

registered for online restore with the Windows Server.
The Windows NT event log may contain more
information.
904
ACN5358E
A Microsoft Exchange API protocol error

has occurred.
Explanation: An unrecoverable Microsoft Exchange

API protocol error has occurred.
ACN5359E
An attempt was made to get the TEMP

environment variable. This attempt
failed.
Explanation: The TEMPLOGRESTOREPATH option

was not set for the restore. Therefore, an attempt was
made to get the TEMP environment variable for the
machine. This attempt failed.
ACN5360E ACN5724I
ACN5705W
User response: Ensure that the TEMP environment

variable is set for this machine. You can also use the
TEMPLOGRESTOREPATH option with the restore.
ACN5360E
The /ERASEexistingdata option is not

allowed during a partial restore.
Explanation: A partial storage group restore was

requested with the /ERASEexistingdata option. The
/ERASEexistingdata option is not allowed during a
partial restore.
User response: Enter the command to restore the
entire storage group or enter the command without the
/ERASEexistingdata option.
Explanation: An attempt was made to run setup for

the Tivoli Storage Manager API. However, errors were
encountered.
determine the problem. If this file does not exist, it is
possible that the TSM API is not installed properly. If
this is the case, reinstall the TSM API and try running
the command again.
ACN5706I
ACN5361E
It is invalid to have an * within a

storage group name.
Explanation: An attempt was made to backup a

storage group that contains an *. It is invalid to have
an * in a storage group name.


pruning.

pruned.
System action: Processing continues, but this storage

group will not be backed up.

pruned at a later date. If the log file is too large now,
lower the number of days the log entries are retained.
User response: Rename the storage group, otherwise

this storage group cannot be backed up.
ACN5707W
ACN5362W
The filespace <filespace> in an invalid

filespace name.
The logfile_name log file could not be

opened for writing. The log was not
pruned and there will be no logging of
events.
Explanation: The filespace displayed in the message

exists, but is an invalid filespace.
Explanation: The log could not be opened for append.

Therefore, there will be no logging done and the
request to prune was not done.
System action: Processing continues, but this filespace

will not be used.

User response: Ensure that the storage group name

does not contain invalid characters. Refer to the
Microsoft Exchange documentation for the list of
invalid characters.
User response: Determine why the log could not be

opened. You may need to ensure that the file is not
read-only, or ensure that a valid drive or partition is
specified with the log file name.
ACN5500E
ACN5724I
The MultiByteToWideChar() function

failed.
Explanation: An internal error occurred.

ACN5501E
The WideCharToMultiByte() function

failed.
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.
User response: Select a database and press the Backup
button.

905
ACN5725I ACN5805E
ACN5725I
No Storage Groups have been selected

for backup.
Explanation: The Backup button was pressed but no

Storage Groups have been selected in the tree or list in
the graphical user interface.
ACN5798E
MS Exchange API api name failed with

HRESULT: api retcode -
Explanation: A Microsoft Exchange API error occurred

during an operation. The specific API function that
failed along with the HRESULT code of the failure and
possible message associated with that error is
displayed.
User response: Select a Storage Group and press the

Backup button.
ACN5741I
User response: If the Windows Event Log does not

help resolve the problem, stop and restart the Exchange
server and retry the operation. If the error persists,
No Backups have been selected for

restore.
Explanation: The Restore button was pressed but

nothing was selected in the tree or list view.
ACN5800E

User response: Make a selection in the tree or list
view and press the Restore button again.
ACN5758W
At least one of the databases services

that is selected for restore is running.
Do you want to stop the service(s)?
Explanation: A service that you are trying to restore is

running. The service cannot be running in order to
perform the restore.
Explanation: When attempting to process an Exchange

backup on the Tivoli Storage Manager Server, not all
required objects were present. The operation cannot
proceed. The specific backup affected is logged.
User response: Retry the operation. If the error
ACN5802I
When a Recovery Storage Group exists,

mailbox and public folder databases
cannot be restored in the same
operation. ACTION: Please select either
a mailbox OR public folder database for
restore.
ACN5803I
When performing a mailbox database

restore to a Recovery Storage Group, the
Replay Restored Logs ONLY option
must be specified or the restore may
fail. ACTION: The Replay Restored
Logs ONLY option will
AUTOMATICALLY be used on the
restore. Do you wish to continue with
the restore?
ACN5805E
Restore failed. File already exists.
System action: None

User response: Choose the desired response and
continue.
ACN5759W
At least one of the databases that is

selected for restore is mounted. Do you
want to dismount the database(s)?
Explanation: A database you are trying to restore is

mounted.
System action: None
User response: Click OK to dismount and continue,
or cancel to stop.
ACN5766E
Unable to dismount database database in

storage group storage group. Do you want
to continue the restore process?
Explanation: An error occurred while trying to

dismount a database.
User response: Press OK to continue the restore or
press cancel to stop.
906
Backup is corrupt. See log file for

Explanation: The specified file already exists in the

restore (/INTO) path. The RESTOREFILES command is
designed not to overwrite existing files.
System action: The restore operation fails and
processing ends.
User response: If you want to restore the specified
file, you must first delete the file that exists in the
restore (/INTO) path and retry the operation or specify
a different restore (/INTO) path and retry the
operation.
ACN5810E ACN5817E
ACN5810E
Restoring Legacy backups and VSS

backups in the same restore operation is
not supported. Retry the restores in
separate operations.
ACN5814E
Invalid command. Data Protection for

Exchange does not support OFFLOAD
with the specified backup destination.
Explanation: At least one VSS backup object and one

Legacy backup object were selected for a restore in the
same operation. This is not supported.
Explanation: The OFFLOAD option was specified

with an unsupported backup destination. Data
Protection for Exchange only supports offload with a
backup destination of TSM.
System action: The restore operation is canceled.
System action: The backup operation is canceled.
User response: Retry the restores specifying the

Legacy backups and VSS backups in separate
operations.
User response: Retry the VSS offloaded backup

operation specifying a backup destination of TSM.
ACN5815E
ACN5811E

Exchange only supports VSS backup
types of FULL and COPY.
Explanation: An invalid backup type was specified on

the VSS backup request. Data Protection for Exchange
supports backup types of FULL and COPY when using
the VSS backup method.
User response: Retry the backup operation specifying
a supported VSS backup type.
ACN5812E

User response: Retry the backup operation without
specifying the offload option or by specifying the VSS
backup method.
ACN5813E
Explanation: There was a failure when Data Protection

for Exchange performed the VSS operation.
User response: Verify that the Client Acceptor
ACN5816E

Exchange does not support OFFLOAD
with the Legacy backup method.

when using the Legacy backup method. Data
Protection for Exchange does not support offload with
the Legacy backup method. Data Protection for
Exchange supports offload with the VSS backup
method only.

Exchange only supports Legacy backups
with a backup destination of TSM.
Explanation: An invalid backup destination was

specified with the Legacy backup method. Data
Protection for Exchange only supports a backup
destination of TSM when using the Legacy backup
method.
a backup destination of TSM.

returncode.
Data Protection for Exchange is not able

to run VSS operations. You must be
running Exchange Server 2003 (or later)
and have the Tivoli Storage Manager for
Copy Services - Microsoft Exchange VSS
Integration Module installed.
Explanation: In order to perform VSS operations, Data

Protection for Exchange verifies that the Exchange
Server level is at least Exchange Server 2003 and that
the Tivoli Storage Manager for Copy Services Microsoft Exchange VSS Integration Module is
installed. If the Tivoli Storage Manager for Copy
Services - Microsoft Exchange VSS Integration Module
is installed, there will be a license file, acsexc.lic, in the
Data Protection for Exchange installation directory.
User response: Verify that the prerequisites identified
above are met and retry the operation. If the error
ACN5817E
Missing, blank, or invalid Local

DSMAGENT Node Name is not
allowed.
Explanation: In order to run VSS operations, Data

Protection for Exchange verifies that the Local
DSMAGENT Node Name is specified and valid. This
error indicates that the Local DSMAGENT Node Name
is missing, blank, or invalid.
User response: Set the Local DSMAGENT Node
Name to a valid value and retry the operation.
907
ACN5818E ACN5836T
ACN5818E

Exchange only supports restoring VSS
backup types of FULL and COPY.

the VSS restore request. Data Protection for Exchange
supports restoring backups of type FULL and COPY.
User response: Retry the restore operation specifying
ACN5824I
Explanation: Replica for the storage group specified

by the user is not found on this Exchange server.
spelled correctly and has a replica and enter the
command again.
ACN5825E
ACN5819E
Multiple backup objects were found for

the specified storage group(s) and
backup destination. Use the OBJECT=
and BACKUPDESTINATION= options
to identify which specific backup object
to restore.
Explanation: The backup object specified for the VSS

restore operation was not specific enough to be unique.
More information is required in order to restore the
correct backup object.
the /OBJECT= and /BACKUPDESTINATION
parameters.
There were no Exchange backups found
on the Tivoli Storage Manager server
matching the specified criteria.

Exchange does not support
FROMREPLICA with the Legacy backup
method.
Explanation: The FROMREPLICA option was

specified when using the Legacy backup method. Data
Protection for Exchange does not support fromreplica
with the Legacy backup method. Data Protection for
Exchange supports fromreplica with the VSS backup
method only.
specifying the fromreplica option or by specifying the
VSS backup method.
ACN5829E
ACN5820E
Storage Group <storagegroup> does not

have replica - skipping.

Exchange does not support INTOSG
with the Legacy restore method.
Explanation: A query was issued to the Tivoli Storage

Manager server to find the Data Protection for
Exchange backups that match the specified search
criteria. There were no backups found.
Explanation: The INTOSG option was specified when

using the Legacy restore method. Data Protection for
Exchange does not support INTOSG with the Legacy
restore method. Data Protection for Exchange supports
INTOSG with the VSS restore method only.
User response: Retry the restore operation without

specifying the INTOSG option or by specifying the VSS
restore method.
ACN5821I
908
You have selected a VSS backup for

restore. Please note the following: 1.
Even if a Recovery Storage Group exists,
it will NOT be used for this restore. The
data will be restored directly to the
production storage groups. 2. ALL
mounted databases within the chosen
storage group(s) will be dismounted, not
just the databases selected for restore. 3.
If the chosen VSS backups are LOCAL
and reside on devices that support VSS
Instant Restore, ALL data on the source
volumes will be overwritten,
INCLUDING the current Exchange
transaction logs. (This is not true if the
Disable VSS Instant Restore checkbox
is selected.) Do you want to continue
with the VSS restore operation?
ACN5836T
You have selected a VSS backup for

restore. Please note the following: 1.
ALL mounted databases within the
storage group(s) being restored into will
be dismounted, not just the databases
selected for restore. 2. If the chosen VSS
backups are LOCAL and reside on
devices that support VSS Instant
Restore, ALL data on the source
volumes will be overwritten,
INCLUDING the current Exchange
transaction logs. (This is not true if the
Disable VSS Instant Restore checkbox
is selected.) Do you want to continue
with the VSS restore operation?
ACN5837E ACN5843I
ACN5837E

Exchange does not support INTOSG
with the Exchange Servers earlier than
Exchange 2007.
Explanation: The INTOSG option was specified when

using not Exchange 2007 or later. Data Protection for
Exchange does not support INTOSG with the Exchange
Servers earlier than Exchange 2007. Data Protection for
Exchange supports INTOSG with the Exchange Server
2007 or later.
User response: Retry the restore operation without
specifying the INTOSG option or by using Exchange
2007.
ACN5839E
recreate the database on the Exchange Server from the

restored files.
ACN5843I
No backups found for a Storage Group

<storagegroup> that match the
specifications entered.
Explanation: No backups found for the entered

storage group that match specified backup method,
backup destination and OBJECT (if any).
spelled correctly, backup method, backup destination
and OBJECT (if any) are specified correctly and enter
the command again.
Alternate or recovery storage

group(s)/database(s) you are restoring to
do not exist.
Explanation: The alternate or recovery storage groups

that were entered do not exist on the Microsoft
Exchange Server or the databases within the storage
groups do not exist on the Microsoft Exchange Server.
User response: Verify that the storage groups and
databases exist and the databases have been
dismounted before starting the restore.
ACN5840W
Did not find any storage group on

Exchange Server that has all databases
that matched databases selected to
alternate restore. Verify that all
necessary databases are created in the
alternate storage group then try calling
the dialog again.
Explanation: Did not find any storage group on

Exchange Server that has all databases that matched
databases selected to alternate restore.
System action: The Restore Into dialog is not pop up.
User response: Verify that all necessary databases are
created in the alternate storage group then try calling
the dialog again.
ACN5841W
Database database from storage group

storagegroup has not been found on
Exchange Server. The database files will
be restored.
Explanation: Database has not been found on

Exchange Server. The restore will continue to allow VSS
writer to restore the database files.
System action: The restore operation continues.
User response: After the restore completed, you can
909
910
Chapter 8. Data Protection for Microsoft SQL Server

(ACO0000ACO9999)
This chapter describes the messages issued by Data Protection for Microsoft SQL
Server. The messages begin with the prefix ACO and are listed in numerical order.
ACO0003S

occurred.

occurred.
ACO0004E

a return code.
ACO0005E


ACO0053E

opened.

failed.

failed.
ACO0056E

in a valid format.

ACO0057E

string text.

correct level.
ACO0058E



product.
ACO0054E
ACO0100E
Incomplete command:




ACO0101E
ACO0055E
Invalid argument:
911
ACO0102E ACO0152I
ACO0133W



ACO0102E

command entered.
Invalid command:

ACO0103E

command:

command options.
ACO0104E
Invalid option:

that was detected.
command options.
ACO0105E
Missing argument:

ACO0132W

will continue.

up correctly.
ACO0134W


command entered.
up correctly.
ACO0150I

Protection for Microsoft SQL Server application client
end by entering ctrl-C.
User response: None
ACO0151E

request.


beginning.


command entered.
ACO0152I



User response: None
912
ACO0153I ACO0200E
ACO0153I

in function

User response: None
ACO0154E
The Data Protection for Microsoft SQL

Server application client cannot work
with the version of the Tivoli Storage
Manager API you have installed. Please
install version version.release.level or
greater.

Microsoft SQL Server application client.
ACO0160E

password.

ACO0161E


ACO0162E


ACO0155E
The Data Protection for Microsoft SQL

Server application client cannot work
with the release of Tivoli Storage
Manager API you have installed. Please
install release version.release.l evel or
greater.

ACO0156E

Manager API.

ACO0163E

fully-qualified.

ACO0167E

long.

attempt failed.

not be loaded.
User response: None
ACO0200E

is correctly installed. Run the Data Protection for
Microsoft SQL Server application client with the

reading.

User response: None
Chapter 8. Data Protection for Microsoft SQL
913
ACO0201E ACO0213E
ACO0201E

writing.
ACO0208E



User response: None
User response: None
ACO0202E
ACO0209E

User response: None

(filename2) failed.

User response: None
ACO0203E

User response: None
ACO0210E


ACO0204E

User response: None

ACO0211E

User response: None
ACO0205E

obtained.



User response: None
ACO0212E
User response: None

ACO0206E

User response: None
ACO0207E

User response: None

name is too long.

attempt failed.
User response: None
ACO0213E


for Microsoft SQL Server application client.
914
ACO0214E ACO0259E
ACO0214E


ACO0219E


valid.

ACO0215E

destination.

destinations.
ACO0216E
ACO0256E




ACO0257E

User response: None

ACO0217E
ACO0258E

name is invalid.

Processing ends.


a valid password.


valid password.
ACO0218E
ACO0259E


valid.

changed.

915
ACO0260I ACO357E
ACO0260I

ACO0266E

Manager HTML books.

User response: None

ACO0261I
ACO0267E

named servername.



new password.
User response: None

verify password.
ACO0263E


failed.
ACO0264I


ACO0300E

valid restore type.
ACO0301E

valid backup type.
ACO351E



ACO0265E

ACO357E

file-name.

916
ACO366E ACO495E
ACO366E

file-name.

space).
ACO385E


ACO367E

Tracing disabled.

ACO476E

error.

operation.

continues.
ACO487E


link.
ACO368E

ACO383E


link.
tracefile option.
ACO384E




ACO488E


ACO495E


given log location.
917
ACO496I ACO519E
ACO496I

minutes.

and old data saved.
ACO497I

minutes.

ACO498I

ACO515E

ACO516I

nodename.

operation.
representative.


the Data Protection for Microsoft SQL Server processes
or programs. The following events can be recevied:
was stopped.
ACO517I

Explanation: None.
ACO518E

ACO501E

dsmagentnode.

LOCAL).

ACO519E

returncode.

918
ACO520E ACO3003I
ACO520E

properly.

representative.
ACO521E


ACO522E
DIAG:

ACO524S


on the disk).
are incomplete.
ACO3000I
Data Protection for SQL: Starting backup

type backup of database database name
from server server name.
Explanation: This is an informational message written

a backup is started.
System action: None
ACO3001I
Data Protection for SQL: backup type

backup of database database name from
server server name completed
successfully.

a database backup completes successfully.
System action: None
ACO3002E

server server name failed, rc = return code.

a database restore fails.
System action: None
ACO3003I
Data Protection for SQL: Starting restore

type restore of backup object object name
to database database name on server server
name.

a restore is started.
System action: None
919
ACO3004I ACO3011I
ACO3004I
Data Protection for SQL: restore type

restore of backup object object name to
database database name on server server
name completed successfully.
ACO3008I

a database restore completes successfully.
System action: None
ACO3005E

database database name on server server
name failed.

a database restore fails.

to the Tivoli Storage Manager Server activity log
indicating the end of a backup request.
System action: None
ACO3009I
System action: None

ACO3006I
Data Protection for SQL: Starting

backup for server server name.

indicating the start of a backup.
Data Protection for SQL: Backup of

server servername is complete. Total SQL
backups selected: number selected Total
SQL backups attempted: number
attempted Total SQL backups completed:
number completed Total SQL backups
excluded: number excluded Total SQL
backups inactivated: number inactivated
Throughput rate: rate Kb/Sec Total bytes
time: time Secs

server server name canceled by user.

indicating that a backup request was canceled by the
user.
System action: None
System action: None

ACO3007I
Data Protection for SQL: Backup of

server servername is complete. Total SQL
backups selected: number selected Total
SQL backups attempted: number
attempted Total SQL backups completed:
number completed Total SQL backups
excluded: number excluded Throughput
rate: rate Kb/Sec Total bytes transferred:
bytes Elapsed processing time: time Secs

indicating the end of a backup request.
System action: None
ACO3010I
Data Protection for SQL: Starting restore

for server servername.

indicating the start of a restore.
System action: None
ACO3011I
Data Protection for SQL: Restore from

server server name to server server name is
complete. Total database backups
inspected: number inspected Total
database backups requested for restore:
number requested Total database backups
restored: number restored Total database
skipped: number skipped Throughput rate:
rate Kb/Sec Total bytes transferred: bytes
Elapsed processing time: time Secs

indicating the end of a restore.
System action: None
920
ACO3012I ACO5057I
ACO3012I

database database name from server server
name canceled by user.

indicating that a backup request was canceled by the
user.
ACO5051I

Explanation: The file specififed in the /configfile

parameter cannot be found.
User response: Ensure the correct file name is
specified.
System action: None

ACO3013I
Data Protection for SQL: Starting

Inactivate processing for backup objects
from server servername

an inactivate process begins.
ACO5052E

requested configuration option.

configuration file.
User response: View any other messages that were
displayed. After reviewing the messages and
performing necessary actions, run the command again.
System action: None

ACO3014I
Data Protection for SQL: Inactivate

processing complete Total database
backups inspected: number inspected Total
database backups requested for
inactivation: number requested Total
database backups inactivated: number
inactivated Total database skipped:
number skipped Elapsed processing time:
time Secs

to the Tivoli Storage Manager Server activity log to
indicate the end of an inactivate command.
ACO5053E
The value for the option option is not

valid. See the TDPSQLC Help Set
output or the Users Guide for valid Set
command parameters.
Explanation: The configuration option being set is not

valid.
User response: Run TDPSQLC Help Set or refer to
the Users Guide for valid Set command parameters.
ACO5054I
The configuration option was set

successfully.
System action: None
Explanation: The configuration option specified on the

Set command was set successfully.
User response: None

User response: None
ACO3015I
Data Protection for SQL: Inactivating

backup type backup backup object.
ACO5056I


an inactivation of a backup object is started.

unsuccessful.
System action: None
User response: The log file may not exist. If the log
file exists, view the log for indications of possible
problems.
ACO5050I
A new configuration file was created.
Explanation: The file specified in the /configfile

parameter does not exist. A new file was created.
ACO5057I
The logfile log file was pruned

successfully.
Explanation: The log file mentioned pruned

successfully.
921
ACO5058W ACO5097I
ACO5058W
The logfile name is greater than the

maximum allowed. Processing will
continue using a logfile name of logfile
in the current directory.
Explanation: The logfile name entered was not fully

qualified. When the fully qualified log file name was
created, it was longer than the possible length of a log
file.
System action: Processing continues by creating and
using a log file in the current directory.
User response: Consider updating the log file name
using a fully qualified path.
ACO5059W

writing. There will be no logging of
events.
Explanation: The log mentioned could not be opened

for appends. Therefore, no logging is performed.
System action: Processing continues without logging.
be opened. The log file may refer to a non-existent
drive or partition, or the log file is marked read-only.
ACO5060E

occurred.
Explanation: A Tivoli Storage Manager API error has

occurred.
ACO5064W
Explanation: The log mentioned could not be opened

for appends. Therefore, no logging or pruning is
performed.
be opened. The log file may refer to a non-existent
drive or partition, or the log file is marked read-only.
ACO5065E

User response: Issue the command and either specify
the /sqluser value which matches the registry entry or
specify the desired values for both the /sqluser and
/sqlpassword options on the command.
ACO5091E

A Microsoft SQL API error has occurred.
Explanation: A Microsoft SQL API error occurred.

ACO5063I

pruning.

pruned.
pruned at a later date. If the log file is currently too
large, decrease the number of days the log entries are
retained.
922
The value specified for the /SQLUSer

option does not match the registry entry.
Explanation: A Backup, Restore or Query Sql

command was issued with both the
/SQLAUTHentication=SQLUserid and the /SQLUSer
option specified. An attempt was made to obtain the
sqlpassword value from the registry but the user ID in
the registry does not match the user ID specified with
the /sqluser option.
ACO5061E
The logfile_name log file could not be

opened for writing. The log was not
pruned and there will be no logging of
events.

have a stored password, use the
-TSMPassword=xxx option to set and
Explanation: The PASSWORDACCESS option is set to

generate in the client options file. However, no
password is stored. An initial password needs to be
stored.
-TSMPassword option. Any subsequent commands
should now complete without specifying a password.
ACO5097I
Data Protection for SQL is not

configured for VSS operations.
Explanation: Data Protection for SQL has not been

configured to perform VSS operations.
there must be a valid Tivoli Storage Manager Advanced
Copy Services license installed and the Data Protection
for SQL LOCALDSMAGENTNODE preference must be
ACO5098E ACO5170E
set correctly. Refer to the Data Protection for SQL
Users Guide for details on configuring the client for
VSS operations.
ACO5098E
Error obtaining VSS information from

Local DSMAgent Node:
localdsmagentnode.
Explanation: Data Protection for SQL attempted to

obtain VSS information through the specified
LOCALDSMAGENTNODE but failed. The error
message encountered is also displayed.
ACO5127E

SQL does not support OFFLOAD with
the specified backup destination.

with an unsupported backup destination. Data
Protection for SQL only supports offload with a backup
destination of TSM.
User response: Retry the VSS offloaded backup
operation specifying a backup destination of TSM.
System action: VSS information is not displayed.

User response: Refer to the error message displayed
along with this message.
ACO5124E

SQL only supports VSS backup type of
FULL.

the VSS backup request. Data Protection for SQL
supports backup types of FULL when using the VSS
backup method.
ACO5128E
Explanation: There was a failure when Data Protection

for SQL performed the VSS operation.
User response: Verify that the Client Acceptor
ACO5129E

ACO5125E

SQL does not support OFFLOAD with
the Legacy backup method.

when using the Legacy backup method. Data
Protection for SQL does not support offload with the
Legacy backup method. Data Protection for SQL
supports offload with the VSS backup method only.
specifying the offload option or by specifying the VSS
backup method.
ACO5126E

SQL only supports Legacy backups with
Explanation: An invalid backup destination was

specified with the Legacy backup method. Data
Protection for SQL only supports a backup destination
of TSM when using the Legacy backup method.

returncode.
Data Protection for SQL is unable to run

VSS operations. A valid VSS license file
(acssql.lic) could not be located.
Explanation: In order to perform VSS operations, Data

Protection for SQL a valid and that the Tivoli Storage
Manager for Advanced Copy Services - MS Exchange
VSS Integration Module is installed. If the Tivoli
Storage Manager for Advanced Copy Services - MS
Exchange VSS Integration Module is installed, there
will be a license file, acsexc.lic, in the Data Protection
for SQL installation directory.
User response: Verify that the prerequisites identified
above are met and retry the operation. If the error
ACO5170E
Missing, blank, or invalid Local

DSMAGENT Node Name is not
allowed.
Explanation: In order to run VSS operations, Data

Protection for SQL verifies that the Local DSMAGENT
Node Name is specified and valid. This error indicates
that the Local DSMAGENT Node Name is missing,
blank, or invalid.
User response: Set the Local DSMAGENT Node
Name to a valid value and retry the operation.
923
ACO5171E ACO5402E
ACO5171E

SQL only supports restoring VSS
backup types of FULL and COPY.
ACO5188E
BOTH may not be specified for

/BACKUPDESTINATION, only TSM or
LOCAL are valid.

the VSS restore request. Data Protection for SQL
supports restoring backups of type FULL and COPY.
Explanation: The restore command only allows

specifying backup destinations of TSM or LOCAL for
identifying database(s) to restore.


TSM or LOCAL with /BACKUPDESTINATION
parameters.
ACO5177E

dsmagentnode.

ACO5204E
Explanation: A request was made to backup SQL

database(s) which doesnt exist or isnt available.
User response: Ensure that all of the databases exist
and are available and restart the backup.
ACO5400E
ACO5186E
The VSS writer didnt return any

selectable backup components for the
specified database(s). Ensure that the
SQL Server VSS writer service has been
started.
Explanation: The SQL Server VSS writer service didnt

return any selectable backup components for the
specified database(s).
System action: Backup fails, processing ends.
User response: Ensure that the SQL Server VSS writer
service has been started and that service start type is
set to automatic.
ACO5187E
Multiple backup objects with

conflicting backup desitinations were
found for one or more of the specified
database(s). The /OBJECT and/or
/BACKUPDESTINATION options
should be used to restore a specific
database.
Explanation: The backup object specified for the VSS

restore operation was not specific enough to be unique.
More information is required in order to restore the
correct backup object.
the /OBJECT= and /BACKUPDESTINATION
parameters.
One or more of the specified databases

do not exist or are unavailable for
backup.
The Virtual Device Interface is not

registered with the Common Object
Model.
Explanation: The virtual device interface could not be

created because it is not registered with the common
object model. The SQL server may not be installed
properly.
User response: Verify that the SQL server is installed
properly and retry the operation. Contact your service
representative if the error persists.
ACO5401E
The Virtual Device Interface could not

be created.
Explanation: The virtual device interface could not be

created. The SQL server virtual device interface log or
User response: If the SQL server messages do not
resolve the problem, retry the operation. Contact your
ACO5402E
The Virtual Device Set could not be

created.
Explanation: The virtual device set could not be

created. The SQL server virtual device interface log or
924
ACO5403E ACO5424E
ACO5403E
The configuration of the Virtual Device

Set could not be obtained.
Explanation: The configuration of the virtual device

set could not be obtained. The SQL server virtual
device interface log, SQL server activity log, SQL server
error log, or Windows NT event log may contain more
information.
User response: If the SQL server messages do not help
resolve the problem retry the operation. If the error
ACO5407E
The SQL server aborted the operation.
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
log, or Windows NT event log may contain more
information.
ACO5420E
Explanation: A SQL API error has occurred.
ACO5404E
The Virtual Device Set could not open a

virtual device.
Explanation: The virtual device set could not open a

virtual device. The SQL server virtual device interface
log, SQL server activity log, SQL server error log, or
System action: Processing for this operation ends.

ACO5421E

ACO5405E
An unknown virtual device error has

been detected.
Explanation: A virtual device returned and unknown

return code.\n The SQL server virtual device interface
log, SQL server activity log, SQL server error log, or
Received the following from the MS

COM component: SQL message
Explanation: A SQL error has occurred.

ACO5422E
Received the following from the MS

SQL server: SQL message


ACO5406E
ACO5423E
The SQL server closed a virtual device

prematurely.
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
log, or Windows NT event log may contain more
information.
The following string is too long: string


ACO5424E
Could not connect to SQL server; SQL

server returned: SQL message

925
ACO5425E ACO5434E
ACO5425E
The SQL server is not running: SQL

message

User response: Start the SQL server and retry the
operation.
ACO5426E
The SQL log on does not have the

Sysadmin role: SQL message
Explanation: An attempt was made to logon to the

SQL server but the specified logon name does not have
the Sysadmin role.
User response: Try the operation again and specify
either a log on name with the Sysadmin role or change
the specified log on name to have the Sysadmin role.
ACO5427E
The SQL server version is less than 7.0:

SQL message
Explanation: An attempt was made to use Data

Protection for SQL Server V2 with a SQL server version
earlier than the version 7.0 level. This is not allowed.
ACO5430E
The SQL Server Name is blank or

NULL.
Explanation: In the query to obtain the SQL Server

Name, the system returned a blank name. A valid SQL
Server Name is necessary to continue the operation.
System action: Processing for the current operation
ends.
User response: Check the SQL Server Name by using
the select @@servername command from the SQL
Query Analyzer. If that returns NULL, use the
sp_addserver stored procedure to set the SQL Server
Name to the correct value. After setting the SQL Server
Name, retry the operation. Contact your service
representative if the error persists.
ACO5431E
Multiple dbnames are not allowed.
Explanation: An invalid RESTORE command was

issued. It is not valid to specify multiple database
names in the <dbname> parameter list when using the
/STANDBY, /RELOCATE, or /INTO options.
User response: Enter the command again with a valid
value in the positional parameter or option.

User response: Use the Data Protection for SQL V1
client with SQL server earlier than the version 7.0 level,
or retry the operation with a SQL server verison 7.0 or
later.
ACO5428E
The SQL server is not on the local

machine: SQL message
Explanation: An attempt was made to use the

application client specifying a SQL server that was not
on the local machine.
ACO5432E
Equal numbers of the /RELOCATE and

/TO options must be specified.
Explanation: Unequal numbers of the /RELOCATE

and /TO options were specified on a RESTORE
command.
User response: Re-enter the command specifying the
same number of /RELOCATE and /TO options.
ACO5433E

following parameters/options:
User response: Retry the operation on the machine

where the SQL server resides.
Explanation: This message displays the positional

parameters and/or options that were specified
incorrectly.
ACO5429E
Could not obtain an event from SQL

server: SQL message
User response: Re-enter the command specifying the

correct parameters and/or options.

ACO5434E
The following options cannot be

specified together:
Explanation: This message displays the conflicting

command options that were entered.
command options.
926
ACO5435E ACO5456W
ACO5435E
This command requires one of the

following options:
ACO5453E
Explanation: This message displays the options that

were missing from the command entered.
User response: Re-enter the command specifying one
of the command options required by the command.
ACO5436E
A failure occurred on stripe number

(stripe number), rc = return code
Explanation: A failure occurred on the numbered

stripe.
the problem.
ACO5450E
The specified number of stripes (number

of stripes) is invalid. Processing will
continue with the maximum number of
stripes (maximum number of stripes).
Explanation: An invalid number of stripes was

specified.
System action: Processing continues utilizing the
allowed maximum number of stripes.
User response: None
ACO5451E
A failure occurred on vdev (vdev name),

rc = return code
Explanation: A failure occurred on the named virtual

device.
User response: There should be other messages
displayed with this message. Refer to the other
messages to determine the problem.
ACO5452E
Unable to delete temporary object:

(filespace name) (high level qualifier) (low
level qualifier)
Explanation: When a backup fails, the DP agent

attempts to delete all temporary backup data objects
from the TSM server. This message indicates that the
specified temporary backup data object could not be
deleted from the TSM server. This error is usually
caused by the loss of all TSM server sessions.
User response: None. A backup of the database
should detect the temporary backup data object and
delete it from the TSM server.
The number of TSM sessions (number of

TSM sessions) is invalid for the specified
number of stripes (number of stripes).
Processing will continue with the
number of TSM sessions (number of TSM
sessions) as the number of stripes.
Explanation: An invalid number of TSM sessions was

detected for the specified number of stripes. This
message is caused by the circumvention of an internal
error.
System action: Processing continues utilizing the
number of TSM sessions as the number of stripes.
service representative if this error persists.
ACO5454E

allowed per TSM transaction (number of
objects allowed per TSM transaction) is
invalid for the specified number of
stripes (number of stripes). Processing will
continue with (new number of stripes)
stripes.
Explanation: The maximum number of objects

allowed per TSM transaction is invalid for the specified
number of stripes for at least one of the TSM sessions.
All TSM sessions must allow at least one more object
per TSM transaction than the number of stripes
System action: Processing continues utilizing the new
number of stripes.
User response: Reduce the number of stripes. You can
also update the TSM server to increase the maximum
number of logical files that a client can send to the
server in a single transaction (TxnGrpMax).
ACO5455E
The backup is corrupt and can not be

restored.
Explanation: The backup being restored is corrupt

because the data object or objects found do not
correspond to the metadata.
ACO5456W
The backup is corrupt and is not fully

restorable. Processing will continue.
Explanation: The backup being restored is corrupt

because the data object or objects found do not
correspond to the metadata. Depending on the restore
command and the backup type, a partial restore may
be possible.
927
ACO5457E ACO5616T
ACO5457E
An unknown SQL API error has

occurred.
Explanation: A SQL API error has occurred but the

associated error message could not be found. The SQL
server activity log, SQL server error log, or Windows
NT/2000 event log may contain more information.
resolve the problem, try the operation again. Contact
your service representative if the error persists.
ACO5458W
The TSM Server backup delete setting

for node (TSM server NODENAME) is set
to NO. It should be set to YES for
proper operation. Processing will
continue.
Explanation: The TSM Server setting that allows TSM

clients to delete their own backups is set to NO for the
specified NODENAME. This valuemust be set to YES
in order for cleanup operations to perform successfully.
A NO value means that unusable residual data may be
stored on the TSM Server.

service representative if this error persists.
ACO5501E
The Common Object Model (COM)

library failed to initialize.
Explanation: The unsuccessful call was

CoInitializeEx(NULL,COINIT_MULTITHREADED).
OLE32.dll or another COM dll may be missing,
down-level, or corrupted.
System action: Processing for this database ends.
User response: Verify your Windows NT (version 4 or
later) installation is complete and try the operation
again. Contact your service representative if this error
persists.
ACO5550I

filespec directorypathfilename and the

Tivoli Storage Manager server for the specified server
name.
User response: None

User response: Make sure the backup delete setting
for the specified NODENAME is set to YES on the TSM
Server. Your TSM Server administrator can change this
setting for your NODENAME. The setting can only be
changed on the TSM Server.
ACO5459W
Database object name excluded from

backup.
Explanation: The specified database was excluded

from backup by the /EXCLUDEDB setting.
System action: Database isnt backed up.
ACO5551I

Tivoli Storage Manager server matching the query
criteria for the specified server name.
User response: Specify a broader range of search
criteria when issuing this query.
ACO5552I

ACO5460E
Database object name doesnt exist or

isnt valid.
Explanation: The specified database doesnt exist or

isnt valid.
System action: Database isnt backed up.
User response: Make sure the specified database
exists.

criteria specified for server name
servername.
No matches were found for the criteria

specified.
Explanation: The SQL Server was searched for

databases that matched the specified criteria.
User response: Check the specified search criteria
(database name, group name, logical filename). Enter
the command again.
ACO5616T
Database cannot be backed up because

its name contains \ or : character(s).
The MultiByteToWideChar() function

failed.
Explanation: Databases whose names contain

directory or volume separator cannot be backed up or
restored.
Explanation: This is an internal error that indicates

corrupted storage.
System action: Database was excluded from backup.
ACO5500E
System action: Processing for this database ends.
928
ACO5617I ACO5718I
User response: Rename the database and restart
backup.
ACO5634E
ACO5617I
Explanation: The logical name specified during

relocation was not found in the database.
Database was excluded from backup

because database name contains \ or :
character(s).
Logical name was not found in the

database.
Explanation: Databases whose names contain

directory or volume separator cannot be backed up or
restored.
User response: Specify the correct logical name and

System action: Database was excluded from backup.
ACO5715E
User response: Rename the database and restart

backup.
ACO5629E
No Backups have been selected for

restore.
Explanation: The Restore button was pressed but

nothing was selected in the tree or list view.
Error writing option_name preference to

the configuration file.
Explanation: Could not write the specified preference

to the configuration file.
System action: Preferences processing ends.
User response: Make sure you have a valid
configuration file, then try to update the preference
again.

User response: Make a selection in the tree or list
view and press the Restore button again.
ACO5630E
Backups from multiple Server instances

have been selected for restore.
Explanation: The Restore button was pressed and the

user has selected backups from multiple server
instances.
User response: Make a selection in the tree for
backups belonging to the same server instance only
ACO5631E
Restoring full Legacy backups and full

VSS backups in the same restore
operation is not supported. Retry the
restores in separate operations.
Explanation: At least one VSS backup object and one

Legacy backup object were selected for a restore in the
same operation. This is not supported.
User response: Retry the restores specifying the
Legacy backups and VSS backups in separate
operations.
ACO5633E
Database state does not allow log

backup with TRUNCATE=YES.
Explanation: Database status is not Normal. Log has

to be backed up with truncation turned off.
System action: The backup operation failed.
User response: Back up log with TRUNCATE=NO.
ACO5716W

Explanation: Errors were encountered during an

attempt to run setup for the Tivoli Storage Manager
API.
determine the problem. If this file does not exist, the
TSM API may not be installed properly. If the TSM API
is not installed properly, install the TSM API and run
the command again.
ACO5717E
Unable to log on to the SQL server.
Explanation: An error occurred while trying to log on

to the SQL server.
System action: If running the client from the
command line, the client ends. If running the client
from the GUI, a prompt is displayed to enter the SQL
user ID and password, or to choose Windows
authentication.
User response: Make sure the SQL server is running.
ACO5718I
When the view is refreshed all

selections will be lost and an attempt
will be made to expand the new tree to
the currently highlighted item. Do you
want to continue?
Explanation: The refresh toolbar button or pulldown

menu item has been selected.
929
ACO5719I ACO5805W
ACO5784E
ACO5719I
Explanation: A log must be selected before setting

point in time parameters.
There are currently no backups on TSM.
A log must be selected to use point in

time.
Explanation: The SQL server name expansion button

was pressed on the Inactivate page.
User response: Select at least one log for restore

before specifying a point in time.
User response: Either nothing was backed up to a

TSM server or all active backups were inactivated.
ACO5720I
No databases have been selected for

backup.
Explanation: The Backup button was pressed on the

GUI but no databases were selected from the tree or
list.
User response: Select a database and press the Backup
button again.
ACO5721I
No backups have been selected for

restore.
Explanation: The restore button was pressed on the

GUI but no backup objects were selected from the tree
or list.
User response: Select a backup object and press the
Restore button again.
ACO5722I
No backups have been selected for

inactivate.
Explanation: The Inactivate button was pressed on the

GUI but no backup objects were selected from the tree
or list.
User response: Select a backup object and press the
Inactivate button again.
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.
930
ACO5804I
Unable to get information. If data is

backed up to tape check the Wait for
Tape Mounts for File Information
checkbox.

System action: None
User response: Try checking the box specified in the
message.
ACO5805W
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 9. Data Protection for Oracle Version 5.4.1

(ANU0000ANU9999)
The messages in this section are for the Data Protection for Oracle Version 5.4.1.
The messages begin with the prefix ANU and are listed in numerical order.
ANU0003S

occurred.

occurred.
ANU0004E

a return code.
ANU0005E


ANU0053E

opened.

failed.

failed.
ANU0056E

in a valid format.

ANU0057E

string text.

correct level.
ANU0058E



product.
ANU0054E
ANU0100E
Incomplete command:




ANU0101E
ANU0055E
Invalid argument:
931
ANU0102E ANU0152I
ANU0133W Could not locate installation directory.



ANU0102E

command entered.
Invalid command:

ANU0103E

command:

command options.
ANU0104E
Invalid option:

that was detected.
command options.
ANU0105E
Missing argument:

ANU0132W Tracing could not be started. Processing
will continue.

up correctly.
ANU0134W Could not locate log directory.
command entered.
up correctly.
ANU0150I

Protection for Oracle application client end by entering
ctrl-C.
User response: None
ANU0151E

request.


beginning.


command entered.
ANU0152I



User response: None
932
ANU0153I ANU0200E
ANU0153I

in function

User response: None
ANU0154E
The Data Protection for Oracle

version of the Tivoli Storage Manager
API you have installed. Please install
version version.release.level or greater.

Oracle application client.
ANU0160E

password.

ANU0161E




copy is distributed with the Data Protection for Oracle
application client.
ANU0162E


ANU0155E
The Data Protection for Oracle

release of Tivoli Storage Manager API
you have installed. Please install release

Oracle application client.
copy is distributed with the Data Protection for Oracle
application client.
ANU0156E

Manager API.

not be loaded.
is correctly installed. Run the Data Protection for Oracle
application client with the /TRACEFLAGS=API
/TRACEFILE=filename options and view the tracefile
to determine why it could not be loaded. Another
possible cause is that the TSMAPI.DLL does not exist in
the system directory. Re-install the Tivoli Storage
Manager API, if this is the case.

ANU0163E

fully-qualified.

ANU0167E

long.

attempt failed.
User response: None
ANU0200E

reading.

User response: None
933
ANU0201E ANU0213E
ANU0201E

writing.
ANU0208E



User response: None
User response: None
ANU0202E
ANU0209E

User response: None

(filename2) failed.

User response: None
ANU0203E

User response: None
ANU0210E


ANU0204E

User response: None

ANU0211E

User response: None
ANU0205E

obtained.



User response: None
ANU0212E
User response: None

ANU0206E

User response: None
ANU0207E

User response: None

name is too long.

attempt failed.
User response: None
ANU0213E


for Oracle application client.
934
ANU0214E ANU0259E
ANU0214E


ANU0219E


valid.

ANU0215E

destination.

destinations.
ANU0216E
ANU0256E




ANU0257E

User response: None

ANU0217E
ANU0258E

name is invalid.

Processing ends.


a valid password.


valid password.
ANU0218E
ANU0259E


valid.

changed.

935
ANU0260I ANU357E
ANU0260I

ANU0266E

Manager HTML books.

User response: None

ANU0261I
ANU0267E

named servername.



new password.
User response: None

verify password.
ANU0263E


failed.
ANU0264I


ANU0300E

valid restore type.
ANU0301E

valid backup type.
ANU351E



ANU0265E

ANU357E

file-name.

936
ANU366E ANU495E
ANU366E

file-name.

space).
ANU385E


ANU367E

Tracing disabled.

ANU476E

error.

operation.

continues.
ANU487E


link.
ANU368E

ANU383E


link.
tracefile option.
ANU384E




ANU488E


ANU495E


given log location.
937
ANU496I ANU519E
ANU496I

minutes.

and old data saved.
ANU497I

minutes.

ANU498I

ANU515E

ANU516I

nodename.

operation.
representative.


the Data Protection for Oracle processes or programs.
The following events can be recevied:
was stopped.
ANU517I

Explanation: None.
ANU518E

ANU501E

dsmagentnode.

LOCAL).

ANU519E

returncode.

938
ANU520E ANU2507E
ANU520E

properly.

representative.
ANU521E



ANU2501E
Oracle passed a null file name
Explanation: Null file name passed by Oracle.

procedure.
ANU2502E
Explanation: Wrong data block size.

procedure.
ANU2503E
Backup object filespacehlll already exists

on TSM Server.
Explanation: The object has previously been backed

up to the TSM Server.
System action: Data Protection for Oracle returns to
the calling procedure.
User response: If backing up an object, make sure
Oracle is generating a unique backup object name.
ANU2504E
Dissimilar Oracle handle

procedure.
ANU2505I
End of file reached

procedure.
ANU522E
DIAG:

ANU2500E
Oracle passed an invalid mode

procedure.
ANU2506E
Wrong Read State

procedure.
User response: Contact TSM support.
ANU2507E

API.
939
ANU2508E ANU2519E
procedure.
User response: Check compile time API level, obtain
same or higher level of API library.
ANU2508E
Wrong write state

procedure.
User response: Contact TSM support.
ANU2509E
Invalid flag passed
Explanation: Oracle passed an invalid flag.

procedure.
ANU2514E
Could not write license file: license file
Explanation: The license file could not be written.

procedure.
User response: Check that the license file permissions
are correct.
ANU2515E
Invalid data format in license file: license

file
Explanation: The license file data format is invalid.

procedure.
User response: Reinstall the license that came with
Data Protection for Oracle.
ANU2516E
Bad checksum of license file: license file
Explanation: The license file has a bad checksum.

ANU2510E
The Caller must be a root user

password
procedure.

procedure.
ANU2517E
ANU2511E
Explanation: The Try and Buy Evaluation period is

over.
Reduce the number of copies to that

specified in RMAN
Try and Buy Evaluation period is over

for license file: license file
Explanation: The duplex copy feature has reached

maximum allowed copies.

procedure.

procedure.
User response: Purchase the product or discontinue

use.
User response: Reduce the number of backup copies

to that allowed by RMAN.
ANU2518E
ANU2512E
Could not open license file: license file
Explanation: The license file could not be opened.

procedure.
User response: Check that the license file exists with
the correct permissions.
ANU2513E
Could not read license file: license file
License file: license file not valid for this

application
Explanation: The license file is not intended for this

application.
procedure.
ANU2519E
Could not read password
Explanation: The license file could not be read.
Explanation: There is an invalid password or the

password file cannot be not found.

procedure.

procedure.
User response: Check that the license file permissions

are correct.
User response: Check that password file exists and is

valid.
940
ANU2521E ANU2536I
ANU2521E
Error opening file name. Check

permissions.
Explanation: A directory could not be created.

procedure.
User response: Check that permissions allow the
creation of directories.
workstation that has a screen with the minimum size.

ANU2531E
Could not create a temporary file name

for Data Protection for Oracle utility
Explanation: A temporary file name could not be

created by the Operating System call to tempnam().
procedure.
Explanation: There is not enough system memory to

complete the action.
User response: Check with the Operating System

Vendor for specific reasons why the function call to
tempnam() could fail. Take the necessary corrective
action and try operation again.

procedure.
ANU2532E
ANU2522E
No memory available
User response: Make more system resources available

by closing other applications, then try the action again.
ANU2523E
The Management Class does not match
Unknown Error - View the Data

Protection for Oracle error log
Explanation: There was an unknown error. View the

tdpoerror.log.
System action: None
Explanation: The management class for the query

object could not be found.
User response: None

procedure.
ANU2533E
SQLPLUS error
Explanation: The utility could not find SQLPLUS or

there was a scripting error.
ANU2525E

procedure.
Input date does not match expected date

format or range.
Explanation: The input date does not match the

expected date format or range.
procedure.
User response: Check that the format and length of
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
ANU2529E
User response: Check that SQLPLUS is installed and

located in your search path. Verify the password.
ANU2534E
Option file error.
Explanation: The option or option file name is invalid.

procedure.
User response: Check the tdpoerror.log file for an
explanation of the error.
To Date cannot occur before From Date
Explanation: The specified To Date occurs before From

Date.
System action: The system returns this error.
User response: Enter a valid To Date that occurs after
the From Date.
ANU2535I
File /fs/hl/ll = number bytes sent
Explanation: This is the total bytes sent to the server

for that file name
procedure.
User response: Check the TSM Server activity log.
ANU2530E
Screen size is too small to accurately

display the PICK window.

across and 10 lines down.
ANU2536I
File /fs/hl/ll = number bytes recieved
Explanation: This is the total bytes received from the

server for that backup file name.
System action: The operation was not completed.

procedure.
User response: Retry the operation using a
User response: Check the TSM Server activity log.

941
ANU2537E ANU2614E
ANU2537E
Error found while parsing options in

Data Protection for Oracle options file.
Explanation: There was an error found while parsing

the Data Protection for Oracle options file.
procedure.
User response: Check that the options and the options
file are valid.
ANU2538E
Error found while initializing tracing for

Explanation: Error found while initializing the Data

Protection for Oracle trace facility.
procedure.
ANU2539E
Function Name: Error - string pointer is

NULL.

procedure.
User response: Check to ensure that the file named in
the error exists in the path specified and that the file
named has read permissions. Take the necessary
corrective action and try operation again.
ANU2600E
There is no Registry entry for the TSM

API.
Explanation: The Windows Registry entry was not

found.
procedure.
User response: Check that the TSM API is installed
correctly.
ANU2601E
There is no Registry entry for the Data

Protection for Oracle install path.
Explanation: The Registry Entry for the Data

Protection for Oracle install path was not found.
Explanation: A NULL pointer was passed to Data

Protection for Oracle.

procedure.

procedure.
User response: Check that Data Protection for Oracle

was installed correctly.

ANU2602E
ANU2571E
Could not load the library: library Data

Protection for Oracle
Explanation: Library cannot be loaded.

procedure.
User response: Check that the library exists.
ANU2575E
An error was detected while attempting

to open the file filename for writing.
Explanation: The Data Protection for Oracle utility

failed to open the file named in the error message.
procedure.
User response: Check to ensure that the directory
exists or that the directory has write permission, and
that the disk is not full. Take the necessary corrective
action and try operation again.
ANU2576E
An error was detected while attempting

to open the file filename for reading.
Explanation: The Data Protection for Oracle utility

failed to open the temporary file named in the error
message.
942
The object Filespace NameHigh Level

NameLow Level Name was not found on
the TSM Server
Explanation: The object name was not found on the

TSM Server.
procedure.
User response: Check that the object name is correct
and that it exists on the TSM Server.
ANU2603E
The option Option Name in file Filename

is invalid.
Explanation: An incorrect option was passed into the

Data Protection for Oracle options file.
procedure.
User response: Verify that your options are correct in
the Data Protection for Oracle options file.
ANU2614E
Invalid sequence of function calls to

Data Protection for Oracle
Explanation: Data Protection for Oracle received a

function call from Oracle that is out of sequence.
System action: Data Protection for Oracle returns to
the calling procedure.
ANU2615E ANU2623I
User response: Contact Oracle or Data Protection for
Oracle support.
ANU2622E
ANU2615E
Explanation: An invalid parameter value was

specified at the command-line.
Options file filename not found.
Explanation: The option file name specified could not

be located.
procedure.
User response: Ensure that an option file exists in the
default path or that the user specified option file is
valid.

procedure.
User response: Check the Users Guide for correct
usage of option parameters and the possible values for
this command. Retry the command with valid option
values.
ANU2623I
ANU2616E
Empty parameter specified for option

option in options file filename.
Explanation: The option specified must have a

parameter supplied.
procedure.
User response: Ensure that a valid parameter for the
given option is entered and valid.
ANU2620E
One or more option parameters contain

invalid values.
No user input detected.
Explanation: Valid user input is required to fullfill the

parameter request.
System action: The operation gives the user 3
attempts before returning to the calling procedure.
User response: Check the Users Guide for correct
usage of the command and the possible values for this
command. Retry the command with valid values.
Attempting to create or modify Data

Protection for Oracle prompted
password as non-root user.
Explanation: According to the settings in your Data

Protection for Oracle options file you are attempting to
authenticate using passwordaccess=prompt as a
non-root user. Root access is needed to modify the Data
Protection for Oracle password file.
procedure.
User response: To create or modify the Data
Protection for Oracle password file, switch to the root
user and re-run the Data Protection for Oracle
password configuration utility.
ANU2621E
Attempting to create or modify Data

Protection for Oracle generated
password as root user.
Explanation: According to the settings in your Data

Protection for Oracle options file the TDPO_NODE is
not defined which indicates that you are attempting to
authenticate using passwordaccess=generate. As a root
user this is not allowed.
procedure.
User response: If you intend to use
passwordaccess=prompt method of authentication
please modify the Data Protection for Oracle and set
TDPO_NODE to a valid registered TSM node and
re-run the password configuration utility as root user.
943
944
Chapter 10. Shared Library Messages: Data Protection for

SAP (DB2 and Oracle)
Prefix BKI
In Version 5.5, BKI messages are generated by Data Protection for SAP for DB2 and
for Oracle. The same message can be generated by either of these components.
The messages begin with the prefix BKI and are listed in numerical order.
For each message, the following information is provided:
v Message number
v Severity code
The following letters give an indication of the severity of the action that
generated the message. The severity codes and their meanings are as follows:
E
W
I
Error
Warning
Information

Processing can continue, but problems may occur later.
v Explanation
v User Response
BKI0000E
Profile not specified.
Explanation: Cannot locate the profile.
for SAP 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) .
User response: Ensure that a profile is available.

(Oracle) Note that the BACKINT call must have the
following form: backint -p init<SID>.utl .
BKI0007E
BKI0004E
Explanation: Not all environment variables required

have been set. At least environment variables where
missing.
Function not defined.
Explanation: BRTOOLS, BRBACKUP, or BRARCHIVE

passed an invalid argument to DP for SAP.
User response: Ensure that you have the correct
version of BR*Tools installed. Valid functions are: -f
backup or -f restore or -f password or -f delete or -f inquire.
BKI0005I
Start of program at: time
Mode mode requires the environment

variable environment variables to be set.
User response: Set the missing environment variables.

BKI0008E
The environment variable name is not

set correctly. The current value is value.
Explanation: The value of the environment variable

name is wrong.
Explanation: DP for SAP received control from a

BR*Tools utility at the time denoted.
User response: Set name to an appropriate value.
BKI0020I
BKI0006E
Explanation: (Oracle) DP for SAP returned control to a

BR*Tools utility at the time denoted. (DB2) Program
tdppasswd ended at the time indicated.
Type for backup not defined [type].

Please use file or file_online.
End of program at: time
Explanation: DP for SAP expects as backup type

parameter only file or file_online.
User response: If you start DP for SAP manually to

do a backup, ensure that the type option (-t) receives
the correct arguments (file or file_online). If your DP
BKI0021I
Elapsed time: elapsedtime
945
Explanation: The time needed for the complete

backup was elapsedtime.
BKI0023I
Time: current_time
Done: saved_bytes (percent) of bytes
Estimated end time: end_time
Explanation: Finished saving a specific object at

current_time. The saved_bytes amount of the total
number of bytes have been saved. percent shows the
percentage. This call will be completed at the estimated
end_time.
BKI0024I
Return code is: return code
Explanation: 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 program. If the return code
is 2, at least one error message was issued.
User response: For return codes other than 0, check
the run log for warnings or error messages.
BKI0027I
Time: current_time
Objects: current_num of total_num
in process: file_name
MGMNT-CLASS: management_class
TSM Server: server name.
Explanation: DP for SAP started saving current_num

files at 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
Manager server server name, which stores them in the
Management Class management_class.
BKI0032E
User response: Read the system error description.

Please enter password for node nodename
on server server name
Explanation: The password for the node nodename on

the Tivoli Storage Manager server server name has to be
entered for storing it in the DP for SAP configuration
file.
User response: Enter the password for the
corresponding Tivoli Storage Manager server.
946
Please enter password for node nodename

on server server name again
Explanation: In order to avoid typing errors, you have

to enter the password twice.
User response: Enter the password again.
BKI0051I
Password successfully verified for node

nodename on server server name.
Explanation: The password for the node nodename on

the Tivoli Storage Manager server server name was
changed successfully.
BKI0052E
Password verification for node nodename

on server server name failed.
Explanation: The password you entered for the node

nodename on the Tivoli Storage Manager server server
name was wrong.
User response: Enter the password again. If this error
still exists, contact your Tivoli Storage Manager
administrator.
BKI0053I
Time: current_time
done: file_name with: bytes saved with
description object_desc.
Explanation: DP for SAP completed saving

current_num file at current_time. The total number of
files to be saved is total_num. The file file_name with the
size bytes is saved with the description object_desc.
BKI0054I
Error opening file file name: system error

description
Explanation: A system error occurred during opening

of the file file name. system error description will describe
the error in more detail.
BKI0049I
BKI0050I
Time: current_time
done: file_name with: bytes
restored with description object_desc.
Explanation: DP for SAP completed restoring of

current_num file at current_time. The total number of
files to be restored is total_num. The file file_name with
the size bytes is restored with the description
object_class.
BKI0055I
Object objectname with size saved with

description description.
Explanation: The object objectname was saved

successfully.
BKI0056I
Object objectname with size restored with

description description.
Explanation: The object objectname was restored

successfully.
BKI0057I
Time: current_time Object objectname with

size saved with description description.
Explanation: The object objectname was saved

successfully.
BKI0058I
Time: current_time Object objectname with

size restored with description description.
Explanation: The object objectname was restored

successfully.
BKI0063E
The UTL file file name is not valid.
Explanation: Unable to read the input file file name

correctly.
User response: Check the path and name of the
profile (UTL file) and the appropriate file access
permission.
BKI0064E
The option option is unknown.
Explanation: An option is invalid or unknown.

User response: Check the specified option(s) and try
again.
BKI0065E
The argument is missing for option

option.
Explanation: Every option requires an argument.
User response: Insert the missing argument and try

again.
BKI0059E
BKI0101I
You have to set the environment

variable DSMI_CONFIG to the full
filename of the Tivoli Storage Manager
client option file dsm.opt.
Explanation: Tivoli Storage Manager client option file

not found.
User response: Verify that the Tivoli Storage Manager
option file dsm.opt is pointed to by DSMI_CONFIG.
BKI0060E
The parameter parameter is not known.
Explanation: The command parameter parameter is

unknown.
User response: Check the specified command
parameter and try again.
BKI0061W
The output file file name is not valid.
Explanation: The specified output file file name could

not be created.
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
the file within the specified directory. The directory
must already exist. If the file already exists, rename the
old one.
BKI0062E
The input file file name is not valid.
Session session: Please enter cont to

continue or stop to cancel.
Explanation: If DP for SAP is running in unattended

mode (profile keyword BATCH), it terminates the
current run if operator intervention is required.
User response: Enter cont or stop.
BKI0102I
Your reply: reply.
Explanation: The reply you made is confirmed.

BKI0311E
Request canceled by user.
Explanation: (Oracle) BACKINT terminated at users

request. (DB2) Program terminated at users request.
User response: None
BKI0400I
TDP is waiting for BRBACKUP
Explanation: DP for SAP is waiting for BRBACKUP to

set a tablespace in the begin/end backup mode.
BKI0405I
TDP waited num_sec sec. for

BRBACKUP in util_file_online
communication.
Explanation: Unable to read the input file file name

correctly.
Explanation: DP for SAP waited num_sec seconds for

BRBACKUP to set a tablespace in begin/end backup
mode.
User response: Check the path and name of the input

file and the appropriate file access permission.
Chapter 10. Shared Library Messages: Data Protection for SAP (DB2 and Oracle)
947
BKI0410E
Cannot open or delete switch file file

name. Check permissions.
Explanation: If DP for SAP is not installed correctly

(as the root user on UNIX or Linux or administrator
group on Windows) then DP for SAP is not able to
open the necessary communication file to the SAP
system.
BKI0453W
This version of product will expire in

number days.
Explanation: This is a test version with a time limit. It

will expire in number days.
User response: Order a release version of the product
or contact your IBM/Tivoli Sales Representative before
the version expires.
User response: Check the file permission.

BKI0454I
BKI0411E
Maximum time waiting for BRBACKUP

expired.
Explanation: The SAP database utilities did not

respond within the expected time.
User response: Contact your SAP administrator.
BKI0412E
BRBACKUP wasnt able to switch

requested tablespace in BEGIN/END
BACKUP mode.
Explanation: DP for SAP could not continue the

backup, because BRBACKUP was not able to switch the
requested tablespace in BEGIN or END backup mode.
This is necessary for locking the tablespace.
BKI0413E
Error while requesting tablespace

switch.
Explanation: BRBACKUP could not switch tablespace

in BEGIN or END backup mode.
BKI0414E
Error while requesting tablespace

switch.
Explanation: BRBACKUP reported an error while

trying to switch a tablespace in BEGIN or END backup
mode.
BKI0450I
Version 2 restore: file
Explanation: A restore of data backed up with DP for

SAP version 2 was executed.
*** This copy is NOT FOR RESALE. ***
Explanation: This version is not for resale.

BKI0455E
License file file name does not exist.
Explanation: The license file agent.lic was not found

where expected.
User response: Make sure that the agent.lic file resides
in the same directory as the init<SID>.utl file.
BKI0456E
Unable to access license file file name.
Explanation: The license file could not be accessed.

User response: Make sure the access permissions
allow read/write access.
BKI0457E
License file file name contains invalid

data/checksum.
Explanation: The license file is invalid.

User response: Make sure you have the right agent.lic
file for the right platform installed. agent.lic files are
platform dependent.
BKI0458I
Fake-Mode is activated.
Explanation: This message signals that the current

operation is a simulated operation. Simulations can be
performed using the Administration Assistant.
BKI0459E
More than one mux file is found with

the same name detailed backup description.
Explanation: Two or more data sources with name

detailed backup description exist.
User response: Contact the product administrator.
BKI0452E
This version of product has expired.
Explanation: This is a test version that has expired.
BKI1000E
User response: Order a release version of the product

or contact your IBM/Tivoli Sales Representative.
Explanation: The statement statement in the DP for

SAP profile is unknown or incorrect.
Syntax error in line line: statement
User response: Correct the error and try again.
948
BKI1001E
Syntax error in file file name. Exiting

Program.
BKI1007E
The NODENAME must be less than

max_char characters.
Explanation: A syntax error has been detected in the

file file name and the action has been halted.
Explanation: You have used a NODENAME with

more than max_char characters.
User response: Correct the error(s) in the file file name

and try again.
User response: Use a shorter NODENAME.

BKI1008E
BKI1002E
BACKUPIDPREFIX must be
number_of_characters characters.
The MANAGEMENTCLASSNAME
must be less than max_char characters.
Explanation: The length of BACKUPIDPREFIX must

be number_of_characters characters.
Explanation: You have used a

MANAGEMENTCLASSNAME with more than
User response: Enter a BACKUPIDPREFIX with the

required length (e.g., SAP___, BKI___).
User response: Use a shorter

MANAGEMENTCLASSNAME.
BKI1003W
BKI1009W
Please set REDOLOG_COPIES to a

number between 1 and max_copies. Now
it is set to act_copies.
Explanation: DP for SAP currently supports 1 to 9

copies of offline (redo) log files.
User response: Adapt the REDOLOG_COPIES settings
in the DP for SAP profile.
BKI1004W
You should specify the

BACKUPIDPREFIX before the
TRACEFILE statement, so that the
BACKUPIDPREFIX can be used in the
tracefile name.
Explanation: The BACKUPIDPREFIX is used to build

the Name of the tracefile. Therefore,
BACKUPIDPREFIX must be specified before the
TRACEFILE statement.
User response: Define a 6-character
BACKUPIDPREFIX in the DP for SAP profile (e.g.,
SAP___, BKI___)
BKI1005W
The tracefile name trace_filename should

be absolute.
Please set MULTIPLEX to a number

between 1 and max_multiplex. Now it is
set to act_multiplex.
Explanation: You have set multiplexing to an

unsupported number. DP for SAP now uses
act_multiplex.
User response: Set multiplexing to a number between
1 and max_multiplex.
BKI1010W
The configfile name

configuration_filename should be absolute.
Explanation: None.
User response: Specify an absolute file name, for
example /oracle/C21/dbs/initC21.bki or
/db2/C21/dbs/initC21.bki
BKI1011W
The sortfile name sortfile_filename should

be absolute.
Explanation: None.
User response: Specify an absolute file name, for
example /oracle/C21/dbs/sortfile.
Explanation: None.
BKI1012E
User response: Specify an absolute tracefile name, for

example /oracle/C21/saptrace/tracefile or
/db2/C21/saptrace/tracefile .
Explanation: DP for SAP is unable to read the file

configuration_filename.
BKI1006E
The SERVERNAME must be less than

Explanation: You have used a SERVERNAME with

more than max_char characters.
User response: Use a shorter SERVERNAME.
Configfile not found or permission

denied: configuration_filename.
User response: This error could have various reasons,

try the following:
1. Check the path of the configuration file. The path
must be specified in the profile (parameter
CONFIG_FILE).
2. Make sure that the file access permissions are set
correctly.
949
BKI1013E
Profile not found or permissions denied:

profile_filename.
Explanation: DP for SAP is unable to open the profile

profile_filename.
User response: (Oracle) Ensure that the SAP backup
profile init<SID>.sap contains a valid entry
util_par_file for the DP for SAP profile. (DB2) Ensure
that the vendor environment file contains a valid entry
XINT_PROFILE. Furthermore, this file must be readable
by DP for SAP. For details see Installing Data
Protection for SAP in the Data Protection for SAP
Installation and Users Guide and Problem Resolution
During installation and Setup in the Data Protection for
SAP Installation and Users Guide.
BKI1016W
The trace file name file name could not

be opened for writing!
BKI1023W
Could not establish connection to log

server log server name.
Explanation: In the DP for SAP profile, log server log

server name is specified (keyword LOG_SERVER).
However, a connection to the server named could not
be established. No log records are sent to the log server.
User response:
v Check that the server name defined with keyword
LOG_SERVER is spelled correctly in the DP for SAP
profile.
v Make sure there is a SERVER section in the profile
for the log server defined with keyword
LOG_SERVER.
v Check the corresponding SERVER section and correct
any setup problems.
v Make sure that the log server named is available.
Explanation: The trace file could not be opened for

writing.
BKI1200E
User response: Ensure that you have specified a

correct path for the trace file.
Explanation: The program is unable to read or write a

data file (file name) of a tablespace being backed up or
restored.
BKI1019E
Failed to respond to a message received

from XINT.
Cannot read/write file: file name.
User response: Check the file access permission of the

affected file(s). Try again. If the problem still exists,
contact the product's administrator.
Explanation: This messages indicates an internal error.

User response: Contact IBM support.
BKI1020W
The compress info file file name should

be absolute !
Explanation: The argument for the parameter

COMPR_INFO in the profile is an relative filename.
User response: Always use an absolute filename as
argument for the parameter COMPR_INFO.
BKI1021E
component_name terminates the

connection due to a previous error.
Explanation: A serious error has occurred which

caused a shutdown of the communication channel
between the component_name process and this
application.
User response: Look for previous error messages to
detect the root cause of the problem.
BKI1022E
component_name terminates the

connection due to a previous error.
Explanation: See message BKI1021E.

User response: See message BKI1021E.
BKI1201E
There are no Tivoli Storage Manager

Servers available.
Explanation: DP for SAP cannot locate a Tivoli

Storage Manager server. This may be due to a
configuration problem or to a problem while trying to
connect to the Tivoli Storage Manager server. Most
probably, a preceding error message points to the cause
of the problem.
User response: Look for and respond to preceding
error messages. You may also want to check the DP for
SAP profile and the IBM Tivoli Storage Manager client
options and client system options files.
BKI1202E
You must specify either

MAX_SESSIONS, or all three specific
session options
(MAX_ARCH_SESSIONS,
MAX_BACK_SESSIONS, and
MAX_RESTORE_SESSIONS).
Explanation: Information on the number of Tivoli

Storage Manager client sessions to be established by DP
for SAP is missing from the profile.
User response: In the DP for SAP profile, either
specify a value for keyword MAX_SESSIONS, or
specify values for the three specific session parameters
(MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, and
MAX_RESTORE_SESSIONS).
Any of the specific options can be specified in
950
combination with MAX_SESSIONS. Then, it overrides

the value of MAX_SESSIONS for the specific function.
User response: If the problem persists check for and

respond to preceding error messages
BKI1203E
BKI1209E
Not enough sessions available (number

of sessions required and number of
sessions available).
Explanation: The sum of available sessions specified

in the various server statements (parameter SESSIONS)
does not cover the required number of sessions
(parameter MAX_SESSIONS).
User response: Change the values of the
corresponding parameters in the DP for SAP profile, so
that the condition mentioned in the explanation is
fulfilled.
BKI1205E
If you want num_redo

REDOLOGCOPIES on Tivoli Storage
Manager-Server servername, you should
give me at least num_mc different
Archive Management Classes.
Explanation: DP for SAP requires 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 or log file copies (parameter
REDOLOG_COPIES).
User response: Define at least as many different
Archive Management Classes as log file copies
requested.
Explanation: The object cannot be located.

User response: The backup integrity is affected.
Contact SAP or IBM support.
BKI1210E
If you want num_redo

REDOLOGCOPIES on Tivoli Storage
Manager Server server name, you should
give me at least num_mc different
Archive Management Classes.
Explanation: The message appears during a

BRBACKUP run. A BRARCHIVE run afterwards would
fail.
User response: Define at least as many different
Archive Management Classes as log file copies
requested.
BKI1207E
User response: Ensure that you have the correct

version of BR*Tools installed. For details, check with
the release notes (RELNOTE).
BKI1211E
There is something wrong with your

CONFIG_FILE file name.
Explanation: There is a problem with your DP for

SAP configuration file setup.
User response: Check the file permission and the file
name specified in the DP for SAP profile keyword
CONFIG_FILE.
The file file name was not found in the
manual sorting file.
Explanation: The file you want to back up was not

found in the manual sorting file.
User response: Check and correct the manual sorting
file so that it contains all the files you are backing up.
BKI1214E
TSM Error: error text
Explanation: The specified TSM error occurred.

User response: Check error text and correct the
problem. For further information you may want to
refer to IBM Tivoli Storage Manager Messages SC32-9090
Directory backup not supported
Explanation: This option is not yet available.

User response: Wait for a future release of DP for SAP,
which supports this option.
BKI1208W
Input file not found or not accessible file

name.
Explanation: DP for SAP cannot locate the temporary

file named. This file contains the list of Oracle objects
to be backed up or restored. It is passed to DP for SAP
by one of the BR*Tools utilities.
BKI1212W
BKI1206W
Object not found or not accessible

objectname.
The object file name will be retried

[retry_num]
BKI1215I
Average transmission rate was number

GB/h (number MB/sec).
Explanation: The average transmission rate is

displayed.
Explanation: An error occurred while processing

object file_name. DP for SAP is repeating the action
according to the number of retries specified in the
profile. retry_num is the current retry count.
951
BKI1216E
There are no BRBACKUPMGTCLASSES

available.
Explanation: The BRBACKUPMGTCLASSES you have

specified in your init<SID>.utl file are not correct.
in the DP for SAP configfile. Each time your password

expires you have to repeat the last step.
BKI1229E
User response: Check the management classes on the

TSM server and specify correct ones.
BKI1217E
There are no
BRARCHIVEMGTCLASSES available.
Explanation: The BRARCHIVEMGTCLASSES you

have specified in your init<SID>.utl file are not correct.
User response: Check the management classes on the
TSM server and specify correct ones.
BKI1222E
Version mismatch error. Check setup

(version_1:version_2).
Value for parameter BUFFSIZE (actual

cur_number, maximum max_number) is
too large for BUFFCOPY mode
PREVENT.
Explanation: To utilize the BUFFCOPY mode

PREVENT the value for the parameter BUFFSIZE must
not be larger than max_number.
User response: In the DP for SAP profile, specify a
BUFFSIZE less or equal to max_number if you need to
prevent copying buffers when passing data between
Tivoli Storage Manager components. If you need large
buffers you can set option BUFFCOPY to SIMPLE or
AUTO. As a consequence, buffers are copied when data
is passed between Tivoli Storage Manager components.
Explanation: Different components with inconsistent

versions are used.
BKI1230E
User response: Check your setup or contact IBM

support.
Explanation: The operation was terminated due to a

previous error. As a consequence, the file named could
not be processed. The cause of the error should be
found in an earlier message.
BKI1223W
A problem occurred during send of

performance data to Administration
Assistant .
Explanation: There was a problem sending the

performance data to the Administration Assistant over
the network.
User response: Check your setup or contact IBM
support.
BKI1227I
Average compression factor was number.
Explanation: The data transferred had been

compressed by the factor number.
User response: None
BKI1228W
Server server name can not be used with

password access method GENERATE in
this environment. The process is
running with user ID number but the
effective user ID is number.
Explanation: The user ID and the effective user ID of

the process are different. In order to utilize the
password access method GENERATE the IDs must be
equal.
User response: Change the value for the parameter
PASSWORDACCESS in the file dsm.sys (UNIX and
Linux) or servername.opt (Windows) from generate to
prompt. Reset the password for this node at the Tivoli
Storage Manager server and run (for Oracle) backint
-f password or (for DB2) backom -c password . This
prompts you for the password and stores it encrypted
952
The following file was not processed:

path.
User response: Check for and respond to preceding

error messages.
BKI1505E
Operation aborted because a different

operation by this database client is
already running.
Explanation: Different concurrent operations of the

same type were started for the same database. This is
not supported. The current operation is aborted.
This message is also issued when a cooperative
operation of two or more participating partitions was
started, but the profile settings used for the various
partitions do not match.
User response: Wait until the currently running
operation has ended and try again. Make sure that
multiple operations are not started concurrently for a
database.
If this is a cooperative operation with two or more
participating partitions, check that the profile settings
of the various partitions (for example, DEVICE_TYPE,
MAX_VERSIONS, etc.) do not differ. If they do, fix the
profile settings, cancel the current operation, and start
the operation again. Also, investigate the possibility of
sharing the same profile among all partitions.
BKI1506E
Failed to execute command command.

Output follows:
Explanation: The system tried to execute the

command cited. During execution, an error occurred.
The output received from the command shell is listed

in the following.
User response: Determine the cause of the problem
from the command and the output listed in the
message, and resolve the problem.
BKI1507E
The process needs to run with root

authority.
BKI1513I
*****> Database client connected:

Instance instance, database database_name,
partition partition_number
Explanation: This message follows a message

BKI1511I and indicates the connection of one of the
database clients taking part in the operation. A
database client is an instance of the snapshot backup
library representing a single partition of the database.
Explanation: The current process requires root

authority.
User response: Start the process under an account

with root authority.
BKI1514I
BKI1508E
The service service_name has terminated

due to a previous error. Please check all
logs for additional information.
*****> Device client connected.
Explanation: This message follows a message

BKI1511I and indicates the connection of one of the
device clients taking part in the operation. A device
client is an instance of the device agent for the storage
device.
Explanation: The cited service is no longer available.
User response: Check the appropriate logs for the

cause of its termination.
BKI1515I
BKI1509E
Explanation: The clients log messages are written to

the indicated file.
Authentication failure. The password

specified does not qualify for accessing
component.
Explanation: To access the named component, a

password is required. However, the password provided
could not be verified.
User response: Make sure that the password files used
by the different components of the system match.
Client is logging to file_name.

BKI1517I
Deleting target data container defined

by container_description.
Explanation: The data in the container indicated is

removed.
BKI1510I
New connection received.
Explanation: The server received a new connection

request.
BKI1518E

BKI1511I
New type_of_operation operation started

for database instance instance, database
database_name.
Internal error: The system is trying to

use the same device agent, although the
synchronization mode is not
PARALLEL.
Explanation: The system has been told to use the

same device agent for multiple database clients, but the
database indicated serial synchronization mode. This
setup is not supported.
Explanation: A connection request resulted in the start

of a new operation of the type indicated.
User response: Contact your IBM support personnel.
BKI1519E
BKI1512E
An error occurred during shutdown:

Error information
Explanation: During shutdown of the component, a

problem occurred. The error information is given.
User response: Resolve the problem indicated by the
error information.
A failure occurred during initialization

of one or more of the nodes
participating in this operation. Please
check the logs for more information.
Explanation: Some problem occurred during the

initialization of a new operation. The problem may be
with any component required for this operation.
User response: Check the acsd log file for messages
BKI1515I to determine the log file names of the
participating agents. Check the log files of each
component for the cause of the problem.
953
BKI1520E
Volume volume_name is shared across

partitions. Volume sharing is not
allowed.
Explanation: At least two partitions own data residing

on the volume indicated. This setup is not supported.
User response: With the current disk layout of the
database, the requested function cannot be used. If you
want to use the function, change the disk layout of the
database so that each data volume is dedicated to a
partition.
BKI1521I
process again using a valid configuration file.

BKI1529E
The device device_type you entered is

not supported by the wizard.
Explanation: The device type represents a certain type

of storage device. While using the setup wizard, a
device type was entered that is not supported by the
current version of the wizard.
User response: Refer to your user documentation for a
list of the device types that are supported by default.
Specify one of the supported types.
Retaining number backups
Explanation: When enforcing profile parameter

MAX_VERSIONS, the indicated number of backups is
kept.
BKI1530E
Failed to launch the device agent for

device_type. Please consult your user
documentation to make sure that all
requirements for the specified device
are met.
The requested meta-information

(subject=description) is not available.
Explanation: The system was unable to launch the

appropriate device agent for the type indicated because
some of its requirements are not met.
Explanation: Some meta-information about each

backup is stored in the repository. An error occurred
when trying to retrieve part of this information.
User response: Refer to your user documentation and

make sure that the system is set up correctly for the
specified device type.
BKI1522E

BKI1534E
BKI1523W
Warning: The following containers were

reused without being explicitly released:
description
Explanation: The containers defined by the

description are used by the current backup. They were
used before by a different backup. This message is
expected in SAN environments where data containers
are usually kept until they are reused. In this case, this
message does not indicate a problem.
BKI1525E
The process service_name is in an

inconsistent state. Please check for
previous errors and restart the process
afterwards.
Explanation: The process indicated cannot continue

with inconsistent data.
User response: Check the logs for messages pointing
to the cause of the inconsistency. After resolving any
problems, restart the process.
BKI1526E
A configuration file (profile) must be

provided.
Unexpected version actual_version of the

repository located in path. Expected
version: supported_version
Explanation: The server located the repository in the

path indicated. However, the version of the repository
located on disk does not match the current version of
the server.
User response: Make sure to use the correct instance
of the server. Ensure that the path of the repository was
specified correctly. Refer to the release notes for a list of
possible incompatibilities.
BKI1535E
Unexpected characteristics
(bitwidth=number) of the repository
located at path. Expected bitwidth:
number
Explanation: The repository located in the path

indicated was saved to disk using a bit width different
from the bit width the server is using to load the
repository.
The repository located at path is not
valid.
Explanation: An operation was started without

providing a profile.
BKI1536E
User response: Check the user documentation on how

to provide the profile to the current process. Start the
Explanation: A repository could not be found at the

location indicated by path.
954
User response: Ensure that the path of the repository

was specified correctly. Do not edit any files in the
repository path.
BKI1537E
The repository located at path was

written with an incompatible protocol
(protocol_version). Expected protocol:
protocol_version
Explanation: The repository found at the location

indicated was written to disk using the protocol
version named. However, the server currently supports
the expected protocol version.
Explanation: During the automatic setup, entries for

this product were detected in /etc/inittab. This is an
indication that the product was not previously
uninstalled.
User response: Run the setup with option '-a disable'
and then start the installation process again. If the
entries in /etc/inittab should be retained, refer to your
user documentation for information on how to
complete the installation manually.
BKI1542E
User response: Ensure that the path of the repository

was specified correctly. Do not edit any files in the
repository path.
BKI1538E
Unexpected repository type. The path

path does not point to a repository of
type protocol_type.
Explanation: The repository located in the path

indicated was written to disk using a protocol different
from the protocol supported by the server process.
BKI1539E
Failed to uninstall because some of the

processes to be uninstalled are still
listed in /etc/inittab. Please re-run the
setup after stopping the component by
calling the setup script with option '-a
stop'.
Explanation: Before uninstalling the product, the

affected processes must be stopped. This is done by
running the setup script with the option -a stop,
which will remove the entries from /etc/inittab and
stop the processes.
User response: Refer to your user documentation for
information on the uninstall process. Run the setup
with the option -a stop and then continue
uninstalling.
BKI1543E
Root privileges required. Could not

change user ID to root.
The component is still referenced within

the /etc/inittab. In order to terminate the
component rerun the setup script with
option -a stop.
Explanation: The requested operation requires root

privileges. However, the process could not acquire
them.
Explanation: The setup utility detected that the

product is still active in the system. Apparently, its
entries in /etc/inittab are not yet removed.
User response: Make sure the appropriate privileges

(s-bit) are granted to the executable.
User response: Call this process again with the option

-f stop.
BKI1540E
BKI1544E
/etc/inittab entries are limited to 127

characters. Please consult your user
documentation for information on
manually completing the installation
procedure.
Explanation: The command line generated by the

setup function exceeds 127 characters. This situation
requires user intervention. The setup function did not
update /etc/inittab.
User response: Refer to your user documentation for
information on what entries to add to /etc/inittab.
BKI1541E
/etc/inittab was not updated because

some of the processes have apparently
already been added. Please re-run the
setup after calling the setup script with
option '-a disable' if you want to change
to a standard setup.
New entries cannot be added to

/etc/inittab because it already contains
too many entries starting with ac.
Please refer your user documentation for
a manual setup of this package.
Explanation: During setup, an unusually high number

of entries beginning with ac were detected in
/etc/inittab. /etc/inittab was not modified.
User response: Determine if these entries are
expected, or if they were added due to a problem. If
these entries are required, refer to your user
documentation for information on how to complete the
installation manually.
BKI1545E
IBM Tivoli Storage Manager for

Advanced Copy Services is currently
running.
Explanation: This failure happens during

(de)installation and indicates that not all TSM for ACS
955
components could be stopped.

User response: Check that no backup or restore is
currently running and retry the operation. If you have
customized the process of starting TSM for ACS, it
might be necessary to manually stop it by undoing
those customization steps.
BKI1546E
IBM Tivoli Storage Manager for

Advanced Copy Services was not
started.
Explanation: This failure happens during installation

and indicates that not all TSM for ACS components
could be started successfully.
User response: Check that all TSM for ACS
components have the appropriate access rights and
retry the operation. Contact the support function if the
operation continues to fail.
BKI1547E
Failed to remove the data associated

with the deleted backup backup_id.
Explanation: The backup named was deleted.

However, its data could not be removed from the
repository and from the storage device.
User response: Look for a previous message pointing
to the cause of the problem. Resolve any problems
indicated there. Once the cause of this problem is
resolved, the daemon will take care of the deleted
backups eventually.
BKI1548E
User response: Look for a previous message pointing

to the cause of the problem. Resolve any problems
indicated there. Once the cause of this problem is
resolved the daemon will take care of the deleted
backups eventually.
Failed to load component_name due to the
following reason: error_information.
Explanation: The system was unable to load the

named component of the product.
User response: Check the error information given in
the message. Resolve any problem indicated.
956
Unable to perform required operations

for container container_id for time_span.
Explanation: For the data container noted, an

operation to be performed by a background daemon
has been pending for the given time. This might
indicate a problem and may result in storage not being
released for an extended period.
User response: Make sure the background daemons
are running. Check their log files for messages pointing
to problems. Resolve any problems indicated.
BKI1553I
Component_name is logging to path.
Explanation: The file denoted is the log file of the

named component.
User response: If you need to check the log of the
indicated component, look for this message to identify
the log file to examine.
BKI1554W
The agent component_name terminated

with exit code number.
Explanation: The process denoted ended with the

given exit code.
User response: Check the agents log for any
messages pointing to a problem. Resolve any problem
indicated.
BKI1555I
Failed to monitor the data associated

with the deleted backup backup_id.
Explanation: A background daemon is supposed to

monitor the states of backups in order to determine if
data needs to be deleted from the storage device.
However, the monitor was not able to access the
appropriate data.
BKI1549E
BKI1550E
Profile successfully created. Performing

additional checks. Make sure to restart
all ACS components to reload the
profile.
Explanation: The setup wizard created a new profile.

The profile will be validated.
User response: Restart the ACS components after the
wizard ends, in order to activate the new settings.
BKI1556E
Some data of backup backup_id are

unavailable. It is impossible to restore
the data requested.
Explanation: The system detected that some of the

data originally contained in the backup is no longer
available. The occurrence of this message depends on
the type of storage device employed. For example, if an
earlier backup data was restored from an N-Series
device, some data of a later backup will be destroyed.
User response: The backup is no longer complete and
cannot be used for the requested operation. Try the
operation with a different backup.
BKI1557I
Device agent is logging to path.
BKI2010E
Error occurred processing FRONTEND
Explanation: The device agents log messages are

written to the file named.
Explanation: An error occurred during the frontend

processing.
User response: Check the frontend script/program

and the settings in the DP for SAP profile (keyword
FRONTEND) and try again.
BKI2000I
Successfully connected to
component_name on port portnumber.
Explanation: One of the DP for SAP modules

BACKINT or the backup library libtdp_r3 initiated a
successful connection to the background process
component_name on port portnumber.
BKI2001E
Socket error while connecting to

component_name: reason.
BKI2011E
Error occurred processing BACKEND.
Explanation: An error occurred during the backend

processing.
User response: Check the backend script/program
and the settings in the DP for SAP profile (keyword
BACKEND) and try again.
BKI2012E
Passwords do not match. Try again.
Explanation: The background process component_name

is not running.
Explanation: The first and second password you

entered do not match.
User response: Start component_name manually and try

again.
User response: Enter the password correctly.

BKI2013I
BKI2003I
File file_name, BID deleted.
Explanation: The file file_name with the backup ID

BID was deleted from the Tivoli Storage Manager.
BKI2007E
Explanation: The frontend program is executing.

BKI2014I
FRONTEND program finished.
Explanation: The frontend program is finished.
Unknown Port: port
Explanation: The port specified for communication

between component_name and BACKINT or the backup
library is unknown.
User response: Check the port value specified when
component_name was started. Additionally, check the
environment variable PROLE_PORT for the BACKINT
environment. These two values must match.

BKI2015I
Unable to connect to component_name.
Explanation: Internal error.
Starting BACKEND program.
Explanation: The backend program is executing.

BKI2016I
BKI2008E
Starting FRONTEND Program.
BACKEND program finished.
Explanation: The backend program is finished.


BKI2017I
BKI2009I
Deleting all versions with version

number <= version_number on server
server_name.
Explanation: All full database backups and their

corresponding log file backups will be deleted from
Tivoli Storage Manager storage, if their version number
is less than or equal to version_number.
Blocksize is set to num_bytes bytes.
Explanation: The operational blocksize is num_bytes

bytes.
BKI2022E
Unable to change mode of file file name:

description
Explanation: Unable to change mode of file file name.

description may contain the system error text.
User response: Check the description. If the error
957
BKI2024E
Error in connection to component_name.
Explanation: The connection to component_name

terminated unexpectedly. This message might be
displayed due to previous errors or after an unexpected
termination of the component_name process.
User response: Check for other error messages and
restart component_name if necessary. Try again. If the
problem persists, contact IBM support.
BKI2025E
Failed to respond to a message received

from component_name.
BKI4000W
The attributes of file file name cannot be

restored. Reason: errno (error_num)
error_desc.
Explanation: The file file name was restored

successfully but one or more file attributes (permission,
ownership, date/time) of the file file name cannot be
restored correctly.
User response: Check the error number error_num and
the error description error_desc to avoid this problem in
the future. An initial solution could be to set the
appropriate correct permission for the file file name
manually.
Explanation: This is an internal error

BKI2026E
Unexpected exception in handler: handler
Explanation: This is an internal error.

BKI2027I
Using TSM API version your API version

(compiled with compiled with version).
Explanation: Version information about the TSM-API.

User response: None
BKI2028W
Unable to terminate session session.
Explanation: This is an internal error during cleanup

that has no effect on the success of the service.
User response: None
BKI2029E
The requested buffer allocator cannot be

instantiated due to the following
incompatibility: expression.

BKI4001E
File file name cannot be created. Reason:

errno (error_num) error_desc.
Explanation: The file file name to be restored could not

be created/written. It is possible, that you do not have
the appropriate rights for writing the file file name to
the destination path.
the future. Furthermore, check the write permission of
the user who started the restore.
BKI4002E
Error during write of file file name.

Reason: errno (error_num) error_desc.
Explanation: An error occurs during the restore

process of the file file name.
the future.
BKI4005E
Error allocating memory block for file

file name. BLOCKSIZE may be too large.
Explanation: Unable to request new memory blocks

during the backup of file file name.
User response: Verify that you have set a valid value

for BLOCKSIZE. If you are not sure what value is
valid, comment it out so the default value is used.
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
another application, increase memory, or change the
configuration.
BKI2033E
BKI4007E
BKI2031E
A buffer allocator cannot

simultaneously satisfy all of the
following properties: list of properties
Cannot instantiate allocator of type

allocator type with the following
additional properties: list of properties

File filename cannot be read. Reason:

errno(errno number) errno text.
Explanation: Data could not be read due to some

system error. Check errno text for further information. If
this error recurs, this might indicate some hardware
problems.
958
BKI4008E
File filename cannot be opened. Reason:

errno(errno number) errno text.
Explanation: Could not open the file file name due to

some system specific problems.
BKI5005E
Tivoli Storage Manager Error:

error_message
Explanation: See BKI5001E.

User response: See BKI5001E.

BKI5006E
BKI4009E
Not enough space to write file file name.

Possible reasons: disk full or ulimit
exceeded.
Explanation: The system rejected a request to write

data into file file name. The storage media might not
have enough free space to keep the file or the system
rejected writing the file due to administrative resource
constraints such as ulimits.
BKI5000E

error_message

error_message

BKI5007E

error_message

BKI5008E

error_message
Explanation: During a connection of DP for SAP to

Tivoli Storage Manager server, a Tivoli Storage
Manager error error_message occurred.
User response: Use the Tivoli Storage Manager

Messages guide and correct the Tivoli Storage Manager
server error. Try your last action again.
BKI5009E
BKI5001E

error_message
Explanation: During a connection of DP for SAP to

Tivoli Storage Manager server, a Tivoli Storage
Manager error error_message occurred.
User response: Use the Tivoli Storage Manager
Messages guide and correct the Tivoli Storage Manager
server error. Try your last action again.
BKI5002E

error_message

error_message

BKI5010E

error_message

BKI5011E

error_message


BKI5003E

error_message
BKI5012E
Cannot open TSM API message text file.

Check if DSMI_DIR is set correctly.
Current value of DSMI_DIR is: value
Explanation: The TSM-API could not be initialized.
User response: Correct the value of the environment

variable DSMI_DIR.
BKI5004W

error_message

BKI5013E
Value for name is too long. Current

value: value
Explanation: The value of the environment variable

name has too many digits.
959
User response: Check if the variable is set correctly.

BKI5014E

error_message
BKI7049I
The default ProLE port will be used.
Explanation: The port for the internal communication

of DP for SAP is set during installation. The message
indicates that this port is being used.

BKI7051E
BKI5015W
Data description could not be restored,

because it was backed up with a newer
version (objInf=support information)
The environment variable

XINT_PROFILE is not set. It must be set
and contain the fully qualified path to
the *.utl file to be used.
Explanation: The TSM server hosts backups (i.e. data

description) which were made with a new version of
backint or backom, which ignores this data in further
processing.
Explanation: The way DP for SAP works is specified

in a profile. When called, DP for SAP looks for the
environment variable XINT_PROFILE which must
contain the fully qualified path to the profile.
User response: Upgrade the product.
User response: Check the environment for

XINT_PROFILE of the user who started DP for SAP.
BKI5016I
Time: current_time New TSM session

created: MGMNT-CLASS:
management_class, TSM-Server:
server_name, type: session_type.
Explanation: A new session to TSM server server_name

has been established at current_time. Data will be stored
in management class management_class.
BKI7053E
Service setup failed due to previous

error.
Explanation: Initialization of the product failed due to

previous errors.
User response: Check the product log file for further
detailed messages.

BKI7055E
BKI5017E
Internal Tivoli Storage Manager Error:

Transaction succeeded although it was
expected to fail.
Explanation: An internal Tivoli Storage Manager error

occurred.
User response: Retry the action. If the error occurs
again contact IBM support.
BKI5018E
The requested buffer has a size

(current_size bytes) that is smaller than
requested requested_size.
Explanation: The request for a new buffer returned

successful. The buffer, however, has not the requested
size.
User response: Check if the system is running low on
memory and retry the action. If the error occurs again
contact IBM support.
BKI7048I
The default port to connect to

server_name will be used.
Explanation: A server port for the connection to the

named server was not explicitly specified. Therefore,
the default port is used.
User response: Make sure the named server is
listening to the default port. In the case of connection
failures, specify the server port in the profile.
960
Service open failed due to previous

error in data mover.
Explanation: The command could not be started due

to previous errors.
detailed messages.
BKI7056E
Service open failed because configured

TSM server could not be accessed.
Explanation: The command could not be started

because the TSM server defined in the profile could not
be accessed.
detailed messages.
BKI7057E
Service open failed because all

configured sessions are currently in use.

because all configured sessions in the profile are
currently in use.
User response: With Oracle RMAN the number of
channels configured either in SAP profile or the RMAN
script must be less or equal to the maximum number of
allowed sessions (MAX_SESSIONS). If multiple servers
are used see: Multiple Servers in Data Protection for
SAP Installation and Users Guide for Oracle for further
details. Also check the DP for SAP log file for further
detailed messages.
BKI7058E
Service open failed because more than

one file was found with the same name.

because two or more files with the same name were
found.
detailed messages.
BKI7059E
Service open failed because a file was

not found.

because a file specified was not found.
detailed messages.
BKI7060I
product
<version>.<release>.<modification>
(<build number>) <build date> session:
process ID
Explanation: This message is to verify the version of

the shared library used for backup. On UNIX and
Linux systems this message will be written multiple
times into the log per backup depending on the RMAN
setup. On Windows, it is written just once.
User response: None, if the right version is used. If
the version within the log does not match the installed
version, see "RMAN Problem Resolution" in the Data
Protection for SAP Installation and User's Guide.
BKI7303W
Profiles for Data Protection for Snapshot

Devices are different.
backup: file name
restore: file name
Explanation: During backup the profile used by DP

for Snapshot Devices can be determined automatically.
For restore and inquire operations the profile for DP for
Snapshot Devices must be specified in the profile using
the parameter FCS_FILE. For restore DP for Snapshot
Devices must use the same profile as for backup.
BKI7305E
Error during call to Data Protection for

Snapshot Devices error message
Explanation: DP for Snapshot Devices could not

process the requested operation successfully. Processing
may not stop at this point. Depending on the type of
request (backup to both TSM and snapshot disks or to
snapshot disks only, restore of data which is available
in both modes) there are possibilities to recover from
this error and continue operation.
User response: Use the information from error message
and the output of DP for Snapshot Devices to
determine the cause of the problem and try again.
BKI7307W
Data Protection for Snapshot Devices

reported an error during a snapshot-type
operation. Do you want to continue to
backup to TSM?
Explanation: The backup was requested to be stored

on both the TSM server and the snapshot-type disks.
The snapshot operation has failed. Backup can continue
to save data on the TSM server only.
User response: Enter stop if you want to solve the
cause of this error and to try again. Enter cont if you
want to save this data on the TSM server only.
BKI7308E
DISK ONLY backup has failed.
Explanation: The current backup tried to store data on

snapshot-type disks only and did not finish
successfully.
User response: Check the output from DP for
Snapshot Devices prior to this error message to detect
the root cause of this error and try again.
BKI7309W

operation. Do you want to continue to
restore from TSM?
Explanation: The data you wanted to be restored is

located on the TSM server and on snapshot-type disks.
The snapshot operation has failed. The process can
continue to restore data from the TSM server.
User response: Correct the entry for the FCS_FILE

parameter in the profile (init<SID>.utl).
User response: Enter stop if you want to resolve the

cause of this error and to try again. Enter cont if you
want to restore from the TSM server.
BKI7304I
BKI7310W
Performing DISK ONLY backup
Explanation: The data for this backup is stored on

snapshot-type disks only and will not be sent to TSM.
User response: None

operation. CAUTION: Not all
filesystems are available. Do you want
to retry the operation?
Explanation: In contrast to message BKI7309W not all

file systems are mounted. In this case it is not possible
to continue the restore from the TSM server.
961
User response: Enter stop if you want to terminate

this restore process. Enter cont if you want to retry the
snapshot process.
BKI7311I
Profile used by DP for Snapshot

Devices:
Explanation: The message shows the name of the

profile used by DP for Snapshot Devices.
you want to continue or stop this operation. If you

want to wait until the snapshot process has finished
choose stop and the restore attempt will terminate. If
you choose continue an attempt is made to restore the
data from TSM if available.
BKI7316I
User response: None

BKI7312W
Profile for DP for Snapshot Devices not

specified in profile. For restore this
must be specified
Explanation: For restore and inquire operation in

conjunction with DP for Snapshot Devices this
parameter is mandatory. Without this parameter a
restore using DP for Snapshot Devices is not possible
and DP for SAP will continue to inquire/restore from
the TSM server only.
User response: Add the parameter FCS_FILE to the
DP for SAP profile
BKI7313W
Inquire results from DP for Snapshot

Devices are not available
Explanation: DP for SAP was unable to retrieve

information from DP for Snapshot Devices about
available backups on snapshot-type disks. This message
may be issued in consequence of message BKI7305E.
Snapshot Devices to determine the cause of the error
and try again.
BKI7314E
The data you want to restore is not

available on the TSM server.
Explanation: If a restore from snapshot-type disks can

not be finished successfully DP for SAP tries to
continue to restore data from the Tivoli Storage
Manager server. But if the backup was performed on
snapshot disks only, the data can not be found on the
TSM server.
Snapshot Devices prior to this error message to detect
the root cause of this error and try again.
BKI7315W
The copy process of the files you want

to restore is not yet finished. If you
continue the files will be restored from
TSM.
Explanation: The snapshot process running in the

background has not finished moving the files from the
source to the target volumes. A snapshot restore of
these volumes is currently not possible.
User response: After that message you will be asked if
962
The following backup types for the

BACKUPID Backup ID have been found:
- TSM
- Snapshot
Explanation: The backup for the backup ID Backup ID

was stored on the Tivoli Storage Manager as well as on
snapshot-type disks. For restore both data sources can
be used.
BKI7318E
The DP for Snapshot Devices profile file

name is not valid.
Explanation: The profile for DP for Snapshot Devices

specified in init<SID>.utl could not be accessed.
User response: Check the file name and the
permissions for this file and try again.
BKI7319I
Start TSM restore
Explanation: The restore uses data from Tivoli Storage

Manager.
User response: None
BKI7320I
Start restore from snapshot.
Explanation: The restore is using data from

snapshot-type disks.
User response: None
BKI7321E
The DP for Snapshot Devices profile file

name found in parameter FCS_FILE of
the DP SAP profile can not be used if
you need to restore this backup.
Explanation: In the DP for SAP profile the FCS_FILE

parameter is set, however the DP for Snapshot Devices
profile specified either
v is not a DP for Snapshot Devices profile
v does not point to the same DP for Snapshot Devices
configuration file which was used by the preceding
DP for Snapshot Devices splitint operation.
User response: You need
v
to correct the FCS_FILE parameter thus a valid DP

for Snapshot Devices profile is used, e.g. the file DP
for Snapshot Devices had used when running its
snapshot function in the preceding brbackup task
(see preceding message BKI7303W)
to ensure that if different DP for Snapshot Devices

SAP profiles are used, all use the same control file
(the value of the IDS_CONTROL_FILE parameter in

the DP for Snapshot Devices profile)
BKI7322E
Request for a partial restore or restore

from snapshot with brrestore -m all is
not supported. In case of brrestore
attempt rerun with -m full.
Explanation: DP for Snapshot Devices can only restore

the whole content of a backup and not only a subset of
a disk backup as requested. Most likely this is caused
by running brrestore with the option -m all.
User response: Restore complete backups only, e.g.
run brrestore with the option -m full.
BKI7323W
Request for a partial restore or restore

from snapshot with brrestore -m all is
not supported. If you want to restore the
backup:
- with a snapshot-type restore enter
stop and rerun brrestore with -m full
- from TSM enter cont
Explanation: This message has the same reason as

message BKI7322E, but in this case the data is also
available from the TSM server. So you may continue to
restore this data without the snapshot functionality
from TSM server.
User response: Enter stop if you want to try to
restore a different set of files. Enter cont if you want
to restore this data from TSM server.
BKI7324E
Restore of multiple backup IDs in one

run from a snapshot is not possible.
BKI8201E
Explanation: The current operation was a simulation

performed via the Administration Assistant. This
simulation was canceled since a production operation
(backup or restore) has been started.
User response: Check your backup schedule and run
simulations only when no other operations are
scheduled.
BKI8300I
User response: If the return information indicates a

problem, look for preceding error messages in the log
files. Otherwise, no response is required.
BKI8301E
Explanation: The command command name could not

be executed successfully.
User response: Check the explanation explanation and
the preceding output of the command execution to
detect the cause of the error.
BKI7536I
Execute command command name.
Explanation: The command command name is executed

by the application. This message is followed by the
output of the command executed.
Product_name: Exception caught in

function function_name. Error
information: error_information
Explanation: The named product implementing the

DB2 Advanced Copy Services API received an error in
the named API function. The error information is
shown.
User response: Analyze the error information to find
the cause of the problem. Resolve any problems
indicated.
BKI8302E
User response: Make sure the files you want to restore

belong to one single backup ID and try again.
Error executing command command name.
Reason: errno (error number) explanation.
Function_name returned with code

return_information.
Explanation: This message indicates that the named

API function ended with the specified return
information.
Explanation: The data requested for this restore

belongs to multiple backup IDs
BKI7535W
SIMULATION CANCELED BY
PRODUCTION OPERATION!!!
Product_name: Exception caught in

function function_name. More
information may be available in file
log_file_name. Error information:
error_information

shown.
User response: Analyze the error information and the
appropriate log files to find the cause of the problem.
Resolve any problems indicated.
BKI8305E
Invalid option option in options string:

options_string.
Explanation: An invalid option was found while

parsing the options string specified in the 'db2'
command.
User response: Correct the command and try again.
User response: None
963
BKI8306E
The keyword keyword is not allowed

multiple times within the profile.
Explanation: The keyword indicated was found more

than once in the profile. However, this keyword must
not be specified multiple times.
User response: Correct the profile.
BKI8307E
The parameter keyword must be specified

in the profile.
Explanation: A required keyword is missing in the

profile.
BKI8313E

DB2 Advanced Copy Services API detected an interface
problem in the named API function. An invalid value
was found in one of the API data structures.
BKI8314E

BKI8308E
Single argument required for parameter

keyword.
Explanation: The keyword indicated requires a single

value. However, two or more values are found in the
profile.
BKI8309E
Missing argument for parameter

keyword.
Explanation: In the profile, a value is missing for the

named parameter.
BKI8310E
The keyword keyword is not allowed.
Explanation: An invalid keyword was detected in the

profile.
BKI8311E
For parameter keyword, both server and

port must be specified.
Explanation: A value of the named parameter is

missing from the profile.
User response: As the value for the specified
parameter, specify both server and port.
BKI8312E
Error while parsing parameter keyword.

In order for value1 to be valid value2 is
required to be an existing directory.
Explanation: Value1 was found to be an invalid value

for the parameter named. For this specific parameter, a
file name can be specified whose path must already
exist in the system.
User response: Specify the name of a file in an
existing path.
964
Product_name: DB2 - TSM interface

problem in function function_name:
Invalid value of parameter: value

problem in function function_name: The
session is already in use by a different
operation.

problem in the named API function. Either the session
handle is used for various operations simultaneously,
or the functions are called in an order not supported by
the current version of the library.
BKI8315E
Function_name: The following object is

not under the control of product_name:
path

DB2 Advanced Copy Services API detected a problem
in the named API function: The path passed by the
database is not under the control of the product.
User response: Make sure the database to be backed
up meets the requirements for employing snapshot
backups.
BKI8316E

problem in function function_name:
Empty group list passed by DB2.

problem in the named API function: The database
passed a group list containing no elements.
BKI8317W
Product_name: Verification of
configuration requested by user. No
backup started.
Explanation: The user requested a verification of the

configuration. The backup flow continued without
errors up to the point where the snapshot would
actually be done and was then cancelled. The system is
ready for a snapshot backup, but no action beyond
verification has been taken so far.
BKI8318E

problem in function function_name: Not
enough space provided to write meta
data.

problem in the named API function: The buffer
provided by the database is too small to contain the
requested meta data.
BKI8319W
Error while deleting old versions. This

problem does not affect the new
backup. Error information:
error_information
Explanation: After a successful backup, the system

tries to remove older backups of the database according
to the value of profile parameter MAX_VERSIONS.
However, a problem occurred while trying to remove
expired backups. The new backup is not affected by
this problem.
User response: Check the appropriate log files in
order to determine the cause of the problem. Resolve
any problems indicated. In case the storage device runs
out of storage because outdated snapshot backups have
not been removed, delete these snapshot backups
manually.
BKI8320I
Deleting full backup backup_id

backup_key.

During this process, the full backup listed is removed.
BKI8321I
BKI8323E
Product_name: Problem occurred while

processing function_name. Please check
log file log_file_name for more
information. Error information:
error_information

shown.
User response: Analyze the error information and the
appropriate log files to find the cause of the problem.
Resolve any problems indicated.
BKI8324E
Product_name: Problem occurred while

processing function_name: Device agent
returned code return_information.

DB2 Advanced Copy Services API received an error
from the device agent in the named API function. The
device agents return information is given.
User response: Check the appropriate log files to find
the cause of the problem. Resolve any problems
indicated.
BKI8325E
Failed to determine hostname.
Explanation: The system was not able to determine

the host name of the machine.
User response: Make sure the system setup allows for
querying the hostname via system function
gethostname(). Ensure that the requirements for doing
snapshot backups are met.
BKI8326E
Failed to create log directory path.
Explanation: The log path indicated is not available in

the system and could also not be created.
Deleting partial backup backup_id for

node:host:partition_number.

During this process, the backup listed for the named
partition is removed.
User response: Check the properties of the path

indicated and make sure that its properties and the
properties of the parent directory are set accordingly.
Make sure all prerequisites for doing snapshot backups
are met.
BKI8327E
Invalid value specified for parameter

keyword: value
Explanation: A parameter value is not valid.

BKI8322E
Interface problem: Current database

partition number not listed in the
partition list.
Explanation: The partition list passed by the database

does not contain the named partition participating in
an operation.
User response: Correct the profile or the call as

appropriate.
BKI8328E
Product_name must be licensed to set

parameter keyword to a value of value.
Explanation: Selected functions are supported only

with a full TSM license.
965

appropriate. If you need the functionality requested,
obtain a full TSM license and install the license file.
BKI8330E
Parameter keyword requires YES, NO,

or number.
different from the value it had at backup time. This

value is given in the message.
User response: Correct the profile by setting the
indicated parameter to the value indicated in the
message.
Explanation: For the named parameter, only numeric

values, YES, and NO are accepted.
BKI8336E

appropriate.
Explanation: An option value is not valid.
BKI8331E
The parameter keyword1 is not allowed if

keyword2 is set to value.
Explanation: There is a dependency between

parameters keyword1 and keyword2. If the latter is set to
the value named, keyword1 must not be specified.
appropriate.
BKI8332E
Failed to parse parameter keyword. File

names in the profile need to be fully
qualified.
Explanation: As the value of the parameter indicated,

a fully qualified file name is expected. However, the
specified value is not a fully qualified path.
appropriate.
BKI8333E
In order to enable the parameter

keyword1 you need to set keyword2 to
value.
Explanation: There is a dependency between

parameters keyword1 and keyword2. If keyword1 is
specified, keyword2 must be given the specific value
indicated in the message.
appropriate.
BKI8334E
Profile section section_name is required

for function operation.
Explanation: The specified profile section is required

in order to perform the requested operation. However,
it is not included in the profile.
BKI8335E
Profile section section_name refers to a

value for keyword that differs from the
one used at backup time. Expected
value: value.
Explanation: The profile parameter named must not

change its value between backup and restore. However,
in the named profile section, the parameter has a value
966
Invalid value specified for option

keyword:value
User response: Correct the call.

BKI8337E
Error while parsing profile: Missing

section name.
Explanation: The profile is organized into named

sections. However, a section name was not found.
User response: Check that the profile name is
specified correctly or that the default profile is a valid
profile. Refer to your user documentation for the syntax
of the profile or use the profile wizard to create a new
profile.
BKI8338E
Error while parsing profile: Section

section_name is not allowed to be nested.
Explanation: In the profile, the named section starts

before the previous section ends. However, the section
in question cannot be nested.
BKI8339E
Error while parsing profile: Profile

section section_name is not valid.
Explanation: An invalid section name was found in

the profile.
BKI8340E

section section_name must not be
specified more than once.
Explanation: In the profile, only a single section with

the name indicated can be specified. However, during
parsing, a second occurrence was detected.
BKI8341E

section section_name missing.
Explanation: The required profile section indicated

was not found in the profile.
BKI8343W
The parameter keyword1 of keyword2

value2 has changed its value from value1
to value3.
Explanation: The profile parameter named must not

change its value between backup and restore. However,
in the named profile section, the parameter has a new
value value3 different from the value value1 it had at
backup time. Both values are given in the message.
User response: Check the log file for problems that
may result from the change of parameter values. If so,
you may want to change the profile, restoring
parameter keyword1 to the value it had when creating
the backup in order to perform a specific operation.
BKI8344E
Path path is listed more than once for

partitioning.
Explanation: This is a DB2 - TSM interface problem.

BKI8345E
Error while parsing parameter keyword.

path is required to be type_information.
Explanation: A path of the type indicated in the

message is expected as a value of the named parameter.
However, the specified path was not found to be of the
correct type.
appropriate.
BKI8349I
Deleting incomplete backup backup_id

backup_key .

During this process, the incomplete backup listed is
removed. A backup becomes incomplete when parts of
its data expire. This can happen when a backup that is
marked destructively restorable is restored.
BKI8511I
The command is: command name.
The requested action was performed

successfully; however, some warnings were
issued.
2 or greater
The requested action could not be performed
due to errors. In this case, an error message
should be logged, too.
1
User response: None if the return code is 0.

If the return code is greater than 0, analyze the error
and/or warning messages. Resolve errors before
starting the action again.
BKI8513I
TDP_DIR is not set. The temporary

path will be used
Explanation: The variable TDP_DIR is not set in the

user environment. All run logs will be written to the
machines temporary directory instead.
User response: Define the environment variable
TDP_DIR .
BKI8514W
TDP_DIR is not set correctly. The

temporary path will be used.
Explanation: The variable TDP_DIR is set but contains

an invalid path. All run logs will be written to the
machines temporary directory instead.
User response: Check and reset the environment
variable TDP_DIR.
BKI8520E
No command was specified.
Explanation: backom was called without a command.

User response: Check the command syntax and
correct the call.
BKI8521E
Command option command option

requires an argument.
Explanation: A command option requiring an

argument was specified without an argument.
correct the call.
Explanation: This is an information message echoing

the command.
BKI8522E
Explanation: backom was called with an invalid

command.
BKI8512I
Return code is: return code.
Explanation: This message shows the return code of

the Backup Object Manager.
Valid return codes:
0
The requested action was performed
successfully.
Invalid command command.

correct the call.
BKI8523E
Error during action.
Explanation: An error occurred while performing the

named action.
967
User response: Look for other error messages in order

to analyze the problem.
User response: Correct the timestamp.

BKI8529E
BKI8524E
Tablespace online restore is not allowed.
Explanation: Either the database setup or the kind of

backup prevents an online tablespace backup.
User response: If you need to do a tablespace restore
it must be done offline.
Invalid log sequence number. Specify it

in the format log sequence format.
Explanation: The information on the log sequence

number(s) does not comply with the expected format.
Accepted log sequence numbers are for example 123
or S0000123.LOG.
User response: Correct the log sequence number(s).
BKI8525E
The DB2 instance name can consist of at

most 8 characters.
Explanation: The name given for the DB2 instance

does not comply with the DB2 naming conventions.
User response: Correct the DB2 instance name.
BKI8526E
The DB2 database alias can consist of at

most 8 characters.
Explanation: The name given for the DB2 alias does

not comply with the DB2 naming conventions.
BKI8530E
Profile file name does not exist or cannot

be accessed.
Explanation: Either an existing file could not be

opened, or a file could not be created.
User response: Check the attributes of the file and/or
its directory. For backup processing, read access is
required for the files to be backed up. For restore
processing, write access is required for the target
location of the files to be restored.
Directory file path does not exist or
cannot be accessed.
User response: Correct the DB2 alias name.
BKI8531E
BKI8527E
Explanation: A file path cannot be accessed.
Invalid node. Specify it in the format

node format.
Explanation: The name given for the DB2 node does

not comply with the DB2 naming conventions. Node
numbers must be specified in the displayed format, for
example NODE0000 or 0000.
User response: Check the attributes of the file and/or

its directory. For backup processing, read access is
required for the files to be backed up. For restore
processing, write access is required for the target
location of the files to be restored.
User response: Correct the DB2 node number.

BKI8532E
BKI8528E
Invalid timestamp. It must consist of 14

digits with format yyyymmddhhmmss
or digits and wildcards * or ?.
Explanation: Specify digits in the format

yyyymmddhhmmss or mixed with wildcards * or ?.
Explanation: The information on the log chain

number(s) does not comply with the expected format.
Accepted log chain number(s) are for example 123 or
C0000123. file path
User response: Correct the log chain number(s).
where:
v yyyy is the year, specified as four digits,
v
mm is the month, specified as two digits, with

leading zero for the months January to September,
dd is the day of the month, specified as two digits,

with leading zero for days 1 to 9,
hh is the hour of the day, 00 to 23, with leading zero

for hours 0 to 9,
mm is the minutes of the hour, 00 to 59, with

leading zero for minutes 0 to 9,
ss is the second of the minute, 00, to 59, with

leading zero for seconds 0 to 9.
BKI8533E
v * means any number of any digits,

? means exactly one digit of any value.
968
A timestamp range is not allowed for

the command command .
Explanation: A timestamp range is not allowed for

command restore database, restore
tabelspace, restore tablespace online and restore
DB2 history file. Only a single timestamp argument
can be used.
User response: Correct the timestamp command
option.
BKI8534E
Any digits can be replaced by wildcards * or ?,

where
v
Invalid log chain number. Specify it in

the format log chain format.
Command option command option is

missing.
Explanation: A command was issued without

specifying a required command option.

correct the call.
at the location specified in option -e on the command

line or in environment variable XINT_PROFILE.
BKI8535E
Check the attributes of the profile and the

corresponding directory and make sure that the file can
be accessed.
Invalid output mode. Specify one of the

keywords keyword list.
Explanation: Only the listed keyword values are

allowed with the output mode command option -m.
BKI8543I
Querying TSM for file(s) file list.
User response: Correct the output mode command

option.
Explanation: The Backup Object Manager checks if the

files listed are available on the TSM server(s) specified
in the corresponding profile.
BKI8536E
Wildcard characters are not allowed for

command command.
Explanation: For the BackOM commands restore

database, restore tablespace, restore tablespace
online and restore DB2 history file its not allowed to
specify the wildcard characters * and ? in a
timestamp command option.
User response: Correct the timestamp command
option.
BKI8537E
The path path is not absolute.
Explanation: A command line argument requires a

fully qualified path which was not given.
User response: Specify the fully qualified path.
BKI8538E
The TDI file name cannot be processed.
Explanation: The TDI file could not be parsed because

of errors. There are more specific parser error messages
before this message occurs.
error messages in the Backup Object Manager log.
BKI8540I
Using component_name at host name:port

number.
Explanation: The component_name service named is

used for the current action.
No image type image(s) found.
Explanation: A request could not be satisfied because

the files to be processed are not available on the TSM
server.
User response: Check if the file(s) were specified
correctly in the request.
BKI8546E
Environment variable environment

variable is not set or not set correctly.
Explanation: A required environment variable is not

set at all or has a value that is not allowed.
User response: Check the documentation for the
appropriate values of the environment variable named
and set its value accordingly.
BKI8548I
Elapsed time: time value.
Explanation: After restore and delete, the time elapsed

during the action is displayed.
BKI8549E
Explanation: During restore, the file to be restored

cannot be created in the target location.
User response: Check if there is sufficient space
available for the file to be restored.

BKI8541I
BKI8545I
Check the attributes of the target directory; write access

is required.
Using profile profile path.
Explanation: The profile named is used for the current

action.
If the target file already exists, check that write access

is granted

BKI8550W
BKI8542E
Profile profile path cannot be read.
Explanation: The Backup Object Manager tried to use

the profile named but the profile was not available or
could not be read. The location of the profile is
specified via command line as argument to option -e
or in environment variable XINT_PROFILE.
User response: Make sure that the profile is available
Environment variable environment

variable for output mode has wrong
value. Using default.
Explanation: The default output mode can be

overridden by the named environment variable.
Accepted values are short, normal, or detailed.
The system default is short for actions on DB2 log
files, normal otherwise.
969
User response: Specify an appropriate value for the

environment variable named, or remove the
environment variable.
BKI8551E
Not all data written to file path.
Explanation: Restoring raw or DB2 log file data ended

before all data retrieved from TSM could be written to
the file named.
The file is incomplete.
User response: Make sure there is sufficient space for
the data to be restored.
BKI8552E
File file path could not be closed.
Explanation: After restoring raw or DB2 log file data,

the target file could not be closed.
User response: Retry the action.
BKI8555E
Variable DB2DBDFT or command

option alias is required.
Explanation: The password command needs the

name/alias of the database, for which the DP for SAP
configuration file has to be adapted.
BKI8559W
For partition partition number switch to

host host name and issue the command
again.
Explanation: When verifying the TSM password, the

DP for SAP configuration file is modified.
If the DP for SAP profile keyword CONFIG_FILE
points to an NFS mounted (UNIX or Linux) or a shared
(Windows) path accessible to all hosts in a DB2 ESE
(EEE) environment, for example the instance home, all
configuration files of the various partitions can be
modified simultaneously. If, in contrast, keyword
CONFIG_FILE points to a local path, only the
configuration files of the local partitions can be
modified. In this case, the password verification needs
to be done from each host. The message indicates the
partitions whose associated configuration files are not
accessible. In order to avoid this administrative
overhead, it is recommended to place the DP for SAP
configuration files in a filesystem shared by all hosts
hosting a partition of the database.
User response: Make sure to verify the TSM
password(s) for all partitions of the database.
BKI8560E
Partition partition number not found in

the database configuration.
User response: Either set the environment variable

DB2DBDFT or provide the command option alias with
the password command and try again.
Explanation: The DB2 partition specified could not be

found in the database configuration.
BKI8556E
User response: Check the configuration of the DB2

ESE(EEE) environment (db2nodes.cfg, environment
variable DB2NODE) and try again.
Unable to get hostname.
Explanation: The machines hostname could not be

determined.
User response: Check the TCP/IP configuration of the
machine.
BKI8557E
The config file file name could not be

created.
Explanation: DP for SAP tries to create the

configuration file named if it is not present at the
location specified by the DP for SAP profile keyword
CONFIG_FILE. However, the file cannot be created.
This may either be caused by an incorrect path
specified by keyword CONFIG_FILE, or the user may
not have the appropriate permissions for creating the
file.
User response: Make sure the path specified by
keyword CONFIG_FILE is correct and the permissions
are set appropriately.
BKI8558I
Setting TSM password for partition

partition number on host host name.
Explanation: The DP for SAP TSM password is set on

the host named for the DB2 partition indicated.
970
BKI8561W
Database alias not listed in the system

database directory.
Explanation: The database alias does not exist.

Because there is a dependency between the alias and
the settings for DP for SAP there might be problems
during database backup or restore runs. Nevertheless,
the DP for SAP configuration file (init<alias>.utl) will
be created and adapted.
User response: Check if the alias specified does match
to an entry in the DB2 system database directory.
Further, check the argument for the DP for SAP profile
keyword CONFIG_FILE and if necessary adapt it
appropriately.
BKI8584I
Delete command completed successfully.
Explanation: The object(s) specified with the delete

command were successfully deleted from the TSM
server.
BKI8585W
Delete command completed successfully,

but had warning(s).
Explanation: The object(s) specified with the delete

command were deleted with warning(s) from the TSM
server.
User response: Check the Backup Object Manager log
file for further detailed messages and if required, do
the requested interventions manually.
BKI8613E
Explanation: An error occurred, and the database

restore terminates.
error messages in the Backup Object Manager and the
shared library run logs. Additional information may be
found in the DB2 diagnostic log (db2diag.log).
BKI8615I
BKI8586I
Delete command was aborted.
Explanation: The delete command was aborted by the

user. No object(s) were deleted from the TSM server.
User response: None
Terminating restore ...
Restore command completed

successfully.
Explanation: The object(s) specified with the restore

command were successfully restored from the TSM
server.
BKI8587E
Delete command failed due to an error.
Explanation: The delete command failed during

execution. Not all objects were deleted from the TSM
server.
file for further detailed messages and try to resolve the
error which led to the delete failure. Retry the action. If
the error still exists, contact the IBM support.
BKI8588E
Delete command has not been started or

no delete result information is available.
BKI8616W
Restore command completed

successfully. Warning(s) encountered.
Explanation: The object(s) specified with the restore

command were restored with warning(s) from the TSM
server.
file for further detailed messages and if required, do
the requested interventions manually.
BKI8617I
Restore command was aborted.
Explanation: This message indicates that an operation

did not complete successfully. Typically, some other
error condition was detected before.
Explanation: The restore command was aborted by

the user. No object(s) were restored from the TSM
server.
User response: Contact the IBM support.
BKI8589E
BKI8618E
Query command failed due to an error.
Explanation: The query command failed during

execution. Not all queried objects can be displayed.
error messages in the Backup Object Manager log. In
the absence of preceding error messages, contact IBM
support.
BKI8610I
Explanation: The restore command failed during

execution. Not all objects were restored from the TSM
server.
file for further detailed messages and try to resolve the
error which led to the restore failure. Retry the action.
If the error still exists, contact the IBM support.
Restoring type ...
Explanation: The restore of type has started.

BKI8612I
Restore command failed due to an error.
Continuing restore ...
Explanation: The database restore continues.

BKI8619E
Restore command has not been started

or no restore result information is
available.
Explanation: This message indicates that an operation

did not complete successfully. Typically, some other
error condition was detected before.
971
BKI8621I
Restoring file file name...
BKI8634E
Backup command failed due to an error.
Explanation: The system started restoring the file

indicated.
Explanation: No backup was made due to previous

errors.

BKI8622I
Deleting type ...
Explanation: The deletion of type has started.

BKI8623I
Deleting file file name ...
Explanation: The system started deleting the file

indicated.
BKI8635E
Explanation: An invalid argument was specified for

command option option.
User response: Correct the command syntax.
BKI8636E

BKI8626W
The TDI file name could not be deleted.
The command option option must be a

floating point number.
The command option option must be one

of values.

Explanation: The system tried to remove the TDI

image from TSM, but did not succeed.
User response: Try to remove the image manually

using the Backup Object Manager raw delete facility.
BKI8637I
BKI8630E
The command option option must be a

number.

Explanation: A backup operation of database alias of

type type has started.
BKI8638I

BKI8631I
Backup command completed

successfully.
Explanation: The backup operation completed

successfully; the backup image can be used for
restoring. In the case of a full database backup, the TDI
image was generated and stored to TSM, too.
BKI8632W
Backup command completed

successfully. Warning(s) encountered.
Explanation: The backup operation completed

successfully; the backup image can be used for
restoring. However, some problems occurred.
User response: Check the warning messages and take
corrective actions if necessary.
BKI8633I
Backup command was aborted.
Type online/offline backup of alias started

...
Type online/offline backup of tablespace(s)

tablespace#1,...,tablespace#n of alias started
...
Explanation: A backup operation of tablespace(s)

tablespace#1 ... tablespace#n of database alias of type type
was started.
BKI8639I
Including log files in backup image ...
Explanation: The DB2 log files are stored as part of

the backup image.
BKI8640I
Using number buffers with a size of size

...
Explanation: For backup or restore operations, the

indicated number of buffers of the size displayed are
used.
Explanation: The backup operation was cancelled by

user interaction. No backup image was created.
BKI8641I

indicated number of TSM sessions is used.
Using number session(s) ...
972
BKI8642I
Using a degree of parallelism of number

...

degree of parallelism is displayed.
BKI8643I
Using vendor library at lib path ...

named vendor library is used.
None.
BKI8644W
Offline backups cannot include log

files. The option -L is being ignored.
Explanation: An offline backup operation was started,

requesting the DB2 log files to be included. This is not
possible with an offline backup. The backup is done
without including DB2 log files.
User response: Make sure to backup DB2 log files
separately.
BKI8651W
Your version of DB2 does not support

including log files. The option -L is
being ignored.
Explanation: A backup was started, requesting the

DB2 log files to be included, but your version of DB2
does not support this feature. For including DB2 log
files in the backup image, DB2 V.8.2 or later is required.
User response: Make sure to backup DB2 log files
separately.
BKI8652I
Detected DB2 version version with

number bits.
Explanation: The indicated DB2 version was detected

by Backup Object Manager.
User response: None
BKI8653I
Using autonomic buffer size and

number of buffers ...
BKI8655I
Using an autonomic number of buffers

with a size of size ...
Explanation: The number of buffers to be used for

backup and restore are determined by DB2. The buffer
size to be used was specified in the call to the Backup
Object Manager.
BKI8656I
Using an autonomic degree of

parallelism...
Explanation: The number of DB2 processes (UNIX or

Linux) or threads (Windows) used for reading or
writing data from/to tablespace containers during
backup and restore is determined by DB2.
BKI8657W
Number is not a valid partition number.

Assuming partition 0.
Explanation: The partition number specified in the

call to Backup Object Manager does not denote a valid
partition of the database. Therefore, the default
partition 0 will be used by DB2 and by Backup Object
Manager.
User response: If your database is not partitioned do
not specify the partition number for further actions.
BKI8658E
Number is not a partition number of the

database or does not denote a partition
on this host.
Explanation: The partition number specified does not

denote a valid database partition or is not the partition
located on the system where Backup Object Manager is
called. Backup Object Manager can only operate on
partitions residing on the same host.
User response: Either change number to a partition
number of a local partition, or start Backup Object
Manager from the same host where the partition
resides.
BKI8659I
Creating tablespace definition

information ...
Explanation: The buffer size and the number of

buffers used for backup or restore is automatically
determined by DB2.
Explanation: The tablespace definition information

(TDI) is being created in memory.
User response: None
BKI8654I
BKI8660I
Using an autonomic buffer size with

number buffers ...
Explanation: The buffer size used for backup and

restore is automatically determined by DB2. The
number of buffers to be used was specified in the call
to the Backup Object Manager.
Saving tablespace definition

information ...
Explanation: The tablespace definition information

(TDI) is being stored on the TSM server.

973
BKI8661W
Could not create TDI. The backup

cannot be used for redirected restore
with BackOM.
Explanation: The system could not collect the

tablespace definition information. The backup was
made without TDI. As a result, the backup can be used
for restoring the system, but it cannot be used for
restoring to a different location.
User response: Ensure that your database is enabled
to accept CLI connections.
BKI8662W
Could not save TDI. The backup cannot

be used for redirected restore with
BackOM.
Explanation: The system could not save the TDI on

TSM. The backup was made without TDI. As a result,
the backup can be used for restoring the system, but it
cannot be used for restoring to a different location.
BKI8663W
The TDI contains device containers. The

backup cannot be used for redirected
restore with BackOM.
Explanation: A backup of a database using device

containers was requested. The backup was successful, it
can be used to restore the system, but it cannot be used
for restoring to a different location. Restoring to a
different location is not supported with device
containers.
BKI8664E
Connecting to alias using CLI failed. The

return code was return code.
Explanation: The system tried to connect to the

database named via the CLI. The operation did not
succeed and returned the error code indicated.
User response: Ensure that your database is enabled
to accept CLI connections.
BKI8665I
The backup timestamp is: timestamp.
Explanation: The DB2 backup finished successfully

with the timestamp timestamp.
BKI8666I
Redirecting tablespace tablespace with ID

id.
Explanation: The named tablespace is restored to the

location requested.
974
BKI8667I
Tablespace tablespace with ID id was not

redirected because its container on the
source system SID is not located in a
path starting with path .
Explanation: The named tablespace of type SMS is not

redirected because the definition of the tablespace
container in the source system does not match the
database characteristics that Backup Object Manager
expects and that are cited in the message. Therefore,
Backup Object Manager tries to restore the tablespace
to a location identical to the location in the original
system.
User response: Make sure that the tablespace
mentioned can be restored to the original location. This
includes that the user initiating the redirected restore
has the appropriate permissions for placing the
tablespace container in this location and that the
tablespace can be restored without overwriting other
data.
In order to avoid this situation in the future, the
administrator of the source system may want to
recreate the tablespace according to the database
characteristics Backup Object Manager expects.
BKI8690E
Free space test for container path failed.

Only free bytes MB free space left but
required bytes MB required.
Explanation: The system requires a tablespace

container of the size indicated at the path named, but
there is not sufficient free space available to create it.
User response: Try to make available the free space
required, for example by
1. Removing some files on the volume or file system
the container shall reside on.
2. Increasing the size of the file system the container
shall reside on.
3. Shrinking the size of the container requested so that
it fits in the free space.
Note: Backup Object Manager assumes that a small
part (0.05%) of the free space will be required by the
operating system for administrative use. As a
consequence, only 99.95% of the free space on the
volume or file system is actually available.
BKI8692E
The requested data could not be

retrieved.
Explanation: The TDI data of a backup image could

not be retrieved and displayed.
User response: Look for and respond to preceding
error messages.
BKI8693E
More than one TDI file matches your

query.
Explanation: More than one TDI file matching the

search criteria was found on TSM.
User response: Specify additional BackOM command
options to restrict the result set.
BKI8700E
Internal parser error in TDI parser.
Explanation: An unexpected error occurred in the TDI

parser.
BKI8701E
BKI8706E
The container at path is inappropriate

for tablespace tablespace.
Explanation: The container at the location indicated

cannot be added to the tablespace named because of
incompatible properties.
User response: Check the properties of the container
and the tablespace. Ensure that the IDs of the
containers are unique for the tablespace named.
BKI8707E
Missing statement keyword in block block

name near line line number.
Explanation: A keyword is missing in the named

block ending at the line given.
This parser cannot process TDI version

version.
User response: Insert the required statement in the

block.
Explanation: The current version of Backup Object

Manager is not compatible with the version the TDI
image was created with. As a consequence, the TDI
data cannot be processed.
BKI8708E
User response: Check the release notes for the

appropriate migration procedure.
Explanation: The TDI image does not start with the

required header ([TDI] block). Only comments or
whitespace are allowed before this block.
BKI8702E
User response: Ensure that the [TDI] block is the first

block in the TDI image.
Too many errors. Bailing out.
Explanation: The TDI parser encountered a number of

errors. Restoring is stopped.
BKI8703E
Out of memory.
Explanation: The TDI parser encountered a token that

cannot be read into the main memory. The TDI image
cannot be processed, and restoring is stopped.
BKI8709E
Error while reading input file.
Explanation: The TDI parser tried to read more data

from disk or from TSM, but did not succeed.
User response: Ensure that the TDI image to be
processed exists at the expected location and that the
system has sufficient privileges to read it.
User response: Insert the missing block using valid

values.
BKI8710W
error in line line number.
Explanation: The TDI parser encountered a syntax

error in the line indicated. As a consequence, the TDI
image cannot be analyzed.
User response: Respond to the error message and
correct your TDI image.
Duplicate block block name ignored at

line line number.
Explanation: At the line indicated, a block begins

whose name was encountered before. The system
ignores the duplicate block; it uses the data from the
first occurrence of duplicate blocks.
User response: Make sure that block names are
unique within a TDI image.
BKI8711W
BKI8705E
The required block block name is

missing.
Explanation: The named block is missing in your TDI

image.

BKI8704E
The [TDI] header block must be the

first block.
Duplicate statement keyword ignored in

line line number.
Explanation: At the line indicated, a duplicate

statement was encountered within a block. The system
ignores the duplicate statement.
User response: Make sure to not specify duplicate
statements within a block.
975
BKI8730I
Scaling tablespace containers to number

percent ...
BKI8738E
The container at path has a page size

that is incompatible with its tablespace.
Explanation: All tablespace containers will be

increased by the percentage indicated during the
tablespace container redefinition step.
Explanation: The container indicated does not have

the same page size as its tablespace according to the
definitions in the TDI image.
User response: Contact IBM support
BKI8731I
BKI8739E
Normalizing tablespace containers ...
Explanation: All containers of a tablespace will be of

the same size after redefinition.
BKI8732E
The TDI used for redirected restore

contains an invalid database alias.
Explanation: There is an invalid database alias

specified in the alias statement of the TDI image.
The type of the container at path is

incompatible with its tablespace.
Explanation: The container indicated cannot be used

with its associated tablespace according to the
definitions in the TDI image. SMS tablespaces can only
have path containers, and DMS tablespaces must have
file or device containers.
User response: Ensure that the appropriate types of
containers are used with each tablespace
The path path of a container must not be
relative.
User response: Provide a valid alias.
BKI8740E
BKI8733E
Explanation: In the TDI image, the named path

defining a container does not seem to be a fully
qualified path.

contains an invalid instance name.
Explanation: There is an invalid database instance

specified in the instance statement of the TDI image.
User response: Provide a valid instance name.
BKI8734E

contains an invalid partition number.
Explanation: There is an invalid partition number

specified in the Node statement of the TDI image.
User response: Provide a valid partition number.
BKI8736E
Tablespace tablespace must have at least

one container.
Explanation: The TDI image defines the tablespace

named without containers.
User response: Ensure that there is at least one
container associated with every tablespace.
BKI8737E
Tablespace tablespace has containers with

the combined storage too small.
Explanation: The number of used pages of the

tablespace named exceeds the combined size of its
tablespace containers defined in the TDI image.
User response: Ensure that every tablespace has
containers of a combined size that is sufficient to hold
the used pages of the tablespace.
976
User response: Ensure that all paths in your TDI are

fully qualified
BKI8741E
The container at path would overwrite

existing files or directories.
Explanation: The TDI image contains the definition of

the container indicated whose location is already in
use. This is only allowed when restoring to the source
database. Restoring to a different location is stopped.
User response: Ensure that all path containers defined
in the TDI image point to non-existing paths and all
file containers point to non-existing files
BKI8742E
The container at path is a device

container which is not supported.
Explanation: In the TDI image, a device container is

defined. However, device containers are not supported
by Backup Object Manager.
User response: Do not use device containers.
BKI8743I
Local TDI check returned return code.
Explanation: The TDI with the target database

tablespace definition was checked. If the return code
given does not equal 0 errors occurred.
User response: In the case of a non-zero return code,
BKI8744I
TDI replacement check returned return

code.
Explanation: The system checked whether the

tablespace definitions of the target TDI can replace the
definitions of the source TDI. If the return code given
does not equal 0 the tablespace definitions of the target
TDI are not valid.
User response: In the case of a non-zero return code,
BKI8745E
The TDI is invalid.
Explanation: The TDI with the target tablespace

definitions is not valid. Restoring to a different location
is stopped.
for the return code of the validation. Check for and
respond to preceding error messages in the Backup
Object Manager log.
BKI8746I
The number of used pages of a

tablespace in the TDI does not match
the one of the original database.
Explanation: The target TDI contains at least one

tablespace with a matching ID in the source TDI, but
the number of used pages of the target tablespace does
not match the number of used pages in the original
database.
User response: Ensure that the number of used pages
of a tablespace is the same in both the source and the
target TDI.
BKI8751E
The tablespace type in the TDI does not

match the one of the original database.
Explanation: The target TDI holds at least one

the tablespace types are different.
User response: Ensure that the type of a tablespace is
the same in both the source and the target TDI.
The TDI is valid.
Explanation: The TDI with the target tablespace

definition is valid. Processing continues.
BKI8747E
BKI8750E
Not all tablespaces of the original

database are contained in the TDI.
Explanation: At least one tablespace of the original

database is missing in the TDI definitions of the target
database. However, a new location must be given for
all tablespaces of the original database. Therefore,
restoring to a different location is stopped.
BKI8752E
BackOM does not support redirected

restore with device containers.

definition of a device container. However, device
containers are not supported by Backup Object
Managers redirected restore function.
User response: Do not use the Backup Object
Managers redirected restore facility for device
containers.
BKI8753E
A container cannot be created at path.
User response: Provide the information on the

missing tablespaces and their containers.
Explanation: Either the location where the tablespace

container is to be created does not exist, or the
permissions of the user are not sufficient.
BKI8748E
User response: Check the location and the

permissions.
The TDI does not define enough storage

to hold all the data of the original
database.
Explanation: The target TDI has at least one

tablespace whose containers are too small to hold the
data of the source database.
User response: Increase the container size or add
more containers to the tablespaces.
BKI8749E
The page size of a tablespace in the TDI

does not match the one of the original
database.

their page sizes do not match.
User response: Ensure that tablespaces have the same
page sizes in both the source and the target TDI.
BKI8755I
Getting reference TDI from TSM ...
Explanation: Retrieving the appropriate TDI to be

used by internal checking routines from the TSM
server.
BKI8756W
Could not get reference TDI from TSM.

No input validation is done.
Explanation: The system could not find a TDI image

matching the database backup to be restored on TSM.
The restore action will be continued, but the input data
cannot be validated before the restore starts.
977
BKI8757I
Performing redirected restore from

source alias to target alias...
Explanation: Redirected restore of source alias to target

alias is starting.
User response: None
BKI8758E
The TDI does not contain data for

tablespace tablespace.
Explanation: A definition of the tablespace named is

expected to be provided in the TDI, but could not be
found.
User response: Ensure that all tablespaces of the
source database are also defined in the target TDI.
BKI8759E
Redirecting of at least one container

failed.
Explanation: The system tried to create the containers

for a tablespace, but at least one of them could not be
redirected to a different location. Usually, the location
of one of the tablespace containers is not allowed. A list
of containers the system tries to create can be found in
the Backup Object Manager log. One of them failed.
User response: Check for and respond to further error
messages in the Backup Object Manager log.
BKI8760E
Not all directories for the containers

could be created.
Explanation: The system tried to create the directories

to place the containers in, but at least one failed.
User response: Ensure that the system has sufficient
privileges to create the directories at the desired
locations.
BKI8761E
The container at path does not have the

minimum size of two extends.
Explanation: A tablespace container to be created

must have at least the size of two extends.
BKI8763E
The extent size of a tablespace in the

TDI does not match the one of the
original database.
Explanation: The extend sizes of corresponding

tablespaces defined in the source and target TDIs must
be equal. However, for at least one tablespace different
extend sizes are defined in the source and target
databases.
User response: Define matching extend sizes for
corresponding tablespaces.
BKI8765I
Testing redirected restore from source

alias to target alias ...
Explanation: The system is testing whether the

original database can be restored to the target location.
It checks whether
v the filesystem where the tablespace containers are to
be created has sufficient free space. (If specified,
normalizing and scaling are also considered.)
v there are existing files and directories identical to the
containers defined for the target database. This
would indicate that a database of same name and of
same structure already exists, and data could be
overridden.
v the structures of the source and target databases
(tablespace types, page sizes, extend sizes) allow for
a redirected restore.
BKI8766I
Check successful. Redirected restore

possible with these settings.
Explanation: The redirected restore test finished

successfully. Thus, the redirected restore operation can
be started with the options specified for the test run.
BKI8767W
Warnings occurred.
User response: Correct the size of the container to be

created.
Explanation: The redirected restore test detected one

or more minor conflicts. These conflicts may or may
not prevent a successful redirected restore operation.
Nevertheless, it is recommended to resolve them.
Set tablespace container with ID id and

name tablespace_container.

warning messages in the Backup Object Manager log.
BKI8762I
Explanation: Backup Object Manager redirects a

tablespace container to the ID and name indicated.
BKI8768E
Check failed. Redirected restore not

possible with these settings.
Explanation: The redirected restore test detected one

or more major errors which will prevent a successful
redirected restore with these settings.
978
BKI8770I
Getting TDI for redirected restore from

TSM ...
Explanation: The system is retrieving the TDI image

from the TSM server.
BKI8771E
The TDI for the redirected restore could

not be retrieved.
Explanation: The TDI image specified could not be

found.
User response: Provide the correct location of the TDI
image.
BKI8799E
A container must have a size of at least

twice the extent size (minimum size for
this tablespace).
Explanation: The container size specified is too small.

The minimum size of a container is twice the extent
size.
User response: Correct the container size.
BKI8800I
The command is: command.
Explanation: Displays the command that was issued.

The following commands are possible: Backup, Restore,
Archive/Retrieve.
BKI8772E
The selected database has a structure

that prevents automatic cloning.
Explanation: You tried to clone an SAP database using

redirected restore, but the database does not have the
default directory structure of an SAP database. The
cloning facility of Backup Object Manager redirected
restore cannot be used for this system.
User response: You may use either the interactive or
the batch mode of Backup Object Manager redirected
restore.
BKI8773E
The interactive modification of the

containers failed.
Explanation: You tried to interactively change the

location of containers, but this operation failed.
BKI8801I
Explanation: Displays the process id of the DB2

process which called the shared library.
BKI8802I
You are not allowed to delete this

container.
Explanation: You tried to delete the last container of a

tablespace. However, at least one container must be
available to every tablespace.
User response: Make sure that there is at least one
container defined for every tablespace.
BKI8798E
You cannot continue as there are errors.
Explanation: You tried to start a restore operation

after redefining the containers interactively, but errors
were detected in the input data. The operation cannot
continue.
User response: Check all tablespaces with !! error
marks in the list and correct the definitions of their
containers. Then continue.
Found number backup image(s) on TSM

server.
Explanation: For restore and delete operations DP for

SAP queries TSM for backup images by means of a
timestamp and shows the number of found images.
BKI8803I

BKI8776E
PID of calling process: PID_number.
The DB2 backup image size for this

session is about size.
Explanation: The estimated size of the data to be

backed up is displayed.
BKI8804W
The recovery log could not be written.
Explanation: After every backup or restore, DP for

SAP writes a record into the recovery log file
tdprlf.<SID>.<node_name>.log. It is located in the path
pointed to by environment variable TDP_DIR.
User response: Check, if the permissions are set
correctly and if there is sufficient free space in your
filesystem.
BKI8805W
The restore was cancelled by the user.

Existing data not overwritten.
Explanation: During a restore, the user decided not to

overwrite existing data. As a result, the action was
cancelled
979
BKI8806I
product version.release.modification (Beta)

build_number build_data
BKI8815I
Explanation: Writes version information into the

product log file.
BKI8807I
Archive log file log number of chain log

chain number.
Explanation: Writes information about the log file to

be archived into the product log file.
Information for Log Manager:

DB2_instance DB2_database_name
DB2_database_alias
log_and_log_chain_number partition
Explanation: The information listed is provided to the

DB2 Log Manager.
BKI9001E
Internal error: error
Explanation: The following internal error: error has

been encountered.
BKI8808I
Retrieve log file log number of chain log

chain number.
Explanation: Writes information about the log file to

be retrieved into the product log file.
User response: None
BKI8810I
Cleaning up resources of process

PID_number.
Explanation: All resources used by the product will be

released.
BKI8812I
Committed TSM sessions will be

deleted.
Explanation: During a backup with multiple sessions,

an error occurred. The backup operation is stopped.
TSM sessions already committed during this operation
are being deleted from the TSM server in order to
prevent them from being considered restorable.
BKI8813E
Error deleting committed TSM sessions.
Explanation: One or more committed TSM sessions

could not be deleted during the postprocessing of the
failed backup run.
User response: Use the Backup Object Manager to
delete the file(s) manually..
BKI8814I
Inquire TSM with mask search mask.
BKI9003E
Incompatible components installed:

component name component name
Explanation: The components mentioned in the

message text can not be used together. This may be the
result of an incomplete upgrade.
BKI9005E
A not supported by B.
Explanation: The installed version of product B does

not support product A. Most likely you need to
upgrade product B.
User response: Contact the IBM support.
BKI9006E
Internal error while reading

environment variable: variable.

BKI9007W
An error occurred while terminating the

application: the error
Explanation: While terminating the application, an

error occurred. This has no impact on the success of the
operation.
User response: None
BKI9008E
This product requires at least version

number of product name to be installed.
Explanation: The string denoted is used to inquire

TSM for backup images.
Explanation: The version of the application product

name is not supported by this application. Most likely
application product name needs to be upgraded.
980
BKI9009W
The following products are not

compatible: product name (product version)
and product name (product version).
Explanation: This message is similar to BKI9008E. But

in this case its not obvious which one of the products
needs to be upgraded. .
BKI9205E
Additional support information: Unable

to instantiate name at position position.
Explanation: This error message typically follows a

previous error. If so this error message can be ignored.
Otherwise contact IBM support.
User response: Contact IBM support

BKI9206E
BKI9200E
Additional support information: An

exception was thrown at position:
position.

Otherwise contact IBM support
Additional support information: Unable

to use actual when expecting expected at
position position.


BKI9207E
BKI9201E

Exception was thrown at position:
position.


position.


BKI9208E
BKI9202E

position.

BKI9203E

BKI9204E
User response: Check errno and errno text with you

system administrator. If you cannot resolve the
problem, contact IBM support.

Additional support information: No

handler registered for message type
message. Thrown at position: position.

BKI9210E

position (text=description).
Explanation: A system call failed with errno.
BKI9209E

position.
System error errno: errno text at position

position.
ESD_AbortDispatchingException thrown
at position: position.

BKI9211E

position. (State state)

981
BKI9212E
Additional support information: No

handler registered for message type type.
Thrown at position: position.

BKI9219E
Additional support information: Invalid

error type typeencountered.


BKI9220E
BKI9213E
Internal error: A memory allocation

request failed at position: position.
Explanation: This error message indicates an

out-of-storage condition. It may occur due to a
previous error, or it may be owed to a large size of the
internal buffers
error messages. You may also want to reduce the size
of the internal buffers (keyword BUFFSIZE in the Data
Protection for SAP profile).
BKI9214E

exception was thrown from a destructor.
Callstack follows: callstack.

BKI9216E

position.
Additional support information: Second

call of call.

Otherwise contact your IBM support.
User response: Contact your IBM support.
BKI9300E
Additional support information:

Aborting send operation. See previous
error.
Explanation: This error may have been caused by

previous errors.
User response: Check for previous errors and correct
them.
BKI9301E
Additional support information: State

state does not match state pattern pattern.


BKI9302E

Otherwise contact your IBM support.
BKI9217E

position.

BKI9218E

position.

982
Additional support information: Unused

ESD_ReturnChannel destroyed.
Dumping callstack: callstack

BKI9306I
Dumping callstack: call stack.
Explanation: This message is always preceded by an

error message indicating the problem. It provides
additional information that might help IBM support to
analyze the cause of the problem.
User response: If you need to call IBM support,
provide the information given in this message together
with the error information.
BKI9307E
Did not find a winsock dll compatible

with version expected version. Version
found is available version
Explanation: The product failed to load the

appropriate winsock dll.
User response: Contact your system administrator
BKI9308E
A socket request timed out after

processing number of bytes bytes position.
Explanation: A socket request was issued with a

timeout and the requested action could not be
completed within the time specified. It was cancelled
after processing number of bytes bytes.
User response: If you need to call IBM support,
provide the information given in this message together
with the error information.
BKI9309E
Operation terminated due to an explicit

abort request.
Explanation: An operation was terminated due to

customer intervention.
BKI9310E
persists contact your IBM support personnel.

BKI9313E
Explanation: The information on the named backup

could not be updated in the repository located at the
path named.
User response: Check the logs for other messages
pointing to the cause of this problem. Resolve any
problems indicated. If the problem persists contact your
IBM support personnel.
BKI9314E
Explanation: The system was not able to add

information on the named backup to the repository
located in the path indicated.
User response: Make sure the repository path is set
correctly. If you need to correct the repository location,
restart the server executable afterwards. If the problem
User response: Check the logs for other messages

pointing to the cause of this problem. Resolve any
problems indicated. If the problem persists contact your
IBM support personnel.
Could not find backup_id in the

repository at path.
Explanation: Information on the backup denoted by

the backup ID could not be found in the repository
located in the path indicated.
Could not access the repository at path

because it is currently locked by another
process.
Explanation: When starting up, the server tried to

load the repository located at the path named.
However, the repository was locked by a different
process. This can happen if two server processes try to
use the same repository. This is not supported.
User response: Make sure each instance of the server
uses its own repository.
BKI9316E
BKI9311E
Could not remove backup_id from the

repository at path.
Explanation: An attempt to remove the information

on the backup named from the repository located at the
path indicated failed.
BKI9315E
Could not add backup_id to the

repository at path.
Failed to update backup_id in the

repository at path.
The path path does not point to a valid

repository location.
Explanation: When starting up, the server could not

locate its repository.
appropriate.
User response: Make sure the repository path is set

correctly. If you need to correct the repository location,
restart the server executable afterwards. If the problem
BKI9312E
backup_id is currently locked in the

repository at path.
Explanation: The information on the backup denoted

by the backup ID is currently locked by a different
process. Make sure to run only a single operation using
a specific backup at a time.
User response: Wait for the other operation to finish
or abort this operation. Then start again. If the problem
983
984
Chapter 11. Data Protection for Snapshot Devices for mySAP

for DB2 UDB Version 5.4.1 (EEP0000EEP7999) and
(IDS0000IDS2999)
This chapter describes the messages issued by the components of Tivoli Storage
Manager for Advanced Copy Services: Data Protection for Snapshot Devices for
mySAP for DB2 UDB Version 5.4.1. The two components are:
v Data Protection for FlashCopy Devices for mySAP for DB2 UDB
v Data Protection for N Series Snapshot for mySAP for DB2 UDB
The messages begin with the prefix EEP or IDS and are listed in numerical order
within each prefix group.
Note: References to the term hardware unit should be understood as meaning SVC
cluster in the case of an SVC configuration.
Messages from splitint

Prefix EEP
EEP0020I
====>Performing DP for Snapshot

Devices <v1> command.
Explanation: This message is displayed starting the

specified function.
EEP0022I
attempted to withdraw the FlashCopy relationship

between the source and target volumes.
User response: Check the error log for details.
EEP0059E
AIX Version: <var1> Oslevel: <var2>.
Explanation: Displays AIX version and oslevel.

EEP0030I
Number of volumes involved in the

FlashCopy: <v1>
Explanation: Number of volumes to be processed by

FlashCopy.
EEP0056I
Received error errno while disabling

the new resources.
Explanation: An error occurred when the process

attempted to disable the resources obtained for
performing the DB backup.
EEP0058I
Received error errno while resetting

the target volumes.

The database was backed up using

NOCOPY type of FlashCopy. The data
in the target volumes is not valid, and
cannot be used to perform a FlashBack
Restore.
Explanation: In order to restore the database using

FlashBack Restore, the database needs to be backed up
using the COPY or INCR type of FlashCopy.
User response: Restore the database from TSM Server.
EEP0062E
The source/target LUN information in

the setup file has been modified.
FlashBack Restore is currently not
supported for restoring the database to a
new location.
Explanation: The source/target information in the

setup file cannot be modified. In order to back up the
database to different target LUNs, use a different setup
file. At this time, FlashBack Restore is only supported
for restoring the database to the original source LUNs.
User response: The source/target information in the
setup file cannot be modified. In order to backup the
file. If you want to restore the database to a new
location, restore it from the Tivoli Storage Manager
server.
985
EEP0065E EEP0125E
EEP0065E
IBM2105 Copy Service CLI is not

installed.
Explanation: The ibm2105cli.rte file is not installed.

lslpp -lc ibm2105cli.rte command failed.
User response: Make sure Copy Service CLI is
installed on your host machine.
EEP0068W
WARNING!!! Incremental Change

Recording is enabled. Performing
incremental FlashCopy instead of
NOCOPY type of FlashCopy.
Explanation: Incremental Change Recording is

enabled. Performing a NOCOPY type of FlashCopy will
fail in this case.
User response: Withdraw the persistent FlashCopy
relationship for all the source volumes for this
database, using the DP for Snapshot Devices withdraw
command, if you are interested in a NOCOPY type of
FlashCopy.
EEP0069W
WARNING!!! Incremental FlashCopy

feature is not supported on this version
of AIX: <v1>. A generic FlashCopy will
be performed instead.
Explanation: Incremental FlashCopy is only supported

on AIX versions 5.1.0 or later. As this version of AIX is
lower than 5.1.0, an incremental FlashCopy cannot be
performed.
User response: Upgrade to AIX version 5.1.0 or later
in order to take advantage of the Incremental
FlashCopy feature.
of backup or from target volumes to source volumes in

case of restore.
EEP0120E

determine a logical volume name from the list of
database files.
User response: Verify that the calling program has
passed the list of database files. Check for preceding
errors.
EEP0121E
Some of the volumes belonging to this

database have Incremental Change
Recording enabled while others do not.
Explanation: In order to perform an incremental

FlashCopy, all the volumes belonging to the database
must have Incremental Change Recording enabled.
User response: Withdraw the FlashCopy relationships
for those volumes that have Incremental Change
Recording enabled, using the DP for Snapshot Devices
withdraw command, and then retry the command. In
the case of the monitor command (FlashCopy agent),
withdraw the FlashCopy relationships and retry both
the backup and monitor (FlashCopy agent) commands.
In an SAP environment, you only need to retry the
backup, because the FlashCopy agent is started
automatically.
EEP0071I
Source volume: <v1> Target volume:

<v2> Pending Sectors: <v3>
Explanation: Displays the number of sectors yet to be

copied from source volumes to target volumes in case
986
A null volume group has been detected.

determine a volume group name from the list of
database files.
errors.
EEP0122E
An error is detected in volume group :

vg1.
Explanation: An error was returned from specified

volume group.
User response: Verify the target database information
is specified correctly in the setup file. Verify that the
AIX volume manager is running. If the problem
persists, gather information from the trace file and log
file and contact your IBM service representative.
EEP0123E
EEP0070E
A null logical volume has been detected.
The physical volumes of the volume

group <v1> were not found.
Explanation: DP for Snapshot Devices will issue the

command lsvg -M <vgname> in an LVM mirror
environment to determine the physical and logical
volumes on which the production database resides.
This command failed.
User response: Check the return code of lsvg. Consult
the AIX system documentation.
EEP0124I
Mounting filesystem : fs1.
Explanation: Currently attempting to mount the file

system.
User response: None
EEP0125E
The serial number for the device

logdev could not be found.
Explanation: DP for Snapshot Devices will determine

the volume serial numbers from the list of database
files passed. In order to do that, several system
commands will be used such as: lscfg -pvl devname or
EEP0126I EEP0139W
lsvpcfg or hdwmap.sh. One of these commands has
failed or the specified device was not displayed.
User response: Check the specific error message. Issue
the commands above from the command line and
check that the specified device is displayed in the list.
Consult the AIX system documentation.
EEP0126I
Trying to find new devices to match the

source device. This process will take
some time...
EEP0130W
Removing the mount point directory

<mntpt1> failed with rc: <rc1>.

remove a mount point. Processing continues.
EEP0131E
The physical volume ID <pvid1> is

duplicated on the production machine.
Explanation: Currently trying to find a target device

to match the source device.
Explanation: The output of the command lspv shows

that two logical devices (hdisk/vpath) have the same
physical volume id.
User response: Perform one of the following:
EEP0127I
v If the hdisks with the same pvid belong to the same

multipath, convert the hdisk device volume group to
a Subsystem Device Driver vpath device volume
group.
Removing device : devname
Explanation: DP for Snapshot Devices will remove the

logical devices from the Device Configuration database
(ODM) on the backup system after the backup has
ended and prior to withdrawing the relationships of
the volumes.
User response: None
EEP0128E
Configuring the target volume would

cause duplicate physical volume ID :
pvid1
Explanation: A different set of target volumes that

were previously associated with the same source
volumes was detected.
1. Delete the disk on the backup system only:
a. find the disk using the AIX lspv command
b. run smitty and choose the following from the
menu: devices- fixed diskremove a disk- select
the disk to be removed
c. press return
2. Clear the pvid of each physical volume hdisk by
issuing the AIX chdev command with the following
arguments: chdev -1 (hdisk#) -a pv=clear .
EEP0129E
Removing device parm1 failed.

(ODM) on the backup system after the backup ended
and prior to the withdraw of the relationships of the
volumes. The rmdev command has failed.
Consult the AIX system documentation. Check if the
device is a member of an active volume group. Check
for preceding errors.
v If the problem is the result of a corrupt ODM,

consult the AIX Troubleshooting documentation
v If the physical volume involved neither belongs to a
volume group nor contains file systems to be
imported in the future, you can clear the pvid by
arguments: chdev -l hdisk# -a pv=clear
EEP0132W
The umount command failed with rc

<rc> for mount point <mntpt>.

EEP0138I
FlashCopy type is set to NOCOPY.

Removing disk meta data for all target
disks.. This backup is NOT valid for a
FlashBack Restore. Please restore from
TSM Server.
Explanation: Target PVIDs are cleared. This process

removes disk metadata for all target disks. These target
volumes can now be used as targets for source volumes
from multiple databases. However, this backup is not
valid for a FlashBack Restore. You can only restore
from a TSM Server.
EEP0139W
Removing the file system on the mount

point <mntpt1> failed with rc: <rc1>.

remove a file system during the FlashBack Restore.
Processing continues. The restore will resolve this
problem.
Chapter 11. Data Protection for Snapshot Devices for mySAP for DB2 UDB
987
EEP0140I EEP0156I
EEP0140I
FlashCopy type is set to COPY or INCR.

Leaving disk meta data intact for all
target disks.. This backup is valid for a
FlashBack Restore.
Explanation: The target PVIDs are not cleared. This

process leaves disk metadata intact for all target disks.
This backup can be used for a FlashBack Restore.
EEP0143E
Unsupported volume group <v1> has

been detected.
Explanation: The volume group to which the database

has been allocated is an unsupported type.
User response: Make sure that volume group is not
rootvg.
EEP0146E
A physical disk from the volume group

vgname was not found.
Explanation: A physical disk from the specified

database volume group was not found in the Device
Configuration database.
Consult the AIX system documentation. Check if this
device is a member of one active volume group. Check
EEP0147I
Exporting volume group vgname

failed.

command exportvg prior to the withdraw of the
FlashCopy relationships to remove the volume group
from the Device Configuration database. This command
has failed.
Consult the AIX system documentation. Check for
preceding errors during the unmount of the file
systems.
EEP0150E
Logical Volume cannot be found for the

file fnm1.
Explanation: An error has occurred determining the

logical volume of a file in the list of database files.
EEP0151E
Varying off volume group vgname

failed.
Explanation: Prior to the withdraw of the FlashCopy

relationships, DP for Snapshot Devices will vary off the
database volume group on the backup system. The
command varyoffvg has failed.
preceding errors during the unmount process.
EEP0152I
Removing volume group fnm1 ....
Explanation: Attempting to remove the volume

groups.
EEP0153I
Varied off and exported volume group :

vgname
Explanation: The specified volume group was varied

off and exported successfully.
User response: None
EEP0154I
<lvname> <copy> <pv> <serialno>

<status>
Explanation: Finding the source volumes of the

production database in an LVM mirror environment,
DP for Snapshot Devices will display a list of all the
logical volumes with the number of copies, the physical
volumes, the serial number and the status. The status is
only displayed for the case of stale partitions.
EEP0148I
Importing volume groups now...
Explanation: Processing an importing volume group

command.
User response: None
EEP0149I
Newly imported volume group:

vgname
Explanation: DP for Snapshot Devices has successfully

imported this new volume group on the backup system
after the FlashCopy.
User response: None
988
EEP0156I
Finding the serial numbers ...
Explanation: DP for Snapshot Devices gets as input a

list of database files to be backed up and from them
determines the logical volumes, volume groups and
serial numbers of the physical volumes where the
production database resides.
User response: None
EEP0161E EEP0178I
EEP0161E
No volume group was found.
Explanation: The AIX command lsvg failed on the

backup system, and the newly added volume groups
after the FlashCopy could not be determined.
User response: Check the operating system error
issued by lsvg. Consult the AIX documentation.
EEP0162E
Volume group <vg1> cannot be found.
Explanation: The AIX commandlsvg failed on the

production system and the source volumes of the
production database could not be determined.
EEP0164E
Quorum of the volume group vgname

must be off.
Explanation: In a high-availability LVM mirror

environment, DP for Snapshot Devices requires that the
quorum of the volume group be set to off. If a mirror is
inactive due to a failure, the database should continue
working properly.
User response: Set the quorum of the volume group
off.
User response: Check why you have stale partitions.

If necessary, synchronize the logical volumes of the
production database.
EEP0172E
Explanation: Mirror write consistency ensures data

consistency among mirrored copies of a logical volume
during normal I/O processing. If a system or volume
group is not shut down properly, then mwc will
identify which logical partitions may be inconsistent.
DP for Snapshot Devices requires that this capability be
set for the logical volumes of the production database.
User response: Set mirror write consistency on.
EEP0174E
User response: You have to reconfigure the allocation

on the production system.
Logical volume vgname must have at

least 2 copies.
Explanation: If the parameter for working with LVM

mirrors is active, DP for Snapshot Devices requires that
two copies of each logical volume exist.
User response: Create a copy of each logical volume
on separate machines. Ensure that, for each source
volume, you have a target volume for the FlashCopy in
the same hardware unit.
EEP0168E
Logical volume lvname must have the

parallel scheduling policy.
Explanation: DP for Snapshot Devices requires the

parallel scheduling policy. With the parallel scheduling
policy, there is no primary or secondary mirror. All
copies in a mirror set are referred to as copies,
regardless of which one was created first.
User response: Set the scheduling policy of this logical
volume to parallel.
EEP0170W
Logical volume lvname has number

stale partitions.
Explanation: DP for Snapshot Devices first checks all

the logical volumes for stale partitions and initially
issues only a warning if it finds any. The mirror set that
resides in the hardware unit that was chosen for the
FlashCopy on this specific run must be free of stale
partitions.
None of the mirror copies of the logical

volume lvname resides completely on
the specified hardware unit identifier.
Explanation: DP for Snapshot Devices requires that all

the partitions of one mirror set reside on the physical
volumes of one hardware unit.
EEP0176E
EEP0166E
Logical volume lvname must have

mirror write consistency on.
Some of the partitions of lvname are

stale on the specified hardware unit
identifier.

partitions.
User response: Check the reason you have stale
partitions. Synchronize the logical volumes of the
EEP0178I
Could not determine the number of

paths to target volumes. Using default
value of 1.
Explanation: DP for Snapshot Devices supports SDD

(Subsystem Device Driver). SDD is a pseudo device
driver designed to support the multipath configuration
environments in the storage system and is used to
enhance data availability. DP for Snapshot Devices will
determine the number of multiple paths by querying
the Device Configuration database (ODM).
User response: If you want to take advantage of SDD,
check the Subsystem Device Driver Users Guide for a
correct configuration.
989
EEP0180E EEP0290E
EEP0180E
Failure in changing the mount point

mp, return code rc from command
chfs.

environment, DP for Snapshot Devices will use the
recreatevg command to create the volume groups after
the FlashCopy on the backup system. Because
recreatevg inserts the prefix /fs at the start of the
mount point, DP for Snapshot Devices must remove it
by calling the command chfs to the original names.
preceding errors.
User response: You have to reconfigure your

EEP0191I
Explanation: After the importvg or recreatevg, DP for

Snapshot Devices will vary on the database volume
group on the backup system. The command varyonvg
has failed.
preceding errors.
EEP0272I
EEP0182E
The same hdisk devname cannot be

associated with two different vpaths
(serial numbers serial#1 and serial#2).
Varying on volume group vgname

failed.
Flushing the buffers to disk...
Explanation: Currently synchronizing to force the

buffers to disk.
Explanation: DP for Snapshot Devices has

encountered a corrupted configuration in your system.
User response: None
User response: By issuing the command lsvpcfg you

can identify this error. Check the Subsystem Device
Driver Users Guide for a correct configuration.
EEP0273I
EEP0184E
lsvg command failed.
Explanation: DP for Snapshot Devices uses the

command lsvg to determine the physical and logical
volume of the volume group. This command has failed.
preceding errors.
Explanation: Currently attempting to unmount the file

system from the mount point.
User response: None
EEP0274I
Recreating the new volume groups...

the FlashCopy on the backup system.
User response: None
EEP0188E
lvm queryvg failed.
Explanation: DP for Snapshot Devices uses the system

routine lvm_queryvg to read information of the VGDA
of the volumes.
preceding errors.
EEP0190E
The number of new volume groups is

limited to 256.
Explanation: DP for Snapshot Devices can support a

database with a maximum of 256 volume groups.
990
Bringing up the volume groups...
Explanation: The new resources will be available after

the FlashCopy.
User response: None
EEP0275I
EEP0186I
Unmounting the file system mntpt1...
There are too many file systems.
Explanation: The number of file systems exceeds the

compiled limit of 4096.
EEP0290E
The source volume with serial number

serial # is no longer attached to the
production system.
Explanation: The specified physical volume was

found during the FlashCopy backup as part of the
database volumes on the production system. Now,
during the FlashBack Restore, it could no longer be
found on the production system.
User response: Logon with the user root and issue the
command lsvpcfg. Check if the volume is displayed.
Use the storage-system user interface to find out to
which host this volume is attached. You will be able to
restart the FlashBack Restore anytime, as long as you
have a valid disk backup on the target volumes.
EEP0291E EEP0302E
EEP0291E

serial # belongs to another volume
group.

during the FlashBack Restore, DP for Snapshot Devices
found it as a member of another volume group and
cannot proceed with the restore.
User response: You must remove this volume from
the other volume group if you want to use the
specified FlashCopy backup for the FlashBack Restore.
You will be able to restart the FlashBack Restore
anytime, as long as you have a valid disk backup on
the target volumes.
EEP0292W
The logical volume lvname on the

mount point mp was renamed or
newly added.
Explanation: DP for Snapshot Devices found a

difference between the names of the logical volumes
which were on the production database at the time of
FlashCopy backup and the current logical volumes at
the time of the FlashBack Restore.
User response: DP for Snapshot Devices will ask you
during the FlashBack Restore if you are sure you want
to continue, before all the file systems and logical
volumes are removed. After that, DP for Snapshot
Devices will only reconstruct the file systems which
were backed up with FlashCopy. You have to manually
add all the additional system changes that were made
after the FlashCopy backup.
EEP0293I
List of the current file systems on the

backed up volume groups ...
Explanation: Prior to the start of the FlashBack

Restore, DP for Snapshot Devices will display a list of
all the file systems which are currently on the
production database system.
User response: None
EEP0294I
List of file systems which will be

restored...

all the file systems that were on the production
database system at the time of the FlashCopy backup.
Snapshot Devices will call this command during the

FlashBack Restore to remove the physical volumes
added to the database volume groups after the
FlashCopy backup.
User response: None
EEP0299I
The following commands should be run

after the FlashCopy process in the
background is finished to synchronize
the LVM copies.
Explanation: DP for Snapshot Devices will not

automatically synchronize the copies after the
reconstruction of the LVM mirror. A basic command
will be created and displayed.
User response: You have to start the synchronization
of the LVM mirror manually after the FlashCopy
process in the background has finished. If necessary
you have to add additional parameters to the
commands to improve the performance of the
synchronization.
EEP0300E
Error converting the hdisk device

volume group vgname to a Subsystem
Device Driver vpath device volume
group.
Explanation: For the function FlashCopy backup, DP

for Snapshot Devices will use the command hd2vp to
convert the hdisk device volume group to a Subsystem
Device Driver vpath volume group. This will take effect
after the importvg and prior to the mount of the file
systems on the backup system.
User response: Check the return code and the error
message of the hd2vp command. Consult the AIX
system documentation.
EEP0301W
The rmlv command lv ended with

return code rc.
Explanation: For the function FlashBack Restore, DP

for Snapshot Devices will use the command rmlv to
remove the logical volumes onto which the production
database should be restored. This will take effect after
the unmount and prior to the exportvg and the actual
FlashCopy reverse.
message of the rmlv command. Consult the AIX system
documentation. You will be able to restart the
FlashBack Restore anytime, as long as you have a valid
disk backup on the target volumes.
User response: None

EEP0302E
EEP0297W
The newly added volume logdev will

be deleted from the database volume
group vgname.
Explanation: The reducevg command removes

physical volumes from a volume group. DP for
DP for Snapshot Devices encountered a

problem when using the FlashCopy
function of Copy Services.
Explanation: DP for Snapshot Devices requested, for a

set of source/target volume pairs, that a FlashCopy be
done by the Copy Services. If the request fails within
991
EEP0303E EEP0311W
the storage system with a non-zero return code for one
or more pairs, DP for Snapshot Devices will provide
the return code and then terminate.
User response: In order to identify which volume(s)
were the cause of the problem, you need to view the
Copy Services status log for failures. There, you will
find the failing volume(s) along with details about
possible causes of the problem.
EEP0303E
The file system fs already has an entry

in /etc/filesystems.
Explanation: On the backup system after the

FlashCopy, DP for Snapshot Devices found that the
specified file system still exists in /etc/filesystems.
User response: Normally the command exportvg will
remove the corresponding file systems from
/etc/filesystems. Check for errors during the
unmount and withdraw process.
EEP0304W
The reducevg command cmd ended

with return code rc.

Snapshot Devices will call it
1. on FlashBack Restore to remove the physical
volumes added after the FlashCopy backup
2. on FlashBack Restore with LVM mirroring to
remove the physical volumes which reside in the
hardware unit that is not yet involved in the
FlashBack.
3. on FlashCopy backup with LVM mirroring if the
environment variable IMPORTVG is set, to remove
the physical volumes which reside in the hardware
unit that is not yet involved in the FlashCopy
message of the reducevg command. Consult the AIX
EEP0305W
The extendvg command cmd ended

Explanation: The extendvg command adds physical

volumes to a volume group. DP for Snapshot Devices
will call it to add the volumes which reside in the
hardware unit that is not yet involved in the FlashBack
to the database volume groups.
message of the extendvg command. Consult the AIX
EEP0306W
The mklvcopy command cmd ended

Explanation: DP for Snapshot Devices will call the

command mklvcopy to add a copy of a logical volume
on the physical volumes residing in the second
hardware unit. This call will only take effect in an LVM
992
mirroring environment, after the FlashBack Restore was

initiated. The FlashBack Restore and the recovery will
continue, but the second copy of the logical volumes
will be missing.
message of the mklvcopy command. Consult the AIX
system documentation. Check for errors during the
disabling process (unmount, rmfs, rmlv, varyoffvg,
exportvg). You will be able to restart the FlashBack
Restore anytime, as long as you have a valid disk
backup on the target volumes.
EEP0307I
Removing copies from the logical

volumes ...

for Snapshot Devices will use the command rmlvcopy
to remove the copies of the logical volumes residing in
the second hardware unit. This will take effect after the
unmount and prior to the exportvg and the actual
FlashCopy reverse.
User response: None
EEP0308I
Removing physical volumes from the

volume groups ...
Explanation: For the function FlashBack Restore, after

the rmlvcopy and prior to the exportvg and the actual
FlashCopy reverse, DP for Snapshot Devices will use
the command reducevg to remove the physical
volumes residing in the second hardware unit.
User response: None
EEP0309I
Adding physical volumes to the volume

groups ...
Explanation: On the function FlashBack Restore, after

the FlashCopy reverse and the import of the volume
groups, DP for Snapshot Devices will add the physical
volumes residing in the second hardware unit to the
database volume groups.
User response: None
EEP0310I
Adding copies to the logical volumes ...
Explanation: On the function FlashBack Restore, DP

for Snapshot Devices will use the command mklvcopy
to add the copies of the logical volumes on the second
hardware unit. This will take effect after the importvg
and the extendvg.
User response: None
EEP0311W
The command cmd ended with return

code rc.
Explanation: The execution of the system command

ended with the displayed return code.
EEP0312E EEP0321E
message of the specified command. Consult the AIX
EEP0312E
Importing the volume group from hdisk

logdev failed.
Explanation: DP for Snapshot Devices will use the

command importvg on the function FlashCopy backup.
This command will be issued on the backup system
after the actual FlashCopy and the run of the
configuration manager (cfgmgr). It takes a volume from
each volume group making up the production
database, reads its VGDA and makes this information
available to the operating system.
message of the importvg command. Consult the AIX
EEP0313E
Recreating the volume group from the

hdisks hdisks failed.

command recreatevg for the function FlashCopy
backup if the production database resides in a
high-availability LVM mirror environment. This
command will be issued on the backup system after the
actual FlashCopy and the run of the configuration
manager (cfgmgr). The difference from the command
importvg is that recreatevg will create the volume
group only with the specified volumes. These form
exactly the one copy on the hardware unit where the
FlashCopy was issued.
message of the recreatevg command. Consult the AIX
EEP0314W
Removing the logical device logdev

with the same PVID pvid in the ODM.
Explanation: There is still a logical device (hdisk or

vpath) in the state defined with the same PVID as one
of the source volumes.
User response: None
EEP0315I
Could not mount all the filesystems

originally present.
Explanation: This message will appear if, when

running the function FlashBack Restore, a file system
was found that was added after the FlashCopy backup.
User response: The user is responsible for creating the
new file system after the FlashCopy reverse, but before
the recovery, if this file system was already used from
the production database.
EEP0316W
The database volume groups do not

currently contain any file system.

running the function FlashBack Restore, no file system
was found on the original database volume group.
Following this, DP for Snapshot Devices will display a
list of the file systems that reside on the FlashCopy
target volumes. These will be restored by means of
FlashBack.
EEP0317W
One or more errors were found

disabling the production system
resources. However, the FlashBack
Restore will continue.

running the function FlashBack Restore, an error occurs
unmounting the existing file systems and removing the
volume groups. However, DP for Snapshot Devices will
continue with the FlashBack Restore.
EEP0320E
Although the pvid <pvid> is contained

in the descriptor area of the volume
group <vgname>, no logical device
(hdisk/vpath) has this on the production
system.

that no physical volume hdisk/vpath exists with this
pvid, although the pvid was found on the descriptor
area of the volume group.
User response: You very likely have an ODM
corruption for the involved volume group. Check this
volume group with the command lsvg -l <vgname>
and lsvg -p <vgname>. Depending on the error, you
have to take different actions. Consult the AIX
troubleshooting documentation to repair the ODM.
EEP0321E
Physical volume <hdisk> is in the

descriptor area of the volume group
<vgname> but does not belong to this
volume group.
Explanation: The output of the command lsvg -p

<vgname> does not show that the hdisk/vpath belongs
to this volumegroup, but its pvid is registered in the
descriptor area of the volume group.
User response: If the hdisks with the same pvid
belong to the same multipath, convert the hdisk device
volume group to a Subsystem Device Driver vpath
device volume group. If you have ODM corruption,
check the involved volume group with the command
lsvg -l <vgname> and lsvg -p <vgname>. Depending
on the error, you have to take different actions. Consult
the AIX troubleshooting documentation to repair the
ODM.
993
EEP0322W EEP0332I
EEP0322W
The major number of the volume group

<vgname> could not be determined.
Explanation: The command getlvodm, which is used

to determine the major number of the specified volume
group, failed. The option -V of the command
importvg will not be used on a FlashBack Restore of
this backup.
User response: Check for error messages issued by
getlvodm.
EEP0323W
Major number major already exists on

the production machine. The system
will assign the next available major
number to the volume group vgname.
EEP0327E
Error freezing the file system fsname:

txtmsg.
Explanation: The function FREEZE failed for this file

system.
System action: Check the specific error reported by
the operating system, which is appended to this
message.
EEP0328E
Error thawing the file system fsname:

txtmsg.
Explanation: The function THAW failed for this file

system.
Explanation: DP for Snapshot Devices found that the

major number of the given volume group is being used
by another device. The importvg command will be
issued without the option -V <major number>. The
system will then generate the next available major
number automatically.

message.
User response: Check the major numbers on the

system with the command ls -al /dev.
EEP0329I
EEP0324E
Production database does not reside in

an LVM mirror environment.
Explanation: The LVM mirroring capability of DP for

Snapshot Devices is on, but the database logical
volumes do not have a mirror copy.
User response: Set the parameter for LVM mirroring
off, or set up your system in a high-availability LVM
mirror environment.
EEP0325E
Error reading the status information of

the file system fsname: txtmsg.
Explanation: The system call 'stat' failed. Check the

specific error message appended to this message. In
some cases the user will need administrator rights to
execute this command.
Ensure that the user has sufficient rights.

Freezing file system : fs1.
Explanation: Currently attempting to freeze the file

system.

EEP0330I
Thawing file system : fs1.
Explanation: Currently attempting to thaw the file

system.
EEP0331I
Performing snaprestore of the source

volume srcvol to the snapshot snapid
(LUN lunpath).
Explanation: The function 'snaprestore' will revert the

source volume to the specified snapshot name. This
message will appear for each LUN involved in the
restore process. The snap restore is performed based on
the volume.
EEP0326W
The file system fsname is not of type

jfs2. The freeze/thaw function will be
applied only on file systems of type
jfs2.
Explanation: The freeze/thaw function will be applied

only on file systems of type jfs2.

EEP0332I
Performing snapshot of the source

volume srcvol (LUN lunpath).
Explanation: A snapshot will be taken of this volume.

This message will appear for each LUN involved in the
snapshot process. However, when several LUNs belong
to the same volume, only one snapshot of this volume
is taken.
994
EEP0333I EEP0358E
User response: None
EEP0333I
EEP0354I
The snapshot snapid was generated for

the source volume srcvol (LUN lunpath).
Explanation: A snapshot with the name displayed was

taken from this volume. This message will appear for
each LUN involved in the snapshot process. However,
when several LUNs belong to the same volume, only
one snapshot of this volume is taken.
EEP0350E
Error to get the size of the target volume

src1 with return code rc1.
Explanation: The storage-system query command

cannot determine the size of the target volume.
User response: Issue a query command from the Copy
Services Web Interface to verify that the disk exists. If
the problem persists, save the diagnostic information
and contact IBM service.
EEP0351E
The sizes of source volume src1 and

target volume tgt1 are different.
Explanation: The sizes of the source volume and

target volume are different. The source volume and
target volume must be the same size and reside in the
same hardware unit.
EEP0352E
Wrong volume size for the target

volume tgt1 is specified in the setup
file.
Performing <fctype> FlashCopy of

source volume <src1> to target volume
<tgt1>
Explanation: A FlashCopy from the source volume to

the target volume was requested.
EEP0355E
The FlashCopy command failed.
Explanation: The FlashCopy command failed. This

could be due to various reasons:
1. Some library or jar files may be missing from the
Copy Services command line interface package.
2. The source volumes or target volumes are in
another FlashCopy relationship.
3. The Copy Services command line interface package
and Copy Services microcode are not in sync.
User response: If the command line interface package
is missing files, install the command line interface
package again. If the source volumes or target volumes
are in another FlashCopy relationship, wait until the
concerned volumes exit the relationship or use other
target volumes. If the command line interface package
and Copy Services microcode are not in sync, check
with the storage system administrator to obtain the
appropriate level of Copy Services command line
interface and microcode.
EEP0356E
Cannot find a target volume to match

the source volume parm1.
Explanation: A target volume could not be found.

User response: Make sure that the target volumes are
available to the backup system and that the syntax is
correct for the following parameters:
1. TARGET_VOLUME
2. PRIMARY_COPYSERVICES_SERVERNAME
3. COPYSERVICES_USERNAME
Explanation: The TARGET_VOLUME parameter specifies

an incorrect size for the target volume.
EEP0357I
User response: Make sure the parameter in the setup

file specifies a correct size for the target volume. If you
do not know the exact size of the target volume,
specify a dash (-) for both the source value and size
value. The size of the target volume will be determined
automatically.
Explanation: A FlashCopy withdraw of the source

volume from the target volume was requested.
EEP0353E
Explanation: An error was detected when trying to

open the file. The file may not exist.

EEP0358E
Unable to open file file1.
Performing FlashCopy withdraw of

source volume <src1> from target
volume <tgt1>
No target volume is available.

Terminating......
Explanation: No target volume was found.

1. TARGET_VOLUME
995
EEP0359I EEP0376E
Explanation: Value of Incremental Change Recording.
Explanation: Whenever the user performs an

incremental FlashBack Restore operation, the source
and target volumes will be reversed.
EEP0360I
EEP0368I
EEP0359I
Incremental Change Recording: <val1>
Querying the storage system for the size

of volume volser1...
The backup Copy Services server is

ready...
Explanation: A query of the target volume was

requested.
Explanation: The backup Copy Services server is

ready.
User response: None
User response: None
EEP0361I
EEP0371I
A NOCOPY FlashCopy was performed.

Withdrawing the NOCOPY FlashCopy
relationship
Explanation: The FlashCopy relationship between the

source and target volumes terminates after the
NOCOPY FlashCopy is performed.
Explanation: None.
EEP0372I
User response: None

EEP0362I
Checking the status of the primary Copy

Services server...
Explanation: Currently verifying the primary Copy

Services server status.
User response: None
EEP0363I
Primary Copy Services server is ready.
Explanation: The primary Copy Services server is

ready.
Value of FlashCopy type is: <parm1>.
A primary Copy Services server has not

been specified.
Explanation: The primary Copy Services server is not

defined in the setup file. An attempt to use the backup
Copy Services server is made.
User response: None
EEP0374I
Querying the storage system for the

status of volumes volser1...
Explanation: A query of all the source and target

volumes was requested to ensure that they are not
involved in a FlashCopy or PPRC operation.
User response: None

EEP0375E
EEP0365I
Checking the status of the backup Copy

Services server...
Explanation: Currently verifying the backup Copy

User response: None
EEP0366I
FlashCopy was performed with

<parm1> option.
Explanation: This is the type of FlashCopy that was

actually performed. It may be different from the value
specified by the user, since DP for Snapshot Devices
overrides this value under certain conditions.
EEP0367I
996
Source and target volumes have been

switched due to a previous incremental
FlashBack Restore operation. Previous
target volume: <parm1> is now the
source volume. Previous source volume:
<parm2> is now the target volume.
Error: Volumes are involved in a

FlashCopy or a PPRC operation.
Explanation: Source or target volumes are involved in

a FlashCopy or a PPRC operation. FlashCopy backup
or restore command will not be performed.
volumes are not in use in a FlashCopy or PPRC
operation, before issuing the FlashCopy backup or
restore command.
EEP0376E
Error: target volume v1 involved in the

previous backup does not exist in the
setup file.
Explanation: The list of target volumes specified in

the setup file for restoring a specified database using
FlashBack Restore needs to be the same as those
specified in the setup file at the time of FlashCopy
Backup. This is necessary to ensure that a complete
image of the database is available to the restore
process.
User response: Ensure that the target volumes
specified in the setup file are accurate.
EEP0380E EEP1625I
EEP0380E
An invalid value: <parm1> has been

specified for FlashCopy type.
EEP0648E
Explanation: FlashCopy type can only be NOCOPY,

COPY or INCR.
User response: Specify NOCOPY, COPY or INCR for
the option FlashCopy type and retry the command.
EEP0381I
Querying storage system for pending

sectors for volume: <volser1>

volumes was requested to ensure that a background
copy is not in progress between them.
Explanation: None.
EEP0649E

EEP0400E
Error on running command: parm1
Explanation: An error was detected while running a

system command.
User response: Gather log file information and contact
your IBM service representative.
EEP0630E
A memory allocation error has occurred.
Explanation: Not enough memory was available to

applications.
EEP0640E
Could not open trace file <v1>.
Explanation: There were some problems opening

tracefile. Make sure you can open the trace file which
was specified in the setup file.
Could not create the trace object.
Explanation: There was a problem creating the trace

class object.
EEP0647E
Error while querying volume properties

of volume <volume name>. Please
verify that the volume specified in the
target volumes file exists.
Explanation: The volume information of <volume

name> cannot be found in the copy services
configuration. This can be the result of a typographical
error for the specified volume in the target volumes file
(.fct). This error can also occur if the specified storage
hardware unit cannot be found in the current copy
services configuration.
User response: Verify that the volume <volume
name> specified in the target volumes file exists. In
case of ESS 800, DS6000 or DS8000, verify the CIM
Agent configuration with the command
/opt/IBM/cimagent/verifyconfig u <CIM user>
-p <CIM user password>
If the specified storage hardware unit is not found in
the CIM Agent configuration, contact CIM Agent
support.
EEP0651E

EEP0641E

TSM function name : function-name
TSM function : function-desc
TSM return code : TSM-rc
TSM file :
A FlashCopy background copy is in

progress between source volume: source
volume and target volume: target volume.
Explanation: A FlashCopy background copy from a

and target volumes.
System action: The command will fail.
User response: Wait until the background copy is
complete and retry the command.
A FlashCopy association exists between

source volume: source volume and a
different target volume: target volume.
Explanation: A FlashCopy association exists between

System action: The restore command will fail.
User response: Withdraw the FlashCopy association
between the source and target volumes and retry the
restore command.
EEP1625I
Number of volumes to be processed by

FlashCopy: v1

FlashCopy.
997
EEP1626E EEP1650E
EEP1626E

processing a Tivoli Storage Manager for
Advanced Copy Services function.
TDP function name : function-name
TDP function : function-desc
TDP return code : TSM-rc
TDP file : filename (line-number)
Explanation: None.
User response: Contact the TDP administrator with
EEP1627E
Explanation: The specified virtual disk was not found

in the list of virtual disks provided by the connected
SVC cluster.
EEP1631E

applications.
EEP1635I


virtual disks are in the same SVC cluster.
EEP1629E


virtual disks have the same size.
EEP1630E

operation of the Common Information
Model (CIM).
TDP CIM return code: 0xCIM-rc
Explanation: An error occurred calling a CIM

User response: See CIM Agent Return Codes (SVC)
in Data Protection for Snapshot Devices for mySAP
Installation and Users Guide for DB2 UDB for possible
values of CIM-rc.
998
The ONTAP filer version on this

appliance is: n.
Explanation: None.
System action: Process continues.
EEP1636I

the SVC cluster.
EEP1628E

The option fractional reserve on volume

vol_name was reduced to less than 100
percent.
Explanation: When using N series devices, it is

strongly recommended that, when the fractional reserve
is set to less than 100%, you actively monitor space
consumption and the rate of change of data on the
volume to ensure you do not run out of space reserved
for overwrites. In this case, if you run out of overwrite
reserve space, writes to the active file system fail and
the host application or operating system might crash.
System action: The process continues.
User response: Ensure that you monitor the space
consumption. Consult the NetApp vendor for tools to
monitor available space on your volume.
EEP1650E
The execution of command lscfg failed.

Please verify that the command tset -I
-Q is not set in the user's environment
files .profile, .login,
.dbenv_<hostname>.sh,
.dbenv_<hostname>.csh, and
.sapenv_<hostname>.sh,
sapenv_<hostname>.csh.
Explanation: If the command tset -I -Q is set in the

user's environment files .profile,
.dbenv_<hostname>.sh, and .sapenv_<hostname>.sh,
the command lscfg will fail with the output Not a
terminal and will not return any configuration. This
will cause the DP for Snapshot Devices script
hdwmap.sh to fail.
User response: Ensure that the command tset -I -Q is
not set in the user's environment files .profile,
.dbenv_<hostname>.sh, and .sapenv_<hostname>.sh.
EEP2051W EEP2060W
EEP2051W

found on location.

period of time to proceed. In the mySAP environment,

that time is 1 hour.

be built in the specified directory.
EEP2052E

missing.

subsystem.



messages.
EEP2058E

error messages.
EEP2053E
EEP2057E


corresponding properties. A failure occurred during
that process.
such as memory allocation error or other system error.

applications.
EEP2054E

unexpected-message error during the execution of a
EEP2055I

be locked.

application unlocks the local repository.
EEP2056I
EEP2059W
Explanation: During a FlashCopy backup, TSM for

Advanced Copy Services tries to find a target data
container that matches the source data container to
satisfy the FlashCopy backup. A matching target data
container could not be found.
User response: See the rules for selecting one of
multiple target data containers. For example, this
message will be displayed if the user is trying to start a
FlashCopy backup of type INCR and all the target sets
are being used for the FlashCopy type COPY. Make
sure also that the target volumes are available to the
backup system and the syntax is correct for the
following parameters:
1. TARGET_VOLUME
EEP2060W

application.
Explanation: While the local repository is locked by


matches the source data container.

container dcID to match the source srcvol.

the specific source no target volume could be found in
this target data container that matches for a FlashCopy
operation. If multiple target data containers are being
used, the processing will continue checking the
volumes of the next target data container.
999
EEP2061W EEP2070E
EEP2061W

Explanation: An inquiry of the data container with the

set does not exist in the local repository.
System action: Processing may continue. The
application that is requesting the inquiry will decide
whether or not the error should end the program.
User response: Check for succeeding messages.
EEP2066E

permissions for the file.
EEP2067E


EEP2062W

criteria.

application will decide whether or not the warning
application specific. Check for succeeding messages.
EEP2063W


EEP2064I


being created.
EEP2065I


User response: Look for an operating system error
message.
1000

EEP2068E

Explanation: The program will search in the .fct file,

for each specific data container, for a list of entries with
the label TARGET_VOLUME. Either you have an
incorrect label for the target volumes of the specified
data container or this data container in the .fct file does
not have any target LUNs.
User response: This error can only occur if the
format will be automatically checked. If so, please
EEP2069E


permissions of the file.
EEP2070E

empty or has an incorrect format.

in not correct.
format of this file is correct. Check for a preceding
error.
EEP2071E EEP7826E
EEP2071E


Inserting an entry for a new data container caused an
error.
preceding error. If no other error is indicated, collect
the logs and traces and contact support.
EEP2730E
The primary and secondary Copy

Services servers are down.
Explanation: None.
User response: Start at least one of the Copy Services
servers.
EEP2731E
Cannot open the command output file

v1 for writing.
Explanation: The file cannot be opened for writing.

EEP2072E

processing a TSM for Advanced Copy
Services function.
Explanation: None.

your system and write permissions to the file.
EEP2732E

writing.

generated an error.
Explanation: None.
User response: Release LUNs in order to reuse them.

EEP7366E
User response: Check the permissions of the file.

Lun ID v1 is not valid.
Explanation: Length of LUN ID must be 8 characters.
Unable to close trace output file filename.

trace output filename (for example, not enough disk
space).
User response: Check the specific operating system
error message.
EEP7367E
EEP2727E
The LUNs are already in use.
EEP2073E

Tracing disabled.

User response: Ensure the device for the tracefile is
available and has sufficient space for the file. Retry the
command.

User response: Make sure the length of the LUN ID is
8.
EEP2729E

failed; rc=rc.
Explanation: None.
EEP7826E

<filename>.
Explanation: The DP for Snapshot Devices user does

not have permission to open the specified trace file.
User response: Check the access rights for the
directory of the specified trace file.

1001
Prefix IDS
IDS0064E
The parameter <parameter_name> in the

topic <topic_name> of the profile <.fcs
filename> is not known.
Explanation: In the section <topic_name> of the setup

file .fcs, a parameter was found that is not supported
by DP for Snapshot Devices.
User response: Remove the cited parameter from the
.fcs file.
IDS1000E
Profile not specified
Explanation: DP for Snapshot Devices cannot locate

the profile.
User response: Ensure that a profile is available. Note
that the splitint call must have the following form:
<path>/splitint -p <path>/init<SID>.fcs -f
<function>....
IDS1001E
Function not defined
Explanation: An invalid argument has been specified

for the -f option of DP for Snapshot Devices.
User response: Ensure that you pass a valid function
name with the option -f. Valid functions are: withdraw,
flashcopy, password, unmount, inquire, ts_inquire, and
query.
IDS1004E
Subfunction not defined.

for the -s option of DP for Snapshot Devices. This
option has been designed for internal splitint use only
and should not be used externally.
User response: Do not use the -s option with the
splitint call.
IDS1005I
Start of splitint program at: time.
User response: Set the parameter <keyword> and its

value in the profile for DP for Snapshot Devices.
IDS1009E
Directory path <path> for the IDS

control file does not exist.
Explanation: Either the entry for the parameter

IDS_CONTROL_FILE is incorrect or the path does not
exist.
User response: Ensure that the parameter
IDS_CONTROL_FILE in the profile has a valid path. If
the path does not exist, you must create it.
IDS1010E
Option -i <backup_list> not specified.
Explanation: The function -f getresources requires the

specification of the option -i <backup_list> too.
User response: Ensure that you transfer the list of the
files to back up when you call the function -f
getresources. Note that the splitint call must in this case
have the following form: <path>/splitint -p
<path>/init<SID>.fcs -f getresources -i <backup_list> ...
IDS1011E
Option -f <function> not specified.
Explanation: splitint always requires the option -f

<function> with a valid function.
User response: Ensure that the splitint call has the
following form: <path>/splitint -p
<path>/init<SID>.fcs -f <function>....
IDS1014I
<subsystem message>
Explanation: DP for Snapshot Devices received an

information message from the IDS subsystem.
IDS1015I
Start of splitint program at <timestamp>
Explanation: DP for Snapshot Devices started at time.
Explanation: Reports the activation of splitint.
IDS1007I
End of splitint program at: time.
Explanation: DP for Snapshot Devices ended at time.

Control will be returned to either the shell or to
tdphdwdb2 when splitint was called by tdphdwdb2.
IDS1015W
<subsystem message>
Explanation: DP for Snapshot Devices received a

warning message from the IDS subsystem.

IDS1016E
IDS1008E
Parameter <keyword> in the profile file

required.
Explanation: The parameter <keyword> in the profile

for DP for Snapshot Devices could not be found. It
must be defined.
1002
<subsystem message>

error message from its IDS control part.
User response: See the subsystem error messages for
more information and perform required action.
IDS1020I
The FlashBack Restore ended

successfully.
Explanation: The high-performance restore issued

with the FlashCopy from the target volumes to the
source volumes was completed successfully.
IDS1030I
FlashCopy started ...
Explanation: The command with the flashcopy

function has been issued on the production system, and
the program splitint waits until this action has finished.

IDS1031I
IDS1023I
Exiting with return code <rc>.
Explanation: The splitint program issues this message

on terminating. The program returns the value 0 if
successful, or nonzero if the execution of the called
function failed.
User response: If the called function has failed, check
for previous error messages.
IDS1024I

function failed.
IDS1025I
Time stamp: <current_time>
Explanation: DP for Snapshot Devices performs

several tasks in sequence (e.g. initiate the FlashCopy of
source volumes on the production system and mount
file systems on the backup system). Tracking the
various time stamps allows analyzing how long each
task took.
IDS1026I
Start of splitint on the production

system ...
Explanation: DP for Snapshot Devices has issued a

call to the production system and is waiting for the end
of the execution.
IDS1027I
Explanation: The command for the FlashCopy of the

volume pairs has terminated successfully on the
production system.
IDS1032W
Information from DP for mySAP was

not found.
Explanation: The exchange data between DP for

Snapshot Devices and DP for mySAP was not found.
The information is exchanged through the call of the
DP for Snapshot Devicess function set_bki_info by
backint prior to the Tivoli Storage Manager backup. For
older versions, the information is first exchanged after
the Tivoli Storage Manager backup during the
execution of the unmount function. Either the DP for
mySAP you have installed does not support DP for
Snapshot Devices, or DP for mySAP has failed after a
successful FlashCopy and mount.
User response: Check the run logs of tdphdwdb2.
This error could have various reasons and should be
resolved depending on the specific situation:
Case 1: tdphdwdb2 has finished successfully.
Result: The backup on disk (FlashCopy target volumes)
as well as the one done to the TSM server are valid.
However, DP for Snapshot Devices cannot show the
backup ID in its report when using the function
inquire.
Reason for warning: It is very likely that DP for mySAP
(AIX version) does not have DP for Snapshot Devices
support (prior to version 3.1.0.3).
Action: Install the appropriate DP for mySAP version.
Case 2: tdphdwdb2 has terminated abnormally.
splitint ended on the production system

successfully.
Explanation: DP for Snapshot Devices has ended the

call to the production system successfully.
IDS1028E
FlashCopy successful.
splitint ended with errors on the

production system.
Explanation: The remote exec call to the production

system has ended with errors.
Result: Check carefully the run log of tdphdwdb2 for

any BKI, ANS or ANR error messages. Most likely, the
backup on disk (FlashCopy target volumes) is valid
(check with splitint -f inquire whether PSI is
PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but
the backup to the TSM server is invalid.
Cause: Problems with the network or on the TSM
server caused DP for mySAP to fail when running a
backup.
Action: Depending on the error message, eliminate the
reason for not getting a successful backup to the TSM
server.

1003
IDS1033I
Information from DP for mySAP has

been found with BACKUPID
<backupid>.

mySAP and DP for Snapshot Devices has been found
during the execution of the function unmount. The
backups on disk (FlashCopy target volumes) as well as
to the Tivoli Storage Manager server are valid. The list
of files has been saved in the Tivoli Storage Manager
with the backup ID <backupid>.
IDS1034E
Entry <field_name> in the current

backup cycle of the IDS control file is
missing.
User response: Contact Data Protection for mySAP

support.
IDS1041W
The value of the field field_name in

the file file_name is empty.
Explanation: The program tdphdwdb2 updates the

IDS repository after the Tivoli Storage Manager backup
but also in case of a disk-only backup. A temporary file
is created with the following format:
>>>
BID
UTL
INF
EBC
EBB
EBR
<<<
backint_data
<backup id>
<name of the application profile used>
<EEE or ESE backup ID>
<log directory>
<backup type>
<first active log>
backint_data
Explanation: The field with the name <field_name> in

the current backup cycle was unexpectedly empty.
User response: Check for preceding errors.
IDS1035I
The IDS control file exists and a new

backup cycle entry has been created.
Explanation: At the start of the function -f

getresources, DP for Snapshot Devices 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. FlashCopy target volumes/file
systems being mounted or unmounted).
IDS1038I
The IDS control file <ids_control_file>

does not exist. It will be created.
Explanation: DP for Snapshot Devices will write the

first record to the IDS control file specified in the entry
IDS_CONTROL_FILE of the profile.
>>> input_file
<file list>
<<< input_file
If one of the fields of the topic backint_data is empty
(missing), this message is displayed. If the backup ID is
empty, the process terminates with error IDS1036E.
IDS1042W
Info data from DP for mySAP

/tmp/bki<SID>.ids cannot be read.
Explanation: Before the unmount process, DP for

Snapshot Devices will read /tmp/bki<SID>.ids, which
contains information about the backup that was done
by DP for mySAP. Among the information read is:
v Backup id
v Util file used for the backup
v List of files used for the backup
v Backup type
IDS1039E
This message will be issued if DP for mySAP

terminated unsuccessfully for some reason.
The IDS control file has no entry.
Explanation: DP for Snapshot Devices has found the

IDS control file, but it has no records. This error occurs
when you start one of the functions inquire, withdraw
or unmount before you have run the flashcopy
function for the first time.
User response: Ensure that DP for mySAP runs

successfully.
User response: After you run at least one tdphdwdb2

with a successful FlashCopy, the problem will be
resolved.
Explanation: The maximum number of backups

controlled via the parameter BACKUP_MAX will be
exceeded with the new inserted record. If the
parameter is not set, the program will use the default
value of 30.
IDS1040E
The IDS control file must be read or

inserted before update.
Explanation: DP for Snapshot Devices has detected a

logical error when processing the IDS control file.
1004
IDS1043I
The maximum number of backup cycles

in the IDS control file has been reached.
IDS1044I
Delete backup cycle with BSEQ_N =

<bseq_n> and all associated files ...
Explanation: Since the maximum number of records

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
that backup cycle will be deleted.
Directory path <directory> for the report

files does not exist. Using the current
directory.
Explanation: The directory entry of the parameter

LOG_TRACE_DIR in the profile could not be found.
The current directory will be used for the log and trace
files.
User response: In order to avoid directories cluttered
with reports and traces, the parameter
LOG_TRACE_DIR should be used, or the directory it
specifies must be created if necessary.
IDS1046I
User response: Ensure that you install the same

version of DP for Snapshot Devices on the production
and backup systems. You get the version number when
you start splitint without parameters.
IDS1051I

IDS1045W
on the production system is different from the version

on the backup system.
Start of listing of importing volume

groups/mounting file systems ...
Explanation: After initiating the FlashCopy

source/target volumes on the production system, DP
for Snapshot Devices will make the corresponding
target volumes available to the backup host. A list of
mount points or volume groups will be shown.
Enter the password for the user <user

ID>
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
this user ID and password have to be the same on the
production and backup systems. The DP for Snapshot
Devices program splitint uses the user ID to execute a
remote shell on the production system.
corresponding user ID.
IDS1052I

ID> again

IDS1053I
The password entry does not match,

please try again
Explanation: The two entered passwords are not

identical. You must enter the password again.
IDS1047I
User response: Enter the password again. You are

permitted three attempts before the program
terminates.
End of listing.
Explanation: Corresponds to start message IDS1046I.

IDS1048I
IDS1054E
The unmount process will be skipped

because the progress status indicator
(PSI) has a value of psi.
Explanation: When the withdraw function is started,

the unmount process will be performed only if the PSI
has a value of PSI_MOUNT_STARTED or
PSI_MOUNT_DONE.
User response: The table Possible Progress Status
Indicator (PSI) Values in Data Protection for Snapshot
Devices for mySAP Installation and Users Guide for DB2
UDB shows the permissible functions depending on the
backup progress status indicator.
IDS1050E
The version of the splitint program

must be the same on the backup and
production systems.
Explanation: The version of DP for Snapshot Devices
No password stored.

identical. You have tried three times, and the
passwords were different in each case.
User response: You must start the splitint program
with the function -f password again. If no password is
stored, or it is invalid, splitint fails when the flashcopy
function is used.
IDS1055E
The config file named <config_file>

could not be opened. Please call splitint
with the password function to create
that file.
Explanation: DP for Snapshot Devices is unable to

read the configuration file <config_file>.
User response: This error could have various reasons.
Try the following:
1. Call splitint with the password function to create
the file.
1005

CONFIG_FILE).

IDS1063E

correctly.
IDS1056E
The information of DP for mySAP could

not be set in the IDS repository.
Explanation: After the mount of the file systems on

the backup system was finished, the call of DP for
mySAP (backint) takes place. Backint then calls DP for
Snapshot Devices with the function -f set_bki_info to
set the Tivoli Storage Manager backup ID and other
information. This information is mandatory for using a
FlashCopy backup for restore. This information could
not now be set.
User response: Ensure that you have the version of
backint compatible for FlashBack Restore.
IDS1057E
No target set entries were found in the

IDS repository.
Explanation: The target set entries in the IDS

repository are generated automatically from the entries
configured in the .fct file (set of target volumes). This
happens during the FlashCopy backup.
User response: Check the .fct file (set of target
volumes). Check the parameters IDS_CONTROL_FILE
(IDS repository) and VOLUMES_FILE (.fct file).
IDS1060I
Start of listing of exported volume

groups/unmounting file systems ...
Explanation: A list of unmount points or exported

disk groups will be shown. Due to the use of the
unmount function on the backup host, DP for Snapshot
Devices will unmount the file systems and export
volume groups on the backup host that had been
imported or mounted when the DP for Snapshot
Devices flashcopy function was executed.
IDS1061I
Start the withdraw of the target-source

pairs ...
Explanation: The command with a withdraw has been

issued from the backup system to the primary Copy
Services server for the storage system.
IDS1062I
The progress status indicator (PSI) is

already PSI_UNMOUNT_DONE.
Explanation: DP for Snapshot Devices has been called

with the function withdraw or unmount, but the PSI
value of the latest backup cycle was already updated to
PSI_UNMOUNT_DONE in a previous splitint call.
1006
Parameters LOGON_HOST_PROD/
LOGON_HOST_BACK in profile wrong
or missing.
Explanation: Either DP for Snapshot Devices is unable

to read one of the parameters LOGON_HOST_PROD or
LOGON_HOST_BACK from the profile, or the
parameter values are incorrect. Note that these
parameters must have the following format:
LOGON_HOST_PROD <hostname/TCP name> <user
ID>
LOGON_HOST_BACK <hostname>
The host names must match the respective host names
of the production and backup systems. The TCP/IP
address will be used for the communication between
the two systems. The user ID specified must match the
DB2 user ID (db2<sid>).
User response: Ensure that the profile contains valid
entries for LOGON_HOST_PROD and
LOGON_HOST_BACK.
IDS1064E
The parameter <keyword> in the profile

is not known.
Explanation: An unknown parameter <keyword> has

been found in the profile.
User response: Check the specified parameter in the
profile and try again.
IDS1065E
You cannot run the function function if

the progress status indicator (PSI) has a
value of psi.
Explanation: The backup cycle was left in a state that

does not allow DP for Snapshot Devices to start the
specified function.
UDB shows the permissible functions depending on the
IDS1066E
The option -f flashcopy can only be

used on the backup system.
Explanation: You cannot start the flashcopy function

User response: Make sure you start splitint with the
function -f flashcopy on the backup system only.
Ensure that the profile contains a valid entry for
LOGON_HOST_BACK.
IDS1067E
The options -f flashcopy -s performsplit

can only be used on the production
system.
Explanation: The option -s was designed for internal

splitint use only and should not be used externally.
init<SID>.fct does not contain any of the source

volumes.
IDS1073E
No target volumes were specified for

the set <volumes_set_#> in file
<filename>.
User response: Make sure you issue splitint -f

flashcopy on the backup system only. Ensure that the
profile contains valid entries for LOGON_HOST_PROD
and LOGON_HOST_BACK. Do not use the -s option
with the splitint call.
Explanation: DP for Snapshot Devices has read file

<filename> contained in the parameter
VOLUMES_FILE. The format of the file is correct, but
the list of target volumes is missing.
IDS1068E
User response: See the description of the FlashCopy

target volumes file under DP for FlashCopy Target
Volumes File in Data Protection for Snapshot Devices for
mySAP Installation and Users Guide for DB2 UDB.
The option -f withdraw can only be

Explanation: You cannot start the function withdraw

function -f withdraw on the backup system only.
LOGON_HOST_BACK.
IDS1069E
The option -f unmount can only be used

Explanation: You cannot start the function unmount

function -f unmount on the backup system only. Ensure
that the profile contains a valid entry for
LOGON_HOST_BACK.
IDS1071E
Topic named <topicname> could not be

found in the file <filename>.
Explanation: DP for Snapshot Devices was able to

read the file <filename> but the expected entry for the
topic <topicname> was not found.
User response: When the affected file is the field
value of the parameter VOLUMES_FILE, you need to
check whether the topic name has the format:
>>> volumes_set_#
where # is a placeholder for the volume set number (1,
2, etc.)
When the affected file is another file, you likely have
another error prior to this one. Otherwise, contact Data
Protection for mySAP support.
IDS1072E
The source volume <serial number>

cannot be specified as a target volume
in the .fct file.
Explanation: DP for Snapshot Devices found one of

the source volumes in the list of target volumes in the
init<SID>.fct file.
IDS1074E
The backup ID (timestamp) is empty.

This FlashCopy backup cannot be used
for FlashBack Restore.
Explanation: Prior to this error, the warning

IDS1041W is displayed. The backup ID (timestamp) is
mandatory for using a FlashCopy backup for the
restore. The program tdphdwdb2 was not able to
generate a timestamp.
User response: Check for preceding errors. Check if
the backup to Tivoli Storage Manager ended
successfully.
IDS1075I
Creating a semaphore for the critical

part of importing/exporting ...
Explanation: When multiple production systems run a

backup via a single backup system at the same time,
DP for Snapshot Devices will ensure that the critical
parts of the code run for a single instance of the
program at a time. These phases are:
1. when the FlashCopy has been done and resources
(volume groups and file systems) are being enabled
2. before the FlashCopy relationship is withdrawn and
resources (volume groups and file systems) are
being disabled.
For this synchronization process, a semaphore with the
fixed key 0x88886666 will be created.
User response: None
IDS1076I
Trying to set the semaphore for the

critical part of importing/exporting ...
Explanation: If the DP for Snapshot Devices

semaphore is already allocated, the program will wait
until it is released. Otherwise, the program will set it
and pass into the 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
User response: Ensure that the target volumes list in

1007
IDS1077I
Semaphore released.
Explanation: After the program has passed the critical

part of the run, the semaphore is released.
User response: None
IDS1078W
The semaphore could not be created.

System error <sys_errno>:
<sys_message>.
Explanation: If DP for Snapshot Devices could not

create the semaphore, the system error number and
message will be issued as a warning. The concurrent
run of multiple production systems with a single
backup system will not work properly.
User response: Check the system error number and
message with your system administrator.
IDS1079W
The semaphore could not be initialized.

<sys_message>.

initialize the semaphore, the system error number and
IDS1080W
The semaphore could not be allocated.

<sys_message>.

allocate the semaphore, the system error number and
IDS1081W
The semaphore could not be released.

System error <sys_error>:
<sys_message>.

1008
IDS1082E
Duplicate target volume serial number

was found in the target list.

duplicate serial number for a target volume in the file
specified in the VOLUMES_FILE parameter.
User response: Ensure that the serial numbers of the
target volumes in the file VOLUMES_FILE are unique.
IDS1084I
This is your last chance to stop the

FlashBack Restore. Please enter c[ont]
to continue or s[top] to cancel.
Explanation: DP for Snapshot Devices will ask the

user a last time before the program begins with the
restore process. After that the original data will be
overwritten with the data of the FlashCopy backup.
User response: Be sure that you want to restore from
the FlashCopy backup.
IDS1085E
You cannot restore from a FlashCopy

backup of the type NOCOPY.
Explanation: Only the FlashCopy backups made with

the parameter FLASHCOPY_TYPE set to COPY or
INCR can be used for the FlashBack Restore.
User response: Normally the calling program must
make sure to determine one backup sequence number
that contains a FlashCopy backup of type COPY or
INCR. Check for preceding errors.
IDS1086E
You cannot run the function flashback

if the backup status indicator (BSI) has
a value of bsi_value.
Explanation: The flashcopy function can only be

called with a backup sequence number that has a
backup status of BSI_DISKONLY or
BSI_DISKANDTAPE. All other values such as
BSI_START, BSI_TAPEONLY or BSI_INVALID are not
allowed.
determine one backup sequence number that contains a
FlashCopy backup with one of the allowed values for
the backup status indicator. Check for preceding errors.
IDS1088W

resources.
Explanation: Before the actual FlashBack Restore to

the database volume occurs, DP for Snapshot Devices
will do the following: .
1. unmount of the database file systems .
2. in case of LVM mirroring
remove the mirror copies from the logical volumes
remove the mirror physical volumes from the
volume groups
3. remove the volume group from the AIX ODM .
One or more of these operations have ended with

errors. DP for Snapshot Devices will issue a warning
but the FlashBack Restore will continue.
User response: None
IDS1089I
The FlashBack Restore was previously

started using the target set id. Please
enter c[ont] to restart again or s[top]
to cancel.
Explanation: Having a valid disk backup on the target

volumes, the user is always able to start the FlashBack
Restore again, even though the background copy of a
prior FlashBack Restore is still running. This can also
be necessary if, for example due to an unexpected
situation on the production system, the mounting of
the file systems fails after the successful FlashCopy
reverse of the volumes.
User response: If DP for Snapshot Devices fails for
some reason during the FlashBack Restore between the
statements #UNMOUNTING_FS and #FS_MOUNTED,
then the user should restart the FlashBack Restore.
Enter c to continue or s to stop.
IDS1091E

the restore status indicator (RSI) on
target set id has a value of RSI_START.
Explanation: If the restore status RSI of the target set

has a value of RSI_START, then a FlashBack Restore is
still running in the background. You cannot start a
FlashCopy backup again until the background copy to
the database volume is finished. In this case the RSI
value is either RSI_DISKONLY or in case of LVM
mirroring RSI_DISKANDLVM.
User response: Wait until the FlashCopy background
process is finished.
IDS1092E

IDS1097E
The option -f set_bki_info can only be

Explanation: DP for mySAP (backint) calls DP for

Snapshot Devices with the function -f set_bki_info for a
FlashCopy backup on the backup machine after the
mount of the file systems. This call is not allowed on
the production machine.
User response: Consult the documentation to
understand the flow of the FlashCopy backup in an
SAP environment.
IDS1100E
The parameter
HARDWARE_ID_LVM_MIRROR has
to be moved from the profile
filename.fcs to the corresponding
target set in filename.fct
Explanation: In case of AIX LVM mirroring the

parameter HARDWARE_ID_LVM_MIRROR indicates
the identifier of the hardware unit to be selected for the
mirror copy that should be used for the FlashCopy.
This parameter is now contained in the target set
topic(s) in the .fct file.
User response: Move the parameter from the .fcs to
the .fct file.
FlashCopy failed.
Explanation: The procedure for establishing the

FlashCopy relationship between the source and target
volumes in the storage subsystem failed.
User response: This is a significant error because the
source/target pair could be left in a different state.
Check for prior errors, and check the connection to the
CIM agent and to the storage subsystem. In case of the
FlashCopy backup, you need to start the withdraw
function of splitint to clean up the relationships. In the
case of a FlashBack Restore, restart the restore. The
software will detect the state and ask you for the
withdraw.
IDS1093E
which hardware unit should be taken as the source,

will be specified here under the corresponding target
set as well. Internally DP for Snapshot Devices keeps
the status of each target set (progress status, backup
status, restore status, backup sequence number, etc) in
the housekeeping directory. After the FlashCopy, DP for
Snapshot Devices will reread the target set information.
This message will only be displayed if this information
was destroyed, is corrupt or something unexpected
occurs.
The target set id was not found.
IDS1102E
The target set id target_set_id could

not be read or inserted.
Explanation: For the handling of 2 different LVM

mirror sets, the user must now specify 2 different target
sets in the .fct file. The parameter
HARDWARE_ID_LVM_MIRROR, which determines
which hardware unit should be selected for the
FlashCopy, will be specified under the corresponding
target set as well. Internally DP for Snapshot Devices
keeps the status of each target set (progress status,
backup status, restore status, backup sequence number,
etc) in the housekeeping directory. The file containing
the information of the target set could not be read or
written.

1009
IDS1103W
The restore status indicator (RSI) has a

value of RSI_INVALID on target set id.

has a value of RSI_INVALID, this means that a
FlashBack Restore was initiated but did not terminate.
Nevertheless, DP for Snapshot Devices will issue this
warning and continue with the FlashCopy backup.
User response: Check if the FlashCopy backup ended
successfully.
IDS1104E
No target set assigned to the last backup

cycle. Specify the option -n target_set_ID.
Explanation: When called without the -n option, the

functions unmount and withdraw are applied to the
last backup cycle. However, one requirement for this is
that a target set was assigned to the last backup cycle.
The system ensures that a target set ID is always
assigned to the backup cycle during the FlashCopy
backup. This error can only occur as a consequence of
other very severe errors.
User response: Call the functions -f unmount or -f
withdraw together with the option -n target_set_ID.
To see the correlation of backup ID to target set ID call
the function -f ts_inquire. Check also for preceding
errors during the FlashCopy backup.
IDS1125I

environment, DP for Snapshot Devices ensures that the
LVM mirror setup complies with the requirements
listed below prior to and after the actual FlashCopy:
1. The quorum of each involved volume group must
be off. This means that if a mirror set is inactive
due to a failure, the database can continue working
properly (see EEP0164E).
2. Each logical volume must have at least two copies
(see EEP0166E).
3. Each logical volume must have the parallel
scheduling policy (see EEP0168E).
4. The mirror set that resides in the hardware unit that
was chosen for the FlashCopy must be free of stale
partitions (see EEP0176E).
5. All the partitions of each logical volume copy must
reside on the physical volumes of the same
hardware unit (see EEP0174E).
6. Each logical volume must have the mirror write
consistency on (see EEP0172E). This ensures that the
mirror set used for the FlashCopy is consistent from
the point of view of the file system level.
User response: None
IDS1128I
IDS1121I
Getting the source volumes ...
Explanation: The first step of DP for Snapshot Devices

in a FlashCopy backup is to determine the source
volumes from the list of files passed by the
corresponding calling UI backup tool.
IDS1122I
FlashCopying the sources to the target

volumes ...
Explanation: After finding the pairs of volumes to be

copied, DP for Snapshot Devices signals to the calling
program to set the database into backup mode or shut
down the database. Then the actual FlashCopy can be
requested to the Copy Services server.
User response: None
IDS1123I
Enabling the volumes and filesystems ...
Explanation: After the FlashCopy, the target volumes

attached to the backup machine are imported in the
operating system and the file systems are mounted
User response: None
1010
Checking AIX LVM mirroring ...
The parameter CLEAR_TARGET_PVID

in the profile filename.fcs is obsolete
and will be ignored.
Explanation: This parameter is no longer needed

because the clearing of the physical volume IDs now
depends directly on the value of the parameter
FLASHCOPY_TYPE and whether the backup is a
disk-only backup.
User response: Delete the parameter
CLEAR_TARGET_PVID from the .fcs file.
IDS1129E
You cannot run an incremental

FlashCopy until all the changed tracks
are copied.
Explanation: If you set the parameter

FLASHCOPY_TYPE of the .fcs file to the value INCR,
then an incremental FlashCopy is issued. This means
that only the data that has changed since the last
time-zero (first incremental) or subsequent incremental
FlashCopy is copied. This helps reduce background
copy completion time when only a subset of the data
has changed.
User response: If you want to start a new time-zero
FlashCopy backup in any case, you must issue the
function withdraw.
IDS1130E
The list of files passed by DP for

mySAP in the file temp_file is empty.
Explanation: DP for mySAP calls DP for Snapshot

Devices with the function set_bki_info to pass, among
other things, the backup ID and the list of files used by
backint. This list of files was now found to be empty.
User response: Check that you are using a compatible
version of backint for FlashBack Restore. The version of
backint must be v3.3.10 or higher.
IDS1131E
DP for Snapshot Devices cannot be used

for partial restores. The following
database files are in the restore list but
were not on the backup list.
Explanation: Unlike other backup techniques, DP for

Snapshot Devices moves the complete data on a
physical volume instead of individual files. Two
requirements are necessary to build a backup of a
database:
1. The complete set of physical volumes making up a
so-called volume group must be moved.
2. Also, all the volume groups in which the database
resides must also be completely moved. The
operating system allows access to the data on each
physical volume only if all the volumes are
represented as a consistent group to the system.
Also, you can only start up a database if all the
volume groups containing the database files are
available.
User response: Restore the data using Tivoli Storage
Manager from tape.
IDS1133E
Some of the production logical volumes

are mirrored. You have to set the
hardware unit ID in the parameter
HARDWARE_ID_LVM_MIRROR for
the corresponding target set in the .fct
file <filename>.
Explanation: DP for Snapshot Devices found that

some of the logical volumes on which the production
database resides are mirrored using the mirror
capability of the Logical Volume Manager. However,
the parameter HARDWARE_ID_LVM_MIRROR was
not specified in the .fct file. This parameter causes DP
for Snapshot Devices to make all the necessary checks
to get a consistent copy via the FlashCopy on the target
volumes in an LVM mirror environment.
User response: Set the parameter
HARDWARE_ID_LVM_MIRROR with the hardware
unit ID that is used for the FlashCopy.
IDS1134I
Disabling the volumes and file systems

...
Explanation: Prior to the FlashBack Restore from the

backup to the production volumes, the production
volumes and file systems will be disabled. The
following actions will be started:
v unmount
v remove devices
v remove logical volumes
v vary off the volume group
v export volume groups.
IDS1135I
FlashCopying the target to the source

volumes ...
Explanation: This message is displayed during the

FlashCopy restore process to the production volumes.
IDS1136I
The parameter parameter_name was not

specified in the profile.
Explanation: The specified parameter was not found

in the .fcs profile. However, this does not impact the
program, and processing will continue with the default
value. If the parameter is FLASHCOPY_TYPE, the
default value will be used as the intended
FLASHCOPY_TYPE (see Intended and Effective
FLASHCOPY_TYPE in Data Protection for Snapshot
UDB).
User response: Add the specified parameter to the
profile if necessary.
IDS1137I
The option -C copy_type will determine

the copy type. The parameter
FLASHCOPY_TYPE was not specified in
the profile.
Explanation: The argument of the command line

option -C specifies the FlashCopy type that should be
used. It overrides the default value of the parameter
FLASHCOPY_TYPE.
IDS1138E
The parameter
the target set target_set_id is set in the
.fct-file file_name, but the production
logical volumes are not mirrored.
Explanation: The HARDWARE_ID_LVM_MIRROR

parameter should only used in an LVM mirror
environment.
User response: If you want to use this feature you
need to mirror the production logical volumes on
1011
source volumes residing on different hardware units.

Otherwise, remove the parameter
HARDWARE_ID_LVM_MIRROR parameter from the
.fct file.
IDS1141E
The option -n <target_set_ID> must be

specified.
Explanation: The option -n is used to specify the

FlashCopy target set that should be used by DP for
Snapshot Devices. It is required for the function -f
modify_copyrate.
User response: Specify the target set involved using
the option -n <target_set_ID>.
IDS1174E
Explanation: The call of splitint with the function -f

flashback requires a backup sequence number (also
called backup cycle number) or timestamp that is a
unique identifier for the backup to be restored. With
this identifier DP for Snapshot Devices will find the
volumes target set containing the disk backup to be
restored.
determine one valid backup ID or backup sequence
number to be passed. Check for preceding errors.
IDS1175E
IDS1142I

already PSI_WITHDRAW_DONE.
Explanation: A rerun of the withdraw function will

detect that the progress status of the specified (option
-n) or last FlashCopy backup is already
PSI_WITHDRAW_DONE.
User response: If for some reason the status
PSI_WITHDRAW_DONE is not in sync with the status
of the source/target relationships, the withdraw_force
function can be used.
IDS1143E
The function withdraw_force requires

src/tgt pairs to be specified in the .fct
file file_name. The matching list of
src/tgt volumes could not be set.
Explanation: In contrast to the normal withdraw

function, where the source/target volumes are taken
from the local repository, the withdraw_force function
needs to get this information from the .fct file. The
reason for that is that the withdraw function removes
the matching list from the local repository, because a
restore after a withdraw is not allowed.
User response: Check the .fct file.
IDS1147I
Reconciling the local snapshot directory

with the storage system....
Explanation: In the case of N series, Tivoli Storage

Manager for ACS checks that, for each snapshot kept in
its Local Snapshot Manager, a valid snapshot exists on
the N series storage system.
User response: None
IDS1148I
Deleting the snapshot 'snap id' of the

volumes in the data container 'dc id'.
The option -b backup ID or -b backup

sequence number must be specified.
The backup ID or the backup sequence

number identifier was not found.
Explanation: DP for Snapshot Devices did not find

any entry in the IDSSAVE for the specified backup ID
or backup sequence number.
IDS1176I
The target set target_number does not

contain a valid FlashCopy backup.
(backup ID identifier).
Explanation: This message can be displayed when DP

for mySAP calls DP for Snapshot Devices to inquire for
disk backups on the target sets. The target sets are
enumerated starting with 1.
IDS1177E
The FlashCopy run backup sequence

number was not a valid disk backup.
Explanation: To do a FlashBack Restore, a valid disk

backup must exist on one of the target sets. The backup
status indicator (BSI) must have the value
BSI_DISKONLY or BSI_DISKANDTAPE.
User response: Check the backup status indicator
(BSI) of your target volumes calling the tdphdwdb2
executable: tdphdwdb2 -p initSID.fcs -f ts_inquire -n
target set number
IDS1178E
The backup status indicator (BSI) for

the FlashCopy run backup sequence
number is not valid.
Explanation: The backup status indicator can accept

one of the following values in the IDSSAVE:
Explanation: The specified snapshot will be deleted.
v BSI_START: a disk backup as background copy was

started and is still running
User response: None
v BSI_TAPEONLY: only a backup on TSM is available

v BSI_DISKONLY: only a backup on disk is available
1012
v BSI_DISKANDTAPE: both disk and TSM backups are

available
v BSI_INVALID: invalid entry for disk backup
Any other value is not allowed and makes the backup
cycle unusable.
(BSI) of your IDSSAVE calling the tdphdwdb2
executable with the option -f inquire : tdphdwdb2 -p
initSID.fcs -f inquire -b backup sequence number
Check for preceding errors.
IDS1179E

target set number is not valid.

one of the following values for one specific target set:
v BSI_DISKANDTAPE: both disk and TSM backups are
available
IDS1182E

Advanced Copy Services tries to find a target set (data
container) that matches the source data container to
satisfy the FlashCopy backup. It can be a target set in
the state AVAILABLE or the state IN_USE (in which
case it will be re-used). A matching target data
container could not be found, however.
are being used for the FlashCopy type COPY. Also
make sure that the target volumes are available to the
v TARGET_VOLUME
v PRIMARY_COPYSERVICES_SERVERNAME
v COPYSERVICES_USERNAME
IDS1183I

cycle unusable.
executable with the option -f ts_inquire (target set
inquire): tdphdwdb2 -p initSID.fcs -f ts_inquire -n
target set number Check for preceding errors.
IDS1180E

number is a valid disk backup.
No target set ID could be assigned to

the backup run backup_sequence_number.
A disk-only backup (option -d) was

invoked, forcing the parameter
FLASHCOPY_TYPE of the .fcs-file to
COPY.
Explanation: If the user specified a disk-only backup

via the parameter -d and the parameter
FLASHCOPY_TYPE of the .fcs file has the value of
NOCOPY, DP for Snapshot Devices sets the value to
COPY.
IDS1184I
Checking the backup status on Tivoli

Storage Manager and on disk ...
Explanation: DP for Snapshot Devices has found that

the selected backup to be restored has a valid disk
backup with an entry in the IDSSAVE.
Explanation: This message is displayed by DP for

Snapshot Devices during the inquiry of the backups on
Tivoli Storage Manager and on disk.
User response: None
IDS1181E
IDS1185I

number is not the last backup of target
set number.
Explanation: The specified backup sequence number

cannot be used for FlashBack because on the target
volumes a newer FlashCopy run was already entered.
inquire): tdphdwdb2 -p initSID.fcs -f ts_inquire -n
target set number Select another backup Id for
FlashBack.
Reading the SAP backup log

<PATH>/back<SID>.log ...
Explanation: This message is displayed by DP for

Snapshot Devices while reading the backup of the SAP
system ID <SID>.
IDS1186E
The parameter param in the profile

<.sap file name> or the environment
variable env_var is required.
Explanation: This error is issued by DP for Snapshot

Devices if the specified parameter of the .sap file
passed by the option -p could not be read.
User response: Check that the passed .sap file is a
1013
valid setup file for the SAP environment.

IDS1189E
The option -C copy_type will override

the value value of the parameter
FLASHCOPY_TYPE in the profile.
Explanation: The value of the copy type parameter in

the option -C copy_type, if specified in the command
line, will override the value found in the DP for
Snapshot Devices profile (.fcs)
IDS1190E
User response: Check the error log

file splitint_[p|b]_runagent_jjjjmmddHHMMSS.log in
the directory specified in the parameter
LOG_TRACE_DIR of the .fcs file. Check the availability
of the storage system using the applicable tool
(STORWATCH Specialist, DS Storage Manager, or SVC
console).
Check the parameters in the .fcs file:
v COPYSERVICES_SERVERPORT
Also verify the availability of the CIM agent and its
connection to the storage system as described in the
storage-system documentation.
The target volumes set number does
not contain a valid disk backup.
Explanation: This informational message is displayed

during the call of the function get_disk_backups of DP
for Snapshot Devices (which is issued by the calling UI
backint or DP for Snapshot Devices) if one of the target
sets contains an invalid disk backup.
IDS1192I
No disk backups were found on the

target volumes.

backint or DP for Snapshot Devices) if none of the
target sets contains a valid backup.
User response: You will have to select a backup from
Tivoli Storage Manager.
The FlashCopy run with backup ID id

was of type NOCOPY.

backint or DP for Snapshot Devices) if one of the target
sets contains a FlashCopy backup of type NOCOPY.
IDS1194I
The information of the source/target

volumes could not be found.
Explanation: The executable splitint will be started

automatically as a daemon (sometimes referred as
fcagent) to monitor the background copy. An attempt to
obtain the status of the copy process has failed.
IDS1191I
IDS1193I
The FlashCopy run

backup_sequence_number has a
backup status indicator (BSI) of status
and is therefore not valid for FlashBack.

backint or DP for Snapshot Devices). The values of the
backup status (BSI) BSI_DISKONLY and
BSI_DISKANDTAPE are valid values for a FlashBack
Restore. The values BSI_START and BSI_TAPEONLY
could be valid values at a later point in time. Any other
value is invalid.
IDS1196E
The list of files to be restored does not

exist for the specified backup ID
identifier.
Explanation: A FlashCopy disk backup can only be

restored in coordination with DP for mySAP. At restore
time, DP for Snapshot Devices has to know about the
corresponding list that was passed at backup time.
User response: Check that you have the version of DP
for mySAP supporting FlashBack Restore. Otherwise,
you will have to restore from Tivoli Storage Manager.
IDS1197I

exist for the FlashCopy run
backup_cycle_number.

backint or DP for Snapshot Devices) if the list of files
was not found for one of the target sets.
IDS1200E
The exception CIdsException was

thrown.
Reason: <reason text>
Explanation: At present, the only reason text is: Not

enough memory space. Allocation error in file <file
name>, line <line number>.
User response: Ensure that db2<sid> and the root
user have the right setting for memory allocation. The
1014
output of ulimit shows these values. Check the SAP

documentation for the respective release installed.
Perform the following steps as recommended by SAP:
Checking Created Users
Check, as root, all existing users. To do this:
1. Enter the command smitty.
2. Select: Security & Users .Users .Change/Show
Characteristics of a User
3. Press F4 to get a list of users.
4. For user root and each created user <user>:
a. Select <user>.
b. Change field Soft CPU time to -1 (this is the
default value).
c. Change field Soft CORE file size to 2097151 (this
is the default value).
d. Change field Soft FILE size to 4194302.
e. Change field Soft DATA segment to -1.
f. Change field Soft STACK size to -1.
v <LOG_TRACE_DIR>/splitint_p_
<date_time_stamp>.log
v <LOG_TRACE_DIR>/splitint_b_
<date_time_stamp>.trace
v <config_file>
v <ids_control_file>
v the field value EXCHANGE_FILE in a backup cycle
record.
User response: Check the access permissions of the
affected file and try again.
IDS1302E
The environment variable <env_var>

must be set.
Explanation: The environment variable <env_var> is

required. The following environment variables must be
set when running DP for Snapshot Devices:
v INSTHOME: to the home directory of the DB2 user
v DB2INSTANCE: to the DB2 instance
v DB2DBDFT: to the DB2 default database
You must make sure that the system-wide default

HARD values are not explicitly defined to be lower
than the number indicated above. Check the file
/etc/security/limits under the default: stanza. If they
are not explicitly set, then the values are as shown in
the table at the top of the file.
User response: Set the missing environment variable

and try again.
IDS1212W
IDS1303E
One or more errors were found checking

the FlashCopy relations.
Explanation: This message can appear during the

FlashBack Restore if the check of the source/target
relations ended with any error that originated in the
storage subsystem. This check takes part before any
resource is removed.
User response: Examine the preceding message
output.
IDS1300E
Cannot read file: <filename>.

read the data file <filename>. The affected files could
be, e.g.:
v <INSTHOME>/dbs/init<SID>.fcs
v the argument value of the option -i (file containing
the list of files to back up)
v <config_file>
v the field value of EXCHANGE_FILE in a backup
cycle record.
IDS1301E
Cannot write file: <filename>.

write to the data file filename. The affected files could
be, e.g.:
The environment variable <env_var> is

not correct.
Explanation: This error can occur when the

environment variable is set but contains a non-existent
directory path.
User response: Check the value of the environment
variable and try again.
IDS1304E
File not found or not accessible:

<filename>.
Explanation: The file <filename> was not found or is

not accessible to DP for Snapshot Devices. The affected
files could be: <INSTHOME>/dbs/init<SID>.fcs or the
argument value of the option -i (the file that contains
the list of files to back up).
User response: Check path, name and the permissions
of the file and try again.
IDS1305E
The effective user ID of the process

could not be set to the user <userid>.
Explanation: One of the following cases can cause this

error:
v the access rights for splitint are not set to 4750. Since
the s-bit is not set, DP for Snapshot Devices cannot
switch between the users db2<sid> and root
during the execution of the program.
v the file system in which splitint is installed was
mounted with the NOSUID option.
User response:
1015
v Check the splitint file in the directory

/usr/tivoli/tsm/acssap/db2/x.y.z, and set the access
rights for splitint with chmod 4750 splitint. After the
installation, the command
ls -l splitint.... outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 splitint
(This is what setup.sh would do if the user had used

it.)
v If the file system in which splitint is installed was
mounted with the NOSUID option, mount the file
system with SUID allowed.
IDS1306I
Issuing command command_string ...
Explanation: DP for Snapshot Devices is running the

specified system command with the parameter as
shown.
IDS1308W
Warning: File <file name> still exists on

the backup system.
IDS1311W
splitint requires free space of at least 5

MB in the file system containing the
directory path.
Explanation: If the free space of the checked file

systems (see the explanation for IDS1310W) is under 5
MB this error message will be issued and the program
fails throwing an exception.
User response: Ensure that the free space on the
database file system is large enough.
IDS1318E
Operating system error <error_no>:

<message text>.
Explanation: DP for Snapshot Devices encountered an

and message text will be displayed. The message will
appear, for example, as a result of
v an incorrect user ID on the parameter
LOGON_HOST_PROD in the .fcs file
v an incorrect password given for the user ID on the
parameter LOGON_HOST_PROD in the .fcs file
Explanation: DP for Snapshot Devices checks at the

start of the function flashcopy if any of the files passed
in the file list still exist on the backup system. If so, this
warning will be issued. Normally, none of the files
should exist because the withdraw function, which
should run prior to the FlashCopy, unmounts the files
systems, varies them offline, exports the volume
groups, and removes the devices.
User response: Always run the function withdraw

prior to starting the FlashCopy again.
IDS1322I
IDS1310W
The free space in the file system

containing the directory path is only
amount MB.
Explanation: The existing free space of the file

systems containing the following directories will be
checked:
v an incorrect TCP/IP name on the parameter

LOGON_HOST_PROD in the .fcs file (for example:
connection timeout)
v a failure allocating memory using the function
malloc, and the operating system cannot satisfy the
request
The file filename is locked, waiting

one second and retry!
Explanation: DP for Snapshot Devices saves control

information for the FlashCopy process in an internal
repository that consists of several files. Some of these
files may need to be written concurrently by several
processes. To ensure consistency, DP for Snapshot
Devices uses a lock mechanism.
v the database home directory and
v the directory specified by the parameter

LOG_TRACE_DIR in the .fcs file and
IDS1325I
v the directory containing the idssave file specified by

the parameter IDS_CONTROL_FILE in the .fcs file.
If the free space of these file systems falls below 50 MB,
DP for Snapshot Devices warns the user. If it is under 5
MB an error will be issued and the program fails,
throwing an exception.
User response: Ensure that the free space on these file
systems is large enough.
1016
Please check the messages above. Enter

r[etry] to retry or any other key to stop
the process.
Explanation: This message is asking you to retry an

operation that previously failed.
User response: Check the specific message and decide
whether to retry or stop the process. In the case of
critical restore runs, it is recommended to retry the
operation after the reason for the failure has been
identified and remedied.
IDS1326E
Password input file <input file> not

found.
IDS1331E
Explanation: The input file specified by the i <input

file> option was not found.
User response: Specify a vaild filename with full path
for the input file for the password/configure function.
IDS1327I
Topic named <topic name> could not

be found in the file <input file>. The
password of user <username> will not
be changed.

file> option doesnt have the topic <topic name>
specified. The user <username> will not be changed.
There are two topic names (DBUSER, CSUSER). If none
of these topics are found in the <input file>, then no
password will be changed.
IDS1328W
Parameter named <parameter name>

could not be found in the file <input
file>. The password of user
<username> will not be changed.
The file <filename> could not be

found. Please check that this file exists
or that the symbolic link points to an
existing file.
Explanation: The file <filename> is not valid.

User response: Please check that the file <filename>
exists or that the symbolic link points to an existing
file.
IDS1400E
The backup status on target set

targetSetID must be BSI_DISKONLY or
BSI_DISKANDTAPE for re-use with
incremental copy type.
Explanation: A FlashCopy backup of type INCR in a

non-AIX LVM mirror environment will re-use the
already existing target set with FlashCopy type INCR
only if the background process is already finished.
User response: Check the background process by
starting the program splitint with the function inquire
or ts_inquire.
IDS1401E
The target set targetSetID does not match

the source volumes.

file> option doesnt have a valid format. The parameter
<parameter name> is not found in it. The password of
the user <username> will not be changed.
Explanation: DP for Snapshot Devices checks whether

the target set for the FlashCopy backup contains a
target volume for each source volume, residing in the
same hardware unit and with the same size.
User response: Please check for the valid format of

the <input file>. Parameter <parameter name> is
required in the topics DBUSER and CSUSER.
User response: Check the volume list of this target set

and ensure that the volumes are in the same hardware
unit and have the same size as the source.
IDS1329I
IDS1402E
The password of user <username> will

be changed.

file> option has a valid format and the password of the
user <username> of either the DBUSER or the CSUSER
topic will be changed.
IDS1330E
The file <diskmapper filename> could

not be found. Please check that the
parameter DISKMAPPER_SCRIPT is
specified as a full qualified
path/filename.
Explanation: The script <diskmapper filename>

specified by the parameter DISKMAPPER_SCRIPT in
the DP for Snapshot Devices profile is not valid.
for the DISKMAPPER_SCRIPT parameter.
A background copy process of type

CopyType is still running on target set
targetSetID.
Explanation: DP for Snapshot Devices fails if a

background copy is still running for the same logical
FlashCopy group (see Logical FlashCopy Group in
Installation and Users Guide for DB2 UDB). However,
any target set (state AVAILABLE) that does not yet
belong to a logical FlashCopy group (state
AVAILABLE) can be selected.
User response: Check the backup status of the
FlashCopy backups that may be running.
IDS1404I
The target set with ID targetSetID is

selected for this run.
Explanation: DP for Snapshot Devices use two

procedures for the selection of a target set. See
Algorithm Used for Automated Target Set Selection
Using the Intended FlashCopy Type and Algorithm
Used for Specific Target Set Selection in Data Protection
for Snapshot Devices for mySAP Installation and Users
Guide for DB2 UDB.
1017
other value is not valid. INCR is invalid for an SVC

configuration.
IDS1405E
User response: Specify one valid value.
No target set found to accept a backup

of type copy_type.
Explanation: If all the target sets are being used with

the same type of logical FlashCopy group (either INCR
or COPY), you will not find a target set to make a
FlashCopy with a different copy type.
User response: To make a target set AVAILABLE, start
the function withdraw on the specific target set using
the option -n.
IDS1408E
The copy type argument copy_type is not

valid.
Explanation: The argument (FLASHCOPY_TYPE) of

the command line option -C <FLASHCOPY_TYPE> can
have the following values: COPY, NOCOPY and INCR.
Any other value is not valid. Furthermore, INCR is not
valid for an SVC configuration.
IDS1418E
The target set targetSetID is already

using incremental FlashCopy.
Explanation: Using the procedure of specific target set

selection, it is not allowed to select more the one target
set for incremental FlashCopy on the same storage
device.
User response: Re-use the same target set or
withdraw the existing relationship.
IDS1436E
The value of the parameter

COPYSERVICES_HARDWARE_TYPE in
the file profile_name is invalid. Valid
values are: DS8000, DS6000, SVC,
ESS800 and SAN_NSERIES.
Explanation: The parameter can only accept the

specified values.
IDS1410E
User response: Change to the value according with

the storage system.
You cannot run a FlashBack Restore

from target set targetSetID if the sources
are involved in a relationship of type
copytype with the target set targetSetID
Explanation: DP for Snapshot Devices exploits the

feature Multiple Relationship FlashCopy of the
storage system. This means that for DP for Snapshot
Devices the source set of volumes can participate in
multiple FlashCopy relationships with several target
sets of volumes. However, there are some limitations: v A source can have up to 12 targets
v A target can only have one source
v A target cannot be a source at the same time
User response: To start a FlashBack Restore
(FlashCopy in reverse, from the target to the source
volumes) you have to withdraw the relationship with
the specified target set.
IDS1411E
The intended FlashCopy type has a

value of copy_type.
IDS1437E
The next FlashCopy Backup after an

incremental FlashBack Restore must
involve the same source/target LUNs as
the FlashBack Restore.
Explanation: Possible reasons for this error are as

follows:
v Ensure that you are using the same backup type
online_mirror or offline_mirror for this FlashCopy
Backup as the one that you used with the FlashBack
Restore.
v Any structural changes on source/target volumes
like adding new source volumes or deleting source
volumes will cause this error.
User response:
v If applicable, start a new FlashCopy Backup with the
same backup type as the one that you used with the
FlashBack Restore. Otherwise, perform the following
step.
Explanation: See Intended and Effective

UDB.
v Start a withdraw (-f withdraw) of this incremental

FlashCopy target volumes set. This implies that the
subsequent FlashCopy Backup will be a full copy.
IDS1438W
IDS1413E
An invalid value copy_type has been

specified for the FlashCopy type in the
profile .fcs file.
Explanation: The parameter FLASHCOPY_TYPE of

the DP for Snapshot Devices profile (.fcs file) can have
the following values: COPY, NOCOPY and INCR. Any
1018
No source LUNs found for the prior

FlashCopy run in the file
ids_repository_file.
Explanation: TSM for ACS was not able to find the

matching list of source/target LUNs involved in the
last FlashCopy backup in the local repository.
User response: None. TSM for ACS will proceed with
IDS1439W
No matching list found in this

FlashCopy run.

User response: Order a release version of Data

Protection for Snapshot Devices for mySAP or contact
your IBM/Tivoli marketing representative before the
version expires.
IDS1454I

IDS1440E
An incremental FlashBack Restore was

already started using the target set
target_set_id. You can re-start again only
after the background copy process is
finished. See the progress of the
FlashBack using the menu point **show
details**.
Explanation: This is a limitation imposed by the

storage system.
IDS1455E
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
License file filename does not exist.
Explanation: Unable to access license file.

IDS1441I
Checking the FlashCopy relations,

please wait ...

Explanation: TSM for ACS is reading the

source/target FlashCopy relations from the storage
system.
IDS1457E
IDS1443E
User response: Make sure you have the right

agentess.lic file installed.
Data container id dcID cannot be used

to force a cleanup (function
'withdraw_force') when the snapshot
was already removed.
Explanation: This messages applies only to the

component Data Protection for N Series Snapshot for
mySAP. The function 'withdraw_force' of TSM for
ACS requires, in the case of N Series, that the snapshot
which is the base of the cloned, mounted volumes on
the backup system is still available.
IDS1452E
This version of Data Protection for

Snapshot Devices for mySAP has
expired.

your IBM/Tivoli marketing representative.
IDS1453W

Snapshot Devices for mySAP will expire
in number days.

IDS1520E

data/checksum.
The FlashCopy agent can only be started

if the last FlashCopy run was of type
COPY or INCR.
Explanation: DP for Snapshot Devices will

automatically start a daemon called the FlashCopy
agent to monitor the background copy, provided the
parameter FLASHCOPY_TYPE of the .fcs file was set to
COPY or INCR.
User response: Normally, the calling program will
control this process. Check for preceding errors.
IDS1531E
Timestamp string cannot be converted.
Explanation: The status of the background copy will

be written by the FlashCopy agent daemon to a file
named fc_exchange.bseq_number in the directory
containing the IDSAVE specified by the parameter
IDS_CONTROL_FILE. The file
fc_exchange.bseq_number has, for each volume pair,
the entry volume_pair: target source size state
YYYY-MM-DD-HH.MM.SS YYYY-MM-DD-HH.MM.SS
rate, where target is the serial number of the target
volume, source is the serial number of the source
volume, state can be active if the background copy is
running or none if the background copy is finished.
YYYY-MM-DD-HH.MM.SS represents approximate
1019
times for the start and end of the background process

(in seconds since 00:00:00 GMT, January 1, 1970, which
is the time standard the operating system uses), and
rate is the transfer rate within the storage system. To
calculate the transfer rate some conversion is needed.
When doing this conversion, an error occurred. The
rate value will be invalid.
unable to add an entry to /etc/inittab.
User response: Check the date and time setting of the

machine.
Explanation: DP for Snapshot Devices automatically

starts a daemon (called the FlashCopy agent) to
monitor the background copy after the start of a
FlashCopy backup of type COPY or INCR on the
backup system and after the start of the FlashBack
Restore on the production system. An entry in
/etc/inittab allows the daemon to be started
periodically. In an attempt to add such an entry, DP for
Snapshot Devices detected that an entry already
existed.
IDS1540I
Start of the FlashCopy agent on the

backup system

automatically start a daemon (called the FlashCopy
agent) to monitor the background copy after the start
of a FlashCopy backup of type COPY or INCR on the
backup system.
User response: Check the rights of the DP for

Snapshot Devices executable (splitint or tdphdwdb2).
IDS1551W
The FlashCopy agent already exists in

/etc/inittab.
User response: None
User response: None

IDS1552E
IDS1541I
Removing the FlashCopy agent on the

backup system

automatically stop the FlashCopy agent daemon after
the background copy has finished on the backup
system.
User response: None
IDS1545I

production system

of a FlashBack Restore on the production system.
User response: None
IDS1546I

production system

the background copy has finished the restore on the
production system.

system or, in the case of FlashBack Restore, on the
production system. The entry in /etc/inittab will be
removed. However, DP for Snapshot Devices was
unable to remove the entry.
Snapshot Devices executable (splitint or tdphdwdb2).
IDS1553W
The FlashCopy agent could not be

added to /etc/inittab.

periodically. However, DP for Snapshot Devices was
1020
The FlashCopy agent has already been

removed from /etc/inittab.

removed. However, DP for Snapshot Devices detected
that the entry no longer exists in the table.
IDS1602I
User response: None

IDS1550E

Waiting for SyncPoint number on all

EEE nodes...
Explanation: DP for Snapshot Devices is waiting for

all running tdphdwdb2 processes to reach the specified
SyncPoint.
IDS1603E
Timeout of number seconds on waiting

for SyncPoint number on all EEE
nodes reached.
Explanation: While DP for Snapshot Devices is

waiting for all running tdphdwdb2 processes to reach
the specified SyncPoint, a time out condition occurs.

This error can have the following reasons:
1. The DP for Snapshot Devices parameter
DB2_EEE_SYNCTIMEOUT is set too low. Check the
DP for Snapshot Devices parameter
DB2_EEE_SYNCTIMEOUT in the DP for Snapshot
Devices configuration file.
2. DP for Snapshot Devices is not started for each
production server.
3. One or more DP for Snapshot Devices processes
running for the production servers were terminated.
User response:
1. Check the DP for Snapshot Devices parameter
2. Check that DP for Snapshot Devices is running on
the backup system for all production servers.
3. Check for error messages in the DP for Snapshot
Devices log files for each process.
IDS1605I
has to be changed by calling the tdphdwdb2 function

configure.
IDS1620E
The TCPIP service port number could

not be found in /etc/services.
Explanation: This error occurs, if the TCP/IP port for

the socket server communication is not configured in
the file /etc/services.
User response: Make sure, that the socket service
configuration is done by calling tdphdwdb2 with
function configure on the production system and that
the backup system is configured with the script
setupDB2BS. If the DB2 UDB EEE or ESE configuration
is changed (e.g. a new EEE/ESE partition is added),
you have to reconfigure the socket server, see:
Considerations for DB2 UDB ESE with DPF in Data
Protection for Snapshot Devices for mySAP Installation and
Users Guide for DB2 UDB.
The last socket synchronization is still

active.
Explanation: The last DP for Snapshot Devices socket

synchronization was not stopped.
IDS1606E
Socket synchronization could not be

started.
Explanation: The last DP for Snapshot Devices socket

synchronization was not stopped. DP for Snapshot
Devices failed in trying to stop and restart the socket
synchronization.
User response: Restart the socket server on the
production server which holds the EEE or ESE
coordination partition. Use the function stopsocket.
After stopping the socket server, it will automatically
be restarted because of the entry in the /etc/inittab
file.
IDS1607I
Socket server was not running.
Explanation: tdphdwdb2 was called with function

stopsocket to stop the socket server, but the socket
server was not running.
IDS1610E
Invalid user name or password.
Explanation: While tdphdwdb2 is sending a socket

request from the socket client to the socket server, the
user and the encrypted password are checked on the
socket server. The user and/or password sent to the
socket server are incorrect.
User response: If the password for the user db2<sid>
or the Copy Services user ID is changed, the socket
server has to be restarted. The password for the users
1021
Messages from tdphdwdb2

IDS2000E
Profile not specified.

the profile.
that the tdphdwdb2 call must have the following form:
<path>/tdphdwdb2 -p <path>/init<SID>.fcs -f
<function>....
IDS2001E
Function not defined.

name with the option -f. Valid functions are: backup,
restore, query, flashcopy, withdraw, inquire, password.
IDS2005I
Start of tdphdwdb2 program at: <time> .

IDS2007I
End of tdphdwdb2 program at: <time> .

Control will be returned to either the shell or to a script
when tdphdwdb2 was called by a script.
IDS2008E

required.

must be defined.
IDS2009E

control file does not exist!

CONTROL_FILE is incorrect or the path does not exist.
CONTROL_FILE in the profile has a valid path. If the
path does not exist, you must create it.
IDS2010E
Another instance of tdphdwdb2 is

running.
Explanation: DP for Snapshot Devices is already

running or the last run was abnormally terminated.
User response: If another DP for Snapshot Devices is
running, you must wait for the end of this run before
1022
you can restart DP for Snapshot Devices. If no other DP

for Snapshot Devices is running, you must remove the
lock-file /db2/<SID>/dbs/work/.tdphdwdb2_lock
manually.
IDS2011E
Explanation: tdphdwdb2 always requires the option -f

User response: Ensure that the tdphdwdb2 call has
the following form: <path>/tdphdwdb2 -p
IDS2012E
The backup type <-t flashcopy> can

only be used on the backup system.

backup and backup type flashcopy. This combination of
parameters is only valid on the backup system.
User response: Ensure that tdphdwdb2 with function
backup and backup type flashcopy is called on the
backup system.
IDS2013E
The arguments specified for the backup

type <-t flashcopy> are not valid.

backup and backup type flashcopy. You specified an
invalid argument for the backup type flashcopy.
User response: Ensure that you pass valid arguments
with backup type flashcopy. Valid arguments are:
no/unmount, no/withdraw.
IDS2014E
The arguments <withdraw> and

<nounmount> for the backup type <-t
flashcopy> do not work together.

backup and backup type flashcopy and the optional
arguments nounmount and withdraw. This is an
invalid combination of the arguments for the backup
type flashcopy.
with backup type flashcopy. The combination
nounmount and withdraw is not valid.
IDS2015E
The backup type -t online/offline can

only be used on the production system.

backup and backup type online/offline. This
combination of parameters is only valid on the
production system.
User response: Ensure that the tdphdwdb2 with
function backup and backup type online/offline is
called on the production system.
IDS2016E
The option -f restore can only be used


restore. This parameter is only valid on the production
system.
function restore is called on the production system.
IDS2017E
The option -f query can only be used on

the backup system.
IDS2023E
The socket options <-f initsocket> and

<-f stopsocket> can only be used on the
production system.
Explanation: You tried to start or stop the socket

server on the backup system but these functions can
User response: None
IDS2024E
The option -f dbresume can only be

used on the production system.

query. This parameter is only valid on the backup
system.
Explanation: You tried to resume the DB2 database on

the backup system but this function can only be used

function query is called on the backup system.
User response: None

IDS2028E
IDS2018E
The option -f flashcopy can only be


flashcopy. This parameter is only valid on the backup
system.
The arguments specified for the option

-f restore are not valid.

restore. You specified an invalid argument for the
function restore.

function flashcopy is called on the backup system.

with function restore. Valid arguments are: database,
no/rollforward.
IDS2019E
IDS2029E


unmount. This parameter is only valid on the backup
system.
function unmount is called on the backup system.
Explanation: tdphdwdb2 checks the size of the DB2

Logdir filesystem. This check fails.
User response: Ensure that the DB2 Logdir filesystem
exists and is mounted.
IDS2030E
IDS2020E


withdraw. This parameter is only valid on the backup
system.
function withdraw is called on the backup system.
IDS2022E
Error while checking filesystem size for

DB2 Logdir <logdir>.
Not enough freespace in DB2 logpath

(<logdir>). Need at least 55% freespace.
Explanation: tdphdwdb2 checks the freespace of the

DB2 Logdir filesystem. tdphdwdb2 needs at least 55%
freespace for copying all online logfiles to a
safe-directory in the same filesystem.
User response: Ensure that the DB2 Logdir filesystem
is large enough for the restore. You need twice the
space as usual for the DB2 logdir filesystem.
The backup type <type> is not valid.
Explanation: The backup type given with option t

<type> is not valid.
User response: Valid values for backup type are:
online, offline, flashcopy [no/unmount] [no/withdraw]
IDS2031E
Backup Timestamp <time> cannot be

converted.
Explanation: tdphdwdb2 cannot read and convert the

backup timestamp from the db2 recovery logfile
(DB2_RECOVERY_LOG parameter).
User response: Ensure that the db2 recovery log file
can be accessed by tdphdwdb2 and is not corrupted.
1023
IDS2032W

not been found.

Snapshot Devices and DP for mySAP was not found
during the execution of the unmount function. Either
the DP for mySAP you have installed does not support
DP for Snapshot Devices, or DP for mySAP has failed
after a successful FlashCopy and mount.
User response: None

IDS2036E
The options -b <backup sequence

number> or -b <backupID> must be
specified.
Explanation: The function you called needs the

additional parameter b <backup sequence number> or
-b <backupID>.
User response: Check the run logs of tdphdwdb2.

This error could have various reasons and should be
User response: Restart the function you called with

the b option.
Case 1: tdphdwdb2 has finished successfully.
IDS2037E

as well as the one done to the TSM server are valid.
However, DP for Snapshot Devices cannot show the
backup ID in its report when using the function
inquire.
Explanation: You tried to start the function configure

on the backup system but this function can only be

User response: None

IDS2038E

Case 2: tdphdwdb2 has terminated abnormally.
Result: Check carefully the run log of tdphdwdb2 for
any BKI, ANS or ANR error messages. Most likely, the
the backup to the TSM server is invalid.
Cause: Any problems with the network or on the TSM
server caused DP for mySAP to fail when running a
backup.
reason for not getting a successful backup to the TSM
server.
IDS2033I

<backupid>.

backup on disk (FlashCopy target volumes) as well as
to the TSM server are valid. The list of files has been
saved in the Tivoli Storage Manager with the backup
ID <backupid>.
User response: None
IDS2035E
The option -f restore can only be used

Explanation: You tried to start a restore on the backup

system but the function restore can only be used on the
production system.
1024
The option -f configure can only be

The option -f configure can only be

used on the coordinating production
server.
Explanation: You tried to start the function configure

on a production server which does not hold the
coordinating EEE partition. This function can only be
used on the production server which holds the
coordinating EEE partition.
User response: None
IDS2039E
The option -s <socket_port> can only be

used in EEE environments.
Explanation: Explanation: You called tdphdwdb2 with

option s but this option can only be used in DB2 UDB
EEE environments.
User response: None
IDS2040E
The socket port <> specified with the

option -s <socket_port> is invalid.
Explanation: You specified an invalid port with the

option s. Valid numbers for this option can be found
in the DB2 EEE configuration file db2nodes.cfg.
User response: None
IDS2051I

ID>

Devices program splitint uses the user ID to access the
production system.

IDS2052I

ID> again

IDS2053I

please try again.

terminates.
IDS2054E
No password stored.

User response: You must start the tdphdwdb2
program with the function -f password again. If no
password is stored, or it is invalid, tdphdwdb2 fails
when the flashcopy function is used.
IDS2055E

could not be opened. Please call
tdphdwdb2 with the function
configure to create this file.

Try the following:
1. Call tdphdwdb2 with the configure function to
create the file
CONFIG_FILE)
correctly.
IDS2062E
Invalid value <value> specified for

parameter <parameter> in the profile.
IDS2063E
LOGON_HOST_BACK in Profile wrong
or missing.

LOGON_HOST_PROD <tcp_name> <user ID>
The tcp_name must match the TCP/IP name via which
the production system can be reached from the backup
system. The host name must match the respective host
name of the backup system. The user ID specified must
match the DB2 user ID (db2<sid>).
LOGON_HOST_BACK.
IDS2064E

is not known.

IDS2065E
You cannot run the function <function>

if the progress status indicator (PSI) has
a value of <psi>.

specified function.
User response: Refer to the permissible functions
depending on the backup progress status indicator.
IDS2071E

Explanation: DP for Snapshot Devices could read the

file <filename> but the expected entry for the topic
<topicname> was not found.
Explanation: The value specified for the parameter in

the profile is not valid.
>>> volumes_set_#
User response: Check the specified value in the profile

and try again.

2, etc.) When the affected file is another file, you likely
have another error prior to this one. Otherwise, contact
IBM support.
1025
IDS2090E
The NLS catalog could not be loaded.

Make sure that the catalog <%s/%s>
exists.
Explanation: DP for Snapshot Devices uses an English

NLS catalog for the LVM and the storage-system part
of the product. The installation process will copy the
catalog to the displayed path.
User response: Check for errors during the installation
procedure.
IDS2094E
You cannot use FlashBack Restore and

Restore from TSM together.
Explanation: In an EEE environment, for a restore of

the database, DP for Snapshot Devices must be started
on all production servers. You selected different types
of restore (FlashBack Restore and Restore from TSM)
for one restore run. This is not allowed by DP for
Snapshot Devices.
User response: You have to select the same type or
restore.

IDS2174E
The option -b backup ID or -b backup

sequence number must be specified.
Explanation: The call of splitint with the function -f

flashback requires a backup sequence number (also
called backup cycle number) or timestamp that is a
unique identifier for the backup to be restored. With
this identifier, DP for Snapshot Devices will find the
volumes target set containing the disk backup to be
restored.
IDS2175E
The backup ID or backup sequence

number number was not found.
Explanation: The specified Backup ID or backup

sequence number could not be found in the DP for
Snapshot Devices housekeeping files.
User response: None
IDS2095W
You have selected a different Backup ID

than on the coordinating server.
Explanation: In an EEE environment, for a restore of

the database, DP for Snapshot Devices must be started
on all production servers. You selected different Backup
IDs to restore. This is just a warning. DP for Snapshot
Devices allows to restore different Backup IDs.
User response: None
IDS2185I
reading <DP for mySAP recovery log>

and checking backup status...
housekeeping files.
Explanation: DP for Snapshot Devices is reading the

information from the DP for mySAP recovery log file
and checks the entries with the DP for Snapshot
Devices
User response: None
IDS2104E

cycle. Specify the option -n
target_set_ID.

To see the correlation of backup ID to target set ID, call
IDS2124I
Explanation: The tdphdwdb2 program issues this

message on terminating. The program returns the value
0 if successful, or nonzero if the execution of the called
function failed.
1026
IDS2200E

thrown.

User response: Ensure that db2<sid> and the root
user have the right setting for memory allocation. The
a. Select <user>.
default value).

You must make sure that the system-wide default
HARD values are not explicitly defined to be lower
than the number indicated above. Check the file
IDS2300E
IDS2304E

<filename>.

files could be: <INSTHOME>/dbs/init<SID>.fcs or the
argument value of the option -i (the file that contains
the list of files to back up).

be, e.g.: <INSTHOME>/dbs/init<SID>.fcs,
<config_file>, <ids_control_file> or the field value of
EXCHANGE_FILE in a backup cycle record.
IDS2305E


error:

v the access rights for tdphdwdb2 are not set to 4750.

Since the s-bit is not set, DP for Snapshot Devices
cannot switch between the users db2<sid> and
root during the execution of the program.
IDS2301E
v the file system in which tdphdwdb2 is installed was


be, e.g.:
v one of the log/trace files as listed in Summary of
Log and Trace Files in Data Protection for Snapshot
Devices for mySAP Installation and Users Guide for
DB2 UDB.
v <config_file>
record.
IDS2302E
Environment variable <env_var> must

be set!
User response:
v Check the tdphdwdb2 file in the directory
/usr/tivoli/tsm/acssap/db2/1.x.y.z, and set the
access rights for tdphdwdb2 with chmod 4750
tdphdwdb2. After the installation, the command
ls -l tdphdwdb2.... outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 tdphdwdb2

it.)
v If the file system in which tdphdwdb2 is installed
was mounted with the NOSUID option, mount the
file system with SUID allowed.
IDS2306I
Issuing command <cmd>

INSTHOME: to the home directory of the DB2 user
DB2INSTANCE: to the DB2 instance DB2DBDFT: to the
DB2 default database

message when running a system command.

and try again.

message when running a DB2 command.

IDS2307I
Issuing DB2 command <cmd>

IDS2303E
Environment variable <env_var> is not

correct!

directory path.
IDS2310W

containing the directory <dir> is only
<freespace>.

checked:
v the database home directory and
1027
v the directory specified by the parameter

v the directory containing the idssave file specified by
If the free space of these file systems falls below of 50
mega bytes, DP for Snapshot Devices warns the user. If
it is under 5 mega bytes an error will be issued and the
program fails throwing an exception.
IDS2311E

directory <dir>.

systems (see Explanation of IDS2310W) is under 5
mega bytes this error message will be issued and the
program fails, throwing an exception.
IDS2315W
Environment variable DB2NODE has

value <value>.
Explanation: In DB2 UDB EEE environments the

environment variable DB2NODE is used by DB2 to
attach or connect to a specified EEE partition. If this
variable is set prior to starting DP for Snapshot
Devices, then DP for Snapshot Devices must unset this
variable for the DP for Snapshot Devices execution.
User response: None
IDS2316E
Environment variable DB2NODE could

not be unset!
Unset this variable and restart
tdphdwdb2.
Explanation: In DB2 UDB EEE environments the

environment variable DB2NODE is used by DB2 to
attach or connect to a specified EEE partition. If this
variable is set prior to starting DP for Snapshot
Devices, then DP for Snapshot Devices must unset this
variable for the DP for Snapshot Devices execution.
While trying to unset the variable DB2NODE, DP for
Snapshot Devices encountered an error.
User response: You have to unset the variable
DB2NODE manually and rerun DP for Snapshot
Devices.
IDS2317I
Environment variable DB2NODE is

successfully unset.
Explanation: Explanation: In DB2 UDB EEE

environments the environment variable DB2NODE is
used by DB2 to attach or connect to a specified EEE
partition. If this variable is set prior to starting DP for
Snapshot Devices, then DP for Snapshot Devices must
1028
unset this variable for the DP for Snapshot Devices

execution.
User response: None
IDS2326E
The function -f restart_backup can only

be used on the backup system.
Explanation: You cannot start the restart_backup

function on the production system.
User response: Make sure you start tdphdwdb2 with
the function -f restart_backup on the backup system
only. Ensure that the profile contains a valid entry for
LOGON_HOST_BACK.
IDS2327E

be started if the progress status
indicator (PSI) has a value of
PSI_MOUNT_DONE. Current value of
the progress status indicator (PSI) is
value.

restart_backup function. You can only use this function,
if the progress status indicator (PSI) has a value of
PSI_MOUNT_DONE.
User response: Specify the parameter
DB2_RESTART_TSM_BACKUP YES in the DP for
Snapshot Devices profile so that, on the next FlashCopy
backup run, the filesystems will be kept mounted on
the backup system so that the restart_backup function
can be used.
IDS2328E

be used if the TSM backup failed for at
least one DB2 partition.
Explanation: The last FlashCopy backup run was

successful. The TSM backups of all DB2 partitions were
successfully completed or the restart_backup function
was already successfully started so that all DB2
partitions have been successfully backed up to TSM.
The function restart_backup can only be started if a
TSM backup of at least one DB2 partition has failed.
IDS2407E
Not enough memory space.
Explanation: The operating system returned an error

while allocating memory.
User response: Check the memory settings for the
users root and db2<sid>. See message IDS2200E for
details.
IDS2408W

the backup system.

start of the function flashcopy if any of the files passed
in the file list still exist on the backup system. If so,
then this warning will be issued. Normally, none of the
files should exist because the withdraw function, which
production system. If the database manager was

already started, you have to check your network and
db2 setup. Possible reasons may be
v missing db2 instance level registry parameter
DB2COMM=TCPIP
v wrong db2 database manager configuration
parameter SVCENAME
v different db2 TCP/IP ports on the production and
backup system
IDS2505E
User response: Always run the function withdraw

IDS2500E
DB2 command failed: <cmd>.
Explanation: The DB2 command <cmd> failed.

User response: Check for the SQL-Code returned by
the DB2 command and/or check for errors in the DB2
diag logfile.
IDS2501E
DB2 connection to production database

<DBname> failed.
Please start the database manager on
production system.
Explanation: DP for Snapshot Devices tried to connect

to the DB2 database <DBname> on the production
system via a db2 remote connection. While trying to
connect, DP for Snapshot Devices encountered an error.
Typically in this error situation the database manager
on the production system was not started.
User response: If the database manager on the
production system was not started, the you have to
start it by calling db2start as user db2<sid> on the
production system. If the database manager was
already started, you have to check your network and
db2 setup. Possible reasons may be
v missing db2 instance level registry parameter
DB2COMM=TCPIP
v wrong db2 database manager configuration
parameter SVCENAME
v different db2 TCP/IP ports on the production and
backup system
IDS2502E
Attachment to production DB2 instance

<instance> failed. Please check if the
database manager on production system
is started.
Explanation: DP for Snapshot Devices tried to attach

to the DB2 instance <instance> on the production
system via a db2 remote connection. While trying to
attach, DP for Snapshot Devices encountered an error.
Typically in this error situation the database manager
on the production system was not started.
User response: If the database manager on the
production system was not started, then you have to
start it by calling db2start as user db2<sid> on the
The DB2 instance <instance> is running

in <bitwidth> bit mode but tdphdwdb2
is running in <bitwidth> bit mode.
Explanation: DP for Snapshot Devices determined,

that the DB2 instance <instance> is running in
<bitwidth> bit mode. But the version of DP for
Snapshot Devices which is installed, is running in a
different bit mode. This is not allowed.
User response: You have to install the DP for
Snapshot Devices package with the correct bitwidth
IDS2510E
The DB logretain mode is not

supported. Please switch logretain to
RECOVERY.
Explanation: The DB2 production database must be in

archival logging mode.
User response: Change the DB2 database
configuration parameter LOGRETAIN to RECOVERY
with the command: db2 update db cfg for <SID> using
LOGRETAIN RECOVERY Important: After changing
this parameter, you must restart the database and you
must perform a backup of the database.
IDS2511E
The DB userexit mode is not supported.

Please switch DB userexit ON.
Explanation: The DB2 Userexit mode of the

production database must be set to on.
User response: Change the DB2 database
configuration parameter USEREXIT to ON with the
command: db2 update db cfg for <SID> using
USEREXIT ON
IDS2515E
SMS tablespaces are not supported
Explanation: The DB2 production database must not

have any SMS tablespaces.
User response: Change the corresponding SMS
tablespace to be managed by database (DMS).
IDS2516E
Tablespaces of type UNKNOWN are not

supported.
Explanation: DP for Snapshot Devices determined one

or more tablespaces with an unsupported type on the
1029
production DB2 database. Only DMS tablespaces are

supported. .
User response: Change all tablespaces to DMS
IDS2517E
Tablespace <TBSname> is not in

NORMAL state.
Explanation: DP for Snapshot Devices determined that

tablespace <TBSname> on the production DB2 database
is in an unsupported state.
User response: Make sure, that all tablespaces are in
state NORMAL
IDS2518E
Tablespace container <CONTname> is

in exception state.
Explanation: DP for Snapshot Devices determined that

tablespace container <CONTname> on the production
DB2 database is in an unsupported state.
User response: Make sure, that all tablespace
containers are in state NORMAL
IDS2520I
Node <nodename> has been created
Explanation: DP for Snapshot Devices has created a

new DB2 node <nodename> on the backup system. The
remote database on the production system will be
cataloged on this new node.
IDS2521I
Database <DB alias name> has been

cataloged
Explanation: On the backup system DP for Snapshot

Devices has cataloged the remote database <DB alias
name> of the production system. This database alias
name is used to connect to the remote database on the
production system.
IDS2522I
Press [ENTER] when all logfiles are

restored...
Explanation: DP for Snapshot Devices is waiting for

confirmation that all log files needed for the DB2
recovery process are restored from TSM.
User response: If you are performing a FlashBack
Restore and if you have configured the SAP DBA tools
(db2uext2, brarchive, brrestore) for indirect archiving
(using the SAP DBA administration database
ADM<SID>), you have to do the following steps, prior
to restoring the log files from TSM:
v drop the SAP DBA administration database
ADM<SID>
v recreate the SAP DBA administration database
ADM<SID> by calling sddb6ins r as user root.
1030
IDS2550E
Database <DBname> cannot be set to

write suspend mode
Explanation: DP for Snapshot Devices tried to

suspend the write activities on the production DB2
database.
User response: Make sure, the database is up and
running.
IDS2551E
Database <DBname> cannot be set to

write resume mode
Explanation: DP for Snapshot Devices tried to resume

the write activities on the production DB2 database
User response: Make sure, the database is up and
running.
IDS2555E
Connection to production system via

socket failed...
Explanation: DP for Snapshot Devices tried to connect

to the production system via TCP/IP socket
communication. Normally the cause for this error is,
that the DP for Snapshot Devices socket server on the
production system is not running or the configuration
for the DP for Snapshot Devices socket communication
on the production and / or backup system is incorrect.
User response: User Response: Check the DP for
Snapshot Devices socket configuration (/etc/services,
/etc/inittab) and check for a running DP for Snapshot
Devices socket server on the production system.
IDS2600E
Starting synchronization for all EEE

nodes failed
Explanation: DP for Snapshot Devices tried to start

the synchronization for all DB2 logical / physical EEE
partitions on the production server which holds the
coordination EEE partition.
User response: Restart the socket server on the
production server which holds the EEE coordination
partition. Use the function stopsocket. After stopping
the socket server, it will automatically be restarted
because of the entry in the /etc/inittab file.
IDS2601E
SyncPoint <port> was not reached for

all EEE nodes
Explanation: While DP for Snapshot Devices is

waiting for all running tdphdwdb2 processes to reach
the specified SyncPoint, one or more tdphdwdb2
processes have not reached this syncpoint. This error
can have the following reasons:
1. The DP for Snapshot Devices parameter
DB2_EEE_SYNCTIMEOUT is set too low. Check it
in the DP for Snapshot Devices configuration file
2. DP for Snapshot Devices is not started for each
production servers
3. One or more DP for Snapshot Devices processes

running for the production servers were terminated
User response:
1. Check the DP for Snapshot Devices parameter
2. Check that DP for Snapshot Devices is running on
the backup system for all production servers.
3. Check for error messages in the DP for Snapshot
Devices log files for each process.
IDS2607I
Enter the TCPIP service port for the

socket server [57330]:

implemented a TCP/IP socket communication. For
configuration of the socket communication, a TCP/IP
service port must be defined on the production and
backup systems. The DP for Snapshot Devices function
configure will perform this configuration on the
production system. You have to enter a TCP/IP service
port to use for DP for Snapshot Devices.
User response: User Response: None
IDS2608E
The TCPIP service port <port> is

already in use. Please select another
port.

backup system. The DP for Snapshot Devices function
User response: You have to enter a valid TCP/IP port,
which is not used.
IDS2609E
The TCPIP service port <port> is

invalid. Please select another port.

backup system. The DP for Snapshot Devices function
User response: You have to enter a valid TCP/IP port.
1031
1032
Chapter 12. Data Protection for Snapshot Devices for mySAP

for Oracle Version 5.4.1 (EEO0000EEO7999) and
(IDS0000IDS1999)
This chapter describes the messages issued by the components of Tivoli Storage
Manager for Advanced Copy Services: Data Protection for Snapshot Devices for
mySAP for Oracle Version 5.4.1. The two components are:
v Data Protection for FlashCopy Devices for mySAP for Oracle
v Data Protection for N Series Snapshot for mySAP for Oracle
The messages begin with either the prefix EEO or IDS and are listed in numerical
order.
Prefix EEO
EEO0020I
====>Performing DP for Snapshot

Devices <v1> command.
EEO0059E
Explanation: This message is displayed starting the

specified function.
EEO0022I
AIX Version: <var1> Oslevel: <var2>.
The database was backed up using

NOCOPY type of FlashCopy. The data
in the target volumes is not valid, and
cannot be used to perform a FlashBack
Restore.

FlashBack Restore, the database needs to be backed up
using the COPY or INCR type of FlashCopy.
User response: Restore the database from TSM Server.

EEO0062E
EEO0030I
Number of volumes involved in the

FlashCopy: <v1>

FlashCopy.
EEO0056I
Received error errno while disabling

the new resources.

EEO0058I
Received error errno while resetting

the target volumes.
The source/target LUN information in

the setup file has been modified.
FlashBack Restore is currently not
supported for restoring the database to a
new location.
Explanation: The source/target information in the

setup file cannot be modified. In order to back up the
file. At this time, FlashBack Restore is only supported
for restoring the database to the original source LUNs.
User response: The source/target information in the
file. If you want to restore the database to a new
location, restore it from the Tivoli Storage Manager
server.
EEO0065E
IBM2105 Copy Service CLI is not

installed.

attempted to withdraw the FlashCopy relationship
Explanation: The ibm2105cli.rte file is not installed.

lslpp -lc ibm2105cli.rte command failed.
User response: Make sure Copy Service CLI is

installed on your host machine.
1033
EEO0068W EEO0125E
EEO0068W
WARNING!!! Incremental Change

Recording is enabled. Performing
incremental FlashCopy instead of
NOCOPY type of FlashCopy.
Explanation: Incremental Change Recording is

enabled. Performing a NOCOPY type of FlashCopy will
fail in this case.
User response: Withdraw the persistent FlashCopy
relationship for all the source volumes for this
database, using the DP for Snapshot Devices withdraw
FlashCopy.
EEO0069W
WARNING!!! Incremental FlashCopy

of AIX: <v1>. A generic FlashCopy will
be performed instead.
Explanation: Incremental FlashCopy is only supported

lower than 5.1.0, an incremental FlashCopy cannot be
performed.
User response: Upgrade to AIX version 5.1.0 or later
in order to take advantage of the Incremental
FlashCopy feature.
EEO0070E
Some of the volumes belonging to this

database have Incremental Change
Recording enabled while others do not.

FlashCopy, all the volumes belonging to the database
must have Incremental Change Recording enabled.
User response: Withdraw the FlashCopy relationships
for those volumes that have Incremental Change
Recording enabled, using the DP for Snapshot Devices
withdraw command, and then retry the command. In
the case of the monitor command (FlashCopy agent),
withdraw the FlashCopy relationships and retry both
the backup and monitor (FlashCopy agent) commands.
In an SAP environment, you only need to retry the
backup, because the FlashCopy agent is started
automatically.
EEO0071I
Source volume: <v1> Target volume:

<v2> Pending Sectors: <v3>

copied from source volumes to target volumes in case
of backup or from target volumes to source volumes in
case of restore.
EEO0120E
A null logical volume has been detected.

determine a logical volume name from the list of
database files.
errors.
EEO0121E
A null volume group has been detected.

determine a volume group name from the list of
database files.
errors.
EEO0122E
An error is detected in volume group :

vg1.

volume group.
is specified correctly in the setup file. Verify that the
AIX volume manager is running. If the problem
persists, gather information from the trace file and log
file and contact your IBM service representative.
EEO0123E
The physical volumes of the volume

group <v1> were not found.

command lsvg -M <vgname> in an LVM mirror
environment to determine the physical and logical
volumes on which the production database resides.
This command failed.
User response: Check the return code of lsvg. Consult
the AIX system documentation.
EEO0124I

system.
User response: None
EEO0125E
The serial number for the device

logdev could not be found.
Explanation: DP for Snapshot Devices will determine

the volume serial numbers from the list of database
files passed. In order to do that, several system
commands will be used such as: lscfg -pvl devname or
lsvpcfg or hdwmap.sh. One of these commands has
failed or the specified device was not displayed.
User response: Check the specific error message. Issue
the commands above from the command line and
1034
EEO0126I EEO0140I
check that the specified device is displayed in the list.
EEO0126I

some time...

to match the source device.
EEO0127I
Removing device : devname

(ODM) on the backup system after the backup has
ended and prior to withdrawing the relationships of
the volumes.
EEO0131E
The physical volume ID <pvid1> is

duplicated on the production machine.

that two logical devices (hdisk/vpath) have the same
physical volume id.
v If the hdisks with the same pvid belong to the same
multipath, convert the hdisk device volume group to
a Subsystem Device Driver vpath device volume
group.
v If the problem is the result of a corrupt ODM,
consult the AIX Troubleshooting documentation
v If the physical volume involved neither belongs to a
volume group nor contains file systems to be
imported in the future, you can clear the pvid by
arguments: chdev -l hdisk# -a pv=clear
User response: None

EEO0132W
EEO0128E
Configuring the target volume would

cause duplicate physical volume ID :
pvid1

The umount command failed with rc

<rc> for mount point <mntpt>.


1. Delete the disk on the backup system only:
a. find the disk using the AIX lspv command
b. run smitty and choose the following from the
menu: devices- fixed diskremove a disk- select
the disk to be removed
c. press return
2. Clear the pvid of each physical volume hdisk by
arguments: chdev -1 (hdisk#) -a pv=clear .
EEO0138I
EEO0129E
Removing device parm1 failed.

(ODM) on the backup system after the backup ended
and prior to the withdraw of the relationships of the
volumes. The rmdev command has failed.
Consult the AIX system documentation. Check if the
device is a member of an active volume group. Check
EEO0130W
Removing the mount point directory

<mntpt1> failed with rc: <rc1>.

FlashCopy type is set to NOCOPY.

disks.. This backup is NOT valid for a
FlashBack Restore. Please restore from
TSM Server.

valid for a FlashBack Restore. You can only restore
from a TSM Server.
EEO0139W
Removing the file system on the mount

point <mntpt1> failed with rc: <rc1>.

remove a file system during the FlashBack Restore.
Processing continues. The restore will resolve this
problem.
EEO0140I
FlashCopy type is set to COPY or INCR.

target disks.. This backup is valid for a
FlashBack Restore.
Explanation: The target PVIDs are not cleared. This

This backup can be used for a FlashBack Restore.
Chapter 12. Data Protection for Snapshot Devices for mySAP for Oracle
1035
EEO0143E EEO0161E
EEO0143E
Unsupported volume group <v1> has

been detected.
Explanation: The volume group to which the database

has been allocated is an unsupported type.
rootvg.
EEO0146E
A physical disk from the volume group

vgname was not found.
Explanation: A physical disk from the specified

database volume group was not found in the Device
Configuration database.
Consult the AIX system documentation. Check if this
device is a member of one active volume group. Check
EEO0147I
Exporting volume group vgname

failed.

command exportvg prior to the withdraw of the
FlashCopy relationships to remove the volume group
from the Device Configuration database. This command
has failed.
preceding errors during the unmount of the file
systems.
EEO0151E
Varying off volume group vgname

failed.
Explanation: Prior to the withdraw of the FlashCopy

relationships, DP for Snapshot Devices will vary off the
database volume group on the backup system. The
command varyoffvg has failed.
preceding errors during the unmount process.
EEO0152I

groups.
EEO0153I

vgname..
Explanation: The specified volume group was varied

off and exported successfully.
User response: None
EEO0154I
<lvname> <copy> <pv> <serialno>

<status>
Explanation: Finding the source volumes of the

production database in an LVM mirror environment,
DP for Snapshot Devices will display a list of all the
logical volumes with the number of copies, the physical
volumes, the serial number and the status. The status is
only displayed for the case of stale partitions.
EEO0148I

command.
User response: None
EEO0149I
Newly imported volume group:

vgname

imported this new volume group on the backup system
after the FlashCopy.
User response: None
EEO0150E
Logical Volume cannot be found for the

file fnm1.
Explanation: An error has occurred determining the

logical volume of a file in the list of database files.
1036
EEO0156I
Finding the serial numbers ...
Explanation: DP for Snapshot Devices gets as input a

list of database files to be backed up and from them
determines the logical volumes, volume groups and
serial numbers of the physical volumes where the
production database resides.
User response: None
EEO0161E
No volume group was found.
Explanation: The AIX command lsvg failed on the

backup system, and the newly added volume groups
after the FlashCopy could not be determined.
EEO0162E EEO0180E
EEO0162E
Volume group <vg1> cannot be found.
Explanation: The AIX commandlsvg failed on the

production system and the source volumes of the
production database could not be determined.
EEO0164E
Quorum of the volume group vgname

must be off.

environment, DP for Snapshot Devices requires that the
quorum of the volume group be set to off. If a mirror is
inactive due to a failure, the database should continue
working properly.
EEO0172E
Logical volume lvname must have

mirror write consistency on.
Explanation: Mirror write consistency ensures data

consistency among mirrored copies of a logical volume
during normal I/O processing. If a system or volume
group is not shut down properly, then mwc will
identify which logical partitions may be inconsistent.
DP for Snapshot Devices requires that this capability be
set for the logical volumes of the production database.
User response: Set mirror write consistency on.
EEO0174E
None of the mirror copies of the logical

volume lvname resides completely on
the specified hardware unit identifier.
User response: Set the quorum of the volume group

off.
Explanation: DP for Snapshot Devices requires that all

the partitions of one mirror set reside on the physical
volumes of one hardware unit.
EEO0166E
User response: You have to reconfigure the allocation

Logical volume vgname must have at

least 2 copies.
Explanation: If the parameter for working with LVM

mirrors is active, DP for Snapshot Devices requires that
two copies of each logical volume exist.
User response: Create a copy of each logical volume
on separate machines. Ensure that, for each source
volume, you have a target volume for the FlashCopy in
the same hardware unit.
EEO0168E
Logical volume lvname must have the

parallel scheduling policy.
Explanation: DP for Snapshot Devices requires the

parallel scheduling policy. With the parallel scheduling
policy, there is no primary or secondary mirror. All
copies in a mirror set are referred to as copies,
regardless of which one was created first.
User response: Set the scheduling policy of this logical
volume to parallel.
EEO0170W
Logical volume lvname has number

stale partitions.

partitions.
User response: Check why you have stale partitions.
If necessary, synchronize the logical volumes of the
EEO0176E
Some of the partitions of lvname are

stale on the specified hardware unit
identifier.

partitions.
User response: Check the reason you have stale
partitions. Synchronize the logical volumes of the
EEO0178I

value of 1.
Explanation: DP for Snapshot Devices supports SDD

(Subsystem Device Driver). SDD is a pseudo device
driver designed to support the multipath configuration
environments in the storage system and is used to
enhance data availability. DP for Snapshot Devices will
determine the number of multiple paths by querying
the Device Configuration database (ODM).
User response: If you want to take advantage of SDD,
check the Subsystem Device Driver Users Guide for a
correct configuration.
EEO0180E
Failure in changing the mount point

mp, return code rc from command
chfs.

the FlashCopy on the backup system. Because
1037
EEO0182E EEO0291E
recreatevg inserts the prefix /fs at the start of the
mount point, DP for Snapshot Devices must remove it
by calling the command chfs to the original names.
preceding errors.
group on the backup system. The command varyonvg

has failed.
preceding errors.
EEO0272I
EEO0182E
The same hdisk devname cannot be

(serial numbers serial#1 and serial#2).

encountered a corrupted configuration in your system.
User response: By issuing the command lsvpcfg you
can identify this error. Check the Subsystem Device
Driver Users Guide for a correct configuration.

buffers to disk.
User response: None
EEO0273I

User response: None
EEO0184E
lsvg command failed.
Explanation: DP for Snapshot Devices uses the

command lsvg to determine the physical and logical
volume of the volume group. This command has failed.
preceding errors.
EEO0274I
Explanation: The new resources will be available after

the FlashCopy.
User response: None
EEO0275I
EEO0186I
Recreating the new volume groups...

the FlashCopy on the backup system.
User response: None
EEO0188E

preceding errors.
EEO0190E
The number of new volume groups is

limited to 256.
Explanation: DP for Snapshot Devices can support a

database with a maximum of 256 volume groups.
EEO0191I
Varying on volume group vgname

failed.
Explanation: After the importvg or recreatevg, DP for

Snapshot Devices will vary on the database volume
1038
Explanation: The number of file systems exceeds the

compiled limit of 4096.
EEO0290E
lvm queryvg failed.
Explanation: DP for Snapshot Devices uses the system

routine lvm_queryvg to read information of the VGDA
of the volumes.

serial # is no longer attached to the
production system.

during the FlashBack Restore, it could no longer be
found on the production system.
Use the storage-system user interface to find out which
host this volume is attached to. You will be able to
restart the FlashBack Restore anytime, as long as you
have a valid disk backup on the target volumes.
EEO0291E

serial # belongs to another volume
group.

during the FlashBack Restore, DP for Snapshot Devices
found it as a member of another volume group and
cannot proceed with the restore.
EEO0292W EEO0302E
specified FlashCopy backup for the FlashBack Restore.
You will be able to restart the FlashBack Restore
the target volumes.
EEO0292W
The logical volume lvname on the

mount point mp was renamed or
newly added.

difference between the names of the logical volumes
which were on the production database at the time of
FlashCopy backup and the current logical volumes at
the time of the FlashBack Restore.
User response: DP for Snapshot Devices will ask you
during the FlashBack Restore if you are sure you want
to continue, before all the file systems and logical
volumes are removed. After that, DP for Snapshot
Devices will only reconstruct the file systems which
were backed up with FlashCopy. You have to manually
add all the additional system changes that were made
after the FlashCopy backup.
EEO0293I


all the file systems which are currently on the

restored...

all the file systems that were on the production
User response: None
EEO0297W
The newly added volume logdev will

be deleted from the database volume
group vgname.

Snapshot Devices will call this command during the
FlashBack Restore to remove the physical volumes
FlashCopy backup.
User response: None

after the FlashCopy process in the
the LVM copies.
Explanation: DP for Snapshot Devices will not

automatically synchronize the copies after the
will be created and displayed.
process in the background has finished. If necessary
you have to add additional parameters to the
commands to improve the performance of the
synchronization.
EEO0300E
Error converting the hdisk device

volume group vgname to a Subsystem
group.
Explanation: For the function FlashCopy backup, DP

for Snapshot Devices will use the command hd2vp to
convert the hdisk device volume group to a Subsystem
Device Driver vpath volume group. This will take effect
after the importvg and prior to the mount of the file
systems on the backup system.
EEO0301W
User response: None

EEO0294I
EEO0299I
The rmlv command lv ended with

return code rc.

for Snapshot Devices will use the command rmlv to
remove the logical volumes onto which the production
database should be restored. This will take effect after
the unmount and prior to the exportvg and the actual
FlashCopy reverse.
FlashBack Restore anytime, as long as you have a valid
disk backup on the target volumes.
EEO0302E
DP for Snapshot Devices encountered a

function of Copy Services.
Explanation: DP for Snapshot Devices requested, for a

set of source/target volume pairs, that a FlashCopy be
done by the Copy Services. If the request fails within
the storage system with a non-zero return code for one
or more pairs, DP for Snapshot Devices will provide
the return code and then terminate.
User response: In order to identify which volume(s)
were the cause of the problem, you need to view the
Copy Services status log for failures. There, you will
1039
EEO0303E EEO0311W
find the failing volume(s) along with details about
EEO0303E
The file system fs already has an entry

in /etc/filesystems.
Explanation: On the backup system after the

FlashCopy, DP for Snapshot Devices found that the
specified file system still exists in /etc/filesystems.
User response: Normally the command exportvg will
remove the corresponding file systems from
/etc/filesystems. Check for errors during the
unmount and withdraw process.
EEO0304W
The reducevg command cmd ended


Snapshot Devices will call it
1. on FlashBack Restore to remove the physical
volumes added after the FlashCopy backup
2. on FlashBack Restore with LVM mirroring to
remove the physical volumes which reside in the
hardware unit that is not yet involved in the
FlashBack.
3. on FlashCopy backup with LVM mirroring if the
environment variable IMPORTVG is set, to remove
the physical volumes which reside in the hardware
unit that is not yet involved in the FlashCopy
EEO0305W
The extendvg command cmd ended


volumes to a volume group. DP for Snapshot Devices
will call it to add the volumes which reside in the
hardware unit that is not yet involved in the FlashBack
to the database volume groups.
EEO0306W
The mklvcopy command cmd ended

Explanation: DP for Snapshot Devices will call the

command mklvcopy to add a copy of a logical volume
on the physical volumes residing in the second
hardware unit. This call will only take effect in an LVM
mirroring environment, after the FlashBack Restore was
initiated. The FlashBack Restore and the recovery will
continue, but the second copy of the logical volumes
will be missing.
1040

Restore anytime, as long as you have a valid disk
backup on the target volumes.
EEO0307I

volumes ...

for Snapshot Devices will use the command rmlvcopy
to remove the copies of the logical volumes residing in
the second hardware unit. This will take effect after the
unmount and prior to the exportvg and the actual
FlashCopy reverse.
User response: None
EEO0308I
Removing physical volumes from the

volume groups ...
Explanation: For the function FlashBack Restore, after

the rmlvcopy and prior to the exportvg and the actual
FlashCopy reverse, DP for Snapshot Devices will use
the command reducevg to remove the physical
volumes residing in the second hardware unit.
User response: None
EEO0309I

groups ...
Explanation: On the function FlashBack Restore, after

the FlashCopy reverse and the import of the volume
groups, DP for Snapshot Devices will add the physical
volumes residing in the second hardware unit to the
database volume groups.
User response: None
EEO0310I
Explanation: On the function FlashBack Restore, DP

for Snapshot Devices will use the command mklvcopy
to add the copies of the logical volumes on the second
hardware unit. This will take effect after the importvg
and the extendvg.
User response: None
EEO0311W
The command cmd ended with return

code rc.

EEO0312E EEO0322W
EEO0312E
Importing the volume group from hdisk

logdev failed.

command importvg on the function FlashCopy backup.
after the actual FlashCopy and the run of the
configuration manager (cfgmgr). It takes a volume from
each volume group making up the production
database, reads its VGDA and makes this information
available to the operating system.
list of the file systems that reside on the FlashCopy

target volumes. These will be restored by means of
FlashBack.
EEO0317W

resources. However, the FlashBack
Restore will continue.


running the function FlashBack Restore, an error occurs
unmounting the existing file systems and removing the
volume groups. However, DP for Snapshot Devices will
continue with the FlashBack Restore.
EEO0313E
Recreating the volume group from the

hdisks hdisks failed.

command recreatevg for the function FlashCopy
backup if the production database resides in a
high-availability LVM mirror environment. This
command will be issued on the backup system after the
actual FlashCopy and the run of the configuration
manager (cfgmgr). The difference from the command
importvg is that recreatevg will create the volume
group only with the specified volumes. These form
exactly the one copy on the hardware unit where the
FlashCopy was issued.
EEO0314W
Removing the logical device logdev

with the same PVID pvid in the ODM.
EEO0320E

that no physical volume hdisk/vpath exists with this
pvid, although the pvid was found on the descriptor
area of the volume group.
User response: You very likely have an ODM
corruption for the involved volume group. Check this
volume group with the command lsvg -l <vgname>
and lsvg -p <vgname>. Depending on the error, you
have to take different actions. Consult the AIX
troubleshooting documentation to repair the ODM.
EEO0321E
Explanation: There is still a logical device (hdisk or

vpath) in the state defined with the same PVID as one
of the source volumes.
User response: None
EEO0315I

originally present.

running the function FlashBack Restore, a file system
was found that was added after the FlashCopy backup.
User response: The user is responsible for creating the
new file system after the FlashCopy reverse, but before
EEO0316W
The database volume groups do not

currently contain any file system.

running the function FlashBack Restore, no file system
was found on the original database volume group.
Following this, DP for Snapshot Devices will display a
Although the pvid <pvid> is contained

in the descriptor area of the volume
group <vgname>, no logical device
(hdisk/vpath) has this on the production
system.
Physical volume <hdisk> is in the

descriptor area of the volume group
<vgname> but does not belong to this
volume group.
Explanation: The output of the command lsvg -p

<vgname> does not show that the hdisk/vpath belongs
to this volumegroup, but its pvid is registered in the
descriptor area of the volume group.
User response: If the hdisks with the same pvid
belong to the same multipath, convert the hdisk device
volume group to a Subsystem Device Driver vpath
device volume group. If you have ODM corruption,
check the involved volume group with the command
lsvg -l <vgname> and lsvg -p <vgname>. Depending
on the error, you have to take different actions. Consult
the AIX troubleshooting documentation to repair the
ODM.
EEO0322W
The major number of the volume group

<vgname> could not be determined.
Explanation: The command getlvodm, which is used

to determine the major number of the specified volume
group, failed. The option -V of the command
1041
EEO0323W EEO0332I
importvg will not be used on a FlashBack Restore of
this backup.

message.
User response: Check for error messages issued by

getlvodm.

EEO0328E
EEO0323W
Major number major already exists on

the production machine. The system
will assign the next available major
number to the volume group vgname.
Explanation: DP for Snapshot Devices found that the

major number of the given volume group is being used
by another device. The importvg command will be
issued without the option -V <major number>. The
system will then generate the next available major
number automatically.
User response: Check the major numbers on the
system with the command ls -al /dev.
EEO0324E
Production database does not reside in

an LVM mirror environment.
Explanation: The LVM mirroring capability of DP for

Snapshot Devices is on, but the database logical
volumes do not have a mirror copy.
User response: Set the parameter for LVM mirroring
off, or set up your system in a high-availability LVM
mirror environment.
Error thawing the file system fsname:

txtmsg.
Explanation: The function THAW failed for this file

system.
message.
EEO0329I
Freezing file system : fs1.
Explanation: Currently attempting to freeze the file

system.
EEO0330I
Thawing file system : fs1.
Explanation: Currently attempting to thaw the file

system.
EEO0325E
Error reading the status information of

the file system fsname: txtmsg
Explanation: The system call 'stat' failed. Check the

specific error message appended to this message. In
some cases the user will need administrator rights to
execute this command.
Ensure that the user has sufficient rights.
EEO0326W
The file system fsname is not of type

jfs2. The freeze/thaw function will be
applied only on file systems of type
jfs2.
Explanation: The freeze/thaw function will be applied

only on file systems of type jfs2.
EEO0327E
Error freezing the file system fsname:

txtmsg.
Explanation: The function FREEZE failed for this file

system.
1042
EEO0331I
Performing snaprestore of the source

volume srcvol to the snapshot snapid
(LUN lunpath).
Explanation: The function 'snaprestore' will revert the

source volume to the specified snapshot name. This
message will appear for each LUN involved in the
restore process. The snap restore is performed based on
the volume.
EEO0332I
Performing snapshot of the source

volume srcvol (LUN lunpath).
Explanation: A snapshot will be taken of this volume.

This message will appear for each LUN involved in the
snapshot process. However, when several LUNs belong
to the same volume, only one snapshot of this volume
is taken.
User response: None
EEO0333I EEO0358E
EEO0333I
The snapshot snapid was generated for

the source volume srcvol (LUN lunpath).
Explanation: A snapshot with the name displayed was

taken from this volume. This message will appear for
each LUN involved in the snapshot process. However,
when several LUNs belong to the same volume, only
one snapshot of this volume is taken.
Error to get the size of the target volume

src1 with return code rc1.
Explanation: The storage-system query command

cannot determine the size of the target volume.
EEO0351E
The sizes of source volume src1 and

target volume tgt1 are different.
Explanation: The sizes of the source volume and

target volume are different. The source volume and
target volume must be the same size and reside in the
same hardware unit.
EEO0352E
Wrong volume size for the target

volume tgt1 is specified in the setup
file.
Explanation: The TARGET_VOLUME parameter specifies

an incorrect size for the target volume.
User response: Make sure the parameter in the setup
file specifies a correct size for the target volume. If you
do not know the exact size of the target volume,
specify a dash (-) for both the source value and size
value. The size of the target volume will be determined
automatically.
Performing <fctype> FlashCopy of

source volume <src1> to target volume
<tgt1>
Explanation: A FlashCopy from the source volume to

EEO0355E
User response:
EEO0350E
EEO0354I
The FlashCopy command failed.
Explanation: The FlashCopy command failed. This

could be due to various reasons:
1. Some library or jar files may be missing from the
Copy Services command line interface package.
2. The source volumes or target volumes are in
another FlashCopy relationship.
3. The Copy Services command line interface package
and Copy Services microcode are not in sync.
are in another FlashCopy relationship, wait until the
with the storage system administrator to obtain the
appropriate level of Copy Services command line
interface and microcode.
EEO0356E
Cannot find a target volume to match

the source volume parm1.
Explanation: A target volume could not be found.

1. TARGET_VOLUME
EEO0357I
Performing FlashCopy withdraw of

source volume <src1> from target
volume <tgt1>
Explanation: A FlashCopy withdraw of the source

EEO0353E
Unable to open file file1.

EEO0358E
No target volume is available.

Terminating......

1. TARGET_VOLUME
1043
EEO0359I EEO0376E
Explanation: Value of Incremental Change Recording.
Explanation: Whenever the user performs an

incremental FlashBack Restore operation, the source
and target volumes will be reversed.
EEO0360I
EEO0368I
EEO0359I
Incremental Change Recording: <val1>
Querying the storage system for the size

of volume volser1...

ready...

requested.

ready.
User response: None
User response: None
EEO0361I
EEO0371I
A NOCOPY FlashCopy was performed.

Withdrawing the NOCOPY FlashCopy
relationship
Explanation: The FlashCopy relationship between the

NOCOPY FlashCopy is performed.
Explanation: None.
EEO0372I
User response: None

EEO0362I

Services server...

User response: None
EEO0363I

ready.
Value of FlashCopy type is: <parm1>.

been specified.

defined in the setup file. An attempt to use the backup
User response: None
EEO0374I
Querying the storage system for the

status of volumes volser1...

User response: None

EEO0375E
EEO0365I

Services server...

User response: None
EEO0366I
FlashCopy was performed with

<parm1> option.
Explanation: This is the type of FlashCopy that was

specified by the user, since DP for Snapshot Devices
overrides this value under certain conditions.
EEO0367I
1044
Source and target volumes have been

switched due to a previous incremental
FlashBack Restore operation. Previous
target volume: <parm1> is now the
source volume. Previous source volume:
<parm2> is now the target volume.
Error: Volumes are involved in a

FlashCopy or a PPRC operation.
Explanation: Source or target volumes are involved in

a FlashCopy or a PPRC operation. FlashCopy backup
or restore command will not be performed.
volumes are not in use in a FlashCopy or PPRC
operation, before issuing the FlashCopy backup or
restore command.
EEO0376E
Error: target volume v1 involved in the

previous backup does not exist in the
setup file.
Explanation: The list of target volumes specified in

the setup file for restoring a specified database using
FlashBack Restore needs to be the same as those
specified in the setup file at the time of FlashCopy
Backup. This is necessary to ensure that a complete
image of the database is available to the restore
process.
User response: Ensure that the target volumes
specified in the setup file are accurate.
EEO0380E EEO1627E
EEO0380E
An invalid value: <parm1> has been

specified for FlashCopy type.
EEO0648E
Explanation: FlashCopy type can only be NOCOPY,

COPY or INCR.
User response: Specify NOCOPY, COPY or INCR for
the option FlashCopy type and retry the command.
EEO0381I
Querying storage system for pending

sectors for volume: <volser1>

volumes was requested to ensure that a background
copy is not in progress between them.

Tivoli Storage Manager function name :
function-name
Tivoli Storage Manager function :
function-desc
Tivoli Storage Manager return code :
TSM-rc
Tivoli Storage Manager file :
Explanation: None.
User response: Contact the Tivoli Storage Manager

administrator with the information provided in this
message.
EEO0400E
EEO0651E
Error on running command: parm1

system command.
EEO0630E
A memory allocation error has occurred.

applications.
EEO0640E
Explanation: A FlashCopy background copy from a

and target volumes.
System action: The command will fail.
User response: Wait until the background copy is
complete and retry the command.
EEO1625I
Could not open trace file <v1>.

EEO1626E

Could not create the trace object.
Explanation: There was a problem creating the trace

class object.
EEO0647E
Number of volumes to be processed by

FlashCopy: v1

FlashCopy.

tracefile. Make sure you can open the trace file which
was specified in the setup file.
EEO0641E
A FlashCopy background copy is in

progress between source volume: source
volume and target volume: target volume.

processing a Tivoli Storage Manager for
Hardware function.
Explanation: None.
A FlashCopy association exists between

source volume: source volume and a
different target volume: target volume.

Explanation: A FlashCopy association exists between

EEO1627E
System action: The restore command will fail.
Explanation: The specified virtual disk was not found

in the list of virtual disks provided by the connected
SVC cluster.
User response: Withdraw the FlashCopy association

between the source and target volumes and retry the
restore command.
1045
EEO1628E EEO2054E
the SVC cluster.
EEO1628E


virtual disks are in the same SVC cluster.
EEO1636I
The option fractional reserve on volume

vol_name was reduced to less than 100
percent.
Explanation: When using N series devices, it is

strongly recommended that, when the fractional reserve
is set to less than 100%, you actively monitor space
consumption and the rate of change of data on the
volume to ensure you do not run out of space reserved
for overwrites. In this case, if you run out of overwrite
reserve space, writes to the active file system fail and
the host application or operating system might crash.
System action: The process continues.
EEO1629E


virtual disks have the same size.
EEO1630E

operation of the Common Information
Model (CIM).
TDP CIM return code: 0xCIM-rc
Explanation: An error occurred calling a CIM

User response: See CIM Agent Return Codes (SVC)
in Data Protection for Snapshot Devices for mySAP
Installation and Users Guide for Oracle for possible
values of CIM-rc.
EEO1631E

User response: Ensure that you monitor the space

consumption. Consult the NetApp vendor for tools to
monitor available space on your volume.
EEO2051W

found on location.

be built in the specified directory.
EEO2052E

missing.

subsystem.
error messages.
EEO2053E




applications.

applications.
EEO1635I
EEO2054E
The ONTAP filer version on this

appliance is: n.
System action: Process continues.

Explanation: None.
1046
EEO2055I EEO2063W
EEO2055I

be locked.

application unlocks the local repository.
1. TARGET_VOLUME
EEO2060W

EEO2056I


application.
Explanation: While the local repository is locked by

period of time to proceed. In the mySAP environment,
that time is 1 hour.

container dcID to match the source srcvol.

the specific source no target volume could be found in
this target data container that matches for a FlashCopy
operation. If multiple target data containers are being
used, the processing will continue checking the
volumes of the next target data container.
EEO2061W
EEO2057E
Explanation: An inquiry of the data container with the

set does not exist in the local repository.

messages.
EEO2058E


corresponding properties. A failure occurred during
that process.
such as memory allocation error or other system error.
EEO2059W

matches the source data container.

Advanced Copy Services tries to find a target data
container that matches the source data container to
satisfy the FlashCopy backup. A matching target data
container could not be found.
are being used for the FlashCopy type COPY. Make
sure also that the target volumes are available to the


application that is requesting the inquiry will decide
whether or not the error should end the program.
EEO2062W

criteria.

application specific. Check for succeeding messages.
EEO2063W


1047
EEO2064I EEO2073E
EEO2064I

EEO2069E


being created.


permissions of the file.
EEO2065I


User response: Look for an operating system error
message.
EEO2066E

permissions for the file.
EEO2067E


EEO2070E

empty or has an incorrect format.

in not correct.
format of this file is correct. Check for a preceding
error.
EEO2071E


Inserting an entry for a new data container caused an
error.
preceding error. If no other error is indicated, collect
the logs and traces and contact support.

EEO2072E
EEO2068E

Explanation: The program will search in the .fct file,

for each specific data container, for a list of entries with
the label TARGET_VOLUME. Either you have an
incorrect label for the target volumes of the specified
data container or this data container in the .fct file does
not have any target LUNs.
User response: This error can only occur if the
format will be automatically checked. If so, please

processing a TSM for Hardware
function.
Explanation: None.
EEO2073E

writing.

generated an error.
1048
EEO2727E EEO7826E
User response: Check the permissions of the file.
EEO2727E
Lun ID v1 is not valid.
Explanation: Length of LUN ID must be 8 characters.

User response: Ensure the device for the tracefile is

available and has sufficient space for the file. Retry the
command.
EEO7826E

<filename>.
User response: Make sure the length of the LUN ID is

8.
Explanation: The DP for Snapshot Devices user does

not have permission to open the specified trace file.
EEO2729E
User response: Check the access rights for the

directory of the specified trace file.

failed; rc=rc.
Explanation: None.
EEO2730E
The primary and secondary Copy

Services servers are down.
Explanation: None.
User response: Start at least one of the Copy Services
servers.
EEO2731E
Cannot open the command output file

v1 for writing.
Explanation: The file cannot be opened for writing.

your system and write permissions to the file.
EEO2732E
The LUNs are already in use.
Explanation: None.
User response: Release LUNs in order to reuse them.
EEO7366E
Unable to close trace output file filename.

trace output filename (for example, not enough disk
space).
User response: Check the specific operating system
error message.
EEO7367E

Tracing disabled.

1049
Prefix IDS
IDS0064E
The parameter <parameter_name> in the

topic <topic_name> of the profile <.fcs
filename> is not known.
Explanation: In the section <topic_name> of the setup

file .fcs, a parameter was found that is not supported
by DP for Snapshot Devices.
User response: Remove the cited parameter from the
.fcs file.
IDS1000E
Profile not specified

must be defined.
IDS1009E

control file does not exist.

IDS_CONTROL_FILE is incorrect or the path does not
exist.

the profile.

IDS_CONTROL_FILE in the profile has a valid path. If
the path does not exist, you must create it.

that the splitint call must have the following form:
<path>/splitint -p <path>/init<SID>.fcs -f
<function>....
IDS1010E
IDS1001E
Function not defined

name with the option -f. Valid functions are: withdraw,
split, password, unmount, inquire, ts_inquire, flashback,
and resync.
IDS1004E
Subfunction not defined.
Option -i <backup_list> not specified.
Explanation: The function -f split requires the

specification of the option -i <backup_list> too.
User response: Ensure that you transfer the list of the
files to back up when you call the function -f split. The
SPLITINT interface uses the following syntax:
<path>splitint -u <user_id> [-f <function>]
[-t <type>]
[-i <in_file>]
[-o <out_file>]
[-c]
[-s <split_options>]

for the -s option of DP for Snapshot Devices. This
option has been designed for internal splitint use only
and should not be used externally.
When the FlashCopy function runs under the control of

brbackup, it is automatically passed the list of files via
the i option. The string specified in the parameter
split_options of the init<SID>.sap file is also passed via
the s option.
User response: Do not use the -s option with the

splitint call.
IDS1011E
IDS1005I
Start of splitint program at: time.

IDS1007I
End of splitint program at: time.
Explanation: splitint always requires the option -f

User response: Ensure that the splitint call has the
following form: <path>/splitint -p
IDS1014I
<subsystem message>

Control will be returned to either the shell or to
brbackup when splitint was called by brbackup based
on the entries split_options and split_resync entries in
the brbackup profile (e.g., init<SID>.sap)

information message from the IDS subsystem.
IDS1015I

Start of splitint program at <timestamp>
Explanation: Reports the activation of splitint.

IDS1008E

required.
1050
IDS1016E
<subsystem message>
IDS1028E

error message from its IDS control part.
User response: See the subsystem error messages for
more information and perform required action.
IDS1020I
The FlashBack Restore ended

successfully.
Explanation: The remote exec call to the production

system has ended with errors.
IDS1030I
Explanation: The high-performance restore issued

with the FlashCopy from the target volumes to the
source volumes was completed successfully.
splitint ended with errors on the

production system.
FlashCopy started ...
Explanation: The command with the split function has

been issued on the production system, and the program
splitint waits until this action has finished.

IDS1031I
IDS1023I

function failed.
IDS1024I

function failed.
IDS1025I
Time stamp: <current_time>
Explanation: DP for Snapshot Devices performs

several tasks in sequence (e.g. initiate the FlashCopy of
source volumes on the production system and mount
file systems on the backup system). Tracking the
various time stamps allows analyzing how long each
task took.
IDS1026I
Start of splitint on the production

system ...
FlashCopy successful.
Explanation: The command for the FlashCopy of the

volume pairs has terminated successfully on the
production system.
IDS1032W
Information from DP for mySAP was

not found.

Snapshot Devices and DP for mySAP was not found.
As of DP for mySAP version 3.3.10, the information is
exchanged through the call of the DP for Snapshot
Devicess function set_bki_info by backint prior to the
Tivoli Storage Manager backup. For older versions, the
information is first exchanged after the Tivoli Storage
Manager backup during the execution of the unmount
function. Either the DP for mySAP you have installed
does not support DP for Snapshot Devices, or DP for
mySAP has failed after a successful FlashCopy and
mount.
User response: Check the run logs of brbackup. This
error could have various reasons and should be
Case 1: brbackup has finished successfully.
as well as the one done to the Tivoli Storage Manager
server are valid. However, DP for Snapshot Devices
cannot show the backup ID in its report when using
the function inquire.
Explanation: DP for Snapshot Devices has issued a

call to the production system and is waiting for the end
of the execution.


Case 2: brbackup has terminated abnormally.
IDS1027I
splitint ended on the production system

successfully.
Explanation: DP for Snapshot Devices has ended the

call to the production system successfully.
Result: Check carefully the run log of brbackup for any

BKI, ANS or ANR error messages. Most likely, the
1051
the backup to the Tivoli Storage Manager server is

invalid.
Cause: Problems with the network or on the Tivoli
Storage Manager server caused DP for mySAP to fail
when running a backup.
reason for not getting a successful backup to the Tivoli
Storage Manager server.
IDS1038I
Explanation: DP for Snapshot Devices will write the

first record to the IDS control file specified in the entry
IDS_CONTROL_FILE of the profile.
IDS1039E
IDS1033I

<backupid>.

backups on disk (FlashCopy target volumes) as well as
to the Tivoli Storage Manager server are valid. The list
of files has been saved in the Tivoli Storage Manager
with the backup ID <backupid>.
Entry <field_name> in the current

backup cycle of the IDS control file is
missing.
Explanation: The field with the name <field_name> in

the current backup cycle was unexpectedly empty.
User response: After you run at least one brbackup

with a successful FlashCopy, the problem will be
resolved.
IDS1040E
The IDS control file exists and a new

backup cycle entry has been created.
Explanation: At the start of the function -f split, DP

for Snapshot Devices 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. FlashCopy target volumes/filesystems being
mounted or unmounted).
IDS1036E
The backup ID was not passed by DP

for mySAP. This FlashCopy backup
cannot be used for FlashBack Restore.
Explanation: Prior to this error, the warning

IDS1041W is displayed. The backup ID is mandatory
for using a FlashCopy backup for the restore.
User response: In order to use FlashBack Restore,
ensure that you have installed DP for mySAP (backint)
version 3.3.10.
The IDS control file must be read or

inserted before update.
Explanation: DP for Snapshot Devices has detected a

logical error when processing the IDS control file.
User response: Contact Data Protection for mySAP
support.
IDS1041W

IDS1035I
The IDS control file has no entry.
Explanation: DP for Snapshot Devices has found the

IDS control file, but it has no records. This error occurs
when you start one of the functions inquire, withdraw
or unmount before you have run the split function for
the first time.

IDS1034E
The IDS control file <ids_control_file>

does not exist. It will be created.
The value of the field field_name in

the file file_name is empty.

Snapshot Devices (splitint) prior to the Tivoli Storage
Manager backup, and also in case of a disk-only
backup, with the following options:
splitint -p <fcs-file> -f set_bki_info
-i <ids-file>
where
ids-file is an input file for splitint with the following
format:
>>>
BID
UTL
INF
EBT
EBC
EBB
EBR
<<<
backint_data
<backup id>
<name of the application profile used>
<name of the in-file>
<backup type: file or file_online>
<BRBACKUP or BRARCHIVE>
<FULL, INCREMENTAL, PARTIAL>
<NEW, OLD>
backint_data
>>> input_file
<file list>
<<< input_file
If one of the fields of the topic backint_data is empty
(missing), this message is displayed. If the backup ID is
empty, the process terminates with error IDS1036E.
1052
User response: In order to use FlashBack Restore,

ensure that you have installed DP for mySAP (backint)
version 3.3.10 or higher.
IDS1042W
Info data from DP for mySAP

/tmp/bki<SID>.ids cannot be read.
Explanation: Before the unmount process, DP for

Snapshot Devices will read /tmp/bki<SID>.ids, which
contains information about the backup that was done
by DP for mySAP. Among the information read is:
IDS1046I
Start of listing of importing volume

groups/mounting file systems ...
Explanation: After initiating the FlashCopy

source/target volumes on the production system, DP
for Snapshot Devices will make the corresponding
target volumes available to the backup host. A list of
mount points or volume groups will be shown.
v Backup id
IDS1047I
End of listing.
v Util file used for the backup
Explanation: Corresponds to start message IDS1046I.
v List of files used for the backup
v Backup type
This message will be issued if DP for mySAP
terminated unsuccessfully for some reason.
IDS1048I
User response: Ensure that DP for mySAP runs

successfully.
IDS1043I
The maximum number of backup cycles

in the IDS control file has been reached.
Explanation: The maximum number of backups

controlled via the parameter BACKUP_MAX will be
exceeded with the new inserted record. If the
parameter is not set, the program will use the default
value of 30.
IDS1044I
Explanation: When the withdraw function is started,

the unmount process will be performed only if the PSI
has a value of PSI_MOUNT_STARTED or
PSI_MOUNT_DONE.
Devices for mySAP Installation and Users Guide for Oracle
shows the permissible functions depending on the
IDS1050E
Delete backup cycle with BSEQ_N =

<bseq_n> and all associated files ...
Explanation: Since the maximum number of records

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
that backup cycle will be deleted.
The unmount process will be skipped

because the progress status indicator
(PSI) has a value of psi.
The version of the splitint program

must be the same on the backup and
production systems.
Explanation: The version of DP for Snapshot Devices

on the production system is different from the version
User response: Ensure that you install the same

version of DP for Snapshot Devices on the production
and backup systems. You get the version number when
you start splitint without parameters.
IDS1045W
IDS1051I
Directory path <directory> for the report

files does not exist. Using the current
directory.
Explanation: The directory entry of the parameter

LOG_TRACE_DIR in the profile could not be found.
The current directory will be used for the log and trace
files.
User response: In order to avoid directories cluttered
with reports and traces, the parameter
LOG_TRACE_DIR should be used, or the directory it
specifies must be created if necessary.

ID>

Devices program splitint uses the user ID to execute a
remote shell on the production system.
1053
IDS1052I

ID> again

IDS1053I

please try again

terminates.
IDS1054E
No password stored.

User response: You must start the splitint program
with the function -f password again. If no password is
stored, or it is invalid, splitint fails when the split
function is used.
IDS1055E

could not be opened. Please call splitint
with the password function to create
that file.

Try the following:
1. Call splitint with the password function to create
the file.
CONFIG_FILE).
correctly.
IDS1056E
The information of DP for mySAP could

not be set in the IDS repository.

the backup system was finished, the call of DP for
mySAP (backint) takes place. Backint then calls DP for
information. This information is mandatory for using a
FlashCopy backup for restore. This information could
not now be set.
User response: Ensure that you have the version of
backint compatible for FlashBack Restore.
1054
IDS1057E
No target set entries were found in the

IDS repository.
Explanation: The target set entries in the IDS

repository are generated automatically from the entries
configured in the .fct file (set of target volumes). This
happens during the FlashCopy backup.
User response: Check the .fct file (set of target
volumes). Check the parameters IDS_CONTROL_FILE
(IDS repository) and VOLUMES_FILE (.fct file).
IDS1060I
Start of listing of exported volume

groups/unmounting file systems ...
Explanation: A list of unmount points or exported

disk groups will be shown. Due to the use of the
unmount function on the backup host, DP for Snapshot
Devices will unmount the file systems and export
volume groups on the backup host that had been
imported or mounted when the DP for Snapshot
Devices split function was executed.
IDS1061I
Start the withdraw of the target-source

pairs ...
Explanation: The command with a withdraw has been

issued from the backup system to the primary Copy
Services server for the storage system.
IDS1062I

already PSI_UNMOUNT_DONE.
Explanation: DP for Snapshot Devices has been called

with the function withdraw or unmount, but the PSI
value of the latest backup cycle was already updated to
PSI_UNMOUNT_DONE in a previous splitint call.
IDS1063E
LOGON_HOST_BACK in profile wrong
or missing.

LOGON_HOST_PROD <hostname/TCP name> <user ID>
The host names must match the respective host names
of the production and backup systems. The TCP/IP
address will be used for the communication between
the two systems. The user ID specified must match the
Oracle DBA user ID (ora<sid>).

LOGON_HOST_BACK.
IDS1064E

is not known.

IDS1065E

the progress status indicator (PSI) has a
value of psi.

specified function.
Devices for mySAP Installation and Users Guide for Oracle
shows the permissible functions depending on the
IDS1066E
The option -f split can only be used on

the backup system.
Explanation: You cannot start the split function on the

production system.
function -f split on the backup system only. Ensure
that the profile contains a valid entry for
LOGON_HOST_BACK.
IDS1067E
The options -f split -s performsplit can

Explanation: The option -s was designed for internal

splitint use only and should not be used externally.
User response: Make sure you issue splitint -f split on
the backup system only. Ensure that the profile contains
valid entries for LOGON_HOST_PROD and
LOGON_HOST_BACK. Do not use the -s option with
the splitint call.
IDS1068E

Explanation: You cannot start the function withdraw

function -f withdraw on the backup system only.
LOGON_HOST_BACK.
IDS1069E

Explanation: You cannot start the function unmount

function -f unmount on the backup system only.
LOGON_HOST_BACK.
IDS1071E

Explanation: DP for Snapshot Devices was able to

read the file <filename> but the expected entry for the
topic <topicname> was not found.
>>> volumes_set_#
2, ..)
When the affected file is another file, you likely have
another error prior to this one. Otherwise, contact Data
Protection for mySAP support.
IDS1072E
The source volume <serial number>

cannot be specified as a target volume
in the .fct file.
Explanation: DP for Snapshot Devices found one of

the source volumes in the list of target volumes in the
init<SID>.fct file.
User response: Ensure that the target volumes list in
init<SID>.fct does not contain any of the source
volumes.
IDS1073E
No target volumes were specified for

the set <volumes_set_#> in file
<filename>.
Explanation: DP for Snapshot Devices has read file

<filename> contained in the parameter
VOLUMES_FILE. The format of the file is correct, but
the list of target volumes is missing.
User response: See the description of the FlashCopy
target volumes file under DP for Snapshot Devices
Target Volumes File in Data Protection for Snapshot
Devices for mySAP Installation and Users Guide for Oracle.
IDS1074E
The option -f flashback can only be

Explanation: The FlashBack Restore (option -f

flashback) can only be started from the production
machine.
1055
User response: To start the FlashBack Restore, log on

to the production machine.
IDS1075I
Creating a semaphore for the critical

part of importing/exporting ...
Explanation: When multiple production systems run a

backup via a single backup system at the same time,
DP for Snapshot Devices will ensure that the critical
parts of the code run for a single instance of the
program at a time. These phases are:
1. when the FlashCopy has been done and resources
(volume groups and file systems) are being enabled

IDS1080W
The semaphore could not be allocated.

<sys_message>.

2. before the FlashCopy relationship is withdrawn and

resources (volume groups and file systems) are
being disabled.

For this synchronization process, a semaphore with the

fixed key 0x88886666 will be created.
IDS1081W
User response: None

IDS1076I
Trying to set the semaphore for the

critical part of importing/exporting ...
Explanation: If the DP for Snapshot Devices

semaphore is already allocated, the program will wait
until it is released. Otherwise, the program will set it
and pass into the critical part of the run. Another
instance arriving at this point will now have to wait for
the release of the semaphore.

IDS1082E
User response: None

IDS1077I
Semaphore released.
Explanation: After the program has passed the critical

part of the run, the semaphore is released.
User response: None
IDS1078W
The semaphore could not be created.

<sys_message>.

create the semaphore, the system error number and
IDS1079W
The semaphore could not be initialized.

<sys_message>.

initialize the semaphore, the system error number and
1056
The semaphore could not be released.

System error <sys_error>:
<sys_message>.
Duplicate target volume serial number

was found in the target list.

duplicate serial number for a target volume in the file
specified in the VOLUMES_FILE parameter.
User response: Ensure that the serial numbers of the
target volumes in the file given by VOLUMES_FILE are
unique.
IDS1083I
Function query ended successfully.

ended the query function to check the correct setup.
IDS1084I
This is your last chance to stop the

FlashBack Restore. Enter c[ont] to
continue, s[top] to cancel.
Explanation: This message is the breakpoint in the

FlashBack Restore process. At this time, DP for
Snapshot Devices has already made all the required
checks for the FlashBack Restore. Although brrestore
has removed all the database files, you can still stop
here and choose a Tivoli Storage Manager restore. If
you choose to continue, the string #UNMOUNTING_FS
is displayed and the production system is then in a
state of unavailability, in which you are not allowed to
perform any operation on the production database (or
its file systems). This critical stage has passed when the
string #FS_MOUNTED is displayed.
the file systems fails after the successful FlashCopy

reverse of the volumes.
User response: Enter c to continue or s to stop.
User response: If DP for Snapshot Devices fails for

some reason during the FlashBack Restore between the
statements #UNMOUNTING_FS and #FS_MOUNTED,
then the user should restart the FlashBack Restore.
Enter c to continue or s to stop.
IDS1085E
You cannot restore from a FlashCopy

backup of the type NOCOPY.
Explanation: Only the FlashCopy backups made with

the parameter FLASHCOPY_TYPE set to COPY or
INCR can be used for the FlashBack Restore.
User response: Normally the calling program (backint)
considers only valid disk backups of FlashCopy type
COPY or INCR. Check for preceding errors.
IDS1086E
You cannot run the function flashback

if the backup status indicator (BSI) has
a value of bsi_value.
Explanation: The FlashBack Restore can only be called

for a FlashCopy backup with a backup status of
BSI_DISKONLY. All other values, such as BSI_START,
BSI_TAPEONLY or BSI_INVALID, are not allowed.
User response: The calling program (backint)
determines the backup ID of the disk backup that
contains a FlashCopy backup with one of the allowed
values of the backup status indicator. Check for
preceding errors.
IDS1088W

resources.
Explanation: Before the actual FlashBack Restore to

the database volume occurs, DP for Snapshot Devices
will do the following: .
1. unmount of the database file systems .
2. in case of LVM mirroring
v remove the mirror copies from the logical volumes
IDS1090E
The NLS catalog could not be loaded.

Make sure that the catalog exists.
Explanation: DP for Snapshot Devices uses an English

NLS catalog for the LVM and storage-system parts of
the product. The installation process will copy the
catalog to the displayed path.
User response: Check for errors during the installation
procedure.
IDS1091E

the restore status indicator (RSI) on
target set id has a value of RSI_START.

has a value of RSI_START, then a FlashBack Restore is
still running in the background. You cannot start a
FlashCopy backup again until the background copy to
the database volume is finished. In this case the RSI
value is either RSI_DISKONLY or in case of LVM
mirroring RSI_DISKANDLVM.
User response: Wait until the FlashCopy background
process is finished.
IDS1092E
FlashCopy failed.
Explanation: The procedure for establishing the

FlashCopy relationship between the source and target
volumes in the storage subsystem failed.
User response: None
User response: This is a significant error because the

source/target pair could be left in a different state.
Check for prior errors, and check the connection to the
CIM agent and to the storage subsystem. In case of the
FlashCopy backup, you need to start the withdraw
function of splitint to clean up the relationships. In the
case of a FlashBack Restore, restart the restore. The
software will detect the state and ask you for the
withdraw.
IDS1089I
IDS1093E
v remove the mirror physical volumes from the

volume groups
3. remove the volume group from the AIX ODM .
One or more of these operations have ended with
errors. DP for Snapshot Devices will issue a warning
but the FlashBack Restore will continue.
The FlashBack Restore was previously

started using the target set id. Please
enter c[ont] to restart again or s[top]
to cancel.
Explanation: Having a valid disk backup on the target

volumes, the user is always able to start the FlashBack
Restore again, even though the background copy of a
prior FlashBack Restore is still running. This can also
be necessary if, for example due to an unexpected
situation on the production system, the mounting of
The target set id was not found.

which hardware unit should be taken as the source,
will be specified here under the corresponding target
set as well. Internally DP for Snapshot Devices keeps
the status of each target set (progress status, backup
status, restore status, backup sequence number, etc.) in
the housekeeping directory. After the FlashCopy, DP for
1057
Snapshot Devices will reread the target set information.

This message will only be displayed if this information
was destroyed, is corrupt or something unexpected
occurs.
User response: Check if the FlashCopy backup ended

successfully.
IDS1104E

IDS1097E
The option -f set_bki_info can only be


Snapshot Devices with the function -f set_bki_info for a
FlashCopy backup on the backup machine after the
mount of the file systems. This call is not allowed on
the production machine.
User response: Consult the documentation to
understand the flow of the FlashCopy backup in an
SAP environment.
IDS1100E
The parameter
HARDWARE_ID_LVM_MIRROR has
to be moved from the profile
filename.fcs to the corresponding
target set in filename.fct.
Explanation: In case of AIX LVM mirroring the

parameter HARDWARE_ID_LVM_MIRROR indicates
the identifier of the hardware unit to be selected for the
mirror copy that should be used for the FlashCopy.
This parameter is now contained in the target set
topic(s) in the .fct file.
User response: Move the parameter from the .fcs to
the .fct file.
IDS1102E
The target set id target_set_id could

not be read or inserted.

cycle. Specify the option -n target_set_ID.

To see the correlation of backup ID to target set ID call
IDS1122I
FlashCopying the sources to the target

volumes ...
Explanation: After finding the pairs of volumes to be

copied, DP for Snapshot Devices signals to the calling
program (brbackup) to set the database into backup
mode, or, in case of a backup type of offline_mirror, to
shut down the database. Then the actual FlashCopy can
be requested to the Copy Services server.
User response: None
IDS1123I
Enabling the volumes and filesystems ...
Explanation: After the FlashCopy, the target volumes

attached to the backup machine are imported in the
operating system and the file systems are mounted

which hardware unit should be selected for the
FlashCopy, will be specified under the corresponding
target set as well. Internally DP for Snapshot Devices
keeps the status of each target set (progress status,
backup status, restore status, backup sequence number,
etc) in the housekeeping directory. The file containing
the information of the target set could not be read or
written.
User response: None
2. Each logical volume must have at least two copies

(see EEO0166E).
IDS1103W
3. Each logical volume must have the parallel

scheduling policy (see EEO0168E).
The restore status indicator (RSI) has a

value of RSI_INVALID on target set id.

has a value of RSI_INVALID, this means that a
FlashBack Restore was initiated but did not terminate.
Nevertheless, DP for Snapshot Devices will issue this
warning and continue with the FlashCopy backup.
1058
IDS1125I
Checking AIX LVM mirroring ...

environment, DP for Snapshot Devices ensures that the
LVM mirror setup complies with the requirements
listed below prior to and after the actual FlashCopy:
1. The quorum of each involved volume group must
be off. This means that if a mirror set is inactive
due to a failure, the database can continue working
properly (see EEO0164E).
4. The mirror set that resides in the hardware unit that

was chosen for the FlashCopy must be free of stale
partitions (see EEO0176E).
5. All the partitions of each logical volume copy must
reside on the physical volumes of the same
hardware unit (see EEO0174E).
6. Each logical volume must have the mirror write

consistency property on (see EEO0172E). This
ensures that the mirror set used for the FlashCopy
is consistent from the point of view of the file
system level.
User response: None
IDS1128I
The parameter CLEAR_TARGET_PVID

in the profile filename.fcs is obsolete
and will be ignored.
Explanation: This parameter is no longer needed

because the clearing of the physical volume IDs now
depends directly on the value of the parameter
FLASHCOPY_TYPE and whether the backup is a
disk-only backup.
1. The complete set of physical volumes making up a

so-called volume group must be moved.
2. Also, all the volume groups in which the database
resides must also be completely moved. The
operating system allows access to the data on each
physical volume only if all the volumes are
represented as a consistent group to the system.
Also, you can only start up a database if all the
volume groups containing the database files are
available.
User response: Restore the data using Tivoli Storage
Manager from tape.
IDS1133E
User response: Delete the parameter

CLEAR_TARGET_PVID from the .fcs file.
IDS1129E
You cannot run an incremental

FlashCopy until all the changed tracks
are copied.
Explanation: If you set the parameter

FLASHCOPY_TYPE of the .fcs file to the value INCR,
then an incremental FlashCopy is issued. This means
that only the data that has changed since the last
time-zero (first incremental) or subsequent incremental
FlashCopy is copied. This helps reduce background
copy completion time when only a subset of the data
has changed.
User response: If you want to start a new time-zero
FlashCopy backup in any case, you must issue the
function withdraw.
IDS1130E
The list of files passed by DP for

mySAP in the file temp_file is empty.
Explanation: After brbackup has called DP for

Snapshot Devices to make the FlashCopy, DP for
mySAP will be called and it will call DP for Snapshot
Devices with the function set_bki_info to pass, among
other things, the backup ID and the list of files used by
backint. This list of files was now found to be empty.
Some of the production logical volumes

are mirrored. You have to set the
hardware unit ID in the parameter
the corresponding target set in the .fct
file <filename>.
Explanation: DP for Snapshot Devices found that

some of the logical volumes on which the production
database resides are mirrored using the mirror
capability of the Logical Volume Manager. However,
the parameter HARDWARE_ID_LVM_MIRROR was
not specified in the .fct file. This parameter causes DP
for Snapshot Devices to make all the necessary checks
to get a consistent copy via the FlashCopy on the target
volumes in an LVM mirror environment.
User response: Set the parameter
HARDWARE_ID_LVM_MIRROR with the hardware
unit ID that is used for the FlashCopy.
IDS1134I
Disabling the volumes and file systems

...
Explanation: Prior to the FlashBack Restore from the

backup to the production volumes, the production
volumes and file systems will be disabled. The
following actions will be started:
v unmount
v remove devices
v remove logical volumes
v vary off the volume group
User response: Check that you are using a compatible

version of backint for FlashBack Restore. The version of
backint must be v3.3.10 or higher.
IDS1131E
IDS1135I
DP for Snapshot Devices cannot be used

for partial restores. The following
database files are in the restore list but
were not on the backup list.
Explanation: Unlike other backup techniques, DP for

Snapshot Devices moves the complete data on a
physical volume instead of individual files. Two
requirements are necessary to build a backup of a
database:
v export volume groups.
FlashCopying the target to the source

volumes ...
Explanation: This message is displayed during the

FlashCopy restore process to the production volumes.
1059
IDS1136I
The parameter parameter_name was not

specified in the profile.
Explanation: The specified parameter was not found

in the .fcs profile. However, this does not impact the
program, and processing will continue with the default
value. If the parameter is FLASHCOPY_TYPE, the
default value will be used as the intended
FLASHCOPY_TYPE (see Intended and Effective
Devices for mySAP Installation and Users Guide for
Oracle).
User response: Add the specified parameter to the
profile if necessary.
IDS1137I
The option -C copy_type will determine

the copy type. The parameter
FLASHCOPY_TYPE was not specified in
the profile.
Explanation: The argument of the command line

option -C specifies the FlashCopy type that should be
used. It overrides the default value of the parameter
FLASHCOPY_TYPE.
IDS1138E
The parameter
the target set target_set_id is set in the
.fct-file file_name, but the production
logical volumes are not mirrored.
Explanation: The HARDWARE_ID_LVM_MIRROR

parameter should only used in an LVM mirror
environment.
User response: If you want to use this feature you
need to mirror the production logical volumes on
source volumes residing on different hardware units.
Otherwise, remove the parameter
HARDWARE_ID_LVM_MIRROR parameter from the
.fct file.
IDS1139E
Cannot resolve the link for the directory

symbolic link name.
Explanation: If the directory specified by the

environment variable ORACLE_HOME is a symbolic
link, DP for Snapshot Devices tries to resolve it. This
procedure was unsuccessful.
User response: Check the symbolic link of the cited
directory in the operating system.
IDS1140I
Resolving link symbolic link name ->

physical file name.
Explanation: If the directory specified by the

environment variable ORACLE_HOME is a symbolic
link, DP for Snapshot Devices will resolve it.
1060

IDS1141E
The option -n <target_set_ID> must be

specified.
Explanation: The option -n is used to specify the

FlashCopy target set that should be used by DP for
Snapshot Devices. It is required for the function -f
modify_copyrate.
User response: Specify the target set involved using
the option -n <target_set_ID>.
IDS1142I

already PSI_WITHDRAW_DONE.
Explanation: A rerun of the withdraw function will

detect that the progress status of the specified (option
-n) or last FlashCopy backup is already
PSI_WITHDRAW_DONE.
User response: If for some reason the status
PSI_WITHDRAW_DONE is not in sync with the status
of the source/target relationships, the withdraw_force
function can be used.
IDS1143E
The function withdraw_force requires

src/tgt pairs to be specified in the .fct
file file_name. The matching list of
src/tgt volumes could not be set.
Explanation: In contrast to the normal withdraw

function, where the source/target volumes are taken
from the local repository, the withdraw_force function
needs to get this information from the .fct file. The
reason for that is that the withdraw function removes
the matching list from the local repository, because a
restore after a withdraw is not allowed.
User response: Check the .fct file.
IDS1146I
Forcing parameter ORA_SUSPEND_DB

to YES, as LVM_FREEZE_THAW has the
value of YES as well.
Explanation: The file systems will be frozen prior to

the snapshot, TSM for ACS will automatically suspend
the database beforehand.
User response: Check that this is the correct option for
your environment. Otherwise, set the parameters
LVM_FREEZE_THAW and ORA_SUSPEND_DB
accordingly.
IDS1147I
Reconciling the local snapshot directory

with the storage system....
Explanation: In the case on N series, Tivoli Storage

Manager for ACS checks that, for each snapshot kept in
its Local Snapshot Manager, a valid snapshot exists on
the N series storage system.
User response: None
IDS1148I
Deleting the snapshot 'snap id' of the

volumes in the data container 'dc id'.
Explanation: The specified snapshot will be deleted.

User response: None
IDS1175E
The backup ID or the backup sequence

number identifier was not found.
Explanation: DP for Snapshot Devices did not find

any entry in the IDSSAVE for the specified backup ID
or backup sequence number.
IDS1176I
The target set target_number does not

contain a valid FlashCopy backup.
(backup ID identifier).
Explanation: This message can be displayed when DP

for mySAP calls DP for Snapshot Devices to inquire for
disk backups on the target sets. The target sets are
enumerated starting with 1.
IDS1179E

target set number is not valid.

one of the following values for one specific target set:
v BSI_INVALID; invalid entry for disk backup
Any other value is not allowed and makes this backup
cycle unusable.
(BSI) of your target volumes by calling the splitint
inquire): splitint -p initSID.fcs -f ts_inquire -n target
set number Check for preceding errors.
IDS1180E

number is a valid disk backup.
Explanation: DP for Snapshot Devices has found that

the selected backup to be restored has a valid disk
backup with an entry in the IDSSAVE.
User response: None
IDS1177E

number was not a valid disk backup.
Explanation: To do a FlashBack Restore, a valid disk

backup must exist on one of the target sets. The backup
status indicator (BSI) must have the value
BSI_DISKONLY.
(BSI) of your target volumes by calling the splitint
executable: splitint -p initSID.fcs -f ts_inquire
-n target set number
IDS1178E

the FlashCopy run backup sequence
number is not valid.

one of the following values in the IDSSAVE:
cycle unusable.
(BSI) of your IDSSAVE calling the splitint executable
with the option -f inquire : splitint -p initSID.fcs -f
inquire -b backup sequence number Check for
preceding errors.
IDS1181E
The FlashCopy run

backup_sequence_number is not the
last backup of target set number.
Explanation: This error message is issued if the

FlashCopy backup run is no longer a valid disk
backup. Normally, the calling user interface (backint or
tdphdwora) ensures that the backups offered for
selection are valid FlashCopy backups.
User response: Check for preceding errors. Call
tdphdwora and the inquire function of splitint to
check this backup.
IDS1182E
No target set ID could be assigned to

the backup run backup_sequence_number.

Advanced Copy Services tries to find a target set (data
container) that matches the source data container to
satisfy the FlashCopy backup. It can be a target set in
the state AVAILABLE or the state IN_USE (in which
case it will be re-used). A matching target data
container could not be found, however.
are being used for the FlashCopy type COPY. Also
make sure that the target volumes are available to the
1061
v TARGET_VOLUME
IDS1183I
A disk-only backup (option -d) was

invoked, forcing the parameter
FLASHCOPY_TYPE of the .fcs-file to
COPY.
IDS1190E
The information of the source/target

volumes could not be found.
Explanation: The executable splitint will be started

automatically as a daemon (sometimes referred as
fcagent) to monitor the background copy. An attempt to
obtain the status of the copy process has failed.
Explanation: If the user specified a disk-only backup

via the parameter -d and the parameter
FLASHCOPY_TYPE of the .fcs file has the value of
NOCOPY, DP for Snapshot Devices sets the value to
COPY.
User response: Check the error log

file splitint_[p|b]_runagent_jjjjmmddHHMMSS.log in
the directory specified in the parameter
LOG_TRACE_DIR of the .fcs file. Check the availability
of the storage system using the applicable tool
(STORWATCH Specialist, DS Storage Manager, or SVC
console).
Check the parameters in the .fcs file:

IDS1184I
Checking the backup status on Tivoli

Storage Manager and on disk ...
Explanation: This message is displayed by the

program tdphdwora during the inquiry of the backups
on Tivoli Storage Manager and on disk.
v COPYSERVICES_SERVERPORT
Also verify the availability of the CIM agent and its
connection to the storage system as described in the
storage-system documentation.

IDS1191I
IDS1185I
Reading the SAP backup log

<PATH>/back<SID>.log ...
Explanation: This message is displayed by the

program tdphdwora while reading the backup of the
SAP system ID <SID>.
IDS1186E
The parameter param in the profile

<.sap file name> or the environment
variable env_var is required.
Explanation: This error is issued by the program

tdphdwora if the specified parameter of the .sap file
passed by the option -p could not be read.
User response: Check that the passed .sap file is a
valid setup file for the SAP environment.
IDS1189E
The option -C copy_type will override

the value value of the parameter
FLASHCOPY_TYPE in the profile.
Explanation: The value of the copy type parameter in

the option -C copy_type, if specified in the split_options
statement in the mySAP profile (.sap), will override the
value found in the DP for Snapshot Devices profile
(.fcs)
1062
The target volumes set number does

not contain a valid disk backup.

backint or tdphdwora) if one of the target sets contains
an invalid disk backup.
IDS1192I
No disk backups were found on the

target volumes.

backint or tdphdwora) if none of the target sets
contains a valid backup.
User response: You will have to select a backup from
Tivoli Storage Manager.
IDS1193I
The FlashCopy run with backup ID id

was of type NOCOPY.

backint or tdphdwora) if one of the target sets contains
a FlashCopy backup of type NOCOPY.
IDS1194I
The FlashCopy run

backup_sequence_number has a
backup status indicator (BSI) of status
and is therefore not valid for FlashBack.

backint or tdphdwora). The values of the backup status
(BSI) BSI_DISKONLY are valid values for a FlashBack
Restore. The values BSI_START and BSI_TAPEONLY
could be valid values at a later point in time. Any other
value is invalid.
IDS1196E

exist for the specified backup ID
identifier.
Explanation: A FlashCopy disk backup can only be

restored in coordination with DP for mySAP. At restore
time, DP for Snapshot Devices has to know about the
corresponding list that was passed at backup time.
User response: Ensure that ora<sid> and the root user

have the right setting for memory allocation. The
a. Select <user>.
default value).
User response: Check that you have the version of DP

for mySAP supporting FlashBack Restore. Otherwise,
you will have to restore from Tivoli Storage Manager.
You must make sure that the system-wide default Hard

values are not explicitly defined to be lower than the
number indicated above. Check the file
IDS1197I
IDS1211E

exist for the FlashCopy run
backup_cycle_number.

backint or tdphdwora) if the list of files was not found
for one of the target sets.
IDS1198E
Explanation: Use of the -f modify_copyrate function

requires that the new rate be specified using the -R
option.
User response: Include the -R option in the command
line.
IDS1212W

The last FlashCopy run was already
assigned the backup ID identifier.

the backup system finishes, the call of DP for mySAP
(backint) takes place. Backint then calls DP for
information. This message is displayed if this last call
occurs more than once for the same FlashCopy run.
Option -R <copy_rate> not specified.
One or more errors were found checking

the FlashCopy relations.
Explanation: This message can appear during the

FlashBack Restore if the check of the source/target
relations ended with any error that originated in the
storage subsystem. This check takes place before any
resource is removed.
User response: Check the relations. See preceding
message output.
IDS1300E
User response: Check the backup log of the program

brbackup.

be e.g.:
IDS1200E
v <ORACLE_HOME>/dbs/init<SID>.fcs

thrown.

v the argument value of the option -i (file containing

the list of files to back up)
v <config_file>
1063
v the field value of EXCHANGE_FILE in a backup

cycle record.
IDS1301E

be e.g.:
v <config_file>
record.
IDS1305E

error:
v the access rights for splitint are not set to 4750. Since
the s-bit is not set, DP for Snapshot Devices cannot
switch between the users ora<sid> and root
during the execution of the program.
v the file system in which splitint is installed was
User response:
v Check the splitint file in the directory
/usr/tivoli/tsm/acssap/oracle/x.y.z, and set the
access rights for splitint with chmod 4750 splitint.
After the installation, the command
ls -l splitint.... outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 splitint

it.)
v If the file system in which splitint is installed was
mounted with the NOSUID option, mount the file
system with SUID allowed.
IDS1306I
IDS1302E
The environment variable <env_var>

must be set.

ORACLE_HOME: to the home directory of the user ID
ORACLE_SID: to the mySAP for Oracle DB system ID
and try again.

Issuing command command_string ...
Explanation: DP for Snapshot Devices is running the

specified system command with the parameter as
shown.
IDS1308W

the backup system.

directory path.

start of the split function if any of the files passed in
the file list still exist on the backup system. If so, this
warning will be issued. Normally, none of the files
should exist because the withdraw function, which

User response: Always run the withdraw function

IDS1304E
IDS1310W
IDS1303E
The environment variable <env_var> is

not correct.

<filename>.

files could be: <ORACLE_HOME>/dbs/init<SID>.fcs
or the argument value of the option -i (the file that
contains the list of files to back up).
1064

containing the directory path is only
amount MB.

checked:
1. the database home directory
2. the directory specified by the parameter
3. the directory containing the idssave file specified by
If the free space of these file systems falls below 50 MB,

DP for Snapshot Devices warns the user. If it is under 5
MB, an error will be issued and the program fails,
throwing an exception.
IDS1311E

directory path.

systems (see the explanation for IDS1310W) is under 5
MB this error message will be issued and the program
fails throwing an exception.
IDS1318E
Operating system error <error_no>:

<message text>.
Explanation: DP for Snapshot Devices encountered an

and message text will be displayed. The message will
appear, for example, as a result of
v an incorrect user ID given with the parameter
LOGON_HOST_PROD in the .fcs file
v an incorrect password for the user ID given with the
parameter LOGON_HOST_PROD in the .fcs file
v an incorrect TCP/IP name given with the parameter
LOGON_HOST_PROD in the .fcs file (for example:
connection timeout)
v a failure allocating memory using the function
malloc, and the operating system cannot satisfy the
request
offline_mirror, to start the database again.

IDS1322I
Explanation: DP for Snapshot Devices saves control

information for the FlashCopy process in an internal
repository that consists of several files. Some of these
files may need to be written concurrently by several
processes. To ensure consistency, DP for Snapshot
Devices uses a lock mechanism.
IDS1325I
Setting the tablespaces in backup mode

or, in case of offline_mirror, the
database will be shutdown.
Explanation: DP for Snapshot Devices displays this

message prior to initiating the FlashCopy and prior to
signaling to SAP to set the database in the backup
mode or, in case the backup type is offline_mirror, to
shut down the database.
IDS1321I
User response: Check the specific message and decide

whether to retry or stop the process. In the case of
critical restore runs, it is recommended to retry the
operation after the reason for the failure has been
identified and remedied.
IDS1326E
Explanation: DP for Snapshot Devices displays this

message after the FlashCopy was performed and prior
to signaling to SAP to set the database in the
end-backup mode or, in case the backup type is
Password input file <input file> not

found.

file> option was not found.
for the input file for the password function.
IDS1327I
Topic named <topic name> could not

be found in the file <input file>. The
password of user <username> will not
be changed.

file> option does not have the topic <topic name>
specified. The user <username> will not be changed.
There are two topic names (DBUSER, CSUSER). If none
of these topics are found in the <input file>, then no
password will be changed.
IDS1328W
The tablespaces will end the backup

mode or, in case of offline_mirror, the
database will be started.
Please check the messages above. Enter

r[etry] to retry or any other key to stop
the process.
Explanation: This message is asking you to retry an

operation that previously failed.

IDS1320I
The file filename is locked, waiting

one second and retry!
Parameter named <parameter name>

could not be found in the file <input
file>. The password of user
<username> will not be changed.

file> option does not have a valid format. The
parameter <parameter name> was not found. The
password of the user <username> will not be changed.
User response: Please check for the valid format of
1065
the <input file>. Parameter <parameter name> is

required in the topics DBUSER and CSUSER.
IDS1329I
The password of user <username> will

be changed.
IDS1402E
A background copy process of type

CopyType is still running on target set
targetSetID.
Explanation: DP for Snapshot Devices fails if a

background copy is still running for the same logical
FlashCopy group (see Logical FlashCopy Group in
Installation and Users Guide for Oracle). However, any
target set (state AVAILABLE) that does not yet belong
to a logical FlashCopy group (state AVAILABLE) can be
selected.
IDS1330E
User response: Check the backup status of the

FlashCopy backups that may be running.

file> option has a valid format and the password of the
user <username> of either the DBUSER or the CSUSER
topic will be changed.
The file <diskmapper filename> could

not be found. Please check that the
parameter DISKMAPPER_SCRIPT is
specified as a full qualified
path/filename.
Explanation: The script <diskmapper filename>

specified by the parameter DISKMAPPER_SCRIPT in
the DP for Snapshot Devices profile is not valid.
for the DISKMAPPER_SCRIPT parameter.
IDS1331E
The file <filename> could not be

found. Please check that this file exists
or that the symbolic link points to an
existing file.
IDS1404I
The target set with ID targetSetID is

selected for this run.
Explanation: DP for Snapshot Devices use two

procedures for the selection of a target set. See
Algorithm Used for Automated Target Set Selection
Using the Intended FlashCopy Type and Algorithm
Used for Specific Target Set Selection in Data Protection
for Snapshot Devices for mySAP Installation and Users
Guide for Oracle.
IDS1405E
Explanation: The file <filename> is not valid.
No target set found to accept a backup

of type copy_type.
User response: Please check that the file <filename>

exists or that the symbolic link points to an existing
file.
Explanation: If all the target sets are being used with

the same type of logical FlashCopy group (either INCR
or COPY), you will not find a target set to make a
FlashCopy with a different copy type.
IDS1400E
User response: To make a target set AVAILABLE, start

the withdraw function on the specific target set using
the option -n.
The backup status on target set

targetSetID must be BSI_DISKONLY or
BSI_DISKANDTAPE for re-use with
incremental copy type.
Explanation: A FlashCopy backup of type INCR in a

non-AIX LVM mirror environment will re-use the
already existing target set with FlashCopy type INCR
only if the background process is already finished.
User response: Check the background process by
starting the program splitint with the function inquire
or ts_inquire.
IDS1408E
The copy type argument copy_type is not

valid.
Explanation: The argument (FLASHCOPY_TYPE) of

the command line option -C <FLASHCOPY_TYPE> can
have the following values: COPY, NOCOPY and INCR.
Any other value is not valid. Furthermore, INCR is not
valid for an SVC configuration.
IDS1401E
The target set targetSetID does not match

the source volumes.
Explanation: DP for Snapshot Devices checks whether

the target set for the FlashCopy backup contains a
target volume for each source volume, residing in the
same hardware unit and with the same size.
User response: Check the volume list of this target set
and ensure that the volumes are in the same hardware
unit and have the same size as the source.
1066
IDS1410E
You cannot run a FlashBack Restore

from target set targetSetID if the sources
are involved in a relationship of type
copytype with the target set targetSetID
Explanation: DP for Snapshot Devices exploits the

feature Multiple Relationship FlashCopy of the
storage system. This means that for DP for Snapshot
Devices the source set of volumes can participate in
multiple FlashCopy relationships with several target
sets of volumes. A restore to a source set requires that
this set not have any outstanding relationships with

other sets.
User response: To start a FlashBack Restore
(FlashCopy in reverse, from the target to the source
volumes) you have to withdraw the relationship with
the specified target set.
IDS1411E
The intended FlashCopy type has a

value of copy_type.
Explanation: See Intended and Effective

Devices for mySAP Installation and Users Guide for Oracle.
An invalid value copy_type has been

specified for the FlashCopy type in the
profile .fcs file.
Explanation: The parameter FLASHCOPY_TYPE of

the DP for Snapshot Devices profile (.fcs file) can have
the following values: COPY, NOCOPY and INCR. Any
other value is not valid. INCR is invalid for an SVC
configuration.
Mount point mount_point does not

exist anymore on the production system.
Explanation: The program tdphdwora checks, prior to

a FlashBack Restore, whether the original production
file systems still exist. Depending on the result of this
check, brrestore or backint will be used for the restore.
The BR*Tools component brrestore requires the
existence of the file systems, while backint does not.
The FlashBack Restore will automatically create the file
systems.
IDS1418E
Explanation: The program tdphdwora of DP for

Snapshot Devices shows information about the backups
of the SAP log. Each backup run in SAP can have a
TSM backup, a FlashCopy backup or both. A FlashBack
Restore can only be started if a FlashCopy backup
exists for the corresponding backup log.
IDS1422I
There is only a TSM backup available

for the backup log logname.

IDS1423I
The target set targetSetID is already

using incremental FlashCopy.
There is only a FlashCopy backup

available for the backup log logname.

IDS1424E
Explanation: Using the procedure of specific target set

selection, it is not allowed to select more the one target
set for incremental FlashCopy on the same storage
device.
There are no backups available for the

backup log logname.

User response: Select another backup log for restore.
User response: Re-use the same target set or

withdraw the existing relationship.
IDS1425I
IDS1419E
There are both a TSM and a FlashCopy

backup available for the backup log
logname.

IDS1415W
IDS1421I

IDS1413E
User response: Select a backup log with a valid

FlashCopy backup.
There is no FlashCopy backup available

for the backup log logname.

You selected to restore the backup log

logname.
Explanation: The user has selected the menu item to

restore the specified backup, including pre- and
post-processing.
1067
IDS1426E
You cannot start a restore from the

backup machine.
Explanation: A FlashBack Restore (FlashCopy in

reverse, from the target to the source) can be started
from tdphdwora only if it is running on the production
machine.
User response: Start tdphdwora on the production
machine.
IDS1427I
An invalid input was typed: text .
Explanation: The user was asked by tdphdwora to

provide input, which was not valid.
User response: Depending on the input requested, try
again.
IDS1429I
BR*Tool brrestore cannot be used for

the restore, backint will be taken
directly instead.
Explanation: Starting a FlashBack Restore from

tdphdwora will include three main steps: pre-restore,
the actual restore and the post-restore. The BR*Tool
brrestore can only be used if all the file systems are still
available on the production machine. The program
backint of DP for mySAP will be started directly.
IDS1430I
Restore from tdphdwora ended with

return code rc.
Explanation: The database administrator can use the

program tdphdwora of DP for Snapshot Devices to
start a FlashBack Restore (see Checking the Source and
Target Relationships Using tdphdwora in Data
Users Guide for Oracle). This message will be displayed
at the end of the restore, indicating the return code of
the restore operation.
User response: Depending on the return code, an
action can be necessary.
IDS1431I
Do you want to run PreRestore.sh -b

logname -E tdphdwora?
(yes/edit/quit) [y] =>
Explanation: When starting a FlashBack Restore via

the tdphdwora program, the database administrator
will have to decide at several checkpoints how to
proceed. This message appears before all the actions,
prior to starting the FlashBack Restore (see Flow of
tdphdwora Supporting a Restore Request in Data
Users Guide for Oracle).
User response: Specify y or yes to start the
command shown, specify e or edit to change the
command that will be started, and specify q or quit
1068
to return to the selection menu.

IDS1432I
Do you want to run command_line?

Explanation: When starting a FlashBack Restore via

the tdphdwora program, the database administrator
will have to decide at several checkpoints how to
proceed. This message appears before all the actions,
prior to starting the FlashBack Restore (see Flow of
tdphdwora Supporting a Restore Request in Data
command that will be started, and specify q or quit
IDS1433I
Do you want to run PostRestore.sh -b

logname -E tdphdwora?
Explanation: Starting a FlashBack restore via the

program tdphdwora, the database administrator will
have to decide in several checkpoints how to proceed.
This message appears before all the necessary actions
after the actual Flashback Restore is started (see Flow
of tdphdwora Supporting a Restore Request in Data
command that will be started and specify q or quit
IDS1434I
Production volumes and files systems

will be checked.
Explanation: Prior to initiating a FlashBack Restore,

the program tdphdwora checks whether all the
necessary conditions are met (see Flow of tdphdwora
Supporting a Restore Request in Data Protection for
Snapshot Devices for mySAP Installation and Users Guide
for Oracle):
v Checks that all source volumes used in the
FlashCopy backup are still available
v Checks that the restore request was done on the
production system
v Provides information for the file systems it backed
up and that currently exist
v Provides information about any FlashBack Restore
rerun condition encountered
IDS1435I
Enter c[ont] to continue or any other

key to cancel.
IDS1439W
No matching list found in this

FlashCopy run.
Explanation: This message will be displayed in

different points of the restore flow prior to and after
key checks.

User response: Respond according to the specific

context. Press c or cont to proceed or any other key
to return to the main menu.

IDS1440E
IDS1436E
The value of the parameter

COPYSERVICES_HARDWARE_TYPE in
the file profile_name is invalid. Valid
values are: DS8000, DS6000, SVC,
ESS800 and SAN_NSERIES.
Explanation: The parameter can only accept the

specified values.
User response: Change to the value according with
the storage system.
IDS1437E
The next FlashCopy Backup after an

incremental FlashBack Restore must
involve the same source/target LUNs as
the FlashBack Restore.
Explanation: Possible reasons for this error are as

follows:
v Ensure that you are using the same backup type
online_mirror or offline_mirror for this FlashCopy
Backup as the one that you used with the FlashBack
Restore.
v Any structural changes on source/target volumes
like adding new source volumes or deleting source
volumes will cause this error.
User response:
v If applicable, start a new FlashCopy Backup with the
same backup type as the one that you used with the
FlashBack Restore. Otherwise, perform the following
step.
v Start a withdraw (-f withdraw) of this incremental
FlashCopy target volumes set. This implies that the
subsequent FlashCopy Backup will be a full copy.
IDS1438W
No source LUNs found for the prior

FlashCopy run in the file
ids_repository_file.

An incremental FlashBack Restore was

already started using the target set
target_set_id. You can re-start again only
after the background copy process is
finished. See the progress of the
FlashBack using the menu point **show
details**.
Explanation: This is a limitation imposed by the

storage system.
IDS1441I
Checking the FlashCopy relations,

please wait ...
Explanation: TSM for ACS is reading the

source/target FlashCopy relations from the storage
system.
IDS1443E
Data container id dcID cannot be used

to force a cleanup (function
'withdraw_force') when the snapshot
was already removed.
Explanation: This messages applies only to the

component Data Protection for N Series Snapshot for
mySAP. The function 'withdraw_force' of TSM for
ACS requires, in the case of N Series, that the snapshot
which is the base of the cloned, mounted volumes on
the backup system is still available.
IDS1452E

Snapshot Devices for mySAP has
expired.

your IBM/Tivoli marketing representative.
IDS1453W

Snapshot Devices for mySAP will expire
in number days.

1069

your IBM/Tivoli marketing representative before the
version expires.
times for the start and end of the background process,

and rate is the transfer rate within the storage system.
To calculate the transfer rate some conversion is
needed. When doing this conversion, an error occurred.
The rate value will be invalid.
IDS1454I
User response: Check the date and time setting of the

machine.

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
IDS1540I

backup system

of a FlashCopy backup of type COPY or INCR on the
backup system.
User response: None
IDS1541I
Explanation: Unable to access license file.

backup system


system.
IDS1457E
User response: None

data/checksum.

User response: Make sure you have the right
agentess.lic file installed.
IDS1520E
The FlashCopy agent can only be started

if the last FlashCopy run was of type
COPY or INCR.

automatically start a daemon called the FlashCopy
agent to monitor the background copy, provided the
parameter FLASHCOPY_TYPE of the .fcs file was set to
COPY or INCR.
User response: Normally, the calling program will
control this process. Check for preceding errors.
IDS1531E
Timestamp string cannot be converted.
Explanation: The status of the background copy will

be written by the FlashCopy agent daemon to a file
named fc_exchange.bseq_number in the directory
containing the IDSAVE specified by the parameter
IDS_CONTROL_FILE. The file
fc_exchange.bseq_number has, for each volume pair,
the entry volume_pair: target source size state
YYYY-MM-DD-HH.MM.SS YYYY-MM-DD-HH.MM.SS
rate, where target is the serial number of the target
volume, source is the serial number of the source
volume, state can be active if the background copy is
running or none if the background copy is finished.
YYYY-MM-DD-HH.MM.SS represents approximate
1070
IDS1545I

production system

of a FlashBack Restore on the production system.
User response: None
IDS1546I

production system

the background copy has finished the restore on the
production system.
User response: None
IDS1550E

added to /etc/inittab.

periodically. However, DP for Snapshot Devices was
unable to add an entry to /etc/inittab.

Snapshot Devices executable (splitint).
IDS1551W
The FlashCopy agent already exists in

/etc/inittab.

periodically. In an attempt to add such an entry, DP for
Snapshot Devices detected that an entry already
existed.
IDS1946I
BRBACKUP is called with option -q

split. Processing ends here.
Explanation: The SAP brbackup command was

specified with the 'q split' option. The FlashCopy
Backup run will be terminated before starting the tape
backup.
User response: None
User response: None

IDS1552E


removed. However, DP for Snapshot Devices was
unable to remove the entry.
Snapshot Devices executable (splitint).
IDS1553W
The FlashCopy agent has already been


removed. However, DP for Snapshot Devices detected
that the entry no longer exists in the table.
IDS1945E
This is NOT an error message. It is just

to stop BRBACKUP. You can use
brbackup option -q split instead.
Explanation: For FlashCopy Cloning, you are using

the normal brbackup command line that you specify
when running a FlashCopy backup. SAP has added a
new option 'q split' to the brbackup command, which
allows for running a full FlashCopy backup without
calling backint afterwards to run a tape backup. This
allows DP for Snapshot Devices to stop the brbackup
run without an error condition. This option also
produces brbackup runlogs with a different suffix than
usual (.anf, .aff).
User response: Please specify the option 'q split' in
the brbackup command to use the new SAP interface.
1071
1072
Chapter 13. Data Protection for Disk Storage and SAN VC for
Oracle Version 5.3 (EEO0000EEO9999)
This chapter describes the messages issued by Tivoli Storage Manager for
Advanced Copy Services: Data Protection for Disk Storage and SAN VC for Oracle
Version 5.3. The messages begin with the prefix EEO and are listed in numerical
order.
EEO0010I
v1 command completed successfully at:

v2
Explanation: No error was detected.

User response: Enter a supported command. See the
Installation and Users Guide for information about
supported commands.

User response:
EEO0011E
EEO0016I
ERROR!!!Invalid number of arguments

entered.
Explanation: Either incorrect arguments were entered

or the specified file does not exist.
====> Starting IBM Tivoli Storage

Manager for Hardware - Data Protection
for FlashCopy Devices executable on the
BACKUP SYSTEM: v1
Explanation:
User response:
User response: Correct the arguments and start the

process again.
EEO0017E
EEO0012E
Explanation: You have to be root to run this product.
ERROR!!!Unexpected error occurred.
ERROR!!!You have to be root to run this

program.
Explanation: An unexpected error occurred.
User response: Switch user id to root and try again.
User response: Gather information from the trace file

and log file and contact your IBM service
representative.
EEO0018E
EEO0013I
Received signal v1. Exiting...
ERROR!!!More than one instance of this

executable are running now.
Explanation: You have to wait until previous backup

is done before you can run this backup.
Explanation:
User response: Wait until previous backup is done

and try again.
User response:
EEO0014I
Exiting v1 command with errors!!!
EEO0019I
Explanation: Specified command failed with a non

zero return code.
====> Starting IBM Tivoli Storage

Manager for Hardware - Data Protection
for FlashCopy Devices executable on the
PRODUCTION SYSTEM: v1
Explanation:
User response: Please correct the problem indicated

by the previous error message and retry the command.
EEO0015E
ERROR!!!An invalid command was

entered.
Explanation: An unsupported command was entered.
User response:
EEO0021I
Completed Successfully.
Explanation: No error was detected.

1073
EEO0022I EEO0031W
User response:
EEO0022I
AIX Version: var1 Oslevel: var2.

EEO0023I
ESS CopyServices CLI Version:

var1.var2.
Explanation: Displays ESS CopyServices CLI version.

EEO0027I
Database instance name: v1
Explanation: Name of the database instance.

EEO0028I
Number of ESS lun pairs to be

flashcopied: v1
Explanation: Number of ESS lun pairs to be

flashcopied.

EEO0029I
EEO0024I
Filesystem consistency check completed

successfully.
Explanation: Filesystem consistency check on the

filesystems used for FlashCopy processing was
successful.
Explanation: Name of the database.

EEO0030I

EEO0025E
ERROR!!!Filesystem consistency check

failed.
Explanation: Filesystem consistency check failed on

the filesystems that were used for FlashCopy
processing. This means that there were some inode
changes on the filesystem when executing Data
Protection for FlashCopy Devices backup on the
production system.
System action: Please ensure that you do not make
any changes to the production system during flashcopy
backup, that may cause changes to the inodes on the
database filesystems. This will result in inconsistency in
the database filesystems being flashcopied. Examples of
operations resulting in inode changes are: When a file
is created or deleted. When a write() call occurs to a file
opened with O_SYNC and the write causes a new disk
block allocation. When fsync() or sync() functions are
called. When a write causes an indirect or
double-indirect block to be allocated. Another way to
get around this problem is to use raw logical volumes
for your databases.
User response: Please execute the backup command
again.
EEO0026I
User aborted v1 command.
Explanation: Specified command was aborted by user.

1074
Database name: v1
Number of Storage Volumes eligible for

FlashCopy processing: v1
Explanation: Number of Storage volumes eligible for

FlashCopy processing.
EEO0031W
WARNING!!!There was a problem while

we were trying to varyoffvg and
varyonvg with -c option for all the
volume groups which has Database
datafiles and change the owner and
group name for all the Database
datafiles from root to the original oracle
user/group name, therefore you need to
manually do those steps on every cluster
nodes except this local node.
Explanation: There was a problem while we were

trying to varyoffvg and varyonvg with -c option for all
the volume groups which has Database datafiles and
change the owner and group name for all the Database
datafiles from root to the original oracle user/group
name, therefore you need to manually do those steps
on every cluster nodes except this local node.
User response: There was a problem while we were
trying to varyoffvg and varyonvg with -c option for all
the volume groups which has Database datafiles and
change the owner and group name for all the Database
datafiles from root to the original oracle user/group
name, therefore you need to manually do those steps
on every cluster nodes except this local node.
EEO0032E EEO0062E
EEO0032E
ERROR!!! This command is supported

only with AIX 5.1 or higher.
EEO0059E
Explanation: User is running this command with

earlier version than AIX 5.1.
User response: Make sure your AIX version is higher
or equal to AIX 5.1.
ERROR!!!The database was backed up

using NOCOPY type of FlashCopy The
data in the target storage volumes is not
valid, and cannot be used to perform a
FlashCopy restore.

FlashCopy restore, the database needs to be backed up
using COPY or INCR type of FlashCopy.
EEO0033E
ERROR!!! This command is supported

only with ESS V2.3.0 or higher.
Explanation: User is running this command with

earlier version than ESS V2.3.0.
User response: Please restore the database from TSM

Server using DB2 restore command or Data Protection
for Oracle.
EEO0060E

User response: Make sure your ESS version is higher
or equal to ESS V2.3.0.
ERROR!!!Flashcopy type of v1 is invalid

when backup destination is: v2.
Explanation: When backup destination is TSMONLY,

flashcopy type should be set to NOCOPY as this type
of backup cannot be restored using flashcopy. You must
restore from TSM Server.When backup destination is
DISKONLY or DISKANDTSM, flashcopy type should
be set to COPY or INCR as this type of backup can be
restored using flashcopy.
User response:
EEO0054I
User response: Set the correct values for flashcopy

type and backup destination in the setup file and retry
the command.
EEO0052I
Starting database backup process.
Explanation: Database backup process started.
Backup to TSM completed with return

code : rc1.
Explanation: Database backup process completed.

EEO0061I

User response:
EEO0056I
Received error v1 while disabling the

new resources.
Explanation: An error occured when the process

User response: Please check the error log for details.
EEO0058I
Received error v1 while resetting the

target volumes.
Explanation: An error occured when the process

attempted to withdraw the flashcopy relationship
User response: Please check the error log for details.
Since a Nocopy type of Flashcopy

operation is taking place there is no
background copy to be monitored.
Explanation: If a Nocopy type of Flashcopy

operation is performed, a copy operation does not take
place in the background. Hence monitor command will
end.
EEO0062E
ERROR!!!The source / target LUN

information in the setup file has been
modified. Flashcopy Restore is currently
not supported for restoring the database
to a new location.
Explanation: The source / target information in the

database to different target LUNs, please use a different
setup file. At this time, Flashcopy Restore is only
supported for restoring the database to the orginal
source LUNs.
User response: The source / target information in the
database to different target LUNs, please use a different
Chapter 13. Data Protection for Disk Storage and SAN VC for Oracle
1075
EEO0065E EEO0072E
setup file. If you wish to restore the database to a new
location, please use the DB2 restore command to
restore it from TSM.
EEO0065E
ERROR!!!IBM ESS Copyservice CLI is

not installed.
Explanation: We couldnt find ibm2105cli.rte or ESScli

file installed.
User response: Please withdraw the persistent

flashcopy relationship for all the source ESS volumes
for this database, using the DP for ESS withdraw
flashcopy.
EEO0069W

User response: Make sure Copyservice CLI is installed
on your host machine.
EEO0066W
WARNING!!!Incremental flashcopy
cannot be performed on this version of
ESS CopyServices CLI as it is not V2.3.0
or later. A generic flashcopy will be
performed instead.
Explanation: Incremental flashcopy is only supported

on ESS Microcode and CopyServices CLI versions 2.3.0
or later. As this version of ESS CopyServices CLI is
lower than 2.3.0, an Incremental flashcopy cannot be
performed.
System action: A generic flashcopy with full volume
background copy will be performed instead.
User response: Please upgrade to ESS Microcode and
Copyservices CLI version 2.3.0 or later in order to take
advantage of the Incremental flashcopy feature.
EEO0067W
WARNING!!! Incremental change

recording is enabled. Performing
incremental flashcopy instead of COPY
type of flashcopy.
Explanation: Incremental change recording is enabled.

Performing a copy type of flashcopy will fail in this
case.
WARNING!!!Incremental flashcopy
of AIX: v1. A generic flashcopy will be
performed instead.
Explanation: Incremental flashcopy is only supported

lower than 5.1.0, an Incremental flashcopy cannot be
performed.
System action: A generic flashcopy with full volume
background copy will be performed instead.
User response: Please upgrade to AIX version 5.1.0 or
later in order to take advantage of the Incremental
flashcopy feature.
EEO0070E
ERROR!!!Some of the storage volumes

belonging to this database have
Incremental Change Recording Enabled
while others do not.

FlashCopy, all the storage volumes belonging to the
database must have change recording enabled.
User response: Please withdraw the FlashCopy
relationships for those storage volumes that have
incremental change recording enabled, using the Data
Protection for FlashCopy Devices withdraw command
and then retry the command. In the case of the monitor
command, withdraw the FlashCopy relationships and
retry both the backup and monitor commands.
Source volume: v1 Target volume: v2
Pending Sectors: v3
System action: An incremental flashcopy will be

performed instead.
EEO0071I
User response: Please withdraw the persistent

flashcopy relationship for all the source ESS volumes
for this database, using the DP for ESS withdraw
command, if you are interested in a COPY type of
flashcopy.

copied from source ESS volumes to target ESS volumes
in case of backup or from target ESS volumes to source
ESS volumes in case of restore.
EEO0068W
WARNING!!!Incremental change
recording is enabled. Performing
incremental flashcopy instead of
NOCOPY type of flashcopy.
Explanation: Incremental change recording is enabled.

Performing a nocopy type of flashcopy will fail in this
case.
System action: An incremental flashcopy will be
performed instead.

EEO0072E
ERROR!!!DP FOR ESS does not support

flashcopy backup of DB2 UDB
databases with multiple logical and/or
physical partitions.
Explanation: DP FOR ESS only supports flashcopy

backup of DB2 UDB databases having a single physical
partition and a single logical partition only.
1076
EEO0073E EEO0125E
EEO0073E
ERROR!!!DB2 UDB Server has not been

installed.
Explanation: DB2 UDB Server has not been installed.


is specified correctly in the Setup File.
EEO0121E
ERROR!!!A null volume group has been

detected.
Explanation:
WARNING!!!Backup destination option

has not been specified in the user setup
fileIt has been set to the default value
of: v1.
Explanation: If backup destination option is not set in

the user setup file it will default to DISKANDTSM if
flashcopy type is COPY or INCR or to TSMONLY if
flashcopy type is NOCOPY.
EEO0076E
ERROR!!!A null logical volume has

been detected.
DB2 UDB Server Version: v1.
Explanation: Displays the DB2 UDB Server Version.
EEO0075W
EEO0120E
Explanation: A null logical volume was detected.
User response: Please install DB2 UDB Server and set

up your database on Enterprise Storage Server, before
invoking DP FOR ESS.
EEO0074I
User response: Make sure you dont have control files

and redo log files in the same volume group with
Oracle datafiles.
ERROR!!!Current ESS CLI Version does

not support the function that you are
trying to run.
User response:
EEO0122E
ERROR!!!An error is detected in volume

group : vg1.

volume group.
is specified correctly in the Setup File. Verify that AIX
volume manager is operating If the problem persists,
gather information from the trace file and log file and
contact your IBM service representative.
EEO0123E
ERROR!!!The physical volumes of the

volume group v1 were not found.
Explanation: Withdraw command is supported only

with ESS CLI Version 2.3.0 or higher.
Explanation:
System action: Processing Ends.
User response: Please install ESS CLI V230 or higher.
User response:
EEO0110I
Found database file v1 in logical volume

v2 and volume group v3.
Explanation: Found which logical volume and volume

group this particular database file is belong to.
System action: None
EEO0124I

system.
User response:
User response: None

EEO0125E
EEO0115W
WARNING!!!Either Oracle control file or

redo log file is in the same volume
group (v1) with which Oracle datafiles
are.
Explanation: Either Oracle control file or redo log file

is in the same volume group with Oracle datafiles.
ERROR!!!Serial number for the device

v1 is not found.
Explanation:
User response:

1077
EEO0126I EEO0136E
EEO0126I

some time.......

to match with the source device.
User response:
EEO0127I
Removing device : parm1
Explanation:
User response:
EEO0128E
ERROR!!!Configuring the target volume

would cause duplicate physical volume
ID : pvid1.

User response: Perform one of the following: Delete
the disk on the backup system only: 1. find the disk
using the AIX lspv command 2. run smitty and choose
the following from the menu: devices- fixed diskremove a disk- select the disk to be removed 3. press
return Clear the pvid of each physical volume hdisk by
issuing the aix chdev command with the following
arguments:chdev -1 (hdisk#) -a pv=clear
EEO0129E
ERROR!!!Removing device parm1 failed.
EEO0133E
ERROR!!!Failed to open a logical

volume device with errno errno for
logical volume: lv.
Explanation: An error occurred while trying to open a

logical volume device. This will prevent this JFS log
logical volume from being suspended while
establishing flashcopy backup. This may result in an
inconsistent database snapshot during backup.
However, processing will continue.
User response: Please contact AIX support to find out
why the opening of a logical volume device failed.
EEO0134E
ERROR!!!Failed to suspend I/O on a

logical volume device with errno errno
for logical volume: lv.

suspend I/O on a JFS log logical volume device. I/O
on this logical volume will not be suspended while
establishing flashcopy backup. This may result in an
inconsistent database snapshot during backup.
However, processing will continue.
User response: Please contact AIX support to find out
why the suspend I/O on a logical volume device
failed.
EEO0135E
ERROR!!!Failed to resume I/O on a

logical volume device with errno errno
for logical volume: lv.
Explanation: An error occurred while trying to resume

I/O on a JFS log logical volume device.
Explanation:
System action: Processing stops..
User response: Try running the DP for ESS resume

command. If the failure persists, please contact AIX
support to find out why the resume I/O on a logical
volume device failed.
User response:
EEO0130W
WARNING!!!Removing the mount point

directory mntpt1 failed with rc: rc1.

EEO0136E
ERROR!!!Volume group removing failed

with rc rc1 for volume group vg1.
Explanation: An error occurred while performing the

exportvg command.
User response:
EEO0132W
User response: Verify that the volume group is not

corrupt. Run the exportvg command with the volume
group name from the command line.
WARNING!!!The umount command

failed with rc rc1 for mount point
mntpt1.

User response:
1078
EEO0138I EEO0150E
EEO0138I
Flashcopy type is set to NOCOPY.

disks... This backup is NOT valid for a
flashcopy restore. Please restore from
TSM Server.

valid for a flashcopy restore. You can only restore from
TSM Server.
EEO0144E
ERROR!!!A logical volume v1 is not

defined in volume group v2.
Explanation: The physical disk that database allocated

is not found.
User response: If the problem persists, please collect
the trace data and log file and present to IBM service
representative.
EEO0146E
ERROR!!!An physicall disk for the

volume group:v1 is not found.
Explanation: The physical disk that database allocated

is not found.
EEO0140I
Flashcopy type is set to COPY or INCR.

target disks... This backup is valid for a
flashcopy restore.
User response: If the problem persists, please collect

the trace data and log file and present to IBM service
representative.
Explanation: The target PVIDs are not cleared.This

This backup can be used for a flashcopy restore.
EEO0147I
Explanation:
Exporting volume group fnm1 failed.
User response:
EEO0141E
ERROR!!!Unsupported volume v1 has

been detected.
EEO0148I
Explanation: The volume that database has benn

allocated is an unsupported type.

command.
User response:
User response:
EEO0142E
EEO0149I
ERROR!!!Unsupported file system has

been detected.
Explanation: The file system that database allocated is

an unsupported type.
Newly imported volume group: vg1
Explanation:
User response:
User response: Make sure that the mount point exists

and the file system is supported.
EEO0150E
EEO0143E
ERROR!!!Unsupported volume group v1

has been detected.
Explanation: The volume group that database has

been allocated is an unsupported type.
rootvg.
ERROR!!!Logical Volume can not be

found for the file fnm1.
Explanation: The resources reside in an unsupported

volume.
User response: Make sure the volume is supported. If
the problem persists, gather information from the trace
file and log file and contact your IBM service
representative.
1079
EEO0151E EEO0174E
EEO0151E
ERROR!!!Varying off volume group fnm1

failed.
EEO0162E
ERROR!!!Volume group vg1 can not be

found.
Explanation:
Explanation:
User response:
User response:
EEO0152I
EEO0164E
ERROR!!!Quorum of the volume group

vg1 must be off.

groups.
Explanation:
User response:
User response:
EEO0153I
EEO0166E

fnm1
ERROR!!!Logical volume vg1 must have

at least 2 copies.
Explanation:
Explanation:
User response:
User response:
EEO0154I
EEO0168E
<fnm1><fnm2><fnm3><fnm4><fnm5>
Explanation:
User response:

the parallel scheduling policy.
Explanation:
User response:
EEO0158I
LogDev=fn1 Serial Number=fn2

EEO0170W
Explanation:
User response:
EEO0160I
<fn1> VOLUME GROUP : fn2 COPIES :

fn3 SCHED POLICY : fn4 STALE PPs :
fn5 MIRROR WRITE CONSISTENCY:
fn6
WARNING!!!Logical volume vg1 has vg2

stale partitions.
Explanation:
User response:
EEO0172E

the mirror write consistency on.
Explanation:
Explanation:
User response:
User response:
EEO0161E
EEO0174E
ERROR!!!No volume group was found.
Explanation:
User response:
ERROR!!!None of the mirror copies of

vg1 was completed on the specified ESS
vg2.
Explanation:
User response:
1080
EEO0176E EEO0275I
EEO0176E
ERROR!!!Some of the partitions of vg1

are stale on the specified ESS vg2.
EEO0190E
ERROR!!!The number of new volume

groups is limited parm1.
Explanation:
Explanation:
User response:
User response:
EEO0178I
EEO0191I

value of 1.
User response:

User response:
EEO0270E
ERROR!!!Failure in changing the mount

point vg1, return code vg2 from
command chfs.
Explanation:
ERROR!!!Invalid option found in the

Setup File.
Explanation: The parameter value is invalid.

User response: Correct the value and restart the
processing.

User response:
EEO0182E
Explanation:
Explanation:
EEO0180E
Varying on volume group fnm1 failed.
EEO0272I
ERROR!!!The same hdisk vg1 can not be

(serial numbers vg2 and vg3). command
chfs.

buffers to disk.
User response:
Explanation:
EEO0273I
User response:

EEO0184E
ERROR!!!lsvg command failed.
Explanation:
User response:

EEO0274I
User response:
Explanation:
EEO0186I
Recreating the new volume groups....
Explanation:
System action:
User response:

User response:
EEO0188E
ERROR!!!lvm queryvg failed.
Explanation:
EEO0275I
Explanation: The number of file systems exceeds

compiled limit.
User response:
User response:
1081
EEO0280E EEO0294I
EEO0280E
ERROR!!!There have been changes in

the configuration of the volume groups
for the specified Database. Additional
file systems have been detected. As a
result Flashcopy Restore is aborting.

EEO0290E
ERROR!!!The source volume with serial

number cmd is not attached to the
production system anymore.
Explanation: It is recommended that the user perform

a full database backup every timethere are any changes
to the database configuration such as addition ofnew
filesystems or raw logical volumes as tablespace
containers.

database volumes on the production system. Now, on
the FlashBack restore, it could not be found anymore
User response: Please restore the database from TSM

Server using DB2 restore command.
Use the Storage subsystem web interface to find out to
which host this volume is attached. You will be able to
restart the Flashcopy restore anytime, as long as you
have a valid disk backup on the target storage
volumes.
EEO0282I
Data Protection for FlashCopy Devices

found a difference between the names
of the logical volumes which were on
the production database at the time of
the FlashCopy backup and the current
logical volumes at the time of the
FlashCopy restore. If you continue, you
will lose newly added logical volumes.
Do you want to continue? Please enter
Yes or No.
Explanation:
User response:
EEO0291E
ERROR!!!The source volume with serial

number cmd belongs to another volume
group.

database volumes on the production system. Now, on
the Flashcopy restore, Data Protection for FlashCopy
Devices found it as member of another volume group
and can not proceed with the restore.
EEO0284I
Could not query the operating system to

obtain the list of file systems for the
volume groups containing the database.
Explanation:

specified FlashCopy backup for the FlashBack restore.
You will be able to restart the FlashBack restore
the target storage volumes.
User response:
EEO0293I
EEO0286I
Could not query the operating system to

obtain the list of disks for the volume
groups containing the database.
Explanation:
User response:

Explanation: Prior the start of the FlashBack restore,

Data Protection for FlashCopy Devices will display a
list of all the file systems which are currently on
EEO0287W
WARNING!!!
database_control_file_restore is set to
yes in the setup file. You will need to
do the incomplete recovery after the
restore.
Explanation: database_control_file_restore is set to yes

in the setup file. You will need to do the incomplete
recovery after the restore.
1082
EEO0294I

restored...
Explanation: Prior the start of the Flashcopy restore,

Data Protection for FlashCopy Devices will display a
list of all the file systems which were on production
EEO0297W EEO0303W
EEO0297W
WARNING!!!The newly added volume

cmd will be reduced from the database
volume group rc.

physical volumes from a volume group. Data
Protection for FlashCopy Devices is calling it here on
Flashcopy restore to remove the physical volumes
FlashCopy backup.
for ESS will use the command hd2vp to convert the

ESS hdisk device volume group to a Subsystem Device
Driver vpath volume group. This will take effect after
the importvg and prior to the mount of the file systems
EEO0301W

User response:
EEO0298I
Logical volume lv on the mount point

mp was removed during Flashcopy
Restore, because it was newly added
since last backup, needs to be recreated
manually.
Explanation: DP for ESS found a difference between

the names of the logical volumes which were on the
production database at the time of FlashCopy backup
and the current logical volumes at the time of the
FlashBack restore.
WARNING!!!The rmlv command lv

ended with return code rc.
Explanation: On the function FlashBack restore, DP

for ESS will use the command rmlv to remove the
logical volumes on which the production database
should be restored. This will take effect after the
unmount and prior to the exportvg and the actually
flashcopy reverse.
FlashBack restore anytime, as long as you have a valid
disk backup on the target ESS volumes.

User response: DP for ESS will ask you during the
FlashBack restore if you are sure to continue before all
the file systems and logical volumes will be removed.
After that, DP for ESS will only reconstruct the file
systems which were backed up with FlahCopy. You
have to add manually all the additional system changes
that were made after the FlashCopy backup.
EEO0299I

after the FlashCopy process in
the LVM copies:
Explanation: Data Protection for FlashCopy Devices

will not automatically synchronize the copies after the
will be created and put out.
EEO0302E
ERROR!!!DP for ESS encountered a

function of the ESS Copy Services.
Explanation: DP for ESS requested for a set of ESS

source/target volume pairs a FlashCopy to be done by
the ESS Copy Services. If the request fails within the
ESS for one or more pairs with a non-zero return code,
then DP for ESS will provide the return code and then
terminate.
User response: In order to identify which ESS
volume(s) were the cause of the problem you need to
view the ESS Copy Services status log for failures, there
you find the failing volume(s) along with details about
EEO0303W

process in background has finished. If necessary you
have to add additional parameter to the commands to
improve the performance of the synchronization.
Explanation: DP for ESS found on the backup system

after the flashcopy that the specified file system still
exist in the /etc/filesystems.
EEO0300E
ERROR!!!Error converting the ESS hdisk

device volume group vg to a Subsystem
group.
WARNING!!!The file system fs has

already an entry in the /etc/filesystems.

User response: Normally the command exportvg
will remove the corresponding file systems from the
/etc/filesystems. Check for errors during the unmount
and withdraw process.
Explanation: On the function FlashCopy backup, DP

1083
EEO0304W EEO0312E
EEO0304W
WARNING!!!The reducevg command

cmd ended with return code rc.
EEO0307I

volumes ...

physical volumes from a volume group. Data
Protection for FlashCopy Devices will call it 1. on
FlashBack restore to remove the physical volumes
added after the FlashCopy backup. 2. on FlashBack
restore with LVM mirroring to remove the physical
volumes which are residing on the Storage Subsystem
that is not yet involved in the FlashBack. 3. on
FlashCopy backup with LVM mirroring if the
environment variable IMPORTVG is set, to remove the
physical volumes which are residing on the Storage
Subsystem that is not yet involved in the FlashCopy.
Explanation: On the function FlashBack restore, DP

for ESS will use the command rmlvcopy to remove the
copies of the logical volumes residing on the second
ESS. This will take effect after the unmount and prior
to the exportvg and the actually flashcopy reverse.
Explanation: On the function FlashBack restore, after

the flashcopy reverse and the import of the volume
groups, DP for ESS will add the physical volumes
residing on the second ESS to the database volume
groups.


EEO0309I

groups ...

EEO0305W
WARNING!!!The extendvg command


volumes to a volume group. Data Protection for
FlashCopy Devices will call it to add the volumes
which are residing on the Storage Subsystem that is not
yet involved in the FlashBack to the database volume
groups.

EEO0310I
Explanation: On the function FlashBack restore, Data

Protection for FlashCopy Devices will use the
command mklvcopy to add the copies of the logical
volumes on the second Storage Subsystem. This will
take effect after the importvg and the extendvg.
EEO0311W
EEO0306W
WARNING!!!The mklvcopy command


will call the command mklvcopy to add a copy of a
logical volume on the physical volumes residing on the
second Storage Subsystem. This call will only take
effect in a LVM mirroring environment, after the
FlashBack restore was initialized. The FlashBack restore
and the recovery will continue, but the second copy of
the logical volumes will be missing.
restore anytime, as long as you have a valid disk
backup on the target storage volumes.
WARNING!!!The command cmd ended


EEO0312E
ERROR!!!Importing the volume group

from hdisk logdev failed.

will use the command importvg on the function
FlashCopy backup. This command will be issued on
the backup system after the actually FlashCopy and the
run of the configuration manager(cfgmgr). It takes a
volumes from each volume group building up the
production database, reads its VGDA and makes this
information available to the operating system.
1084
EEO0313E EEO0354I
EEO0313E
ERROR!!!Recreating the volume group

from the hdisks hdisks failed.

will use the command recreatevg on the function
FlashCopy backup if the production database is
residing on an high-available LVM mirror environment.
after the actually FlashCopy and the run of the
configuration manager (cfgmgr). The difference to the
command importvg is that recreatevg will create the
volume group only with the specified volumes. These
are building up exact the one copy on the Storage
Subsystem where the FlashCopy was issued.
EEO0314W
WARNING!!!Removing the logical

device logdev whith the same PVID pvid
in the ODM.
Explanation: There is still another logical device

(hdisk or vpath) in the state defined with the same
PVID as one of the source volumes.
EEO0350E
Explanation: The Data Protection for FlashCopy

Devices query command cannot determine the size of
the volume.
User response: Issue a query command from the
Storage Subsystem Copy Service Web Interface to verify
that the disk exists. If the problem persists, save the
diagnostic information and contact IBM service.
EEO0351E
EEO0315I

originally present.
Explanation: This message will appear if running the

function FlashBack restore, a file system was found that
was added after the FlashCopy backup.
System action:
User response: The user is responsible for create the
new file system after the flashcopy reverse, but before
EEO0316W
WARNING!!!The database volume

groups do not contain currently any file
system.
Explanation: This message will appear if running the

function FlashBack restore, none file system was found
on the original database volume group. Following that,
DP for ESS will display a list of the file system which
are residing on the flashcopy target volumes. These will
be restored by means of FlashBack.
System action:
ERROR!!!The size of source volume: src1

size1 and target volume: tgt1 size2 are
different.
Explanation: The size of the source volume and target

volume are different. The source volume and target
volume must be the same size and reside in the same
Logical Subsytem (LSS).
User response: Issue a query command from the ESS
Copy Service Web Interface to verify that the disk
exists. If the problem persists, save the diagnostic
information and contact IBM service.
EEO0352E

ERROR!!!Error while getting the size of

the volume: src1 size.
ERROR!!!Incorrect value size is specified

for thetarget volume: tgt1 in the Setup
File.
Explanation: The shark_target_volume parameter in

the Setup File specifies an incorrect size for the target
volume.
User response: Make sure the shark_target_volume
parameter in the Setup File specifies a correct size for
the target volume. If you do not know the exact size of
the target volume, specify a dash (-) for both the source
value and size value. The size of the target volume will
be determined automatically.
EEO0353E
ERROR!!!Unable to open file file1.

EEO0354I
Performing fctype flashcopy of: Source

ESS volume: src1 to Target ESS volume:
tgt1
Explanation: A flashcopy from the source volume to

1085
EEO0355E EEO0365I
User response:
EEO0355E
ERROR!!!The ESS FlashCopy command

failed.
Explanation: The flashcopy command failed. This

could be due to various reasons: 1. Some library or jar
files may be missing from the Copy Services command
line interface package. 2. The source volumes or target
volumes are in another flash copy relationship. 2. The
Copy Services command line interface package and
Copy Services microcode are not in sync.
are in another flashcopy relationship, wait until the
with the Enterprise Storage Server administrator to
obtain the appropriate level of Copy Services command
line interface and microcode.
EEO0357I
Performing flashcopy withdraw of

source ESS volume src1 from target ESS
volume tgt1
EEO0360I
Querying the ESS for volume size

...Volume: volser1 volsize

requested.
User response:
EEO0361I
A NOCOPY Flashcopy was performed.

Withdrawing the nocopy flashcopy
relationship...
Explanation: The flashcopy relationship between the

NOCOPY Flashcopy is performed.
User response:
EEO0362I

Services Server:serv1

User response:
Explanation: A flashcopy withdraw of the source

EEO0363I

ready.
User response:
EEO0358E
ERROR!!!No target volume is available.

Terminating......

User response:
EEO0364I

User response: Make sure the target volumes reside in
the same Logical Subsystem (LSS) as the source
volumes and that the target volumes are available to
the backup system. Also, make sure the syntax is
correct in these Setup File parameters: 1.
shark_target_volume 2. shark_copy_service_code 3.
java_home_directory 4.
shark_password
EEO0359I
Incremental Change Recording: val1
Explanation: Value of Incremental change recording.

User response:
1086
The connection to the primary Copy

Services server failed. The process
continues to check the backup Copy
Services server.

available. Verify that the TCP/IP connection is valid.
User response:
EEO0365I

Services Server:serv1

User response:
EEO0366I EEO0377I
EEO0366I
Flashcopy was performed with parm1

option.
Explanation: This is the type of flashcopy that was

specified by the user as DP for ESS overrides this value
under certain conditions.
EEO0371I
Explanation: None.
EEO0372I

EEO0367I
Source and Target ESS volumes have

been switched due to a previous
incremental flashcopy restore
operation.Previous target volume: parm1
is now the source volume.Previous
source volume: parm2 is now the target
volume.
Explanation: Whenever user performs an incremental

flashcopy restore operation, the source and target ESS
volumes will be reversed.
Value of Flashcopy type is: parm1.

been specified.

defined in the Setup File. An attempt to use the backup
User response:
EEO0373E
ERROR!!!A required parameter tgtv1 is

missing in the Setup File.
Explanation: A required parameter in the Setup File

has not been specified. This may be caused by incorrect
syntax in the Setup File.
EEO0368I
User response: Make sure all the required parameters

are present in the Setup File and that no space exists
between the parameter and the colon(:).

ready...

ready.
EEO0374I
Querying Storage Subsystem for status

of volume: volser1
User response:

EEO0369E
ERROR!!!Both the primary Copy

Services server and the backup Copy
Services server are not available...
Explanation: The primary Copy Services server and

the backup Copy Services server are not available.
User response: Use the ESS Copy Service Web
Interface to verify the TCP/IP connection is valid for
both the Copy Services servers. Also, verify that the
ESS is configured correctly.
EEO0370E
ERROR!!!A Copy Services backup server

has not been specified. Exiting...
Explanation: The backup Copy Services server is not

specified in the Setup File.
User response: Use the ESS Copy Service Web
Interface to verify the TCP/IP conection is valid for the
backup Copy Services server. Also, verify that the ESS
is configured correctly on the backup Copy Services
server.

EEO0375E
ERROR!!!ESS volumes are involved in a

flashcopy or a PPRC operation.
Explanation: ESS source or target volumes are

involved in a flashcopy or a PPRC operation. Flashcopy
backup or restore command will not be performed.
User response: Ensure that the source and target ESS
volumes are not in use in a flashcopy or PPRC
operation, before issuing the flashcopy backup or
restore command.
EEO0377I
Background copy is in
progress....Sleeping for v1 minutes....
Explanation: Blocking for

SHARK_QUERY_INTERVAL period prior to querying if
the background copy operation has completed.
1087
EEO0378I EEO0410I
EEO0378I
Background copy is complete.
Explanation: Background copy for flashcopy backup

or restore is complete.
EEO0379E
ERROR!!!An invalid value: parm1 has

been specified for backup destination.
Explanation: Backup destination can only be

TSMONLY, DISKONLY or DISKANDTSM.
User response: Please specify TSMONLY, DISKONLY
or DISKANDTSM for the option backup destination
EEO0400E
ERROR!!!Error on running command:

parm1

system command.
EEO0402I
parm1
Explanation:
User response:
EEO0404I
Error: parm1
Explanation:
EEO0380E
ERROR!!!An invalid value: parm1 has

been specified for flashcopy type.
User response:
Explanation: Flashcopy type can only be NOCOPY,

COPY or INCR.
EEO0406I
Explanation: The user has chosen to terminate the

Flashcopy Restore operation.
User response: Please specify NOCOPY, COPY or

INCR for the option flashcopy type and retry the
command.
EEO0381I
Querying ESS for pending sectors for

volume: volser1

volumes was requested to ensure that background copy
is not in progress between them.
User abort; Exiting Flashcopy Restore.
System action: Restore processsing is terminated.

User response: Flashcopy Restore overwrites any
existing data on all the source LUNs, including (but not
not limited to) all filesystems and raw volumes on
them. Make sure all necessary data from the source
LUNs is backed up, and restart the procedure.
EEO0408I
User input was yes; Continuing

Flashcopy Restore.
Explanation: The user has chosen to continue the

Flashcopy Restore operation.
System action: Restore processsing continues.
EEO0382E
ERROR!!!ESS volume volser1 is a PPRC

source lun and PPRC relationship needs
to be removed before flashcopy restore
can be started.
Explanation: ESS target volume is a PPRC source

volume as well. Flashcopy restore command will not be
performed until PPRC relationship is cleared for this
lun volume.
User response: Ensure that target ESS volumes are not
in use in PPRC operation, before issuing the flashcopy
restore command.
User response:
EEO0410I
You are about to perform a Flashcopy

Restore operation. All data on the
source volumes, including (but not
limited to) filesystems and raw volumes,
will be lost. Do you want to continue?
Please enter Yes or No.
Explanation: Flashcopy Restore overwrites any

not limited to) all filesystems and raw volumes on
them. Make sure all necessary data from the source
LUNs is backed up, and restart the procedure.
System action: System waits for a valid user response.
User response: Please enter Yes to continue, or No
1088
EEO0412I EEO0525E
to abort the restore operation.
EEO0412I
A Flashcopy Restore operation has been

requested, with Prompt=No. All data on
source volumes, including (but not
limited to) filesystems and raw volumes,
will be lost. Continuing Flashcopy
Restore operation.
Explanation: Flashcopy Restore overwrites any

limited to) all filesystems and raw volumes on them. It
is strongly recommended that this operation be
performed with Prompt set to Yes. The user has chosen
to perform this operation with Prompt set to no.
System action: Restore operation continues.
User response: Make sure the TSM API is correctly

installed and that the TSM API and TSM Backup
Archive Client environmental variables are set correctly.
EEO0505E
Explanation: An error was detected when calling TSM

API terminate.
EEO0506E
User response:
EEO0500E
ERROR!!!You are trying to use a wrong

version of the TSM API library.
Explanation: Using a different TSM API library. Also,

this error is sometimes returned when an operating
system or DB2 UDB command fails.
User response: Compatible API libraries (insert api,
bit table) and check version. Also check the trace file
and tdpess.log file if error is due to the failed operating
system or DB2 UDB command. Based on the nature of
the failing command, make sure the configuration is
correct.
EEO0502E
ERROR!!!Invalid license is detected.
Explanation: An error was detected when running the

TSM Backup Archive Client Client command line
interface.
User response: Make sure the TSM Backup Archive
Client is correctly installed and that the environmental
variables are set correctly.
EEO0510E
ERROR!!!Incremental FlashCopy type is

not supported for SVC, but was defined
in the setup file.
Explanation: Incremental FlashCopy type was defined

in the setup file, but it is not supported for SVC yet
and you have to use other FlashCopy type.
User response: Change the FlashCopy type in the

setup file to something other than incremental.

User response: Check if there is a mismatch between
the executables (for the production system and backup
system) and the license file(agent.lic).
ERROR!!!An error has been detected
when calling TSM API setup.

API setup.
EEO0504E

when running the TSM Backup Archive
Client command line interface.
Explanation: An invalid license was found.
EEO0503E

when calling TSM API terminate.

when calling TSM API init.
EEO0524E
ERROR!!!Flashcopy type copy is invalid

when backup destination is set to
tsmonly.
Explanation: When backup destination is set to

tsmonly, we want to use nocopy of flashcopy type and
do not allow copy as flashcopy type.
User response: Change the FlashCopy type in the
setup file to nocopy.
EEO0525E
ERROR!!!Failed creating consistency

group.

API init.
Explanation: SVC limits the consistency group to 128

(0-127). When the maximum limit to the consistency
group is reached, the hdworcp backup gives an error
and exits.

1089
EEO0630E EEO0640E
User response:
EEO0630E
ERROR!!!A memory allocation error has

occurred.

applications.
EEO0632E
ERROR!!!A duplicate target volume

serial number tvol1 was found in the
Setup File.
Explanation: A duplicate target volume was specified

in the Setup File.
User response: Correct the duplicate volume serial
number in the Setup File and remove the duplicate
occurrences.
EEO0633E
ERROR!!!A data for required parameter

tgtv1 is missing in the Setup File.
Explanation: A value for a required parameter in the

Setup File has not been specified. This may be caused
by incorrect syntax in the Setup File.
User response: Make sure all the required parameters
are present in the Setup File and that no space exists
between the parameter and the colon(:).
EEO0636E
Explanation: The application could not create a

temporary file in the root filesystem.
User response: Make sure you have enough space in
the root file system, and have permission to create a
file in that file system.
EEO0637E
ERROR!!!An incorrect incremental

backup level found.
Explanation: An incorrect incremental backup level

was specified.
User response: The incremental backup level must be
a decimal number greater than or equal to 1.
ERROR!!!A temporary directory could

not be created.
Explanation: The application could not create a

temporary directory in the root filesystem.
User response: Make sure you have enough space in
the root file system, and have permission to create a
directory in that file system.
EEO0638E
ERROR!!!Background copy operation for

a flashcopy backup or restoreis not
complete.
Explanation: The background copy operation for a

flashcopy backup or restore command has not
completed.
User response: Invoke essorcp (or essdb2p) monitor
command to ensure that the background copy
operation is complete before issuing a flashcopy restore
or backup command.
EEO0639W
EEO0634E
ERROR!!!The metadata file cannot be

created.
WARNING!!!Could not copy setup file

v1 to directory v2.
Explanation: The User setup file is copied into the

specified directory and backed up to Tivoli Storage
Manager. Since the copy operation failed, the setup file
will be backed up to Tivoli Storage Manager from its
current location.
EEO0635E
ERROR!!!Temporary file cannot be

opened for writing.
Explanation: Temporary file cannot be opened for

writing.
User response: Make sure you have enough space to
create one file and have permission to create a file in
that directory.
1090
EEO0640E
ERROR!!!Could not open trace file v1.

tracefile. Please make sure you can open the trace file
which was specified in the setup file.
EEO0641E EEO0651E
EEO0641E
ERROR!!!Could not create the trace

object.
Explanation: There were some problems creating trace

class object.
EEO0642E
Explanation: During the restore process the database

can be brought back on-line but the background copy
must finish before another flash copy backup can
happen.
System action: System continues to monitor
background copy progress.
User response: Database can be brought back on-line
but is not eligible for another FlashCopy backup until
background copy is finished.
ERROR!!!Invalid trace flag: v1.
Explanation: Some invalid trace flags are defined in

the setup file.
EEO0647E

EEO0643E
ERROR!!!Either the database has not

been backed up or it has been backed
upby a previous version of our product.
In order to use the FLASHCOPY
RESTORE feature, the database has to
be backed up by IBM Tivoli Storage
Manager for Hardware. or later.
Explanation: A Flashcopy association exists between

System action: Restore command will fail.
User response: Please withdraw the Flashcopy
association between the source volume and the target
volume and retry the restore command.
EEO0648E
Explanation:
A Flashcopy association exists between

source volume: and a different target
volume: .

User response:

TDP function name : function-name TDP
function : function-desc TDP return code :
TSM-rc TDP file : file-name (line-number)
Explanation: None.
EEO0644E
ERROR!!!Database instance name has

not been specified in the user setup file.
Please specify the instance name and
Explanation: Please specify the database instance

name in the user setup file and retry the operation.

EEO0649I

User response: Please specify the database instance
name in the user setup file and retry the operation.
EEO0645E
ERROR!!!Database name has not been

specified in the user setup file. Please
specify the database name and retry the
operation.
Explanation: Please specify the database name in the

user setup file and retry the operation.
This configuration meets the minimum

requirements for a successfull Data
Protection for FlashCopy Devices
backup
Explanation: The preview command allows a user to

verify their environment prior to running a n actual
backup operation.
EEO0651E
A Flashcopy background copy is in

progress between source volume: and
target volume: .
User response: Please specify the database name in

the user setup file and retry the operation.
Explanation: A Flashcopy background copy from a

and target volumes.
EEO0646I
System action: Command will fail.
Database is successfully restored and

needs recovery. Continuing to monitor
hardware background copy progress.
This database is not eligible for another
FlashCopy operation until this
background copy finishes.
User response: Please wait until the background copy

is complete and retry the command.
1091
EEO1625I EEO2054E
EEO1625I
Number of volumes to be FlashCopied:

v1
Explanation: Number of volumes to be flashcopied.

User response: Please see the section about the CIM
return codes and their descriptions in the product
publication.

EEO1626E

when processing a TDP for Hardware
function. TDP function name :
function-name TDP function : function-desc
TDP return code : TSM-rc TDP file :
Explanation: None.
EEO1631E

in file filename, line number linenumber.&
msgnl;

applications.

EEO1627E
Explanation: The specified virtual disk is not found in

the list of virtual disks provided by the connected SVC
cluster.
EEO2051W

found on location.

be build in the specified directory.

the SVC.
EEO1628E


EEO2052E

subsystem.
subsystem is initilized properly. Check for preceding
error messages.
EEO2053E
EEO1629E


User response: Ensure that of the source and target
EEO1630E

operation of the Common Interface
Model(CIM). TDP function name :
function-name TDP function : function-desc
TDP CIM return code: 0xCIM-rc TDP
file : file-name (line-number)
Explanation: An error occurred when calling a CIM

1092

missing.


applications.
EEO2054E

unexpected message error during the execution of a
EEO2055I EEO2063W
EEO2055I

be locked.

application unlock the local repository.
shark_copy_service_code 3. java_home_directory 4.
shark_password
EEO2060W

EEO2056I

application.
Explanation: During the local repository is locked by

periode of time to proceed. In mySAP environment is
that time 1 hour.

the specific source not any target volume could be
found in this target data container that matchs for a
FlashCopy operation. If multiple target data containers
are being used, the processing will continue chacking
the volumes of the next target data container.
EEO2061W

EEO2057E

local repository is initialzed. Check for preceding error
messages.
EEO2058E


correspondent properties. A failure occurred during
that proccess.

container dcID to match with the source
srcvol.

Explanation: An inquire of the data container with the

set does not exists in the local repository.
User response: The application that is requesting the
inquire will decide whether or not the error should end
the program. Check for following messages.
EEO2062W

criteria.


like memory allocation error or other system error.

application specific. Check for following messages. The
application will decide whether or not that warning
EEO2059E
EEO2063W

match with the source data container.
Explanation: During a FlashCopy backup, DP for

Hardware tries to find a target data container that
matches the source data container to satisfy the
FlashCopy backup. A matching target data container
could not be found.
User response: See the rules for select one of multiple
target data containers. For example, this message will
be displayed if the user is trying to start a FlashCopy
backup of type INCR and all the target sets are being
used for the FlashCopy type COPY. Make sure also
that the target volumes are available to the backup
system and the syntax is correct for the following setup
file parameters: 1. shark_target_volume 2.


User response: The application will decide whether or
not that warning should end the program. Check for
following messages.
1093
EEO2064I EEO2073E
EEO2064I

EEO2069E


being created.


right of the file.
EEO2065I


User response: Look for a operating system error
message.
EEO2066E

EEO2070E

in not correct.
format of this file is correct. Check for preceding error.
EEO2071E

right of the file.
EEO2067E


EEO2068E


Inserting an entry for a new data container occurred an
error.
preceding error. If not any other error can be seen,
collect the loogs and traces and contact the support.
EEO2072E

Explanation: The program will search in the .fct file

for each specific data container a list of entries with the
label <PREFIX>TARGET_VOLUME where the prefix
depends on the hardware type. Either you have a
wrong label for the target volumes of the specified data
container or this data container in the .fct file does not
have any target LUNs.

empty or has a wrong format .

processing a Data Protection for
Hardware function. TDP function name
: function-name TDP function :
function-desc TDP return code : TSM-rc
TDP file : file-name (line-number)
Explanation: None.

User response: This error can only occured if the
format will automatilly be checked. If so, please check
the format of the .fct file.
EEO2073E

writing.

occurred an error.
1094
EEO4000E EEO6020E
User response: Check the rights permission of that
file.
EEO6015E
EEO4000E
Explanation: Oracle database data files were not

found.
ERROR!!!program-name: cannot open file

file-spec: error.
ERROR!!!Oracle database data files were

not found.
Explanation: TDP cannot open the file.

System action: TDP cannot complete the requested
operation.
User response: Make sure the correct database system

identifier (SID) is specified in the Setup File.

continues, check with your system adminis trator.
EEO6016E
EEO6011E
Explanation: Oracle database control files were not

found.
ERROR!!!The Oracle database is

currently in read-only mode.
ERROR!!!Oracle database control files

were not found.
Explanation: The Oracle database is currently

designated as read-only. Processing stops.


User response: Remove the read-only mode of the
Oracle database and run the operation again.
EEO6017E
EEO6012E
Explanation: No table space was found for the Oracle

database.
ERROR!!!An error occurred while

attempting an alter system suspend
action.
Explanation: An error occurred while attempting an

alter system suspend action.
ERROR!!!No table space was found for

the Oracle database.


User response: Make sure the Oracle database to be
backed up is running, then try to suspend the system
with a command line invokation. If the system
suspends successfully, run the operation again.
EEO6018E
ERROR!!!No password file was found

for this database.
Explanation: Either a password file for this database

was not found or the password file cannot be read.
EEO6013E
ERROR!!!An error occurred while

attempting an alter system resume
action.
Explanation: An error occurred while attempting an

alter system resume action.
User response: Make sure the Oracle database to be
backed up is running, then try to resume the system
with a command line invokation. If the system resumes
successfully, run the operation again.
EEO6014E
ERROR!!!The Backup type is online but

the mount mode is either nomount or
startup restricted.
Explanation: The Backup type is online but the mount

mode is either nomount or startup restricted.
User response: Change the mount mode to startup
mount.
User response: Make sure you have a valid password

file for this database.
EEO6019E
ERROR!!!The log mode for this database

is NOARCHIVELOG.
Explanation: The log mode for this database is

NOARCHIVELOG.
User response: Change the log mode for this database
to ARCHIVELOG.
EEO6020E
ERROR!!!The database failed to

shutdown during the flashcopy
operation.
Explanation: The database attempted to shutdown

because the backup type parameter is set to offline. The
database failed to shutdown.
User response: Manually shutdown the database you
1095
EEO6021I EEO6034W
are trying to back up, then run the operation again.
EEO6021I
Changing Oracle mode to: parm1.
EEO6028E
ERROR!!!Oracle database redo log files

were not found.
Explanation:
Explanation: Oracle database redo log files were not

found.
User response:

EEO6022I
Production datafile parm1 cataloged as

parm2.
EEO6030E
Explanation:
ERROR!!!No host name was found for

the Oracle database.
Explanation: No host name was found for the Oracle

database.
User response:
EEO6023I
Retrieved file parm1 from node: parm2.

Explanation:
EEO6031W
User response:
EEO6024E
ERROR!!!RMAN Backup for the

database v1 failed.
Explanation: The RMAN BACKUP cannot be

performed on the database. The detail error code and
the reason code is kept in the error log file. Backup
processing terminates.
User response:
EEO6025I
The Oracle database v1 backed up

successfully.
Explanation:
WARNING!!!Remote process v1 failed. i

Oracle DB on remote cluster node
couldnt be brought down before
Flashcopy Restore was started.
Explanation: We tried to remotely shutdown Oracle

DB on the remote cluster node, but failed.
User response: May need to do Flashcopy Restore
again.
EEO6032W
WARNING!!!Remote process v1 failed. i
Explanation: We tried to remotely varyoffvg,

varyonvg and change the owner of the Oracle Datafile
to Oracle Owner on the remote cluster node, but failed.
User response: May need to do Flashcopy Restore
again.
User response:
EEO6033E
EEO6026E
ERROR!!!Failed to get parallel

information.
Explanation: Failed to get parallel information using

sqlplus.
User response:
EEO6027E
ERROR!!!Failed to get oracle version

information.
Explanation: Failed to get oracle version information

using sqlplus.
User response:
1096
Oracle database owner cant be root.
Explanation: Oracle database owner cant be root.

User response: Need to change the owner of Oracle
files to some other user id.
EEO6034W
WARNING!!! Oracle control files are in

the same volume group with Oracle
datafiles. We strongly recommend that
you put Oracle control files in a
different volume group from the one
which has Oracle datafiles and do the
backup again.
Explanation: It is not a very good practice to have

Oracle control files in the same volume group with
EEO6035W EEO7823E
Oracle datafiles and it could cause some unexpected
problems.
User response: We strongly recommend that user put
Oracle control files in a different volume group from
the one which has Oracle datafiles.
EEO6035W
WARNING!!! Oracle redo log files are in

the same volume group with Oracle
datafiles. We strongly recommend that
you put Oracle redo log files in a
different volume group from the one
which has Oracle datafiles and do the
backup again.
Explanation: It is not a very good practice to have

Oracle redo log files in the same volume group with
Oracle datafiles and it could cause some unexpected
problems.
User response: We strongly recommend that user put
Oracle redo log files in a different volume group from
the one which has Oracle datafiles.
EEO7368E
ERROR!!!Invalid trace file name (name

too long).

EEO7383E
ERROR!!!Specifying the trace file link

as a symbolic link is not allowed.

link.
tracefile option.
EEO7384E
ERROR!!!Symbolic link linkname to

target was successfully deleted.

EEO7152I



User response: None

EEO7366E
EEO7385E
ERROR!!!Unable to close trace output

file file-name.

space).


EEO7367E
ERROR!!!Unable to delete symbolic link

link.
ERROR!!!Unable to write to trace file

tracefile. Tracing disabled.

continues.
EEO7823E
ERROR!!!Invalid trace keyword keyword

User response: Correct the value. See the entry for
TRACEFLAGS in the Trace Facility Guide document for
a list of valid trace flags.

1097
EEO7826E EEO7836E
EEO7826E
ERROR!!!Unable to open trace output

file file-name.

EEO7829E
Initialization functions cannot open one

of the Tivoli Storage Manager logs or a
related file: log-name. errno = errno-value,

On Unix systems, the log may not be placed in the root
directory. Attempts to do so will result in an access
denied error.
current user has write permission.
EEO7830E


EEO7832I
TDP is converting the log-file from

minutes.

and old data saved.
EEO7833I
TDP is converting the log-file from

minutes.

EEO7834I


given log location.
Explanation: This product only supports IBM ESS

microcode level 2.3 and 2.4.

EEO7831E


link.
1098

EEO7835E
The version of IBM Enterprise Storage

Server is not supported.

User response: Ensure that ESS microcode level 2.3 or
2.4 is installed.
EEO7836E
The putenv command failed for path =

v1.
Explanation: None.
User response: *** NEED A BETTER EXPLANATION
***
EEO7837E EEO7844E
EEO7837E
ESS Lun ID v1 is not valid.
EEO7843E
Neither source volume id nor target

volume id is in the volume list.
Explanation: Length of ESS LUN id must be 8

characters.
Explanation: None.
User response: Make sure the length of ESS Lun id is

8.

EEO7844E
EEO7838E
The ESS jar file v1 cannot be found.
Explanation: None.
User response: *** NEED BETTER RESPONSE FOR
THIS ***.
EEO7839E

failed; rc=rc.
Explanation: None.
EEO7840E
The primary and secondary copy service

servers are down.
Explanation: None.
User response: Start at least one of the ESS copy
service servers. If copy server is already running, check
the value of java home specified during configuration
to make sure it is a valid path name of the directory
where JRE is installed on master backup node. Use
configuration wizard to update java home value for the
configuration.
EEO7841E
The operating system refused a TDP

Explanation: TDP requires access to memory in order

to allocate.
System action: TDP cannot complete the requested
operation.
dividing the task into serveral smaller units. For
level directories, run the TDP task serially for each
directory. If the TDP task is an incremental backup, use
The ESS LUN are already in use.
Explanation: None.
User response: Release ESS LUN in order to reuse
them.
EEO7842E
Cannot open the ESS command output

file v1 for writing.
Explanation: Cant open this file for writing.

your system and write permission to the file.
1099
1100
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
E
W
Severe error
Error
Warning
Information

Processing can continue, but problems might develop
later. You should be cautious.
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 Tivoli Storage Manager 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.
1101
-452 E
DSM_RC_SHM_NOTAUTH
-190 E
DSM_RC_NP_ERROR
Insufficient authority to connect to the shared

memory region
Session rejected: Named Pipes connection failure.
Explanation: The user issuing the command does not

have authority to connect to the shared memory
segment. When the shared memory segment is created
by the server, it will be owned by the effective uid of
the server process (dsmserv). Only processes running
under this uid or root will be allowed to connect to the
segment (and thus to the server).
System action: The session is rejected and processing
stops.
User response: Run the command under the uid of
the processing running dsmserv, if possible. Otherwise
contact your system administrator for further help.
-451 E
DSM_RC_SHM_FAILURE
An error occurred using the Shared Memory protocol
Explanation: An error has occurred while reading or
writing data through the Shared Memory
communications protocol.
operation.
continues, see your system administrator for further
help.

using Named Pipes communications failed. This might
have occurred if an incorrect NAMEDPIPENAME was
specified in the options files or if your system
administrator canceled a backup operation.
server comes back up and retry the operation. Ensure
that the value specified on the NAMEDPIPENAME
option is the same as the one used by the server. If the
problem continues, contact your system administrator
for further help.
-124 E
DSM_RC_3270COMM_MISSING_DLL
The TSM DLL dsm3270.dll cannot be found in the
users path.
Explanation: The TSM DLL dsm3270.dll cannot be
found in the user's path.
System action: Communications link is not
established.
User response: Make sure that the TSM DLL
dsm3270.dll is in a directory that is included in the
user's path.
-057 E
DSM_RC_TCPIP_LOADFAILURE
-450 E
DSM_RC_SHM_TCPIP_FAILURE
Session rejected: TCP/IP connection failure for Shared
Memory
Explanation: An attempt to connect to the local server
using the Shared Memory protocol has failed during
initial TCP/IP communications. This error can occur if
the server is not listening on the correct port, or if the
server is down.
further help.
The TCP/IP load function failed.

Explanation: An error occurred while locating a
function. The TCP/IP load function failed.
-056 E
DSM_RC_TCPIP_DLL_LOADFAILURE
An error occurred while loading a library.
library. The TCP/IP DLL load failed.
1102
-055 E
DSM_RC_WINSOCK_MISSING
The TCP/IP WINSOCK.DLL file cannot be found.
Explanation: The TCP/IP WINSOCK.DLL file cannot
be found.
Explanation: An attempt to establish a TCP/IP

connection was rejected by the server.
User response: The server was not fully initialized, is
not currently running, was not enabled for TCP/IP
communications, or an incorrect TCP/IP port number
was specified. If the problem continues, see your

-051 E
DSM_RC_CONN_TIMEDOUT
-054 E
DSM_RC_NETWORK_UNREACHABLE
The specified TCP/IP host name is unreachable
The attempt to establish a TCP/IP connection timed

out before the connection was made.
Explanation: None.
Explanation: The TCP/IP host name specified in the

TCPSERVERADDRESS statement cannot be reached.
User response:
User response: Check your options file for the correct

TCPSERVERADDRESS statement. See your
administrator for the correct name of the server.
-053 E
DSM_RC_BAD_HOST_NAME
An invalid TCP/IP address was specified.
Explanation: The TCP/IP address specified by the
TSM clients TCPSERVERADDRESS setting could not
be found on the network. Common reasons for this
error include:

v Check the client options file and verify that
TCPSERVERADDRESS and TCPPORT specify the
correct TCP/IP address and port number for your
TSM server.
v If the problem persists, see your TSM administrator
-050 E
DSM_RC_TCPIP_FAILURE
v The TCPSERVERADDRESS client option specifies the

wrong TCP/IP address for the TSM server.
Session rejected: TCP/IP connection failure
v The machine that hosts the TSM server is not on the

network.

using TCP/IP communications failed. This error can
occur if the LAN connection went down or if your
system administrator canceled a backup operation.
v A network problem is preventing the TSM client

from reaching the machine that hosts the TSM server.
User response: Verify that the TCPSERVERADDRESS
and TCPPORT settings have the correct values for your
TSM server. Use your operating systems ping (or
similar) utility to ensure that your machine can locate
the machine that hosts the TSM server across the
network. Try the operating again. If the problem
persists, ask your TSM administrator for further
assistance.

further help.
0000 I
DSM_RC_OK
Successfully done.
-052 E
DSM_RC_CONN_REFUSED
Explanation: The operation successfully completed.
An attempt to establish a TCP/IP connection was

rejected by the host
1103
0001 E
DSM_RC_ABORT_SYSTEM_ERROR
Server detected system error
Explanation: The server detected a system error and
notified the clients.
User response: See your system administrator for
further information on server activity.
0002 E
DSM_RC_ABORT_NO_MATCH
No objects on server match query
Explanation: No objects on the server match the query
operation being performed. If this object is part of a
backupset generated on a node, and the node name is
changed on the server, any backup set objects that were
generated prior to the name change will not match the
new node name.
User response: Ensure the names are properly
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
was generated.
version of the file, so the second process will issue this

message for that file.
System action: The object is not expired. Processing
continues with the next object.
User response:
v Review the console output, schedule log, or error log
and locate the ANS1228E message that immediately
precedes this message. ANS1228E will identify the
object that could not be expired.
v Examine the conditions under which the problem
occurred and assess whether those conditions explain
the occurrence of this message. For example, this
message could appear if multiple instances of the
client were attempting to back up the file system
concurrently.
v If the reason this message occurred can not be
determined and the message occurs when the
operation is tried again, then contact IBM support for
further assistance. Also try searching for this message
number on http://www.ibm.com for possible
solutions.
0005 E
DSM_RC_ABORT_NO_DATA
The TSM server has no data for the object.
Explanation: TSM tried to do a restore or retrieve on
an object that has no data associated with it. If a
corrective action is possible, it is with the TSM server.
0003 E
DSM_RC_ABORT_BY_CLIENT
Client ended transaction
Explanation: The client system ended the operation
with the server and ended the current transaction.
User response: Ask the TSM administrator to check

the TSM activity log for any messages related to this
error that might help identify the problem.
0006 E
DSM_RC_ABORT_BAD_VERIFIER
User response: Restart the session.
You entered an incorrect password.

Explanation: None.
0004 W
DSM_RC_ABORT_ACTIVE_NOT_FOUND
An active backup version could not be found.
Explanation: An attempt was made to expire an
object, but the TSM server was unable to find an active
backup version of the object. This message is preceded
by message ANS1228E which specifies the object name.
For instance, this message could be issued if two
separate client processes are backing up the same file
system at the same time. If one of the processes expires
a file, then the TSM server will make that file inactive.
If the second process subsequently attempts to expire
that same file, the TSM server will not find an active
1104

User response: Retry the session with the correct
password. If this fails or you have forgotten your
password, ask the TSM administrator to assign a new
password.
0007 E
DSM_RC_ABORT_NODE_IN_USE
Node in use
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: Retry the operation, or see your
system administrator to see what other operations are
running for your node.
0008 E
DSM_RC_ABORT_EXPDATE_TOO_LOW
Expiration date must be greater than todays date
Explanation: Archive expiration date is too low, the
date must be greater than todays date.
User response: You can take any of the following

actions:
v Request the system administrator to add space to the
storage pool.
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
during compression.
v For API Applications, consult the applications
documentation for recommendations regarding
compression.
v Turn off disk caching in the disk storage pool, and
issue MOVE DATA commands to each disk pool
volume to clear out the cached bitfiles.

User response: Retry archiving the file with an
expiration date that is higher than todays date.
0012 E
DSM_RC_ABORT_MOUNT_NOT_POSSIBLE
Server media mount not possible
0009 W
DSM_RC_ABORT_DATA_OFFLINE
The requested data is offline.
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
depends on your sites offline storage management
policies.
System action: TSM waits for offline storage media to
become available and then continues.
Explanation: Server media mount not possible. The

server timed out waiting for a mount of an offline
volume.
User response: Retry later when server volumes can
be mounted. Ensure that the MAXNUMMP (maximum
number of mount points) defined on the server for this
node is greater than 0.
0013 E
DSM_RC_ABORT_SIZESTIMATE_EXCEED
Size estimate exceeded
0010 E
DSM_RC_ABORT_EXCLUDED_BY_SIZE
Object too large for server limits
Explanation: The object is too large. The configuration
of the server does not have any data storage space that
accepts the object.
determine the maximum file (object) size for which
your sites server is configured.
0011 E
DSM_RC_ABORT_NO_REPOSIT_SPACE
Explanation: The total amount of data for a backup or

archive operation exceeds the estimated size originally
sent to the server for allocating data storage space. This
happens when many files are growing by large
amounts while the backup or archive operation is in
session.
continues, check what other processes are running on
the client machine that are generating large amounts of
data. Disable those operations while the backup or
archive operation is taking place.
0014 E
DSM_RC_ABORT_DATA_UNAVAILABLE

Explanation: The server does not have any space
File data currently unavailable on server

Explanation: The file data is currently unavailable on
the server. A retrieve or restore operation was
attempted. Possible causes are:
1105
v Data was corrupted at the server

v Server found a read error
v File is temporarily involved in a reclaim operation at
the server
v Server requested a tape volume that was marked
unavailable.
Explanation: The server ran out of memory.

User response: This is a temporary problem. Retry
later or see your system administrator.

continues, see your system administrator to determine
the problem from the server console or the activity log.
Check whether any requests were made for a tape
volume that was unavailable. A tape volume may be
marked unavailable if prior read errors were
encountered or the volume is checked out of the tape
library.
0015 E
DSM_RC_ABORT_RETRY
Unexpected retry request. The server found an error
while writing the data.
Explanation: None.
System action: The client retries the operation.
0016 E
DSM_RC_ABORT_NO_LOG_SPACE
0020 E
DSM_RC_ABORT_FS_NOT_DEFINED
The specified file space does not exist on the server.
The file space might have been deleted by another
client or an administrator.
Explanation: The specified file space does not exist on
the server. Your system administrator deleted the file
space or another client using your clients node name
deleted it.
User response: Check the file space name to see if it is
correct, and retry the operation.
0021 S
DSM_RC_ABORT_NODE_ALREADY_DEFED
Open Registration failed because the specified node
name is defined in the server
is defined in the server with the same name.
The server does not have enough recovery log space

to continue the current operation

0022 S
DSM_RC_ABORT_NO_DEFAULT_DOMAIN
Open Registration failed because no default domain
exists
0017 E
DSM_RC_ABORT_NO_DB_SPACE

default policy domain does not exist for you to place
your node.
The server does not have enough database space to

continue the current operation


0018 E
DSM_RC_ABORT_NO_MEMORY
The server does not have enough memory to continue
the current operation.
1106
0023 S
DSM_RC_ABORT_INVALID_NODENAME
Open Registration failed because an invalid node
name was specified
specified node name contains invalid characters.

0024 E
DSM_RC_ABORT_NO_INVALID_POL_BIND
An object in the transaction has been bound to an
invalid management class.
Explanation: One of the objects in the transaction is
bound to a management class that is not part of this
nodes policy, or the management class type is not
supported for this client level.

not have sufficient space to store the data, but the
space will be available soon. For example, a storage
pool migration might free up sufficient space to store
the data.
User response: Try the operation at a later time. If this
fails, contact the TSM administrator and request more
storage pool space.
0027 E
DSM_RC_ABORT_NOT_AUTHORIZED
System action: The current operation ends.

User response: Make sure all objects are bound to a
valid management class, or upgrade the client to the
proper level.
0024 S
DSM_RC_ABORT_INVALID_POL_BIND
The file space cannot be deleted because this node

does not have permission to delete archived or
backed up data.
Explanation: You cannot delete the file space data
unless your TSM administrator has authorized your
node to do so. Authorization permits you to delete
backup data, archive data, or both.
System action: Delete processing fails.
A policy management problem has occurred on the

TSM server.
Explanation: The TSM client error log and TSM server
activity log may contain additional information about
this error.

administrator to provide the necessary authorization or
to delete the file space for you.
System action: Processing is stops.

0028 E
DSM_RS_ABORT_RULE_ALREADY_DEFED
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
the specified node, which already has authorization
defined.
0025 E
DSM_RC_ABORT_DEST_NOT_DEFINED
System action: TSM did not redefine authorization for

the specified node.
Server problem: Destination not defined.
User response: Update the authorization, or delete the

old rule and define a new one, or use the current
authorization.
Explanation: Server problem: Destination not defined.

the error log.
0029 S
DSM_RC_ABORT_NO_STOR_SPACE_STOP
0026 S
DSM_RC_ABORT_WAIT_FOR_SPACE
The TSM server does not currently have space in the
storage pool for this file. This may be a temporary
condition.
Explanation: The server does not have space available

to store the object.

1107
0030 E
DSM_RC_ABORT_LICENSE_VIOLATION
0036 E
DSM_RC_END_NODE_NOT_AUTHORIZED
The operation is not permitted due to server licenses

values.
The node or user does not have proper authority to

perform this operation
Explanation: The node or user is trying to perform an

operation that either exceeds license values, or is not
licensed.
Explanation: The node or user does not have proper

authority to perform this operation.
System action: The session is rejected or the

transaction is cancelled, ending the current operation.
System action: The transaction is ended.

User response: Check the authority for the specified
object.
0032 E
DSM_RC_ABORT_DUPLICATE_OBJECT
A duplicate object was found, operation cannot
complete.
Explanation: A duplicate object was found, operation
cannot complete.
User response: Try the operation with a different file
specification.
0041 E
DSM_RC_ABORT_EXCEED_MAX_MP
This node has exceeded its maximum number of
mount points.
Explanation: Either no tape or sequential disk mount
points are permitted for this operation, or the
maximum number of mount points allowed are already
in use. The operation can not be completed. The TSM
administrator defines the maximum number of mount
points with the MAXNUMMP property of your node
definition.
System action: The object is skipped
0033 E
DSM_RC_ABORT_INVALID_OFFSET
partialObjOffset value for partial object retrieve is
invalid.
Explanation: The partialObjOffset value for partial
object retrieve is invalid.
procedure.
User response: If you are performing any other TSM

operations that might be using mount points, wait until
those operations are complete, then try the failed
operation again. Otherwise contact your TSM
administrator for further assistance
0045 E
DSM_RC_ABORT_MERGE_ERROR
The specified objects failed the merge test.
Explanation: The specified objects failed the merge
test, operation cannot complete.
0034 E
DSM_RC_ABORT_INVALID_LENGTH
partialObjLength value for partial object retrieve is
invalid.

User response: See documentation for the merge test
parameters.
Explanation: partialObjLength value for partial object

0047 E
DSM_RC_ABORT_INVALID_OPERATION

procedure.
An invalid operation was attempted on a node
Explanation: The operation is not valid.

more information.
1108
0048 E
DSM_RC_ABORT_STGPOOL_UNDEFINED
The specified target storage pool is not defined.
Explanation: The storage pool is not defined.

You are not allowed to connect to the server until the
password is updated.
User response: Update your password. You may use
the SET PASSWORD command, or have the TSM
administrator update your node.

more information.
0053 E
DSM_RC_REJECT_ID_UNKNOWN
Session rejected: Unknown or incorrect ID entered
0049 E
DSM_RC_ABORT_INVALID_DATA_FORMAT
A target storage pool does not have the correct data
format for the given node type.
Explanation: none
more information.
0050 E
DSM_RC_ABORT_DATAMOVER_UNDEFINED
No associated data mover is defined for the given
node.
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
to access a migrated file, your node name must be the
same node which migrated the file.
User response: Ensure that you entered your TSM
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
the server.
0054 E
DSM_RC_REJECT_DUPLICATE_ID
Explanation: none
more information.
Session rejected: Duplicate ID entered

Explanation: Another process using this node name is
active with the server.
System action: TSM cannot connect to the server. TSM
canceled the current operation.
0051 E
DSM_RC_REJECT_NO_RESOURCES
Session rejected: All server sessions are currently in
use
Explanation: TSM has all available sessions in use and
cannot accept a new one at this time.
number of concurrently active sessions to the server.
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
node name is unique to the server so that it cannot be
used by another person. See your system administrator
to identify the owner of that node name.
0055 E
DSM_RC_REJECT_SERVER_DISABLED
Session rejected: Server disabled
Explanation: The server is in a disabled state and
cannot be accessed for normal activity.
0052 E
DSM_RC_REJECT_VERIFIER_EXPIRED
The session is rejected. Your password has expired.
User response: Retry the operation after the server

returns to an enabled state. If the problem continues,
Explanation: Your TSM password has expired.
1109
0056 E
DSM_RC_REJECT_CLOSED_REGISTER
0061 E
DSM_RC_REJECT_ID_LOCKED
The server is not configured to allow open

registration
Session Rejected: The specified node name is

currently locked
Explanation: No authorization. Registration is

required by your system administrator. The server is
not configured to allow open registration.
Explanation: The node name you specified is currently

System action: Session not started.

User response: You must obtain a TSM node and
password from your system administrator.
0057 S
DSM_RC_REJECT_CLIENT_DOWNLEVEL

to find out why your node name is locked.
0062 S
DSM_RC_SIGNONREJECT_LICENSE_MAX
Session rejected: Downlevel client code version
SLM LICENSE EXCEEDED: The client licenses for

TSM are exceeded. See your system administrator.

version do not match. The client code is downlevel.

product license count for TSM.


0058 S
DSM_RC_REJECT_SERVER_DOWNLEVEL
0063 E
DSM_RC_REJECT_NO_MEMORY
Session rejected: Downlevel server code version
Session Rejected: The server does not have enough

memory to allow a connection to be established.

version do not match. The server code is downlevel.

with the server.
administrator.
0059 E
DSM_RC_REJECT_ID_IN_USE
Session Rejected: The specified node name is
currently in use
Explanation: The node name you specified is in use
on the server.
User response: The server is probably performing a
task that prevents your node from establishing a
session. Retry later or check with your system
administrator.
1110
0064 E
DSM_RC_REJECT_NO_DB_SPACE
database space to allow a connection to be
established.
0065 E
DSM_RC_REJECT_NO_LOG_SPACE
0068 E
DSM_RC_SESSION_CANCELED

recovery log space to allow a connection to be
established.
Session Rejected: The session was canceled by the


Explanation: The server administrator canceled the

current client session.
System action: Execution of the client connection
request ends.
0066 E
DSM_RC_REJECT_INTERNAL_ERROR
0073 E
DSM_RC_REJECT_INVALID_NODE_TYPE
The session is rejected. The TSM server has an

internal error.
An inconsistency was detected between the client

node and the node that is registered to the TSM
server.

to the TSM server because of an internal server error.
System action: The session was not started.
User response: Notify your TSM administrator of this
error.
0067 S
DSM_RC_SIGNONREJECT_INVALID_CLI
Session Rejected: The server is not licensed for this
platform type. See your system administrator.
Explanation: The server is not licensed for the
requesting client type.
0068 E
DSM_RC_CLIENT_NOT_ARCHRETPROT
The server does not allow a signon of a client that is
not archive-retention protection enabled.
to the server because the server is archive-retention
protection enabled and the client is not.
System action: The session is not started.
Explanation: The user has probably coded the node

option incorrectly. For instance, the node that is
registered to the TSM server might be a type of NAS,
but the node is actually a non-NAS client.
User response: Ensure that the node name is correct
in the client options file. Make sure to use a node of
type NAS only with the nasnodename option.
0074 E
DSM_RC_REJECT_INVALID_SESSIONINIT
Server does not allow client-initiated connections for
this node.
Explanation: The node is not allowed to initiate
connections due to the configuration parameters for
this node on the server. Server is able to initiate
connections to the client scheduler running in
prompted mode.
operation ends.
User response: Contact your systems administrator to
enable client-initiated sessions for your node or update
the SESSIONINITIATION option and run the client
scheduler.
0075 E
DSM_RC_REJECT_WRONG_PORT
Wrong server port.
Explanation: You were trying to open a
backup/archive client session on the server port set up
for administrative sessions only.
1111

operation ends.
User response: Contact your systems administrator
and/or use the correct values for TCP port and TCP
Admin Port.
0101 W
DSM_RC_USER_ABORT
The operation was stopped by the user.
Explanation: The operation was stopped at the request
of the user. This usually occurs when the Q key is
pressed two times.
0104 E
DSM_RC_FILE_NOT_FOUND
File not found during Backup, Archive or Migrate
processing
0105 E
DSM_RC_PATH_NOT_FOUND
The specified directory path could not be found.
0102 E
DSM_RC_NO_MEMORY
()The operating system refused a TSM request for
memory allocation.
to allocate.
operation.
For UNIX systems that support resource limits, you can
check if the memory resource limit is too low by
Explanation: An invalid or unreachable directory path

was specified.
directory path.
0106 E
DSM_RC_ACCESS_DENIED
Access to the specified file or directory is denied
the directory.
0106 E
DSM_RC_ACCESS_DENIED
The specified file is being used by another process
1112
0107 E
DSM_RC_NO_HANDLES
0111 E
DSM_RC_DISK_FULL
No file handles available
Processing stopped; Disk full condition




0108 E
DSM_RC_FILE_EXISTS
0113 E
DSM_RC_PROTOCOL_VIOLATION
Protocol violation
The file exists and cannot be overwritten.

Explanation: The file being restored or retrieved exists
and cannot be overwritten due to lack of authority or
access permissions.
User response: Verify that you have sufficient access
permissions to overwrite the file, then try the operation
again. If the problem persists, contact your system
administrator or TSM administrator for further
assistance.
0109 E
DSM_RC_INVALID_PARM
Invalid parameter was found.
Explanation: The system encountered an internal
program error due to an invalid parameter.
procedure.
User response: Ask your service representative to
Explanation: A communications protocol error

occurred. The communication subsystem is not
properly defined or is itself in error.
User response: Verify that the communication
processes are operating properly, and then retry the
operation.
0114 E
DSM_RC_UNKNOWN_ERROR
An unknown system error has occurred from which
TSM cannot recover.
be a low-level system or communication error from
which TSM cannot recover.
persists, review the TSM error log for any related
messages. Obtain a service trace that captures the
0110 E
DSM_RC_INVALID_HANDLE
An invalid file handle was passed; system error.
Explanation: An internal system error occurred: A file
operation failed because of an invalid file handle.
User response: Try the operation again. If the failure
persists, obtain a service trace that captures the
0115 E
DSM_RC_UNEXPECTED_ERROR
An unexpected error occurred.
Explanation: This is usually caused by a low-level
system error or communication error from which TSM
cannot recover.
additional messages that might be related to this
problem. Try the operation again. If the problem
1113
persists, contact TSM technical support for further

assistance.
0116 E
DSM_RC_FILE_BEING_EXECUTED
File is in use; Write permission denied.
operation.
0120 E
DSM_RC_FILE_SPACE_LOCKED
File system is locked by system
0121 I
DSM_RC_FINISHED
The operation is finished.
Explanation: The operation is finished.
0117 E
DSM_RC_DIR_NO_SPACE
No more files can be restored or retrieved since the
destination directory is full.
retrieved since the destination directory is full.

procedure.
User response: Proceed with next function call.
0122 E
DSM_RC_UNKNOWN_FORMAT

The file has an unknown format.

Explanation: TSM tried to restore or retrieve a file, but
it had an unknown format.
0118 E
DSM_RC_LOOPED_SYM_LINK
Too many symbolic links were detected while
resolving name
User response: The file was either backed up by

another application, or the data is invalid. If the file
belongs to this system, try the operation again. If the
further assistance.

0119 E
DSM_RC_FILE_NAME_TOO_LONG
The file name is too long and can not be processed by
TSM
0123 E
DSM_RC_NO_AUTHORIZATION
Not authorized to restore the other nodes data.
Explanation: The client is not authorized to restore the
other node's data.
procedure.
User response: Get authorization from the other node.
Explanation: None.
User response: See the client manual for the operating
system on which you are receiving this error. The File
specification syntax section of the manual explains file
name lengths supported by TSM.
1114
0124 E
DSM_RC_FILE_SPACE_NOT_FOUND
incorrect or does not exist on the machine.

0129 E
DSM_RC_NOT_COMPRESSED
File is not compressed; System failure.
0125 E
DSM_RC_TXN_ABORTED
Transaction aborted
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
problem.

0130 E
DSM_RC_TOO_MANY_BITS
File compressed on a different client machine that has
more memory
TSM cannot build a directory path because a file

exists with the same name as the directory.

Explanation: None

0126 E
DSM_RC_SUBDIR_AS_FILE
User response: Remove or rename the file that has the

same name as the directory. Alternatively, you can
restore the directory to a different location.
0131 S
DSM_RC_SYSTEM_ERROR
0127 E
DSM_RC_PROCESS_NO_SPACE
An internal program error occurred.
Disk space limit for this process reached
Explanation: TSM encountered an unexpected

condition and can not continue the operation. This
might be a programming error.

owner is full.
0128 E
DSM_RC_PATH_TOO_LONG
Destination directory path length exceeds system
maximum

persists, contact your TSM administrator or IBM
0131 E
DSM_RC_COMPRESSED_DATA_CORRUPTED
The compressed file is corrupted and cannot be
expanded correctly.
Server.
1115

Ethernet adapter on the Server please upgrade the card
0134 E
DSM_RC_NO_LEADING_DIRSEP
The objName field has no leading directory separator.
Explanation: The objName field does not have a
leading directory separator.
procedure.
0135 E
DSM_RC_WILDCARD_DIR
Wildcards are not allowed in the objName directory
path.
0132 E
DSM_RC_NO_SERVER_RESOURCES
The TSM server is out of resources.
Explanation: A lack of a storage resource or a
maximum value condition does not allow any new
activity.
Explanation: Wildcards are not allowed in the

procedure.

If the problem continues, contact your TSM
administrator to isolate what resource is unavailable.
The TSM administrator can check the TSM server
activity log for messages that might explain the
problem.
0133 E
DSM_RC_FS_NOT_KNOWN
The file space for domain domain-name could not be
found on the TSM server.
in progress.
0136 E
DSM_RC_COMM_PROTOCOL_ERROR
The session is rejected: There was a communications
protocol error.
Explanation: An unexpected network message was
received by the client. This could be caused by network
problems or a programming error.
0137 E
DSM_RC_AUTH_FAILURE
Session rejected: Authentication failure

further assistance.
Explanation: Authentication failure. You entered an

incorrect password.
1116

User response: Enter your correct password. If you
cannot remember the correct password, see your
system administrator to have a new one assigned for
your node name.
0138 E
DSM_RC_TA_NOT_VALID
0147 S
DSM_RC_UNCLOSED
The trusted agent execution/owner permissions are

invalid.
There is no closing bracket in the pattern.
Explanation: The trusted agent execution/owner

Explanation: There is no closing bracket in the

pattern. This is a programming failure and the client
program ends.

the trusted agent permissions are set correctly.

0139 S
DSM_RC_KILLED
0148 S
DSM_RC_NO_STARTING_DELIMITER
Process killed.
Include/Exclude pattern must start with a directory

delimiter
Explanation: Processing stopped. This is a

Explanation: The include or exclude pattern must start


0145 S
DSM_RC_WOULD_BLOCK
Trusted agent would block the operation.
Explanation: The trusted agent blocks the operation.
This is a programming failure and the client program
ends.
0149 S
DSM_RC_NEEDED_DIR_DELIMITER
Include/Exclude pattern has a ... without
beginning/ending directory delimiter
Explanation: The include/exclude pattern has a ...
without a beginning or ending directory delimiter.

0150 S
DSM_RC_UNKNOWN_FILE_DATA_TYPE
0146 S
DSM_RC_TOO_SMALL
The area for the include/exclude pattern is too small.
Explanation: The area for the include/exclude pattern
is too small. This is a programming failure and the
client program ends.
The structured file data type is unknown.

Explanation: An unknown and unexpected error code
occurred within the client program. The structured file
data type is unknown. This is a programming failure
and the client program ends.
0151 S
DSM_RC_BUFFER_OVERFLOW
The data buffer overflowed.
1117
Explanation: The data buffer overflowed. This is a

Explanation: The server encountered an error and will

abort the transaction.
System action: The transaction will be aborted. The

reason code is passed on the dsmEndTxn call.

0154 E
DSM_RC_NO_COMPRESS_MEMORY
User response: Issue the dsmEndTxn with a vote of

DSM_VOTE_COMMIT and examine the reason code.
0158 E
DSM_RC_FS_WRITE_LOCKED
Insufficient memory for file compression/expansion

Explanation: Not enough memory is available to do
data compression or expansion. For a restore or
retrieve, the file cannot be recalled from the server until
more storage is made available. For a backup or
archive, try running without compression if storage
cannot be made available.
Destination file or directory is write locked

updated.
User response: Free up extra storage for the operation

to continue, or run the backup or archive process
without compression enabled.

or location.
0155 T
DSM_RC_COMPRESS_GREW
0159 I
DSM_RC_SKIPPED_BY_USER
Compressed Data Grew
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.
Explanation: The size of the file after compression is

greater than the size of the file before compressed.
System action: Even though the size of the file
increased, the file is compressed.
0156 E
DSM_RC_INV_COMM_METHOD
An unsupported communications method was
specified.
Explanation: None.
User response: Specify a communications interface
that is supported by the TSM client on your operating
system. See the TSM client manual for your operating
system for further information on configuring TSM
client communications.
0157 S
DSM_RC_WILL_ABORT
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: Verify the application sets the
mountWait value correctly on dsmBeginGetData.
0160 E
DSM_RC_TA_NOT_FOUND
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.
User response: Make sure the Trusted Agent module
is in the directory specified by DSMI_DIR.
0161 E
DSM_RC_TA_ACCESS_DENIED
The transaction will be aborted.

Access denied for dsmapitca.
1118
Explanation: An attempt to access a system function

has been denied.
0167 E
DSM_RC_CANNOT_MAKE
Cannot make file/directory
0162 E
DSM_RC_FS_NOT_READY
File system/drive not ready
access.

restored or retrieved. Make sure that you have write
access.

0168 E
DSM_RC_NO_PASS_FILE
Password file is not available.
0164 E
DSM_RC_FIO_ERROR

for the specified server-name is unavailable.
File input/output error

User response: The root user must set and store a new
password.
System action: File or file system is skipped.

0165 E
DSM_RC_WRITE_FAILURE
File write error
file.
0169 E
DSM_RC_VERFILE_OLD
PASSWORDACCESS is GENERATE, but password
needed for server server-name. Either the password is
not stored locally, or it was changed at the server.
Explanation: Either the password is not stored locally,
or it was changed at the server.
System action: TSM prompts you for the password if
TSM is running in the foreground.

operating properly.
User response: If TSM was running as a background

process, issue any TSM command from the foreground.
Enter the password in answer to the prompt. Then try
your background TSM command again.
0166 E
DSM_RC_OVER_FILE_SIZE_LIMIT
0173 E
DSM_RC_INPUT_ERROR
File exceeds system/user file limits
The process is running in a non-interactive mode, but

requires user input.
Explanation: A file being restored or retrieved exceeds

system set limits for this user.
properly.
Explanation: This process requires keyboard input,

but non-interactive processes are unable to read input
from keyboard.
User response: Perform the following actions to
resolve this error:
v Run the product in interactive mode.
1119
v Ensure your password is set correctly.

0185 W
DSM_RC_TL_EXCLUDED
0174 E
DSM_RC_REJECT_PLATFORM_MISMATCH
Session rejected: Node type mismatch
Explanation: Your node name is associated with a
different type of operating system (such as OS/2 or
AIX) and cannot be used on this system.
User response: If you need a new node name, see
your system administrator to assign a new one to you.
Generally, you have a unique node name for each
machine and operating system pair that requires access
to the server.
File file-name file-namefile-name excluded by

Include/Exclude list
Explanation: You can not back up, archive, or migrate
files that are excluded.
System action: TSM does not process the file.
User response: If the file is intentionally excluded,
then this message can be ignored. Otherwise modify
the include/exclude list, restart the client, and try the
operation again. Contact your TSM administrator for
further assistance.
0186 E
DSM_RC_TL_NOACG
0175 E
DSM_RC_TL_NOT_FILE_OWNER
Not file owner
Explanation: The file cannot be backed up because the
client is not the file owner.
The management class for this file does not have a

valid archive copy group. This file will not be
archived.
not have an archive copy group specified. This file will
not be archived.
User response: Add a valid archive copy group to the
0177 S
DSM_RC_UNMATCHED_QUOTE
Quotes are not matched
0187 E
DSM_RC_PS_INVALID_ARCHMC

Invalid management class entered
Explanation: You entered an invalid management

class.
User response: Correct the pattern by using matching


operation.
0184 E
DSM_RC_TL_NOBCG
The management class for this file does not have a
valid backup copy group. This file will not be backed
up.
not have a backup copy group specified. This file will
not be backed up.
User response: Add a valid backup copy group to the
User response: Retry the operation using a valid

management class.
0188 S
DSM_RC_NO_PS_DATA
Either the node does not exist on the server or there is
no active policy set for the node.
Explanation: This error occurs when you try to access
another nodes data. Either the node is not registered
with the TSM server, or there is no active policy set for
the node.
User response: Verify that the node whose data you
1120
are trying to access is registered with the TSM server. If

you have more than one TSM server, make sure you
are connecting to the correct server, then try the

more information.
0189 S
DSM_RC_PS_INVALID_DIRMC
An Operation for the requested node and filespace is

already in progress.
The management class assigned to directories does

not exist.
0232 E
DSM_RC_ABORT_ITEM_IN_USE

mover to perform an operation for the indicated node
and filespace. Since an operation for this node and
filespace is already in progress, the new operation
cannot be performed.
0233 E
DSM_RC_ABORT_LOCK_CONFLICT
System resource in use
Explanation: A required resource is in use by another
command or process.
0190 S
DSM_RC_PS_NO_CG_IN_DIR_MC
There is no backup copy group in the management
class used for directories.
0234 E
DSM_RC_ABORT_SRV_PLUGIN_COMM_ERROR
Server plugin communication error
Explanation: Communication between a server plugin
module and a NAS filer failed.
more information.
0235 E
DSM_RC_ABORT_SRV_PLUGIN_OS_ERROR
Server plugin detected unsupported NAS filer
operating system.
0231 E
DSM_RC_ABORT_MOVER_TYPE
Explanation: A plugin module detected that a NAS

filer is running an unsupported operating system or
operating system level.
Unknown Remote Mover type
Explanation: The specified Remote Mover type is

unknown.

more information.
1121
0236 E
DSM_RC_ABORT_CRC_FAILED
0240 E
DSM_RC_ABORT_DATAMOVER_NOT_AVAILABLE
The CRC received from the Server does not match the
CRC calculated by the client.
Data mover is not available.
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
failure.
Explanation: Data mover is not available.

User response: Retry operation with a proper Data
mover.
System action: In some cases, the client can indicate

the failure to the server and retry the operation.
0237 E
DSM_RC_ABORT_INVALID_GROUP_ACTION
0241 E
DSM_RC_ABORT_STGPOOL_COPY_CONT_NO
Operation failed because the copy continue option
was set to NO.
Explanation: Operation failed because the copy
An invalid operation was attempted on a group leader

or group member.
Explanation: An invalid operation was attempted on a
logical group.
User response: This abort code indicates that a store

operation, like backup or archive failed because the
copy continue option was set to NO. The sysadmin will
need to resolve the problem on the server end.

User response: Retry a valid operation.
0242 E
DSM_RC_ABORT_RETRY_SINGLE_TXN
0238 E
DSM_RC_ABORT_DISK_UNDEFINED
Transaction failed because of a problem during a

store operation.
Remote disk not defined.

Explanation: An operation was attempted on a remote
disk that is not defined.
User response: Define the proper remote disk.
Explanation: Transaction failed because of a problem

during a store operation. This error is typical when the
next storage pool has a different copy storage pool list
and we switch to this pool in the middle of a
transaction.
System action: Transaction is aborted.
User response: Resend objects in separate transactions.
0239 E
DSM_RC_ABORT_BAD_DESTINATION
Input destination does not match expected
destination.
Explanation: Input destination does not match
User response: Retry operation with proper
destination.
1122
0245 E
DSM_RC_ABORT_PATH_RESTRICTED
The current client configuration does not comply with
the value of the DATAWRITEPATH or
DATAREADPATH server option for this node.
Explanation: The values of the DATAWRITEPATH
and DATAREADPATH server options specify where the
client is allowed to send data, and where data is read
from. The values for the specified node name should
correspond with the client configuration. For example,
you will get this error message if DATAWRITEPATH
contains a LAN value and the client is configured to
use LAN-free protocol, or vice versa.

User response: Check the client, server, and storage
agent logs to determine why the client was not able to
send data LAN-free. Make sure the client configuration
and server options are compatible.
0247 E
DSM_RC_ABORT_INSERT_NOT_ALLOWED
This server does not support backup operations.
Explanation: This server only supports archive
operations, backup is not allowed.
User response: Use only archive operations with this
server.
0248 E
DSM_RC_ABORT_DELETE_NOT_ALLOWED
Deleting this object: fshlll is not allowed.
Explanation: The object is either under a hold and
cannot be deleted, or it is on a retention-protection
enabled server and has not expired.
System action: The object is skipped and processing
continues.
User response: Check the status of the object through
a query to see if it is held, or when it expires.
User response: Issue a query to see the status of the

objects, and try the operation again, without the object
that is already held.
0292 E
DSM_RC_TCA_FORK_FAILED
Error starting the Trusted Communication Agent
process.
Explanation: An error has occurred starting the
Trusted Communication Agent process; specifically, the
fork() function has failed.
0295 E
DSM_RC_TCA_INVALID_REQUEST
The TSM Trusted Communication Agent received an
invalid request.
Explanation: The Trusted Communication Agent is
invoked by the TSM client and has received an
unknown request argument in the call.
User response: It is possible the Trusted
Communication Agent was mistakenly invoked by a
process other than the TSM client. If that is not the
case, then this is an internal error. If the problem
recurs, contact your IBM service representative.
0249 E
DSM_RC_ABORT_TXN_LIMIT_EXCEEDED
The number of objects in this transaction exceed
TXNGROUPMAX values.
0296 E
DSM_RC_TCA_NOT_ROOT
Explanation: There are too many objects in this

transaction.
This action requires TSM administrative authority on

this system.

User response: Try the operation again with fewer

objects in the transaction, or increase the
TXNGROUPMAX value on the server.

User response: If the activity is required, the
0250 E
DSM_RC_ABORT_OBJECT_ALREADY_HELD
fshlll is already under hold.
0297 E
DSM_RC_TCA_SEMGET_ERROR
Explanation: One of the objects in the transaction The

specified object is already under hold, and it cannot be
placed under a new hold.
Error allocating semaphores.
System action: Current operation ends. This object is

skipped and processing continues.
Explanation: An error has occurred because the

semaphores you are attempting to allocate have become
insufficient.
1123

User response: Ask your system administrator for
assistance, and possibly increase the number of
semaphores in your system.
0298 E
DSM_RC_TCA_SEM_OP_ERROR
Error setting semaphore value or waiting on
semaphore.
Explanation: An error has occurred while attempting
to set or wait on a semaphore.
v You specified the -OPTFILE option when starting the

TSM client, but the options file you provided does
not exist.
v The DSM_CONFIG (or DSMI_CONFIG if you are
using the TSM API) environment variable specifies
an options file that does not exist.
System action: TSM client processing stops.
User response: Make sure that the options file you
want to use exists. Review the information on
configuring TSM in the TSM client manual specific to
your operating system. If the problem persists, ask
your TSM administrator for further assistance.
0408 E
DSM_RC_MACHINE_SAME
A virtual node name must not equal either a node
name or the system host name.
0400 E
DSM_RC_INVALID_OPT
An invalid option was found during option parsing.
Explanation: An invalid option was found.
procedure.
User response: Verify the options in dsm.opt, 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).
0405 E
DSM_RC_NO_HOST_ADDR
TCPSERVERADDRESS not defined for this server in
the System Options File
Explanation: The TCPSERVERADDRESS for this
server is not defined in the server name stanza in the
program ends.
system, and make sure that the server to which you are
trying to connect, has a valid TCPSERVERADDRESS
defined in the system options file.
Explanation: A VIRTUALNODENAME option was

entered with a name the same as either a NODENAME
option or the system host name.
System action: Initialization fails and the program
ends.
User response: If the virtual node name entered was
the same as the host name, remove the virtual node
name option. If it was the same as the node name
option, you can remove either one, depending upon the
intended usage. Node name is used to assign an
alternate name to your system. Virtual node name is
used to access another systems server data.
0409 E
DSM_RC_INVALID_SERVER
Server name not found in System Options File
Explanation: The system options file does not contain
the SERVERNAME option.
program ends.
system, and make sure that the system options file
contains the server name.
0410 E
DSM_RC_INVALID_KEYWORD
0406 S
DSM_RC_NO_OPT_FILE
Options file file-name could not be found.
Explanation: Common reasons for this error include:
v The default options file does not exist.
1124
An invalid option keyword was found during option

parsing.
Explanation: An invalid option keyword was found in
the dsmInit configuration file, the option string,
dsm.sys, or dsm.opt.

procedure.
User response: Correct the spelling of the option
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.
Explanation: The Error Log file could not be opened

during initialization. The specified path may be
not have permission to write to the logfile in the
available at the given logfile location.
0411 S
DSM_RC_PATTERN_TOO_COMPLEX
User response: Make sure the logfile option points to

a valid path and that the user has proper permissions
to write to the file specified.
The include or exclude pattern cannot be parsed.

Explanation: The pattern is formatted incorrectly or is
too complex for TSM to interpret.
User response: Verify that the include or exclude
pattern is specified correctly. If the pattern is correct,
then contact IBM technical support for further
assistance.
0412 S
DSM_RC_NO_CLOSING_BRACKET
Include/Exclude pattern is missing a closing bracket
Explanation: The include or exclude pattern is
incorrectly constructed. The closing bracket is missing.
0600 E
DSM_RC_DUP_LABEL
A duplicate volume label exists. The operation cannot
continue.
Explanation: For removable media, TSM uses the
volume label as the file space name. To prevent data
from different volumes being stored in the same file
space on the TSM server, backup or archive of
removable media volumes having duplicate volume
labels is not allowed.
User response: Change the volume labels on the
removable media volumes so that there are no
duplicate labels. Then restart TSM and try the
operation again.

0426 E
DSM_RC_CANNOT_OPEN_TRACEFILE
Initialization functions cannot open the trace file
specified.
Explanation: The file tracefile-name could not be
opened during initialization. The specified path may be
not have permission to write to the tracefile in the
available at the given tracefile location.
0601 E
DSM_RC_NO_LABEL
The drive has no label. The operation cannot
continue.
Explanation: Backup or archive of removable media
requires that the media have a volume label. An
attempt was made to back up or archive data on a
removable volume that has no label.
User response: Create a volume label on the
removable media, then try the operation again.

User response: Make sure the tracefile option points
to a valid path and that the user has proper
permissions to write to the file specified.
0610 E
DSM_RC_NLS_CANT_OPEN_TXT
Unable to open message text file.
0427 E
DSM_RC_CANNOT_OPEN_LOGFILE
Initialization functions cannot open the Error Log file
specified.
Explanation: The system is unable to open the

message txt file (dscenu.txt or dsmclientV3.cat for AIX).
On the AS/400 platform this file is
QANSAPI/QAANSENU(TXT).
procedure.
1125
User response: Verify that the dscenu.txt file is in the

directory pointed to by DSMI_DIR. For AIX, verify that
the dsmclientV3.cat file has a symbolic link to
/usr/lib/nls/msg/<locale>/dsmclientV3.cat .
0615 E
DSM_RC_NLS_INVALID_NUM_FMT
Invalid value for NUMBERFORMAT specified.
0611 E
DSM_RC_NLS_CANT_READ_HDR
text file (dscenu.txt or dsmclientV3.cat for AIX) because
of an invalid header. On the AS/400 platform this file
is QANSAPI/QAANSENU(TXT).
procedure.

NUMBERFORMAT.
procedure.
0620 E
DSM_RC_LOG_CANT_BE_OPENED
Unable to open error log file.
log file.
0612 E
DSM_RC_NLS_INVALID_CNTL_REC
txt file (dscenu.txt or dsmclientV3.cat for AIX) because
of an invalid control record. On the AS/400 platform
this file is QANSAPI/QAANSENU(TXT).

procedure.
options file.

procedure.
0621 E
DSM_RC_LOG_ERROR_WRITING_TO_LOG
The log file cannot be written to.
0613 E
DSM_RC_NLS_INVALID_DATE_FMT
Invalid value for DATEFORMAT specified.
DATEFORMAT.
procedure.
Explanation: There was an error writing to the log

file.
procedure.
access permission. on the AS/400 platform, verify the
options file.
0622 E
DSM_RC_LOG_NOT_SPECIFIED
0614 E
DSM_RC_NLS_INVALID_TIME_FMT
The log file name was not specified.
Invalid value for TIMEFORMAT specified.

TIMEFORMAT.
procedure.
1126

log file.
procedure.
options file.
0927 E
DSM_RC_NOT_ADSM_AUTHORIZED
Only a TSM authorized user can perform this Action.
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
be the owner of the executable and the set effective
user id bit is set to on (s bit).

current TSM Server.
User response: Upgrade your TSM Server to a level
that supports this function. See error log for version
information.
0997 E
DSM_RC_STORAGEAGENT_DOWNLEVEL
The TSM Storage Agent is downlevel and does not
support the requested function. See error log for
961 E
DSM_RC_DIRECT_STORAGE_AGENT
_UNSUPPORTED

current TSM Storage Agent.
Direct connection to the Storage Agent is not allowed.
User response: Upgrade your TSM Storage Agent to a

level that supports this function. See error log for
Explanation: You cannot connect directly to the

Storage Agent.

User response: To perform Lanfree operations using
the Storage Agent, specify the ENABLELANFREE
option in your options file, and restart the process.
963 E
DSM_RC_FS_NAMESPACE_DOWNLEVEL
The long namespace has been removed from the local
filespace. If you wish to proceed with the
backup/archive operation, rename your filespace on
the server.
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
up the volume using the short names, rename the
filespace on the server. If you would like to back up
using long names, add the long namespace support
back to the volume in question.
0998 E
DSM_RC_SERVER_AND_SA_DOWNLEVEL
The TSM Server and TSM Storage agent are
downlevel and do not support the requested function.
See error log for version information.
current TSM Server and TSM Storage agent
User response: Upgrade your TSM Server and TSM
Storage agent to a level that supports this function. See
2000 E
DSM_RC_NULL_OBJNAME
The object name pointer is NULL.

name pointer.
User response: Add the long namespace support to

the volume or rename(remove) the corresponding
server filespace.

procedure.
User response: Provide an address for the
dsmObjName structure.
0996 E
DSM_RC_SERVER_DOWNLEVEL_FUNC
The TSM server is downlevel and does not support
the requested function. See error log for version
information.
2001 E
DSM_RC_NULL_DATABLKPTR
The data block pointer is NULL.
1127
Explanation: There is no value provided for the data

block pointer.
procedure.
User response: Provide an address for the DataBlk
structure.
2002 E
DSM_RC_NULL_MSG
msg parameter for dsmRCMsg is a NULL pointer.
Explanation: The message parameter for dsmRCMsg
is a NULL pointer.
procedure.
User response: Allocate enough space for the message
parameter.
2004 E
DSM_RC_NULL_OBJATTRPTR
2008 E
DSM_RC_ZERO_BUFLEN
The dataBlk bufferLen value is zero.
Explanation: The value for the dataBlk bufferLen is
zero.
procedure.
User response: Provide a non-zero value for the
bufferLen.
2009 E
DSM_RC_NULL_BUFPTR
The dataBlk bufferPtr is NULL.
dataBlk bufferPtr.
procedure.
User response: Provide an address for the bufferPtr.
The object attribute pointer is NULL.

attribute pointer.
2010 E
DSM_RC_INVALID_OBJTYPE

procedure.
The objType is invalid.
User response: Provide an address for the ObjAttr

structure.
2006 E
DSM_RC_NO_SESS_BLK
There is no server session information.
session information.
procedure.
User response: Verify the server status.
Explanation: The value for the objType is invalid.

procedure.
User response: The value for dsmObjName.objType
must be:
DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for
Backup, or
DSM_OBJ_FILE for Archive.
2011 E
DSM_RC_INVALID_VOTE
The dsmEndTxn vote is invalid.
Explanation: The dsmEndTxn vote is invalid.
2007 E
DSM_RC_NO_POLICY_BLK
There is no server policy information.
policy information.
procedure.
User response: Verify the server policy definitions.
1128

procedure.
User response: The vote must be
DSM_VOTE_COMMIT or DSM_VOTE_ABORT.
2012 E
DSM_RC_INVALID_ACTION
The update action is invalid.
Explanation: The dsmUpdateFS or dsmUpdateObj
action is invalid.
procedure.
User response: Correct the action value. Valid values
are defined in dsmapitd.h and documented in our
Using the API book.
2014 E
DSM_RC_INVALID_DS_HANDLE
There was an error in the TSM API internals.
Explanation: The system encountered an error in the
API internals.
procedure.
User response: Shut down the process and retry the
operation. Verify that any previous dsmInit calls were
cleaned up and terminated by a dsmTerminate call. If
the problem continues, contact your system
administrator or service representative.
2015 E
DSM_RC_INVALID_REPOS
User response: Filespace name should start with the

2017 E
DSM_RC_INVALID_OBJNAME
The object name is either an empty string or has no
leading delimiter.
Explanation: The object name is invalid because of an
empty string or there is no leading delimiter.
procedure.
User response: Verify the format of the dsmObjName
full path.
2018 E
DSM_RC_INVALID_LLNAME
Low level qualifier of the object name should start
with the directory delimiter.
Explanation: The low level qualifier for the object
name is invalid.
procedure.
User response: Start the low level qualifier of the
object name with the directory delimiter.
2019 E
DSM_RC_INVALID_OBJOWNER
The repository type is invalid.

Explanation: The repository type is invalid.
procedure.
User response: For dsmDeleteFS the repository must
be one of the following:
v DSM_ARCHIVE_REP
v DSM_BACKUP_REP
v DSM_REPOS_ALL.
2016 E
DSM_RC_INVALID_FSNAME
Filespace name should start with the directory
delimiter.
Explanation: The filespace name is invalid.
procedure.
The object owner is invalid.

Explanation: The object owner must be either the root
user, or the object owner must be the same as the
session owner.
procedure.
User response: Verify the session owner and object
owner.
2020 E
DSM_RC_INVALID_ACTYPE
The dsmBindMC sendType is invalid.
Explanation: The dsmBindMC sendType is invalid.
procedure.
following:
1129
stBackup
stArchive
User response: The qryBackupData.objState must be

one of the following:
stBackupMountWait
DSM_ACTIVE
stArchiveMountWait
DSM_INACTIVE
DSM_ANY_MATCH
2021 E
DSM_RC_INVALID_RETCODE
2025 E
DSM_RC_INVALID_MCNAME
no text available for this return code.

Explanation: The dsmRC parameter for dsmRCMsg is
an unsupported return code.
procedure.
The management class name was not found.

Explanation: A query or send operation is unable to
find the management class name.
procedure.
User response: Verify the management class name.
2022 E
DSM_RC_INVALID_SENDTYPE
2026 E
DSM_RC_INVALID_DRIVE_CHAR
The dsmSendObj sendType is invalid.

Explanation: The dsmSendObj sendType is invalid.
procedure.
following:
stBackup
stArchive
stBackupMountWait
The drive letter is not an alphabetic character.

Explanation: The drive letter is not an alphabetic
character. This return code is valid on Microsoft
Windows only.
procedure.
User response: Verify that the drive designation is an
alphabetic character. The referenced field is
dsmDosFSAttrib.driveLetter.
stArchiveMountWait
2023 E
DSM_RC_INVALID_PARAMETER
2027 E
DSM_RC_NULL_FSNAME
The Register Filespace name is NULL.
The dsmDeleteObj delType is invalid.

Explanation: The dsmDeleteObj delType is invalid.

Register Filespace name.

procedure.

procedure.
User response: The delType must be dtBackup or

dtArchive.
User response: Provide a filespace name on

dsmRegisterFS.
2024 E
DSM_RC_INVALID_OBJSTATE
2028 E
DSM_RC_INVALID_HLNAME
The query Backup objState is invalid.
High level qualifier of the object name should start

with the directory delimiter.
Explanation: The query Backup objState is invalid.

procedure.
1130
Explanation: The high level qualifier for the object

name is invalid.

procedure.
User response: High level qualifier of the object name
2029 E
DSM_RC_NUMOBJ_EXCEED
The number of objects on dsmBeginGetData exceeds
DSM_MAX_GET_OBJ |
Explanation: The number of objects (numObjId)
specified on the dsmBeginGetData call exceeds
DSM_MAX_GET_OBJ |
procedure.
Explanation: PASSWORDACCESS=GENERATE
establishes a session with the current login user as the
owner. The application should set clientOwnerNameP
to NULL when PASSWORDACCESS=GENERATE is in
effect.
procedure. Whether the application can continue
processing depends on how the application handles the
error.
User response: This message applies to applications
that utilize the TSM API, and is intended primarily for
the vendor of the application for which the message is
issued. Depending on the application, this could be a
configuration issue.
Consult the documentation for the application and
verify that the application is configured correctly. If the
problem persists, contact the application vendor for
further assistance.
User response: Check the number of objects before

calling dsmBeginGetData. If it is greater than
DSM_MAX_GET_OBJ |
DSM_MAX_PARTIAL_GET_OBJ, then issue multiple
Get call sequences.
2033 E
DSM_RC_NO_NODE_REQD
2030 E
DSM_RC_NEWPW_REQD
Explanation: PASSWORDACCESS=generate
establishes a session with the current hostname as the
node.
The new password value is NULL or blank.

procedure.
Explanation: There is no value provided for new

password.
procedure.
User response: Provide a new password on
dsmChangePW.
2031 E
DSM_RC_OLDPW_REQD
The old password value is NULL or blank.
Explanation: There is no value provided for old
password.
procedure.
On dsmInit, the node is not allowed when

PASSWORDACCESS=generate.
User response: When using

PASSWORDACCESS=generate, set clientNodeNameP to
NULL.
2034 E
DSM_RC_KEY_MISSING
The key file is missing.
Explanation: The key file for IBM Tivoli Storage
Manager for Data Retention application client for
Oracle cannot be found.
procedure.
User response: Provide an old password on

dsmChangePW.

client which contains TDP for Oracle, and install the
key file.
2032 E
DSM_RC_NO_OWNER_REQD
2035 E
DSM_RC_KEY_BAD
On dsmInit, the owner is not allowed to establish a

session when PASSWORDACCESS=generate.
The key file content is invalid.
1131
Explanation: The key file content for IBM Tivoli

Storage Manager for Data Retention application client
for Oracle is invalid.
procedure.
client which contains the TDP for Oracle, and install
the key file.
2041 E
DSM_RC_BAD_CALL_SEQUENCE
The sequence of calls is invalid.
Explanation: The sequence of calls is invalid.
procedure.
User response: Verify the transaction call sequence.
2042 E
DSM_RC_INVALID_TSMBUFFER
The tsmBuffHandle is invalid, or the value of dataPtr
is invalid.
Explanation: An invalid value for a handle or dataPtr
has been passed into the API.
procedure.
application. Verify the values of the tsmBuffHandle and
dataptr passed to the API.
2043 E
DSM_RC_TOO_MANY_BYTES
The number of bytes copied into the tsmBuffer is
larger than the allowed value.
Explanation: An invalid number of bytes was copied
to a tsmBuffer.
procedure.
application. Verify the number of bytes copied into the
tsmBuffer.
2044 E
DSM_RC_MUST_RELEASE_BUFFER
1132
dsmTerminate cannot finish because the application is

holding on to 1 or more tsmBuffers.
Explanation: An application is trying to terminate a
session, but is still holding some tsmBuffers.
procedure.
User response: The application must return all buffers
for this session by calling tsmReleaseBuffer, and then
issue dsmTerminate.
2045 E
DSM_RC_BUFF_ARRAY_ERROR
An internal error occurred in the tsmBuffer array.
Explanation: An internal API buffer array error
occurred.
procedure.
representative.
2046 E
DSM_RC_INVALID_DATABLK
When using useTsmBuffers, dataBlk must be NULL
in calls to dsmSendObj and dsmGetObj.
Explanation: The value for dataBlk must be NULL
when using useTsmBuffers.
procedure.
application. Contact your application provider
2047 E
DSM_RC_ENCR_NOT_ALLOWED
Encryption is not allowed when using useTsmBuffers.
encryption.
procedure.
useTsmBuffers, or disable encryption for this operation.
2048 E
DSM_RC_OBJ_COMPRESSED
2052 E
DSM_RC_NO_ENCRYPTION_KEY
This object cannot be restored/retrieved using

useTsmBuffers, because it is compressed.
No encryption key was found. If you are using

-encryptkey=prompt make sure there is a value in the
encryptionPasswordP field and that
bEncryptKeyEnabled is set to true.

compression.
procedure.
useTsmBuffers.
2049 E
DSM_RC_OBJ_ENCRYPTED
This object cannot be restored/retrieved using
useTsmBuffers, because it is encrypted.
encryption.
procedure.
useTsmBuffers.
2050 E
DSM_RC_WILDCHAR_NOTALLOWED
On dsmSendObj, wildcards are not allowed for the
objName.
Explanation: There was no encryption key found in

the password file, or no key was provided by the
application.
procedure.
User response: If you are using -encryptkey=prompt,
make sure there is a value in encryptionPasswordP and
that bEncryptKeyEnabled is set to true.
2053 E
DSM_RC_ENCR_CONFLICT
Conflicting encryption key options have been
specified.
Explanation: When using the ENABLEENCRYPTKEY
option, the parameter bEncryptKeyEnabled for the TSM
API dsmInitExIn_t and tsmInitExIn_t structures cannot
be set to bTrue.
procedure.
User response: Either remove the
ENABLEENCRYPTKEY option from the options file, or
set the parameter bEncryptKeyEnabled to bFalse in the
program using the TSM API.
Explanation: On dsmSendObj, wildcards are not

procedure.
2060 E
DSM_RC_FSNAME_NOTFOUND
User response: Provide a fs, hl, and ll on the

dsmObjName.
The filespace to delete/set access cannot be found.

Explanation: The filespace to delete cannot be found.
2051 E
DSM_RC_POR_NOT_ALLOWED

procedure.
When using useTsmBuffers, a restore/retrieve with

partial object restore is not allowed.
Explanation: useTsmBuffers does not support partial
object restore.
2061 E
DSM_RC_FS_NOT_REGISTERED

procedure.
On dsmSendObj, dsmDeleteObj, or dsmUpdateFS the

filespace is not registered.
User response: Make sure the calling application is

either using Partial object restore or useTsmBuffers.
Explanation: On dsmSendObj, dsmDeleteObj, or

dsmUpdateFS, the filespace is not registered.
1133

procedure.
2062 W
DSM_RC_FS_ALREADY_REGED
On dsmRegisterFS the filespace is already registered.
Explanation: On dsmRegisterFS the filespace is
already registered.
procedure.
User response: Ensure that the stVersion field is set

with the value in the header file. Recompile the
application with the latest header files.
2070 E
DSM_RC_NEEDTO_ENDTXN
Issue dsmEndTxn and then begin a new transaction
session.
Explanation: This transaction must be ended and a
new one must be started due to one of the following
reasons:
The destination changed.
The byte limit is exceeded
The maximum number of objects is exceeded.
2063 E
DSM_RC_OBJID_NOTFOUND
On dsmBeginGetData the objID is NULL.
Explanation: On dsmBeginGetData, the objID is
NULL.
procedure.
User response: Verify the following:
The dsmGetList is not NULL.
Each objID is not NULL.
The dsmGetList numObjId is not zero.

procedure.
User response: Issue dsmEndTxn and start a new
2080 E
DSM_RC_OBJ_EXCLUDED
The backup or archive object is excluded from
processing.
Explanation: The backup or archive object is excluded
from processing.
procedure.
2064 E
DSM_RC_WRONG_VERSION
User response: Verify the objName and Exclude lists.
On dsmInit the callers API version is different than

the TSM library version.
2081 E
DSM_RC_OBJ_NOBCG
Explanation: On dsmInit the caller's API version has a

higher value than the TSM library version.
The backup object does not have a copy group.

procedure.
Explanation: The backup object does not have a copy

group.
User response: Install the latest TSM API library and

trusted agent module.

procedure.
2065 E
DSM_RC_WRONG_VERSION_PARM
The callers structure version is different than the
TSM library version.
Explanation: The caller's structure version is different
procedure.
1134
2082 E
DSM_RC_OBJ_NOACG
The archive object does not have a copy group.
Explanation: The archive object does not have a copy
group.

procedure.
2090 E
DSM_RC_APISYSTEM_ERROR
Memory used by the TSM API has been corrupted.
Explanation: Memory used by the TSM API has been
corrupted.
procedure.
representative.
2100 E
DSM_RC_DESC_TOOLONG
The sendObj Archive description is too long.
Explanation: The sendObj Archive description is too
long.
2103 E
DSM_RC_PASSWD_TOOLONG
The password, or encryptionPassword string provided
is too long.
Explanation: The value provided for password or
encryptionPassword is too long.
procedure.
User response: The password or encrypionPassword
field must be less than
DSM_MAX_VERIFIER_LENGTH.
2104 E
DSM_RC_FILESPACE_TOOLONG
The sendObj dsmObjName.fs is too long.
Explanation: The sendObj dsmObjName.fs is too long.
procedure.
User response: The fs field must be less than or equal
to DSM_MAX_FS_LENGTH.

procedure.
User response: The sndArchiveData.descr string must
be less than or equal to DSM_MAX_DESCR_LENGTH.
2105 E
DSM_RC_LL_TOOLONG
The sendObj dsmObjName.ll is too long.
2101 E
DSM_RC_OBJINFO_TOOLONG
The sendObj ObjAttr.objInfo is too long.
Explanation: The sendObj ObjAttr.objInfo is too long.
Explanation: The sendObj dsmObjName.ll is too long.

procedure.
User response: The ll field must be less than or equal
to DSM_MAX_LL_LENGTH.

procedure.
User response: The objInfo field must be less than or
equal to DSM_MAX_OBJINFO_LENGTH.
2102 E
DSM_RC_HL_TOOLONG
The sendObj dsmObjName.hl is too long.
2106 E
DSM_RC_FSINFO_TOOLONG
On RegisterFS or UpdateFS the fsAttrs fsInfo is too
long.
Explanation: On RegisterFS or UpdateFS the fsAttr's
fsInfo is too long.
Explanation: The sendObj dsmObjName.hl is too long.

procedure.

procedure.
User response: The fsInfo field must be less than or

equal to DSM_MAX_FSINFO_LENGTH.
User response: The hl field must be less than or equal

to DSM_MAX_HL_LENGTH.
1135
2107 E
DSM_RC_SENDDATA_WITH_ZERO_SIZE
2113 E
DSM_RC_NO_FILES_ARCHIVE
Cannot Send data with a zero byte sizeEstimate.
No files have been previously archived for this

filename/filespace.
Explanation: You cannot send data for an object with

size estimate = 0.
procedure.
User response: Set size estimate greater than 0 in
dsmSendObj.

to set access.
2110 E
DSM_RC_INVALID_ACCESS_TYPE
The dsmSetAccess access Type is invalid.
Explanation: The dsmSetAccess accessType is invalid.
procedure.
User response: The accessType must be one of the
following:
atBackup
2114 E
DSM_RC_INVALID_SETACCESS
Invalid format for Set Access command.
Explanation: None.
User response: Enter the SET ACCESS command
using the correct syntax.
atArchive
2111 E
DSM_RC_QUERY_COMM_FAILURE
Communications error with server during object
query
occurred during an object query to the server.
2112 E
DSM_RC_NO_FILES_BACKUP
2120 E
DSM_RC_STRING_TOO_LONG
The following message was too long to log to the
server: shortened message with message number
Explanation: The message text and inserts are too
buffer.
System action: The message number message is written
to the local client error log, then shortened and sent to
the server as a part of this message. The message is
reduced in length by substituting ... in the middle of
the original message.
User response: The message referred to has been
shortened, but describes the error that occurred. Refer
to the documentation for that message for more
information.
No files have been previously backed up for this

filename/filespace.
2200 I
DSM_RC_MORE_DATA

On dsmGetNextQObj or dsmGetData there is more

available data.

you to set access.
1136
Explanation: On dsmGetNextQObj or dsmGetData

procedure.
User response: Call the function again.
2210 E
DSM_RC_BUFF_TOO_SMALL
The dataBlk buffer is too small for the query
response.
Explanation: The dataBlk buffer is too small for the
query response.
procedure.
User response: On dsmGetNextQObj ensure that the
dataBlk buffer is at least as big as the query response
structure.
DSMI_DIR. Verify the file name on the Inclexcl option

in the dsm.sys file.
2231 E
DSM_RC_REJECT_NO_POR_SUPPORT
Partial Object Retrieve is not supported on this
server.
Explanation: The TSM server specified by the user
does not support partial object retrieve.
procedure.
User response: Specify a TSM server which supports
the partial object retrieve function.
2228 E
DSM_RC_NO_API_CONFIGFILE
2300 E
DSM_RC_NEED_ROOT
The configuration file specified on dsmInit cannot be

opened.
Only a UNIX root user can execute dsmChangePW or

dsmDeleteFS.
Explanation: The configuration file specified on



procedure.

procedure.
User response: Verify the file name.
User response: Run this program as a root user.
2229 E
DSM_RC_NO_INCLEXCL_FILE
2301 E
DSM_RC_NEEDTO_CALL_BINDMC
The Include/Exclude definition file was not found.
You must issue dsmBindMC before dsmSendObj.
Explanation: The Include/Exclude definition file was

not found.
Explanation: You must issue dsmBindMC before

dsmSendObj.

procedure.

procedure.
User response: Verify the file name on the Inclexcl

option.
User response: Modify your program.
2230 E
DSM_RC_NO_SYS_OR_INCLEXCL
Either the dsm.sys file was not found, or the Inclexcl
file specified in dsm.sys was not found.
2302 I
DSM_RC_CHECK_REASON_CODE
The dsmEndTxn vote is ABORT, so check the reason
field.
Explanation: Either the dsm.sys file was not found, or

the Inclexcl file specified in dsm.sys was not found.
Explanation: After a dsmEndTxn call, the transaction

is aborted by either the server or client with a
DSM_VOTE_ABORT and the reason is returned.

procedure.

procedure.
User response: The dsm.sys file must be in the

directory referenced by the environment variable

which explains why the transaction has been aborted.
1137
2400 E
DSM_RC_ALMGR_OPEN_FAIL
2404 E
DSM_RC_ALMGR_CKSUM_BAD
License file could not be opened.
The checksum in the license file does not match the

licenseregistration string.

corrupted.
procedure.

procedure.

2405 E
DSM_RC_ALMGR_TRIAL_EXPRD
2401 E
DSM_RC_ALMGR_READ_FAIL
Read failure on the license file.
not be opened because of permissions, or the file is
corrupted.
This is an expired try and buy license.

procedure.

procedure.
2410 E
DSM_RC_ORC_INVALID_MODE
Oracle passed invalid mode
2402 E
DSM_RC_ALMGR_WRITE_FAIL
Write failure on the license file.
corrupted.
procedure.
User response: Check permissions on file. See if
2403 E
DSM_RC__ALMGR_DATA_FMT

procedure.
2411 E
DSM_RC_ORC_NULL_FILENAME
Oracle passed null file name
Explanation: Null filename passed by Oracle.
procedure.
Data in the license file is not in a valid format.

Explanation: The license file is not valid.
2412 E
DSM_RC_ORC_WRONG_BLKSIZE

procedure.
Explanation: Wrong Block Size

procedure.
1138
2413 E
DSM_RC_ORC_OBJ_EXISTS
User response: Use the WHAT command to find out

the compile time API level. Obtain the same or higher
level of API library.
Object exists
Explanation: Backup or Restore Object already exists.
procedure.
2418 E
DSM_RC_ORC_WRONG_WRTSTATE
Wrong write state
User response: If backing up an object, be sure to

generate a unique object name.
2414 E
DSM_RC_ORC_NOTSAME_HANDLE
Not same Oracle handle
2419 E
DSM_RC_ORC_INVALID_FLAG


procedure.
Invalid flag passed

procedure.
Explanation: Invalid flag passed from Oracle.

procedure.
2415 E
DSM_RC_ORC_END_OF_FILE
End of file reached
procedure.
User response: None
2416 E
DSM_RC_ORC_WRONG_RDSTATE
Wrong Read State
4580 E
DSM_RC_ENC_WRONG_KEY
Error processing filespace namepath-name file-name;
invalid encryption key.
entered.
User response: Try the restore operation again and
provide the correct key.

procedure.
2417 E
DSM_RC_ORC_LOWER_APIVER
4582 E
DSM_RC_ENC_NOT_AUTHORIZED
User is not authorized to encrypt filename.

API.

procedure.

1139
4584 E
DSM_RC_ENC_TYPE_UNKOWN
Error processing filespace namepath-namefile-name:
unsupported encryption type.
4600 E
DSM_RC_CLUSTER_INFO_LIBRARY_NOT
_LOADED
CLUSTERNODE is set to YES but the Cluster
Information Daemon is notstarted.
Explanation: The Cluster Information Daemon must
be started in order to specify the CLUSTERNODE
option.
User response: Start the HACMP Cluster Information
Dameon.
4601 E
DSM_RC_CLUSTER_LIBRARY_INVALID
CLUSTERNODE is set to YES but the cluster load
library is not valid.
system provides to obtain the cluster name is not valid.
A possible cause is an out-of-date load library which
does not contain the proper routines this product
expects.
User response: Ensure that the latest cluster software
is installed on the system.
4602 E
DSM_RC_CLUSTER_LIBRARY_NOT_LOADED
CLUSTERNODE is set to YES but the cluster software
is not availableon this system.
systems provides to obtain the cluster name is not
available on this system.
1140

4603 E
DSM_RC_CLUSTER_NOT_MEMBER_OF_CLUSTER
CLUSTERNODE is set to YES but this machine is not
a member of acluster.
Explanation: This machine is not a member of a
cluster node. Possible causes are that the cluster service
has not been configured correctly, or that the cluster is
in the process of initialization.
configured properly. If the cluster is in the process of
initialization, retry the operation at a later time.
4604 E
DSM_RC_CLUSTER_NOT_ENABLED
CLUSTERNODE is set to YES but the cluster service
is not enabledon this system.
Explanation: The cluster service has not been enabled
on this system.
User response: Enable the cluster service on the
system.
4605 E
DSM_RC_CLUSTER_NOT_SUPPORTED
The CLUSTERNODE option is not supported on this
system.
Explanation: This option is not supported on this
system.
User response: Disable the CLUSTERNODE option in
the local options file.
4606 E
DSM_RC_CLUSTER_UNKNOWN_ERROR
An unexpected error (retcode) occurred while the
program was trying to obtain the cluster name from
the system.
Explanation: An unknown error occurred while the
program was trying to obtain the cluster name from the
cluster service. The error code is the reason code
provided directly from the cluster service being used in

this operating system environment.
User response: Consult the documentation for your
clustering software for an explanation of the reason
code. Insure that your clustering service is operational,
then try the TSM operation again.
5717 E
DSM_RC_PROXY_REJECT_INTERNAL_ERROR
Proxy Rejected: The server has an internal error.
Explanation: The client cannot proxy to the node
named by the ASNODENAME option because of an
5702 E
DSM_RC_PROXY_REJECT_NO_RESOURCES

immediately.
Proxy Rejected: The TSM server has run out of

memory.
Explanation: There is not enough memory available to
allow this operation to continue.
amount of memory of the server.
5705 E
DSM_RC_PROXY_REJECT_DUPLICATE_ID
Proxy Rejected: ASNODENAME and NODENAME
are identical.
Explanation: TSM does not allow the ASNODENAME
and NODENAME option values to be the same.
User response: Use the ASNODENAME option only
to access another node. It is not necessary to set
ASNODENAME option to access your own node.
Remove ASNODENAME from your option file unless
you are actually trying to access a node that you have
been granted authority to access with the
administrative command Grant Proxynode.
5722 E
DSM_RC_PROXY_REJECT_NOT_AUTHORIZED
Proxy Rejected: Proxy authority has not been granted
to this node.
Explanation: The node has not been granted proxy
authority to access the node named by the
ASNODENAME option. The TSM administrator must
first grant proxy authority.
grant proxy authority for this node. See the
administrator command Grant Proxynode.
5746 E
DSM_RC_PROXY_INVALID_FROMNODE
The ASNODENAME option is not valid with the
FROMNODE option.
Explanation: None.
from the options file or do not use the FROMNODE
option.
5710 E
DSM_RC_PROXY_REJECT_ID_IN_USE
Proxy Rejected: The node name you specified in the
ASNODENAME option is locked.
Explanation: The TSM administrator has locked the
node you specified as the ASNODENAME option.
unlock the node before you can access it. Try the
operation later, or check with your TSM administrator.
5747 E
DSM_RC_PROXY_INVALID_SERVERFREE
The ASNODENAME option cannot be used with the
ENABLESERVERFREE option.
Explanation: None.
1141
5748 E
DSM_RC_PROXY_INVALID_FUNCTION
The operation that is being attempted cannot be
invoked using the ASNODENAME option.
Explanation: None.
5748 E
DSM_RC_PROXY_INVALID_CLUSTER
The ASNODENAME option cannot be used with the
CLUSTERNODE option.
Explanation: None.
5801 E
DSM_RC_CRYPTO_ICC_ERROR
Unexpected error in cryptography library.
Explanation: There was an unexpected error in the
cryptography library. See the error log for more
information.
support.
1142
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 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 Tivoli Storage Manager, 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
systems 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 IBM Tivoli Storage Manager Installation Guide.
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 servers database or log buffer pool.
To do this, update the value of the BUFPOOLSIZE or LOGPOOLSIZE parameters
in the server options file and restart the server. Note that each page causes an
additional 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.
1143
1144
Appendix C. I/O Error Code Descriptions for Server Messages

This section contains code descriptions for possible I/O error messages from the
Tivoli Storage Manager server for the AIX, HP-UX, Solaris, Linux, and Windows
operating systems.
Code
Description
OP
I/O operation that failed. 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 1149 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 1146 for a list of completion codes. Refer to the IBM
TotalStorage Tape Device Drivers Installation and Users 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 1150 also provides additional information on the common
values of ASC and ASCQ.
1145
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 1149 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 Tivoli
Storage Manager 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,

but sense data was unavailable.
201
X'C9'
Device driver failure
Contact Tivoli Storage Manager

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

information only
No action necessary
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

performing request
Ensure the device is on and ready.

Ensure the DEFINE DRIVE and
DEFINE DEVCLASS have been issued
properly.
208
X'D0'
Command aborted

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

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.
1146
Completion Code Values for Media Changers

numbers, for the media changers. It provides a description for the I/O error
Table 2. Completion Code Values for Media Changers
Decimal
Hexadecimal
Description
Recommended Action
300
X'12C'
Cartridge entry/exit error
Check the entry/exit ports for a

jammed volume.
301
X'12D'
Cartridge load failure
Check the drive for jammed volumes.

On AIX, display the errpt to check for
hardware errors.
302
X'12E'
Cartridge in failed drive
Check the drive for jammed volumes.

hardware errors.
303
X'12F'
Carousel not loaded
Ensure the carousel is correctly in place

and the door is shut.
304
X'130'
Changer failure

hardware errors.
305
X'131'
Drive failure
Ensure the heads have been cleaned.

hardware errors.
306
X'132'
Drive or media failure

hardware errors.
307
X'133'
Entry/exit failure

support.
308
X'134'
Entry/exit port not present

support.
309
X'135'
Library audit error
Ensure that there are no jammed

volumes. It is possible that the library
audit is failing due to hardware errors.
hardware errors.
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

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 an Ensure the volumes have not been
attempt to move a volume.
an AUDIT LIBRARY.
Appendix C. I/O Error Code Descriptions
1147
Table 2. Completion Code Values for Media Changers (continued)

Decimal
Hexadecimal
Description
Recommended Action
315
X'13B'
The destination slot or drive was full in

an attempt to move a volume.
Ensure the volumes have not been

rearranged, or that a volume is not
stuck in the drive. If problem persists,
perform AUDIT LIBRARY.
316
X'13C'
Cleaner cartridge installed

support.
317
X'13D'
Media not ejected

rearranged, or that a volume is not
stuck in the drive. If problem persists,
perform AUDIT LIBRARY.
318
X'13E'
I/O port not configured

support.
319
X'13F'
First destination empty

AUDIT LIBRARY.
320
X'140'
No inventory information
Perform AUDIT LIBRARY.
321
X'141'
Read element status mismatch

support.
322
X'142'
Initialize range failed

support.
Completion Code Values for Tape and Optical Drives

numbers, for tape and optical drives. It provides a description for the I/O error
Table 3. Completion Code Values for Tape and Optical Drives
Decimal
Description
Recommended Action
X'190'
Physical end of media encountered
Ensure the heads are clean on the drive.
401
X'191'
End of data detected

support.
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 Tivoli

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.
400
1148
Hexadecimal
Table 3. Completion Code Values for Tape and Optical Drives (continued)
Decimal
Hexadecimal
Description
Recommended Action
409
X'199'
Media fault
Clean the heads and ensure the media

is not physically damaged or too old.
410
X'19A'
Cleaning complete
411
X'19B'
Logical end of media encountered

support.
412
X'19C'
Media not present in drive
Ensure the media is correctly positioned

in the drive. If problem persists,
perform an AUDIT LIBRARY.
413
X'19D'
Beginning of media encountered

support.
414
X'19E'
Erase failure
Clean the drive heads.
415
X'19F'
Attempted to overwrite written WORM

media
Internal server error. Contact Tivoli

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

support.
418
X'1A2'
Open write only

support.
419
X'1A2'
Media scan failed
Clean the drive and media.
420
X'1A4'
Logical write protect

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 TotalStorage Tape Device Drivers
Installation and Users 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.
1149
Table 4. Operation Code Values for Tape Library Devices (continued)

Hexadecimal
X'6D39'
Name
Description
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 , these codes also
appear in the Event Log. See Windows Event Log Entries on page 1153.
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
1150
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
Table 5. Common Values for ASC and ASCQ Codes (continued)

ASC
ASCQ
Description
0x11
0x01
Read retries exhausted
0x11
0x02
Error too long to correct
0x11
0x03
Multiple read errors
0x11
0x08
Incomplete block read
0x11
0x09
No gap found
0x11
0x0A
Miscorrected error
0x14
0x00
Recorded entity not found
0x14
0x01
Record not found
0x14
0x02
Filemark/setmark not found
0x14
0x03
End-of-data not found
0x14
0x04
Block sequence error
0x15
0x00
Random positioning error
0x15
0x01
Mechanical positioning error
0x15
0x02
Read positioning error
0x17
0x00
No error correction applied
0x17
0x01
Recovered with retries
0x17
0x02
Recovered with positive head offset
0x17
0x03
Recovered with negative head offset
0x18
0x00
ECC applied
0x1A
0x00
Parameter list length error
0x1B
0x00
Synchronous data transfer error
0x20
0x00
Invalid operation code
0x21
0x00
Block out of range
0x21
0x01
Invalid element address
0x24
0x00
Invalid field in CDB
0x25
0x00
LUN not supported
0x26
00
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
Invalid field in parameter list
1151
1152
ASC
ASCQ
Description
0x2F
0x00
Command cleared by initiator
0x30
0x00
Incompatible media
0x30
0x01
Media unknown format
0x30
0x02
Media incompatible format
0x30
0x03
Cleaning cartridge installed
0x31
0x00
Media format corrupted
0x33
0x00
Tape length error
0x37
0x00
Rounded parameter
0x39
0x00
Saving parameters not supported
0x3A
0x00
Medium not present
0x3B
0x00
Sequential positioning error
0x3B
0x01
Positioning error at BOT
0x3B
0x02
Positioning error at EOT
0x3B
0x08
Reposition error
0x3B
0x0D
Medium destination element full
0x3B
0x0E
Medium source element empty
0x3D
0x00
Invalid bits in message
0x3E
0x00
LUN not self-configured
0x3F
0x00
Operating conditions changed
0x3F
0x01
Microcode 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

ASC
ASCQ
Description
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 Event Log Entries

The code values will appear as hexadecimal values in the Data area of the
Windows Event Log. The Event Log omits the 0x prefix for the displayed
information.
In the Windows Event Log, the entries with source AdsmScsi are produced by the
AdsmScsi device driver. In these entries, byte 3E is the sense key, byte 3D is the
ASC, and byte 3C is the ASCQ. (This is also true of entries logged by any of the
Windows 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.
1153
1154
Appendix D. Device Errors in AIX System Error Log

Tivoli Storage Manager 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 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 devices 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
devices 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
1155
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 devices 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.
1156
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 users 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.
1157
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
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
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.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo and the following terms are trademarks of the International
Business Machines Corporation in the United States, other countries, or both:
AFS
AIX
AS/400
DB2
Enterprise Storage Server
FlashCopy
GPFS
HACMP
Lotus
MVS
MVS/DFP
MVS/ESA
Notes
NUMA-Q
OS/2
OS/390
RACF
Redbooks
REXX
SANergy
SP
SystemView
System Storage
Tivoli
Tivoli Enterprise
Tivoli Enterprise Console
WebSphere
z/OS
zSeries
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in
the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
1158
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Other company, product, or service names may be trademarks or service marks of
others.
Notices
1159
1160
Glossary
The terms in this glossary are defined as they
pertain to the IBM Tivoli Storage Manager library.
If you do not find the term you need, refer to the
IBM Software Glossary on the Web at this
address: www.ibm.com/ibm/terminology/.
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
absolute mode. A backup copy group mode that
specifies that a file is considered for incremental
backup even if the file has not changed since the last
backup. See also mode. Contrast with modified mode.
access mode. An attribute of a storage pool or a
storage volume that specifies whether the server can
write to or read from the storage pool or storage
volume. The access mode can be read/write, read-only,
or unavailable. Volumes in primary storage pools can
also have an access mode of destroyed. Volumes in
copy storage pools can also have an access mode of
offsite.
activate. To validate the contents of a policy set and
then make it the active policy set.
active-data pool. A named set of storage pool volumes
that contains only active versions of client backup data.
active policy set. The activated policy set that contains
the policy rules currently in use by all client nodes
assigned to the policy domain. See also policy domain
and policy set.
active version. The most recent backup copy of a file
stored by IBM Tivoli Storage Manager. The active
version of a file cannot be deleted until a backup
process detects that the user has either replaced the file
with a newer version or has deleted the file from the
workstation. Contrast with inactive version.
activity log. A log that records normal activity

messages generated by the server. These messages
include information about server and client operations,
such as the start time of sessions or device I/O errors.
Each message includes a message ID, date and time
stamp, and a text description. The number of days to
retain messages in the activity log can be specified.
administrative client. A program that runs on a file
server, workstation, or mainframe that administrators
use to control and monitor the IBM Tivoli Storage
Manager server. Contrast with backup-archive client.
administrative command schedule. A database record
that describes the planned processing of an
administrative command during a specific time period.
See also client schedule.
administrative privilege class. See privilege class.
administrative session. A period of time in which an
administrator user ID communicates with a server to
perform administrative tasks. Contrast with client node
session.
administrator. A user who has been registered to the
server. Administrators can be authorized to one or
more of the following administrative privilege classes:
system, policy, storage, operator, or analyst.
Administrators can use the administrative commands
and queries allowed by their privileges.
agent node. A client node that has been granted proxy
authority to perform operations on behalf of another
client node, which is the target node.
aggregate. An object, stored in one or more storage
pools, consisting of a group of logical files packaged
together. See logical file and physical file.
analyst privilege class. A privilege class that allows
an administrator to reset statistics. See also privilege
class.
application client. One of the IBM Tivoli Storage
Manager data protection programs installed on a
system to protect an application. The IBM Tivoli
Storage Manager server provides backup services to an
application client.
archive. To copy one or more files to a storage pool
for long-term storage. Archived files can include
descriptive information and can be retrieved by archive
date, by file name, or by description. Contrast with
retrieve.
archive copy. A file that was archived to server
storage.
1161
archive copy group. A policy object containing

attributes that control the generation, destination, and
expiration of archived files. An archive copy group
belongs to a management class.
archive retention grace period. The number of days
that IBM Tivoli Storage Manager retains an archived
file when the server is unable to rebind the file to an
appropriate management class.
assigned capacity. The portion of available space that
can be used to store database or recovery log
information. See also available space.
association. (1) The defined relationship between a
client node and a client schedule. An association
identifies the name of a schedule, the name of the
policy domain to which the schedule belongs, and the
name of a client node that performs scheduled
operations. (2) On a configuration manager, the defined
relationship between a profile and an object such as a
policy domain. Profile associations define the
configuration information that will be distributed to a
managed server when it subscribes to the profile.
audit. To check for logical inconsistencies between
information that the server has and the actual condition
of the system. IBM Tivoli Storage Manager can audit
volumes, the database, libraries, and licenses. For
example, when IBM Tivoli Storage Manager audits a
volume, the server checks for inconsistencies between
information about backed-up or archived files stored in
the database and the actual data associated with each
backup version or archive copy in server storage.
authentication. The process of checking a users
password before allowing that user access to the server.
Authentication can be turned on or off by an
administrator with system privilege.
authority. The right granted to a user to perform tasks
with IBM Tivoli Storage Manager servers and clients.
See also privilege class.
autochanger. A small, multislot tape device that
automatically puts tape cartridges into tape drives. See
also library.
available space. The amount of space, in megabytes,
that is available to the database or the recovery log.
This space can be used to extend the capacity of the
database or the recovery log, or to provide sufficient
free space before a volume is deleted from the database
or the recovery log.
Storage Manager database, and storage pools. Contrast

with restore. See also database backup series and
incremental backup.
backup-archive client. A program that runs on a
workstation or file server and provides a means for
users to back up, archive, restore, and retrieve files.
Contrast with administrative client.
backup copy group. A policy object containing
attributes that control the generation, destination, and
expiration of backup versions of files. A backup copy
group belongs to a management class.
backup retention grace period. The number of days
that IBM Tivoli Storage Manager retains a backup
version after the server is unable to rebind the file to an
appropriate management class.
backup set. A portable, consolidated group of active
backup versions of files, generated for a backup-archive
client.
backup version. A file that a user backed up to server
storage. More than one backup version can exist in
server storage, but only one backup version is the
active version. See also active version and inactive
version.
binding. The process of associating a file with a
management class name. See rebinding.
buffer pool. Temporary space used by the server to
hold database or recovery log pages. See database buffer
pool and recovery log buffer pool.
C
cache. The process of leaving a duplicate copy on
random access media when the server migrates a file to
another storage pool in the hierarchy.
central scheduler. A function that allows an
administrator to schedule client operations and
administrative commands. The operations can be
scheduled to occur periodically or on a specific date.
See client schedule and administrative command schedule.
client. A program running on a PC, workstation, file

server, LAN server, or mainframe that requests services
of another program, called the server. The following
types of clients can obtain services from an IBM Tivoli
Storage Manager server: administrative client,
application client, API client, backup-archive client, and
HSM client (also known as Tivoli Storage Manager for
Space Management).
back up. To copy information to another location to

ensure against loss of data. In IBM Tivoli Storage
Manager, you can back up user files, the IBM Tivoli
client domain. The set of drives, file systems, or

volumes that the user selects to back up or archive
using the backup-archive client.
client migration. The process of copying a file from a
client node to server storage and replacing the file with
1162
a stub file on the client node. The space management

attributes in the management class control this
migration. See also space management.
client node. A file server or workstation on which the
backup-archive client program has been installed, and
which has been registered to the server.
client node session. A period of time in which a client
node communicates with a server to perform backup,
restore, archive, retrieve, migrate, or recall requests.
Contrast with administrative session.
client options file. A file that a client can change,
containing a set of processing options that identify the
server, communication method, and options for backup,
archive, hierarchical storage management, and
scheduling. Also called the dsm.opt file.
client-polling scheduling mode. A client/server
communication technique where the client queries the
server for work. Contrast with server-prompted
scheduling mode.
client schedule. A database record that describes the
planned processing of a client operation during a
specific time period. The client operation can be a
backup, archive, restore, or retrieve operation, a client
operating system command, or a macro. See also
administrative command schedule.
client system options file. A file, used on UNIX
clients, containing a set of processing options that
identify the IBM Tivoli Storage Manager servers to be
contacted for services. This file also specifies
communication methods and options for backup,
archive, hierarchical storage management, and
scheduling. Also called the dsm.sys file. See also client
user options file.
client user options file. A user-created file, used on
UNIX clients, containing a set of processing options
that identify the server, communication method,
backup and archive options, space management
options, and scheduling options. Also called the dsm.opt
file. See also client system options file.
closed registration. A registration process in which
only an administrator can register workstations as
client nodes with the server. Contrast with open
registration.
collocation. The process of keeping all data belonging
to a single client file space, a single client node, or a
group of client nodes on a minimal number of
sequential-access volumes within a storage pool.
Collocation can reduce the number of volumes that
must be accessed when a large amount of data must be
restored.
collocation group. A user-defined group of client
nodes whose data is stored on a minimal number of
volumes through the process of collocation.
compression. The process of saving storage space by

eliminating empty fields or unnecessary data in a file.
In IBM Tivoli Storage Manager, compression can occur
at a workstation before files are backed up or archived
to server storage. On some types of tape drives,
hardware compression can be used.
configuration manager. One IBM Tivoli Storage
Manager server that distributes configuration
information to other IBM Tivoli Storage Manager
servers (called managed servers) via profiles.
Configuration information can include policy and
schedules. See managed server and profile.
copy group. A policy object whose attributes control
how backup versions or archive copies are generated,
where backup versions or archive copies are initially
located, and when backup versions or archive copies
expire. A copy group belongs to a management class.
See also archive copy group, backup copy group, backup
version, and management class.
copy storage pool. A named set of volumes that
contains copies of files that reside in primary storage
pools. Copy storage pools are used only to back up the
data stored in primary storage pools. A copy storage
pool cannot be a destination for a backup copy group,
an archive copy group, or a management class (for
space-managed files). See primary storage pool and
destination.
D
damaged file. A physical file for which IBM Tivoli
Storage Manager has detected read errors.
database. A collection of information about all objects
managed by the server, including policy management
objects, users and administrators, and client nodes.
database backup series. One full backup of the
database, plus up to 32 incremental backups made
since that full backup. Each full backup that is run
starts a new database backup series. A number
identifies each backup series.
database backup trigger. A set of criteria that defines
when and how database backups are run automatically.
The criteria determine how often the backup is run,
whether the backup is a full or incremental backup,
and where the backup is stored.
database buffer pool. Storage that is used as a cache
to allow database pages to remain in memory for long
periods of time, so that the server can make continuous
updates to pages without requiring input or output
(I/O) operations from external storage.
database snapshot. A complete backup of the entire
IBM Tivoli Storage Manager database to media that can
be taken off-site. When a database snapshot is created,
the current database backup series is not interrupted. A
Glossary
1163
database snapshot cannot have incremental database

backups associated with it. See also database backup
series. Contrast with full backup.
data mover. A device, defined to IBM Tivoli Storage
Manager, that moves data on behalf of the server. A
NAS file server can be a data mover.
default management class. A management class
assigned to a policy set that the server uses to manage
backed-up or archived files when a user does not
specify a management class for a file.
desktop client. The group of backup-archive clients
supported by IBM Tivoli Storage Manager that includes
clients on Windows, Apple, and Novell NetWare
operating systems.
destination. A copy group or management class
attribute that specifies the primary storage pool to
which a client file will be backed up, archived, or
migrated.
device class. A named set of characteristics applied to
a group of storage devices. Each device class has a
unique name and represents a device type of disk, file,
optical disk, or tape.
device configuration file. A file that contains
information about defined device classes, and, on some
IBM Tivoli Storage Manager servers, defined libraries
and drives. The file can be created by using an IBM
Tivoli Storage Manager administrative command or by
using an option in the server options file. The
information is a copy of the device configuration
information in the IBM Tivoli Storage Manager
database.
disaster recovery manager (DRM). A function in IBM
Tivoli Storage Manager that assists in preparing and
later using a disaster recovery plan file for the IBM
Tivoli Storage Manager server.
disaster recovery plan. A file created by disaster
recovery manager (DRM) that contains information
about how to recover computer systems if a disaster
occurs and scripts that can be run to perform some
recovery tasks. The file includes information about the
software and hardware used by the IBM Tivoli Storage
Manager server, and the location of recovery media.
domain. See policy domain or client domain.
DRM. A short name for disaster recovery manager.
dsm.opt file. See client options file and client user
options file.
dsmserv.opt. See server options file.
dsm.sys file. See client system options file.
dynamic. A value for serialization that specifies that
IBM Tivoli Storage Manager accepts the first attempt to
1164
back up or archive a file regardless of whether the file

is modified during the backup or archive process. See
also serialization. Contrast with shared dynamic, shared
static, and static.
E
enterprise configuration. A method of setting up IBM
Tivoli Storage Manager servers so that the
administrator can distribute the configuration of one of
the servers to the other servers, using server-to-server
communication. See configuration manager, managed
server, profile, and subscription.
enterprise logging. The sending of events from IBM
Tivoli Storage Manager servers to a designated event
server. The event server routes the events to designated
receivers, such as to a user exit. See also event.
estimated capacity. The available space, in megabytes,
of a storage pool.
event. (1) An administrative command or a client
operation that is scheduled to be run using IBM Tivoli
Storage Manager scheduling. (2) A message that an
IBM Tivoli Storage Manager server or client issues.
Messages can be logged using IBM Tivoli Storage
Manager event logging.
event record. A database record that describes actual
status and results for events.
event server. A server to which other servers can send
events for logging. The event server routes the events
to any receivers that are enabled for the sending
servers events.
exclude. To identify files that you do not want to
include in a specific client operation, such as backup or
archive. You identify the files in an include-exclude list.
exclude-include list. See include-exclude list.
expiration. The process by which files are identified
for deletion because their expiration date or retention
period has passed. Backed-up or archived files are
marked expired by IBM Tivoli Storage Manager based
on the criteria defined in the backup or archive copy
group.
expiration date. On some IBM Tivoli Storage Manager
servers, a device class attribute used to notify tape
management systems of the date when IBM Tivoli
Storage Manager no longer needs a tape volume. The
date is placed in the tape label so that the tape
management system does not overwrite the
information on the tape volume before the expiration
date.
export. To copy administrator definitions, client node
definitions, policy definitions, server control
information, or file data to external media, or directly

to another server. Used to move or copy information
between servers.
extend. To increase the portion of available space that
can be used to store database or recovery log
information. Contrast with reduce.
F
file space. A logical space in IBM Tivoli Storage
Manager server storage that contains a group of files
backed up or archived by a client. For clients on
Windows systems, a file space contains files from a
logical partition that is identified by a volume label.
For clients on UNIX systems, a file space contains files
from the same file system, or the part of a file system
that stems from a virtual mount point. Clients can
restore, retrieve, or delete their file spaces from IBM
Tivoli Storage Manager server storage. IBM Tivoli
Storage Manager does not necessarily store all the files
belonging to a single file space together, but can
identify all the files in server storage that belong to a
single file space.
file space ID (FSID). A unique numeric identifier that
the server assigns to a file space when it is stored in
server storage.
frequency. A copy group attribute that specifies the
minimum interval, in days, between incremental
backups.
FSID. See file space ID.
full backup. The process of backing up the entire
server database. A full backup begins a new database
backup series. See also database backup series and
incremental backup. Contrast with database snapshot.
fuzzy copy. A backup version or archive copy of a file
that might not accurately reflect the original content of
the file because IBM Tivoli Storage Manager backed up
or archived the file while the file was being modified.
See also backup version and archive copy.
H
hierarchical storage management (HSM) client. The
Tivoli Storage Manager for Space Management program
that runs on workstations to allow users to maintain
free space on their workstations by migrating and
recalling files to and from IBM Tivoli Storage Manager
storage. Synonymous with space manager client.
high migration threshold. A percentage of the storage
pool capacity that identifies when the server can start
migrating files to the next available storage pool in the
hierarchy. Contrast with low migration threshold. See
server migration.
HSM client. Hierarchical storage management client.

Also known as the space manager client.
I
IBM Tivoli Storage Manager command script. A
sequence of IBM Tivoli Storage Manager administrative
commands that are stored in the database of the IBM
Tivoli Storage Manager server. You can run the script
from any interface to the server. The script can include
substitution for command parameters and conditional
logic.
image backup. A backup of a full file system or raw
logical volume as a single object.
import. The process of copying exported administrator
definitions, client node definitions, policy definitions,
server control information or file data from external
media to a target server. A subset of information can be
imported to a target server from the external media.
Used to move or copy information between servers. See
export.
inactive version. A backup version of a file that is
either not the most recent backup version, or that is a
backup version of a file that no longer exists on the
client system. Inactive backup versions are eligible for
expiration processing according to the management
class assigned to the file. Contrast with active version.
include-exclude file. A file containing statements that
IBM Tivoli Storage Manager uses to determine whether
to include certain files in specific client operations, and
to determine the associated management classes to use
for backup, archive, and space management. See
include-exclude list.
include-exclude list. A group of include and exclude
option statements that IBM Tivoli Storage Manager
uses. The exclude options identify files that are not to
be included in specific client operations such as backup
or space management. The include options identify files
that are exempt from the exclusion rules. The include
options can also assign a management class to a file or
group of files for backup, archive, or space
management services. The include-exclude list for a
client may include option statements from the client
options file, from separate include-exclude files, and
from a client option set on the server.
incremental backup. (1) The process of backing up
files or directories that are new or have changed since
the last incremental backup. See also selective backup. (2)
The process of copying only the pages in the database
that are new or changed since the last full or
incremental backup of the database. Contrast with full
backup. See also database backup series.
Glossary
1165
L
LAN-free data movement. The direct movement of
client data between a client machine and a storage
device on a SAN, rather than on the LAN.
library. (1) A repository for demountable recorded
media, such as magnetic tapes. (2) For IBM Tivoli
Storage Manager, a collection of one or more drives,
and possibly robotic devices (depending on the library
type), which can be used to access storage volumes. (3)
In the AS/400 system, a system object that serves as a
directory to other objects. A library groups related
objects, and allows the user to find objects by name.
library client. An IBM Tivoli Storage Manager server
that uses server-to-server communication to access a
library that is managed by another IBM Tivoli Storage
Manager server. See also library manager.
library manager. An IBM Tivoli Storage Manager
server that controls device operations when multiple
IBM Tivoli Storage Manager servers share a storage
device. The device operations include mount,
dismount, volume ownership, and library inventory.
See also library client.
logical file. A file stored in one or more server storage
pools, either by itself or as part of an aggregate. See
also aggregate and physical file.
logical occupancy. The space used by logical files in a
storage pool. Because logical occupancy does not
include the unused space created when logical files are
deleted from aggregates, it may be less than physical
occupancy. See also physical file and logical file.
logical volume. (1) A portion of a physical volume
that contains a file system. (2) For the IBM Tivoli
Storage Manager server, the combined space on all
volumes for either the database or the recovery log.
The database is one logical volume, and the recovery
log is one logical volume.
low migration threshold. A percentage of the storage
pool capacity that specifies when the server can stop
the migration of files to the next storage pool. Contrast
with high migration threshold. See server migration.
M
macro file. A file that contains one or more IBM Tivoli
Storage Manager administrative commands, which can
be run only from an administrative client by using the
MACRO command. Contrast with IBM Tivoli Storage
Manager command script.
managed object. A definition in the database of a
managed server that was distributed to the managed
server by a configuration manager. When a managed
server subscribes to a profile, all objects associated with
that profile become managed objects in the database of
1166
the managed server. In general, a managed object

cannot be modified locally on the managed server.
Objects can include policy, schedules, client options
sets, server scripts, administrator registrations, and
server and server group definitions.
managed server. An IBM Tivoli Storage Manager
server that receives configuration information from a
configuration manager via subscription to one or more
profiles. Configuration information can include
definitions of objects such as policy and schedules. See
configuration manager, subscription, and profile.
managed system. A client or server that requests
services from the IBM Tivoli Storage Manager server.
management class. A policy object that users can bind
to each file to specify how the server manages the file.
The management class can contain a backup copy
group, an archive copy group, and space management
attributes. The copy groups determine how the server
manages backup versions or archive copies of the file.
The space management attributes determine whether
the file is eligible to be migrated by the space manager
client to server storage and under what conditions the
file is migrated. See also copy group, space manager client,
binding, and rebinding.
maximum extension. Specifies the maximum amount
of storage space, in megabytes, that you can extend the
database or the recovery log.
maximum reduction. Specifies the maximum amount
of storage space, in megabytes, that you can reduce the
database or the recovery log.
maximum utilization. The highest percentage of
assigned capacity used by the database or the recovery
log.
migrate. To move data from one storage location to
another. See also client migration and server migration.
mirroring. The process of writing the same data to
multiple disks at the same time. The mirroring of data
protects against data loss within the database or within
the recovery log.
mode. A copy group attribute that specifies whether
to back up a file that has not been modified since the
last time the file was backed up. See modified and
absolute.
modified mode. A backup copy group mode that
specifies that a file is considered for incremental
backup only if it has changed since the last backup. A
file is considered changed if the date, size, owner, or
permissions of the file has changed. See also mode.
Contrast with absolute mode.
mount. To place a data medium (such as a tape
cartridge) on a drive in a position to operate.
mount limit. A device class attribute that specifies the

maximum number of volumes that can be
simultaneously accessed from the same device class.
The mount limit determines the maximum number of
mount points. See mount point.
mount point. A logical drive through which volumes
in a sequential access device class are accessed. For
removable media device types, such as tape, a mount
point is a logical drive associated with a physical drive.
For the file device type, a mount point is a logical drive
associated with an I/O stream. The number of mount
points for a device class is defined by the value of the
mount limit attribute for that device class. See mount
limit.
mount retention period. A device class attribute that
specifies the maximum number of minutes that the
server retains a mounted sequential access media
volume that is not being used before it dismounts the
sequential access media volume.
mount wait period. A device class attribute that
specifies the maximum number of minutes that the
server waits for a sequential access volume mount
request to be satisfied before canceling the request.
N
NAS. Network-attached storage.
NAS node. A client node that is a network-attached
storage (NAS) file server. Data for the NAS node is
transferred by the NAS file server, which is controlled
by the IBM Tivoli Storage Manager server. The Tivoli
Storage Manager server uses the network data
management protocol (NDMP) to direct the NAS file
server in its backup and restore operations. A NAS
node is also called a NAS file server node.
native format. A format of data that is written to a
storage pool directly by the IBM Tivoli Storage
Manager server. Contrast with non-native data format.
NDMP. Network Data Management Protocol.
network-attached storage (NAS) file server. A
dedicated storage device with an operating system that
is optimized for file-serving functions. In IBM Tivoli
Storage Manager, a NAS file server can have the
characteristics of both a node and a data mover. See
also data mover and NAS node.
its services. See also client node and NAS node. (2) In a
Microsoft cluster configuration, one of the computer
systems that make up the cluster.
node privilege class. A privilege class that allows an
administrator to remotely access backup-archive clients
for a specific client node or for all clients in a policy
domain. See also privilege class.
non-native data format. A format of data written to a
storage pool that is different from the format that the
server uses for basic LAN-based operations. The data is
written by a data mover instead of the server. Storage
pools with data written in a non-native format may not
support some server operations, such as audit of a
volume. The NETAPPDUMP data format for NAS node
backups is an example of a non-native data format.
O
open registration. A registration process in which any
users can register their own workstations as client
nodes with the server. Contrast with closed registration.
operator privilege class. A privilege class that allows
an administrator to issue commands that disable or halt
the server, enable the server, cancel server processes,
and manage removable media. See also privilege class.
P
page. A unit of space allocation within IBM Tivoli
Storage Manager database volumes.
path. An IBM Tivoli Storage Manager object that
defines a one-to-one relationship between a source and
a destination. Using the path, the source accesses the
destination. Data may flow from the source to the
destination, and back. An example of a source is a data
mover (such as a NAS file server), and an example of a
destination is a tape drive.
physical file. A file stored in one or more storage
pools, consisting of either a single logical file, or a
group of logical files packaged together (an aggregate).
See also aggregate and logical file.
physical occupancy. The amount of space used by
physical files in a storage pool. This space includes the
unused space created when logical files are deleted
from aggregates. See also physical file, logical file, and
logical occupancy.
Network Data Management Protocol (NDMP). An

industry-standard protocol that allows a network
storage-management application (such as IBM Tivoli
Storage Manager) to control the backup and recovery of
an NDMP-compliant file server, without installing
third-party software on that file server.
policy domain. A grouping of policy users with one

or more policy sets, which manage data or storage
resources for the users. In IBM Tivoli Storage Manager,
the users are client nodes. See policy set, management
class, and copy group.
node. (1) A workstation or file server that is registered

with an IBM Tivoli Storage Manager server to receive
policy privilege class. A privilege class that allows an

administrator to manage policy objects, register client
Glossary
1167
nodes, and schedule client operations for client nodes.

Authority can be restricted to certain policy domains.
See also privilege class.
reclamation. A process of consolidating the remaining

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.
Several policy sets can exist within a policy domain but
only one policy set is active at one time. See
management class and active policy set.
reclamation threshold. The percentage of reclaimable

space that a sequential access media volume must have
before the server can reclaim the volume. Space
becomes reclaimable when files are expired or are
deleted. 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
storage, while leaving the original file intact on the
local system.
recovery log. A log of updates that are about to be

written to the database. The log can be used to recover
from system and media failures.
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
nodes. You can back up a primary storage pool to a
copy storage pool. See destination and copy storage pool.
privilege class. A level of authority granted to an
administrator. The privilege class determines which
administrative tasks the administrator can perform. For
example, an administrator with system privilege class
can perform any administrative task. Also called
administrative privilege class. See also system privilege
class, policy privilege class, storage privilege class, operator
privilege class, analyst privilege class, and node privilege
class.
profile. A named group of configuration information
that can be distributed from a configuration manager
when a managed server subscribes. Configuration
information can include registered administrators,
policy, client schedules, client option sets,
administrative schedules, IBM Tivoli Storage Manager
command scripts, server definitions, and server group
definitions. See configuration manager and managed
server.
R
randomization. The process of distributing schedule
start times for different clients within a specified
percentage of the schedules startup window.
rebinding. The process of associating a backed-up file
with a new management class name. For example,
rebinding occurs when the management class
associated with a file is deleted. See binding.
recall. To access files that were migrated from
workstations to server storage by using the space
manager client. Contrast with migrate.
receiver. A server repository that contains a log of
server messages and client messages as events. For
example, a receiver can be a file exit, a user exit, or the
IBM Tivoli Storage Manager server console and activity
log. See also event.
1168
recovery log buffer pool. Storage that the server uses

to hold new transaction records until they can be
written to the recovery log.
reduce. To free up enough space from the database or
the recovery log, such that you can delete a volume.
Contrast with extend.
register. (1) To define a client node or administrator
who can access the server. See registration. (2) To specify
licenses that have been purchased for the server.
registration. The process of identifying a client node
or administrator to the server.
restore. To copy information from its backup location
to the active storage location for use. In IBM Tivoli
Storage Manager, you can restore the server database,
storage pools, storage pool volumes, and users
backed-up files. The backup version of a file in the
storage pool is not affected by the restore operation.
Contrast with backup.
retention. The amount of time, in days, that inactive
backed-up or archived files are kept in the storage pool
before they are deleted. Copy group attributes and
default retention grace periods for the domain define
retention.
retention period. On an MVS server, a device class
attribute that specifies how long files are retained on
sequential access media. When used, IBM Tivoli
Storage Manager passes this information to the MVS
operating system to ensure that other tape management
systems do not overwrite tape volumes that contain
retained data.
retrieve. To copy archived information from the
storage pool to the client node for use. The retrieve
operation does not affect the archive copy in the
storage pool. Contrast with archive.
rollback. To remove changes that were made to
database files since the last commit point.
shared library. A library device that is shared among

multiple IBM Tivoli Storage Manager servers.
schedule. A database record that describes scheduled

client operations or administrative commands. See
administrative command schedule and client schedule.
shared static. A value for serialization that specifies

that a file must not be backed up or archived if it is
being modified during the operation. IBM Tivoli
Storage Manager retries the backup or archive
operation a number of times; if the file is being
modified during each attempt, IBM Tivoli Storage
Manager will not back up or archive the file. See also
serialization. Contrast with dynamic, shared dynamic, and
static.
scheduling mode. The method of interaction between

a server and a client for running scheduled operations
on the client. IBM Tivoli Storage Manager supports two
scheduling modes for client operations: client-polling
and server-prompted.
scratch volume. A labeled volume that is either blank
or contains no valid data, that is not currently defined
to IBM Tivoli Storage Manager, and that is available for
use.
script. See IBM Tivoli Storage Manager command script.
selective backup. The process of backing up selected
files or directories from a client domain. See also
incremental backup.
serialization. The process of handling files that are
modified during backup or archive processing. See
static, dynamic, shared static, and shared dynamic.
server migration. The process of moving data from
one storage pool to the next storage pool defined in the
hierarchy, based on the migration thresholds defined
for the storage pools. See also high migration threshold
and low migration threshold.
server options file. A file that contains settings that
control various server operations. These settings, or
options, affect such things as communications, devices,
and performance.
server-prompted scheduling mode. A client/server
communication technique where the server contacts the
client when a scheduled operation needs to be done.
Contrast with client-polling scheduling mode.
server storage. The primary and copy storage pools
used by the server to store users files: backup versions,
archive copies, and files migrated from space manager
client nodes (space-managed files). See primary storage
pool, copy storage pool, storage pool volume, and volume.
session resource usage. The amount of wait time,
CPU time, and space used or retrieved during a client
session.
shared dynamic. A value for serialization that
specifies that a file must not be backed up or archived
if it is being modified during the operation. IBM Tivoli
Storage Manager retries the backup or archive
operation a number of times; if the file is being
modified during each attempt, IBM Tivoli Storage
Manager will back up or archive the file on its last try.
See also serialization. Contrast with dynamic, shared
static, and static.
snapshot. See database snapshot.

source server. A server that can send data, in the form
of virtual volumes, to another server. Contrast with target
server.
space-managed file. A file that is migrated from a
client node by the space manager client (HSM client).
The space manager client recalls the file to the client
node on demand.
space management. The process of keeping sufficient
free storage space available on a client node by
migrating files to server storage. The files are migrated
based on criteria defined in management classes to
which the files are bound, and the include-exclude list.
Synonymous with hierarchical storage management. See
also migration.
space manager client. The Tivoli Storage Manager for
Space Management program that enables users to
maintain free space on their workstations by migrating
and recalling files to and from server storage. Also
called hierarchical storage management (HSM) client.
startup window. A time period during which a
schedule must be initiated.
static. A value for serialization that specifies that a file
must not be backed up or archived if it is being
modified during the operation. IBM Tivoli Storage
Manager does not retry the operation. See also
serialization. Contrast with dynamic, shared dynamic, and
shared static.
storage agent. A program that enables IBM Tivoli
Storage Manager to back up and restore client data
directly to and from SAN-attached storage.
storage hierarchy. A logical ordering of primary
storage pools, as defined by an administrator. The
ordering is usually based on the speed and capacity of
the devices that the storage pools use. In IBM Tivoli
Storage Manager, the storage hierarchy is defined by
identifying the next storage pool in a storage pool
definition. See storage pool.
storage pool. A named set of storage volumes that is
the destination that the IBM Tivoli Storage Manager
server uses to store client data. A storage pool stores
Glossary
1169
backup versions, archive copies, and files that are

migrated from space manager client nodes. You back
up a primary storage pool to a copy storage pool. See
primary storage pool and copy storage pool.
storage pool volume. A volume that has been
assigned to a storage pool. See volume, copy storage pool,
and primary storage pool.
storage privilege class. A privilege class that allows
an administrator to control how storage resources for
the server are allocated and used, such as monitoring
the database, the recovery log, and server storage.
Authority can be restricted to certain storage pools. See
also privilege class.
stub file. A file that replaces the original file on a
client node when the file is migrated from the client
node to server storage by Tivoli Storage Manager for
Space Management.
subscription. In a Tivoli environment, the process of
identifying the subscribers that the profiles are
distributed to. For IBM Tivoli Storage Manager, this is
the process by which a managed server requests that it
receive configuration information associated with a
particular profile on a configuration manager. See
managed server, configuration manager, and profile.
system privilege class. A privilege class that allows an
administrator to issue all server commands. See also
privilege class.
T
tape library. A term used to refer to a collection of
drives and tape cartridges. The tape library may be an
automated device that performs tape cartridge mounts
and demounts without operator intervention.
tape volume prefix. A device class attribute that is the
high-level-qualifier of the file name or the data set
name in the standard tape label.
target node. A client node for which other client
nodes (called agent nodes) have been granted proxy
authority. The proxy authority allows the agent nodes
to perform operations such as backup and restore on
behalf of the target node, which owns the data being
operated on.
target server. A server that can receive data sent from
another server. Contrast with source server. See also
virtual volumes.
U
UCS-2. An ISO/IEC 10646 encoding form, Universal
Character Set coded in 2 octets. The IBM Tivoli Storage
1170
Manager client on Windows uses the UCS-2 code page

when the client is enabled for Unicode.
Unicode Standard. A universal character encoding
standard that supports the interchange, processing, and
display of text that is written in any of the languages of
the modern world. It can also support many classical
and historical texts and is continually being expanded.
The Unicode Standard is compatible with ISO/IEC
10646. For more information, see www.unicode.org.
UTF-8. Unicode transformation format - 8. A
byte-oriented encoding form specified by the Unicode
Standard.
V
validate. To check a policy set for conditions that can
cause problems if that policy set becomes the active
policy set. For example, the validation process checks
whether the policy set contains a default management
class.
version. A backup copy of a file stored in server
storage. The most recent backup copy of a file is the
active version. Earlier copies of the same file are
inactive versions. The number of versions retained by
the server is determined by the copy group attributes
in the management class.
virtual file space. A representation of a directory on a
network-attached storage (NAS) file system as a path to
that directory. A virtual file space is used to back up
the directory as a file space in IBM Tivoli Storage
Manager server storage.
virtual volume. An archive file on a target server that
represents a sequential media volume to a source server.
volume. The basic unit of storage for the IBM Tivoli
Storage Manager database, recovery log, and storage
pools. A volume can be an LVM logical volume, a
standard file system file, a tape cartridge, or an optical
cartridge. Each volume is identified by a unique
volume identifier. See database volume, scratch volume,
and storage pool volume.
volume history file. A file that contains information
about: volumes used for database backups and
database dumps; volumes used for export of
administrator, node, policy, or server data; and
sequential access storage pool volumes that have been
added, reused, or deleted. The information is a copy of
the same types of volume information in the IBM Tivoli
Storage Manager database.

Program Number: 5608-HSM

5608-ISM
5608-ISX
5608-SAN
5608-ARM
5698-A11
5698-A12
5698-A13
5698-A25
5608-ACS
5608-APD
5608-APE
5608-APW
5608-APR
5608-CCS
SC32-0140-01
Printed in USA

TSM 5 5 Messages PDF

Uploaded by

Document Information

Original Title

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

TSM 5 5 Messages PDF

Uploaded by

Copyright:

Available Formats

Tivoli Storage Manager

Tivoli Storage Manager

New, Changed, and Deleted Messages

Data Protection for Snapshot Devices for mySAP

Summary of Changes for Version 5.5

Chapter 2. Obtaining Help for IBM Tivoli

Part 2. Server Messages . . . . . . 11

Part 3. Client Messages . . . . . . 643

Part 4. Data Protection Products

Chapter 6. Data Protection for Lotus

Chapter 7. Data Protection for

Chapter 13. Data Protection for Disk

Chapter 8. Data Protection for

Appendix A. API Return Codes with

Chapter 9. Data Protection for Oracle

Chapter 11. Data Protection for

Chapter 12. Data Protection for

IBM Tivoli Storage Manager: Messages

Appendix B. Allocating Additional

Appendix D. Device Errors in AIX

About this Guide

IBM Tivoli Storage Manager Publications

IBM Tivoli Storage Manager Library

IBM Tivoli Storage Manager Messages

IBM Tivoli Storage Manager Performance Tuning Guide

IBM Tivoli Storage Manager Problem Determination Guide

IBM Tivoli Storage Manager for AIX Administrators Guide

IBM Tivoli Storage Manager for AIX Administrators Reference

IBM Tivoli Storage Manager for AIX Installation Guide

IBM Tivoli Storage Manager for HP-UX Administrators Guide

IBM Tivoli Storage Manager for HP-UX Administrators Reference

IBM Tivoli Storage Manager for HP-UX Installation Guide

IBM Tivoli Storage Manager for Linux Administrators Guide

IBM Tivoli Storage Manager for Linux Administrators Reference

IBM Tivoli Storage Manager for Linux Installation Guide

IBM Tivoli Storage Manager for z/OS Administrators Guide

IBM Tivoli Storage Manager for z/OS Administrators Reference

IBM Tivoli Storage Manager for z/OS Installation Guide

IBM Tivoli Storage Manager for Sun Solaris Administrators Guide

IBM Tivoli Storage Manager for Sun Solaris Administrators Reference

IBM Tivoli Storage Manager for Sun Solaris Installation Guide

IBM Tivoli Storage Manager for Windows Administrators Guide

IBM Tivoli Storage Manager for Windows Administrators Reference

IBM Tivoli Storage Manager for Windows Installation Guide

Copyright IBM Corp. 1993, 2007

The following table lists Tivoli Storage Manager client publications.

IBM Tivoli Storage Manager for NetWare: Backup-Archive Clients

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive

IBM Tivoli Storage Manager for Windows: Backup-Archive Clients

IBM Tivoli Storage Manager Using the Application Program Interface

The following table lists publications for application protection products.

IBM Tivoli Storage Manager: Messages

Accessing IBM Tivoli Storage Manager Publications

About this Guide

IBM Tivoli Storage Manager: Messages

New, Changed, and Deleted Messages

New Server Messages

IBM Tivoli Storage Manager: Messages

IBM Tivoli Storage Manager: Messages

IBM Tivoli Storage Manager: Messages

IBM Tivoli Storage Manager: Messages

New, Changed, and Deleted Messages

Changed Server Messages