Tivoli Storage Manager - Computers-itcomputers-it.com/downloads/tsm_41_messages.pdf · Tivoli...

Tivoli StorageManagerMessagesVersion 4 Release 1

Note!Before using this information and the product it supports, be sure to read thegeneral information under “Notices” on page 1387.

This publication is also available in a softcopy form that can be viewed with theIBM® BookManager® READ licensed program or the Adobe Acrobat Reader.

First Edition (July 2000)

This edition applies to Version 4 Release 1 of the Tivoli® Storage Manager for AIX® ,AS/400, HP-UX, Sun Solaris, Windows® (5698-DRM, 5698-TSM); MVS™ and OS/390®

(5697-DRS, 5697-TS9, 5698-DRM, 5698-TSM); Tivoli Data Protection for Lotus® Notes™

(5698-DPN), Tivoli Data Protection for Oracle (5698-DPO), Tivoli Data Protection forMicrosoft® SQL (5698-DPS), Tivoli Data Protection for Microsoft Exchange (5698-DPX),Tivoli Space Manager (5698-SPM) and to all subsequent releases and modifications untilotherwise indicated in new editions.

Order publications through your sales representative or the branch office serving yourlocality.

Your feedback is important in helping to provide the most accurate and high-qualityinformation. If you have comments about this book or any other Tivoli Storage Managerdocumentation, please see “Contacting Customer Support” on page xv.

© Copyright International Business Machines Corporation 1993, 2000. All rightsreserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSAADP Schedule Contract with IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiMessages Not Appearing in This Publication. . . . . . . . . . . . . . . . . . . . . . . . vii

Softcopy Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Tivoli Storage Manager Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Related AS/400 System Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Referenced MVS System Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Related IBM Hardware Products Publications. . . . . . . . . . . . . . . . . . . . . . .xiii

IBM International Technical Support Center Publications (Redbooks). . . . . xiv

Referenced Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Software Developer’s Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Tivoli Storage Manager Web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Contacting Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Reporting a Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Summary of Changes for Tivoli Storage Manager . . . . . xixChanges for Version 4 Release 1—July 2000. . . . . . . . . . . . . . . . . . . . . . . xix

Part I. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Understanding Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Message Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Obtaining Help with Tivoli Storage Manager 9Internet and IBMLink Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Internet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

iiiTivoli Storage Manager Messages

IBMLink/ServiceLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Describing the Error with Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Component Identification Keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Type-of-Failure Keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Command Keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Function Keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Obtaining Online HELP (Get Help on Error Messages). . . . . . . . . . . . . . . . 12

Contacting Your Service Representative. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Running Trace Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Messages That Do Not Appear in This Publication. . . . . . . . . . . . . . . . . . . . 13

Part II. Server Messages: Common and PlatformSpecific (ANR); Client Events Logged to Server(ANE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3. Common and Platform Specific Messages(ANR0100–ANR9999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4. Client Events Logged to Server(ANE4000–4999). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083

Part III. Client Messages . . . . . . . . . . . . . . . . . . . . . . . . 1091

Chapter 5. Client Message Repository File(0100–0199) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093

Chapter 6. Application Program Interface(0200–0479) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097

Chapter 7. Client Common Messages (1000–1999) 1115

iv Version 4 Release 1

Chapter 8. Command-Line Client Messages(1053–3999). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155

Chapter 9. Enterprise Management (2500–2999) 1197

Chapter 10. Client Event Logging (4000–4999) . . . . . . . 1203

Chapter 11. Graphical User Interface Client(5000–5999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213

Chapter 12. Macintosh Backup-Archive Client(6000–6999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229

Chapter 13. Windows Backup-Archive Client(7000–7999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231

Chapter 14. Administrative Command-Line Client(8000–8499) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237

Chapter 15. Tivoli Space Manager (9000–9999) 1249

Part IV. Tivoli Data Protection ApplicationClient Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337

Chapter 16. Tivoli Data Protection for Lotus Notes(0900–0999) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339

Chapter 17. Tivoli Data Protection for MicrosoftSQL (ACO0301–5203) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353

Chapter 18. Tivoli Data Protection for Oracle(0500–0599) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1383

Part V. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1385

vTivoli Storage Manager Messages

Appendix A. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387Programming Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1389

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1390

Appendix B. API Return Codes with Explanations 1393

Appendix C. Allocating Additional Server Memory 1447

Appendix D. I/O Error Code Descriptions for ServerMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1449

Completion Code and Operation Code Values. . . . . . . . . . . . . . . . . . . . . .1450

Completion Code Values Common to All Device Classes. . . . . . . . . 1451

Completion Code Values for Media Changers. . . . . . . . . . . . . . . . . .1452

Completion Code Values for Tape and Optical Drives. . . . . . . . . . . . 1454

Operation Code Values for Tape Library Devices. . . . . . . . . . . . . . .1455

Common Values for ASC and ASCQ Codes. . . . . . . . . . . . . . . . . . . . . . .1456

Windows NT Event Log Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . .1460

Appendix E. Device Errors in AIX System Error Log 1461

Appendix F. Checklist for Contacting your ServiceRepresentative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467

vi Version 4 Release 1

Preface

Tivoli Storage Manager (TSM) is a client/server program thatprovides storage management services to customers in a multivendorcomputer environment. TSM provides an automated, centrallyscheduled, policy-managed backup, archive, and space managementfacility for file servers and workstations.

This publication contains explanations and suggested actions formessages issued by the Tivoli Storage Manager server program forstorage management services, the administrative client graphical userinterface, administrative command line client, and backup-archiveclient.

Messages Not Appearing in This PublicationMessage numbers in the range ANR0100–0120, and any with 9999are not published in this manual. They are considered severe errorsand should be recorded and included in a problem report whencontacting the service representative. The following messages are notpublished in this manual:

CommonMessages

AIX Specific MVS Specific WindowsNT® Specific

HP-UXSpecific

Sun SolarisSpecific

ANR0628I ANR7837S ANR7830E ANR7823S ANR7823SANR0680E ANR7845S ANR7831IANR0702E ANR7846S ANR7832EANR0703E ANR7847S ANR7833IANR0704E ANR7848S ANR7836SANR1592E ANR7837SANR1601E ANR7838SANR2704E ANR7839EANR2705E ANR7850SANR2706E ANR7851SANR2710EANR2711EANR2801EANR2802E

viiTivoli Storage Manager Messages

CommonMessages

AIX Specific MVS Specific WindowsNT® Specific

HP-UXSpecific

Sun SolarisSpecific

ANR2830WANR2840IANR2845IANR2846IANR4024IANR4400IANR4401IANR4696E

Message number ANR7831I and numbers in the rangeANR7900–8199 are AS/400® platform specific messages and are notpublished in this manual. You can obtain the explanation for thesemessages using AS/400 commands such as WRKMSGD to get to the"Work with Message Descriptions" panel. The unpublished messagesare:

ANR7831I ANR7918I ANR7937I ANR7980E ANR7998E ANR8066E ANR8124EANR7900E ANR7919E ANR7938E ANR7981E ANR7999E ANR8067E ANR8125EANR7901E ANR7920E ANR7939E ANR7982E ANR8050E ANR8068E ANR8126IANR7902E ANR7921E ANR7940E ANR7983E ANR8051I ANR8069E ANR8127EANR7903E ANR7922E ANR7941E ANR7984E ANR8052I ANR8070E ANR8128EANR7904E ANR7923E ANR7943E ANR7985I ANR8053I ANR8071E ANR8129EANR7905E ANR7924E ANR7944E ANR7986E ANR8054E ANR8072E ANR8130EANR7906E ANR7925E ANR7946I ANR7987I ANR8055I ANR8095E ANR8131EANR7907E ANR7926E ANR7947I ANR7988I ANR8056E ANR8100I ANR8132EANR7908E ANR7927E ANR7950E ANR7989E ANR8057E ANR8101E ANR8133WANR7909E ANR7928E ANR7951E ANR7990E ANR8058E ANR8102E ANR8134WANR7910I ANR7930I ANR7952E ANR7991E ANR8059E ANR8103I ANR8135EANR7911I ANR7931I ANR7955I ANR7992E ANR8060E ANR8110I ANR8136IANR7912S ANR7932I ANR7959E ANR7993I ANR8061E ANR8111I ANR8137IANR7913S ANR7933I ANR7960E ANR7994I ANR8062E ANR8120I ANR8138IANR7914E ANR7934I ANR7961E ANR7995I ANR8063E ANR8121I ANR8139IANR7915E ANR7935I ANR7962E ANR7996E ANR8064E ANR8122I ANR8140EANR7916E ANR7936I ANR7963E ANR7997E ANR8065E ANR8123I ANR8141I

viii Version 4 Release 1

Message numbers in the range ANE4000–4999 are client eventlogging messages. These messages (or events) are sent to the serverfor distribution to various event logging receivers. The client maysend statistics to the server providing information about a backup orrestore. These statistics are informational and self-explanatorymessages that may be enabled or disabled to the various eventlogging receivers. The following messages are not published in thismanual:

ANE4950 ANE4951 ANE4952 ANE4953 ANE4954 ANE4955 ANE4956ANE4957 ANE4958 ANE4959 ANE4960 ANE4961 ANE4962 ANE4963ANE4964 ANE4965 ANE4966 ANE4967 ANE4968 ANE4969 ANE4970ANE4985 ANE4986 ANE4990 ANE4991 ANE4992 ANE4993 ANE4994

See “Internet and IBMLink Assistance” on page 9 for additionalinformation.

Note: You may receive other messages that are not documented inthis manual. Those messages may have been created after thismanual was published. Use the online help facility to displaythe help text specific to the message.

Softcopy PublicationsFor the AIX and Windows NT operating systems, softcopy TSMpublications are included with the TSM product code.

The TSM library is available in softcopy on the followingCD-ROMs:

Title OrderNumber

MVS Collection Kit SK2T-0710

VM Collection Kit SK2T-2067

OS/390 Collection Kit SK2T-6700

Transaction Processing and Data Collection Kit SK2T-0730

ixTivoli Storage Manager Messages

Tivoli Storage Manager PublicationsThe following table lists TSM server publications.

Publication Title Order Number

Tivoli Storage Manager Messages GC35-0405

Tivoli Storage Management Products LicenseInformation

LC23-4470

Tivoli Storage Manager for AIX Quick Start GC35-0402

Tivoli Storage Manager for AIX Administrator’s GuideGC35-0403

Tivoli Storage Manager for AIX Administrator’sReference

GC35-0404

Tivoli Storage Manager, S/390 Edition LicensedProgram Specifications

GI10-4543

Tivoli Disaster Recovery Manager, S/390 EditionLicensed Program Specifications

GI10-4544

Tivoli Storage Manager for MVS and OS/390 QuickStart

GC35-0415

Tivoli Storage Manager for MVS and OS/390Administrator’s Guide

GC35-0416

Tivoli Storage Manager for MVS and OS/390Administrator’s Reference

GC35-0417


LC23-4470

Tivoli Storage Manager for Windows Quick Start GC35-0409

Tivoli Storage Manager for Windows Administrator’sGuide

GC35-0410

Tivoli Storage Manager for Windows Administrator’sReference

GC35-0411


LC23-4470

Tivoli Storage Manager for HP-UX Quick Start GC35-0412

Tivoli Storage Manager for HP-UX Administrator’sGuide

GC35-0413

Tivoli Storage Manager for HP-UX Administrator’sReference

GC35-0414

x Version 4 Release 1



LC23-4470

Tivoli Storage Manager for AS/400 Quick Start GC35-0317

Tivoli Storage Manager for AS/400 Administrator’sGuide

GC35-0315

Tivoli Storage Manager for AS/400 Administrator’sReference

GC35-0316


LC23-4470

Tivoli Storage Manager for Sun Solaris Quick Start GC35-0406

Tivoli Storage Manager for Sun Solaris Administrator’sGuide

GC35-0407

Tivoli Storage Manager for Sun Solaris Administrator’sReference

GC35-0408

The following table lists the TSM client publications.


Tivoli Space Manager for UNIX Using the HierarchicalStorage Management Clients

SH26-4115

Tivoli Storage Manager for Macintosh Using theBackup-Archive Client

SH26-4120

Tivoli Storage Manager for UNIX Using theBackup-Archive Clients

SH26-4122

Tivoli Storage Manager for NetWare Using theBackup-Archive Client

SH26-4116

Tivoli Storage Manager for Windows Using theBackup-Archive Client

SH26-4117

Tivoli Storage Manager Installing the Clients SH26-4119

Tivoli Storage Manager Quick Reference for theBackup-Archive Clients

SH26-4118

Tivoli Storage Manager Trace Facility Guide SH26-4121

Tivoli Storage Manager Using the Application ProgramInterface

SH26-4123

xiTivoli Storage Manager Messages


Tivoli Storage Manager AFS/DFS Backup Clients SH26-4124

The following table lists Tivoli Data Protection publications.

Publication TitleOrderNumber

Tivoli Data Protection for Informix Installation and User’sGuide

SH26-4095

Tivoli Data Protection for Lotus Domino, S/390 EditionLicensed Program Specifications

GI10-4545

Tivoli Data Protection for Lotus Domino for UNIX Installationand User’s Guide

SH26-4088

Tivoli Data Protection for Lotus Domino for Windows NTInstallation

GC26-7320

Tivoli Data Protection for Lotus Notes on AIX Installation andUser’s Guide

SH26-4067

Tivoli Data Protection for Lotus Notes on Windows NTInstallation and User’s Guide

SH26-4065

Tivoli Data Protection for Microsoft Exchange ServerInstallation and User’s Guide

SH26-4110

Tivoli Data Protection for Microsoft SQL Server Installationand User’s Guide

SH26-4111

Tivoli Data Protection for Oracle for UNIX Installation andUser’s Guide

SH26-4112

Tivoli Data Protection for Oracle for Windows NT Installationand User’s Guide

SH26-4113

Tivoli Data Protection for R/3 Version 2.7 Installation andUser’s Guide

SC33-6388

Tivoli Data Protection for Workgroups for Windows NT User’sGuide

GC35-0359

Tivoli Data Protection for Workgroups for NetWare User’sGuide

GC32-0444

xii Version 4 Release 1

Related AS/400 System PublicationsThe following table lists related AS/400 publications.


OS/400 CL Reference SC41-3722

AS/400 Local Device Configuration SC41-3121

AS/400 Publications Reference SC41-3003

AS/400 Automated Tape Library Planning andManagement

SC41-3309

OS/400 Work Management SC41-3306

Backup Recovery and Media Services for OS/400 SC41-3345

OS/400 Backup and Recovery – Basic SC41-3304

OS/400 Backup and Recovery – Advanced SC41-3305

OS/400 Communications Configuration SC41-3401

OS/400 Remote Work Station Support SC41-3402

Referenced MVS System PublicationsThe following table lists referenced MVS publications.


RACF Security Administrator’s Guide SC28-1340

DFSMS/MVS DFSMSrmm Implementation andCustomization Guide

SC26-4932

DFSMS/MVS DFSMSrmm Guide and Reference SC26-4931

Related IBM Hardware Products PublicationsThe following table lists related IBM hardware productspublications.

Title Order Number

IBM 3490 Magnetic Tape Subsystem EnhancedCapability Models E01 and E11 User’s Guide

GA32-0298

xiiiTivoli Storage Manager Messages

Title Order Number

IBM SCSI Tape Drive, Medium Changer, and LibraryDevice Drivers: Installation and User’s Guide

GC35-0154

IBM 3494 Tape Library Dataserver Operator’s Guide GA32-0280

IBM Magstar 3590 Tape Subsystem Operator’s GuideGA32-0330

IBM 3495 Tape Library Dataserver Models L20, L30,L40, and L50 Operator’s Guide

GA32-0235

IBM 3570 Magstar MP Tape Subsystem Operator’sGuide

GA32-0345

IBM International Technical Support CenterPublications (Redbooks)

The International Technical Support Center (ITSC) publishesredbooks, which are books on specialized topics such as using TSMto back up databases. You can order publications through your IBMrepresentative or the IBM branch office serving your locality. Youcan also search for and order books of interest to you by visiting theIBM Redbooks home page on the World Wide Web at this address:

http://www.redbooks.ibm.com/redbooks

Referenced PublicationsThe following table lists other publications referenced in thismanual:

Title OrderNumber

MVS/ESA Programming: Authorized Assembler ServicesGuide

GC28-1467

IBM 3494 Tape Library Dataserver User’s Guide: MediaLibrary Device Driver for AS/400

GC35-0153

MVS/DFP V3R3 Macro Instructions for Data Sets SC26-4747

IBM Local Area Network Technical Reference SC30-3383

LAN Technical Reference IEEE 802.2 & NETBIOS APIs SC30-3587

xiv Version 4 Release 1

Title OrderNumber

AS/400 System API Reference SC41-3801

Software Developer’s ProgramThe IBM Storage Systems Division (SSD) Software Developer’sProgram provides a range of services to software developers whowant to use the TSM application program interface (API).Information about the SSD Software Developer’s Program isavailable in the SSD Software Developer’s Program InformationPackage.

To obtain the Software Developer’s Program Information Package:1. Call 800-4-IBM-SSD (800-442-6773). Outside the U.S.A., call

408-256-0000.2. Listen for the Storage Systems Division Software Developer’s

Program prompt.3. Request the Software Developer’s Program Information Package.

Tivoli Storage Manager Web siteAll TSM publications are available on the TSM home page on theWorld Wide Web at the following address:

http://www.tivoli.com/support/storage_mgr/tivolimain.html

By accessing the TSM home page, you can access subjects thatinterest you. You can also keep up-to-date with the newest TSMproduct information.

Contacting Customer SupportFor support for this or any Tivoli product, you can contact TivoliCustomer Support in one of the following ways:

¶ Visit the Tivoli Storage Manager technical support Web site athttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

xvTivoli Storage Manager Messages

http://www.tivoli.com/support/storage_mgr/tivolimain.html

¶ Submit a problem management record (PMR) electronically atIBMSERV/IBMLINK . You can access IBMLINK athttp://www2.ibmlink.ibm.com.

¶ Submit a problem management record (PMR) electronically athttp://www.tivoli.com/support. See “Reporting a Problem” onpage xvii for details.

¶ Send e-mail to [email protected].

Customers in the United States can also call 1-800-TIVOLI8(1-800-848-6548). For product numbers 5697-TS9, 5697-DRS or5697-DPM call 1-800-237-5511.

International customers should consult the Web site for customersupport telephone numbers.

You can also review theCustomer Support Handbook, which isavailable on our Web site athttp://www.tivoli.com/support/handbook/.

When you contact Tivoli Customer Support, be prepared to provideidentification information for your company so that supportpersonnel can readily assist you. Company identification informationmay also be needed to access various online services available onthe Web site.

The support Web site offers extensive information, including a guideto support services (the Customer Support Handbook); frequentlyasked questions (FAQs); and documentation for all Tivoli products,including Release Notes, Redbooks, and Whitepapers. Thedocumentation for some product releases is available in both PDFand HTML formats. Translated documents are also available forsome product releases.

You can order documentation by e-mail at [email protected]. Pleaseprovide the publication number, part number, or order number of thedesired document. Alternatively, you can provide the document title,version number, and date of publication.

xvi Version 4 Release 1

We are very interested in hearing about your experience with Tivoliproducts and documentation. We also welcome your suggestions forimprovements. If you have comments or suggestions about ourdocumentation, please contact us in one of the following ways:

¶ Send e-mail to [email protected].

¶ Complete our customer feedback survey athttp://www.tivoli.com/support/feedback.

Reporting a ProblemPlease have the following information ready when you report aproblem:

¶ The Tivoli Storage Manager server version, release,modification, and service level number. You can get thisinformation by entering theQUERY STATUS command at the TSMcommand line.

¶ The Tivoli Storage Manager client version, release, modification,and service level number. You can get this information byenteringdsmc at the command line.

¶ The communication protocol (for example, TCP/IP), version, andrelease number you are using.

¶ The activity you were doing when the problem occurred, listingthe steps you followed before the problem occurred.

¶ The exact text of any error messages.

TranslationsSelected TSM publications have been translated into languages otherthan American English. Contact your service representative for moreinformation about the translated publications and whether thesetranslations are available in your country.

xviiTivoli Storage Manager Messages

xviii Version 4 Release 1

Summary of Changes for Tivoli Storage Manager

This section summarizes changes made to the Tivoli StorageManager product and this publication. Refer to theTivoli StorageManager Administrator’s Guideand theTivoli Storage ManagerAdministrator’s Referencefor details.

Changes for Version 4 Release 1—July 2000The following changes are made for this edition:

Support for Mobile ClientsThis function allows mobile users to backup files andafterwards make subsequent backups to the portion(asubfile)of the file that has changed, rather than the entirefile.

This enhancement makes it possible for remote or mobileusers, using modems with limited bandwidth to reduceconnection time, network traffic, and the time it takes to doa backup. This enhancement also uses encryption to protectclients’ data.

Support and Enhancements for Windows 2000Removable Storage Manager (RSM) is a service includedwith Windows 2000 that facilitates communication amongapplications, robotic changers, and media libraries. It enablesmultiple applications to share local robotic media librariesand tape or disk drives, and manage removable media with asingle-server system. RSM is managed by using a MicrosoftManagement Console snap-in.

Support and Enhancements for Windows NTTivoli Removable Media Manager (TRMM) is a serviceincluded with Windows NT that provides the same functionas RMS. TRMM is managed by using a Web-based interfacesimilar to Tivoli Storage Manager’s administrative Webinterface.

xixTivoli Storage Manager Messages

LAN-Free Data Movement in a Storage Area Network (SAN)Environment

Tivoli Storage Manager has been enhanced to supportLAN-free data movement SAN environments. The supportallows client data to move directly from the client system toa server-managed storage device on the SAN, instead ofmoving first from the client system to the server over theLAN and then to the device.

This enhancement reduces data movement on the LAN sothat more bandwidth is available to other applications. Thisenhancement also increases tape library sharing for multipleTSM servers.

Storage Area Network (SAN) Tape Library SharingTivoli Storage Manager takes advantage of SAN-attachedtape libraries by sharing devices among TSM servers thatuse the same operating system. One of the servers acts as thelibrary manager and the other servers are library clients.

LicensingA client is now licensed as amanaged system. A managedsystem can be a client or server that requires backup servicesfrom the TSM server. Each managed system that moves datato and from storage over a local area network requires aManaged System for LAN license. Each managed systemthat moves data to and from storage over a storage areanetwork requires a Managed System for SAN license. Thefollowing table lists changes to license names:

Table 1. License Name ChangesFormer name Current name Notes

Client Connections Managed System forLAN and ManagedSystem for SAN

A managed system thatmoves data to and fromstorage both on a LANand on a SAN, requiresonly the ManagedSystem for SANlicense.

xx Version 4 Release 1

Table 1. License Name Changes (continued)Former name Current name Notes

Client Connections Managed System forLAN

OpenSystem AFS/DFS Support The S/390 platformincludes the S/390UNIX client as part ofManaged System forLAN.

Extended DeviceSupport

Managed Library

xxiTivoli Storage Manager Messages

xxii Version 4 Release 1

I — Introduction

1Tivoli Storage Manager Messages

2 Version 4 Release 1

Introduction

Tivoli Storage Manager (TSM) is an enterprise-wide storagemanagement application for the network. It provides automatedstorage management services to multivendor workstations, personalcomputers, and local area network (LAN) file servers. TSM includesthe following components:

ServerAllows a server system to provide backup, archive, andspace management services to workstations. The servermaintains a database and recovery log for TSM resources,users, and user data.

The server controls the TSM server’s storage, called storagepools. These are groups of random and sequential accessmedia that store backed up, archived, and space-managedfiles.

You can set up multiple servers in your enterprise network tobalance storage, processor, and network resources. TSMallows you to manage and control multiple servers from asingle interface that runs in a web browser (the enterpriseconsole).

Administrative clientAllows administrators to control and monitor serveractivities, define management policies for client files, and setup schedules to provide services at regular intervals.Administrative functions are available from an administrativeclient command line and from a web browser interface.

1


1.Introduction

Backup-archive clientAllows users to maintain backup versions of their files,which they can restore if the original files are lost ordamaged. Users can also archive files for long-term storageand retrieve the archived files when necessary. Users oradministrators can register workstations and file servers asclient nodes with an TSM server.

Hierarchical storage management (HSM) clientProvides space management services for workstations onsome platforms. TSM users can free workstation storage bymigrating less frequently used files to server storage. Thesemigrated files are also calledspace-managed files. Users canrecall space-managed files automatically simply by accessingthem as they normally would.

Application programming interface (API)Allows users to enhance existing applications with backup,archive, restore, and retrieve services. When users install theTSM API client on their workstations, they can register asclient nodes with an TSM server.

This chapter contains information to help you understand themessages issued by the Tivoli Storage Manager (TSM):¶ Server program¶ Administrative client graphical user interface¶ Administrative command line client¶ Backup-archive client¶ Space-management client

Messages can appear on the server console, the administrative client,an operator terminal, the administrative graphical user interface, thebackup-archive client, or the space-management client.

TSM provides an activity log to help the administrator track serveractivity and monitor the system.

The activity log contains messages generated by the server and isstored in the database. To access the activity log from theadministrative graphical user interface, select the SERVER icon. Theserver automatically deletes messages from the activity log after they


have passed the specified retention period. Any messages sent to theserver console are stored in the activity log. Examples of the typesof messages stored in the activity log include:¶ When client sessions start or end¶ When migration starts or ends¶ When backed up files are expired from data storage¶ Any output generated from background processes

Understanding MessagesThe following examples illustrate the format used in this publicationto describe TSM messages:

¶ Messages that begin with prefixANE and are in range4000–4999 originate from the backup-archive client. Thesemessages (or events) are sent to the server for distribution tovarious event logging receivers.

¶ The client may send statistics to the server providing informationabout a backup or restore. These statistics are informationalmessages that may be enabled or disabled to the various eventlogging receivers. These messages are not published in thismanual.

¶ Messages that begin with prefixANR originate from the server.

¶ Messages that begin with prefixANS originate from thebackup-archive or space management clients.

¶ ANS messages that are in range 5000–5999 and 8000–8999originate from the administrative client.

¶ Messages that begin with prefixACO and are in range0301–5203 originate from the administrative client. These aremessages for Tivoli Data Protection Microsoft SQL Server.

Message FormatThe following examples describe the TSM message format:


1.Introduction

The callouts to the right identify each part of the format.

Message variables in the message text appear in italics. The serverand client messages fall into the following categories:

¶ Common messages that pertain to all TSM server platforms

¶ Platform specific messages that pertain to each operatingenvironment for the server and the client

¶ Messages that pertain to application clients

How to Read a Return Code MessageMany different commands can generate the samereturn code. Thefollowing examples are illustrations of two different commandsissued that result in the same return code; therefore, you must readthe descriptive messagefor the command.


Example One for QUERY EVENT Command

Example Two for DEFINE VOLUME Command


1.Introduction

Obtaining Help with TivoliStorage Manager

This section describes the following:

¶ How to obtain help with processing errors by using Internet andIBMLink ™/ServiceLink

¶ How to describe errors with keywords

¶ How to obtain online message help

¶ What information to have available when you contact yourservice representative

Internet and IBMLink AssistanceTSM message help explanations may suggest that you contact yourservice representative for additional help with processing errors.

Online help is available through Internet and IBMLink/ServiceLink.

InternetIf your installation has access to the Internet, the latest server andclient PTFs (maintenance updates) are available on the anonymousftp (file transfer protocol) server. The machine name isindex.storsys.ibm.com.

IBMLink/ServiceLinkIf your installation has access to IBMLink/ServiceLink, aninteractive online database program, you can:

2


2.O

btainingH

elpw

ithTivoliS

torageM

anager

¶ Search for an existing authorized program analysis report(APAR) that is similar to your problem.

¶ Search for an available program temporary fix (PTF) for theexisting APAR.

¶ Order the PTF if it is available.

¶ Create an Electronic Technical Response (ETR) problem reportto get assistance from an TSM service representative.

Describing the Error with KeywordsWhen you use IBMLink/Servicelink or call your servicerepresentative, accurately describe the problem so that the servicerepresentative may quickly help you solve the problem. Identify theprocessing error with a full set of keywords whenever possible. Akeyword is a word or an abbreviation used to describe a singleaspect of a program failure. Each keyword describes an aspect of aprocessing error.

The following example displays the necessary set of keywords:

56480200n R312 type command function

Where Represents56480200n Component identification keywordR312 Release level keywordtype Type-of-failure keywordcommand Command keywordfunction Function keyword

Component Identification KeywordThe component identifiers for TSM are listed below:

Server Platform Component IDDRM 5698-DRMAIX 5698-TSMAS/400 5698-TSMHP-UX 5698-TSMSun Solaris 5698-TSM


Server Platform Component IDWindows 5698-TSMMVS and OS/390 5697-DRS, 5697-TS9, 5698-DRM, 5698-TSM

Type-of-Failure KeywordThe following keywords identify the type of failure that may occur:

Keyword DescriptionABENDxxx Use this keyword when the system ends abnormally.INCORROUT Use this keyword when incorrect output is received or

expected output is missing.LOOP Use this keyword if a part of the program code runs

endlessly; include situations in which a part of theoutput repeats continuously.

MSGANRnnnnt(or)MSGANSnnnnt

Use this keyword when a message:

¶ Indicates an internal program error

¶ Is issued in a set of conditions that should notcause it to be issued

¶ Contains invalid or missing data

See “Understanding Messages” on page 5 for adescription of the message format.

WAIT Use this keyword when you receive no response withina reasonable time that can be perceived as poorresponse or poor performance.

xxxxxxxxxx(Documentation)

Use this keyword when a programming problemappears to be caused by incorrect, missing, orambiguous information in one of the TSM publications.Enter the order number of the publication in place ofxxxxxxxxxx. Include the letter prefix and versionnumber, but omit all hyphens, for example,GC35040500. Refer to “Tivoli Storage ManagerPublications” on page x for a list of the TSMpublications.

PERFM Use this keyword as a closing code for an APAR.


2.O

btainingH

elpw

ithTivoliS

torageM

anager

Command KeywordBuild keywords based on TSM commands. Refer toAdministrator’sReferencefor a list of the commands.

Function KeywordUse keywords that refer to basic TSM functions such as backup,retrieve, archive, recover, migrate, and export-import.

Obtaining Online HELP (Get Help on Error Messages)Use the HELP command on the server console or administrativecommand line client to display information about server andadministrative command line client messages. Use the HELPcommand on the backup-archive client to display information aboutbackup-archive client messages.

The Helperror message numbercommand displays the help textspecific to the error message. You can get help information on servermessages (prefixed by ANR), and administrative command line andbackup-archive client messages (prefixed by ANS or ANE) exceptthose specific to the administrative graphical user interface client.

Contacting Your Service RepresentativeWhen you contact your service representative after the properdiagnostic procedures have been followed and user specificationshave been checked for accuracy, you should have on hand theinformation listed in “Checklist for Contacting your ServiceRepresentative” on page 1465.

Running Trace CommandsYour service representative may request that you run tracecommands to perform diagnostic functions. The output from thetrace commands is classified as Diagnosis, Modification, and TuningInformation.


Messages That Do Not Appear in This PublicationSee “Messages Not Appearing in This Publication” on page vii forinformation about messages that appear online but are notdocumented in this publication.


2.O

btainingH

elpw

ithTivoliS

torageM

anager

II — Server Messages:Common and PlatformSpecific (ANR); Client EventsLogged to Server (ANE)


Common and Platform SpecificMessages (ANR0100–ANR9999)

This chapter contains the common and platform-specific servermessages. The organization of the messages are grouped by themessage prefix ANR and documented in ascending numeric order. Ifa message is platform specific and a duplicate, the appropriateplatform name is added after the message number and it is alsodocumented alphabetically by platform name.

ANR0100E Source file(line number): Error error codecreating table ″table name″.

Explanation: An internal error has occurred in an attempt to create a serverdatabase table. This message always accompanies another error message andprovides more detail about that error.

System Action: The activity that generated this error fails.

User Response: Contact your service representative.

ANR0101E Source file(line number): Error error codeopening table″table name″.

Explanation: An internal error has occurred in an attempt to access a serverdatabase table. This message always accompanies another error message andprovides more detail about that error.



3


3.C

omm

onand

Platform

Specfic

Messages

ANR0102E Source file(line number): Error error codeinserting row in table ″table name″.

Explanation: An internal error has occurred in an attempt to add data to a serverdatabase table. This message always accompanies another error message andprovides more detail about that error.



ANR0103E Source file(line number): Error error codeupdating row in table ″table name″.

Explanation: An internal error has occurred in an attempt to update data in aserver database table. This message always accompanies another error message andprovides more detail about that error.



ANR0104E Source file(line number): Error error codedeleting row from table ″table name″.

Explanation: An internal error has occurred in an attempt to remove data from aserver database table. This message always accompanies another error message andprovides more detail about that error.



ANR0105E Source file(line number): Error setting search bounds for table ″table name″.

Explanation: An internal error has occurred in an attempt to access data in aserver database table. This message always accompanies another error message andprovides more detail about that error.



ANR0106E Source file(line number): Unexpected error error codefetching row in table ″tablename″.

Explanation: An internal error has occurred in an attempt to access data in aserver database table. This message always accompanies another error message andprovides more detail about that error.




ANR0107W Source file(line number): Transaction transaction IDwas not committed due toan internal error.

Explanation: An internal error was detected during transaction commit. Thismessage should be preceded by another error message which provides more detailabout that error.



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.


User Response: Allocate additional storage to the server. For details, issue HELPMEMORY to display the information online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR0110E An unexpected system date has been detected; the server is disabled. Use theACCEPT DATE command to establish the current date as valid.

Explanation: The server has noted that the current system date is suspect. It isearlier than the server install date or has suddenly moved into the future by 30 daysor more.

System Action: The server is disabled for client access. Server expiration will notexecute.

User Response: If the current system date is not valid, reset the date. Use theACCEPT DATE command to establish the current date as valid on the server. Afterexecuting this command, you can use the ENABLE SESSIONS command to enablethe server for client sessions.

ANR0130E DiagnosticID: Server LOG space exhausted.

Explanation: There is no space to write data to the server recovery log.


User Response: To increase the amount of log space available to the server, anauthorized administrator can add log volumes by using the DEFINE LOGVOLUMEcommand, and extend the size of the log by using the EXTEND LOG command.


3.C

omm

onand

Platform

Specfic

Messages

ANR0131E DiagnosticID: Server DB space exhausted.

Explanation: There is no space to write data to the server database.


User Response: To increase the amount of database space available to the server,an authorized administrator can add database volumes by using the DEFINEDBVOLUME command, and extend the size of the database by using the EXTENDDB command.

ANR0132E DiagnosticID: Memory allocation failed: object object name, sizesize.

Explanation: The server cannot obtain enough memory to create the objectnamed.


User Response: Allocate additional storage to the server. For details, issue HELPMEMORY to display the information online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR0200I Recovery log assigned capacity issizemegabytes.

Explanation: The amount of space allocated to the recovery log is shown.

System Action: None.

User Response: None.

ANR0201I Database assigned capacity issizemegabytes.

Explanation: The amount of space allocated to the database is shown.



ANR0202W Database volumevolume namevaried offline due to excessive read errors.

Explanation: The database volume shown has been varied offline because toomany 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 Database volumevolume namevaried offline due to excessive write errors.

Explanation: The database volume shown has been varied offline because toomany write errors have been encountered.


User Response: Correct the cause of the write errors.

ANR0204W Recovery log volumevolume namevaried offline due to excessive read errors.

Explanation: The recovery log volume shown has been varied offline because toomany read errors have been encountered.


User Response: Correct the cause of the read errors.

ANR0205W Recovery log volumevolume namevaried offline due to excessive write errors.

Explanation: The recovery log volume shown has been varied offline because toomany write errors have been encountered.


User Response: Correct the cause of the write errors.

ANR0206W Partial write detected on database volumevolume name, logical pagelogicalpage number(physical pagephysical page number).

Explanation: During a write of a database page, an error occurred so that the pagewas not completely written to disk.

System Action: The failed I/O operation is retried on a mirrored volume.

User Response: See accompanying messages for information about the volume inerror.

ANR0207E Page address mismatch detected on database volumevolume name, logical pagelogical page number(physical pagephysical page number); actual: logical pagenumber.

Explanation: During a read of a database page, the page does not contain theexpected page address.




3.C

omm

onand

Platform

Specfic

Messages

ANR0208W Partial write detected on recovery log volumevolume name, logical pagelogicalpage number(physical pagephysical page number).

Explanation: During a write of a recovery log page, an error occurs so that thepage is not completely written to disk.



ANR0209E Page address mismatch detected on recovery log volumevolume name, logicalpage logical page number(physical pagephysical page number); actual: logicalpage number.

Explanation: During a read of a recovery log page, the page does not contain theexpected page address.



ANR0210S Inconsistency found in LVM data pagepage number- partial write detected.

Explanation: During a write of an LVM internal page, an error occurs so that thepage is not completely written to disk.



ANR0211S Inconsistency found in LVM data pagepage number- page address mismatch(actual page number).

Explanation: During a read of an LVM internal page, the page does not containthe expected page address.



ANR0212E Unable to read disk definition file file specification.

Explanation: At startup, the server cannot read the indicated file in order to obtaina list of disk volumes to mount.

System Action: Server initialization fails.


User Response: Use a text editor to recreate the file; it should contain one linewith the name of a single log or database volume. Then restart the server.

ANR0213W Unable to rewrite disk definition file.

Explanation: An error occurs trying to update the disk definition file.


User Response: Attempt to determine the cause of the write error and correct it.

ANR0214W Database volumevolume nameis in the offline state - VARY ON required.

Explanation: At system startup, the server finds that the specified databasevolume 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.

ANR0215W Recovery log volumevolume nameis in the offline state - VARY ON required.

Explanation: At system startup, the server finds that the recovery log volumeshown 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 volumevolume nameis in the ″stale″ state - synchronization processstarted.

Explanation: At system startup, the server finds that the database volume shownis not synchronized.

System Action: A process is started to synchronize the volume.


ANR0217I Recovery log volumevolume nameis in the ″stale″ state - synchronizationprocess started.

Explanation: At system startup, the server finds that the recovery log volumeshown is not synchronized.

System Action: A process is started to synchronize the volume.



3.C

omm

onand

Platform

Specfic

Messages

ANR0218I Unable to install database volumevolume name- capacity must be at least 5megabytes.

Explanation: An attempt has been made to add a database volume that is smallerthan the server minimum.

System Action: The volume is not added.

User Response: Increase the size of the volume or supply another larger volume.

ANR0219I Unable to install recovery log volumevolume name- capacity must be at least 5megabytes.

Explanation: An attempt has been made to add a recovery log volume that issmaller 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 Synchronization of database volumevolume namestarted as processprocess ID.

Explanation: A background process was started to synchronize the contents of thedatabase volume shown with its copy volume. The background process was assignedthe process ID shown.

System Action: The background process starts to synchronize the volume andserver operation continues.

User Response: The administrator may query the status of the background processby using the QUERY PROCESS command, or cancel the process by using theCANCEL PROCESS command.

ANR0221I Synchronization of recovery log volumevolume namestarted as processprocessID.

Explanation: A background process was started to synchronize the contents of therecovery log volume shown with its copy volume(s). The background process wasassigned the process ID shown.

System Action: The background process starts to synchronize the volume andserver operation continues.

User Response: The administrator may query the status of the background processby using the QUERY PROCESS command, or cancel the process by using theCANCEL PROCESS command.


ANR0222E Error action disk definition file file specification.

Explanation: An error occurred creating or changing the disk definition file.


User Response: Attempt to determine the cause of the write error and correct it.

ANR0223E Error writing list of disks to disk definition file.

Explanation: The disk definition file cannot be written.

System Action: Installation ends.

User Response: Determine the cause of the write error and correct it.

ANR0224E Volumevolume nameis specified more than once - server installation failed.

Explanation: The specified volume name was specified more than once in theserver installation execution.

System Action: Installation ends.

User Response: Reinitialize the server install specifying a unique name for eachdatabase and recovery log volume.

ANR0230E Synchronization process failed for database volumevolume name.

Explanation: The process that was attempting to synchronize the database volumeshown 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 volumevolume name.

Explanation: The process that was attempting to synchronize the recovery logvolume shown has failed.



ANR0232I Synchronization process canceled for database volumevolume name.

Explanation: The process that was attempting to synchronize the database volumeshown has been canceled.



3.C

omm

onand

Platform

Specfic

Messages

User Response: If desired, issue a VARY ONLINE command to start anothersynchronize process.

ANR0233I Synchronization process canceled for recovery log volumevolume name.

Explanation: The process that was attempting to synchronize the database volumeshown has been canceled.


User Response: If desired, issue a VARY ONLINE command to start anothersynchronize process.

ANR0234I Synchronization complete for database volumevolume name.

Explanation: The synchronization process for the database volume named hasfinished successfully.

System Action: The volume is varied online.


ANR0235I Synchronization complete for recovery log volumevolume name.

Explanation: The synchronization process for the recovery log volume named hasfinished successfully.

System Action: The volume is varied online.


ANR0240E Deletion process failed for database volumevolume name.

Explanation: The process that was attempting to delete the database volumeshown has failed.

System Action: The volume is not deleted.


ANR0241E Deletion process failed for recovery log volumevolume name.

Explanation: The process that was attempting to delete the recovery log volumeshown has failed.




ANR0242I Deletion process canceled for database volumevolume name.

Explanation: The process that was attempting to delete the database volumeshown has been canceled.



ANR0243I Deletion process canceled for recovery log volumevolume name.

Explanation: The process that was attempting to delete the recovery log volumeshown has been canceled.



ANR0244I Deletion complete for database volumevolume name.

Explanation: The delete process for the database volume named has finishedsuccessfully.

System Action: The volume is deleted.


ANR0245I Deletion complete for recovery log volumevolume name.

Explanation: The delete process for the recovery log volume named has finishedsuccessfully.

System Action: The volume is deleted.


ANR0246E Error reading logical page logical page number(physical pagephysical pagenumber) from database volumevolume name.

Explanation: An error has been encountered when attempting to read a page fromthe specified database volume.

System Action: The failed I/O operation is retried on a mirrored volume, ifavailable.

User Response: See accompanying messages for information about the volume inerror. If the error persists and another mirrored copy of the volume is available, thefailing volume should be taken offline by using the VARY OFF command, andrepaired. Otherwise, halt the server and repair the volume. Then restart the server.


3.C

omm

onand

Platform

Specfic

Messages

ANR0247I Database pagelogical page numbersuccessfully read from an alternate copy onvolume volume name.

Explanation: After a read error, the server is able to read the desired page fromanother synchronized mirrored volume.

System Action: Processing continues.


ANR0248E Unable to read database pagelogical page numberfrom any alternate copy.

Explanation: After a read error, the server is unable to read the desired page fromanother mirrored volume because no other mirrored volume is in the synchronizedstate. This message is normally preceded by a message indicating which volumefailed.

System Action: Processing is ended.

User Response: You can repair the failed volume by halting the server andcorrecting the volume errors.

ANR0249E Error reading logical page logical page number(physical pagephysical pagenumber) from recovery log volume volume name.

Explanation: An error has been encountered when attempting to read a page fromthe specified recovery log volume.

System Action: The failed I/O operation is retried on a mirrored volume, ifavailable.

User Response: See accompanying messages for information about the volume inerror. If the error persists and another mirrored copy of the volume is available, thefailing volume should be taken offline, by using the VARY OFF command, andrepaired.

ANR0250I Recovery log pagelogical page numbersuccessfully read from an alternate copyon volume volume name.

Explanation: After a read error, the server is able to read the desired page fromanother synchronized mirrored volume.




ANR0251E Unable to read recovery log pagelogical page numberfrom any alternate copy.

Explanation: After a read error, the server is unable to read the desired page fromanother mirrored volume because no other mirrored volume was in the synchronizedstate. This message is normally preceded by a message indicating which volumefailed.



ANR0252E Error writing logical page logical page number(physical pagephysical pagenumber) to database volumevolume name.

Explanation: An error has been encountered when attempting to write a page tothe specified database volume.

System Action: If a mirrored volume is available then the failing volume is forcedinto the offline state.

User Response: Repair the failing volume, and then use the VARY ON commandto bring the volume back online.

ANR0253E Unable to write database pagelogical page numberto any alternate copy.

Explanation: After a write error, the server is unable to write the desired page toanother mirrored volume because no other mirrored volume is in the synchronizedstate. This message is normally preceded by a message indicating which volumefailed.


User Response: Repair the failed volume.

ANR0254E Error writing logical page logical page number(physical pagephysical pagenumber) to recovery log volumevolume name.

Explanation: An error has been encountered when attempting to write a page tothe specified recovery log volume.

System Action: If a mirrored volume is available, the failing volume is forced intothe offline state.



3.C

omm

onand

Platform

Specfic

Messages

ANR0255E Unable to write recovery log pagelogical page numberto any alternate copy.

Explanation: After a write error, the server is unable to write the desired page toanother mirrored volume because no other mirrored volume is in the synchronizedstate. This message is normally preceded by a message indicating which volumefailed.



ANR0256E Error writing physical page physical page numberto restart/checkpoint area ondatabase volumevolume name.




ANR0257E Error writing physical page physical page numberto restart/checkpoint area onrecovery log volumevolume name.




ANR0258E Unable to write complete restart/checkpoint information to disk.

Explanation: While writing restart/checkpoint information to disk, the serverencounters an error writing to a database or recovery log volume for which nosynchronized mirrored copy is available. This message is normally preceded by amessage indicating which volume failed.


User Response: Repair the failing volume.


ANR0259E Unable to read complete restart/checkpoint information from any database orrecovery log volume.

Explanation: During server restart, the server is unable to read a complete set ofrestart/checkpoint information from any of the defined database or recovery logvolumes.

System Action: Server restart is ended.

User Response: Ensure that all defined database and recovery log volumes areavailable for use by the server.

ANR0260I Database pagelogical page numbersuccessfully resynchronized.

Explanation: After detecting a partially-written database page, the server is able torewrite the page by using a synchronized mirror copy.



ANR0261I Recovery log pagelogical page numbersuccessfully resynchronized.

Explanation: After detecting a partially-written recovery log page, the server isable to rewrite the page by using a synchronized mirror copy.



ANR0265E Log disk processing failed: sufficient memory is not available.

Explanation: At server installation, the server is unable to process the server logdisks due to insufficient memory.

System Action: Server installation stops.

User Response: Restart the server installation process with more memoryavailable.

ANR0266E Database disk processing failed: sufficient memory is not available.

Explanation: At server installation, the server is unable to process the serverdatabase disks due to insufficient memory.


User Response: Restart the server installation process with more memoryavailable.


3.C

omm

onand

Platform

Specfic

Messages

ANR0267E Log volumevolume nameis not available.

Explanation: The specified volume cannot be found during installation.


User Response: Determine the reason the disk is unavailable, and correct theproblem. Restart the server installation process.

ANR0268E Database volumevolume nameis not available.

Explanation: The specified volume cannot be found during installation.


User Response: Determine the reason the disk is unavailable, and correct theproblem. Restart the server.

ANR0269E Process for Log volumevolume nameterminated - thread resource notavailable.

Explanation: During installation for the indicated volume, the server cannot start athread to service I/O requests.


User Response: Allocate additional storage to the server. For details, issue HELPMEMORY to display the information online or see “Appendix A. AllocatingAdditional Server Memory”. Restart the server installation process.

ANR0270E Process for Database volumevolume nameterminated - thread resource notavailable.

Explanation: During installation for the indicated volume, the server cannot start athread to service I/O requests.


User Response: Allocate additional storage to the server. For details, issue HELPMEMORY to display the information online or see “Appendix A. AllocatingAdditional Server Memory”. Restart the server installation process.

ANR0271E Maximum number of recovery log volumes exceeded.

Explanation: More recovery log volumes have been specified than the server canmanage.



User Response: Reduce the number of recovery log volumes specified. Restart theserver installation process.

ANR0272E Maximum number of database volumes exceeded.

Explanation: More database volumes have been specified than the server canmanage.


User Response: Reduce the number of database volumes specified. Restart theserver installation process.

ANR0285I Database page shadowing started using filefile name.

Explanation: The database page shadowing function was started. The file specifiedis used to store the shadowed database pages.



ANR0286W Database page shadowing using filefile namefailed to start.

Explanation: The database page shadowing function could not start. An error hasbeen encountered accessing the page shadow file specified.


User Response: Verify that there is enough space for the page shadow file. Thatpage shadow file requires approximately 65 kilobytes of space, if this space is notavailable a new location for the file should be specified.

ANR0287W Contents of the page shadow filefile nameare not valid.

Explanation: The database page shadowing function could not use the contents ofthe existing file. Restart recovery using this file is not possible.

System Action: The server attempts to start without having the database pageshadow file available.

User Response: The database page shadow file contents are not valid. This can becaused by: a partial write to the page shadow file itself, the file being manipulatedby a process outside of the server, the file being overlayed by a different file, or thefile could have been erased.


3.C

omm

onand

Platform

Specfic

Messages

ANR0288W One or more database pages in the last batch written is corrupt - contents ofdatabase page shadow file will be used to fix the page or pages.

Explanation: One or more pages from the last batch of pages written to the serverdatabase has been detected to be corrupt. The server will attempt to use the contentsof 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, istypically caused by a partial write. A partial write may occur when the server isbrought down external to normal server processing. If the server terminated withouta halt command being issued or if the machine the server is running on crashedunexpectedly, this may account for the partial write. Other possible causes of apartial write are a disk drive failure, improperly terminated scsi bus, or a failure in adevice controller. Please try to identify the cause of the partial write and take theappropriate action to prevent this from occurring in the future.

ANR0289W Damaged database pages were successfully replaced using contents of pageshadow file.

Explanation: The damaged database pages were replaced using the correspondingpages from the page shadow file. The pages were successfully replaced.

System Action: The server continues to restart.


ANR0290W Failure occurred attempting to replace one or more damaged database pagesusing the contents of the page shadow file.

Explanation: The damaged database pages could not be replaced using thecorresponding pages from the page shadow file.

System Action: The server continues to restart.


ANR0291E Error writing to db page shadow file - restart will be attempted.

Explanation: The server encountered an error writing to the database page shadowfile. The page shadowing for the server is currently disabled.

System Action: The server will attempt to restart the database page shadowing forthe server once a minute until it is restarted or until the server is halted.

User Response: Check the file specified as the database page shadow file. It maybe that there is not enough space for the file. If enough space is available, check thefilesystem, 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,the server will recovery and begin writing to the page shadow file again.

ANR0292W Database page shadow filefile namedoes not exist.

Explanation: The server attempted to use the page shadow file referenced but wasunable to open the file. The file does not exist.

System Action: The server will continue to operate and will attempt to create thisas a new database page shadow file.


ANR0300I Recovery log format started; assigned capacitycountmegabytes.

Explanation: Initial formatting of the server recovery log has started.

System Action: The log is formatted for use by the server.


ANR0301I Recovery log format in progress;countmegabytes ofcount.

Explanation: The amount of the server recovery log shown has been successfullyformatted.

System Action: Formatting continues.


ANR0302I Recovery log formatting took msecondsmilliseconds.

Explanation: Formatting of the recovery log has completed and took the numberof milliseconds shown.



ANR0303I Format rate: rate pages/second.

Explanation: During formatting, the formatter processed the number of pagesindicated each second.




3.C

omm

onand

Platform

Specfic

Messages

ANR0304I Page service time:rate ms.

Explanation: During formatting, the formatter required the number of millisecondsindicated to process each page.



ANR0305I Recovery log format complete.

Explanation: Formatting of the server recovery log completed successfully.



ANR0306I Recovery log volume mount in progress.

Explanation: During restart, the server is mounting required recovery log volumes.



ANR0307I Recovery log extend in progress;countmegabytes ofcount formatted.

Explanation: As a result of an EXTEND LOG command, the additional recoverylog pages are being formatted.

System Action: Formatting continues.


ANR0309I Recovery log extend terminated - process canceled.

Explanation: The process started as a result of an EXTEND LOG command andhas been canceled.

System Action: The EXTEND command is ended.


ANR0311I Recovery log reduce in progress;countmegabytes ofcountmoved.

Explanation: As a result of a REDUCE LOG command, the amount of data fromthe recovery log shown has been moved.

System Action: The REDUCE LOG command continues.



ANR0313I Recovery log reduce terminated - process canceled.

Explanation: The process started as a result of a REDUCE LOG command andhas been canceled.

System Action: The REDUCE command is ended.


ANR0314W Recovery log usage exceedsutilization percentage% of its assigned capacity.

Explanation: This message is issued to notify the administrator that the serverrecovery log utilization exceeds 90% or more of its assigned capacity.

System Action: Server operation continues.

User Response:¶ 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, orboth, before it fills completely. Refer to the DEFINE LOGVOL, and EXTENDLOG commands for more information on these operations.

¶ If the server is operating in ROLLFORWARD log mode:v backup the database, orv define a database backup trigger if one is not already defined, orv lower the database backup trigger if one is definedRefer to the DEFINE DBBACKUPTRIGGER or UPDATEDBBACKUPTRIGGER commands.

ANR0350I Recovery checkpoint started.

Explanation: During server initialization, the process of bringing the serverdatabase back to a state of consistency has begun.



ANR0351I Recovery checkpoint complete.

Explanation: During server initialization, the process of bringing the serverdatabase back to a state of consistency has completed successfully.




3.C

omm

onand

Platform

Specfic

Messages

ANR0352I Transaction recovery complete.

Explanation: During server initialization, the process of recovering any incompletetransactions has completed successfully.



ANR0353I Recovery log analysis pass in progress.

Explanation: During server initialization, the process of analyzing the serverrecovery log has begun.



ANR0354I Recovery log redo pass in progress.

Explanation: During server initialization, the process of committing incompletetransactions has begun.



ANR0355I Recovery log undo pass in progress.

Explanation: During server initialization, the process of rolling back incompletetransactions has begun.



ANR0356I Recovery log compression started.

Explanation: The process of removing unneeded data from the server recovery loghas begun.



ANR0357I Recovery log compression ended.

Explanation: The process of removing unneeded data from the server recovery loghas completed.




ANR0358E Database initialization failed: sufficient memory is not available.

Explanation: During server initialization, the server database fails initializationbecause sufficient server memory is not available.

System Action: Initialization fails.

User Response: Make more memory available to the server.

ANR0359E Database initialization failed: unable to read database restart record.

Explanation: During server initialization, the server database initialization failsbecause the required restart record cannot be read.



ANR0360E Database initialization failed: database size mismatch; LVM size =size,expected size =size.

Explanation: During server initialization, the server database initialization failsbecause the size of the database does not match its prior size.



ANR0361E Database initialization failed: error initializing database page allocator.

Explanation: During server initialization, the server database initialization failsbecause the page allocator cannot be started.



ANR0362W Database usage exceedsutilization percentage% of its assigned capacity.

Explanation: This message is issued to notify the administrator that the serverdatabase utilization exceeds 80% or more of its assigned capacity.


User Response: Depending upon the size of your database, add database volumes,or extend the database, or both, before it fills completely. The server expiration


3.C

omm

onand

Platform

Specfic

Messages

process may also free up database space making it available to other serverprocesses. Refer to the EXPIRE INVENTORY, DEFINE DBVOL, and EXTENDDB commands for more information on these operations.

ANR0363I Database was automatically upgraded to the server program level.

Explanation: This message is issued to notify the administrator that the serverdatabase was automatically upgraded to the current server program level. Theupgrade is performed when the UPGRADEDB parameter is specified at serverstart-up and the server is started over a database that was written by a down-levelversion of the server program.


User Response: None. The UPGRADEDB parameter does not need to be specifiedduring future server start-ups.

ANR0380W The database buffer pool recovered from an overcommit ofnumber of pagespages. Consider increasing your buffer pool size bykilobytes neededkilobytesunder current server load.

Explanation: During normal processing, additional buffer pool space is requiredbeyond that specified in the BUFPOOLSIZE in the server options file. Theadditional kilobytes of buffer pool space that are required are indicated in themessage.

System Action: Server operation continues; the additional buffer pool space isobtained from available server memory.

User Response: If the current server load is typical, consider increasing the sizespecified for your BUFPOOLSIZE option by the number of kilobytes specified inthe message. To do this, you must halt the server, change the options file, and thenrestart the server.

ANR0381I Bufferpool statistics were successfully reset.

Explanation: Bufferpool statistics, such as the Cache Hit Ratio, have been reset bythe RESET BUFPOOL command.


User Response: The QUERY DB command (FORMAT=DETAILED) can be usedto to display the current values for the buffer pool statistics.

ANR0382I The database maximum utilization statistic was successfully reset.

Explanation: The database maximum utilization statistic has been reset by theRESET DBMAXUTILIZATION command to the current utilization.



User Response: The QUERY DB command (FORMAT=DETAILED) can be usedto display the current value for the maximum utilization.

ANR0383I The recovery log maximum utilization statistic was successfully reset.

Explanation: The recovery log maximum utilization statistic has been reset by theRESET LOGMAXUTILIZATION command to the current utilization.


User Response: The QUERY LOG command (FORMAT=DETAILED) can beused 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 RESETLOGCONSUMPTION command.


User Response: The QUERY LOG command (FORMAT=DETAILED) can beused to display the current value for recovery log consumption.

ANR0385I Could not free sufficient buffers to reach reduced BUFPoolsize.

Explanation: A reduction in the Data Base 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 reductionthat could be achieved is in effect. The new bufpoolsize is written to the options filefor use on the next server startup.


ANR0386I The BUFPoolsize has been changed tobuffer pool size.

Explanation: The BUFPoolsize option has been changed to the indicated value.



ANR0390W A server database deadlock situation has been encountered: lock request fortransaction transaction IDwill be denied to resolve the deadlock.

Explanation: The server detected a deadlock situation between a number ofprocesses attempting to access database information. A lock request for one of the


3.C

omm

onand

Platform

Specfic

Messages

processes will be denied to resolve the database deadlock. When server processesencounter a database deadlock, they usually reattempt the function that was inprogress when the deadlock was encountered. Not all process can explicitly re-tryan operation. For example, migration and reclamation will eventually retry.However, something like a delete volume run in a macro will only retry if the deletecommand is reissued either in the macro or the command line.

System Action: A lock request fails for one of the deadlocked processes. Serveroperation continues.

User Response: If a process can retry (like migration), then monitor the re-tryattempt to see if it succeeds or not. If it fails, contact a service representative. If theprocess or command is not able to retry on it’s own, then reissue the command ormacro that caused the action to occur. If it fails again, contact a servicerepresentative for further assistance to better isolate the deadlock condition.

ANR0400I Sessionsession numberstarted for node node name(client platform)(communication method).

Explanation: A new client session has been initiated by the specified node. Thesession number, client platform type and communication method used by thissession are included in the message.

System Action: The server begins a communications session to service the clientnode.


ANR0401I Sessionsession numberstarted for node node name(client platform)(communication 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 thissession are included in the message.

System Action: The server begins a communications session to service the clientnode.


ANR0402I Sessionsession numberstarted for administrator administrator ID(administrator’s platform) (communication method).

Explanation: A new administrator client session has been initiated by the specifiedadministrator. The session number, administrator’s platform type and communicationmethod used by this session are included in the message.

System Action: The server begins a

Tivoli Storage Manager - Computers-itcomputers-it.com/downloads/tsm_41_messages.pdf · Tivoli...

Documents

Transcript of Tivoli Storage Manager - Computers-itcomputers-it.com/downloads/tsm_41_messages.pdf · Tivoli...